Red Hat Bugzilla – Bug 459020
Need notification that reboot is required after update
Last modified: 2009-02-13 19:30:37 EST
Today the "bug fix available" icon appeared on my upper Gnome panel. I clicked on it and downloaded some RPM updates. I happened to look through the details of the updates and notices that some of them (such as the new kernel) require an reboot to take effect, but I was never prompted to do so. If I had just chosen "update" without examining any details, I never would have known. There should be a pop-up or some other prompt for the benefit of novice or inattentive users. Ideally, it would allow the option of rebooting now, scheduling an overnight reboot, or ignoring the warning.
Bug 149692 and Bug 103962 address the same issue, though they are filed against non-Fedora products.
Created attachment 314379 [details]
Don't you get the restart notifier in the notification area?
No, and it took me about a day before I got around to rebooting after the update.
I can confirm. I finally did an update on my F9 machine as well, and was surprised to see that there was no notification to reboot after updating the kernel.
This is fixed in rawhide, I'll backport to updates-testing now.
Created attachment 329115 [details]
2 screenshots: hover-over and click-on results
I installed kernel-2.6.29-0.35.rc1.git4.fc11.x86_64 today using the GUI. I got a yellow warning triangle in the notification area, with the hover-over popup "You will need to log off and log back on". Clicking on the triangle popped up a menu which offered to restart the computer or hide the icon. Logging off and back on cleared the triangle, but it didn't boot the machine into the new kernel. The hover-over menu is misleading; it should say that the machine needs to be restarted.
With today's Rawhide update, I got a message saying I needed to log out and back in, and a list of packages given as the reason for this, but once again even though a new kernel had been installed, I wasn't prompted to reboot.
I left my desktop alone after the update finished for several hours, and when I came back and de-activated the screen saver, the notification icon was gone. I think it should remain until the user either logs out or explicitly dismisses the icon.
We don't get the restart-required(system) when you're using rawhide as we don't get the metadata from bohdi. We generate the restart-required(session) data in the daemon ourselves, and thus it's the best we can do. As soon as we switch to F11, the restart-required actions will work correctly.
notabug then, I guess