|
Bugzilla – Full Text Bug Listing |
| Summary: | yast2-control-center-gnome has a wrong yast group | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.2 | Reporter: | Uwe Gansert <ug> |
| Component: | YaST2 | Assignee: | J. Daniel Schmidt <jdsn> |
| Status: | RESOLVED FIXED | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Normal | ||
| Priority: | P3 - Medium | CC: | forgotten_h13THG8RK1, jdsn, vuntz |
| Version: | Milestone 8 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Uwe Gansert
2009-10-08 11:55:06 UTC
If I look at the Categories in suse_register.desktop, there's no way to determine this .desktop file belongs to a Support category. The organization in the control center is built with those categories, so the yast team would have to fix this first. (reassigning to the yast team for this, please move back to GNOME once this is done) Also, if I look at /etc/xdg/menus/yast-settings.menu, I see no support submenu. How does yast qt/curses build the structure? (In reply to comment #1) > If I look at the Categories in suse_register.desktop, there's no way to > determine this .desktop file belongs to a Support category. There is. To figure out correct group, Qt4 and ncurses CC read X-SuSE-YaST-Group desktop file entry which is correctly set to 'Support' in this case. If Gnome CC relies upon Categories entry (I reckon X-SuSE-YaST-Support should be there), then indeed, this is not set > Also, if I look at /etc/xdg/menus/yast-settings.menu, I see no support submenu. > How does yast qt/curses build the structure? Qt4 and curses do not (yet) read /etc/xdg/menus (and do not conform to standards, there is a feature request to have this implemented). They create groups using special group .desktop files - /usr/share/applications/YaST2/groups - which also do not conform to freedesktop standards, oh well (In reply to comment #1) > If I look at the Categories in suse_register.desktop, there's no way to > determine this .desktop file belongs to a Support category. The organization in > the control center is built with those categories, so the yast team would have > to fix this first. As we are dealing with a group here, this is correcty set via X-SuSE-YaST-Group=Support Anyway, I will add the flag to the registration desktop, thats faster. To my surprise in my file Categories already contains the flag X-SuSE-YaST-Support in SVN, and so does it in my source tarball. But after building it, the flag got removed - all others survived. Any idea how and why that happens? Katarina? Vincent, you can already start and create the Support group, don't wait for us, as there are also two other modules pointing out to belong to the support group. These are: the support module and the release notes module. These and the registration module should appear inside the Support group. > To my surprise in my file Categories already contains the flag
> X-SuSE-YaST-Support in SVN, and so does it in my source tarball. But after
> building it, the flag got removed - all others survived.
> Any idea how and why that happens? Katarina?
Hmm, I'm not much more knowledgeable here. X-SuSE-YaST-Support flag is part of Categories entry in svn (trunk), but the .desktop file on my installed system mysteriously does not contain it anymore.
The only suspect that could be responsible for removing it during the build is imo
%suse_update_desktop_file run during package installation. Nothing else seems to modify .desktop file in any way.
Coolo, could you please add the category "YaST-Support" resp. add support for the flag "X-SuSE-YaST-Support". Thanks submitted to factory: rq23638 The category was added, so the next builds of the yast2 support modules will contain the new category flag. |