[Bug 1196512] New: pkcon sometimes fails with "The daemon crashed mid-transaction!"
https://bugzilla.suse.com/show_bug.cgi?id=1196512 Bug ID: 1196512 Summary: pkcon sometimes fails with "The daemon crashed mid-transaction!" Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs@opensuse.org Reporter: dfaggioli@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- When on MicroOS Desktop, and trying to use `pkcon` for upgrades, it sometimes fails with the message "The daemon crashed mid-transaction!" Like this:
# pkcon upgrade-system Getting system upgrades [=========================] Testing changes [=========================] g: assertion > 'string != NULL' failed Finished [ ] (0%) The following packages have to be installed: gtk4-tools-4.6.1-2.1.x86_64 Auxiliary utilities for the GTK+ toolkit library v4 The following packages have to be obsoleted: systemd-sysvinit-249.9-4.1.x86_64 System V init tools The following packages have to be updated: Mesa-21.3.6-301.3.x86_64 System for rendering 3-D graphics Mesa-dri-21.3.6-301.3.x86_64 DRI plug-ins for 3D acceleration Mesa-gallium-21.3.6-301.3.x86_64 Mesa Gallium GPU drivers ... ... ... zenity-3.41.0-1.4.x86_64 GNOME Command Line Dialog Utility zstd-1.5.2-1.3.x86_64 Zstandard compression tools zypper-1.14.51-1.2.x86_64 Command line software manager using libzypp Proceed with changes? [N/y]
The daemon crashed mid-transaction!
Now, In order to help debugging, I did the following:
# systemctl stop packagekit # /usr/libexec/packagekitd --disable-timer --verbose 2>&1 | packagekit.log
And then retried the `upgrade-system`. Well, guess what? It worked just fine :-| So, what I'm going to do is to open this bug, and even attach the "good log" that it produced. As soon as I can reproduce a crash with logging enabled, I'll update and post the "bad log". In the meanwhile, if anyone has any idea what it could be that it's failing, I'd be happy to help testing theories. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196512 https://bugzilla.suse.com/show_bug.cgi?id=1196512#c1 --- Comment #1 from Dario Faggioli <dfaggioli@suse.com> --- Created attachment 856586 --> https://bugzilla.suse.com/attachment.cgi?id=856586&action=edit PackageKit logs when everything works Here's the "good log". Just to be clear, this log is what I see when the upgrade works and I *DON'T* get the "daemon crashed" message from the `pkcon upgrade-system` command. I'll post a "bad log" as soon as I manage to capture one. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196512 https://bugzilla.suse.com/show_bug.cgi?id=1196512#c2 --- Comment #2 from Dario Faggioli <dfaggioli@suse.com> --- (In reply to Dario Faggioli from comment #1)
Created attachment 856586 [details] PackageKit logs when everything works
Here's the "good log". Just to be clear, this log is what I see when the upgrade works and I *DON'T* get the "daemon crashed" message from the `pkcon upgrade-system` command.
So, despite everything has worked in this case, I see some instances of:
*** 18:29:03 PackageKit failed to set job id: attempt to write a readonly database ***
Or of:
*** 18:29:44 PackageKit SQL error: attempt to write a readonly database *** *** 18:29:44 PackageKit SQL error: 8: attempt to write a readonly database ***
They seem to be non-fatal, as the actual upgrade worked this time... But I wonder if they could be related and, even if not, we may want to and can fix them anyway... -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1196512 https://bugzilla.suse.com/show_bug.cgi?id=1196512#c3 --- Comment #3 from Dario Faggioli <dfaggioli@suse.com> --- Created attachment 856667 --> https://bugzilla.suse.com/attachment.cgi?id=856667&action=edit Packagekit logs. Another good and 100% workking upgrade Just FTR, I just did another `upgrade-system` and it again worked fine. This time, I spotted this in the logs, but again seems not to be too big of a deal:
15:17:47 PackageKit-DNF got state loading-cache with hint (null)
(packagekitd:3965): libdnf-WARNING **: 15:17:47.934: Skipping refresh of repo-update: cannot update repo 'repo-update': Yum repo downloading error: Downloading error(s): repodata/f4fba37aa004f93b3b9f72917e4621a69964f902184252d9cfce7f49399cb2fe-primary.xml.gz - Cannot download, all mirrors were already tried without success; repodata/a5ca84342048635bc688cde4d58177cedf845481332d86b8e4d6c70182970a86-filelists.xml.gz - Cannot download, all mirrors were already tried without success; repodata/886ae59496d93c03a07e5bd00ae20643def6c4293bf1ab6535c203342298f6fc-updateinfo.xml.gz - Cannot download, all mirrors were already tried without success; Last error: Curl error (60): SSL peer certificate or SSH remote key was not OK for https://rsync.opensuse.org/repositories/openSUSE:/Factory:/Update/standard/r... [SSL certificate problem: unable to get local issuer certificate] 15:17:47 PackageKit-DNF got state loading-cache with hint (null) 15:17:47 PackageKit-DNF got state download-repository with hint (null) 15:17:48 PackageKit-DNF got state loading-cache with hint (null)
This upgrade included the switch to a newer kernel, which also worked (which re-confirms that the old bug we used to have about bootloader updating is also gone, which matches with my recollection of it). Will keep this updated... -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply＠suse.com