Sorry for the bogus component, just want to bring this to KDE team's attention, they'll know what to do with it. In F13 RC2, the SELinux menu entries aren't very polished. There's two, on the System menu. One is just named 'SELinux', and only when you hover over it do you see the subtitle 'SELinux Policy Generation Tool', making clear what it is. It has an icon, but it's somewhat ugly and looks like it's upscaled, at default settings. The other is named 'SELinux Troubleshooter', so you know what it is, but it has no icon. These are failures of the 'desktop menus' validation test: https://fedoraproject.org/wiki/QA:Testcase_desktop_menus . As we don't consider the desktop validation tests to be release blocking for anything but the default desktop in F13, not nominating this as a release blocker, but obviously can be fixed with updates, and for future releases we'd hope to be able to consider this kind of thing release blocking.
Well, this will need to be fixed by the SELinux guys, they're the ones shipping the .desktop files in their packages, KDE just displays what's there. If your Name says "SELinux Policy Generation Tool", then please don't set GenericName to just "SELinux". Leave it blank entirely. For setroubleshoot, please either use a standard freedesktop.org Icon Naming Spec icon (which is also available in Oxygen) or install your icon to the hicolor theme (which is inherited by all others as per the spec).
(To elaborate on the GenericName part: GenericName, if set, is supposed to be more descriptive. By default, if both Name and GenericName are set, Kickoff will display the GenericName and show the Name on mouseover. If you leave GenericName blank, it will display the Name as the primary entry, which is what you want here.)
Kevin Does this look good. [Desktop Entry] Name=SELinux Policy Generation Tool GenericName= Comment=Generate SELinux policy modules StartupNotify=true Icon=system-config-selinux.png Exec=/usr/bin/selinux-polgengui Type=Application Terminal=false Categories=System;Security; X-Desktop-File-Install-Version=0.2
Adam can you grab the latest setroubleshoot from koji it should have the icon. setroubleshoot-2.2.83-1.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/setroubleshoot-2.2.83-1.fc13
Please omit the blank "GenericName=" line entirely. I think having "GenericName=" will have the same effect, but I'm not sure. It might cause some trouble.
Fixed in policycoreutils-2.0.82-16.fc13
policycoreutils-2.0.82-17.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/policycoreutils-2.0.82-17.fc13
d'oh, I'm a bit late, but: Icon=system-config-selinux.png the spec - which I can't quite find atm, it's on freedesktop.org somewhere - specifically states you should specify *either* an icon name, *or* a full canonical location for a specific image file you want to use, not something in the middle. Practically speaking, this should be: Icon=system-config-selinux -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
policycoreutils-2.0.82-17.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update policycoreutils'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/policycoreutils-2.0.82-17.fc13
Ok that will be fixed in -18 Fixed in policycoreutils-2.0.82-18.fc13 I will push when more important fixes happen
policycoreutils-2.0.82-18.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update policycoreutils'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/policycoreutils-2.0.82-18.fc13
policycoreutils-2.0.82-18.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.