zlacker

[return to "Linux on the laptop works so damn well that it’s boring"]
1. mid-ki+H5[view] [source] 2022-09-24 17:38:51
>>tonyst+(OP)
Yeah, no. Maybe with old laptops, but newer laptops still have their fair share of issues. When I bought my thinkpad A485 kernels wouldn't boot without additional parameters, the graphics would freeze at times and cause a hardlock, sleep and hibernation have been fixed and broken again intermittently over several kernel versions, the wifi card's AP mode started causing segfaults in kernel 5.2 due to the driver's rewrite but has since been fixed, the fnlock key LED didn't update properly, which I spent a while debugging and submitted a kernel patch for, and while over the years the fingerprint scanner has been implemented, it's a pain to install and support for fingerprint scanning in linux is still in a very sorry state. Oh and bluetooth still can't connect more than one device at a time, so I had to buy a dongle to connect two joycon controllers.

Granted, I've always had these kinds of issues with new laptops, especially when it came to proprietary nvidia or AMD graphics (before AMDGPU) and I agree it's improved a lot, but I still need to tell people that there's caveats with some (especially newer) laptops.

◧◩
2. _skel+Eu[view] [source] 2022-09-24 20:47:25
>>mid-ki+H5
With Wayland, Gnome and KDE have no way to adjust the scroll speed on a laptop trackpad. Not the pointer speed, the scroll speed.

In 2022.

That is the kind of basic thing that does not work.

In addition to that, if you have a high-DPI laptop display and you want to plug it into a low-DPI desktop monitor (or vice-versa), good luck getting the scaling to work in a usable way.

◧◩◪
3. kaba0+Ie1[view] [source] 2022-09-25 05:52:34
>>_skel+Eu
Here is a comment that may solve it from a recent thread: https://news.ycombinator.com/item?id=32896463

Though it has nothing to do with Wayland before the flamewar starts, it’s just libinput and gtk maintainers not agreeing upon whose responsibility is it to handle scroll events (it is gtk’s though, libinput doesn’t have enough context to implement kinetic scrolling, so it really should be the framework that adds semantic meaning to an event stream)

◧◩◪◨
4. ChuckN+Jx1[view] [source] 2022-09-25 11:37:21
>>kaba0+Ie1
>it has nothing to do with Wayland before the flamewar starts, it’s just libinput and gtk maintainers not agreeing upon whose responsibility is it to handle scroll events

Sure, but for me as an end user, it's irrelevant who's fault of this bazaar engineering endeavor it is that very basic quality of life features from Windows/MacOS do not work on Linux.

As a dev I understand the struggle why this and many other stuff doesn't work right on Linux, but as a consumer/end user I don't care about their internal feud and I expect the product I use to have basic stuff like this working out of the box.

[go to top]