Red Hat Bugzilla – Bug 223507
xdm should use system Xsession file
Last modified: 2014-06-18 05:09:08 EDT
After installing Fedora Core 6, XDM behaves differently. When I first logged
in, it didn't seem to use my ~/.Xclients. I read a little and discovered that
it was looking for xsm. I installed it and created a ~/.xsession file (which
had the same lines as my .Xclients had).
Things somewhat work, however when I log in my fonts are not what they should
be, and some environment settings are not getting set.
Using GDM, things work as they should.
With the assistance of firstname.lastname@example.org, I did the follwowing:
mv /etc/X11/xdm/Xsession /etc/X11/xdm/Xsession.broken
ln -s /etc/X11/xinit/Xsession /etc/X11/xdm/Xsession
Things began to work properly again.
Should not we really use cetralized Xsession from xorg-x11-xinit?
Confirming that this bug still exists in FC7.
*** Bug 242213 has been marked as a duplicate of this bug. ***
Please is there any chance to see this bug fixed in the upcoming F8 release?
Fedora Core 6 is no longer supported, could you please reproduce this with the
updated version of the currently supported distribution (Fedora 7, 8, or
Rawhide)? If this issue turns out to still be reproducible, please let us know
in this bug report. If after a month's time we have not heard back from you, we
will have to close this bug as CANTFIX.
Setting status to NEEDINFO, and awaiting information from the reporter.
[This is mass-filed message to all open Fedora Core 6 bugs related to Xorg or
Gecko. If you see any other reason, why this bug shouldn't be closed, please,
comment on it here.]
I'm still seeing some sort of issue while using XDM.
The sound mixer is unavailable, and the NetworkManager cannot utilize the
gnome-keyring-daemon because the daemon is not started upon login.
I can understand that the gnome-keyring-daemon doesn't start w/ XDM, but the
mixer being unavailable is strange.
Just one nitpicking question -- what's your distro? FC6 is not supported anymore.
Sorry. I'm now using FC8.
:-) :-) :-) (Sorry, but I could not resist... :-)
*** This bug has been marked as a duplicate of 244264 ***