http://bugzilla.suse.com/show_bug.cgi?id=1084864 Noah Davis <noahadvs@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |noahadvs@gmail.com -- 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#c2 --- Comment #2 from Noah Davis <noahadvs@gmail.com> --- Created attachment 763363 --> http://bugzilla.suse.com/attachment.cgi?id=763363&action=edit Searching for "fonts" in KDE Plasma -- 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#c4 --- Comment #4 from Noah Davis <noahadvs@gmail.com> --- I have already done the necessary changes to yast-control-center in a fork on GitHub, but all .desktop files must have a GenericName, including the .desktop files for groups or else YaST Control Center will crash. I talked with kobliha and HuHa about making these changes on the YaST IRC channel and they expressed concern about them breaking things, such as translations and how they will look in other desktop environments. -- 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#c6 Steffen Winterfeldt <snwint@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jsrain@suse.com Flags| |needinfo?(jsrain@suse.com) --- Comment #6 from Steffen Winterfeldt <snwint@suse.com> --- Seems this needs some architectural guidance. Jiri, please check how to move forward. -- 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#c8 --- Comment #8 from Noah Davis <noahadvs@gmail.com> --- (In reply to Jiri Srain from comment #7)

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#c10 --- Comment #10 from Stefan Hundhammer <shundhammer@suse.com> --- 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. -- 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#c11 --- Comment #11 from Noah Davis <noahadvs@gmail.com> --- (In reply to Stefan Hundhammer from comment #10)

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#c13 --- Comment #13 from Ladislav Slezák <lslezak@suse.com> --- 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... -- 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#c15 --- Comment #15 from Noah Davis <noahadvs@gmail.com> --- (In reply to Ladislav Slezák from comment #13)

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#c17 --- Comment #17 from Stefan Hundhammer <shundhammer@suse.com> --- Post on the opensuse-factory mailing list about this: https://lists.opensuse.org/opensuse-factory/2018-05/msg00427.html (no reply, unfortunately) -- 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#c19 Kenneth Wimer <wimer@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(wimer@suse.com) | --- Comment #19 from Kenneth Wimer <wimer@suse.com> --- 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. -- 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 <shundhammer@suse.com> --- 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. -- 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 <wimer@suse.com> --- (In reply to Stefan Hundhammer from comment #21)

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#c25 Lukas Ocilka <locilka@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(pgajdos@suse.com) --- Comment #25 from Lukas Ocilka <locilka@suse.com> --- No "regexing-out" please. Chinese guys probably write YaST as YaST, but there are also other languages and some translations could use YaST at the end of the string, some at the beginning, other in the middle. And we'd get plenty of bugreports that translations contains "YaST &^&&**&((*&", but no "YaST" is shown, etc. So, we definitely MUST show what is in the desktop file. 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? -- 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 <hellcp@mailbox.org> --- I would like to point out that Fonts is not the only module with a generic name, and not every module like that will be that easy to just rename to `System Fonts`. It might also happen that one day, for example, XFCE decides to rename their settings to `System Fonts` because it's literally settings of Fonts afaik (as opposed to Gnome's fonts showcase). This is not a robust solution. Example of generic names: Date and Time, Firewall, Language, Online Update, Partitioner, Printer, Scanner, Sound, Support, all of which I can imagine as standalone apps in repos, or already in DEs settings. I also wasn't literally suggesting to regex everything as it goes, because it's not a good solution in the slightest. However, considering how flexible .desktop files are, I see no issue in making them in a way that would allow YaST Fonts and, inside YaST, Fonts to coexist in a .desktop file. -- 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 <suseforum@Fraser-Bell.ca> --- (In reply to Petr Gajdos from comment #28)

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#c31 --- Comment #31 from Gerry Makaro <suseforum@Fraser-Bell.ca> --- (In reply to Petr Gajdos from comment #30) Hi, Petr:

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 Gerry Makaro <suseforum@Fraser-Bell.ca> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |IN_PROGRESS -- 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#c35 --- Comment #35 from Noah Davis <noahadvs@gmail.com> --- (In reply to Gerry Makaro from comment #32)

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.

https://bugzilla.suse.com/show_bug.cgi?id=1084864 https://bugzilla.suse.com/show_bug.cgi?id=1084864#c42 --- Comment #42 from OBSbugzilla Bot <bwiedemann+obsbugzillabot@suse.com> --- This is an autogenerated message for OBS integration: This bug (1084864) was mentioned in https://build.opensuse.org/request/show/839549 15.2 / yast2-gpmc -- 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#c49 --- Comment #49 from Swamp Workflow Management <swamp@suse.de> --- SUSE-RU-2021:0881-1: An update that has 15 recommended fixes and contains two features can now be installed. Category: recommended (moderate) Bug References: 1084864,1132565,1133568,1135130,1135224,1138203,1138487,1145508,1146898,1150394,1150612,1151713,1152052,1154121,1170998 CVE References: JIRA References: ECO-2527,SLE-5527 Sources used: SUSE Linux Enterprise Module for Server Applications 15-SP2 (src): yast2-adcommon-python-1.6-3.3.10, yast2-aduc-2.2-3.3.11 SUSE Linux Enterprise Module for Python2 15-SP2 (src): samba-4.11.14+git.202.344b137b75d-4.16.2 SUSE Linux Enterprise Module for Basesystem 15-SP2 (src): samba-4.11.14+git.202.344b137b75d-4.16.2 SUSE Linux Enterprise High Availability 15-SP2 (src): samba-4.11.14+git.202.344b137b75d-4.16.2 NOTE: This line indicates an update has been released for the listed product(s). At times this might be only a partial fix. If you have questions please reach out to maintenance coordination. -- You are receiving this mail because: You are on the CC list for the bug.