Bug 270891

Summary:	kfilemetadatareader crash in normal dolphin navigation
Product:	[Applications] dolphin	Reporter:	Davide Marcelli <davide.marcelli>
Component:	general	Assignee:	Peter Penz <peter.penz19>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra, frank78ac, kdelibs-bugs, mail
Priority:	NOR
Version:	16.12.2
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Davide Marcelli 2011-04-13 22:27:32 UTC

Application: kfilemetadatareader ()
KDE Platform Version: 4.6.41 (4.7 >= 20110106) "release 2"
Qt Version: 4.7.2
Operating System: Linux 2.6.37.1-1.2-default i686
Distribution: "openSUSE 11.4 (i586)"

-- Information about the crash:
- Unusual behavior I noticed:

when i use dolphin (for each action) appear the message of a kfilemetadatareader crash, but dolphin continue work

The crash can be reproduced every time.

-- Backtrace:
Application:  (kfilemetadatareader), signal: Aborted
[KCrash Handler]
#7  0xffffe430 in __kernel_vsyscall ()
#8  0xb6d018df in raise () from /lib/libc.so.6
#9  0xb6d03220 in abort () from /lib/libc.so.6
#10 0xb6d3de07 in __libc_message () from /lib/libc.so.6
#11 0xb6d43e2b in malloc_printerr () from /lib/libc.so.6
#12 0xb6d48ad9 in free () from /lib/libc.so.6
#13 0xb6ef4b0f in operator delete(void*) () from /usr/lib/libstdc++.so.6
#14 0xb6ed572b 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 0xb6ed57da in std::basic_string<char, std::char_traits<char>, std::allocator<char> >::~basic_string() () from /usr/lib/libstdc++.so.6
#16 0xb6d0489f in __run_exit_handlers () from /lib/libc.so.6
#17 0xb6d048fd in exit () from /lib/libc.so.6
#18 0xb6cecc36 in __libc_start_main () from /lib/libc.so.6
#19 0x0804a481 in _start ()

Possible duplicates by query: bug 270816, bug 270786, bug 270720, bug 270628, bug 270594.

Reported using DrKonqi

Comment 1 Frank Reininghaus 2011-04-14 13:26:49 UTC

Thanks for the bug report! This crash is due to a bug in the Strigi library. The executable 'kfilemetadatareader' was introduced for KDE 4.7 in order to prevent that the buggy Strigi analyser crashes the entire Dolphin application.

@Peter: Maybe we should find out if there is a way to disable the crash dialog for kfilemetadatareader? The incoming bug reports don't help much, I think...

Comment 2 Peter Penz 2011-04-14 13:33:21 UTC

@Frank: I don't get a crash dialog when kfilemetadatareader crashes, I wonder what is necessary to enable/disable the crash dialog?

@Davide: It is strange that it can be reproduced "everytime" - it should only occur on specific file types where the corresponding Strigi analyzer crashes. Could you please give more information whether the crash only occurs on some specific files? Thanks!

Comment 3 Davide Marcelli 2011-04-14 13:47:17 UTC

@Peter
I have marked "everytime" because each click on a folder, image, song, video, text, appear the crash dialog, and this appens each time i use Dolphin. I have Strigi disabled if can help you.

Comment 4 Frank Reininghaus 2011-04-14 14:53:15 UTC

I think that Darío knows more about the crash dialog than most other people :-)
Maybe you can help us (see Peter's first question in comment 2)? Thanks!

Comment 5 Dario Andres 2011-04-14 15:03:31 UTC

Hi! IIRC you could call "KCrash::setDrKonqiEnabled(false);" after you init the KApplication on the kfilemetadatareader main function
http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/namespaceKCrash.html#a48919f4ca45cf8fff17e8a8c429f8df7

Another idea could be setting the bug report address of "kfilemetadatareader" to point to the Strigi tracker directly. So if people wants to send their reports, they will be redirected to the SourceForge Strigi tracker. Does that make sense ?

Cheers

Comment 6 Peter Penz 2011-04-14 15:11:00 UTC

Thanks Dario, will take care to disable DrKonqi in kfilemetadatareader. Setting the report address to the Strigi tracker is no good idea in my opinion: The Strigi analyzers crash very often, there are already enough bug reports in their tracker and the users will kill us if each time a Strigi analyzer crashes DrKonqi will appear ;-) (e.g. when hovering over some *.ppt files several DrKonqi-dialogs would appear...)

Comment 7 Christoph Feck 2011-04-14 15:47:42 UTC

This is bug 257944, but I had the impression Strigi got updated for 11.4 release...

Comment 8 Peter Penz 2011-04-14 20:33:24 UTC

I've just checked whether a crash in the kfilemetadataprocess results in opening DrKonqi but this does not happen. I also verified of course whether DrKonqi appears when Dolphin itself crashes and this works as expected.

Explanation: kfilemetadataprocess is no KApplication and like described at http://api.kde.org/4.x-api/kdelibs-apidocs/kdeui/html/namespaceKCrash.html#a48919f4ca45cf8fff17e8a8c429f8df7 DrKonqi is disabled per default.

So I'm marking this bug as duplicate of bug 257944 (at least judging from the callstack this seems to be the same rootcause).

I still don't understand why DrKonqi was opened in the environment of Davide (@Dario: Is it possible to globally enable DrKonqi somehow?).

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

Comment 9 Dario Andres 2011-04-16 00:37:37 UTC

I think George knows more about the internals of KCrash

Comment 10 George Kiagiadakis 2011-04-17 16:26:48 UTC

(In reply to comment #8)
> I still don't understand why DrKonqi was opened in the environment of Davide
> (@Dario: Is it possible to globally enable DrKonqi somehow?).

No, it cannot be enabled globally. Each process needs to enable it individually by calling the appropriate KCrash methods.