Bug 330524

Summary:	kontact process does not end after shutdown contact (kmail, knode, contacts and calendar)
Product:	[Applications] kmail2	Reporter:	Russ Fineman <upscope>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	major	CC:	johannes
Priority:	NOR
Version:	4.12.1
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Russ Fineman 2014-01-29 00:50:37 UTC

Kontact process does not end. If you shutdown system and later reboot Kontact will not start agin until you mannual go in (I use KsysGuard and end process. Then you can restart contact and it application (kmail, contacts, calendar and knode in my case. Always occurs if you logout, restart or power off the system.
Note : Found bug that was closed in 2011 that discribed this failure exactly. did another search to find it and get the number, but I cannot find it.

This was working with KDE 4.12.0. started after update to 4.12.1.

Reproducible: Always

Steps to Reproduce:
1. shutdown knotact after use of kmail, calendar,knode or contacts. Window closes.
2. check with KsysGuard, Kontact process still running.
3. I do not end process and do normail shutdown, restart or logout. Kontact will not start when you come up again. Desktop, etc comes up Ok. If you then go into KsysGyuard and kill the Kontact process, and then start Kontact it wil start.
4. If you kill kontact before shutting down, etc then Kontact starts when you come up again.

No errors in log I can find.
Actual Results:  
Have to manually kill thekontact process before leaving system or after system comes up and the start Kontact.

Expected Results:  
expect Kontact to start after powerdown, restart or logout.

openSUSE 13.1(Linux 3.11.6-4-desktop x86_64|
Intel(R) Quad Core(TM) i5-4440 CPU @ 3.10GHz|8GB DDR3|
GeForce 8400GS (NVIDIA-Linux-x86_64-331.38)|KDE 4.12.1

Comment 1 Johannes Studt 2014-02-20 22:20:34 UTC

Confirmed with:

Name        : kontact
Version     : 4.12.2
Release     : 439.1

Distribution: KDE:Release:412 / openSUSE_13.1

Comment 2 Denis Kurz 2016-09-24 18:07:23 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 3 Denis Kurz 2017-01-07 22:33:44 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.