abrt 1.0.3 detected a crash. Comment: Just enabled compiz, loged out and loged in again... Attached file: backtrace cmdline: compiz --sm-client-id 10ff5e205a31138ca312639822166911700000054510033 --ignore-desktop-hints glib gconf gnomecompat component: compiz executable: /usr/bin/compiz kernel: 2.6.31.9-174.fc12.x86_64 package: compiz-0.8.2-21.fc12 rating: 3 reason: Process was terminated by signal 11 (Segmentation fault)
Created attachment 385642 [details] File: backtrace
Hi Throphanis, Many thanks for reporting this issue and giving hints about how to trigger this. It looks like compiz exposed a driver bug, and hence we would need additional information from you for our maintainers (and for me in order to know which team should handle this and redirect this to them). Please could you -attach- as -individual- -uncompressed- file attachments using the bugzilla file attachment link above: 1) the result of the dmesg command 2) your X server config file (/etc/X11/xorg.conf, if available) 3) X server log file (/var/log/Xorg.*.log) 4) Optionally, we would be interested in knowing if your are able to trigger this as will. We will review this issue again once you've had a chance to attach this information. Many thanks in advance. Regards. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers ------------------------------------------------------------------- Program terminated with signal 11, Segmentation fault. #0 0x0000000000000000 in ?? () Thread 1 (Thread 6562): #0 0x0000000000000000 in ?? () No symbol table info available. #1 0x00007f687d58c0fc in sample_nearest_2d (ctx=0x1a1fc10, tObj=0x1e34480, n=<value optimized out>, texcoords=0x7fffad908920, lambda=<value optimized out>, rgba=<value optimized out>) at swrast/s_texfilter.c:1289 i = 0 image = 0x1e34ad0 #2 0x00007f687d580e8c in fetch_texel_deriv (ctx=<value optimized out>, texcoord=0x7fffad908920, texdx=<value optimized out>, texdy=<value optimized out>, lodBias=<value optimized out>, unit=<value optimized out>, color=0x7fffad908930) at swrast/s_fragprog.c:123 texImg = <value optimized out> rgba = {0, 0, 0, 0} lambda = 0.198329449 texObj = 0x1e34480 #3 0x00007f687d563bb8 in _mesa_execute_program (ctx=0x1a1fc10, program= 0x1e39c30, machine=0x1a68288) at shader/prog_execute.c:1619 texcoord = {0, 0, 0, 0} color = {0.432601362, 0.999523818, 0, 1} inst = 0x1e3ed40 pc = 0 numExec = <value optimized out> __PRETTY_FUNCTION__ = "_mesa_execute_program"
Hi Theophanis (and sorry if I misspelled your name). Just for your information https://bugzilla.redhat.com/show_bug.cgi?id=557027 reported the same crash (backtrace). But they triggered this same crash differently, starting there systems "with an external display connected, at log in". We would be interested in knowing as well (sorry to ask a lot :) if in case your hardware support dual head if you can trigger the same crash as well starting up your machine with two displays with compiz. Once I have gathered all information from you and them, I may close this BZ or this other one as duplicate. Again thanks in advance. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Hello as reported here https://bugzilla.redhat.com/show_bug.cgi?id=557027 the problem is with my laptop having agpgart-intel 0000:00:00.0: Intel 945GM Chipset agpgart-intel 0000:00:00.0: detected 7932K stolen memory agpgart-intel 0000:00:00.0: AGP aperture is 256M @ 0xd0000000 when docking it on the docking station. I guess that yes the docking station and the laptop support dual head in various modes (extended desktop - that is the default, cloned desktop, monitor only, lvds only) The problem always happens when I have compiz enabled, and I dock the laptop. Immediatly compiz is crashing. What further information is needed? I will be happy to provide.
*** This bug has been marked as a duplicate of bug 557027 ***