Bug 140362 - writing to samba shares shows unnecessary error box "Cannot change file permissions"
Summary: writing to samba shares shows unnecessary error box "Cannot change file permi...
Status: RESOLVED DUPLICATE of bug 62733
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: smb (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-20 18:27 UTC by Manfred Mislik
Modified: 2008-06-02 13:10 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Manfred Mislik 2007-01-20 18:27:57 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Ubuntu Packages

I got a Debian Sarge server as samba file server with various shares.

I got a (currently) Kubuntu Edgy client with different users. File shares are mountet in fstab as cifs.

When I write to a share directory that has the same user and group I have on the client machine everything is just fine. I can write to and from those directories without any errors.

The server also got shares used by almost everyone like the images share where we save our images to. That share as a force user _images_ force group _images_ constaint so that with members of group _images_ allowed to connect.

The share gets mounted on the client in it's own /home/images/ directory where all members of group _images_ are allowed to read and write. When a _images_ member drag and drops or copies an image into that share using konqueror I get a message box "Cannot change file permissions for <file>". The copying or moving of the file still worked fine though. It's got the correct user and group _images_ and rw-rw----.

I don't know what that message is good for and I've seen bugs that complain about a similar problem when writing to vfat partitions that appears to be solved.

Please make that error box disappear or provide the possibility to disable that message with a simple checkbox or in kde config somehow.

I didn't experience this problem prior to kde 3.5.5 or 3.5.4
Comment 1 Jaime Torres 2008-05-04 01:31:14 UTC
This bug is very similar to #62733 and #139876
Comment 2 Christophe Marin 2008-06-02 13:10:40 UTC

*** This bug has been marked as a duplicate of 62733 ***