-
Notifications
You must be signed in to change notification settings - Fork 807
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Shortcuts generate errors #7579
Comments
Idem for me with Windows 11 |
Idem with Win11 23h2 |
@xXFreeFunXx @Mika-6-9 @Tormak3D sorry for that |
Only update to the last version of the desktop app, nothing before. |
@mgallien I send you account detalis via email, which has dummy files wich fail to sync. |
I was not able to reproduce the issue by creating new windows shortcuts in that test account but at least the same issue occours when I copy files / shortcuts which have issues in other accounts. I suspect it is due to the saved properties of the shortcut. Are these read by Nextcloud Client? |
Seeing this also after updating to 3.15 this morning |
thanks to all that send me logs. That is really nice and appreciated 💙 |
I have the same problem. I uninstalled the Nextcloud Desktop Client, but now I get the error message "The cloud file provider is not running" when trying to open a Windows shortcut. How can I restore these Windows shortcut files? |
We have a couple of users on 3.15.0 who were hit with this. So this happens when there is a .lnk file in an Nextcloud folder. The .lnk file points to another folder (i think to a folder outside Nextcloud). The client tries to sync, then fail and try again a few seconds later, endlessly. It will never sync any files. After removing the .lnk file it syncs perfectly. This should be easy to reproduce. I got a debug log off one of the Windows 3.15.0 clients. It had this "Downloads - Snelkoppeling.lnk" file. Speculation: i am i seeing this right that it is trying to "follow" the link? That's not good. Here's the log, the relevant part (i did replace some file names and the username for privacy reasons). The error/phrase "Het systeem kan het opgegeven pad niet vinden" means "The system cannot find the specified path" in Dutch:
Off-topic: sadly we first had our entire organization hit by the "file too long" bug that crashed all or at least dozens of Nextcloud clients (#7265 and #7258). So we upgraded to latest version and then we had people hit by this. At least this one only affects a couple of users, since it isn't really common to have .lnk files in your nextcloud folder. |
Bug description
After updating to 3.15.0, .lnk files throw errors. These were created a long time ago and have never caused problems.
Steps to reproduce
Update to 3.15.0 from 3.14.0
Expected behavior
That the error “Couldn't update placeholder info” does not occur!
Which files are affected by this bug
*.lnk
Operating system
Windows
Which version of the operating system you are running.
Windows 10
Package
Official Windows MSI
Nextcloud Server version
29.0.8
Nextcloud Desktop Client version
3.15.0
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 3.3.6 to 3.4.0)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Additional info
The text was updated successfully, but these errors were encountered: