Something changed between the 126.96.36.199 and 188.8.131.52 releases that usually stops firefox-bin before it can launch a GUI. When it does manage to launch a window, the widgets are "active" but unresponsive, i.e. the program doesn't hang but it doesn't load web page or even open menus.
Firefox 184.108.40.206 and above are still usable as rendering engine - for instance, www-client/epiphany-2.16.3 can use it fine, so the problem is in Firefox's own GUI changes since 220.127.116.11.
When it fails to produce even a window, it goes like this:
% - - - - - - - - - - - - - - - - - - - %
jeroen@elmer ~ $ firefox
/usr/lib/mozilla-firefox/mozilla-xremote-client: Error: Failed to find a running server.
No running windows found
Removing /home/jeroen/.mozilla/firefox/vg8vpvnr.default/compreg.dat leftover from older firefox
firefox-bin exited with non-zero status (1)
jeroen@elmer ~ $
% - - - - - - - - - - - - - - - - - - - %
Despite recent changes (gcc upgrade from 4.1.1 to 4.1.2, glibc upgrade from 2.3.6 to 2.5) mozilla-firefox-18.104.22.168 still works fine, so the problem must be somewhere in (Firefox's use of) glib or gtk+ (is my best guess).
I am assigning the bug to mozilla@ because the first priority is probably to figure out what changed between 22.214.171.124 and 126.96.36.199's GUIs that produced this problem. When that's clear, it's probably up to hppa@ to find a fix. I noticed that hppa's earlier patch is also still out there.
Sun Jun 3 23:04:04 CEST 2007
Portage 188.8.131.52 (default-linux/hppa/2007.0, gcc-4.1.2, glibc-2.5-r3, 184.108.40.206-hppa-JeR parisc)
System uname: 220.127.116.11-hppa-JeR parisc PA8700 (PCX-W2)
Gentoo Base System release 1.12.9
Timestamp of tree: Sun, 03 Jun 2007 14:50:01 +0000
distcc 2.18.3 hppa2.0-unknown-linux-gnu (protocols 1 and 2) (default port 3632) [disabled]
ccache version 2.4 [disabled]
sys-devel/autoconf: 2.13, 2.61
sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
CFLAGS="-O2 -pipe -mschedule=8000 -march=2.0 -ggdb -Wall"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config /usr/spool/PBS /var/bind /var/www/localhost/htdocs/wordpress/wp-config.php"
CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/php/apache2-php4/ext-active/ /etc/php/apache2-php5/ext-active/ /etc/php/cgi-php4/ext-active/ /etc/php/cgi-php5/ext-active/ /etc/php/cli-php4/ext-active/ /etc/php/cli-php5/ext-active/ /etc/revdep-rebuild /etc/terminfo /etc/texmf/web2c"
CXXFLAGS="-O2 -pipe -mschedule=8000 -march=2.0 -ggdb -Wall"
FEATURES="autoaddcvs buildpkg cvs distlocks fixpackages notitles sandbox sfperms splitdebug strict"
GENTOO_MIRRORS="http://ftp.easynet.nl/mirror/gentoo/ http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ http://ftp.rhnet.is/pub/gentoo/ http://ftp.snt.utwente.nl/pub/os/linux/gentoo "
LINGUAS="en nl he"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*"
Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
It's not just Mozilla Firefox that is affected, but Seamonkey as well.
What about thunderbird?
Test with both 1.5 and 2.0 series please :)
(In reply to comment #2)
> What about thunderbird?
> Test with both 1.5 and 2.0 series please :)
Thunderbird isn't patched or keyworded for HPPA like Seamonkey and Firefox are. Just for good measure, I built and ran Thunderbird (mail-client/thunderbird-18.104.22.168) and it exhibited the exact same problem as Seamonkey: it shows a GUI but doesn't respond (although the GUI itself does respond superficially).
So let's focus our attention to Firefox and Seamonkey.
Same on 22.214.171.124/1.1.3?
(In reply to comment #4)
> Same on 126.96.36.199/1.1.3?
Of course. What could possibly have changed to better the situation? Something broke a few versions ago and nothing has been done to mend it...
armin76 pointed out a HPPA-specific patch that Debian uses for mozilla-firefox that is missing in Gentoo's 188.8.131.52 and up:
--- /var/tmp/portage/www-client/mozilla-firefox-184.108.40.206/work/mozilla/xpcom/reflect/xptcall/src/md/unix/xptcstubs_asm_parisc_linux.s 2007-07-23 13:05:26.000000000 +0000
+++ xpcom/reflect/xptcall/src/md/unix/xptcstubs_asm_parisc_linux.s 2007-07-23 13:18:53.000000000 +0000
@@ -46,6 +46,13 @@
LDO -40-curframesz-lastframesz(%r30),%r24 ; normal args is arg2
LDO -80(%r30),%r23 ; floating args is arg3
+; BL .+8,%r2
+; ADDIL L'PrepareAndDispatch-$PIC_pcrel$0+4,%r2
+; LDO R'PrepareAndDispatch-$PIC_pcrel$1+8(%r1),%r1
+; LDSID (%r1),%r31
+; MTSP %r31,%sr0
.CALL ARGW0=GR,ARGW1=GR,ARGW2=GR,ARGW3=GR,RTNVAL=GR ;in=23-26;out=28;
BL PrepareAndDispatch, %r31
Whatever it does, it does not fix the issue.
Created attachment 125927 [details, diff]
Gentoo's versus Debian's firefox 220.127.116.11, according to armin76.
(In reply to comment #7)
> Gentoo's versus Debian's firefox 18.104.22.168, according to armin76.
Debian's iceweasel 22.214.171.124 too.
After armin76 asked me to a dozen times, I used debootstrap to create a "sid" chroot and found that Debian's iceweasel-126.96.36.199-1 works correctly:
user agent: Mozilla/5.0 (X11; U; Linux parisc; en-US; rv:188.8.131.52) Gecko/20070719 Iceweasel/184.108.40.206 (Debian-220.127.116.11-1);
Again, I have no idea what this proves.
(In reply to comment #9)
> Again, I have no idea what this proves.
Just to be ABSOLUTELY clear on this issue: iceweasel is a fork of firefox, with a different source tree, maintained at a different location. Comparing runtime behaviour is not useful at this point, while comparing the source trees may well be, so we can backport to firefox some of the changes that make iceweasel work on HPPA.
Until www-client/iceweasel hits the Portage tree, testing it in a Debian chroot or testing iceweasel binaries on a Gentoo/HPPA system is useless.
Backporting iceweasel's HPPA-specific changes to firefox might prove a lot more fruitful.
(In reply to comment #10)
> (In reply to comment #9)
> > Again, I have no idea what this proves.
> Just to be ABSOLUTELY clear on this issue: iceweasel is a fork of firefox, with
> a different source tree, maintained at a different location. Comparing runtime
> behaviour is not useful at this point, while comparing the source trees may
> well be, so we can backport to firefox some of the changes that make iceweasel
> work on HPPA.
> Until www-client/iceweasel hits the Portage tree, testing it in a Debian chroot
> or testing iceweasel binaries on a Gentoo/HPPA system is useless.
> Backporting iceweasel's HPPA-specific changes to firefox might prove a lot more
Right, the thing is that we didn't knew if iceweasel on Debian worked on HPPA. So it's stupid to compare their code if we *dont* know if it really works. We now know that on Debian it works, now we have to see if it works under our system, to see if its some lib causing that or it's the app itself.
Again, i just wanted to check that because i know they don't test the packages unless someone has a problem, like there was with qt-4.3.0 on alpha.
Wed Oct 25 13:08:32 2006 >>> www-client/mozilla-firefox-2.0
Fri Nov 10 08:08:47 2006 >>> www-client/mozilla-firefox-2.0
Wed Nov 15 06:13:58 2006 <<< www-client/mozilla-firefox-2.0
Wed Nov 15 06:41:43 2006 >>> www-client/mozilla-firefox-2.0
Mon Nov 20 00:17:24 2006 <<< www-client/mozilla-firefox-2.0
Mon Nov 20 00:17:24 2006 >>> www-client/mozilla-firefox-2.0-r1
Sun Dec 3 07:25:47 2006 <<< www-client/mozilla-firefox-2.0-r1
Sun Dec 3 07:25:47 2006 >>> www-client/mozilla-firefox-2.0-r2
Wed Dec 20 03:28:25 2006 <<< www-client/mozilla-firefox-2.0-r2
Wed Dec 20 14:32:03 2006 >>> www-client/mozilla-firefox-2.0-r2
Thu Dec 21 23:41:31 2006 <<< www-client/mozilla-firefox-2.0-r2
Thu Dec 21 23:41:31 2006 >>> www-client/mozilla-firefox-18.104.22.168
Sun Jan 14 22:43:55 2007 <<< www-client/mozilla-firefox-22.214.171.124
Sun Jan 14 22:43:55 2007 >>> www-client/mozilla-firefox-126.96.36.199-r2
Tue Jan 16 18:40:24 2007 <<< www-client/mozilla-firefox-188.8.131.52-r2
Mon Feb 26 05:21:48 2007 >>> www-client/mozilla-firefox-184.108.40.206
Sat Mar 3 17:06:08 2007 >>> www-client/mozilla-firefox-220.127.116.11
Fri Mar 23 04:26:48 2007 <<< www-client/mozilla-firefox-18.104.22.168
Fri Mar 23 04:26:48 2007 >>> www-client/mozilla-firefox-22.214.171.124
Tue Apr 3 05:29:14 2007 >>> www-client/mozilla-firefox-126.96.36.199
Wed Apr 18 06:13:06 2007 <<< www-client/mozilla-firefox-188.8.131.52
Wed Apr 18 06:21:47 2007 >>> www-client/mozilla-firefox-184.108.40.206
Wed Apr 18 17:44:44 2007 <<< www-client/mozilla-firefox-220.127.116.11
Wed Apr 18 17:44:44 2007 >>> www-client/mozilla-firefox-18.104.22.168
Fri Jun 1 06:12:09 2007 <<< www-client/mozilla-firefox-22.214.171.124
Fri Jun 1 06:12:09 2007 >>> www-client/mozilla-firefox-126.96.36.199
Fri Jun 1 08:53:19 2007 >>> www-client/mozilla-firefox-188.8.131.52
Mon Jun 4 09:39:14 2007 >>> www-client/mozilla-firefox-184.108.40.206
Mon Jun 4 17:26:51 2007 <<< www-client/mozilla-firefox-220.127.116.11
Mon Jun 4 17:26:51 2007 >>> www-client/mozilla-firefox-18.104.22.168
Mon Jun 4 21:16:32 2007 <<< www-client/mozilla-firefox-22.214.171.124
Mon Jun 4 21:16:32 2007 >>> www-client/mozilla-firefox-126.96.36.199
Fri Jul 13 09:41:03 2007 <<< www-client/mozilla-firefox-188.8.131.52
Fri Jul 13 18:05:55 2007 >>> www-client/mozilla-firefox-184.108.40.206
Thu Jul 19 18:13:58 2007 <<< www-client/mozilla-firefox-220.127.116.11
Thu Jul 19 18:13:58 2007 >>> www-client/mozilla-firefox-18.104.22.168
Tue Jul 24 01:49:48 2007 >>> www-client/mozilla-firefox-22.214.171.124
Tue Jul 24 21:04:25 2007 >>> www-client/mozilla-firefox-126.96.36.199
Wed Jul 25 00:13:26 2007 >>> www-client/mozilla-firefox-188.8.131.52
Would it help if I raised the severity?
Created attachment 134249 [details]
I can't test firefox on hake because it never shows up, no version shows up, it just segfaults.
Let's try this way: I've sucessfully built iceweasel on ia64(and the iceweasel source, it's exactly the same as firefox, do a diff and you'll see).
This ebuild applies the patches from Debian, and only the patches they apply.
You need http://sources.gentoo.org/viewcvs.py/*checkout*/gentoo/src/patchsets/mozilla-firefox/184.108.40.206/002_firefox-libdeps.patch?rev=1.1 in the files dir as well.
Let's see if it works...as i can't test it
(In reply to comment #14)
> Let's try this way: I've sucessfully built iceweasel on ia64(and the iceweasel
> source, it's exactly the same as firefox, do a diff and you'll see).
> This ebuild applies the patches from Debian, and only the patches they apply.
> You need
> in the files dir as well.
> Let's see if it works...as i can't test it
I'll test that.
With this "iceweasel" build it doesn't simply quit with a weird exit status, but just sits there presenting a window with two buttons showing no text labels, like in the URL above.
Please attach a build log
(In reply to comment #18)
In other words, we might need to look out for things like this in the future:
--- 004_mozilla-hppa.patch 2007/11/28 11:41:36 1.1
+++ 004_mozilla-hppa.patch 2007/11/29 14:04:43 1.2
@@ -21,7 +21,7 @@
-+ifneq (,$(filter parisc parisc64,$(OS_TEST)))
++ifneq (,$(filter hppa2.0 hppa1.1,$(OS_TEST)))
+#ifeq ($(CC),gcc) # Do not check for gcc since there is only this compiler on linux for hppa
+CPPSRCS := xptcinvoke_pa32.cpp xptcstubs_pa32.cpp
+ASFILES := xptcstubs_asm_parisc_linux.s xptcinvoke_asm_parisc_linux.s
Got the problem located and fixed. It was a regression from bug 168893, it detected hppa2.0 instead of parisc, so it wasn't compiling the right xpcom files, so it didn't work.
It's fixed in mozilla-firefox-220.127.116.11 patchset 0.2.
seamonkey-1.1.6 patchset 0.3
xulrunner-18.104.22.168 patchset 0.1
Sorry for taking this so long.