notify-osd crashed with signal 5 in _XReply()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Not sure what caused this. No obvious problems now (i.e. can get volume notifications)
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: notify-osd 0.9.35+
ProcVersionSign
Uname: Linux 3.11.0-15-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
CheckboxSubmission: 346c69198d9a34d
CheckboxSystem: b633b4f40868d49
Date: Wed Feb 12 00:20:10 2014
DesktopSession: 'ubuntu'
ExecutablePath: /usr/lib/
GtkTheme: 'Ambiance'
IconTheme: 'ubuntu-mono-dark'
InstallationDate: Installed on 2012-07-14 (577 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425)
MachineType: Sony Corporation SVE14A1C5E
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=en_GB.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.7+1ubuntu6
libgl1-mesa-glx 9.2.1-1ubuntu3
libdrm2 2.4.46-1ubuntu1
xserver-
xserver-
Signal: 5
SourcePackage: notify-osd
StacktraceTop:
?? () from /usr/lib/
_XReply () from /usr/lib/
XGetGeometry () from /usr/lib/
?? () from /usr/lib/
gdk_window_
Title: notify-osd crashed with signal 5 in _XReply()
UpgradeStatus: Upgraded to saucy on 2013-09-24 (140 days ago)
UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo
dmi.bios.date: 04/20/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: R0270V4
dmi.board.
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: SVE14A1C5E
dmi.product.
dmi.sys.vendor: Sony Corporation
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1275524, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.