Description of problem: Choosing a screensaver crashes the Gnome session. Version-Release number of selected component (if applicable): rss-glx.i686 0.9.1.p-2.fc13 rss-glx-gnome-screensaver.i686 0.9.1.p-2.fc13 How reproducible: Every time (on my PC). Steps to Reproduce: 1. Install rss-glx-gnome-screensaver on Fedora 13. 2. Go to System/Preferences/Screensaver 3. Click on a screensaver at the list on the left to choose it. Actual results: The Gnome session crashes and one goes back to the login screen. Expected results: The screensaver gets chosen to be used next time. Additional info: RSS is my favourite screensaver suite and it works flawlessly in Fedora 12.
Well, rss is not the only screensaver with issues. I installed tempest-gnome-screensaver.i686. I can choose that screensaver, however when after the screensaver activates I touch the keyboard or mouse to go to normal mode, the Gnome session closes. This is similar to the rss issue. gnome-screensaver-frogs seems to work well, so I will be looking at frogs for a while!
This seems fixed, somewhat. It doesn't crash/close the gnome session for me anyways, but the screensavers do not work (shows just black screen in both previews), except for the frog one... rss-glx stuff is all broken right now for me.
Do any other 3D programs work for you?
I added a module to xorg.conf a couple of weeks ago which fixed some other opengl-related problems I was having (not showing direct rendering in glxinfo), so it must have also fixed this.
(In reply to comment #3) > Do any other 3D programs work for you? Which program in particular are you talking about? I do not play computer games and my PC is old, but as I said, RSS works flawlessly for me in F12 (though I did download the source package and built it myself for my arch for better performance, which is something that I do for about 20 other packages, sort of Gentoo approach). I think the RSS problem might actually be in the Intel video driver, or in its interaction with RSS, as there is another outstanding bug, compiz not working, that also affects me and other people with Intel video: https://bugzilla.redhat.com/show_bug.cgi?id=595924 My hardware is listed below: 00:00.0 Host bridge: Intel Corporation 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02) 00:06.0 System peripheral: Intel Corporation 82865G/PE/P Processor to I/O Memory Interface (rev ff) 00:1d.0 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1 (rev 02) 00:1d.1 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2 (rev 02) 00:1d.3 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #4 (rev 02) 00:1d.7 USB Controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev c2) 00:1f.0 ISA bridge: Intel Corporation 82801EB/ER (ICH5/ICH5R) LPC Interface Bridge (rev 02) 00:1f.1 IDE interface: Intel Corporation 82801EB/ER (ICH5/ICH5R) IDE Controller (rev 02) 00:1f.3 SMBus: Intel Corporation 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) 00:1f.5 Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) 01:02.0 Modem: Intel Corporation FA82537EP 56K V.92 Data/Fax Modem PCI (rev 04) 01:08.0 Ethernet controller: Intel Corporation 82562EZ 10/100 Ethernet Controller (rev 02)
(In reply to comment #4) > I added a module to xorg.conf a couple of weeks ago which fixed some other > opengl-related problems I was having (not showing direct rendering in glxinfo), > so it must have also fixed this. Which module are you talking about? And did you just download it from Fedora repo or did you build Xorg yourself from upstream sources or Fedora source package?
None of the above. A different libglx module that was installed into a path below the default path for libglx.
@Thomas: what sort of video hardware to you have? Intel?
Nvidia To be brutally honest, nouveau/gallium3d just doesn't cut it wrt wine and 3d gaming so I installed the nvidia binary driver from rpmfusion. But I then didn't rename the libglx.so provided by xorg at /usr/lib64/xorg/modules/extensions. So what I did recently was to rename that file, so that the libglx.so that is in /usr/lib64/xorg/modules/extensions/nvidia would get loaded instead, which is what fixed the problem.
These issues sound like problems with 3D acceleration in your respective video drivers. I'll change the component to xorg-x11-drv-intel since that is what the original reporter uses. Thomas, feel free to open up a bug against xorg-x11-drv-nouveau.
Considering that this issue affects at least two architectures (Intel and Nvidia), and that Thomas reported that the problem disappeared for him using a different libglx.so, and that said library comes in Fedora package xorg-x11-server-Xorg: would it not be better to assign this issue - provisionally - to this package rather than the Intel driver?
My issue is a separate bug. I have not ever experienced the gnome session closing. Nils is correct.
Whether that is due to me coming into this much after the release where this was reported or whether it is because it was fixed, now that I think about it, is relevant though. Of course the only way to know for certain is for me to try downgrading to that older version. I'd rather like to not have to do that.
I think Thomas' issue was that his 3rd party driver and the system libglx.so are incompatible (which is really a packaging problem on behalf of the 3rd party driver), not that that the system libglx.so has bugs which caused it to malfunction.
Yep, though it's not a packaging problem because every xorg update puts it's own libglx.so in front of the driver-provided one, with good reason: Nvidia actually overwrites the system one, leaving you screwed if there is some problem either in the driver or in xorg that causes the 2 to be totally incompatible; so rpmfusion packaged it so that that is no longer the case.
OK, so it seems to be Intel specific. This would explain why there are only two users posting comments on this thread. If it affected all architectures I would expect to be more. Unless RSS is not very popular, I have no idea about how popular it is, I only know I like it myself. In any case, there are bigger problems in the world than a screen-saver not working!
(In reply to comment #5) > (In reply to comment #3) > > Do any other 3D programs work for you? > > Which program in particular are you talking about? Traditionally I use /usr/lib*/mesa/teapot from mesa-demos package. Does it work for you? Also, please add drm.debug=0x04 to the kernel command line, restart computer, and attach * your X server config file (/etc/X11/xorg.conf, if available), * X server log file (/var/log/Xorg.*.log) * output of the dmesg command, and * system log (/var/log/messages) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Created attachment 455227 [details] dmesg output
Created attachment 455229 [details] /var/log/messages (edited)
Created attachment 455230 [details] Xorg.0.log.old (this file shows the X crash at line 923)
(In reply to comment #17) > > Which program in particular are you talking about? > > Traditionally I use /usr/lib*/mesa/teapot from mesa-demos package. Does it work > for you? Those are cool demos. I tried a few (tunnel, engine, textures, fire, teapot) and all worked well. > Also, please add drm.debug=0x04 to the kernel command line, restart computer, Done. > and attach > > * your X server config file (/etc/X11/xorg.conf, if available), There is none. > * X server log file (/var/log/Xorg.*.log) I attached just the relevant file (dated just before the crash, which I reproduced today). The backtrace is near the bottom. > * output of the dmesg command done > * system log (/var/log/messages) Done with some editing (left relevant stuff at the bottom). The reproduced crash happened at 9:40 today.
After the test above (with the reproduced issue whereby X stops), I forgot to change the configured screensaver back to one that works, so later on after some inactivity the screensaver kicked in with my configured screensaver (from RSS). The image was fine (I had chosen drempels) the problem is that when I touched a key on my keyboard to stop the screensaver, X and the keyboard froze, so I had to power off my PC.
Backtrace: [ 115.582] 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x809d6a0] [ 115.582] 1: /usr/bin/Xorg (0x8047000+0x565e5) [0x809d5e5] [ 115.582] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0x97440c] [ 115.582] 3: /usr/bin/Xorg (miDoCopy+0x2e) [0x8189c83] [ 115.582] 4: /usr/lib/xorg/modules/drivers/intel_drv.so (0x3ea000+0x37b63) [0x421b63] [ 115.582] 5: /usr/bin/Xorg (0x8047000+0xcc3ae) [0x81133ae] [ 115.582] 6: /usr/lib/xorg/modules/drivers/intel_drv.so (0x3ea000+0x33a10) [0x41da10] [ 115.582] 7: /usr/lib/xorg/modules/drivers/intel_drv.so (0x3ea000+0x34825) [0x41e825] [ 115.582] 8: /usr/lib/xorg/modules/drivers/intel_drv.so (0x3ea000+0x2ed31) [0x418d31] [ 115.582] 9: /usr/lib/libdrm.so.2 (drmHandleEvent+0xf1) [0x7eb8921] [ 115.582] 10: /usr/lib/xorg/modules/drivers/intel_drv.so (0x3ea000+0x2ec93) [0x418c93] [ 115.582] 11: /usr/bin/Xorg (WakeupHandler+0x4b) [0x806fae0] [ 115.582] 12: /usr/bin/Xorg (WaitForSomething+0x19b) [0x809c8b7] [ 115.582] 13: /usr/bin/Xorg (0x8047000+0x468cf) [0x808d8cf] [ 115.583] 14: /usr/bin/Xorg (0x8047000+0x1b635) [0x8062635] [ 115.583] 15: /lib/libc.so.6 (__libc_start_main+0xe6) [0x126cc6] [ 115.583] 16: /usr/bin/Xorg (0x8047000+0x1b231) [0x8062231] [ 115.583] Segmentation fault at address 0x80 [ 115.583] Fatal server error: [ 115.583] Caught signal 11 (Segmentation fault). Server aborting [ 115.583]
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.