Red Hat Bugzilla – Bug 222643
GLblur demo make gnome desktop crash
Last modified: 2008-05-07 04:59:07 EDT
Description of problem: When running the GLblur demo on my Acer Aspire 1700 in most cases the gnme desktop (I did not test KDE) crashes and the login-screen reappears. Version-Release number of selected component (if applicable): all versions for FC6 How reproducible: I only found it up to now on my laptop. Steps to Reproduce: 1.upgrade to FC6 and xscreensaver fc6 version 2. 3. Actual results: when GLblur runs the gneme desktop may crash Expected results: a nice demo, which runs smoothly Additional info:
Well, these types of bug report (i.e. a hack broke my X server) needs some more information, especially when you tried GL hacks. In most cases the cause is not xscreensaver hack but X server or the tipset you are using if "X server crashed" as you said. Please check: http://www.jwz.org/xscreensaver/faq.html#server-crash If the cause is really /usr/libexec/xscreensaver/glblur, you may gain some information using gdb after you install xscreensaver debuginfo rpm. Would you try it?
Also, worth mentioning your video hardware, and which X driver you're using.
The hard-ware : Acer 1700 laptop grahics card: sis m650 I use the standard driver for this card which comes with FC6. I'm up to date installing updates. I;m pretty sure GLblur is the only problem, since : 1) I saw it twice go when running this mode 2) Even when I tried the small demo window in the "setup-window" it crashed the X-session 3) disabling GLblur and leaving all the other modes in makes the crash disappear in several overnight tests. I could do the gdb part ( how should I run this? any suggestion?) If you are right and it is an X-bug, which only appears very rarely to whom should we relay this bug? Jouk
Well, A. First try this. If this is due to glblur bug, some message should be gained. A-1. # yum -y install xscreensaver-debuginfo mesa-debuginfo (note: Both packages are _very_ large!! xscreensaver-debuginfo: 12.8M mesa-debuginfo : 72.1M for i386) A-2 # yum -y install gdb A-3 $ gdb /usr/libexec/xscreensaver/glblur A-4 (gdb) run .... If glblur crashes, then: A-5 (gdb) bt And please attach (not copy/paste) the result. .. When X crashes after this: B-1 Please attach * /etc/X11/xorg.conf * /var/log/Xorg.0.log ... and I will ask X maintainers for advice.
Doing the above make the session crash within a minute. I attached the required files
Created attachment 145983 [details] /etc/X11/xorg.conf
Created attachment 145984 [details] /var/log/Xorg.0.log
Once switching to X server. Dear X maintainers, any advice?
I suspect this is another instance of the various renderbuffer bugs in Mesa atm. If you could attach the X log from the actual crash that would be helpful, as it should contain a backtrace at the end.
Created attachment 152119 [details] After the crash I logon in the Gnome-desk top and find this file in /var/log
Created attachment 152120 [details] after crash and relogon in gnome-desktop
Hope these log files will lead you to the problem
After some updates, since about 2 weeks things became worse : All GL modes of XscreenSaver started to "flicker" (even in the small "demo" window) and all have the potential to crash the gnome session. Jouk
Last weekend I upgraded the machine to Fedora 7. Since then I could not reproduce the crash and the GL-demos work fine again. Jouk
Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
This bug has been in NEEDINFO for more than 30 days since feedback was first requested. As a result we are closing it. If you can reproduce this bug in the future against a maintained Fedora version please feel free to reopen it against that version. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp
According to comment #14 resolution should be "current release"