Created attachment 1445996 [details] Improperly populated gnome-shell networking menu from F28 Description of problem: After definig additional profiles, ie for USB broadband modem, or additional ETH card profile left-top gnome-shell menu shows empty name for running connection Version-Release number of selected component (if applicable): Not sure which package is responsible for that. I assume this one: gnome-shell-3.28.2-1.fc28.x86_64 How reproducible: Add more than one connetcion profile to your network card. Or add another network card. Steps to Reproduce: 1. Create additional connection in "Network settings" either for new card like broadband modem, or new profile for existing card. 2. Click top-right screen corner to display gnome-shell-menu 3. Actual results: Empty menu is displayed as shown on one of attached screenshoots Expected results: Connection status shown as it used to be on F27 Additional info: I had F27 system with multiple profiles/cards defined and it appeared immediatelly after upgrade. I blamed F27 for that and installed F28 from scratch. It reappeared after I added second card (broadband modem) and secondary profile for my ethernet card. I have attached F28 screen showing empty network menu.
I'm randomly having the same issue.
This error may be related: Jun 19 08:37:51 gemlatitude5450 gnome-shell[1747]: JS ERROR: TypeError: item is undefined _sync@resource:///org/gnome/shell/ui/status/network.js:427:17 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _parent@resource:///org/gnome/gjs/modules/_legacy.js:39:12 _sync@resource:///org/gnome/shell/ui/status/network.js:505:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _addConnection@resource:///org/gnome/shell/ui/status/network.js:306:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 checkConnection@resource:///org/gnome/shell/ui/status/network.js:277:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _deviceAdded/<@resource:///org/gnome/shell/ui/status/network.js:1761:21 _deviceAdded@resource:///org/gnome/shell/ui/status/network.js:1760:17 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _readDevices@resource:///org/gnome/shell/ui/status/network.js:1703:13 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 _clientGot@resource:///org/gnome/shell/ui/status/network.js:1663:9 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22
Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/140
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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 please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.