I am posting this bug here after Epiphany devs told me it was a possible Gentoo xulrunner bug. The original bug is at http://bugzilla.gnome.org/show_bug.cgi?id=426076. Epiphany does not have Gecko in the user-agent when using the xulrunner backend. Websites that do browser sniffing for Gecko (i.e., GMail) do not work correctly. http://developer.mozilla.org/en/docs/Browser_Detection_and_Cross_Browser_Support notes that sites should look for "Gecko/" in the user-agent. Changing general.useragent.extra.epiphany to a string in the form of "Gecko/YYYMMDD Epiphany/2.18" fixes the broken sites. Using "Gecko/Epiphany/2.8" does not fix all the sites. Unfortunately, in embed/mozilla/mozilla-embed-single.cpp, Epiphany fills the useragent after loading user preferrences, so if I restart Epiphany the user-agent is set back to "Epiphany/2.18" and I must change it again.
Forgot to mention (again, like on the GNOME bug), I am using xulrunner-1.8.0.4
I've been using this for a while, and I have no problems, with gmail or anything else. My useragent, as nearly as I can tell, shows up as: Mozilla/5.0 (X11; U; Linux x86_64; en; rv:1.8.0.4) Epiphany/2.18 How are you finding your UA? Can you post your emerge --info output?
Note the end paragraph... I am looking at lighttpd logs and using the "Live HTTP Headers" extension. My UA is the same as yours... so now I am confused. Gmail and wellsfargo don't complain when I change it from: Mozilla/5.0 (X11; U; Linux x86_64; en_US; rv:1.8.0.4) Epiphany/2.18 to: Mozilla/5.0 (X11; U; Linux x86_64; en_US; rv:1.8.0.4) Gecko/20070222 Epiphany/2.18 Wells Fargo still complains if I use: Mozilla/5.0 (X11; U; Linux x86_64; en_US; rv:1.8.0.4) Gecko/Epiphany/2.18 With Firefox backend, Ephiphany uses: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.0.3) Gecko/20060503 Epiphany/2.14 Firefox/1.5.0.3" Firefox uses: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.3) Gecko/20061201 Firefox/2.0.0.3 The 20070222 is random date that I am using (build date of official Firefox 2.0.0.4). I don't understand how you are not having problems... I am using paludis, so here is my paludis --info (with repository information removed): paludis 0.22.2 Built by root@Mastermind on 2007-04-02T17:15:52-0500 CXX: x86_64-pc-linux-gnu-g++ 4.1.1 (Gentoo 4.1.1-r3) CXXFLAGS: -march=athlon64 -O2 -g LDFLAGS: -Wl,--as-needed DATADIR: /usr/share LIBDIR: /usr/lib64 LIBEXECDIR: /usr/libexec SYSCONFDIR: /etc stdlib: GNU libstdc++ 20060524 libebt: 1.3.0 libwrapiter: 1.0.0 sandbox: enabled Repository virtuals: Configuration information: format: virtuals Repository installed_virtuals: Configuration information: format: installed_virtuals Repository gentoo: Configuration information: buildroot: /var/tmp/paludis cache: /usr/portage/metadata/cache distdir: /usr/portage/distfiles eclassdirs: /usr/portage/eclass format: ebuild location: /usr/portage names_cache: /usr/portage/.cache/names newsdir: /usr/portage/metadata/news pkgdir: /usr/portage/packages profiles: /usr/portage/profiles/default-linux/amd64/2006.1/desktop securitydir: /usr/portage/metadata/glsa setsdir: /usr/portage/sets sync: rsync://wife/gentoo-portage sync_options: write_cache: /var/cache/paludis/metadata Package information: app-admin/eselect-compiler: (none) dev-java/java-config: 1.3.7, 2.0.31-r5 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: (none) dev-util/confcache: (none) sys-apps/sandbox: 1.2.17 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 sys-devel/binutils: 2.17 sys-devel/gcc-config: 1.3.15-r1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 Variable information: ACCEPT_KEYWORDS: AUTOCLEAN: CBUILD: x86_64-pc-linux-gnu CFLAGS: -march=athlon64 -O2 -g CHOST: x86_64-pc-linux-gnu CONFIG_PROTECT: CONFIG_PROTECT_MASK: CTARGET: CXXFLAGS: -march=athlon64 -O2 -g DISTDIR: /usr/portage/distfiles FEATURES: GENTOO_MIRRORS: INSTALL_MASK: LANG: LC_ALL: LDFLAGS: -Wl,--as-needed LINGUAS: MAKEOPTS: -j2 PKGDIR: PORTAGE_COMPRESS: PORTAGE_COMPRESS_FLAGS: PORTAGE_RSYNC_EXTRA_OPTS: PORTAGE_RSYNC_OPTS: PORTAGE_TMPDIR: /var/tmp/paludis PORTDIR: /usr/portage PORTDIR_OVERLAY: SYNC: USE: www-client/epiphany: installed: 2.18.0* {:0} Use flags: (-debug) (doc) (python) (spell) (xulrunner) net-libs/xulrunner installed: 1.8.0.4* {:0} Use flags: (-debug) (-elibc_FreeBSD) (gnome) (ipv6) (java) (xinerama) (-xprint) I wrote all of this, and then noticed that 1.8.0.11 was added to portage, so I re-checked bug 170101 to find out that the problem I am having was fixed in 1.8.0.8. I will build 1.8.0.11 and then close this bug if it is fixed. I still don't understand why it works for you Daniel...
I will try Xulrunner 1.8.1.3 instead.
The new xulrunner-1.8.1.3 fixes this for me with Gmail, which was the only site I had trouble with. Denis.
Good stuff. We knew that 1.8.0.* had problems, but it was the best we had...
Yep. Fixed me too. Yay! Thanks!
