(In reply to comment #94) > Is there a way to reproduce this crash without having a second computer?
I don't know... if you can tell me how to require a username and password for listing the shared folders in samba, then I can try to reproduce.
> I have zero experience with samba
Ok, looks like it's not gonna happen :p
> Also, as indicated in comment #67, developers probably need the smb.conf > file to reproduce.
smb.conf is for configuring the samba server, and I'm pretty sure it has nothing to do with this bug. Anyway, if you want to see it, here it is:
[global] workgroup = home server string = yoga # printcap name = cups # load printers = yes # printing = cups log file = /var/log/samba/log.%m max log size = 50 ; log level = 3 map to guest = bad user security = user encrypt passwords = yes socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = no
unix extensions = no
[share] path = /home/aditsu/stuff/share public = yes writable = no only guest = yes follow symlinks = yes wide links = yes
(In reply to comment #94)
> Is there a way to reproduce this crash without having a second computer?
I don't know... if you can tell me how to require a username and password for listing the shared folders in samba, then I can try to reproduce.
> I have zero experience with samba
Ok, looks like it's not gonna happen :p
> Also, as indicated in comment #67, developers probably need the smb.conf
> file to reproduce.
smb.conf is for configuring the samba server, and I'm pretty sure it has nothing to do with this bug. Anyway, if you want to see it, here it is:
[global] samba/log. %m
workgroup = home
server string = yoga
# printcap name = cups
# load printers = yes
# printing = cups
log file = /var/log/
max log size = 50
; log level = 3
map to guest = bad user
security = user
encrypt passwords = yes
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = no
unix extensions = no
[share] stuff/share
path = /home/aditsu/
public = yes
writable = no
only guest = yes
follow symlinks = yes
wide links = yes