notify-osd crashed with SIGSEGV in XInternAtom()

Bug #363087 reported by Amit Kucheria
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
notify-osd (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: notify-osd

I just finished dist-upgrading Jaunty today and rebooted when apport popped-up with this crash.

Not sure what causes it though my tomboy applet did crash in the beginning with a message "The panel encountered a problem while loading "OAFIID:TomboyApplet". Do you want to delete the applet from your configuration?"

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/notify-osd/notify-osd
Package: notify-osd 0.9.11-0ubuntu2
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
 XInternAtom () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
 ?? () from /usr/lib/gtk-2.0/modules/libatk-bridge.so
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: notify-osd crashed with SIGSEGV in XInternAtom()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Amit Kucheria (amitk) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:XInternAtom (dpy=0x0, name=0xb726219e "AT_SPI_IOR", onlyIfExists=0)
spi_atk_bridge_get_registry () at bridge.c:391
spi_atk_bridge_do_registration () at bridge.c:276
atk_bridge_init (argc=0xb802f418, argv=0xb802f41c)
default_display_notify_cb (display_manager=0x8964160)

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in notify-osd (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Ara Pulido (ara)
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Hello Amit, is this still an issue with notify-osd 0.9.16 from Karmic?

Changed in notify-osd (Ubuntu):
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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!.

Changed in notify-osd (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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