Wired-only machine has empty volcano icon

Bug #751939 reported by Barry Warsaw
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Low
Unassigned

Bug Description

Binary package hint: network-manager

I just upgraded my maverick desktop machine to natty. This machine only has a wired connection, no wireless. I'm used to seeing the up/down arrows for the nm icon in the menu bar, but now all I see is the empty volcano (or fan, or pie slice :) icon. When I select Edit Connections, I do see just the Auto Ethernet wired connection I expect.

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

Hi Barry,

Do you have any connections configured in /etc/network/interfaces?

Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Barry Warsaw (barry) wrote : Re: [Bug 751939] Re: Wired-only machine has empty volcano icon

On Apr 13, 2011, at 02:14 PM, Mathieu Trudel-Lapierre wrote:

>Do you have any connections configured in /etc/network/interfaces?

Hi Mathieu,

Here's the contents of /etc/network/interfaces:

% cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
auto eth0
#iface eth0 inet dhcp

# Bridged networking for virtual machines
auto br0
iface br0 inet dhcp
      bridge_ports eth0
      bridge_stp off
      bridge_fd 0
      bridge_maxwait 0

This has not changed since Maverick, so I think this is a regression.

Cheers,
-Barry

tags: added: regression-release
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
Barry Warsaw (barry)
Changed in network-manager (Ubuntu):
status: Expired → New
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

I think this was because we changed the logic to be a bit more intelligent about wired devices used for stuff like bridges, but perhaps there's just a bit missing to get the icon to show right.

Marking at Triaged/Low, I'll get back to this ASAP.

There was no other impact than aesthetic, right?

Changed in network-manager (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

That actually might also be relatively palatable for new contributors, so I'll tentatively add the 'bitesize' tag. In theory, changes should be mostly located with the patch that does the state for unmanaged connections and where NM reads /e/n/i. Not terribly easy, but it should be doable for people with some knowledge of C++.

tags: added: bitesize
Revision history for this message
Thomas Hood (jdthood) wrote :

What happens if you comment out *both* "auto eth0" and "iface eth0"?

What happens if you *un*comment *both* "auto eth0" and "iface eth0" with "managed=false" in the "[ifupdown]" section of /etc/NetworkManager/NetworkManager.conf?

What happens if you uncomment both "auto eth0" and "iface eth0" with "managed=true" in the "[ifupdown]" section of /etc/NetworkManager/NetworkManager.conf?

Revision history for this message
Rolf Leggewie (r0lf) wrote :

ping Barry

Revision history for this message
Barry Warsaw (barry) wrote :

This has only been a cosmetic bug for me for a long time. However, I took the ping as an opportunity to try a few of the things in comment #6. Changing managed=false to managed=true was the only change necessary to fix the icon in Utopic. I consider this bug fixed.

Changed in network-manager (Ubuntu):
status: Triaged → Fix Released
Barry Warsaw (barry)
Changed in network-manager (Ubuntu):
status: Fix Released → New
Revision history for this message
Barry Warsaw (barry) wrote :

I take that back. Setting managed=true breaks the networking.

Even though I get the proper icon and all the network connection information appears to be correct (both as displayed by ifconfig and through the NM u/i), I cannot ping or connect to any service outside my LAN. Gateway and DNS services, IPv4 address and netmask all *look* right, but nothing gets outside the LAN. Setting it back to managed=false fixes this but of course volcano-izes the icon.

I'll take functional networking over cosmetics. :)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.