[SOLVED] "Not authorized to perform operation"

[Christoffer]

Hey,

Today, I downloaded and installed SparkyLinux with the Budgie desktop onto my computer. So far, I am very satisfied. It's a good looking system.

When trying to install a game onto my second hard drive, I realized that I can't use it. When clicking on it in the file manager (name is "Hayes") it says:


Any idea how I can properly mount this drive?

Thanks in advance!
Chris

[pavroo]

Hi
Looks like some global permission is missing.
I will have a look and be back.

[MoroS]

Hi
Looks like some global permission is missing.
I will have a look and be back.

We should check what Budgie uses for mounting the other partitions. Most DEs out there use GVFS, which handles everything for them. Normally that requires the user to be in a specific group (don't remember the group name though, but it's always something like "disks" or such). Maybe Budgie requires the user to be in such a specific group. Which file manager does Budgie use for handing file management (PCMan, Thunar, other)? That's probably the point to investigate.

[Christoffer]

As far as I know, it uses Nautilus. Which also uses gvfs, yes.

[pavroo]

I installed the spin last night.
I checked packages around polkit, policykit, pam, gvfs.
I also installed pcmanfm - the same problem.
I added the user to one extra group: disk - no changes.
But there is a message in ~HOME/.xsession-errors:

Code Select Expand

gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1

[pavroo]

Following the message I found:

Since you are not root on system, the process calling gnome-keyring-daemon does not have the privileges to prevent a possible write of the sensitive cryptographic key data to the system's hard disk.

and the command:

Code Select Expand

sudo setcap cap_ipc_lock=+ep `which gnome-keyring-daemon`
solved problem with it.
~HOME/.xsession-errors:

Code Select Expand

localuser:pawel being added to access control list
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
SSH_AUTH_SOCK=/run/user/1000/keyring/ssh
GPG_AGENT_INFO=/run/user/1000/keyring/gpg:0:1
But it didn't solve the problem in a file manager.

[pavroo]

I found it.
The solution is the same as I made in JWM, Openbox and Enlightenment spins.
Install lxpolkit:

Code Select Expand

sudo apt-get update
sudo apt-get install lxpolkit
Create lxpolkit.desktop file in your home directory:

Code Select Expand

~HOME/.config/autostart/lxpolkit.desktop
Paste the text into the desktop file:

Code Select Expand

[Desktop Entry]
Name=Lxpolkit
Exec=/usr/bin/lxpolkit
Terminal=false
Type=Application
NoDisplay=true
Then reboot.

[Christoffer]

I found it.
The solution is the same as I made in JWM, Openbox and Enlightenment spins.
Install lxpolkit:

Code Select Expand

sudo apt-get update
sudo apt-get install lxpolkit
Create lxpolkit.desktop file in your home directory:

Code Select Expand

~HOME/.config/autostart/lxpolkit.desktop
Paste the text into the desktop file:

Code Select Expand

[Desktop Entry]
Name=Lxpolkit
Exec=/usr/bin/lxpolkit
Terminal=false
Type=Application
NoDisplay=true
Then reboot.

You're the man! Thank you!

[Christoffer]

@pavroo

Another question.
With your solution, I am now able to use the drive, but Steam doesn't seem to be able to use it.

When trying to create another library for Steam downloads, I noticed that I don't just have one "Hayes"; I have 2. Another mysterious Hayes popped up, and I have no clue why:


So I have a Hayes and a Hayes1. In a normal Nautilus window, the drive is named Hayes - but I noticed that in a Nautilus opened with the root terminal, it's called Hayes1. And when looking through the properties of both "drives", the normal Hayes is just a folder I can't delete. My drive is actually Hayes1, but it can't be used by Steam (I can use it freely though with your solution).


When trying to use Hayes1 with Steam, it says:


Any ideas?

[pavroo]

Unmount your Hayes and Hayes1 partitions.
If you are not sure about that just reboot.
Make sure your partitions called Hayes and Hayes1 are NOT mounted. Check it:

Code Select Expand

sudo mount | grep /dev
Delete Hayes1 folder as root:

Code Select Expand

sudo rm -f /media/christoffer/Hayes1
After rebooting you should mount your internal partition in Hayes folder.
Be very careful with that.

A few years ago I haven't unmounted a partition so I just deleted all the files :)

[Christoffer]

Well, Hayes1 can be unmounted, but Hayes is just a directory.

You say I have to delete Hayes1, but should I do that since that's the actual drive? Not Hayes?

And if I screw it up, not too big of a deal, I currently have no files on 'em xD :)

EDIT: I managed to delete Hayes dictionary in root Nautilus, now my only problem is the Steam error in the last picture. What's up with that?

[pavroo]

The message says that the partition file system has to have execute permissions.
So it can't be vfat or ntfs.
It should be installed in home directory with Linux file system such as ext4.

[Christoffer]

The message says that the partition file system has to have execute permissions.
So it can't be vfat or ntfs.
It should be installed in home directory with Linux file system such as ext4.

Thank you so much!