[SOLVED] XDM login window loops trying to start i3 session in Slackware64 14.2
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
XDM login window loops trying to start i3 session in Slackware64 14.2
Hi,
I have installed slackware64 14.2 with i3wm. I am having trouble logging into i3 using xdm. XDM login window always loops back to login window. In .xsession-errors, this message is found.
Code:
xdm authorization key matches an existing client:i3 cannot open display
Well I don't use it, but I've checked portage for the list of files and there seems to be a session file /etc/X11/Sessions/i3wm
Maybe locate this file and see how it's starting the session, or point xinitrc symlink to that file, other than that I have no idea.
I've used startfluxbox in ~/.xsession and that's working fine.
The scripts /etc/X11/xinit/xinitrc.i3, /etc/X11/xinit/xinitrc, ~/.xinitrc, ~/.xsession are all identical, yet it fails to start i3 session. So I replaced all the code in .xsession with "exec startx" and it started working. The man page of startx said it reads the .xinitrc file from the home directory for startup scripts, which is great that I am not missing anything of the default script generated by "xwmconfig", but .xsession should have worked. Other out of the box DM/WM's don't have this problem. I also faced it after installing mate desktop.
Some window managers seem not to like being started via dbus-launch and will result in the error you're seeing. I think it has something to do with whether or not they fork()+exec() themselves and whether they still have the same PID that dbus-launch used when they XOpenDisplay(). The XDM message you posted is typically what you see in this case. If you take a look at /etc/X11/xinit/xinitrc.blackbox and the /usr/bin/startblackbox that it invokes you'll see an approach to starting dbus and the window manager which I've found to be reliable and should work for you. I use something similar for starting 'dwm'.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.