Bugzilla – Bug 127516
.xsession doesn't seem to work
Last modified: 2005-10-12 13:14:34 UTC
In SUSE 9.3 i had a simple .xsession file to do some keymappings for my multimedia keyboard #!/bin/bash -l /usr/X11/bin/xmodmap -e "keycode 223 = XF86Standby" /usr/X11/bin/xmodmap -e "keycode 130 = XF86WWW" /usr/X11/bin/xmodmap -e "keycode 236 = XF86Mail" etc I created an .xsession file (executable) in my homedir under SUSE 10, and kdm doesn't start my kde. If I go to init 3, and i do startx, .xsession is ignored. Is this a bug or is .xsession maybe depricated ?
Could you give me some more details by attaching your .xsession file so I can try to reproduce this problem? Thanks.
Created attachment 53621 [details] my .xsession
Could you attach your .xsession-errrors? Thanks.
Created attachment 53645 [details] my .xsession-errors please notice, trying to login from kdm the .xsession-errors is just empty... so the content of this file is generated after the startx (login from kde if .xsession doesn't work like i said in the ticket).
BTW, I can't reproduce this problem when using your .xsession file. The kde session is started without any problems by KDM.
Can't you simply take the .xinitrc.template file, rename it to .xinitrc and add the xmodmap commands you need?
that's ok for me ... but it's still strange why it doesn't work any longer if you try my .xsession file, login from kdm, did it really load the requested settings ?
I couldn't find these settings after login, but it might have been overwritten at a later point.
I just investigated again. You need a complete replacement for xinitrc in your .xsession file, not only some additional commands like xmodmap. Then it shouldn't matter if you use .xsession or .xinitrc. startx only reads .xinitrc. Therefore many users create a .xinitrc and create a symlink .xsession to it. Settting to INVALID therefore.