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

Gnome/Wayland crashes randomly F40 latest (AMD) #1253

Closed
stephan-klein opened this issue May 4, 2024 · 5 comments
Closed

Gnome/Wayland crashes randomly F40 latest (AMD) #1253

stephan-klein opened this issue May 4, 2024 · 5 comments

Comments

@stephan-klein
Copy link

stephan-klein commented May 4, 2024

Describe the bug

Gnome wayland session crashes randomly but often out of the blue (not related to running anything in specific)

journalctl reports at the time of crash a sequence like this. This logs starts with the first entry shown below at the time of crash. There is silence about 2 minutes prior so i can trace it back to this timestamp (output is not reversed):


Mai 04 08:35:51 fedora gnome-logs[44453]: Error reading events from display: Broken pipe
Mai 04 08:35:51 fedora gsd-color[41489]: Error reading events from display: Broken pipe
Mai 04 08:35:51 fedora gsd-keyboard[41494]: Error reading events from display: Broken pipe
Mai 04 08:35:51 fedora gnome-software[41545]: Error reading events from display: Broken pipe
Mai 04 08:35:51 fedora gsd-media-keys[41497]: Error reading events from display: Broken pipe
Mai 04 08:35:51 fedora ptyxis[43245]: Error reading events from display: Broken pipe
Mai 04 08:35:51 fedora gsd-wacom[41558]: Error reading events from display: Broken pipe
Mai 04 08:35:51 fedora evolution-alarm[41613]: Error reading events from display: Broken pipe
Mai 04 08:35:51 fedora polkitd[4471]: Unregistered Authentication Agent for unix-session:5 (system bus name :1.305, object path >
Mai 04 08:35:51 fedora solaar[41597]: Error reading events from display: Broken pipe
Mai 04 08:35:51 fedora gsd-power[41501]: Error reading events from display: Broken pipe
Mai 04 08:35:51 fedora xdg-desktop-por[42105]: Error reading events from display: Broken pipe
Mai 04 08:35:51 fedora xdg-desktop-por[41986]: Error reading events from display: Broken pipe
Mai 04 08:35:51 fedora systemd[6613]: [email protected]: Main process exited, code=killed, status=9/KILL

...
other apps continue to crash

What did you expect to happen?

No crash

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:latest
                   Digest: sha256:81d332a4c3af576a79a22800bf282432a5bb638a297cf5a897cde2aa285be0b6
                  Version: 40.20240503.0 (2024-05-03T16:52:23Z)

  ostree-image-signed:docker://ghcr.io/ublue-os/bluefin-dx:latest
                   Digest: sha256:bd9c89359d9beb9e2bce295e02118db71987bf222b9e89d46a53203896ed607b
                  Version: 40.20240502.0 (2024-05-02T16:53:45Z)

Extra information or context

Hardware: Framework 16. No GPU Attached

What I tried so far:

  • Disabled all Gnome Extensions and rebooted (i still keep them disabled)
@stephan-klein stephan-klein changed the title Gnome/Wayland crashes randomly F40 latest Gnome/Wayland crashes randomly F40 latest (AMD) May 4, 2024
@m2Giles
Copy link
Member

m2Giles commented May 4, 2024

Is this around the time that the screen either blanks or the lockscreen attempts to lock?

@stephan-klein
Copy link
Author

stephan-klein commented May 4, 2024

No its while actively using it, really randomly. Can be while I'm typing or when I'm off the inputs for seconds and thinking about the next line of code. So far it happened while using Firefox, VsCode or Terminal, but none of those in specific. It also happened while using any of those apps all alone. No devices are connected. Happens on battery and on charging.

It would help if somebody gave me a tip what else i could turn off or debug. If there is any other logs than journalctl i could look at or any tests i could run.

@m2Giles
Copy link
Member

m2Giles commented May 4, 2024

I would still try the fix in this issue:
#1081

@m2Giles
Copy link
Member

m2Giles commented May 7, 2024

#1263

Applies the fix for everyone.

@stephan-klein
Copy link
Author

Thanks.

Setting MUTTER_DEBUG_KMS_THREAD_TYPE=user helped

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants