Ubuntu
notification-daemon package

[apport] notification-daemon crashed with SIGSEGV in g_hash_table_lookup()

Bug #104953 reported by Aurel Branzeanu on 2007-04-09

20

Affects		Status	Importance	Assigned to	Milestone
	notification-daemon (Ubuntu)	Fix Released	Medium	Brian Murray

Bug Description

Binary package hint: notification-daemon

First crashed Update Manager with the "http crash" error, then, attempting to send the crash-report, Firefox was't answering, then everything was freezed, reboot, and this crash-report after the reboot

ProblemType: Crash
Architecture: i386
Date: Mon Apr 9 23:50:11 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/lib/notification-daemon/notification-daemon
Package: notification-daemon 0.3.6-0ubuntu3
PackageArchitecture: i386
ProcCmdline: /usr/lib/notification-daemon/notification-daemon
ProcCwd: /
ProcEnviron:
LANGUAGE=en_US:en
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: notification-daemon
StacktraceTop:
g_hash_table_lookup () from /usr/lib/libglib-2.0.so.0
?? () from /usr/lib/libwnck-1.so.18
?? ()
?? () from /usr/lib/libwnck-1.so.18
?? ()
Uname: Linux thunder-mobile 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message

Aurel Branzeanu (thunder-riscom) wrote on 2007-04-09:

#1

Dependencies.txt Edit (2.7 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (903 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (16.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (671 bytes, text/plain; charset="utf-8")
Registers.txt Edit (530 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (608 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (635 bytes, text/plain; charset="utf-8")

Sebastien Bacher (seb128) on 2007-04-09

Changed in notification-daemon:
importance:	Undecided → Medium

Revision history for this message

Apport retracing service (apport) wrote on 2007-04-09: Symbolic stack trace

#2

Stacktrace.txt (retraced) Edit (734 bytes, text/plain)

StacktraceTop:_wnck_atom_get (atom_name=0xb7ef3cfa "_NET_ACTIVE_WINDOW") at xutils.c:664
_wnck_screen_process_property_notify (screen=0x8192da0, xevent=0xbfdb0ee8) at screen.c:809
filter_func (gdkxevent=0xbfdb0ee8, event=0x8080458, data=0x0) at xutils.c:712
?? () from /usr/lib/libgdk-x11-2.0.so.0

Revision history for this message

Apport retracing service (apport) wrote on 2007-04-09: Symbolic threaded stack trace

#3

ThreadStacktrace.txt (retraced) Edit (761 bytes, text/plain)

Revision history for this message

Sebastien Bacher (seb128) wrote on 2007-04-12:

#4

Thanks for your bug report. Could you try to get a valgrind log for the crash (you can follow the instructions from https://wiki.ubuntu.com/Valgrind for that)?

Changed in notification-daemon:
status:	Unconfirmed → Needs Info

Revision history for this message

Aurel Branzeanu (thunder-riscom) wrote on 2007-04-13:

#5

There were several random crashes. But now with fresh Release Candidate the problems with aport and synaptic are seeming to be gone...

Revision history for this message

Brian Murray (brian-murray) wrote on 2007-04-18:

#6

This bug report is being closed due to your last comment regarding this being fixed with an update. Thanks again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Changed in notification-daemon:
assignee:	nobody → brian-murray
status:	Needs Info → Fix Released

Report a bug

This report contains Public information

Everyone can see this information.

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.