Red Hat Bugzilla – Bug 620328
krusader hangs on close / duplicate session start
Last modified: 2016-11-30 19:29:21 EST
Created attachment 435964 [details]
Fix from upstream
the krusader application doesn't shut down properly and leaves
a dead task behind. This leads to an increasing number of
krusader instances on KDE start.
Fix from upstream is available and works fine.
Reports of the same bug:
I've been noticing this myself for a while, it seems triggered by one of our Qt or kdelibs updates.
The upstream commit the attached patch is from: http://websvn.kde.org/?view=revision&revision=1154581
krusader-2.2.0-0.5.beta1.fc14 has been submitted as an update for Fedora 14.
krusader-2.2.0-0.5.beta1.fc13 has been submitted as an update for Fedora 13.
krusader-2.2.0-0.5.beta1.fc12 has been submitted as an update for Fedora 12.
krusader-2.2.0-0.5.beta1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update krusader'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/krusader-2.2.0-0.5.beta1.fc13
krusader-2.2.0-0.5.beta1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
krusader-2.2.0-0.5.beta1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
krusader-2.2.0-0.5.beta1.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
I reopen this bug.
I use Fedora 14 and krusader-2.2.0-0.5.beta1.fc14, and this bug still persist...
Krusader don't close properly, and in top I have a krusader process with 50% cpu.
Other strange thing: when I want delete files, my laptop freeze and I re-start my session with CTRL+ALT+BACKSPACE
Well, I can reopen this, but I haven't seen this happen with 0.5.beta1. For me, Krusader closes just fine with krusader-2.2.0-0.5.beta1.fc13.
(In reply to comment #12)
> Well, I can reopen this, but I haven't seen this happen with 0.5.beta1. For me,
> Krusader closes just fine with krusader-2.2.0-0.5.beta1.fc13.
For information, this bug is not repetitive, it come approximately 1 for 4...
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.