-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apostrophe in wireless password does not appear to be supported #1276
Comments
When you configured it with NetworkManager did you use YaST or NetworkManager directly? In these cases it would better to fill a bug with attached logs. If the ifcfg file is well written by YaST then it is probably a **wicked^ bug but we need logs to confirm that. |
When I configured with NetworkManager it was through GNOME, so no YaST involvement. I'll try to re-install and grab logs later today, sorry I didn't grab them at first wasn't expecting this to be an issue. |
I've attached the Please let me know if there is anything else I can do to help troubleshoot! |
It is a escaping problem as you comment, I already reproduced the issue and it should work if you write the password using double quotes instead of single ones without escaping the single quote... Like So I will create a bug report in order to address it.
|
Thanks for looking into this! I appreciate the advice on how to get it working. |
Now tracked at https://bugzilla.opensuse.org/show_bug.cgi?id=1194222 Thank you guys. |
On a fresh install of Raspberry PI openSUSE LEAP 15.3 (also tried Tumbleweed) I observed that using
yast
to configure the Wifi with a password containing an apostrophe (single quote) fails to connect. (e.g.Thispassworddoesn'twork.
) After inspecting/etc/sysconfig/network/ifcfg-wlan0
it appears as though the single-quote may be breaking the formatting. The same wireless network works just fine when configured with NetworkManager.I'm new to openSUSE/yast and am not sure if this is an issue with the yast tool or wicked itself. Happy to be redirected if this is the wrong place to file this report.
The text was updated successfully, but these errors were encountered: