Collection of Issues on Fedora 40/41 with FW13 (AMD)

Hello everyone!

While using my Framework Laptop 13 (AMD) with Fedora 40 (now 41) for a while I came across a few issues. Some of them I could fix, with others I am still stuck so I thought
it might be a good idea to collect them in a single thread hoping that you can help me solve the rest and that others with similar problems find solutions all at once. After all it shouldn’t be a too uncommon scenario to install Fedora on your new Framework Laptop.
Some issues likely are not at all related to the Framework laptop and probably should be posted in a Fedora forum, but I would like to start here looking for help.

  • Framework Laptop 13 AMD 7840U
  • BIOS: 3.05
  • Fedora 40 (now 41)
  • Current Kernel: 6.8.5-301.fc40.x86_64 (with Fedora 41)
  • Gnome 46 (now 47)
  • high-res display

1. [Solved] Lock Screen not Enabled by default (Fedora 40)

By default there was no GUI option to lock the screen.
Closing the laptop lid also did not lock the screen.

This could be fixed by running:

gsettings set org.gnome.desktop.lockdown disable-lock-screen false

I am surprised that such an elementary function was hidden behind a command-line option. This seems like a strange choice by Fedora.

2. [Open] Docking Station

Using the docking station Lenovo ThinkPad Thunderbolt 3 Dock does not
charge the Framework 13.
Displays and Ethernet usually work, yet sometimes the displays do not work, but instead the laptop charges.
(This is using the back port on the right side)
It always either charges OR works as docking station. Usually it is the latter.

3. [Open] Display configuration not remembered

After unplugging the laptop from the dock the display configuration
is forgotten and has to be set every time.

$ xrandr --listmonitors
Monitors: 3
 0: +*eDP-1 1440/290x960/190+0+1600  eDP-1
 1: +DP-12 1440/600x2560/340+1440+0  DP-12
 2: +DP-14 1440/600x2560/340+2880+0  DP-14

Without any changes, a few days later the configuration
was remembered and this has never caused troubles since.
As the issue was somewhat frustrating at the time, I’d
still appreciate if someone has an idea what went wrong.
Maybe this can also help someone else.

4. [Solved] Scaling issues with some Flatpaks

This so far is the most frustrating issue and likely is Gnome/Wayland/Fedora/Flatpak issue instead of a Framework problem.
Some Flatpaks (e.g. Mattermost, Podman Desktop) are blurry on the Framwork’s display.
Most references to this online argue that fractional scaling is the reason for this, however
I set the scaling to 200% and still have the issue.
Setting the scaling to 100% solves the issue, but is too small to be convenient.

Setting
gsettings set org.gnome.mutter experimental-features "['scale-monitor-framebuffer']"
did not fix the issue (but fixed other issues I had with flatpaks scaling too big)

Using KDE instead of Gnome solves this, but I am just not a big KDE fan.

Solved within 1 minute after posting by inffy:

gsettings set org.gnome.mutter experimental-features '["scale-monitor-framebuffer", "xwayland-native-scaling"]'

5. [Solved] Scaling of mouse cursor (after upgrade to Fedora 41)

Maybe a new bug in Fedora 41 or Gnome 47?
In many applications (e.g. Settings) the mouse cursor is scaled to at least
twice its size and very blurry.
Changing the scaling to 100% (200%, etc.) doesn’t solve this issue.
Changing the cursor size in the accessibility settings has no effect.

Normal Mouse Cursor
Normal size (zoomed in)

Humongous Mouse Cursor
Huge and blurry (same zoom level) as soon as hovering over some applications (file manager, settings)

Edit:
This was likely caused by me installing and uninstalling the KDE desktop environment.
Afterwards the Cursor was still set to the Breeze theme which did not behave well in Gnome.
Solved by setting cursor back to Adwaita in the Gnome tweaks.

6. [Open] Input Source

I usually use the input source “English (US, international)”, which has keys
on the third and fourth level for accented letters and umlauts for
German, French, or Italian.
I could not find this option in the source list

I tried:

gsettings set org.gnome.desktop.input-sources show-all-sources true

This did not fix the issue.

7. [Duplicate] Laptop becomes unresponsive

I can not reliably reproduce it and so far it has happened only twice in the
first two days.
The GUI became suddenly extremely slow with the mouse moving with a few mm/s
on the screen. Opening a terminal and rebooting via command-line solved this
issue but required a lot of patience.

This was seriously worrying me in the first days but never happened since.

Likely duplicate of Fedora KDE becomes suddenly slow

Suggested fix: amdgpu.dcdebugmask=0x200


Even though this is quite a list, I am otherwise very happy with my shiny new laptop.
If you have a solution or idea to any of these topics, please let me know and I will try it.
If problems are resolved that others encountered as well, maybe it would be worth it to add them to the Knowledge Base, even if they are caused by an officially supported distribution instead of Framework directly.

Thanks for reading so far,
Philipp

1 Like

I think you also need the xwayland-scaling setting:

gsettings set org.gnome.mutter experimental-features '["scale-monitor-framebuffer", "xwayland-native-scaling"]'

2 Likes

Thanks a lot, this solved the issue!
I updated the post with your solution to keep this thread as clear as possible.

1 Like

It’s likely this amdgpu issue 680M (Rebrandt) laptop randomly becomes very slow to update the screen (#3647) · Issues · drm / amd · GitLab. See also Fedora KDE becomes suddenly slow

The “amdgpu.dcdebugmask=0x200” kernel param workaround works for now.

3 Likes

Thank you!
If this ever happens again, I at least know it’s an open issue and I’ll try your solution.