Since yesterday, both with official VideoLan and Packman packages, VLC is not able to show the video in fullscreen mode anymore. It only shows a quarter of the video (see attachment)
Furthermore, it does not respond to the "f" shortcut and I lose the mouse cursor when I move it insight the video area.
I have tried some other video output plugins (e.g., openGL) but it does not fix that behavior. Xine works well, but I do not know how many (video) dependencies it has in common with VLC.
How can I run a better diagnostic? What information do you need? I am running openSUSE Tumbleweed with all packages updated yesterday.
Edited
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
If it broke even distro packages, then it's most likely a bug in whatever ELSE you changed yesterday. Without further details, there is pretty much nothing we can do here anyhow.
Well, I do think it is videolan related because when I install the beta packages (vlc-beta-3.0.0-2015021301.14.i586.rpm) it works fine. And when I downgrade to stable again, the bug re-appears. The it seems pretty linked to vlc since the only packages that I install are the vlc ones:
Broken by 37f326297d45564298a2c8cb1958a81b858de57c
71df75966db5f51c66bff1c436dd1cb5a895b51b is half-the-fix, but not more.
Moreover, with Q5.5, you are no longer able to simply "double click" to get the window to fullscreen, for example.
The commit at fault is 53d289ec4c0f512a3475da4bbf1f940cd6838ace ("xcb: Use
XIGrabDevice instead of xcb_grab_pointer with XI 2.2").
A quick workaround is to set the env var QT_XCB_NO_XI2_MOUSE to 1 and all is
back to normal...
Short story: don't use Qt5.5
Jean-Baptiste Kempfchanged title from Fullscreen broken on Linux: shows only quarter of image to Qt5.5: Fullscreen broken on Linux, shows only quarter of image
changed title from Fullscreen broken on Linux: shows only quarter of image to Qt5.5: Fullscreen broken on Linux, shows only quarter of image
0x1000017 is the central stacked widget (stackedWidgetC).
0x10000b4 is the video widget.
The video widget horizontal layout is a client side object without server handle.
0x1000128 is the "stable" widget within the video widget.
0x1400000 is the video output window handle (using !XVideo here). Note the different X11 client ID, as the video output plugin has its own XCB connection.
(You can add some debug to check the winId() properties.)
At that point, the last requested resize was 853x480. For some reason, the video widget is not updated, even though both its parent and child are resized correctly. I can't think of anything, this looks like a Qt bug to me.
Screenshot of fullscreen issue
attachment:vlcdd.png
Replying to [comment:8 courmisch]:
The problem is not specific to fullscreen mode. It's easily reproducible in windowed mode too (for me anyway).
That is also confusion in Attachment - maybe to reporter "fullscreen" is entire video area when max window?
Rémi Denis-Courmontchanged title from Qt5.5: Fullscreen broken on Linux, shows only quarter of image to Qt5.5: X11 video window broken, cropped
changed title from Qt5.5: Fullscreen broken on Linux, shows only quarter of image to Qt5.5: X11 video window broken, cropped
the video size is indeed the initial window size (when I maximize, it's limited to that initial size, when I reduce the window size, it scales down the video and scales up again upon increasing the window size until the point of initial window size)
the first screenshot is maximized window. I will now attach a fullscreen screenshot which is actually very weird (toolbars remain visible)
this bug does not occur in VLC beta (3.x), although it uses the same shared Qt5.5. Furthermore, openSUSE has been shipping Qt5.5 which should be considered stable
as for the following aggressive comment, I do try to describe best the different elements that broke together, as they might be interrelated. I do not submit several bugs in the same report, I am just trying to make a good diagnosis to determine the right root cause (bug) to report.
For the umpteenth time, DO NOT MIX MULTIPLE BUGS IN THE SAME REPORT!!!