Version: unspecified (using KDE 4.5.0) OS: Linux Dolphin crahes ramdomly, but it seems to be more frequently when I'm browsing a USB memory. I always report bugs with the window that appears on after crashes, but, it never founds "debugger symbols for this app.", even though I have reported dolphin bugs previuously, with this KDE version (bug . So, it seems to be, that the backtrace is incomplete. Againg, I don't know haw to generate a complete backtrace if the crash reporter is telling me alwaws that this app. hasn't any debug symbol! I really sorry for this, I feel quite guilty/unusefull. Also, sorry if this bug is already reported, but I really don't understand backtraces, altough for the titles, this bug may be a duplicate of bug 199219 and bug 237479. Reproducible: Always Steps to Reproduce: Open my USB memory, browse some folders boom! OS: Linux (x86_64) release 2.6.32-24-generic Compiler: cc default widget style desktop effect ON
Created attachment 51148 [details] poor backtrace
another one: Application: dolphin (1.5) KDE Platform Version: 4.5.00 (KDE 4.5.0) Qt Version: 4.7.0 Operating System: Linux 2.6.32-24-generic x86_64 Distribution: Ubuntu 10.04.1 LTS -- Information about the crash: <En detalle, comente que estaba haciendo cuando la aplicación se cerró.> -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [Current thread is 1 (Thread 0x7fc4c423b760 (LWP 14236))] Thread 2 (Thread 0x7fc4b0c4a710 (LWP 14241)): #0 0x00007fc4c3b17f83 in *__GI___poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87 #1 0x00007fc4bb6a04a9 in ?? () from /lib/libglib-2.0.so.0 #2 0x00007fc4bb6a08fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #3 0x00007fc4bff12bd6 in QEventDispatcherGlib::processEvents (this=0x14e9ae0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:414 #4 0x00007fc4bfee57b2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #5 0x00007fc4bfee5b9c in QEventLoop::exec (this=0x7fc4b0c49db0, flags=) at kernel/qeventloop.cpp:201 #6 0x00007fc4bfdf123d in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:490 #7 0x00007fc4bfec56d8 in QInotifyFileSystemWatcherEngine::run (this=0x15af3b0) at io/qfilesystemwatcher_inotify.cpp:248 #8 0x00007fc4bfdf41be in QThreadPrivate::start (arg=0x15af3b0) at thread/qthread_unix.cpp:266 #9 0x00007fc4bdc269ca in start_thread (arg=<value optimized out>) at pthread_create.c:300 #10 0x00007fc4c3b246fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112 #11 0x0000000000000000 in ?? () Thread 1 (Thread 0x7fc4c423b760 (LWP 14236)): [KCrash Handler] #6 0x00007fc4b89ff309 in ?? () from /lib/libdbus-1.so.3 #7 0x00007fc4b89e042d in ?? () from /lib/libdbus-1.so.3 #8 0x00007fc4b89f1d0d in ?? () from /lib/libdbus-1.so.3 #9 0x00007fc4b89e3dde in ?? () from /lib/libdbus-1.so.3 #10 0x00007fc4c0232e03 in q_dbus_timeout_handle (this=0xf1ab50, e=<value optimized out>) at qdbus_symbols_p.h:174 #11 QDBusConnectionPrivate::timerEvent (this=0xf1ab50, e=<value optimized out>) at qdbusintegrator.cpp:1040 #12 0x00007fc4bfef8599 in QObject::event (this=0xf1ab50, e=0x0) at kernel/qobject.cpp:1183 #13 0x00007fc4c0b31cdc in QApplicationPrivate::notify_helper (this=0xf33920, receiver=0xf1ab50, e=0x7fffd5a7e770) at kernel/qapplication.cpp:4389 #14 0x00007fc4c0b377cd in QApplication::notify (this=0x7fffd5a7ead0, receiver=0xf1ab50, e=0x7fffd5a7e770) at kernel/qapplication.cpp:4270 #15 0x00007fc4c1886eb6 in KApplication::notify (this=0x7fffd5a7ead0, receiver=0xf1ab50, event=0x7fffd5a7e770) at ../../kdeui/kernel/kapplication.cpp:310 #16 0x00007fc4bfee6a8c in QCoreApplication::notifyInternal (this=0x7fffd5a7ead0, receiver=0xf1ab50, event=0x7fffd5a7e770) at kernel/qcoreapplication.cpp:732 #17 0x00007fc4bff160b2 in QCoreApplication::sendEvent (this=0xf2b4f0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #18 QTimerInfoList::activateTimers (this=0xf2b4f0) at kernel/qeventdispatcher_unix.cpp:602 #19 0x00007fc4bff12e94 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184 #20 0x00007fc4bb69c8c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #21 0x00007fc4bb6a0748 in ?? () from /lib/libglib-2.0.so.0 #22 0x00007fc4bb6a08fc in g_main_context_iteration () from /lib/libglib-2.0.so.0 #23 0x00007fc4bff12b83 in QEventDispatcherGlib::processEvents (this=0xeff560, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412 #24 0x00007fc4c0be380e in QGuiEventDispatcherGlib::processEvents (this=0x1, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #25 0x00007fc4bfee57b2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #26 0x00007fc4bfee5b9c in QEventLoop::exec (this=0x7fffd5a7ea10, flags=) at kernel/qeventloop.cpp:201 #27 0x00007fc4bfee9c4b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009 #28 0x00007fc4c3e0ce6f in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../../../apps/dolphin/src/main.cpp:98 #29 0x00007fc4c3a5cc4d in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fffd5a7efe8) at libc-start.c:226 #30 0x00000000004006b9 in _start () Reportar a https://bugs.kde.org
*** This bug has been marked as a duplicate of bug 226725 ***
(In reply to comment #3) > > *** This bug has been marked as a duplicate of bug 226725 *** Following bug 226725, and then 208921, it seems to be that the problem was Nepomuk, with I has disabled since I installed the OS. THe rest is as default. Sorry for omitting this before
The root cause for this is a bug in libdbus (see https://bugs.freedesktop.org/show_bug.cgi?id=17754). The bug has been fixed in the meantime, but AFAIK not been backported yet to the stable branch of libdbus :-( The libdbus issue affects the whole KDE, not only Dolphin but it gets triggered very often by Dolphin now. To bypass this issue, please disable tooltips and the Information of Dolphin until an updated version of libdbus gets available.
Sorry for this silly question but, I speak spanish, mi KDE is in spanish so What kind of options do you reffer with "tooltips" and "Information of Dolphin"? I mean, what kind of options has "tooltips"? I'm saying this, because the only I know is "search bar", with I have already disabled. Thank you
"Tooltips" are the blue bubbles when moving the mouse above a file or directory. The tooltips can be turned off in the menu Settings -> Configure Dolphin... -> General (= last entry on the bottom) -> [ ] Show tooltips (= 3rd checkbox from the bottom). The "Information Panel" is the grey window on the right showing a preview of the file and some other information. You can close it by pressing the key F11. I hope this helps :-) In the worst case you temporary can switch the application language of Dolphin to English in the menu Help -> Switch application language...
(In reply to comment #7) > "Tooltips" are the blue bubbles when moving the mouse above a file or > directory. The tooltips can be turned off in the menu Settings -> Configure > Dolphin... -> General (= last entry on the bottom) -> [ ] Show tooltips (= 3rd > checkbox from the bottom). > > The "Information Panel" is the grey window on the right showing a preview of > the file and some other information. You can close it by pressing the key F11. > > I hope this helps :-) In the worst case you temporary can switch the > application language of Dolphin to English in the menu Help -> Switch > application language... Oh, thank you very much! Now "Information" should have been quite obvious for me but, I really hadn't any idea of what "tooltips" was hehe. A pity for the "+" and "-" signs, they were very helpful. Well, again, thankyou very much Peter