Description of problem: The nm-connection-editor does not show up in the applications overview nor can it be found in the search bar. A launcher would be available in /usr/share/applications/nm-connection-editor.desktop but it isn't visible anywhere. Should be in the utilities folder, I guess. This worked fine in Fedora 30. Version-Release number of selected component (if applicable): Fedora 31 GNOME 3.34.0 How reproducible: Upgrade from Fedora 30 to Fedora 31. The icon will disappear in the applications overview. Steps to Reproduce: 1. See above 2. 3. Actual results: nm-connection-editor is missing from the applications overview. Expected results: ALL .desktop launchers shall be available in the applications overview. Additional info:
On RHEL8, something similar has been detected: https://bugzilla.redhat.com/show_bug.cgi?id=1715143
Identified root cause: 'NotShowIn=GNOME' is set in the last line of /usr/share/applications/nm-connection-editor.desktop That seems counter-productive
If this is visible in F30, that's a bug. We don't want this app to be user-visible because it doesn't follow our design requirements but it's still a dependency of gnome-control-center, so we can't get rid of it. Once gnome-control-center no longer depends on it and we can remove it from the default install, then we'll remove that line as well so that it shows up for anyone who wants to install it manually. See: https://gitlab.gnome.org/GNOME/network-manager-applet/issues/55
Michael: well, per the very link you gave, this has been flip-flopped: it was made visible for a couple of months, then it was made invisible again, on the grounds that the plan was that by 3.34, g-c-c would no longer depend on it, so it could be made visible but not installed by default. However, the ticket for that: https://gitlab.gnome.org/GNOME/gnome-control-center/issues/512 saw zero activity. So, now we have a 3.34 where g-c-c still requires the applet, but does not provide the advanced functionality that it provides. Following the logic of the upstream ticket, the applet should arguably now be made visible again. I'll post on the upstream ticket too.
Yeah, I see it as a Workstation/GNOME developer failure that gnome-control-center still depends on network-manager-applet. It's sad, but there's never enough developers to do everything we want to do.... That said, the Workstation WG still enforces its desktop/launcher policy, which prohibits new desktop launchers in the default install without approval. And I promise this won't get approval. :) So if the network-manager-applet developers remove this line upstream, as is their right, we would need to patch it back in until we fix gnome-control-center.
I mean, they raise a reasonable point, which is that nm-c-e does stuff that the control center applet just can't. Viewed one way it's pretty odd to hide the launcher for an app that does something the app you're trying to prioritize over it does not do, all for reasons of your own construction.
for the sake of peace, btw, the suggestion to move the .desktop file to a different package seems like a reasonable one that ought to satisfy all parties.
We would like to solve this both upstream and downstream in the best possible way. There are two issues that have been raised upstream: (1) No icon is available for nm-connection-editor launcher. This is not compliant to Gnome policy. (2) Having an "Advanced Network Configuration" app showing by default may be misleading. We have a brand new NetworkManager logo now in .svg format. So, I think we are ready to address point (1). For point (2), if we change the name to something like "NetworkManager connection editor" would it be allowed to be shown by default? Michael, what do you think? Regarding downstream (Fedora): if the above points work we could just align upstream.
Honestly I don't care on how the icon looks like. But if people making their decision dependent on that, it should be the easiest aspect to fix... From my perspective, the nm-connection-editor provides nice additional configuration capabilities, which are available at no other place in the GUI. I personally use it to configure automatic VPN connections, dependent on the used WiFi connection. I'd rather stay at the 'advanced' wording since it is kind of an addition to the gnome-control-center's capabilities. Personally I like the suggestion for providing an additional package which contains the launcher only.
(In reply to Francesco Giudici from comment #8) > For point (2), if we change the name to something like "NetworkManager > connection editor" would it be > allowed to be shown by default? Michael, what do you think? No, sorry but we don't want to expose advanced tools like this by default. That's nothing against nm-connection-editor -- it's a nice tool -- but the UI is too complex for default install, and we want all system configuration centralized in gnome-control-center with no extra tools. I like Adam's suggestion of splitting the desktop file to a subpackage. That allows anyone who wants to have it available "as an app" to install the subpackage. If you have appstream metadata, then it will appear in gnome-software and everything should just work if the user chooses to install it. It's weird for the actual app to be already secretly installed even when it's "not installed" but we already do this for Epiphany (to make sure it's installed by default, but hide its desktop launcher in favor of Firefox) so there is precedent.
Discussed during the 2019-09-30 blocker review meeting: [0] The decision to classify this bug as a "RejectedFreezeException" was made as we're generally agreed that the risk/reward for changing this during a freeze period would not be worthwhile. [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2019-09-30/f31-blocker-review.2019-09-30-16.00.txt
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
So it doesn't appear anything much actually happened here. There's a new active upstream ticket: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1157 but g-c-c still *does* use nm-c-e, and the nm-c-e .desktop file still has NotShowIn=GNOME . So bumping to Rawhide.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
It seems the plan to split the .desktop file out happened. It now doesn't have NotShowIn=GNOME, and is in a separate subpackage, nm-connection-editor-desktop . I don't think it has appstream metadata, though - at least a search for "advanced netw", part of its .desktop file name "Advanced Network Configuration", shows nothing in my GNOME Software. So it's still a bit hard to discover.
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '36'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
In current Rawhide, nm-connection-editor-desktop has /usr/share/metainfo/nm-connection-editor.appdata.xml , so I think we've probably addressed everything here now...I guess we'll leave it to go EOL unless anyone thinks there is more to do now.
Fedora Linux 36 entered end-of-life (EOL) status on 2023-05-16. Fedora Linux 36 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.