78352 2004-03-24 07:07:37 +0000 Problem when kontact session is restored after logout,login 2007-12-11 17:44:27 +0000 1 1 10 Unmaintained kmail general unspecified RedHat Enterprise Linux Linux RESOLVED FIXED NOR normal --- 1 zabilcm molkentin Stefan.Borggraefe 100 oldest_to_newest 218584 0 zabilcm 2004-03-24 07:07:37 +0000 Version: (using KDE KDE 3.2.1) Installed from: RedHat RPMs OS: Linux The "lock" file in '~/.kde/share/apps/kmail' folder does not get deleted when the user ends session/logs out while running 'kontact'. Because of this reason when the user log's in, an attempt is made to restore the kontact session and while this happens a message stating that there is already one instance of kmail running as indicated by the "lock" file. The only way to get contact running after this is manually deleting the "lock" file in the '~/.kde/share/apps/kmail' folder. 218830 1 tjg 2004-03-25 04:25:22 +0000 I have a similar problem, though it doens not happen every time. It happens frequently enough to be annoying. I believe it is related to Kontact or KMail not shutting down correctly when I shut my notebook down without closing KMail first. I'm not sure, but I don't believe I've ever had the problem if I've closed Kontact before shutting my system down. 289031 2 info 2004-11-25 18:37:59 +0000 I had this problem in previous versions but never in 3.3. or 3.3.1. 317623 3 mail 2005-02-23 21:17:10 +0000 I can confirm #1, and this is very annoying. BTW: Is the session saved when calling "halt"? 339246 4 arturj 2005-05-03 11:05:48 +0000 I have a related bug in 3.3. When I login kontact is always restored correctly. But when I try to start kontact (again), to bring it to front I get this error message that kontact is already running and I have the option to kill kontact or to go on. This only habbens when the first instance of kontact is started by restoring the previous session. It does not appear when I start kontact manually and then try to start kontact again. Very annoying since I use my multi-media-keys to bring kontact to front... 349012 5 molkentin 2005-06-09 15:27:44 +0000 Can someone from the kmail hackers please have a look at the session management when running in kontact? 368710 6 meybohm 2005-08-25 15:23:52 +0000 I got a similar prblem in KDE3.4.0 (Kontact 1.1). If Kontakt is killed with kill oder killall the pid value in the lock file will not be set to -1. If I log out from KDE (Kontact still running) the pid value is set to -1 (sometimes, not every time.). 369500 7 12415 meybohm 2005-08-29 11:37:29 +0000 Created attachment 12415 Patch for kmstartup.cpp. We have created a Patch for KMails kmstartup.cpp. It fixes the problem for us. (Sets -1 as Pid value in the lock-file. Even if Kontact gets SIGTERM or SIGHUP etc.) 407596 8 Stefan.Borggraefe 2006-01-20 07:42:55 +0000 I still run into this bug with Kontact 1.2/KDE 3.5. Why wasn't the attached patch checked in? Maybe it could be refactored to avoid the code duplication, but isn't it the right approach? 562303 9 finex 2007-12-11 17:44:27 +0000 Kontact on KDE 3.5.8 and KDE 4 is working fine. After killing process there is no more file locking problems. 12415 2005-08-29 11:37:29 +0000 2005-08-29 11:37:29 +0000 Patch for kmstartup.cpp. kmail-startup-pid.patch text/plain 835 meybohm LS0tIGttc3RhcnR1cC5jcHAub3JpZwlGcmkgQXVnIDI2IDA3OjI4OjU5IDIwMDUKKysrIGttc3Rh cnR1cC5jcHAJVGh1IEF1ZyAyNSAxNjo0NDozMyAyMDA1CkBAIC0zNiw2ICszNiwxMCBAQAogewog ICBrbXNldFNpZ25hbEhhbmRsZXIoU0lHX0RGTCk7CiAgIGZwcmludGYoc3RkZXJyLCAiKioqIEtN YWlsIGdvdCBzaWduYWwgJWQgKEV4aXRpbmcpXG4iLCBzaWdJZCk7CisgIFFTdHJpbmcgbG9ja0xv Y2F0aW9uID0gbG9jYXRlTG9jYWwoImRhdGEiLCAia21haWwvbG9jayIpOworICBLU2ltcGxlQ29u ZmlnIGNvbmZpZyhsb2NrTG9jYXRpb24pOworICBjb25maWcud3JpdGVFbnRyeSgicGlkIiwgLTEp OworICBjb25maWcuc3luYygpOwogICAvLyB0cnkgdG8gY2xlYW51cCBhbGwgd2luZG93cwogICBp ZiAoa21rZXJuZWwpIGtta2VybmVsLT5kdW1wRGVhZExldHRlcnMoKTsKICAgOjpleGl0KC0xKTsg Ly8KQEAgLTQ2LDYgKzUwLDEwIEBACiB7CiAgIGttc2V0U2lnbmFsSGFuZGxlcihTSUdfREZMKTsK ICAgZnByaW50ZihzdGRlcnIsICIqKiogS01haWwgZ290IHNpZ25hbCAlZCAoQ3Jhc2hpbmcpXG4i LCBzaWdJZCk7CisgIFFTdHJpbmcgbG9ja0xvY2F0aW9uID0gbG9jYXRlTG9jYWwoImRhdGEiLCAi a21haWwvbG9jayIpOworICBLU2ltcGxlQ29uZmlnIGNvbmZpZyhsb2NrTG9jYXRpb24pOworICBj b25maWcud3JpdGVFbnRyeSgicGlkIiwgLTEpOworICBjb25maWcuc3luYygpOwogICAvLyB0cnkg dG8gY2xlYW51cCBhbGwgd2luZG93cwogICBpZiAoa21rZXJuZWwpIGtta2VybmVsLT5kdW1wRGVh ZExldHRlcnMoKTsKICAgLy8gUmV0dXJuIHRvIERyS29ucWkuCg==