Issue with screen resolution (post 2025-12-08 update)

Support Graphics & Display
1

After the Gnome 49 update my login screen & desktop were zoomed 130%.
I was able to change the overall system in settings > display > scale & set it back to 100%

But the login screen remains at 130%, how to correct that?

Only the login screen is affected, not the lockscreen.

I’m running a Thinkpad X1 Carbon 6th gen.

$ inxi -zv8
System:
  Kernel: 6.12.62-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=a41bacfe-b970-40c0-9da8-ef09eb54a441 ro quiet
    udev.log_priority=3
  Desktop: GNOME v: 49.2 tk: GTK v: 3.24.51 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 49.2 Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 20KH003BMX v: ThinkPad X1 Carbon 6th
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: LENOVO model: 20KH003BMX v: SDK0J40697 WIN
    serial: <superuser required> part-nu: LENOVO_MT_20KH_BU_Think_FM_ThinkPad
    X1 Carbon 6th uuid: <superuser required> Firmware: UEFI vendor: LENOVO
    v: N23ET76W (1.51 ) date: 04/21/2021
Battery:
  ID-1: BAT0 charge: 39.7 Wh (84.6%) condition: 47/57 Wh (82.3%) power: 5.4 W
    volts: 12.04 min: 11.52 model: SMP 01AV430 type: Li-poly serial: <filter>
    charging: status: discharging control: start: 70% end: 90% cycles: 700
Memory:
  System RAM: total: 8 GiB available: 7.52 GiB used: 2.76 GiB (36.7%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 8 GiB slots: 2 modules: 2 EC: None
    max-module-size: 4 GiB note: est.
  Device-1: ChannelA-DIMM0 type: LPDDR3 detail: synchronous unbuffered
    (unregistered) size: 4 GiB speed: 2133 MT/s volts: curr: 1 width (bits):
    data: 64 total: 64 manufacturer: Samsung part-no: K4E6E304EB-EGCG
    serial: <filter>
  Device-2: ChannelB-DIMM0 type: LPDDR3 detail: synchronous unbuffered
    (unregistered) size: 4 GiB speed: 2133 MT/s volts: curr: 1 width (bits):
    data: 64 total: 64 manufacturer: Samsung part-no: K4E6E304EB-EGCG
    serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i7-8550U bits: 64 type: MT MCP arch: Coffee Lake
    gen: core 8 level: v3 note: check built: 2017 process: Intel 14nm family: 6
    model-id: 0x8E (142) stepping: 0xA (10) microcode: 0xF6
  Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
    smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
    desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
  Speed (MHz): avg: 400 min/max: 400/4000 scaling: driver: intel_pstate
    governor: powersave cores: 1: 400 2: 400 3: 400 4: 400 5: 400 6: 400 7: 400
    8: 400 bogomips: 32012
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_perfmon art avx avx2 bmi1 bmi2 bts clflush
    clflushopt cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
    dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
    fsgsbase fxsr ht hwp hwp_act_window hwp_epp hwp_notify ibpb ibrs ida
    intel_pt invpcid lahf_lm lm mca mce md_clear mmx monitor movbe mpx msr
    mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq pdcm pdpe1gb pebs pge
    pln pni popcnt pse pse36 pti pts rdrand rdseed rdtscp rep_good sdbg sep
    sgx smap smep ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2
    tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi vpid x2apic
    xgetbv1 xsave xsavec xsaveopt xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: KVM: Split huge pages
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS; IBPB: conditional; STIBP: conditional;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds mitigation: Microcode
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel UHD Graphics 620 vendor: Lenovo driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
    empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:5917
    class-ID: 0300
  Device-2: IMC Networks Integrated Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:3 chip-ID: 13d3:56b2
    class-ID: 0e02
  Display: wayland server: X.org v: 1.21.1.21 with: Xwayland v: 24.1.9
    compositor: gnome-shell driver: X: loaded: intel dri: i965 gpu: i915
    display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x06df built: 2016 res: 1920x1080
    dpi: 158 gamma: 1.2 chroma: red: x: 0.639 y: 0.329 green: x: 0.306 y: 0.608
    blue: x: 0.145 y: 0.055 white: x: 0.314 y: 0.329
    size: 309x173mm (12.17x6.81") diag: 354mm (13.9") ratio: 16:9
    modes: 1920x1080
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.3.1-arch1.2
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 620 (KBL
    GT2) device-ID: 8086:5917 memory: 7.35 GiB unified: yes display-ID: :0.0
  API: Vulkan v: 1.4.328 layers: 6 device: 0 type: integrated-gpu name: Intel
    UHD Graphics 620 (KBL GT2) driver: mesa intel v: 25.3.1-arch1.2
    device-ID: 8086:5917 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo x11: xdpyinfo,xprop
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3
    chip-ID: 8086:9d71 class-ID: 0403
  API: ALSA v: k6.12.62-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.4.9 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: Intel Ethernet I219-V vendor: Lenovo driver: e1000e v: kernel
    port: N/A bus-ID: 00:1f.6 chip-ID: 8086:15d8 class-ID: 0200
  IF: enp0s31f6 state: down mac: <filter>
  Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie:
    gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0 chip-ID: 8086:24fd
    class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface driver: btusb v: 0.8 type: USB
    rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-7:2 chip-ID: 8087:0a2b
    class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 4.2
    lmp-v: 8 status: discoverable: no pairing: no class-ID: 6c010c
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 238.47 GiB used: 133.01 GiB (55.8%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Intel model: SSDPEKKF256G8L
    size: 238.47 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: L08P temp: 27.9 C scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 156.25 GiB size: 152.74 GiB (97.75%)
    used: 132.97 GiB (87.1%) fs: ext4 dev: /dev/nvme0n1p5 maj-min: 259:5
    label: N/A uuid: a41bacfe-b970-40c0-9da8-ef09eb54a441
  ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
    used: 41 MiB (16.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
    label: SYSTEM uuid: B45D-2893
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: file size: 3 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Unmounted:
  ID-1: /dev/nvme0n1p2 maj-min: 259:2 size: 16 MiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-2: /dev/nvme0n1p3 maj-min: 259:3 size: 80.98 GiB fs: bitlocker
    label: N/A uuid: baa3cc88-01c3-4821-b69b-5b0329a5c241
  ID-3: /dev/nvme0n1p4 maj-min: 259:4 size: 1000 MiB fs: ntfs
    label: WinRE_DRV uuid: 105861545861399C
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 1-7:2 info: Intel Bluetooth wireless interface type: bluetooth
    driver: btusb interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1
    mode: 1.1 power: 100mA chip-ID: 8087:0a2b class-ID: e001
  Device-2: 1-8:3 info: IMC Networks Integrated Camera type: video
    driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 500mA chip-ID: 13d3:56b2 class-ID: 0e02
  Device-3: 1-9:4 info: Synaptics Metallica MIS Touch Fingerprint Reader
    type: <vendor specific> driver: N/A interfaces: 1 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
    chip-ID: 06cb:009a class-ID: ff00 serial: <filter>
  Hub-2: 2-0:1 info: super-speed hub ports: 6 rev: 3.0
    speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
    class-ID: 0900
  Device-1: 2-3:2 info: Realtek USB3.0-CRW type: mass storage
    driver: usb-storage interfaces: 1 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s)
    lanes: 1 mode: 3.2 gen-1x1 power: 800mA chip-ID: 0bda:0328 class-ID: 0806
    serial: <filter>
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 2 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-4: 4-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 34.0 C pch: 37.0 C mobo: N/A
  Fan Speeds (rpm): fan-1: 0
Repos:
  Packages: pm: pacman pkgs: 2109 libs: 509 tools: pamac,yay pm: flatpak
    pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 277
  1: cpu: 13.8% command: firefox pid: 4495 mem: 333.5 MiB (4.3%)
  2: cpu: 8.6% command: firefox pid: 3974 mem: 571.5 MiB (7.4%)
  3: cpu: 3.1% command: gnome-shell pid: 2385 mem: 389.3 MiB (5.0%)
  4: cpu: 2.7% command: firefox pid: 4536 mem: 290.0 MiB (3.7%)
  5: cpu: 2.2% command: firefox pid: 4434 mem: 327.0 MiB (4.2%)
  Memory top: 5 of 277
  1: mem: 571.5 MiB (7.4%) command: firefox pid: 3974 cpu: 8.6%
  2: mem: 389.3 MiB (5.0%) command: gnome-shell pid: 2385 cpu: 3.1%
  3: mem: 333.5 MiB (4.3%) command: firefox pid: 4495 cpu: 13.8%
  4: mem: 327.0 MiB (4.2%) command: firefox pid: 4434 cpu: 2.2%
  5: mem: 320.9 MiB (4.1%) command: firefox pid: 4652 cpu: 2.0%
Info:
  Processes: 277 Power: uptime: 40m states: freeze,mem,disk suspend: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
    image: 2.99 GiB services: gsd-power,upowerd Init: systemd v: 258
    default: graphical tool: systemctl
  Compilers: clang: 21.1.6 gcc: 15.2.1 Shell: Bash v: 5.3.8
    running-in: tmux: inxi: 3.3.40
3

Your post has been moved to a dedicated topic.

Hi @Luddd3

Note that adding your own Support issue to that of another member’s topic is discouraged in this forum, regardless of any apparent similarities.

See Forum Rules: Thread Hijacking

Instead, please edit your first post in this topic to include a detailed description of your issue so that others have a better understanding of the problem. :eyes:

Include also your system information as described (below) to allow others to identify possible contributors. :eyes:

Note also that all code or command output should be displayed as pre-formatted text according to forum guidelines. :eyes:

A relevant link is provided (below) that shows how to do this in a Discourse-based forum – discover also the differences between “quoted” and “pre-formatted” text, for example.

Take some time to search through recent forum topics as similar issues have already been reported and subsequently resolved.

Lastly, please do read through the entire Stable Update 2025-12-08 announcement thread for anything that might be related – in particular, the Known Issues and Solutions section:

Note that the thread has been temporarily unlisted to allow you time to make the aforementioned edits and add needed details, and will be relisted when ready.

I’m sure someone will help when they are able, and once you have provided some useful information.

Regards.

What follows is from a standard template.

Welcome to the Manjaro community

As a new or infrequent forum user, please take some time to familiarise yourself with forum requirements, and the many ways to use the forum to your benefit.

Note: By virtue of using the Manjaro forum you acknowledge and agree to follow Rules and Guidelines outlined; so, you really should read them:

Required Reading
Highly Recommended

Work with us, not against us

It is important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem. Please also be prepared to provide output from commands if/when asked.

Simply waiting for others to ask you questions is counter-productive – typically, nobody has a :crystal_ball: at their disposal – and your clear, concise and accurate input is often relied upon in order to help you.

Please help others to make informed suggestions based on information you provide.

System Information

While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly; :eyes:

Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:

Suggested inxi command (use either):
inxi -zv8 (short-form)
inxi --filter --verbosity=8 (long-form)
inxi man pages (manual)
If running `inxi` within a `chroot` environment
  • Add --color=0 to the long-form command, or…
  • Change the short-form command to inxi -zv8c0
Your privacy is respected

Update Announcements

Technical Resources

4

The majority of issues with screen resolution is caused by Nvidia.

The x1 gen 6 GPU is Intel UHD620 Graphics. Intel graphics is provided in kernel using i915 or xe driver.

Which it is for your system - will depend on your Intel hardware - I think I saw once on Intel’s web that core and vcore 6.gen and newer has support for Iris Xe - but please verify your hardware.

However - you may want to check if you have kms enabled in /etc/mkinitcpio.conf HOOKS=(... kms ...) array.

If you have kms - you may try getting it to load earlier by adding i915 to the MODULES=(... i915 ...) array.

More info Intel graphics - ArchWiki

If you system is supported by the newer driver you may exhange i915 for xe in the MODULES= array.

One of my testing systems is a Tuxedo Infinitibookpro with Intel i7-13700H cpu and a screen size of 2880x1800 - no problem at all.

5

Thank you for your reply. i915 and kms was already included in MODULES and HOOKS.

Excerpts from /etc/mkinitcpio.conf

MODULES=(i915)
HOOKS=(base udev autodetect modconf kms block keyboard keymap filesystems)

Any other ideas?

7

It may not be anything to do with the issue, but you seem to be missing the microcode hook, which should be located between autodetect & modconf.

microcode

Prepends an uncompressed initramfs image with early microcode update files for Intel and AMD processors. Uses microcode files from /usr/lib/firmware/amd-ucode/ and /usr/lib/firmware/intel-ucode/ if they are available or extracts /boot/amd-ucode.img and /boot/intel-ucode.img otherwise.

If the autodetect hook runs before this hook, it will only add early microcode update files for the processor of the system the image is built on.

The use of this hook replaces the now deprecated --microcode flag, and the microcode option in the preset files. This also allows you to drop the microcode initrd lines from your boot configuration as they are now packed together with the main initramfs image.

The hook was added a year or two ago, so if your system is older than that, there should have been a .pacnew file created with the change.

3 Likes
8

I added the hook. Unfortunately, it didn’t fix the issue, but thank you anyway!

9

After adding the hooks you ran

$ sudo mkinitcpio -P

and rebooted to enable the change, right?

3 Likes
10

Yes, I did :+1: