Bug 162484

Summary:	Kopete crash, problem with info bubbles
Product:	[Unmaintained] kopete	Reporter:	Michal Kucera <mkem>
Component:	general	Assignee:	Kopete Developers <kopete-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	joaomitch
Priority:	NOR
Version First Reported In:	0.50.1
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	crash of Kopete during save new settings here is screenshot of bubbles error

Description Michal Kucera 2008-05-22 19:46:00 UTC

Version:            (using KDE 4.0.4)
Installed from:    Fedora RPMs
OS:                Linux

When I go to settings of Kopete and set something in TAB "BEHAVIOUR" and than I click on "USE" or "OK" button, kopete crash without any information. But new settings is saved. 

I have problems with info bubbles. When somebody write me, bubbles are shown but they don't disappear.

Comment 1 Michal Kucera 2008-05-22 19:49:37 UTC

Created attachment 24894 [details]
crash of Kopete during save new settings

Comment 2 Michal Kucera 2008-05-22 19:50:26 UTC

Created attachment 24895 [details]
here is screenshot of bubbles error

Comment 3 Michal Kucera 2008-05-22 19:51:47 UTC

It is Kopete v. 0.50.1

Comment 4 Dennis Nienhüser 2008-05-23 01:36:35 UTC

Confirming as it happens on my little brother's system as well ;-)

The bubbles will automatically close in the Kopete version coming with KDE 4.1.

Comment 5 Dennis Nienhüser 2008-05-23 09:54:54 UTC

Michal, can you please check the following: In the Behavior settings, open the "Chat" tab. Is the drop down box in the "Interface Preference" group empty?

Comment 6 Dennis Nienhüser 2008-05-23 10:49:19 UTC


*** This bug has been marked as a duplicate of 161078 ***

Comment 7 Michal Kucera 2008-05-24 21:16:50 UTC

yes It is empty

Comment 8 Dennis Nienhüser 2008-05-24 22:38:46 UTC

Ok, thanks for the verification. It will be fixed in the Kopete version coming with KDE 4.0.5.

Comment 9 Dennis Nienhüser 2008-06-27 22:17:38 UTC

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