Page 1 of 3 123 LastLast
Results 1 to 10 of 25

Thread: Polkit update from 0.112 to 0.113 Affects USB mounts

  1. #1
    Join Date
    Nov 2010
    Location
    Texas, USA
    Posts
    97

    Default Polkit update from 0.112 to 0.113 Affects USB mounts

    openSUSE 13.2 x64, KDE default (4.14.9).

    yesterday, Oct 14, 2015, YOU (Yast Online Update) updated 3 PolicyKit (polkit) packages from 0.112-3.5.1 to 0.113-3.8.1.
    The 3 packages were: typelib-1_0-PolKit-1_0, libpolkit0, polkit.

    After these updates, I could not use the KDE System Tray Device Notifier to mount
    external USB (2.0) drives MORE THAN ONCE. I could mount a drive, browse the drive,
    then un-mount (via the KDE Notifier) the drive. If I later (even after a logoff/logon) tried
    to mount the USB drive a popup dialog requesting the root password would appear.

    Only after rebooting could I again mount/un-mount an external USB drive - but again JUST ONE time.

    This morning I reverted the three PolicyKit packages back to version 0.112-3.5.1.
    Now mounting/un-mounting external USB drives via the KDE System Tray Device Notifier works as expected,
    and as it always has.

  2. #2
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,818

    Default Re: Polkit update from 0.112 to 0.113 Affects USB mounts

    I can confirm that I also need to enter root password to mount or remove a USB drive
    Ownership is still to my user and the users group

    Has anyone reported this yet or is this new normal operation?

  3. #3

    Default Re: Polkit update from 0.112 to 0.113 Affects USB mounts

    Hm, I don't have such a problem here.

    What is the exact reason *why* the root password is requested?
    You can find out by clicking on "Details..." in the authentification dialog.

    Maybe that would provide a clue...

    If you need the password *every* time, it could be that the drive is misdetected as an internal (system) one or something like that (which would probably be unrelated to the polkit update though), or that your polkit rules are messed up.
    But I have no idea what could cause it to work once and then afterwards require a password.
    Last edited by wolfi323; 15-Oct-2015 at 08:52.

  4. #4
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,818

    Default Re: Polkit update from 0.112 to 0.113 Affects USB mounts

    Action is Mount a file system
    It is polkit-subject-PID 11154 for what that is worth

    So it is polkit and this did not happen before the last update The op says dropping back pol-kit fixes it. The question is this intentional or just a bug

    I'm running standard 13.2 nothing fancy

  5. #5

    Default Re: Polkit update from 0.112 to 0.113 Affects USB mounts

    Quote Originally Posted by gogalthorp View Post
    Action is Mount a file system
    Yes, that is ok, and should be possible *without* a root password with the default ("easy") rules.

    It is polkit-subject-PID 11154 for what that is worth
    That's irrelevant, it's just the process ID of the application that wants to mount the filesystem.

    So it is polkit and this did not happen before the last update The op says dropping back pol-kit fixes it. The question is this intentional or just a bug
    It's definitely not intentional, but I'm not sure yet it is a bug.
    And as mentioned, I don't have such a problem here.

    Just to be clear here: you get that *every time*, or does it work without a password the first time as the OP wrote?
    Those would probably be two completely different issues.

    What does this output?
    Code:
    sudo grep -R -A1 org.freedesktop.udisks2.filesystem-mount /etc/polkit-1/rules.d/
    And verify that your user session is listed by "loginctl".
    Last edited by wolfi323; 15-Oct-2015 at 09:10.

  6. #6
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,818

    Default Re: Polkit update from 0.112 to 0.113 Affects USB mounts

    So far have needed ever time.

    Tried with both Windows and ext4 file systems

    I don't mount USB that much and may not have noticed except I was checking the OP's report. I think the update came in last night

  7. #7

    Default Re: Polkit update from 0.112 to 0.113 Affects USB mounts

    Quote Originally Posted by gogalthorp View Post
    So far have needed ever time.
    Well, as I wrote, that's likely a different issue then. For the OP it seems to work without a password the first time, only subsequents mounts need a password.
    Your problem could be caused by too strict security settings, or that your user session is not registered.
    So what is the output of those commands I asked, please?

    Tried with both Windows and ext4 file systems
    The filesystem type shouldn't really make a difference.

    I don't mount USB that much and may not have noticed except I was checking the OP's report.
    So you are not even sure that it worked before the update?
    Have you tried to downgrade polkit?

    I think the update came in last night
    Yes.

  8. #8
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,818

    Default Re: Polkit update from 0.112 to 0.113 Affects USB mounts

    Code:
    gogalthorp@linux:~> sudo grep -R -A1 org.freedesktop.udisks2.filesystem-mount /etc/polkit-1/rules.d/
    root's password:
    /etc/polkit-1/rules.d/90-default-privs.rules:           'org.freedesktop.udisks2.filesystem-mount-system':
    /etc/polkit-1/rules.d/90-default-privs.rules-                   [ 'auth_admin', 'auth_admin', 'auth_admin_keep' ],
    --
    /etc/polkit-1/rules.d/90-default-privs.rules:           'org.freedesktop.udisks2.filesystem-mount-other-seat':
    /etc/polkit-1/rules.d/90-default-privs.rules-                   [ 'auth_admin', 'auth_admin', 'auth_admin_keep' ],
    --
    /etc/polkit-1/rules.d/90-default-privs.rules:           'org.freedesktop.udisks2.filesystem-mount':
    /etc/polkit-1/rules.d/90-default-privs.rules-                   [ 'auth_admin', 'auth_admin', 'yes' ],

  9. #9
    Join Date
    Nov 2009
    Location
    West Virginia Sector 13
    Posts
    15,818

    Default Re: Polkit update from 0.112 to 0.113 Affects USB mounts

    Are you running 0.113?

  10. #10

    Default Re: Polkit update from 0.112 to 0.113 Affects USB mounts

    Quote Originally Posted by gogalthorp View Post
    Code:
    gogalthorp@linux:~> sudo grep -R -A1 org.freedesktop.udisks2.filesystem-mount /etc/polkit-1/rules.d/
    ...
    /etc/polkit-1/rules.d/90-default-privs.rules:           'org.freedesktop.udisks2.filesystem-mount':
    /etc/polkit-1/rules.d/90-default-privs.rules-                   [ 'auth_admin', 'auth_admin', 'yes' ],
    Looks ok.
    The last 'yes' means that a locally logged in user should not need a password for mounting filesystems.

    So, is the session listed by "loginctl"?
    Otherwise you are not regarded as "locally logged in user".

    Quote Originally Posted by gogalthorp View Post
    Are you running 0.113?
    Yes, since yesterday:
    Code:
    wolfi@amiga:~/Desktop> rpm -qi polkit
    Name        : polkit
    Version     : 0.113
    Release     : 3.8.1
    Architecture: x86_64
    Install Date: Mit 14 Okt 2015 11:25:34 CEST
    Group       : System/Libraries
    Size        : 257725
    License     : LGPL-2.1+
    Signature   : RSA/SHA256, Mit 14 Okt 2015 09:08:38 CEST, Key ID b88b2fd43dbdc284
    Source RPM  : polkit-0.113-3.8.1.src.rpm
    Build Date  : Tue 06 Oct 2015 19:31:24 CEST
    Build Host  : build21
    Relocations : (not relocatable)
    Packager    : http://bugs.opensuse.org
    Vendor      : openSUSE
    URL         : http://www.freedesktop.org/wiki/Software/polkit/
    Summary     : PolicyKit Authorization Framework
    Description :
    PolicyKit is a toolkit for defining and handling authorizations.
    It is used for allowing unprivileged processes to speak to privileged
    processes.
    Distribution: openSUSE 13.2
    wolfi@amiga:~/Desktop>
    And I have rebooted a few times since, so it is definitely in use as well.

    That said, I also have the reverted systemd update installed (it didn't give me any problem, as grub2-mkconfig doesn't add a 'ro' to the kernel command line on my non-EFI system), maybe that contains a fix that causes it to work for me and not for you.
    I'll try to revert that and see if it still works then.

Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •