rhythmbox could not open resource for reading

The description makes it sound more like it is a possible issue with the rhythmbox database. Will convert to a question and give the answer that I believe should fix it. I was unable to reproduce the error after running two tests.

Please try to delete the file:

/home/<user>/.gnome2/rhythmbox/rhythmdb.xml

If that does not work I will convert this back to a bug.

That didn't solve the problem. As noted in the original report, when attempting to import files, I receive a "Could not open resource for reading" error. Deleting the library DB file and having to reimport everything simply reinforced that problem. Now I have zero files in my library, and an import error log full of "Could not open resource for reading" errors.

I have converted the bug back...

Can you try moving the files from the XP share to the local HD and then add those to the library.

I want to see if it is an issue with the file format or the XP Share.

I copied the folder to a local folder, successfully added the files to the library and played them. BTW - There has been no change on the WinXP side (other than the addition of these new files) - the only changes have been made on the Ubuntu/Rhythmbox side, with the version of Ubuntu that I'm running.

Here's info I also added to the bug:
Additional info: Because I have Music Player Preferences - Music - Music files are placed in: configured to smb://server/share, every time I open Rhythmbox, the mount is automatically added to my desktop. When I open that mount and right click on an MP3 file and choose "Play with Rhythmbox", it generates the following error in the Import Errors: "Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer." Since I had already reinstalled Rhythmbox, I went through Synaptic and chose reinstall on all the GStreamer packages. After rebooting, I have the same problem - no change.

pwhitted...

The information from the fact that they worked when copied locally and do not when on the XP share indicates that the issue is with your share (potentially with SAMBA) and not the file. I would lean away from Rhythmbox being the culprit.

I disagree with PrivateVoid; On client machine with Ubuntu 8.04 Rythmbox workes flawless with my Windows Server 2003 share. My second client machine with Ubuntu 8.10 Rythmbox can not read files from the same smb address. (Btw Amarok shows the same problems on my 8.10-machine, have not tested on the 8.04 yet)

Additional information if of any value:
On client machine with 8.04, in Amorok when adding media I can browse the network, this is not available on the 8.10 machine.
Both machines are running pure Ubuntu installations, Gnome GUI.

Landy88:

When I say there is a problem with the share I simply mean there is a problem with the Ubuntu 8.10 machine using the share. I did not mean to imply that the problem was in the W2K3 server. From the fact that you report that Amarok has issues in addition to Rhythmbox it would appear that the problem with using the share for music is not inside the specific music package itself.

I got around this by mounting the share with CIFS. Works very well and actually seems a bit faster.

Cool... glad you got it working.

i have the same issue... i have not been able to find any solution as of yet on the net.
this was working fine with ubuntu 7.10 - 8.06 (until some update). since then playing any mp3 files over ssh on rhythmbox is impossible and i get the following error message:
"Could not open resource for reading"

i also vaguely remembering getting a "Internal Gstreamer Error" when doing the above with ubuntu 8.06.

i have no problems listening to music over ssh using totem or vlc.

i also set up my server with a samba share, and again trying to listen to music over smb does not work using rhythmbox. it works however with totem and vlc.
i again get the same error message as stated above.
i started rhythmbox in debug mode, but i don't really get more infos out of it. i can attach the output if anybody would like to have a look...

Hi,

No idea why it works but look at the solution I posted for this here;

http://ubuntuforums.org/showthread.php?p=6688627#post6688627

Geoff

I have approximately 500 CDs on a Samba server. Running 7.10 all was well and I could play all of the files on the server. Starting with either 8.4 or 8.10 I was able to play fewer and fewer of the music files in Rhythmbox and received hundreds and hundreds of error messages "Could not open resource for reading" yet all files will play using Movie Player. The results are the same on each of 3 different Ubuntu desktops.

I setup a Mt-daapd daemon on the server with no change to playback capability in Rhythmbox. Additionally, a clean install of 9.4 results in no change to playback - the problem persists. The server is running a very lean 7.4 version. On a couple of windows machines (running Vista and W2k) there are no playback issues. I have not been able to narrow the problem yet to any other source but Rhythmbox.

I'd like to resolve this issue but have absolutely no idea how to proceed, the suggested solution on 6 Feb did not solve the problem.

I'm running the Ubuntu 9.10 Beta and this problem still exists.

I have put some effort into finding the reason why some people have this issue and others don't. I might have found it.
It seems that this problem only comes up when the share requires a username and password and is not available via the guest account.

When I use Nautilus -> Network -> My Server -> Share to "mount" the share and then go into Rhythmbox and use Music -> Import Folder to import a folder within that share it works.

When I use Nautilus -> File -> Connect to Server -> enter my data including a custom username and password there to "mount" the share and then use the same way in Rhythmbox described above to add my music it fails with the message given in the original post. (In Nautilus browsing and copying music files works fine though!)

In the Error Log of Rhythmbox it tries to open smb://user@servername/sharename with no password behind the user. I guess that this is somehow the root of the problem.

Using the gnome vfs folder /home/user/.gvfs works every time, as another user here mentioned - however I consider this a dirty hack and not the way it's meant to be. The problem might be in Rhythmbox or in Gnome VFS or somewhere else, I can't really tell.

It is real though, and it has existed since 8.10 as these posts seem to prove. Since this could be a real turn down for potential Ubuntu triers I would suggest to give this issue more thought than has been in the past.

In my previous comment part of the info was wrong:

The .gvfs solution also does not work when using a username and password.
Ryhthmbox resolves those files to the same smb://user@host/share scheme and thus can't open them.

Excuse the spam, but I have just found out additional stuff:

If you set up your server in a way that it actively refuses guest account logins, Nautilus asks you to supply a username and password when going the usual Network route (browsing for your server instead of using the connect to server menu).

When you supply the username and password that way, Rhythmbox works fine.

In other words it only seems to fail when using the File -> Connect to Server method instead of browsing for your server. (No matter if using a custom username / password or not)

Can we convert this back to a bug report? I think it's pretty clear now that this is a bug.

Stuart and everyone else reading:

There is already a bug report about this issue.

https://bugs.launchpad.net/rhythmbox/+bug/273294

Regards,
Lee