[Kde-hardware-devel] Re: 4.7 Release is coming, are we ready?

[Jacopo De Simoi]

> Hi there fellow metalworkers!
> 
> I just noticed that we're 1 month and a few days away from the KDE SC 4.7 
> releae, so I thought that would be a good idea to ask this question, are we 
> ready?
> 
> From my side, there are a few things to fix or to improve before the release:
> 
> BlueDevil 1.2 must be released on time, with better kio_obexftp support and 
> fixing all crashes.
> 
> LibSolid: I'd like to take a look at one crash and fix the support for iPod 
> devices, one of the most requested features.
> 
> If you have any doubts just aks :) these are my questions:

There are a few bugreports that have been reported against
the device notifier and that are indeed mostly relevant to
solid-udisks

https://bugs.kde.org/show_bug.cgi?id=270490
https://bugs.kde.org/show_bug.cgi?id=274982

which are indeed related to the fix to

https://bugs.kde.org/show_bug.cgi?id=267398

and in general to the udisks teardown routine, which 
appears to have some issues; 
Would it be possible to coordinate some tests among us 
using different removable devices to see if the first two bugs
can be reproduced?

Apparently there are issues when deciding if and how 
a device should be ejected on unmount.
At the moment the fix to bug 267398 forces 
basically all devices with a valid parent device to be
ejected, even if they don't require so, since 
apparently most devices don't set the "DriveIsEjectable" 
property when they should. This causes bug 270490.
Something related should indeed cause bug 274982.

I don't believe the current approach (eject anyways) is correct, 
if the device doesn't set the property correctly, there should
be a udev rule to fix that instead,
pretty much as we solvedthe eSATA business.

Thanks
  __J

-- Plasma Device Notifier mantainer