After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 773704 - Extracting already extracted track from CD fails with "Could not open resource for writing"
Extracting already extracted track from CD fails with "Could not open resourc...
Product: rhythmbox
Classification: Other
Component: Removable Media
Other Linux
: Normal normal
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Reported: 2016-10-30 17:31 UTC by gnome.vrb
Modified: 2018-05-24 19:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description gnome.vrb 2016-10-30 17:31:49 UTC
Steps to reproduce:

1. Select any preferred audio format. 
2. Extract a track ( say "track1" ) from Audio CD.
3. After 2 completes, repeat 2.
4. Expected a "Do you want to overwrite" dialog. But, rhythmbox displays a "Could not open resource for writing" dialog.

This is not reproducible in 3.4.1. Seems to be introduced after that.

Relevant log:

(22:54:21) [0x55fa0e55a130] [transcode_track] rb-encoder-gst.c:464: transcoding to profile mp3
(22:54:22) [0x55fa0e55a130] [bus_watch_cb] rb-encoder-gst.c:172: received error gstgiobasesink.c(113): gst_gio_base_sink_start (): /GstPipeline:pipeline/GstGioStreamSink:giostreamsink6:
No output stream provided by subclass
(22:54:22) [0x55fa0e55a130] [encoder_completed_cb] rb-track-transfer-batch.c:564: encoder finished (error: Could not open resource for writing.)
(22:54:22) [0x55fa0e55a130] [track_done_cb] rb-library-source.c:1195: fatal transfer error: Could not open resource for writing.
(22:54:22) [0x55fa0e55a130] [_rb_track_transfer_batch_cancel] rb-track-transfer-batch.c:448: batch being cancelled
Comment 1 GNOME Infrastructure Team 2018-05-24 19:18:00 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: