I am using 2 user accounts simultaneously : one to work and one to go on the web, etc. I am switching from one session to the other using the keys ctrl-alt-F7 / ctrl-alt-F8. On versions 6.8.1 and 6.8.2 X freezes when beginning to display the new session : no more keyboard (numlock doesn't work), sometimes ctrl-alt-del enables to reboot "cleanly". ctrl-alt-backspace to kill X does not work. This is typically a bug on the driver : I had the problem with XFree with the first versions of the driver. I have a Radeon 9200SE * Slackware 10.0 - Xorg 6.7 (Release Date: 18 December 2003 - X Protocol Version 11, Revision 0) !! OK !! * Slackware 10.1 - Xorg 6.8.1 : PROBLEM * Slackware 10.1 - Xorg 6.8.2 (binary package) : PROBLEM * Slackware 10.1 - Xorg 6.8.2 (compiled with the Slackbuild) : PROBLEM Back to 6.7: * Slackware 10.1 - Xorg 6.7 (binary package of Slack 10.0) : !! OK !! There is a bug on the 2 last versions of Xorg but I had no better perfs (on single display, with glxgears) than with the 6.7 version... Thanks
Submitter: Please try the latest release.
Hello Thomas Hood, I don't know if there is a new source version. But I installed the latest slackware (10.2 released the 14 september 2005). I always have the problem...
And I do not have the problem with the option : Option "NoAccel" "yes" But it is not very interesting without acceleration....
Have you tried with the latest slack packages ie 6.9.0?
No. I had no time to try. Info : when I sent this bug my kernel was not compiled with the shared memory (/dev/shm) support.
Please attach (as opposed to paste) config and log files.
Created attachment 5302 [details] xorg.conf Actual xorg.conf. But it was VERY probably the same when I had the crashes (I made many tries...)
I have no log file beacause the PC freezed. I had to do on/off... But if you do not have the problem on your own computer, I don't know how you can suppress a bug that do not exist for you...
You can perform a remote backtrace by logging in remotely via ssh, attach gdb to the X process and try to catch the crash. In gdb, issue the bt command to receive a full backtrace.
I have only one computer at home... And I have no time to do tries for you (that's why I didn't try the package 6.9.0 of the slackware). I am running the 6.7 version which has not the bug. As soon as I have more time I will try the 6.9 version and post here the result of the test.
It's better to remount the filesystem containing /var/log/Xorg.0.log with the sync flag anyway, e.g. mount -o remount,sync / Does it also happen if you don't enable the DRI or don't specify Option "GARTSize"?
> Does it also happen if you don't enable the DRI or don't specify Option "GARTSize"? It also happened with or without "GARTSize" option. I can't remember what happened without DRI...
Just disable dri in xorg.conf and see if you can reproduce the bug.
Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status. Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.