Comment 43 for bug 191889

On Mon, Mar 24, 2008 at 9:31 PM, Alexander Sack <email address hidden> wrote:
> can you please NOT change bug states unless you know the technical
> details? For now this is

Dude, even if there is buggy code in NetworkManager which causes the
technical issue, it still means this is a functional defect in Firefox
for *relying* on NetworkManager! What don't you get? I think that
many people have voted here to log this as a Firefox issue and not a
NetworkManager issue. I can prove that this is a Firefox bug.

khermans@khermans-laptop:~$ ping 4.2.2.2 -c 1
PING 4.2.2.2 (4.2.2.2) 56(84) bytes of data.
64 bytes from 4.2.2.2: icmp_seq=1 ttl=243 time=285 ms

--- 4.2.2.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 285.857/285.857/285.857/0.000 ms

Yet, when I launch Firefox, it starts in offline mode. Also, there is
a point at which NetworkManager can become stuck with the two green
balls lit up and the circling blue comet spinning around, but NM never
actually becomes into the "Connection Established" state. I will
attach a screenshot of exactly this scenario. This is a functional
defect in FIREFOX for relying on NetworkManager unless you can
convince us otherwise or link us to the appropriate mailing list
discussion or documentation which describes this as a "Known
Condition" or "Accepted Defect". Dude, this is just plain moronic
though if you ask me. Read my lips. You are going to piss a lot of
Ubuntu desktop users off with this issue. I'm seriously about to
switch back to Debian with no GUI and lynx. Watch the Firefox heads
roll when 8.04 LTS final hits the internets...
--
Kristian Erik Hermansen
--
"Clever ones don't want the future told. They make it."