Clicking the gnome-netstatus-applet causes: SIOCGIFFLAGS error: no such device

[Arthur Peters]

Using a completely fresh install of Breezy (daily Sept. 2). Once I log in to
gnome I click the netstatus applet in the notification area and I get a error
dialog with the message "Please contact you system administrator to resolve the
following problem:\n\nSIOCIFFLAGS error: No such device" (I will attach a screen
shot of the dialog as well).

Right clicking and selecting Properties brings up a connection propreties window
(see screenshot) and there is no interface selected. This is probably the direct
cause of the error message. I drop down the menu and notice that there are only
2 options the blank line and "lo". So I select lo and it now works to click the
icon. I can type in eth0 by hand to make the icon display the status of my
ethernet, but that should at least be an option in the drop-down box and
probably should be the default.

I saw this problem a few weeks ago, too, in an earlier daily CD image. So this
is not new.

The system is a Compaq R3000z AMD64 system with a RTL-8139 ethernet chip and a
broadcom wireless card (not detected by the install).

BTW, I initially though that the netstatus applet would provide network control
(DHCP'ing, and hopefully wireless scaning, etc.) and it doesn't seem to. Maybe
it should have an item in the right-click menu to get this functionality. Just
to prevent people from having to search.

Below is a bunch of system info to help debugging. If you need any more info or
you want me to test something please ask.

ifconfig -a:
eth0 Link encap:Ethernet HWaddr 00:0F:B0:44:9D:A3
          inet addr:192.168.101.136 Bcast:192.168.101.255 Mask:255.255.255.0
          inet6 addr: fe80::20f:b0ff:fe44:9da3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:3634 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2354 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5089945 (4.8 MiB) TX bytes:206633 (201.7 KiB)
          Interrupt:19 Base address:0x8800

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:9481 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9481 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:851252 (831.3 KiB) TX bytes:851252 (831.3 KiB)

sit0 Link encap:IPv6-in-IPv4
          NOARP MTU:1480 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[Arthur Peters (amp)]

Created an attachment (id=3522)
Error dialog

[Arthur Peters (amp)]

Created an attachment (id=3523)
the preferences dialog showing the empty interface selection

[James Boyden (jboy)]

Hi,

Some more information on this bug:

I'm seeing the bug on my new laptop: laptop = Asus A6B00K (aka "A6K"); Ubuntu
installation = vanilla 5.10 AMD64.

When I log in, I see the "Network connection: Error" icon in the panel. Note
that I can successfully ping and ssh-to remote hosts by IP address
(xxx.xxx.xxx.xxx), so networking isn't completely hosed. What seems to be hosed
is networking by domain name.

Clicking on the "Network connection: Error" icon in the panel brings up an error
dialog. Right-clicking on the icon, and selecting "Properties", brings up the
"Connection Properties:" dialog, which (as already mentioned by Arthur) has a
blank connection name selected and a connection status of error.

Rather than dropping down the menu to select "lo", if I click on the "Configure"
button, I am prompted to enter my password to run network-admin. Upon entering
my password, I am presented with a "Network settings" dialog. I want to create
a new location, so in the "Location" drop-down menu, I select "Create location".
 I enter a location name ("home", say), and the "Location" menu is now set to
that value. If I then select the "DNS" tab, I am presented with the "DNS
Servers" and "Search Domains" text boxes in their default configurations. All
very well and good: The obvious thing to do now is to delete the default DNS
server value and add my own values for the DNS server and search domain (as
supplied by my ISP), then click OK.

Unfortunately, the "Network connection:" icon remains in the error state after
all this, and when I right-click on the icon and select "Properties", I am again
presented with a "Connection Properties:" dialog with a blank connection and an
error status. Clicking on the "Configure" button again, I am presented with the
"Network settings" dialog, and if I click on "Configure", I observe that the
"Location" drop-down menu is now blank again!

OK, I manually select "home" and the dialog box thinks for a little bit, then I
select the "DNS" tab again, and the text boxes are now in their default settings
once again! Oh noes!

Of course, I *could* just sudo and edit /etc/resolve.conf by hand, but that
rather defeats the purpose of a beginner-friendly distro...

JB

[James Boyden (jboy)]

Created an attachment (id=4967)
"Network connection: Error" icon in the panel

[James Boyden (jboy)]

Created an attachment (id=4968)
"Connection Properties:" dialog

[James Boyden (jboy)]

Created an attachment (id=4969)
"Network settings" dialog

[James Boyden (jboy)]

Created an attachment (id=4970)
the "DNS Servers" and "Search Domains" text boxes in their default
configurations

[James Boyden (jboy)]

Created an attachment (id=4971)
values for the DNS server and search domain (as supplied by my ISP)

[Daniel Holbach (dholbach)]

Thanks for your bug report and all the information. This seems to be very much
like http://bugzilla.ubuntu.com/show_bug.cgi?id=15007, which could be addressed
with http://bugs.gnome.org/show_bug.cgi?id=307422