Sorry, I really can't reproduce this, so please who is affected should help in debugging. You can just install bamf-dev from repositories, and download and extract the latest bamfdaemon .tar.gz you can find at http://packages.ubuntu.com/precise/bamfdaemon
Then, a way to get a more helpful stack trace should be: - Open a terminal, and keep it always on top, so you can do something else when the daemon will crash - cd to the bamfdaemon source directory (i.e. the "src" .tar.gz directory, where the main.c file is) - The point above can be done also setting manually the bamf's src directory on gdb using the "directory" command - Do: sudo gdb -p $(pidof bamfdaemon) 2>&1 | tee gdb-bamf.txt - Wait gdb to be loaded and press "c", then Return. - Now the daemon will continue running, start playing with your application until you get a crash. - At that point go back to gdb, write "bt full", press Return and attach the generated gdb-bamf.txt stacktrace file to this bug ;) - Then exit gdb with Ctrl+D bamfdaemon should be reloaded automatically, if it doesn't a "killall -9 bamfdaemon" could help You can get more informations about gdb at https://wiki.ubuntu.com/Backtrace ** Also affects: bamf Importance: Undecided Status: New ** Changed in: bamf Status: New => Triaged ** Changed in: bamf Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/926208 Title: bamfdaemon crashed with SIGABRT in g_assertion_message() To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/926208/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
