Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
I have a bond and two slaves connected but GS' icon says I am not connected (two computers icon with x). This is obviously not true. Not sure about other virtual devices.
Version-Release number of selected component (if applicable):
NetworkManager-0.9.9.1-12.git20140326.4dba720.el7.x86_64
gnome-shell-3.8.4-31.el7.x86_64
How reproducible:
always
Steps to Reproduce:
1.create bond with slave
2.connect them and make sure no ethernet is connected
Actual results:
disconnected icon
Expected results:
connected icon
Additional info:
This is still unfixed in 3.14.x and NM-1.0.x.
connecting to bond with ethernet bond-slave leads to:
1. no icon at all in panel (neither connected nor disconnected)
2. unstable ethernet icon in drop down menu (will disappear after nmcli con up bond-slave). reappearing after gnome shell restart.
do we want to do anything more with it? I would expect ethernet connection to be present once bond (with slave) is connected.
when team is created (w/o any slaves), gnome-shell thinks network doesn't work (so app like evolution thinks they're offline) and shows question mark as a connection. This should be fixed too. I think we can handle it under this bug.
(In reply to Vladimir Benes from comment #5)
> when team is created (w/o any slaves), gnome-shell thinks network doesn't
> work (so app like evolution thinks they're offline)
No, how gnome-shell displays the network status (or fails to display it) has no influence on applications. If the status is confused in both gnome-shell and evolution, then either both have a bug there, or there is an issue on the NetworkManager side.
Somehow related: Since bug 1100812, the shell does display an icon in the top bar if there is a connection through a connection type that is not handled explicitly in the menu (wired/wifi/modem/bluetooth).
Comment 8RHEL Program Management
2020-12-15 07:30:25 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.