Ubuntu
notification-daemon package

notification-daemon crashed with SIGSEGV in g_main_context_dispatch()

Bug #530153 reported by tysinsh
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
notification-daemon (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Binary package hint: notification-daemon

On system startup, popped up the notification about crush. No actions were taken by me before. Hope this brief helps.

ProblemType: Crash
Architecture: i386
Date: Mon Mar 1 19:34:20 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/notification-daemon/notification-daemon
NonfreeKernelModules: nvidia
Package: notification-daemon 0.4.0-1ubuntu3
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-20.57-generic
Signal: 11
SourcePackage: notification-daemon
StacktraceTop:
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_main_loop_run () from /lib/libglib-2.0.so.0
 gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
Title: notification-daemon crashed with SIGSEGV in g_main_context_dispatch()
Uname: Linux 2.6.31-20-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape video
SegvAnalysis:
 Segfault happened at: 0x6e30ff: call *%eax
 PC (0x006e30ff) ok
 source "*%eax" (0x098b79b8) ok
 destination "(%esp)" (0xbfa60d60) ok
 SP (0xbfa60d60) ok
 Reason could not be automatically determined.
SegvReason: Reason could not be automatically determined.

See original description
Revision history for this message
tysinsh (anton-troshin) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? () from /lib/libglib-2.0.so.0
g_main_context_dispatch () from /lib/libglib-2.0.so.0
?? () from /lib/libglib-2.0.so.0
g_main_loop_run () from /lib/libglib-2.0.so.0
IA__gtk_main ()

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in notification-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Kees Cook (kees)
description: updated
Revision history for this message
Robert Roth (evfool) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

visibility: private → public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

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

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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