GNOME Bugzilla – Bug 536949
Can not read from Samba location with weird charaters
Last modified: 2008-06-21 12:39:29 UTC
[ forwarded from http://bugs.debian.org/484703 ] When starting totem with a file from a gnome-vfs with a space in it totem can not play that file. Opening a file with Movie->Open and browsing to a Samba-Share with a space I get: ** Message: Error: Could not read from resource. gstgnomevfssrc.c(683): gst_gnome_vfs_src_create (): /play/source: Failed to read data: Invalid parameters The error is the same when I drag and drop a file from nautilus. An example filename would be (as dragging from nautilus in a terminal window): smb://foobar/shares/public/video/Prof.%20Haber%20berichtet/2224870.divx A name without spaces in the location works.
I have a hard time believing that spaces are creating this problem. Does this work: gst-launch-0.10 playbin uri=smb://foobar/shares/public/video/Prof.%20Haber%20berichtet/2224870.divx Or does this work: gvfs-cat smb://foobar/shares/public/video/Prof.%20Haber%20berichtet/2224870.divx | totem fd://0
> Does this work: > > gst-launch-0.10 playbin uri=smb://foobar/shares/public/video/Prof.%20Haber%20berichtet/2224870.divx This does not work: > > Or does this work: gst-launch-0.10 playbin uri=smb://foobar/public/home-old/shares/public/video/Prof.%20Haber%20berichtet/2205961.divx This does not work: Setting pipeline to PAUSED ... Pipeline is PREROLLING ... ERROR: from element /playbin0/source: Could not read from resource. Additional debug info: gstgnomevfssrc.c(683): gst_gnome_vfs_src_create (): /playbin0/source: Failed to read data: Invalid parameters ERROR: pipeline doesn't want to preroll. Setting pipeline to NULL ... FREEING pipeline ... > gvfs-cat smb://foobar/shares/public/video/Prof.%20Haber%20berichtet/2224870.divx | totem fd://0 This works: ** Message: opening smb://foobar/shares/public/public/video/Prof.%20Haber%20berichtet/2205961.divx Seems to be a gstreamer problem? Regards, Kai
It's a gnome-vfs problem, or a problem with the person's SMB setup, yes. Could you please get a debug output: GST_DEBUG="*:3" gst-launch-0.10 gnomevfssrc uri=smb://foobar/shares/public/video/Prof.%20Haber%20berichtet/2224870.divx ! fakesink
Created attachment 112739 [details] gnomevfssrc debug trace
You could try and catch my stupidness as well: WARNING: erroneous pipeline: no property "uri" in element "gnomevfssrc0" The property is names location for gnomevfssrc. Try again with that.
Oh right... I'm not an expert with this stuff :)
Created attachment 112854 [details] gnomevfssrc debug output
Seems to work fine, there's no error messages in there. Are there any 2205961.txt, or any other 2205961.* files in that directory? Can you try disabling the subtitle autoload?
No other files in there... I attached the gnomevfs-ls output
Created attachment 112866 [details] Directory listing gnomevfs-ls "smb://foobar/public/home-old/shares/public/video/Prof. Haber berichtet"
I still don't see what could be happening here. Is the share password protected? Could you please attach the (compressed) output of: GST_DEBUG='*:5' totem <uri>
Hi, I got a hand on the samba log file: it's a samba failure! Samba dumps core when trying to read a file bigger than a number of bytes. I will investigate this further and blame samba. So all in all: sorry for making so much noise. Close the bug! If anyone is interessted, the samba logfile looks like this: [2008/06/20 19:27:38, 0] smbd/reply.c:send_file_readX(2621) send_file_readX: sendfile failed for file home-old/shares/public/video/2174759.divx (Broken pipe). Terminating [2008/06/20 19:27:38, 1] smbd/service.c:close_cnum(1150) 192.168.178.23 (192.168.178.23) closed connection to service public [2008/06/20 19:27:38, 0] smbd/server.c:exit_server_common(657) =============================================================== [2008/06/20 19:27:38, 0] smbd/server.c:exit_server_common(659) Abnormal server exit: send_file_readX sendfile failed [2008/06/20 19:27:38, 0] smbd/server.c:exit_server_common(660) =============================================================== [2008/06/20 19:27:38, 0] lib/util.c:log_stack_trace(1706) BACKTRACE: 0 stack frames: [2008/06/20 19:27:38, 0] smbd/server.c:exit_server_common(664) Last message was SMBreadX [2008/06/20 19:27:38, 5] lib/util.c:show_msg(485) [2008/06/20 19:27:38, 5] lib/util.c:show_msg(495) size=55 smb_com=0x2e smb_rcls=0 smb_reh=0 smb_err=0 smb_flg=8 smb_flg2=55297 smb_tid=1 smb_pid=5747 smb_uid=100 smb_mid=87 smt_wct=10 smb_vwv[ 0]= 255 (0xFF) smb_vwv[ 1]= 0 (0x0) smb_vwv[ 2]= 5381 (0x1505) smb_vwv[ 3]=11852 (0x2E4C) smb_vwv[ 4]= 3704 (0xE78) smb_vwv[ 5]=64512 (0xFC00) smb_vwv[ 6]=64512 (0xFC00) smb_vwv[ 7]= 1 (0x1) smb_vwv[ 8]= 0 (0x0) smb_vwv[ 9]= 0 (0x0) smb_bcc=0 [2008/06/20 19:27:38, 0] lib/fault.c:dump_core(173) dumping core in /var/log/samba/cores/smbd
I take all back... It is not obviously samba's fault: samba's log is very interessting. The client connection seems to be closed after sending/receiving exactly 130111 bytes. All the errors are with different files: [2008/06/20 20:00:01, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client 192.168.178.23. Error Connection reset by peer [2008/06/20 20:00:01, 0] lib/util_sock.c:send_smb(761) Error writing 130111 bytes to client. -1. (Connection reset by peer) [2008/06/20 20:00:36, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client 192.168.178.23. Error Connection reset by peer [2008/06/20 20:00:36, 0] lib/util_sock.c:send_smb(761) Error writing 130111 bytes to client. -1. (Connection reset by peer) [2008/06/20 20:02:26, 0] lib/util_sock.c:write_data(562) write_data: write failure in writing to client 192.168.178.23. Error Connection reset by peer [2008/06/20 20:02:26, 0] lib/util_sock.c:send_smb(761) Error writing 130111 bytes to client. -1. (Connection reset by peer) I attach a totem debug log.
Created attachment 113137 [details] Totem debug log Command line was GST_DEBUG_NO_COLOR=1 GST_DEBUG="*:5" totem "smb://foobar/public/home-old/shares/public/video/Prof. Haber berichtet/2189975.divx" 2> output.log
Created attachment 113138 [details] Totem debug log Command line was GST_DEBUG_NO_COLOR=1 GST_DEBUG="*:5" totem "smb://foobar/public/home-old/shares/public/video/Prof. Haber berichtet/2189975.divx" 2> output.log
Whether or not it's the client's fault, I'm not going to touch this until smbd stops crashing, for whatever reason. Please file a bug against your distribution, or samba.org directly upstream, and let me know when that problem is solved. I'd probably need new debug logs by then.
Samba does not crash anymore. The crashes had nothing to do with the original bug report. Seems I am bitten by this bug, filed first 2 years ago. Obviously a gnome-vfs problem: http://bugzilla.gnome.org/show_bug.cgi?id=35913
Bug doesn't exist...
The correct url is http://bugzilla.gnome.org/show_bug.cgi?id=359133
Fair dos. Newer versions of GNOME should be using GIO instead, which should have this problem fixed. *** This bug has been marked as a duplicate of 359133 ***