24 Sep
2016
24 Sep
'16
3:59 p.m.
Sorry for the previous hijacked thread.
The problem is I get error instead of mounting a drive:
Unable to mount this device.
Potential reasons include:
Improper device and/or user privilege level
Corrupt data on storage device
Technical details:
org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to
perform operation
I checked my groups. They are: disk, floppy, cdrom, vboxusers, root.
Aren't they enough?
24 Sep
24 Sep
5:12 p.m.
J. Drahun wrote:
I checked my groups. They are: disk, floppy, cdrom,
vboxusers, root.
Aren't they enough?
I have plugdev netdev for usb and nfs disks
Try getting more detailed message from dmesg or syslog. Which kind of
authentication is not provided?
It might be policykit related if the above does not help.
regards
4:53 p.m.
New subject: [trinity-users] Re: Konqueror doesn't mount drives - correct thread
24.09.2016 21:12, deloptes wrote:
Try getting more detailed message from dmesg or
syslog. Which kind of
authentication is not provided?
Sorry, forgot to mention.
My distro is openSuse 13.1.
What kind of information should I seek for in dmesg out? The only
message I get is Konqueror message.
6 p.m.
J. Drahun wrote:
24.09.2016 21:12, deloptes wrote:
what is the authentication problem or the dbus problem?
I am on debian - time ago I had to tweak the policykit files to be able to
do certain things/use services as simple user.
regards
Try getting more detailed message from dmesg or
syslog. Which kind of
authentication is not provided?
Sorry, forgot to mention.
My distro is openSuse 13.1.
What kind of information should I seek for in dmesg out? The only
message I get is Konqueror message.
5:56 p.m.
New subject: [trinity-users] Re: Re: Konqueror doesn't mount drives - correct thread
deloptes wrote:
what is the authentication problem or the dbus
problem?
Here's dbus-monitor out:
dest=:1.46 serial=2 path=/org/freedesktop/DBus;
interface=org.freedesktop.DBus; member=NameAcquired
string ":1.46"
method call sender=:1.46 -> dest=org.freedesktop.DBus serial=3
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
string "eavesdrop=true,type='method_call'"
method call sender=:1.46 -> dest=org.freedesktop.DBus serial=4
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
string "eavesdrop=true,type='method_return'"
method call sender=:1.46 -> dest=org.freedesktop.DBus serial=5
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
string "eavesdrop=true,type='error'"
Don't know if that's what you want.
I am on debian - time ago I had to tweak the policykit
files to be able to
do certain things/use services as simple user.
I'll look for it, but it seems I don't have it installed.
7:06 p.m.
J. Drahun wrote:
deloptes wrote:
Look here: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2444
I posted below in hurry. Check this file and if the options are set
/usr/share/polkit-1/actions/org.freedesktop.udisks.policy
<action id="org.freedesktop.udisks.filesystem-mount">
...
<allow_any>yes</allow_any>
...
<allow_active>yes</allow_active>
</action>
regards
what is the authentication problem or the dbus
problem?
Here's dbus-monitor out:
dest=:1.46 serial=2 path=/org/freedesktop/DBus;
interface=org.freedesktop.DBus; member=NameAcquired
string ":1.46"
method call sender=:1.46 -> dest=org.freedesktop.DBus serial=3
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=AddMatch
string "eavesdrop=true,type='method_call'"
method call sender=:1.46 -> dest=org.freedesktop.DBus serial=4
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=AddMatch
string "eavesdrop=true,type='method_return'"
method call sender=:1.46 -> dest=org.freedesktop.DBus serial=5
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=AddMatch
string "eavesdrop=true,type='error'"
Don't know if that's what you want.
I am on debian - time ago I had to tweak the
policykit files to be able
to do certain things/use services as simple user.
I'll look for it, but it seems I don't have it installed.
7:28 p.m.
New subject: [trinity-users] Re: Re: Re: Konqueror doesn't mount drives - correct thread
deloptes wrote:
I posted below in hurry. Check this file and if the
options are set
/usr/share/polkit-1/actions/org.freedesktop.udisks.policy
<action id="org.freedesktop.udisks.filesystem-mount">
...
<allow_any>yes</allow_any>
...
<allow_active>yes</allow_active>
</action>
I set those options to "yes" both in udisks and udisks2 files (they were
set to auth_admin before in udisks2).
Must I restart TDE?
9:46 p.m.
J. Drahun wrote:
deloptes wrote:
won't hurt I guess. I don't recall anymore ... perhaps no is the right
answer.
sorry
regards
I posted below in hurry. Check this file and if
the options are set
/usr/share/polkit-1/actions/org.freedesktop.udisks.policy
<action id="org.freedesktop.udisks.filesystem-mount">
...
<allow_any>yes</allow_any>
...
<allow_active>yes</allow_active>
</action>
I set those options to "yes" both in udisks and udisks2 files (they were
set to auth_admin before in udisks2).
Must I restart TDE?
24 Sep
24 Sep
5:13 p.m.
J. Drahun wrote:
Sorry for the previous hijacked thread.
The problem is I get error instead of mounting a drive:
Unable to mount this device.
Potential reasons include:
Improper device and/or user privilege level
Corrupt data on storage device
Technical details:
org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to
perform operation
I checked my groups. They are: disk, floppy, cdrom, vboxusers, root.
Aren't they enough?
sorry forgot to mention
sudo pam-auth-update --force
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug…
5:41 p.m.
New subject: [trinity-users] Re: Konqueror doesn't mount drives - correct thread
Am Samstag, 24. September 2016 schrieb deloptes:
J. Drahun wrote:
And then there are the errors in the udev hardware database ...
http://trinity-users.pearsoncomputing.net/?0::9343
nik
Sorry for the previous hijacked thread.
The problem is I get error instead of mounting a drive:
Unable to mount this device.
Potential reasons include:
Improper device and/or user privilege level
Corrupt data on storage device
Technical details:
org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to
perform operation
I checked my groups. They are: disk, floppy, cdrom, vboxusers, root.
Aren't they enough?
sorry forgot to mention
sudo pam-auth-update --force
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug…
---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-users-unsubscribe(a)lists.pearsoncomputing.net
For additional commands, e-mail: trinity-users-help(a)lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/
Please remember not to top-post:
http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
--
Please do not email me anything that you are not comfortable also sharing with the NSA.
5:57 p.m.
Dr. Nikolaus Klepp wrote:
Am Samstag, 24. September 2016 schrieb deloptes:
> J. Drahun wrote:
>
> > Sorry for the previous hijacked thread.
> >
> > The problem is I get error instead of mounting a drive:
> > Unable to mount this device.
> > Potential reasons include:
> > Improper device and/or user privilege level
> > Corrupt data on storage device
> > Technical details:
> > org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to
> > perform operation
> >
> > I checked my groups. They are: disk, floppy, cdrom, vboxusers, root.
> > Aren't they enough?
>
> sorry forgot to mention
>
> sudo pam-auth-update --force
>
>
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug…
And then there are the errors in the udev hardware database ...
http://trinity-users.pearsoncomputing.net/?0::9343
nik
Yes might be similar. I also noticed that recently I do not get notified
when I plug in the phone as usb storage.
6:25 p.m.
Dr. Nikolaus Klepp wrote:
Am Samstag, 24. September 2016 schrieb deloptes:
> J. Drahun wrote:
>
> > Sorry for the previous hijacked thread.
> >
> > The problem is I get error instead of mounting a drive:
> > Unable to mount this device.
> > Potential reasons include:
> > Improper device and/or user privilege level
> > Corrupt data on storage device
> > Technical details:
> > org.freedesktop.UDisks2.Error.NotAuthorizedCanObtain: Not authorized to
> > perform operation
> >
> > I checked my groups. They are: disk, floppy, cdrom, vboxusers, root.
> > Aren't they enough?
>
> sorry forgot to mention
>
> sudo pam-auth-update --force
>
>
https://bugs.launchpad.net/ubuntu/+source/policykit-desktop-privileges/+bug…
And then there are the errors in the udev hardware database ...
http://trinity-users.pearsoncomputing.net/?0::9343
nik
Look here: http://bugs.pearsoncomputing.net/show_bug.cgi?id=2444
3009
days inactive
3010
days old
13 comments
3 participants
participants (3)
-
deloptes -
Dr. Nikolaus Klepp -
J. Drahun