Trying to open the network panel in Lubuntu 12.04 caused a problem
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
network-manager-applet (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Trying to open the networking manager applet induced a problem. The hardware was Dell Latitude D610 with all normal kit. Wired connections work, Wireless connections are not OK but I can configure them at a shell prompt.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: network-
ProcVersionSign
Uname: Linux 3.2.0-18-
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Tue Mar 13 15:13:04 2012
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Lubuntu 12.04 "Precise Pangolin" - Beta i386 (20120301.1)
IpRoute:
default via 10.1.10.1 dev eth0 proto static
10.1.10.0/24 dev eth0 proto kernel scope link src 10.1.10.26 metric 1
NetworkManager.
[main]
NetworkingEnab
WirelessEnable
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: nm-applet
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
RfKill:
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
Signal: 6
SourcePackage: network-
UpgradeStatus: Upgraded to precise on 2012-03-13 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
Wired connection 1 4c9dc433-
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth1 802-11-wireless disconnected /org/freedeskto
eth0 802-3-ethernet connected /org/freedeskto
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.3.0 connected enabled enabled enabled enabled disabled
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 #908380, 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.