I notice a strange bug with the new version of xorg packages ( 1.13.0 ) if I use the "startx" method for running KDE4.9.2, description of this weird bug : 1) I type "startx -- vt1" in a tty1 console 2) KDE4 loads successfully 3) I run a 3D game ( or glxgears ) 4) I choose the "logout" menu in KDE4 5) then I type again "startx -- vt1" to start again KDE4 6) KDE4 loads but if I move the mouse I get a black screen, but I can see the HDD led continues to light this bug doesn't occur if I start KDE with KDM, the problem occurs only with startx when I decide to re-run the startx command ( first time it's Ok, but the second attempt brings the bug ), the logs ( Xorg.log, dmesg ) don't bring a clue, all seem ok my system: - archlinux 32 bits - laptop with pentium 4 2.4 Ghz 1.2 Gb ram - SIS645DX chipset - ati radeon 9000 AGP ( I use DRI2 with KMS, xf86-video-ati driver 1:6.14.6-2 )
Please always attach the Xorg.0.log and dmesg output corresponding to the problem.
Created attachment 68581 [details] dmesg file when the bug occurs dmesg file when the bug occurs
Created attachment 68582 [details] Xorg.0.log file when the bug occurs Xorg.0.log file when the bug occurs
(In reply to comment #3) > Created attachment 68582 [details] > Xorg.0.log file when the bug occurs The end of this log shows that the X server terminated cleanly. Was it really captured from an X server showing the black screen? After you've logged out the first time, does sudo lsof /dev/dri/card0 show any processes still using the DRI device?
(In reply to comment #4) > (In reply to comment #3) > > Created attachment 68582 [details] > > Xorg.0.log file when the bug occurs > > The end of this log shows that the X server terminated cleanly. Was it > really captured from an X server showing the black screen? > yes, that's why it's a weird bug because logs files seem ok, > After you've logged out the first time, does > > sudo lsof /dev/dri/card0 > > show any processes still using the DRI device? no, when I type "sudo lsof /dev/dri/card0" it shows nothing the bug only occurs with startx, if I use KDM ( or Slim ) for login ( graphical login ) I have no black screen, all is ok
Created attachment 68587 [details] a copy of the file ".xsession-errors a copy of the file ".xsession-errors, it shows some errors like "X Error: BadDrawable (invalid Pixmap or Window parameter) 9 Major opcode: 72 (X_PutImage) Resource id: 0x0" but I don't know if these errors are related to the bug ( black screen after a second attempt of using startx )
(In reply to comment #5) > > The end of this log shows that the X server terminated cleanly. Was it > > really captured from an X server showing the black screen? > > yes, that's why it's a weird bug because logs files seem ok, I'm still confused about why the X server with the black screen terminated cleanly. Did you manage to log out of the second session somehow? At what point exactly did you grab the log file?
(In reply to comment #7) > (In reply to comment #5) > I'm still confused about why the X server with the black screen terminated > cleanly. Did you manage to log out of the second session somehow? At what > point exactly did you grab the log file? when the black screen occurs ( when I move the mouse after KDE4 has finished to load ) I hit "ctrl-alt-backspace" in order to kill X and to get a tty1 console the screen is still black but I can type some commands ( in blind mode ) in order to copy /var/log/Xorg.0.log to my /home/folder
I discover also another problem since the update of ati-dri and xorg packages on my archlinux installation, I don't know if this is related to this bug but I have opened a bug here : https://bugs.freedesktop.org/show_bug.cgi?id=56038
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/issues/46.
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.