← Home ← Back to /g/

Thread 105980516

36 posts 14 images /g/
Anonymous No.105980516 [Report] >>105980759 >>105980775 >>105980788 >>105980818 >>105981828 >>105981978 >>105982017 >>105982056 >>105982974 >>105983597
>stutters your cursor
Anonymous No.105980681 [Report]
It's funny because it happens on xorg actually (thanks to the shitty AMD kernel drivers).
Anonymous No.105980759 [Report] >>105982123 >>105982828 >>105983090
>>105980516 (OP)
I have never experienced any of the issues people here say related to linux or linux software.

Are you guys just making shit up?
Anonymous No.105980775 [Report]
>>105980516 (OP)
Sounds like a poorfag problem
Anonymous No.105980788 [Report]
>>105980516 (OP)
Use case for smooth cursor movement?
Anonymous No.105980802 [Report]
Never had this problem on GNOME. Must be a KDE bug.
Anonymous No.105980818 [Report]
>>105980516 (OP)
how is this a wayland problem? it is just a protocol. sounds like a shitty compositor implementation or a GPU driver bug, which isnt wayland's problem.
Anonymous No.105981726 [Report]
Never had this issue with Windows 10, so sorry, can't relate.
Anonymous No.105981828 [Report]
>>105980516 (OP)
Works on my machine running KDE on CachyOS
Anonymous No.105981978 [Report] >>105982833 >>105982861
>>105980516 (OP)
It has HDR though.
Anonymous No.105982017 [Report]
>>105980516 (OP)
Works on machine running hyprland on gentoo
Anonymous No.105982056 [Report] >>105984400
>>105980516 (OP)
Cursor stutter was fixed in KDE and GNOME year or two ago.
Anonymous No.105982063 [Report]
>Set DPI to 150%
>X11 apps are now unusably blurry
Thanks, Ebussy.
Anonymous No.105982123 [Report]
>>105980759
Also works fine for me over here on KDE Fedora.
I assume that problems only occur on outdated machines
Anonymous No.105982132 [Report] >>105982840 >>105983044
Why does high disk IO stutter out the system even when I have 128GB of RAM? What's the usecase of having a desktop that doesn't lock up just because you're copying some files? Linux does this on every DE under X11 or Wayland.
Anonymous No.105982828 [Report] >>105983120
>>105980759
>I have never experienced any of the issues people here say related to linux or linux software.
same, but I don't use linux
Anonymous No.105982833 [Report]
>>105981978
does wine?
Anonymous No.105982840 [Report]
>>105982132
i dont fukcing know i really don't i thought i was my pc because i run rt kernel with zfs but i guess i was wrong
Anonymous No.105982861 [Report] >>105983037
>>105981978
Who cares, i have HDR monitor and dont use it at all. I want to see what most people see not minority with HDR enabled.
Anonymous No.105982974 [Report] >>105983060 >>105983070
>>105980516 (OP)
X11 user here. I like some of the security features of Wayland but all of the posts here about it being shit for vidya have me worried. Is it really that much worse for games or is it overblown because of the console war?
Anonymous No.105983037 [Report]
>>105982861
Same here. I have a HDR monitor with VRR but I dont use any of those features. Wayland is really just for meme features.
Anonymous No.105983044 [Report]
>>105982132
I dont have that issue but I have heard others that have it. I dunno what you have fucked up. Maybe some weird filesystem. I just use ext4.
Anonymous No.105983060 [Report] >>105983074
>>105982974
I can guarantee you 100% that the "security features" of wayland means absolutely nothing and a keylogger can be installed on your system easily regardless of if you use x11 or wayland. For example, is your ~/.bashrc / ~/.zshrc file writable to by your user? then the "security" of your display server doesn't matter at all.
Anonymous No.105983070 [Report]
>>105982974
If you are playing competitive games then wayland is worse. Also if your game is heavy on cpu then your cursor will lag as much as the game on wayland, which makes it feel like shit. Other than that it's ok.
Anonymous No.105983074 [Report] >>105983082 >>105983091 >>105983218
>>105983060
>um, what are namespaces bro?
It's 2025 retard. ~ isn't always the same ~. Flatpak, containers, etc. Wayland actually being secure is a good thing for these cases.
Anonymous No.105983082 [Report] >>105983091 >>105983123
>>105983074
99% of wayland users dont use such namespaces for all applications. Also xlibre has namespace support with Xnamespace.
Anonymous No.105983090 [Report]
>>105980759
Grammy, what are you doing here and how did you get past the captcha? I could have sworn I set your browser to open to Facebook. Did your caregiver use your computer again?
Anonymous No.105983091 [Report] >>105983119 >>105983123
>>105983082
>>105983074
Besides that, flatpak doesn't actually prevent flatpak applications from writing to your ~/.bashrc file! so if you run a flatpak it can easily fuck up your system anyways.
Anonymous No.105983119 [Report]
>>105983091
I mean flatpak does prevent that, but most flatpaks (that people use) need access to $HOME.
Anonymous No.105983120 [Report]
>>105982828
Based.
Anonymous No.105983123 [Report] >>105983278
>>105983082
>xlibre
nigga, you straight clowning. gtfo.
>>105983091
Post zero day in bubble wrap or fuck off. wtf is this shit?
Anonymous No.105983218 [Report]
>>105983074
>Flatpak
Why are you still using this thing knowing they are turning it into android store. You guys are crazy.
Anonymous No.105983278 [Report] >>105983927
>>105983123
>nigga, you straight clowning. gtfo.
Not an argument. Im using xlibre right now and I can namespace applications to prevent applications from having access to each other.

>Post zero day in bubble wrap or fuck off. wtf is this shit?
I meant that a lot of software that you use with flatpak need access to $HOME and they have access for that in their manifest. 99% of wayland users dont namespace all of their shit like a schizo. You are trying to turn linux desktop into android. Just use android if you want to lock everything down and use garbage like flatpak.
Anonymous No.105983597 [Report]
>>105980516 (OP)
The stuttering will continue until code improves
Anonymous No.105983927 [Report]
>>105983278
>dis nigga actually using xlibre
Anonymous No.105984400 [Report]
>>105982056
it was improved , it is not fixed, still happens under high gpu load.