Bug 156770 - lost menus and kcontrol/kinfocenter stopped working in kde3 after installing kde4
Summary: lost menus and kcontrol/kinfocenter stopped working in kde3 after installing ...
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-27 11:49 UTC by Peter Lunicks
Modified: 2009-01-06 14:00 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Lunicks 2008-01-27 11:49:18 UTC
Version:            (using KDE 3.5.8)
Installed from:    Compiled From Sources
Compiler:          gcc 4.0.3 
OS:                Linux

I had KDE 3.5.5 installed in /opt/kde-3.5.5. It worked fine.
I then installed KDE 4.0.0 in /opt/kde-4.0.0.
I backed up my ~/.kde directory before using KDE 4.
I used KDE 4 then went back to KDE 3
I restored my ~/.kde directory and went back to KDE 3.
Also restored all environment variables back to their KDE values (KDEDIR, KDEDIRS, KDE_PREFIX, PATH).

When I got back to KDE 3, I had several problems.
1) My KMenu was entirely broken. Categories (Games, Graphics, Internet) had the standard 'folder' icon instead of their regular icon. Most of the actual menu entries were missing.
2) kinfocenter shows no modules to view
3) kcontrol shows only one module, "Network", which doesn't actually allow configuring anything. Selecting Network only shows its name in the main area to the right.

I thought that possibly something in my KDE 3 installation had been overwritten. So I installed a fresh KDE 3.5.8 to /opt/kde-3.5.8. I also tried removing ~/.kde and making a new user with no ~/.kde or other config directories in his home directory. Even with a fresh KDE 3 and a fresh user home directory,
the same problems occur.

This is very odd and I have not had problems with KDE 3 like this before.
Normally KDE 3 will always make a default set of menus for a fresh user.

Also, kmenuedit does not show the normal menus either.
One clue might be that kmenuedit displays the following when loading:
kmenuedit: WARNING: Could not read /home/foo/.config/menus/applications-kmenuedit.menu

But I do not know why that would suddenly matter, when KDE 3 menus have always worked before...

kcontrol prints:
kcontrol: WARNING: No K menu group with X-KDE-BaseGroup=settings found ! Defaulting to Settings/

and kinfocenter prints:
kinfocenter: WARNING: No K menu group with X-KDE-BaseGroup=info found ! Defaulting to Settings/Information/

Maybe kcontrol, kinfocenter (and thus KServiceGroup?), and the menu are all looking for a list of items in the wrong place?

Apparently the menus use the ~/.config/menus/applications-kmenuedit.menu and ~/.local/share/applications/ directories, ignoring all KDE's directories and menu information in /opt/kde-3.5.8/share/applnk.
As for kcontrol and kinfocenter, I don't know...

In addition to bug fixes, suggested work-arounds would also be helpful...
Comment 1 Peter Lunicks 2008-01-27 12:27:03 UTC
Well, I found the work-around.
Removed export XDG_DATA_DIRS=/usr/share from /etc/profile and delete ~/.local and ~/.config
Even so, this behavior can't be right for KDE. Leaving the bug open.
Comment 2 Nicolas Ternisien 2008-04-02 09:35:12 UTC

*** This bug has been marked as a duplicate of 156771 ***
Comment 3 Nicolas Ternisien 2008-04-02 09:36:29 UTC
Oups infinite loop of duplicate bugs...
Comment 4 FiNeX 2008-12-09 00:28:04 UTC
This is certainly a packaging/installing problem. Install both KDE version need some attentions.

You should try with more recent KDE version following, for example, the instructions available on the KDE wiki, or for distributions like OpenSuse or Ubuntu which explain how to keep both the two versions.
Comment 5 Dario Andres 2009-01-06 14:00:10 UTC
As FiNeX said this is because packaging issues, so closing as DOWSTREAM.
Check out with an updated KDE distribution to re-open the bug report if the problem is still there