Registered Member
|
[edit]solution[/edit]
Alright, I'm stumped. I recently installed KDE 4.2 on my system, and I've been having a horrible time getting everything working all day long. I finally have *almost* everything up and running again. However, I've run into a problem: kdm is not executing the Xsessions script pointed to by my kdmrc file. I do, however, know that the Xstartup script is executing properly, as I added the line:
to the Xstartup script located in the same folder as the Xsession script. A similar line placed at the top of the Xsession script yields no effect, so I am presuming that kdm is not even executing the command. As such, kdm does not open the desktop environment that I tell it to - it always opens up the failsafe (xterm). From xterm, I can get kde up and running just fine by executing "startkde". In fact, I have temporarily edited my kdmrc file to use "/usr/bin/startkde" as my failsafe client. Anyways, this is the relevant portion of my kdmrc file:
And this is what /usr/share/config/kdm/Xsession looks like:
I'm at the end of my rope here, and I'm completely confused as to how I can get this working the way it should be. I highly doubt that using "startkde" as the failsafe is the best way to do things. I am also pretty certain that I am referring to the correct files, unless of course my file system is lying to me. Any help would be greatly appreciated.
Last edited by Taedrin on Wed Feb 11, 2009 3:14 am, edited 1 time in total.
|
Administrator
|
On openSUSE, the configuration of KDM is not used, instead it uses the configuration of XDM. You may wish to check this.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
It's definitely not using xdm's config, as xdm is not starting xterm, but kdm is.
More information: After a bit of research (IE, finally figuring out where the log file was), I discovered this line in /var/log/messages:
ls -l /usr/share/config/kdm/Xsession yields this output:
just in case kdm needs to write to the file, for some odd reason, I even temporarily did a chmod 777 on it:
no luck - kdm still is not reading the Xsession script. |
Administrator
|
Do you have Apparmor or SELinux active on your machine? If so, try shutting them down. They are known to cause obscure access denied issues like this.
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
Registered Member
|
Hello,
I had the same problem, and thanks to you I notice the message in /var/log/messages The solution is not the file itself, but the path. Check all directories!
As user I had no permission to /usr/share/config So I made
Good Luck. |
Registered Member
|
I just emerged kdelibs and notice this message. |
Registered Member
|
That fixed it, thanks for your help! |
Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell