abrt detected a crash. Comment: Just stop switching from compiz to standard in desktop effects Attached file: backtrace cmdline: compiz --ignore-desktop-hints glib gconf gnomecompat component: compiz executable: /usr/bin/compiz kernel: 2.6.31.5-117.fc12.x86_64 package: compiz-0.8.2-19.fc12 rating: 1 reason: Process was terminated by signal 11
Created attachment 367854 [details] File: backtrace
I can reproduce it with the following steps every time: 1. In fusion-icon set Window Manager to Metacity 2. Open Desktop Effects, enable Compiz and accept changes. 3. Open Desktop Effects again and set to Standard. ABRT reports this crash.
I received this crash when doing the opposite. I'd just installed the latest Nvidia driver and was turning on desktop effects and it crashed without the "accept settings" popping up.
Yup. I have the NVidia driver installed as well. I can't use the nouveau driver because I need stable 3D support...
This morning, I used the /sbin/new-kernel-pkg script to create a new initramfs file. The new initramfs does not load the nouveau driver and now compiz works fine using just the NVidia driver.
What steps did you take using the new-kernel-pkg script?
The first thing I did was save off my initramfs file (as root): cd /boot mv initramfs-2.6.31.5-127.fc12.x86_64.img initramfs-2.6.31.5-127.fc12.x86_64.img.SAVE And then ran the following: /sbin/new-kernel-pkg --package kernel --mkinitrd --dracut --depmod --install 2.6.31.5-127.fc12.x86_64 Finally, I rebooted and problem solved...
Didn't fix it for me I'm afraid. Just did the steps mentioned above to the letter, rebooted and still it won't apply the compiz 3D effects. This is my grub.conf though: title Fedora (2.6.31.5-127.fc12.x86_64) root (hd0,5) kernel /vmlinuz-2.6.31.5-127.fc12.x86_64 ro root=/dev/mapper/vg_xwing-LogVol01 LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=uk rhgb quiet nouveau.modeset=0 initrd /initramfs-2.6.31.5-127.fc12.x86_64.img I made the that change "nouveau.modeset=0" based on what people had said regarding installing the Nvidia drivers online. It also wouldn't load the desktop (Gnome Metacity) until I did that.
Lee, I'm using the NVidia driver from rpmfusion. It blacklists the nouveau driver. Is the nouveau driver still loading for you? If so, that could be your problem...
Just FYI, the crash I triggered happened when using the OSS radeon driver so it's not nvidia specific issue.
Thank you for taking the time to report this bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash, because there are no debugging symbols loaded (probably abrt failed to load them). Unfortunately, we cannot use this backtrace. Closing as INSUFFICIENT_DATA.
What steps _CAN_ I take to provide you all with SUFFICIENT_DATA to troubleshoot this problem. As of now, every time switch between compiz to standard, I get abrt jumping out at me complaining about a crash. It's a pity to let this go as it can be reproduced at will.
(In reply to comment #10) > Lee, > > I'm using the NVidia driver from rpmfusion. It blacklists the nouveau driver. > Is the nouveau driver still loading for you? If so, that could be your > problem... I manually added the nouveau driver to the blacklist file (In reply to comment #10) > Lee, > > I'm using the NVidia driver from rpmfusion. It blacklists the nouveau driver. > Is the nouveau driver still loading for you? If so, that could be your > problem... I manually added the nouveau driver to the blacklist file(In reply to comment #12) > Thank you for taking the time to report this bug report. Unfortunately, that > stack trace is not very useful in determining the cause of the crash, because > there are no debugging symbols loaded (probably abrt failed to load them). > > Unfortunately, we cannot use this backtrace. > > Closing as INSUFFICIENT_DATA. We are providing as much data as we can and working through this problem actively and its just been closed? Help us to help you, don't just close things without giving us a chance to assist further.
The response to one of my other bugs: id=537259 by Martin Stransky is much more helpful: > Unfortunately we're missing any debug-info here. Please install debuginfo > packages (by debuginfo-install xulrunner firefox) and try to catch the crash > again...
Ironically, I reported this bug using the automatic bug reporting tool that popped up when Compiz crashed. What's even more ironic is that the problem is now fixed for me by eliminating the load of the nouveau driver. Let me see if I can come up with a version of Compiz that has the debug symbols in it. If I can, I'll try to reproduce the problem, attach the stack trace, and reopen this bug...
Running debuginfo-install xulrunner firefox compiz for me just grabbed 49 packages at 140MB or so. Anyone else having mirror problems? (off topic, sorry)
Oddly, it works fine now. Maybe an update has resolved it?
here it's fixed, too. I've enabled testing-updates.
It's not fixed for me after today's update. I've just triggered this isse again.
I've installed the necessary debuginfo rpms with: debuginfo-install compiz I've also put my system back to the state where the problem occurs and I can now reproduce. Unfortunately, even with the debuginfo RPMs installed, the stack traces don't have any more useful information. It looks like the compiz debuginfo RPM installs a debug version of the executable and puts it in /usr/lib/debug/usr/bin/compiz.debug but it won't run (even with executable permissions). I've tried manually killing the metacity window manager and then starting compiz with: /usr/bin/compiz --ignore-desktop-hints glib gconf gnomecompat --replace After several minutes, compiz starts and I have a 3D desktop. This makes me wonder if the desktop-effects executable doesn't do a kill -6 on the compiz executable which creates the core file. This is, of course, only speculation on my part but it would explain things. For me, with the nouveau removed, the compiz executable starts immediately using only the NVidia driver. With the nouveau driver installed in the kernel along with the NVidia driver, compiz takes several minutes to come up. But, it does come up eventually.
(In reply to comment #21) > For me, with the nouveau removed, the compiz executable starts immediately > using only the NVidia driver. With the nouveau driver installed in the kernel > along with the NVidia driver, compiz takes several minutes to come up. But, it > does come up eventually. Have you installed the NVidia driver and then blacklisted the nouveau driver? Don't know if this helps at all but here are all my installed rpms: http://www.leenukes.co.uk/documents/rpms and my blacklist.conf file: http://www.leenukes.co.uk/documents/blacklist
since there are now quite a few users on cc on this, can we re-open this as an active bug or is there a final solution?
I'm getting the same crash using the xorg-x11-drv-intel package and booting my system with "nomodeset". Same backtrace, I'm enabling updates-testing now and see what happens.
OK, now I have a full backtrace https://bugzilla.redhat.com/attachment.cgi?id=373272
For me, compiz crashes only if I try to use the "Desktop Effects" dialog to enable it. If I simply kill metacity and start compiz, it works fine. It takes about a minute to start but it runs fine. It hangs on the XSync that follows the call to XCompositeRedirectSubWindows at line 2300 in display.c.