SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have the following problem: Slackware 12.2, openoffice 3.0.1. When I want to save a file from openoffice to mounted cifs directory I get the following error:
Error saving the document. Object is not accessible. The object can not be accessed due to insufficient user rights.
But I can write to this directory for example with copy, that is no problem.
My mounting command is:
mount -tcifs -ocredentials=/root/.creds,uid=szaboa,nobrl,rw //router/szaboa/privat/munka2 /home/szaboa/diatech/munka2
It sounds like openoffice can't write. Go figure out it's permissions. check the binaries. If some things are started as root they drop to user nobody
I have checked the permissions of the binaries: scalc, swriter, soffice and soffice.bin. All have the permissions 755, the owner is root. What should be they? Or which files must I look more for?
//server/folder & /mnt/folder are truncated in the above code sample. /mnt/folder is chown'd to keith:user, keith is a user on the server.
You can try adding/changing some options on the samba server, create mask =, directory mask =, inherit permissions = Yes, inherit owner = Yes, force user=.
mount -tcifs -ocredentials=/root/.creds,uid=szaboa,nobrl,rw //router/szaboa/privat/munka2 /home/szaboa/diatech/munka2
where the /home/szaboa/diatech/munka2 chown'd to szaboa:users and the user szaboa is a user on the server. I can check/change the samba options on the server but on Monday.
Try chmodding your mount place for 777 temporarily. uid should be numeric value, shouldn't it?
I chmodded for 777 the mount place but no change. I don't understand the second item, uid, what does it mean here?
But I must add some more informations to the problem: I have Debian also on this machine, I mount under Debian with the same command and there is no such problem, I can save to the mounted directories with Openoffice, the Openoffice on Debian has also the same versionnumber as on Slackware.
uid=value and gid=value
Set the owner and group of the root of the file system (default:
uid=gid=0, but with option uid or gid without specified value,
the uid and gid of the current process are taken)
If it works in debian, are samba versions the same in both distros?
If it works in debian, are samba versions the same in both distros?
But according to the man mount.cifs:
Excerpt from "man mount.cifs":
"uid=arg
sets the uid that will own all files on the
mounted filesystem. It may be specified
as either a username or a numeric uid.
This parameter is ignored when the target
server supports the CIFS Unix extensions."
Not only uid-number it can be username also.
The samba versions:
Slackware 3.2.5
Debian 3.2.4
And yet anything: I can't save only from Openoffice, from another applications no problem, I can copy to the mounted directories any files without problems.
Then the problem is definitely with OpenOffice.org. Since this isn't included with Slackware, you had to have gotten it elsewhere. It's possible you got a bad build or something. Grab the latest build script from www.slackbuilds.org and try that. Let us know if that fixes the problem, or if it persists.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.