Totem locks up with 17.10 on AMD® E1-6010 apu with amd radeon r2 graphics × 2 (Lenovo)

Please install 'vainfo':

  sudo apt install vainfo

and then run 'vainfo' and paste the output here.

Please also try:

  sudo apt install mpv

and tell is if playing videos with mpv works better.

and tell us if playing videos with mpv works better.

I have the same problem - at least the same symptoms as the OP when playing MP4 viedos with totem on wayland.
My video card is an ATI HD5850 using the radeon driver.
The video will play in totem on xorg. It will also play on wayland with mpv or vlc.

The only warning I get from totem is:

(totem:7298): Gtk-WARNING **: Drawing a gadget with negative dimensions. Did you forget to allocate a size? (node slider owner GtkScale)

but I'm not sure if it is relevant.

vainfo output:

$ vainfo
libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_0_40
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.40 (libva )
vainfo: Driver version: mesa gallium vaapi
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple : VAEntrypointVLD
      VAProfileMPEG2Main : VAEntrypointVLD
      VAProfileVC1Simple : VAEntrypointVLD
      VAProfileVC1Main : VAEntrypointVLD
      VAProfileVC1Advanced : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264Main : VAEntrypointVLD
      VAProfileH264High : VAEntrypointVLD
      VAProfileNone : VAEntrypointVideoProc

As I prefer totem over the other players, my current workaround is to fallback to xorg.

It seems bug 1720820 is similar.

But for the moment this bug is owned by Ernest and is awaiting his reply.

MPV will play a choppy video stream, however once open, will not close. Had to reboot to close the player.

________________________________
From: <email address hidden> <email address hidden> on behalf of Daniel van Vugt <email address hidden>
Sent: Wednesday, October 25, 2017 2:11:38 AM
To: <email address hidden>
Subject: [Bug 1727210] Re: Totum locks up with 17.10

and tell us if playing videos with mpv works better.

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1727210

Title:
  Totum locks up with 17.10

Status in totem package in Ubuntu:
  Incomplete

Bug description:
  when trying to play videos in Totum on AMD® E1-6010 apu with amd
  radeon r2 graphics × 2 (Lenovo), the timer shows it's playing but
  there is no video. After about 10 seconds I get the "Video is not
  responding" "what do you want to do" "wait/force close" window. the
  only way to close it is to force it closed. Same result with MP4 and
  FLV videos.

  totum version= 3.26.0-0ubuntu1

  Ubuntu 17.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1727210/+subscriptions

libva info: VA-API version 0.40.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/r600_drv_video.so
libva info: Found init function __vaDriverInit_0_40
libva info: va_openDriver() returns 0
vainfo: VA-API version: 0.40 (libva )
vainfo: Driver version: mesa gallium vaapi
vainfo: Supported profile and entrypoints
      VAProfileMPEG2Simple : VAEntrypointVLD
      VAProfileMPEG2Main : VAEntrypointVLD
      VAProfileVC1Simple : VAEntrypointVLD
      VAProfileVC1Main : VAEntrypointVLD
      VAProfileVC1Advanced : VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointVLD
      VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
      VAProfileH264Main : VAEntrypointVLD
      VAProfileH264Main : VAEntrypointEncSlice
      VAProfileH264High : VAEntrypointVLD
      VAProfileH264High : VAEntrypointEncSlice
      VAProfileNone : VAEntrypointVideoProc

MPV will play a choppy video stream, however once open, will not close. Had to reboot to close the player.

You can exit mpv by pressing "q" - that one caught me as well.

Does totem work for you in an xorg session?

how do I enter an xorg session?

Logout. Then at the login screen click on the gear icon next to the Sign On button and select "Ubuntu on Xorg" and login. (the default selection "Ubuntu" uses Wayland now).

It's not absolutely critical to test this - I just thought it would be a useful data point to show we're both seeing the same problem with totem on Wayland. But, if it works, then it is a viable workaround until it gets fixed.

It will not work in either "Ubuntu" or "Ubuntu on Xorg" but will work when I load with Unity. That will have to be my back up until the bug is figured out.

Ernest, thanks for your testing. Two more questions:

(1) When you log into "Ubuntu on Xorg", can you please run this and send us the output?

  xrandr

Then verify again that totem doesn't work in that session.

(2) Does the situation improve after you do this?;

  sudo apt remove mesa-va-drivers

Removing the mesa-va-drivers works for me, so I can switch back to Wayland now instead of falling back to Xorg.

Thanks.

Screen 0: minimum 320 x 200, current 1366 x 768, maximum 16384 x 16384
eDP connected primary 1366x768+0+0 (normal left inverted right x axis y axis) 344mm x 194mm
   1366x768 60.00*+
   1280x720 59.97
   1152x768 59.95
   1024x768 59.95
   800x600 59.96
   848x480 59.94
   720x480 59.94
   640x480 59.94
HDMI-0 disconnected (normal left inverted right x axis y axis)
VGA-0 disconnected (normal left inverted right x axis y axis)

and yes, removing the mesa-va driver worked.

It is now working in the Default Ubuntu now as well with the driver gone.

Thanks Ernest. Did removing mesa-va-driver also fix the choppy mpv behaviour? You might also want to try this:

   mkdir ~/.config/mpv
   echo hwdec=no > ~/.config/mpv/mpv.conf

Kent: It sounds like your issue is just slightly different if "Ubuntu on Xorg" is working for you. You may want to consider opening a new bug as resolving Ernest's issue may not also solve yours.

it did. MPV is working as well now. Thank you.

did not need to run the mkdir commands.... Driver removal fixed all issues I was experiencing.

Indeed it looks like my issue is slightly different from both this and bug 1720820, but given we have a workaround I'm happy to wait until those are fixed and checking if they also fix my problem before raising yet another minor bug variant - unless there is something specific I can add that could be of assistance.

I'm going to group this with bug 1720820 just to keep us organized and on the same page.

If a fix for bug 1720820 arrives and this bug is not resolved then we can un-duplicate this one.