Bug 29690 - xine exits silently - BadAtom (invalid Atom parameter)
Summary: xine exits silently - BadAtom (invalid Atom parameter)
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2021-11-23 01:52 CET by Ben McMonagle
Modified: 2021-11-26 09:05 CET (History)
1 user (show)

See Also:
Source RPM: xine-ui
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Ben McMonagle 2021-11-23 01:52:19 CET 
Description of problem: attempting to play an .mp4 file by choosing xine fails as xine exits silently.

attempting to invoke xine from terminal results;

$ xine
This is xine (X11 gui) - a free video player v0.10.1.
(c) 2000-2019 The xine Team.
X Error of failed request:  BadAtom (invalid Atom parameter)
  Major opcode of failed request:  18 (X_ChangeProperty)
  Atom id in failed request:  0x0
  Serial number of failed request:  776
  Current serial number in output stream:  779

plasma DE on GDM 

Version-Release number of selected component (if applicable):


How reproducible:
always

Steps to Reproduce:
1.update to latest cauldron (22/11/2021)
2.invoke xine from menu launcher or terminal
3.
Comment 1 Marja Van Waes 2021-11-23 22:59:55 CET 
Couldn't reproduce this in Plasma on LightDM, haven't tried with GDM

I installed xine-ui-0.99.12-3.mga8.tainted.x86_64.rpm and its dependencies.
Starting it from CLI, it complained about missing libvdpau_va_gl.so
So I installed lib64vdpau-va-gl1-0.4.2-4.mga8.x86_64.rpm

Then started an mp4 file which played fine.

Ben, when did it last work?

What does "rpm -qa | grep xine" return?

CC: (none) => marja11
Keywords: (none) => NEEDINFO
Summary: xine exits silently => xine exits silently - BadAtom (invalid Atom parameter)
Source RPM: (none) => xine-ui

Comment 2 Ben McMonagle 2021-11-26 09:05:54 CET 
after another update and reboot it is now working

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.