http://bugzilla.opensuse.org/show_bug.cgi?id=954125 http://bugzilla.opensuse.org/show_bug.cgi?id=954125#c1 Bjørn Lie changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED CC| |zaitor@opensuse.org --- Comment #1 from Bjørn Lie --- I just reproduced this. I've seen it before too, but at the time I was playing with a hacked PackageKit so I assumed it was that.... For some reason the reboot is not triggered, even if packagekit exits as done. Nov 07 15:14:51 linux-b3rv PackageKit[860]: update-packages transaction /1_bcdebaed from uid 0 finished with success after 104197ms Nov 07 15:14:51 linux-b3rv kernel: audit: type=1130 audit(1446934491.219:100): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=packagekit-offline-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 07 15:14:51 linux-b3rv kernel: audit: type=1131 audit(1446934491.219:101): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=packagekit-offline-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 07 15:14:51 linux-b3rv audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=packagekit-offline-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 07 15:14:51 linux-b3rv audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=packagekit-offline-update comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Nov 07 15:15:07 linux-b3rv PackageKit[860]: daemon quit Nov 07 15:15:07 linux-b3rv packagekitd[860]: (packagekitd:860): GLib-CRITICAL **: Source ID 11 was not found when attempting to remove it -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=954125 http://bugzilla.opensuse.org/show_bug.cgi?id=954125#c3 --- Comment #3 from Bjørn Lie --- (In reply to Atri Bhattacharya from comment #2)

Seems to be a regular occurrence now. Happened to me again, this time while updating to 20151110.

Please do a systemctl status packagekit-offline-update and lets see what it says (I reproduced the error today too, and forgot the above.. shame on me!) -- You are receiving this mail because: You are on the CC list for the bug.

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.

http://bugzilla.opensuse.org/show_bug.cgi?id=954125 http://bugzilla.opensuse.org/show_bug.cgi?id=954125#c7 --- Comment #7 from Dominique Leuenberger --- Buhuu... pk 1.0.10 checks if /system-update points to /var/cache/PackageKit (where it would expect the rpms to reside); if not, it's meant to not do the update, as it would indicate 'something else prepared for the update'. we do not provide the /var/cache/PackageKit directory. as we do not store the RPMs there.. hence, the /system-update symlink is dangling, resulting in pk-offline-update claiming the triggers were not set (REBOOT action not being set) pk-offline-update later on verifies if the symlink points to /var/cache/PackageKit (without caring if the target exists) and if it does, it applies the patches... The easiest fix for us is to just provide an empty directory /var/cache/PackageKit I guess. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=954125 http://bugzilla.opensuse.org/show_bug.cgi?id=954125#c9 Dominique Leuenberger changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #9 from Dominique Leuenberger --- Request: #344260 submit: home:dimstar:branches:GNOME:Factory/PackageKit@3(cleanup) -> GNOME:Factory Message: - Add PackageKit-fix-offline-trigger.patch: Fix the PK trigger detection: if not done properly, PK might believe that something else triggered the system update and expects something else to handle the update (boo#954125). -- You are receiving this mail because: You are on the CC list for the bug.