Description of problem: When updating packages that require a restart (or a logout/login) with packagekit, notifications appear before the end of the yum upgrade. The notifications appear in a stack coming from the 'i' icon in the kde system tray. I think they come around the end of the testing packages phase, or the beginning of the install packages phase. Then when the update is complete, a restart icon appears in the systray. Additionally, there is one notification stacking up per package requiring restart. None of these notifications show which package caused it. The kpackagekit restart icon is much friendlier - it simply lists the packages requiring update in a list in a tooltip. Version-Release number of selected component (if applicable): kpackagekit-0.4.1.1-1.fc11.i586 kdebase-workspace-4.2.4-5.fc11.i586 PackageKit-0.4.8-2.fc11.i586
IIRC the notifications actually come from PackageKit, is that correct Richard? -- Steven M. Parrish - KDE Triage Master - PackageKit Triager Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Yes, the signals come from packagekitd, which kpackagekit turns into notifications. I think that restart notifications should be just a tooltip as suggested, not notification bubbles.
We filed this bug in the upstream database () and believe that it is more appropriate to let it be resolved upstream. We will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates. Thank you for the bug report. -- Steven M. Parrish - KDE Triage Master - PackageKit Triager Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I've now seen notifications at the very beginning of the update process. In that case a larger cluster of notifications occurred later in the process, while I was away from the computer. I also noticed that the update icon in the systray during the update process. It's suppressed by the icon kpackagekit uses to show what it's currently doing, but is visible in the list of tasks if the kpackagekit systray icon is clicked on. I see that upstream believes that the timing of the notifications is the responsibility of the packagekit backend.
(In reply to comment #4) > I see that upstream believes that the timing of the notifications is the > responsibility of the packagekit backend. No, it's up to the frontend to take the notifications whenever they happen and batch them up to show the user at the end. There's nothing in the spec about when signals have to come during the transaction.
Is this related to bug #513856 ?
Seems so.
*** Bug 521236 has been marked as a duplicate of this bug. ***
*** Bug 524070 has been marked as a duplicate of this bug. ***
This may be fixed in kpackagekit 0.5.x, but I think this release requires a newer PackageKit (intended for F12?). Would this be worth back-porting to kpackagekit 0.4.x?
Just saw this. Resolved bug upstream does not solve this. PackageKit-0.4.9-1.fc11.i586 kpackagekit-0.4.2-1.fc11.i586 Can f11 go to kpackagekit 0.5?
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. 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 Fedora version prior to Fedora 11'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 Fedora 11 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 Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
This has been cloned a couple of times (bug 582079 and bug 553356). I'm not sure why there's no link from this bug to the clones nor what the utility of cloning is. Anyway, this behaviour has re-appeared in f12, albeit with a new twist. https://bugzilla.redhat.com/show_bug.cgi?id=553356#c2 gives details.
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.
The main difference now, Fedora 13 (and iirc 12 as well), is that there is no longer one stacked notification per package. Thankfully, the "Restart" button from the systray does not work - if it did, a reboot would occur during yum's update, which is probably undesirable...
Seen on F13 as well
*** Bug 622450 has been marked as a duplicate of this bug. ***
Have this on Fedora 13: kpackagekit-0.6.0-2.fc13.x86_64 kernel 2.6.33.6-147.fc13.x86_64 kdebase-4.4.5-1.fc13.x86_64 yum-3.2.28-1.fc13.noarch rpm-4.8.1-2.fc13.x86_64 Also Fedora 12 on other computrer has this issue.
so looks like the original bug is: https://bugzilla.redhat.com/show_bug.cgi?id=513755 so that following may be closable duplicates: https://bugzilla.redhat.com/show_bug.cgi?id=553356 https://bugzilla.redhat.com/show_bug.cgi?id=582079 https://bugzilla.redhat.com/show_bug.cgi?id=616915
No longer a problem in current F13.
*** Bug 616915 has been marked as a duplicate of this bug. ***