Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 234068 - kde-base/kdelibs-4.1.0: Closed KDE4 processes don't terminate
Summary: kde-base/kdelibs-4.1.0: Closed KDE4 processes don't terminate
Status: RESOLVED UPSTREAM
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] KDE (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo KDE team
URL: http://bugs.kde.org/show_bug.cgi?id=1...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-06 10:36 UTC by Ken Rossato
Modified: 2008-09-18 12:43 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ken Rossato 2008-08-06 10:36:50 UTC
Upstream bug: http://bugs.kde.org/show_bug.cgi?id=167826

The reference counting on class KApplication is broken.  Apps deriving from it (most notably Konqueror) won't terminate when they're closed.  Instead, the processes clutter up the process and dbus tables and poll for new events until they receive a QCoreApplication::quit() or are killall'ed (at which point they terminate gracefully).

This is a fairly serious bug, and IMO should be patched in the ebuild for 4.1 when it is released.  The patch (included in the upstream bug-report) is very small, about 10 lines.

Reproducible: Always

Steps to Reproduce:
1. Get KDE 4.1 (via kdesvn-portage, raw source, or another distro)
2. Open a terminal
3. Run "konqueror"
4. Close konqueror via the "x" button in the window decoration.
Actual Results:  
Konqueror continues to run, you don't get back to your prompt.  You can also see the process in qdbusviewer, where it responds to commands.

Expected Results:  
The process should have terminated and returned you to the prompt.  It should no longer be visible via "ps" or "qdbusviewr".
Comment 1 Jorge Manuel B. S. Vicetto (RETIRED) Gentoo Infrastructure gentoo-dev 2008-08-16 11:58:09 UTC
This patch has been added on commit aa312f0770c37c2ea6947ec42a309878814efbd7 to the kde overlay.
You can check the commit at http://git.overlays.gentoo.org/gitweb/?p=proj/kde.git;a=commit;h=aa312f0770c37c2ea6947ec42a309878814efbd7
Comment 2 Patrizio Bassi 2008-09-03 19:15:56 UTC
can you check if fix was included in 4.1.1?
Comment 3 Ken Rossato 2008-09-04 06:07:23 UTC
(In reply to comment #2)

It appears that it was.(In reply to comment #2)
> can you check if fix was included in 4.1.1?
> 

Looking at the unpacked code for kdelibs-4.1.1 in kdesvn-portage, it appears that the fix was included.
Comment 4 Patrizio Bassi 2008-09-04 19:18:22 UTC
so we can mark this closed as upstream...right?
Comment 5 Ken Rossato 2008-09-12 13:58:15 UTC
(In reply to comment #4)
> so we can mark this closed as upstream...right?
> 

Fine with me.  I'm not sure what etiquette is on closing bugs here.  Since nobody from the "official" KDE team has yet, I will.
Comment 6 Ken Rossato 2008-09-18 12:43:05 UTC
N.B.:

There is a bug with very similar symptoms on 4.1.1, but it only affects Konqueror, and only after a page with HTML is loaded.  See http://bugs.kde.org/show_bug.cgi?id=170461