[Bug 1084864] New: YaST module names are too similar to some desktop environment configuration modules
http://bugzilla.suse.com/show_bug.cgi?id=1084864 Bug ID: 1084864 Summary: YaST module names are too similar to some desktop environment configuration modules Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Enhancement Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: noahadvs@gmail.com QA Contact: jsrain@suse.com Found By: --- Blocker: --- Created attachment 763361 --> http://bugzilla.suse.com/attachment.cgi?id=763361&action=edit How it should look when fixed YaST, GNOME, KDE Plasma and Enlightenment all have configuration modules named "Fonts" and a YaST module with the same exact name shows up when searching for "fonts" in all 3 DEs. This is not currently too much of a problem for users because the YaST Fonts module uses an icon representing X11 instead of an icon representing fonts, but there's no way to tell the difference without the icon. This will also be a problem for me because I am working on a KDE Breeze theme for YaST and intend to change the icon of the YaST Fonts module to a proper fonts icon. Fixing this problem will require changes to the code of yast-control-center and changes to the .desktop files shown for all YaST modules. 1. Every Name field needs to be prefixed with "YaST " or something similar to show association with YaST. However, this will cause every module name shown in the YaST Control Center to also have that prefix, which doesn't look good. 2. GenericName can be the field that YaST Control Center uses for module names instead. For example, the Name field could be "YaST Fonts" and the GenericName field could be "Fonts". 3. The GenericName field is currently used as if it was the Comment field, so YaST Control Center needs to display the Comment field instead of the GenericName field for module descriptions. All descriptions in the .desktop files need to be moved to the Comment field. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
Noah Davis
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c1
--- Comment #1 from Noah Davis
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c2
--- Comment #2 from Noah Davis
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c3
--- Comment #3 from Noah Davis
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c4
--- Comment #4 from Noah Davis
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c5
--- Comment #5 from Noah Davis
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c6
Steffen Winterfeldt
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c7
Jiri Srain
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c8
--- Comment #8 from Noah Davis
Frankly speaking, I don't know what the best approach is. I would postpone any changes in this for after SLE15 (we share the code stream with openSUSE), as the side effects may be unpredictable.
But clearly, I don't have any good solution :-(
The problem must have been present for ages, therefore I also wonder how much of a real severity it is.
Yes, kobliha and HuHa also mentioned that I would likely have to wait until after Leap 15 to contribute this. So, SLE and Leap 15 can't use a separate branch from master? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c9
--- Comment #9 from Stefan Hundhammer
Yes, kobliha and HuHa also mentioned that I would likely have to wait until after Leap 15 to contribute this. So, SLE and Leap 15 can't use a separate branch from master?
Right now, clearly no. If anything goes to a branch, it must be experimental features such as this. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c10
--- Comment #10 from Stefan Hundhammer
http://bugzilla.suse.com/show_bug.cgi?id=1084864
Stefan Hundhammer
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c11
--- Comment #11 from Noah Davis
Also, this will probably need extensive discussion between our UX experts and also including the community, preferably with opinions from at least the major desktops (GNOME, KDE / Plasma), and certainly not ignoring the minor ones (Xfce, LXDE, Enlightenment and whatnot).
Until that point in time, this issue is blocked.
-> Moving to our Trello task queue so this isn't forgotten.
I tried to go to the Trello link, but it says
Card not found. This card may be on a private board. If someone gave you this link, they may need to invite you to one of their boards or teams.
It seems a bit odd for an open source project to keep their task board private. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c12
--- Comment #12 from Noah Davis
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c13
--- Comment #13 from Ladislav Slezák
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c14
Ladislav Slezák
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c15
--- Comment #15 from Noah Davis
Um, this is not an YaST specific issue, there is also collision between "Fonts" from KDE and Gnome. I do not know how to solve this on the distribution level...
The KDE Fonts vs GNOME Fonts issue is not YaST specific, but this is not a bug report about *that* issue. The $DE Fonts vs YaST Fonts issue is a YaST issue. Most users do not have multiple DEs installed at the same time anyway, but I would expect most openSUSE users to have YaST and a DE installed. (In reply to Ladislav Slezák from comment #14)
Maybe in this case we could change the "Fonts" label in YaST to something like "Default Font" or "Default System Font" to make it a bit different.
Petr?
That could work, but the Fonts module is only an example. There is still the issue that any YaST Module could have a name that is too similar to a DE config module name and users have no idea that it's a YaST module until they open or edit the desktop file. My proposed fix would prevent that issue completely and fix an issue with the desktop files where they don't use the correct field for the description. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c16
Petr Gajdos
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c17
--- Comment #17 from Stefan Hundhammer
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c18
Stefan Hundhammer
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c19
Kenneth Wimer
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c20
--- Comment #20 from Noah Davis
I agree that we will probably never solve this problem. If each app/package had a unique-ish name or rather one descriptive enough it would go a long way to fixing things. A simple desktop file change would help change:
Fonts Fonts Fonts
to
Fonts(Gnome) Fonts(YaST) Fonts(YourDesktopNameHere)
The only other thing I can imagine is to add a pop-over with a description of the package or such but that would be a lot of work to maintain and assume that we have accurate concise descriptions of all packages.
Are you saying module names should be suffixed with "(YaST)" instead of prefixing them with "YaST" or that it would be better to just rename the Fonts module in particular to "Fonts(YaST)"? I'm not sure what you mean by "add a pop-over with a description of the package". Are you saying YaST Control Center should have the pop-over? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c21
--- Comment #21 from Stefan Hundhammer
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c22
--- Comment #22 from Kenneth Wimer
(In reply to Kenneth Wimer from comment #19)
I agree that we will probably never solve this problem. If each app/package had a unique-ish name or rather one descriptive enough it would go a long way to fixing things. A simple desktop file change would help change:
Fonts Fonts Fonts
to
Fonts(Gnome) Fonts(YaST) Fonts(YourDesktopNameHere)
The only other thing I can imagine is to add a pop-over with a description of the package or such but that would be a lot of work to maintain and assume that we have accurate concise descriptions of all packages.
Are you saying module names should be suffixed with "(YaST)" instead of prefixing them with "YaST" or that it would be better to just rename the Fonts module in particular to "Fonts(YaST)"? I'm not sure what you mean by "add a pop-over with a description of the package". Are you saying YaST Control Center should have the pop-over?
My point was just to either use the .desktop file names better by providing more detailed, accurate information as to the name of each package AND/OR to find a mechanism to drill down to more information about a given package, in this case I suggested a pop-over but it does not have to be limited to that. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c23
--- Comment #23 from Kenneth Wimer
Maybe we should start with making better use of the fields that are already there in the .desktop files:
Name=Google Chrome GenericName=Web Browser Comment=Access the Internet
(and translations for most of them)
Of course, that would require support for all (or at least more than one) of those fields in all relevant control centers or desktop environment menus; this might be the crucial problem.
Unfortunately, many desktop environments only bother with one of them; sometimes it's even the GenericName which IMHO is pretty useless; with the given example, you'll get "Web Browser" for each of Firefox, Chrome, Opera and whatever else you might have installed.
We can start to fix things on our local level, i.e. for YaST modules. But I am not so sure how much we can push for this for any of the desktop environments; they might have their own views what to display.
I agree completely. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c24
Stasiek Michalski
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c25
Lukas Ocilka
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c26
--- Comment #26 from Kenneth Wimer
Ken, it would probably be quite hard to patch in pop-overs to every DE, however, making "YaST Module" naming scheme in desktop file, and then regexing out "YaST" in YaST Control Center so we don't have too much YaST in CC wouldn't. We have to think about our capacity to bring that stuff into reality.
As Lukas mentions below, I would use "System Fonts" or something similar for the YaST font module. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c27
--- Comment #27 from Stasiek Michalski
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c28
Petr Gajdos
Which IS the solution: Changing the text in desktop file. e.g., "System Fonts", or something like that. Petr, now it seems to be the good time for change for SLE 15 SP1 / Leap 15.1, what do you think?
yast2-fonts is not in 15sp1. 15.1: Fraser, could you please take care? If you want to help, feel free to contact me via email or irc. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c29
--- Comment #29 from Gerry Makaro
yast2-fonts is not in 15sp1. 15.1: Fraser, could you please take care? If you want to help, feel free to contact me via email or irc.
Yes, I have been following this closely with interest, Petr. Will send you message and we can go from there. Right now, though, I am at a location difficult to work from, suse.com does not work right from here. Every move I make stops "Waiting for www.suse.com ..." for two-plus minutes before continuing. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c30
--- Comment #30 from Petr Gajdos
Yes, I have been following this closely with interest, Petr. Will send you
Perfect.
message and we can go from there. Right now, though, I am at a location difficult to work from, suse.com does not work right from here. Every move I make stops "Waiting for www.suse.com ..." for two-plus minutes before continuing.
I hope suse.com is just an example. Anyway, I think there's no hurry, this is a minor issue. After you solve your internet connection problem, feel free to contact me or YaST guys whenever needed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c31
--- Comment #31 from Gerry Makaro
I hope suse.com is just an example.
Unfortunately, no. All other servers, such as microfocus, opensuse.org, and so on are responding decently. On the Forums, I can sit with a blank page "Waiting for www.suse.com ..." for a few minutes. Here, on bugzilla, I was waiting for "bugzilla.suse.com" for almost two minutes before I could write this reply.
Anyway, I think there's no hurry, this is a minor issue. After you solve your internet connection problem, feel free to contact me or YaST guys whenever needed.
Okay, will do, I still have way too much to learn and way too little learned. :-( -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c32
--- Comment #32 from Gerry Makaro
http://bugzilla.suse.com/show_bug.cgi?id=1084864
Gerry Makaro
http://bugzilla.suse.com/show_bug.cgi?id=1084864
Gerry Makaro
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c35
--- Comment #35 from Noah Davis
I am attempting to make the change today, will see if it works.
Changing to:
Name=System-Wide Fonts GenericName=Configuring System-Wide Fonts
Let's see how this works out, since I really have no clue what I am doing. LOL
Sorry I haven't replied to this bug in a while, although I wasn't really sure what to say anyway. I appreciate you giving some attention to this, but since these YaST modules show up in searches, shouldn't we have some indication that the module is from YaST in the name? Also, isn't it incorrect to use the GenericName field like a Comment field (https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06.htm... This is what my patched version of YaST Control Center was for in comment #5. I'm willing to do work, but after this discussion, I'm not sure exactly how much work there is to be done. I can fix the .desktop files of modules (It's tedious, but I've done it once before I lost the work) and I've already got a working patch, but I can't translate anything and I don't know everything I need to test. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=1084864
http://bugzilla.suse.com/show_bug.cgi?id=1084864#c36
Gerry Makaro
Sorry I haven't replied to this bug in a while, although I wasn't really sure what to say anyway.
No problems at all, Noah.
I appreciate you giving some attention to this,
My pleasure. Sorry it took so long.
but since these YaST modules show up in searches, shouldn't we have some indication that the module is from YaST in the name?
I will let full-fledged Yast Team members answer that question. I do not want a title that stretches across two monitors, though, LOL.
Also, isn't it incorrect to use the GenericName field like a Comment field (https://specifications.freedesktop.org/desktop-entry-spec/latest/ar01s06. html)? This is what my patched version of YaST Control Center was for in comment #5.
Not too sure about that, Noah. I just went by the other examples in Yast. I am in early stages of learning how to maintain and continue developing this Fonts module.
I'm willing to do work,
... above all, please do not feel I was needling you, Noah. I was not, so I would like you not to feel uncomfortable.
From the first time you reported this issue, I have been eager to find the time to learn what to do and then actually fix this issue for you and any others interested.
But, I have a heck of a lot to learn, yet, as well as so many other things to do.
but after this discussion, I'm not sure exactly how much work there is to be done. I can fix the .desktop files of modules (It's tedious, but I've done it once before I lost the work) and I've already got a working patch, but I can't translate anything and I don't know everything I need to test.
If you are inclined, and if you feel you have the time, there are many ways you can help contribute to openSUSE. This would be a good starting point: https://en.opensuse.org/Portal:How_to_participate Any and all help is always appreciated. Thanks, Gerry -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1084864
https://bugzilla.suse.com/show_bug.cgi?id=1084864#c42
--- Comment #42 from OBSbugzilla Bot
https://bugzilla.suse.com/show_bug.cgi?id=1084864
https://bugzilla.suse.com/show_bug.cgi?id=1084864#c44
--- Comment #44 from Swamp Workflow Management
https://bugzilla.suse.com/show_bug.cgi?id=1084864
https://bugzilla.suse.com/show_bug.cgi?id=1084864#c49
--- Comment #49 from Swamp Workflow Management
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com