https://bugs.kde.org/show_bug.cgi?id=516154
Bug ID: 516154
Summary: Plasma Setup session management broken on openSUSE
Classification: Applications
Product: Plasma Setup
Version First unspecified
Reported In:
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: General
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: ---
SUMMARY
With Plasma 6.6, KDE Initial Setup was released. Unfortunately, it is currently
not usable on openSUSE Tumbleweed, since a) it's not in the official repos yet
(an unofficial one packaging it exists though and this is not your problem :D )
and b) the session management is broken. Initial Setup writes a config file in
/etc/sddm.d or in the directory for the plasma login manager. Unfortunately
though, openSUSE uses /etc/sysconfig/displaymanager with the key
DISPLAYMANAGER_AUTOLOGIN= to determine the autologin user and a config setting
in in /etc/sddm.d is ignored, meaning the initial setup wizard never runs. It
is possible to set this manually, but then of course, after creating a user
(which works great by the way), you are logged in automatically again to the
setup wizard and you need to manually remove the autologin key again.
I tested this with Plasma 6.5, but I don't think that this should matter.
STEPS TO REPRODUCE
1. Install openSUSE Tumbleweed
2. Add this repository:
https://build.opensuse.org/project/show/KDE:Unstable:Frameworks
3. Install plasma6-setup
4. Enable the service
5. reboot
6. observe
OBSERVED RESULT
Initial Setup fails to control the autologin sessions correctly
EXPECTED RESULT
After installing and rebooting, it should start automatically
SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20260214
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.9-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 7840U w/ Radeon 780M Graphics
Memory: 32 GiB of RAM (30.7 GiB usable)
Graphics Processor: AMD Radeon 780M Graphics
Manufacturer: Framework
Product Name: Laptop 13 (AMD Ryzen 7040Series)
System Version: A7
ADDITIONAL INFORMATION
I had a look at how GNOME and GDM handle the initial setup routine, just to get
an inspiration of how it _could_ work (since their initial setup system works
on openSUSE). If I'm not mistaken, their solution is: GDM checks if a "real
user" that can login exists and if not, GDM internally sets the autologin
session and logs into their setup user. Once the user is created, GDM receives
a signal via D-Bus to login the new user.
Since KDE now has their own display manager as well, maybe at least for plasma
login manager a similar approach should be used as well. The login manager
should check if a user exists that can login and then boot the setup routine on
its own. This way, you wouldn't depend on any configuration files being in the
correct order/respected the way you assume. This would then also allow directly
logging in as the new user and this won't touch configuration files, so there
are no persistent autologin configs potentially removing/changing user
configurations or similar. This also can't lead to a situation where
accidentally the user is trapped in an autologin situation of the initial setup
wizard or similar.
If this is chosen, you also wouldn't have to rely on /etc/plasma-setup-done to
exist.
On a system where the last real user is accidentally removed, KDE initial setup
would just run again keeping the system usable (maybe, instead (like GDM), add
a file to indicate that the initial setup should _not_ run even without a valid
user?)
--
You are receiving this mail because:
You are watching all bug changes.
