Bug 22365

Summary:	mpv picture turns pink, upstream says this mpv version is no longer supported.
Product:	Mageia	Reporter:	Bunk Bunk <soccerhub>
Component:	RPM Packages	Assignee:	José Jorge <lists.jjorge>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	lists.jjorge, marja11
Version:	6
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	mpv-0.25.0-2.mga6	CVE:
Status comment:

Description Bunk Bunk 2018-01-09 20:00:58 CET

Description of problem:

MPV picture turns pink. 

MPV people said, 0.25 is outdated and they don´t support anymore. Should be at least 0.27

Comment 1 Bunk Bunk 2018-01-09 20:01:55 CET

Picture example 
http://tinyimg.io/i/FMl0tQG.png

Marja Van Waes 2018-01-10 09:26:30 CET

Source RPM: 0.25.0-2.mga6 => mpv-0.25.0-2.mga6
Summary: mpv picture => mpv picture turns pink, upstream says this mpv version is no longer supported.
CC: (none) => marja11
Assignee: bugsquad => lists.jjorge

Comment 2 José Jorge 2018-01-20 17:08:02 CET

I have submitted to updates_testing mpv version 0.27. Please ensure it fixes your problem.

I have also noticed version 0.25 segfaults when trying to play a DVD with "mpv dvd://" so I hope it will also fix that.

Status: NEW => ASSIGNED

Comment 3 José Jorge 2018-01-20 19:13:49 CET

If 0.27 does not fix this bug for you, I think it may be a bug in hardware acceleration drivers : we default to enable them in mageia's mpv as it is it's main advantage over other players.

To disable them, launch with :

mpv -vo=opengl, -hwdec=no

Comment 4 Bunk Bunk 2018-01-21 19:28:27 CET

(In reply to José Jorge from comment #2)
> I have submitted to updates_testing mpv version 0.27. Please ensure it fixes
> your problem.
> 
> I have also noticed version 0.25 segfaults when trying to play a DVD with
> "mpv dvd://" so I hope it will also fix that.

---
Ugh. Did not solve. Shredded style, icons and font. Trying variant II

José Jorge 2018-01-21 20:13:23 CET

CC: (none) => lists.jjorge

Comment 5 Bunk Bunk 2018-01-27 14:07:35 CET

OK, fixed now. Which package did it ?

Comment 6 José Jorge 2018-01-27 16:14:42 CET

Well, only you can say if it was the update to 0.27 that fixed it? Anyway, closing.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED