Summary: | kopete crashes as it starts | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | Mauro <capo_drugo> |
Component: | general | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | kopete log using valgrind |
Description
Mauro
2009-02-03 10:22:29 UTC
This is probably a duplicate of bug 179425 Can you reproduce this on every start? Is anyone of yours contact using emesene ? I can't reproduce everytime I start Kopete. It happened three times today, never before. No updates since two days. I really ignore if someone is using emesene. Maybe someone using emesene sent you an offline message and when Kopete started and fetched the message it crashed on showing it (as in bug bug 179425) You could try creating some MSN test account , and connecting to it using emesene. You can send your main MSN account an offline message and then try if Kopete crashes when starting/loading the account and the offline message. (or ask for someone to send you an offline message) Thanks I confirm this bug. I'm using Debian Lenny with experimental repositories (for kde 4.2) with kopete 0.70.0: These are the details of the debugger: Application: Kopete (kopete), signal SIGABRT [Current thread is 0 (LWP 2522)] Thread 2 (Thread 0xb3113b90 (LWP 2523)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb5f41025 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0 #2 0xb640e7fd in pthread_cond_wait () from /lib/i686/cmov/libc.so.6 #3 0xb6ebf542 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #4 0xb5fbe312 in ?? () from /usr/lib/libQtNetwork.so.4 #5 0xb6ebe52e in ?? () from /usr/lib/libQtCore.so.4 #6 0xb5f3d4c0 in start_thread () from /lib/i686/cmov/libpthread.so.0 #7 0xb64006de in clone () from /lib/i686/cmov/libc.so.6 Thread 1 (Thread 0xb58766c0 (LWP 2522)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb63bbef6 in nanosleep () from /lib/i686/cmov/libc.so.6 #2 0xb63bbd0f in sleep () from /lib/i686/cmov/libc.so.6 #3 0xb7569128 in ?? () from /usr/lib/libkdeui.so.5 #4 0x00000000 in ?? () Thank you ;) @marco: I can't confirm your crash is the same as the original reported. May you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and check if the complete backtrace is *similar* to the reported here ? You need to install kdenetwork-dbg, and libqt4-dbg Thanks :) @Darío Andrés: I've tried to get the backtrace from gdb, but using the command `thread apply all backtrace` it says : No registers. However, I've run the program valgrind, and it created the log file, that I've attached. Finally, this is the error shown in the konsole (with valgrind): terminate called after throwing an instance of 'std::runtime_error' what(): Incorrectly specified message format! KCrash: Application 'kopete' crashing... sock_file=/home/marco/.kde4/socket-net-home/kdeinit4__0 I'm trying to re-debug kopete and I hope that the backtrace command will work. Thank you ;) Created attachment 31038 [details]
kopete log using valgrind
@marco: your crash seems to be different. Can you file a new bug report ? Thanks Fixed in libmsn 4 beta 5, please update libmsn *** This bug has been marked as a duplicate of bug 192304 *** |