You are not logged in.
hey all. I've run across an extremely weird bug that I can't figure out how to even track down what's causing it. right now it looks like it's probably in Wayland, but it could be in the kernel too I guess?
in any case. I'm running GNOME on Wayland, amdgpu drivers on a 6800 XT, 6.1.27-1-lts kernel. it's been quite good for me, until I just discovered a reproducible and frankly baffling crash: if I open rpcs3 (installed via the rpcs3-bin in AUR), choose File -> Install Packages, and then select multiple files in the file selector that pops up... Wayland crashes completely, dumping me out to my login manager. behaviour doesn't occur if I login with the same GNOME session under X11.
Anyone have a clue how I can debug this Wayland crash? I don't really have a clue what steps I should go through to figure out what it doesn't like here, but it's the only completely reproducible crash I've had with Wayland since installing this box a couple years ago.
Offline
https://wiki.archlinux.org/title/Step-b … ging_guide
https://wiki.archlinux.org/title/Systemd/Journal
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Alright, there's no core dumps from the crashes, but core dumps aren't disabled (`kernel.core_pattern = |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h`). my journal is a mess, but I'll dig into it...
aha! looks like `gnome-shell` is responsible, typical:
```
May 15 10:13:06 boxxy gnome-shell[4159]: **
May 15 10:13:06 boxxy gnome-shell[4159]: libmutter:ERROR:../mutter/src/core/window.c:1513:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
May 15 10:13:06 boxxy gnome-shell[4159]: Bail out! libmutter:ERROR:../mutter/src/core/window.c:1513:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
May 15 10:13:06 boxxy gnome-shell[4159]: == Stack trace for context 0x55d4137045f0 ==
May 15 10:13:06 boxxy systemd[1]: Created slice Slice /system/systemd-coredump.
May 15 10:13:06 boxxy systemd[1]: Started Process Core Dump (PID 976216/UID 0).
May 15 10:13:06 boxxy systemd-coredump[976217]: Resource limits disable core dumping for process 4159 (gnome-shell).
May 15 10:13:06 boxxy systemd-coredump[976217]: Process 4159 (gnome-shell) of user 1000 dumped core.
May 15 10:13:06 boxxy systemd[1]: systemd-coredump@0-976216-0.service: Deactivated successfully.
May 15 10:13:06 boxxy rpcs3[96391]: Error reading events from display: Broken pipe
May 15 10:13:06 boxxy xdg-desktop-por[5430]: Error reading events from display: Broken pipe
May 15 10:13:06 boxxy xdg-desktop-por[5578]: Error reading events from display: Broken pipe
May 15 10:13:06 boxxy syncthing-gtk[4718]: Error reading events from display: Broken pipe
May 15 10:13:06 boxxy gsd-power[4586]: Error reading events from display: Broken pipe
May 15 10:13:06 boxxy guake.desktop[4686]: System doesn't support transparency
May 15 10:13:06 boxxy gsd-wacom[4612]: Error reading events from display: Broken pipe
May 15 10:13:06 boxxy gsd-keyboard[4583]: Error reading events from display: Broken pipe
May 15 10:13:06 boxxy gsd-color[4576]: Error reading events from display: Broken pipe
May 15 10:13:06 boxxy gsd-media-keys[4585]: Error reading events from display: Broken pipe
May 15 10:13:06 boxxy xdg-desktop-por[5750]: Error reading events from display: Broken pipe
```
I'll see about bumping the resources limits so that gnome-shell can core dump, and then see where it's dying.
Offline