No valid active connection found and Unmanaged device found

[Mélodie]

Hi,

I am using Ubuntu Trusty 64bits, with an Openbox environment, a tint2 panel and nm-applet started with the session.

$ apt-cache policy network-manager
network-manager:
  Installé : 0.9.8.8-0ubuntu7
  Candidat : 0.9.8.8-0ubuntu7
 Table de version :
 *** 0.9.8.8-0ubuntu7 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
        100 /var/lib/dpkg/status
$ apt-cache policy network-manager-gnome
network-manager-gnome:
  Installé : 0.9.8.8-0ubuntu4.1
  Candidat : 0.9.8.8-0ubuntu4.1
 Table de version :
 *** 0.9.8.8-0ubuntu4.1 0
        500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     0.9.8.8-0ubuntu4 0
        500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
$

Here is my hardware configuration:
Ethernet:
00:19.0 Ethernet controller: Intel Corporation 82577LM Gigabit Network Connection (rev 06)

Wifi:
Centrino Advanced-N 6200 driver=iwlwifi driverversion=3.13.0-29-generic firmware=9.221.4.1

Here is the problem: when I start the X session with wireless and ethernet both enabled, the nm-applet does show in the panel; once I deactivate the wifi in nm-applet, it just disappears;

From there it does not reconnect to Ethernet (though the cable is plugged in). If I reboot completely, once logged into X (I use lightdm), the applet still doesn't show, however when I click on the panel where it is supposed to be, I see the menus : left-click, right-click : it is a ghost applet! Left click all entries except configure vpn are grayed, right click lets me access to all entries, and information about the connections states "Erreur lors de l'affichage des informations de connexion :

Aucune connexion valide active trouvée !" (Error while displaying informations about connection : no valid active connection found!") and in /var/log/syslog:
Jun 7 21:56:33 gazelle NetworkManager[1612]: <info> Unmanaged Device found; state CONNECTED forced. (see http://bugs.launchpad.net/bugs/191889)

(but #191889 is not the same as the one I am hitting here).

If I use dhclient eth0 as root it will (re)connect same if I reboot completely.

Thanks for fixing network-manager and it's applet!

If you need me to bring more log files, I'll be around.

Regards,
Mélodie

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[David V. (viro-free)]

I have the same bug on Wily;

My network interface is called em1, it's the only one I have besides lo
It was configured that way by the ubuntu installer. This machine was installed with 15.04 then upgraded to 15.10.
The system's locale is French, in case it's relevant.

I think the interface name is why network-manager doesn't handle it.

LANG=C apt-cache policy network-manager
network-manager:
  Installed: 1.0.4-0ubuntu5.2
  Candidate: 1.0.4-0ubuntu5.2
  Version table:
 *** 1.0.4-0ubuntu5.2 0
        500 http://fr.archive.ubuntu.com/ubuntu/ wily-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     1.0.4-0ubuntu5 0
        500 http://fr.archive.ubuntu.com/ubuntu/ wily/main amd64 Packages

LANG=C ifconfig em1
em1 Link encap:Ethernet HWaddr 74:d4:35:bb:e4:02
          inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
          inet6 addr: fe80::76d4:35ff:febb:e402/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:8379619 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7880493 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7041853239 (7.0 GB) TX bytes:6122637468 (6.1 GB)
          Interrupt:20 Memory:f7100000-f7120000

LANG=C lspci -k
00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller (rev 06)
 Subsystem: Gigabyte Technology Co., Ltd Device 5000
 Kernel driver in use: hsw_uncore
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
 Kernel driver in use: pcieport
00:14.0 USB controller: Intel Corporation 9 Series Chipset Family USB xHCI Controller
 Subsystem: Gigabyte Technology Co., Ltd Device 5007
 Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation 9 Series Chipset Family ME Interface #1
 Subsystem: Gigabyte Technology Co., Ltd Device 1c3a
 Kernel driver in use: mei_me
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V
 DeviceName: Onboard LAN
 Subsystem: Gigabyte Technology Co., Ltd Device e000
 Kernel driver in use: e1000e
00:1a.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #2
 Subsystem: Gigabyte Technology Co., Ltd Device 5006
 Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 9 Series Chipset Family HD Audio Controller
 Subsystem: Gigabyte Technology Co., Ltd Device a182
 Kernel driver in use: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 1 (rev d0)
 Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root Port 4 (rev d0)
 Kernel driver in use: pcieport
00:1d.0 USB controller: Intel Corporation 9 Series Chipset Family USB EHCI Controller #1
 Subsystem: Gigabyte Technology Co., Ltd Device 5006
 Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation 9 Series Chipset Family Z97 LPC Controller
 Subsystem: Gigabyte Technology Co., Ltd Device 5001
 Kernel driver in use: lpc_ich
00:1f.2 SATA controller: Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]
 Subsystem: Gig...

[Mélodie (meets)]

Hi,

The IP of your machine maybe should not be 192.168.0.1, as it could be conflicting with the one of your router. Can you type "sudo dhclient em1" and give back the result? And if it connects your machine fine, can you then type in "sudo route" and provide the result?

Besides that, what kind of machine is it? Tower or laptop? If a laptop, do you use a workstation with it?

I don't think the language is relevant, but as I also use French in my computers, I'll try to upgrade one to Wily and see if I also get difficulties with the connection.