Still wish we had the actual crash dump rather than just a patch -- I
guess this makes sense though.
I'll manually debug this just to make sure, but the patch makes sense
anyway. I may even have already fixed this if the compiler complained
since, assuming that was for prior to quantal.
Could you please confirm exactly which Ubuntu release this was for?
** Changed in: network-manager-applet (Ubuntu)
Status: New => Triaged
** Changed in: network-manager-applet (Ubuntu)
Importance: Undecided => High
** Changed in: network-manager-applet (Ubuntu)
Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1046210
Title:
segfault in create_new_ap_item
Status in “network-manager-applet” package in Ubuntu:
Triaged
Bug description:
In certain circumstances, nm-applet can crash in create_new_ap_item.
This is caused by the "dupes" variable introduced in debian/patches
/nm-applet-use-indicator.patch not being initialized.
Note that I first observed this only with optimizations turned off
(-O0), so apparently if one gets lucky, -O2 will cause the variable to
be initialized to NULL.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1046210/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
