"apply plasma settings to SDDM" not working (KDE Neon, Wayland)

[NitramO_Off]

As you can see here

@NitramO_Off

So, when i start my computer, and SDDM runs, it doesn’t have the same monitor settings that inside the OS, the screens are not in the right order and the 1080p is a replica of my Internal Laptop Monitor, and sometime if i type the password in the 2k it freezes and i need to type it also on the 1080p and then somehow it works!

I have some problems with my KDE Neon experience

Hi, i’m using KDE Neon for a while now, and i have some little problems here and there which accumulate with the time and that was also (little problems accumulating making big troubles) the reason i left Windows… So i’m gonna try to list all here and i hope you can help me to fix some of them if not all! Here is my setup: OS: KDE neon 6.2 x86_64 Host: Pulse 17 B13VFK REV:1.0 Kernel: 6.8.0-49-generic Packages: 2617 (dpkg), 21 (flatpak), 7 (snap) Shell: bash 5.2.21 DE: Plasma 6.2.3 WM: kw…

@NitramO_Off

Yes i use the Breeze Theme

@skyfishgoo

when you click on the (i) in the SDDM settings page, do you not get a preview of what the screen should look like?

@NitramO_Off

Yes

@skyfishgoo

if you change it to the other one does it ask you for the password?

and does that change the SDDM login screen upon reboot, or is it the same?

@NitramO_Off

Yes, it asks me for the password, and i tried many combinations, like applying a new SDDM theme then applying the plasma settings to SDDM, same in reverse, same twice, and so on… Nothing changed!

Please help me, thanks in advance for your help!

[NitramO_Off]

Up!
I hope someone can help me to fix this…

[NitramO_Off]

I hope someone can help me…

[johnandmegh]

While folks are generally happy to help here, of course, I think you will find more satisfaction in your experience, and feel more empowered as a power user of your device (which, based on the things you seem to be doing with your computer, I’m guessing is of interest to you), if you also build additional capabilities to independently research issues related to KDE software.

Just my personal perspective, but repeatedly “bumping” threads on the forum to try to push them toward the top of the list will likely lead to more frustration for you, since it’s relatively unlikely to produce the results you want (it doesn’t increase anyone else’s capacity or ability to help), and may be the “long way” to get to the answer you want if it’s actually available through another means.

In this particular case, for example, I would check to see if there are existing bug reports describing the behavior I’m experiencing. This would involve:

• Going to the KDE Bugtracking System (https://bugs.kde.org/)
• Clicking the Search text link at the top
• Selecting all Status options, so I can see potential duplicate variations in how the same core bug was described, and see recently resolved issues for which I may not have received a released updated version yet
• Choosing search terms that relate to the core of the issue - in this case, “sddm settings” and “sddm monitor”

Those two searches lead to finding the following bugs among the top few results:

484034 – SDDM cannot apply plasma settings of scaling | 495830 – Can't login with SDDM breeze theme on second monitor | 494804 – With Qt 6.8 controls to log in or unlock screen are non-functional on some monitors when using the Breeze SDDM or Plasma theme ("TypeError: [thing] is not a function" error)

By reviewing the metadata fields at the top, and the comments underneath, you can then see that some of which are resolved upstream and pending inclusion in future KDE Plasma releases, some of which are confirmed bugs but still pending resolution.

Hope that helps,

[NitramO_Off]

Thanks for your answer and advice!
But if i came on this forum to ask for help, it’s because i don’t have too much time to search for hours a solution or if my issue is known for all of my problems on my KDE System, because i had and i have lot of it. So i was hoping that some people here could help me or at least like you just did, tell me that the problem i was having was known and in debug state!

So thanks for the info, i’ll just wait a future update for now…