| 1 |
On Saturday 13 June 2009 11:33:56 Mick wrote: |
| 2 |
> On Saturday 13 June 2009, Philip Webb wrote: |
| 3 |
> > Yet another step reveals the locus of the problem here at least: |
| 4 |
> > (11) try to run 'klauncher' from CLI : "must be started by Kdeinit"; |
| 5 |
> > (12) restart in KDE, fix Krusader + Apwal ; |
| 6 |
> > (13) reboot & restart FB but without 'kdeinit &' in ~/.xinitrc : |
| 7 |
> > Krusader 'open with' ok ! |
| 8 |
> > |
| 9 |
> > So my problem seems to lie in starting 'kdeinit' without the KDE desktop. |
| 10 |
> > It will take another couple of reboots (tomorrow) to confirm this. |
| 11 |
> > Mick mb doing things a bit differently & his problem mb elsewhere. |
| 12 |
> |
| 13 |
> I have rebooted a number of times (it's a laptop), always in xdm/fluxbox, |
| 14 |
> but my Konqueror menus/kcontrol work fine now. I do not have kdeinit in |
| 15 |
> the fluxbox startup file. Once I have booted up I will typically run {kgpg |
| 16 |
> && kmail} to check my mail and occasionally launch konqueror with |
| 17 |
> {kfmclient openProfile webbrowsing}. By that stage kdeinit will be running |
| 18 |
> (when things are normal): |
| 19 |
|
| 20 |
On the odd occasion when I run e17 these days, I run "kcminit" as step 1 after |
| 21 |
logging in. |
| 22 |
|
| 23 |
I have no idea how this actually works, but it fixes odd errors like fonts, |
| 24 |
themes and IIRC once a weird menu problem (the details I forget). |
| 25 |
|
| 26 |
Worth a try. |
| 27 |
|
| 28 |
-- |
| 29 |
alan dot mckinnon at gmail dot com |
Archives