I had installed GWARE a while back for GNOME on Slackware.

It installed ok, but when I logged into KDE I had loads of GNOME menu items in the K Menu!

Now GWARE says the package zzz_gware should have prevented my K Menu being messed up. Looks like it didn't.

So, on the Freerock website it says running kbuildsyooca from Konsole in KDE should fix it. However it came up with an error saying that it doesn't exist.

Another thing, although it seems to put GNOME menu items in KDE, it still has left some things out, like I wanted Totem in my K Menu, but that didn't come up.

Even though I know using K Menu Editor fixes this, but it takes a long time and its extremely boring!

Any help on this would be good.

Thanks,

Kourosh

Its kbuildsycoca. Uninstalling kde-menu, deleting all the menu entries, then reinstalling kde-menu might work.

Just wondering now, since I've seen this issue float up a few times already. Since GWARE GNOME as well as any version is a completely different DE, and in no way associated with KDE, then why the hell is it messing with KDE? I just don't understand that, and it just seems a bit sloppy on the part of the developers.

I think KDE and GNOME stores their menus in the same place. zborgerd can give you better answers, cause he is a GNOME developer and I don't like either DE anyway.

Ok ok, I am biased, and I will admit, and I use KDE, then perhaps BOTH KDE and the GNOME variants must somehow find a better way in where they are storing their own files. I just don't know, /opt/kde/ and /opt/gware/ seems logical to me, but then again I have no idea where GNOME files are stored, let alone all the variants, such as dropline, freerock, etc. Its bad enough that linux distros after slackware like to place system files, and such in non-standard places, and now it seems that the DE, are doing the same. Don't get me wrong, I really like linux, but this is the only downside to it, and thats the fact that each variant, likes to place files in new areas, and muck things up for the more orthodox distros and users.

Many distro vendors now participate in using a common menu system. In KDE, the global menus are stored in /opt/kde/etc/xdg/menus. User modifications to the menus are stored in ~/.config/menus. I have not had the time to better investigate how all of this is supposed to work. However, I did discover that an easy way to create a modified KDE global menu is to perform all menu changes as root, customize to taste, and then move the resulting menu file from ~/config/menus to the common /opt/kde/etc/xdg/menus directory. I don't recall all of the specifics but that's the general idea.

I am unfamiliar with any other desktop environment, but if the distro vendor supports the common menu project (I don't have the links handy at the moment---please search the web), then all of this is supposed to work seamlessly from one distro and desktop environment to another.

I hope this helps.

It's not messing with KDE. Slackware's KDE simply does not support the new Freedesktop menu specifications (yet). The newer gnome and gnome-menus packages are aware of the the new specifications (while KDE is not). KDE must be forcibly told to look in its proper xdg locations.

See here:

http://gsb.freerock.org/faqs/


/opt/ is normally used for "add-on" packages (with static files) that are not part of the normal distribution. While it's fine to assume that these third-party GNOME desktops are "optional add-ons", installing them into /opt/ is asking for trouble. Many of the GNOME-centric libraries are components that must be replaced on a GNOME install/upgrade (to keep things working), and all are (were) typically installed to /usr/ on Slackware. Sure, Slackware no longer includes GNOME, but Slackware does still include a lot of the libraries and apps from ftp.gnome.org... And most are usually really too outdated for something as new as an GNOME 2.12 install and need to be upgraded.

It's pretty safe to assume that most sane packages from either a third-party GNOME distributor or from linuxpackages.net will prefix to /usr/; especially since /opt/bin isn't even in the default system $PATH (which makes it even more out of the question). At least, that's going to be the case when replacement/upgrade libraries and programs are involved. The system is not safe to upgrade with the package manager when you start fooling around in /opt/ and /usr/local/, particularly when a lot of third-party installers (e.g. games, openoffice.org, netscape, etc.) mindlessly blow away files in these locations. There is no telling what kind of stuff, that gets installed there, that will cause some sort of conflict with an existing (original) system library or binary in /usr/. KDE can be an exception because the majority of what it needs is all self-contained. GNOME is not. Slackware's GNOME packages have never gone into /opt/ and the GNOME "upgrades" probably should not either.

I'm so stupid, can't read...

So running kbuildsycoca should recreate all my K Menu?

Gonna have to try that.

Thanks all, oh yeah and thanks for the extra info!

Decided to come back to this thread,

I had a problem whilst trying to install KDE 3.5.

This is what happened:

- I downloaded all KDE 3.5 slackware packages from the KDE website.

- I then transferred them all to my Linux computer

- I checked the MD5SUM of them all by doing:
They were all OK

- I then removed all KDE packages, removed .kde from my root directory (I wanted root to look like KDE default) and removed all packages from /var/log/removed-packages to make space

- Next I installed all KDE 3.5 packages by running:
- Once fininshed, I rebooted (just for good measure)

- I then rebooted into runlevel 4 which was KDM.

- KDM displayed exactly like before except fonts were unclear (un-anti-aliased?) so I logged in as root.

- I ran through the wizard and was brought up with a desktop - without icons on the panel (except K Menu and Konqueror)

- I then checked the K Menu, everything was new (assumed because of KDE 3.5) However MANY icons were missing.

- I thought it might of been because of GNOME so I added:
to the beginning of the startkde script.
Logged out, back in, then ran kbuildsycoca from Konsole.

- Menus now were re-arranged OK but things were still wrong with it (GNOME still interfering)

- So I removed all KDE packages, removed the whole /opt/kde, all .* folders from my root and all other home directorys.

- Reinstalled KDE, made sure to run in runlevel 3 and rebooted.

- Ran startx - with an error saying startkde not found.

- So I switched to runlevel 4:
- Came up with a brand new KDM

- Logged in as root, did the same as before with startkde script etc.

- Same as before, so I gave up, went through K Menu Editor and Control Centre alot, with all accounts, until everything was set up.

- Then I realised there is now a sound delay.

Any Ideas what's happening?

Oh yeah and now it doesn't seem to mount CD's and DVD's - comes with an error saying bad fs type or something.

Thanks,

Vampirite

Ouch! That is some serious borking. I think you need to start from scratch now.

Yeah, its crazy I don't know whats the cause for it.

Running alsaconf, and alsamixer lots didn't help. Plus editing things in Control Centre didn't help either.

GNOME works though.

But seriously, starting from scratch really is going to kill me. I have tweaked, installed and configured loads, and it's annoying going to have to start again!

Being limited to having my whole Slackware installation on one ext2 partition is also annoying, and hard to backup what I need.

One of the nicest thing about Slackware is that the config files are easy to save. You just have to think up which ones you want to save. One option here is to try to clean the system completely of Gnome, then redo KDE.

I could try...

Thats what I'll do, remove GNOME and KDE completely remove all config files associated with them, then reinstall KDE.

And possibly install GNOME later if things go well and it works :-)

I noticed this same delay when I updated from KDE 3.3.2 to 3.4.2/3.4.3. I think delaying the startup sound is by design, but I haven't looked into the issue. I find the delay awkward because the delay period is too long, even with my older hardware. But I suppose the delay helps improve the overall startup time. Who knows.

I enjoy KDE, but the moving target philosophy can be trying at times. For example, after updating KDE to 3.4.2, I noticed that Kate is now hard-coded to a Recent List of 10 items. :angry: There is no Settings option to modify this and editing the config file makes no difference. This mod ticks me off because after a couple of years of setting the Recent List to a larger number, the modification now plays havoc with my mind every time I use the list. I wish the developers had left this one alone!

Oh well, it works worse now. I removed all KDE packages, /opt/kde and all .* in home directories. Then I removed GWARE with the instructions provided. Reinstalled KDE, then GNOME and now...

Exactly the same as before except I can mount, though GNOME now doesn't display icons properly. (I also chmoded them to 777 but that didn't work.)

I think I might really have to start from scratch!