Description of problem: I have an IBM Thinkpad X41t with an Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03). "Desktop Effects" works fine in Fedora 11, and it worked fine on F12 Alpha, but trying F12 Beta, my system completely hangs when I enable it. Version-Release number of selected component (if applicable): Name : compiz Relocations: (not relocatable) Version : 0.8.2 Vendor: Fedora Project Release : 15.fc12 Build Date: Tue 22 Sep 2009 04:13:08 AM NZST Install Date: Thu 15 Oct 2009 04:39:32 PM NZDT Build Host: x86-6.fedora.phx.redhat.com How reproducible: Always Steps to Reproduce: 1. Boot on the Live USB 2. System - Preferences - Desktop Effects 3. Choose 3D effects with compiz Actual results: System freezes completely. Expected results: My windows should wobble and I should spin like a cube! Additional info: Yah, it used to work fine. KMS seems to work fine enough, in that Plymouth or whatever we have now displays a cute Fedora logo at boot. However, grepping dmesg, /var/log/messages and /var/log/Xorg.* for kms (case insensitively) doesn't bring up any mention of it.
Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. Please attach your X server config file (/etc/X11/xorg.conf, if available), output of the dmesg command, and X server log file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file attachments using the bugzilla file attachment link below. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Do you have any advice on how to make those files actually persistent? I use livecd-iso-to-disk to create a persistent overlay, but the only part that's ever persistent is /home/**. Once it's hung, I can't really access the file system without rebooting, which sort of loses those logs. I'll try having the relevant logs tailed or linked onto my USB drive.
Created attachment 368085 [details] Xorg.0.log including crash stack trace Strangely, when I tried to reproduce it, instead of hanging my system this time, it just crashed X. Here's the Xorg.0.log with the stack trace in it. Even when I install a debuginfo for X, its stacktrace doesn't appear very helpful. I'll try this again with gdb and remotely logging in.
Created attachment 368086 [details] xorg.conf that gets generated by X (but not in use) This is what X generate when I do Xorg -configure :1, but I don't have that in use when this happens. Just providing it if it gives you any insight as to how X might be working.
Created attachment 368087 [details] dmesg, annotated with point where I turn on compiz Doesn't seem to contain any messages at the point of turning compiz on, but there's some interesting drm_mode_rmfb's before that.
Er, to get debuginfo for xorg-x11-server-Xorg and xorg-x11-drv-intel, I had to upgrade them. After doing that, it hung as it did before. I logged into it remotely and was running gdb at the time. After a minute, it didn't appear to segfault at all, despite being frozen, so I did a "killall -9 compiz" which allowed my mouse cursor to move again (though it's busy throbber animation is still frozen). A backtrace at this point says this: Program received signal SIGINT, Interrupt. 0x0096e416 in __kernel_vsyscall () (gdb) bt #0 0x0096e416 in __kernel_vsyscall () #1 0x0055edb9 in ioctl () from /lib/libc.so.6 #2 0x0036288e in drmIoctl () from /usr/lib/libdrm.so.2 #3 0x00362cd3 in drmCommandNone () from /usr/lib/libdrm.so.2 #4 0x00aac59e in I830BlockHandler (i=<value optimized out>, blockData=<value optimized out>, pTimeout=<value optimized out>, pReadmask=<value optimized out>) at i830_driver.c:2194 #5 0x081b332b in AnimCurScreenBlockHandler (screenNum=<value optimized out>, blockData=<value optimized out>, pTimeout=<value optimized out>, pReadmask=<value optimized out>) at animcur.c:211 #6 0x080e801b in compBlockHandler (i=<value optimized out>, blockData=<value optimized out>, pTimeout=<value optimized out>, pReadmask=<value optimized out>) at compinit.c:166 #7 0x080736b8 in BlockHandler (pTimeout=<value optimized out>, pReadmask=<value optimized out>) at dixutils.c:379 #8 0x080a0e1c in WaitForSomething (pClientsReady=<value optimized out>) at WaitFor.c:216 #9 0x0806df30 in Dispatch () at dispatch.c:381 #10 0x080628c5 in main (argc=<value optimized out>, argv=<value optimized out>, envp=<value optimized out>) at main.c:285 I'll try again and post something more useful, I hope.
(In reply to comment #7) > I'll try again and post something more useful, I hope. I think this is perfect: Backtrace: 0: /usr/bin/Xorg (xorg_backtrace+0x3c) [0x80e57bc] 1: /usr/bin/Xorg (0x8048000+0x5eba6) [0x80a6ba6] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xd7340c] 3: /usr/lib/libpixman-1.so.0 (0xb82000+0x38b0) [0xb858b0] 4: /usr/lib/libpixman-1.so.0 (0xb82000+0x3f705) [0xbc1705] 5: /usr/lib/libpixman-1.so.0 (0xb82000+0x1477a) [0xb9677a] 6: /usr/lib/libpixman-1.so.0 (0xb82000+0x39d50) [0xbbbd50] 7: /usr/lib/libpixman-1.so.0 (0xb82000+0x41a7a) [0xbc3a7a] 8: /usr/lib/libpixman-1.so.0 (0xb82000+0x42c9b) [0xbc4c9b] 9: /usr/lib/libpixman-1.so.0 (0xb82000+0x399f4) [0xbbb9f4] 10: /usr/lib/libpixman-1.so.0 (0xb82000+0x152f4) [0xb972f4] 11: /usr/lib/libpixman-1.so.0 (0xb82000+0x3b9af) [0xbbd9af] 12: /usr/lib/libpixman-1.so.0 (0xb82000+0x152f4) [0xb972f4] 13: /usr/lib/libpixman-1.so.0 (0xb82000+0x46df4) [0xbc8df4] 14: /usr/lib/libpixman-1.so.0 (0xb82000+0x152f4) [0xb972f4] 15: /usr/lib/libpixman-1.so.0 (0xb82000+0x4d5ca) [0xbcf5ca] 16: /usr/lib/libpixman-1.so.0 (0xb82000+0x152f4) [0xb972f4] 17: /usr/lib/libpixman-1.so.0 (pixman_image_composite+0x177) [0xbbc847] 18: /usr/lib/xorg/modules/libfb.so (fbComposite+0x170) [0x554d70] 19: /usr/lib/xorg/modules/drivers/intel_drv.so (0x95c000+0x5b27c) [0x9b727c] 20: /usr/lib/xorg/modules/drivers/intel_drv.so (0x95c000+0x59855) [0x9b5855] 21: /usr/bin/Xorg (0x8048000+0xd3977) [0x811b977] 22: /usr/bin/Xorg (CompositePicture+0x290) [0x810ee70] 23: /usr/bin/Xorg (0x8048000+0x1686ed) [0x81b06ed] 24: /usr/bin/Xorg (0x8048000+0x168a09) [0x81b0a09] 25: /usr/bin/Xorg (0x8048000+0xa16d8) [0x80e96d8] 26: /usr/bin/Xorg (0x8048000+0xa17d1) [0x80e97d1] 27: /usr/bin/Xorg (0x8048000+0x4b6e3) [0x80936e3] 28: /usr/bin/Xorg (MapWindow+0x15e) [0x809796e] 29: /usr/bin/Xorg (0x8048000+0x25829) [0x806d829] 30: /usr/bin/Xorg (0x8048000+0x26187) [0x806e187] 31: /usr/bin/Xorg (0x8048000+0x1a875) [0x8062875] 32: /lib/libc.so.6 (__libc_start_main+0xe6) [0x3b2b36] 33: /usr/bin/Xorg (0x8048000+0x1a461) [0x8062461] Segmentation fault at address 0x9dba000
This is probably a duplicate of my other X crashing bug, then, bug 530804. I have a better backtrace for it, with function names got out from GDB. My concern is that originally when I tried this, compiz was hanging X. Now when I try it without upgrading X and the intel driver, it crashes it like with bug 530804. But when I upgrade and try it, compiz hangs X again. (Killing compiz allows me to move the pointer, but its animation remains frozen, but there are no panels or windows and I can't cause any to appear from the terminal (setting the appropriate DISPLAY) either.)
*** Bug 530804 has been marked as a duplicate of this bug. ***
Let's focus on this one.
Should I re-upload the stacktrace from bug 530804 with its GDB-acquired function names to this one?
(In reply to comment #12) > Should I re-upload the stacktrace from bug 530804 with its GDB-acquired > function names to this one? You don't have to ... thanks to magic of bugzilla we still know it is attachment 366076 [details]
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
I just preupgraded to Fedora 12 final and this bug still exists. I can no longer use compiz or desktop effects with Fedora 12, as I could with Fedora 10 and 11. Sigh :( Anything more I can do to help?
Here's a useful update. I only have issues when I have a second monitor attached. When I detach the second monitor, compiz starts just fine. Could there possible be video card memory issues? I vaguely remember being able to use compiz with a dual monitor setup as long the dimensions remained below 2047x768 last year.
Er, "below 2048x768". If I enable compiz and using xrandr I set my secondary monitor to 1023x768, with my primary display (laptop screen) being 1024x768, it works fine, and for sizes below that. When I change the secondary monitor to 1024x768 or higher, the screen becomes distorted or most of it turns black or white. I can still move the cursor though. When I set the secondary monitor to 1600x1200, X soon after freezes up, but I can move the mouse for a little bit.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.