bug from nowhere
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
i didnt do anything special
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: network-
ProcVersionSign
Uname: Linux 3.11.0-2-generic x86_64
NonfreeKernelMo
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
Date: Tue Aug 20 00:41:12 2013
ExecutablePath: /usr/bin/nm-applet
InstallationDate: Installed on 2013-06-27 (54 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
IpRoute:
default via 192.168.1.254 dev eth2 proto static
10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1
192.168.1.0/24 dev eth2 proto kernel scope link src 192.168.1.3 metric 9
MarkForUpload: True
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: nm-applet
ProcEnviron:
LANGUAGE=es_CL:es
PATH=(custom, no user)
XDG_RUNTIME_
LANG=es_CL.UTF-8
SHELL=/bin/bash
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: network-
UpgradeStatus: Upgraded to saucy on 2013-08-04 (15 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth1 802-3-ethernet unavailable /org/freedeskto
eth2 802-11-wireless connected /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.8.0 connected enabled enabled enabled enabled enabled
| Nicolás José Diego Narváez Barría (edge731) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| information type: | Private → Public |
| tags: | removed: need-amd64-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1189309, 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.