In the past I tried "which udisks2-inhibit" to find the location of the command, but this always returned no results. I didn't dig any deeper because I regularly use Kubuntu and Ubuntu and the problem with automounting does not occur.
Today I started my Ubuntu 14.04 Virtual Machine and ran the following command:
find / -name udisks2-inhibit -print 2>/dev/null
which returned the following result:
/usr/lib/udisks2/udisks2-inhibit
It seams that this command is in a non-standard location which explains why it didn't show up when using the "which" command.
When using Ubuntu 14.04, I have never encountered the problem with automounting of newly created or edited partitions, and I do a lot of testing using Ubuntu and Kubuntu. This make me think the problem might be unique to Xubuntu and perhaps XFCE.
To determine if udisks2-inhibit works on Xubuntu, would you be able to test gparted by using the following command line invocation?
In the past I tried "which udisks2-inhibit" to find the location of the command, but this always returned no results. I didn't dig any deeper because I regularly use Kubuntu and Ubuntu and the problem with automounting does not occur.
Today I started my Ubuntu 14.04 Virtual Machine and ran the following command:
find / -name udisks2-inhibit -print 2>/dev/null
which returned the following result:
/usr/ lib/udisks2/ udisks2- inhibit
It seams that this command is in a non-standard location which explains why it didn't show up when using the "which" command.
When using Ubuntu 14.04, I have never encountered the problem with automounting of newly created or edited partitions, and I do a lot of testing using Ubuntu and Kubuntu. This make me think the problem might be unique to Xubuntu and perhaps XFCE.
To determine if udisks2-inhibit works on Xubuntu, would you be able to test gparted by using the following command line invocation?
sudo /usr/lib/ udisks2/ udisks2- inhibit /usr/sbin/ gpartedbin