Description of problem: GNOME Control Center crashes when trying to use VPN settings menu. Version-Release number of selected component (if applicable): control-center-1:3.26.0-1.fc27 How reproducible: Steps to Reproduce: 1. Install Private Internet Access VPN by using the pia-nm.sh file provided at: https://helpdesk.privateinternetaccess.com/hc/en-us/articles/219660347-OpenVPN-setup-in-Fedora 2. Log into one of their servers through the NetworkManager applet in GNOME. 3. Go to VPN Settings and select the gear icon next to the server you use. Select (this might not be exact since I can't get into the menu without it crashing right now) "Connect Automatically" then exit. 4. Restart the computer. 5. At this point, note that the VPN does not connect automatically, but you can still connect manually. If you go to VPN Settings and click the gear icon, GNOME Control Center crashes. Actual results: GNOME Control Center crashes. Expected results: The settings menu for my VPN connection pops up. Additional info: ABRT says that the problem has been reported to the ABRT server: https://retrace.fedoraproject.org/faf/reports/1704061/ Running the Control Center from the terminal gives this as soon as you click the gear icon: (gnome-control-center:4540): GLib-GObject-CRITICAL **: g_type_instance_get_private: assertion 'instance != NULL && instance->g_class != NULL' failed (gnome-control-center:4540): GLib-GObject-CRITICAL **: g_object_ref: assertion 'G_IS_OBJECT (object)' failed Segmentation fault (core dumped)
*** Bug 1495363 has been marked as a duplicate of this bug. ***
Looks like the crash fixed in https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b18896f77048399e7a8b6ddd4fa0961e603836fa
(In reply to Rui Matos from comment #2) > Looks like the crash fixed in > https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/ > ?id=b18896f77048399e7a8b6ddd4fa0961e603836fa also backported to nm-1-8 as https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=b363a6cfad5996b5436b6f7c1d9337068fcb4c99
Should be fixed by NetworkManager-1.8.4-3 Currently only builds exists for Fedora 27 and later: https://koji.fedoraproject.org/koji/search?match=glob&type=package&terms=NetworkManager (Fedora update not yet done, because 1.8.4-2 is still testing, and I'd rather get that one stable first).
I just installed the RPMs from Koji and rebooted and the problem is fixed, so it must have been a duplicate.
Just so I don't report something else as a bug on the wrong component, I noticed that GNOME doesn't automatically connect to a VPN server that I select "Connect Automatically" to. I have to manually connect on each boot. Any idea what that is?
Thomas, updating to the version NetworkManager-1.8.4-3 (comment #4) the crash is gone.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.