Ubuntu
network-manager-applet package

could not see network manager applet after a reboot

Bug #478438 reported by Anand Venkatanarayanan on 2009-11-08

This bug report is a duplicate of: Bug #439448: Visual corruption affecting several panel applets. Edit Remove

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	network-manager-applet (Ubuntu)	New	Undecided	Unassigned

Bug Description

Release:
anandv@anandv-laptop:~$ lsb_release -rd
Description: Ubuntu 9.10
Release: 9.10

Package Version:
anandv@anandv-laptop:~$ apt-cache policy network-manager-gnome
network-manager-gnome:
  Installed: 0.8~a~git.20091014t134532.4033e62-0ubuntu1
  Candidate: 0.8~a~git.20091014t134532.4033e62-0ubuntu1
  Version table:
*** 0.8~a~git.20091014t134532.4033e62-0ubuntu1 0
        500 http://in.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

Expectation:
After a system reboot and subsequent login , I should be able to
1) Automatically connect to the wireless network that I was connected to before the reboot.
2) Click the network manager applet in the notification area and view the list of networks, connect to vpn etc.

What happended instead:
1) I am able to automatically connect to the wireless network that I was connected to and Internet access does work well.
2) I cannot see the network manager applet's icon. Instead I see the screen settings applet's icon displayed twice on the
notification area and clicking on one of the icons allows me to change my display settings, but the other is non-responsive.
3) If I kill the nm-applet process via 'kill -9' and then restart it, then the additional display applet icon disappears, the nm-applet
icon appears and then every thing works fine.

ProblemType: Bug
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Sun Nov 8 20:45:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/nm-applet
IfupdownConfig:
auto lo
iface lo inet loopback
IpRoute:
192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.1 metric 2
169.254.0.0/16 dev wlan0 scope link metric 1000
default via 192.168.1.254 dev wlan0 proto static
Package: network-manager-gnome 0.8~a~git.20091014t134532.4033e62-0ubuntu1
ProcEnviron:
LANG=en_IN
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: network-manager-applet
Uname: Linux 2.6.31-14-generic i686
WpaSupplicantLog:

Tags:

Revision history for this message

Anand Venkatanarayanan (ubuntu-phoberos) wrote on 2009-11-08:

Screen shot of my desktop screen Edit (148.1 KiB, image/png)
Dependencies.txt Edit (4.7 KiB, text/plain; charset="utf-8")
Gconf.txt Edit (4.7 KiB, text/plain; charset="utf-8")
IpAddr.txt Edit (1.0 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (659 bytes, text/plain; charset="utf-8")
NetDevice.eth0.txt Edit (1.0 KiB, text/plain; charset="utf-8")
NetDevice.lo.txt Edit (2.9 KiB, text/plain; charset="utf-8")
NetDevice.pan0.txt Edit (2.9 KiB, text/plain; charset="utf-8")
NetDevice.vboxnet0.txt Edit (2.9 KiB, text/plain; charset="utf-8")
NetDevice.wlan0.txt Edit (1.1 KiB, text/plain; charset="utf-8")
NetDevice.wmaster0.txt Edit (1.1 KiB, text/plain; charset="utf-8")
PciNetwork.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (23.6 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (761 bytes, text/plain; charset="utf-8")
RfKill.txt Edit (182 bytes, text/plain; charset="utf-8")
WifiSyslog.gz Edit (44.1 KiB, application/x-gzip)
XsessionErrors.txt Edit (1.0 KiB, text/plain; charset="utf-8")
nm-system-settings.conf.txt Edit (313 bytes, text/plain; charset="utf-8")

Revision history for this message

Giordano Battilana (jordan83) wrote on 2009-11-09:

In my case instead there is a blank space in the position where I should find the nm-applet.
http://img141.imageshack.us/img141/2754/nmapplet.png

Revision history for this message

Giordano Battilana (jordan83) wrote on 2009-11-09:

dmesg output Edit (48.9 KiB, text/plain)

I noticed this error in dmesg, which might be related to the icon disappearing:
e1000e 0000:00:19.0: pci_enable_pcie_error_reporting failed 0xfffffffb

I attach dmesg for more details.