-
-
Notifications
You must be signed in to change notification settings - Fork 346
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
Linux (mono): v1.18.0 refuses to run. #1791
Comments
What's your mono version? |
$ mono -V |
Also happens for me, with the same mono version. Solution was upgrading to the latest (4.4.0) mono version by following the instructions from http://www.mono-project.com/docs/getting-started/install/linux/#debian-ubuntu-and-derivatives . |
We removed support for testing against mono 3.2.8 in #1715. I'm not sure exactly when we stopped being compatible, but between v1.16.1 and v1.18.0 obviously, so this is something we should be able to find using Mono 3.2.8 is filled with bugs compared to more modern releases, but it's also extremely widespread on Linux, particularly the Debian/Ubuntu/Mint ecosystems, which is a lot of our overall user-base. I have partial blame to for this. I saw that testing on 3.2.8 had been removed as part of the last release, and didn't say "hey, are we really sure we want to do that?". I'm not around anywhere near as much as I'd like, so I'm not the one to champion a return for 3.2.8 support, but it's certainly thing I think would be nice to have, and definitely in the interests of our users. |
It may be an idea to rollback a little and put support for Mono 3.2.8 back in as a backport until Debian/Ubuntu pulls the newer Mono into stable? |
fixed by #1784 |
CKAN Version: v1.18.0 (v1.16.1 works fine)
Operating System: Linux (BunsenLabs (Debian 8), with SteamOS repos for nvidia driver updates)
The issue you are experiencing: CKAN v1.18.0 won't even show its window, but crashes instead.
How to recreate this issue: Run v1.18.0 through mono.
CKAN error codes (if applicable): CKAN window won't appear, so none?
The text was updated successfully, but these errors were encountered: