Version: unknown (using KDE 3.1.0) Installed from: SuSE Compiler: gcc version 2.95.3 20010315 (SuSE) OS: Linux (i686) release 2.5.58 A corrupt JPEG can cause this message when konqueror tries to produce a thumbnail: mcop warning: user defined signal handler found for SIG_PIPE, overriding kioslave : ###############SEG FAULT############# First line is unrelated, the warning comes with "good" images as well. Obviously, no thumbnail is produced. Now if the mouse pointer is moved over the broken picture, konquerer crashes immediately instead of providing the file tip. One way to achieve this is by putting extra data in JPEG segments. I suppose the parser doesn't take it well if it doesn't find a marker where one is expected (at the end of a segment, that is). I've got a 28 byte file that does the trick.
Created attachment 977 [details] this file causes crash in kioslave and konqueror * kioslave segfaults when trying to thumbnail this file * konqueror crashes when creating file tip for this file ("Show file tips must be enabled", "Show previews in file tips" makes no difference(!))
With KDE 3.1.1, konqueror itself doesn't crash anymore. Still seeing an error message for kioslave, though: kioslave: ####### CRASH ###### pid = 3866 signal = 11 Leaves me wondering how CRASH with signal 11 is an improvement over SEGFAULT :). Half of it solved. Leaving as not resolved.
With KDE 3.1.1 RedHat packages (RedHat 8.0), there are also a lot of following messagess: "kioslave: ####### CRASH ###### pid = xxxx signal = 11" in .xsession-errors file. However it does not depend only on JPEG file thumbnail which is to be displayed, but as I suppose, this is also with MS doc or xls files. Of course no thumbnail is displayed. While there are many files in folder to be thumbnailed, this causes kio_slave to eat a lot of memory resources. After I kill all kio* processess, the system gets back to normall
The CRASH message is gone in KDE 3.2.1 AFAICT. I assume that means somebody fixed the bug rather than just removing the error message :-).