You are not logged in.
With a recent update of Arch linux I found that the login manager responds too slow to user inputs. I am using SLIM as login manager with 'archlinux-darch-grey' as the login theme and with XFCE as the desktop environment.
Once the login screen flashes up, it takes quite a while for SLIM to display the text I have entered for username and move to the password screen when I press enter. It again takes quite a time to respond to the password I enter. This used to happen before also, once in a while. But the response delay was not too much at that time. However, with the latest update the delay has increased like anything and it happens for every boot, which is quite frustrating.
Is there any fix for this?
Last edited by matrix13 (2013-05-10 01:45:18)
Offline
So, everything is fine as soon as you're booted? I used to be a big fan of SLIM myself, but I found it seems to act up in other distros as well. Have you tried lightDM? It's, in my opinion, better, and barely consumes any more resources. Just as easy to configure.
Offline
I would move to lightdm too if it had a basic screen locking integration. I'm using slim with slimlock and it works great! Only issue is that after few relogins it switches back to tty, then I need to restart slim to get it working again. By the way I've encountered this not only on my system.
--
Yeah on no slowness issues for me. Maybe it's PAM slowing down? Try logging in via tty.
Last edited by kellerman (2013-05-06 20:22:58)
Offline
I haven't tried this on Arch yet but there is a nice little program called xtrlock, or you can use xscreensaver for screen locking. Just as a fyi with xtrlock, it basically just turns your mouse pointer into a lock symbol and the only way to get out of it is to type your password and press enter.
Offline
Thank you for the inputs. So it seems SLIM has a few problems. I will try lightDM then.
xtrlock is also new to me. Will try it.
Offline
I dont really like xscreensaver, I prefer more integration with the desktop. Slimlock really can do that, a lot of themes are compatible with it. But of course in the first place there is functionality so I'll probably now try lightdm and how it acts with multiple relogins.
And xtrlock seems to work nice.
edit:
after migrating:
works very well, although there are some little problems
- I cant set png/jpg as background to gtk greeter, works with svg
- the default X cursor is set (no theme)
- i miss the reboot option in gtk menu
Last edited by kellerman (2013-05-07 20:53:02)
Offline
OK. I found that the problem is much more serious than I thought.
I removed SLIM and installed lightDM. I had problems with starting lightDM as the associated daemon did not start and I could not enable it using systemctl. Eventually I fixed it and now lightDM is running.
During the meantime I was using the console login. I noticed that after I feed in the username, it takes a lot of time to ask before asking the password. Once lightDM was up and running, I saw that it takes a lot of time for lightDM to come up and show the login screen.
All this makes me feel that, it is not the problem associated just with the login manager. Something else is causing the huge delay. How do we diagnose this?
Offline
There seems to be some problem with the login mechanism irrespective of what you use to log in. Anyway, maybe strace can help you out.
First login to a tty, or start a terminal from X.
Now get the pid of a getty, say tty2, in which you haven't logged in yet.
Then, do:
# strace -fc -p <PID> -o ./strace.outNow, log in to tty2, and log out immediately after logging in.
Then view the contents of strace.out. It will sort the contents in decreasing order of time taken by each syscall. See which syscalls take the most time, and one of them should be the culprit. Post the output here, so we can help you out.
Offline
@x33a : I tried what you have suggested. I am not sure whether I have followed the correct procedure. This is what I have done.
1. Logged into tty1.
2. Found the PID of tty2.
3. Did strace the way you mentioned.
4. Logged into tty2 and logged out.
The maximum delay I found in
98.92 0.013334 13334 1 wait4
However, I did not find any visible delay in logging into tty2. I realize that the delay is only one time after boot. I had this delay when I logged into tty1 for the first time.
One more thing. Every time when I boot into my machine, my wlan doesn't work. I will have to then do
netcfg wifi_nametwice. Not once. Does this has to do anything with the login delay?
Offline
Since you mention that the delay only happens when logging in for the first time, your issue seems to be similar to this:
https://bbs.archlinux.org/viewtopic.php?id=162855
Also, netcfg has been deprecated in favour of netctl. I hope you are aware of that, and running a fully updated system.
Offline
Apologies for the long delay in replying. I was travelling.
I did the following.
[matrix@black ~]$ systemd-analyze; systemd-analyze blame
Startup finished in 3.944s (kernel) + 42.349s (userspace) = 46.294s
36.669s dhcpcd@eth0.service
3.913s net-auto-wireless.service
1.094s lightdm.service
1.091s systemd-logind.service
477ms systemd-udev-trigger.service
459ms polkit.service
447ms systemd-tmpfiles-setup-dev.service
446ms sys-kernel-config.mount
446ms systemd-vconsole-setup.service
446ms sys-kernel-debug.mount
446ms dev-mqueue.mount
424ms systemd-fsck@dev-sda11.service
411ms dev-hugepages.mount
380ms systemd-remount-fs.service
274ms upower.service
220ms systemd-random-seed-load.service
202ms systemd-user-sessions.service
141ms udisks2.service
140ms alsa-restore.service
135ms systemd-sysctl.service
114ms systemd-update-utmp.service
110ms systemd-journal-flush.service
57ms systemd-tmpfiles-clean.service
32ms systemd-udevd.service
23ms dev-sda10.swap
20ms systemd-tmpfiles-setup.service
16ms home.mount
1ms sys-fs-fuse-connections.mount
943us tmp.mountI find that dhcpcd@eth0.service is eating away most of the time and added to that net-auto-wireless.service. How do I fix this?
Also my machine is up-to date and it still runs netcfg, and not netctl. Shouldn't it be like that?
Offline
I migrated to netctl. But, with every boot up I have to start my wireless profile manually with
netctl start wifi_nameeven after enabling the service using
netctl enable wifi_nameThis is the output of systemd-analyze
[matrix@black ~]$ systemd-analyze; systemd-analyze blame
Startup finished in 3.907s (kernel) + 38.017s (userspace) = 41.924s
32.359s dhcpcd@eth0.service
9.630s netctl@wifi_name.service
...
...Offline