Version: (using KDE 4.2.0) Compiler: gcc (GCC) 4.1.2 (Gentoo 4.1.2 p1.0.2) OS: Linux Installed from: Gentoo Packages When renaming a contact for which a notification is currently present in the system tray but has not been acknowledged yet, the notification will remain indefinitely. Steps to reproduce: 1. Open a chat window to a contact, get the other person to say something after a few seconds delay. 2. Before that person says something, switch away from the chat window. 3. Wait for the notification in the system tray. 4. Switch to the main kopete window and rename the contact to something else. 5. No matter what you do (switch to the chat window, click on either "view" or "ignore" buttons in the notification or even restart kopete), the notification remains and cannot be removed (short of logging in again). I reproduced this with a metacontact that had two accounts (Jabber and ICQ) attached, I don't know if this only occurs with simple contacts.
Btw. found a workaround to actually remove the notification without having to login again: 1) Run dbus-monitor "path=/VisualNotifications" 2) Click on any notification button (view or ignore) and look for the _first_ uint32 parameter of the message that was generated by clicking the button (something with "invoke") 3) Run the following python script: import dbus bus = dbus.SessionBus() notify = dbus.Interface (bus.get_object('org.kde.VisualNotifications', '/VisualNotifications'), dbus_interface='org.kde.VisualNotifications') notify.CloseNotification (20) Where 20 is the id of the notification from dbus-monitor. 4) Notification should be gone.
*** Bug 192319 has been marked as a duplicate of this bug. ***
- Can anyone check this on KDE4.3 ? Thanks
I just tried to verify this with a recent trunk (r1061124) and closing the notification always worked. :) However, I also noticed that usually the notification is closed automatically when changing focus to the chat window. This was not the case after renaming the contact and I had to close the notifications myself.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!