Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#64845 - [kwin] No full-screen video on YouTube

Attached to Project: Arch Linux
Opened by Andrej Podzimek (andrej) - Sunday, 15 December 2019, 01:59 GMT
Last edited by Antonio Rojas (arojas) - Friday, 21 February 2020, 22:42 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Antonio Rojas (arojas)
Felix Yan (felixonmars)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 5
Private No

Details

Description:
Full-screen mode doesn't work on YouTube. Instead of going full-screen, the video is displayed in a tiny area in the top left corner. What I mean by tiny: I'm using two 5K monitors (5120x2880) and the size of the video is ~720p or the like. I've tried this with 5K videos from YouTube and it failed the same way; it ends up in a tiny frame regardless the original resolution.

Firefox works fine and displays full-screen videos just fine.
Chromium used to display full-screen videos without any issues until a recent update.
Chrome from AUR is also affected the same way as chromium; the same tiny frame appears instead of a full-screen video.
Resetting chrome://flags to defaults doesn't help.

Additional info:
* package version(s)
firefox 71.0-1 [works]
chromium 79.0.3945.79-1 [doesn't work]
google-chrome 79.0.3945.79-1 [doesn't work]
linux 5.4.3.arch1-1
nvidia 440.44-2
xorg-server 1.20.6-1

* config and/or log files etc.
N/A

Here's my monitor configuration (relevant lines from xrandr) (two DP ports per monitor, two 5120x2880 monitors):
DP-0 connected 2560x2880+5120+0 (normal left inverted right x axis y axis) 299mm x 336mm
2560x2880 59.98*+
DP-2 connected 2560x2880+7680+0 (normal left inverted right x axis y axis) 1mm x 1mm
2560x2880 59.98*
DP-4 connected primary 2560x2880+0+0 (normal left inverted right x axis y axis) 299mm x 336mm
2560x2880 59.98*+
DP-6 connected 2560x2880+2560+0 (normal left inverted right x axis y axis) 1mm x 1mm
2560x2880 59.98*

* link to upstream bug report, if any
N/A

Steps to reproduce:
Try to maximize a YouTube video to full-screen.
This task depends upon

Closed by  Antonio Rojas (arojas)
Friday, 21 February 2020, 22:42 GMT
Reason for closing:  Upstream
Additional comments about closing:  Not a packaging issue. Please report upstream
Comment by Andrej Podzimek (andrej) - Sunday, 15 December 2019, 21:04 GMT
Update:

1. This affects *any* video in Chromium and Chrome, not just YouTube.
2. Tried to install `libva-vdpau-driver-chromium` instead of `libva-vdpau-driver`, but it didn't help at all.
Comment by Justin Capella (justincapella) - Tuesday, 17 December 2019, 03:55 GMT
01:00.0 3D controller: NVIDIA Corporation GM107M [GeForce GTX 950M] (rev a2)
glibc 2.30-3
chromium 79.0.3945.79-1


I am able to full screen on my single 4k display.

That being said, I've had segfaults in other gtk applications when they hand off to wayland from either drawing a frame or resizing a window. And the screen "zoom" setting seems to really mess up full screen calculation, can you maybe check the chromium console for warnings (

#0 0x00007fd085d1be94 wl_proxy_marshal_constructor (libwayland-client.so.0 + 0x5e94)
#1 0x00007fd087330f50 n/a (libgdk-3.so.0 + 0x62f50)
#2 0x00007fd087326bbd n/a (libgdk-3.so.0 + 0x58bbd)
#3 0x00007fd087326c29 n/a (libgdk-3.so.0 + 0x58c29)
#4 0x00007fd08735175e n/a (libgdk-3.so.0 + 0x8375e)
#5 0x00007fd087351bfd gdk_window_begin_draw_frame (libgdk-3.so.0 + 0x83bfd)
#6 0x00007fd0874f4484 n/a (libgtk-3.so.0 + 0x12d484)
#7 0x00007fd087650e4a gtk_main_do_event (libgtk-3.so.0 + 0x289e4a)



Have you tried a single display as a test?
Comment by Dinko Ninev (dinko) - Tuesday, 17 December 2019, 10:28 GMT
Have the same problem on a laptop connected to an external 1080p monitor.

Running chromium with `--disable-gpu` flag "fixes" the problem.

This is the output to the console without the flag

[2952:2952:1217/122745.629011:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process.
[2952:2952:1217/122745.904327:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command

Comment by Andrej Podzimek (andrej) - Thursday, 19 December 2019, 01:20 GMT
In my case, `--disable-gpu` doesn't change anything. Everything is disabled in `chrome://gpu`, but the video problem is *exactly* the same, a tiny window in the top left corner.

(This is on X11; I don't use Wayland, simply because it doesn't work (and never has). It can't handle >1 monitor properly and barely works on drivers other than Intel, open-source AMD or Nouveau, so there's no intersection with what I'm using.)
Comment by Andrej Podzimek (andrej) - Thursday, 19 December 2019, 01:24 GMT
BTW I can also see the line reported above:

[522062:522062:1219/022117.771255:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process.

(But I don't get the second error message. And `--disable-gpu` doesn't solve the video problem in my case; everything stays the same, except for lots of red in chrome://gpu and super-choppy video.)
Comment by Dinko Ninev (dinko) - Thursday, 19 December 2019, 15:34 GMT
Update:

For me full screen works only if I press the button while chromium is NOT maximized.

chromium 79.0.3945.88-1
Comment by Valentin (vially) - Thursday, 19 December 2019, 20:00 GMT
I have the same problem on three 4K monitors with an AMD Vega 64 GPU and it happens while opening any page in fullscreen (F11), not just with videos. I have tested it in sway (using XWayland) and in i3 and the bug is present in both. The workaround suggested by dinko (go full-screen from non-maximized window) also works for me.

Does anyone know if it's specific to archlinux or is it an upstream bug?
Comment by Andrej Podzimek (andrej) - Thursday, 19 December 2019, 20:22 GMT
In my case the workaround succeeds in even more cases than described above! In KDE I have a keyboard shortcut to hide decorations of a particular window (because why have decorations on a maximized window and/or when one doesn't want/need them). Well, strangely enough:

* maximized window with window decorations hidden: FAILS
* maximized window with window decorations shown: WORKS (Heck! Why hadn't I tried this?!)
* non-maximized window with window decorations hidden: WORKS (Surprising!)
* non-maximized window with window decorations shown: WORKS

This is on KDE and X.org (because Wayland has never worked on my systems).

So this seems to have *something* in comon with KWin, I guess. But what? It's definitely not purely KWin-specific when people see the issue on other WMs / environments.

I have ~all desktop gimmicks and animations (and compositing, of course) switched on. (It's a Quadro P5000, so two 5K monitors are in the "meh" zone for this GPU.)
Comment by Dinko Ninev (dinko) - Thursday, 19 December 2019, 22:13 GMT
Another update:

If I disable Auto-Hide on my plasma panel the problem disappears. This seams like a plasma bug.
Comment by Antony Williams (syxbit) - Tuesday, 24 December 2019, 20:09 GMT
Hardware: Nvidia binary driver, dual monitors
software: Gnome, xserver
Same issue. I can make YouTube fullscreen on monitor1, but not on monitor2.

Loading...