Bug 2681

Summary: Kontact doesn't shutdown properly at logout/shutdown
Product: Mageia Reporter: Praedor Atrebates <praedor>
Component: RPM PackagesAssignee: John Balcaen <balcaen.john>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Low CC: alien, balcaen.john, marja11
Version: 1   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=185544
Whiteboard:
Source RPM: kdepim4 CVE:
Status comment:

Description Praedor Atrebates 2011-09-09 15:12:56 CEST 
Description of problem: Kontact misbehaves after intial startup in all subsequent sessions.  I want kontact to be started in an initial session and from then on, whenever I startup and login from that point onward, kontact starts at login and shuts down at logout or shutdown.  It USED to do this but now what happens is with every single subsequent login, kontact produces a warning message: "Kontact appears to already be running on another display..."  It warns that starting anyway can lead to loss of email and do I want to continue.  If I say "yes" kontact opens 2 windows.  If I shutdown one of them they both go down and I have to manually restart it.  If I say "no" then I still have to manually start kontact and the whole process will start again with the next login.  I should NOT have to manually shut down kontact before logging off or shutting down and manually start it again with the next login.  It USED to work properly (KDE 3.x) but since KDE 4.x it has done this.  I have tried creating a script to delete a left-behind lock file from the last session just prior to kde startup but it doesn't work.  If I MANUALLY delete the lock file and then start kontact I don't get the message and only 1 window starts.  I have also tried deleting the left-behind lock file with a script that runs at kde shutdown.  Doesn't work.  


Version-Release number of selected component (if applicable): 4.4.11.1-2 mga


How reproducible: Every login subsequent to initial login and starting kontact.


Steps to Reproduce:
1. Login to KDE and start kontact and leave default "restore previous session"
2. Logout or shutdown
3. Startup and/or login again.  Kontact produces message.
Comment 1 Praedor Atrebates 2011-09-09 15:16:01 CEST 
Addendum to "Steps to Reproduce":

In step 1. the "restore previous session" setting is in kcontrol under Startup and Shutdown, Session Management.
Comment 2 Manuel Hiebel 2011-09-10 15:08:01 CEST 
That is an upstream bug no ?

Source RPM: kontact-4.4.11.1-2.1.mga1 => kdepim4

Manuel Hiebel 2011-09-10 15:08:20 CEST

Assignee: bugsquad => balcaen.john

Comment 3 John Balcaen 2011-09-10 20:51:34 CEST 
Someone report it already on irc during the beta phase however i was not able to reproduce.
The problem here is that upstream (see https://bugs.kde.org/show_bug.cgi?id=185544 ) did not fix it kdepim 4.x but on kdepim 4.6.x (which is not shipped by mageia).
So for the moment maybe a workaround would be to not restore kontact on session restore ?

So far it's more a wontfix until i'm able to find the correct commit in kdepim git & eventually to backport it :/

Priority: Normal => Low
CC: (none) => balcaen.john
See Also: (none) => https://bugs.kde.org/show_bug.cgi?id=185544

Comment 4 John Balcaen 2011-09-10 20:57:22 CEST 
Hum in fact it's already included in kdepim 4.4.10 since it's this commit https://projects.kde.org/projects/kde/kdepim/repository/revisions/cb87362163afbed2dca419c839c342a7b5ec675f  :/
Comment 5 AL13N 2011-09-19 17:45:05 CEST 
the last time i rebooted for updates i experience a message about double kontact. i'm using kdepim4-4.4.11.1-2.1.mga1 .

(is it odd that alot of versions are different here?)
[root@localhost ~]# rpm -q -a | grep kdepim
lib64kdepim-copy4-4.4.11.1-0.1.mga1
lib64kdepim4-4.4.11.1-2.1.mga1
kdepim4-kresources-4.4.11.1-2.1.mga1
kdepim4-core-4.4.11.1-2.1.mga1
kdepimlibs4-core-4.6.5-0.mga1
kdepim4-4.4.11.1-2.1.mga1

CC: (none) => alien

Comment 6 Marja Van Waes 2011-12-31 14:52:09 CET 
pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW

@ John

Do you have any news and can you answer AL13N's question in comment 5?

CC: (none) => marja11

Comment 7 John Balcaen 2011-12-31 15:22:34 CET 
(In reply to comment #5)
> the last time i rebooted for updates i experience a message about double
> kontact. i'm using kdepim4-4.4.11.1-2.1.mga1 .
> 
> (is it odd that alot of versions are different here?)
> [root@localhost ~]# rpm -q -a | grep kdepim
> lib64kdepim-copy4-4.4.11.1-0.1.mga1
> lib64kdepim4-4.4.11.1-2.1.mga1
> kdepim4-kresources-4.4.11.1-2.1.mga1
> kdepim4-core-4.4.11.1-2.1.mga1
> kdepimlibs4-core-4.6.5-0.mga1
> kdepim4-4.4.11.1-2.1.mga1
kdepim4 is != then kdepim.
& we did the choice to provide kdepim4 from 4.4.x branch instead of the 4.6.x branch.
So in summary we have package providing here from :
kdepimlibs 4.6.x
kdepim4-runtime 4.4.x
kdepim4 4.4.x

(In reply to comment #6)
> @ John
> 
> Do you have any news and can you answer AL13N's question in comment 5?
I did not answer to al13n's comment initially because it was obvious for me, sorry.
& as i said initially it's more a « wontfix » the workaround here is to not restore kontact.
Comment 8 Marja Van Waes 2011-12-31 17:09:23 CET 
(In reply to comment #7)

> & as i said initially it's more a « wontfix » the workaround here is to not
> restore kontact.

@ John

Closing as wontfix for now. It can of course be reopened later, when you think it isn't a wontfix anymore :)

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX