Bug#624502: iceweasel: URL bar not working anymore

[Mike Hommey]

On Fri, Apr 29, 2011 at 09:58:26AM +0530, Onkar Shinde wrote:
> Package: iceweasel
> Version: 3.5.18-1
> Severity: important
> 
> For last few days the URL bar in iceweasel is not responding to 'Enter' key. Also the right arrow (indicating 'Go to URL' action) does not work. So I can not open any websites from URL bar. Following error is seen in 'Error Console' when I try.
> 
> 
> Error: uncaught exception: [Exception... "Component returned failure code: 0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE) [nsIJSCID.getService]"  nsresult: "0x80570016 (NS_ERROR_XPC_GS_RETURNED_FAILURE)"  location: "JS frame :: chrome://browser/content/search/search.xml :: get_searchService :: line 145"  data: no]
> 
> 
> Please note that I can open websites from bookmarks menu.
> I thought that the installation had become corrupt somehow. So I reinstalled xulrunner-1.9.1 and iceweasel. At the time of installation I see following error which might be related to the problem.
> 
> 
> Selecting previously deselected package xulrunner-1.9.1.
> (Reading database ... 165411 files and directories currently installed.)
> Unpacking xulrunner-1.9.1 (from .../xulrunner-1.9.1_1.9.1.18-1_powerpc.deb) ...
> Selecting previously deselected package iceweasel.
> Unpacking iceweasel (from .../iceweasel_3.5.18-1_powerpc.deb) ...
> Adding 'diversion of /usr/bin/firefox to /usr/bin/firefox.real by iceweasel'
> Processing triggers for man-db ...
> Processing triggers for menu ...
> Processing triggers for gnome-menus ...
> Processing triggers for desktop-file-utils ...
> Processing triggers for hicolor-icon-theme ...
> Setting up xulrunner-1.9.1 (1.9.1.18-1) ...
> ../xpcshell: error while loading shared libraries: ./libxul.so: R_PPC_REL24 relocation at 0x0f9ed56c for symbol `_restgpr_29_x' out of range
> update-alternatives: using /usr/lib/xulrunner-1.9.1/xulrunner-stub to provide /usr/bin/xulrunner-stub (xulrunner-stub) in auto mode.
> Setting up iceweasel (3.5.18-1) ...
> Processing triggers for menu ...

This error should be fixed in version 3.5.19-2. Can you check if the
other problem still remains?

Mike