Fedora Account System
Red Hat Associate
Red Hat Customer
abrt detected a crash. How to reproduce ----- 1. 2. 3. Comment ----- Was playing around with VirtualBox and Seamless mode. It doesn't work right with compiz enabled, so was switching back and forth. Apparently compiz crashed. Additional information ====== Attached files ---- backtrace cmdline ----- compiz --ignore-desktop-hints glib gconf gnomecompat --replace component ----- compiz executable ----- /usr/bin/compiz kernel ----- 2.6.31.5-96.fc12.i686.PAE package ----- compiz-0.8.2-19.fc12 reason ----- Process was terminated by signal 11
Created attachment 366961 [details] File: backtrace
I encountered an evidently similar crash by running compiz-manager. I started the session with Metacity, then in a terminal ran compiz --replace, and later I installed and ran compiz-manager and it crashed. Every time I run that command, the crash occurs.
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Switching incorrect assignees to the default one.
I also had this crash happen to me. After upgrading to FC12 from FC11 the desktop was almost unusable it was so slow. The automatic bug reporting service detected a crash in compiz. After turning off compiz from within the Desktop Effects option under system\preferences the desktop is stable again, though I'm without all the great 3D enabled effects. I should probably note that I never had issues with compiz under FC11.
(In reply to comment #6) > After turning off compiz from within the Desktop > Effects option under system\preferences the desktop is stable again, though I'm > without all the great 3D enabled effects. I should probably note that I never > had issues with compiz under FC11. Out of curiosity, what graphics hardware do you have and are you running KMS or did you pass nomodeset to the kernel? PS. I have Intel graphics and for me 3D stuff is unusable (bug #537494).
I have an ATI radeon X1650 Pro, an R535 series chipset. I haven't made any explicit changes to the kernel that I know of. To be honest I just started using Linux about 3 months ago with Fedora 11. I still get the Plymouth boot screen, which I thought was only available with KMS, but perhaps that's not the case. I've tried removing then re-installing the radeonhd driver from within PackageKit but it doesn't seem to make a difference.
01:00.1 Display controller: ATI Technologies Inc RV370 secondary [Sapphire X550 Silent]
(In reply to comment #7) > (In reply to comment #6) > > After turning off compiz from within the Desktop > > Effects option under system\preferences the desktop is stable again, though I'm > > without all the great 3D enabled effects. I should probably note that I never > > had issues with compiz under FC11. > > Out of curiosity, what graphics hardware do you have and are you running KMS or > did you pass nomodeset to the kernel? > > PS. I have Intel graphics and for me 3D stuff is unusable (bug #537494). After searching a bit on KMS I can tell you I was running KMS when the bug happened. I added the "nomodeset" kernel argument to GRUB during the startup process and now compiz seems to work fine, or at least works well enough that you can enable it. Is there a way to permanently add "nomodeset" to the kernel arguements for the time being so I don't have to add it each time I turn the computer on?
After playing around with settings further, here's a matrix similar to what Bojan did with the bug he referenced in his comment. KMS+Compiz = Desktop is nearly unusable. Choppy mouse movement, 30 seconds or more lag time when responding to mouse clicks. KMS+Metacity = Works. No KMS+Metacity = Works. No KMS+Compiz = Seems to be fully functional, though some of the 3D window effects aren't quite as smooth as they were under FC11.
(In reply to comment #10) > Is there a way to permanently add "nomodeset" to the kernel > arguements for the time being so I don't have to add it each time I turn the > computer on? Yes. Just edit /boot/grub/grub.conf file and add nomodeset there (on the kernel line).
Hi all, @ Brian, many thanks for reporting the issue. @ All, the corresponding backtrace file that Brian reported is a related to a -very- specific issue that our maintainers are tracking down. This issue is independent: - from the KMS setting - from the video card that you might use - from the fact that you are experiencing X display corruptions or slowness. So please feel free to open other tickets in order to report any issue you were commenting that is not related to the issue described in the ticket 531714 (Compiz crashs when disabling desktop effect). Regards. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** This bug has been marked as a duplicate of bug 531714 ***
(In reply to comment #12) > (In reply to comment #10) > > Is there a way to permanently add "nomodeset" to the kernel > > arguements for the time being so I don't have to add it each time I turn the > > computer on? > Yes. Just edit /boot/grub/grub.conf file and add nomodeset there (on the kernel > line). When I browse to that directory in nautilus I'm not able to open\edit the grub.conf file because I don't have the right privledges to do so. I'm not prompted to provide the root password either like you are with some other system functions. I became root from within the terminal with -su, but I don't know the command to open\edit the grub.conf file in the command-line. How do I go about editing the grub.conf file? Thanks in advance!
(In reply to comment #15) > How do I > go about editing the grub.conf file? Open Terminal. Run "su -". Run "vi /boot/grub/grub.conf".
NVIDIA FX5200 dmesg say: SELinux: initialized (dev fuse, type fuse), uses genfs_contexts NVRM: Xid (0001:00): 6, PE0000 0f5c 00000000 0000fa98 00ffffff 00000000 NVRM: Xid (0001:00): 6, PE0000 0180 01010400 00000000 00ffffff 00000000 NVRM: Xid (0001:00): 3, C 00000000 SC 00000006 M 00000180 Data 01010400 NVRM: Xid (0001:00): 6, PE0000 0180 01010400 00000000 00000000 00000000 NVRM: Xid (0001:00): 3, C 00000000 SC 00000006 M 00000180 Data 01010400 NVRM: Xid (0001:00): 6, PE0000 0180 01010400 00000000 00000000 00000000 NVRM: Xid (0001:00): 3, C 00000000 SC 00000006 M 00000180 Data 01010400 NVRM: Xid (0001:00): 6, PE0000 0180 01010400 00000000 00000000 00000000 compiz[2061]: segfault at 60b68a0 ip 060b68a0 sp bf8c3170 error 4 in libxml2.so.2.7.6[6132000+144000]
*** Bug 546962 has been marked as a duplicate of this bug. ***
For me everything works well including compiz and effects on Intel G31(GMA3100) but executing compiz-fusion icon opens the bug report tool. Any change through compiz fusion generates a new crash even though it seems to be working fine. I have SELinux disabled.