Summary: | Dolphin crashed during KDE startup | ||
---|---|---|---|
Product: | [Applications] dolphin | Reporter: | David <davidsboogs> |
Component: | general | Assignee: | Peter Penz <peter.penz19> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | andresbajotierra, mail |
Priority: | NOR | ||
Version: | 16.12.2 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | My dolphin layout |
Description
David
2010-01-11 07:32:04 UTC
This seems to be the same as bug 198297, so the bug is still unfixed. @Peter: could it be related to session restore ? Regards @Dario: I tried hard to reproduce a crash by session restore (e. g. I restored 10 Dolphin instances with the folders panel each showing a different directory), but I could not reproduce the crash... @David: Would it be possible that you attach a screenshot of your Dolphin setup to this report? My guess is that the viewport of the tree is 0 and maybe this is resulted by a special layout... Just happened again, the boot after upgrading to RC2: Application: dolphin (1.4) KDE Platform Version: 4.3.95 (KDE 4.3.95 (KDE 4.4 RC2)) Qt Version: 4.6.0 Operating System: Linux 2.6.31-17-generic x86_64 Distribution: Ubuntu 9.10 I don't know what you mean by "a screenshot of [my] Dolphin setup" - When I shut down before crash I had about half a dozen windows in the session, some with multiple tabs, scattered on multiple desktops. They are gone now of course. (Unless you know a way to recover them from the session manager before my next reboot tomorrow - I don't, but that would be awesome to know if there is a way) I also have no idea what "viewport of the tree is 0 and maybe this is resulted by a special layout..." might mean. -- Information about the crash: -- Backtrace: "A useful backtrace could not be generated" (No clue why, I have the relevant -dbg packages installed) Created attachment 40187 [details]
My dolphin layout
Oh, Now I think I know what you mean - sorry about that. Anyway, here is what my dolphin windows look like. I don't think I have changed much, but of course I'm not getting potential new defaults on upgrades.
Can someone still reproduce this with the newest version of Dolphin (17.12.3)? Probably fixed. Well, all my dolphin windows Did crash on first boot after I upgraded my distro from Kubuntu 17.04 to 17.10 (Dolphin is now 17.04.3) - it couldn't find symbols though. Without them it looks like this, and I'd guess it's a different issue just because if nothing else it's been 8 years and new major QT version: Application: Dolphin (dolphin), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f60ff143280 (LWP 2025))] Thread 3 (Thread 0x7f60d6a23700 (LWP 2057)): #0 0x00007f60fe9fa06d in __GI___libc_read (fd=17, buf=0x7f60d6a22a90, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:26 #1 0x00007f60f03cc073 in ?? () from /usr/lib/nvidia-384/tls/libnvidia-tls.so.384.111 #2 0x00007f60f1be0280 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f60f1b9bc4b in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f60f1b9c110 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f60f1b9c27c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x00007f60f8c4b49b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x00007f60f8bf0e3a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007f60f8a103ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x00007f60f8a1529d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x00007f60f3d777fc in start_thread (arg=0x7f60d6a23700) at pthread_create.c:465 #11 0x00007f60fea0ab5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f60dffff700 (LWP 2029)): #0 0x00007f60fe9fe951 in __GI___poll (fds=0x7f60d801ae70, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x00007f60f1b9c169 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f60f1b9c27c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f60f8c4b49b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x00007f60f8bf0e3a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x00007f60f8a103ca in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x00007f60f90c7e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x00007f60f8a1529d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x00007f60f3d777fc in start_thread (arg=0x7f60dffff700) at pthread_create.c:465 #9 0x00007f60fea0ab5f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f60ff143280 (LWP 2025)): [KCrash Handler] #6 0x00007f60fed24d2d in ?? () from /usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so #7 0x00007f60fed2e051 in ?? () from /usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so #8 0x00007f60fed2ffc6 in ?? () from /usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so #9 0x00007f60fc284cd8 in KMainWindow::readPropertiesInternal(KConfig*, int) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #10 0x00007f60fc284d22 in KMainWindow::restore(int, bool) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #11 0x00007f60fed33dfa in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_dolphin.so #12 0x00007f60fe9171c1 in __libc_start_main (main=0x5585c8e38730, argc=3, argv=0x7fff6c0f0e38, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff6c0f0e28) at ../csu/libc-start.c:308 #13 0x00005585c8e3876a in _start () @David, yes, this is probably a different issue. Please file a new bug if you can reproduce this crash (and install the development packages first). I'll close this bug now. |