Bug 181005 - Nothing happens when clicking "View" or "Ignore" in Kopete notification window
Summary: Nothing happens when clicking "View" or "Ignore" in Kopete notification window
Status: RESOLVED DUPLICATE of bug 182481
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: 0.60.82
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
: 180782 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-01-16 19:13 UTC by Ole Rasmussen
Modified: 2009-02-01 15:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Ole Rasmussen 2009-01-16 19:13:18 UTC 
Version:           0.60.82 (using 4.1.96 (KDE 4.1.96 (KDE 4.2 RC1)) "release 77.1", KDE:KDE4:Factory:Desktop / openSUSE_11.1)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.27.7-9-default

When Kopete is set to show a message window on incoming messages (default behavior) nothing happens when I click the "View" or "Ignore" button on the window when I receive a new message. Normally, View would close the notification window and show the IM window but neither happens.
The only way to close the notification window is to drag it. If I drag it a bit away from it's default position in the bottom lower right corner it disappears when I release the mouse button.

This is consistent behavior. The buttons *never* work for me.
Comment 1 Ole Rasmussen 2009-01-18 15:17:14 UTC 
Actually this seems to be not a problem specific to Kopete but generally all notification windows in KDE. The buttons simply doesn't work.
Comment 2 Florian Reinhard 2009-01-27 01:15:05 UTC 
*** Bug 180782 has been marked as a duplicate of this bug. ***
Comment 3 Caleb Cushing 2009-02-01 01:25:11 UTC 
confirmed 4.2.0 kopete 0.70.0 (if it is all notifications then re-assign bug to appropriate people).
Comment 4 Roman Jarosz 2009-02-01 15:42:26 UTC 

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