Red Hat Bugzilla – Bug 457526
Konqueror, Kopete don't fully terminate in KDE 4.1
Last modified: 2008-09-10 05:37:30 EDT
Description of problem: In KDE 4.1 from updates-testing, Konqueror and Kopete (and upstream, reportedly several other KDE apps) can't be terminated using their own GUI facilities. Neither "File --> Quit" nor closing the window results in complete process termination, only the GUI is closed. If "On Login --> Restore from previous session" is enabled (as per default) in "System Settings --> Advanced --> Session Manager" then the phantom Konqueror and Kopete instances will be launched next time you log into KDE -- previously saved Konqueror sessions will launch without a GUI and Kopete will only have a visible GUI presence if its system tray icon was enabled previously. See the output of `ps aux | grep session` for accumulated Konqueror and Kopete instances from previous KDE 4.1 sessions. Version-Release number of selected component (if applicable): From updates-testing repo: kdelibs-4.1.0-3.fc9.i386 kdebase-4.1.0-1.fc9.1.i386 kdenetwork-4.1.0-2.fc9.i386 How reproducible: Always. Steps to Reproduce: 1. Launch Konqueror/Kopete 2. Try "File --> Quit" or closing window Actual results: The applications' GUIs close but their main processes continue to run. Expected results: Applications should terminate fully. Additional info: Marked fixed upstream in kdelibs: http://bugs.kde.org/show_bug.cgi?id=167826
doh, ouchie momma. Snagging this one.
%changelog * Fri Aug 01 2008 Rex Dieter <rdieter@fedoraproject.org> 4.1.0-4 - -devel: Requires: phonon-devel >= 4.2 (helps multilib upgrades) - konq processes never terminate (kde#167826, rh#457526)
bleh, upstream patch doesn't build against stock 4.1.0. may need tweaking.
Here's the 4.1 patch http://websvn.kde.org/branches/KDE/4.1/kdelibs/kdecore/kernel/kglobal.cpp?r1=829867&r2=840377&pathrev=840377&view=patch
that's the "upstream patch doesn't build against stock 4.1.0". :) I think I've fixed it (the original commit missed adding a declaration to kglobal.h), and am doing a test build now.
*** Bug 458149 has been marked as a duplicate of this bug. ***
kdebase-runtime-4.1.0-1.fc9, kdeaccessibility-4.1.0-1.fc9, kdegames-4.1.0-1.fc9, kdeplasma-addons-4.1.0-1.fc9, kdebase-workspace-4.1.0-8.fc9, kdebase-4.1.0-1.fc9.1, qgtkstyle-0.0-0.2.20080719svn693.fc9, qt-4.4.0-17.fc9, kdeutils-4.1.0-1.fc9.1, qscintilla-2.2-3.fc9, kdegraphics-4.1.0-3.fc9, kde-i18n-3.5.9-8.fc9, kdeartwork-4.1.0-1.fc9, kdeedu-4.1.0-1.fc9, compiz-0.7.6-3.fc9.1, PyQt4-4.4.2-2.fc9, automoc-1.0-0.8.rc1.fc9, phonon-4.2.0-2.fc9, akonadi-1.0.0-2.fc9, kdenetwork-4.1.0-2.fc9, quarticurve-kwin-theme-0.0-0.5.beta4.fc9, sip-4.7.6-1.fc9, kdepimlibs-4.1.0-2.fc9, kdelibs-4.1.0-4.fc9, kdebindings-4.1.0-5.fc9, kdesdk-4.1.0-1.fc9, kde-filesystem-4-17.fc9, soprano-2.1-1.fc9, kde-l10n-4.1.0-2.fc9, kdemultimedia-4.1.0-1.fc9, kdetoys-4.1.0-1.fc9, kdeadmin-4.1.0-2.fc9 has been pushed to the Fedora 9 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 kdebase-runtime kdeaccessibility kdegames kdeplasma-addons kdebase-workspace kdebase qgtkstyle qt kdeutils qscintilla kdegraphics kde-i18n kdeartwork kdeedu compiz PyQt4 automoc phonon akonadi kdenetwork quarticurve-kwin-theme sip kdepimlibs kdelibs kdebindings kdesdk kde-filesystem soprano kde-l10n kdemultimedia kdetoys kdeadmin'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-6743
kdelibs-4.1.0-5.fc9, kdeedu-4.1.0-1.fc9, quarticurve-kwin-theme-0.0-0.5.beta4.fc9, kdeartwork-4.1.0-1.fc9, kdetoys-4.1.0-1.fc9, kdesdk-4.1.0-1.fc9, PyQt4-4.4.2-2.fc9, kde-i18n-3.5.9-8.fc9, kdebase-4.1.0-1.fc9.1, sip-4.7.6-1.fc9, phonon-4.2.0-2.fc9, kdebase-workspace-4.1.0-8.fc9, automoc-1.0-0.8.rc1.fc9, kdegames-4.1.0-2.fc9, akonadi-1.0.0-2.fc9, soprano-2.1-1.fc9, konq-plugins-4.1.0-2.fc9, compiz-0.7.6-3.fc9.1, qt-4.4.1-2.fc9, qscintilla-2.2-3.fc9, kdepimlibs-4.1.0-2.fc9, kdegraphics-4.1.0-3.fc9, kdebindings-4.1.0-5.fc9, kdenetwork-4.1.0-2.fc9, kde-l10n-4.1.0-2.fc9, kdeplasma-addons-4.1.0-1.fc9, qgtkstyle-0.0-0.2.20080719svn693.fc9, kdeutils-4.1.0-1.fc9.1, kdemultimedia-4.1.0-1.fc9, kdebase-runtime-4.1.0-1.fc9, kdeadmin-4.1.0-2.fc9, kde-filesystem-4-17.fc9, kdeaccessibility-4.1.0-1.fc9 has been pushed to the Fedora 9 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 kdelibs kdeedu quarticurve-kwin-theme kdeartwork kdetoys kdesdk PyQt4 kde-i18n kdebase sip phonon kdebase-workspace automoc kdegames akonadi soprano konq-plugins compiz qt qscintilla kdepimlibs kdegraphics kdebindings kdenetwork kde-l10n kdeplasma-addons qgtkstyle kdeutils kdemultimedia kdebase-runtime kdeadmin kde-filesystem kdeaccessibility'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F9/FEDORA-2008-6743
I still see this with kdelibs-4.1.0-5.fc9.x86_64 from updates-testing.
Ah nevermind, it looks like I had some old sessions still around from before this was fixed. New instances seem to close correctly.
kdeedu-4.1.0-1.fc9, quarticurve-kwin-theme-0.0-0.5.beta4.fc9, kdeartwork-4.1.0-1.fc9, kdetoys-4.1.0-1.fc9, kdesdk-4.1.0-1.fc9, PyQt4-4.4.2-2.fc9, kde-i18n-3.5.9-8.fc9, kdebase-4.1.0-1.fc9.1, sip-4.7.6-1.fc9, kdebase-workspace-4.1.0-8.fc9, automoc-1.0-0.8.rc1.fc9, kdegames-4.1.0-2.fc9, akonadi-1.0.0-2.fc9, soprano-2.1-1.fc9, konq-plugins-4.1.0-2.fc9, compiz-0.7.6-3.fc9.1, qt-4.4.1-2.fc9, qscintilla-2.2-3.fc9, kdepimlibs-4.1.0-2.fc9, kdebindings-4.1.0-5.fc9, kdenetwork-4.1.0-2.fc9, kde-l10n-4.1.0-2.fc9, kdeplasma-addons-4.1.0-1.fc9, qgtkstyle-0.0-0.2.20080719svn693.fc9, kdeutils-4.1.0-1.fc9.1, kdemultimedia-4.1.0-1.fc9, kdeadmin-4.1.0-2.fc9, kde-filesystem-4-17.fc9, kdeaccessibility-4.1.0-1.fc9, kdebase-runtime-4.1.0-3.fc9, phonon-4.2.0-4.fc9, kdegraphics-4.1.0-5.fc9, kdelibs-4.1.0-7.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.