notification-daemon crashed with SIGSEGV in g_closure_invoke()

Bug #127904 reported by hawkes
210
Affects Status Importance Assigned to Milestone
notification-daemon (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: notification-daemon

On startup, instead of the notifications about network and battery, the crash dialog came up.

ProblemType: Crash
Architecture: amd64
Date: Tue Jul 24 10:16:29 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/notification-daemon/notification-daemon
Package: notification-daemon 0.3.7-1ubuntu2
PackageArchitecture: amd64
ProcCmdline: /usr/lib/notification-daemon/notification-daemon
ProcCwd: /
ProcEnviron:
 LANGUAGE=de_DE.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: notification-daemon
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
Title: notification-daemon crashed with SIGSEGV in g_closure_invoke()
Uname: Linux ela 2.6.22-8-generic #1 SMP Thu Jul 12 16:09:47 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip lpadmin plugdev pulse-rt scanner video

Tags: apport-crash
Revision history for this message
hawkes (hawkes) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_gtk_marshal_BOOLEAN__BOXED (closure=0x618960, return_value=0x7fffe16ea900, n_param_values=<value optimized out>, param_values=0x7fffe16eaa10,
IA__g_closure_invoke (closure=0x618960, return_value=0x7fffe16ea900, n_param_values=2, param_values=0x7fffe16eaa10, invocation_hint=0x7fffe16ea8c0)
signal_emit_unlocked_R (node=0x652d60, detail=0, instance=0x65d040, emission_return=0x7fffe16eac30, instance_and_params=0x7fffe16eaa10)
IA__g_signal_emit_valist (instance=0x65d040, signal_id=<value optimized out>, detail=0, var_args=0x7fffe16eac90)
IA__g_signal_emit (instance=0x2, signal_id=0, detail=32) at /build/buildd/glib2.0-2.13.7/gobject/gsignal.c:2243

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in notification-daemon:
importance: Undecided → Medium
Revision history for this message
sam tygier (samtygier) wrote :

also seen this in gutsy on amd64

Changed in notification-daemon:
status: New → Confirmed
Revision history for this message
Michael Vogt (mvo) wrote :

I commited some changes into the hardy version of notification-daemon. I hope this fixes the issues. Feedback is very welcome. I was not able to reproduce this problem myself yet, any hints on how to trigger it would be greatly appreciated.

Thanks,
 Michael

Revision history for this message
Hew (hew) wrote :

There have been no comments about this problem since Michael Vogt's changes were committed, so I'm marking this as Fix Released. Thanks for your report.

Changed in notification-daemon:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.