I have a problem with kontact at logon. When you logoff from a session without closing kontact first, and then log back on, I get the standard prompt from kwallet and another prompt stating the following. 'Kontact already seems to be running on another display on this machine. Running Kontact more than once can cause the loss of mail. You should not start Kontact unless you are sure that it is not already running.' Then there's two prompts. Selecting 'Start Kontact' and then entering my passphrase in kwallet will start two instances of kontact. Selecting 'Exit' will not start kontact at all. Furthermore, with the two instances of kontact running, closing one will close the other as well, probably because it crashes. In the end, I have to manually start kontact again anyway. Here's a copy of the crash dump of the crash I mentioned. Application: Kontact (kontact), signal SIGSEGV [Current thread is 0 (LWP 19093)] Thread 3 (Thread 0xb0d32b90 (LWP 19330)): #0 0xb7ef8424 in __kernel_vsyscall () #1 0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6 #3 0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb75f752e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb6b360de in clone () from /lib/i686/cmov/libc.so.6 Thread 2 (Thread 0xb020eb90 (LWP 19337)): #0 0xb7ef8424 in __kernel_vsyscall () #1 0xb539d2e2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb6b44f84 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6 #3 0xb75f851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb75ed7c6 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb75f752e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb53994e5 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb6b360de in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb4a86700 (LWP 19093)): #0 0xb7ef8424 in __kernel_vsyscall () #1 0xb6af2376 in nanosleep () from /lib/i686/cmov/libc.so.6 #2 0xb6af218e in sleep () from /lib/i686/cmov/libc.so.6 #3 0xb7c35738 in ?? () from /usr/lib/libkdeui.so.5 #4 0x00000000 in ?? ()
Do you have kontact to start twice? I had set kontact to autostart in my .kde/Autostart dir and also as part of a saved session, and I saw this exact behaviour. /Sune
I don't have kontact set to autostart. Not sure what you mean by saved session. This behavior happens to me when I leave kontact open when logging off and then logging back on.
Hi, I have the same problem as described by Andres, and I don't have kontact in .kde/Autostart/ Regards Gerard
If you have an IMAP based address book, this could be causing a start at login if the "Contacts" plugin of KRunner (ALT+F2 thingy) is enabled. The reason is that the plugin accesses the addressbook which in turn needs to access the IMAP addressbook which in turn needs KMail (stand-alone or in Kontact) to provide the IMAP access. Cheers, Kevin
Hi, I don't have an IMAP based Adressebook, but an FTP based calendar. So normally no call to kmail. But thanks for your hint I will have a closer look at KRunner. Regards Gerard----- Message d'origine ---- De : Kevin Krammer <kevin.krammer@gmx.at> À : Gerard Mensoif <mensoif_gerard@yahoo.fr>; 523363@bugs.debian.org Envoyé le : Lundi, 13 Juillet 2009, 12h40mn 26s Objet : Re: Bug#523363: kontact: problem at logon when starting kontact If you have an IMAP based address book, this could be causing a start at login if the "Contacts" plugin of KRunner (ALT+F2 thingy) is enabled. The reason is that the plugin accesses the addressbook which in turn needs to access the IMAP addressbook which in turn needs KMail (stand-alone or in Kontact) to provide the IMAP access. Cheers, Kevin
tags 523363 + moreinfo thanks Hi, you reported http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523363 some time ago. Since then, KDE Software Compilation had several releases. Can you please verify whether the bug you reported is still present in a more current version (and - if yes - specify which version)? Eckhart
tags 523363 + moreinfo thanks Hi, you reported http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=523363 some time ago. Since then, KDE Software Compilation had several releases. Can you please verify whether the bug you reported is still present in a more current version (and - if yes - specify which version)? Eckhart
This bug is still present in Sid (kontact 4:4.3.4-2)
I have test KDE 4.4.2 (experimental) - looks like bug is fixed.
This bug appears only when an akonadi contact resource is present. If not, Kontact starts normally at logon but the contact component does not work (ubuntu bug 564263)
You have received a new fax. Please, download fax document attached to this email. Sender: Kyle Werner Document name: task-000773910.doc Scanned: Tue, 27 Oct 2015 21:54:20 +0300 Quality: 100 DPI Scan duration: 22 seconds Number of pages: 3 File size: 115 Kb Thanks for using Interfax service!