Bug 173190 - KCrash: Application 'dolphin' crashing
Summary: KCrash: Application 'dolphin' crashing
Status: RESOLVED DUPLICATE of bug 169103
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-20 14:27 UTC by Holger Hellmuth
Modified: 2008-10-21 23:56 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Holger Hellmuth 2008-10-20 14:27:38 UTC
Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Debian testing/unstable Packages

Eine korrekte Rückverfolgung ist nicht möglich.
Wahrscheinlich sind die Dateien Ihres Systems in einer Weise erstellt worden, die eine solche Rückverfolgung (Backtrace) nicht erlaubt. Oder der so genannte „Stack Frame“ für das Programm wurde durch den Absturz unbrauchbar gemacht.

Tranlation: No backtrace possiblr

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5fee6c0 (LWP 8456)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb68cafeb in nanosleep () from /lib/libc.so.6
[Current thread is 0 (process 8456)]

Thread 1 (Thread 0xb5fee6c0 (LWP 8456)):
#0  0xb68cafeb in nanosleep () from /lib/libc.so.6
#1  0xb68cae30 in sleep () from /lib/libc.so.6
#2  0xb7b6afc8 in ?? () from /usr/lib/libkdeui.so.5
#3  0x00000000 in ?? ()
#0  0xb68cafeb in nanosleep () from /lib/libc.so.6



Terminal-message:
holger@siduxbox:~$ dolphin
ASSERT: "(*it).isValid()" in file /tmp/buildd/kde4libs-4.1.2/kio/kio/previewjob.cpp, line 565
<unknown program name>(8455)/: Communication problem with  "dolphin" , it probably crashed. 
Error message was:  "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " 

holger@siduxbox:~$ KCrash: Application 'dolphin' crashing...
sock_file=/home/holger/.kde4/socket-siduxbox/kdeinit4__0
Comment 1 Holger Hellmuth 2008-10-20 14:29:02 UTC
My Linux is Sidux (Debian SID), but I installed KDE4 fron experimental source.
Gruß
Holger Hellmuth
Comment 2 Oliver Putz 2008-10-21 20:23:34 UTC
Hello,

Thanks for your report. Unfortunately your backtrace is not really usable as is. Can you have a look at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and try to install the debugging packages for your distribution? Can you reproduce the crash? If so, how? If not: What where you doing when the crash occurred?
Comment 3 Frank Reininghaus 2008-10-21 23:56:46 UTC
I'm 99.8% sure that this is a duplicate. The bug will be fixed in KDE 4.1.3. To solve your problem now, delete the dolphinrc file (probably located at
~/.kde4/share/config/dolphinrc or ~/.kde/...). If I'm wrong and this does not help, please tell us and reopen this bug report. Thanks!

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