abrt detected a crash. Attached file: backtrace cmdline: compiz --replace --sm-disable --ignore-desktop-hints ccp --indirect-rendering component: compiz executable: /usr/bin/compiz kernel: 2.6.31.5-127.fc12.i686.PAE package: compiz-0.8.2-19.fc12 rating: 3 reason: Process was terminated by signal 11
Created attachment 374075 [details] File: backtrace
------------------------------------------------- Core was generated by `compiz --replace --sm-disable --ignore-desktop-hints ccp --indirect-rendering'. Program terminated with signal 11, Segmentation fault. #0 0x00914eb0 in ?? () Thread 1 (Thread 1981): #0 0x00914eb0 in ?? () No symbol table info available. #1 0x00cf60d3 in _dbus_timeout_list_add_timeout ( timeout_list=<value optimized out>, timeout=<value optimized out>) at dbus-timeout.c:319 No locals. #2 0x00ce060e in protected_change_timeout (connection=0xa0f4228, timeout=<value optimized out>, add_function=<value optimized out>, remove_function=<value optimized out>, toggle_function=<value optimized out>, enabled=<value optimized out>) at dbus-connection.c:788 timeouts = 0xa0f41a0 retval = <value optimized out> #3 0x00ce088f in _dbus_connection_add_timeout_unlocked ( connection=<value optimized out>, timeout=<value optimized out>) at dbus-connection.c:826 No locals. #4 0x00ce29e3 in _dbus_connection_attach_pending_call_unlocked ( pending=<value optimized out>, connection=<value optimized out>) at dbus-connection.c:888 reply_serial = <value optimized out> timeout = <value optimized out> ------------------------------------------------------------------------- Hi Per Arnold. Many thanks for reporting this issue. In order to get as much information as possible in order to increase the possibility for this crash to be fixed as easily as possible, could I kindly ask you the following ? : 1) Give us a hint about how this crash occurred, if you remember if a specific action you did trigereed this (clicking around, launching/activation/desactivating stuff - changing setting .. etc ..), or if looks like it appended randomly. 2) Upload to this bugzilla the /var/cache/ccpp*/coredump file that has been generated (in the ccpp* directory that was created at the time of the crash). Thanks in advance. Regards. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Hi, I am sorry for not uploading the coredump. I have big problems with my ath9k driver since upgrading to FC12. It will not let me upload or download larger files. 1) I do not remember exactly what I was doing. At the time of the bug abrt had problem with DNS lookups ad I submitted it a couple of days later. If I remember correctly I was doing just surfing with Firefox. I have not seen it after this so I guess we have to call it a randomly bug. 2) I will upload the coredump as soon as I connect to a stable connection. Btw. the core dump was in /var/cache/abrt/ccpp*/coredump. You was missing the abrt folder. The size is 256 Mb, so I made it a tgz file that is 31 Mb instead. Regards.
Created attachment 374431 [details] Coredump for compiz crash
Had compress the coredump with lzma to get it under 20Mb limit for Redhat bugzilla. Is there any other way to make the coredump smaller?
Hi Arnold. Sorry to come late. Well you can actually split the file and upload each one of the chunks individually. "split -b 15M filename filename" What will generate you files filenameaa, filenameab, filenameac ... Regards. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Thanks for the idea. As you see I got it uploaded without splitting it this time. Hope you can use it.
Actually, backtrace in comment 1 is more useful for us than the coredump. It is very difficult to deal with (I would need to have special machine, special versions of packages, and in the end I wouldn't get much more than what's in the coredump).
*** Bug 547483 has been marked as a duplicate of this bug. ***
*** Bug 548199 has been marked as a duplicate of this bug. ***
BZ#548199 reported the same crash for compiz-0.8.4-1.fc12 Matej, looking forward for your patch. Regards. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 547190 has been marked as a duplicate of this bug. ***
*** Bug 551896 has been marked as a duplicate of this bug. ***
*** Bug 553196 has been marked as a duplicate of this bug. ***
*** Bug 555817 has been marked as a duplicate of this bug. ***
*** Bug 565517 has been marked as a duplicate of this bug. ***
Seeing "libnvidia-tls.so.1" makes it look like you may be using the NVIDIA binary driver. Can you confirm that? 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 above. We will review this issue again once you've had a chance to attach this information. Thanks in advance. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 562716 has been marked as a duplicate of this bug. ***
Created attachment 408607 [details] Additional info including xorg.conf Xorg.*.log and dmesg
William, thank you for providing the requested information. Unfortunately, we cannot help you with your problem, as we are not able to support binary-only drivers. If you are able to reproduce this issue using only open source software, please, and a comment to this bug with the additional information. The open source 'nouveau' driver (in package xorg-x11-drv-nouveau) is the recommended alternative for users of Nvidia graphic chips. It is used by default in Fedora 11 and later if you remove any customizations that explicitly sets the video driver. (The older "nv" driver may be needed in some cases. It is also available in older Fedora releases.) Install the packages xorg-x11-drv-nouveau (or xorg-x11-drv-nv) and override the X server's default choice if necessary. See https://fedoraproject.org/wiki/Features/NouveauAsDefault for more information. If you used a non-packaged version of the driver from the Nvidia website please clean your system of all additional libraries and software that it installed. For users who are experiencing problems (un)installing, configuring, or using the unsupported 3rd party proprietary "nvidia" video driver, Nvidia provides indirect customer support via an online web based support forum. Nvidia monitors these web forums for commonly reported problems and passes them on to Nvidia engineers for investigation. Once they've isolated a particular problem, it is often fixed in a future video driver update. The NVNews Nvidia Linux driver forum is located at: http://www.nvnews.net/vbulletin/forumdisplay.php?s=&forumid=14 Once you have reported this issue in the Nvidia web forums, others who may have experienced the particular problem may be able to assist. If there is a real bug occuring, Nvidia will be able to determine this, and will likely resolve the issue in a future driver update for the operating system releases that they officially support. While we does not support the proprietary nvidia driver, users requiring technical support may also find the various X.Org, XFree86, and Red Hat/Fedora mailing lists helpful in finding assistance: X.Org mailing lists: http://www.freedesktop.org/XOrg/XorgMailingLists XFree86 mailing lists: http://www.xfree86.org/sos/lists.html Red Hat/Fedora mailing lists: https://listman.redhat.com/mailman/listinfo I am resetting the NEEDINFO flag to give others an opportunity to upload their copies of the data requested in Comment 17. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** Bug 585528 has been marked as a duplicate of this bug. ***
*** Bug 586468 has been marked as a duplicate of this bug. ***
*** Bug 591360 has been marked as a duplicate of this bug. ***
*** Bug 592520 has been marked as a duplicate of this bug. ***
*** Bug 593146 has been marked as a duplicate of this bug. ***
*** Bug 594008 has been marked as a duplicate of this bug. ***
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers