Bug 249374

Summary: Dolphin 1.5.9 only runs successfully once, can't close and then restart dolphin.
Product: [Applications] dolphin Reporter: N.M <IcarianHeights>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: normal CC: cfeck, kernelcruncher
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description N.M 2010-08-29 03:10:13 UTC 
Version:           unspecified (using Devel) 
OS:                Linux

Upon inital logon I am able to open Dolphin via the application launcher menu/start menu as expected. I am able to navigate and otherwise use Dolphin as expected.

I then exit out of Dolphin by either just hitting the 'X' close window button in the upper right hand corner, or selecting File-Exit from the file menu. Dolphin appears to exit normally and gives no warnings/errors.

However, if I then attempt to open dolphin again anytime after I initially opened it, the program just hangs. To be specific the an entry appears on in taskbar with a constantly looping cirlce and the bouncy Dolphin icon/cursor appears indicating Dolphin is attempting to open. After 30 secs or so the tak bar entry appears and nothing else happens or is communicated to the user.

Running a "ps aux | grep dolphin" usually then shows at 3-4 processes an example of which is posted below:

carus   25151  1.0  0.8 387860 34624 ?        Sl   20:54   0:08 kdeinit4: dolphin [kdeinit] -icon system-file-manager -caption Dolphin
icarus   25775  0.0  0.2 260316  9992 ?        S    21:09   0:00 kdeinit4: dolphin [kdeinit] -icon system-file-manager -caption Dolphin
icarus   25776  0.0  0.0      0     0 ?        Z    21:09   0:00 [dolphin] <defunct>

killing all these processes from then allows me to run Dolphin again. However I have to manually kill these processes everytime I try to close the application in order to run it again.

Reproducible: Always

Steps to Reproduce:
Start Dolphin, then exit dolphin.

Attempt to start Dolphin again.

Actual Results:  
Again a window appears in my taskmanager bar/pamel with the words "Dolphin" and an endlessly looping circle in the left corner of the window... indicating it is attempting to open.

Also my mouse cursor changes to the bouncing icon of Dolphin also indicating Dolphin is attempting to load. However, Dolphin is unable to start and after 30 secs or so the window in the task manager panel/bar goes away.

Expected Results:  
Dolphin file manager open successfully and allow for accessing system's files.

OS: Linux (x86_64) release 2.6.34-12-default
Compiler: gcc
Comment 1 N.M 2010-08-29 19:02:45 UTC 
Just some more information I am using Dolphin 1.5.9 under the current KDE trunk repo from opensuse 11.3 repos.

Using the command "kde4-config -v" returns the following: QT 4.6.3 and KDE Development Platform: 4.5.66 (4.6 >= 20100825) "release 6"
       

http://pastebin.com/xbswAMYR

This is the pastebin of the processes that are not stopped when closing the dolphin window and that have to be manually stopped via CLI.
Comment 2 N.M 2010-08-29 22:30:26 UTC 
(In reply to comment #1)
> Just some more information I am using Dolphin 1.5.9 under the current KDE trunk
> repo from opensuse 11.3 repos.
> 
> Using the command "kde4-config -v" returns the following: QT 4.6.3 and KDE
> Development Platform: 4.5.66 (4.6 >= 20100825) "release 6"
> 
> 
> http://pastebin.com/xbswAMYR
> 
> This is the pastebin of the processes that are not stopped when closing the
> dolphin window and that have to be manually stopped via CLI.

Also wanted to add this pastebin of errors I received when opening dolphin for the first time since login from the command line. Might be related.

http://pastebin.com/vuqTVYWt
Comment 3 Christoph Feck 2010-08-30 02:20:25 UTC 
Seeing it here since about 10 days. Probably related to UPNP changes to trunk, but developers are still investigating.
Comment 4 N.M 2010-08-30 17:36:20 UTC 
(In reply to comment #3)
> Seeing it here since about 10 days. Probably related to UPNP changes to trunk,
> but developers are still investigating.

Great, also this bug report seems to be a duplicate of 

https://bugs.kde.org/show_bug.cgi?id=249451

which has some good info attached, (i.e more responses/comments and even a backtrace) maybe they can be merged somehow??
Comment 5 Peter Penz 2010-08-31 10:59:45 UTC 
*** Bug 249451 has been marked as a duplicate of this bug. ***
Comment 6 Christoph Feck 2010-08-31 13:14:07 UTC 
In bug 249557 it was suggested not to file a new bug report to solid developers. Since the fixing commit resolved bug 249557, I mark this one as a duplicate.

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