Ubuntu
notification-daemon package

notification-daemon crashed with SIGSEGV

Bug #438787 reported by tenertener@yahoo.com on 2009-09-29

28

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	notification-daemon (Ubuntu)	Confirmed	Medium	Unassigned

Bug Description

Binary package hint: notification-daemon

I don't know what's happens

ProblemType: Crash
Architecture: i386
Date: Tue Sep 29 16:43:52 2009
Disassembly: 0xc3d050: Cannot access memory at address 0xc3d050
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/notification-daemon/notification-daemon
Package: notification-daemon 0.4.0-1ubuntu3 [modified: usr/share/dbus-1/services/org.freedesktop.Notifications.service]
ProcCmdline: /usr/lib/notification-daemon/notification-daemon
ProcEnviron:
LANG=es_ES.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SegvAnalysis:
Segfault happened at: 0xc3d050: Cannot access memory at address 0xc3d050
PC (0x00c3d050) not located in a known VMA region (needed executable region)!
SegvReason: executing unknown VMA
Signal: 11
SourcePackage: notification-daemon
StacktraceTop:
?? ()
?? () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgtk-x11-2.0.so.0
?? () from /usr/lib/libgtk-x11-2.0.so.0
?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: notification-daemon crashed with SIGSEGV
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

tenertener@yahoo.com (tenertener) wrote on 2009-09-29:

#1

Dependencies.txt Edit (3.8 KiB, text/plain; charset="utf-8")
ProcMaps.txt Edit (27.3 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (762 bytes, text/plain; charset="utf-8")
Registers.txt Edit (480 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1.4 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-30: Stacktrace.txt (retraced)

#2

Stacktrace.txt (retraced) Edit (2.1 KiB, text/plain)

StacktraceTop:?? ()
?? () from /usr/lib/libgobject-2.0.so.0
gtk_object_finalize (gobject=0x817e3d0)
gtk_widget_finalize (object=0x81a1840)
gtk_window_finalize (object=0x81a1840)

Revision history for this message

Apport retracing service (apport) wrote on 2009-09-30: ThreadStacktrace.txt (retraced)

#3

ThreadStacktrace.txt (retraced) Edit (2.1 KiB, text/plain)

Changed in notification-daemon (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-i386-retrace

Revision history for this message

Robert Roth (evfool) wrote on 2012-04-09:

#4

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 on 2012-04-09:

#5

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

Changed in notification-daemon (Ubuntu):
status:	New → Confirmed

Report a bug

This report contains Public information

Everyone can see this information.

Duplicates of this bug

Bug #468616

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

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