I installed gutsy on my laptop and the bug seems to be solved. I'll
open a new bug if it ever reappears.
--
both wireless and wired connections are up after boot
https://bugs.launchpad.net/bugs/94760
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug con
On Wed, Oct 03, 2007 at 02:53:03PM -, Charles Perreault wrote:
> I cannot test the new network-manager with a Live CD : it doesn't boot
> on my laptop. I used Ubuntu Gutsy Tribe 5 Live CD. GDM comes up, I can
> see the background with the mouse cursor then all freeze. No tty, no
> ctrl+al
I cannot test the new network-manager with a Live CD : it doesn't boot
on my laptop. I used Ubuntu Gutsy Tribe 5 Live CD. GDM comes up, I can
see the background with the mouse cursor then all freeze. No tty, no
ctrl+alt+backspace to reset X, even the power button (acpi shutdown)
don't work.
Even if the interfaces are in roaming mode in gnome-network-manager ?
Alexander Sack wrote:
> this should be fixed since network-manager 0.6.5-0ubuntu12 which stopped
> to manage interfaces managed by ifupdown.
>
>
> ** Changed in: network-manager (Ubuntu)
>Status: Incomplete => Fix Releas
this should be fixed since network-manager 0.6.5-0ubuntu12 which stopped
to manage interfaces managed by ifupdown.
** Changed in: network-manager (Ubuntu)
Status: Incomplete => Fix Released
--
both wireless and wired connections are up after boot
https://bugs.launchpad.net/bugs/94760
You
I'll try it whenever I get a chance, the environment where I found the
bug uses Wireless Distribution on multiple access points and I must go
back there to see if the bug is solved or not. Will take a few days.
Henrik Nilsen Omma wrote:
> Hi, could you please test this in Gutsy (perhaps with a
Hi, could you please test this in Gutsy (perhaps with a Live CD)? We'll
only be able to address most network-manager bugs in the latest release.
FWIW, I don't see this problem on my gutsy system.
Thanks.
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Medium
Status: New
I also disagree because having both interfaces enabled is the opposite
of the network manager primary goal, which was to manage wired /
wireless connections for mobile desktop users (laptop) and assure
everything would work plug'n'play. It's the opposite of
"configurations", "metric" and whats
I disagree. If you have both interfaces enabled, both should be active
after a reboot. It is not up to the OS to decide which connection you
want to use. You can however set the metric of your interfaces to decide
which one should be your first choice.
This bug should be close AFAIK.
--
both wir
