Opened 13 months ago
Closed 13 months ago
#542 closed enhancement (fixed)
Indicate when reboot is required after Dom0 update
| Reported by: | joanna | Owned by: | aga |
|---|---|---|---|
| Priority: | major | Milestone: | Release 1 |
| Component: | other | Keywords: | |
| Cc: |
Description
Change History (5)
comment:1 Changed 13 months ago by marmarek
- Resolution set to worksforme
- Status changed from new to closed
comment:2 Changed 13 months ago by joanna
- Resolution worksforme deleted
- Status changed from closed to reopened
Ok, looks good. But there is one more thing -- updates to qubes-manager should probably automatically restart the manager... This might be done in the manager's %post perhaps?
comment:3 Changed 13 months ago by marmarek
- Owner set to aga
- Status changed from reopened to assigned
qubes-manager needs to be started in user environment (with some varibles from KDE - at least XAUTHORITY and DBUS session), but rpm is installed without access to it - in corner case from PackageKit? daemon...
Perhaps this can be done by doing exec() on some signal, which can sent from rpm %post?
comment:4 Changed 13 months ago by aga
Manager restarting after update:
comment:5 Changed 13 months ago by aga
- Resolution set to fixed
- Status changed from assigned to closed

The short story: already working in gpk-update-viewer!
The long story:
Data flow: gpk-update-viewer requests update list from PackageKit?, which fetch it from repository metadata using yum (via PackageKit? yum backend). Metadata sent to Packagekit by PackageKit?-yum can contain 'reboot_sugested' flag.
This flag can be triggered one of:
class PackageKitYumBackend(PackageKitBaseBackend, PackagekitPackage): # Packages there require a reboot rebootpkgs = ("kernel", "kernel-smp", "kernel-xen-hypervisor", "kernel-PAE", "kernel-xen0", "kernel-xenU", "kernel-xen", "kernel-xen-guest", "glibc", "hal", "dbus", "xen")Because of the second option, IMHO there is no need to implement the first one. Which would BTW require some non-trivial work to do it securely, because repository metadata isn't signed by design - only packages have signature (currently we transfer only rpms to dom0 and then recreate metadata).
Of course all of this will work only when using "GUI mode" of qubes-dom0-update (--gui switch). This is default when called by qubes-manager or update-notification icon.