Amarok startup blocks when NFS mounts are not accessible

[Bart Cerneels]

first on: NfsDeviceHandlerFactory::canHandle()

NfsDeviceHandler.cpp:153 KMountPoint::Ptr m =
KMountPoint::currentMountPoints().findByPath( access->filePath() );


Then after forcefully unmounting the shares, m is valid and
canHandle() returns true, then it blocks on the next call to
NfsDeviceHandler where exactly the same function is excecuted:

MountPointManager.cpp:503 DeviceHandler *handler =
factory->createHandler( device, udi, m_storage );

This might have been a fluke caused by unmouting while it was blocked
on the previous


Seems MountPointManager is another one of those rotten codebases that
need review and cleanup.


Bart
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/amarok-devel/attachments/20120817/90e8ba13/attachment.html>