- Package:
- iceweasel
- Source:
- firefox-esr
- Submitter:
- Marc Haber
- Date:
- 2015-12-17 16:54:35 UTC
- Severity:
- minor
- Tags:
Hi, I have just pointed firefox to obtain its proxy configuration from file://etc/proxy.pac (note that there is one slash missing). I didn't receive any error message, but the proxy settings were silently ignored. I think that at least the "Reload" button should make firefox emit an error message if the proxy configuration file is not found. Greetings Marc
severity 259711 minor thanks I agree. I suggest filing a bug upstream as well. * Marc Haber (mh+debian-bugs@zugschlus.de) wrote:-----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ G e h! r- y+ ------END GEEK CODE BLOCK------
I tend to disagree. Ignoring proxy settings is quite a bad bug as it might lead to people trying to debug a proxy that is functioning properly. With all due respect, I believe that interaction with upstream is the duty of the Debian maintainer. Greetings Marc
[This is a message issued by a semi-automatic script] Hello, If you receive this message, it means you have filed a bug report on the Debian BTS about phoenix/firebird/firefox. You can read the history of the given bug report at the following URL: http://bugs.debian.org/259711 Now the bug list for firefox is quite inhuman to track, we (maintainers) need to clean up these and for that we would need your help. What you are asked for is to check whether, for the bug you're contacted for, - it still happens with the mozilla-firefox 1.0 package you can find in the testing or the unstable distribution - we are awaiting for your feedback/answer to a question/test to know what we can further do If you don't see the bug anymore with newer versions of firefox, please send a message to 259711-done@bugs.debian.org saying it is gone. That will close the bug. If you still can see the bug, please send a message to 259711@bugs.debian.org to confirm it still happens. If you have some more information to give, it will be much appreciated. If the last message(s) in the bug were asking for more information, please answer our questions. Thank you in advance for helping us to sort out all these bugs. Mike and Eric
[This is a message issued by a semi-automatic script] Hello, If you receive this message, it means you have filed a bug report on the Debian BTS about phoenix/firebird/firefox. You can read the history of the given bug report at the following URL: http://bugs.debian.org/259711 Now the bug list for firefox is quite inhuman to track, we (maintainers) need to clean up these and for that we would need your help. What you are asked for is to check whether, for the bug you're contacted for, - it still happens with the mozilla-firefox 1.0 package you can find in the testing or the unstable distribution - we are awaiting for your feedback/answer to a question/test to know what we can further do If you don't see the bug anymore with newer versions of firefox, please send a message to 259711-done@bugs.debian.org saying it is gone. That will close the bug. If you still can see the bug, please send a message to 259711@bugs.debian.org to confirm it still happens. If you have some more information to give, it will be much appreciated. If the last message(s) in the bug were asking for more information, please answer our questions. Thank you in advance for helping us to sort out all these bugs. Mike and Eric
reassign 259711 firefox thanks Still seeing this problem in 1.5?-----BEGIN GEEK CODE BLOCK----- Version: 3.12 GCS d- s++: a-- C+++ UL+++ P++ L++ E++ W++ N+ o K- w+ O? M++ V-- PS+ PE Y+ PGP++ t++ 5++ X+ R tv++ b+++ DI+ D+ G e h! r- y+ ------END GEEK CODE BLOCK------
yes. Greetings Marc
Dear Firefox/Iceweasel user, Thanks for your interest in Firefox/Iceweasel and the bug report you have contributed. Your bug report [0] was done for a version which isn't a part of debian anymore. Debian 4.0 (Etch) was released with version 2.0.0.3. Please reproduce your bug on an updated version of Iceweasel and confirm it still exists, or close it as irrelevant for recent versions. If you don't know or are not sure how to update or close your bug report, please contact me directly, and I'll help you. IMPORTANT: In any case, please provide version info, as we use it to determine the relevance of the bug. As this bug is quite old, I intend to close it if you don't update your bug report in the next 6 weeks. This is the time line for the old bugs cleanup: 1. October 1st - first notice. 2. October 15th - Second notice. 3. October 29th - Third notice. 4. November 12th - Closing the bug. Please help the Firefox/Iceweasel maintainer to help you (: [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=259711
Dear Firefox/Iceweasel user, Thanks for your interest in Firefox/Iceweasel and the bug report you have contributed. Your bug report [0] was done for a version which isn't a part of debian anymore. Debian 4.0 (Etch) was released with version 2.0.0.3. Please reproduce your bug on an updated version of Iceweasel and confirm it still exists, or close it as irrelevant for recent versions. If you don't know or are not sure how to update or close your bug report, please contact me directly, and I'll help you. IMPORTANT: In any case, please provide version info, as we use it to determine the relevance of the bug. As this bug is quite old, I intend to close it if you don't update your bug report in the next 6 weeks. This is the time line for the old bugs cleanup: 1. October 1st - first notice. 2. October 15th - Second notice. 3. October 29th - Third notice. 4. November 12th - Closing the bug. Please help the Firefox/Iceweasel maintainer to help you (: [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=259711
tags #259711 - moreinfo thanks Yes, because nobody cared about this bug in three years and three months. Done. Confirmed. Any more burning hoops to jump trough to allow this bug to rot away in the BTS for three more years?
tags #259711 - moreinfo thanks Yes, because nobody cared about this bug in three years and three months. Done. Confirmed. Any more burning hoops to jump trough to allow this bug to rot away in the BTS for three more years?
tags #259711 - moreinfo thanks Yes, because nobody cared about this bug in three years and three months. Done. Confirmed. Any more burning hoops to jump trough to allow this bug to rot away in the BTS for three more years?