Summary: | NetworkManager Setting Editor crashed on saving WLAN connection | ||
---|---|---|---|
Product: | Network Management | Reporter: | Anton Samsonov <avsco> |
Component: | general | Assignee: | Lamarque V. Souza <lamarque> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Anton Samsonov
2012-09-27 19:35:56 UTC
Which libdbus, Qt and Plasma NM versions do you have installed? For the Plasma NM version string please send what you see in "Manage Connections" -> "Other", the package version used by OpenSuse is bogus. (In reply to comment #1) > Which libdbus, Qt and Plasma NM versions do you have installed? NM -> "Manage Connections" -> "Other": 0.9.0.2 (nm09 20120507) YaST2 -> "Software Management": libdbus-1-3(x86-64) = 1.5.12-4.1.2 libqt4(x86-64) = 4.8.1-2.1.4 / qt = 4.4.0 NetworkManager(x86-64) = 0.9.4.0-5.8.1 Today I finally figured out how to create the connection with stored password, which even authenticates successfully without password re-prompting. The trick was to fill-in the "Identity" field: I entered certificate's Common Name there (myhost.mydom.tld). This is exactly how I was able to connect early, now I recall it. As for the "Subject match" field, it still behaves strangely: once filled, it can not be emptied, unless the connection is deleted and then created again without filling-in this field. Earlier, I put AP's Common Name here, which resulted in authentication errors, because full "CN=.../DC=.../DC=..." notation was required here. Still wonder, though, why NM asked for private key's password again and again, if the problem was not with password mis/matching. Still confirm that password re-prompting window lacks the text input field, if connection is not system-wide: the window pops up with only a button and a checkbox, so an empty password is considered input by user on proceeding. Also noticed that /var/log/NetworkManager got several lines of > has_system_secrets: assertion `setting_name != NULL' failed when I was adding / editing the connection now. the missing password field is a known bug: http://bugs.kde.org/show_bug.cgi?id=299868. I just cannot reproduce it here because I do not have access to any wpa2 enterprise connection. *** This bug has been marked as a duplicate of bug 299863 *** Git commit 8815f26e37afc28c1e92cd0adf0973899fc8d64c by Lamarque V. Souza. Committed on 01/10/2012 at 02:13. Pushed by lvsouza into branch 'master'. Allow empty string in 'Subject Match' and 'Alternative Subject Matches' fields in wifi WPA2 enterprise dialog. M +1 -1 libs/ui/security/peapwidget.cpp M +1 -1 libs/ui/security/tlswidget.cpp M +1 -1 libs/ui/security/ttlswidget.cpp http://commits.kde.org/networkmanagement/8815f26e37afc28c1e92cd0adf0973899fc8d64c Git commit 0329218c4259397399f94f9dbec5cafee933dd15 by Lamarque V. Souza. Committed on 01/10/2012 at 02:13. Pushed by lvsouza into branch 'nm09'. Allow empty string in 'Subject Match' and 'Alternative Subject Matches' fields in wifi WPA2 enterprise dialog. (cherry picked from commit 8815f26e37afc28c1e92cd0adf0973899fc8d64c) M +1 -1 libs/ui/security/peapwidget.cpp M +1 -1 libs/ui/security/tlswidget.cpp M +1 -1 libs/ui/security/ttlswidget.cpp http://commits.kde.org/networkmanagement/0329218c4259397399f94f9dbec5cafee933dd15 (In reply to comment #3) > The missing password field is a known bug 299868. I just cannot reproduce it here because I do not have access to any WPA2 enterprise connection. (In reply to comment #4) > Git commit 8815f26e37afc28c1e92cd0adf0973899fc8d64c: Allow empty string in 'Subject Match' and 'Alternative Subject Matches' fields in wifi WPA2 enterprise dialog. This is all good, but how about the "Identity" field? According to my observations, this one is the real offender: if it's filled-in, then connection is saved successfully, but if it's left blank, the crash occurs for sure. Actually, this is the first time I ever needed to provide the "Identity" manually: although all systems allow for custom value, it defaults to certificate's "Common Name" if not specified. |