notify-osd crashed by choqok, initially thought to crash randomly

Bug #409663 reported by Craig Cabrey
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Notify OSD
New
Undecided
Unassigned
choqok (Ubuntu)
New
Undecided
Unassigned
notify-osd (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: notify-osd

I was just installing an application (via aptitude) when notify-osd crashed. Nothing was attemping to use it at the time. I don't know how I could reproduce this.

ProblemType: Crash
Architecture: i386
Date: Wed Aug 5 23:11:18 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/notify-osd/notify-osd
GtkTheme: Shiki-Brave
IconTheme: gnome-brave
MachineType: ASUSTeK Computer INC. 900HA
Package: notify-osd 0.9.16-0ubuntu1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-5-generic root=UUID=7d1b08a5-1692-45fc-abab-55bbbc7e00f7 ro quiet splash
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.5-1ubuntu1
 libdrm2 2.4.12-1ubuntu1
 xserver-xorg-video-intel 2:2.8.0-0ubuntu2
 xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu5
SegvAnalysis:
 Segfault happened at: 0xdbfa62 <g_type_check_instance_cast+50>: mov (%edx),%edi
 PC (0x00dbfa62) ok
 source "(%edx)" (0x000001d8) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
 g_type_check_instance_cast ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_container_forall () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: notify-osd crashed with SIGSEGV in g_type_check_instance_cast()
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WindowManager: gnome-wm
dmi.bios.date: 12/18/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0502
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 900HA
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x00000000
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTek Computer INC.
dmi.chassis.version: x.x
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0502:bd12/18/2008:svnASUSTeKComputerINC.:pn900HA:pvrx.x:rvnASUSTeKComputerINC.:rn900HA:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x:
dmi.product.name: 900HA
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.

Revision history for this message
Craig Cabrey (cabrey) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:IA__g_type_check_instance_cast (type_instance=0x8bfff00,
widget_add_child_draw_rectangle (widget=0x8bfff00,
gtk_box_forall (container=0x897ecc8, include_internals=1,
IA__gtk_container_forall (container=0x897ecc8,
gtk_widget_get_draw_rectangle (widget=0x897ecc8,

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
visibility: private → public
Revision history for this message
Craig Cabrey (cabrey) wrote : Re: notify-osd crashed randomly

I don't see a way to edit my original report, so I'll add this as a comment.

I think notify-osd crashes when Choqok (a microblogging app for KDE/Qt) tries to send a notification. It just happened again to me and I recall Choqok running when it happened the first time (and when I submitted this report).

Revision history for this message
Peter Antoniac (pan1nx) wrote :

I added the Choqok source package to the report.

summary: - notify-osd crashed randomly
+ notify-osd crashed by choqok, initially thought to crash randomly
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.