Bug 143859

Summary:	rhythmbox - cannot get anything on a new playlist
Product:	[Fedora] Fedora	Reporter:	Michal Jaegermann <michal>
Component:	rhythmbox	Assignee:	John (J5) Palmieri <johnp>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3	CC:	jkeck, mattdm
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:	2008-02-03 20:08:28 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 Michal Jaegermann 2004-12-30 06:10:04 UTC

Description of problem:

Regardless of all other problems if I open a new playlist,
with ctrl-N or from the menu, then all attempts to add files
by "Import Folder" (are we in M$-Windows?) end up with
"O songs, 0 minutes, 0 bytes".  If that thing will not croak,
which is likely, then new files end up in the main browser window.

The only way I managed to get some files on such playlist was
to copy and paste things from the main browser window.  But if
I will try to save such list to a file and load that file later
then I am indeed getting a new, unnamed, playlist but again with
"O songs, 0 minutes, 0 bytes".

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

Comment 1 Matthew Miller 2006-07-10 22:46:41 UTC

Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.

Thank you!

Comment 2 petrosyan 2008-02-03 20:08:28 UTC

The information we've requested above is required in order
to review this problem report further and diagnose/fix the
issue if it is still present.  Since there haven't been any
updates to the report in quite a long time now after we've
requested additional information, we're assuming the problem
is either no longer present in our current OS release, or
that there is no longer any interest in tracking the problem.

Setting status to "INSUFFICIENT_DATA", however if you still
experience this problem after updating to our latest Fedora
release and are still interested in Red Hat tracking
the issue, and assisting in troubleshooting the problem,
please feel free to provide the information requested above,
and reopen the report.

Thank you in advance.