abrt 1.0.9 detected a crash.
Attached file: backtrace
reason: Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
The crash happened when I clicked "Edit" on a VPN connection in the connection editor.
Possibly relevant: Yesterday, I changed the saved password for that VPN using the connection editor, and I have not used the VPN since then. Now, if I open the "VPN password secret" entry in seahorse, the password text field is empty and uneditable (weird).
Created attachment 410596 [details]
I bet I had a "null VPN secret" as described in bug 532084. After deleting the entry manually in seahorse, I was able to re-enter the password in the connection editor without a crash. That still leaves the question of how the null secret got in my keyring.
Yeah, though there was one location that wasn't checking for a NULL secret.
NetworkManager-0.8.1-1.fc13 has been submitted as an update for Fedora 13.
NetworkManager-0.8.1-1.fc12 has been submitted as an update for Fedora 12.
NetworkManager-0.8.1-1.fc13 has been pushed to the Fedora 13 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update NetworkManager'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/NetworkManager-0.8.1-1.fc13
NetworkManager-0.8.1-1.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
NetworkManager-0.8.1-4.git20100817.fc12 has been submitted as an update for Fedora 12.
NetworkManager-0.8.1-6.git20100831.fc12 has been submitted as an update for Fedora 12.
NetworkManager-0.8.1-6.git20100831.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.