| 15 Nov 2025 |
Capypara | I have 14 installed, none of them are compatible it seems | 14:44:16 |
Capypara | I didn't even want to update GNOME yet, I know 25.11 isn't out yet, I just missed that GNOME 49.1 landed in unstable now already - and I guess now I can't really go back anymore 😅 | 14:45:25 |
Capypara | that image doesn't load for me unforunately | 14:45:38 |
ghpzin | https://github.com/NixOS/nixpkgs/pull/461080 Seems like update is on master, just did not get to unstable yet | 14:46:06 |
Capypara | ah great, was just about to check | 14:46:25 |
Capypara | Well I'll live with this then for a few days :) | 14:46:35 |
Capypara | but no working shortcuts in Firefox is really strange | 14:46:43 |
Capypara | okay they just randomly now work again, and I can't reproduce it anymore. 🤷♂️ | 15:03:06 |
ElvishJerricco | Ok, I don't actually use orca; I just noticed that it was definitely broken: https://github.com/NixOS/nixpkgs/pull/461953 | 15:30:17 |
ElvishJerricco | can anyone who actually uses orca on nixos-unstable test this? | 15:30:33 |
Capypara | I don't know if I'm just unlucky, but wow has GNOME 49 been unstable for me so far. | 20:46:04 |
Capypara | For example, GNOME consistently crashes when trying to close a background app | 20:46:19 |
Capypara | and with no log message, fun | 20:48:14 |
Capypara | the compositor just says: good bye | 20:48:24 |
Capypara | Nov 15 21:45:18 kirschbaum org.gnome.Fractal[9165]: 2025-11-15T20:45:18.230247Z WARN fractal::utils::media::image: Could not decode image: the server returned an error: [400 / M_UNKNOWN] Cannot fi>
Nov 15 21:45:43 kirschbaum systemd[2994]: Started Application launched by gnome-shell.
Nov 15 21:45:43 kirschbaum systemd[2994]: Started Application launched by gnome-shell.
Nov 15 21:45:43 kirschbaum pipewire[8028]: mod.x11-bell: X11 I/O error handler called on display :0
Nov 15 21:45:43 kirschbaum pipewire[8028]: mod.x11-bell: X11 display (:0) has encountered a fatal I/O error
Nov 15 21:45:43 kirschbaum fractal[9165]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum kgx[9676]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum gnome-calendar[8825]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum epiphany-search-provider[8833]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum gnome-control-center-search-provider[8823]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum gnome-control-center-global-shortcuts-provider[8221]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum io.github.alain[8214]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum xdg-desktop-portal-gnome[8069]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum evolution-alarm-notify[8020]: Error reading events from display: Broken pipe
Nov 15 21:45:43 kirschbaum gnome-software[8024]: Lost connection to Wayland compositor.
Nov 15 21:45:43 kirschbaum xdg-desktop-portal-gtk[8266]: Error reading events from display: Broken pipe
Nov 15 21:45:43 kirschbaum systemd[2994]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL
| 20:49:01 |
K900 | coredumpctl debug is probably the place to start looking then | 20:50:14 |
Capypara | No idea what that is | 20:52:01 |
Capypara | but I'll try | 20:52:13 |
Capypara | but GNOME isn't segfaulting or anything like that | 20:54:00 |
Capypara | it just exits | 20:54:01 |
Capypara | As far as I can tell at least | 20:54:08 |
K900 | The compositor is very likely crashing | 20:54:25 |
Capypara | Is it supposed to break then when I hit coredumpctl debug and trigger the crash? | 20:54:56 |
Capypara | because coredumpctl doesn't break | 20:55:13 |
K900 | No, coredumpctl debug starts a debugger on the last core dump it has recorded | 20:55:35 |
Capypara | okay but that is Spotify, so I guess GNOME is not segfaulting | 20:56:21 |
K900 | You can use coredumpctl (no arguments) to see all the core dumps | 20:56:37 |
K900 | And then use coredumpctl debug <pid> | 20:56:45 |
Capypara | Last one is from yesterday. | 20:56:53 |
K900 | Last or first? They're ordered oldest to newest | 20:57:08 |