abrt 1.0.0 detected a crash. How to reproduce ----- 1.Enabled blur 2. 3. Comment: Session crashed and took me back to the login page.. Couldn't use system afterwards. Had to disable blur from a console and then log back in. Attached file: backtrace cmdline: /usr/bin/compiz --ignore-desktop-hints --replace ccp component: compiz executable: /usr/bin/compiz kernel: 2.6.31.6-166.fc12.x86_64 package: compiz-0.8.2-19.fc12 rating: 4 reason: Process was terminated by signal 6
Created attachment 380123 [details] File: backtrace
--------------------------------------------------------------------- Program terminated with signal 6, Aborted. #0 0x0000003d3a6326b5 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 64 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); Thread 1 (Thread 3765): #0 0x0000003d3a6326b5 in raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 resultvar = 0 pid = <value optimized out> selftid = <value optimized out> #1 0x0000003d3a633e95 in abort () at abort.c:92 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0x7f06aeead85e, sa_sigaction = 0x7f06aeead85e}, sa_mask = {__val = {262973670320, 140733708159136, 117, 140733708159376, 262972787542, 206158430232, 140733708159392, 140733708159168, 262972697384, 206158430256, 140733708159416, 42207824, 113, 113, 0, 140733708171420}}, sa_flags = 980659469, sa_restorer = 0x7f06aeead84d} sigs = {__val = {32, 0 <repeats 15 times>}} #2 0x0000003d3a62b7a5 in __assert_fail (assertion= 0x7f06aeead85e "!image->base.Data", file=<value optimized out>, line=117, function=<value optimized out>) at assert.c:81 buf = 0x2840a50 "compiz: radeon_texture.c:117: radeon_teximage_map: Assertion `!image->base.Data' failed.\n" #3 0x00007f06aee9e120 in radeon_teximage_map (image=0x282a430, write_enable=<value optimized out>) at radeon_texture.c:117 __PRETTY_FUNCTION__ = "radeon_teximage_map" #4 0x00007f06aee9ee1e in radeon_texsubimage (ctx=0x1960610, dims=<value optimized out>, target=<value optimized out>, level=<value optimized out>, xoffset=<value optimized out>, yoffset=<value optimized out>, zoffset=<value optimized out>, width=<value optimized out>, height=<value optimized out>, depth=<value optimized out>, imageSize=<value optimized out>, format=<value optimized out>, type=<value optimized out>, pixels= 0x28417c0, packing=<value optimized out>, texObj=<value optimized out>, texImage=<value optimized out>, compressed=<value optimized out>) at radeon_texture.c:752 dstRowStride = <value optimized out> rmesa = <value optimized out> t = <value optimized out> image = 0x282a430 ----------------------------------------------------------------- Hi Namit, Thanks for the bug report. It looks like compiz is exposing a driver issue. I am forwarding this to the correct maintainers. There is some additional information we require that will be helpful in our diagnosis of this issue. 1) Please attach your X server config file (/etc/X11/xorg.conf, if available) 2) output of the dmesg command 3) And X server log file (/var/log/Xorg.*.log) 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. And merry Xmas. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 380191 [details] Output of dmesg
Created attachment 380192 [details] xorg.conf file
Created attachment 380193 [details] Xorg log file 0
Created attachment 380194 [details] Xorg log file 1
Created attachment 380195 [details] Xorg log file 2
Created attachment 380197 [details] Xorg log file 3
Created attachment 380198 [details] Xorg log file 4
Created attachment 380199 [details] Xorg log file 5
Created attachment 380200 [details] Xorg log file 9 6,7,8 are missing...
Hi Namit, Thanks for the quick answer. Changing status from NEW to ASSIGNED. This bug has been triaged. PS: As per comment https://bugzilla.redhat.com/show_bug.cgi?id=548231#c4 assiging to Airlied and CCing Ajax. Regards. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
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.