[SOLVED] lxdm on current - unable to login on freshly installed laptop

moesasji · 12-20-2015, 04:24 PM

I have a curious problem logging in on a freshly installed laptop that uses lxdm as login-manager. This is using a fully up to date current, installed today (=current 20151219) and using MLED 14.2 repository. I'm posting this here as it appears to require someone with a deep knowledge of Slackware itself.

The symptom is that despite a valid login I remain on the graphical login-screen (console login using CTRL+ALT+F1 works fine).

I tried the following:

1) If I remove lxdm and drop back to xdm the graphical login works fine on that machine.

2) Hence one would think the problem is the lxdm package, but the exact same setup works without problems on an older laptop (Lenovo T430). Same kernel, same packages, both have intel graphics card, etc. only difference is the physical hardware as the problematic laptop is newer with a Skylake based CPU.

3) There are no obvious error messages in any of the logs or dmesg. Only thing I notice is the following in /var/log/messages when I try to login on the GUI.

Code:

 Dec 20 21:07:59 aurora acpid: client connected from 1175[0:0]
Dec 20 21:07:59 aurora acpid: 1 client rule loaded
Dec 20 21:08:05 aurora acpid: client 1175[0:0] has disconnected
Dec 20 21:10:37 aurora acpid: client connected from 1175[0:0]
Dec 20 21:10:37 aurora acpid: 1 client rule loaded
Dec 20 21:10:42 aurora acpid: client 1175[0:0] has disconnected
Dec 20 21:10:54 aurora acpid: client connected from 1175[0:0]
Dec 20 21:10:54 aurora acpid: 1 client rule loaded
Dec 20 21:10:57 aurora acpid: client 1175[0:0] has disconnected
Dec 20 21:18:48 aurora acpid: client connected from 1175[0:0]
Dec 20 21:18:48 aurora acpid: 1 client rule loaded
Dec 20 21:18:55 aurora acpid: client 1175[0:0] has disconnected

Each cycle of connect; rule; disconnect is a login attempt on the GUI. On the machine that works properly these disconnects only seem to happen on logout, which makes me think this has something to do with acpid, i.e. acpi events. Searching for this error shows that I'm not the first to hit something like this, but I can't find an obvious fix.

4) As this is a new system with a Skylake CPU I upgraded to the latest 4.4.0-rc5 kernel. This problem remains unfortunately.

After these steps I'm out of ideas how to debug this any further. Any suggestions how to find out why lxdm refuses to work on this laptop only?

Bertman123 · 12-20-2015, 05:03 PM

At the login screen for lxdm, what does it say next to desktop? Di yiu have an actual desktop selected, xfce, kde, etc? Default doesn't do anything I've noticed.

moesasji · 12-20-2015, 06:24 PM

Quote:

Originally Posted by Bertman123

At the login screen for lxdm, what does it say next to desktop? Di yiu have an actual desktop selected, xfce, kde, etc? Default doesn't do anything I've noticed.

Jackpot Bertman123, thanks! I can indeed log in if I set the desktop selector to "Xfce Session", it doesn't work if is is set to "default" (which it was set to). Using "default" doesn't work even after a successful log in though the GUI.

The strange thing remains that on the T430 it works fine with the session set to "default", so there somehow is a difference. I removed the package including the /etc/lxdm directory and reinstalled. Even after that it works fine on that machine with the session set to "default". Weird.

Bertman123 · 12-20-2015, 07:14 PM

Glad I could help. There might be a way to set the default in the setup, but I honestly didn't look into it that much once I found a solution. :-)