You are not logged in.
Hello
I have a strange behaviour with GDM/Gnome 3.10, on a Archlinux fresh install (December, 27th).
[ISSUE]
If I configure systemd to launch gdm (systemctl enable gdm.service) and then reboot the system, I can login but
(A) when I lock the screen or the laptop goes to sleep, on wake up I cannot authenticate myself:
if I type the wrong password it complains about it, but if I type the correct password, the
field blanks and nothing happens.
Also on the log there are lines (2 lines for each authentication awith correct password attempt):
Jan 10 13:57:24 scoobydoo gdm[401]: GdmSlave: could not fetch type of session 'c1': No such file or directory
Jan 10 13:57:24 scoobydoo gdm-password][1089]: gkr-pam: unlocked login keyring
Jan 10 13:57:19 scoobydoo gdm[401]: GdmSlave: could not fetch type of session 'c1': No such file or directory
Jan 10 13:57:19 scoobydoo gdm-password][1084]: gkr-pam: unlocked login keyring
I can still log in thru virtual console and reboot the system
(B) when I plug-in a USB stick, to mount it I have to authenticate myself
(C) the airplane switch on Gnome Settings/Network Panel is completely missing
[WORKAROUND]
Investigating by myself I discovered a workaround I can live with (but I'd rather prefer to fix the main issue).
If I reconfigure systemd to disable gdm and enable multi-user (systemctl enable multi-user.target), then I log-in
as root and *manually* start gdm (systemd start gdm.service); now I can log-in as user and...
(1) everything works as expected: I can wake up after a sleep or a screen lock; I do not have to authenticate
for USB stick mounts and the airplane switch is available and working
(2) nobody (no users, nor root) can authenticate on tty1; only tty2..6 (on my /etc/securetty there are:
"console, tty[1-6], ttyS0, hvc0"), not really an issue but it is puzzling me
(3) obviously I have to manually start the "bumblebeed" daemon
So I added "/usr/lib/systemd/system/gdm.service" in the "/etc/systemd/system/multi-user.target.wants",
but the behaviour is exactly the same as described on the "issue" part.
Things are working as expected only if I log-in as root and manually type the start command for gdm.service.
This is the /etc/systemd/system subtree:
/etc/systemd/system
├── dbus-org.freedesktop.ModemManager1.service -> /usr/lib/systemd/system/ModemManager.service
├── dbus-org.freedesktop.NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
├── dbus-org.freedesktop.nm-dispatcher.service -> /usr/lib/systemd/system/NetworkManager-dispatcher.service
├── default.target -> /usr/lib/systemd/system/multi-user.target
├── getty.target.wants
│ ├── console-getty.service -> /usr/lib/systemd/system/console-getty.service
│ └── getty@tty1.service -> /usr/lib/systemd/system/getty@.service
├── graphical.target.wants
│ └── bumblebeed.service -> /usr/lib/systemd/system/bumblebeed.service
└── multi-user.target.wants
├── cronie.service -> /usr/lib/systemd/system/cronie.service
├── ModemManager.service -> /usr/lib/systemd/system/ModemManager.service
├── NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
├── nginx.service -> /usr/lib/systemd/system/nginx.service
├── php-fpm.service -> /usr/lib/systemd/system/php-fpm.service
└── remote-fs.target -> /usr/lib/systemd/system/remote-fs.target
Does anybody has an idea on how to fix the problem? Or at least where to investigate?
Also I'm curious on what could be the cause for it.
Regards,
Andrew
Offline
You're not the only one, see https://bbs.archlinux.org/viewtopic.php?id=163605
Also, looking at the gdm source this might be systemd related; the message actually comes from sd_session_get_type which is defined in systemd.
Offline
Answering my own post. Finally I solved it.
First of all, "loginctl show-session $XDG_SESSION_ID" gave me:
...
Class=user
Active=no
...
and reading from:
https://wiki.archlinux.org/index.php/Ge … ermissions
[...] make sure that X runs on the same tty where the login occurred. This is required in order to preserve the logind session.
I knew that "Active" should be "Yes".
At the end I was able to fix this situation with:
systemctl disable console-getty
(I had "enable" the console-getty service) after a reboot all of the problems reported on my initial post are fixed
Offline
Thanks for sharing, might be useful for others too!
Offline