XDM display manager login loop

G-Known · 11-14-2015, 10:12 PM

I've noticed that whenever I entered my credentials on the login screen, it will reset and revert back to the login screen again. I'm uncertain where's the log for lxdm but this is the conf file:

Code:

 [base]
## uncomment and set autologin username to enable autologin
# autologin=dgod

## uncomment and set timeout to enable timeout autologin,
## the value should >=5
# timeout=10

## default session or desktop used when no systemwide config
 session=/usr/bin/startlxde

## uncomment and set to set numlock on your keyboard
# numlock=0

## set this if you don't want to put xauth file at ~/.Xauthority
# xauth_path=/tmp

# not ask password for users who have empty password
# skip_password=1
## greeter used to welcome the user
greeter=/usr/libexec/lxdm-greeter-gtk

[server]
## arg used to start xserver, not fully function
# arg=/usr/bin/X -background vt1
# uncomment this if you really want xserver listen to tcp
# tcp_listen=1
# uncoment this if you want reset the xserver after logou
# reset=1

[display]
## gtk theme used by greeter
gtk_theme=Clearlooks

## background of the greeter
bg=/usr/share/wallpapers/stripes-lxdm.jpg

## if show bottom pane
bottom_pane=1

## if show language select control
lang=1

## if show keyboard layout select control
keyboard=0

## the theme of greeter
theme=Industrial

[input]

[userlist]
[userlist]
## if disable the user list control at greeter
disable=0

## whitelist user
white=

## blacklist user
black=

Some people suggest that some files are owned by the root and need to change the ownership to the user but that's the case for me.
If there's any advice, it's much appreciated.

ponce · 11-14-2015, 11:25 PM

Quote:

Originally Posted by G-Known

I've noticed that whenever I entered my credentials on the login screen, it will reset and revert back to the login screen again. I'm uncertain where's the log for lxdm

/var/log/lxdm.log

Quote:

but this is the conf file:

Code:

 [base]
## uncomment and set autologin username to enable autologin
# autologin=dgod

## uncomment and set timeout to enable timeout autologin,
## the value should >=5
# timeout=10

## default session or desktop used when no systemwide config
 session=/usr/bin/startlxde

## uncomment and set to set numlock on your keyboard
# numlock=0

## set this if you don't want to put xauth file at ~/.Xauthority
# xauth_path=/tmp

# not ask password for users who have empty password
# skip_password=1
## greeter used to welcome the user
greeter=/usr/libexec/lxdm-greeter-gtk

[server]
## arg used to start xserver, not fully function
# arg=/usr/bin/X -background vt1
# uncomment this if you really want xserver listen to tcp
# tcp_listen=1
# uncoment this if you want reset the xserver after logou
# reset=1

[display]
## gtk theme used by greeter
gtk_theme=Clearlooks

## background of the greeter
bg=/usr/share/wallpapers/stripes-lxdm.jpg

## if show bottom pane
bottom_pane=1

## if show language select control
lang=1

## if show keyboard layout select control
keyboard=0

## the theme of greeter
theme=Industrial

[input]

[userlist]
[userlist]
## if disable the user list control at greeter
disable=0

## whitelist user
white=

## blacklist user
black=

Some people suggest that some files are owned by the root and need to change the ownership to the user but that's the case for me.

which files? have you already changed some permissions?

G-Known · 11-15-2015, 04:34 PM

No, people have suggested that files such as .Xauthority or .xinitrc is root that's causing the issue but that's not the case for me.

G-Known · 11-15-2015, 08:53 PM

I did more research and discovered it's X display manager that's acting up not LXDE. So here's the xinitrc file:

Code:

!/bin/sh
# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps
[ -f $sysresources ] && xrdb -merge $sysresources
[ -f $sysmodmap ] && xmodmap $sysmodmap
[ -f $userresources ] && xrdb -merge $userresources
[ -f $usermodmap ] && xmodmap $usermodmap

# Start the window manager:
if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
    ck-launch-session dbus-launch --exit-with-session startlxde
else
    startlxde
fi

I cannot read the file directory /usr/bin/xdm, tried reinstalling but there's all sorts of weird typos such as: @^V^L^@À^E^@^@^@^@^@^@^@^@^@^@^R^@^@^@ª^F^@^@^@^@^@^@^@^@^@^$
^@^@p©^E^H^B^@^@^@^R^@^L^.

G-Known · 11-15-2015, 09:36 PM

I may have to conclude that this is a bug as if I tried to login several times, it'll load the desktop and also most likely the first time it boots.

bassmadrigal · 11-16-2015, 08:27 AM

Quote:

Originally Posted by G-Known

I cannot read the file directory /usr/bin/xdm, tried reinstalling but there's all sorts of weird typos such as: @^V^L^@À^E^@^@^@^@^@^@^@^@^@^@^R^@^@^@ª^F^@^@^@^@^@^@^@^@^@^$
^@^@p©^E^H^B^@^@^@^R^@^L^.

This is because the file is binary, not a script. You won't be able to view it.

(You can test this using file /usr/bin/xdm and compare it with file /usr/bin/startx, which is a script)

gus3 · 11-22-2015, 04:31 PM

I'm bumping this back to the first page.

I used to use remote XDM occasionally. Then I stopped using it for a while. Then I tried to use it, but in the interim something changed, or broke, and now a successful login leaves me in a loop. The only way out is to switch to a text console, log in as root, and do "telinit 3" (I use runlevel 4 by default). Using Xephyr gives similar results, although killing it is easier than switching runlevels.

I have display management enabled on my desktop, my server, and my Raspberry Pi, but none of them can get to an actual working user GUI.

chris.willing · 11-22-2015, 06:45 PM

Just a thought based on a not dissimilar issue that involved xdm - the actual trigger/cause of that issue was an entry in /etc/bash_completion.d that wasn't entirely posix conformant. For that particular issue, the resolution was to change that particular entry (pulseaudio, as it happens). The connection to xdm was that its Xsession sets the login shell which choked on the "deviant" bash completion script.

Another, possibly better, fix was also proposed to remove posix mode from xdm's Xsession file (as is already done for kdm's Xsession file). See: http://www.linuxquestions.org/questi...ml#post5419799 for a link to a patch to /etc/X11/xdm/Xsession.

If that patch works for you, then there will be (at least) two instances demonstrating a need to update Xsession in the official xdm package.

chris

gus3 · 11-23-2015, 11:15 AM

Well, whaddya know... it's working. I just hadn't tried it in a couple weeks. PulseAudio wasn't the problem (not installed anywhere on my network).

Actually, I'm not sure what the problem was, but I'm pretty sure it got fixed when I did an upgradepkg on every single Slackware-current package. If anything was out of alignment (like an out-of-date X11 library), that probably brought it back in line.