I also had a problem with the KDE menu missing after the upgrade to 3.5.10
I've investigated starting from the message form kbuildsycoca and found a
solution to get the KDE menu to be build. I found that in ~/.config/menus/
nothing was there as expected by kbuildsyscoca
So I did:
Copy
090614 Tal2baro wrote:
I also had a problem with the KDE menu missing after the upgrade to 3.5.10
I've investigated starting from the message from kbuildsycoca
found there was nothing in ~/.config/menus/ expected by kbuildsyscoca
So I copied /usr/kde/3.5/etc/xdg/menus/ content to
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 :
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
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
090613 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
090613 Philip Webb wrote:
It looks as if the problem here is that if 'kdeinit' is started
without an existing desktop to relate to, some connection is not made.
I've investigated further can't find which file Krusader uses
to remember its file associations. However, I did find the changelog
On Thursday 11 June 2009, Philip Webb wrote:
090611 Philip Webb wrote:
You can test this by restoring the settings in KDE,
then without rebooting check they're there in Fluxbox,
then reboot see what has happened, presumably they wb lost again.
Actually, there are 2 possibilities, at
090612 Mick wrote:
I've rebooted twice with same kernel (gentoo-2.6.29-r5)
and the settings seem to have stuck.
Not sure what I've done differently before to cause the settings to be lost.
No changes of kernel here (same as yours).
I've experimented with the same experience as you :
(1) (with
Further steps reveal something re the problem:
(8) reboot: restart KDE: ok; (9) restart FB: Krusader 'open with' ok
(yes, these repeat steps 6-7 in the previous msg);
(10) reboot: restart FB : try Krusader: Cannot talk to klauncher !
(click to close msg box) when Krusader starts, 'open
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
090611 Mick wrote:
I spoke too soon.
This morning same story ... Menus are not present and running
There must be a more intelligent fix to this than me booting into KDE
every time I want to use a KDE application ?
What's up with your KDE menu Philip?
Were you able to make the changes stick?
090611 Philip Webb wrote:
You can test this by restoring the settings in KDE,
then without rebooting check they're there in Fluxbox,
then reboot see what has happened, presumably they wb lost again.
Actually, there are 2 possibilities, at user login at reboot,
so both need checking
13 matches
Mail list logo
