Bug 222178 - Dolphin crashed during KDE startup
Summary: Dolphin crashed during KDE startup
Status: RESOLVED FIXED
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-11 07:32 UTC by David
Modified: 2018-03-31 12:20 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
My dolphin layout (109.32 KB, image/png)
2010-01-24 11:00 UTC, David
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David 2010-01-11 07:32:04 UTC
Application: dolphin (1.4)
KDE Platform Version: 4.3.90 (KDE 4.3.90 (KDE 4.4 RC1))
Qt Version: 4.6.0
Operating System: Linux 2.6.31-17-generic x86_64
Distribution: Ubuntu 9.10

-- Information about the crash:
I just upgraded to KDE 4.4rc1 and on the third reboot since then, (the second with a desktop and panels present) I encountered this crash immediately on startup.  The (closed) bug that this is a Potential Duplicate of mentioned folder views, and sure enough the upgrade enabled a Desktop Folder view on my desktop which I didn't have before. (I was thinking I would keep it, but not if it crashes Dolphin)


 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  QWidget::height (this=0x2e61650) at /usr/include/qt4/QtGui/qwidget.h:1009
#6  KTreeView::KTreeViewPrivate::startScrolling (this=0x2e61650) at ../../../../apps/dolphin/src/panels/folders/ktreeview.cpp:61
#7  0x0000000000445fb8 in KTreeView::KTreeViewPrivate::qt_metacall (this=0x2e61650, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffbc4edd40) at ./ktreeview_p.moc:75
#8  0x00007f521da75dc3 in QMetaObject::activate (sender=0x2e619d0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fffbc4edd40) at kernel/qobject.cpp:3294
#9  0x00007f521da72a33 in QObject::event (this=0x2e619d0, e=0x7fffbc4ee400) at kernel/qobject.cpp:1224
#10 0x00007f521e655e8c in QApplicationPrivate::notify_helper (this=0x2418a50, receiver=0x2e619d0, e=0x7fffbc4ee400) at kernel/qapplication.cpp:4242
#11 0x00007f521e65c48d in QApplication::notify (this=0x7fffbc4ee750, receiver=0x2e619d0, e=0x7fffbc4ee400) at kernel/qapplication.cpp:4125
#12 0x00007f521f356e16 in KApplication::notify (this=0x7fffbc4ee750, receiver=0x2e619d0, event=0x7fffbc4ee400) at ../../kdeui/kernel/kapplication.cpp:302
#13 0x00007f521da6304c in QCoreApplication::notifyInternal (this=0x7fffbc4ee750, receiver=0x2e619d0, event=0x7fffbc4ee400) at kernel/qcoreapplication.cpp:704
#14 0x00007f521da8fd52 in QCoreApplication::sendEvent (this=0x2424a60) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#15 QTimerInfoList::activateTimers (this=0x2424a60) at kernel/qeventdispatcher_unix.cpp:603
#16 0x00007f521da8c958 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#17 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#18 0x00007f52199b6bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#19 0x00007f52199ba598 in ?? () from /lib/libglib-2.0.so.0
#20 0x00007f52199ba6c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#21 0x00007f521da8c623 in QEventDispatcherGlib::processEvents (this=0x23e0b70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#22 0x00007f521e7042fe in QGuiEventDispatcherGlib::processEvents (this=0x309ad90, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#23 0x00007f521da61972 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#24 0x00007f521da61d4c in QEventLoop::exec (this=0x7fffbc4ee6a0, flags=) at kernel/qeventloop.cpp:201
#25 0x00007f521da65a8b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#26 0x000000000043a535 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../../apps/dolphin/src/main.cpp:101

This bug may be a duplicate of or related to bug 198297.

Possible duplicates by query: bug 198297.

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-11 13:48:36 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
Comment 2 Peter Penz 2010-01-12 12:45:21 UTC
@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...
Comment 3 David 2010-01-24 10:43:45 UTC
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)
Comment 4 David 2010-01-24 11:00:47 UTC
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.
Comment 5 Julian Steinmann 2018-03-13 19:58:30 UTC
Can someone still reproduce this with the newest version of Dolphin (17.12.3)? Probably fixed.
Comment 6 David 2018-03-15 07:12:14 UTC
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 ()
Comment 7 Julian Steinmann 2018-03-31 12:20:33 UTC
@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.