Screen size exceeds physical display limits

just_created · 19 October 2025 04:44

Hi, I’m on a fresh install of manjaro w/ xfce and there are some problems with my desktop screen.

To put it simply, it looks like system thinks my screen is bigger than it actually is, making it so that the desktop exceeds the screen boundaries being bigger than my actual screen.

I don’t think it has anything to do with the screen resolution, as I tried every one of them and nothing worked, scale didn’t help either.

I started raising an issue in the Xfce forums, as it looked like the DE was at fault, but then I booted up a live USB stick with KDE plasma and the same issue was present, so I figured it was better to ask here.

I am using an Sony Vaio VPCF115FM (I will donate it to the museum once I’m done with it).

my-user% inxi -G
Graphics:
  Device-1: NVIDIA GT216M [GeForce GT 330M] driver: nouveau v: kernel
  Device-2: Suyin Sony Visual Communication Camera driver: uvcvideo
    type: USB
  Display: x11 server: X.org v: 1.21.1.18 driver: X: loaded: modesetting
    dri: nouveau gpu: nouveau resolution: 2048x1536~60Hz
  API: EGL v: 1.5 drivers: nouveau,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 25.2.3-arch1.2
    renderer: NVA5
  Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings
    x11: xprop,xrandr


my-user% xrandr
Screen 0: minimum 320 x 200, current 2048 x 1536, maximum 8192 x 8192
LVDS-1 connected 2048x1536+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
   2048x1536     59.99*+
   1920x1440     60.00  
   1856x1392     60.01  
   1792x1344     60.01  
   2048x1152     59.99    59.98    59.90    59.91  
   1920x1200     59.95    59.88    59.95  
   1920x1080     60.01    59.97    60.00    59.96    59.93  
   1600x1200     60.00    59.95  
   1680x1050     60.00    59.95    59.88  
   1400x1050     59.98    60.00  
   1600x900      59.99    59.94    59.95    59.82  
   1280x1024     59.95    60.02  
   1400x900      59.96    59.88  
   1280x960      60.00    59.99  
   1440x810      60.00    59.97  
   1368x768      59.88    59.85  
   1280x800      59.99    59.97    59.81    59.91  
   1152x864      59.97  
   1280x720      60.00    59.99    59.86    59.74  
   1024x768      60.04    60.00    59.95  
   960x720       60.00  
   928x696       60.05  
   896x672       60.01  
   1024x576      59.95    59.96    59.90    59.82  
   960x600       59.93    60.00  
   960x540       59.96    59.99    59.63    59.82  
   800x600       60.00    60.32    59.96    56.25  
   840x525       60.01    59.88  
   864x486       59.92    59.57  
   700x525       59.98  
   800x450       59.95    59.82  
   640x512       60.02  
   700x450       59.96    59.88  
   640x480       60.00    59.94    59.94  
   720x405       59.51    58.99  
   720x400       59.97  
   684x384       59.88    59.85  
   640x400       59.88    59.98    59.96  
   640x360       59.86    59.83    59.84    59.32  
   640x350       59.84  
   512x384       60.00  
   512x288       60.00    59.92  
   480x270       59.63    59.82  
   400x300       60.32    56.34  
   432x243       59.92    59.57  
   320x240       60.05  
   360x202       59.51    59.13  
   320x180       59.84    59.32  
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)

I appreciate any help with this issue, as it is really annoying no being able to access the whole screen.

just_created · 19 October 2025 04:47

To better illustrate my issue, in the link below I maximized a Thunar window of a folder filled with dummy files, everything marked with orange is out of bounds. And even though I can’t see it, I’m still able to interact with it.

https://imgur.com/TyQKGNT

soundofthunder · 19 October 2025 06:35

You might try switching to using Wayland (dropdown, bottom/ left of the SDDM login screen) to see if that improves things.

However, as the problem seems to manifest on both machines it might be something else. Perhaps search the forum to see if you can find others with a similar issue.

I see nothing listed under Known Issues and Solutions that seems to apply.

Please provide system information as described (below) so that others might identify any possible contributors to the issue, otherwise.

Regards.

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.

To that end, links are provided (below) - Please use them.

Be prepared to provide outputs from various commands when asked. It’s equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.

Waiting for others to blindly ask questions can be counter-productive – typically, nobody has a at their disposal – Instead, please help others to make informed suggestions, based on information you provide.

Update Announcements

The Update Announcements contain important information and a Known Issues and Solutions section that should generally be checked before posting a request for support.

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;

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

inxi --filter --verbosity=8

or the short form (preferred):

inxi -zv8

inxi man pages (Arch Manual)

Highly Recommended

Technical Resources

Required Reading

linux-aarhus · 19 October 2025 07:12

just_created:

Graphics:
  Device-1: NVIDIA GT216M [GeForce GT 330M] driver: nouveau v: kernel

...

  Display: x11 server: X.org v: 1.21.1.18 driver: X: loaded: modesetting
    dri: nouveau gpu: nouveau resolution: 2048x1536~60Hz

Screen and display is two different objects.

The display is the physical object - the screen is generated by the software - the display driver.

Try setting the zoom factor to a fraction below 1.0 or create/edit a monitor configuration file in /etc/X11/xorg.conf.d - one may already exist as /etc/X11/xorg.conf.

You may be able to learn something useful from the Arch wiki on Xorg and monitor settings Xorg - ArchWiki

nikgnomic · 19 October 2025 08:20

Sony Vaio VPC-F115FM specifications and reviews

Display Sony VAIO VPC-F115FM

Display: 16.4-inch, 1920x1080, Widescreen

Graphics Controller: discrete

Graphics Chipset Model: NVIDIA GeForce GT 330M

Graphics Memory: 1024 MB

just_created · 21 October 2025 01:35

Hi, I will try to change to wayland but as the dropdown is on the bottom left (and I can’t see it) it may be a little more challenging

output of inxi -zv8

System:
  Kernel: 6.12.48-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=650bdfa1-92e4-4c21-b1c3-270ec3091698 rw quiet splash apparmor=1
    security=apparmor udev.log_priority=3
  Desktop: Xfce v: 4.20.1 tk: Gtk v: 3.24.48 wm: xfwm4 v: 4.20.0
    with: xfce4-panel tools: xfce4-screensaver vt: 7 dm: LightDM v: 1.32.0
    Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: Sony product: VPCF115FM v: C603CKVR
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Sony model: VAIO serial: <superuser required>
    uuid: <superuser required> BIOS: American Megatrends v: R0250Y6
    date: 12/07/2009
Battery:
  ID-1: BAT0 charge: 13 Wh (77.2%) condition: 16.8/57.2 Wh (29.4%)
    power: 786.4 W volts: N/A min: 122.3 model: Sony Corp. type: Li-ion
    serial: N/A charging: status: charging cycles: N/A
Memory:
  System RAM: total: 16 GiB available: 15.6 GiB used: 4.64 GiB (29.7%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: N/A slots: 2 modules: 2 EC: None max-module-size: N/A
  Device-1: SODIMM1 type: DDR3 detail: N/A size: 8 GiB speed: N/A volts: N/A
    width (bits): data: 64 total: 64 manufacturer: N/A part-no: N/A serial: N/A
  Device-2: SODIMM2 type: DDR3 detail: N/A size: 8 GiB speed: N/A volts: N/A
    width (bits): data: 64 total: 64 manufacturer: N/A part-no: N/A serial: N/A
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core i7 Q 720 bits: 64 type: MT MCP arch: Nehalem
    gen: core 1 level: v2 built: 2008-10 process: Intel 45nm family: 6
    model-id: 0x1E (30) stepping: 5 microcode: 0xA
  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: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 931 min/max: 933/1600 boost: enabled scaling:
    driver: acpi-cpufreq governor: schedutil cores: 1: 931 2: 931 3: 931 4: 931
    5: 931 6: 931 7: 931 8: 931 bogomips: 25544
  Flags: acpi aperfmperf apic arch_perfmon bts clflush cmov constant_tsc
    cpuid cx16 cx8 de ds_cpl dtes64 dtherm dts ept est flexpriority flush_l1d
    fpu fxsr ht ibpb ibrs ida lahf_lm lm mca mce mmx monitor msr mtrr
    nonstop_tsc nopl nx pae pat pbe pdcm pebs pge pni popcnt pse pse36 pti
    rdtscp rep_good sep smx ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall
    tm tm2 tpr_shadow tsc vme vmx vnmi vpid xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  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 status: Vulnerable: Clear CPU buffers attempted, no microcode;
    SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data status: Unknown: No mitigations
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  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: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape status: Not affected
Graphics:
  Device-1: NVIDIA GT216M [GeForce GT 330M] vendor: Sony driver: nouveau
    v: kernel non-free: series: 340.xx status: legacy (EOL~2019-12-xx) last:
    release: 340.108 kernel: 5.4 xorg: 1.20 arch: Tesla process: 40-80nm
    built: 2006-2013 pcie: gen: 2 speed: 5 GT/s lanes: 16 ports:
    active: LVDS-1 empty: HDMI-A-1,VGA-1 bus-ID: 01:00.0 chip-ID: 10de:0a29
    class-ID: 0300 temp: 67.0 C
  Device-2: Suyin Sony Visual Communication Camera driver: uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.2:3
    chip-ID: 064e:2100 class-ID: 0e02 serial: <filter>
  Display: x11 server: X.org v: 1.21.1.18 compositor: xfwm4 v: 4.20.0
    driver: X: loaded: modesetting alternate: fbdev,vesa dri: nouveau
    gpu: nouveau display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2048x1536 s-size: <missing: xdpyinfo>
  Monitor-1: LVDS-1 res: mode: 2048x1536 hz: 60 scale: 100% (1) size: N/A
    modes: 2048x1536, 1920x1200, 1920x1080, 1600x1200, 1680x1050, 1400x1050,
    1280x1024, 1280x960, 1152x864, 1024x768, 800x600, 640x480, 720x400,
    640x400, 640x350
  API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
    device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
    drv: nouveau inactive: wayland
  API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 25.2.3-arch1.2 glx-v: 1.4
    direct-render: yes renderer: NVA5 device-ID: 10de:0a29 memory: 987.3 MiB
    unified: no
  Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings
    x11: xprop,xrandr
Audio:
  Device-1: Intel 5 Series/3400 Series High Definition Audio vendor: Sony
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:3b56
    class-ID: 0403
  Device-2: NVIDIA GT216 HDMI Audio vendor: Sony driver: snd_hda_intel
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.1
    chip-ID: 10de:0be2 class-ID: 0403
  API: ALSA v: k6.12.48-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.8 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Qualcomm Atheros AR9287 Wireless Network Adapter vendor: Foxconn
    driver: ath9k v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1
    bus-ID: 02:00.0 chip-ID: 168c:002e class-ID: 0280
  IF: wlp2s0 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: dynamic noprefixroute scope: global
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Marvell 88E8057 PCI-E Gigabit Ethernet vendor: Sony driver: sky2
    v: 1.30 pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: a000 bus-ID: 04:00.0
    chip-ID: 11ab:4380 class-ID: 0200
  IF: enp4s0 state: down mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Message: No bluetooth data found.
Logical:
  Message: No logical block device data found.
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 476.94 GiB used: 211.57 GiB (44.4%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/sda maj-min: 8:0 model: P3-512 size: 476.94 GiB block-size:
    physical: 512 B logical: 512 B speed: 3.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 117D scheme: MBR
  Optical-1: /dev/sr0 vendor: ■■■■■■■■ model: BD-CMB UJ141AS rev: 1.00
    dev-links: cdrom
  Features: speed: 62 multisession: yes audio: yes dvd: yes
    rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
Partition:
  ID-1: / raw-size: 107.42 GiB size: 105.18 GiB (97.91%) used: 7.88 GiB (7.5%)
    fs: ext4 dev: /dev/sda7 maj-min: 8:7 label: N/A
    uuid: 650bdfa1-92e4-4c21-b1c3-270ec3091698
  ID-2: /home raw-size: 223.02 GiB size: 218.46 GiB (97.96%)
    used: 203.69 GiB (93.2%) fs: ext4 dev: /dev/sda5 maj-min: 8:5 label: N/A
    uuid: cf19a8aa-d16d-4849-bb39-83f5a81f2df5
Swap:
  Alert: No swap data was found.
Unmounted:
  ID-1: /dev/sda1 maj-min: 8:1 size: 50 MiB fs: ntfs label: System Reserved
    uuid: 782E53342E52EB20
  ID-2: /dev/sda2 maj-min: 8:2 size: 145.93 GiB fs: ntfs label: N/A
    uuid: 185E61B35E6189F8
  ID-3: /dev/sda3 maj-min: 8:3 size: 516 MiB fs: ntfs label: N/A
    uuid: B6E0A726E0A6EBB5
  ID-4: /dev/sda4 maj-min: 8:4 size: 1 KiB fs: <superuser required>
    label: N/A uuid: N/A
  ID-5: /dev/sda6 maj-min: 8:6 size: 8.3 MiB fs: ext4 label: N/A
    uuid: 445b5d30-95ad-499a-8b96-21325802885a
USB:
  Hub-1: 1-0:1 info: full speed or root hub 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-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:0020
    class-ID: 0900
  Device-1: 1-1.2:3 info: Suyin Sony Visual Communication Camera type: video
    driver: uvcvideo interfaces: 2 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 100mA chip-ID: 064e:2100 class-ID: 0e02
    serial: <filter>
  Hub-3: 2-0:1 info: full speed or root hub 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: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:0020
    class-ID: 0900
  Device-1: 2-1.5:4 info: Xenta Game mouse type: keyboard,mouse
    driver: hid-generic,usbhid interfaces: 2 rev: 1.1 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 1d57:ffa8 class-ID: 0301
Sensors:
  System Temperatures: cpu: 72.0 C mobo: N/A gpu: nouveau temp: 67.0 C
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1139 libs: 327 tools: pamac,yay pm: flatpak
    pkgs: 0
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirrors2.manjaro.org/stable/$repo/$arch
    2: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
    3: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
    4: https://ipng.mm.fcix.net/manjaro/stable/$repo/$arch
    5: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    6: https://manjaro.c3sl.ufpr.br/stable/$repo/$arch
    7: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
    8: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 266
  1: cpu: 8.8% command: firefox pid: 1166 mem: 778.2 MiB (4.8%)
  2: cpu: 4.9% command: firefox pid: 1785 mem: 605.8 MiB (3.7%)
  3: cpu: 3.1% command: xfce4-terminal pid: 13245 mem: 56.9 MiB (0.3%)
  4: cpu: 2.1% command: firefox pid: 12789 mem: 353.2 MiB (2.2%)
  5: cpu: 1.9% command: firefox pid: 3730 mem: 853.1 MiB (5.3%)
  Memory top: 5 of 266
  1: mem: 949.9 MiB (5.9%) command: firefox pid: 1841 cpu: 1.5%
  2: mem: 936.4 MiB (5.8%) command: firefox pid: 1895 cpu: 1.6%
  3: mem: 853.1 MiB (5.3%) command: firefox pid: 3730 cpu: 1.9%
  4: mem: 778.2 MiB (4.8%) command: firefox pid: 1166 cpu: 8.8%
  5: mem: 605.8 MiB (3.7%) command: firefox pid: 1785 cpu: 4.9%
Info:
  Processes: 266 Power: uptime: 9h 44m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 6.21 GiB services: upowerd,xfce4-power-manager
    Init: systemd v: 257 default: graphical tool: systemctl
  Compilers: gcc: 15.2.1 Shell: Zsh v: 5.9 running-in: xfce4-terminal
    inxi: 3.3.39

If changing to wayland doesn’t solve the issue, I will dabble with the zoom configurations.
And to be clear with the terminology, now that you have explained it, my problem is that the screen is bigger than the display.

Teo · 21 October 2025 03:54

Did you try setting the resolution to the native 1920x1080 as suggested above?

just_created · 21 October 2025 13:13

If I try to set the resolution to 1920x1080, the problem persists and I don’t think that you can tell based on the image, but everything becomes a little stretched (especially in the vertical direction)
Again, in the image below, blue show everything that is out of the display and is not visible.

It seems that the system truly believes my display is 2048x1536 and is forcing the screen to match this resolution

just_created · 21 October 2025 13:54

Ok, I did some testing with my two live usb devices

One has manjaro 25 xfce (I used this one to install my current system)
And the other has manjaro 25 KDE

On both, if I boot with open source drivers, the problem is reproducible, if I boot with proprietary drivers, the problem disappears. Therefore, either a driver is missing, or one open source driver can’t generalize to my hardware configs.

I will try to reinstall my system, if the problem disappears, I will edit this message and mark it as solved (even though the truest solution would be implement/modify a driver, but I figure it’s too much to ask).

Aragorn · 21 October 2025 14:07

You are overlooking something…: Xfce defaults to X11, and Plasma defaults to Wayland. The proprietary drivers — especially the older ones — work best with X11. Only the newest proprietary drivers support Wayland.

Teo · 21 October 2025 15:39

If it is only the nvidia driver, you can change it with mwhd. You do not need reinstalling.

nikgnomic · 21 October 2025 17:33

Use inxi -G to verify display drivers and resolution

just_created · 23 October 2025 00:22

Hmmm, I understand, but I don’t think these defaults have something to do with the issue as both Xfce (with X11) and Plasma (with Wayland) worked if I booted with proprietary drivers

Summarizing in case it was not clear:
Xfce with open source drivers: Problem does reproduce
Xfce with proprietary drivers: Problem does not reproduce

Plasma with open source drivers: Problem does reproduce
Plasma with proprietary drivers: Problem does not reproduce

I also tried to boot endeavor (also plasma), as it’s also Arch based and

EOS with open source drivers: Problem does reproduce
EOS with proprietary drivers: Problem does not reproduce

So I really think it is something related to a missing driver now

nikgnomic · 23 October 2025 09:56

Xfce does not support Wayland or XWayland

Xfce 4.20 tour – Xfce

Wayland

Important Notice: Please be aware that the Wayland support in Xfce 4.20 is experimental. It is recommended for advanced users only, as you may encounter bugs and experience incomplete functionality. Proceed with caution!

XWayland will not be required to run any of the ported Xfce components.

Plans are underway to add Wayland support to Xfwm4 while preserving its existing X11 functionality. However, such a restructurization will be a major effort and we cannot tell yet when/if it will be done, so please don’t hold your breath waiting for it.

For few components and multiple features, it was not possible to port them to Wayland, partly because there are no standardized Wayland protocols available yet to provide the required services:

Some other Xfce components don’t run at all on Wayland:

More detailed info on the current Wayland status can be found on our Wayland roadmap.

For Xfce there is only one option available

Verified in previous post

just_created:

System:

  Desktop: Xfce v: 4.20.1  

Graphics:
  Device-1: NVIDIA GT216M [GeForce GT 330M] vendor: Sony driver: nouveau
 
  Display: x11 server: X.org v: 1.21.1.18 compositor: xfwm4 v: 4.20.0
    driver: X: loaded: modesetting alternate: fbdev,vesa dri: nouveau
    gpu: nouveau display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2048x1536

Please post more information to verify this solution

inxi -Ga

just_created · 24 October 2025 02:37

Oh, right, I think I get it what you all are saying now, I was focusing on the wrong details.

Well, about inix :

#live USB w/ proprietary drivers
user% inxi -Ga
Graphics:
  Device-1: NVIDIA GT216M [GeForce GT 330M] vendor: Sony driver: N/A
    alternate: nouveau non-free: series: 340.xx status: legacy (EOL~2019-12-xx)
    last: release: 340.108 kernel: 5.4 xorg: 1.20 arch: Tesla process: 40-80nm
    built: 2006-2013 pcie: gen: 2 speed: 5 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:0a29 class-ID: 0300
  Device-2: Suyin Sony Visual Communication Camera driver: uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.2:3
    chip-ID: 064e:2100 class-ID: 0e02 serial: CN031B-R876-MI01-VS-R03.00.00
  Display: x11 server: X.org v: 1.21.1.18 compositor: xfwm4 v: 4.20.0
    driver: X: loaded: modesetting,nouveau alternate: fbdev,nv,vesa gpu: N/A
    display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 1024x768 s-size: <missing: xdpyinfo>
  Monitor-1: Unknown-1 mapped: None-1 res: mode: 1024x768 hz: 60
    scale: 100% (1) size: N/A modes: 1024x768
  API: EGL v: 1.5 platforms: device: 0 drv: swrast surfaceless: drv: swrast
    x11: drv: swrast inactive: gbm,wayland
  API: OpenGL v: 4.5 vendor: mesa v: 25.2.1-manjaro1.2 glx-v: 1.4
    direct-render: yes renderer: llvmpipe (LLVM 20.1.8 128 bits)
    device-ID: ffffffff:ffffffff memory: 15.23 GiB unified: yes
  Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings
    x11: xprop,xrandr

#live USB w/o proprietary drivers
Graphics:
  Device-1: NVIDIA GT216M [GeForce GT 330M] vendor: Sony driver: nouveau
    v: kernel non-free: series: 340.xx status: legacy (EOL~2019-12-xx) last:
    release: 340.108 kernel: 5.4 xorg: 1.20 arch: Tesla process: 40-80nm
    built: 2006-2013 pcie: gen: 2 speed: 5 GT/s lanes: 16 ports:
    active: LVDS-1 empty: HDMI-A-1,VGA-1 bus-ID: 01:00.0 chip-ID: 10de:0a29
    class-ID: 0300 temp: 69.0 C
  Device-2: Suyin Sony Visual Communication Camera driver: uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.2:3
    chip-ID: 064e:2100 class-ID: 0e02 serial: CN031B-R876-MI01-VS-R03.00.00
  Display: x11 server: X.org v: 1.21.1.18 compositor: xfwm4 v: 4.20.0
    driver: X: loaded: modesetting alternate: fbdev,vesa dri: nouveau
    gpu: nouveau display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2048x1536 s-size: <missing: xdpyinfo>
  Monitor-1: LVDS-1 res: mode: 2048x1536 hz: 60 scale: 100% (1) size: N/A
    modes: max: 2048x1536 min: 640x350
  API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
    device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
    drv: nouveau inactive: wayland
  API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 25.2.1-manjaro1.2
    glx-v: 1.4 direct-render: yes renderer: NVA5 device-ID: 10de:0a29
    memory: 987.3 MiB unified: no
  Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings
    x11: xprop,xrandr

#Current System, installed via an live USB w/ proprietary drivers
Graphics:
  Device-1: NVIDIA GT216M [GeForce GT 330M] vendor: Sony driver: nouveau
    v: kernel non-free: series: 340.xx status: legacy (EOL~2019-12-xx) last:
    release: 340.108 kernel: 5.4 xorg: 1.20 arch: Tesla process: 40-80nm
    built: 2006-2013 pcie: gen: 2 speed: 5 GT/s lanes: 16 ports:
    active: LVDS-1 empty: HDMI-A-1,VGA-1 bus-ID: 01:00.0 chip-ID: 10de:0a29
    class-ID: 0300 temp: 76.0 C
  Device-2: Suyin Sony Visual Communication Camera driver: uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-1.2:3
    chip-ID: 064e:2100 class-ID: 0e02 serial: CN031B-R876-MI01-VS-R03.00.00
  Display: x11 server: X.org v: 1.21.1.18 compositor: xfwm4 v: 4.20.0
    driver: X: loaded: modesetting alternate: fbdev,vesa dri: nouveau
    gpu: nouveau display-ID: :0.0 note: <missing: xdpyinfo/xrandr>
  Monitor-1: LVDS-1 size-res: N/A modes: max: 2048x1536 min: 640x350
  API: EGL v: 1.5 hw: drv: nvidia nouveau platforms: device: 0 drv: nouveau
    device: 1 drv: swrast gbm: drv: nouveau surfaceless: drv: nouveau x11:
    drv: nouveau inactive: wayland
  API: OpenGL v: 4.5 compat-v: 3.3 vendor: mesa v: 25.2.3-arch1.2 glx-v: 1.4
    direct-render: yes renderer: NVA5 device-ID: 10de:0a29 memory: 987.3 MiB
    unified: no
  Info: Tools: api: eglinfo,glxinfo de: xfce4-display-settings x11: xprop

Kostiantyn · 24 October 2025 18:52

Yes, it’s most likely a driver issue. However, I’d suggest trying the xrandr command to change your screen resolution, since GUI settings can be limited, but xrandr can force any mode the driver supports.

You can run xrandr in the terminal to see your screen (remember its name) and the resolutions it supports. Then you can try:

xrandr --output <put_here_your_screen> --mode 1920x1080

Make sure to use the exact names and supported resolutions when running the command

If you want more information about xrandr I will provide a link to the Arch Wiki: xrandr - ArchWiki

just_created · 27 October 2025 16:38

Yeah, I tried that again and its no use. I see the same cropped screen but with a worse perceived resolution

The thing is, if I set the resolution to the correct 1920x1080, the screen is stretched to fit the 2048x1536 resolution while having only 1920x1080 pixels. It is as if you initially have the pink area, but then have to make it cover the whole blue area. Any other resolution configurations have the same problem, they are stretched to the blue area because (I assume) the driver is certain that my laptop display is 2048x1536.

I also tried to using xrandr --transform, but the scaling options have a similar effect to setting a different resolution.

just_created · 27 October 2025 17:42

Aaaand after fiddling a bit with xrandr --panning I thing I solved my main problem , the screen being within bounds.

The following commands have to be ran in this sequence for it to work

#!/bin/bash
xrandr --output LVDS-1 --mode 2048x1536 --panning 2048x1536
xrandr --output LVDS-1 --mode 2048x1536 --panning 1920x1080
xrandr --output "LVDS-1" --fb 1920x1080

(most of this was found on here)

To finish, I would like this commands to be ran on startup, reading through Autostarting I think the most appropriated option “On XOrg Startup” as it is important to me that the greeter (lightdm-gtk-greeter) is also using the correct cropped/panned screen.

To achieve this, I put the above commands on ~/.xprofile and restarted my laptop, but nothing really happened. Do Y’all know what I may be missing now?

Kostiantyn · 27 October 2025 20:35

Do Y’all know what I may be missing now?

I think this article from the Arch Wiki ( LightDM - ArchWiki ) might help in your case, especially the explanations starting from section 5, which cover LightDM configuration details

just_created · 28 October 2025 14:58

Okay, good news and bad news too I guess.

At first I tried many options and made lightdm be stuck on an boot loop (even the tty’s were affected somehow), luckily I was able to reverted everything back to normal and test one option at a time.

First, I retried putting everything on ~/.xprofile and it didn’t work, to be sure the file was being executed, I put some prints to systemd with journalctl, and the file did execute, but no difference to be seen.

Then, I edited /etc/lightdm/lightdm.conf and pointed to a script with the exact same contents withdisplay-setup-script=/home/myusername/fix_screen.sh. And it ended up working!

But then after unlocking the greeter the screen went back to the wrong size

journalctl | grep lightdm

out 28 11:17:17 myusername lightdm[974]: pam_unix(lightdm:session): session closed for user myusername
out 28 11:17:18 myusername systemd[1]: lightdm.service: Deactivated successfully.
out 28 11:17:18 myusername systemd[1]: lightdm.service: Consumed 24.404s CPU time, 118.8M memory peak.
out 28 11:17:52 myusername lightdm[919]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=964) by (uid=0)
out 28 11:17:52 myusername systemd-logind[750]: New session c1 of user lightdm.
out 28 11:17:52 myusername (systemd)[926]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[lightdm] ruser=[<unknown>] rhost=[<unknown>]
out 28 11:17:52 myusername (systemd)[926]: pam_unix(systemd-user:session): session opened for user lightdm(uid=964) by lightdm(uid=0)
out 28 11:17:52 myusername systemd-logind[750]: New session 1 of user lightdm.
out 28 11:17:52 myusername systemd[1]: Started Session c1 of User lightdm.
out 28 11:18:03 myusername lightdm[973]: gkr-pam: unable to locate daemon control file
out 28 11:18:03 myusername lightdm[973]: gkr-pam: stashed password to try later in open session
out 28 11:18:03 myusername systemd[1]: session-c1.scope: Killing process 919 (lightdm) with signal SIGTERM.
out 28 11:18:03 myusername systemd[1]: session-c1.scope: Killing process 937 (lightdm-gtk-gre) with signal SIGTERM.
out 28 11:18:03 myusername systemd[1]: Stopping Session c1 of User lightdm...
out 28 11:18:03 myusername lightdm[919]: pam_unix(lightdm-greeter:session): session closed for user lightdm
out 28 11:18:03 myusername systemd[1]: Stopped Session c1 of User lightdm.
out 28 11:18:03 myusername lightdm[973]: pam_unix(lightdm:session): session opened for user myusername(uid=1000) by myusername(uid=0)
out 28 11:18:04 myusername lightdm[973]: gkr-pam: unlocked login keyring
out 28 11:18:04 myusername echo[1029]: Testing lightdm from .xprofile, xprofile executed
out 28 11:18:04 myusername echo[1032]: Testing lightdm from .xprofile, 1st executed
out 28 11:18:04 myusername echo[1035]: Testing lightdm from .xprofile, 2nd executed
out 28 11:18:05 myusername echo[1038]: Testing lightdm from .xprofile, 3rd executed
out 28 11:18:13 myusername (sd-pam)[928]: pam_unix(systemd-user:session): session closed for user lightdm
out 28 11:20:03 myusername sudo[1506]:    myusername : TTY=pts/0 ; PWD=/home/myusername ; USER=root ; COMMAND=/usr/bin/nvim /etc/lightdm/lightdm.conf
out 28 11:20:33 myusername lightdm[973]: pam_unix(lightdm:session): session closed for user myusername
out 28 11:20:34 myusername lightdm[897]: Error terminating login1 session: GDBus.Error:org.freedesktop.login1.NoSuchSession: No session '2' known
out 28 11:20:34 myusername systemd[1]: lightdm.service: Deactivated successfully.
out 28 11:20:34 myusername systemd[1]: lightdm.service: Consumed 6.733s CPU time, 116.7M memory peak.
out 28 11:21:07 myusername echo[922]: Testing lightdm from script, xprofile executed
out 28 11:21:07 myusername echo[925]: Testing lightdm from script, 1st executed
out 28 11:21:07 myusername lightdm[927]: X Error of failed request:  BadMatch (invalid parameter attributes)
out 28 11:21:07 myusername lightdm[927]:   Major opcode of failed request:  140 (RANDR)
out 28 11:21:07 myusername lightdm[927]:   Minor opcode of failed request:  29 (RRSetPanning)
out 28 11:21:07 myusername lightdm[927]:   Serial number of failed request:  28
out 28 11:21:07 myusername lightdm[927]:   Current serial number in output stream:  28
out 28 11:21:07 myusername echo[928]: Testing lightdm from script, 2nd executed
out 28 11:21:07 myusername lightdm[930]: xrandr: specified screen 1920x1080 not large enough for output LVDS-1 (2048x1536+0+0)
out 28 11:21:08 myusername lightdm[930]: X Error of failed request:  BadMatch (invalid parameter attributes)
out 28 11:21:08 myusername lightdm[930]:   Major opcode of failed request:  140 (RANDR)
out 28 11:21:08 myusername lightdm[930]:   Minor opcode of failed request:  29 (RRSetPanning)
out 28 11:21:08 myusername lightdm[930]:   Serial number of failed request:  30
out 28 11:21:08 myusername lightdm[930]:   Current serial number in output stream:  30
out 28 11:21:08 myusername echo[931]: Testing lightdm from script, 3rd executed
out 28 11:21:08 myusername lightdm[934]: pam_unix(lightdm-greeter:session): session opened for user lightdm(uid=964) by (uid=0)
out 28 11:21:08 myusername systemd-logind[749]: New session c1 of user lightdm.
out 28 11:21:09 myusername (systemd)[941]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 service=[systemd-user] terminal=[] user=[lightdm] ruser=[<unknown>] rhost=[<unknown>]
out 28 11:21:09 myusername (systemd)[941]: pam_unix(systemd-user:session): session opened for user lightdm(uid=964) by lightdm(uid=0)
out 28 11:21:09 myusername systemd-logind[749]: New session 1 of user lightdm.
out 28 11:21:09 myusername systemd[1]: Started Session c1 of User lightdm.
out 28 11:21:59 myusername lightdm[989]: gkr-pam: unable to locate daemon control file
out 28 11:21:59 myusername lightdm[989]: gkr-pam: stashed password to try later in open session
out 28 11:21:59 myusername systemd[1]: session-c1.scope: Killing process 934 (lightdm) with signal SIGTERM.
out 28 11:21:59 myusername systemd[1]: session-c1.scope: Killing process 952 (lightdm-gtk-gre) with signal SIGTERM.
out 28 11:21:59 myusername systemd[1]: Stopping Session c1 of User lightdm...
out 28 11:21:59 myusername lightdm[934]: pam_unix(lightdm-greeter:session): session closed for user lightdm
out 28 11:21:59 myusername systemd[1]: Stopped Session c1 of User lightdm.
out 28 11:21:59 myusername lightdm[989]: pam_unix(lightdm:session): session opened for user myusername(uid=1000) by myusername(uid=0)
out 28 11:22:00 myusername lightdm[989]: gkr-pam: unlocked login keyring
out 28 11:22:09 myusername (sd-pam)[943]: pam_unix(systemd-user:session): session closed for user lightdm
out 28 11:23:44 myusername echo[2020]: Testing lightdm from script, xprofile executed
out 28 11:23:44 myusername echo[2023]: Testing lightdm from script, 1st executed
out 28 11:23:44 myusername echo[2026]: Testing lightdm from script, 2nd executed
out 28 11:23:45 myusername echo[2029]: Testing lightdm from script, 3rd executed

Furthermore, running the scriptc manually or not, always gives some warnings, that I think can be ignored but just in case:

myusername% sh fix_screen.sh 
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  29 (RRSetPanning)
  Serial number of failed request:  28
  Current serial number in output stream:  28
xrandr: specified screen 1920x1080 not large enough for output LVDS-1 (2048x1536+0+0)
X Error of failed request:  BadMatch (invalid parameter attributes)
  Major opcode of failed request:  140 (RANDR)
  Minor opcode of failed request:  29 (RRSetPanning)
  Serial number of failed request:  30
  Current serial number in output stream:  30

And finally, the script itself

#!/bin/sh

systemd-cat echo "Testing lightdm from script, xprofile executed"

xrandr --output "LVDS-1" --mode 2048x1536 --panning 2048x1536
systemd-cat echo "Testing lightdm from script, 1st executed"

xrandr --output "LVDS-1" --mode 2048x1536 --panning 1920x1080
systemd-cat echo "Testing lightdm from script, 2nd executed"

xrandr --output "LVDS-1" --fb 1920x1080
systemd-cat echo "Testing lightdm from script, 3rd executed"

So, do I really need to run this script somewhere else if I want my screen to always have the correct size? I wanted any instance of X to be the correct size but don’t really like the idea to be spreading configurations everywhere.

Display Sony VAIO VPC-F115FM
Display:	16.4-inch, 1920x1080, Widescreen
Graphics Controller:	discrete
Graphics Chipset Model:	NVIDIA GeForce GT 330M
Graphics Memory:	1024 MB