bamfdaemon crashed with SIGABRT in raise()

[M@ts]

I do not know how this happened, I had several programs running
and when I finished them became panic message visible.

This was a new installed 12:04,

for about 4 days ago came new changes and
they destroyed the old 12:04 installation.
It was dead, was unable to boot.

// M@ts

Description: Ubuntu precise (development branch)
Release: 12.04

Programcentral för Ubuntu 5.1.8

mats@HP-6000-L:~$ apt-cache policy pkgname
N: Kunde inte hitta paketet pkgname

mats@HP-6000-L:~$ sudo apt-cache policy pkgname
[sudo] password for mats:
N: Kunde inte hitta paketet pkgname

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bamfdaemon 0.2.108-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3
Uname: Linux 3.2.0-14-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Sun Feb 5 23:44:33 2012
DuplicateOf: https://bugs.launchpad.net/bugs/926135
ExecutablePath: /usr/lib/bamf/bamfdaemon
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111129.1)
ProcCmdline: /usr/lib/bamf/bamfdaemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=sv_SE.UTF-8
Signal: 6
SourcePackage: bamf
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: bamfdaemon crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to precise on 2012-02-04 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #926135, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.