the crash is a libsmbclient one
** Changed in: samba (Ubuntu)
Sourcepackagename: gvfs => samba
--
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
Server Team, which is subscribed to samba in u
100% reproducable here.
** Changed in: samba (Ubuntu)
Status: New => Confirmed
--
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
Server Team, which is subscribed to samba in ubuntu.
-
I suspect bug 284572 is a duplicate of this bug.
--
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
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubu
Yes, it is.
But I'm not sure which way to merge them. Bug 284572 has most of the
data while this one has already 4 duplicates and seems to be the target
for automatically generated bug reports. Any suggestions?
Cheers,
Tomek
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.n
Marking bug 284572 as a duplicate of this one. tomek.bury: you can add a
comment here linking to the most relevant comments from the other bug.
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this bug notification because you are a member of Ubunt
Well, this bug causes crash in libsmbclient accessed through nautilus
while bug 284572 does the same through smbclient. The smbclient gives
some extra hints: weird domain/os/server - probably some parsing error,
info level 1 is, I guess, type of package received from landrive:
$ smbclient //nas/PU
I tracked down the problem to the following lines in "clilist.c" function
"interpret_long_filename".
Here the following lines causes that "finfo->name" contains a null-pointer (as
the function returns before setting finfo->name):
approx. line 90 of clilist.c (samba-3.2.5)
---
if (p + len + 1
Hi!
Same problem here with a Conceptronic CH3DNAS NAS disk. Please could
someone give a workaroud?
Thanks
^_Pepe_^
--
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
Server Team, which is sub
** Bug watch added: Debian Bug tracker #500129
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500129
** Also affects: samba (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500129
Importance: Unknown
Status: Unknown
--
gvfsd-smb crashed with SIGSEGV in strlen()
htt
Hi!
In https://bugs.launchpad.net/ubuntu/+source/samba/+bug/284572
(duplicate bug), someone indicates that with smbmount
sudo smbmount 192.168.1.102\\video video
it seem to work, but not in my case.
[EMAIL PROTECTED]:~$ sudo smbmount 192.168.1.11\\public donwload
mount error: can not ch
Following advice in comment 10, I rollbacked the changes made in
clilist.c and built a new package for Intrepid...
Could people affected by this bug test the samba-2:3.2.3-1ubuntu3.4~ppa1
package in my PPA:
https://launchpad.net/~tcarrez/+archive
and report success/failure/adverse side-effects.
I'm terribly sorry to ask some information about patch.
1st. Could you publish a mini (really mini) HowTo? Any to uninstall first???
2nd. Could you please what could kind side-effects are expected to appear, and
how to reverse samba situation to actual "as is". I guess that reinstalling
smbclien
I've upgraded all of my samba packages using the new versions from
https://launchpad.net/~tcarrez/+archive
but iit didn't work for me:
$ smbclient //nas/PUBLIC
Enter tomek's password:
Domain=[ȇ] OS=[] Server=[���]
smb: \> ls
Segmentation fault
Comparing to previous version the line:
cli_list_n
** Changed in: samba
Status: Unknown => Confirmed
--
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
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing
I'll do a simpler patch just removing the offset check Marcus talks
about in comment 10. Apparently the affected NAS use info level 1 (which
is usually used by OS/2) !? Stay tuned.
** Bug watch added: Samba Bugzilla #5942
https://bugzilla.samba.org/show_bug.cgi?id=5942
** Also affects: samba v
Please try samba - 2:3.2.3-1ubuntu3.4~ppa2 from
https://launchpad.net/~tcarrez/+archive
--
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
Server Team, which is subscribed to samba in ubuntu.
your samba from your ppa works well without crashing
--
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
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
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. How
I would be wary to remove the offset check. I'm not really into that
code, but removing it will break offsets when there actually is no name
in that Info1 struct. Can anybody provide a tcpdump/wireshark capture
file of a smb connection that causes mentioned segfault?
--
gvfsd-smb crashed with SIG
Kai Blin:
Removing the check is clearly not a permanent solution, I figured it could help
in pointing out where the problem is and maybe serve as band-aid for those
affected, waiting for the proper fix. Unfortunately I don't own the affected
hardware so I can't reproduce the problem, and I'm lef
should I capture packets for the broken samba or the one from your ppa
that works.
--
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
Server Team, which is subscribed to samba in ubuntu.
--
U
Hi all,
Here is a capture from my box, running Ubuntu Ibex, 2.6.27-9-generic #1 SMP
i686 GNU/Linux.
Samba is 3.2.3, using Iomega Network Hard Drive 350 GB with latest firmware. I
remember this worked with Gutsy, I believe the samba version was 3.0.something,
unfortunately can't remember what it
@Shawn: the one that fails, preferably.
--
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
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-serve
For what this is worth:
- I confirm it woked in 8.04 and is now broken after upgrade in 8.10
- I works in Debian Etch (3.0.24-6etch10) but is broken as well in
Debian Lenny (2:3.2.4-1)
- As already mentionned somewhere, mounting the device (mount -t cifs)
works, so if really needed there is a wo
I'll look into this some more tomorrow. This seems to be an issue
introduced in Samba 3.2.x. I should be able to write a test case using
the network trace.
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this bug notification because you are a mem
** Changed in: samba
Status: Confirmed => Invalid
--
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
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing
This is tracked in a different Samba bug.
** Changed in: samba
Bugwatch: Samba Bugzilla #5942 => Samba Bugzilla #5953
Status: Invalid => Unknown
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this bug notification because you are a m
** Changed in: samba
Status: Unknown => Confirmed
--
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
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing
Seems like Jeremy Allison pushed a fix for that to git on 2008-12-08
already.
However, the reporter of the samba bug is experiencing the same issues
as rossjenkins. I'll follow up on that.
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this bug
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 rout
** 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
Server Team, which is subscribed to samba
** 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
Server Team, which is subscribed to samba in ubunt
The pcap dump (i.e. the binary data, not the text file) was pretty much
what I needed. Thanks alot.
Could anyone try the attached patch on top of current v3-2-test git?
** Attachment added: "Fix offset check in interpret_long_filename"
http://launchpadlibrarian.net/20398252/bug_5953_fix.patch
I'll try it if you tell me how to do 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
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu-serv
Kai Blin: thanks for the patch, I'll build a new package in my PPA for
Intrepid with this patch in, for easier user testing.
--
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
Server Team, whic
samba - 2:3.2.3-1ubuntu3.4~ppa3 from
https://launchpad.net/~tcarrez/+archive is compiled with the patch from
Kai Blin on comment 33, for those interested in testing.
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this bug notification because you
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
Hi everyone.
same behavior as last comment with my Conceptronic NAS disk. with patch
(only smbclient and smbfs installed) I can now read, but not write.
Anyway it's a huge enhancement for me! :-D
Thanks for all.
^_Pepe_^
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net
Hm, our initial guess is that these NAS disks all run the same CIFS
server, which doesn't handle what our smbclient is sending and dies,
giving back a "disk full" error. It should be unrelated to the segfault
this bug is about, though. I'm still trying to contact the person who
initially added that
Hi,
I tested the latest patch (2:3.2.3-1ubuntu3.4~ppa3), my NAS is an Iomega
Home Network HD 500gb ( Previewed URL: http://is.gd/bQv1- ).
Reading of the hard disk is now working.
When writing I get a "No space left on device" error.
I can provide more details if necessary.
My NAS is firmware u
Iomega support have responded but seem to think this is only an Ubuntu
issue, which I doubt.
If there is a bug in there CIFS server which is preventing write access
I would love to be able to provide them with details so they can
produces a firmware upgrade for their drive.
--
gvfsd-smb crashed
I'm trying to get some informations from my landrive tech support. I've
provided them with the technical data they have requested (model HD9-U2LA based
on RDC R2882-G chip if anyone's interested) and waiting for a response.
As for the new samba packages:
1. reading seems to work fine now - I ca
I've just noticed that adding a parameter to 'ls' has quite interesting
results.
smb: \> ls *.txt
(lists all files)
smb: \> ls test.*
SUCCESS - 0 listing \test.*
smb: \> ls test.txt
cli_list_new: Error: unable to parse name from info level 1
cli_list_new: unable to parse name from info level 1
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 syst
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) com
The ls command in smbclient works just as expected against a Samba
server. I suspect that the server's handling of the list command is
broken, but I'd need a network trace of this. Ideally for a directory
that contains multiple files with multiple suffixes, running ls, ls
*. ls .* and ls ..
Howev
Could someone that can reproduce it post the ERRHRD - 39 error as a separate
bug ? I don't feel like posting a bug that I can 't even reproduce myself...
Note that the two bugs are very linked, since you can't see the second one
before the first one is fixed (and they should be fixed in the same
Well, you'd probably see the ERRHRD - 39 bug if you try to put a file
without doing an "ls" first, on a broken CIFS server. But anyway,
separate report for this, please. We can discuss if it's really
something that should be fixed in Samba that report ;)
A good way to get a working NAS box is to g
On my Iomega Home Network Harddrive 500gb NAS I experience the ERRHD 39
bug after applying the patch.
I would love to file a new bug report to have it looked at, but I need
some hand holding, in describing the error in the correct terms.
Especially since you have to first patch the first bug befor
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 p
Hear, hear Ross. I undoubtedly have a similar NAS.
Another option I can think of of is SSH forwarding some CIFS ports on my
NAS via a server I have in the United States. (In this way making the
ports publicly available).
This would allow the developers to test against by NAS.
Please get back to
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
Ok, seems like we're also tracking the write problem in the same Samba bug, so
I'd suggest we keep the discussion here after all. I can confirm that if this
worked with Samba 3.0 and works with Windows, there's a Samba bug we need to
fix. Could anyone get me a trace of Samba 3.2 trying to put a
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 the
** Changed in: samba
Status: Confirmed => In Progress
--
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
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs mail
As a short status update, especially for the Ubuntu packaging folks:
- A patch in Samba 3.2.6 fixes the crash bug, but does not correctly display
all the directories.
- The patch I posted, which fixes the display problem, has been pushed to the
v3-2-test branch and will be in the next 3.2. bugfix
Thanks for the update,
Since the put error affects the same range of NAS boxes as the crash, I'd
prefer to wait a little and see if we can fix both in the same update. Those
who quickly (and only) need read access to work can use the
2:3.2.3-1ubuntu3.4~ppa3 from my PPA.
--
gvfsd-smb crashed wi
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 /
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
Server Team, which is subscrib
Thanks for the traces, I'll have a look at them first thing 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
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-
Ok, it seems like we're misreporting the byte count in the WriteAndX
request, looking at a fix.
--
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
Server Team, which is subscribed to samba in u
Ok the difference I can see is that 3.2 adds a byte of null padding. The
changelog indicates that WinXP does that as well, but Samba 3.0 didn't
do this. So here's a patch that removes the null padding again. I can't
commit this patch just like that, but it should help pinpointing the
difference.
*
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
Serv
Here it is:
samba 2:3.2.3-1ubuntu3.4~ppa4 available for testing at
https://launchpad.net/~tcarrez/+archive
--
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
Server Team, which is subscribed t
Hi!
Unfortunately, write does not work, at least with my NAS (Conceptronic).
There's a different behaviour between ppa3 and ppa4: In ppa3, after
starting the "copy" command in Nautilus, automatically and "no disk
space" was shown, and now, there's a progress bar (with time remaining,
and so on...
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
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
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 notificati
This is a bit tricky to fix, as we're basically not doing anything
wrong. It seems like the TCP/IP stack and/or the SMB server on the NAS
box doesn't cope with fragmentation. But that's one layer below of our
control, and perfectly valid in TCP networking.
However, Samba developer Volker Lendecke
Here you go :)
samba 2:3.2.3-1ubuntu3.4~ppa5 available for testing at
https://launchpad.net/~tcarrez/+archive
--
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
Server Team, which is subscribe
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 f
** Changed in: samba
Status: In Progress => Fix Released
--
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
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server-bugs m
Hi everyone!
Worked for me, for read AND write into my Conceptronic NAS disk!
Good job guys!
Thanks for all to everyone
Regards
--
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
Server Tea
This is now fixed in the Samba git trees, will be in the next 3.2.
bugfix release and in 3.3.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
Server Team, which is subscribed to samba in ub
As requested by Christian, here's a patch for the v3-2-stable tree,
applies to both 3.2.5 and 3.2.6 without any problems.
** Attachment added: "Complete patch for segfault, visibility issue and write
issue."
http://launchpadlibrarian.net/20795250/bug_5953_complete.patch
--
gvfsd-smb crashed
darn, the samba update from Jan 05 (http://www.ubuntu.com/usn/USN-702-1)
overwrites Thierrys PPA :-S
So atm I can't tell if this patch fixes this problem with my Iomega Home
Network Harddrive, but I guess it would :}
I so hope this patch can be included into the normal ubuntu packages
soon...
--
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 mig
Ross, this would make your system more insecure, since Thierrys packages don't
include the security fixes for the USN mentioned in my comment above.
Maybe you still want to do the same, but when posting workarounds, you should
always mention the drawbacks.
--
gvfsd-smb crashed with SIGSEGV in s
The real solution would be to finally get this fix included in Ubuntu.
I'm not sure who's feeling responsible for Samba packages on the Ubuntu
side of things. Given that intrepid is on 3.2.3, the patch would have to
be backported anyway, so there's no need to wait for the next 3.2 bugfix
release.
> I'm aware that the write patch is kind of large, but at least the
segfault is an easy target.
Well, yes, but not anymore, the work has been done now..
Since Thierry already made version 3.2.3 packages with this fix included, the
Ubuntu Maintainers "just" need to take his patchset and include it
That's not what I'm talking about. the bigger the patches you pull in,
the bigger the risk of regressing other things that used to work. I
doubt Thierry's patches have been tested by many people not affected by
this bug. While I personally doubt there's a problem for standard
setups, I can understa
Well the patches are from the Samba developer Volker Lendecke, but for version
3.2.5 (or 3.2.6 or such) and have been backported to 3.2.3 by Thierry.
So you think that the backporting would cause regressions?
As I'm no developer, I have to cope with your opinion here, so thank you
for this info.
I'm kinda busy those days, but I'll refresh my PPA tomorrow with a
2:3.2.3-1ubuntu3.5~ppa1 that builds on the recent security release.
Concerning the official intrepid update, I'll file a SRU report and let
the ubuntu-sru powers decide if the fix is worth the regression risk, as
this is definitely
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 s
samba_3.2.3-1ubuntu3.5~ppa1 should be (if it builds) in my PPA in a few minutes
for those wanting to test it.
It's using the complete patch from Kai Blin posted on comment 76.
The SRU will be based on it if successful.
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bug
Used your new version now for about 1 hour and have not seen any problem so far.
Thank you so much for your work!
--
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
Server Team, which is subscr
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
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-serve
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 "t
Tried these packages as well and so far they are really working great.
I tried the following on my IOMega NAS:
Using the share with KDE's smb:// kio plugin, uploaded, downloaded, renamed,
deleted files from the share.
Using it with smbnetfs (based on fuse, it's using libsmbclient.so)
So far I foun
I have tried the smbclient and samba packages and everything seems to be
working great thanks.
I seem to get odd messages saying the connection does not exist but you click
on it a second time and off it goes.
I will try and be more precise if needed.
I now need to find out how I can make a samba
> I now need to find out how I can make a samba file system connection
as seamless as connecting to directory on the computer.
I mentioned smbnetfs above.
http://smbnetfs.sourceforge.net/
sudo apt-get install smbnetfs
man smbnetfs
Enjoy!
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bu
Hi everyone.
New patch tested in my Conceptronic NAS Disk (CH3DNAS).
it works perfectly.
[off topic] P.S.: Very interested in smbnetfs. I've installed it,
googled information so far, but I guess I need an example or a fool-
proof howto...
Regards,
^_Pepe_^
Spain
--
gvfsd-smb crashed with SIGS
I don't want to discuss this here since this is absolutely off-topic for this
bug. I will write you an email.
If anyone wants more infos about this, too, feel free to contact me.
https://launchpad.net/~daniel-eckl/+contactuser
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad
Accepted samba into intrepid-proposed, please test and give feedback
here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Tags added: verification-needed
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://b
Please fix ASAP in Jaunty. Thanks!
** Changed in: samba (Ubuntu Jaunty)
Assignee: (unassigned) => Chuck Short (zulcss)
** Changed in: samba (Ubuntu Intrepid)
Status: New => Fix Committed
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You receive
FWIW, this bug is fixed in Debian version 3.2.5-4, so a straightforward
merge should take care of it for jaunty.
--
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
Server Team, which is subscri
Hi all,
It works!
I've just disabled Thierry's ppa and installed samba related packages
from intrepid proposed repository - it's all yummy. I can read and write
to NAS drive.
Could anyone else check the intrepid-proposed version of samba?
Thanks,
Tomek
--
gvfsd-smb crashed with SIGSEGV in str
I can confirm that a first try works very well.
I will update in case I notice any flaws.
Thanks to all participants!
--
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
Server Team, which is s
** Tags added: verification-done
** Tags removed: verification-needed
--
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
Server Team, which is subscribed to samba in ubuntu.
--
Ubuntu-server
This bug was fixed in the package samba - 2:3.2.5-4ubuntu1
---
samba (2:3.2.5-4ubuntu1) jaunty; urgency=low
* Merge from Debian unstable, remaining changes:
+ debian/patches/VERSION.patch:
- setup SAMBA_VERSION_SUFFIX to Ubuntu.
+ debian/smb.conf:
- add "(Samba,
1 - 100 of 114 matches
Mail list logo
