Bug 252182 - Krusader does not exit when quitting (keeps running in the background); caused by splash screen
Summary: Krusader does not exit when quitting (keeps running in the background); cause...
Status: RESOLVED DUPLICATE of bug 240319
Alias: None
Product: krusader
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Shie Erlich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-23 22:56 UTC by Daniel Hahler
Modified: 2010-12-07 07:16 UTC (History)
6 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Hahler 2010-09-23 22:56:11 UTC 
Version:           unspecified (using KDE 4.5.1) 
OS:                Linux

When calling the Quit action of Krusader, it does not exit really; the process keeps running.

Starting krusader again creates a new, separate instance (when not in single instance mode, of course).

Version: 2.2.0-beta1 "DeKade"

Reproducible: Always

Steps to Reproduce:
1. Enable the splash screen (Setting => Startup => Show splashscreen)
2. Stop and restart Krusader from a terminal
3. Quit it right away

Actual Results:  
The process does not end, and no shell prompt gets displayed.

Expected Results:  
A new shell prompt should get displayed and Krusader should have quit.

OS: Linux (i686) release 2.6.35-22-generic
Compiler: cc
Comment 1 Alexey Khuraskin 2010-10-14 23:45:21 UTC 
Reproduced on krusader version 2.2.0-beta1 "DeKade" from distribution

The problem disappeared after disabling splash-screen (thank you for workaround, Daniel!)
Comment 2 magist3r 2010-12-05 06:07:18 UTC 
*** Bug 240319 has been marked as a duplicate of this bug. ***
Comment 3 Francesco Davini 2010-12-05 16:03:00 UTC 
------- Comment #2 From magist3r@gmail.com 2010-12-05 06:07:18 (-) [reply] -------

*** Bug 240319 has been marked as a duplicate of this bug. ***

Can anyone explain the rationale after the above???
How can a bug reported back in June 2010 (240319) be a duplicate of this one here (252182) which was reported only in September? Someone has strange concepts about timelines or is there anything I cannot see?
Comment 4 magist3r 2010-12-05 16:46:53 UTC 
It is the same bug. I have marked my bug report as the duplicate of this one, that's all.
Comment 5 Kevin Kofler 2010-12-05 18:01:21 UTC 
You should in most cases mark the newer bug as a duplicate of the older one, not the other way round.

*** This bug has been marked as a duplicate of bug 240319 ***
Comment 6 Daniel Hahler 2010-12-06 13:53:23 UTC 
Kevin, it's not about the time line / bug number only; in general the master bug should become the one which contains better information (and e.g. workarounds).
Comment 7 Kevin Kofler 2010-12-07 07:16:07 UTC 
That's why I said "in most cases". :-)
Can we please stop this discussion here? It doesn't help actually getting the bug fixed.