MASTER notify-osd crashed with signal 5 in _XError()

Bug #331365 reported by vnieto
204
This bug affects 16 people
Affects Status Importance Assigned to Milestone
notify-osd (Ubuntu)
Fix Released
High
David Barth

Bug Description

Binary package hint: notify-osd

Before update

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/notify-osd/notify-osd
NonfreeKernelModules: nvidia
Package: notify-osd 0.8-0ubuntu3
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
 PATH=(custom, user)
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: notify-osd
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XEventsQueued () from /usr/lib/libX11.so.6
 XPending () from /usr/lib/libX11.so.6
Title: notify-osd crashed with signal 5 in _XError()
Uname: Linux 2.6.28-8-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
vnieto (vnieto) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:gdk_x_error (display=<value optimized out>,
_XError (dpy=0x235c8f0, rep=0x27e5710)
process_responses (dpy=0x235c8f0,
_XEventsQueued (dpy=0x235c8f0,
XPending (dpy=0x235c8f0) at ../../src/Pending.c:56

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in notify-osd:
importance: Undecided → Medium
Revision history for this message
Martin Pitt (pitti) wrote : Re: notify-osd crashed with signal 5 in _XError()

Just got the same crash.

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

Same for me, I can easily reproduce disabling the compositor in metacity.

Revision history for this message
Alexander Sack (asac) wrote :

bumping to high as this has already attracted 5 dupes.

Changed in notify-osd:
importance: Medium → High
Revision history for this message
Alexander Sack (asac) wrote :

The error seems to be:
  buf = "BadAlloc (insufficient resources for operation)", '\0' <repeats 16 times>

The request code seems to be 53:
  xerror = {type = 0, display = 0x235c8f0, resourceid = 61, serial = 1119,
      error_code = 11 '\v', request_code = 53 '5', minor_code = 0 '\0'},

which is
/usr/include/X11/Xproto.h:#define X_CreatePixmap 53

Maybe non-freed server side pixmaps?

Changed in notify-osd:
status: Confirmed → Triaged
Revision history for this message
David Barth (dbarth) wrote :

I've tried to reproduce this by playing with metacity's compositing flag, but I cannot make it crash as of notify-osd-0.8-0ubuntu3.

Can you provide a test case?

Changed in notify-osd:
importance: Undecided → Medium
status: New → Incomplete
David Barth (dbarth)
Changed in notify-osd:
assignee: nobody → dbarth
Revision history for this message
ScottyJavea (scotty-kmts) wrote : Re: [Bug 331365] Re: MASTER notify-osd crashed with signal 5 in _XError()

David,

The problem was with an upgrade from 8.1 to 9.04.

I have installed 9.04 from an iso and so far, so good.

Regards,
Keith Scott

----- Original Message -----
From: "David Barth" <email address hidden>
To: <email address hidden>
Sent: Wednesday, February 25, 2009 4:32 PM
Subject: [Bug 331365] Re: MASTER notify-osd crashed with signal 5 in
_XError()

** Changed in: notify-osd
     Assignee: (unassigned) => David Barth (dbarth)

--
MASTER notify-osd crashed with signal 5 in _XError()
https://bugs.launchpad.net/bugs/331365
You received this bug notification because you are a direct subscriber
of the bug.

Status in Canonical's Notification Display Agent: Incomplete
Status in “notify-osd” source package in Ubuntu: Triaged

Bug description:
Binary package hint: notify-osd

Before update

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/notify-osd/notify-osd
NonfreeKernelModules: nvidia
Package: notify-osd 0.8-0ubuntu3
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
 PATH=(custom, user)
 LANG=es_CO.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: notify-osd
StacktraceTop:
 ?? () from /usr/lib/libgdk-x11-2.0.so.0
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XEventsQueued () from /usr/lib/libX11.so.6
 XPending () from /usr/lib/libX11.so.6
Title: notify-osd crashed with signal 5 in _XError()
Uname: Linux 2.6.28-8-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
pitwalker (pitwalker) wrote :

I use 2.6.28-8 generic kernel
I have also this crash under XFCE. Afer a login. After a kernel oops.
I have a Dell Inspiron 1520 and after a upgrade the sound not works.

lspci -v
00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)
 Subsystem: Dell Device 01f1
 Flags: bus master, fast devsel, latency 0, IRQ 21
 Memory at fe9fc000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: <access denied>
 Kernel driver in use: HDA Intel
 Kernel modules: snd-hda-intel

aplay -l
aplay: device_list:217: no soundcards found...

lsmod |grep snd
snd_hda_intel 424884 0
snd_pcm_oss 46336 0
snd_mixer_oss 22656 1 snd_pcm_oss
snd_pcm 82820 2 snd_hda_intel,snd_pcm_oss
snd_seq_dummy 10756 0
snd_seq_oss 37760 0
snd_seq_midi 14336 0
snd_rawmidi 29696 1 snd_seq_midi
snd_seq_midi_event 15104 2 snd_seq_oss,snd_seq_midi
snd_seq 56880 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer 29704 2 snd_pcm,snd_seq
snd_seq_device 14988 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd 62628 9 snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore 15200 1 snd
snd_page_alloc 16904 2 snd_hda_intel,snd_pcm

Revision history for this message
Martin Olsson (mnemo) wrote :

Ah that reminds me. I also had xorg segv just before and it's very likely that I too had a kernel oops crash notification about to be displayed (I got kerneloops package installed btw but that's not related I guess?).

Revision history for this message
pitwalker (pitwalker) wrote :

I change the appearance from normal to none. That cause the error. (also on 2009-02-25)
When I make the cange I use the CRUX theme.
My 2nd panel is aligned to the left side.

Revision history for this message
pitwalker (pitwalker) wrote :

notify-osd 0.8-0ubuntu4 steps to reproduce error:

login to gnome as normal user
set the panelt to the left and the right side (order is not important, I use 32pixel wide panels)
open 3 windows for example: firefox, gnome terminal, openoffice.org writer
open appearance
change effects to normal
change themes
change effects to none
wait half minute

(i install xfce but packages every dependency are ok
every package is ut to date)

Revision history for this message
Nikolay Botev (nikolaybotevb) wrote :

same crash, 904 upgrade from 810, 64-bit ubuntu, happens on start of fusion-icon, using custom built-from-source opensolaris nimbus theme

Revision history for this message
electhor (electhor) wrote :

Seems like I have had the same crash too! Hope the 1.1mb of things copied re the crash download OK.

Revision history for this message
firebird76 (firebird76) wrote :

Same crash after update 8.10 to 9.04 64 bit.

Revision history for this message
Sebastien Bacher (seb128) wrote :

that is fixed in jaunty now

Changed in notify-osd (Ubuntu):
status: Triaged → Fix Released
Changed in notify-osd:
status: Incomplete → Fix Released
Revision history for this message
Daniel Santibáñez Polanco (dansanti) wrote :

hello!

this also happend before upgrade from jaunty to karmic alpha2.

Revision history for this message
Anthony Hook (anthonyhook) wrote :

I had a problem with this running the latest version of Karmic Alpha2

Revision history for this message
UGN (eugene-korneev) wrote :

i have same bug 5 min ago!!! (system updated [karmic])

Changed in notify-osd (Ubuntu):
assignee: nobody → David Barth (dbarth)
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.