Intrepid: Kubuntu Nvidia setting appears in applications->system and applications->settings

[Dave Morley]

Binary package hint: nvidia-settings

RELEASE: Intrepid
CD/DVD VARIANT: 32bit Kubuntu Alternative cd
ISO BUILD: 20080914

SYMPTOMS: Nvidia setting appears in both apps->system and apps->settings and should only apper in one or the other.

CAUSE: Wrong settings in categories of the desktop file

STEPS TO REPRODUCE:
1/ install the Nvidia driver
2/ check the two menu options see it produced in both.

[Bryce Harrington (bryce)]

Hi davmor2,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[Dave Morley (davmor2)]

Hi Bryce.

As far as I can see everything is working as expected. The issue is with the way KDE organizes it's menu listings. Riddell asked me to write the bug report as a reminder to him. I'll double check and add the info you requested :)

[Harald Sitter (apachelogger)]

10:11 apachelogger_ davmor2, Riddell: I don't think the problem lies within KDE
  10:11 apachelogger_ system and settings are both main categories, IMHO this behavior is to be expected
  10:12 apachelogger_ about main categories "By including one of these categories in an application's desktop entry file the application will be ensured that it will show up in a section of the application menu dedicated to this category."
  10:12 apachelogger_ sounds like ksycoca does exactly what the spec say

Also see http://standards.freedesktop.org/menu-spec/menu-spec-1.0.html for reference.

[bugbot (bugbot)]

This bug report was filed against an old version of Ubuntu.
Can you confirm whether this is still an issue in natty?

If you don't mind, it would be very helpful if you could update the bug
report in launchpad to 'Fix Released' if it is no longer an issue for
you, or if it is still occurring under natty, please tag the bug 'natty'
so it's easier for us to track.

[bugbot (bugbot)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.