| 1 |
On 20/08/13 09:21, Grant wrote: |
| 2 |
>>>>>>> This is actually a portage question. How can I install udisks-2 in a |
| 3 |
>>>>>>> way that will fix this problem? I'm confused by how to handle the |
| 4 |
>>>>>>> slotting behavior. |
| 5 |
>>>> |
| 6 |
>>>> |
| 7 |
>>>> I think the issue here is that we are not understanding what the |
| 8 |
>>>> problem is. It happens with an application in particular, or with a |
| 9 |
>>>> desktop environment? It happens when you try to umount the device, or |
| 10 |
>>>> when you disconnect it from the computer? Do you loose data in the |
| 11 |
>>>> camera, or when transferring photos to your computer? Or is only that |
| 12 |
>>>> you don't like the error reported? |
| 13 |
>>> |
| 14 |
>>> |
| 15 |
>>> When trying to eject a USB camera in thunar in xfce4, the error |
| 16 |
>>> appears and the device does not umount. Here is a command that also |
| 17 |
>>> produces the error: |
| 18 |
>> |
| 19 |
>> |
| 20 |
>> [ ... ] |
| 21 |
>> |
| 22 |
>> Just saying you should be using `udisksctl` command instead of the now |
| 23 |
>> obsolete `udisks` command |
| 24 |
>> |
| 25 |
>> udisksctl command = new udisks 2 |
| 26 |
>> udisks command = old udisks 1 |
| 27 |
> |
| 28 |
> OK, but first I need to figure out how to get gvfs to use udisks instead of gdu. |
| 29 |
> |
| 30 |
> - Grant |
| 31 |
> |
| 32 |
|
| 33 |
by emerging gnome-base/gvfs from ~arch with USE="udev udisks" |
| 34 |
|
| 35 |
the stable gnome-base/gvfs is not compatible with UDisks 2.1 |
| 36 |
|
| 37 |
but by upgrading gnome-base/gvfs on stable to ~arch version with |
| 38 |
USE="udev udisks" is then again not compatible all the way with GNOME |
| 39 |
2.x, so that's why it's still in ~arch |
Archives