61–70 of 72 posts
What does that mean? Well, depending on your region, ISP, and a bit of luck, you'll hit different Google servers, at different places, etc.
Some of them have different things, some of them have new updates others don't, etc.
Which may be an explanation for the author having issues (then again it's just ONE possibility).
Specially it could be that regular HTTP was failing and not SPDY for example.
Personally I haven't had that either.
Another potential possibility: Ubuntu Firefox is Mozilla's Firefox coupled with arbitrary modifications by the Ubuntu developers. In principle I respect Ubuntu's position and desire to make things right by their users. But in practice, having been in the same relationship as an author of Chrome for Linux I can tell you that it's always dangerous to have people who aren't browser developers make modifications to a bro…
(OK, that's the cranky developer-speak for "If you can reproduce the problem while taking a packet capture I'd be glad to help troubleshoot".)
I don't work at Google or on Chromium but I can take a look at it and pass it along if it looks like something out of the ordinary. My email is in my profile.
Another potential possibility: Ubuntu Firefox is Mozilla's Firefox coupled with arbitrary modifications by the Ubuntu developers. In principle I respect Ubuntu's position and desire to make things right by their users. But in practice, having been in the same relationship as an author of Chrome for Linux I can tell you that it's always dangerous to have people who aren't browser developers make modifications to a bro…
Another potential possibility: Ubuntu Firefox is Mozilla's Firefox coupled with arbitrary modifications by the Ubuntu developers. In principle I respect Ubuntu's position and desire to make things right by their users. But in practice, having been in the same relationship as an author of Chrome for Linux I can tell you that it's always dangerous to have people who aren't browser developers make modifications to a bro…
I think this is precisely it. I've had this same problem and others on Linux Mint. I wasn't able to fix them until I built FF from source.
Earlier quoted context omitted.
Maintaining Chromium packages on Linux is a nightmare. Here's the line count for different browser packages on Gentoo: 408 chromium/chromium-20.0.1123.4.ebuild 349 firefox/firefox-12.0.ebuild 42 rekonq/rekonq-0.9.2.ebuild 98 midori/midori-0.4.5.ebuild 90 epiphany/epiphany-3.4.1.ebuild 61 conkeror/conkeror-1.0_pre20120223.ebuild 64 dillo/dillo-3.0.2.ebuild
So, it's of the same order of difficulty as Firefox? Is this surprising?
Earlier quoted context omitted.
Maintaining Chromium packages on Linux is a nightmare. Here's the line count for different browser packages on Gentoo: 408 chromium/chromium-20.0.1123.4.ebuild 349 firefox/firefox-12.0.ebuild 42 rekonq/rekonq-0.9.2.ebuild 98 midori/midori-0.4.5.ebuild 90 epiphany/epiphany-3.4.1.ebuild 61 conkeror/conkeror-1.0_pre20120223.ebuild 64 dillo/dillo-3.0.2.ebuild
The interesting question isn't the raw number, it's what those 408 lines are doing - it's entirely possible that half of that could go upstream. For some years, lots of vendors had patches to mess around with perl's default @INC order, all of which were distro-specific and not really generalisable, because nobody had bothered to submit the upstream change that would have got rid of that whole class of patches. Now, I…
Earlier quoted context omitted.
Firefox has SPDY support as of a version or two ago and uses SPDY on Google sites. I seem to that feature being on by default, even.
SPDY isn't enabled by default until Firefox 13 (currently on the beta channel, scheduled for release in four weeks).
It's not all the time and I haven't investigated to find out what the problem is... Bing search always works so I just use that.