GNOME Bugzilla – Bug 656212
Renaming a vpn connection does not update the name
Last modified: 2021-06-09 16:11:07 UTC
(I'm reporting a bunch of bugs that I had today with nm. NetworkManager-0.8.9997-6.git20110721.fc15.x86_64) If I rename a vpn connection, the name does not get updated in the left pane of the gui, nor in the applet dropdown list. If I close and re-open the list, it might update, and if I close and re-open options it might update, but this is inconsistent.
Is this in nm-connection-editor or the KDE editor tool? I've tested with latest git and the name changes in both nm-connection-editor and nm-applet, but if we're talking about the GNOME Shell indicator that's different code so it might have the bug... which GUI stuff are we talking about here?
I'm using gnome3 and clicking on what used to be called the panel in the top right (the list of connections, at the bottom> network settings).
You mean gnome-control-panel, I think. What version do you use? There was a fix for the issue in late August: http://git.gnome.org/browse/gnome-control-center/commit/?id=e04d0bb7875cbb7bf472e59e709235e50fed8f46
Do you mean control-center-3.0.1.1-6.fc15.x86_64 ?
Dupe downstream (but with a nice screenshot): https://bugzilla.redhat.com/show_bug.cgi?id=745441
(In reply to comment #4) > Do you mean control-center-3.0.1.1-6.fc15.x86_64 ? The fix for control-center is present in build control-center-3.1.90-1.fc16 and up. F15 still uses Gnome 3.0, so I think the fix is not there. (In reply to comment #5) > Dupe downstream (but with a nice screenshot): > https://bugzilla.redhat.com/show_bug.cgi?id=745441 Yeah, nice screenshot for describing the things. The "Network" titled window is gnome-control-center (control-center package). You can see that the 'renamed' name is properly displayed both in the left and the right pane (after it was edited in editor through 'Configure...' button). That is the fix, I mentioned in comment #3. The black window is the GnomeShell network indicator written in JavaScript. It is a application separate from control center. I guess, there is no fix for it yet, regarding connection renaming. If your report is due to this, the proper component would be gnome-shell.
(In reply to comment #6) > The black window is the GnomeShell network indicator written in JavaScript. It > is a application separate from control center. I guess, there is no fix for it > yet, regarding connection renaming. If your report is due to this, the proper > component would be gnome-shell. Reassigning to gnome-shell in case the bug is also/still present there. If not, please simply close the bug.
The bug is not present in gnome-shell: all name changes happen correctly; I did not test changing the name with a script and the menu open, but heh, it's the edge of an edge case. On the other hand, the bug exists in gnome-control-center master. I'm not sure what to do now.
We do not make changes to the menu while it is open.
(In reply to comment #9) > We do not make changes to the menu while it is open. Really? I thought queueDeferredWork used later_add if the actor was already mapped (and I don't check if the menu is open or not, I just destroy everything and queue a rebuild)
(In reply to comment #8) > On the other hand, the bug exists in gnome-control-center master. Reproduced here. As there's no gnome-shell bug, I'll reassign.
(In reply to comment #10) > (In reply to comment #9) > > We do not make changes to the menu while it is open. > > Really? I thought queueDeferredWork used later_add if the actor was already > mapped (and I don't check if the menu is open or not, I just destroy everything > and queue a rebuild) I've seen several cases where I had a menu open and it closed on me automatically. Maybe it's worth a separate bug.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new bug report at https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/ Thank you for your understanding and your help.