-
-
Notifications
You must be signed in to change notification settings - Fork 297
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
System.ArgumentException: Illegal characters in path when launched using Wine #15520
Comments
Please test with the current snapshot build which has #12590 applied. |
Thank you for the support. Today, I just updated Cyberduck to 8.7.3 as I assumed that the fix will be contained. However, I still have the same error:
Here's the full log: I checked my Wine user profile directory. It's What else can I do to make it run? Still worth testing the snapshot build @dkocher mentioned? Thank you for support. |
We are getting into the weeds with IKVM and Wine. To resolve this, you may check whether removing the "~"-character and specifying an absolute path in all paths (tmp, userprofile, appdata, localappdata, etc.) resolves the issues you are seeing - though I'm not entirely sure this'll help you. Either way, this will require extensive amounts of work to be compatible with Wine, especially as this looks like an issue within IKVM, not Cyberduck. Footnotes |
Thanks for getting back to this @AliveDevil . The absolute path of my Wine user profile directory is In |
After a chat with people over at https://github.com/ikvmnet/ikvm it turns out that the stack trace you posted is actually from Mono, which has a bug in the linked method Can you please verify that you have at least The paths were just a guess, which don't need changes. |
Thanks for the investigation. I don't have winetricks installed yet. I have installed Wine Mono. Using latest version 8.1.0 . These are the installed packages. I will take time later today and install winetricks. |
Reporting back from installing winetricks as described on https://wiki.winehq.org/Winetricks . Unfortunately, it doesn't seem to work as expected. This is the warning message
So apparently, this seems to be a bug in winetricks. Nevertheless, I think winetricks isn't needed necessarily as I have Wine Mono already installed. When I tried to run Cyberduck with wine for the first time I had this error So, I can only wait for the bugfix in Wine Mono / ikvm or are there any other possible solutions / workarounds? |
So, I created a fresh OpenSuse 15.5 Leap VM, installed wine, winetricks and with that both dotnet40 and dotnet48, set the Wine-emulated version to Windows 10, and installed Cyberduck. This worked fine, until it tried loading types through WinRT:
e.g. need not to inline this method-call, as all types are preloaded at entry of method, thus it tries to load Windows Runtime-Types that aren't available in Wine. This particular issue could be fixed, but highlights several issues you'll run into when trying to emulate Cyberduck through Wine - there are several assumptions made in the Cyberduck Windows sources, that may crash or are not implemented, to the point, where it is impossible to use Cyberduck at all. |
Relates to #6061. |
@AliveDevil Thank you for your efforts to install and run Cyberduck with Wine. I could successfully fix my Winetricks installation applying this manual fix Winetricks/winetricks#2119 (comment) . Afterwards I installed Still, when launching Cyberduck I still have the same error. Did you use a Wine 64 bit prefix or Wine 32 bit prefix? I'm using a 64 bit prefix. Might give it a shot with a 32 bit prefix again. However, if Cyberduck still won't be usable with Wine due to the Windows sources assumptions that's definitely a blocker. I just need Cyberduck on Linux to view the contents of my remote Cryptomator vaults (on WebDav). Don't even need to download or upload files. Just viewing them would be enough in the first place. Do you think this is possible with Wine launched Cyberduck? If not, I'd also strongly vouch for a native Linux version of Cyberduck, as in #6061. Would also be willing to donate for that. How realistic is it that you guys could put that to the roadmap for this year? Thanks for an estimation. |
I suggest to use Cryptomator for Linux.
It is not realistic. It would require someone to step up and wanting to implement the user interface in Linux. This might be more straight forward when we rewrite the current user interface implementation for Windows using XAML/WinUI frameworks 1 that might be reusable on Linux. Footnotes |
I already use Cryptomator for Linux. The issue is that I have really big vaults with several 100 GB stored in my cloud. I can't download all of them locally because of limited space on my notebook. However, I started to restructure my remote vaults and make them smaller using Cyberduck on Windows. I wanted to continue to do that on Linux but then apparently for now I need to switch back to Windows to accomplish that task.
That's sad to read. If ever it gets put on the roadmap I would be willing to contribute financially and code-wise. |
I just gave this issue another try and tried to run Cyberduck using Bottles on Ubuntu 22.04 LTS which looks more promising than my last attempt. At least I don't run into the error I initially posted here. However, I run into another one and Cyberduck still doesn't launch.
My bottle runs with Win64 and soda-8.0-2 having |
Should be the same issue as mentioned here. Cyberduck isn't "just" using Win32 APIs, that are available in Wine, but makes extensive use of several Windows Runtime-types (introduced between Windows 8 and Windows 11), that may not be available in Wine at the moment. Some other parts, that I'm not sure are implemented completely:
|
Describe the bug
Cyberduck crashes at launch. It doesn't even start. There is no UI to be seen.
To Reproduce
Steps to reproduce the behavior:
Cyberduck.exe
or run commmandwine Cyberduck.exe
on Ubuntu.Expected behavior
Cyberduck should launch successfully.
Screenshots
None as there is no UI to be seen.
Desktop (please complete the following information):
Log Files
Log file generated with
wine Cyberduck.exe &>log.txt
.log.txt
I believe this part is relevant.
Additional context
It seems to be the same error message as here #11911. So, may be the same fix can be applied.
FYI: I'm running on Ubuntu derivative with Wine.
The text was updated successfully, but these errors were encountered: