nm-applet crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
nm-applet crashes while apt-get upgrade is running (usually while the python trigger is running after packages are installed)
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: network-
ProcVersionSign
Uname: Linux 2.6.38-5-generic x86_64
NonfreeKernelMo
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
CheckboxSubmission: 53600264fb13d2d
CheckboxSystem: e704f33cc0866ff
CrashCounter: 1
Date: Sat Mar 19 01:38:59 2011
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100620)
IpRoute:
192.168.11.0/24 dev wlan0 proto kernel scope link src 192.168.11.4 metric 2
192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1
169.254.0.0/16 dev wlan0 scope link metric 1000
default via 192.168.11.1 dev wlan0 proto static
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
ProcCmdline: /usr/bin/nm-applet
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f0931d2eda0: movsbl (%rdi),%eax
PC (0x7f0931d2eda0) ok
source "(%rdi)" (0x00000001) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: nm-applet crashed with SIGSEGV
UpgradeStatus: Upgraded to natty on 2011-01-10 (67 days ago)
UserGroups: adm admin audio cdrom dialout dip disk fax floppy fuse kvm libvirtd lpadmin netdev plugdev sambashare tape vboxusers video
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #729150, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.