| 26 Nov 2023 |
 Hubble the Wolverine (they/them) | In reply to @hubofeverything:bark.lgbt
I don't really know where to start debugging. I don't get any gnome-related crashes listed in coredumpctl I didn't get any | 12:58:04 |
| Hubble the Wolverine (they/them) | Charlotte 🦝 (it/rac/racs/racself/🦝/plush): | 12:58:48 |
| Hubble the Wolverine (they/them) | * Charlotte 🦝 (it/rac/racs/racself/🦝/plush) | 12:58:53 |
| Hubble the Wolverine (they/them) | Look at the reply thread | 12:59:13 |
| Hubble the Wolverine (they/them) | I'm not sure where else to look at for debug logs | 13:38:34 |
 Jan Tojnar | In reply to @hubofeverything:bark.lgbt
Now I have a separate issue
When I plug in my display with displayport, gnome seems to restart. This doesn't happen with my HDMI display.
Short excerpt from the log of display-manager.service
Nov 21 04:30:40 Gulo-Laptop gdm[1842]: Gdm: GdmDisplay: Session never registered, failing
Nov 21 04:30:40 Gulo-Laptop gdm[1842]: Gdm: Child process -7523 was already dead.
I'm on the gnome branch, using a laptop with nvidia hybrid graphics.
maybe look a bit further in the journal history, not just for display-manager, often these things cascade | 16:34:57 |
| Hubble the Wolverine (they/them) | https://gist.github.com/the-furry-hubofeverything/51e2ff8cf2e6b168c1ca4070a5b8a022
Here's the log, for when I plug in the displayport display while logged in | 16:48:54 |
| Hubble the Wolverine (they/them) | In reply to @jtojnar:matrix.org
maybe look a bit further in the journal history, not just for display-manager, often these things cascade The journal only has few entries before "08:36:50", so I assumed that's when I plugged in the cable | 17:03:27 |
| Hubble the Wolverine (they/them) | The only entry around this time in coredumpctl is Discord:
Sun 2023-11-26 08:36:53 PST 6765 1000 100 SIGABRT present /app/discord/Discord 66.5M
| 17:04:39 |
| Hubble the Wolverine (they/them) | This is the flatpak version of it btw | 17:05:12 |
| Hubble the Wolverine (they/them) | GOT IT!
https://gitlab.gnome.org/GNOME/mutter/-/issues/3037 | 17:07:27 |
| Hubble the Wolverine (they/them) | The workaround at https://gitlab.gnome.org/GNOME/mutter/-/issues/3037#note_1850361 worked | 17:07:45 |
| Hubble the Wolverine (they/them) | sudo chrt -a -o -p 0 PID_OF_CURRENT_GNOME_SHELL_PROCESS | 17:07:56 |
| Jan Tojnar | Hubble the Wolverine (they/them): I guess we need 45.1 | 17:10:16 |
| Hubble the Wolverine (they/them) | I thought release-23.11 is on 45.1 | 17:13:07 |
| Hubble the Wolverine (they/them) | I'll reboot and see if I can redo the workaround | 17:13:29 |
| Hubble the Wolverine (they/them) | Might be a fluke | 17:13:33 |
| Jan Tojnar | hmm, it is | 17:17:02 |
| Jan Tojnar | and the commit that closed the issue should be part of 45.1 https://gitlab.gnome.org/GNOME/mutter/-/commit/5d3e31a49968fc0da04e98c0f9d624ea5095c9e0 | 17:17:47 |
| Hubble the Wolverine (they/them) | In reply to @hubofeverything:bark.lgbt
I'll reboot and see if I can redo the workaround So I rebooted, and I tried replicating the failure again by plugging in the displayport monitor - sure enough, all screens went black.
I did it again to confirm, and it still did it.
when I tried the workaround, and plugged in the monitor - it worked. But only once.
If I unplug the monitor and plug it back in after the workaround, the screens black out again
| 17:20:33 |
| Hubble the Wolverine (they/them) | So, it turns out that I have to run this command every time I plug in that monitor | 17:26:40 |
| Hubble the Wolverine (they/them) | But the workaround works | 17:27:59 |
| Hubble the Wolverine (they/them) | I wonder if ananicy has anything to do with it | 17:34:39 |
| Hubble the Wolverine (they/them) | Since it's related to scheduling and ananicy changes that based on rules, but it doesn't seem like ananicy did anything | 17:37:16 |
| 27 Nov 2023 |
|  Edmund Miller joined the room. | 01:29:01 |
| Edmund Miller | I'm getting a weird failure that might be related with nvidia on wayland. I login to gdm and then it just goes back to the login page. The logs are showing something about Unable to update utmp entry | 01:33:23 |
 uep | Hm. There's still something weird going on in bluetooth audio land. Another reboot, and now no bluetooth headsets show up in audio devices at all. | 02:55:12 |
| uep | In reply to @adam:robins.wtf
linsui got to it while i was asleep. they turned fractal-next into an alias. https://github.com/NixOS/nixpkgs/pull/269852 This has landed in unstable-small and the pkg is on cache.nixos.org. Hi from fractal | 03:01:49 |
 @adam:robins.wtf | it's working quite well for me. | 03:02:23 |
| @adam:robins.wtf | I don't recommend trying to compile fractal with less than 16GB of memory btw, so it's good to wait for it to be cached. | 03:03:09 |
