libboo2.0-cil fails to install on armel

Bug #452066 reported by Loïc Minier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
boo (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: boo

Hi

When installing banshee, apt-get got hung when installing libboo2.0-cil:
Processing triggers for man-db ...
Processing triggers for hicolor-icon-theme ...
Processing triggers for desktop-file-utils ...
Setting up libboo2.0-cil (0.8.2.2960+dfsg-1) ...
* Installing 7 assemblies from libboo2.0-cil into Mono
Stacktrace:

  at string.Format (System.IFormatProvider,string,object[]) <0xffffffff>
  at string.Format (System.IFormatProvider,string,object[]) <0x00030>

Native stacktrace:

        [0xb]
        [(nil)]

Debug info from gdb:

Nothing else was printed and it just got stuck there.

Bye

ProblemType: Bug
Architecture: armel
Date: Thu Oct 15 12:58:02 2009
DistroRelease: Ubuntu 9.10
Package: libboo2.0-cil 0.8.2.2960+dfsg-1
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-206.14-dove
SourcePackage: boo
Uname: Linux 2.6.31-206-dove armv7l
XsessionErrors:
 (gnome-settings-daemon:1858): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1858): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:1919): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:1929): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Loïc Minier (lool) wrote :
Revision history for this message
Loïc Minier (lool) wrote :

root 1723 0.0 0.1 1668 532 pts/2 S+ 12:56 0:00 | \_ /bin/sh /var/lib/dpkg/info/libboo2.0-cil.postinst configure
root 1833 0.0 0.4 5584 2408 pts/2 S+ 12:56 0:00 | \_ /usr/bin/perl /usr/share/cli-common/gac-package-install libboo2.0-cil
root 1835 0.0 0.4 5432 2244 pts/2 S+ 12:56 0:00 | \_ /usr/bin/perl /usr/share/cli-common/runtimes.d/mono install libboo2.0-cil /usr/lib/cli/boo-2.0/Boo.Lang.CodeDom.dll /usr/lib/cli/boo-2.0/Boo.Lang.Compiler.dll /usr/lib/cli/boo-2.0/Boo.Lang.Extensions.dll /usr/lib/cli/boo-2.0/Boo.Lang.dll /usr/lib/cli/boo-2.0/Boo.Lang.Interpreter.dll /usr/lib/cli/boo-2.0/Boo.Lang.Parser.dll /usr/lib/cli/boo-2.0/Boo.Lang.Useful.dll
root 1847 0.0 0.0 0 0 pts/2 Z+ 12:56 0:00 | \_ [sh] <defunct>
root 1851 0.0 0.0 1668 496 pts/2 S+ 12:56 0:00 | \_ sh -c (cd `dirname /usr/lib/cli/boo-2.0/Boo.Lang.Compiler.dll` && /usr/bin/gacutil -i `basename /usr/lib/cli/boo-2.0/Boo.Lang.Compiler.dll` > /dev/null)
root 1852 0.4 1.5 20404 7916 pts/2 Tl+ 12:56 0:01 | \_ /usr/bin/mono /usr/lib/mono/2.0/gacutil.exe -i Boo.Lang.Compiler.dll
root 1863 19.0 3.5 22236 17916 pts/2 S+ 12:56 0:46 | \_ /usr/bin/gdb -ex attach 1852 --ex info threads --ex thread apply all bt --batch

Revision history for this message
Loïc Minier (lool) wrote :

After kill -9 on the gdb process, apt-get resumed; it passed on second try:
A package failed to install. Trying to recover:
Setting up libboo2.0-cil (0.8.2.2960+dfsg-1) ...
* Installing 7 assemblies from libboo2.0-cil into Mono

Setting up banshee (1.5.1~git2260a87-0ubuntu1) ...

Loïc Minier (lool)
Changed in boo (Ubuntu):
assignee: nobody → David Sugar (dyfet)
Revision history for this message
Oliver Grawert (ogra) wrote :
Revision history for this message
Oliver Grawert (ogra) wrote :

as you can see in the attached log it works fine here (install is from beta on a babbage 2.5 and been regulary updated)

Revision history for this message
Paul Larson (pwlars) wrote :

For the sake of completeness, I also tried this on dove, package version is the same as in the original report.
Setting up libboo2.0-cil (0.8.2.2960+dfsg-1) ...
* Installing 7 assemblies from libboo2.0-cil into Mono

Setting up libmono-zeroconf1.0-cil (0.9.0-1) ...
* Installing 5 assemblies from libmono-zeroconf1.0-cil into Mono

Setting up libnotify0.4-cil (0.4.0~r3032-1ubuntu1) ...
* Installing 1 assembly from libnotify0.4-cil into Mono

I'm thinking this was an odd fluke of some kind. We'll reopen or open a new bug if it ever resurfaces, but nobody seems to be able to reproduce this for now. Thanks!

Changed in boo (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.