Opened 5 years ago

Closed 2 years ago

#4726 closed defect (fixed)

Browse can't reproduce html5 video

Reported by: manuq Owned by:
Priority: High Milestone: Unspecified
Component: Browse Version: Unspecified
Severity: Major Keywords: AU
Cc: Distribution/OS: Unspecified
Bug Status: Unconfirmed

Description

Environment: XO-1.75, os 13.2.0 build 13 (latest one)

TestCase:

The sound can be heard, but the video is frozen. The video updates only after several seconds.

I attach two test scripts.

  • videoweb1.py opens the testpage mentioned above with WebKit1, the same used by Browse. The same symptoms are shown.
  • videoweb2.py tries to use WebKit2, but returns with a segfault. WebKit2 was in development when Fedora 18 was released.

It would be great to check if the WebKit in F20 fixes this. We need an XO build with F20 for that.

Another possibility might be video drivers.

Attachments (2)

videoweb1.py (435 bytes) - added by manuq 5 years ago.
videoweb2.py (411 bytes) - added by manuq 5 years ago.

Download all attachments as: .zip

Change History (8)

Changed 5 years ago by manuq

Changed 5 years ago by manuq

comment:1 Changed 5 years ago by godiard

Testing on a xo-4 with 13.3.0 (Au image) with vmeta the examples from http://www.quirksmode.org/html5/tests/video.html:

  • H264/MP4: video not displayed
  • WebM: very slow (may be one frame by second)
  • Ogg/Theora: slow, but better than WebM

comment:2 Changed 5 years ago by quozl

Thanks. Interesting. 13.2.0-13 does not include VMeta. XO-1.75 performance is quite different to XO-4. Are the VMeta components installed on the XO-1.75 laptop? http://wiki.laptop.org/go/Vmeta

comment:3 Changed 5 years ago by mmack

  • Keywords AU added

comment:4 follow-up: Changed 5 years ago by SAMdroid

Is this a sugar bug? Shouldn't this be on the OLPC bug tracker?

comment:5 in reply to: ↑ 4 Changed 5 years ago by quozl

Replying to SAMdroid:

Is this a sugar bug? Shouldn't this be on the OLPC bug tracker?

Not until it is proven that it isn't a Browse problem. That can be done by using the WebKit GTK launchers, /usr/libexec/webkitgtk{,3}/GtkLauncher ... if the problem persists, then it isn't Browse, but is instead WebKit, or graphics drivers. Fedora 20 does change all this.

comment:6 Changed 2 years ago by quozl

  • Resolution set to fixed
  • Status changed from new to closed

WebKit2 based Browse-200 and later from git does fix this on generic hardware, closing.

Note: See TracTickets for help on using tickets.