User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b4pre) Gecko/20090309 Shiretoko/3.1b4pre Build Identifier: recent firefox nightlies, both mozilla-central and the 1.9.1 branch stopped playing videos that are served by oggz-chop. or are missing the Content-Length header. i.e. any time offset request on archive.org: http://ia331342.us.archive.org/2/items/night_of_the_living_dead/night_of_the_living_dead.ogv?t=0:20:00/0:20:50 Reproducible: Always Steps to Reproduce: 1. open http://ia331342.us.archive.org/2/items/night_of_the_living_dead/night_of_the_living_dead.ogv?t=0:20:00/0:20:50 Actual Results: does not play video, just gives loading feedback Expected Results: video should play
Regression range is http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=af782d5ec362&tochange=d5c6400afebd
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: x86 → All
Version: unspecified → Trunk
Bug 477899 landing caused the problem.
Status: NEW → ASSIGNED
Flags: blocking1.9.1? → blocking1.9.1+
Priority: -- → P1
I've tracked this down to the update to the latest liboggz changes in bug 477899. liboggplay won't play videos produced by oggz-chop when used with this version of liboggz.
Trac ticket 453 raised for this with the liboggplay/liboggz maintainers: https://trac.annodex.net/ticket/453
The fix is available in oggplay's git repository: "http://git.xiph.org/?p=liboggplay.git;a=commit;h=b4a7efa06d46596515071490cb255c3548d90371"
Status: ASSIGNED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Hey Chris - is it okay if I assign this to you for 1.9.1 landing? Just trying to make sure that every blocker has an assignee.
Assignee: nobody → chris.double
Bug 485291 has landed in 1.9.1 fixing this.
Verified fix on Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.2a1pre) Gecko/20090507 Minefield/3.6a1pre and Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b5pre) Gecko/20090507 Shiretoko/3.5b5pre
Status: RESOLVED → VERIFIED
Keywords: fixed1.9.1 → verified1.9.1
You need to log in before you can comment on or make changes to this bug.