Additionally, have you tried running a flatpak from the command line to see any error output? That would help us pinpoint what broke. After a driver update, I needed to update libraries Flatpak needed for example.
flatpak run com.super_productivity.SuperProductivity
[3:0129/073050.987010:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Start app...
07:30:51.137 › { enabled: null, showDevTools: false, mode: 'bottom' }
Gtk-Message: 07:30:51.181: Failed to load module "canberra-gtk-module"
Gtk-Message: 07:30:51.182: Failed to load module "canberra-gtk-module"
[3:0129/073051.196215:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0129/073051.196256:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Saving backups to /home/futoshdirozini/.var/app/com.super_productivity.SuperProductivity/config/superProductivity/backups
07:30:51.271 › Saving backups to /home/futoshdirozini/.var/app/com.super_productivity.SuperProductivity/config/superProductivity/backups
[3:0129/073051.274403:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0129/073051.274458:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0129/073051.274486:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
^C
flatpak run io.gdevelop.ide
07:32:03.510 › GDevelop Electron app starting...
Gtk-Message: 07:32:03.591: Failed to load module "canberra-gtk-module"
Gtk-Message: 07:32:03.593: Failed to load module "canberra-gtk-module"
[3:0129/073203.636468:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0129/073203.636546:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3 preload-host-spawn-strategy] Dropping 0x33740026d140 (3) because of connection closed
^C
flatpak run com.rtosta.zapzap
setHighDpiScaleFactorRoundingPolicy must be called before creating the QGuiApplication instance
Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Qt: Session management error: Could not open network socket
qt.gui.imageio: libpng warning: iCCP: known incorrect sRGB profile
QPropertyAnimation: you're trying to animate the non-writable property width of your QObject
Might be more complicated than that. I just updated my kernel to match v9um's: 6.8.0-52-generic #53~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jan 15 19:18:46 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
My flatpaks worked, so I installed two that they listed errors for (Super Productivity and GDevelop), both of which also worked.
Depends on what the change to the kernel was. If it was a non-security related bugfix, then it's no problem. This was a relatively small update, given the version number, but I don't have a change list handy.
Just a side comment donct know if using flatseal would improve things. Personally on any GNu/Linux I will be sticking with X11 and APT. Once these options are gone back to the Amiga if I can get a zz9000 board for it.
I'd like to stick to wayland, it's more secure and I have no problem experiencing some minor bugs that will help in improving wayland for others by reporting the bug.
[3:0130/180210.534287:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Start app...
18:02:10.833 › { enabled: null, showDevTools: false, mode: 'bottom' }
Gtk-Message: 18:02:10.920: Failed to load module "canberra-gtk-module"
Gtk-Message: 18:02:10.922: Failed to load module "canberra-gtk-module"
[3:0130/180210.950208:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0130/180210.950286:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Saving backups to /home/futoshdirozini/.var/app/com.super_productivity.SuperProductivity/config/superProductivity/backups
18:02:11.128 › Saving backups to /home/futoshdirozini/.var/app/com.super_productivity.SuperProductivity/config/superProductivity/backups
[3:0130/180211.136100:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0130/180211.136196:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0130/180211.136264:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
^C
futoshdirozini@futoshdirozini-IdeaPad-5-15ITL05:~$ [3 preload-host-spawn-strategy] Dropping 0x266000038d80 (3) because of connection closed
[3:0130/180704.007239:FATAL:bus.cc(1246)] D-Bus connection was disconnected. Aborting.
/app/bin/run.sh: line 2: 3 Trace/breakpoint trap zypak-wrapper.sh /app/superproductivity/superproductivity "$@"