Hello,
I have been using the Framework Laptop (11th gen i5) since the summer 2022. Early on I changed my OS to Ubuntu 22.04. As a learning Linux user and a college student it has sometimes been a roller coaster of troubleshooting issues to say the least.
With some help, I managed to fix some bugs including the Intel wifi firmware getting corrupted by apt update. However, there are still a few noticeable bugs that linger today.
Extremely Sensitive 2-finger Trackpad Scrolling: Scrolling through pages on Firefox, pdf and word documents is insanely sensitive. Not to the point that it is unuseable, but jarring to anyone coming from “normal” scroll rates. I think it is a Wayland issue, but either way I have yet to find a solution. (Note: I have zero scroll issues when on Windows 10)
Function media keys randomly stop working: For whatever reason, the media keys such as volume, screen brightness, etc always seem to eventually stop working and default back to the f keys. Toggling the fn lock seems to have no effect. The only temporary solution I’ve found is to reboot.
Connecting External Displays: Connecting to a TV or projector via HDMI while on Ubuntu always seems to have an issue where the target resolution is too small (maxed at 1024/768) for example which makes the image have a mismatched aspect ratio. Rebooting seems to fix temporarily. (Note: again works fine on Windows 10).
Any thoughts on how I should try fixing these issues? I understand if any of you think this should go on an Ubuntu forum instead of here, but I figure these affect the Framework Laptop just as well personally.
I’m also experiencing this since my framework came back from repair (new main board, bios 03.06). I don’t recall it ever doing it previously. The OS has been updated in that time (not a major version update though):
The problem is that there is no setting specifically for two-touch scrolling speed via touchpad. Mouse scroll wheels are just fine. I wonder if there is just something wrong with the Framework Touchpad drivers for Linux OS.
you could also just run this in a terminal but it doesn’t persist after boot so adding it to that file should permanently fix the issue. The 40 can be changed to any other value, although keep in mind that, counter intuitively, higher numbers are slower (maybe the number represents like dots per scroll or something? idk)
@Loell_Framework hello, yes i was having this same issue with the media keys. also, do i know you? my apologies if we’ve talked, im not the best with names.
I’m seeing the same symptoms recently, under Ubuntu 23.04, with the keys not being correctly identified at all (i.e. just showing up as *** (-1) instead of e.g. KEY_LEFT (105) pressed). Might be a general issue with some internal drivers since regular keys on the keyboard (e.g. “Shift” or “e”) are showing up similarly unidentifiable.