On 3/31/2013 4:46 AM, gugrim wrote:
>
> When I upgraded to 12.2 I posted this:
>
> http://tinyurl.com/cspvk5u
>
> The policykit solution worked although there were error notifications
> on every boot even though the mounting worked.
>
> Now I’ve upgraded to 12.3 and Smb4K has started prompting again. The
> policy looks fine but seems to be ignored:
>
> Contents of
> /var/lib/polkit-1/localauthority/10-vendor.d/de.berlios.smb4k.mounthelper.mount.pkla:
>
> Code:
> --------------------
>
> [de.berlios.smb4k.mounthelper.mount]
> Identity=unix-user:gugrim;
> Action=de.berlios.smb4k.mounthelper.mount
> ResultAny=yes
> ResultInactive=yes
> ResultActive=yes
>
> --------------------
>
>
> Anyone knows what’s wrong?
>
> TIA,
> Gunnar
>
>
A work around, which works quite well, was given by jdmcdaniel3 in post 8 of this thread:
Yes, I’ve seen that and unless I’ve misunderstood something it isn’t really about a way to make smb4k work, more about how to get by without smb4k. KDE smb-links are fine but I really like
smb4k and it worked very well before suse 12.2 and acceptably before 12.3. Perhaps this isn’t even an smb4k problem but symptoms of a bug in how policies are handled.
This is really annoying, I’ve got the same bug here. I’ve looked into the manpage of polkit, which gave a hint: Polkit seems to look for rules either in /etc/polkit-1 or in /usr/share/polkit-1, but not in /var/lib/polkit-1. So I copied the whole folder /var/lib/polkit-1/10-vendor.d to /etc/polkit-1 and now I can mount via smb4k without giving root’s pw.
Why annoying? Because s2ram depends on umount of the connection.
But probably I opended a hole for whatever security reasons. I even do not know where to leave a bug report.