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 619711 - Brasero doesn't burn sftp/smb files
Brasero doesn't burn sftp/smb files
Status: RESOLVED OBSOLETE
Product: brasero
Classification: Applications
Component: general
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: Brasero maintainer(s)
Brasero maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2010-05-26 12:59 UTC by Pedro Villavicencio
Modified: 2018-09-21 17:03 UTC
See Also:
GNOME target: ---
GNOME version: 2.29/2.30


Description Pedro Villavicencio 2010-05-26 12:59:47 UTC 
this report has been filed here:

https://bugs.edge.launchpad.net/ubuntu/+source/brasero/+bug/583225

"Procedure:
- Open nautilus
- At location type in an sftp or smb share
- Open brasero and start a new data cd/dvd project
- Drag files from nautilus and drop into brasero
- Burn it.
- Brasero copies remote files locally and after that it tells the project burned succesfully. But the cd/dvd (or iso image) is empty.

Looking at the log files it seems that the file has been copied correctly (and effectively they are at /tmp) but the file used as the -path-list with genisoimage only contains the md5 checksum file but not the files to be burned. Even the md5 file is empty.

I have attached every brasero file involved in the procedure."

http://launchpadlibrarian.net/48802710/brasero-sftp.tar.bz2

Thanks,
Comment 1 Kiren Pillay 2015-09-14 07:53:05 UTC 
I'm experiencing this as well now. I'm burning from files on a Samba share and the disk comes out empty, while the disk name is being written. I tried with and without Windows shortened names, but same result.
Comment 2 GNOME Infrastructure Team 2018-09-21 17:03:24 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: https://gitlab.gnome.org/GNOME/brasero/issues/110.