Bug 20930

Summary:	alsaplayer crashed
Product:	Mageia	Reporter:	peter lawford <petlaw726>
Component:	RPM Packages	Assignee:	Shlomi Fish <shlomif>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	alsaplayer-0.99.81-9.mga5	CVE:
Status comment:

Description peter lawford 2017-05-25 00:31:10 CEST

Description of problem:
if attempting to run alsaplayer:(an example)

[toto@mageia5_64 ~]$ alsaplayer Musique/M_ROSTROPOVITCH/haydn-cello-concertos-nos-1-2-mstislav-rostropovich/01-01-Cello_Concerto_No_1_in_C_Major_Hob_VIIb_1_I_Moderato_Cadenza_by_Britten-SMR.flac 
Erreur de segmentation



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


How reproducible: see above


Steps to Reproduce:see above
1.
2.
3.

Comment 1 peter lawford 2017-05-25 01:09:45 CEST

I have just uninstalled, and reinstalled the package alsaplayer-0.99.81-9.mga5,
and now it no longer works, but what it is displayed is different:

[toto@mageia5_64 ~]$ alsaplayer Musique/M_ROSTROPOVITCH/haydn-cello-concertos-nos-1-2-mstislav-rostropovich/01-01-Cello_Concerto_No_1_in_C_Major_Hob_VIIb_1_I_Moderato_Cadenza_by_Britten-SMR.flac 
CBSetcurrent: 1

(alsaplayer:16938): Gtk-CRITICAL **: IA__gtk_list_store_set_valist: assertion 'VALID_ITER (iter, list_store)' failed

using the gui doesn't work too

Comment 2 peter lawford 2017-05-25 01:28:24 CEST

with some others *.flac music files, I obtain the same phenomenon as describded by Jonas Thiem in bug #13317

Comment 3 Marja Van Waes 2017-05-28 06:54:45 CEST

Assigning to the registered maintainer.

Assignee: bugsquad => shlomif
CC: (none) => marja11

Comment 4 Marja Van Waes 2018-09-18 15:52:04 CEST

Hi Peter,


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

This bug was filed against Mageia 5. Did it 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 continued to get limited extended support since then, but that support has now ended, too.
As a result we are closing this bug report as OLD.

If you still see this issue in a newer Mageia version, then please reopen this report and say so.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

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

Comment 5 peter lawford 2018-09-18 23:09:57 CEST

(In reply to Marja Van Waes from comment #4)
> Hi Peter,
> 
> 
> Thank you for having taken the needed time to report this issue!
> 
> This bug was filed against Mageia 5. Did it 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 continued to get limited extended support since then, but that support
> has now ended, too.
> As a result we are closing this bug report as OLD.
> 
> If you still see this issue in a newer Mageia version, then please reopen
> this report and say so.
> 
> ==> If you didn't reset your password after February 2018, then you'll need
> to reset it here https://identity.mageia.org/forgot_password to be able to
> log in and comment in this report. <==

Hi Marja,
it's a long long long time I no longer interest to this bug, I have decided to use one another player (there are many) to play music, and I can't say if this bug is fixed or not, since I no longer use mageia5
I've just tested it now, it works only with CD-resolution pieces (44,1kHz 16 bits) but not with Hi-Res pieces (24 bits, 88kHz or more); then nothing has changed since mageia5