Flatpak issues after 42630 update

General Discussion
1

Hello, I have the next output for every app. installed using flatpak, when I try to update them:

$ flatpak update
Looking for updates…
F: Warning: Treating remote fetch error as non-fatal since runtime/org.gtk.Gtk3theme.Breeze/x86_64/3.22 is already installed: No such ref ‘runtime/org
.gtk.Gtk3theme.Breeze/x86_64/3.22’ in remote flathub
F: Warning: Treating remote fetch error as non-fatal since runtime/org.freedesktop.Sdk/x86_64/24.08 is already installed: No such ref ‘runtime/org.fre
edesktop.Sdk/x86_64/24.08’ in remote flathub
F: Warning: Treating remote fetch error as non-fatal since runtime/org.freedesktop.Sdk/x86_64/23.08 is already installed: No such ref ‘runtime/org.fre
edesktop.Sdk/x86_64/23.08’ in remote flathub
[…]

Useful commands for debugging:

$ flatpak remote-list
Name Options
flathub user

$ flatpak list
Name Application ID Version Branch Installation
Portal for Teams com.github.IsmaelMartinez.teams_for_linux 1.11.2 stable user
Microsoft Edge com.microsoft.Edge 130.0.2849.80-1 stable user
VSCodium com.vscodium.codium 1.95.2.24313 stable user
Freedesktop Platform org.freedesktop.Platform freedesktop-sdk-23.08.25 23.08 user
Freedesktop Platform org.freedesktop.Platform freedesktop-sdk-24.08.6 24.08 user
Mesa org.freedesktop.Platform.GL.default 24.2.5 23.08 user
Mesa (Extra) org.freedesktop.Platform.GL.default 24.2.5 23.08-extra user
Mesa org.freedesktop.Platform.GL.default 24.2.6 24.08 user
Mesa (Extra) org.freedesktop.Platform.GL.default 24.2.6 24.08extra user
Intel VAAPI driver org.freedesktop.Platform.VAAPI.Intel 23.08 user
Intel VAAPI driver org.freedesktop.Platform.VAAPI.Intel 24.08 user
openh264 org.freedesktop.Platform.openh264 2.1.0 2.2.0 user
openh264 org.freedesktop.Platform.openh264 2.4.1 2.4.1 user
Freedesktop SDK org.freedesktop.Sdk freedesktop-sdk-23.08.25 23.08 user
Freedesktop SDK org.freedesktop.Sdk freedesktop-sdk-24.08.6 24.08 user
Breeze GTK theme org.gtk.Gtk3theme.Breeze 6.2.3 3.22 user
Xonotic org.xonotic.Xonotic 0.8.6 stable user

I tried this command, but, I get the next output:

$ flatpak remote-add --authenticator-install flathub https://flathub.org/repo/flathub.flatpakrepo
error: Can’t load uri https://flathub.org/repo/flathub.flatpakrepo: Key file contains line “�������W���r��W���õ4
r��
r�{���f�d?�,y�D��sDwWU��0��7��t���xF▒8d�����O|3fj�/�4��B�{�M8�B`l�l���i��}K:��w��n�r�9W�����;�y�������k��߿_�?ir�����s=�c=�?DKT���і
��Vn����l���ʨY��fB*��������4w�” which is not a key-value pair, group, or comment

$ flatpak remote-add --user flathub https://flathub.org/repo/flathub.flatpakrepo
error: Can’t load uri https://flathub.org/repo/flathub.flatpakrepo: Key file contains line “�������W���r��W���õ4
r��
r�{���f�d?�,y�D��sDwWU��0��7��t���xF▒8d�����O|3fj�/�4��B�{�M8�B`l�l���i��}K:��w��n�r�9W�����;�y�������k��߿_�?ir�����s=�c=�?DKT���і
��Vn����l���ʨY��fB*��������4w�” which is not a key-value pair, group, or comment

The repair option of flatpak was already tried without luck.

I have another CL installed on a KVM, and the update to 42630 and 42660 starts with the same issue.

I would like to know, if there are another solution, or workaround, without loosing the apps installed, and their configurations.

Thanks in advance.

1 Like
2

Having the same issue, the only way to make it work would be to go back to 42590 version.
There’s may be an issue with curl causing flatpak not to work.

1 Like
3

I’m facing the same issue and it really seems to be linked to curl.
It had been reported, → 8.11.0 seems to break flatpak update · Issue #15509 · curl/curl · GitHub
and solved. → Fixing HTTP content decoding enabled (broken in commit 30da1f5) by jmalopoy · Pull Request #15510 · curl/curl · GitHub

I would like to find a solution, but I guess we’ll have to wait for curl to make a release.

edit :
I’ve fixed the second link

1 Like
4

Same boat. Looks like we need to wait.

5

Ah thanks for finding that one, I’ve applied the patch to our curl.

2 Likes
6

Hrm so applying the patch I see some test failures. Might just have to wait for a new upstream release.

1 Like
7

I’ve solved the issue on my install. It’s probably not the cleanest solution, but it works for now.
For those who don’t want to wait, you can do the following:

# Install the dependencies for compiling curl:
sudo swupd bundle-add devpkg-openssl

# Clone the curl git repo:
git clone https://github.com/curl/curl.git

# The usual cd curl:
cd curl

# CMake, do your magic (make the Makefile and such):
cmake .

# Let's compile:
make

# ***Just some precautions to avoid nuking your install:***  
mkdir -p $HOME/oldlib
sudo cp /usr/lib64/libcurl.so.* $HOME/oldlib/

# Last step but the one we need:
sudo cp lib/libcurl.so.* /usr/lib64/

With this, it works like a charm on my installation.

Edit: Fixed a few details.

Edit 2: Added some precautions. (I don’t want to be blamed if you destroy your install)

5 Likes
8

Finally got around to trying your fix. I wanted to backup some important files before giving it a shot.

Everything went through without error. The auto updater is now working again. Currently waiting for 24 updates to finish. Then I will reboot to see if I can log back in without issues.

John

1 Like
9

Thanks @Pacidus, your workaround works perfectly!

1 Like
10

You’re welcome and thanks for the update. :+1:

11

thx!!!
its work for me

1 Like