https://bugs.kde.org/show_bug.cgi?id=234007
Summary: umask not honored by file resource
Product: kaddressbook
Version: unspecified
Platform: unspecified
OS/Version: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
AssignedTo: kdepim-bugs at kde.org
ReportedBy: mc-kde-bug at oak.homeunix.org
CC: tokoe at kde.org
Version: (using KDE 4.3.2)
OS: Linux
Installed from: Unlisted Binary Package
I would like a simple way to share an addressbook with other local users. In
the past, I've done it with a file resource. With this version, it seems to no
longer work.
To replicate the bug:
Set everyone's umask to 002 by opening konsole, running "umask 002", and
starting kontact from that konsole (to factor out any issues with whether umask
is set correctly for the X session). As user1, create a new file resource, for
example, ~user1/tmp/abc.vcf. It will be created according to umask (so far so
good). As user2, who shares default group with user1's default group, and who
also can write to ~user1/tmp/, create a file resource using the same file name.
Now, as user2, add an address. The file will be recreated with permissions
0600, aka -rw------- (surprising, and breaks my address sharing solution).
user1 will see message, "Unable to open file: '/home/user1/tmp/abc.vcf'".
Desired behavior:
I expect user2's addressbook to recreate the file according to user2's umask,
which would preserve the group read/write access. Actually, this worked as I
expected in a prior version of KDE.
Work around:
After editing the file, manually chmod g+rw $file. The permission change will
stick for several edits, as long the *other* user does not edit the resource.
This seems to affect korganizer in the same way.
I see support for an akonadi resource, but that seems to slow everything down
and it's not clear to me that it supports multi-user sharing (perhaps it only
shares between a single user's many applications and devices).
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.