You are not logged in.
Pages: 1
Hi,
I recently changed my display manage from xdm to lightdm. xdm used to invoke $HOME/.xinitrc . I am using awesome as my window manager with no DE. I had xautolock invocation and awesome messages being redirected to file (both stdout an dstderr) . Now i see in lightdm never calls this $HOME/.xinitrc . So the xautolock never runs and redirection of awesome never happens. awesomewm launches correctly. I want to know from where does lightdm detects to launch awesome and how do i make the xautolock and redirection work again?
Offline
Have you read https://wiki.archlinux.org/index.php/LightDM ?
https://wiki.archlinux.org/index.php/Li … _from_SLiM says you should use xprofile instead of .xinitrc.
Offline
I assume moving ~/.xinitrc to ~/.xprofile would solve the xautolock problem. But the redirection of awesome output and error stream to file problem ? The slim part states specifically that i should not move the window manager calls to ~/.xprofile I would like to know how has lightdm know that it has to call awesome wm. I read the wiki on lightdm but it does not answer how lightdm has decided to call awesomewm.
Offline
.xprofile is like .profile for X, so mainly to set environment variables. To run commands like xautolock, .xsession is more appropriate.
Lightdm reads .desktop files from /usr/share/xsessions to find the available sessions. You get to pick one when you login (unless a specific greeter hides the session list). The latest slim also uses this directory, but it still passes the executable name to .xinitrc. Lightdm uses /etc/lightdm/Xsession.
Last edited by Raynman (2013-10-07 16:06:12)
Offline
When I was first messing around with bspwm - whose default examples center on ~/.xinitrc - I used the following two files to get LightDM to use mine. Maybe this can be an option for you.
/usr/share/xsessions/custom.desktop
[Desktop Entry]
Encoding=UTF-8
Name=Custom
Comment=Launch a session defined by your ~/.xinitrc
Exec=/usr/bin/custom-session
Type=XSession/usr/bin/custom-session
#!/bin/bash
/bin/bash --login -i $HOME/.xinitrcNote that I do not know how necessary those options to bash are. As I recall, I just copied them directly from my slim.conf.
.xprofile is like .profile for X, so mainly to set environment variables. To run commands like xautolock, .xsession is more appropriate.
Lightdm reads .desktop files from /usr/share/xsessions to find the available sessions. You get to pick one when you login (unless a specific greeter hides the session list). The latest slim also uses this directory, but it still passes the executable name to .xinitrc. Lightdm uses /etc/lightdm/Xsession.
I created xautolock.desktop with the following content:
[Desktop Entry]
Name=xautolock
Comment=X server basic screen lock program
Exec=xautolock -time 15 -locker slock "&"
Type=ApplicationBut it never gets called. I have this placed in /usr/share/xsessions/ . There is also awesome.desktop in that path which i have edited like below:
[Desktop Entry]
Name=awesome
Comment=Highly configurable framework window manager
TryExec=awesome
Exec=awesome ">> ~/awesome-stdout.log 2>>/awesome-stderr.log"
Type=ApplicationThat also does not output to those redirections. So i guess /usr/share/xsessions/*.desktop is not being called.
Offline
Maybe reread my post? xautolock does not belong there and lightdm lets you pick one of the available sessions; it doesn't "call" desktop files. The Exec line of the desktop file is probably not directly interpreted by a shell, so you need to invoke one explicitly if you want to do redirections. See aoba's example.
Offline
Thanks Raynman, now i understand what is happening. I will implement aoba example and i think it will make it work the way xdm used to do of invoking ~/.xinitrc
Offline
aoba implementation broke the lightdm and the screen would flicker and never reach the login screen. So i removed the custom.desktop and moved back awesome.desktop and got back to working awesomewm.
Offline
The example I posted will not work if /usr/bin/custom-session is not executable, or if you fail to launch your WM/session from your ~/.xinitrc .
Pages: 1