The filemanager UI used to (I am not sure if it still does) create 2 instances of DirModel class, the second instance was used to check paths being typed by the user, this second instance can be responsible to issue the message "Ignoring path change request, request already running...", I do not remember, it would require some investigation.
The "libsmbclient" is hard to work with, but filemanager used to work fine, any change in the "libsmbclient" can affect the filemanager.
Another thing is, the filemanager used to embed the "libsmbclient" in its package (I do not know if it is active or not), it was done because we could not install "libsmbclient" on the phone due to space restrictions (talk to Popey about this), this is something that needs to investigated to make sure which "libsmbclient" version is being loaded by the filemanager.
The filemanager UI used to (I am not sure if it still does) create 2 instances of DirModel class, the second instance was used to check paths being typed by the user, this second instance can be responsible to issue the message "Ignoring path change request, request already running...", I do not remember, it would require some investigation.
The "mAwaitingResults" is set to false in DirModel: :onItemsFetched (), see bazaar. launchpad. net/~ubuntu- filemanager- dev/ubuntu- filemanager- app/trunk/ view/head: /src/plugin/ folderlistmodel /dirmodel. cpp#L539.
http://
The "libsmbclient" is hard to work with, but filemanager used to work fine, any change in the "libsmbclient" can affect the filemanager.
Another thing is, the filemanager used to embed the "libsmbclient" in its package (I do not know if it is active or not), it was done because we could not install "libsmbclient" on the phone due to space restrictions (talk to Popey about this), this is something that needs to investigated to make sure which "libsmbclient" version is being loaded by the filemanager.