Description of problem:
If 3 packages require a system restart, and 4 other require a logout, 7
notification window appear on top of each other.
I would rather expect one or two windows with a summary.
Version-Release number of selected component (if applicable): 0.4.1.1-2.fc11
How reproducible: very often
Steps to Reproduce:
1. Juste wait for a couple of restart or logout-requiring updates to happen
2. approve the update
Actual results: There are as many notification windows as updates
Expected results: One window requiring the a logout if there are only logout-requiring updates, or a restart if there is a restart-requiring update
Additional info: I already reported the bug on bugs.kde.org and was told that it was Fedora's problem.
Created attachment 357700 [details]
Screenshot showing the bug
Yeah, there's a relevant PackageKit bug for numerous restart requests too, don't have that handy offhand.
*** This bug has been marked as a duplicate of bug 517476 ***
I think the "fedora problem" mentioned is about the timing of update notifications, not the number of them. See bug #513755.
I'm not sure whether any consensus has been reached on whether kpackagekit or the PackageKit backend are responsible for delaying the notifications until the update is complete.
(In reply to comment #5)
> I'm not sure whether any consensus has been reached on whether kpackagekit or
> the PackageKit backend are responsible for delaying the notifications until the
> update is complete.
There's nothing in the PackageKit spec about timing, so the frontend has to queue these, not the daemon or backend.