|
Bugzilla – Full Text Bug Listing |
| Summary: | Xsession crashes after login | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Ulrich Derenthal <uli.2001> |
| Component: | KDE | Assignee: | E-mail List <kde-maintainers> |
| Status: | RESOLVED NORESPONSE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Final | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
Xorg.0.log after the second (successful) login
Xorg.0.log.old .xsession-errors after crash after login .xsession-errors after 1st crash after next reboot .xsession-errors after 2nd crash after next reboot xsession-errors after booting into runlevel 3 and logging in as user Xorg.0.log after booting into runlevel 3 and logging in as user |
||
|
Description
Ulrich Derenthal
2007-11-17 13:45:59 UTC
Created attachment 183789 [details]
Xorg.0.log after the second (successful) login
Created attachment 183790 [details]
Xorg.0.log.old
This is the file /var/log/Xorg.0.log.old after the second (successful) login, so I guess that this is the Xorg.0.log from the first login try when the X-server crashed.
--- Xorg.0.log +++ Xorg.0.log.old -BOGUS LENGTH in write keyboard desc, expected 4992, got 4996 -BOGUS LENGTH in write keyboard desc, expected 5312, got 5316 -Synaptics DeviceOn called -(--) Mouse[3] auto-dev sets device to /dev/input/event2 (waited 0 msec) -(**) Option "Device" "/dev/input/event2" -(--) Mouse[3] touchpad found -(II) Open ACPI successful (/var/run/acpid.socket) -(II) Mouse[1]: ps2EnableDataReporting: succeeded +(II) fglrx(0): Shutdown CMMQS +(II) fglrx(0): [drm] removed 1 reserved context for kernel +(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0x2000 at 0xb7c07000 Could you also attach your ~/.xsession-errors right after the login failure? >Could you also attach your ~/.xsession-errors right after the login failure?
Could you reopen once you can provide the requested information? Thanks.
Created attachment 185634 [details]
.xsession-errors after crash after login
Created attachment 185635 [details]
.xsession-errors after 1st crash after next reboot
Created attachment 185636 [details]
.xsession-errors after 2nd crash after next reboot
I had the following behavior recently:
After one reboot, I could login without a crash.
Ater the second reboot, I got a crash first (see the first .xsession-errors) and then could login in the second try.
After the third reboot, I got a crash (second .xsession-error) and then in the second try another crash (third .xsession-errors) and then the third try to login worked.
After each crash, I did
cp .xsession-error .xsession-errors-copy
(resp. ...2 resp. ...3) on the command line in my home directory, and I attached the files.
Reopening after attaching some files. This seems to be a KDE isssue. Reassigning. What makes you think so? The only thing I can see in those ~/.xsession-errors is IO error which seems to be from X crashing. Why I think so? Because there is no Xserver crash (see comment #2). ~/.xsession-errors is full of KDE application errors. Please investigate. I don't have the knowledge to do so. Maybe kdm crashed. Would make sense. Please log in text mode, run "init 3" and "startx". Are there any problems when you start KDE this way? After "init 3", it says "Shutting down service kdm" and "runlevel 3 has been reached" and some other (normal looking) lines before.
After "startx" (also as root), it says:
xauth creating new authority file /root/.serverauth.3639
Fatal server error:
Server is already active for display 0
If this server is no longer running, remove /tmp/.X0-lock
and start again.
Then I cannot do anything else (when I press keys, the corresponding letters appear on the screen; ctrl+c does not do anything; pressing ctrl+alt+f7, the screen does not change, but now when I press more keys, they do not appear on the screen; pressing ctrl+alt+del causes a beep, some harddisk activity, but no screen activity, and after a while the computer restarts, i.e. this combination seems to have caused a shutdown and reboot as expected, but with a frozen screen).
You're not supposed to have any X running by the time you do startx. Try booting directly to runlevel 3. Also, don't run startx as root but as the user. I did not have X running because the first thing I did was "init 3". Now I booted directly into runlevel 3, logged in as a user and typed startx. It worked, but I did not try several times. However, I think that lately it never worked immediately after booting into runlevel 5, so this might be an improvement. I am attaching Xorg.0.log and .xsession-errors. Created attachment 191868 [details]
xsession-errors after booting into runlevel 3 and logging in as user
Created attachment 191869 [details]
Xorg.0.log after booting into runlevel 3 and logging in as user
You've been of course asked to provide log files for the case when the error occurs - what do you think can be done with files that don't show any problem? I don't know - maybe to compare them with the files that show problems? Anyway, booting into runlevel 3 and doing "startx" as a user does not show any problems when trying it 3 times. Switching back to booting into runlevel 5, the problem shows up immediately again. - Does the problem exist also if you use KDM to start something else than KDE (GNOME, failsafe session, whatever)? - Does the problem exist also if you login into failsafe session first and then launch KDE using 'startkde 2>/tmp/kde.txt'? If there's a problem in that case, please attach /tmp/kde.txt. please reopen when you can provide the information requested above |