notify-osd crashed with SIGSEGV in malloc_consolidate()

Bug #449779 reported by Juan Sebastián Marulanda
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Python
Invalid
Undecided
Unassigned
gnome-python-extras (Ubuntu)
Invalid
Low
Unassigned
notify-osd (Ubuntu)
Invalid
High
Unassigned

Bug Description

Binary package hint: notify-osd

Getting this error constantly.

ProblemType: Crash
Architecture: i386
CheckboxSubmission: b921af5b1a4fc862d51d74bcbde28d88
CheckboxSystem: daed2f3d6643b4a84b4520a2427f8c2b
CrashCounter: 1
Date: Mon Oct 12 14:08:36 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/notify-osd/notify-osd
GtkTheme: Human
IconTheme: Humanity-Dark
Package: notify-osd 0.9.23-0ubuntu1
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-13-generic-pae root=UUID=93469d8a-de2b-4ba1-aa65-806e3e03f86b ro quiet splash
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.44-generic-pae
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.6.0-1ubuntu2
 libdrm2 2.4.14-1ubuntu1
 xserver-xorg-video-intel 2:2.9.0-1ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20090825.fc74e119-0ubuntu3
SegvAnalysis:
 Segfault happened at: 0xb6e3410f <malloc_consolidate+239>: mov 0x4(%edi),%edx
 PC (0xb6e3410f) ok
 source "0x4(%edi)" (0xbfbef0bc) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
 malloc_consolidate (av=<value optimized out>) at malloc.c:5089
 _int_malloc (av=<value optimized out>,
 _int_realloc (av=<value optimized out>, oldp=0x84ba130,
 *__GI___libc_realloc (oldmem=0x84ba138, bytes=16384)
 g_realloc () from /lib/libglib-2.0.so.0
Title: notify-osd crashed with SIGSEGV in malloc_consolidate()
Uname: Linux 2.6.31-13-generic-pae i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
WindowManager: compiz
dmi.bios.date: 07/31/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: ECG3510M.86A.0117.2009.0731.1421
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DG35EC
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE29266-205
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrECG3510M.86A.0117.2009.0731.1421:bd07/31/2009:svn:pn:pvr:rvnIntelCorporation:rnDG35EC:rvrAAE29266-205:cvn:ct3:cvr:

Revision history for this message
Juan Sebastián Marulanda (juanchito2006) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:malloc_consolidate (av=<value optimized out>) at malloc.c:5089
_int_malloc (av=<value optimized out>,
_int_realloc (av=<value optimized out>, oldp=0x84ba130,
*__GI___libc_realloc (oldmem=0x84ba138, bytes=16384)
g_realloc () from /lib/libglib-2.0.so.0

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
Mirco Müller (macslow)
Changed in notify-osd (Ubuntu):
assignee: nobody → Mirco Müller (macslow)
importance: Medium → High
milestone: none → ubuntu-9.10
Mirco Müller (macslow)
Changed in notify-osd (Ubuntu):
status: New → Incomplete
Revision history for this message
Mirco Müller (macslow) wrote :

Juan, can you please update to current notify-osd 0.9.24 and see if that crasher remains?

Revision history for this message
Mirco Müller (macslow) wrote :

Juan, can you also attach the file ~/.cache/notify-osd.log _after_ the crash occured so we'll be able to see what exactly did get send to notify-osd. Also please provide the exact thing you did causing the crash, if you can do so. Or log onto the IRC-server irc.freedesktop.org, channel #ubuntu-devel and ping me (MacSlow), so we can try to force this crasher together.

Revision history for this message
Mirco Müller (macslow) wrote :

From a conversation I had with Juan on IRC and via emesene (not crashing my notify-osd :) one should start looking at the libnotify-plugin of it. It's part of emesene upstream. Right now there's no deterministic way to force the crash to occur.

David Barth (dbarth)
Changed in notify-osd:
assignee: nobody → Mirco Müller (macslow)
importance: Undecided → High
status: New → Incomplete
Revision history for this message
Mirco Müller (macslow) wrote :

The plugin as emesene itself are written in Python. The plugins code is in emesene-1.5/plugins_base/NotifyOsdImproved.py so if anybody wants to join the bug-hunt... be my guest.

David Barth (dbarth)
Changed in notify-osd:
milestone: none → ubuntu-9.10
Mirco Müller (macslow)
Changed in notify-osd (Ubuntu):
status: Incomplete → Triaged
David Barth (dbarth)
Changed in notify-osd:
status: Incomplete → Triaged
Changed in gnome-python-extras (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
Changed in python:
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
Revision history for this message
Sebastien Bacher (seb128) wrote :

GerryC, could you stop opening random and wrong tasks on launchpad?

Changed in gnome-python-extras (Ubuntu):
importance: Undecided → Low
status: New → Invalid
Revision history for this message
Mitch Towner (kermiac) wrote :

unsubscribed Ubuntu Desktop Bugs & invalidated python task.

Changed in python:
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
status: New → Invalid
Mitch Towner (kermiac)
Changed in gnome-python-extras (Ubuntu):
assignee: Ubuntu Desktop Bugs (desktop-bugs) → nobody
Revision history for this message
Sebastien Bacher (seb128) wrote :

is somebody still getting the issue with current versions?

Changed in notify-osd (Ubuntu):
milestone: ubuntu-9.10 → none
Revision history for this message
Sebastien Bacher (seb128) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in notify-osd:
status: Triaged → Invalid
Changed in notify-osd (Ubuntu):
assignee: Mirco Müller (macslow) → nobody
status: Triaged → Invalid
no longer affects: notify-osd
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.