RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1853358 - drop dependency on nm-connection-editor
Summary: drop dependency on nm-connection-editor
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnome-control-center
Version: 8.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 8.0
Assignee: Carlos Garnacho
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1715143
TreeView+ depends on / blocked
 
Reported: 2020-07-02 13:33 UTC by Vladimir Benes
Modified: 2021-04-14 21:35 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-14 21:35:50 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNOME Gitlab GNOME gnome-control-center issues 1157 0 None None None 2021-01-11 15:48:20 UTC

Description Vladimir Benes 2020-07-02 13:33:09 UTC 
Description of problem:
c-c doesn't need nm-connection-editor anymore so we should drop dependency

Version-Release number of selected component (if applicable):
NM-1.26
gnome-control-center-3.28.2-19.el8.x86_64
Comment 1 Thomas Haller 2020-07-02 14:15:58 UTC 
for context...


The issue is that originally gnome-control-center depends on nm-connection-editor, for certain advanced features.
In fact, that is resolved in the meantime (upstream) -- I think?

But since on a default installation both gnome-control-center and nm-connection-editor was installed, nm-connection-editor was hidden in Gnome (bug 1715143). That is to avoid confusing the users by having two GUIs for networking. On the other hand, nm-connection-editor has some advanced features, and it might make sense to use it.

Now, we are going to solve that by not installing nm-connection-editor by default (and gnome-control-center no longer depending on nm-c-e). Then, when a user installs nm-connection-editor, it's fair to assume that the user wants to use it, and we shall no longer hide it.


Related to this was also the split of libnma out of network-manager project (which originally provides libnma, nm-applet and nm-connection-editor). That is done in rhel-8.3 by the rebase to libnma-1.28.0+ and network-manager-applet-1.16.0+.



Slightly related is also Fedora 32 issue https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/881#note_732563 .
On Fedora 32 this is not yet done, due to issue#881. On Fedora 33, split that this rhbz requests, is planned to be completed.
Comment 3 Benjamin Berg 2021-01-11 15:48:23 UTC 
Unfortunately, that is not true. We are still calling it from some panels, see https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1157

My take is, that this will definitely not happen for RHEL 8.x. And even for RHEL 9, it can only happen if the upstream issue is resolved. i.e. seems like a WONTFIX/CANTFIX to me.
Note You need to log in before you can comment on or make changes to this bug.