You are not logged in.
Hello is now an upgrade systemd-tools, KDM Auto Login will fail, even if it is to open the testing source to install the latest version of the same is the case.
The error message is:
"System is booting up" click ok
"authentication failed"
Manually enter the account password you can log in normally
Offline
I had the same problem. Moving kdm to the last position in the daemons array of rc.conf fixed the problem for me.
Offline
I have the same issue but KDM was already at the end of the daemons array so no changes to be made here. It may be PAM related so I also tried moving /etc/pam.d/ and resintalling these files with pacman in case of some bad file being present but this made no difference. Checking /var/log/kdm.log does give something interesting involving dbus:
klauncher(588) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(549)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
kdmgreet(549)/kdecore (K*TimeZone*): No time zone information obtained from ktimezoned
Yet dbus is the first daemon to be started in my rc.conf and dbus status is reported as OK with everything else working with it fine. How can I tell if dbus is running when kdm starts? Would it be possible to put in some check at this point and start dbus if that is the problem?
I've had this for the last 3 weeks I think and have tried a number of things but it does not seem to be very widespread as otherwise everyone would be complaining about it.
Offline
As GaDDim wrote, moving kdm to the last postition in rc.conf helped me too.
Offline
Does 'systemctl enable kdm.service' not work ? That's what I used when I played around with systemd...
Offline
Thanks for your replies, still being a problem here.
As GaDDim wrote, moving kdm to the last postition in rc.conf helped me too.
I have always had kdm listed last, hence nothing has changed here so there is another problem afoot.
Does 'systemctl enable kdm.service' not work ? That's what I used when I played around with systemd...
This is what it returns:
ln -s '/usr/lib/systemd/system/kdm.service' '/etc/systemd/system/display-manager.service'
Offline
theshadster wrote:Does 'systemctl enable kdm.service' not work ? That's what I used when I played around with systemd...
This is what it returns:
ln -s '/usr/lib/systemd/system/kdm.service' '/etc/systemd/system/display-manager.service'
...that's what it should return, as I recall. Have you tried rebooting ? Kdm should now work.
Offline
...that's what it should return, as I recall. Have you tried rebooting ? Kdm should now work.
It has been rebooted since I tried that this morning. KDM still does not work correctly. I did also previously try completely removing /etc/pam.d and reinstalling pambase and dependencies and this did not change anything so PAM itself is installed OK.
Offline
Open a terminal and, as root, run 'systemctl --all'
... that should tell you what's loaded/running/failed/in an error state.
Offline
Thanks for that advice, what is returned again suggests a DBus issue:
Failed to get D-Bus connection: No connection to service manager.
Offline
What's the output of:
#ps ax | grep dbus
?
Offline
What's the output of:
#ps ax | grep dbus
?
305 ? Ss 0:00 dbus-daemon --system
691 ? S 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
692 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
1282 pts/1 S+ 0:00 grep dbus
Thanks for the suggestion. Not sure if this is good or bad.
Offline
For comparison, here's mine:
214 ? Ss 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
351 ? S 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
352 ? Ss 0:00 /usr/bin/dbus-daemon --fork --print-pid 4 --print-address 6 --session
764 pts/1 S+ 0:00 grep dbus
...as you can see, a difference on line 1. It looks like your dbus isn't being picked up by systemd.
Have you enabled the 'testing' repo ? Something in your first post suggests you have. If so, this *may* be the problem.
Either way, have you tried re-installing dbus ? [ not from 'testing' ]
Offline
Just as a note: He talked about a systemd package, but they are omnipresent now, it does not mean he has systemd in use...
... but maybe you should, OP. Have a look at the systemd wiki page, the switch was easier than expected.
Online
I've never used testing so that can't be the problem here. DBus has been upgraded since this became a problem aswell. If this is down to systemd that would be a nuisance, I will take a look through the Wiki page anyway.
Edit: Fixed the issue for me by adding init=/bin/systemd to /boot/grub/menu.lst as referenced here:
https://wiki.archlinux.org/index.php/Sy … stallation
Why has this wiki page not been listed on the Arch frontpage with the move to systemd?
I would suggest the OP tries the same although they have not returned to this thread since they started it so maybe they have also solved it.
Last edited by edh (2012-09-01 10:33:55)
Offline
Arch has not moved to systemd yet, there was only the libsystemd package replaced by systemd. You still have to migrate manually, the switch will not be forced on you.
Online
Hello,
Could you solve it?
I can start KDE only in safe mode.
ps ax | grep dbus
350 ? Ss 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork
--nopidfile --systemd-activation
1184 tty1 S+ 0:00 grep dbus
And I have same error. So what can I do?
Offline
Hello all,
I also had this issue, after doing a fresh install a few days ago (my first Arch Linux + KDE setup).
After testing the daemon start order and all kinds of combination, this is what works for me:
- kdm on the last position
- dbus immediately before kdm
My rc.conf:
DAEMONS=(syslog-ng @networkmanager @alsa @crond rpcbind @nfs-common @gpm @vmware dbus kdm)
Putting dbus in the front or in the middle of the startup order doesn't work, it has to be right before kdm.
Hope it helps!
Offline