[Bug 361936] Re: Xorg crashed with SIGSEGV in nis_print_group_entry()
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/25507490/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25507491/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/25507492/Disassembly.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/25507493/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/25507494/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/25507495/LsPci.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/25507496/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/25507497/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/25507498/Registers.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/25507499/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/25507500/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/25507501/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/25507502/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/25507503/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/25507504/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/25507505/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/25507506/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/25507507/xkbcomp.txt ** Visibility changed to: Public -- Xorg crashed with SIGSEGV in nis_print_group_entry() https://bugs.launchpad.net/bugs/361936 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
I hate to be wet blanket, but I still have problems with samba/smbfs under Intrepid. I installed the samba files from Thierry's ppa repository. Nautilus indeed now lets me see and list the contents of my Iomega 500 GB Home Network Hard Drive and copy files from the drive to my Intrepid desktop. However, I can't write any files to the drive using Nautilus and SMB/CIFS or via ftp. I tried using smbclient in a terminal to "put" a test file onto the NAS drive and this is the output: [EMAIL PROTECTED]:~$ smbclient //192.168.0.198/ubuntu Enter ross's password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/test.file test.file Error writing file: ERRHRD - 39 putting file /home/ross/Desktop/test.file as \test.file Receiving SMB: Server stopped responding Call returned zero bytes (EOF) closing remote file \test.file smb: \> The same test under Hardy from a laptop results in this successful output: [EMAIL PROTECTED]:~$ smbclient //192.168.0.198/ubuntu Password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/test.file test.file putting file /home/ross/Desktop/test.file as \test.file (135.9 kb/s) (average 135.9 kbs) smb: \> So something is still wrong with Samba, at least on my Intrepid desktop. I am going to revert back to release Samba package for Intrepid and see what smbclient does and see if I can at least get ftp to the NAS working again. Any thoughts? BTW, the Nautilus error that gets thrown up when I try to write a file with the new Samba installed is: Error while copying "test.file". There was an error copying the file into smb://192.168.0.198/ubuntu/. V Show more details No space left on device. Maybe that is how Nautilus interprets ERRHRD -39 ? The NAS disk is 500GB with lots of room. Ideas? -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
The latest official Ubuntu Samba update regresses the one in Thierry's ppa repository. I used Synaptic Package Manager to force the Samba packages back to the ones from Thierry's ppa and then used Synaptic again to lock those versions so they won't be "upgraded" via Intrepid- Updates again. You might want to do the same. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Replying to Christian Perrier & Daniel Eckl: Sorry guys, I didn't mean to sound like I was recommending that everyone lock in Thierry's ppa Samba patches without the most recent security fixes. It is a balance between usability and security and in my specific case the usability aspect trumps the security one. I will check out any new updates as they are made available from Intrepid - Updates but if they break my NAS access I will go back to the ppa fixes - I need a functional NAS and I don't want the fuss of going back to Ubuntu 8.04 to get it. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Ditto for me as well - new ppa version working OK as far as I can tell. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Christian: I installed your packages with the patches for Debian in Ubuntu 8.10 using the Synaptic front end for apt without any problems. I did not change my smb.conf file. The following tests to my IOmega 500 GB Home Network Harddrive (NAS) worked without any problems. 1. Created a test file "test.txt" and using smbclient via a terminal "put" the file into the /public folder of the NAS. 2. Using smbclient, used the "get" command to retrieve "test.txt" and rename it and put it on my desktop as "testret.txt". 3. Using Nautilus under the Gnome desktop opened (mounted) the /public folder on the NAS and dragged the "test.txt" file into it. 4. Deleted the "test.txt" file from the NAS via the Nautilus window. 5. Copied a 700.1 MB avi file from the /public folder of the NAS to the Gnome desktop via Nautilus "drag & drop". All these tests worked OK. I will keep your Samba version for a couple of days to give it some more of a workout, but so far it seems to work the same as the one in Thierry's latest ppa for Ubuntu. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: The patch does not appear to have changed the behaviour from the previous patch. An smbclient "put" of a file from a terminal still results in the ERRHRD -39 error message (after doing a successful "ls" first) and a Nautilus "drag and drop" of a file from the Desktop into the open NAS folder still results in the same "No space left on device" error message as noted by ^_Pepe_^ in the previous message. I've attached another Wireshark trace of the attempt to write the file "Test2.txt" from the Desktop into the NAS folder //192.168.0.195/public using Nautilus. The second Wireshark trace, in the following message (I can't seem to attach more than one file to a message in Launchpad) is the same drag and drop type of write but from the desktop of the virtual WinXP Pro SP3 into //192.168.0.195/public for comparison purposes. There is one other visual oddity that I have noticed that may or may not be a clue to something. When I have mounted the NAS folder //192.168.0.195/public on my Desktop and I select the folder using a right mouse button click, the dialog window that opens up shows the entry "Paste into Folder" occasionally flickering from greyed out status to selectable and then back to greyed out. ^_Pepe_^, do you see that as well? I checked the same thing out using Smaba 3.0 instead of Samba 3.2 and the "Paste into Folder" flickering from inactive to active doesn't occur. It is almost like something is trying automatically activate the "Paste into Folder" function, fails, waits and then tries again and again. ** Attachment added: "cap_fail_wrt.pcap" http://launchpadlibrarian.net/20582264/cap_fail_wrt.pcap -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: The WinXP SP3 trace for reference. Same file name, text2.txt, and NAS address //192.168.0.195/public ** Attachment added: "winxpsp3_cap.pcap" http://launchpadlibrarian.net/20582319/winxpsp3_cap.pcap -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
If anyone is still following this thread, they seem to be making progress on the root problem of the write issue to NAS devices in samba- bugs# 5953 (link at the top of the page). -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai & Thierry: Volker Lendecke's patch seems to have done the trick! Both a write using an smbclient 'put' as well as a drag and drop via Nautilus now work as expected. The visual side effect in Nautilus I noted five messages above is still present but since it doesn't seem to have a bearing on file writing functionality to the NAS I think it can be ignored for now. Using 'get' in smbclient continues to work just fine as well. Good work! And Happy Holidays to all... -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
OK, attached are some files. First a pdf file showing how my network is laid out (1 picture worth 1000 words etc.). Next is a text file of the network capture on eth0 between my Linux comp (ubuntu-test) at ip 192.168.0.100 and my IOmega 500 GB NAS aka "Home Network Hard Drive" via a DLink 615 router. The IOmega NAS is at 192.168.0.195. I used Wireshark for the capture. The last file is the same information but in the Wireshark proprietary format. I am using Samba 2:3.2.3-1ubuntu3.3. I tried to connect to smb://192.168.0.195/PUBLIC/ from Nautilus and it momentarily connects but then Nautilus reverts to displaying my home folder as previous posters have mentioned. The IOmega NAS uses an embedded Linux server of some kind to serve requests. ftp works OK. ** Attachment added: "Network.pdf" http://launchpadlibrarian.net/20394588/Network.pdf -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
** Attachment added: "wiresharkdmp.txt" http://launchpadlibrarian.net/20394606/wiresharkdmp.txt -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
** Attachment added: "wiresharkdmp" http://launchpadlibrarian.net/20394611/wiresharkdmp -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Thierry and Kai: Preliminary tests with the most recent patch (2:3.2.3-1ubuntu3.4~ppa3) of samba shows the following: Read access to my NAS works as expected in Nautilus and read access using smclient in a terminal works. However, a put access (ie write access) using smbclient still returns an ERRHD -39 error as seen in the message below. r...@ubuntu-test:~$ smbclient //192.168.0.195/public Enter ross's password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/disk_layout.png disk_layout.png Error writing file: ERRHRD - 39 putting file /home/ross/Desktop/disk_layout.png as \disk_layout.png Receiving SMB: Server stopped responding Call returned zero bytes (EOF) closing remote file \disk_layout.png smb: \> Also, attempting a write access by dragging a file into the smb:// Nautilus window generates the disk full error message as seen in the attachment. In other words, the latest patch has produced about the same result as the 2:3.2.3-1ubuntu3.4~ppa2 patch. What is common to both smbclient write access and Nautilus write access during a write to a NAS device? Is there any other capture I can do that might help to pinpoint that area? Any idea what ERRHRD -39 might point towards? So, in summary, with the latest patch, read access is OK, write access is still FUBAR. ** Attachment added: "error.png" http://launchpadlibrarian.net/20441556/error.png -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Tomek's results are interesting, I will have to see if I get the same effect. I tried something a little different. I uninstalled all the Samba packages except for libsmbclient and libwbclient0. Removal of either of these packages would also result in the removal of 17-20 other packages on my system, including Nautilus, that depend on these libraries so they have to be left in place. After removing all the Samba packages I could I tried to write to the NAS from Nautilus by dragging and dropping a file and I got the same error as before about the disk being full (see my previous message). Of course, since I had uninstalled smbclient, I couldn't run a test from a terminal. My hunch is that the root of the problem is in either the libsmbclient or libwbclient0 libraries. I might try to do a "dpkg -i force-downgrade" for the whole Samba suite to the Hardy version packages just to see what happens (my guess is that it will break something so I'll have to set up an experimental system to play on). In any event, I will reinstall the Samba packages and see if I can replicate Tomek's results. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
OK. I repeated Tomek's smbclient tests and got the same results as he did. I also noticed as Tomek did that smb: \> ls *.txt list all files, as does smb: \> ls *.* and smb: \> ls * and smb : \> ls In other words it seems that if the "*" character is the first one after the smb "ls" (list) command, it produces the same result as an "ls" command with no parameters. Is this normal parsing behaviour for smbclient? I will have to test this out on my Hardy system. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
I can concur with Kai Blin re: the ls command parsing behaviour in smbclient. I tested the smbclient ls command on a working Hardy system against the same IOmega NAS that is giving me problems (under Intrepid) and it produces the same results, so I don't think that it is related to the ERRHRD -39 problem. All I know about the embedded server in the IOmega NAS is that it is some kind of linux server. The embedded linux on the NAS also handles some other "slight of hand" such as transparently breaking files larger than 4 GB into smaller pieces. It does this because it only will work as a NAS if its hard drive is formatted as FAT32. IOmega claims that FAT32 gives it the broadest range of compatability since Windows, Mac OS and Linux/Unix can all read and write that format. The NAS also has a local USB2 port, as well as a 10/100 ethernet port, so the embedded linux must have a fairly complete communication suite. Thierry, would it help if I set my NAS up in a DMZ off my router so that it is exposed to the great unwashed internet? Maybe you would be able to test against it then? I'd have to experiment a bit to see what IP address it would end up with so you could access it via smb, but 'm willing to give it a try. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
For what it is worth, write access to my IOmega NAS using WinXP in a virtual machine environment on my Linux box works just fine. See attached screen shot which shows the result of having just "dragged & dropped" a file called bookmarks.html into the NAS window. This definitely seems to point to a Samba regression of some kind as Thierry Carrez has suggested. I mean when WinXP works with an embedded linux Samba in the NAS but Ubuntu Intrepid doesn't, something "just ain't right". :-) Richard Wooding, your SSH port forwarding idea might work better than my DMZ one since I can't figure out how to get around the private address range (192.168.0.xxx) for the NAS when it is exposed to the internet. Maybe some kind of virtual server and port forwarding arrangement in my router would work? I'm getting out of my networking depth here... ** Attachment added: "Screenshot.png" http://launchpadlibrarian.net/20473139/Screenshot.png -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai Blin: I should be able to do those traces using Wireshark since I have both Hardy and Intrepid installed on two different machines. Does it matter if the Hardy install is via wireless to the router? I shouldn't think so. One other tidbit about the IOmega NAS from their brief technical spec they say that Linux must use Samba 3 or later. This does suggest that the NAS also uses a version of Samba 3. One more test I just completed was to revert samba-common to version 3.0 .28a-1ubuntu4.7 and smbclient to version 3.0.28a-1ubuntu4.7 which are the Hardy versions for those two packages. Doing this allowed an smbclient "put" to the NAS to work correctly but did not fix write access via Nautilus. Unfortunately I couldn't revert nautilus-share and libsmbclient because of package dependency issues. I have reinstalled Thierry's latest ppa version of the Samba packages so I will use those for the 3.2 trace and the Hardy install for the 3.0 trace. I'll have the traces done by tomorrow. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: Here are the two traces you requested. The first trace, sam_cap3.0, is from the wlan0 interface of my laptop with Hardy installed and shows a successful attempt to write a small file, text2.txt, using Nautilus and a drag and drop of the file from the Desktop into the open Nautilus folder of //192.168.0.195/public (the NAS address). The second capture, sam_cap3.2, attached in the next message, is an unsuccessful attempt to write the same file, text2.txt, from the Desktop of my main computer, with Intrepid installed, into the open Nautilus folder of //192.168.0.195/public using the same drag and drop procedure as above. The interface in this case is eth0 since my main computer is hard wired into the router. Both traces are in the pcap format that you want and were taken using Wireshark. I could tray and pry out the Samba version in the NAS from IOmega tech support, although I rate my chances of success as about the same as a snowball's chance in Hell... I defer to your much deeper and more comprehensive understanding of Samba. ** Attachment added: "sam_cap3.0" http://launchpadlibrarian.net/20495242/sam_cap3.0 -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: The second trace. ** Attachment added: "sam_cap3.2" http://launchpadlibrarian.net/20495250/sam_cap3.2 -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Thierry: Can you bulid a new package in your PPA for Intrepid with this latest patch from Kai? I'll test ASAP once the package is ready. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
I hate to be wet blanket, but I still have problems with samba/smbfs under Intrepid. I installed the samba files from Thierry's ppa repository. Nautilus indeed now lets me see and list the contents of my Iomega 500 GB Home Network Hard Drive and copy files from the drive to my Intrepid desktop. However, I can't write any files to the drive using Nautilus and SMB/CIFS or via ftp. I tried using smbclient in a terminal to "put" a test file onto the NAS drive and this is the output: [EMAIL PROTECTED]:~$ smbclient //192.168.0.198/ubuntu Enter ross's password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/test.file test.file Error writing file: ERRHRD - 39 putting file /home/ross/Desktop/test.file as \test.file Receiving SMB: Server stopped responding Call returned zero bytes (EOF) closing remote file \test.file smb: \> The same test under Hardy from a laptop results in this successful output: [EMAIL PROTECTED]:~$ smbclient //192.168.0.198/ubuntu Password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/test.file test.file putting file /home/ross/Desktop/test.file as \test.file (135.9 kb/s) (average 135.9 kbs) smb: \> So something is still wrong with Samba, at least on my Intrepid desktop. I am going to revert back to release Samba package for Intrepid and see what smbclient does and see if I can at least get ftp to the NAS working again. Any thoughts? BTW, the Nautilus error that gets thrown up when I try to write a file with the new Samba installed is: Error while copying "test.file". There was an error copying the file into smb://192.168.0.198/ubuntu/. V Show more details No space left on device. Maybe that is how Nautilus interprets ERRHRD -39 ? The NAS disk is 500GB with lots of room. Ideas? -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
OK, attached are some files. First a pdf file showing how my network is laid out (1 picture worth 1000 words etc.). Next is a text file of the network capture on eth0 between my Linux comp (ubuntu-test) at ip 192.168.0.100 and my IOmega 500 GB NAS aka "Home Network Hard Drive" via a DLink 615 router. The IOmega NAS is at 192.168.0.195. I used Wireshark for the capture. The last file is the same information but in the Wireshark proprietary format. I am using Samba 2:3.2.3-1ubuntu3.3. I tried to connect to smb://192.168.0.195/PUBLIC/ from Nautilus and it momentarily connects but then Nautilus reverts to displaying my home folder as previous posters have mentioned. The IOmega NAS uses an embedded Linux server of some kind to serve requests. ftp works OK. ** Attachment added: "Network.pdf" http://launchpadlibrarian.net/20394588/Network.pdf -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
** Attachment added: "wiresharkdmp.txt" http://launchpadlibrarian.net/20394606/wiresharkdmp.txt -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
** Attachment added: "wiresharkdmp" http://launchpadlibrarian.net/20394611/wiresharkdmp -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Thierry and Kai: Preliminary tests with the most recent patch (2:3.2.3-1ubuntu3.4~ppa3) of samba shows the following: Read access to my NAS works as expected in Nautilus and read access using smclient in a terminal works. However, a put access (ie write access) using smbclient still returns an ERRHD -39 error as seen in the message below. r...@ubuntu-test:~$ smbclient //192.168.0.195/public Enter ross's password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/disk_layout.png disk_layout.png Error writing file: ERRHRD - 39 putting file /home/ross/Desktop/disk_layout.png as \disk_layout.png Receiving SMB: Server stopped responding Call returned zero bytes (EOF) closing remote file \disk_layout.png smb: \> Also, attempting a write access by dragging a file into the smb:// Nautilus window generates the disk full error message as seen in the attachment. In other words, the latest patch has produced about the same result as the 2:3.2.3-1ubuntu3.4~ppa2 patch. What is common to both smbclient write access and Nautilus write access during a write to a NAS device? Is there any other capture I can do that might help to pinpoint that area? Any idea what ERRHRD -39 might point towards? So, in summary, with the latest patch, read access is OK, write access is still FUBAR. ** Attachment added: "error.png" http://launchpadlibrarian.net/20441556/error.png -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Tomek's results are interesting, I will have to see if I get the same effect. I tried something a little different. I uninstalled all the Samba packages except for libsmbclient and libwbclient0. Removal of either of these packages would also result in the removal of 17-20 other packages on my system, including Nautilus, that depend on these libraries so they have to be left in place. After removing all the Samba packages I could I tried to write to the NAS from Nautilus by dragging and dropping a file and I got the same error as before about the disk being full (see my previous message). Of course, since I had uninstalled smbclient, I couldn't run a test from a terminal. My hunch is that the root of the problem is in either the libsmbclient or libwbclient0 libraries. I might try to do a "dpkg -i force-downgrade" for the whole Samba suite to the Hardy version packages just to see what happens (my guess is that it will break something so I'll have to set up an experimental system to play on). In any event, I will reinstall the Samba packages and see if I can replicate Tomek's results. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
OK. I repeated Tomek's smbclient tests and got the same results as he did. I also noticed as Tomek did that smb: \> ls *.txt list all files, as does smb: \> ls *.* and smb: \> ls * and smb : \> ls In other words it seems that if the "*" character is the first one after the smb "ls" (list) command, it produces the same result as an "ls" command with no parameters. Is this normal parsing behaviour for smbclient? I will have to test this out on my Hardy system. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
I can concur with Kai Blin re: the ls command parsing behaviour in smbclient. I tested the smbclient ls command on a working Hardy system against the same IOmega NAS that is giving me problems (under Intrepid) and it produces the same results, so I don't think that it is related to the ERRHRD -39 problem. All I know about the embedded server in the IOmega NAS is that it is some kind of linux server. The embedded linux on the NAS also handles some other "slight of hand" such as transparently breaking files larger than 4 GB into smaller pieces. It does this because it only will work as a NAS if its hard drive is formatted as FAT32. IOmega claims that FAT32 gives it the broadest range of compatability since Windows, Mac OS and Linux/Unix can all read and write that format. The NAS also has a local USB2 port, as well as a 10/100 ethernet port, so the embedded linux must have a fairly complete communication suite. Thierry, would it help if I set my NAS up in a DMZ off my router so that it is exposed to the great unwashed internet? Maybe you would be able to test against it then? I'd have to experiment a bit to see what IP address it would end up with so you could access it via smb, but 'm willing to give it a try. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
For what it is worth, write access to my IOmega NAS using WinXP in a virtual machine environment on my Linux box works just fine. See attached screen shot which shows the result of having just "dragged & dropped" a file called bookmarks.html into the NAS window. This definitely seems to point to a Samba regression of some kind as Thierry Carrez has suggested. I mean when WinXP works with an embedded linux Samba in the NAS but Ubuntu Intrepid doesn't, something "just ain't right". :-) Richard Wooding, your SSH port forwarding idea might work better than my DMZ one since I can't figure out how to get around the private address range (192.168.0.xxx) for the NAS when it is exposed to the internet. Maybe some kind of virtual server and port forwarding arrangement in my router would work? I'm getting out of my networking depth here... ** Attachment added: "Screenshot.png" http://launchpadlibrarian.net/20473139/Screenshot.png -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai Blin: I should be able to do those traces using Wireshark since I have both Hardy and Intrepid installed on two different machines. Does it matter if the Hardy install is via wireless to the router? I shouldn't think so. One other tidbit about the IOmega NAS from their brief technical spec they say that Linux must use Samba 3 or later. This does suggest that the NAS also uses a version of Samba 3. One more test I just completed was to revert samba-common to version 3.0 .28a-1ubuntu4.7 and smbclient to version 3.0.28a-1ubuntu4.7 which are the Hardy versions for those two packages. Doing this allowed an smbclient "put" to the NAS to work correctly but did not fix write access via Nautilus. Unfortunately I couldn't revert nautilus-share and libsmbclient because of package dependency issues. I have reinstalled Thierry's latest ppa version of the Samba packages so I will use those for the 3.2 trace and the Hardy install for the 3.0 trace. I'll have the traces done by tomorrow. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: Here are the two traces you requested. The first trace, sam_cap3.0, is from the wlan0 interface of my laptop with Hardy installed and shows a successful attempt to write a small file, text2.txt, using Nautilus and a drag and drop of the file from the Desktop into the open Nautilus folder of //192.168.0.195/public (the NAS address). The second capture, sam_cap3.2, attached in the next message, is an unsuccessful attempt to write the same file, text2.txt, from the Desktop of my main computer, with Intrepid installed, into the open Nautilus folder of //192.168.0.195/public using the same drag and drop procedure as above. The interface in this case is eth0 since my main computer is hard wired into the router. Both traces are in the pcap format that you want and were taken using Wireshark. I could tray and pry out the Samba version in the NAS from IOmega tech support, although I rate my chances of success as about the same as a snowball's chance in Hell... I defer to your much deeper and more comprehensive understanding of Samba. ** Attachment added: "sam_cap3.0" http://launchpadlibrarian.net/20495242/sam_cap3.0 -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
The latest official Ubuntu Samba update regresses the one in Thierry's ppa repository. I used Synaptic Package Manager to force the Samba packages back to the ones from Thierry's ppa and then used Synaptic again to lock those versions so they won't be "upgraded" via Intrepid- Updates again. You might want to do the same. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Replying to Christian Perrier & Daniel Eckl: Sorry guys, I didn't mean to sound like I was recommending that everyone lock in Thierry's ppa Samba patches without the most recent security fixes. It is a balance between usability and security and in my specific case the usability aspect trumps the security one. I will check out any new updates as they are made available from Intrepid - Updates but if they break my NAS access I will go back to the ppa fixes - I need a functional NAS and I don't want the fuss of going back to Ubuntu 8.04 to get it. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Ditto for me as well - new ppa version working OK as far as I can tell. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Christian: I installed your packages with the patches for Debian in Ubuntu 8.10 using the Synaptic front end for apt without any problems. I did not change my smb.conf file. The following tests to my IOmega 500 GB Home Network Harddrive (NAS) worked without any problems. 1. Created a test file "test.txt" and using smbclient via a terminal "put" the file into the /public folder of the NAS. 2. Using smbclient, used the "get" command to retrieve "test.txt" and rename it and put it on my desktop as "testret.txt". 3. Using Nautilus under the Gnome desktop opened (mounted) the /public folder on the NAS and dragged the "test.txt" file into it. 4. Deleted the "test.txt" file from the NAS via the Nautilus window. 5. Copied a 700.1 MB avi file from the /public folder of the NAS to the Gnome desktop via Nautilus "drag & drop". All these tests worked OK. I will keep your Samba version for a couple of days to give it some more of a workout, but so far it seems to work the same as the one in Thierry's latest ppa for Ubuntu. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: The second trace. ** Attachment added: "sam_cap3.2" http://launchpadlibrarian.net/20495250/sam_cap3.2 -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Thierry: Can you bulid a new package in your PPA for Intrepid with this latest patch from Kai? I'll test ASAP once the package is ready. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: The patch does not appear to have changed the behaviour from the previous patch. An smbclient "put" of a file from a terminal still results in the ERRHRD -39 error message (after doing a successful "ls" first) and a Nautilus "drag and drop" of a file from the Desktop into the open NAS folder still results in the same "No space left on device" error message as noted by ^_Pepe_^ in the previous message. I've attached another Wireshark trace of the attempt to write the file "Test2.txt" from the Desktop into the NAS folder //192.168.0.195/public using Nautilus. The second Wireshark trace, in the following message (I can't seem to attach more than one file to a message in Launchpad) is the same drag and drop type of write but from the desktop of the virtual WinXP Pro SP3 into //192.168.0.195/public for comparison purposes. There is one other visual oddity that I have noticed that may or may not be a clue to something. When I have mounted the NAS folder //192.168.0.195/public on my Desktop and I select the folder using a right mouse button click, the dialog window that opens up shows the entry "Paste into Folder" occasionally flickering from greyed out status to selectable and then back to greyed out. ^_Pepe_^, do you see that as well? I checked the same thing out using Smaba 3.0 instead of Samba 3.2 and the "Paste into Folder" flickering from inactive to active doesn't occur. It is almost like something is trying automatically activate the "Paste into Folder" function, fails, waits and then tries again and again. ** Attachment added: "cap_fail_wrt.pcap" http://launchpadlibrarian.net/20582264/cap_fail_wrt.pcap -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: The WinXP SP3 trace for reference. Same file name, text2.txt, and NAS address //192.168.0.195/public ** Attachment added: "winxpsp3_cap.pcap" http://launchpadlibrarian.net/20582319/winxpsp3_cap.pcap -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
If anyone is still following this thread, they seem to be making progress on the root problem of the write issue to NAS devices in samba- bugs# 5953 (link at the top of the page). -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai & Thierry: Volker Lendecke's patch seems to have done the trick! Both a write using an smbclient 'put' as well as a drag and drop via Nautilus now work as expected. The visual side effect in Nautilus I noted five messages above is still present but since it doesn't seem to have a bearing on file writing functionality to the NAS I think it can be ignored for now. Using 'get' in smbclient continues to work just fine as well. Good work! And Happy Holidays to all... -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
I hate to be wet blanket, but I still have problems with samba/smbfs under Intrepid. I installed the samba files from Thierry's ppa repository. Nautilus indeed now lets me see and list the contents of my Iomega 500 GB Home Network Hard Drive and copy files from the drive to my Intrepid desktop. However, I can't write any files to the drive using Nautilus and SMB/CIFS or via ftp. I tried using smbclient in a terminal to "put" a test file onto the NAS drive and this is the output: [EMAIL PROTECTED]:~$ smbclient //192.168.0.198/ubuntu Enter ross's password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/test.file test.file Error writing file: ERRHRD - 39 putting file /home/ross/Desktop/test.file as \test.file Receiving SMB: Server stopped responding Call returned zero bytes (EOF) closing remote file \test.file smb: \> The same test under Hardy from a laptop results in this successful output: [EMAIL PROTECTED]:~$ smbclient //192.168.0.198/ubuntu Password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/test.file test.file putting file /home/ross/Desktop/test.file as \test.file (135.9 kb/s) (average 135.9 kbs) smb: \> So something is still wrong with Samba, at least on my Intrepid desktop. I am going to revert back to release Samba package for Intrepid and see what smbclient does and see if I can at least get ftp to the NAS working again. Any thoughts? BTW, the Nautilus error that gets thrown up when I try to write a file with the new Samba installed is: Error while copying "test.file". There was an error copying the file into smb://192.168.0.198/ubuntu/. V Show more details No space left on device. Maybe that is how Nautilus interprets ERRHRD -39 ? The NAS disk is 500GB with lots of room. Ideas? -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
OK, attached are some files. First a pdf file showing how my network is laid out (1 picture worth 1000 words etc.). Next is a text file of the network capture on eth0 between my Linux comp (ubuntu-test) at ip 192.168.0.100 and my IOmega 500 GB NAS aka "Home Network Hard Drive" via a DLink 615 router. The IOmega NAS is at 192.168.0.195. I used Wireshark for the capture. The last file is the same information but in the Wireshark proprietary format. I am using Samba 2:3.2.3-1ubuntu3.3. I tried to connect to smb://192.168.0.195/PUBLIC/ from Nautilus and it momentarily connects but then Nautilus reverts to displaying my home folder as previous posters have mentioned. The IOmega NAS uses an embedded Linux server of some kind to serve requests. ftp works OK. ** Attachment added: "Network.pdf" http://launchpadlibrarian.net/20394588/Network.pdf -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
** Attachment added: "wiresharkdmp.txt" http://launchpadlibrarian.net/20394606/wiresharkdmp.txt -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
** Attachment added: "wiresharkdmp" http://launchpadlibrarian.net/20394611/wiresharkdmp -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Replying to Christian Perrier & Daniel Eckl: Sorry guys, I didn't mean to sound like I was recommending that everyone lock in Thierry's ppa Samba patches without the most recent security fixes. It is a balance between usability and security and in my specific case the usability aspect trumps the security one. I will check out any new updates as they are made available from Intrepid - Updates but if they break my NAS access I will go back to the ppa fixes - I need a functional NAS and I don't want the fuss of going back to Ubuntu 8.04 to get it. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Ditto for me as well - new ppa version working OK as far as I can tell. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Christian: I installed your packages with the patches for Debian in Ubuntu 8.10 using the Synaptic front end for apt without any problems. I did not change my smb.conf file. The following tests to my IOmega 500 GB Home Network Harddrive (NAS) worked without any problems. 1. Created a test file "test.txt" and using smbclient via a terminal "put" the file into the /public folder of the NAS. 2. Using smbclient, used the "get" command to retrieve "test.txt" and rename it and put it on my desktop as "testret.txt". 3. Using Nautilus under the Gnome desktop opened (mounted) the /public folder on the NAS and dragged the "test.txt" file into it. 4. Deleted the "test.txt" file from the NAS via the Nautilus window. 5. Copied a 700.1 MB avi file from the /public folder of the NAS to the Gnome desktop via Nautilus "drag & drop". All these tests worked OK. I will keep your Samba version for a couple of days to give it some more of a workout, but so far it seems to work the same as the one in Thierry's latest ppa for Ubuntu. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361936] Re: Xorg crashed with SIGSEGV in nis_print_group_entry()
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/25507490/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25507491/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/25507492/Disassembly.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/25507493/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/25507494/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/25507495/LsPci.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/25507496/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/25507497/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/25507498/Registers.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/25507499/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/25507500/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/25507501/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/25507502/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/25507503/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/25507504/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/25507505/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/25507506/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/25507507/xkbcomp.txt ** Visibility changed to: Public -- Xorg crashed with SIGSEGV in nis_print_group_entry() https://bugs.launchpad.net/bugs/361936 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
The latest official Ubuntu Samba update regresses the one in Thierry's ppa repository. I used Synaptic Package Manager to force the Samba packages back to the ones from Thierry's ppa and then used Synaptic again to lock those versions so they won't be "upgraded" via Intrepid- Updates again. You might want to do the same. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
If anyone is still following this thread, they seem to be making progress on the root problem of the write issue to NAS devices in samba- bugs# 5953 (link at the top of the page). -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai & Thierry: Volker Lendecke's patch seems to have done the trick! Both a write using an smbclient 'put' as well as a drag and drop via Nautilus now work as expected. The visual side effect in Nautilus I noted five messages above is still present but since it doesn't seem to have a bearing on file writing functionality to the NAS I think it can be ignored for now. Using 'get' in smbclient continues to work just fine as well. Good work! And Happy Holidays to all... -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361936] Re: Xorg crashed with SIGSEGV in nis_print_group_entry()
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/25507490/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25507491/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/25507492/Disassembly.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/25507493/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/25507494/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/25507495/LsPci.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/25507496/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/25507497/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/25507498/Registers.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/25507499/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/25507500/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/25507501/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/25507502/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/25507503/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/25507504/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/25507505/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/25507506/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/25507507/xkbcomp.txt ** Visibility changed to: Public -- Xorg crashed with SIGSEGV in nis_print_group_entry() https://bugs.launchpad.net/bugs/361936 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
I hate to be wet blanket, but I still have problems with samba/smbfs under Intrepid. I installed the samba files from Thierry's ppa repository. Nautilus indeed now lets me see and list the contents of my Iomega 500 GB Home Network Hard Drive and copy files from the drive to my Intrepid desktop. However, I can't write any files to the drive using Nautilus and SMB/CIFS or via ftp. I tried using smbclient in a terminal to "put" a test file onto the NAS drive and this is the output: [EMAIL PROTECTED]:~$ smbclient //192.168.0.198/ubuntu Enter ross's password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/test.file test.file Error writing file: ERRHRD - 39 putting file /home/ross/Desktop/test.file as \test.file Receiving SMB: Server stopped responding Call returned zero bytes (EOF) closing remote file \test.file smb: \> The same test under Hardy from a laptop results in this successful output: [EMAIL PROTECTED]:~$ smbclient //192.168.0.198/ubuntu Password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/test.file test.file putting file /home/ross/Desktop/test.file as \test.file (135.9 kb/s) (average 135.9 kbs) smb: \> So something is still wrong with Samba, at least on my Intrepid desktop. I am going to revert back to release Samba package for Intrepid and see what smbclient does and see if I can at least get ftp to the NAS working again. Any thoughts? BTW, the Nautilus error that gets thrown up when I try to write a file with the new Samba installed is: Error while copying "test.file". There was an error copying the file into smb://192.168.0.198/ubuntu/. V Show more details No space left on device. Maybe that is how Nautilus interprets ERRHRD -39 ? The NAS disk is 500GB with lots of room. Ideas? -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
OK, attached are some files. First a pdf file showing how my network is laid out (1 picture worth 1000 words etc.). Next is a text file of the network capture on eth0 between my Linux comp (ubuntu-test) at ip 192.168.0.100 and my IOmega 500 GB NAS aka "Home Network Hard Drive" via a DLink 615 router. The IOmega NAS is at 192.168.0.195. I used Wireshark for the capture. The last file is the same information but in the Wireshark proprietary format. I am using Samba 2:3.2.3-1ubuntu3.3. I tried to connect to smb://192.168.0.195/PUBLIC/ from Nautilus and it momentarily connects but then Nautilus reverts to displaying my home folder as previous posters have mentioned. The IOmega NAS uses an embedded Linux server of some kind to serve requests. ftp works OK. ** Attachment added: "Network.pdf" http://launchpadlibrarian.net/20394588/Network.pdf -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
** Attachment added: "wiresharkdmp.txt" http://launchpadlibrarian.net/20394606/wiresharkdmp.txt -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
** Attachment added: "wiresharkdmp" http://launchpadlibrarian.net/20394611/wiresharkdmp -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361936] Re: Xorg crashed with SIGSEGV in nis_print_group_entry()
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/25507490/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25507491/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/25507492/Disassembly.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/25507493/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/25507494/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/25507495/LsPci.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/25507496/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/25507497/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/25507498/Registers.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/25507499/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/25507500/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/25507501/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/25507502/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/25507503/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/25507504/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/25507505/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/25507506/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/25507507/xkbcomp.txt ** Visibility changed to: Public -- Xorg crashed with SIGSEGV in nis_print_group_entry() https://bugs.launchpad.net/bugs/361936 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Replying to Christian Perrier & Daniel Eckl: Sorry guys, I didn't mean to sound like I was recommending that everyone lock in Thierry's ppa Samba patches without the most recent security fixes. It is a balance between usability and security and in my specific case the usability aspect trumps the security one. I will check out any new updates as they are made available from Intrepid - Updates but if they break my NAS access I will go back to the ppa fixes - I need a functional NAS and I don't want the fuss of going back to Ubuntu 8.04 to get it. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Ditto for me as well - new ppa version working OK as far as I can tell. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Christian: I installed your packages with the patches for Debian in Ubuntu 8.10 using the Synaptic front end for apt without any problems. I did not change my smb.conf file. The following tests to my IOmega 500 GB Home Network Harddrive (NAS) worked without any problems. 1. Created a test file "test.txt" and using smbclient via a terminal "put" the file into the /public folder of the NAS. 2. Using smbclient, used the "get" command to retrieve "test.txt" and rename it and put it on my desktop as "testret.txt". 3. Using Nautilus under the Gnome desktop opened (mounted) the /public folder on the NAS and dragged the "test.txt" file into it. 4. Deleted the "test.txt" file from the NAS via the Nautilus window. 5. Copied a 700.1 MB avi file from the /public folder of the NAS to the Gnome desktop via Nautilus "drag & drop". All these tests worked OK. I will keep your Samba version for a couple of days to give it some more of a workout, but so far it seems to work the same as the one in Thierry's latest ppa for Ubuntu. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
The latest official Ubuntu Samba update regresses the one in Thierry's ppa repository. I used Synaptic Package Manager to force the Samba packages back to the ones from Thierry's ppa and then used Synaptic again to lock those versions so they won't be "upgraded" via Intrepid- Updates again. You might want to do the same. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
If anyone is still following this thread, they seem to be making progress on the root problem of the write issue to NAS devices in samba- bugs# 5953 (link at the top of the page). -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai & Thierry: Volker Lendecke's patch seems to have done the trick! Both a write using an smbclient 'put' as well as a drag and drop via Nautilus now work as expected. The visual side effect in Nautilus I noted five messages above is still present but since it doesn't seem to have a bearing on file writing functionality to the NAS I think it can be ignored for now. Using 'get' in smbclient continues to work just fine as well. Good work! And Happy Holidays to all... -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Thierry and Kai: Preliminary tests with the most recent patch (2:3.2.3-1ubuntu3.4~ppa3) of samba shows the following: Read access to my NAS works as expected in Nautilus and read access using smclient in a terminal works. However, a put access (ie write access) using smbclient still returns an ERRHD -39 error as seen in the message below. r...@ubuntu-test:~$ smbclient //192.168.0.195/public Enter ross's password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/disk_layout.png disk_layout.png Error writing file: ERRHRD - 39 putting file /home/ross/Desktop/disk_layout.png as \disk_layout.png Receiving SMB: Server stopped responding Call returned zero bytes (EOF) closing remote file \disk_layout.png smb: \> Also, attempting a write access by dragging a file into the smb:// Nautilus window generates the disk full error message as seen in the attachment. In other words, the latest patch has produced about the same result as the 2:3.2.3-1ubuntu3.4~ppa2 patch. What is common to both smbclient write access and Nautilus write access during a write to a NAS device? Is there any other capture I can do that might help to pinpoint that area? Any idea what ERRHRD -39 might point towards? So, in summary, with the latest patch, read access is OK, write access is still FUBAR. ** Attachment added: "error.png" http://launchpadlibrarian.net/20441556/error.png -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Tomek's results are interesting, I will have to see if I get the same effect. I tried something a little different. I uninstalled all the Samba packages except for libsmbclient and libwbclient0. Removal of either of these packages would also result in the removal of 17-20 other packages on my system, including Nautilus, that depend on these libraries so they have to be left in place. After removing all the Samba packages I could I tried to write to the NAS from Nautilus by dragging and dropping a file and I got the same error as before about the disk being full (see my previous message). Of course, since I had uninstalled smbclient, I couldn't run a test from a terminal. My hunch is that the root of the problem is in either the libsmbclient or libwbclient0 libraries. I might try to do a "dpkg -i force-downgrade" for the whole Samba suite to the Hardy version packages just to see what happens (my guess is that it will break something so I'll have to set up an experimental system to play on). In any event, I will reinstall the Samba packages and see if I can replicate Tomek's results. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
OK. I repeated Tomek's smbclient tests and got the same results as he did. I also noticed as Tomek did that smb: \> ls *.txt list all files, as does smb: \> ls *.* and smb: \> ls * and smb : \> ls In other words it seems that if the "*" character is the first one after the smb "ls" (list) command, it produces the same result as an "ls" command with no parameters. Is this normal parsing behaviour for smbclient? I will have to test this out on my Hardy system. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
I can concur with Kai Blin re: the ls command parsing behaviour in smbclient. I tested the smbclient ls command on a working Hardy system against the same IOmega NAS that is giving me problems (under Intrepid) and it produces the same results, so I don't think that it is related to the ERRHRD -39 problem. All I know about the embedded server in the IOmega NAS is that it is some kind of linux server. The embedded linux on the NAS also handles some other "slight of hand" such as transparently breaking files larger than 4 GB into smaller pieces. It does this because it only will work as a NAS if its hard drive is formatted as FAT32. IOmega claims that FAT32 gives it the broadest range of compatability since Windows, Mac OS and Linux/Unix can all read and write that format. The NAS also has a local USB2 port, as well as a 10/100 ethernet port, so the embedded linux must have a fairly complete communication suite. Thierry, would it help if I set my NAS up in a DMZ off my router so that it is exposed to the great unwashed internet? Maybe you would be able to test against it then? I'd have to experiment a bit to see what IP address it would end up with so you could access it via smb, but 'm willing to give it a try. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
For what it is worth, write access to my IOmega NAS using WinXP in a virtual machine environment on my Linux box works just fine. See attached screen shot which shows the result of having just "dragged & dropped" a file called bookmarks.html into the NAS window. This definitely seems to point to a Samba regression of some kind as Thierry Carrez has suggested. I mean when WinXP works with an embedded linux Samba in the NAS but Ubuntu Intrepid doesn't, something "just ain't right". :-) Richard Wooding, your SSH port forwarding idea might work better than my DMZ one since I can't figure out how to get around the private address range (192.168.0.xxx) for the NAS when it is exposed to the internet. Maybe some kind of virtual server and port forwarding arrangement in my router would work? I'm getting out of my networking depth here... ** Attachment added: "Screenshot.png" http://launchpadlibrarian.net/20473139/Screenshot.png -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai Blin: I should be able to do those traces using Wireshark since I have both Hardy and Intrepid installed on two different machines. Does it matter if the Hardy install is via wireless to the router? I shouldn't think so. One other tidbit about the IOmega NAS from their brief technical spec they say that Linux must use Samba 3 or later. This does suggest that the NAS also uses a version of Samba 3. One more test I just completed was to revert samba-common to version 3.0 .28a-1ubuntu4.7 and smbclient to version 3.0.28a-1ubuntu4.7 which are the Hardy versions for those two packages. Doing this allowed an smbclient "put" to the NAS to work correctly but did not fix write access via Nautilus. Unfortunately I couldn't revert nautilus-share and libsmbclient because of package dependency issues. I have reinstalled Thierry's latest ppa version of the Samba packages so I will use those for the 3.2 trace and the Hardy install for the 3.0 trace. I'll have the traces done by tomorrow. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: Here are the two traces you requested. The first trace, sam_cap3.0, is from the wlan0 interface of my laptop with Hardy installed and shows a successful attempt to write a small file, text2.txt, using Nautilus and a drag and drop of the file from the Desktop into the open Nautilus folder of //192.168.0.195/public (the NAS address). The second capture, sam_cap3.2, attached in the next message, is an unsuccessful attempt to write the same file, text2.txt, from the Desktop of my main computer, with Intrepid installed, into the open Nautilus folder of //192.168.0.195/public using the same drag and drop procedure as above. The interface in this case is eth0 since my main computer is hard wired into the router. Both traces are in the pcap format that you want and were taken using Wireshark. I could tray and pry out the Samba version in the NAS from IOmega tech support, although I rate my chances of success as about the same as a snowball's chance in Hell... I defer to your much deeper and more comprehensive understanding of Samba. ** Attachment added: "sam_cap3.0" http://launchpadlibrarian.net/20495242/sam_cap3.0 -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: The second trace. ** Attachment added: "sam_cap3.2" http://launchpadlibrarian.net/20495250/sam_cap3.2 -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Thierry: Can you bulid a new package in your PPA for Intrepid with this latest patch from Kai? I'll test ASAP once the package is ready. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: The patch does not appear to have changed the behaviour from the previous patch. An smbclient "put" of a file from a terminal still results in the ERRHRD -39 error message (after doing a successful "ls" first) and a Nautilus "drag and drop" of a file from the Desktop into the open NAS folder still results in the same "No space left on device" error message as noted by ^_Pepe_^ in the previous message. I've attached another Wireshark trace of the attempt to write the file "Test2.txt" from the Desktop into the NAS folder //192.168.0.195/public using Nautilus. The second Wireshark trace, in the following message (I can't seem to attach more than one file to a message in Launchpad) is the same drag and drop type of write but from the desktop of the virtual WinXP Pro SP3 into //192.168.0.195/public for comparison purposes. There is one other visual oddity that I have noticed that may or may not be a clue to something. When I have mounted the NAS folder //192.168.0.195/public on my Desktop and I select the folder using a right mouse button click, the dialog window that opens up shows the entry "Paste into Folder" occasionally flickering from greyed out status to selectable and then back to greyed out. ^_Pepe_^, do you see that as well? I checked the same thing out using Smaba 3.0 instead of Samba 3.2 and the "Paste into Folder" flickering from inactive to active doesn't occur. It is almost like something is trying automatically activate the "Paste into Folder" function, fails, waits and then tries again and again. ** Attachment added: "cap_fail_wrt.pcap" http://launchpadlibrarian.net/20582264/cap_fail_wrt.pcap -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: The WinXP SP3 trace for reference. Same file name, text2.txt, and NAS address //192.168.0.195/public ** Attachment added: "winxpsp3_cap.pcap" http://launchpadlibrarian.net/20582319/winxpsp3_cap.pcap -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 361936] Re: Xorg crashed with SIGSEGV in nis_print_group_entry()
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/25507490/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/25507491/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/25507492/Disassembly.txt ** Attachment added: "LsHal.txt" http://launchpadlibrarian.net/25507493/LsHal.txt ** Attachment added: "LsMod.txt" http://launchpadlibrarian.net/25507494/LsMod.txt ** Attachment added: "LsPci.txt" http://launchpadlibrarian.net/25507495/LsPci.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/25507496/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/25507497/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/25507498/Registers.txt ** Attachment added: "XorgConf.txt" http://launchpadlibrarian.net/25507499/XorgConf.txt ** Attachment added: "XorgLog.txt" http://launchpadlibrarian.net/25507500/XorgLog.txt ** Attachment added: "XorgLogOld.txt" http://launchpadlibrarian.net/25507501/XorgLogOld.txt ** Attachment added: "Xrandr.txt" http://launchpadlibrarian.net/25507502/Xrandr.txt ** Attachment added: "glxinfo.txt" http://launchpadlibrarian.net/25507503/glxinfo.txt ** Attachment added: "setxkbmap.txt" http://launchpadlibrarian.net/25507504/setxkbmap.txt ** Attachment added: "system.txt" http://launchpadlibrarian.net/25507505/system.txt ** Attachment added: "xdpyinfo.txt" http://launchpadlibrarian.net/25507506/xdpyinfo.txt ** Attachment added: "xkbcomp.txt" http://launchpadlibrarian.net/25507507/xkbcomp.txt ** Visibility changed to: Public -- Xorg crashed with SIGSEGV in nis_print_group_entry() https://bugs.launchpad.net/bugs/361936 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Thierry and Kai: Preliminary tests with the most recent patch (2:3.2.3-1ubuntu3.4~ppa3) of samba shows the following: Read access to my NAS works as expected in Nautilus and read access using smclient in a terminal works. However, a put access (ie write access) using smbclient still returns an ERRHD -39 error as seen in the message below. r...@ubuntu-test:~$ smbclient //192.168.0.195/public Enter ross's password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/disk_layout.png disk_layout.png Error writing file: ERRHRD - 39 putting file /home/ross/Desktop/disk_layout.png as \disk_layout.png Receiving SMB: Server stopped responding Call returned zero bytes (EOF) closing remote file \disk_layout.png smb: \> Also, attempting a write access by dragging a file into the smb:// Nautilus window generates the disk full error message as seen in the attachment. In other words, the latest patch has produced about the same result as the 2:3.2.3-1ubuntu3.4~ppa2 patch. What is common to both smbclient write access and Nautilus write access during a write to a NAS device? Is there any other capture I can do that might help to pinpoint that area? Any idea what ERRHRD -39 might point towards? So, in summary, with the latest patch, read access is OK, write access is still FUBAR. ** Attachment added: "error.png" http://launchpadlibrarian.net/20441556/error.png -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Tomek's results are interesting, I will have to see if I get the same effect. I tried something a little different. I uninstalled all the Samba packages except for libsmbclient and libwbclient0. Removal of either of these packages would also result in the removal of 17-20 other packages on my system, including Nautilus, that depend on these libraries so they have to be left in place. After removing all the Samba packages I could I tried to write to the NAS from Nautilus by dragging and dropping a file and I got the same error as before about the disk being full (see my previous message). Of course, since I had uninstalled smbclient, I couldn't run a test from a terminal. My hunch is that the root of the problem is in either the libsmbclient or libwbclient0 libraries. I might try to do a "dpkg -i force-downgrade" for the whole Samba suite to the Hardy version packages just to see what happens (my guess is that it will break something so I'll have to set up an experimental system to play on). In any event, I will reinstall the Samba packages and see if I can replicate Tomek's results. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
OK. I repeated Tomek's smbclient tests and got the same results as he did. I also noticed as Tomek did that smb: \> ls *.txt list all files, as does smb: \> ls *.* and smb: \> ls * and smb : \> ls In other words it seems that if the "*" character is the first one after the smb "ls" (list) command, it produces the same result as an "ls" command with no parameters. Is this normal parsing behaviour for smbclient? I will have to test this out on my Hardy system. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
I can concur with Kai Blin re: the ls command parsing behaviour in smbclient. I tested the smbclient ls command on a working Hardy system against the same IOmega NAS that is giving me problems (under Intrepid) and it produces the same results, so I don't think that it is related to the ERRHRD -39 problem. All I know about the embedded server in the IOmega NAS is that it is some kind of linux server. The embedded linux on the NAS also handles some other "slight of hand" such as transparently breaking files larger than 4 GB into smaller pieces. It does this because it only will work as a NAS if its hard drive is formatted as FAT32. IOmega claims that FAT32 gives it the broadest range of compatability since Windows, Mac OS and Linux/Unix can all read and write that format. The NAS also has a local USB2 port, as well as a 10/100 ethernet port, so the embedded linux must have a fairly complete communication suite. Thierry, would it help if I set my NAS up in a DMZ off my router so that it is exposed to the great unwashed internet? Maybe you would be able to test against it then? I'd have to experiment a bit to see what IP address it would end up with so you could access it via smb, but 'm willing to give it a try. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
For what it is worth, write access to my IOmega NAS using WinXP in a virtual machine environment on my Linux box works just fine. See attached screen shot which shows the result of having just "dragged & dropped" a file called bookmarks.html into the NAS window. This definitely seems to point to a Samba regression of some kind as Thierry Carrez has suggested. I mean when WinXP works with an embedded linux Samba in the NAS but Ubuntu Intrepid doesn't, something "just ain't right". :-) Richard Wooding, your SSH port forwarding idea might work better than my DMZ one since I can't figure out how to get around the private address range (192.168.0.xxx) for the NAS when it is exposed to the internet. Maybe some kind of virtual server and port forwarding arrangement in my router would work? I'm getting out of my networking depth here... ** Attachment added: "Screenshot.png" http://launchpadlibrarian.net/20473139/Screenshot.png -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai Blin: I should be able to do those traces using Wireshark since I have both Hardy and Intrepid installed on two different machines. Does it matter if the Hardy install is via wireless to the router? I shouldn't think so. One other tidbit about the IOmega NAS from their brief technical spec they say that Linux must use Samba 3 or later. This does suggest that the NAS also uses a version of Samba 3. One more test I just completed was to revert samba-common to version 3.0 .28a-1ubuntu4.7 and smbclient to version 3.0.28a-1ubuntu4.7 which are the Hardy versions for those two packages. Doing this allowed an smbclient "put" to the NAS to work correctly but did not fix write access via Nautilus. Unfortunately I couldn't revert nautilus-share and libsmbclient because of package dependency issues. I have reinstalled Thierry's latest ppa version of the Samba packages so I will use those for the 3.2 trace and the Hardy install for the 3.0 trace. I'll have the traces done by tomorrow. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: Here are the two traces you requested. The first trace, sam_cap3.0, is from the wlan0 interface of my laptop with Hardy installed and shows a successful attempt to write a small file, text2.txt, using Nautilus and a drag and drop of the file from the Desktop into the open Nautilus folder of //192.168.0.195/public (the NAS address). The second capture, sam_cap3.2, attached in the next message, is an unsuccessful attempt to write the same file, text2.txt, from the Desktop of my main computer, with Intrepid installed, into the open Nautilus folder of //192.168.0.195/public using the same drag and drop procedure as above. The interface in this case is eth0 since my main computer is hard wired into the router. Both traces are in the pcap format that you want and were taken using Wireshark. I could tray and pry out the Samba version in the NAS from IOmega tech support, although I rate my chances of success as about the same as a snowball's chance in Hell... I defer to your much deeper and more comprehensive understanding of Samba. ** Attachment added: "sam_cap3.0" http://launchpadlibrarian.net/20495242/sam_cap3.0 -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: The second trace. ** Attachment added: "sam_cap3.2" http://launchpadlibrarian.net/20495250/sam_cap3.2 -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Thierry: Can you bulid a new package in your PPA for Intrepid with this latest patch from Kai? I'll test ASAP once the package is ready. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: The patch does not appear to have changed the behaviour from the previous patch. An smbclient "put" of a file from a terminal still results in the ERRHRD -39 error message (after doing a successful "ls" first) and a Nautilus "drag and drop" of a file from the Desktop into the open NAS folder still results in the same "No space left on device" error message as noted by ^_Pepe_^ in the previous message. I've attached another Wireshark trace of the attempt to write the file "Test2.txt" from the Desktop into the NAS folder //192.168.0.195/public using Nautilus. The second Wireshark trace, in the following message (I can't seem to attach more than one file to a message in Launchpad) is the same drag and drop type of write but from the desktop of the virtual WinXP Pro SP3 into //192.168.0.195/public for comparison purposes. There is one other visual oddity that I have noticed that may or may not be a clue to something. When I have mounted the NAS folder //192.168.0.195/public on my Desktop and I select the folder using a right mouse button click, the dialog window that opens up shows the entry "Paste into Folder" occasionally flickering from greyed out status to selectable and then back to greyed out. ^_Pepe_^, do you see that as well? I checked the same thing out using Smaba 3.0 instead of Samba 3.2 and the "Paste into Folder" flickering from inactive to active doesn't occur. It is almost like something is trying automatically activate the "Paste into Folder" function, fails, waits and then tries again and again. ** Attachment added: "cap_fail_wrt.pcap" http://launchpadlibrarian.net/20582264/cap_fail_wrt.pcap -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai: The WinXP SP3 trace for reference. Same file name, text2.txt, and NAS address //192.168.0.195/public ** Attachment added: "winxpsp3_cap.pcap" http://launchpadlibrarian.net/20582319/winxpsp3_cap.pcap -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
I hate to be wet blanket, but I still have problems with samba/smbfs under Intrepid. I installed the samba files from Thierry's ppa repository. Nautilus indeed now lets me see and list the contents of my Iomega 500 GB Home Network Hard Drive and copy files from the drive to my Intrepid desktop. However, I can't write any files to the drive using Nautilus and SMB/CIFS or via ftp. I tried using smbclient in a terminal to "put" a test file onto the NAS drive and this is the output: [EMAIL PROTECTED]:~$ smbclient //192.168.0.198/ubuntu Enter ross's password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/test.file test.file Error writing file: ERRHRD - 39 putting file /home/ross/Desktop/test.file as \test.file Receiving SMB: Server stopped responding Call returned zero bytes (EOF) closing remote file \test.file smb: \> The same test under Hardy from a laptop results in this successful output: [EMAIL PROTECTED]:~$ smbclient //192.168.0.198/ubuntu Password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/test.file test.file putting file /home/ross/Desktop/test.file as \test.file (135.9 kb/s) (average 135.9 kbs) smb: \> So something is still wrong with Samba, at least on my Intrepid desktop. I am going to revert back to release Samba package for Intrepid and see what smbclient does and see if I can at least get ftp to the NAS working again. Any thoughts? BTW, the Nautilus error that gets thrown up when I try to write a file with the new Samba installed is: Error while copying "test.file". There was an error copying the file into smb://192.168.0.198/ubuntu/. V Show more details No space left on device. Maybe that is how Nautilus interprets ERRHRD -39 ? The NAS disk is 500GB with lots of room. Ideas? -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
OK, attached are some files. First a pdf file showing how my network is laid out (1 picture worth 1000 words etc.). Next is a text file of the network capture on eth0 between my Linux comp (ubuntu-test) at ip 192.168.0.100 and my IOmega 500 GB NAS aka "Home Network Hard Drive" via a DLink 615 router. The IOmega NAS is at 192.168.0.195. I used Wireshark for the capture. The last file is the same information but in the Wireshark proprietary format. I am using Samba 2:3.2.3-1ubuntu3.3. I tried to connect to smb://192.168.0.195/PUBLIC/ from Nautilus and it momentarily connects but then Nautilus reverts to displaying my home folder as previous posters have mentioned. The IOmega NAS uses an embedded Linux server of some kind to serve requests. ftp works OK. ** Attachment added: "Network.pdf" http://launchpadlibrarian.net/20394588/Network.pdf -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
** Attachment added: "wiresharkdmp.txt" http://launchpadlibrarian.net/20394606/wiresharkdmp.txt -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
** Attachment added: "wiresharkdmp" http://launchpadlibrarian.net/20394611/wiresharkdmp -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Replying to Christian Perrier & Daniel Eckl: Sorry guys, I didn't mean to sound like I was recommending that everyone lock in Thierry's ppa Samba patches without the most recent security fixes. It is a balance between usability and security and in my specific case the usability aspect trumps the security one. I will check out any new updates as they are made available from Intrepid - Updates but if they break my NAS access I will go back to the ppa fixes - I need a functional NAS and I don't want the fuss of going back to Ubuntu 8.04 to get it. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Ditto for me as well - new ppa version working OK as far as I can tell. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Christian: I installed your packages with the patches for Debian in Ubuntu 8.10 using the Synaptic front end for apt without any problems. I did not change my smb.conf file. The following tests to my IOmega 500 GB Home Network Harddrive (NAS) worked without any problems. 1. Created a test file "test.txt" and using smbclient via a terminal "put" the file into the /public folder of the NAS. 2. Using smbclient, used the "get" command to retrieve "test.txt" and rename it and put it on my desktop as "testret.txt". 3. Using Nautilus under the Gnome desktop opened (mounted) the /public folder on the NAS and dragged the "test.txt" file into it. 4. Deleted the "test.txt" file from the NAS via the Nautilus window. 5. Copied a 700.1 MB avi file from the /public folder of the NAS to the Gnome desktop via Nautilus "drag & drop". All these tests worked OK. I will keep your Samba version for a couple of days to give it some more of a workout, but so far it seems to work the same as the one in Thierry's latest ppa for Ubuntu. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
The latest official Ubuntu Samba update regresses the one in Thierry's ppa repository. I used Synaptic Package Manager to force the Samba packages back to the ones from Thierry's ppa and then used Synaptic again to lock those versions so they won't be "upgraded" via Intrepid- Updates again. You might want to do the same. -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
If anyone is still following this thread, they seem to be making progress on the root problem of the write issue to NAS devices in samba- bugs# 5953 (link at the top of the page). -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Kai & Thierry: Volker Lendecke's patch seems to have done the trick! Both a write using an smbclient 'put' as well as a drag and drop via Nautilus now work as expected. The visual side effect in Nautilus I noted five messages above is still present but since it doesn't seem to have a bearing on file writing functionality to the NAS I think it can be ignored for now. Using 'get' in smbclient continues to work just fine as well. Good work! And Happy Holidays to all... -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 264943] Re: gvfsd-smb crashed with SIGSEGV in strlen()
Thierry and Kai: Preliminary tests with the most recent patch (2:3.2.3-1ubuntu3.4~ppa3) of samba shows the following: Read access to my NAS works as expected in Nautilus and read access using smclient in a terminal works. However, a put access (ie write access) using smbclient still returns an ERRHD -39 error as seen in the message below. r...@ubuntu-test:~$ smbclient //192.168.0.195/public Enter ross's password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/disk_layout.png disk_layout.png Error writing file: ERRHRD - 39 putting file /home/ross/Desktop/disk_layout.png as \disk_layout.png Receiving SMB: Server stopped responding Call returned zero bytes (EOF) closing remote file \disk_layout.png smb: \> Also, attempting a write access by dragging a file into the smb:// Nautilus window generates the disk full error message as seen in the attachment. In other words, the latest patch has produced about the same result as the 2:3.2.3-1ubuntu3.4~ppa2 patch. What is common to both smbclient write access and Nautilus write access during a write to a NAS device? Is there any other capture I can do that might help to pinpoint that area? Any idea what ERRHRD -39 might point towards? So, in summary, with the latest patch, read access is OK, write access is still FUBAR. ** Attachment added: "error.png" http://launchpadlibrarian.net/20441556/error.png -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
