Bazzite 41 Multi-Monitor Scaling

[franchise2099]

Describe the bug

My Rig has two displays with two different refresh rates. Primary LG 1440 165 hz & 24 inch Wacom Cintiqu 4k 60 hz.

What did you expect to happen?

After updating to Bazzite 41, the main display (LG 1440 p @ 165 hz does not scale full screen. (Image is too large and doesn't scale correctly.

Output of rpm-ostree status

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
Digest: sha256:d4c237d6b9147cc56126f775ca4a3629fe652dc6f26bc7246984e54a91aa8e54
Version: 41.20241030.1 (2024-10-31T03:09:36Z)

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-gnome:stable
Digest: sha256:258385734de22069ce42c19fdb5c64a70a54b6ccc99e5506ea371258722f36a8
Version: 41.20241029.1 (2024-10-29T15:36:33Z)

Hardware

H/W path Device Class Description

                                system      Computer

/0 bus Motherboard
/0/0 memory 16GiB System memory
/0/1 processor AMD Ryzen 7 2700X Eight-Core Processor
/0/100 bridge Family 17h (Models 00h-0fh) Root Complex
/0/100/0.2 generic Family 17h (Models 00h-0fh) I/O Memory Management Unit
/0/100/1.3 bridge Family 17h (Models 00h-0fh) PCIe GPP Bridge
/0/100/1.3/0 bus Advanced Micro Devices, Inc. [AMD]
/0/100/1.3/0.1 storage 400 Series Chipset SATA Controller
/0/100/1.3/0.2 bridge 400 Series Chipset PCIe Bridge
/0/100/1.3/0.2/0 bridge 400 Series Chipset PCIe Port
/0/100/1.3/0.2/0/0 enp3s0 network I211 Gigabit Network Connection
/0/100/1.3/0.2/1 bridge 400 Series Chipset PCIe Port
/0/100/1.3/0.2/1/0 wlp4s0 network RTL8822BE 802.11a/b/g/n/ac WiFi adapter
/0/100/1.3/0.2/2 bridge 400 Series Chipset PCIe Port
/0/100/1.3/0.2/3 bridge 400 Series Chipset PCIe Port
/0/100/1.3/0.2/4 bridge 400 Series Chipset PCIe Port
/0/100/3.1 bridge Family 17h (Models 00h-0fh) PCIe GPP Bridge
/0/100/3.1/0 bridge Navi 10 XL Upstream Port of PCI Express Switch
/0/100/3.1/0/0 bridge Navi 10 XL Downstream Port of PCI Express Switch
/0/100/3.1/0/0/0 display Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT]
/0/100/3.1/0/0/0.1 card0 multimedia Navi 21/23 HDMI/DP Audio Controller
/0/100/3.1/0/0/0.1/0 input57 input HDA ATI HDMI HDMI/DP,pcm=3
/0/100/3.1/0/0/0.1/1 input58 input HDA ATI HDMI HDMI/DP,pcm=7
/0/100/3.1/0/0/0.1/2 input59 input HDA ATI HDMI HDMI/DP,pcm=8
/0/100/3.1/0/0/0.1/3 input60 input HDA ATI HDMI HDMI/DP,pcm=9
/0/100/3.1/0/0/0.1/4 input61 input HDA ATI HDMI HDMI/DP,pcm=10
/0/100/3.1/0/0/0.1/5 input62 input HDA ATI HDMI HDMI/DP,pcm=11
/0/100/3.3 bridge Family 17h (Models 00h-0fh) PCIe GPP Bridge
/0/100/3.3/0 /dev/nvme0 storage Samsung SSD 970 EVO Plus 250GB
/0/100/3.3/0/0 hwmon0 disk NVMe disk
/0/100/3.3/0/2 /dev/ng0n1 disk NVMe disk
/0/100/3.3/0/1 /dev/nvme0n1 disk NVMe disk
/0/100/7.1 bridge Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
/0/100/7.1/0 generic Zeppelin/Raven/Raven2 PCIe Dummy Function
/0/100/7.1/0.2 generic Family 17h (Models 00h-0fh) Platform Security Processor (PSP) 3.0 Device
/0/100/7.1/0.3 bus Zeppelin USB 3.0 xHCI Compliant Host Controller
/0/100/8.1 bridge Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B
/0/100/8.1/0 generic Zeppelin/Renoir PCIe Dummy Function
/0/100/8.1/0.2 storage FCH SATA Controller [AHCI mode]
/0/100/8.1/0.3 card1 multimedia Family 17h (Models 00h-0fh) HD Audio Controller
/0/100/8.1/0.3/0 input63 input HD-Audio Generic Rear Mic
/0/100/8.1/0.3/1 input64 input HD-Audio Generic Front Mic
/0/100/8.1/0.3/2 input65 input HD-Audio Generic Line
/0/100/8.1/0.3/3 input66 input HD-Audio Generic Line Out
/0/100/8.1/0.3/4 input67 input HD-Audio Generic Front Headphone
/0/100/14 bus FCH SMBus Controller
/0/100/14.3 bridge FCH LPC Bridge
/0/100/14.3/0 system PnP device PNP0c01
/0/100/14.3/1 system PnP device PNP0b00
/0/100/14.3/2 system PnP device PNP0c02
/0/100/14.3/3 system PnP device PNP0c02
/0/101 bridge Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
/0/102 bridge Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
/0/103 bridge Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
/0/104 bridge Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
/0/105 bridge Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
/0/106 bridge Family 17h (Models 00h-1fh) PCIe Dummy Host Bridge
/0/107 bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0
/0/108 bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1
/0/109 bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2
/0/10a bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3
/0/10b bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4
/0/10c bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5
/0/10d bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6
/0/10e bridge Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7
/1 scsi9 storage
/2 card2 multimedia Controller
/3 card3 multimedia Audio
/4 input0 input Power Button
/5 input1 input Power Button
/6 input15 input Generic USB Audio Consumer Control
/7 input16 input Generic USB Audio
/8 input44 input Wacom Cintiq Pro 24 Touch Finger
/9 input47 input Wacom Express Key Remote Pad
/a input49 input Wacom Cintiq Pro 24 Pen
/b input51 input Wacom Cintiq Pro 24 Pad
/c input52 input Logitech K830
/d input53 input Logitech K350
/e input54 input Logitech G602
/f input55 input PC Speaker
/10 input56 input Eee PC WMI hotkeys
/11 input69 input Sony Interactive Entertainment Wireless Controller
/12 input70 input Sony Interactive Entertainment Wireless Controller Motion Sensors
/13 input71 input Sony Interactive Entertainment Wireless Controller Touchpad

Extra information or context

Everything scaled and worked correctly under bazzite 40

[franchise2099]

This is specific to applications that is using "fullscreen" (Youtube Fullscreen, Steam Games, Plex HTPC, Pegasus Front end launcher, etc.)

[franchise2099]

Ok.... I changed the Scaling from 100% to 125% and that seemed to fix the issue? weird since I didn't touch anything before the update.

[finsterdexter]

I'm noticing similar behavior on my current setup. LG Ultragear 45" monitor, native resolution 3440x1440 @ 240 Hz. I also have connected an Asus Predator 27" native resolution 2560x1440 @ 144 Hz.

If I set the scaling on both to 100%, everything is fine. I'd like to set the scaling to 125% on the Asus, though. When I do, xrandr no longer lists the native resolution 3440x1440 for the LG, but instead reports 4300x1800. When I run games in fullscreen or borderless, they also run at 4300x1800. The desktop on the LG doesn't appear to be 4300x1800. Windows, UI, etc. is all scaled to native 3440x1440. Only when I run something fullscreen does it run at 4300x1800 (which is then scaled to the LG native 3440x1440.)

If I set scaling on the Asus to 150%, then xrandr is reporting 5160x2160 for the LG, and fullscreen wants to render that as well.

When I reset the scaling on the Asus back to 100% everything works normally and at their native resolutions. Really weird. It's kind of a cool undocumented feature, as I could scale up the resolution on LG to crazy high levels if I wanted. However, I suspect I could also do that with just xrandr commands, so idk.

[CheckYourFax]

Is this still an issue on the latest version of Bazzite? There have been multiple updates to both KDE and GNOME integrated in the latest version of Bazzite.

Just leave a comment if the issue is still relevant.

[finsterdexter]

Just tested on my setup, and I see the same behavior as previously noted.

[CheckYourFax]

If you're on KDE:

Try setting under Display & Monitor (in System Settings) "Legacy applications" to Apply scaling themselves instead of the now default Scaled by the system. Could you try to play around with these settings to see if it solves your issue?

[mitterman2]

same problem here. scaling primary display to 125% locks the resolution in games using fullscreen windowed.
gnome-nvidia

[OriginalAlienOne]

I am experiencing this same issue. Changing the scaling actually causes apps and games to open on different monitors, lock out resolutions, and pushes primary desktop display slightly onto other monitors.

Output of rpm-ostree status:

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
Digest: sha256:005d7a0eccac4bee7bff1651c5bf11267eb14d4de349144f83f1bad6482ddc93
Version: 41.20250409.1 (2025-04-09T19:11:15Z)
LayeredPackages: coolercontrol liquidctl

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
Digest: sha256:005d7a0eccac4bee7bff1651c5bf11267eb14d4de349144f83f1bad6482ddc93
Version: 41.20250409.1 (2025-04-09T19:11:15Z)

For reference, I've included a "print screen" screenshot of what it does to my desktop if monitors 1&2 are at 100% scaling and monitor 3 is at 95%. The desktop is pushing slightly to the left into the left monitor (lower image). Current setup has all three monitors at 100% scaling, and Cyberpunk's highest resolution on my primary monitor will only go up to 2215x1246, and the monitor is a 3440x1440 display (upper image).

[KyleGospo]

I am experiencing this same issue. Changing the scaling actually causes apps and games to open on different monitors, lock out resolutions, and pushes primary desktop display slightly onto other monitors.

Output of rpm-ostree status:

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
Digest: sha256:005d7a0eccac4bee7bff1651c5bf11267eb14d4de349144f83f1bad6482ddc93
Version: 41.20250409.1 (2025-04-09T19:11:15Z)
LayeredPackages: coolercontrol liquidctl

ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
Digest: sha256:005d7a0eccac4bee7bff1651c5bf11267eb14d4de349144f83f1bad6482ddc93
Version: 41.20250409.1 (2025-04-09T19:11:15Z)

For reference, I've included a "print screen" screenshot of what it does to my desktop if monitors 1&2 are at 100% scaling and monitor 3 is at 95%. The desktop is pushing slightly to the left into the left monitor (lower image). Current setup has all three monitors at 100% scaling, and Cyberpunk's highest resolution on my primary monitor will only go up to 2215x1246, and the monitor is a 3440x1440 display (upper image).

You're on 41, update to 42 and open a new issue if this still occurs.