Bug 384410 - nm-applet fails to connect to APs whose SSID can't be decoded with system locale
Summary: nm-applet fails to connect to APs whose SSID can't be decoded with system locale
Status: RESOLVED WORKSFORME
Alias: None
Product: plasma-nm
Classification: Plasma
Component: general (show other bugs)
Version: 5.10.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Jan Grulich
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-06 06:48 UTC by Leonard Lausen
Modified: 2022-12-10 05:14 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leonard Lausen 2017-09-06 06:48:17 UTC
If an AP name cannot be decoded with the system locale (or fallback locale), nm-applet will display gibberish instead of the AP name. Clicking connect will fail to connect to the network.

Instead, if the AP name cannot be decoded, the BSSID should be displayed in nm-applet, which would make it possible to still connect to the network.

For example, in greater China region some AP names may use the gb18030 encoding, which cannot be decoded with en_US.UTF-8 locale. The user should not be required to switch his system locale to zh_CN.gb18030 locale just to connect to networks for which the AP name cannot be decoded.


Secondly, nm-applet should use LC_CTYPE to determine the encoding (and list of fallback encodings [1]) used for decoding AP names.



https://bugzilla.gnome.org/show_bug.cgi?id=784415 contains more background information.


[1]: https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/libnm-core/nm-utils.c?id=a47153f5b8a114ce1f0d226b33d0ad6d6ec7f150#n76
Comment 1 Justin Zobel 2022-11-10 08:52:23 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 2 Bug Janitor Service 2022-11-25 05:17:22 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-12-10 05:14:31 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!