Page MenuHomeSolus

Kernel patches don't require a reboot
Closed, InvalidPublic

Description

Whenever kernel patches arrive and install, there is no notification saying that a reboot is necessary to activate them. One could easily make the mistake of thinking that they had taken immediate effect. I don't think it's right to force users to reboot, because then Solus would end up like other distros that constantly annoy with that sort of thing. But if, and only if, there are updates which which require a reboot, then it would be nice to see a notification of that somewhere, even just during the download and install process.

Event Timeline

Indeed. Although, this should be done in software center or budgie so you might want to report it to their respective github issue trackers.

Yeah so I want to make this two fold and will welcome any feedback on this one..

Right now in the kernel pspec we actually set the action to needing reboot, but the SC doesn't currently notify. I think perhaps a visual warning in the SC before performing the update should be shown, saying they'll need to reboot after.

Perhaps also a dialog at the end? I don't know.

The other part is that some ypkg packages would also justify a reboot, such as glibc security updates. Currently we emit this information based on git changelog, so if we see CVE-XXXX-XXXX we know it's a security update. What I can't figure out is a nice way of expressing in the changelog that the user needs to reboot.

@JoshStrobl thoughts?

But is there really need to reboot? It's not like the system won't function properly, right? I think a reboot button once the updates are applies would suffice.

You do need to reboot after installing kernel updates yes. No kernel modules can be activated on a version update until you've rebooted.
This means if you plug in a USB for the first time, it won't work

Perhaps you might consider changing the update button colour to the same colour used in the restart computer dialog to subtly indicate that a package requiring a reboot has been selected. Also a pop up when clicked explaining why a reboot is necessary? Next time, it will be immediately visible that a reboot is required without reading the pop up.

DataDrake moved this task from Backlog to Improvement on the Software board.Oct 28 2016, 8:38 PM
DataDrake triaged this task as Normal priority.Oct 29 2016, 3:14 AM
ikey closed this task as Invalid.Feb 4 2017, 11:53 PM

Closing this as it won't be necessary when we bring in clr-boot-manager (T2145)