Bugzilla – Bug 557385
Firefox can only open the homepage, no other page from other servers
Last modified: 2009-12-09 21:15:25 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); wa; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 fter having installed an experimental language pack made by myself (http://walotux.walon.org/firefox/walloon_language_pack-3.5.0.1.20091111.1-fx.xpi) I tried to uninstall it to install a more up to date version. After uninstalling it, I got a message of XML error (sorry, I haven't copied it). Sinds then, I can't open anymore any other page but the homepage. I start with for example firefox.com and I open a page from another server adress, it gives a page from mozilla "404 not found". If I start with openSUSE (command "firefox http://www.opensuse.org"), it will open opensuse.org but when trying after firefox.com, it gives an error page from opensuse.org... I've uninstalled all the walloon language pack and set it back tu en-US. I've tried to remove the profile in ~/.mozilla/firefox, it doesn't help. I've created a new profile it doesn't change anything I've tried in safe mode, it doesn't help I've uninstalled and reinstalled the RPM, to change to Firefox 32bit (suse's RPM) but it doesn't change anything. When I try with another Linux user (without installing the addon) it works without problem. I've tried to reproduce it with the new package on the official build Mozilla/5.0 (X11; U; Linux i686 (x86_64); wa; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5 and it doesn't reproduce it. I'll try with a fresh installation of openSUSE on a virtual box. Everything happens like my addon changed something in a config file in the user home folder but that's not located in ~/.mozilla/firefox/ Something strange, another tester in Windows XP has reported a similar problem, after uninstalling it and reseting the locale to fr, het got this: http://walon.org/pipermail/linux-wa/attachments/20091119/4d2cedc7/attachment-0001.jpe and had problems with "downloading some attachments from gmail and with many other pages". He says that it works well now. The message he got looks very similar with the one I had the first time I restarted FF after uninstalling language pack. Reproducible: Sometimes Steps to Reproduce: Steps to Reproduce: 1. Install Firefox (in openSUSE 11.2?, may buggy on other platforms, to try) 2. Install Walloon language pack from here: http://walotux.walon.org/firefox/walloon_language_pack-3.5.0.1.20091111.1-fx.xpi 3. Set general.useragent.locale in about:config to "wa" 4. Restart FF, it should be in Walloon. 5. Go to Usteyes->Pacaedjes and uninstall the Walloon language pack, don't close the addon window 6. Go to about:config and reset general.useragent.locale in about:config to "en-US" 7. Click in the addon window on the button "Restart Minefield" (or "Renonder Minefield", in Walloon) Actual Results: You get an XML error on the about:config page and when you try to open another page than the homepage, it doesn't work (as described above). Next time you launch FF, it should open about:config without problem but the other problem will persist Expected Results: No XML error message and to be able to navigate to more than one webpage. Notice that in the language pack that makes the problem there were one error: the file wa.jar was put on the root of the archive and not in the folder chrome/. I have since corrected it in an updated version. Another problem in that language pack is that I enabled the branding translations, it's why Firefox become Minefield. I also corrected it later. I've also installed and uninstalled the language pack in Moblin and it doesn't make any problem. Please help me to get my FF work correctly and to identify the problem want I want to distribute that language pack more widely. Thanks. PS: I reported the bug in Mozilla's bugzilla (https://bugzilla.mozilla.org/show_bug.cgi?id=530029) but I fill it here because I think it may be platform related.
I tried FF in Icewm and the problem wasn't present. The default theme in ICEWM is slightly different. So I tried to change of theme in KDE but it didn't solve anything. I've tried to reproduce it in a fresh installation of openSUSE 11.2 in virtualbox but it didn't reproduced it. I installed frome the OBS repo Mozilla the 3.5.5 version and it seems to work now. So, I can use FF but I don't know what happened... A kind of interference between KDE, my language pack and FF 3.5.4...
I am having a similar problem with Firefox, but I've not installed any language pack or anything other than standard updates. Firefox will only show the site it's been opened with, and won't open any link or bookmark. I've tried deleting my .mozilla directory for a fresh start, but this didn't work. Starting firefox from the command line doesn't show any error message, except for: *** nss-shared-helper: Shared database disabled (set NSS_USE_SHARED_DB to enable).
Same here after updating my clean x86_64 11.2 final installation with online update. Before the update firefox was working for me. A user local copy of the mainstream firefox version (32 bit) works very well.
Note: I also did not install any additional language pack.
I have the exact same problem after no changes to my system at all. One hour it was working - the next it simply stopped. Can view only homepage. Trying to access any other page gives the message "forbidden" or a messed up version of my home page. Changed to Firefox from the buildservice repo and all is working again - and even seems more snappy than the version that shipped with Opensuse 11.2
I definitely think it's not related to the language pack, so I removed the mention of it in the summary. I must say that for me, an update to 3.5.5 from the oS official updater solved the problem. Mark, Karsten, Colin, is the bug resolved with the official update (not the buildservice)?
I am afraid that for me, the problem persists with the official update. I haven't checked with any other update, including the OBS.
Anyone who still has a problem please tell us: - exact version of FF (please upgrade to the latest available from your repos; include if official or from some mozilla repo in OBS) - if you are using proxies - which desktop/wm you use - contents from your "Error console" within Firefox
kkeil@pingi6:~> rpm -qiv MozillaFirefox Name : MozillaFirefox Relocations: (not relocatable) Version : 3.5.5 Vendor: obs://build.opensuse.org/mozilla Release : 3.1 Build Date: Di 24 Nov 2009 16:14:08 CET Install Date: Di 08 Dez 2009 13:30:21 CET Build Host: build24 Group : Productivity/Networking/Web/Browsers Source RPM: MozillaFirefox-3.5.5-3.1.src.rpm Size : 3523221 License: GPL v2 or later ; LGPL v2.1 or later ; MPL 1.1 or later Signature : DSA/SHA1, Di 24 Nov 2009 16:15:15 CET, Key ID 026b47f3766da614 URL : http://www.mozilla.org/ Summary : Mozilla Firefox Web Browser No proxies. KDE4 with defaults error console has nothing if I do the following steps: call firefox from terminal: kkeil@pingi6:~> firefox forums.opensuse.org *** nss-shared-helper: Shared database disabled (set NSS_USE_SHARED_DB to enable).(see screenshot 1) I get the webpage, but without graphics. If I click on Register/Login I get page not found error.(see screenshot 2) Karsten
Created attachment 331557 [details] screenshoot1
Created attachment 331559 [details] screenshot 2
Karsten, to rule out one thing, please set Firefox in its preferences to use "No proxy" instead of the default 'Use system proxy settings'. I want to be sure that this is not the reason.
Good catch ! After changing this, it seems firefox is working again. I looked into yast/network/proxy it is deactivated. So what proxy was set and used ?
ok, good (or rather not). So everyone using official Firefox packages should not be affected! If you are, please let us know explicitely. Ok, in the OBS builds I have enabled one feature which is not in the official builds yet and that is libproxy support. So Firefox is using libproxy to figure out the proxy for every connection and there is either an issue in the new feature in Firefox or an issue with libproxy and its config on your system. Dominique can hopefully enlighten us how to check libproxy itself and from where it gets the settings on your system.
There is one other possibility: It could also be an issue with KDE integration for proxy settings. So please also let us know the exact KDE settings for proxy.
Forget my last comment and sorry for the noise. The libproxy support overrides the KDE integration so we need to check libproxy.
I already tested it. KDE proxy settings was "manually proxy config", but no proxy was set. If I change back firefox to "use system proxy settings", I get strange behavior again. After setting KDE to "direct internet connect" it is working too.
Last comment was a collision. Note: I never played with Proxy settings before, so this KDE setting was the default or caused by some other event.
One thing to verify is what libproxy finds as proxy configuration. The easiest for this is: sudo zypper install libproxy-tools and then proxy http://www.google.com (proxy is a small test application from the libproxy project, that uses the library and can be helpful for debugging as we do here). Please let us know the output of the the proxy command (with your proxy configured as it was, in the way when it did not work0.
(In reply to comment #17) > I already tested it. > KDE proxy settings was "manually proxy config", but no proxy was set. > If I change back firefox to "use system proxy settings", I get strange behavior > again. After setting KDE to "direct internet connect" it is working too. This makes one wonder what KDE actually expects to happen if you say you want to use the specified proxy but then don't specify a proxy... I though the default in KDE was to use http_envvar.
I cannot reproduce it any longer. If I try to change the KDE settings back, a popup complains about wrong values. I tried to modify .kde4/share/config/kioslaverc by hand (set ProxyType=1) but this do not give the bad behavior back. proxy http://www.google.com gives always direct:// The only idea is, that here was more wrong content in .kde4/share/config/kioslaverc which was then cleaned up. Unfortunately I do not have a backup of this file.
This turns out to be the same what coolo had once in bug 548678. Inconsistent proxy settings in KDE. Dominique, as I confirmed that libproxy is in use by the build. Does libproxy on KDE read from KDE settings in 11.2?
I can confirm that changing the proxy setting in Firefox solves the issue. I can now connect again, and I am very happy about that! I may have an idea of what is the root of the issue (but have no idea why it might be). My Firefox worked fine at first after installing 11.2. Then, I installed the nfs kernel server through YAST, and around about the same time Firefox stopped working. Memory is a bit fuzzy though, and I could be completely wrong. But the nfs server is the only thing I installed that may have anything to do with the system network settings.
The only "proof" we have currently is that the proxy settings in KDE were somehow screwed. That actually leads to connection issues with _and_ without libproxy support as we read from KDE on 11.2 directly by default. The reason how the proxy settings in KDE get messed up is unknown to me. I'll close this and reopen the other one. No idea if anything can be found though. In the end this really seems to be a dupe even if with more noise. Anyone who is experiencing this issue and running KDE should check his KDE proxy settings. Having empty manual proxies seems to be just wrong. If the problem persists for you, please reopen this one. *** This bug has been marked as a duplicate of bug 548678 ***
I must just say that the problem, resolved for me by upgrading, wasn't linked with the proxy, I don't use one, I use direct adsl. The problem is maybe more complex than that. But what is true is that it occured in KDE and not in IceWM.
(In reply to comment #25) > I must just say that the problem, resolved for me by upgrading, wasn't linked > with the proxy, I don't use one, I use direct adsl. The problem is maybe more > complex than that. > > But what is true is that it occured in KDE and not in IceWM. There is no way to prove that your issue wasn't the same or similar thing. Nobody here uses a proxy but for the analyzed systems the proxy settings were confused on KDE level. So currently we can only assess this issue.
(In reply to comment #23) > I can confirm that changing the proxy setting in Firefox solves the issue. I > can now connect again, and I am very happy about that! > Collin if you did not change KDE proxy settings, can you please attach(not copy & paste) your .kde4/share/config/kioslaverc
Created attachment 331822 [details] kioslaverc, as requested
if the issue is a KDE proxy error then the issue should also effect Konqueror should it not?