Hi all, I have a possible cause of this bug you experienced. The virtual machine (mono-jit), the mono runtime libraries (libmono0) and the corlib (libmono-corlib*-cil) are not in sync (version wise).
This could happen by mixing Mono packages between testing and unstable, still this situation should not be possible with strict enough dependencies. mono-jit and libmono-corlib*-cil are forced to be in sync, but not libmono0. To be sure that this is the problem, please reply to this email with giving me the output of: COLUMNS=250 dpkg -l | grep mono Please reply ASAP, this is a show stopper for Mono in testing. PS: This problem can't happen with the current Mono in unstable, because libmono0 is statically linked (as of mono 1.1.17.1-2) -- Regards, Mirco 'meebey' Bauer PGP-Key: http://keyserver.noreply.org/pks/lookup?op=get&search=0xEEF946C8 -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d s-:+ a-- C++ UL++++$ P L++$>+++$ E- W+++$ N o? K- w++>! O---- M- V? PS PE+ Y- PGP++ t 5+ X++ R tv+ b+ DI? D+ G>++ e h! r->++ y? ------END GEEK CODE BLOCK------
signature.asc
Description: This is a digitally signed message part
