Your message dated Wed, 27 Sep 2006 13:45:19 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Bug#389334: possible cause
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: libdbus-1-cil
Version: 0.62-4
Severity: grave
Justification: renders package unusable
Upgrade of libdbus-1-cil is impossible.
The error seems to come from threadpool.c: line 990
(mono_thread_pool_init)
Here is the full error message:
Preparing to replace libdbus-1-cil 0.62-4 (using
..../libdbus-1-cil_0.63.git.2006
0719-4_all.deb) ...
Removing libdbus-1-cil from Mono
** ERROR **: file threadpool.c: line 990 (mono_thread_pool_init):
assertion fail
ed: (async_call_klass)
aborting...
=================================================================
Got a SIGABRT while executing native code. This usually indicates
a fatal error in the mono runtime or one of the native libraries
used by your application.
=================================================================
Stacktrace:
Native stacktrace:
/usr/lib/libmono.so.0(mono_handle_native_sigsegv+0x113) [0xb7e205fa]
/usr/lib/libmono.so.0 [0xb7df51e2]
[0xffffe440]
/lib/tls/libc.so.6(abort+0x109) [0xb7ba10c9]
/usr/lib/libglib-2.0.so.0(g_logv+0x454) [0xb7d33114]
/usr/lib/libglib-2.0.so.0(g_log+0x29) [0xb7d33149]
/usr/lib/libglib-2.0.so.0(g_assert_warning+0x77) [0xb7d331c7]
/usr/lib/libmono.so.0(mono_thread_pool_init+0x16a) [0xb7eb68de]
/usr/lib/libmono.so.0(mono_runtime_init+0x23) [0xb7ebdc65]
/usr/lib/libmono.so.0(mini_init+0xb34) [0xb7df64f3]
/usr/lib/libmono.so.0(mono_main+0x1388) [0xb7e12922]
/usr/bin/mono [0x8048522]
/lib/tls/libc.so.6(__libc_start_main+0xc8) [0xb7b8bea8]
/usr/bin/mono [0x8048471]
sh: line 1: 7269 Aborted /usr/bin/mono
/usr/lib/mono/1.0/gacuti
l.exe /u dbus-sharp, Version=0.60.0.0, Culture=neutral,
PublicKeyToken=9eef26920
33670f5 >/dev/null
E: removing Assembly dbus-sharp, Version=0.60.0.0, Culture=neutral,
PublicKeyTok
en=9eef2692033670f5 failed
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686-pte
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages libdbus-1-cil depends on:
ii cli-common 0.4.3 common files between all CLI (.NET
ii libdbus-glib-1-2 0.71-2 simple interprocess messaging syst
ii libmono-corlib1.0-cil 1.1.13.8-1 Mono core library (1.0)
libdbus-1-cil recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.1.17.1-4
On Wed, Sep 27, 2006 at 02:56:30PM +0200, Mirco Bauer wrote:
> 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)
That being the case, I believe the correct action is to close the bug with
version tracking to document that it's fixed in unstable, and then get this
version into testing so that the bugs of the previous version become
irrelevant :)
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
--- End Message ---
