Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 252215 - net-analyzer/openvas-client-2.0.0: .desktop file doesn't point to the correct executable
Summary: net-analyzer/openvas-client-2.0.0: .desktop file doesn't point to the correct...
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High minor (vote)
Assignee: Hanno Böck
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-12-22 22:01 UTC by Cliff Barbier
Modified: 2008-12-24 11:54 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Cliff Barbier 2008-12-22 22:01:56 UTC
The OpenVAS-Client .desktop file does not point to the correct executable.  This means that the client does not show up in the Gnome menu.  I haven't tested with other menuing systems, but I imagine they would have the same problem.

Reproducible: Always

Steps to Reproduce:
1. Emerge openvas-client-2.0.0
2. killall gnome-panel (to make sure panel reloads all .desktop files)
3. See no menu item for OpenVAS-client
4. cat /usr/share/applications/OpenVASClient-openvas-client.desktop 
5. updatedb && locate OpenVASClient 
6. ll /usr/bin/OpenVAS-Client
Actual Results:  
Found that the .desktop file is trying to run and see "OpenVASClient".  Found that the true executable is named "OpenVAS-Client".

Expected Results:  
The .desktop file would point to the correct executable name, so that the OpenVAS GUI shows up in the menu.

The case of the executable name, "OpenVAS-Client", is inconsistent with the naming case of the other OpenVAS components.  The others are all lowercase.  For openvas-client to be CamelCase is inconsistent, and can lead to confusion.  It took me a while to even find the correct executable when I was looking for the problem with the .desktop issue.  I'm not filing this as another bug, because you might as well fix both at once.  

BTW -- the OpenVAS project bumped OpenVAS-Client to 2.0.1 for a seemingly unrelated bug.
Comment 1 Wormo (RETIRED) gentoo-dev 2008-12-23 22:29:37 UTC
Thanks for reporting this issue, assigning to maintainer.
Comment 2 Hanno Böck gentoo-dev 2008-12-24 11:54:33 UTC
Fixed in 2.0.1. As for the CamelCase-filename, I already requested upstream to rename it to openvas-client, though they didn't like the idea. But you are welcome to try again ;-)