bug triage: kmenuedit / kbuildsycoca ignoring /usr/share/applications/kde4

Harald Sitter apachelogger at ubuntu.com
Sat Jun 6 09:32:05 BST 2009

On Samstag, 6. Juni 2009 03:24:49 Jason Straight wrote:
> I'm considering filing a bug, but maybe I could use a primer on the
> operations of the kde menu, editor and kbuildsycoca
> Concerning /usr/share/applications/kde4/amarok.desktop:
> - shows in kde launcher, and lancelot (verified by changing Generic Name
> field)
> - running kbuildsycoca --menutest or kbuildsycoca4 --menutest piped to
> grep amarok shows nothing
> - kmenuedit has no amarok entry for me to edit
> - creating a symlink in /usr/share/applications makes kbuildsycoca
> report it, and kmenuedit can now see it in "Multimedia"
> - After creating the symlink and editing Amaroks' entry with kmenuedit,
> the changes do not appear when kmenuedit is reopened, nor in the app
> menu, although there is an amarok.desktop file in
> ~/.local/share/applications which should override Amarok for this user -
> right?
> NOTE: This is with Amarok 2:2.1mysql5.1.30-0ubuntu2~jaunty2
> I thought the kde app menus got their data from the ksycoca files in
> /var/tmp, apparently this isn't the case since they see apps ksycoca
> doesn't?
> Thanks

me at apoc { ~ }$ kbuildsycoca4  --menutest | grep -i amarok
Multimedia/     amarok-nightly.desktop  /usr/share/applications/amarok-
Multimedia/     amarok-nightly-kcm-phonon.desktop       
Multimedia/     kde4-amarok.desktop     

Seems to work just fine. I would assume there is some weird condition on your 

Anyway, if you report a bug, please make sure to attach the amarok.desktop 
file, as well as screenshots of what you did to proof the entry in the menu is 
the one from the desktop file. Also, please compress and attach the directory

But before you do that, you might wanna try
kbuildsycoca4 --noincremental --menutest | grep -i amarok
That should fix the sycoca if there is some internal breakage that is 
preventing Amarok from showing up (e.g. you machine crashed while the sycoca 
file was being written or something like that).

More information about the kubuntu-devel mailing list