Summary: | Kbuildsycoca4 crashes after packages update [not null KSycocaEntry::offset, KBuildMimeTypeFactory::save, KBuildSycoca::save] | ||
---|---|---|---|
Product: | [Unmaintained] kdelibs | Reporter: | Zdeněk Zikán <zdenek.zikan> |
Component: | ksycoca | Assignee: | David Faure <faure> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andresbajotierra, bh.inbox, bleamz, chris, diego_bernardi, kde, tburdge222, thodpol |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Zdeněk Zikán
2009-07-07 16:20:24 UTC
Did you installed KDE from Ubuntu packages or from any other way? THanks I have them installed from Kubuntu Backports PPA (http://ppa.launchpad.net/kubuntu-ppa/backports/ubuntu) I'm not so sure whether does this help, but in my case, I've removed .local and .config which is located in home directory(Additional, I've also removed all FILES in ~/.kde/cache-{systemname}/ and all FILES in ~/.kde/cache-{systemname}/kpc.) then re-login and that crash of kbuildsyscoca4 has gone. I also experienced this bug when I updated kde from the kubuntu Backports PPA. Now I can't start kde or run any kde apps from gnome, I get a kbuildsycoca4 crash. The "KDE Crash Handler" that automatically starts gives the following information: Application that crashed: kbuildsycoca4 Version of the application: 1.1 KDE Version: 4.3.00 (KDE 4.3.0) Qt Version: 4.5.2 Operating System: Linux 2.6.28-15-generic x86_64 Distribution: Ubuntu 9.04 -- Backtrace: Application: KBuildSycoca (kbuildsycoca4), signal: Segmentation fault [KCrash Handler] #5 KSycocaEntry::offset (this=0x0) at /build/buildd/kde4libs-4.3.0/kdecore/sycoca/ksycocaentry.cpp:132 #6 0x00007f71e521f9a8 in KBuildMimeTypeFactory::savePatternLists (this=0x14cc320, str=@0x148ca30) at /build/buildd/kde4libs-4.3.0/kded/kbuildmimetypefactory.cpp:361 #7 0x00007f71e521fe63 in KBuildMimeTypeFactory::save (this=0x14cc320, str=@0x148ca30) at /build/buildd/kde4libs-4.3.0/kded/kbuildmimetypefactory.cpp:307 #8 0x00007f71e5218d61 in KBuildSycoca::save (this=0x14cccb0, str=0x148ca30) at /build/buildd/kde4libs-4.3.0/kded/kbuildsycoca.cpp:525 #9 0x00007f71e521af05 in KBuildSycoca::recreate (this=0x14cccb0) at /build/buildd/kde4libs-4.3.0/kded/kbuildsycoca.cpp:433 #10 0x00007f71e521cd5c in kdemain (argc=1, argv=0x7fffed667b78) at /build/buildd/kde4libs-4.3.0/kded/kbuildsycoca.cpp:829 #11 0x00007f71e1d925a6 in __libc_start_main (main=0x4007d0 <main>, argc=1, ubp_av=0x7fffed667b78, init=0x400800 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffed667b68) at libc-start.c:220 #12 0x0000000000400709 in _start () at ../sysdeps/x86_64/elf/start.S:113 I think bug 202871 is a duplicate of this bug, because if I remove the ~/.local/share/mime/globs file, the problem is resolved. And I can confirm the description of that bug 202871: kbuildsycoca4 also crashes if ~/.local/share/mime/globs is empty. *** Bug 206720 has been marked as a duplicate of this bug. *** *** Bug 199745 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 202871 *** Reopening as this is a different crash. Christoph's comments (comment 4 and comment 5) are indeed bug 202871 (which is fixed in SC 4.4beta2), but it seems they are unrelated to this (which is still unfixed). From bug 219550: --- What I was doing when the application crashed: I was installing a number of new packages through Add/Remove Applications including some that required confirmation, such as Sun Java 6. The message appeared after to downloads, while the packages were being installed -- but I can't remember which package was being installed at the time. *** Bug 219550 has been marked as a duplicate of this bug. *** Everyone with this crash: please check if you don't have the umask problem that leads to bug 202871 (I'm still not sure if it's the same bug or not). More precisely: type ls -l ~/.local/share/mime and check if any directory misses "x" permissions in the 4th character, like drw-r--r-- If so, making the directory executable (+x) again will fix the crash, and then this is the same as 202871. Otherwise, I need a way to reproduce this one... Also, is anyone here not using Ubuntu? From a quick look, it seems like a Ubuntu-only crash? *** Bug 221271 has been marked as a duplicate of this bug. *** *** Bug 225071 has been marked as a duplicate of this bug. *** fixed in kde 4.4 |