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@opensuse.org
Reporter dfaggioli@suse.com
QA Contact qa-bugs@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: