polmr

Thanks for reporting that @KissesRefined The above log hammering will be fixed in next MEGAcmd version. In the meantime reducing log level would be a workaround. Log level configuration is...

> that a second instance of the server is running if there were no `mega-cmd-server` process running, that could have been because there was a `~/.megaCmd/lockMCMD` when it shouldn't be...

Hi @nunob37 , The issue is heppening because MEGAcmd 1.5.1 is not compatible with new share folders. We will release a new version of MEGAcmd for Raspbian 10 & Raspbian...

You may want to update to a newer MEGAcmd (see https://mega.io/nas)

That would be an intel 64 architecture. Would you mind trying `megacmdpkg-kvmx64-1.6.3-0001.spk` ?

You need to have MEGAsync running (and logged in IIRC) to avoid that warning. In any case, we will review the extension code to try to avoid that logging flooding....

Thanks @dirkdavidis The _smart_ option will be available in the future, but is yet pending. For the time being you can use _megasync_ for that. Apologies for any inconvenience and...

Hi @cezar-pimentel Is the issue persistent? Perhaps you can try to use the Desktop application (https://mega.io/desktop). With it, you can increase the number of connections per transfers to boost single-upload...

What are the steps you follow to try and compile it? This should do: ``` cd src/MEGAShellExtDolphin/ mv CMakeLists_kde5.txt CMakeLists.txt cmake -DCMAKE_INSTALL_PREFIX="`kf5-config --prefix`" $PWD make ``` Notice there are two...

In case you can spot any difference: cmake -DCMAKE_INSTALL_PREFIX="`kf5-config --prefix`" $PWD ``` -- The C compiler identification is GNU 5.4.0 -- The CXX compiler identification is GNU 5.4.0 -- Check...