October 2021 - openSUSE Kubic Bugs - openSUSE Mailing Lists

[Bug 1188110] New: pkcon system-upgrade leads to unbootable system with kernel upgrade
by bugzilla_noreply＠suse.com 23 Nov '21

23 Nov '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1188110 Bug ID: 1188110 Summary: pkcon system-upgrade leads to unbootable system with kernel upgrade Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Major Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: alois1(a)gmx-topmail.de QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- I recently installed MicroOS Desktop KDE. I attempted to upgrade this system from 20210704 to 20210706 using pkcon, which included a kenel upgrade to 5.13. This upgrade lead to an unbootable system with the following symptoms: * In the GRUB menu, it is attempted to load the wrong kernel version (5.12.13). * When manually editing the kernel and initrd version to 5.13.0, the initrd enters emergency mode after some delay. * Further investigation shows that initrd is incomplete and lacks at least crypttab, so the partitions on the encrypted disks cannot be mounted and caused the timeout. The issue is reproducible, after rolling back to the last snapshot on 20210704 and attempting the upgrade again the symptoms are the same. I have for now upgraded the system using zypper dup inside tukit. This lead to a working upgraded system. -- You are receiving this mail because: You are the assignee for the bug.

1 14

[Bug 1191945] New: [Build 20211020] t-u 3.5.7 - results in emergency console
by bugzilla_noreply＠suse.com 22 Oct '21

22 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191945 Bug ID: 1191945 Summary: [Build 20211020] t-u 3.5.7 - results in emergency console Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other URL: https://openqa.opensuse.org/tests/1983403/modules/disk _boot/steps/5 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: dimstar(a)opensuse.org QA Contact: qa-bugs(a)suse.de Found By: openQA Blocker: Yes ## Observation openQA test in scenario microos-Tumbleweed-MicroOS-Image-ContainerHost-x86_64-container-host@64bit fails in [disk_boot](https://openqa.opensuse.org/tests/1983403/modules/disk_boot/step… From the journal: Oct 22 07:26:34.116234 localhost combustion[634]: transactional-update 3.5.7 started Oct 22 07:26:34.118437 localhost combustion[634]: Options: shell Oct 22 07:26:34.183109 localhost combustion[634]: Separate /var detected. Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 tukit 3.5.7 started Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 Options: -c1 open Oct 22 07:26:34.682648 localhost combustion[634]: Failure (dbus fatal exception). Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 Using snapshot 1 as base for new snapshot 2. Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 No previous snapshot to sync with - skipping Oct 22 07:26:34.682648 localhost combustion[634]: ID: 2 Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/log] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/lib/zypp] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/lib/ca-certificates] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/lib/alternatives] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/lib/selinux] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/cache] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 ERROR: filesystem error: cannot remove all: Device or resource busy [/.snapshots/2/snapshot/var/tmp] Oct 22 07:26:34.682648 localhost combustion[634]: 2021-10-22 07:26:34 Transaction completed. �� Oct 22 07:26:35.114100 localhost combustion[634]: transactional-update finished Oct 22 07:26:35.134257 localhost combustion[931]: umount: /sysroot/var: target is busy. Oct 22 07:26:35.135028 localhost systemd[1]: combustion.service: Main process exited, code=exited, status=32/n/a Oct 22 07:26:35.142244 localhost systemd[1]: combustion.service: Failed with result 'exit-code'. Oct 22 07:26:35.142512 localhost systemd[1]: Failed to start Combustion. ## Test suite description ## Reproducible Fails since (at least) Build [20211020](https://openqa.opensuse.org/tests/1982883) ## Expected result Last good: [20211019](https://openqa.opensuse.org/tests/1980808) (or more recent) ## Further details Always latest result in this scenario: [latest](https://openqa.opensuse.org/tests/latest?arch=x86_64&distri=microos… -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1191677] php8-nginx container broken
by bugzilla_noreply＠suse.com 18 Oct '21

18 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191677 https://bugzilla.suse.com/show_bug.cgi?id=1191677#c3 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Noah Kalish from comment #2) > Howdy, looks like it's only a problem with rootless podman. I'm not sure if > that's a supported use case or not. rootless podman works fine for me, too. I fail too see why it should not work. The file and directories are readable by everybody. This sounds like something on your container runtime is not Ok, not the latest updates? Some other modifications blocking access to the file? There are no problems with that container as root or rootless with podman on current, fully patched openSUSE MicroOS, Tumbleweed and SLES15 SP3. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191677] New: php8-nginx container broken
by bugzilla_noreply＠suse.com 16 Oct '21

16 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191677 Bug ID: 1191677 Summary: php8-nginx container broken Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: noah(a)spacemule.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- The container registry.opensuse.org/opensuse/php8-nginx fails to start. Here is the output: podman run -v /home/pod/dir-vols/nginx/:/etc/nginx --env DEBUG=1 --pod public --replace --label io.containers.autoupdate=image --name nginx registry.opensuse.org/opensuse/php8-nginx + /usr/bin/find /docker-entrypoint.d/ -mindepth 1 -maxdepth 1 -type f -print -quit + read v /docker-entrypoint.d/ is not empty, will attempt to perform configuration Looking for shell scripts in /docker-entrypoint.d/ + echo '/docker-entrypoint.d/ is not empty, will attempt to perform configuration' + echo 'Looking for shell scripts in /docker-entrypoint.d/' + find /docker-entrypoint.d/ -follow -type f -print + sort -V + read -r f + case "$f" in Launching /docker-entrypoint.d/30-populate-etc.sh + '[' -x /docker-entrypoint.d/30-populate-etc.sh ']' + echo 'Launching /docker-entrypoint.d/30-populate-etc.sh' + /docker-entrypoint.d/30-populate-etc.sh + ETC_DIR=/etc/nginx + '[' '!' -f /etc/nginx/nginx.conf ']' + exit 0 + read -r f Launching /docker-entrypoint.d/40-populate-htdocs.sh + case "$f" in + '[' -x /docker-entrypoint.d/40-populate-htdocs.sh ']' + echo 'Launching /docker-entrypoint.d/40-populate-htdocs.sh' + /docker-entrypoint.d/40-populate-htdocs.sh + HTDOCS_DIR=/srv/www/htdocs ++ ls -A /srv/www/htdocs + '[' '!' '50x.html index.php nginx.html' ']' + exit 0 + read -r f + case "$f" in + '[' -x /docker-entrypoint.d/50-set-timezone.sh ']' + echo 'Launching /docker-entrypoint.d/50-set-timezone.sh' Launching /docker-entrypoint.d/50-set-timezone.sh + /docker-entrypoint.d/50-set-timezone.sh + '[' -n '' ']' + read -r f + case "$f" in + '[' -x /docker-entrypoint.d/90-run-php-fpm.sh ']' + echo 'Launching /docker-entrypoint.d/90-run-php-fpm.sh' Launching /docker-entrypoint.d/90-run-php-fpm.sh + /docker-entrypoint.d/90-run-php-fpm.sh + echo 'Starting php-fpm...' Starting php-fpm... + /usr/sbin/php-fpm [14-Oct-2021 23:41:51] ERROR: failed to open configuration file '/etc/php8/fpm/php-fpm.conf': Permission denied (13) [14-Oct-2021 23:41:51] ERROR: failed to load configuration file '/etc/php8/fpm/php-fpm.conf' [14-Oct-2021 23:41:51] ERROR: FPM initialization failed -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1191678] New: samba container broken since update to 4.15
by bugzilla_noreply＠suse.com 15 Oct '21

15 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1191678 Bug ID: 1191678 Summary: samba container broken since update to 4.15 Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kubic Assignee: kubic-bugs(a)opensuse.org Reporter: noah(a)spacemule.net QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Since samba update to 4.15, the container registry.opensuse.org/opensuse/samba:latest refuses to start. Debug output: podman run --rm --env USER=noah:PASSWORD --env USER1=zogs:PASSWORD -v /var/slow/samba:/samba --env SHARE=zogga:/samba/torrents:yes::yes:noah,zogs:noah,zogs:noah,zogs:Movies_and_Television --env DEBUG=1 --label io.containers.autoupdate=image -p 137:137/udp -p 138:138/udp -p 139:139/tcp -p 445:445/tcp --name samba registry.opensuse.org/opensuse/samba:latest + HOSTNAME=ae50166c364b + WORKGROUP=WORKGROUP + export PATH=/usr/sbin:/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + PATH=/usr/sbin:/sbin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin + CONFIG_FILE=/etc/samba/smb.conf + setup_timezone + '[' -n '' ']' + init_smb_conf + cat + getopts :u:s:h opt + read -r user ++ env ++ awk '/^USER[0-9=_]/ {sub (/^[^=]*=/, "", $0); print}' + add_user zogs:PASSWORD + IFS=: + read -r name password uid group gid + echo -n 'Add user zogs... ' Add user zogs... + [[ -n '' ]] + grep -q '^zogs:' /etc/passwd + useradd -M zogs Failed opening /etc/nsswitch.conf: No such file or directory+ echo -e 'PASSWORD\nPASSWORD' + smbpasswd -s -a zogs Added user zogs. + echo DONE DONE + read -r user + add_user noah:PASSWORD + IFS=: + read -r name password uid group gid Add user noah... + echo -n 'Add user noah... ' + [[ -n '' ]] + grep -q '^noah:' /etc/passwd + useradd -M noah Failed opening /etc/nsswitch.conf: No such file or directory+ echo -e 'PASSWORD\nPASSWORD' + smbpasswd -s -a noah Added user noah. DONE + echo DONE + read -r user + read -r share ++ env ++ awk '/^SHARE[0-9=_]/ {sub (/^[^=]*=/, "", $0); print}' + add_share zogga:/samba/torrents:yes::yes:noah,zogs:noah,zogs:noah,zogs:Movies_and_Television + IFS=: + read -r sharename sharepath browseable ro guest users admins writelist comment + echo -n 'Add share '\''zogga'\'' with path '\''/samba/torrents'\''... ' Add share 'zogga' with path '/samba/torrents'... + echo '[zogga]' + echo ' path = "/samba/torrents"' + [[ -n yes ]] + echo ' browseable = yes' + [[ -n '' ]] + [[ -n yes ]] + echo ' guest ok = yes' + [[ -n noah,zogs ]] ++ tr , ' ' + echo ' valid users = noah zogs' + [[ -n noah,zogs ]] ++ tr , ' ' + echo ' admin users = noah zogs' + [[ -n noah,zogs ]] ++ tr , ' ' + echo ' write list = noah zogs' + [[ -n Movies_and_Television ]] ++ tr _ ' ' + echo ' comment = Movies and Television' + echo '' + [[ ! -d /samba/torrents ]] DONE + echo DONE + read -r share + '[' -n '' ']' + '[' -n '' ']' + exec catatonit -- smbd -FS --no-process-group --configfile=/etc/samba/smb.conf Invalid option -FS: unknown option Usage: smbd [-?bDiFV] [-?|--help] [--usage] [-b|--build-options] [-p|--port=STRING] [-P|--profiling-level=PROFILE_LEVEL] [-d|--debuglevel=DEBUGLEVEL] [--debug-stdout] [-s|--configfile=CONFIGFILE] [--option=name=value] [-l|--log-basename=LOGFILEBASE] [--leak-report] [--leak-report-full] [-D|--daemon] [-i|--interactive] [-F|--foreground] [--no-process-group] [-V|--version] -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1191677] php8-nginx container broken
by bugzilla_noreply＠suse.com 15 Oct '21

15 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191677 https://bugzilla.suse.com/show_bug.cgi?id=1191677#c1 --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- This must be something strange with our container host. Works fine for me on current MicroOS with odman and php8-nginx container. The file and parent directories are all root:root and readable by everybody. microos:~ # podman run --name nginx --rm --env DEBUG=1 opensuse/php8-nginx + /usr/bin/find /docker-entrypoint.d/ -mindepth 1 -maxdepth 1 -type f -print -quit + read v + echo '/docker-entrypoint.d/ is not empty, will attempt to perform configuration' /docker-entrypoint.d/ is not empty, will attempt to perform configuration + echo 'Looking for shell scripts in /docker-entrypoint.d/' Looking for shell scripts in /docker-entrypoint.d/ + find /docker-entrypoint.d/ -follow -type f -print + read -r f + sort -V + case "$f" in + '[' -x /docker-entrypoint.d/30-populate-etc.sh ']' + echo 'Launching /docker-entrypoint.d/30-populate-etc.sh' Launching /docker-entrypoint.d/30-populate-etc.sh + /docker-entrypoint.d/30-populate-etc.sh + ETC_DIR=/etc/nginx + '[' '!' -f /etc/nginx/nginx.conf ']' + echo 'Populate /etc/nginx' Populate /etc/nginx + cp -a /usr/local/nginx/etc/conf.d /usr/local/nginx/etc/fastcgi.conf /usr/local/nginx/etc/fastcgi_params /usr/local/nginx/etc/koi-utf /usr/local/nginx/etc/koi-win /usr/local/nginx/etc/mime.types /usr/local/nginx/etc/nginx.conf /usr/local/nginx/etc/scgi_params /usr/local/nginx/etc/uwsgi_params /usr/local/nginx/etc/vhosts.d /usr/local/nginx/etc/win-utf /etc/nginx/ + cp -a /usr/local/php/nginx.conf /etc/nginx/ + exit 0 + read -r f + case "$f" in + '[' -x /docker-entrypoint.d/40-populate-htdocs.sh ']' + echo 'Launching /docker-entrypoint.d/40-populate-htdocs.sh' Launching /docker-entrypoint.d/40-populate-htdocs.sh + /docker-entrypoint.d/40-populate-htdocs.sh + HTDOCS_DIR=/srv/www/htdocs ++ ls -A /srv/www/htdocs + '[' '!' '50x.html index.php nginx.html' ']' + exit 0 + read -r f + case "$f" in + '[' -x /docker-entrypoint.d/50-set-timezone.sh ']' + echo 'Launching /docker-entrypoint.d/50-set-timezone.sh' Launching /docker-entrypoint.d/50-set-timezone.sh + /docker-entrypoint.d/50-set-timezone.sh + '[' -n '' ']' + read -r f + case "$f" in + '[' -x /docker-entrypoint.d/90-run-php-fpm.sh ']' + echo 'Launching /docker-entrypoint.d/90-run-php-fpm.sh' Launching /docker-entrypoint.d/90-run-php-fpm.sh + /docker-entrypoint.d/90-run-php-fpm.sh + echo 'Starting php-fpm...' + /usr/sbin/php-fpm Starting php-fpm... + read -r f + echo 'Configuration complete; ready for start up' Configuration complete; ready for start up + [[ / = \- ]] + [[ /usr/sbin/nginx == nginx ]] + [[ /usr/sbin/nginx == /usr/sbin/nginx ]] + EXTRA_ARGS= + set -- + [[ -z '' ]] + echo 'Starting nginx...' Starting nginx... + exec /usr/sbin/nginx -g 'daemon off;' -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1188110] pkcon system-upgrade leads to unbootable system with kernel upgrade
by bugzilla_noreply＠suse.com 15 Oct '21

15 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1188110 https://bugzilla.suse.com/show_bug.cgi?id=1188110#c11 --- Comment #11 from Thorsten Kukuk <kukuk(a)suse.com> --- (In reply to Dario Faggioli from comment #10) > Could it be that it's not update-bootloader itself, but either > grub2-mkconfig or some other wrapper? update-bootloader is only a wrapper around pbl. The kernel calls /usr/lib/bootloader/bootloader_entry, which is also only a wrapper around pbl. Both call the same plugins in the end from perl-Bootloader. To be more precise: both call "pbl --config --install". -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1191678] samba container broken since update to 4.15
by bugzilla_noreply＠suse.com 15 Oct '21

15 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1191678 https://bugzilla.suse.com/show_bug.cgi?id=1191678#c1 Thorsten Kukuk <kukuk(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Thorsten Kukuk <kukuk(a)suse.com> --- They removed the log-stdout option from smbd and it looks like there is no replacement... I removed it from the entrypoint script, too, but this also means there are no messages anymore on stdout (podman logs). No idea how to solve that. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1186127] selinux-ready error
by bugzilla_noreply＠suse.com 14 Oct '21

14 Oct '21

https://bugzilla.suse.com/show_bug.cgi?id=1186127 Gayane Osipyan <gayane.osipyan(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|gayane.osipyan(a)suse.com |kubic-bugs(a)opensuse.org -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1185647] New: GNOME Software not updating RPM packages
by bugzilla_noreply＠suse.com 12 Oct '21

12 Oct '21

http://bugzilla.opensuse.org/show_bug.cgi?id=1185647 Bug ID: 1185647 Summary: GNOME Software not updating RPM packages Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: kubic-bugs(a)opensuse.org Reporter: dfaggioli(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- So, with Snapshot 20210427, pkcon now works for installing packages, e.g., from a terminal (although, it does follow weak dependencies, but that's another issue). However, updating via GNOME Software does not work yet. So, this is the situation right after install: dario@localhost:~> sudo snapper list # | Type | Pre # | Date | User | Used Space | Cleanup | Description | Userdata ---+--------+-------+---------------------------------+------+------------+---------+-----------------------+-------------- 0 | single | | | root | | | current | 1* | single | | Wed 05 May 2021 07:17:32 AM UTC | root | 43.02 MiB | | first root filesystem | 2 | single | | Wed 05 May 2021 07:24:05 AM UTC | root | 36.47 MiB | number | after installation | important=yes In GNOME Software, I see the notification of some updates, I can go to the proper tab, click 'Download' and then click 'Restart & Install'. At which point, on the GUI, I see this error message: "Unable to install updates: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._pk_2dengine_2derror-2dquark.Code1:Failed to create symlink: Read-only file system" If I go ahead, after the reboot, the updates have not been installed. This is the status of system snapshots: dario@localhost:~> sudo snapper list [sudo] password for root: # | Type | Pre # | Date | User | Used Space | Cleanup | Description | Userdata ---+--------+-------+---------------------------------+------+------------+---------+-----------------------+------------------------------------- 0 | single | | | root | | | current | 1* | single | | Wed 05 May 2021 07:17:32 AM UTC | root | 144.00 KiB | | first root filesystem | 2 | single | | Wed 05 May 2021 07:24:05 AM UTC | root | 36.47 MiB | number | after installation | important=yes 3 | single | | Wed 05 May 2021 10:51:00 AM UTC | root | 19.75 MiB | | Snapshot Update of #1 | transactional-update-in-progress=yes 4 | single | | Wed 05 May 2021 10:55:47 AM UTC | root | 19.75 MiB | | Snapshot Update of #1 | transactional-update-in-progress=yes 5 | single | | Wed 05 May 2021 11:06:10 AM UTC | root | 19.75 MiB | | Snapshot Update of #1 | transactional-update-in-progress=yes 6 | single | | Wed 05 May 2021 11:06:48 AM UTC | root | 160.00 KiB | | Snapshot Update of #1 | transactional-update-in-progress=yes In journalctl, I see a bunch of lines like these: May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-.snapshots.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-boot-writable.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-root.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-sys-fs-fuse-connections.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-sys-kernel-config.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-sys-kernel-tracing.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: \x2esnapshots-6-snapshot-sys.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-proc.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-dev.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-kernel-config.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-kernel-tracing.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-kernel-debug.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-fs-selinux.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-fs-bpf.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-fs-pstore.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-fs-cgroup.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-kernel-security.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys-fs-fuse-connections.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy-sys.mount: Succeeded. May 05 11:07:19 localhost.localdomain systemd[1706]: tmp-transactional\x2dupdate\x2djNF9Qy.mount: Succeeded. PackageKit logs does not seem to me to contain anything related to this operation, but I'm happy to provide further info. After a few seconds, `snapper list` is slightly different (probably due to the fact that, right after boot, packagekit was scanning for updates): dario@localhost:~> sudo snapper list # | Type | Pre # | Date | User | Used Space | Cleanup | Description | Userdata ---+--------+-------+---------------------------------+------+------------+---------+-----------------------+------------------------------------- 0 | single | | | root | | | current | 1* | single | | Wed 05 May 2021 07:17:32 AM UTC | root | 19.72 MiB | | first root filesystem | 2 | single | | Wed 05 May 2021 07:24:05 AM UTC | root | 36.47 MiB | number | after installation | important=yes 3 | single | | Wed 05 May 2021 10:51:00 AM UTC | root | 19.75 MiB | | Snapshot Update of #1 | transactional-update-in-progress=yes 4 | single | | Wed 05 May 2021 10:55:47 AM UTC | root | 19.75 MiB | | Snapshot Update of #1 | transactional-update-in-progress=yes 5 | single | | Wed 05 May 2021 11:06:10 AM UTC | root | 19.75 MiB | | Snapshot Update of #1 | transactional-update-in-progress=yes Of course, the expected results would be that packages are actually updated/installed. -- You are receiving this mail because: You are the assignee for the bug.

1 6