Bug 1043139

Summary:	Rhythmbox doesn't allow adding files from network
Product:	[Fedora] Fedora	Reporter:	Rolle <rolle.hoffmann>
Component:	rhythmbox	Assignee:	Bastien Nocera <bnocera>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	20	CC:	bnocera
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-06-29 13:30:59 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 Rolle 2013-12-14 04:01:54 UTC

Description of problem:
When I try to add some file there is:
1) no working drag'n'drop support
2) when I try to "add  music" from the menu and a file/dir-dialog appears I can go to a server-share, but only to the first hierarchy.level. When I go in that directory rhythmbox maybe tries to analyze that directory? It didn't get into this hierarchy-level and didn't let me choose the next deeper hierarchy-level.

Version-Release number of selected component (if applicable):
Fedora 20 Beta, Rhythmbox 3.0

How reproducible:
100%

Steps to Reproduce:
1. Start Rhythmbox
2. Try to add a song per drag'n'drop from a network share.
3. Try to add a song/directory from a netwrok share with the menu command "Add music"

Actual results:
2.) Nothing happens, no crash, no adding the song to rhythmbox
3.) When I selected the server and then go deeper in the hierarchy-level (go into a subdirectory) -> Rhythmbox tries to analyze(?) that file or directory -> but nothing more happens

Expected results:
2.) Drag'n' drop with files/directories from a network shar should work
3.) Adding files/directory from the menu command "add music" let me choose the right direcroy on a server and then add the music files to rhythmbox. 


Additional info:

Comment 1 Fedora End Of Life 2015-05-29 09:59:20 UTC

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2015-06-29 13:30:59 UTC

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.