Certain web pages cannot be opened

[Harry]

Binary package hint: chromium

I have the latest daily version (5.0.393.0) installed from the PPA for Ubuntu Chromium - Daily Builds.
And I found that certain web pages cannot be opened, for example:
www.gigabyte.com.tw
www.gigabyte.fi
I get the error message "the page is unresponsive", which is non sense of course.
The former chromium version (5.0.391.0) works OK, like Firefox 3.6.3 does too.
When I downgrade chromium to 5.0.391.0 it opens gigabyte page right away.
I have tested this with both 32-bit jaunty and 64-bit lucid, both fully updated.

[davosmith (8-launchpad-davosmith-co-uk)]

I appear to be having the same problem with signing in to mail.google.com (the 'loading' screen appears, but gets no further) and a locally installed version of Moodle, running via apache on localhost. In both cases Firefox 3.5.9 is displaying them fine.

I can confirm that the two websites listed above are giving the same problem (I note that the title of the page appears in the tab, but then the page times out).

[Alex Valavanis (valavanisalex)]

This bug certainly seems to exist upstream in Chromium, but unless I'm mistaken, it doesn't affect the latest official Ubuntu package (5.0.342.9~r43360-0ubuntu2). For that reason, I'll mark it as Invalid in Ubuntu but keep it open as an upstream bug. If anyone is able to reproduce this with the latest official Ubuntu package, please feel free to change its status.

[Harry (harry33)]

Alex,
This bug has appeared only after the version 5.0.391.0 of the daily builds.
The above mentioned is the latest version without the bug.
The version (5.0.342) in official lucid repos is way much older and does not have the bug.
This bug has already been reported upstream:
http://code.google.com/p/chromium/issues/detail?id=43013

What is interesting here is that the more recent version 5.0.395 in Archlinux appears to be working OK.

[Fabien Tassin (fta)]

This regression appeared at the worse time ever, i.e. when almost all the builders were re-affected to another task, leaving a really long queue of unbuilt packages behind (queue estimated to ~5 days, still growing).
Once the builders are back, this will return to normal.
There's nothing i can do in the meantime, except advise you to wait, rollback to the previous version or switch to the dev or beta PPAs.

[Evan Martin (Chromium) (evan-chromium)]

I am not sure what caused this problem, but I expect you got an unlucky version.

Fabien: I wonder if, for your daily builds, it'd be more effective to use
  http://chromium-status.appspot.com/lkgr
which is the latest version that passed our tests. It's typically between 0 and 20 revisions behind the most recent revision (we don't allow people to commit when the tests fail, but sometimes it takes a while for us to discover the more lengthy tests have failed).

[Fabien Tassin (fta)]

@evan: yep, probably an unlucky version.
as for lkgr, i used to use it, but it was so often broken that i gave up (~ last Sept).

Users of daily builds should expect regressions from time to time. Otherwise, there are more stable versions available.

[Harry (harry33)]

The issue seems to fixed in the latest Ubuntu Daily Builds version (5.0.395.0).
I will check this once the 5.0.396.0 is published (building right now).

[Harry (harry33)]

I can confirm now the bug is gone.
I have tested 32-bit jaunty and 64-bit lucid with both Chromium 5.0.395.0 and 5.0.396.0.
There is no bug anymore.
So this suggests the version 5.0.393.0 was an unlucky one.

[Pierre Habouzit (madcoder)]

For what it's worth, version 6.0.396.0~svn20100505r46428-0ubuntu1~ucd1~jaunty from PPA is also (and still) affected...

[Christopher Forster (christopherforster)]

I still get the error message "Page(s) Unresponsive" on Chromium 9.0.570.0 (64562) Ubuntu 10.10.