** Changed in: samba
Importance: Unknown = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
https://bugs.launchpad.net/bugs/264943
Title:
gvfsd-smb crashed with SIGSEGV in strlen()
--
Ubuntu-server-bugs
** Changed in: samba
Importance: Unknown = Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/264943
Title:
gvfsd-smb crashed with SIGSEGV in strlen()
--
ubuntu-bugs mailing list
This bug was fixed in the package samba - 2:3.2.3-1ubuntu3.5
---
samba (2:3.2.3-1ubuntu3.5) intrepid-proposed; urgency=low
* debian/patches/fix-libnss-sigabrt.patch: Fix sigabort when using
wins client. Taken from upstream. (LP: #286119)
* debian/patches/ Fix sigsev when
This bug was fixed in the package samba - 2:3.2.3-1ubuntu3.5
---
samba (2:3.2.3-1ubuntu3.5) intrepid-proposed; urgency=low
* debian/patches/fix-libnss-sigabrt.patch: Fix sigabort when using
wins client. Taken from upstream. (LP: #286119)
* debian/patches/ Fix sigsev when
** Changed in: samba (Debian)
Status: Unknown = 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.
--
** Changed in: samba (Debian)
Status: Unknown = 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hi,
This is my first post to this bug so let me summarize my situation:
-NAS ViPower (Software/Hardware Pleiades - firmware NAS-BASIC48B6, LOADER
70,2007-8-15)
-I have same problem with 8.10
Now I tested intrepid-proposed package and now it is working again in
nautilus and smbclient. Guys,
Hi,
I forgot to mention about my test environment. I am using Ubuntu version 8.10
(64bits) on a AMD Turion X2.
The package was installed from intrepid-propose and test did with ViPower NAS
transferring (to and from) a file from about 4GB over wired network and another
file (~2MB) over wireless
Thanks ! I guess we are done with verification here, fix publication is
waiting on confirmation that bug 286119 is also fixed by the update.
--
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
Hi,
This is my first post to this bug so let me summarize my situation:
-NAS ViPower (Software/Hardware Pleiades - firmware NAS-BASIC48B6, LOADER
70,2007-8-15)
-I have same problem with 8.10
Now I tested intrepid-proposed package and now it is working again in
nautilus and smbclient. Guys,
Hi,
I forgot to mention about my test environment. I am using Ubuntu version 8.10
(64bits) on a AMD Turion X2.
The package was installed from intrepid-propose and test did with ViPower NAS
transferring (to and from) a file from about 4GB over wired network and another
file (~2MB) over wireless
Thanks ! I guess we are done with verification here, fix publication is
waiting on confirmation that bug 286119 is also fixed by the update.
--
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
Hi everyone.
I've installed a 9.04 Alpha-3 version onto a VMWare Windows-based-
machine, and my NAS disk worked fine with the software just out-of-the-
box.
Good news!!!
Regards,
^_Pepe_^
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this
Hi everyone.
I've installed a 9.04 Alpha-3 version onto a VMWare Windows-based-
machine, and my NAS disk worked fine with the software just out-of-the-
box.
Good news!!!
Regards,
^_Pepe_^
--
gvfsd-smb crashed with SIGSEGV in strlen()
https://bugs.launchpad.net/bugs/264943
You received this
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,
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,
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
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
** 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.
--
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
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
Bugs, which is
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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()
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 received
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
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()
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 received
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
Bugs, which is subscribed to
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
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
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()
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
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()
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
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()
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
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
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
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()
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
Bugs, which is subscribed
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
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
Quoting Thierry Carrez (thierry.car...@ubuntu.com):
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
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
Quoting rossjenkins (rossawjenk...@gmail.com):
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
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
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
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
Quoting Thierry Carrez (thierry.car...@ubuntu.com):
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
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...
Same thing for me, I am sorry to say.
Packard Bell Netstore 3500, 8.10 amd64
Similar behaviour as ever:
Nautilus bounces back to /home/user
smbclient on the commandline gives errormessages.
i.e.
tree connect failed: ERRSRV - ERRaccess (The requester does not have
the necessary access rights
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
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
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...
Same thing for me, I am sorry to say.
Packard Bell Netstore 3500, 8.10 amd64
Similar behaviour as ever:
Nautilus bounces back to /home/user
smbclient on the commandline gives errormessages.
i.e.
tree connect failed: ERRSRV - ERRaccess (The requester does not have
the necessary access rights
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
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
For me too,
Great work
Thanks
Willem
Op maandag 29-12-2008 om 01:56 uur [tijdzone +], schreef tomek.bury:
Works for me too.
Good work!
Thanks,
Tomek
2008/12/28 ^_Pepe_^ jose.angel.fernandez.fre...@gmail.com
Hi everyone!
Worked for me, for read AND write into my
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
For me too,
Great work
Thanks
Willem
Op maandag 29-12-2008 om 01:56 uur [tijdzone +], schreef tomek.bury:
Works for me too.
Good work!
Thanks,
Tomek
2008/12/28 ^_Pepe_^ jose.angel.fernandez.fre...@gmail.com
Hi everyone!
Worked for me, for read AND write into my
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
Bugs, which is subscribed to Ubuntu.
--
Quoting Kai Blin (kai.blin+launch...@gmail.com):
This is now fixed in the Samba git trees, will be in the next 3.2.
bugfix release and in 3.3.0
Could you post the final patch ?
I think I could convince my co-maintainers and Debian release managers
to have this patch in Debian lenny while we
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
Works for me too.
Good work!
Thanks,
Tomek
2008/12/28 ^_Pepe_^ jose.angel.fernandez.fre...@gmail.com
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()
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
Bugs,
Works for me too.
Good work!
Thanks,
Tomek
2008/12/28 ^_Pepe_^ jose.angel.fernandez.fre...@gmail.com
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()
** 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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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
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
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
Bugs, which is subscribed to
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
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
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
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
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 still
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
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 still
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
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
Bugs, which is subscribed to
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
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
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
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
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.
--
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
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
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
Bugs, which is subscribed to
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
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
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
Bugs, which is subscribed to Ubuntu.
--
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
*.one of the suffixes ls
1 - 100 of 209 matches
Mail list logo
