On Saturday 07 February 2004 09:12, Jani-Matti Hätinen wrote:
> Sorry, scratch that.
> Check your environment to see where the KDEDIR variable points to. If
> it's 3.1, check what you have in /etc/env.d/. I have 48kdepaths-3.2.0 and
> 57kdedir-3.2.0, which set the KDEDIR and PATH variables. If th
Hi,
I just upgraded to kde 3.2.0, and I just know I've missed something crucial.
My kicker etc was still the 3.1 version, so I mv'd by ~/.kde to ~/.kde-BAK.
Then restarted X... and kicker didn't start. It was still looking for libs
in /usr/kde/3.1/*. For now I just just "mv /usr/kde/3.1 /us
On Thursday 10 July 2003 10:42 pm, Joseph A Nagy Jr wrote:
> On Thursday 10 July 2003 10:04, Joseph A Nagy Jr wrote this in an
>
> attempt to be witty and informative:
> > On Thursday 10 July 2003 05:57, JG wrote this in an attempt to be
> > witty
> >
> > and informative:
> > > i'm having the same
Anyone seen this? When I try to launch konsole via kdeinit (ie from the
taskbar, Alt-F2, or kdemenu in kde), it won't launch. For the taskbar icon
only, I get an error message:
KDEInit could not launch 'konsole'
I can launch fine from a shell session (ie an xterm/Eterm/ another konsole
etc)
Hi,
I recently upgraded to xfree 4.3.0-r2, nividia-kernel 1.0.4363-r1 and
nvidia-glx 1.0.4363. Now things have gone very, very wrong.
If I start up kdm via /etc/init.d/xdm, X consumes 100% of cpu, and I haven't
yet seen gdm load. I can startx manually - it takes an age (ie 5-10 minutes)
con
On Saturday 08 March 2003 9:11 pm, [EMAIL PROTECTED] wrote:
> Any graceful way to recover from, uhhh, accidentally whacking
> "/etc/init.d"??
Sure... just restore from your most recent backup! Oh... oops. ;o) I guess
you could do a "qpkg -f /etc/init.d", to determine which packages you have
