| 25 Nov 2023 |
|  edgar.vincent joined the room. | 00:26:38 |
|  @adam:robins.wtf joined the room. | 02:07:01 |
| @adam:robins.wtf | Hi. There's a new release of fractal. Should I bump both fractal and fractal-next to v5? | 02:16:56 |
 uep | sounds good to me | 02:37:29 |
| uep | have been waiting for this | 02:37:41 |
| @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 | 13:36:41 |
 Jan Tojnar | In reply to @jayhenks:matrix.org
huh, but loupe does not really do the same as photos. Instead of showing all your photos in a nice grid you just have to click through them all photos was removed without replacement, see https://blogs.gnome.org/mcatanzaro/2023/08/17/gnome-45-core-apps-update/ | 14:08:35 |
 jayhenks | In reply to @jtojnar:matrix.org
photos was removed without replacement, see https://blogs.gnome.org/mcatanzaro/2023/08/17/gnome-45-core-apps-update/ Oh, interesting. Seems like not enough people cared about it | 23:17:39 |
| jayhenks | a bit sad | 23:17:42 |
| 26 Nov 2023 |
| uep | another minor annoyance (not at all nixos specific, I assume) - the process monitor graphs clip at 0% / 100% and look bad when all the cpus are busy.
| 09:58:59 |
| uep | 
Download Screenshot from 2023-11-26 09-02-56.png | 10:05:20 |
| uep | I'm guessing a consequence of changes as part of moving to gtk4 or something | 10:08:33 |
| uep | have to muster the energy to report upstream | 10:08:43 |
 Hubble the Wolverine (they/them) | In reply to @hubofeverything:bark.lgbt
Re: displayport instability on 23.11
Nov 24 06:06:16 Gulo-Laptop systemd[2731]: Starting GNOME Shell on Wayland...
Nov 24 06:06:16 Gulo-Laptop .gnome-shell-wr[2907]: Running GNOME Shell (using mutter 45.1) as a Wayland display server
Nov 24 06:06:17 Gulo-Laptop .gnome-shell-wr[2907]: Made thread 'KMS thread' realtime scheduled
Nov 24 06:06:17 Gulo-Laptop .gnome-shell-wr[2907]: Device '/dev/dri/card1' prefers shadow buffer
Nov 24 06:06:17 Gulo-Laptop systemd[2731]: org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL
Nov 24 06:06:17 Gulo-Laptop systemd[2731]: org.gnome.Shell@wayland.service: Failed with result 'signal'.
Nov 24 06:06:17 Gulo-Laptop systemd[2731]: Failed to start GNOME Shell on Wayland.
Nov 24 06:06:17 Gulo-Laptop systemd[2731]: org.gnome.Shell@wayland.service: Triggering OnFailure= dependencies.
Still a problem on commit e42a638b | 12:16:34 |
| Hubble the Wolverine (they/them) | I can't use my third monitor reliably, gnome shell keeps crashing | 12:19:21 |
| Hubble the Wolverine (they/them) | Sometimes it crashes on connect, and is able to run, but other times it crashes and is just not able to start | 12:19:46 |
 @lotte:chir.rs | what does systemd-coredumpctl info say about the crashes? | 12:36:21 |
| 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 |
