On 01/23/2014 04:14 AM, Guido Berhoerster wrote:
Hi,

* Robert Schweikert <[email protected]> [2014-01-22 21:11]:
Ran zypper up earlier this week on my daughters machine (13.1
x86_64) and now when she connects here phone a dialog appears

how is it connected, via USB cable, does it appear as a mass
storage device?

requesting the root password.

The message, although this is probably not very useful info ;)

"An Application is attempting to perform an action that requires
privileges. Authentication as the super user is required."

That is the policykit agent, in the normal case (i.e. default
policykit privileges and everyting working as intended) a local
user whose session is considered active by systemd-logind should be
authorized to mount any removable storage.

Marcus already wrote some instructions for you to check against
policykit whether you are authorized to mount filesystems.

In order to determine whether the current session is marked
active, find the session number of the current user session with:

loginctl -al list-sessions

and then check with:

loginctl  show-session <number> | grep ^Active

whether it is active.

That was it, a logout login cycle fixed the issue. Thanks.

Prior to zypper up this did not happen. I did not keep a log of the
packages that were updated.

But zypper did, have a look at /var/log/zypp/history. Note that
upgrade actions are referred to as |install|. Would be interesting
if there are any suspicious updates (udisks2, udev, systemd,
policykit) which might have triggered that.

There was a systemd update on the 21st, but as we all know kids reporting is a bit spotty thus I cannot say whether this actually triggered the issue or if the problem existed prior to this update.

Thanks Marcus and Guido for the info and help.
Robert



--
Robert Schweikert                           MAY THE SOURCE BE WITH YOU
SUSE-IBM Software Integration Center                   LINUX
Tech Lead
Public Cloud Architect
[email protected]
[email protected]
781-464-8147
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to