Bugzilla – Bug 267903
KDM kcm module conflicts with /etc/sysconfig/displaymanager settings
Last modified: 2020-07-31 13:52:39 UTC
If the KDE Control Center is used to allow for automatic logins, options are lost from the "End Session" window. Whereas, if the change is made in YAST, everything works as expected. The options that are lost include the ability to choose a specific restart or suspend behavior.
More kdm configuration files confusion?
I'm not following. automatic login was never in End Session.
Open the KDE Control Center. Navigate to the login mangement section. Change the configuration to allow for an automatic login. Those simple steps are all that are necessary to lose options from "End Session." If the same functional changes are made with YAST rather than the KDE Control Center, the "End Session" options remain unchanged. I don't know how the kdm is affected by either method, but the problem remains. I don't know what further information you would need since I have described how to replicate this bug, and I have noticed the same behavior on multiple computers.
I'm keeping this one as generic 'KDM config module conflicts with /etc/sysconfig/displaymanager'.
*** Bug 393008 has been marked as a duplicate of this bug. ***
*** Bug 478424 has been marked as a duplicate of this bug. ***
*** Bug 466861 has been marked as a duplicate of this bug. ***
*** Bug 414197 has been marked as a duplicate of this bug. ***
*** Bug 437181 has been marked as a duplicate of this bug. ***
I can confirm bug exists. You cannot switch a KDM theme in Systemsettings, but in /etc/sysconfig editor in Yast.
*** Bug 540503 has been marked as a duplicate of this bug. ***
*** Bug 547816 has been marked as a duplicate of this bug. ***
*** Bug 553509 has been marked as a duplicate of this bug. ***
*** Bug 550307 has been marked as a duplicate of this bug. ***
*** Bug 558150 has been marked as a duplicate of this bug. ***
I can also confirm the bug. I did changes of KDM settings in KDE Control Center (I wished to turn on password less login, because I have encrypted root), I still asked to the password. When I did the changes in YaST | System | Editor of /etc/sysconfig | Desktop | Display manager | ... I could change everything as I wished. Might be I do not understand this YaST module so much, but every config file, at least in this section, is appearing twice: for example /etc/sysconfig/displaymanager and /etc/sysconfig/displaymanager.orig. I can / must? change both.
*** Bug 564296 has been marked as a duplicate of this bug. ***
when will this bug be fixed? I really need to apply settings from the original kdmrc, and not from yast.
This Bug is now open over many months. I've the same Problem and I'm waiting too for a solution. Are there any reasons, why it isn't able to fix this bug?
*** Bug 571476 has been marked as a duplicate of this bug. ***
I think the problem is that the script /usr/share/kde4/apps/kdm/read_sysconfig.sh generates the file /var/adm/kdm/kdmrc.sysconfig on the fly (according to the settings in /etc/sysconfig/displaymanager kdmrc.sysconfig is used for configuration of kdm instead of /usr/share/kde4/apps/kdm/kdmrc which is the file edited by the kde control panel settings. In my opinion, this is a design issue in the yast sysconfig method, which causes a lot of confusion. Maybe the kdm configuration should be left to kde tools, so the script read_sysconfig.sh will just cat the kdmrc file to the kdmrm.sysconfig file. This would require a hint or documentation what's going on. It's e.g. not possible to have only certain users with password-less login, becaus read_sysconfig has: f [ "$DISPLAYMANAGER_PASSWORD_LESS_LOGIN" = "yes" ]; then echo "NoPassEnable=true" echo "NoPassAllUsers=true" else echo "NoPassEnable=false" echo "NoPassAllUsers=false" fi There is eg. no equivalent setting for NoPassUsers in sysconfig/displaymanager, so whatever the setting for the users which aren't required entering a password done via the kde systemsettings might be - it has no effect. (I changed the echo "NoPassAllUsers=true to echo "NoPassUsers=user1,user2,user4" as a dirty workaround for getting what I want).
*** Bug 566252 has been marked as a duplicate of this bug. ***
System config files belong in the /etc tree. Why /usr/share/kde4/apps/kdm/kdmrc and not /etc/kde4/apps/kdm/kdmrc, at least by symlink, maybe with a note file in /etc/kde4/apps/kdm/ or /usr/share/kde4/apps/kdm/kdmrc about /etc/sysconfig/displaymanager?
I have the same problem in opensuse 11.3 SO: Linux 2.6.34-12-desktop x86_64 Sistema: openSUSE 11.3 (x86_64) KDE: 4.4.4 (KDE 4.4.4) "release 4" This Bug is now open over many months.
(In reply to comment #24) > I have the same problem in opensuse 11.3 > > SO: Linux 2.6.34-12-desktop x86_64 > Sistema: openSUSE 11.3 (x86_64) > KDE: 4.4.4 (KDE 4.4.4) "release 4" > > This Bug is now open over many months. So true. The same on every system I had install. (OpenSuse 11.2 and 11.3) Will this Bug still exist on 11.4 ? By the way, I've changed the Plattform from OpenSuse 11.2 to 11.3
@all Please vote for this Bug! I wish I can fix it on my own, but I can't
I have the same problem here with openSUSE 11.3. I can not change the theme in KDE -> Personal Settings -> Advanced -> Login Manager -> Theme. Even Yast -> System -> sysconfig editor does not work sometimes because Yast mangles Capitals and normal charcters. For me, the only solution is to edit manually the sysconfig file. This bug exist for a long time. Why does it take so much time to solve this?
*** Bug 669279 has been marked as a duplicate of this bug. ***
Yeah, this does not work on 11.3 either. But I had no idea this was an opensuse issue since 2007!! Kubuntu had this working right, but their KDE integration usually sucks. How is this possible in a distro that boast KDE as de-facto Desktop Environment?
Another dirty workaround: chmod -x /usr/share/kde4/apps/kdm/read_sysconfig.sh rm -f /var/adm/kdm/kdmrc.sysconfig as root (renaming or emptying kdmrc.sysconfig will also work). This will allow to successfully edit KDM settings from kcm module (which is expected behaviour). I guess that read_sysconfig.sh script is part of some SUSE-specific kdm patch that needs to be reverted, so that we have a real fix. IMHO, /etc/sysconfig/displaymanager should only contain common DM options, keeping KDM-specific parameters there doesn't make a lot of sense to me. Maybe coolo can shed some light on this?
Still the same problem on OpenSuse 11.4 Just as OpenSuse 11.3; 11.2; 11.1; 11.0 !!
*** Bug 691104 has been marked as a duplicate of this bug. ***
The following work-around works under openSUSE 11.4: cd /usr/share/kde4/apps/kdm mv read_sysconfig.sh read_sysconfig.sh-orig rm -f /var/adm/kdm/kdmrc.sysconfig This, naturally, inhibits changes made to "/etc/sysconfig/displaymanager" to take any effect, but at least (kickoff) -> Configure Desktop (Personal Settings) -> System Settings -> Login Screen works as intended. Taken into account that this bug is now over 4 (four!!) years old, it is about time that it gets fixed -- for real. The script "/usr/share/kde4/apps/kdm/read_sysconfig.sh" is really not worth having around -- It is a hack, and a very bad one at that, and in its current version it does not even handle the settings of variables in "/etc/sysconfig/displaymanager" correctly, besides from ignoring the settings from the KDE System Settings.
Sorry, changed wrong field (priority instead of severity) -- was corrected here.
*** Bug 715934 has been marked as a duplicate of this bug. ***
*** Bug 734984 has been marked as a duplicate of this bug. ***
After hours of searching for this problem if found this more than 4 Years !! old bug with 16 duplicates and its already buggy in 12.1. Any chance this will be fixed ?
*** Bug 665027 has been marked as a duplicate of this bug. ***
*** Bug 629018 has been marked as a duplicate of this bug. ***
This has been NEEDINFO from coolo for 10 months, and annoying to those who prefer upstream theming.
Does Coolo still work for openSuse? Is his e-mail adress right? Maybe he does not know about his NEEDINFO? Or he is the wrong person for that?
Yes. Yes. Maybe. He was filled here as NEEDINFO as he seemed an author of this need-to-be-reverted kdm patch (or at least of changelog entry for it =) )
for once - coolo@suse.de is not my bugzilla account.
?? In the Headline stand: "Info Provider: Stephan Kulow <coolo@suse.de>" Are you the Person for NEEDINFO, or not? And if not, why is the headline wrong?
The correct info provider is most probably coolo@suse.COM (not .de) ;-) Changed.
*** Bug 757485 has been marked as a duplicate of this bug. ***
I know, this is not a place for rants, but this bug is such a perfect example for why I have stopped to file bug reports months ago: they are too often a waste of time, unfortunately. > for once - coolo@suse.de is not my bugzilla account. why not use the time and add a teeny tiny mini comment about the future of this issue while you're already adding a post?
*** Bug 770511 has been marked as a duplicate of this bug. ***
the problem is not easy to fix as you might have guessed from it's age.
*** Bug 784265 has been marked as a duplicate of this bug. ***
Out of curiosity, what is the reason that this bug hasn't been solved in five years? Not important enough? Lack of programmers? Gnome environment has priority? Because KDE isn't used in the enterprise edition? Other reasons?
On 12.2 I stumbled over this issue because I wanted to allow the main display user to shutdown the system despite there might be a root TTY session open. I found a Novell Knowledge Base support article on this http://www.novell.com/support/kb/doc.php?id=7007124 and another discussion here http://comments.gmane.org/gmane.linux.suse.kde/16594 So, we seem to have several options: * link /var/adm/kdm/kdmrc.sysconfig to /dev/null (I think I did this years ago with an old suse distro...) * make the file immutable (why, if it seems not to be missed if /dev/null{ed}?) * edit the script /usr/share/kde4/apps/kdm/read_sysconfig.sh to do what you have configured in /usr/share/kde4/config/kdm/kdmrc (so why use it at all?) Everybody who is confronted with a kdm issue is directed to editing /usr/share/kde4/config/kdm/kdmrc. The existence of /usr/share/kde4/apps/kdm/read_sysconfig.sh is quite "surprising" and I found it only by googling for "/var/adm/kdm/kdmrc.sysconfig" Don't ask me how I stumbled over this file search string... At first I opted for the /dev/null method... but then you loose this nice 12.2 login screen... so now I use a modified /usr/share/kde4/apps/kdm/read_sysconfig.sh. I think the real intention of /usr/share/kde4/apps/kdm/read_sysconfig.sh should be clarified and then a good concept might be created. Right now it seems that the script does too many different things, display manager selection, security, ... Sorry for this long story, but I wasted so much time on this.............
Even though this is an old issue I changed Product and Platform to 12.2 (not shure this survives the commit of this comment)
I propose to remove the status of NEEDINFO from this bug now... I would love to see it being solved when I upgrade to 12.3 (and not heaving a Groundhog Day experience)
(In reply to comment #53) I studied the setup from OS 11.3 (yes, I have a backup) and found the following CLEAN solution for the user shutdown issue: With YAST /etc/sysconfig editor the following THREE parameters must be set: PERMISSION_SECURITY = secure local POLKIT_DEFAULT_PRIVS = standard DISPLAYMANAGER_SHUTDOWN = all Tested on fresh install of OS 12.2 . So, for the case of user shutdown this is merely a documentation issue (?)
*** Bug 811550 has been marked as a duplicate of this bug. ***
Wow. (In reply to comment #52) > Out of curiosity, what is the reason that this bug hasn't been solved in five > years? Not important enough? Lack of programmers? Gnome environment has > priority? Because KDE isn't used in the enterprise edition? Other reasons? From a GNOME perspective - I (personally) think /etc/sysconfig controlling the display manager is complete nonsense. Desktop environments already handle that; why have conflicting distro-specific settings? (In reply to comment #55) > I propose to remove the status of NEEDINFO from this bug now... Actually it looks like the script that's breaking everything was written by Coolo, so that's not an unreasonable NEEDINFO.
*** Bug 831803 has been marked as a duplicate of this bug. ***
*** Bug 813459 has been marked as a duplicate of this bug. ***
This is an autogenerated message for OBS integration: This bug (267903) was mentioned in https://build.opensuse.org/request/show/197850 Factory / kdebase4-workspace
This is an autogenerated message for OBS integration: This bug (267903) was mentioned in https://build.opensuse.org/request/show/197921 Factory / branding-openSUSE
Fixed in openSUSE 13.1 and KDE 4.11.1 (KDE:Release:411 repository)
This bug is not resolved, I have it on openSUSE 13.1 and KDE 4.11.1 (KDE:Release:411 repository). I specially made clean install in Virtual Box and I added KDE:Release:411 repository, then I added one more user and tried to make password less login for him, no luck. This option does not work in KDE's systemsettings.
@ Дмитрий Мишаров it is working. Don't get abuse on openSUSE if you want passwordless login for user aka auto-login then you have to stick on what is written in the documentation Use Yast user to set auto-login for the desired user. http://activedoc.opensuse.org/book/opensuse-start-up/chapter-10-managing-users-with-yast#sec.y2.userman.adv
I dont need autologin (when user has logged in right after boot), I need passwordless login (when in kdm user may just hit enter or doublclick) for certain user and this option does not working on clean install openSUSE 13.1 with or without KDE repos. Steps to reproduce: 1) Download latest image of openSUSE 2) Install it on Virtual Box 3) Create a new user via YAST 4) Set passwordless login for this user from KDE's systemsettings 5) Reboot system 6) Try login without password for user which you've created before and you receive login error
Note in bug 833253 that passwordless users can no longer be created using normal tools.