rhythmbox could not open resource for reading

Bug #303604 reported by pwhitted
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

I recently tried to use Rhythmbox to play music files that are on a WinXP share, that had previously been added to the Rhythmbox library. Each file that I attempt to play generates an "unknown error" message. If I try to "Import from a folder", I can browse to the folder, but then each file generates the "Could not open resource for reading" error. I can browse to WinXP share, successfully mount it, and I can double-click files and they will play in the Totem Movie Player. I was able to play these MP3 files before. This is the first time I've tried playing them since upgrading from Ubuntu 8.04 to 8.10. I have already gone back into Synaptic and had it reinstall Rhythmbox, but even after restarting I still get these errors.

Description: Ubuntu 8.10, Release: 8.10
Installed Package Version: 0.11.6svn20081008-0ubuntu4.2 (matches Latest Version in Synaptic)

Revision history for this message
Charles Profitt (cprofitt) wrote :

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.

Changed in rhythmbox:
status: New → Invalid
Revision history for this message
Charles Profitt (cprofitt) wrote :

The suggested fix did not solve the issue. I still have not been able to confirm.

Revision history for this message
pwhitted (pat-whitted) wrote :

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.

Revision history for this message
Charles Profitt (cprofitt) wrote :

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.

Revision history for this message
Charles Profitt (cprofitt) wrote :

based on the information you put in the question about the file working if you copied them locally... the issue appears to be with your share (potentially with SAMBA) and not the file. I would lean away from Rhythmbox being the culprit.

Revision history for this message
Charles Profitt (cprofitt) wrote :

changed this to incomplete because it appears the bug is with the share or SAMBA and not Rhythmbox.

Changed in rhythmbox:
status: Invalid → Incomplete
Revision history for this message
pwhitted (pat-whitted) wrote :

Help me understand. As you can see by the other notes I've added, Rhythmbox is reporting this as an issue with Rythmbox or GStream. I've made sure both apps are up to date. Other apps using the same mount have no problem. I've even verified that I can write to the mount, not just read. How is this just a Samba problem? How do I resolve it?

Revision history for this message
Charles Profitt (cprofitt) wrote :

Rhythmbox may be reporting that error because that is the fork that application has taken.

You might want to run Rhythm box from a terminal to see if anything interesting is listed.

you can also run it from the terminal with the following command:

rhythmbox -d

Which will produce a lot of output... that might help narrow things down.

------------
I am making a 'leap' to Samba / XP Share issue because of the fact that the same music working when you move the file locally. IMHO that eliminates the codecs. It may still be a Rhythmbox issue, but it would be with the share more than the codec involved in playing the file.

Revision history for this message
pwhitted (pat-whitted) wrote :

I followed your suggestion. I am attaching the output of the terminal screen - had to manually copy it. Please provide steps to output directly to a file. I'm an Ubuntu noob - the typical DOS style redirect to a file didn't result in any contents. Thanks! - Pat

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in rhythmbox:
assignee: nobody → desktop-bugs
importance: Undecided → Low
status: Incomplete → Invalid
Revision history for this message
M (maxim-collin) wrote :

the same bug applies to when i try to copy files from my HD via rhythmbox to my samsung galaxy s6... i can read acces and delete files with file manager but rhythmbox wont tranfer songs nor podcast....

Revision history for this message
M (maxim-collin) wrote :

I tryied with terminal and the -d suffix and i got this in my log:

(12:37:24) [0x214d410] [rb_track_transfer_batch_check_profiles] rb-track-transfer-batch.c:316: copying entry file:///home/gmax/Music/electro/Pegboard%20Nerds/Pegboard%20Nerds%20-%20Self%20Destruct.mp3
(12:37:24) [0x214d410] [start_next] rb-track-transfer-batch.c:628: 1 entries remain in the batch
(12:37:24) [0x214d410] [start_next] rb-track-transfer-batch.c:644: attempting to transfer file:///home/gmax/Music/electro/Pegboard%20Nerds/Pegboard%20Nerds%20-%20Self%20Destruct.mp3
(12:37:24) [0x214d410] [select_profile_for_entry] rb-track-transfer-batch.c:247: can use lossy encoding audio/x-aac
(12:37:24) [0x214d410] [select_profile_for_entry] rb-track-transfer-batch.c:243: can use preferred encoding audio/x-vorbis
(12:37:24) [0x214d410] [select_profile_for_entry] rb-track-transfer-batch.c:238: can use source encoding audio/mpeg
(12:37:24) [0x214d410] [select_profile_for_entry] rb-track-transfer-batch.c:250: can use lossless encoding audio/x-flac
(12:37:24) [0x214d410] [rb_transfer_target_build_dest_uri] rb-transfer-target.c:101: built dest uri for media type 'audio/mpeg', extension 'mp3': mtp://[usb:001,004]/Phone/Music/Pegboard%20Nerds/www.downsong.com/00%20-%20Self%20Destruct.mp3.mp3
(12:37:24) [0x214d410] [attach_output_pipeline] rb-encoder-gst.c:500: attempting to open output file mtp://[usb:001,004]/Phone/Music/Pegboard%20Nerds/www.downsong.com/00%20-%20Self%20Destruct.mp3.mp3
(12:37:24) [0x214d410] [attach_output_pipeline] rb-encoder-gst.c:509: giostreamsink can't write to mtp://[usb:001,004]/Phone/Music/Pegboard%20Nerds/www.downsong.com/00%20-%20Self%20Destruct.mp3.mp3
(12:37:24) [0x214d410] [sync_window_settings] rb-shell.c:1918: paned position 160
(12:37:24) [0x214d410] [sync_window_settings] rb-shell.c:1925: right_paned position 400
(12:37:24) [0x214d410] [sync_window_settings] rb-shell.c:1932: sidebar paned position 300
(12:37:24) [0x214d410] [bus_watch_cb] rb-encoder-gst.c:186: received error gstgiosink.c(299): gst_gio_sink_get_stream (): /GstPipeline:pipeline/GstGioSink:sink:
Could not open location mtp://[usb:001,004]/Phone/Music/Pegboard%20Nerds/www.downsong.com/00%20-%20Self%20Destruct.mp3.mp3 for writing: Operation unsupported
(12:37:24) [0x214d410] [rb_encoder_gst_emit_completed] rb-encoder-gst.c:139: couldn't get size of destination mtp://[usb:001,004]/Phone/Music/Pegboard%20Nerds/www.downsong.com/00%20-%20Self%20Destruct.mp3.mp3: File not found
(12:37:24) [0x214d410] [encoder_completed_cb] rb-track-transfer-batch.c:561: encoder finished (error: Could not open resource for writing.)
(12:37:24) [0x214d410] [track_done_cb] rb-transfer-target.c:366: fatal transfer error: Could not open resource for writing.
(12:37:24) [0x214d410] [_rb_track_transfer_batch_cancel] rb-track-transfer-batch.c:445: batch being cancelled
 im not a programing bomb but whats going on with the **.mp3.mp3 ?

Revision history for this message
moragos (moragos) wrote :

still happening using Galaxy 8, Ubuntu 17.10 and rhythmbox 3.4.1

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.