Bug 161790

Summary:	Kopete crashes on startup after showing offline messages notification
Product:	[Applications] kopete	Reporter:	Alexey Chernov <4ernov>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	anton.galitch, ben.lewis, blacknascool, nedimmuminovic
Priority:	NOR
Version:	0.50.1
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Crash report

Description Alexey Chernov 2008-05-08 13:03:56 UTC

Version:           0.50.1 (using KDE 4.0.3)
Installed from:    Compiled From Sources
Compiler:          GCC 4.1.2 Target: x86_64-unknown-linux-gnu Configured with: ../gcc-4.1.2/configure --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++ --disable-multilib Thread model: posix
OS:                Linux

Kopete crashes on startup when there're some offline messages (I noticed this with messages from jabber contacts). It shows stardard KDE notifications about messages and immediately crashes. Bug report will follow.

Comment 1 Alexey Chernov 2008-05-08 13:04:35 UTC

Created attachment 24671 [details]
Crash report

Comment 2 Dennis Nienhüser 2008-05-15 23:18:53 UTC

*** Bug 162002 has been marked as a duplicate of this bug. ***

Comment 3 Dennis Nienhüser 2008-05-15 23:43:27 UTC

*** Bug 162131 has been marked as a duplicate of this bug. ***

Comment 4 Dennis Nienhüser 2008-05-15 23:48:57 UTC

SVN commit 808179 by nienhueser:

Don't call postNewEvent if event is zero. Already fixed in trunk, see commit 796127.
BUG: 161790


 M  +1 -1      kopeteviewmanager.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=808179

Comment 5 Dennis Nienhüser 2008-05-19 19:37:40 UTC

*** Bug 162221 has been marked as a duplicate of this bug. ***

Comment 6 Roman Jarosz 2008-10-16 22:41:40 UTC

*** Bug 164923 has been marked as a duplicate of this bug. ***

Comment 7 George Kiagiadakis 2008-11-01 10:49:05 UTC

*** Bug 173854 has been marked as a duplicate of this bug. ***