Flatpak applications unable to be installed or updated on Main

[parkerlreed [Linux represent]]

0424 Main

Flatpak applications installed to the system instance are unable to be updated by the user with an error stating

Warning: Could not unmount revokefs-fuse filesystem at /var/tmp/flatpak-cache-JLUYS1/org.freedesktop.Platform.GL.default-G58MS1: Child
process exited with code 1

This applies to any updates to system instance applications and new application installs from Discover

Have attempted to downgrade to beta or stable to confirm operation but both of those are failing when coming from Main (EDIT: The downgrade itself is failing just sitting on the steam deck boot logo)

[parkerlreed [Linux represent]]

Adding verbose to the update command shows its failing on fusermount unmount not having permissions for the mounted folder

fusermount3: failed to unmount /var/tmp/flatpak-cache-P7TR31/org.freedesktop.LinuxAudio.Plugins.TAP-YFZZ31: Operation not permitted

Although it I unmount manually it works fine?...

(deck@steamdeck ~)$ ls -lah /var/tmp/flatpak-cache-P7TR31/org.freedesktop.LinuxAudio.Plugins.TAP-YFZZ31
total 12K
drwxr-xr-x 3 deck flatpak 4.0K Apr 26 15:14 .
drwxr-xr-x 5 deck deck    4.0K Apr 26 16:46 ..
drwxr-xr-x 7 deck flatpak 4.0K Apr 26 16:46 repo-ZSUUgO
-rw------- 1 deck flatpak    0 Apr 26 15:14 repo-ZSUUgO-lock
(deck@steamdeck ~)$ umount /var/tmp/flatpak-cache-P7TR31/org.freedesktop.LinuxAudio.Plugins.TAP-YFZZ31
(deck@steamdeck ~)$

[parkerlreed [Linux represent]]

 fusermount -u path 

works equally as well after Flatpak exits but not during execution it seems.

[parkerlreed [Linux represent]]

Finally got Beta downgrade to work and Flatpaak works as expected. Compared updates and flatpak got updated from 1.12 to 1.14, likely causing some issues.

(deck@steamdeck ~)$ diff beta-3.4.7.txt main-3.5.txt 
7c7
< alsa-card-profiles 1:0.3.59-2.2
---
> alsa-card-profiles 1:0.3.62.2.dv-1
17d16
< appstream-glib 0.8.1-1
41,43c40,42
< bluez 5.63-1.8
< bluez-libs 5.63-1.8
< bluez-plugins 5.63-1.8
---
> bluez 5.66-1.1
> bluez-libs 5.66-1.1
> bluez-plugins 5.66-1.1
45c44
< bluez-utils 5.63-1.8
---
> bluez-utils 5.66-1.1
73c72
< cpupower 5.13-1
---
> cpupower 6.0-1
85a85
> ding-libs 0.6.2-1
119a120
> firewalld 1.2.1-1
123c124
< flatpak 1.12.4-1.1
---
> flatpak 1.14.4-2
136c137
< gamescope 3.11.48.1-1.1
---
> gamescope 3.11.52.beta6-5
157d157
< glslang 11.11.0-1
166c166
< gpu-trace 2.8-1
---
> gpu-trace 2.10-1
171c171
< grub 2:2.06-4.5
---
> grub 2:2.06-4.6
173a174
> gssproxy 0.9.1-2
186c187
< holo-desync r667.d02b4b6-2
---
> holo-desync r733.2ba71c7-1
188,190c189,191
< holo-pipewire r667.d02b4b6-2
< holo-sudo r667.d02b4b6-2
< holo-wireplumber r667.d02b4b6-2
---
> holo-pipewire r733.2ba71c7-1
> holo-sudo r733.2ba71c7-1
> holo-wireplumber r733.2ba71c7-1
217,220c218,222
< jupiter-dock-updater-bin 20221026.01-1
< jupiter-fan-control 20221107.1-1
< jupiter-hw-support 3.4.20221221.1-1
< jupiter-legacy-support 1.135-1
---
> jupiter-dock-updater-bin 20230126.01-1
> jupiter-fan-control 20230209.1-1
> jupiter-firewall 0.1-1
> jupiter-hw-support 20230424.1-2
> jupiter-legacy-support 1.139-1
253c255
< kdump-steamos 0.9-2
---
> kdump-steamos 0.92-2
329a332
> lib32-gamescope 3.11.52.beta2-1
362c365
< lib32-libva-mesa-driver 22.2.0.157821.radeonsi_3.4.0_2-2
---
> lib32-libva-mesa-driver 22.2.0.157821.radeonsi_3.4.0_2-1
368a372
> lib32-libxcrypt-compat 4.4.28-2
382,384c386,388
< lib32-mangohud 0.6.8.r17.gebb0f96-2
< lib32-mesa 22.2.0.157821.radeonsi_3.4.0_2-2
< lib32-mesa-vdpau 22.2.0.157821.radeonsi_3.4.0_2-2
---
> lib32-mangohud 0.6.9.1.r16.g1093de8-1
> lib32-mesa 22.2.0.157821.radeonsi_3.4.0_2-1
> lib32-mesa-vdpau 22.2.0.157821.radeonsi_3.4.0_2-1
400c404
< lib32-vulkan-radeon 23.1.0_devel.166656.steamos_3.5.2-1
---
> lib32-vulkan-radeon 23.1.0_devel.166652.steamos_3.5.1-1
469a474
> libmalcontent 0.10.5-1
542c547
< libva-mesa-driver 22.2.0.157821.radeonsi_3.4.0_2-2
---
> libva-mesa-driver 22.2.0.157821.radeonsi_3.4.0_2-1
555a561
> libxcrypt-compat 4.4.28-2
588,589c594,595
< linux-firmware-neptune 20220624.650ab31-1
< linux-neptune 5.13.0.valve36-1
---
> linux-firmware-neptune jupiter.20230420-1
> linux-neptune-61 6.1.21.valve1-1
605c611
< mangohud 0.6.8.r17.gebb0f96-2
---
> mangohud 0.6.9.1.r16.g1093de8-1
609c615
< mesa 22.2.0.157821.radeonsi_3.4.0_2-2
---
> mesa 22.2.0.157821.radeonsi_3.4.0_2-1
611c617
< mesa-vdpau 22.2.0.157821.radeonsi_3.4.0_2-2
---
> mesa-vdpau 22.2.0.157821.radeonsi_3.4.0_2-1
625a632
> networkmanager-openvpn 1.10.0-1
626a634,636
> nfs-utils 2.6.2-1
> nfsidmap 2.6.2-1
> nftables 1:1.0.5-1
641c651
< opencl-mesa 22.2.0.157821.radeonsi_3.4.0_2-2
---
> opencl-mesa 22.2.0.157821.radeonsi_3.4.0_2-1
676,680c686,690
< pipewire 1:0.3.59-2.2
< pipewire-alsa 1:0.3.59-2.2
< pipewire-audio 1:0.3.59-2.2
< pipewire-jack 1:0.3.59-2.2
< pipewire-pulse 1:0.3.59-2.2
---
> pipewire 1:0.3.62.2.dv-1
> pipewire-alsa 1:0.3.62.2.dv-1
> pipewire-audio 1:0.3.62.2.dv-1
> pipewire-jack 1:0.3.62.2.dv-1
> pipewire-pulse 1:0.3.62.2.dv-1
692a703
> plasma-remotecontrollers 5.27.4-1.1
700c711
< plymouth 22.02.122-1.3
---
> plymouth 22.02.122-1.4
772a784
> rpcbind 1.2.6-2
809,810c821,823
< steam-jupiter-stable 1.0.0.75-1.4
< steamdeck-kde-presets 0.16-1
---
> steam-jupiter-stable 1.0.0.76-1
> steam_notif_daemon v1.0.1-1
> steamdeck-kde-presets 0.17-1
812c825
< steamos-customizations-jupiter 20220713.1-1
---
> steamos-customizations-jupiter 20220727.1-2
814a828
> steamos-tweak-mtu-probing 1-1
845c859
< udisks2 2.9.4-1
---
> udisks2 2.9.4-1.1
849c863
< usbhid-gadget-passthru 0.1.0-1
---
> usbhid-gadget-passthru 0.1.1-1
863c877
< vulkan-radeon 23.1.0_devel.166656.steamos_3.5.2-1
---
> vulkan-radeon 23.1.0_devel.166652.steamos_3.5.1-1
869a884
> wireguard-tools 1.0.20210914-1
872c887
< wireplumber 0.4.12.4.dv-1
---
> wireplumber 0.4.13.5.dv-1
887c902
< xdg-desktop-portal 1.12.1-1.1
---
> xdg-desktop-portal 1.15.0-1

[perti boi]

Can confirm am having same issue on main.

[Bee🐝]

If a simple total reboot doesn't sort it.

Try running: "systemctl restart flatpak-system-helper.service" in the terminal without the "".

If that doesn't work: "flatpak --user repair"

There's been success with both commands but usually a total reboot shakes something loose.

[KoTiiK]

Interesting that installing and updating flatpaks are working for me, but installed apps are not visible in "add non steam game" list window. Any ideas how to make it visible again?

[parkerlreed [Linux represent]]

Originally posted by Bee🐝:

If a simple total reboot doesn't sort it.

Try running: "systemctl restart flatpak-system-helper.service" in the terminal without the "".

If that doesn't work: "flatpak --user repair"

There's been success with both commands but usually a total reboot shakes something loose.

This has definitely been persisting across reboots. Lost count at this point!

Restarted the service and verified it's running. Still seeing the same issues on the HDR Main update.

(deck@steamdeck ~)$ systemctl status flatpak-system-helper.service
● flatpak-system-helper.service - flatpak system helper
     Loaded: loaded (/usr/lib/systemd/system/flatpak-system-helper.service; static)
     Active: active (running) since Fri 2023-04-28 15:15:34 EDT; 42s ago
   Main PID: 25114 (flatpak-system-)
      Tasks: 3 (limit: 17681)
     Memory: 2.0M
        CPU: 34ms
     CGroup: /system.slice/flatpak-system-helper.service
             └─25114 /usr/lib/flatpak-system-helper

Apr 28 15:15:34 steamdeck systemd[1]: Starting flatpak system helper...
Apr 28 15:15:34 steamdeck systemd[1]: Started flatpak system helper.
(deck@steamdeck ~)$ flatpak update
Looking for updates…

Info: (pinned) runtime org.gnome.Sdk branch 3.36 is end-of-life, with reason:
   The GNOME 3.36 runtime is no longer supported as of February 13, 2021. Please ask your application developer to migrate to a supported platform.

Info: runtime org.gnome.Platform branch 42 is end-of-life, with reason:
   The GNOME 42 runtime is no longer supported as of March 21, 2023. Please ask your application developer to migrate to a supported platform.
Info: applications using this runtime:
   org.inkscape.Inkscape

Info: (pinned) runtime org.gnome.Platform.Compat.i386 branch 42 is end-of-life, with reason:
   The GNOME 42 runtime is no longer supported as of March 21, 2023. Please ask your application developer to migrate to a supported platform.

Info: runtime org.freedesktop.Platform.GL.default branch 19.08 is end-of-life, with reason:
   The Freedesktop SDK 19.08 runtime is no longer supported as of September 1, 2021. Please ask your application developer to migrate to a supported version


        ID                           Branch          Op         Remote          Download
 1. [—] org.ryujinx.Ryujinx          stable          u          flathub            1.0 kB / 20.6 MB
        ID                           Branch          Op         Remote          Download
        ID                           Branch          Op         Remote          Download
 1. [—] org.ryujinx.Ryujinx          stable          u          flathub            1.0 kB / 20.6 MB
 2. [ ] org.yuzu_emu.yuzu            stable          u          flathub         < 19.9 MB

Warning: Could not unmount revokefs-fuse filesystem at /var/tmp/flatpak-cache-PH1231/org.ryujinx.Ryujinx-DDU031: Child process exited with code 1
Warning: Could not unmount revokefs-fuse filesystem at /var/tmp/flatpak-cache-PH1231/org.ryujinx.Ryujinx-DDU031: Child process exited with code 1

(flatpak update:25186): GLib-CRITICAL **: 15:16:25.744: g_propagate_error: assertion 'src != NULL' failed

(flatpak update:25186): GLib-CRITICAL **: 15:16:25.744: g_error_copy: assertion 'error != NULL' failed

(flatpak update:25186): GLib-CRITICAL **: 15:16:25.744: g_propagate_error: assertion 'src != NULL' failed
**
GLib:ERROR:../glib/glib/gerror.c:1154:g_propagate_prefixed_error: assertion failed: (*dest != NULL)
Bail out! GLib:ERROR:../glib/glib/gerror.c:1154:g_propagate_prefixed_error: assertion failed: (*dest != NULL)
Aborted (core dumped)

[parkerlreed [Linux represent]]

--user has been and works fine. It's only the --system installed applications facing this issue (Which includes installs from Discover)

[fanmoefoe]

This *might* not be the cause for everyone, but it's a good idea to check if your deck is using the correct `fusermount` and `fusermount3` binary. To check, run in the Konsole app on Desktop mode:

```
which fusermount
```
> This should return `/usr/bin/fusermount`

and

```
which fusermount3
```
> This should return `/usr/bin/fusermount3`

This is especially true if you so happen to have installed `podman` or `distrobox`, which also means you may have added `$HOME/.local/podman/bin` or `~/.local/podman/bin` to your Shell's path, which may also mean you may have gotten `/home/deck/.local/podman/bin/fusermount3` when you ran `which fusermount3`.

If that is the case, simply ensure `/usr/bin` is higher in priority over `$HOME/.local/podman/bin` or `~/.local/podman/bin` in your $PATH, then reload your Shell config or restart the Konsole app and try running `flatpak update` again. That should fix it.

[inFantry-32]

Originally posted by parkerlreed Linux represent:

Finally got Beta downgrade to work and Flatpaak works as expected. Compared updates and flatpak got updated from 1.12 to 1.14, likely causing some issues.

(deck@steamdeck ~)$ diff beta-3.4.7.txt main-3.5.txt 
7c7
< alsa-card-profiles 1:0.3.59-2.2
---
> alsa-card-profiles 1:0.3.62.2.dv-1
17d16
< appstream-glib 0.8.1-1
41,43c40,42
< bluez 5.63-1.8
< bluez-libs 5.63-1.8
< bluez-plugins 5.63-1.8
---
> bluez 5.66-1.1
> bluez-libs 5.66-1.1
> bluez-plugins 5.66-1.1
45c44
< bluez-utils 5.63-1.8
---
> bluez-utils 5.66-1.1
73c72
< cpupower 5.13-1
---
> cpupower 6.0-1
85a85
> ding-libs 0.6.2-1
119a120
> firewalld 1.2.1-1
123c124
< flatpak 1.12.4-1.1
---
> flatpak 1.14.4-2
136c137
< gamescope 3.11.48.1-1.1
---
> gamescope 3.11.52.beta6-5
157d157
< glslang 11.11.0-1
166c166
< gpu-trace 2.8-1
---
> gpu-trace 2.10-1
171c171
< grub 2:2.06-4.5
---
> grub 2:2.06-4.6
173a174
> gssproxy 0.9.1-2
186c187
< holo-desync r667.d02b4b6-2
---
> holo-desync r733.2ba71c7-1
188,190c189,191
< holo-pipewire r667.d02b4b6-2
< holo-sudo r667.d02b4b6-2
< holo-wireplumber r667.d02b4b6-2
---
> holo-pipewire r733.2ba71c7-1
> holo-sudo r733.2ba71c7-1
> holo-wireplumber r733.2ba71c7-1
217,220c218,222
< jupiter-dock-updater-bin 20221026.01-1
< jupiter-fan-control 20221107.1-1
< jupiter-hw-support 3.4.20221221.1-1
< jupiter-legacy-support 1.135-1
---
> jupiter-dock-updater-bin 20230126.01-1
> jupiter-fan-control 20230209.1-1
> jupiter-firewall 0.1-1
> jupiter-hw-support 20230424.1-2
> jupiter-legacy-support 1.139-1
253c255
< kdump-steamos 0.9-2
---
> kdump-steamos 0.92-2
329a332
> lib32-gamescope 3.11.52.beta2-1
362c365
< lib32-libva-mesa-driver 22.2.0.157821.radeonsi_3.4.0_2-2
---
> lib32-libva-mesa-driver 22.2.0.157821.radeonsi_3.4.0_2-1
368a372
> lib32-libxcrypt-compat 4.4.28-2
382,384c386,388
< lib32-mangohud 0.6.8.r17.gebb0f96-2
< lib32-mesa 22.2.0.157821.radeonsi_3.4.0_2-2
< lib32-mesa-vdpau 22.2.0.157821.radeonsi_3.4.0_2-2
---
> lib32-mangohud 0.6.9.1.r16.g1093de8-1
> lib32-mesa 22.2.0.157821.radeonsi_3.4.0_2-1
> lib32-mesa-vdpau 22.2.0.157821.radeonsi_3.4.0_2-1
400c404
< lib32-vulkan-radeon 23.1.0_devel.166656.steamos_3.5.2-1
---
> lib32-vulkan-radeon 23.1.0_devel.166652.steamos_3.5.1-1
469a474
> libmalcontent 0.10.5-1
542c547
< libva-mesa-driver 22.2.0.157821.radeonsi_3.4.0_2-2
---
> libva-mesa-driver 22.2.0.157821.radeonsi_3.4.0_2-1
555a561
> libxcrypt-compat 4.4.28-2
588,589c594,595
< linux-firmware-neptune 20220624.650ab31-1
< linux-neptune 5.13.0.valve36-1
---
> linux-firmware-neptune jupiter.20230420-1
> linux-neptune-61 6.1.21.valve1-1
605c611
< mangohud 0.6.8.r17.gebb0f96-2
---
> mangohud 0.6.9.1.r16.g1093de8-1
609c615
< mesa 22.2.0.157821.radeonsi_3.4.0_2-2
---
> mesa 22.2.0.157821.radeonsi_3.4.0_2-1
611c617
< mesa-vdpau 22.2.0.157821.radeonsi_3.4.0_2-2
---
> mesa-vdpau 22.2.0.157821.radeonsi_3.4.0_2-1
625a632
> networkmanager-openvpn 1.10.0-1
626a634,636
> nfs-utils 2.6.2-1
> nfsidmap 2.6.2-1
> nftables 1:1.0.5-1
641c651
< opencl-mesa 22.2.0.157821.radeonsi_3.4.0_2-2
---
> opencl-mesa 22.2.0.157821.radeonsi_3.4.0_2-1
676,680c686,690
< pipewire 1:0.3.59-2.2
< pipewire-alsa 1:0.3.59-2.2
< pipewire-audio 1:0.3.59-2.2
< pipewire-jack 1:0.3.59-2.2
< pipewire-pulse 1:0.3.59-2.2
---
> pipewire 1:0.3.62.2.dv-1
> pipewire-alsa 1:0.3.62.2.dv-1
> pipewire-audio 1:0.3.62.2.dv-1
> pipewire-jack 1:0.3.62.2.dv-1
> pipewire-pulse 1:0.3.62.2.dv-1
692a703
> plasma-remotecontrollers 5.27.4-1.1
700c711
< plymouth 22.02.122-1.3
---
> plymouth 22.02.122-1.4
772a784
> rpcbind 1.2.6-2
809,810c821,823
< steam-jupiter-stable 1.0.0.75-1.4
< steamdeck-kde-presets 0.16-1
---
> steam-jupiter-stable 1.0.0.76-1
> steam_notif_daemon v1.0.1-1
> steamdeck-kde-presets 0.17-1
812c825
< steamos-customizations-jupiter 20220713.1-1
---
> steamos-customizations-jupiter 20220727.1-2
814a828
> steamos-tweak-mtu-probing 1-1
845c859
< udisks2 2.9.4-1
---
> udisks2 2.9.4-1.1
849c863
< usbhid-gadget-passthru 0.1.0-1
---
> usbhid-gadget-passthru 0.1.1-1
863c877
< vulkan-radeon 23.1.0_devel.166656.steamos_3.5.2-1
---
> vulkan-radeon 23.1.0_devel.166652.steamos_3.5.1-1
869a884
> wireguard-tools 1.0.20210914-1
872c887
< wireplumber 0.4.12.4.dv-1
---
> wireplumber 0.4.13.5.dv-1
887c902
< xdg-desktop-portal 1.12.1-1.1
---
> xdg-desktop-portal 1.15.0-1

You should report this on Github if you really want it fixed tbh, this will be lost in an endless list of posts lacking in as much detaIl as you've provided.

[parkerlreed [Linux represent]]

Originally posted by fanmoefoe:

This *might* not be the cause for everyone, but it's a good idea to check if your deck is using the correct `fusermount` and `fusermount3` binary. To check, run in the Konsole app on Desktop mode:

```
which fusermount
```
> This should return `/usr/bin/fusermount`

and

```
which fusermount3
```
> This should return `/usr/bin/fusermount3`

This is especially true if you so happen to have installed `podman` or `distrobox`, which also means you may have added `$HOME/.local/podman/bin` or `~/.local/podman/bin` to your Shell's path, which may also mean you may have gotten `/home/deck/.local/podman/bin/fusermount3` when you ran `which fusermount3`.

If that is the case, simply ensure `/usr/bin` is higher in priority over `$HOME/.local/podman/bin` or `~/.local/podman/bin` in your $PATH, then reload your Shell config or restart the Konsole app and try running `flatpak update` again. That should fix it.

Holy crap that was it! Thank you!

[Eliot]

Originally posted by fanmoefoe:

If that is the case, simply ensure `/usr/bin` is higher in priority over `$HOME/.local/podman/bin` or `~/.local/podman/bin` in your $PATH, then reload your Shell config or restart the Konsole app and try running `flatpak update` again. That should fix it.

THANK you, I am a Distrobox user and this was the exact issue I was having, your fix worked like a charm.

[Senpai_chuck]

Originally posted by fanmoefoe:

This *might* not be the cause for everyone, but it's a good idea to check if your deck is using the correct `fusermount` and `fusermount3` binary. To check, run in the Konsole app on Desktop mode:

```
which fusermount
```
> This should return `/usr/bin/fusermount`

and

```
which fusermount3
```
> This should return `/usr/bin/fusermount3`

This is especially true if you so happen to have installed `podman` or `distrobox`, which also means you may have added `$HOME/.local/podman/bin` or `~/.local/podman/bin` to your Shell's path, which may also mean you may have gotten `/home/deck/.local/podman/bin/fusermount3` when you ran `which fusermount3`.

If that is the case, simply ensure `/usr/bin` is higher in priority over `$HOME/.local/podman/bin` or `~/.local/podman/bin` in your $PATH, then reload your Shell config or restart the Konsole app and try running `flatpak update` again. That should fix it.

Hey so I’m running into this issue, but I’m not quite sure what commands I’m supposed to put into the konsole. Literally opened my steam deck and I can’t download any apps on it on desktop mode.