notification-daemon crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()

[Andrew Conkling]

Binary package hint: notification-daemon

I saw a notification pop up briefly. I'm not sure what popped it up, but I was opening a movie in VLC at the time, so that might have been it.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Fri Jul 27 00:31:35 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/notification-daemon/notification-daemon
NonfreeKernelModules: cdrom
Package: notification-daemon 0.3.7-1ubuntu2
PackageArchitecture: i386
ProcCmdline: /usr/lib/notification-daemon/notification-daemon
ProcCwd: /
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/zsh
Signal: 11
SourcePackage: notification-daemon
StacktraceTop:
 _gtk_marshal_BOOLEAN__BOXED (closure=0x80978c0,
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 ?? ()
Title: notification-daemon crashed with SIGSEGV in _gtk_marshal_BOOLEAN__BOXED()
Uname: Linux SnappyLappy 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:_gtk_marshal_BOOLEAN__BOXED (closure=0x80978c0, return_value=0xbfe45280, n_param_values=2, param_values=0xbfe4538c, invocation_hint=0xbfe4526c,
IA__g_closure_invoke (closure=0x80978c0, return_value=0xbfe45280, n_param_values=2, param_values=0xbfe4538c, invocation_hint=0xbfe4526c)
signal_emit_unlocked_R (node=0x8081930, detail=0, instance=0x8087048, emission_return=0xbfe4554c, instance_and_params=0xbfe4538c)
IA__g_signal_emit_valist (instance=0x8087048, signal_id=45, detail=0, var_args=0xbfe455d0 "��\204V�p\b\b\224�b\b��\b")
IA__g_signal_emitv (instance_and_params=0x8087048, signal_id=45, detail=0, return_value=0xbfe45684) at /build/buildd/glib2.0-2.13.7/gobject/gsignal.c:2031

[Hew (hew)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[Hew (hew)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!