folder sharing in gnome not working in Lucid

Bug #562960 reported by Henti Smith
36
This bug affects 7 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Trying to share a folder on desktop called "shared", the required software is installed and all seems well.

Options selected are :

Share this folder: ticked
Share name: shared
Comment: Random Shares
Allow others to create and delete files in this folder: not ticked
Guest access: ticked

When trying to access share from windows the share is viewable using the \\ipadddress, however when clicking on it windows displays a message:

Share is not accessible. You might not have permission to use this network resource. Contact the administrator of the server to find out if you have access permissions.

No network provider accepted the given network path

My /var/og/samba/ log file contains the following:

  process_usershare_file: stat of /var/lib/samba/usershares/shared failed. Permission denied
[2010/04/14 13:35:11, 0] smbd/service.c:988(make_connection_snum)
  canonicalize_connect_path failed for service shared, path /home/username/Desktop/Shared

Revision history for this message
Rickard Närström (riccetn) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingSamba#samba-server.

Please change the status of this report back to new when the requested information is attached.

affects: ubuntu → samba (Ubuntu)
Changed in samba (Ubuntu):
status: New → Incomplete
Chuck Short (zulcss)
Changed in samba (Ubuntu):
importance: Undecided → Low
Revision history for this message
Nick Cave (njcave) wrote :
Download full text (15.6 KiB)

Is it a regression ?

Did this use to work properly with a previous release ?

Yes, it worked in Ubuntu 9.10.

---------------------------------------------------

What version of samba packages are used ?

Please give the output of:

dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba

libpam-smbpass 2:3.4.7~dfsg-1ubuntu3 samba install ok installed
libsmbclient 2:3.4.7~dfsg-1ubuntu3 samba install ok installed
libwbclient0 2:3.4.7~dfsg-1ubuntu3 samba install ok installed
samba 2:3.4.7~dfsg-1ubuntu3 install ok installed
samba-common 2:3.4.7~dfsg-1ubuntu3 samba install ok installed
samba-common-bin 2:3.4.7~dfsg-1ubuntu3 samba install ok installed
smbclient 2:3.4.7~dfsg-1ubuntu3 samba install ok installed

------------------------------------------------

Which clients are failing to connect?

Windows Vista machine is failing to connect.

------------------------------------------------

What is the error message produced on the client?

Open Folder
\\192.168.0.100\downloads is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.

A device attached to the system is not functioning.

--------------------------------------------

Other information to include

    *

      the content of the /etc/samba/smb.conf file
    *

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no

# WINS Server - Tells the NMBD components of Samba to be a ...

Revision history for this message
confiq (confiq) wrote :

I think I'm also affected of this bug.
attaching file from "tail -f /var/log/samba/log.*" from the moment when i try to mount smb://confiq-bigcomp/video (confiq-bigcomp is local machine)

Interesting is that shared folder is "Video" and not "video", also this happened on clean Ubuntu Lucid Install!

Changed in samba (Ubuntu):
status: Incomplete → New
Revision history for this message
confiq (confiq) wrote :

Changed status to New,
What I forgot to mention is that i chmod shared folder to '777'...

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

I have this bug too, and I figured out that the problem is that the whole path to the directory should be accessible (but not writable).

/home/username/Desktop/

/home should be at least o+rx
/home/username should be at least o+rx
/home/username/Desktop/ should be at least o+rx

Revision history for this message
Michael van der Kolff (mvanderkolff) wrote :

Per Nicolo's remarks, they are spot on. Encrypting home directories is also a common choice that is incompatible with sharing the home directory. Public directory, as always, remains sharable.

Quick brainstorm on fixing this - Perhaps a script that works under sudo that:
(a) If home directory is encrypted, advise user to share stuff out of ~/Public;
(b) Run a script under sudo, perhaps controlled by a group (samba-sharers?) that runs a mount --bind ${HOMEDIR}/Public/share /var/lib/samba/usershares/${SHARENAME}
(c) net usershare /var/lib/samba/usershares/${SHARENAME}

Thoughts?

Cheers,

Michael

Revision history for this message
Cedric L'homme (rangzen) wrote :

@Nicolò Chieffo #5 :

Oh god … 2 hours of guess/try/fail the root path was in 700 and now in 705 it works … Thanks A LOT !!!

Revision history for this message
Chuck Short (zulcss) wrote :

Closing according to comments below.

Changed in samba (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.