Christopher Snowhill

Nope. Here's a log with the latest sfwbar running on a slightly older croissant. I need to update croissant, but I need to bug the dev about building a dependency...

Sorry about that, it took me too long to realize this was happening because of multiple monitors and multiple bars. Edit: Looks like I guess I tripped a general issue...

Yes, that fixes it. Excellent. Fixes all of the bars. Waybar, sfwbar, ironbar. Edit: Scratch that. The hack now makes gtk-layer-shell hang attempting to open the bluetooth menu on any...

Same issue on AMD on KDE 6.5: ``` [gamescope] [Info] xdg_backend: uMaxContentLightLevel: 80 [gamescope] [Info] xdg_backend: HDR INFO [gamescope] [Info] xdg_backend: cv_hdr_enabled: true [gamescope] [Info] xdg_backend: uTF: GAMMA22 [gamescope] [Info]...

> > Replying to [#2000 (comment)](https://github.com/ValveSoftware/gamescope/issues/2000#issuecomment-3448094509) > > Did that fix it? Yes. Sorry for not posting last night when I actually tested it. Edit: And the issue I had...

It fixes the CPU usage registering, but now sfwbar live locks and stops responding entirely shortly after startup.

Yeah, something that would disable this block of code and only print the IP address: https://github.com/janikrabe/oidentd/blob/3226029233be270955c71463f48939255622e30d/src/oidentd.c#L263-L266