Bug 494315

Summary:	Sound Juicer crashes if no MusicBrainz disc ID match
Product:	[Fedora] Fedora	Reporter:	carl <stillcdg>
Component:	sound-juicer	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	rawhide	CC:	bnocera, mclasen
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:	2009-04-14 13:41:38 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description carl 2009-04-06 11:25:23 UTC

Description of problem: Sound Juicer crashes when certain CDs are present/inserted. Seems to be CDs whose disc ID is not in MusicBrainz


Version-Release number of selected component (if applicable): 2.26.0-1.fc11


How reproducible: Run Sound Juicer with a CD whose disc ID is not in MusicBrainz


Steps to Reproduce:
1. Insert a CD whose disc ID is not in MusicBrainz
2. Start Sound Juicer, either from the choose action dialog or menu or command line
  
Actual results: displays a blank screen briefly, then terminates


Expected results: displays information from another source, or a list of untitled tracks. Possibly with a message saying the album could not be found in MusicBrainz.


Additional info: Error also occurs if Sound Juicer is running and the disc is inserted.

Once the album is added to MusicBrainz by another means (eg Picard) Sound Juicer loads with no problems.

When run from the command line, the final output is:

** (sound-juicer:1580): CRITICAL **: album_details_free: assertion `album != NULL' failed

Comment 1 Matthias Clasen 2009-04-14 02:25:51 UTC

Can you still reproduce with 2.26.1 ? 
It has a fix for http://bugzilla.gnome.org/show_bug.cgi?id=575820 which looks very similar.

Comment 2 Bastien Nocera 2009-04-14 13:41:38 UTC

I'm pretty certain this is fixed by the latest release. Reopen if not.