Bug 157886 - Dolphin fails to start up
Summary: Dolphin fails to start up
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Peter Penz
: 158709 (view as bug list)
Depends on:
Reported: 2008-02-15 19:15 UTC by András Manţia
Modified: 2008-03-20 13:05 UTC (History)
3 users (show)

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

My dolphinrc (1.45 KB, text/plain)
2008-02-16 09:15 UTC, András Manţia

Note You need to log in before you can comment on or make changes to this bug.
Description András Manţia 2008-02-15 19:15:09 UTC
Version:            (using Devel)
Installed from:    Compiled sources

qt-copy, kde from trunk, today. The Dolphin mainwindow appears than quickly disappears. The program does not crash, here is the output:
(gdb) set args --nofork
(gdb) r
Starting program: /opt/kde4/bin/dolphin --nofork
[Thread debugging using libthread_db enabled]
[New Thread 0x2b16add56530 (LWP 16739)]
Qt: gdb: -nograb added to command-line options.
         Use the -dograb option to enforce grabbing.
Object::connect: No such slot DolphinView::updateCutItems()
[New Thread 0x40800950 (LWP 16743)]
QProcess: Destroyed while process is still running.
[Thread 0x40800950 (LWP 16743) exited]

Program exited normally.
Comment 1 Peter Penz 2008-02-15 20:33:51 UTC
Hmm, I just committed a patch that no connecting is done anymore to a non-existent slot, but I doubt that this was the reason of the crash. Would it be possible that you attach your dolphinrc file to this bug-report (~/.kde4/share/config/dolphinrc)? Thanks!
Comment 2 András Manţia 2008-02-16 09:14:12 UTC
I doubt that connection caused the problem, more suspect is the other line from the debug output:
QProcess: Destroyed while process is still running.

I'll attach the dolphinrc as well.
Comment 3 András Manţia 2008-02-16 09:15:06 UTC
Created attachment 23592 [details]
My dolphinrc
Comment 4 Peter Penz 2008-02-16 13:29:37 UTC
Thanks, I can confirm the crash here too. The root cause is that in dolphinrc


is set. I'll take a look on this but I'm wondering, because AFAIK we did not change anything on this topic...
Comment 5 András Manţia 2008-02-16 13:35:34 UTC
IIRC KComboBox was recently changed if you use that in Dolphin if Editab
Comment 6 Peter Penz 2008-03-03 10:24:47 UTC
*** Bug 158709 has been marked as a duplicate of this bug. ***
Comment 7 David Faure 2008-03-20 13:03:28 UTC
OK, let's see. Breakpoint in QCoreApplication::quit() shows that it's receiving a posted QEvent::Quit event. Conditional breakpoint in QCoreApplication::postEvent shows that it comes from QApplicationPrivate::emitLastWindowClosed. 

#4  0x00002b5fbc34ed9c in KUrlNavigator::Private::deleteButtons (this=0x90c470)
    at /d/kde/src/4/kdelibs/kfile/kurlnavigator.cpp:774
774             button->close();

Why close() being called on a non-toplevel??
I think hide() was meant instead. Yep, works.
Comment 8 David Faure 2008-03-20 13:05:44 UTC
SVN commit 787999 by dfaure:

Fix "Dolphin fails to start up" when having EditableUrl=true in dolphinrc.
close() being called on buttons was triggering "lastWindowClosed -> quit" in Qt ;-)
hide() was meant instead.
BUG: 157886

 M  +3 -3      kurlnavigator.cpp  

WebSVN link: http://websvn.kde.org/?view=rev&revision=787999