[opensuse] Kontact crash/timesout
I use opensuse 11 x86_64 with kontact Version 1.3 from the opensuse 11 repo. Kontact use to work without this problem but since my workstation ip changed, i get a constant error: connection to the server <servername> was unexpectedly closed or timed out. It will be established automatically if possible" And in fact, some times it does get re-established but other times, kontact crashes. Some things i have done to try to fix this: -tried just kmail->same problem -delete existing account and recreated the email account->same problem -other email clients work fine -updated kontact from the opensuse repo->same problem -uninstall kontact/kmail and its dependencies. then delete all kmail/kontact folders. Reinstall kmail/kontact->same problem -reformat hdd and reinstall opensuse 11 with kontact->same problem So, i would like to now know where to look on the workstation for kontact error logs? /var/log/messages (i don't see anything in there)? I have also looked into the mail server logs for errors and found some java errors that happen around the same time of the error on the workstation. I restarted the mail server services and do not get that java error but still get the error on the workstation/kontact. I use zimbra 5.0.4 OSS as a mail server. I have asked over at their forums and they don't have an answer either. Is there anyone here who can help me find out how to fix this error? I really want to use kontact. Here is the backtrace of the crash when i get that message and click "OK": Application: Kontact (kontact), signal SIGSEGV [?1034h(no debugging symbols found) (no debugging symbols found) {same as above} [Thread debugging using libthread_db enabled] [New Thread 0x7f80f7d6f700 (LWP 12050)] (no debugging symbols found) {same as above} [KCrash handler] #5 0x00007f80f2610fd1 in QMutex::lock () from /usr/lib64/libQtCore.so.4 #6 0x00007f80f26e6b5e in QCoreApplication::postEvent () from /usr/lib64/libQtCore.so.4 #7 0x00007f80dff6e782 in ?? () from /usr/lib64/libkmailprivate.so.4 #8 0x00007f80dff70a2f in ?? () from /usr/lib64/libkmailprivate.so.4 #9 0x00007f80f26f84e0 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4 #10 0x00007f80f35f3a42 in KJob::result () from /usr/lib64/libkdecore.so.5 #11 0x00007f80f35f3db7 in KJob::emitResult () from /usr/lib64/libkdecore.so.5 #12 0x00007f80f4d32ae0 in KIO::SimpleJob::slotFinished () from /usr/lib64/libkio.so.5 #13 0x00007f80f4d30567 in KIO::SimpleJob::slotError () from /usr/lib64/libkio.so.5 #14 0x00007f80f4d30762 in KIO::SimpleJob::qt_metacall () from /usr/lib64/libkio.so.5 #15 0x00007f80f26f84e0 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4 #16 0x00007f80f4dd38e6 in KIO::SlaveInterface::error () from /usr/lib64/libkio.so.5 #17 0x00007f80f4dd6064 in KIO::SlaveInterface::dispatch () from /usr/lib64/libkio.so.5 #18 0x00007f80f4dd3f22 in KIO::SlaveInterface::dispatch () from /usr/lib64/libkio.so.5 #19 0x00007f80f4dc775e in KIO::Slave::gotInput () from /usr/lib64/libkio.so.5 #20 0x00007f80f4dc7a68 in KIO::Slave::qt_metacall () from /usr/lib64/libkio.so.5 #21 0x00007f80f26f84e0 in QMetaObject::activate () from /usr/lib64/libQtCore.so.4 #22 0x00007f80f4d078a1 in ?? () from /usr/lib64/libkio.so.5 #23 0x00007f80f4d07f4a in KIO::Connection::qt_metacall () from /usr/lib64/libkio.so.5 #24 0x00007f80f26f49ce in QObject::event () from /usr/lib64/libQtCore.so.4 #25 0x00007f80eeeab92d in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4 #26 0x00007f80eeeb1cfa in QApplication::notify () from /usr/lib64/libQtGui.so.4 #27 0x00007f80f444b66b in KApplication::notify () from /usr/lib64/libkdeui.so.5 #28 0x00007f80f26e6e9c in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4 #29 0x00007f80f26e77cb in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib64/libQtCore.so.4 #30 0x00007f80eef2c277 in ?? () from /usr/lib64/libQtGui.so.4 #31 0x00007f80f26e57f2 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4 #32 0x00007f80f26e5985 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4 #33 0x00007f80f26e7a25 in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4 #34 0x0000000000404a04 in _start () #0 0x00007f80ece1c230 in nanosleep () from /lib64/libc.so.6 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, Jul 13, 2008 at 7:24 PM, Chris Arnold
I use opensuse 11 x86_64 with kontact Version 1.3 from the opensuse 11 repo. Kontact use to work without this problem but since my workstation ip changed, i get a constant error:
connection to the server <servername> was unexpectedly closed or timed out. It will be established automatically if possible"
And in fact, some times it does get re-established but other times, kontact crashes.
In each case where I get the "will be established automatically" message, killing Kontact and restarting it solves the problem. Every time. I've had Kontack crash repeatedly on some specific messages in an Imap maibox that I had to delete via some other client. But never from a simple IP change. I travel with my laptop all the time. New IP almost every day. -- ----------JSA--------- Sig line deleted for the humor impaired. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Monday 14 July 2008 04:24:57 Chris Arnold wrote:
I use opensuse 11 x86_64 with kontact Version 1.3 from the opensuse 11 repo. Kontact use to work without this problem but since my workstation ip changed, i get a constant error:
Hi Chris I'm the Kontact maintainer at Novell. Does this happen whenever your workstation's IP changes, or did the IP address only change once and the problem continues to manifest whenever you run Kontact although the IP address is now constant?
connection to the server <servername> was unexpectedly closed or timed out. It will be established automatically if possible"
And in fact, some times it does get re-established but other times, kontact crashes.
Some things i have done to try to fix this:
-tried just kmail->same problem
-delete existing account and recreated the email account->same problem
-other email clients work fine
-updated kontact from the opensuse repo->same problem
-uninstall kontact/kmail and its dependencies. then delete all kmail/kontact folders. Reinstall kmail/kontact->same problem
(no debugging symbols found)
-reformat hdd and reinstall opensuse 11 with kontact->same problem
So it's an endemic problem to the kmail component of Kontact. Let's try to get to the bottom of this.
So, i would like to now know where to look on the workstation for kontact error logs? /var/log/messages (i don't see anything in there)?
I have also looked into the mail server logs for errors and found some java errors that happen around the same time of the error on the workstation. I restarted the mail server services and do not get that java error but still get the error on the workstation/kontact. I use zimbra 5.0.4 OSS as a mail server. I have asked over at their forums and they don't have an answer either.
Is there anyone here who can help me find out how to fix this error? I really want to use kontact. Here is the backtrace of the crash when i get that message and click "OK":
Application: Kontact (kontact), signal SIGSEGV
[?1034h(no debugging symbols found)
<snip> It shouldn't crash when ok'ing that message. Can you install kdelibs3-debuginfo and kdepim3-debuginfo and file a bug report with a new backtrace (showing line numbers) please? regards Will -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi Chris HI Will!
I'm the Kontact maintainer at Novell. Does this happen whenever your workstation's IP changes, or did the IP address only change once and the problem continues to manifest whenever you run Kontact although the IP address is now constant? That is correct, the IP address only change once and the problem continues to manifest whenever you run Kontact although the IP address is now constant.
So it's an endemic problem to the kmail component of Kontact. Let's try to get to the bottom of this. I would love to find the bottom and fix this.
<snip> It shouldn't crash when ok'ing that message. Can you install kdelibs3-debuginfo and kdepim3-debuginfo and file a bug report with a new backtrace (showing line numbers) please? I should be able to do this later today. Are there any specific steps i need to take to get what is needed from the debug?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Chris Arnold
-
John Andersen
-
Will Stephenson