Description of problem:
I switched to KDM to see if it was any less horrible than GDM, and found that
it apparently doesn't have any idea how to run ~/.xsession if my
~/.dmrc file is set to xinit-compat.
As soon as I login, I get logged out again as the login script apparently
just exits. I added echo commands to my ~/.xsession file (which GDM runs
just fine), and there is no evidence that it ever got as far as running
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. edit /etc/sysconfig/desktop
2. say DISPLAYMANAGER=KDE
3. Have a ~/.dmrc file that looks like:
4. Get logged out as soon as you login
Run my ~/.xsession file
rpm -q xorg-x11-xinit-session
In the meantime, I'll see if I can reproduce.
Curious, what is the contents of your ~/.xsession ?
rpm -q xorg-x11-xinit-session gives:
It works fine when I run GDM.
My .xsession file is kinda complex and invokes some programs I wrote
myself, but for what it is worth, here it is:
-rwxr-xr-x 1 tom users 1942 Mar 16 19:53 /home/tom/.xsession*
exec >> $HOME/.xsession-errors 2>&1
echo Starting X session `date`
killall -9 gnome-keyring-daemon
ps f -u tom
# Try everything possible to disable every kind of power saver mode.
# The radeon driver seems to flake out the monitor after power saver
# kicks in 1st time...
#xset s off
#xset dpms 0 0 0
#setterm -blank 0
#setterm -powersave off
#setterm -powerdown 0
if [ -z "$SSH_AUTH_SOCK" ]
echo .xsession starting ssh-agent
eval `ssh-agent -s`
echo ssh-agent already started
if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]
echo .xsession starting dbus
eval `dbus-launch --sh-syntax --exit-with-session`
echo dbus already started
# Tricky bit - the /usr/libexec/gnome-settings-daemon program is good to
# run to revive the font settings, but it also revives all sorts of
# useless crap I don't want, so start it, wait a bit and then remove
# all the crap it adds to the xrdb database.
# Breaking news! Every damn time I connect from work via VNC, the next
# time I login to the console X session, I get a $#@! popup about
# "The X system keyboard settings differ from your current GNOME
# keyboard settings." After near infinite amounts of poking sticks
# in random holes, I finally discovered that the $@#! gconf keys
# under /desktop/gnome/peripherals/keyboard/kbd.sysbackup need to
# be reset to make this go away, so just always reset that key before
# starting gnome-settings-daemon.
/usr/bin/gconftool-2 --recursive-unset /desktop/gnome/peripherals/keyboard/kbd.sysbackup
xrdb -all -remove
xrdb -load $HOME/.Xdefaults
ps f -u tom
xmessage -geometry +0-0 -buttons 'to Log Out':1 -default 'to Log Out' 'Click Here'
if [ "$kill_agent" = "yes" ]
I notice that the /usr/share/xsessions/xinit-compat.desktop file is the
only one with a complex command to run as the Exec= parameter. I wonder
if kdm is trying to do a direct exec of the line rather than running
it through a shell to interpret the arguments properly?
I can reproduce the problem alright.
Replacing /usr/share/xsessions/xinit-compat.desktop Exec= with either
Exec=sh -c 'exec ~/.xsession || exec ~/.Xclients || exec /etc/X11/xinit/Xclients'
makes it work. Not sure how/why the " characters are causing mischief here.
I personally suspect kdm is attempting to run the command:
'sh' '-c' '"exec' '~/.xsession' '||' ... etc.
anyway, I made a script in /usr/local/bin that runs the command
exec ~/.xsession || exec ~/.Xclients || exec /etc/X11/xinit/Xclients
then made a new .desktop file in /usr/share/xsessions that just
runs that script, and I can login now with KDM.
Same problem here, is this now a 'xorg-x11-xinit-session' script bug or a KDM/KDE bug? And would the workaround from comment #4 (' instead of ") work also for GDM? Because then a new 'xorg-x11-xinit-session' script would fix the problem.
> And would the workaround from comment #4 (' instead of ")
> work also for GDM?
Good question, if someone could help test that, it would be great (I'll do so myself eventually when I accumulate enough round-tuits).
Rex, how many round-tuits you got saved up?
Steven M. Parrish - KDE Triage Master
- PackageKit Triager
Fedora Bugzappers volunteer triage team
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
I strongly suspect this is still valid, rebasing.
Withdrawing some round-tuits from savings to investigate per comment #7
*** Bug 540365 has been marked as a duplicate of this bug. ***
Dup'ing against bug #540546 , where we're working to simplify xinit-compat instead.
*** This bug has been marked as a duplicate of bug 540546 ***