Application: dolphin (1.4) KDE Platform Version: 4.4.61 (KDE 4.4.61 (KDE 4.5 >= 20100127)) (Compiled from sources) Qt Version: 4.6.1 Operating System: Linux 2.6.32-020632-generic x86_64 Distribution: Ubuntu 9.04 -- Information about the crash: dolphin crash after enabling and disabling preview -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #5 QUrl (this=0x7fffb4bbd4f0, other=@0x30) at /home/kde-devel/kdesvn/qt-copy/src/corelib/io/qurl.cpp:4108 #6 0x00007f9c68dc8465 in Soprano::Vocabulary::RDFS::Resource () at /home/kde-devel/kdesvn/kdesupport/soprano/soprano/vocabulary/rdfs.cpp:97 #7 0x00007f9c69083af0 in Nepomuk::ResourceData::resetAll (this=0x37a6fb0) at /home/kde-devel/kdesvn/kdelibs/nepomuk/core/resourcedata.cpp:198 #8 0x00007f9c69083939 in Nepomuk::ResourceData::deleteData (this=0x7fffb4bbd4f0) at /home/kde-devel/kdesvn/kdelibs/nepomuk/core/resourcedata.cpp:204 #9 0x00007f9c6908af49 in Nepomuk::ResourceManagerPrivate::cleanupCache (this=<value optimized out>, num=-1) at /home/kde-devel/kdesvn/kdelibs/nepomuk/core/resourcemanager.cpp:204 #10 0x00007f9c6908b9c5 in ~ResourceManager (this=0x2628030) at /home/kde-devel/kdesvn/kdelibs/nepomuk/core/resourcemanager.cpp:261 #11 0x00007f9c6908bad7 in destroy () at /home/kde-devel/kdesvn/kdelibs/nepomuk/core/resourcemanager.cpp:275 #12 0x00007f9c650116ed in *__GI_exit (status=0) at exit.c:75 #13 0x00007f9c64ff95ad in __libc_start_main (main=0x43a770 <main>, argc=5, ubp_av=0x7fffb4bbd6d8, init=0x475150 <__libc_csu_init>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffb4bbd6c8) at libc-start.c:252 #14 0x0000000000425849 in _start () at ../sysdeps/x86_64/elf/start.S:113 Reported using DrKonqi
hmm this should be change to nepomuk bug
now it happens by just opening and closing dolphin
@Sebastian: I hope the backtrace tells you more than me ;-) Thanks!
This is caused by a patch that is not even applied to svn. Plus I already fixed it here. :)
great, I hope the updated patch make it into trunk :)
I will commit as soon as I am sure there are no regressions. After all it did not seem to fix your issues with the filewatch service...