|
Bugzilla – Full Text Bug Listing |
| Summary: | sometimes KDE is not loaded during boot process | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | F. Seidel <dgfs> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED WORKSFORME | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | eich, hvogel, stefan.brandner |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | Customer | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
The file /var/log/messages
The file /var/log/kdm.log All needed log files |
||
|
Description
F. Seidel
2005-10-21 21:20:54 UTC
Please have a look at http://www.opensuse.org/Submit_a_bug#Reporting_a_Bug All SUSE Linux OSS bugs should go into the product SUSE LINUX 10.0 or newer, because SUSE Linux is based on the SUSE Linux OSS code base. Always choose the right product when reporting a bug Out of memory for KDE display manager? Please report how many RAM this system includes? I want to see /var/log/kdm.log /var/log/messages and ~/.xsession-errors - do you use autologin or not? The system has 1GB of RAM. I use autologin. The files are appended, except ~/.xsession-errors. I do not found this file. Created attachment 55340 [details]
The file /var/log/messages
Created attachment 55341 [details]
The file /var/log/kdm.log
Oct 18 10:05:47 linux kdm[5970]: X server startup timeout, terminating Oct 18 10:05:52 linux kdm[5970]: X server for display :0 can't be started, session disabled and it always shows together with vmnet-dhcpd - are you saying you run vmware? What is vmnet-dhcpd? I never heared of it. Unfortunately it's impossible to say what happens there as the kdm.log doesn't have timings. We would need the logs if the session failed. i read the both files and i also see the startup timeout. But why is the startup timed-out? That's the interesting question. Yes, i run vmware. I don't know what vmnet -dhcpd is. I heard it the first time. Which logs you exactly needs if the session failed? tar up messages, kdm.log and Xorg.* from /var/log the next time your session fails - before you rapair it. Created attachment 57399 [details]
All needed log files
Sorry for my late response.
Here are the files.
Unfortunately the log files are still inconclusive. All logfiles you have sent indicate that there is no problem and everything is good. Maybe you should try the following: Before you do the 'init 3; init 5' step, please check the timestamp of your XOrg.0.log file and see if it was generated *after* the last boot. Please do the same for the kdm.log file. There may be a problem with the 3D fireglx kernel module. Would you please turn off 3D (remove the line which loads the DRI module in the "modules" section of your config file) and see if the problem still occurs. I have exactly the same problem. I get exactly the same message as Stephan Kulow. Mar 18 18:37:45 Popper kdm[7034]: X server startup timeout, terminating Mar 18 18:37:53 Popper kdm[7034]: X server for display :0 can't be started, session disabled When I now start kdm manually I get the message: Mar 18 18:39:29 Popper kdm[7803]: Can't lock pid file /var/run/kdm.pid, another xdm is running (pid 7034) So after deleting /var/run/kdm.pid kde starts fine with kdm. Since kdm was never really started kdm.log does not get any updates. As soon as it is restarted eg. with init 3 and init 5 xorg.log and kdm.log get data. I checked the timings of the log files. I found a workaround for the problem. In /etc/init.d/rc5.d I renamed K19earlykdm to K22earlykdm. Then kdm is started later in the boot process. This works so far. no idea what's causing it, but it seems a very rare problem and I can't fix such ;( |