Mnglw

[narrator voice: it wasn’t “just as easy as” nor did “everything work great”]

how are you only getting 1% battery drain overnight? my pixel 7 w grapheneos drains 10% overnight and battery saver makes it worse somehow

I would like to know your secrets

exactly this, I’ll use it when it works with no questions asked. I.e: when it becomes invisible to me as an enduser

as for now, it isn’t, far from it

fucking what synergy doesn’t work on Wayland? welp. I use that daily and no, that’s not optional, its rather critical for my setup

you’re right, I kinda let past experiences cloud my judgment for a bit there, and missed that you were doing the right thing,my apologies for that

sadly the fact that I did does point to the very problem I described.

that said I hope you can get somewhere and improve things, my apologies for the mix up

because a lot of foss devs, contributers and even users are so extremely hostile when suggesting ux improvement/report bugs/etcetc for end users not like them that frankly I dont wanna bother. Same reason I don’t report bugs

maybe first tackle that situation before you ask people to throw themselves into what effectively is a lion’s den to mauled by fossbros who can’t get over themselves edit: I no longer stand behind the last bit but Im keeping it here for downthread clarity

I’m not a she but otherwise yes I agree

for the end user, that is irrelevant

all of these arguments are great and all but as an enduser: I just want things to work

I don’t care about the why’s or hows. A lot of these arguments explain and justify breakage

I am an enduser. I expect things to work, specifically I expect the programs I already use to continue working. I expect to lose no functionality

If they don’t work, then clearly its broken. If I lose functionality, Wayland clearly wasn’t ready

I use a trackball mouse for disability reasons. I have to actively slow my cursor movement to a crawl and deliberately slowly click each square otherwise I fail captcha’s

it’s infuriating

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