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
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
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
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
ubu
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
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
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
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 U
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
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
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
Bugs, which is subscribed to Ubuntu.
--
** 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-b
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
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
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
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
** 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
** Attachm
@Steve,
Running Lucid Alpha 2 x86-64 with all the updates (as of Feb 12, 2010
00:30 EST) I get the splash screen OK but also get the freeze if I hit
the Enter key after entering my password. I'm not sure if anyone else
here has this config, but I am running Lucid as a Guest OS under Virtual
Box on
I can confirm that this bug still affects the video driver used within
Virtual Box as well. System is Lucid Alpha 3 running in a virtual
environment under Virtual Box 3.1.4 on a Karmic host system. The systems
are exactly the same as those seen with Nvidia proprietary drivers. GDM
restarts after hi
Oops, sentence above should have read "... symptoms are exactly the same
as those seen with Nvidia proprietary drivers."
--
Pressing key causes gdm to restart on VGA16FB system
https://bugs.launchpad.net/bugs/522692
You received this bug notification because you are a member of Ubuntu
Bugs, whic
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/32182823/BootDmesg.txt
** Attachment added: "CoreDump.gz"
http://launchpadlibrarian.net/32182824/CoreDump.gz
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/32182825/CurrentDmesg.txt
** Attachment
I started to get this bug (9.10 AMD 64) after the most recent updates on
November 4, 2009. The crash is reported right after I log on. I don't
remember what all the updates were unfortunately but I think Xsplash was
one of them. I'm not using Compiz, just Metacity with compositing turned
on.
--
s
Ditto for me running Karmic Beta AMD64 as guest in VirtualBox 3.06 on a
Jaunty 9.04 AMD64 host; 8 Gbyte ram, 2 Gbyte dedicated to Karmic guest.
If I open the Network Manager applet then use "Edit Connections...", and
select Auto eth0 for editing, I don't actually have to edit anything,
just hit the
I think this may be related to a much older bug report # 218906 which
was opened back in April of 2008 but never resolved. A work around that
was suggested then, and which I have used successfully through Jaunty,
Karmic and Lucid is to add the following line to the bottom of
/etc/modprobe.d/alsa-ba
29 matches
Mail list logo
