[BUG] SDDM & KScreen issue

Rashino · 2022-11-04 06:42:51

Hello all,

I'm having this issue in this video

How it happened:

I attempted to fix my sddm screen using this guide

The problem is that now after logging in, the right monitor fails to turn on but the left one does. Moving the mouse to the right outer bound of the middle monitor moves both the middle and left monitor desktop GUI's to the left, and vice versa if I put the mouse to the left outer bound of the left monitor. I have a script that I run to fix this everytime I log in now. This problem goes away when I remove the sddm script and the monitors are in the correct order after logging in (not during sddm login though), but then they're inverted in that the shortcut to move an application to the right monitor moves it left instead.

What I've tried:

autorandr (tried setting it to run on login)
xrandr script to run on login
Changing Xorg config to properly display monitors in correct order
Enabling early KMS
Deleting KScreen cache in /home/$USER/.local/share/kscreen

What I've discovered:

It may be related to Kscreen as it produces 4 files and the 4th says the third monitor is disabled.

My settings:
Using an AMD CPU and NVIDIA GPU with nvidia driver (I've tried nvidia-lts as well)

Any help would be tremendously appreciated!!

seth · 2022-11-04 07:42:45

Post the (bogus) /usr/share/sddm/scripts/Xsetup you created and the output of "xrandr -q" when "the monitors are in the correct order"

the monitors are in the correct order […] but then they're inverted in that the shortcut to move an application to the right monitor moves it left instead

Could it be that the shortcuts are inverted?

Rashino · 2022-11-04 08:13:33

The shortcut I was using was:

Super + SHIFT + Right Arrow

I've managed to fix the monitors somewhat for sddm by just manually plugging them into the wrong hdmi ports (non-linear), and it seems to have fixed the inversed problem too. The only other issue that remains is when the script is run, the right monitor doesn't come on and the weird movement in the video happens.

The script being used (the comments were just for me, but weren't used):

Xsetup Script:

#!/usr/bin/env bash
# Xsetup - run as root before the login dialog appears
#
# HDMI-0 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 521mm x 293mm
# HDMI-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm
# HDMI-2 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 521mm x 293mm

# Set sddm displays
xrandr --output HDMI-0 --pos '1920x0' --rotate normal ---rate 144 --primary
xrandr --output HDMI-1 --off
xrandr --output HDMI-2 --off

# Set correct displays
# xrandr --output HDMI-0 --mode '1920x1080' --pos '1920x0' --rotate normal --rate 144 --primary
# xrandr --output HDMI-1 --mode '1920x1080' --pos '0x0' --rotate normal ---rate 144 --noprimary
# xrandr --output HDMI-2 --mode '1920x1080' --pos '3840x0' --rotate normal ---rate 144 --noprimary

The part under set correct displays is the part I run in a separate script to fix the monitors

Monitors Correct ~~But Inverted~~ (Run without the Xsetup script running):

Screen 0: minimum 8 x 8, current 5760 x 1080, maximum 32767 x 32767
DP-0 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 521mm x 293mm
   1920x1080     60.00 + 144.00*  119.88   100.00    59.94    50.00  
   1680x1050     59.95  
   1440x900      59.89  
   1440x576      50.00  
   1440x480      59.94  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1280x720      60.00    59.94    50.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94    59.93  
HDMI-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 521mm x 293mm
   1920x1080     60.00 + 144.00*  119.88   100.00    59.94    50.00  
   1680x1050     59.95  
   1440x900      59.89  
   1440x576      50.00  
   1440x480      59.94  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1280x720      60.00    59.94    50.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94    59.93  
HDMI-2 connected primary 1920x1080+3840+0 (normal left inverted right x axis y axis) 521mm x 293mm
   1920x1080     60.00 + 144.00*  119.88   100.00    59.94    50.00  
   1680x1050     59.95  
   1440x900      59.89  
   1440x576      50.00  
   1440x480      59.94  
   1280x1024     75.02    60.02  
   1280x960      60.00  
   1280x720      60.00    59.94    50.00  
   1152x864      75.00  
   1024x768      75.03    70.07    60.00  
   800x600       75.00    72.19    60.32    56.25  
   720x576       50.00  
   720x480       59.94  
   640x480       75.00    72.81    59.94    59.93  
USB-C-0 disconnected (normal left inverted right x axis y axis)

seth · 2022-11-04 13:50:08

You've (had) 3 outputs:
HDMI-1 | HDMI-0 | HDMI-2

This here

xrandr --output HDMI-0 --pos '1920x0' --rotate normal ---rate 144 --primary
xrandr --output HDMI-1 --off
xrandr --output HDMI-2 --off

disables the left and the right one, makes the one in the center primary and will fail to position it at 1920x0, because it's gonna be the only output left.

What was the intention of the SDDM script?

Rashino · 2022-11-04 16:36:59

What was the intention of the SDDM script?

The sddm script is meant to make it so only one monitor is on during initial login. It's taken from this guide: Guide Link

If I have to keep all 3 on though, I might just. It seems like kscreen is the problem since deleting the kscreen folder in home directory changes which ones turn on (only the main one does when it's deleted until I reconfigure it through plasma, and then it's back to only main and left).

Rashino · 2022-11-04 16:56:52

I've managed to find a workaround but not a fix. By disabling kscreen manager in kded, and using autorandr, it seems to work now. The problem is indeed kscreen.

V1del · 2022-11-04 18:02:47

Have you ever tried to explicitly configure kscreen correctly and that didn't stick? Do you have a journal/log excerpt of such a run?

Arch Linux

#1 2022-11-04 06:42:51

[BUG] SDDM & KScreen issue

#2 2022-11-04 07:42:45

Re: [BUG] SDDM & KScreen issue

#3 2022-11-04 08:13:33

Re: [BUG] SDDM & KScreen issue

#4 2022-11-04 13:50:08

Re: [BUG] SDDM & KScreen issue

#5 2022-11-04 16:36:59

Re: [BUG] SDDM & KScreen issue

#6 2022-11-04 16:56:52

Re: [BUG] SDDM & KScreen issue

#7 2022-11-04 18:02:47

Re: [BUG] SDDM & KScreen issue

Board footer