BeagleDaemon.exe crashed with SIGSEGV in mono_class_from_typeref()

[Ulrich Beyer]

Binary package hint: beagle

This happens consistently after upgrading from 7.10 to 8.04.
When starting beagled BeagleDaemon.exe crashes after a few seconds.
This also happens when no ~/.beagle directory exists.
My home directory is on a NFS volume.

ProblemType: Crash
Architecture: amd64
Date: Sun Mar 16 10:09:37 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/lib/beagle/BeagleDaemon.exe
InterpreterPath: /usr/bin/mono
NonfreeKernelModules: nvidia
Package: beagle 0.3.3-1ubuntu1
PackageArchitecture: amd64
ProcCmdline: beagled /usr/lib/beagle/BeagleDaemon.exe --replace --bg
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=de_DE.UTF-8
Signal: 11
SourcePackage: beagle
StacktraceTop:
 mono_class_from_typeref ()
 mono_class_get_full ()
 ?? ()
 ?? ()
 mono_class_init ()
Title: BeagleDaemon.exe crashed with SIGSEGV in mono_class_from_typeref()
Uname: Linux 2.6.24-12-generic x86_64
UserGroups: adm admin audio avahi avahi-autoipd cdrom dialout dip floppy fuse haldaemon lpadmin netdev plugdev powerdev pulse pulse-access pulse-rt sambashare scanner vboxusers video

[Apport retracing service (apport)]

StacktraceTop:mono_class_from_typeref ()
mono_class_get_full ()
?? ()
?? ()
mono_class_init ()

[dBera (dbera-web)]

See if this helps:
https://bugs.launchpad.net/ubuntu/+source/beagle/+bug/194608

[Pedro Villavicencio (pedro)]

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!.