telepathy-salut assert failure: telepathy-salut: glib-watch.c:205: timeout_free: Assertion `!t->dead' failed.

[P. Oscar Boykin]

Binary package hint: telepathy-salut

This was an automatically generated report. I don't recall the app crashing, but I guess it may have done so on shutdown.

This is on a system that was recently upgraded from 9.04 to 9.10. I did the upgrade using the alternate CD image, but there have been some issues since the upgrade with stability.

ProblemType: Crash
Architecture: i386
AssertionMessage: telepathy-salut: glib-watch.c:205: timeout_free: Assertion `!t->dead' failed.
Date: Fri Oct 30 17:33:43 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/telepathy/telepathy-salut
Package: telepathy-salut 0.3.10-1
ProcCmdline: /usr/lib/telepathy/telepathy-salut
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
Signal: 6
SourcePackage: telepathy-salut
StacktraceTop:
 __kernel_vsyscall ()
 *__GI_raise (sig=6)
 *__GI_abort () at abort.c:92
 *__GI___assert_fail (assertion=0x2f0cc3 "!t->dead",
 ?? () from /usr/lib/libavahi-glib.so.1
Title: telepathy-salut assert failure: telepathy-salut: glib-watch.c:205: timeout_free: Assertion `!t->dead' failed.
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
XsessionErrors:
 (gnome-settings-daemon:3726): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:3726): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:3771): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:3761): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #441694, 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.