Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 334725 - kde-misc/krusader-2.2.0_beta1: Stuck in an infinite loop at exit
Summary: kde-misc/krusader-2.2.0_beta1: Stuck in an infinite loop at exit
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High critical (vote)
Assignee: Gentoo KDE team
Depends on:
Reported: 2010-08-27 03:03 UTC by Navid Zamani
Modified: 2011-01-09 14:56 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---

Fixup ebuild (krusader-2.2.0_beta1-r1.ebuild,933 bytes, text/plain)
2010-11-04 18:29 UTC, Vadim Fint
Fixup patch (krusader-2.2.0_beta1-fix-closing-bug-on-recent-qt.patch,507 bytes, patch)
2010-11-04 18:30 UTC, Vadim Fint
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Navid Zamani 2010-08-27 03:03:17 UTC
Krusader stays in an infinite loop when you close it. I looked into it a bit, and it appears to rotate in the qt4 main event loop or something (first time I used GDB, and I’m not a KDE programmer, so I can’t be more exact).

It wouldn’t be half that annoying, if it would not mean, that after some normal usage during the day, not knowing of the problem, you have a lot of krusader processes running in the background, slowing everything down.
And most annnoyingly, since they all get stored in the session, they all come up next morning. Which means a flood of Krusader windows. Plus, when you close them all, of course you’re no better off that before you rebooted. Still slow and everything. (Although as a emergency workaround, you can either force kde, to not store krusader in a session, or just not ever close your single krusader window.)

Reproducible: Always

Steps to Reproduce:
1. Run Krusader.
2. Close its window.
3. Watch it run forever, via top or ps.
4. Run another couple of Krusader processes.
5. Close all those windows too.
6. Log out.
7. Log in again.

Actual Results:  
Lots of Krusader windows pop up.

Expected Results:  
Krusader should exit properly, not hog any resources anymore, and not come up at next login. Even when not using above session managemend blocking workaround.

Severety: Crashes = critical, according to Bugzilla.
Also, the file manager is the most important piece of software on a computer, except for the kernel. And since there is no other real file manager for KDE (Dolphin is an insult, even to mentally very limited people.), I say, Bugzilla is about right.
Comment 1 Vadim Fint 2010-11-04 18:29:32 UTC
Created attachment 253199 [details]
Fixup ebuild

Fixup ebuild (added patch processing only).
Comment 2 Vadim Fint 2010-11-04 18:30:04 UTC
Created attachment 253201 [details, diff]
Fixup patch

Ebuild which fixes exit problem with qt >= 4.6.3
Comment 3 Vadim Fint 2010-11-04 18:30:46 UTC
There is an exit bug in krusader, yes. Got it after updating to qt 4.6.3.
But for me it didnt eat all cpu, just not exists correctly.

Here is a fixup patch + ebuild:

# krusader-2.2.0_beta1-r1.ebuild
# files/krusader-2.2.0_beta1-fix-closing-bug-on-recent-qt.patch
Comment 4 Vadim Fint 2010-11-04 18:31:45 UTC
(patch above is not mine -- ported from krusader trunk).
Comment 5 Andreas K. Hüttel archtester gentoo-dev 2011-01-09 14:40:40 UTC
Fixed in krusader-2.3.0_beta1
Comment 6 Navid Zamani 2011-01-09 14:56:09 UTC
Yep, fixed here. But I had a little session manager hiccup where it wasn’t saved in the session at all. Works fine now though. Thanks. :)