abrt detected a crash. How to reproduce ----- 1. 2. 3. Additional information ====== Attached files ---- backtrace cmdline ----- /usr/bin/kbuildsycoca4 --incremental component ----- kdelibs executable ----- /usr/bin/kbuildsycoca4 kernel ----- 2.6.31.1-56.fc12.i686.PAE package ----- kdelibs-6:4.3.2-3.fc12 reason ----- Process was terminated by signal 6
Created attachment 366665 [details] File: backtrace
Looking at where the qFatal got called from, it seems you have different Qt versions installed. Could you please post the output of: rpm -qa | grep qt Also, this can help us determine if you are using KDE that was built against some odd version: rpm -q kdelibs Thanks.
Also: ldd /usr/bin/kbuildsycoca4 ls -l /usr/lib/libQt*.so.4
$ rpm -qa | grep qt|sort PackageKit-qt-0.5.3-1.fc12.x86_64 avahi-qt3-0.6.25-5.fc12.x86_64 ibus-qt-1.2.0.20091014-1.fc12.x86_64 pinentry-qt-0.7.6-4.fc12.x86_64 poppler-qt4-0.12.1-3.fc12.x86_64 qt-4.5.3-7.fc12.x86_64 qt-devel-4.5.3-7.fc12.x86_64 qt-sqlite-4.5.3-7.fc12.x86_64 qt-x11-4.5.3-7.fc12.x86_64 qt3-3.3.8b-28.fc12.x86_64 qtscriptbindings-0.1.0-8.fc12.x86_64 $ rpm -q kdelibs kdelibs-4.3.2-4.fc12.x86_64 $ ldd /usr/bin/kbuildsycoca4 linux-vdso.so.1 => (0x00007fff98d45000) libkdeinit4_kbuildsycoca4.so => /usr/lib64/libkdeinit4_kbuildsycoca4.so (0x0000003c92a00000) libkio.so.5 => /usr/lib64/libkio.so.5 (0x0000003c93a00000) libkdeui.so.5 => /usr/lib64/libkdeui.so.5 (0x0000003c92200000) libkdecore.so.5 => /usr/lib64/libkdecore.so.5 (0x0000003c90800000) libQtDBus.so.4 => /usr/lib64/libQtDBus.so.4 (0x0000003c90000000) libQtCore.so.4 => /usr/lib64/libQtCore.so.4 (0x0000003c8ee00000) libpthread.so.0 => /lib64/libpthread.so.0 (0x000000314a000000) libQtSvg.so.4 => /usr/lib64/libQtSvg.so.4 (0x0000003c92e00000) libQtNetwork.so.4 => /usr/lib64/libQtNetwork.so.4 (0x0000003c90400000) libQtXml.so.4 => /usr/lib64/libQtXml.so.4 (0x0000003c8f400000) libQtGui.so.4 => /usr/lib64/libQtGui.so.4 (0x0000003c91200000) libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003c8b600000) libm.so.6 => /lib64/libm.so.6 (0x0000003149c00000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003c8b200000) libc.so.6 => /lib64/libc.so.6 (0x0000003149400000) libz.so.1 => /lib64/libz.so.1 (0x000000314b400000) libstreamanalyzer.so.0 => /usr/lib64/libstreamanalyzer.so.0 (0x0000003c94000000) libstreams.so.0 => /usr/lib64/libstreams.so.0 (0x0000003c93600000) libsolid.so.4 => /usr/lib64/libsolid.so.4 (0x0000003c93200000) libSM.so.6 => /usr/lib64/libSM.so.6 (0x000000314c400000) libICE.so.6 => /usr/lib64/libICE.so.6 (0x000000314c800000) libX11.so.6 => /usr/lib64/libX11.so.6 (0x0000003c8a600000) libXext.so.6 => /usr/lib64/libXext.so.6 (0x0000003c8aa00000) libXft.so.2 => /usr/lib64/libXft.so.2 (0x0000003c8f800000) libXau.so.6 => /usr/lib64/libXau.so.6 (0x000000314ac00000) libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x0000003156400000) libXpm.so.4 => /usr/lib64/libXpm.so.4 (0x0000003c8fc00000) libfam.so.0 => /usr/lib64/libfam.so.0 (0x0000003159a00000) libacl.so.1 => /lib64/libacl.so.1 (0x0000003156800000) libattr.so.1 => /lib64/libattr.so.1 (0x0000003154e00000) libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x0000003c8c600000) libXtst.so.6 => /usr/lib64/libXtst.so.6 (0x0000003c91e00000) libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x0000003c8de00000) libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x0000003c8be00000) libbz2.so.1 => /lib64/libbz2.so.1 (0x0000003153400000) liblzma.so.0 => /usr/lib64/liblzma.so.0 (0x0000003154200000) libresolv.so.2 => /lib64/libresolv.so.2 (0x000000314d800000) libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x000000314dc00000) libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x0000003c8c200000) librt.so.1 => /lib64/librt.so.1 (0x000000314a400000) libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x0000003c8ae00000) libdl.so.2 => /lib64/libdl.so.2 (0x0000003149800000) /lib64/ld-linux-x86-64.so.2 (0x0000003149000000) libpng12.so.0 => /usr/lib64/libpng12.so.0 (0x000000314ec00000) libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x000000314f800000) libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x0000003c8ba00000) libXi.so.6 => /usr/lib64/libXi.so.6 (0x0000003c8ca00000) libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x0000003c8da00000) libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x0000003c8d600000) libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x000000314f400000) libssl.so.10 => /usr/lib64/libssl.so.10 (0x0000003c8ea00000) libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x0000003c8ce00000) libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x0000003c90e00000) libuuid.so.1 => /lib64/libuuid.so.1 (0x000000314bc00000) libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x000000314b000000) libcap-ng.so.0 => /lib64/libcap-ng.so.0 (0x000000314e000000) libexpat.so.1 => /lib64/libexpat.so.1 (0x000000314f000000) libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x0000003c8e200000) libkrb5.so.3 => /lib64/libkrb5.so.3 (0x0000003c8e600000) libcom_err.so.2 => /lib64/libcom_err.so.2 (0x0000003c8d200000) libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x0000003151c00000) libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x0000003152400000) libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000003152c00000) libselinux.so.1 => /lib64/libselinux.so.1 (0x000000314c000000) $ ls -l /usr/lib*/libQt*.so.4 lrwxrwxrwx 1 root root 22 Oct 31 17:46 /usr/lib64/libQt3Support.so.4 -> libQt3Support.so.4.5.3 lrwxrwxrwx 1 root root 29 Oct 31 17:46 /usr/lib64/libQtAssistantClient.so.4 -> libQtAssistantClient.so.4.5.3 lrwxrwxrwx 1 root root 21 Oct 31 17:46 /usr/lib64/libQtCLucene.so.4 -> libQtCLucene.so.4.5.3 lrwxrwxrwx 1 root root 18 Oct 31 17:46 /usr/lib64/libQtCore.so.4 -> libQtCore.so.4.5.3 lrwxrwxrwx 1 root root 18 Oct 31 17:46 /usr/lib64/libQtDBus.so.4 -> libQtDBus.so.4.5.3 lrwxrwxrwx 1 root root 22 Oct 31 17:46 /usr/lib64/libQtDesigner.so.4 -> libQtDesigner.so.4.5.3 lrwxrwxrwx 1 root root 32 Oct 31 17:46 /usr/lib64/libQtDesignerComponents.so.4 -> libQtDesignerComponents.so.4.5.3 lrwxrwxrwx 1 root root 17 Oct 31 17:46 /usr/lib64/libQtGui.so.4 -> libQtGui.so.4.5.3 lrwxrwxrwx 1 root root 18 Oct 31 17:46 /usr/lib64/libQtHelp.so.4 -> libQtHelp.so.4.5.3 lrwxrwxrwx 1 root root 21 Oct 31 17:46 /usr/lib64/libQtNetwork.so.4 -> libQtNetwork.so.4.5.3 lrwxrwxrwx 1 root root 20 Oct 31 17:46 /usr/lib64/libQtOpenGL.so.4 -> libQtOpenGL.so.4.5.3 lrwxrwxrwx 1 root root 20 Oct 31 17:46 /usr/lib64/libQtScript.so.4 -> libQtScript.so.4.5.3 lrwxrwxrwx 1 root root 25 Oct 31 17:46 /usr/lib64/libQtScriptTools.so.4 -> libQtScriptTools.so.4.5.3 lrwxrwxrwx 1 root root 17 Oct 31 17:46 /usr/lib64/libQtSql.so.4 -> libQtSql.so.4.5.3 lrwxrwxrwx 1 root root 17 Oct 31 17:46 /usr/lib64/libQtSvg.so.4 -> libQtSvg.so.4.5.3 lrwxrwxrwx 1 root root 18 Oct 31 17:46 /usr/lib64/libQtTest.so.4 -> libQtTest.so.4.5.3 lrwxrwxrwx 1 root root 20 Oct 31 17:46 /usr/lib64/libQtWebKit.so.4 -> libQtWebKit.so.4.5.3 lrwxrwxrwx 1 root root 17 Oct 31 17:46 /usr/lib64/libQtXml.so.4 -> libQtXml.so.4.5.3 lrwxrwxrwx 1 root root 25 Oct 31 17:46 /usr/lib64/libQtXmlPatterns.so.4 -> libQtXmlPatterns.so.4.5.3
Hmmm, no irregularities there... All Qt libs loaded are the system ones and they're all 4.5.3.
*** Bug 533208 has been marked as a duplicate of this bug. ***
Another report, same backtrace.
Does /usr/bin/kbuildsycoca4 --incremental hang when runned manually from shell? What's the output?
(In reply to comment #8) > Does /usr/bin/kbuildsycoca4 --incremental hang when runned manually from shell? > What's the output? Seems to work fine: $ time /usr/bin/kbuildsycoca4 --incremental kbuildsycoca4 running... real 0m1.014s user 0m0.556s sys 0m0.316s
*** Bug 537031 has been marked as a duplicate of this bug. ***
From the duplicate, a backtrace with more debugging info (thanks!): https://bugzilla.redhat.com/attachment.cgi?id=369162
*** Bug 537429 has been marked as a duplicate of this bug. ***
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
*** Bug 538107 has been marked as a duplicate of this bug. ***
Hmm, it's tracing through some weird places. From the style to hashing to the Xinput translator. I don't even know why this call stack would make sense (haven't looked at the code yet). Maybe everyone is using some style that triggers this? To those who have had this happen to you: What widget and window decorations do you have set?
I have been using default settings. Can you tell me which config files I should attach to this bug report ?
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.