Bug 1297192

Summary:	category strage: qmmp crashes if started for a .m4a via nautilus , but from bash it works
Product:	[Fedora] Fedora	Reporter:	customercare
Component:	qmmp	Assignee:	Karel Volný <kvolny>
Status:	CLOSED CANTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	23	CC:	kvolny
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-01-11 14:33:20 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description customercare 2016-01-10 12:10:15 UTC

Description of problem:

qmmp crashes if started for a .m4a via nautilus , but from bash it works.

if started via nautilus, a window comes up and vanishes immediatly ( i guess a crash ).

if started for the same m4a file from bash, qmmp ignores all config options, i.e. the skin theme, and plays it back, with specurumanalyzer working and volume controls etc.


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

  qmmp.x86_64 0.9.5-1.fc23                                                      
  qmmp-plugin-pack.x86_64 0.9.3-1.fc23                                          
  qmmp-plugins-freeworld.x86_64 0.9.5-1.fc23      


How reproducible:

100% 

Steps to Reproduce:
1. go to youtube.com
2. download an m4a file with media type AAC
3. try to use nautilus on it after you had made qmmp the default player for that type of file ( "open with" in the options menu)

Actual results:

crash - no playback nor a gui window

Expected results:

playback as in fedora 21, where the same procedure worked flawless.

Additional info:

Comment 1 Karel Volný 2016-01-11 14:33:20 UTC

thanks for the report

however, the package qmmp-plugins-freeworld which includes the AAC plugin isn't part of Fedora - please follow up in Bugzilla instance associated with the repository that includes the package (I've copied the report already, but I cannot include your e-mail address in CC as it isn't registered there)