Dapper: Network settings behave strangely

Bug #50373 reported by Alex Bligh
2
Affects Status Importance Assigned to Milestone
gnome-network (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnome-network

I have an IBM T60p with a wireless LAN card and a wired ethernet card. I enabled both in the hope that it would use the wired connection in priority. However, on boot up the wireless interface does not connect as it does not remember the WEP key (this isn't the main bug). Disabling the wireless interface then disabling and reenabling the fixed interface gets the fixed interface working. However, this is lost by a reboot (this is the main bug) - it always comes up with both interfaces enabled (and thus not working). I don't know whether the fact the wireless interface and wired interface are on the same subnet has confused things.

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Thank you for your bug report. Do you still have this issue with the latest release of Ubuntu ?

Changed in gnome-network:
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

Any news on this ?

Revision history for this message
Jérôme Guelfucci (jerome-guelfucci-deactivatedaccount) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in gnome-network:
status: Incomplete → Invalid
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.