Description of problem:
Synaptic shows up 3 times in the KDE menu: twice under "Administration" and
once under "System". This is due to category bloat in the .desktop file.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install Synaptic.
2. Start KDE.
3. Inspect the menu.
Alternatively, run kbuildsycoca --menutest | grep synaptic to get the 3
entries printed to the terminal.
3 menu entries.
1 menu entry.
We analyzed this during the KDE SIG meeting and found that this is caused by
too many categories being listed in the .desktop file.
Hmm, it shows twice in GNOME too. Settings category looks wrong, but what are
the other places in KDE it shows up?
On F7, it shows up in "System/", "Administration/More System Settings/", and
"Administration/". Removing the (nowadays invalid anyway ) Application and
SystemSetup categories causes it to be show in "System/" only.
And as "Administration/More System Settings" and "Administration" are merged
these days, it actually shows up twice under "Administration" and once
So, what's the recommended setting?
synaptic-0.57.2-14.fc8.x86_64 has "Categories=PackageManager;GTK;System;" and
shows up only once in my KDE menus (in System). I think that's fine.
Yes, it's fixed in the current F8 package. The problem is still there in F7
Once the CVS is back online again I'll submit an F7 build to get this fixed.
Well, I tried building this one for F-7, but it fails w/o even entering the
This is probably unrelated to synaptic and maybe a koji bug, but in case anyone
wants to check the builds and see if I'm doing something wrong, here are the
No bug there, there's no apt-devel >= 0.5.15lorg3.92 in F7 yet. You have to
update and build apt first, then get it included in dist-fc7-override (ask
rel-eng), then build the new synaptic.
Thanks Kevin, I hadn't looked at root.log as I thought that the presence of
build.log implies that the build started. :/
synaptic-0.57.2-13.99.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.