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
_______________________________________________ Amarok-devel mailing list Amarok-devel@kde.org https://mail.kde.org/mailman/listinfo/amarok-devel
