Display resolution change not supported on Wayland

Bug report on New iso.

On this hardware, Wayland does not let me change desktop resolution (defaults to 1024x7xx). It seems to be the case on other Wayland ISO’s as well.

There’s not a lot on this issue online. I don’t know what unsupported means here. Is 1920x1200 not supported or is the display not supported?

A data point.


I wonder too, if there is going to be xorg legacy solution, would be beneficial on older hardware (the oldies here are Dell Ultrasharp Ips monitors).

➜  ~ garuda-inxi
System:
  Kernel: 6.5.4-zen2-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc available: hpet,acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=cd4e199c-5699-4822-9f3c-b5e74d75ff6c rw rootflags=subvol=@
    quiet quiet rd.udev.log_priority=3 vt.global_cursor_default=0 loglevel=3
    ibt=off
  Desktop: KDE Plasma v: 5.27.8 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
    dm: SDDM Distro: Garuda Linux base: Arch Linux
Machine:
  Type: Desktop Mobo: ASUSTeK model: PRIME B450M-A v: Rev X.0x
    serial: <superuser required> UEFI: American Megatrends v: 3604
    date: 02/25/2022
CPU:
  Info: model: AMD Ryzen 7 2700X bits: 64 type: MT MCP arch: Zen+ gen: 2
    level: v3 note: check built: 2018-21 process: GF 12nm family: 0x17 (23)
    model-id: 8 stepping: 2 microcode: 0x800820D
  Topology: cpus: 1x cores: 8 tpc: 2 threads: 16 smt: enabled cache:
    L1: 768 KiB desc: d-8x32 KiB; i-8x64 KiB L2: 4 MiB desc: 8x512 KiB
    L3: 16 MiB desc: 2x8 MiB
  Speed (MHz): avg: 3507 high: 3700 min/max: 2200/3700 boost: disabled
    scaling: driver: acpi-cpufreq governor: performance cores: 1: 2406 2: 3239
    3: 3700 4: 3700 5: 3700 6: 2973 7: 3700 8: 3700 9: 3700 10: 3700 11: 3700
    12: 3700 13: 3700 14: 3094 15: 3700 16: 3700 bogomips: 118393
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities: <filter>
Graphics:
  Device-1: NVIDIA GP104 [GeForce GTX 1080] vendor: Gigabyte driver: nvidia
    v: 535.104.05 alternate: nouveau,nvidia_drm non-free: 535.xx+
    status: current (as of 2023-08) arch: Pascal code: GP10x
    process: TSMC 16nm built: 2016-21 pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 09:00.0 chip-ID: 10de:1b80 class-ID: 0300
  Device-2: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:4 chip-ID: 046d:0825
    class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.2.1
    compositor: kwin_x11 driver: X: loaded: modesetting,nouveau,nvidia
    alternate: fbdev,nv,vesa gpu: nvidia display-ID: :0 screens: 1
  Screen-1: 0 s-res: 3840x1200 s-dpi: 93 s-size: 1049x321mm (41.30x12.64")
    s-diag: 1097mm (43.19")
  Monitor-1: DVI-D-0 pos: primary,right res: 1920x1200 hz: 60 dpi: 94
    size: 518x324mm (20.39x12.76") diag: 611mm (24.05") modes: N/A
  Monitor-2: HDMI-0 pos: left res: 1920x1200 hz: 60 dpi: 94
    size: 518x324mm (20.39x12.76") diag: 611mm (24.05") modes: N/A
  Monitor-3: None-1-1 size-res: N/A modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 535.104.05 renderer: NVIDIA GeForce GTX
    1080/PCIe/SSE2 direct-render: Yes
Audio:
  Device-1: NVIDIA GP104 High Definition Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
    bus-ID: 09:00.1 chip-ID: 10de:10f0 class-ID: 0403
  Device-2: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 0b:00.3
    chip-ID: 1022:1457 class-ID: 0403
  Device-3: C-Media CM6631A Audio Processor
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 mode: 2.0 bus-ID: 1-2:2 chip-ID: 0d8c:0004 class-ID: 0300
  Device-4: Logitech Webcam C270 driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-3:4 chip-ID: 046d:0825
    class-ID: 0102 serial: <filter>
  API: ALSA v: k6.5.4-zen2-1-zen status: kernel-api tools: N/A
  Server-1: PipeWire v: 0.3.80 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Qualcomm Atheros AR9285 Wireless Network Adapter driver: ath9k
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 07:00.0
    chip-ID: 168c:002b class-ID: 0280
  IF: wlp7s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: ASUSTeK PRIME B450M-A driver: r8169 v: kernel pcie: gen: 1
    speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 08:00.0 chip-ID: 10ec:8168
    class-ID: 0200
  IF: enp8s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
    v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-8:4
    chip-ID: 0a12:0001 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
    lmp-v: 6 status: discoverable: no pairing: no class-ID: 7c0104
Drives:
  Local Storage: total: 3.41 TiB used: 187.95 GiB (5.4%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Silicon Power
    model: SPCC M.2 PCIe SSD size: 476.94 GiB block-size: physical: 512 B
    logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: H211011a temp: 43.9 C scheme: GPT
  ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
    model: WD20EARX-00PASB0 size: 1.82 TiB block-size: physical: 4096 B
    logical: 512 B speed: 6.0 Gb/s tech: N/A serial: <filter> fw-rev: AB51
    scheme: MBR
  ID-3: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT1000MX500SSD1
    size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 046 scheme: GPT
  ID-4: /dev/sdc maj-min: 8:32 vendor: Kingston model: SUV400S37240G
    size: 223.57 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
    tech: SSD serial: <filter> fw-rev: 96R9 scheme: GPT
Partition:
  ID-1: / raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
    used: 187.95 GiB (39.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 580 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
    used: 187.95 GiB (39.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-4: /var/log raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
    used: 187.95 GiB (39.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-5: /var/tmp raw-size: 476.64 GiB size: 476.64 GiB (100.00%)
    used: 187.95 GiB (39.4%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 15.53 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 16 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 43.8 C mobo: N/A gpu: nvidia temp: 44 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Info:
  Processes: 371 Uptime: 0m wakeups: 0 Memory: total: 16 GiB
  available: 15.53 GiB used: 3.14 GiB (20.2%) Init: systemd v: 254
  default: graphical tool: systemctl Compilers: gcc: 13.2.1 Packages:
  pm: pacman pkgs: 1567 libs: 481 tools: octopi,paru,yay Shell: fish v: 3.6.1
  default: Bash v: 5.1.16 running-in: wezterm-gui inxi: 3.3.29
Garuda (2.6.16-1):
  System install date:     2023-08-06
  Last full system update: 2023-09-24
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:

You can maybe add resolutions with xrandr or something, I can’t remember just now :slight_smile: and not sure for wayland.

1 Like

wlr-randr is an equivalent to xrandr for Wayland that works for wlroots compositors such as Hyprland.
(may work for you too)
As Xwayland has a “read-only” XRandR support, but it cannot send request back to the Wayland compositor, so X11 applications have no control over the output configurations.

Take a look in ~/.local/share/kscreen/, your display ID should be in there and maybe if you add your mode directly in the file it will work.

I had one machine where Wayland would not keep higher resolution, it was listed in System Settings, I could change it, but as soon as the display was turning off and back on, it would lower the res. I added the more with proper X-Y and it fixed the issue.

2 Likes

Bug likely driver related.

Display configuration files look proper.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.