abrt detected a crash. Comment: Was attempting to start Desktop Effects in a VirtualBox environment. Attached file: backtrace cmdline: desktop-effects component: desktop-effects executable: /usr/bin/desktop-effects kernel: 2.6.31.5-122.fc12.x86_64 package: desktop-effects-0.8.4-2.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 368169 [details] File: backtrace
Is this reproducable? Can you repeat it after doing 'debuginfo-install desktop-effects' (debuginfo-install is in the yum-utils package)
100% reproducable. Crashes every time I start it no matter what modules I have loaded. Looking through much of the error logs I am leaning towards thinking this is an issue with the vboxvideo driver module. I'll do a debuginfo run tomorrow and see what that will turn up.
*** Bug 553617 has been marked as a duplicate of this bug. ***
In the case where glXChooseVisual() fails, an uninitialized value for context is passed to glXDestroyContext(), which is almost certainly triggering this crash.
desktop-effects-0.8.7-2.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/desktop-effects-0.8.7-2.fc13
desktop-effects-0.8.7-2.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update desktop-effects'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/desktop-effects-0.8.7-2.fc13
Michael: Are you able to confirm this problem is fixed using the update posted in comment#7? Please feel free to add feedback either here in bugzilla, or at http://admin.fedoraproject.org/updates/desktop-effects-0.8.7-2.fc13 Thanks!
I'm experiencing the same bug as the OP in F13 x86_64 running as a VirtualBox 3.2.6 guest (PUEL version). Filed abrt backtrace as bug 611821.
desktop-effects-0.8.7-2.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.