There are some reports about curl and ostree having issues with flatpak. So I updated ostree once more with a patch for supporting latest curl … I need a list of non-working flatpaks to check also on my end …
No, not at all. more like: All my network adapters disappears and wont come back until I reboot the system.
Even lo
Since the update, I have a weird bug: the Alt key is sometimes logically stuck (maybe linked to a new shortcut introduced by KDE 6.6?). So each time I press a key, it opens the File menu, triggers a shortcut, etc…
A reboot solves temporary the issue.
Any clue?
Update announcement has a link to the online mirror check below the poll
you can also check status of system mirrors with pacman-mirrors
The Global mirrors are usually more up to date, but can be slower than local mirrors if everyone is using them to get updates
1 Like
On my system, following flatpak apps are not working
- Telegram
- LibreWolf
- All Electron applications
- Zotero
What are the electron apps @amnol ?
More precisely, I would say chromium based browsers: Vivaldi, Brave.
For me these flatpaks fail to start:
SyncThingy com.github.zocker_160.SyncThingy
Zen io.github.zen_browser.zen
KPatience org.kde.kpat
EDIT to add:
As far as I can tell Steam client and Electron both use libcef, the ‘Chromium Embeded Framework’, still looking at other failing apps to see if they use it – for the failing browsers that seems likely – that would maybe tie a lot of these problems together.
(There were libcef errors in the first log snippet I posted in the steam specific thread, just before the libc errors.)
EDIT 2: Zen browser is Firefox based, not Chromium and neither of my other failing flatpaks seem to use libcef.
1 Like
Telegram still not working. Flatpak package name: org.telegram.desktop
mesa version: 1:24.2.4-0.1
ostree version: 2024.8-0
I noticed that after launching with the command flatpak run org.telegram.desktop, the process starts, hangs for a while, loading one logical core of the processor to 100%, then crashes with a segfault.
$ ps -C telegram-desktop --format pid,cmd,pcpu,vsize
PID CMD %CPU VSZ
5428 telegram-desktop 99.7 430752
From journalctl output:
oct 10 14:41:06 desktop systemd[1103]: Started app-flatpak-org.telegram.desktop-5415.scope.
oct 10 14:43:31 desktop kernel: telegram-deskto[5428]: segfault at 7ffccf74aff8 ip 000078e5ff2662f3 sp 00007ffccf74b000 error 6 in libc.so.6[582f3,78e5ff234000+166000] likely on CPU 4 (core 4, socket 1)
1 Like
A couple of minutes ago I saw a message with Mesa upgrades from version 1:24.2.4-0 to 1:24.2.4-1 and also Vulkan - I had upgraded the system prior to the notification and now I am confused - hold or upgrade? I haven’t noticed any strange behaviour today…
I have Brave (flatpak) installed.
Brave works normally on x11 but does not launch on wayland.
No recent mesa updates installed.
2 Likes
I confirm that they work on X11
1 Like
I have it also from the official repos.
Using KDE with wayland and the “Ozone” flag inside Vivaldi (vivaldi://flags) set to “Auto”
Сonfirm. On X11 the problem does not appear - telegram starts normally. On Wayland - does not work.
Maybe the problem only appears under Wayland? People, please write back, what kind of graphic server do you have, and whether the problem with launching flatpak applications appears on it.
1 Like
Vivaldi crash on X11 for me.
console
[3914:3914:1010/175003.837218:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not implemented
[3914:3914:1010/175004.041083:ERROR:CONSOLE(242)] "<webview>: Script cannot be injected into content until the page has loaded.", source: extensions::webView (242)
[3914:3940:1010/175005.679003:ERROR:registration_request.cc(291)] Registration response error message: DEPRECATED_ENDPOINT
fish: Job 1, 'vivaldi' terminated by signal SIGSEGV (Address boundary error)
log
Stack trace of thread 3943:
#0 0x00007f481361463d __poll (libc.so.6 + 0x10b63d)
#1 0x00007f4814170e0d n/a (libglib-2.0.so.0 + 0xbfe0d)
#2 0x00007f481410d795 g_main_context_iteration (libglib-2.0.so.0 + 0x5c795)
#3 0x00007f481410d7f2 n/a (libglib-2.0.so.0 + 0x5c7f2)
#4 0x00007f481413e1b6 n/a (libglib-2.0.so.0 + 0x8d1b6)
#5 0x00007f481359d39d n/a (libc.so.6 + 0x9439d)
#6 0x00007f481362249c n/a (libc.so.6 + 0x11949c)
ELF object binary architecture: AMD x86-64
Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text
After the update I couldn’t get past the login screen. Using KDE Plasma. Reverted the update using timeshift for now, will maybe try it later again.
EDIT: Similar to [Stable Update] 2024-10-10 - Kernels, Pacman 7.0, KDE Frameworks 6.6, Virtualbox 7.1.2, Mesa - #31 by Rathori but I haven’t check the journal before restoring.
EDIT2: In my case running journalctl -b -1 -p3 shows errors related to libvirt unable to access paths of storage pools I used but deleted since then. This can’t be right.
The brave-bin from AUR still works with wayland without issues.
mattermost-desktop won’t even start with xwayland.
All browsers from flaptak (chrome, edge, firefox) still won’t start on wayland.
Flatpak Chrome creates this log:
18:14:03 systemd: app-flatpak-com.google.Chrome-103987.scope: Consumed 32.401s CPU time, 19.8M memory peak.
18:14:03 systemd-coredum: Process 104017 (cobalt) of user 1000 dumped core.
Stack trace of thread 2:
#0 0x00007dc78b873404 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x60404)
#1 0x00007dc78b896436 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x83436)
#2 0x00007dc78b9392dc n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x1262dc)
#3 0x00007dc78aefe87b n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x387b)
#4 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#5 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#6 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#7 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#8 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#9 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#10 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#11 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#12 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#13 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#14 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#15 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#16 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#17 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#18 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#19 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#20 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#21 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#22 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#23 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#24 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#25 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#26 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#27 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#28 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#29 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#30 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#31 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#32 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#33 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#34 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#35 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#36 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#37 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#38 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#39 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#40 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#41 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#42 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#43 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#44 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#45 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#46 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#47 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#48 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#49 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#50 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#51 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#52 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#53 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#54 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#55 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#56 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#57 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#58 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#59 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#60 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#61 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#62 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
#63 0x00007dc78aefe7c9 n/a (/usr/lib/x86_64-linux-gnu/libwayland-cursor.so.0.22.0 + 0x37c9)
Stack trace of thread 7:
#0 0x00007dc78b9279cd n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x1149cd)
#1 0x00007dc78c5c208b n/a (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7600.6 + 0x2b08b)
#2 0x00007dc78c62c573 n/a (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7600.6 + 0x95573)
#3 0x00007dc78c62a862 n/a (/usr/lib/x86_64-linux-gnu/libglib-2.0.so.0.7600.6 + 0x93862)
#4 0x00007dc78b8a1ea9 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x8eea9)
#5 0x00007dc78b929a44 n/a (/usr/lib/x86_64-linux-gnu/libc.so.6 + 0x116a44)
ELF object binary architecture: AMD x86-64
18:14:03 systemd: Started Process Core Dump (PID 104173/UID 0).
18:14:03 systemd-coredum: Process 104017 (cobalt) of user 1000 terminated abnormally with signal 11/SEGV, processing...
18:14:03 kernel: Code: 60 0c 00 0f 1f 00 f3 0f 1e fa 55 48 89 e5 41 57 49 89 d7 41 56 49 89 f6 41 55 49 89 fd 4c 89 f7 41 54 53 48 81 ec e8 04 00 00 <48> 89 b5 08 fb ff ff be 25 00 00 00 89 8d 28 fb ff ff 64 48 8b 04
18:14:03 kernel: cobalt[104017]: segfault at 7ffd14ff6fe8 ip 00007dc78b873404 sp 00007ffd14ff6fd0 error 6 in libc.so.6[60404,7dc78b839000+166000] likely on CPU 3 (core 4, socket 0)
1
I tried all browsers in x11 and everything works.
Updated everything, Flatpak applications worked fine (Telegram, Viber, Zoom, flatseal, Okular)
CPU temps are high after the update in 70-80 range.
Still on 6.10 kernel, the new update to the mesa drivers is up, so I’ll try upgrading and moving to kernel 6.11 and reporting back.
The whole idea of flatpak is to be independent of system changes. 
1 Like
So far I was able to run those non-working flatpaks and chrome-based browsers in a VM using X11 and GNOME. Also some people already pointed out that the issue might be with wayland and some flags, especially OZONE flags they set for electron apps: Wayland - ArchWiki
Then others claim that with similar settings on Arch steam works. The testing branch is ready and similar to Arch stable. You can try to switch to that. For now I still don’t get what might cause that issue. There were several electron updates also included within this update-set.
In addition to the Steam bug in Steam games won't launch after 2024-10-10 stable update - #38 by scheuri, I’m seeing intermittent Tailscale connectivity as of this update, which I’m hoping is the bug referred to in Changelog · Tailscale (though they don’t link to a description, annoyingly).