Hmmm, Well ideally, you can report this under beagle in Debian, and they weill reassign it to the appropriate place (which I'm sorry to say I don't know where that is) and they should at least let you know if its a configuration problem, or a known issue. Unfortunately, its really a bug in dbus, and most packagers have beagle marked correctly as relying on galago/dbus if that feature is active, but it looks like the dependency tree broke in debian... A short/possible solution would probably be installing/reinstalling your dbus packages. =/ Sorry I can't be of more help, I'm gonna look for a way to remove the chance of this killing us, but it looks like we have to keep it.. Debian bug reporting (sorry its so complicated, if you can't get it, e-mail me the info, and I'll file one..) http://www.debian.org/Bugs/Reporting Cheers, Kevin Kubasik On Thu, 2007-03-08 at 22:38 +0100, Atte André Jensen wrote: > Hi > > I get a crash from beagle when clicking on an IM Conversation in > beagle-search. The following is the final output from beagle-search in > the term it was started in: > > ================================================================= > 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. > ================================================================= > > Aborted > > I'm running debian/etch, with Beagle Search 0.2.12 and Gaim 2.0.0beta5. > Any ideas if I could do anything about it? >
Attachment:
signature.asc
Description: This is a digitally signed message part