| Summary: | session management problems (kontact often thinks it is already running) | ||
|---|---|---|---|
| Product: | [Applications] kontact | Reporter: | Anders Lund <anderslund> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | alinm.elena, andreas, andresbajotierra, arne.schmitz, cfreier, getaceres, goretux, henk.vanvelden, igor.poboiko, jrenner.rouliez, kde, maednoldor, praedor, santi.flores, smartins, sven.burmeister |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Anders Lund
2007-03-18 21:16:14 UTC
*** Bug 143595 has been marked as a duplicate of this bug. *** This might be fixed by >SVN commit 645744 by winterz: >forward port SVN commit 645708 by dfaure: >Fix kmail saying "I seem to be running already" upon session restoration due to a stale lock file. >Now (on linux) it checks if the pid in the lock file really belongs to a running kmail or kontact. But I am not sure. On Thursday 29 March 2007, Thomas McGuire wrote: > >SVN commit 645744 by winterz: > > > >forward port SVN commit 645708 by dfaure: > > > >Fix kmail saying "I seem to be running already" upon session restoration > > due to a stale lock file. Now (on linux) it checks if the pid in the lock > > file really belongs to a running kmail or kontact. > > But I am not sure. I'll look forward to try the next version, this *sounds* right. *Sounds* right indeed. When you can explain why it didn't happen in earlier versions you are done. When not, I think it is anyway *good programming practice* to check the PID. *** Bug 147148 has been marked as a duplicate of this bug. *** How is it going fixing this? It's my #1 reason to get pissed with KDE :-( Any news on this? Annoys me totally. Using KDE 3.5.7 on Opensuse 10.2. I installed a new system with openSUSE 10.2 and KDE 3.5.7. I leave Kontakt runnung when I log-out during several weeks now and it restarts on every log-in without any complaints. So for me the problem is solved :) On Monday 01 October 2007, hcvv wrote: I still have problems, running kubuntu feisty with all available updates. It appears that the problem with the lockfile doesn't happen if kmail is minimized or not at top when i shutdown, in those cases the shutdown routines (deleting mail, emptying trash folder) doesn't happen. I just logged out/in with kmail top in kontact, not iconised. No problems. Problem is still there, OpenSuSE with KDE 3.5.8. Also on another machine with Debian Lenny, KDE 3.5.7. Got it too, on Kubuntu Gutsy with KDE 3.5.8. One difference: I only get one popup. Same Problem on an ArchLinux installation with a daily-compiled version of the KDE4 svn. I don't have any Idea how to reproduce the error but it happens quite frequently. I see it too with KDE 4.2 RC1. It only happens if I add an IMAP account though. As long as I only have pop3 accounts, it works fine. When trying to reproduce this I get the crash at bug 156292. Without imap it's fine. I'm getting this bug on Kubuntu Intrepid with KDE 4.2.0. I have an IMAP account. Everytime KDE starts, it warns be about kontact being running. If I click on continue, then two instances of Kontact open, if I close one of them, both of them crash. If I click on exit, nothing happens but I have to start kontact manually and then everything is ok. It didn't happen with KDE 4.1 I can confirm, KDE 4.2 from Debian Experimental repo.. Same problem as in comment #16. PS sorry for my bad english *** Bug 185544 has been marked as a duplicate of this bug. *** I've got the same problem here with a fresh install of KDE 4.3 RC 3 (on Kubuntu Jaunty). I've already post on bug 185544 which is a duplicate of this bug. I quote a description from bug 185544, as I think it precisely describes the problem. > The bug occurs everytime after logging out of KDE without closing Kontact. > After the next login, a message window appears: "kontact is already running in > another window. start anyway?" After clicking on "no", kontact is not opened at > all. After clicking on "yes" two kontact windows appear. Closing either of them > leads to the described crash. *** Bug 192902 has been marked as a duplicate of this bug. *** *** Bug 187023 has been marked as a duplicate of this bug. *** I have the same problem here. Now I'm running KDE 4.3.85 (KDE 4.4 Beta2) and I still have the problem (since my first notification in bug 198791). Bug 160598 seems to be related in a way. I've tested this: Anytime I start a session in KDE, kontact crashes with the advise that another instance is running. But if another application (e.g. kopete) starts before kontact and calls kdewallet before kontact does, the advice about kontact is already running doesn't appears. That's right. Now I have Kopete running and set to online by default, so it starts first and opens kwallet. Then, Kontact does not crash. The same happens with NetworkManager using kwallet to store its passwords. But if nothing opens kwallet and kontact tries to open it, it fails with the aforementioned error. *** This bug has been marked as a duplicate of bug 185544 *** (In reply to comment #24) > That's right. Now I have Kopete running and set to online by default, so it > starts first and opens kwallet. Then, Kontact does not crash. The same happens > with NetworkManager using kwallet to store its passwords. But if nothing opens > kwallet and kontact tries to open it, it fails with the aforementioned error. Me too. I just realized that. I see a different behaviour. If I have both Amarok and Kontact as part of a session that is restored and both ask for access to kwallet, kontact claims it is already running. If only Kontact is restored it works as expected. *** Bug 192596 has been marked as a duplicate of this bug. *** |