| Summary: | KNotify messages do not go away when action is performed | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Max <bogusman222> |
| Component: | RPM Packages | Assignee: | John Balcaen <balcaen.john> |
| Status: | RESOLVED OLD | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | balcaen.john, marja11, stormi-mageia |
| Version: | 1 | Keywords: | UPSTREAM |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| See Also: | https://bugs.kde.org/show_bug.cgi?id=277428 | ||
| Whiteboard: | |||
| Source RPM: | kdebase4-runtime | CVE: | |
| Status comment: | |||
|
Description
Max
2011-07-05 22:44:43 CEST
All apps exhibit this behaviour or particular ones? The updates applet, you mean the Mageia system updates? (that's mgaapplet). Source RPM:
(none) =>
kdebase4-runtime (In reply to comment #1) > All apps exhibit this behaviour or particular ones? > > The updates applet, you mean the Mageia system updates? (that's mgaapplet). No. When an update is available KNotify sends you a message. The message states that an update is available and contains a button that will open mgaaplet. In Mandriva this worked the same way, however clicking the button also dismissed the message. This behavior can also be observed after copying a large file (so it takes a few seconds). The Notifications and Jobs plasmoid shows the progress of the file being copied, and when it is complete KNotify shows you a message declaring it complete, with a button that will open the file destination in Dolphin. However, clicking the button does not dismiss the message. To dismiss the message I need to click the Notifications and Jobs plasmoid, then click the X on the message. Additionally: the same behavior appears when you get a ping on Quassel. KNotify pops up with the message and a "View" button. Clicking the button sends you to Quassel, but does not dismiss the message. I'm thinking this is a global problem with KNotify, and if so, I'll submit this bug to the KDE people. Just let me know.
Ahmad Samir
2011-07-09 15:37:06 CEST
Assignee:
bugsquad =>
balcaen.john It seems to be an upstream « bug » because this behavior is still available for KDE SC 4.7 (in cauldron), i doubt it will be fixed for KDE SC 4.6 (since 4.6.5 is out) but it should be better to report it & eventually get it fixed for KDE SC 4.7 Maybe you can also give a try to colibri as an alternative for notifications in kde. CC:
(none) =>
balcaen.john
Samuel Verschelde
2011-10-01 16:20:37 CEST
Keywords:
(none) =>
UPSTREAM (In reply to comment #4) > It seems to be an upstream « bug » because this behavior is still available for > KDE SC 4.7 (in cauldron), i doubt it will be fixed for KDE SC 4.6 (since 4.6.5 > is out) but it should be better to report it & eventually get it fixed for KDE > SC 4.7 @ Max Did you report upstream? Please put the link in the "See Also: Add Bug URLs" field of this bug report CC:
(none) =>
marja11
Max
2012-01-07 18:26:00 CET
See Also:
(none) =>
https://bugs.kde.org/show_bug.cgi?id=277428 @ Max Thanks I don't really Reza's comment, I do not know what "master" means, nor what he means by his last line. https://bugs.kde.org/show_bug.cgi?id=277428#c1 > I'm trying to reproduce this at 4.8 master. but cannot. > Can you please try again using the recent 4.7 series or master if possible? > The notification icon display 'no active job or notifications' @ John From comment 4 I understand you reproduced this for 4.7. If that is correct, do you mind saying that in a comment upstream? 3 monthly ping. Upstream's question wasn't answered, btw. This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad Appears to be fixed in Mga2 KDE 4.8, so setting RESOLVED OLD. Status:
NEW =>
RESOLVED |