-
-
Notifications
You must be signed in to change notification settings - Fork 348
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
Crash on start under Ubuntu 16.04 #1871
Comments
Do you have the |
How would I know? I just freshly installed mono... |
OK, now it says: |
OK, installed transaction too. How deep do I have to follow this? |
No idea where to go now. mono ./ckan.exe |
Are you trying to build CKAN from source? |
No. Just put the ckan.exe into an empty folder. |
And you got that from the current release? |
Latest Releas "StarTrammier" |
I've just upgraded to Ubuntu 16.04, but I have Mono 4.4.2 from the mono-project.org PPA, and it's working fine for me. |
And you've done |
Yes, did that |
That's what's Ubuntu's providing. To get 4.4.2, you have to go upstream to the mono-project ppa. |
But 4.2.1 ought to work, unless Ubuntu have b0rked it. |
There's the |
Oh, yes, definitely need |
Installing... |
...aaaaaand: Works like a charm! |
Was that installing mono-complete, or switching to the mono-project PPA that fixed it? |
Yes, last step with mono-complete soved it. |
CKAN Version:
1.18.1
mono 4.2.1
certs are synced
Operating System:
ubuntu 16.04
The issue you are experiencing:
mono ./ckan.exe crashes on start.
Same for new empty diectory as for old directory with 100+ mods installed.
How to recreate this issue:
see above. launching it as "mono ckan" or "ckan" does crash every time.
CKAN error codes (if applicable):
Unhandled Exception:
System.TypeInitializationException: The type initializer for 'CKAN.CmdLine.MainClass' threw an exception. ---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies.
File name: 'System.Core, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
at log4net.Repository.Hierarchy.DefaultLoggerFactory+LoggerImpl..ctor (System.String name) <0x40298000 + 0x00013> in :0
The text was updated successfully, but these errors were encountered: