Bug 517907

Summary: Too many notification windows (1 per restart or logout-requiring update)
Product: [Fedora] Fedora Reporter: Grégoire Paris <postmaster>
Component: kpackagekitAssignee: Steven M. Parrish <smparrish>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 11CC: balajig81, kevin, ltinkl, rdieter, rhughes, richard, smparrish
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-08-17 21:07:51 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot showing the bug none

Description Grégoire Paris 2009-08-17 20:04:51 UTC 
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
3.
  
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.
Comment 1 Grégoire Paris 2009-08-17 20:06:42 UTC 
Created attachment 357700 [details]
Screenshot showing the bug
Comment 2 Rex Dieter 2009-08-17 20:11:07 UTC 
See:
https://admin.fedoraproject.org/updates/F11/FEDORA-2009-8633
Comment 3 Rex Dieter 2009-08-17 20:13:03 UTC 
Yeah, there's a relevant PackageKit bug for numerous restart requests too, don't have that handy offhand.
Comment 4 Kevin Kofler 2009-08-17 21:07:51 UTC 

*** This bug has been marked as a duplicate of bug 517476 ***
Comment 5 Oliver Henshaw 2009-08-17 21:13:00 UTC 
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.
Comment 6 Richard Hughes 2009-08-18 08:11:32 UTC 
(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.