I ahve recently installed the latest Tuxedo-OS4.0 with KDE 6.2.3 and Wayland. I have a dual screen setup which works well once logged in, but for the login screen I have the following problems:
The left and right screens are swapped around, with the result that I need to move the mouse to navigate between them.
This would not have been noticed, but it defaults to the right screen and will take my password input, but then only go grey.
I must then navigate with the mouse towards the right to go to the screen on the left, in order to enter my password here as well. After entering the password, it logs in and the navigation is fixed.
Is there some way to fix these problems, which are most likely related to the same problem.
Note: the screens are different sizes:
AOC 32" 155Hz gaming monitor on left
LG 29@ wide screen on the right
Hey there, I dealt with some of these issues a bit ago, would like a little more info in order to (hopefully) help.
Are you talking about when you’re completely logged out of Tuxedo (i.e. SDDM), or when you or the system has just locked your screen?
If you know, how are you connecting to the monitors? If your machine uses integrated graphics, often times the boot process will choose the inputs available only to it, and initially ignore anything available to your hard-earned actual graphics card (i.e. NVIDIA).
You have already tried to export your KDE monitor settings to SDDM I guess? If not that may be the issue, or one contributing factor of it.
KDE settings - Loginscreen (SDDM) and “Apply Plasma settings” at the top.
Judging by the monitors used, I would say he has a desktop PC with 2 monitors.
I have the same issue with TuxedoOS 2 (Kernel 6.11), Plasma 5.27.10 and X11. And single GPU (RX6600).
One monitor is connected via DP (primary, right) and other one via HDMI (secondary, left), and login is active on both, it makes no difference where I type password
Though for me this isn’t a big deal, so I didn’t report it or looked for solution. But now I saw this thread and maybe this will be useful. I will look more into this
Never bothered me as well, because I thought it doesn’t matter on which Monitor to login if the layout is correct after login anyway.
But switching from TuxedoOS2 to Arch, when Plasma 6 came out, I (had to) read a lot of Archwiki articles to set up everything correctly and that included: https://wiki.archlinux.org/title/SDDM#Match_Plasma_display_configuration
Changes to your display configuration made in a Plasma Wayland session (e.g. monitor layout, resolution, etc) will not persist to SDDM. To make them persist open Plasma’s System Settings and navigate to Colors & Themes > Login Screen (SDDM) and click “Apply Plasma Settings…”. You will need to have permission to perform this action.
And noticed that, as stated in that quote, also applied my Plasma monitor layout to SDDM.
So I hope, as sJBs never tried, that alone maybe can solve the issue as he stated it is only swapped around at the SDDM (login) stage.
It is a desktop i4790/16GB/GTX1070. The screens are connected using DP and HDMI cables. Whe the input defaulting to HDPI screen, but only using the input from the DP screen.
Changes to your display configuration made in a Plasma Wayland session (e.g. monitor layout , resolution, etc) will not persist to SDDM. To make them persist open Plasma’s System Settings and navigate to Colors & Themes > Login Screen (SDDM) and click “Apply Plasma Settings… ”. You will need to have permission to perform this action.
Unfortunately same problems persist:
still defaults to screen on the left (HDMI), where you can type in your password and press enter, after which this screen goes grey.
Then I have to navigate to the screen on the right (DP), but moving the mouse left.
Then re-enter my password after which I successfully login and proceed to the desktop.
Somehow i missed that one display not accept the password, That’s strange. Did it not even at least correct the swap around?
Has TuxedoOS / Tomte installed the latest Nvidia driver? If I remember correctly Tomte (The Tuxedo software/driver helper that also manages the Nivdia stuff) had, as one user complaint at the Tomte github in the past, problems to identify a Nvidia card correctly on a non tuxedo machine and to install the appropriate driver.
1070 should be able to use the latest driver, if I’m not mistaken and that is basically a necessity for wayland as a older one could create problems as well. modinfo nvidia | grep ^version
from commandline should tell you the version.
Unfortunately not. Just restarted again to answer this and it is still the wrong way around. Also didn’t log in on entering my password on the default screen on the left.
See below
modinfo nvidia | grep ^version
version: 560.35.03
Is there a command to run that will give you all the information about my system that should be included in all “help” queries?
This is from About this System, using the “Copy Details” button, but it didn’t include the Nvidia driver.
Operating System: TUXEDO OS 4
KDE Plasma Version: 6.2.3
KDE Frameworks Version: 6.8.0
Qt Version: 6.8.0
Kernel Version: 6.11.0-105009-tuxedo (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-4790 CPU @ 3.60GHz
Memory: 15.6 GiB of RAM
Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2
This (because of the -R flag) updates your initramfs to properly refer to the correct theme, and updates the settings that M.Karrde mentioned.
Theoretically, when you follow the system settings he mentioned, kde is supposed to do this for you. But I’ve definitely noticed a bug or 30 in there, and have had to do this manually more than once.
If you don’t know the theme name, you can just run # plymouth-set-default-theme --list (-l for short). Just lists your themes, so you can find the correctly formatted name.
EDIT: in the off chance you were waiting by the computer for this reply, know that I did add the -R flag just now, which initiates the initramfs update.
That looks okay, I’m one version ahead but 560 should be no issue.
Maybe / Hopefully archisthebest remembered the solution.
“About this System” should be fine to begin with as i think that is the main purpose of the “Copy Details” button.
On top of that Inxi is quiet powerful to get not necessary all, that would be a lot but depending on the flag it is run with slightly deeper info if needed or at least to be easier able to answer possible questions about your Hardware/Software setup.