Bug 172723

Summary:	Dolphin doesn't start / crashes immediately
Product:	[Applications] dolphin	Reporter:	Hans Überacher <lodp>
Component:	general	Assignee:	Peter Penz <peter.penz19>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	frank78ac
Priority:	NOR
Version:	16.12.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:
Attachments:	backtrace

Description Hans Überacher 2008-10-13 15:43:18 UTC

Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

I can't say much other than that I can't seem to start dolphin anymore. Don't know how to trigger this. Reboot solves it.

Comment 1 Hans Überacher 2008-10-13 15:44:46 UTC

Created attachment 27852 [details]
backtrace

Comment 2 Frank Reininghaus 2008-10-13 18:10:16 UTC

Thanks for the bug report. Please do not attach backtraces but paste them inline (see below) because that makes looking for duplicates easier for us.

Does a reboot solve the problem forever for you, or does it return at some point?

It might be a duplicate of bug 169103. Could you
provide the contents of your dolphinrc file (probably located at
~/.kde4/share/config/dolphinrc) to be sure? If I'm right, deleting that file
should solve the problem.

Application: Dolphin (dolphin), signal SIGABRT
(no debugging symbols found)
...
(no debugging symbols found)
[KCrash handler]
#6  0xb7f40410 in __kernel_vsyscall ()
#7  0xb6782085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6783a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb7588367 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb7588458 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb7588505 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb7dc1321 in KIO::filePreview () from /usr/lib/kde4/lib/libkio.so.5
#13 0x0807e124 in ?? ()
#14 0xb6c518b0 in QWidget::event () from /usr/lib/libQtGui.so.4
#15 0xb6bf9f9c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#16 0xb6bfece8 in QApplication::notify () from /usr/lib/libQtGui.so.4
#17 0xb7b13483 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#18 0xb767c0b9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#19 0xb6c4fc3b in QWidgetPrivate::show_helper () from /usr/lib/libQtGui.so.4
#20 0xb6c4f921 in QWidgetPrivate::show_recursive ()
   from /usr/lib/libQtGui.so.4
#21 0xb6c4fa8b in QWidgetPrivate::showChildren () from /usr/lib/libQtGui.so.4
#22 0xb6c4fb51 in QWidgetPrivate::show_helper () from /usr/lib/libQtGui.so.4
#23 0xb6c501b8 in QWidget::setVisible () from /usr/lib/libQtGui.so.4
#24 0xb6f7eeb9 in ?? () from /usr/lib/libQtGui.so.4
#25 0xb6f7f3aa in ?? () from /usr/lib/libQtGui.so.4
#26 0xb6fad4dd in ?? () from /usr/lib/libQtGui.so.4
#27 0xb6fadd09 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb6fa8d04 in QMainWindow::restoreState () from /usr/lib/libQtGui.so.4
#29 0xb7bcb822 in KMainWindow::applyMainWindowSettings ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#30 0xb7c07012 in KXmlGuiWindow::applyMainWindowSettings ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#31 0xb7bc8e75 in KMainWindow::setAutoSaveSettings ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#32 0xb7bc8eec in KMainWindow::setAutoSaveSettings ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#33 0xb7c070eb in KXmlGuiWindow::finalizeGUI ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#34 0xb7c05396 in KXMLGUIBuilder::finalizeGUI ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#35 0xb7c06fc7 in KXmlGuiWindow::finalizeGUI ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#36 0xb7c10ef7 in KXMLGUIFactory::addClient ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#37 0xb7c07839 in KXmlGuiWindow::createGUI ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#38 0xb7c07a09 in KXmlGuiWindow::setupGUI ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#39 0xb7c07b11 in KXmlGuiWindow::setupGUI ()
   from /usr/lib/kde4/lib/libkdeui.so.5
#40 0x0806c6c9 in _start ()
#0  0xb7f40410 in __kernel_vsyscall ()

Comment 3 Hans Überacher 2008-10-13 22:02:44 UTC

Hi, thanks for your help. I'll remember pasting backtraces inline for next time.

The error survived a reboot the last time I tried. Removing dolphinrc really did it for me, so it might be a duplicate. At any rate, I'm confident I never moved either one of the panels out of the main window before (as the instructions for triggering the crash in the comments there go). Although when I do now, dolphin does crash on the next startup, as predicted.


Here's the content of dolphinrc before the removal:

[General]
FirstRun=false
ViewPropsTimestamp=2008,10,9,9,27,6

[KPropertiesDialog]
Height 800=465
Width 1280=273

[MainWindow]
Height 800=738
State=AAAA/wAAAAD9AAAAAwAAAAAAAABpAAACmPwCAAAAAvsAAAAYAHQAcgBlAGUAVgBpAGUAdwBEAG8AYwBrAAAAAAD/////AAAAFwAH///7AAAAFABwAGwAYQBjAGUAcwBEAG8AYwBrAQAAAEoAAAKYAAAAVAAH//8AAAAB/////QAAApj8AgAAAAH7AAAAEABpAG4AZgBvAEQAbwBjAGsDAAAETwAAAF8AAACwAAACmAAAAAMAAAUA/////fwBAAAAAfsAAAAYAHQAZQByAG0AaQBuAGEAbABEAG8AYwBrAAAAAAD/////AAAASAAH//8AAASUAAACmAAAAAQAAAAEAAAACAAAAAj8AAAAAQAAAAIAAAABAAAAFgBtAGEAaQBuAFQAbwBvAGwAQgBhAHIBAAAAAAAABQAAAAAAAAAAAA==
Width 1280=1280

Comment 4 Frank Reininghaus 2008-10-13 22:23:37 UTC

Hans, thanks for the update! I verified that I get exactly the same backtrace both when running Dolphin with your dolphinrc file and when moving panels out of the window and restarting. Therefore, I'm pretty sure it's a duplicate. You're probably right, though: There seems to be more than one way to get the dolphinrc into a state that crashes Dolphin on startup.

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