[RESPONDED] A Few Irritating bugs on Ubuntu 22.04

Community Support
#1

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.

  1. 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)

  2. 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.

  3. 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.

Thanks,
-Michael

#2

11th Gen i7 1165 since Feb 2022
Updated to 22.10 in October :slight_smile:

No problems on 22.04 or 22.10

Haven’t tried a TV or screen

#3

Hi @Michael_Knudsen, welcome back :blush:

  1. what’s your mouse and touchpad speed on ubuntu settings? can we have the screenshot?

  2. when media keys suddenly stops can you try

libinput debug-events

see if keys has output when pressed?

  1. When External display has wrong res, can you try
wlr-randr --list-outputs

should display the HDMI connected device

then reset, like so

wlr-randr --output HDMI-1 --auto

Let us know how that goes :slight_smile:

3 Likes
#4

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):

OS: Ubuntu 22.04.2 LTS x86_64
Host: Laptop (12th Gen Intel Core) A6
Kernel: 5.19.0-35-generic
Uptime: 9 days, 13 hours, 31 mins
Packages: 3232 (dpkg), 43 (flatpak), 29 (snap)
Shell: bash 5.1.16
Resolution: 2256x1504
WM: sway
Theme: Adwaita [GTK3]
Icons: Papirus [GTK3]
Terminal: tilix
CPU: 12th Gen Intel i7-1260P (16) @ 4.700GHz
GPU: Intel Alder Lake-P
Memory: 8077MiB / 64020MiB

Output of libinput F1 to F10 when it stops working:

-event2   KEYBOARD_KEY            +0.000s	*** (-1) pressed
^[OP event2   KEYBOARD_KEY            +0.123s	*** (-1) released
 event2   KEYBOARD_KEY            +2.046s	*** (-1) pressed
^[OQ event2   KEYBOARD_KEY            +2.206s	*** (-1) released
 event2   KEYBOARD_KEY            +3.316s	*** (-1) pressed
^[OR event2   KEYBOARD_KEY            +3.430s	*** (-1) released
 event2   KEYBOARD_KEY            +4.069s	*** (-1) pressed
^[OS event2   KEYBOARD_KEY            +4.210s	*** (-1) released
 event2   KEYBOARD_KEY            +4.760s	*** (-1) pressed
^[[15~ event2   KEYBOARD_KEY            +4.884s	*** (-1) released
 event2   KEYBOARD_KEY            +5.300s	*** (-1) pressed
^[[17~ event2   KEYBOARD_KEY            +5.439s	*** (-1) released
 event2   KEYBOARD_KEY            +5.856s	*** (-1) pressed
^[[18~ event2   KEYBOARD_KEY            +5.994s	*** (-1) released
 event2   KEYBOARD_KEY            +6.596s	*** (-1) pressed
^[[19~ event2   KEYBOARD_KEY            +6.723s	*** (-1) released
 event2   KEYBOARD_KEY            +7.130s	*** (-1) pressed
^[[20~ event2   KEYBOARD_KEY            +7.255s	*** (-1) released
 event2   KEYBOARD_KEY            +7.738s	*** (-1) pressed
^[[21~ event2   KEYBOARD_KEY            +7.889s	*** (-1) released

I also reboot to fix at the minute.

1 Like
#5

@Loell_Framework I haven’t had these bugs happen again so far, but I will try these out next time it does.
Thanks

1 Like
#6

copy @Michael_Knudsen let us know if symptoms show again.

#7

if anyone finds out please do tell, ive been having the same issue since i got my 11th gen 13 inch over a year ago.

#8

Hi @ostap_tymchenko,

welcome back it’s been a bit while :slight_smile:

by the way what issue are you having? is it with media keys as well?

1 Like
#9

@Loell_Framework

My media keys stopped working again. Tested F1 through F10 with the following output below:
Looks similar to what monkeydiesel has I think.

-event2 KEYBOARD_KEY +0.000s *** (-1) pressed
^[OP event2 KEYBOARD_KEY +0.080s *** (-1) released
event2 KEYBOARD_KEY +0.774s *** (-1) pressed
^[OQ event2 KEYBOARD_KEY +0.925s *** (-1) released
event2 KEYBOARD_KEY +3.262s *** (-1) pressed
^[OR event2 KEYBOARD_KEY +3.413s *** (-1) released
event2 KEYBOARD_KEY +3.764s *** (-1) pressed
^[OS event2 KEYBOARD_KEY +3.890s *** (-1) released
event2 KEYBOARD_KEY +4.216s *** (-1) pressed
^[[15~ event2 KEYBOARD_KEY +4.358s *** (-1) released
event2 KEYBOARD_KEY +4.693s *** (-1) pressed
^[[17~ event2 KEYBOARD_KEY +4.795s *** (-1) released
event2 KEYBOARD_KEY +5.170s *** (-1) pressed
^[[18~ event2 KEYBOARD_KEY +5.293s *** (-1) released
event2 KEYBOARD_KEY +5.632s *** (-1) pressed
^[[19~ event2 KEYBOARD_KEY +5.730s *** (-1) released
event2 KEYBOARD_KEY +6.080s *** (-1) pressed
^[[20~ event2 KEYBOARD_KEY +6.181s *** (-1) released

Also here is a screenshot of my mouse touchpad settings:

image
image1722Ă—1427 256 KB

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.

#10

On my mint installation (which is ubuntu based ofc), I managed to fix the scrolling issue by adding the following to my .xsessionrc file:

idt=$(xinput list --id-only 'PIXA3854:00 093A:0274 Touchpad')
xinput --set-prop $idt "libinput Scrolling Pixel Distance" 40

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)

Hope this helps!

1 Like
#11

@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.

#12

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.

#13

Not seeing that here on my install of 23.04. When did you first experience this? Is this also happening on a Live USB of Ubuntu 23.04?

#14

I didn’t test this on a Live-CD 23.04. I just recently upgraded from 22.10 to 23.04. But the symptoms are happening.

There are a few people here as well: [TRACKING] Fn key stops working on PopOS after a while - #27 by Chris_Guidry

This is a 12th gen Framework, purchased last year. I have not run any BIOS update (as it’s still in beta).

#15

The thread linked was for 11th gen and it’s an issue we’re tracking down. Please try Live-USB of 23.04 and report back.