Hello everybody,
I’ve got an issue with boundaries of the workspace. Hardware Dell 5521 (11th generation i7), 64GB ram, 1TB SSD (NVMe), dock WD22TB4, 2 graphic cards - NVidia MX450 + Intel on chip). According the specification the notebook should be able to handle 3x 4K @60Hz connected to dock through its TB4 connection (seems kernel recognize it as TB3 only) so only 2x 4k through dock and remaining one through other USB-C/Video + adapter. Everything seems to work properly except the fact after login the workspace seems to be “moving” to down/right when I moved the mouse over the down/right edge of the visible area. I’m observing this for quite time now. Could not exactly tell when this started. Re-alignment of the screens occasionally helps right after login (when the area had already moved only re-login/restart helps) but it is annoying to re-align screen each time the machine starts.
Any suggestion how to fix this annoying issue would be welcomed…
You seem to be describing the behavior of a “virtual” desktop larger than the desktop defined by the dimensions of your displays. If that’s been configured, “realignment” should require no more than moving the mouse back to the upper left extreme. If you don’t want a larger virtual desktop, you should be able to disable it in the same manner as it was configured, probably via NVidia settings. Virtual desktop is probably an optional setup via checkbox option in Plasma display settings as well. I always disable KScreen, so can’t be sure whether it’s there or what it might be called. Sharing the Xorg configuration file(s) created by NVidia setup should tell us if that is what happened, either /etc/X11/xorg.conf (likely), or (possibly) a group of files in /etc/X11/xorg.conf.d/. Sharing also output from inxi -Gaz should be useful. Please use PRE tags for any command input/output you paste here in reply, the </> icon above the input window, to preserve the command formatting.
#(00-keyboard.conf)
# Written by systemd-localed(8), read by systemd-localed and Xorg. It's
# probably wise not to edit this file manually. Use localectl(1) to
# instruct systemd-localed to update it.
Section "InputClass"
Identifier "system-keyboard"
MatchIsKeyboard "on"
Option "XkbLayout" "us"
Option "XkbModel" "pc105+inet"
Option "XkbOptions" "terminate:ctrl_alt_bksp"
EndSection
Well I would understand the virtual desktop would be bigger than the screen resolution (that way I’ll me able to move mouse out of screen) but the behavior is a bit different. It allows me to move cursor out of screen on bottom/right side but after that the upper left corner (where I could move the mouse cursor) shifts right/down by probably the offset I moved out of screen. So after that the upper left corner is not reachable anymore (was reachable before I moved the cursor out of screen).
If you remove the existing kscreen configuration (in ~/.local/share/kscreen directory) then log out and back in again, does the problem remain? As mrmazda mentioned already kscreen2 (background services) can be disabled if found to be the cause of this issue.
I think you’re observing a bug, but here are a few things to do before reporting or deciding where to report:
1-Do you get the same behavior in a wayland session?
2-Do you get the same behavior in an IceWM session instead of Plasma?
3-Do you get the same behavior if you completely disconnect one external display and not disable the laptop screen?
4-Can you reproduce by booting 15.5, Neon, or some other recently released distro’s live media?
5-Paste here input/output from running xrandr, so we can see if it reports anything useful that inxi didn’t. Feel free to omit most or all resolution lines that contain neither * nor +.
Well xrandr returns “interesting” values for Screen 0 (still have 3x 4K in line so shouldn’t it be 11520x2160 ?). It is right after the restart of machine and immediate log-in, interestingly enough on the login screen this behavior is not observable (it is working as expected)…
Well I had installed elementaryOS 6.x before Tumbleweed (basically customized Ubuntu) there I’ve observed it sometimes “forgot” screen configuration completely (same machine + dock + external monitors). Leap was struggling same issue as Ubuntu that time and Manjaro KDE same. Linux Mint was working properly.
Personally got some issues with any Ubuntu based distros and don’t like Fedora/CentOS at all .
Ok, that is good to know. For the most part you may not notice any difference. It really depends on your exact software/hardware environment and requirements, but there is solid development and support for Plasma Wayland, bugs are being actively squashed when reported.
I follow the following developer blog…
If you observe any issues or just want to get more technically familiar with KDE Wayland, the following link may be of value to you… https://community.kde.org/KWin/Wayland
By what means was the laptop display being disabled when using X11? According to Intel, the i7-11850H should support 4 at once, unlike most of its predecessors limited to 3, which probably hampered/hampers software development and testing for 4 display configurations.
It sure should, as long as only 3 displays are connected. But, you have 4 - the laptop display AFAIK can’t be physically disconnected. X11 (kernel?) doesn’t necessarily do very well when un-powered but connected displays are present. It apparently knows and wants to be ready if/when its power comes on.
That suggests brokenness in X11, given lack of trouble with your Wayland session. 13440 minus 1920 leaves 11520. 7560 is 1920 + 3 * 2160. So, xrandr seems to think X11 has given you all 4 displays across at the same time as all 4 stacked, while not visibly locating a presumptive FHD display.
If Wayland keeps on behaving as expected, keep on using it, but you might wish to get the Xorg failure on record in Bugzilla, in case you find an issue with Wayland.
