Bug 1400911

Summary: Offline upgrade to F25 failed (packagekitd crashed); no visible feedback
Product: [Fedora] Fedora Reporter: Will Thompson <will>
Component: PackageKitAssignee: Richard Hughes <rhughes>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: jonathan, klember, rdieter, rhughes, smparrish
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 19:23:49 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
journal from the boot where the offline upgrade failed. none

Description Will Thompson 2016-12-02 09:37:49 UTC
Created attachment 1227251 [details]
journal from the boot where the offline upgrade failed.

Description of problem:

I attempted an upgrade from F24 to F25 using GNOME Software. On reboot, I saw the “upgrading system; this may take a while” message and the Fedora logo progress indicator began to move, then stopped.

On logging in on another VT, I discovered that packagekitd had aborted:

PackageKit[1031]: upgrade-system transaction /4699_adbeeaeb from uid 0 finished with failed after 1190ms
pk-offline-update[1011]: status finished
packagekitd[1031]: *** Error in `/usr/libexec/packagekitd': corrupted double-linked list (not small): 0x00007fb78817bdf0 ***
audit[1031]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=system_u:system_r:rpm_t:s0 pid=1031 comm="packagekitd" exe="/usr/libexec/packagekitd" sig=6
packagekitd[1031]: ======= Backtrace: =========
packagekitd[1031]: /lib64/libc.so.6(+0x7566b)[0x7fb7ad25266b]
packagekitd[1031]: /lib64/libc.so.6(+0x7b844)[0x7fb7ad258844]
packagekitd[1031]: /lib64/libc.so.6(+0x7e615)[0x7fb7ad25b615]
packagekitd[1031]: /lib64/libc.so.6(cfree+0x4c)[0x7fb7ad25e36c]
packagekitd[1031]: /lib64/librepo.so.0(lr_yum_repo_free+0x3a)[0x7fb79da4be0a]
packagekitd[1031]: /lib64/librepo.so.0(lr_result_clear+0x23)[0x7fb79da4a533]
packagekitd[1031]: /lib64/librepo.so.0(lr_result_free+0xe)[0x7fb79da4a55e]
packagekitd[1031]: /lib64/libhif.so.1(+0x11d18)[0x7fb79e343d18]
packagekitd[1031]: /lib64/libgobject-2.0.so.0(g_object_unref+0x1a7)[0x7fb7adcf4117]
packagekitd[1031]: /lib64/libglib-2.0.so.0(g_ptr_array_foreach+0x3b)[0x7fb7ad9f007b]
packagekitd[1031]: /lib64/libglib-2.0.so.0(+0x1e110)[0x7fb7ad9f0110]
packagekitd[1031]: /usr/lib64/packagekit-backend/libpk_backend_hif.so(pk_backend_stop_job+0x54)[0x7fb79f5f95c4]
packagekitd[1031]: /usr/libexec/packagekitd(+0x130d8)[0x55fe7485d0d8]
packagekitd[1031]: /usr/libexec/packagekitd(+0x1ce46)[0x55fe74866e46]
packagekitd[1031]: /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x15a)[0x7fb7ada1b6ba]
packagekitd[1031]: /lib64/libglib-2.0.so.0(+0x49a70)[0x7fb7ada1ba70]
packagekitd[1031]: /lib64/libglib-2.0.so.0(g_main_loop_run+0xc2)[0x7fb7ada1bd92]
packagekitd[1031]: /usr/libexec/packagekitd(main+0x4e9)[0x55fe74858239]
packagekitd[1031]: /lib64/libc.so.6(__libc_start_main+0xf1)[0x7fb7ad1fd731]
packagekitd[1031]: /usr/libexec/packagekitd(_start+0x29)[0x55fe748583e9]

(Full log attached.)

There was no user-facing indication that this had happened (beyond no progress being shown). If I didn't know how to VT switch and check what was going on, I would probably have left it for a while and then hard power-cycled the computer.

Version-Release number of selected component (if applicable):

PackageKit-1.1.3-2.fc24.x86_64

How reproducible:

Only happened once. When the system came back up, I ran `dnf update` in the hope of getting an updated PackageKit (nope) and tried another system upgrade from GNOME Software. This "upgrade" completed very quickly and did not, in fact, upgrade my system – I am still running F24.

Unfortunately I don't have a core file.

Comment 1 Fedora End Of Life 2017-07-26 00:02:19 UTC
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2017-08-08 19:23:49 UTC
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.