Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#34001 - [gnome-control-center] segfault when a WiFi network with a umlaut is in range
Attached to Project:
Arch Linux
Opened by asack (asack) - Sunday, 24 February 2013, 17:34 GMT
Last edited by Jan de Groot (JGC) - Thursday, 23 May 2013, 08:07 GMT
Opened by asack (asack) - Sunday, 24 February 2013, 17:34 GMT
Last edited by Jan de Groot (JGC) - Thursday, 23 May 2013, 08:07 GMT
|
DetailsDescription:
It is not possible to open the Networksettings in the gnome-control-center when there is a Wifi with a umlaut in the SSID in range. In my case a "ΓΌ" is in the SSID. Then this happens: gnome-control-c[795]: segfault at 7f5166813000 ip 00007f5181e63a9a sp 00007fffbc14df60 error 4 in libglib-2.0.so.0.3400.3[7f5181e1b000+eb000] Additional info: * package version(s) glib2 2.34.3-1 gnome-control-center 3.6.3-4 NetworkManager 0.9.6.4-2 * config and/or log files etc. Steps to reproduce: Try to open the networksettings when a Wifi with a umlaut in the SSID is in range. It works when this network is out of range! |
This task depends upon
Closed by Jan de Groot (JGC)
Thursday, 23 May 2013, 08:07 GMT
Reason for closing: Fixed
Additional comments about closing: gnome-control-center 3.8.x doesn't call g_markup_escape_text anymore.
Thursday, 23 May 2013, 08:07 GMT
Reason for closing: Fixed
Additional comments about closing: gnome-control-center 3.8.x doesn't call g_markup_escape_text anymore.
Comment by asack (asack) -
Sunday, 24 February 2013, 17:39 GMT
added Backtrace
Comment by Cheng Ye (honestleaf) -
Tuesday, 02 April 2013, 00:56 GMT
This problem seems to be no longer existed in the lastest version of gnome.
trace.log