kinfocenter does not show eth0 interface

Bug #31261 reported by PeterK
12
Affects Status Importance Assigned to Milestone
Ubuntu
Invalid
Medium
Unassigned
kdebase (Ubuntu)
Fix Released
Medium
Kubuntu Bugs

Bug Description

kubuntu dapper amd64
kinfocenter shows only loopback interface at 127.0.0.1. does not show existing and working eth0 interface

Kenny Duffus (kduffus)
Changed in kdebase:
assignee: nobody → kubuntu-team
Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

I have the same problem on kubuntu dapper amd64 with latest updates

On the "Network Interfaces" page only lo shows up even though eth0 is working and active and I'm using it right now.

This bug was reported on KDE bugzilla but was dismissed because the person had the interface down.
http://bugs.kde.org/show_bug.cgi?id=122257
However, there is a "State" column on the page, so interfaces that are not activated should still show up, with "down" in that column.

Revision history for this message
Frode M. Døving (frode) wrote :

I can confirm that only active devices are listed.
I have no problems with active devices not showing.

Can someone confirm that active devices are listed correctly?

Revision history for this message
Matt Zimmerman (mdz) wrote :

Rejecting generic Ubuntu task; bug remains open against kdebase

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

Active devices are now listed for me, tested on two dapper systems. I still think inactive devices should be listed as well, though the KDE people seem to disagree, see the upstream bug kde-bugs #122257.

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

I was previously using amd64 when I had this problem, but am now using i386 and don't. Also, according to kde bug #125263, this is likely an amd64 problem. Is anyone else still having this problem and are you running amd64?

Revision history for this message
Jonathan Jesse (jjesse) wrote :

Good afternoon,

I noticed the last update to this bug is from 2006-05-21 and am wondering what the current status of things are?
Could we please get an update to this bug and close it if there is no longer the problem reported here?

Revision history for this message
Yuriy Kozlov (yuriy-kozlov) wrote :

I don't have an AMD64 install to test on, but according to http://bugs.kde.org/show_bug.cgi?id=125263 this was fixed back in May.

Changed in kdebase:
status: Unconfirmed → Fix Released
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.