|
Home > Archive > Red Hat General > January 2004 > Help with kde startup failure.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Help with kde startup failure.
|
|
|
| Iv been using Fedora for about a month and suddenly kde (gnome also) fails
at login. This only effects my "normal" account, root login works fine.
..xsessions-errors contains:
/etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w
/var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h "" -l ":0" "sj"
/home/sj/.Xclients-default: line 2: exec: startkde: not found
I can use a failsafe login and start kde manually. Anyone know whats going
on?
--
Remove underscores from email address to respond
| |
|
| sj thought it would be good to say:
quote:
> Iv been using Fedora for about a month and suddenly kde (gnome also) fails
> at login. This only effects my "normal" account, root login works fine.
>
> .xsessions-errors contains:
>
> /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and
> utmp /etc/X11/gdm/PreSession/Default: running: /usr/bin/X11/sessreg -a -w
> /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h "" -l ":0"
> "sj" /home/sj/.Xclients-default: line 2: exec: startkde: not found
>
>
> I can use a failsafe login and start kde manually. Anyone know whats going
> on?
No, but you could try
which startkde
from your usual account (text mode, obviously), then check that the path is
in your $PATH.
Pip
| |
|
| Pip wrote:
quote:
> sj thought it would be good to say:
>
>
> No, but you could try
>
> which startkde
>
> from your usual account (text mode, obviously), then check that the path
> is in your $PATH.
>
>
>
> Pip
Yes it is on the search path, that was the first thing I checked.
--
Remove underscores from email address to respond
| |
|
| sj thought it would be good to say:
quote:
> Yes it is on the search path, that was the first thing I checked.
Of course it is. Sorry, but we have to start from basics. Just in case.
Is the error any different if you do a switchdesk to gnome? Or rather, what
difference is there? How about if you put the path in to .Xclients-default?
If you can set up a new user, log in to that account and start up KDE, then
it would definitely indicate something in your .bash files is misleading
the system. Has anything changed there recently?
Pip
| |
| Scott Lurndal 2004-01-23, 7:14 pm |
| Pip <Pip@cwci.TheKinkyUnderwear.com> writes:quote:
>sj thought it would be good to say:
>
>
>Of course it is. Sorry, but we have to start from basics. Just in case.
And, just because it is in the search path when you are logged into
an interactive shell, doesn't mean that it is in the search path when
the .xinitrc file or other X startup script is run.
See for examples /usr/lib/X11/xdm/kdmrc, /usr/lib/X11/xdm/Xsession, et. al.
scott
quote:
>Is the error any different if you do a switchdesk to gnome? Or rather, what
>difference is there? How about if you put the path in to .Xclients-default?
>If you can set up a new user, log in to that account and start up KDE, then
>it would definitely indicate something in your .bash files is misleading
>the system. Has anything changed there recently?
>
>
>Pip
| |
|
| It is path related. A while back I removed the current directory './' from
my search path in .bash_profile. I typically stay logged in for weeks on
end so didn't notice the problem until now. Not real sure why the current
directory is required but it apparently is. I suspect it is as Scott
suggested.
Thanks all for your help
Scott Lurndal wrote:
[QUOTE][color=darkred]
> Pip <Pip@cwci.TheKinkyUnderwear.com> writes:
>
> And, just because it is in the search path when you are logged into
> an interactive shell, doesn't mean that it is in the search path when
> the .xinitrc file or other X startup script is run.
>
> See for examples /usr/lib/X11/xdm/kdmrc, /usr/lib/X11/xdm/Xsession, et.
> al.
>
> scott
>
--
Remove underscores from email address to respond
|
|
|
|
|