| View previous topic :: View next topic |
| Author |
Message |
musv
Advocate
Joined: 01 Dec 2002
Posts: 3337
Location: de
|
 Posted: Thu Jul 23, 2015 5:03 am Post subject: [solved] Failed to login with KDM |
 |
|
Good morning,
I've installed on my notebook KDE 5 - first from portage later I switched to the KDE overlay. Of course KDE5 still needs some time to mature. So I switched back to KDE4.
And here I'm at the point, that I'm unable to login via KDM.
Issue:
KDM simply doesn't accept the password. I get always: "Login failed." There's no approach to load the desktop or to do some other activity.
What works:
Starting the KDE desktop or other window managers (using e16) via startx works without problems.
What I've tried already:
- removed the KDM config in /usr/share/config/kdm
- removed ~/.kde ~/.kde4 ~/.config/*kde* (every kde-related stuff in .config)
- created a new user and tried to login
- configured KDM via systemsettings (allowed users) (btw. where are they saved?)
Logs:
(using Systemd instead of openrc)
| /var/log/kdm.log: | kdmgreet(2200)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
(II) Server terminated successfully (0). Closing log file.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
kdmgreet(2199) KdmPixmap::definePixmap: Cannot find wallpaper "Air"
klauncher(2300) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(2199)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server" |
appears always at the startup of KDM. Dbus is running:
| systemctl status dbus: |
● dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib64/systemd/system/dbus.service; static; vendor preset: enabled)
Active: active (running) since Do 2015-07-23 06:43:20 CEST; 16min ago
Docs: man:dbus-daemon(1)
Main PID: 2147 (dbus-daemon)
CGroup: /system.slice/dbus.service
└─2147 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation |
How do I get to motivate KDM to accept my password?
Last edited by musv on Mon Sep 07, 2015 5:21 am; edited 2 times in total |
|
| Back to top |
|
 |
musv
Advocate
Joined: 01 Dec 2002
Posts: 3337
Location: de
|
| Posted: Mon Jul 27, 2015 1:57 pm Post subject: |
|
|
For unknown reasons some pam files were missing:
| /etc/pam.d/kde: | #%PAM-1.0
auth required pam_nologin.so
auth include system-local-login
account include system-local-login
password include system-local-login
session include system-local-login |
| /etc/pam.d/kde-np: | #%PAM-1.0
auth required pam_nologin.so
auth required pam_permit.so
account include system-local-login
password include system-local-login
session include system-local-login |
I have never studied the internals of pam. So I don't have any clue, how it works. But after creating the files above, the login was possible again. |
|
| Back to top |
|
|
LubosD
Apprentice
Joined: 30 Jun 2005
Posts: 211
Location: Czech Republic
|
| Posted: Sat Sep 05, 2015 8:53 pm Post subject: |
|
|
Today I faced the same problem in the same scenario. Thanks a lot!
Something apparently removes files installed by kdebase-pam. |
|
| Back to top |
|
|
davidm
Guru
Joined: 26 Apr 2009
Posts: 557
Location: US
|
| Posted: Sat Sep 05, 2015 9:24 pm Post subject: |
|
|
| LubosD wrote: | Today I faced the same problem in the same scenario. Thanks a lot!
Something apparently removes files installed by kdebase-pam. |
Just wanted to say that I faced the same problem. Perhaps the ebuild should trigger a rebuild under certain circumstances? Just emerging it wasn't enoung but I also had to do 'dispatch-conf' to get the two necessary files in place. |
|
| Back to top |
|
|
|
Desktop Environments
