Bug#707543: dolphin: Acl management inconsistent
Package: dolphin
Version: 4:4.10.2-1
Severity: important
Dear Maintainer,
* What led up to the situation?
I'm trying to set some ACL to a particular user (my patition is mounted with
ACL option...)
* What exactly did you do that was effective (or
ineffective) ?
Clicking right on a folder, select the tab access right, clicking on advanced->
add an entry, selecting the particular user.
* What was the outcome of this action?
As direct result, all the informations of Access right are desactivated (as
expected) and if I click on the OK button, nothing happen...
If I'm going back to access right there are no changes
* What outcome did you expect instead?
Applying the right ACL and reading it correctly...
This is a long term disfunction, please take care about it, ACL are very
usefull but compliquate in command line...
Best regards
Mourad
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.8-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages dolphin depends on:
ii kde-runtime 4:4.10.2-2
ii libc6 2.13-38
ii libkactivities6 4:4.10.2-1
ii libkcmutils4 4:4.10.2-3
ii libkdecore5 4:4.10.2-3
ii libkdeui5 4:4.10.2-3
ii libkfile4 4:4.10.2-3
ii libkio5 4:4.10.2-3
ii libknewstuff3-4 4:4.10.2-3
ii libkonq5abi1 4:4.10.2-1
ii libkparts4 4:4.10.2-3
ii libnepomukcore4 4:4.10.2-1
ii libnepomukwidgets4 4:4.10.2-1
ii libphonon4 4:4.6.0.0-3
ii libplasma3 4:4.10.2-3
ii libqt4-dbus 4:4.8.4+dfsg-1
ii libqt4-xml 4:4.8.4+dfsg-1
ii libqtcore4 4:4.8.4+dfsg-1
ii libqtgui4 4:4.8.4+dfsg-1
ii libsolid4 4:4.10.2-3
ii libsoprano4 2.8.0+dfsg.1-0r2
ii libstdc++6 4.7.2-5
ii libxrender1 1:0.9.7-1
ii phonon 4:4.6.0.0-3
Versions of packages dolphin recommends:
ii ruby 1:1.9.3
Versions of packages dolphin suggests:
pn kdesdk-dolphin-plugins <none>
-- no debconf information
Reply to: