© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
First time user of bugzilla today, apologizing for any resulting
rough edges.
424626 is described in the Release Notes for 3.0.1 as having been
fixed, but, it has not been fixed as far as I can observe on my system
(details below).
As best I can tell the present "fixed 1.9.0.1" status of 424626,
is/was the basis for the 3.0.1 ReleaseNotes wording.
A couple days ago I installed Ubuntu 7.0.4 i386 (Desktop) from scratch
using a CD sold by linuxcentral. Then, used synaptic etc. to obtain
and apply all updates. Hence, 'uname -a' now says "2.6.20-17-generic
#2 SMP Thu Jul 10 00:05:43 UTC 2008 i686 GNU/Linux".
Subsequently downloaded and installed Firefox 3.0.1 manually; because
the native Ubuntu mechanisms do not understand that any Firefox rev
higher than 2.* might exist and warrant downloading/
I am at home, using a dialup land line connection to my ISP, and ppp
(via 'wvdial'). There is no other computer, telephone or network
gear in my home. The linux is "out of the box" except for installing
the aforementioned up-to-current-revs patches. I don't know whether
NM is running, nor how to determine whether it is running. I am a
"simple end user" when it comes to linux.
When I startup Firefox, it is in Offline mode. I am forced to uncheck
the "Offline" box in the menu, else Firefox will not be able to access
internet sites. This behavior, I believe, is exactly the unwanted
behavior described in the Summary line for 424646. That is why I say,
it has not been fixed.
If "you" (the maintainer(s)) understand that the unwanted behavior
is still occurring, please amend the ReleaseNotes and the underlying
status code for 424646, to reflect that the bug has not been fixed.
Or let me know where/how to file an issue directly to someone who
maintains the release notes, if that is the usual mechanism for correcting them.
It appears, though, that possibly the maintainer(s) may be declining to
fix the bug under the premise that "it does not deserve fixing" -- or
however you might summarize that kind of argument -- and that leaving
users in the situation of working around the bug by either unchecking
the Offline box, or editing about:config (too dangerous for an
simple end user?) may be the most advisable approach for now.
I don't happen to agree with that view. But even if you hold that view,
I don't believe it is possible to justify calling the bug "fixed".
It has not been fixed!