Summary: | Kopete crashes on exit | ||
---|---|---|---|
Product: | [Unmaintained] kopete | Reporter: | Michal Klich <klich.michal> |
Component: | Jabber Plugin | Assignee: | Kopete Developers <kopete-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | andresbajotierra, kde, skyphyr |
Priority: | NOR | ||
Version: | 0.50.1 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
kopete crash log
gdb kopete |
Description
Michal Klich
2008-05-26 14:49:18 UTC
This stacktrace doesn't tell us much exact that the crash is in the Jabber protocol. Please read http://fedoraproject.org/wiki/StackTraces and http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports to help us get better information to fix the bug faster. Thanks! Created attachment 26133 [details]
kopete crash log
Created attachment 26134 [details]
gdb kopete
Please find two attached files. I hope they are useful. *** Bug 165858 has been marked as a duplicate of this bug. *** can you still reproduce with kde 4.1.2 or the kde 4 from your distribution ? Yes i can reproduce that error. It gets even worse. Now i am not able to close kopete in tray, i can not log back in when i logged out and it still crashes on exit. Though i can not exit kopete, because it still shows in tray, but when i do not login to kopete after fresh reboot and close kopete it crashes. If you need any info like crash-log please let me know. Qt: 4.4.3 KDE: 4.1.2 (KDE 4.1.2) Kopete: 0.60.2 can be fixed by commit : http://websvn.kde.org/?view=rev&revision=881699 I can confirm this Bug too This may be related/duplicate of bug 167831 Hi All, Thanks for the report. Could somebody with this bug confirm it still exists and provide a backtrace with debug symbols? Even if done with the same version as originally this will still assist in confirming if it's a dupe as suspected or a different bug. Cheers, Alan. No news from the bug reporter, marking as WORKSFORME. Please reopen this bug report if you experience the same bug again. |