-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 07/11/2011 10:46 AM, David Zeuthen wrote:
> Note that this is now controllable via the UDISKS_AUTOMOUNT_HINT property, see
I thought all such malarkey was simply supposed to go away because there
is just no good way to decide what the correct value
Hi
On Mon, Jul 11, 2011 at 9:25 AM, Tom Gundersen wrote:
> On Mon, Jul 11, 2011 at 12:58 AM, Ansgar Burchardt wrote:
>> I reported a bug in KDE [1] about eSATA drives not being seen as a
The problem with eSATA, in a nutshell, is that there is no reliable
way of figuring out if a device is conne
On Mon, Jul 11, 2011 at 12:58 AM, Ansgar Burchardt wrote:
> I reported a bug in KDE [1] about eSATA drives not being seen as a
> "removable" device (in KDE's device manager). I believe this is a bug
> in KDE's solid as they do not use the correct properties from udisks,
> however they disagree.
Hi,
I reported a bug in KDE [1] about eSATA drives not being seen as a
"removable" device (in KDE's device manager). I believe this is a bug
in KDE's solid as they do not use the correct properties from udisks,
however they disagree.
The device manager shows by default "hotpluggable" and "remova
The thing is that i do not know what to blame.
I consider this change necessary to cope with misbehaving hardware.
The hardware affected by this is the ones that
1: Does not interrupt on state change.
2: Reports state change late.
Because there is no way of knowing if the hardware is fawlty the
On 10 July 2011 21:34, Mikael Hjelm wrote:
> - not if we've guessed the state to be fully charged */
> - supply->priv->enable_poll = (state !=
> UP_DEVICE_STATE_FULLY_CHARGED);
> + not if we've guessed the state to be fully charged. This
> function
> + has been dis
