Bug 16358

Summary:	vdr-sxfe crashes when --hud is enabled
Product:	Mageia	Reporter:	Herbert Poetzl <herbert>
Component:	RPM Packages	Assignee:	All Packagers <pkg-bugs>
Status:	RESOLVED OLD	QA Contact:
Severity:	critical
Priority:	Normal	CC:	anssi.hannula, marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	vdr-plugin-xineliboutput-1.1.0-7.mga5.src.rpm	CVE:
Status comment:

Description Herbert Poetzl 2015-07-12 17:27:46 CEST

Description of problem:
when using the --hud option, vdr-sxfe crashes as soon as the hud gets displayed with:

X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  130 (MIT-SHM)
  Minor opcode of failed request:  3 (X_ShmPutImage)
  Value in failed request:  0x730
  Serial number of failed request:  504
  Current serial number in output stream:  507

or
X Error of failed request:  0
  Major opcode of failed request:  156 (GLX)
  Minor opcode of failed request:  26 (X_GLXMakeContextCurrent)
  Serial number of failed request:  314
  Current serial number in output stream:  314

or
X Error of failed request:  BadWindow (invalid Window parameter)
  Major opcode of failed request:  3 (X_GetWindowAttributes)
  Resource id in failed request:  0x40000c
  Serial number of failed request:  182
  Current serial number in output stream:  183


Version-Release number of selected component (if applicable):
vdr-sxfe 1.1.0  (build with xine-lib 1.2.6, using xine-lib 1.2.6)

How reproducible:
Always

Steps to Reproduce:
1. vdr-sxfe --hud
2. activate OSD (e.g. mute/unmute or menu)
3.



Reproducible: 

Steps to Reproduce:

Comment 1 Samuel Verschelde 2016-11-01 13:45:42 CET

Assigning to all packagers collectively since the maintainer Anssi is currently inactive.

CC: (none) => anssi.hannula
Assignee: bugsquad => pkg-bugs

Comment 2 Marja Van Waes 2018-05-03 08:19:14 CEST

Hi Herbert,


Thank you for having taken the needed time to report this issue!

Did this bug get fixed? If so, please change its status to RESOLVED - FIXED

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, because we are waiting for a big Plasma5 update in Mageia 6, that'll fix many of the Mageia 5 => 6 upgrade issues.

If you haven't seen that this bug got fixed, then please check whether this bug still exists in Mageia 6. If it does, then please change the Version (near the top, at the left) to "6". If you know it exists in Cauldron, then change Version to Cauldron. If you see it in both Cauldron and Mageia 6, then please set Version to Cauldron and add MGA6TOO on the Whiteboard.

Thanks,
Marja

CC: (none) => marja11

Comment 3 Marja Van Waes 2018-10-07 16:33:53 CEST

No reply, so closing as OLD since Mageia 5 is no longer maintained.

Status: NEW => RESOLVED
Resolution: (none) => OLD