Package: mono-complete Version: 5.18.0.240-0xamarin1+debian9b1 Severity: important
Dear Maintainer, Since an update in unstable, I can't run the KSP CKAN software (was working correctly few weeks ago). It crashes with the following error: Unhandled Exception: System.InvalidOperationException: object_op ---> System.BadImageFormatException: Method has no body at System.IO.CoreFX.FileSystemWatcher.StartRaisingEvents () [0x00024] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at System.IO.CoreFX.FileSystemWatcher.StartRaisingEventsIfNotDisposed () [0x0001c] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at System.IO.CoreFX.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean value) [0x0002a] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at (wrapper remoting-invoke-with-check) System.IO.CoreFX.FileSystemWatcher.set_EnableRaisingEvents(bool) at System.IO.CoreFXFileSystemWatcherProxy.<StartDispatching>m__0 (System.IO.CoreFX.FileSystemWatcher internal_fsw, System.IO.FileSystemWatcher fsw) [0x00048] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at System.IO.CoreFXFileSystemWatcherProxy.Operation (System.Action`4[T1,T2,T3,T4] map_op, System.Action`2[T1,T2] object_op, System.Object handle, System.Action`2[T1,T2] cancel_op) [0x001d3] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 --- End of inner exception stack trace --- at System.IO.CoreFXFileSystemWatcherProxy.Operation (System.Action`4[T1,T2,T3,T4] map_op, System.Action`2[T1,T2] object_op, System.Object handle, System.Action`2[T1,T2] cancel_op) [0x001f8] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at System.IO.CoreFXFileSystemWatcherProxy.StartDispatching (System.Object handle) [0x00007] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at System.IO.FileSystemWatcher.Start () [0x00024] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at System.IO.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean value) [0x00049] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at (wrapper remoting-invoke-with-check) System.IO.FileSystemWatcher.set_EnableRaisingEvents(bool) at CKAN.NetFileCache..ctor (System.String path) [0x000b6] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.NetFileCache..ctor (CKAN.KSPManager mgr, System.String path) [0x00000] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.NetModuleCache..ctor (CKAN.KSPManager mgr, System.String path) [0x00006] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.KSPManager.TrySetupCache (System.String path, System.String& failureReason) [0x0003d] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.KSPManager.LoadInstancesFromRegistry () [0x000ad] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.KSPManager..ctor (CKAN.IUser user, CKAN.IWin32Registry win32_registry) [0x00028] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.CmdLine.MainClass.Execute (CKAN.KSPManager manager, CKAN.CmdLine.CommonOptions opts, System.String[] args) [0x0015b] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.CmdLine.MainClass.Main (System.String[] args) [0x00091] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.InvalidOperationException: object_op ---> System.BadImageFormatException: Method has no body at System.IO.CoreFX.FileSystemWatcher.StartRaisingEvents () [0x00024] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at System.IO.CoreFX.FileSystemWatcher.StartRaisingEventsIfNotDisposed () [0x0001c] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at System.IO.CoreFX.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean value) [0x0002a] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at (wrapper remoting-invoke-with-check) System.IO.CoreFX.FileSystemWatcher.set_EnableRaisingEvents(bool) at System.IO.CoreFXFileSystemWatcherProxy.<StartDispatching>m__0 (System.IO.CoreFX.FileSystemWatcher internal_fsw, System.IO.FileSystemWatcher fsw) [0x00048] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at System.IO.CoreFXFileSystemWatcherProxy.Operation (System.Action`4[T1,T2,T3,T4] map_op, System.Action`2[T1,T2] object_op, System.Object handle, System.Action`2[T1,T2] cancel_op) [0x001d3] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 --- End of inner exception stack trace --- at System.IO.CoreFXFileSystemWatcherProxy.Operation (System.Action`4[T1,T2,T3,T4] map_op, System.Action`2[T1,T2] object_op, System.Object handle, System.Action`2[T1,T2] cancel_op) [0x001f8] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at System.IO.CoreFXFileSystemWatcherProxy.StartDispatching (System.Object handle) [0x00007] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at System.IO.FileSystemWatcher.Start () [0x00024] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at System.IO.FileSystemWatcher.set_EnableRaisingEvents (System.Boolean value) [0x00049] in <a9a08e39ba304bd0a84c49bd158dfc02>:0 at (wrapper remoting-invoke-with-check) System.IO.FileSystemWatcher.set_EnableRaisingEvents(bool) at CKAN.NetFileCache..ctor (System.String path) [0x000b6] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.NetFileCache..ctor (CKAN.KSPManager mgr, System.String path) [0x00000] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.NetModuleCache..ctor (CKAN.KSPManager mgr, System.String path) [0x00006] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.KSPManager.TrySetupCache (System.String path, System.String& failureReason) [0x0003d] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.KSPManager.LoadInstancesFromRegistry () [0x000ad] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.KSPManager..ctor (CKAN.IUser user, CKAN.IWin32Registry win32_registry) [0x00028] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.CmdLine.MainClass.Execute (CKAN.KSPManager manager, CKAN.CmdLine.CommonOptions opts, System.String[] args) [0x0015b] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 at CKAN.CmdLine.MainClass.Main (System.String[] args) [0x00091] in <2c2371fb3f2949b2a6dfae930758e6ee>:0 An issue has been opened : https://github.com/KSP-CKAN/CKAN/issues/2664 One solution is to use mono packaged by the mono-project. Don't know anything about mono, so I don't know how to better identify the problem. (the versions reported in the bug are the ones from mono-project. I was using the same versions (5.18.0.240) from unstable: was forced to pin the mono-project repository, see the issue in github.) -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.19.0-1-amd64 (SMP w/12 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mono-complete depends on: ii ca-certificates-m 5.18.0.240-0xamarin1+debian9b1 ii libmono-2.0-1 5.18.0.240-0xamarin1+debian9b1 ii libmono-cil-dev 5.18.0.240-0xamarin1+debian9b1 ii libmono-profiler 5.18.0.240-0xamarin1+debian9b1 ii mono-4.0-gac 5.18.0.240-0xamarin1+debian9b1 ii mono-4.0-service 5.18.0.240-0xamarin1+debian9b1 ii mono-csharp-shell 5.18.0.240-0xamarin1+debian9b1 ii mono-devel 5.18.0.240-0xamarin1+debian9b1 ii mono-jay 5.18.0.240-0xamarin1+debian9b1 ii mono-llvm-support 5.18.0.240-0xamarin1+debian9b1 ii mono-mcs 5.18.0.240-0xamarin1+debian9b1 ii mono-roslyn 5.18.0.240-0xamarin1+debian9b1 ii mono-runtime 5.18.0.240-0xamarin1+debian9b1 ii mono-runtime-sgen 5.18.0.240-0xamarin1+debian9b1 ii mono-utils 5.18.0.240-0xamarin1+debian9b1 ii monodoc-base 5.18.0.240-0xamarin1+debian9b1 ii monodoc-manual 5.18.0.240-0xamarin1+debian9b1 ii msbuild 1:16.0+xamarinxplat.2018.09.26.17.53-0xamarin3+debian9b1 ii referenceassembli 2014.04.14-1xamarin5+debian9b1 mono-complete recommends no packages. mono-complete suggests no packages. -- no debconf information
