Bug 819055

Summary:	Rhythmbox misbehaves if album is not in database
Product:	Red Hat Enterprise Linux 6	Reporter:	o.h.weiergraeber
Component:	rhythmbox	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED WONTFIX	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2	CC:	tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-06 11:29:17 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:
Embargoed:

Description o.h.weiergraeber 2012-05-04 17:05:00 UTC

Description of problem:
If Rhythmbox opens a newly inserted CD, it first displays tracks with a generic name (track xyz...). It then automatically tries to find the album in the MusicBrainz database.
If this lookup fails (i.e., the album is not (yet) in the database), the track list immediately disappears! At this point the user is not able to do anything with these tracks (in particular playing them) since there is nothing to select.
This means that the program is completely useless if a CD is not found in the database!


Version-Release number of selected component (if applicable):
rhythmbox-0.12.8-1.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Insert CD which is not in MusicBrainz database
2. Open Rhythmbox
  
Actual results:
No tracks listed after database lookup.

Expected results:
Tracks should continue to be displayed with generic names.

Additional info:

Comment 2 RHEL Program Management 2012-07-10 08:46:15 UTC

This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.

Comment 3 RHEL Program Management 2012-07-11 01:51:32 UTC

This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.

Comment 4 RHEL Program Management 2012-09-07 05:37:46 UTC

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unable to address this
request at this time.

Red Hat invites you to ask your support representative to
propose this request, if appropriate, in the next release of
Red Hat Enterprise Linux.

Comment 5 Jan Kurik 2017-12-06 11:29:17 UTC

Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.

The official life cycle policy can be reviewed here:

http://redhat.com/rhel/lifecycle

This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:

https://access.redhat.com/