Fixed
Status Update
Comments
dt...@chromium.org <dt...@chromium.org> #2
I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
sa...@chromium.org <sa...@chromium.org> #3
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
da...@chromium.org <da...@chromium.org> #4
me as well....
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
sw...@chromium.org <sw...@chromium.org> #5
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
sw...@chromium.org <sw...@chromium.org> #6
Having the same issue:
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
ri...@gmail.com <ri...@gmail.com> #7
same
[Deleted User] <[Deleted User]> #8
SAME ! - Google can't do sth working in 100 percent?
st...@chromium.org <st...@chromium.org> #9
same issue - Google Play services out of date. Requires 3159100 but found 3158130
bu...@chops-service-accounts.iam.gserviceaccount.com <bu...@chops-service-accounts.iam.gserviceaccount.com> #10
Having the same issure:
07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130
07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130
st...@chromium.org <st...@chromium.org> #11
API 18 (4.3) same issue
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130
is...@google.com <is...@google.com> #12
Same issue here.
Description
Steps to reproduce the problem:
1. On a recent Linux system, open any YouTube video and start playing
2. Execute `busctl --user get-property org.mpris.MediaPlayer2.chromium.instance1451275 /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2.Player CanControl CanPause` (busctl is a command provided by systemd).
What is the expected behavior?
The output should be "true" and "true" for the 2 properties. An explanation can be found in the fd.o specification.
What went wrong?
The output is "false" and "true" for the 2 properties respectively, which is against the fd.o standard[1]. It says "If CanControl is false, this property (CanPause) should also be false.". In this case, since the media player is perfectly controllable, CanControl should be set to "true".
[1]
Did this work before? N/A
Chrome version: 80.0.3987.106 Channel: n/a
OS Version: Arch Linux
Flash Version:
Looks like "CanControl" is set to false and never changed, although "CanPause" and other similar properties may be toggled later[2]. According to the standard, it should be "true" in the first place.
This is causing problems with MPRIS2 consumers, such as the media player applet on the Plasma desktop. media playback cannot be controlled by the applet, which is not ideal.
[2]