Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Flatpaks crashing after rebasing to stable from gts (nvidia-dx) #1647

Open
axel-kaliff opened this issue Sep 4, 2024 · 17 comments
Open

Flatpaks crashing after rebasing to stable from gts (nvidia-dx) #1647

axel-kaliff opened this issue Sep 4, 2024 · 17 comments
Labels
bug Something isn't working upstream Something that likely isn't us

Comments

@axel-kaliff
Copy link

Describe the bug

After rebasing to stable from gts (nvidia-dx), several flatpaks became unstable and crashes frequently. Obsidian, Zen browser, Software center to name a few.

Devpod isn't usable at all, crashing immediately after starting.

What did you expect to happen?

Flatpaks working as they did before (not crashing randomly).

Output of rpm-ostree status

State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: no runs since boot
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:stable
                   Digest: sha256:2a636edacae4ed133547475a4b6f4f8d4c20de2227716548ed35ec658e910fb8
                  Version: 40.20240902.0 (2024-09-03T05:53:45Z)
          LayeredPackages: gnome-shell-extension-pop-shell

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx-nvidia:gts
                   Digest: sha256:0524a47515e10033d6daa58bf361c7256ec868f2b52ae7f2ba927be3131aa3e5
                  Version: 39.20240831.0 (2024-09-01T17:53:39Z)
          LayeredPackages: gnome-shell-extension-pop-shell

Output of groups

axelkaliff wheel docker

Extra information or context

Using nvidia-dx stable branch.

The problem was not present on gts branch.

@dosubot dosubot bot added bug Something isn't working dx Developer Experience Image specific labels Sep 4, 2024
@axel-kaliff
Copy link
Author

Problems persists with "latest" branch

@castrojo
Copy link
Member

castrojo commented Sep 4, 2024

Anything on the terminal when you try to launch one by hand?

@castrojo castrojo removed the dx Developer Experience Image specific label Sep 4, 2024
@axel-kaliff
Copy link
Author

Running dev-pod:

** (dev-pod:84272): WARNING **: 01:44:36.337: webkit_settings_set_enable_offline_web_application_cache is deprecated and does nothing. Gdk-Message: 01:44:36.671: Error 71 (Protocol error) dispatching to Wayland display.

@castrojo
Copy link
Member

castrojo commented Sep 5, 2024

devpod isn't a flatpak, it'd be flatpak run org.mozilla.Firefox or something along those lines.

@axel-kaliff
Copy link
Author

axel-kaliff commented Sep 5, 2024

You're right, sorry about the misleading issue title.

Gnome Software also isn't a flatpak, but it crashes in the same way. Couldn't find a way to run it from terminal without the command finishing, so can't find error outputs for that.

Captured two flatpak crashes however:

flatpak run com.rtosta.zapzap:

The Wayland connection experienced a fatal error: Protocol error

flatpak run io.github.zen_broswer.zen:

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1@67: error 3: Release or Acquire point set but no buffer attached
 (t=3707.43) [GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1@67: error 3: Release or Acquire point set but no buffer attached
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=4Exiting due to channel error.
7.2723) Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=167.282) Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=2Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=3482.7) Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=3708.97) Exiting due to channel error.
Exiting due to channel error.

All crashes came after varying periods of the apps running, not immediate like dev-pods

@castrojo
Copy link
Member

castrojo commented Sep 5, 2024

Can you try on the X11 session? (Log into the GNOME Xorg session at the login screen via the gear icon on the bottom right).

@axel-kaliff
Copy link
Author

This seems to work better. No flatpak crashes yet, but dev-pods still isn't working.

It doesn't crash, but just gives a white screen
Screenshot from 2024-09-05 14-50-16

Running dev-pods in terminal:
(dev-pod:68756): WARNING 14:51:38.966: webkit_settings_set_enable_offline_web_application_cache is deprecated and does nothing.
Failed to create GBM buffer of size 1908x953: Invalid argument

@castrojo
Copy link
Member

castrojo commented Sep 5, 2024

Yeah the wayland errors led me to believe that it's an nvidia issue on wayland. Not sure on devpod but maybe someone else might have a clue.

@Pryka
Copy link

Pryka commented Sep 5, 2024

You're right, sorry about the misleading issue title.

Gnome Software also isn't a flatpak, but it crashes in the same way. Couldn't find a way to run it from terminal without the command finishing, so can't find error outputs for that.

Captured two flatpak crashes however:

flatpak run com.rtosta.zapzap:

The Wayland connection experienced a fatal error: Protocol error

flatpak run io.github.zen_broswer.zen:

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1@67: error 3: Release or Acquire point set but no buffer attached
 (t=3707.43) [GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1@67: error 3: Release or Acquire point set but no buffer attached
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=4Exiting due to channel error.
7.2723) Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=167.282) Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=2Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=3482.7) Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=3708.97) Exiting due to channel error.
Exiting due to channel error.

All crashes came after varying periods of the apps running, not immediate like dev-pods

ZapZap is dead on Wayland for many people including me. I can confirm this, also there is a bug issue on their github about it.

When it comes to Gnome Software it was always flaky, no matter the distro. At least for me.

Zen Browser uses Firefox and Firefox have issues on Wayland.

All your problems are unfortunately related to Wayland and Nvidia. Or just Wayland in some cases.

@tuht97
Copy link

tuht97 commented Sep 5, 2024

I also have the same problem with devpod crashing immediately. Also rebasing to stable from gts

Run dev-pod in terminal:
** (dev-pod:56246): WARNING **: 23:43:53.520: webkit_settings_set_enable_offline_web_application_cache is deprecated and does nothing. Gdk-Message: 23:43:53.685: Error 71 (Protocol error) dispatching to Wayland display.

@castrojo
Copy link
Member

castrojo commented Sep 5, 2024

Are you on nvidia also?

@tuht97
Copy link

tuht97 commented Sep 5, 2024

Are you on nvidia also?

Yes

@castrojo castrojo added the upstream Something that likely isn't us label Sep 5, 2024
@jmmaranan
Copy link

jmmaranan commented Sep 8, 2024

Hi there!
I just switched to Bluefin from Silverblue F40 and after install rebased to latest. I am on a RazerBlade 14 running Wayland with Nvidia card 3080. DevPod, VS Code, and Flatpaks, etc still work fine without crashing after reboot.

I used the nvidia-dx-gts image to install.

image

@saltrocks
Copy link

A temporary fix I've found is to run dev-pod with the following environment variable, as shown in this terminal command:

WEBKIT_DISABLE_COMPOSITING_MODE=1 dev-pod

@tuht97
Copy link

tuht97 commented Sep 18, 2024

Another fix i've found is just add this to .bashrc file
export WEBKIT_DISABLE_COMPOSITING_MODE=1 WEBKIT_DISABLE_DMABUF_RENDERER=1
OctoputApp/Yaak#75 (comment)

@awest03
Copy link

awest03 commented Oct 11, 2024

I'm in a similar situation with Intel/Nvidia hybrid graphics. Calendar, Calculator, Text Editor and Mission Center all fail to launch for me (on stable).

Output trying to launch Mission Center:

❯ flatpak run io.missioncenter.MissionCenter
MissionCenter::Application-Message: 14:57:57.268: Starting Mission Center v0.6.1
👋
F: child_pid: 8134
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:57.387: Starting v0.6.1...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:57.388: Initializing system state...
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:763: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:794: FINISHME: support more multi-planar formats with DRM modifiers
Gdk-Message: 14:57:57.704: Error 71 (Protocol error) dispatching to Wayland display.

~ 
❯ (missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.156: Setting up background data refresh thread...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Initializing platform utilities...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Setting up connection to main app...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Setting up D-Bus connection...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Requesting bus name...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Bus name acquired
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Setting up D-Bus proxy...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Setting up D-Bus signal match...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Setting up D-Bus crossroads...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus properties and methods...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus property `RefreshInterval`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `GetCPUStaticInfo`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `GetCPUDynamicInfo`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `GetDisksInfo`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `GetGPUList`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `GetGPUStaticInfo`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `GetGPUDynamicInfo`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `GetFansInfo`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `GetProcesses`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `GetApps`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `GetServices`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `TerminateProcess`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `KillProcess`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `EnableService`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `DisableService`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `StartService`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `StopService`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `RestartService`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `GetServiceLogs`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus interface `org.freedesktop.DBus.Peer`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `GetMachineId`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Registering D-Bus method `Ping`...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Instantiating System and inserting it into Crossroads...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.157: Creating thread pool...
(missioncenter-gatherer:8134): Gatherer::Main-MESSAGE: 4:57:58.158: Serving D-Bus requests...
❯ 
(missioncenter-gatherer:8134): Gatherer::Processes-CRITICAL **: 5:10:21.586: Failed to read `stat` file for process 9542, skipping: No such file or directory (os error 2)

(missioncenter-gatherer:8134): Gatherer::Processes-CRITICAL **: 5:10:21.586: Failed to read `stat` file for process 9559, skipping: No such file or directory (os error 2)

(missioncenter-gatherer:8134): Gatherer::Processes-CRITICAL **: 5:10:21.586: Failed to read `stat` file for process 9560, skipping: No such file or directory (os error 2)

(missioncenter-gatherer:8134): Gatherer::Processes-CRITICAL **: 5:10:21.586: Failed to read `stat` file for process 9563, skipping: No such file or directory (os error 2)

(missioncenter-gatherer:8134): Gatherer::Processes-CRITICAL **: 5:10:21.586: Failed to read `stat` file for process 9564, skipping: No such file or directory (os error 2)

(missioncenter-gatherer:8134): Gatherer::Processes-CRITICAL **: 5:10:21.587: Failed to read `stat` file for process 9585, skipping: No such file or directory (os error 2)

Seems as if it is running but without a window?

@Erin-22
Copy link

Erin-22 commented Oct 28, 2024

Now on bluefin-dx-nvidia:stable 40.20241027.0 from yesterday and all gnome apps seem to work fine without GSK_RENDERER=gl. Nvidia driver version was updated since the issue happened for me (now 565.57.01).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working upstream Something that likely isn't us
Projects
None yet
Development

No branches or pull requests

8 participants