this post was submitted on 20 Aug 2024
13 points (59.7% liked)

Framework Laptop Community

2654 readers
1 users here now

Related links:

Related communities:

founded 3 years ago
MODERATORS
 

cross-posted from: https://lemmy.world/post/18838538

Wuuttup. I'm here complaining again about Framework's Linux unfriendly display. The new one this time.

https://frame.work/products/display-kit?v=FRANJF0001

Old display, 2256 x 1504 (3:2)

GNOME

100% scale

  • Nothing looks blurry
  • Everything is tiny
  • Unusable

100% scale + large text accessibility

  • Nothing looks blurry
  • Most apps scale appropriately
  • Some apps don’t respect GNOME’s large text setting (Alacritty)

125% scale

  • Most apps look blurry (Picard, Firefox, Spotify, Alacritty)

200% scale

  • Everything is way too big
  • Unusable

Plasma

100% scale

  • Nothing looks blurry
  • Everything is tiny
  • Unusable

125% scale + Apply scaling themselves

  • Nothing looks blurry
  • Most apps scale appropriate
  • Some apps can’t scale themselves and look tiny (Picard)

125% scale + Scaled by system

  • Most apps look blurry (Picard, Firefox, Spotify, Alacritty)

200% scale

  • Everything is way too big
  • Unusable

New display, 2880 x 1920 (3:2)

GNOME

100% scale

  • Nothing looks blurry
  • Everything is tiny
  • Unusable

100% scale + large text accessibility

  • Nothing looks blurry
  • Most apps scale appropriately
  • Some apps don’t respect GNOME’s large text setting (Alacritty)
  • Everything is tiny

150% scale

  • Most apps look blurry (Picard, Firefox, Spotify, Alacritty)

200% scale

  • Everything is way too big
  • Unusable

Plasma

100% scale

  • Nothing looks blurry
  • Everything is tiny
  • Unusable

150% scale + Apply scaling themselves

  • Nothing looks blurry
  • Some apps can’t scale themselves, but look a little better here? (Picard)

150% scale + Scaled by system

  • Most apps look blurry (Picard, Firefox, Spotify, Alacritty)

200% scale

  • Everything is way too big
  • Unusable

tl;dr

In the old display, GNOME at 100% + large text was the best compromise. In the new display, Plasma at 150% + Apply scaling themselves is the best compromise.

Interestingly, Picard scaling itself looks super tiny in the old display, but in the new display it looks... better. It's still not correctly scaled like native Wayland apps, but it's better.

Warning

If you can't stomach moving from GNOME to Plasma, then 🚨 DO NOT BUY THE NEW DISPLAY 🚨. The new display is worse for GNOME.

Once again

I am once again begging Framework to just give us a damn regular DPI display that works! Without workarounds. Without forcing users on specific DEs. Without forcing users to stop using their favorite apps. This new display has basically all of the flaws as the previous one.

you are viewing a single comment's thread
view the rest of the comments
[–] Darohan@lemmy.zip 20 points 3 months ago (2 children)

Not to be all "it works on my machine" but like,, it does. I've never seen or heard of any of these issues on a framework on Linux - using Plasma in NixOS in my case, and frequently using Picard, Spotify, and Firefox. Given they have official support for both Ubuntu and Fedora (Big Gnome moment), and have done in-house testing on both distros, as well as having Arch(?) and NixOS users on the engineering team, I think you might be looking at a problem in your own config rather than something innate to Framework?

[–] zurohki@aussie.zone 10 points 3 months ago

using Plasma

Plasma and "apps apply scaling themselves" works perfectly for everything except non-DPI aware apps. If you don't use any of those, it all just works.

Ideally all DPI aware apps would apply scaling themselves and non-DPI aware apps would be scaled by the system, but this is complicated to actually do. All apps run in the same xwayland environment at the same DPI under Plasma, so you have to set scaling for the whole environment.

[–] PlexSheep@infosec.pub 1 points 3 months ago

Ive had weird scaling with plasma on various distros with 1.5 global scaling. Currently on gnome pop!_os and it either works or I've learned to ignore it.

I remember steam was a bad one.