Created attachment 1910462 [details] journal Description of problem: As shown in the attached screencast,try to disable a vpn channel by left clicking the button,but failed. Version-Release number of selected component (if applicable): openvpn-2.5.7-3.fc37.x86_64 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 1910463 [details] screencast
Created attachment 1910464 [details] screencast
Proposed as a Blocker for 37-final by Fedora user lnie using the blocker tracking app because: This affects: For all release-blocking desktop / arch combinations, the following applications must start successfully and withstand a basic functionality test
From what I can grasp from the screencasts, this is related to the GUI front-end of OpenVPN - which is handled by the NetworkManager OpenVPN plug-in (NetworkManager-openvpn)
Sep 08 06:32:44 ovpn-12-35.pek2.redhat.com gnome-shell[2075]: JS WARNING: [resource:///org/gnome/gjs/modules/core/overrides/Gio.js 287]: Too many arguments to method Gio.AsyncInitable.init_async: expected 3, got 4 Is that related to the failure, or is that unrelated? Problem is I don't see any attempt to disable the VPN in the logs at all, so I kinda suspect a gnome-shell bug maybe? Not clear what component is to blame here.
I can reproduce this here. But if I go to Control Center's Network pane, I can turn the connection off fine. So it seems this is only broken from the Shell top-right menu, there's something specific to that path.
Sending back to gnome-shell at least for now.
Looks like this was filed upstream as https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5779 and fixed with https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/2426 . I just checked, and it does work for me with gnome-shell-43~rc-2.fc37.x86_64 , so I think https://bodhi.fedoraproject.org/updates/FEDORA-2022-50e585b456 (the 43-rc mega-update) probably fixed this. Lili, can you update GNOME to 43-rc and try again? Thanks!
Checked with 43-rc,didn't see this bug any more.
Discussed during the 2022-09-12 blocker review meeting: [0] The decision to classify this bug as an "AcceptedBlocker (Final)" was made as it violates the following criterion: "All elements of the default panel (or equivalent) configuration in all release-blocking desktops must function correctly in typical use" [0] https://meetbot.fedoraproject.org/fedora-blocker-review/2022-09-12/f37-blocker-review.2022-09-12-16.01.txt
The update that fixed this is stable, so closing.