I’ve a dual monitor setup and its been working great under Tumbleweed for quite some time. But after I recent zupper -dup I got some problems. There has been several updates since then but the problem remains.
I have two monitors and a extended desktop that uses both of them, the left monitor is rotated into portrait mode and the right one is in landscape. I’ve set everything up using the monitor settings in systemsettings5. Resolutions, rotation and offset of the monitors (related to each other) is all set up by the monitor settings. But since a while back Plasma forgets and resets the offset/postion settings at every logout/login. I need to launch systemsettings and manually reposition one of the monitors after every login or else will the monitors partly overlap.
Try the same procedure as comment 2, but with a slightly different command:
rm -rf ~/.cache/*
To me this smells like a permissions problem preventing proper saving of settings, but this seems quite unlikely to reproduce with a new user. How was the new user created, YaST? Will this reproduce if you try using the root user? If not, it supports the theory of a permissions problem
It might be useful for us to see pasted here using code tags some information collected while the screens are not running as desired:
Tried to clean the cache-direcory but with same result as before.
The new user was created using Yast.
Same problem appears for root as well so I dont think its a permission problem
xrandr | egrep 'onnect|creen|\*' | grep -v disconn | sort -r
Screen 0: minimum 320 x 200, current 2527 x 2236, maximum 16384 x 16384
DVI-I-1 connected primary 1920x1080+607+1156 (normal left inverted right x axis y axis) 531mm x 299mm
DVI-D-1 connected 1080x1920+0+0 left (normal left inverted right x axis y axis) 477mm x 268mm
1920x1080 60.00*+ 59.96 50.00 59.94 59.93
1920x1080 60.00 + 59.96 50.00 59.94 59.93*
1002:6658 is GCN2, so most likely should be using the DDX from xf86-video-amdgpu, while inxi reports you’re using the default modesetting DDX. If xf86-video-amdgpu is not installed, see if installing it helps. If it’s already installed, amdgpu may need explicit configuration via a Driver line in /etc/X11/xorg.conf.d/50-device.conf, and/or a cmdline option or two, maybe radeon.si_support=0 amdgpu.si_support=1.
I’ve never seen both DVI-I-1 and DVI-D-1 reported simultaneously, so to me is suspect to being mishandled in several places.
Let’s try using xrandr “directly”, via a startup miniscript, instead of going through desktop settings, and for now, not fuss over which DDX is in use. Create the miniscript using superuser permission as:
On the opensuse-factory mailing list it was announced that Mesa version 19.2.3 since TW20191110 has a “critical bug”, but didn’t describe what it is. I have it on several installations and no idea what is supposedly wrong. 19.2.4 is in the Xorg:X11 repo for any wishing to have a patched version.
BTW, in the standard TW OSS repo is the utility arandr. It can be used to generate the script to be used as /etc/X11/xinit/xinitrc.d/50-xrandr.sh. When used arandr can save the script as a file in ~/.screenlayout/ (or anywhere else writable that you choose), then copied, renamed, edited, and if necessary, re-permissioned.
When you configure screen layout in /etc/X11/xinit/xinitrc.d/50-xrandr.sh, it will be applied to any desktop session type you select, not just Plasma.
50-xrandr.sh is an arbitrary name. You can make it any name you please. A number at its start can affect when it gets run during X startup.
Tried to execute the script from X-terminal and it just gives me an error “Can’t open display”
Possibly our definitions for X terminal are out of sync. In Plasma the script should be run from Konsole, Xterm or Alt-F2, not one of the virtual terminals reached via Ctrl-Alt-Fn, which is where “cannot open display” errors typically come from.