Bug 368232

Summary:	video players (e.g. mpv; mplayer) stuck/freeze after wake up from suspend to RAM
Product:	[Plasma] plasmashell	Reporter:	Florian <alfaflo>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	bshah, nate, plasma-bugs-null
Priority:	NOR
Version First Reported In:	5.7.3
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Florian 2016-09-04 09:07:24 UTC

plasma 5.7.3 and 5.7.4
openSUSE Leap 42.1
nvidia driver version 340.96 (9600m GT)

Watching videos (e.g. x264 with VDPAU) - mplayer and mpv works fine with hardware acceleration.
After resuming system from suspend, the video player make problems e.g. when switching to full screen or changing window size the video freezes, or disappears (sound is still played). Stopping and restarting the video starts playback again. Maximize player-window  is less problematic.
Also CPU usage is higher than expected (maybe VDPAU is not working after resume from suspend?!)

If I "kill" and restart plasmashell, the video player works fine again.
Kwin_x11 seems not to be involved (at least kill and restart has no effect).

Reproducible: Always

Steps to Reproduce:
1. suspend to RAM
2. wake up system
3. play video with hardware acceleration (x264 with mpv, mplayer, vlc)
4. change to fullscreen or change window size

Actual Results:  
Video window freezes or stuck (sound is still be played). This happens with mpv, mplayer and vlc (hardware accelerated VDPAU).

Expected Results:  
Smooth video playback :-)

openSUSE LEAP 42.1
plasma 5.7.4 from openSUSE kdeframeworks5 repo

Comment 1 Nate Graham 2021-03-10 00:15:34 UTC

This does not strike me as related to Plasma, but rather with the kernel or those apps themselves. However it's been quite a while; is it still happening with Plasma 5.21? Can you check? Thanks!

Comment 2 Bug Janitor Service 2021-03-25 04:33:40 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Florian 2021-03-25 07:18:41 UTC

Hello,
The problematic hardware does not exist anymore, so I can't check if the big still exists. Sorry...

For me it's OK to close the bug report.
Kind regards!

Comment 4 Nate Graham 2021-03-25 17:19:34 UTC

OK thanks. :)