On Saturday 13 June 2009, Alan McKinnon wrote:
> On Saturday 13 June 2009 11:33:56 Mick wrote:
> > On Saturday 13 June 2009, Philip Webb wrote:
> > > Yet another step reveals the locus of the problem here at least:
> > > (11) try to run 'klauncher' from CLI : "must be started by Kdeinit";
> > > (12) restart in KDE, fix Krusader + Apwal ;
> > > (13) reboot & restart FB but without 'kdeinit &' in ~/.xinitrc :
> > > Krusader 'open with' ok !
> > >
> > > So my problem seems to lie in starting 'kdeinit' without the KDE
> > > desktop. It will take another couple of reboots (tomorrow) to confirm
> > > this. Mick mb doing things a bit differently & his problem mb
> > > elsewhere.
> >
> > I have rebooted a number of times (it's a laptop), always in xdm/fluxbox,
> > but my Konqueror menus/kcontrol work fine now. I do not have kdeinit in
> > the fluxbox startup file. Once I have booted up I will typically run
> > {kgpg && kmail} to check my mail and occasionally launch konqueror with
> > {kfmclient openProfile webbrowsing}. By that stage kdeinit will be
> > running (when things are normal):
>
> On the odd occasion when I run e17 these days, I run "kcminit" as step 1
> after logging in.
>
> I have no idea how this actually works, but it fixes odd errors like fonts,
> themes and IIRC once a weird menu problem (the details I forget).
>
> Worth a try.Thanks Alan, I will remember to try this next time the menus go sideways for me. I can't recall if I mentioned it that running kbuildsycoca --noincremental only produced a result when I was logged in KDE/kdm *and* ran the command in konsole, but not in aterm ... -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
