Krusader process doesn't exit after closing the window

Bug #641650 reported by mlx on 2010-09-17
This bug affects 13 people
Affects Status Importance Assigned to Milestone
krusader (Ubuntu)

Bug Description

Binary package hint: krusader

1) Fully updated Maverick installation
2) Installed: 1:2.2.0~beta1-1
3) The process should exit
4) The process keeps running (no visible errors from launching krusader in terminal [a]) so the number of krusader processes grows - this is a PITA, as KDE will launch THAT MANY instances of Krusader on next login - of course, closing them does nothing, the user has to figure out that the processes are still running and manually kill them.

michal@esprimo:/tmp$ krusader
krusader(2194) UserAction::UserAction: Initialisising useractions...
krusader(2194) UserAction::UserAction: 10 useractions read.
QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory
QFileSystemWatcher: failed to add paths: /home/michal/.config/ibus/bus
Bus::open: Can not get ibus-daemon's address.
IBusInputContext::createInputContext: no connection to ibus-daemon

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: krusader 1:2.2.0~beta1-1
ProcVersionSignature: Ubuntu 2.6.35-22.32-generic
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Fri Sep 17 23:39:04 2010
InstallationMedia: Kubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100907)
 PATH=(custom, user)
SourcePackage: krusader

mlx (myxal-mxl) wrote :
Floop (floop) wrote :

Exactly the same problem with my Maverick 64bit installation.

mlx (myxal-mxl) wrote :

Just noticed this is actually already reported (and possibly fixed) upstream>

mlx (myxal-mxl) wrote :
tags: added: patch-available
Changed in krusader (Ubuntu):
status: New → In Progress
Thomas87 (knot-tomas) on 2010-10-14
visibility: public → private
visibility: private → public
Ganton (ganton) wrote :

For anyone interested: there's a discussion about the solution to this problem in

incunabulum (mz-incunabulum) wrote :

There is a fix by the developers published in June. There are various confirmations that this fix works. So, any chance to get this finally fixed before 11.04? Just publishing the Beta2 should work.

yurikoles (yurikoles) wrote :

it seems that this bug was fixed in Debian testing.

Ganton (ganton) wrote :

> So, any chance to get this finally fixed before 11.04?

In they said that a workaround was useful to avoid the problem:
Disable the splash screen (Go to Krusader, to the menu Setting => Startup => Show splashscreen)

Fabian Kosmale (fakos) wrote :

@Ganton: That workaround doesn't work for me in 11.04 beta 2.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.