Description of problem: When there are updates found by mgaupdate it popup a notification. From this notification there is a button to install updates. This button doesn't call application to launch update like red icon do. Mageia-5-beta3-x86_64-DVD on VM. I also put a picture of 2 notifications : - first notification is the default notification, - second : button "install" disappear after click on it but not action is triggered. Reproducible: Steps to Reproduce:
Created attachment 5938 [details] mgaupdate notification in FR I forgot to mention : I use FR localization.
looks kde, thierry I remember it was supposed to be fixed no ?
CC: (none) => balcaen.john, lmenut, neoclustAssignee: bugsquad => thierry.vignaudSummary: Button of mgaupdate notification didn't work => Button of mgaupdate notification didn't work (kde)
That would be an issue with whatever notification daemon is used by KDE (knotify4), not an mgaonline bug
Assignee: thierry.vignaud => bugsquadSource RPM: mgaonline => kdebase4-runtime
Here is a patch that fixes the issue for me: diff --git a/mgaapplet b/mgaapplet index 4c80055..690a14f 100755 --- a/mgaapplet +++ b/mgaapplet @@ -685,7 +685,7 @@ sub setState { } } elsif ($state eq 'updates') { unshift @arr, 'upgrade_distro' if $new_distro; - $bubble->add_action('updates', N("Install updates"), sub { installUpdates() }); + $bubble->add_action('updates', N("Install updates"), launch => \&installUpdates ); } elsif (member($state, qw(no_enabled_medium no_update_medium))) { $bubble->add_action('add_med', N("Add media"), sub { add_media() }); } If the workaround is good enough, the same changes should probably be applied for the other "bubble" actions that are "upgrade", "no_more", "add_med". WDYT Thierry?
CC: (none) => remi
Nevermind my comment 4, I was testing my patch without having restarted mgaapplet, so maybe my patch is completely bogus. Will investigate more.
Note that the Install button *does* work when the notification first pops up. It's once it gets saved into the notifications list (after a few seconds) that the button is still there but doesn't do anything.
I've done a bit more debugging, and actually it looks like something times out after a couple of seconds and the button doesn't work anymore afterwards. - If you click the first popup as soon as you are notified, the button works - If you wait 3/4 seconds and then click the button (still in the same popup), the button does not work - If you close or ignore the popup, but instead open the notifications list, it exhibits the same behaviour. If you open the list and click the button, all under less than 3/4 seconds after being first notified by the popup, the button works. - Similarly, if you wait too long and click on the button in the notifications list, it doesn't work.
Whiteboard: (none) => MGA5TOO FOR_ERRATA
Is this bug likely to hit many users?
The same problem was reported in KDE4 with the popup in mgaapplet that says a repository needs to be added, see attachment 7732 [details] After clicking on "Ajouter" (Add) it disappears and nothing happens. https://bugs.mageia.org/show_bug.cgi?id=9386#c20
CC: (none) => marja11
don't know why this never got assigned to KDE team
Assignee: bugsquad => mageia
Version: Cauldron => 5Whiteboard: MGA5TOO FOR_ERRATA => (none)
Assignee: mageia => kde
CC: lmenut => (none)
CC: (none) => mageiaAssignee: kde => mageiatools
@ Stéphane, We regret if this issue didn't get fixed in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/ It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed. I assume this bug doesn't exist in Mageia 6 or later, because KDE and its tools are entirely different there. Closing as OLD. Please reopen this report and change its "Version:" at the top left to "6", if the same bug still exists in Mageia 6. ==> If you didn't reset your password after february 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report.<==
(In reply to Marja Van Waes from comment #11) > > Closing as OLD. > Now really closing :-/
Status: NEW => RESOLVEDResolution: (none) => OLD