Bug 274724

Summary: Background crashed when changing folders in Dolphin
Product: [I don't know] kde Reporter: Anthony Archer <archeybunker>
Component: generalAssignee: Unassigned bugs mailing-list <unassigned-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: cfeck
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Anthony Archer 2011-06-02 05:17:15 UTC
Application: kfilemetadatareader ()
KDE Platform Version: 4.6.80 (4.7 Beta1)
Qt Version: 4.7.3
Operating System: Linux 2.6.39-ARCH i686
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:

I browsed into a folder in dolphin that contained pdf files.  The folder is mounted to a cifs share, but this is done in fstab.  I'm not sure what crashed, but this dialog popped up.  I think it might be akonadi or nepomuk, but dolphin did not visibly crash.

4.7 Beta1

-- Backtrace:
Application:  (kfilemetadatareader), signal: Aborted
[KCrash Handler]
#7  0xb775c424 in __kernel_vsyscall ()
#8  0xb6befbbf in raise () from /lib/libc.so.6
#9  0xb6bf1545 in abort () from /lib/libc.so.6
#10 0xb6c2a0dc in ?? () from /lib/libc.so.6
#11 0xb6c30a85 in ?? () from /lib/libc.so.6
#12 0xb6c34879 in free () from /lib/libc.so.6
#13 0xb6dd947f in operator delete(void*) () from /usr/lib/libstdc++.so.6
#14 0xb6dc0b0b in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Rep::_M_destroy(std::allocator<char> const&) () from /usr/lib/libstdc++.so.6
#15 0xb6dc0b4c in ?? () from /usr/lib/libstdc++.so.6
#16 0xb6dc0bbe in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/libstdc++.so.6
#17 0xb6bf2c31 in ?? () from /lib/libc.so.6
#18 0xb6bf2cbd in exit () from /lib/libc.so.6
#19 0xb6bdb10b in __libc_start_main () from /lib/libc.so.6
#20 0x0804b411 in _start ()

Possible duplicates by query: bug 274696, bug 274609, bug 274423, bug 274398, bug 274353.

Reported using DrKonqi
Comment 1 Christoph Feck 2011-06-02 13:14:43 UTC
This is bug 257944, which used to be an openSUSE bug. Now that it appears on Archlinux, it probably means there were package updates to strigi.

Please add a valgrind backtrace with full debugging information for strigi enabled (compile options -O0 -g). For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_Valgrind

*** This bug has been marked as a duplicate of bug 257944 ***