Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)MN
Posts
0
Comments
65
Joined
2 yr. ago

  • if I knew what exactly was causing it hardware wise I would have a way to fix it, and I don't

    given GNOME's solution is "use Wayland" (which I can't for a variety of reasons) I don't think I can ever figure out what the problem is. Their attitude from the start is already non helpful.

    all I know is my hardware isn't niche nor really really old. And Im not the only one experiencing this

  • certain hardware configurations. I have two computers on linux. One of them has issues with GTK4, the other one doesn't. The only difference between these machines is hardware.

    And yeah, I agree that's premature for them to do

  • I would switch if it worked at all I just get a black screen if I try a Wayland session lmao. If switching is such a hassle then I'll just stick with what works.

    That's not to even mention all the things I use that aren't supported

  • Nobody's requiring it until devs start not supporting X11 anymore and start saying things like "won't fix, use Wayland". Which is already happening

    See: GNOME's response to a critical GTK4 bug on x11 that makes any program using GTK4 unusable on certain devices under x11