http://bugzilla.opensuse.org/show_bug.cgi?id=954125
http://bugzilla.opensuse.org/show_bug.cgi?id=954125#c5
Dominique Leuenberger changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dimstar@opensuse.org
--- Comment #5 from Dominique Leuenberger ---
Strange one...
checking the service from within the 'running but not yet rebooted offline
update boot':
● packagekit-offline-update.service - Updates the operating system whilst
offline
Loaded: loaded (/usr/lib/systemd/system/packagekit-offline-update.service;
static; vendor preset: disabled)
Active: inactive (dead) since Thu 2015-11-12 19:48:21 CET; 1min 25s ago
Main PID: 731 (code=exited, status=0/SUCCESS)
=> so, the service EXITED with status 0...
the exit status is as such is not strange, but the end of pk-offline-update.c
is:
/* we have to manually either restart or shutdown */
if (action == PK_OFFLINE_ACTION_REBOOT)
pk_offline_update_reboot ();
else if (action == PK_OFFLINE_ACTION_POWER_OFF)
pk_offline_update_power_off ();
return retval;
On my last attempt, I checked the content of
/var/lib/PackageKit/offline-update-action, which was correctly set to reboot.
so, we should expect pk_offline_update_reboot to be the next thing to happen;
BUT that would do SD logging as very first thing.
if the status is 'unknown', it would go for a reboot
There are 4 possible actions:
UNSET
REBOOT
POWEROFF
UNKNOWN
UNSET is the only one resulting in the daemon exiting without a reboot/shutdown
trigger, but that should only happen when the env variable
PK_OFFLINE_UPDATE_TEST has been set
--
You are receiving this mail because:
You are on the CC list for the bug.