nm-applet crashed with SIGSEGV
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
crashed suddenly and regurlarly without any reason.
Thanks for your help.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: network-
ProcVersionSign
Uname: Linux 2.6.38-6-generic i686
Architecture: i386
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
CrashCounter: 1
Date: Sun Mar 13 15:47:11 2011
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
IpRoute:
Keyfiles: Error: [Errno 2] Aucun fichier ou dossier de ce type
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
ProcCmdline: nm-applet --sm-disable
ProcEnviron:
LANGUAGE=fr_FR:en
LANG=fr_FR.UTF-8
SHELL=/bin/bash
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SegvAnalysis:
Segfault happened at: 0x488ba6: movsbl (%eax),%eax
PC (0x00488ba6) ok
source "(%eax)" (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: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
| Le Gluon Du Net (legluondunet) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
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.