Manually Change in CLI: s-dpi, s-size & s-diag [Solved]

[operadude]

ok, so in my VM I found:
- No such file as /usr/local/share/sddm/scripts/Xsetup

- I DID find /usr/share/sddm/scripts/Xsetup

and indeed adding the following did change my login window sizes:
I added to the file ( using Kate) :
xrandr -s 640x480

before the exit 0

So, my entire Xsetup file looks like this

Code: Select all

#!/bin/sh
# Xsetup - run as root before the login dialog appears

xrandr -s 640x480

exit 0

and then logged out and *little tiny login screen*. Played with various res's and it reacted across them, so that does work. and didnt play with anything else. (ie no dpi, or s- or anything. )

I am going to say set yours to something like this and you should be good:

Code: Select all

xrandr -s 1920x1080 

Remember I am in a VM, but here are my graphics setup from QSI which also show "strange" s-dpi settings. no clue what these are about, but I am sure someone can explain that.

Code: Select all

Graphics:
  Device-1: VMware SVGA II Adapter driver: vmwgfx v: 2.20.0.0 ports: active: Virtual-1
    empty: Virtual-2, Virtual-3, Virtual-4, Virtual-5, Virtual-6, Virtual-7, Virtual-8
    bus-ID: 00:02.0 chip-ID: 15ad:0405 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: vmware unloaded: fbdev,modesetting,vesa dri: swrast gpu: vmwgfx display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1729x980 s-dpi: 47 s-size: 932x528mm (36.69x20.79") s-diag: 1071mm (42.17")
  Monitor-1: Virtual-1 mapped: Virtual1 res: 1729x980 hz: 60 size: N/A modes: max: 1729x980
    min: 640x480
  API: OpenGL v: 4.5 Mesa 24.2.8-1mx23ahs renderer: llvmpipe (LLVM 15.0.6 256 bits)
    direct-render: Yes

Well, that looks like a quick and easy fix

Will try later, and get back to you...

[operadude]

@CharlesV Unfortunately, this did nothing:

Code: Select all

/usr/share/sddm/scripts/Xsetup

Add this line (before "exit 0"):

Code: Select all

xrandr -s 1920x1080

Unfortunately, upon reboot, same huge login screen...


CORRECTION:

I had written earlier that the Login screen on the testing rig is HUGE, and that I can't see the whole field for the password.

Now, I do see the whole field (not sure what changed somewhere along the way), AND, I have enough room to put my whole password.

EDIT: [Emendations in Text boxes, like this one]:

The only inconvenience is that the other options that appear below the password box are too [very] large, and [almost, but not quite] overlap one another. I can still choose "X11"/"Wayland", but some of the other options are overlapping, and looks like I wont be able to choose them, or maybe very carefully! I think the last option ("Other") is also occluded., and the other options are very large, but they ARE accessible. The only one that is a bit tricky, but still doable, is the "X-Session V. Wayland" option, which is kinda sandwiched between the other options. Whatever...

At this point, changing the login screen (SDDM) is NOT a deal-breaker, and I am willing to live with the current state.

Having said that, I would, for the Geek-Factor (Upping My Linux Skills), like to successfully tweak this sucker, so that I can have the Computer Bend To My Will (Too Cringe? )

EDIT/ADDENDUM:

Just tried various combinations of editing the "Xsetup" file, with:

Code: Select all

xrandr --primary --fb 1920x1080 --dpi 96

None of those worked; neither singly, nor all together.

So, @CharlesV , let me know, "Before Midnight Tonight " , if you have any further thoughts or recommendations.

[CharlesV]

hmmm... please verify that you do NOT have this file - And if you DO, lets see what the contents of that are.

Code: Select all

 /usr/local/share/sddm/scripts/Xsetup

[operadude]

hmmm... please verify that you do NOT have this file - And if you DO, lets see what the contents of that are.

Code: Select all

 /usr/local/share/sddm/scripts/Xsetup

Nope!

I have this folder:

Code: Select all

/usr/local/share/

But NO "sddm" folder !

I also tried adding the same file, but renamed as ".xsession", in my home folder, since the "man" page for "xsession.options" says this:

Code: Select all

allow-user-xsession
              If  users  have  an executable file called .xsession in their home directories, it
              can be used as the startup program for the X session (see  Xsession(5)).   If  the
              file  is  present but not executable, it may still be used, but is assumed to be a
              Bourne shell script, and executed with sh(1).

I tried with permissions set to both "root" and "opera-dude" (separately), but this also had NO EFFECT.

Grasping at straws...

The only other thing I have noticed, is that when the machine boots (before login screen), there are a few ACPI errors flashed to the screen (something about "BIOS bug"), and then very quickly, those same errors appear MUCH LARGER. So, yeah, not sure what is causing that...

[CharlesV]

Perfect. (I was thinking maybe that local was overriding the other location.)

This is starting to sound like your wayland scaling is broken - and I bet this is that wayland / nvidia issue I read about.

That Xsetup is to manipulate X11 around and since it has no effect ... Let me see if I can find a wayland equivalent. ( or since that machine has nvidia, maybe we can push back to X11 ? Let me see what I can find. )

[operadude]

Perfect. (I was thinking maybe that local was overriding the other location.)

This is starting to sound like your wayland scaling is broken - and I bet this is that wayland / nvidia issue I read about.

That Xsetup is to manipulate X11 around and since it has no effect ... Let me see if I can find a wayland equivalent. ( or since that machine has nvidia, maybe we can push back to X11 ? Let me see what I can find. )

Fantastic

But, are you sure I am using Wayland?
I thought I was using the X11 Session ?

FYI, I have BOTH my rigs going now, and both signed into the Forum !

ADDITION:

Is this info from my QSI (testing rig, "problematic" system) relevant?:

Code: Select all

Snapshot created on: 20250617_1407
System:
  Kernel: 6.1.0-37-amd64 [6.1.140-1] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.1.0-37-amd64 root=UUID=<filter> ro quiet splash
  Desktop: KDE Plasma v: 5.27.5 info: plank wm: kwin_x11 vt: 7 dm: SDDM Distro: MX-23.6_x64
    Libretto October 13 2023 base: Debian GNU/Linux 12 (bookworm)

That shows the "wm" as kwin_x11

So, NOT Wayland ?

ADDITION:

Ahh..., but I also see this from the QSI:

Code: Select all

Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
    loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia display-ID: :0
    screens: 1

So, how does this work? X11 server WITH Xwayland?

[CharlesV]

Xactly ! ( Sorry, had to do it !) .. That was why I headed for the XSetup file.

Lets try this...

in your /etc/addm.conf file , under the General section add the following and reboot.

Code: Select all

EnableHiDPI=true

and if that STILL has no change, then add this line (also under the General Section )

Code: Select all

DisplayServer=x11

I dont believe thsi second line will make any difference as I think you are already ON the X11 server.. but ... worth a try.

[operadude]

Xactly ! ( Sorry, had to do it !) .. That was why I headed for the XSetup file.

Lets try this...

in your /etc/addm.conf file , under the General section add the following and reboot.

Code: Select all

EnableHiDPI=true

and if that STILL has no change, then add this line (also under the General Section )

Code: Select all

DisplayServer=x11

I dont believe thsi second line will make any difference as I think you are already ON the X11 server.. but ... worth a try.

No "/etc/addm.conf file"

EDIT:

Ahh...looks like a typo...must be "sddm.conf"

Will try now...

[CharlesV]

sorry.. typo.

sddm.conf


Also.. I just saw there are system-settings for sddm.

Start system-settings from the MX menu, then type in sddm
click on Login Screen, and at the bottom there is a button that says "Apply Plasma Settings"
If you click that button shows a number of things that are about to be changed, ONE of which IS DPI to match your desktop!!

Please try that.

[operadude]

@CharlesV No "General" section !

Here are the complete contents of /etc/sddm.conf

Code: Select all

[Theme]
CursorTheme=breeze_cursors