Unable to move or rename some items

[luisvalenzuelar]

I have this problem in Linux. It seems to happen when compiling latex quickly. It is like if compilation twice in same computer goes faster than internet, so server does not realise of the changes.

Worst is that it is not solved. It doesn't go away. So annoying.

PD: #1006 is similar issue but was closed without a reason.

[luisvalenzuelar]

Can this happen because the two computers do not have the same megasync version? To solve it, I had to select the cloud option, then go to sync debris, and manually restore from the cloud the edited documents.

[LyndsayVegan]

hi hoe did you select the Cloud option please? It only lets me select the Local option? thanks a lot

[hinst]

I have been getting this error lately on Windows, even though I do NOT compile any code in MEGA folder. I use only one PC. I am worried about loosing my files because the error message does not say what is wrong or which files are getting overwritten 🐞, and it's not like I can check every individual file manually after the error, because I have hundreds of files

[technikker]

I have been getting this error lately on Windows, even though I do NOT compile any code in MEGA folder. I use only one PC. I am worried about loosing my files because the error message does not say what is wrong or which files are getting overwritten 🐞, and it's not like I can check every individual file manually after the error, because I have hundreds of files

Always keep a local backup, especially now, since Mega is having a lot of issues the last few months. Although I would say the same for google/onedrive.

[mguzmann]

I have the same issue. I cannot choose the cloud files. This is super frustrating.

[zhampu]

Same Issue here

[ggand0]

+1
It doesn't show which file is causing the error and I'm unable to fix it manually

[mfm-mega]

Hello!

This type of error is the most complex one we face on a daily basis. There is no simple reason, there are many different scenarios and each of you may be in a different one.
That's why some of you see both options and some of you see only one. It depends on our analysis of the error.

That said, we are working on displaying the conflicting paths in the GUI so that you can manually analyze the problem when our solver fails.

In the meantime you can read the app log and search for the lines "Stall detected! stalled local path (MoveOrRenameCannotOccur):", there you can see which paths are causing the error so you can manually fix the problem.

You can find your logs in:

1. Windows: C:\Users<your_user>\AppData\Local\Mega Limited\MEGAsync\Logs
2. macOS: ~/Library/Application\ Support/Mega\ Limited/MEGAsync/Logs
3. Linux: .local/share/data/Mega Limited/MEGAsync/Logs

If you still have problems to detect the error in the logs, we will be happy to help you. Please reach our support team at https://mega.io/contact to provide logs and other related information about your issue. Once you have a ticket id, you can paste it here for reference.

Thank you!

[luisvalenzuelar]

Thank you. How to read those files in Linux? PS: last folder in path is with lowercase in Ubuntu: ".local/share/data/Mega Limited/MEGAsync/logs"

…

________________________________ From: Mauro Ferreiro ***@***.***> Sent: 25 February 2025 09:03 To: meganz/MEGAsync ***@***.***> Cc: Luis Valenzuela ***@***.***>; Author ***@***.***> Subject: Re: [meganz/MEGAsync] Unable to move or rename some items (Issue #1014) Hello! This type of error is the most complex one we face on a daily basis. There is no simple reason, there are many different scenarios and each of you may be in a different one. That's why some of you see both options and some of you see only one. It depends on our analysis of the error. That said, we are working on displaying the conflicting paths in the GUI so that you can manually analyze the problem when our solver fails. In the meantime you can read the app log and search for the lines "Stall detected! stalled local path (MoveOrRenameCannotOccur):", there you can see which paths are causing the error so you can manually fix the problem. You can find your logs in: 1. Windows: C:\Users<your_user>\AppData\Local\Mega Limited\MEGAsync\Logs 2. macOS: ~/Library/Application\ Support/Mega\ Limited/MEGAsync/Logs 3. Linux: .local/share/data/Mega Limited/MEGAsync/Logs If you still have problems to detect the error in the logs, we will be happy to help you. Please reach our support team at https://mega.io/contact to provide logs and other related information about your issue. Once you have a ticket id, you can paste it here for reference. Thank you! — Reply to this email directly, view it on GitHub<#1014 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADMLWAFWF77R54VIBPIGQAD2RRLX3AVCNFSM6AAAAABRCHI26GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBRG4ZTKMZXGY>. You are receiving this because you authored the thread.Message ID: ***@***.***> [mfm-mega]mfm-mega left a comment (meganz/MEGAsync#1014)<#1014 (comment)> Hello! This type of error is the most complex one we face on a daily basis. There is no simple reason, there are many different scenarios and each of you may be in a different one. That's why some of you see both options and some of you see only one. It depends on our analysis of the error. That said, we are working on displaying the conflicting paths in the GUI so that you can manually analyze the problem when our solver fails. In the meantime you can read the app log and search for the lines "Stall detected! stalled local path (MoveOrRenameCannotOccur):", there you can see which paths are causing the error so you can manually fix the problem. You can find your logs in: 1. Windows: C:\Users<your_user>\AppData\Local\Mega Limited\MEGAsync\Logs 2. macOS: ~/Library/Application\ Support/Mega\ Limited/MEGAsync/Logs 3. Linux: .local/share/data/Mega Limited/MEGAsync/Logs If you still have problems to detect the error in the logs, we will be happy to help you. Please reach our support team at https://mega.io/contact to provide logs and other related information about your issue. Once you have a ticket id, you can paste it here for reference. Thank you! — Reply to this email directly, view it on GitHub<#1014 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ADMLWAFWF77R54VIBPIGQAD2RRLX3AVCNFSM6AAAAABRCHI26GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOBRG4ZTKMZXGY>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[page200]

Thank you, the log message with MoveOrRenameCannotOccur pointed to a directory (folder) that didn't exist anymore. I created that directory, waited (the app status turned to "Up to date"), closed the issues window, opened it again (because there was still a red button for that), closed it again, and that solved the problem. After that, I deleted the directory, and the issue didn't reappear. 👍

@luisvalenzuelar Try something like grep 'MoveOrRenameCannotOccur' '.local/share/data/Mega Limited/MEGAsync/logs/MEGAsync.log'