notify-osd crashed with signal 5 in _gdk_region_get_xrectangles()

Bug #398910 reported by sdrc92126
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
notify-osd (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: notify-osd

Soon after boot and login, I opened the nvidia tool. I,m not sure where the error occured

ProblemType: Crash
Architecture: i386
Date: Mon Jul 13 10:12:21 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/notify-osd/notify-osd
GtkTheme: Human
IconTheme: Human
Lsusb:
 Bus 002 Device 003: ID 046d:c00e Logitech, Inc. M-BJ58/M-BJ69 Optical Wheel Mouse
 Bus 002 Device 002: ID 046d:c503 Logitech, Inc. Cordless Mouse+Keyboard Receiver
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: System manufacturer System Product Name
NonfreeKernelModules: nvidia
Package: notify-osd 0.9.14.1-0ubuntu1
ProcCmdLine: root=UUID=65d5becc-e269-432c-9270-889bbd874544 ro quiet splash
ProcCmdline: /usr/lib/notify-osd/notify-osd
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-2.17-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4+3ubuntu5
 libgl1-mesa-glx 7.5~rc4-1ubuntu3
 libdrm2 2.4.11-1ubuntu1
 xserver-xorg-video-intel 2:2.7.99.901+git20090702.74227141-0ubuntu1
 xserver-xorg-video-ati 1:6.12.99+git20090629.f39cafc5-0ubuntu1
Signal: 5
SourcePackage: notify-osd
StacktraceTop:
 _gdk_region_get_xrectangles (region=0x998c5a8,
 _XError () from /usr/lib/libX11.so.6
 ?? () from /usr/lib/libX11.so.6
 _XReply () from /usr/lib/libX11.so.6
 XShapeGetRectangles () from /usr/lib/libXext.so.6
Title: notify-osd crashed with signal 5 in _gdk_region_get_xrectangles()
Uname: Linux 2.6.31-2-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video
WindowManager: gnome-wm
dmi.bios.date: 06/20/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: ASUS M2N-SLI DELUXE ACPI BIOS Revision 1102
dmi.board.name: M2N-SLI DELUXE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.XX
dmi.chassis.asset.tag: 123456789000
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvrASUSM2N-SLIDELUXEACPIBIOSRevision1102:bd06/20/2007:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-SLIDELUXE:rvr1.XX:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

StacktraceTop:?? ()

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

do you still get this with notify-osd 0.9.16 ? May you also tell us a few easy steps in order to reproduce the crash? Thanks.

Changed in notify-osd (Ubuntu):
status: New → Incomplete
Revision history for this message
sdrc92126 (sdrc92126) wrote : Re: [Bug 398910] Re: notify-osd crashed with signal 5 in _gdk_region_get_xrectangles()

I'm sorry. I'm sure that this was the only time that I saw the crash, but it
has been too long and I don't remember any details.

On Thu, Aug 13, 2009 at 5:57 AM, Pedro Villavicencio <email address hidden> w't
remember any detailsrote:

> do you still get this with notify-osd 0.9.16 ? May you also tell us a
> few easy steps in order to reproduce the crash? Thanks.
>
> ** Changed in: notify-osd (Ubuntu)
> Status: New => Incomplete
>
> --
> notify-osd crashed with signal 5 in _gdk_region_get_xrectangles()
> https://bugs.launchpad.net/bugs/398910
> You received this bug notification because you are a direct subscriber
> of the bug.
>

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