notification-daemon crashed with signal 5 in g_return_if_fail_warning()

[steinhauser christian]

vv

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: notification-daemon 0.7.6-1
ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3
Uname: Linux 3.8.0-0-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
CrashCounter: 1
Date: Fri Jan 18 22:46:09 2013
ExecutablePath: /usr/lib/notification-daemon/notification-daemon
ExecutableTimestamp: 1351469005
InstallationDate: Installed on 2013-01-01 (17 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121231)
MarkForUpload: True
ProcCmdline: /usr/lib/notification-daemon/notification-daemon
ProcCwd: /home/test
ProcEnviron:
 LANGUAGE=fr:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: notification-daemon
StacktraceTop:
 g_return_if_fail_warning (log_domain=log_domain@entry=0x7f89548a1846 "Gdk", pretty_function=pretty_function@entry=0x7f89548a33b0 <__PRETTY_FUNCTION__.29144> "gdk_error_trap_pop_internal", expression=expression@entry=0x7f89548a2d06 "trap != NULL") at /build/buildd/glib2.0-2.35.4/./glib/gmessages.c:1016
 gdk_error_trap_pop_internal (need_code=0) at /build/buildd/gtk+3.0-3.6.4/./gdk/gdkdisplay.c:2146
 ?? () from /usr/lib/x86_64-linux-gnu/gtk-3.0/modules/libcanberra-gtk-module.so
 gdk_threads_dispatch (data=0xeb64c0) at /build/buildd/gtk+3.0-3.6.4/./gdk/gdk.c:788
 g_main_dispatch (context=0xd66240) at /build/buildd/glib2.0-2.35.4/./glib/gmain.c:2784
Title: notification-daemon crashed with signal 5 in g_return_if_fail_warning()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #1013693, 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.