notify-osd crashed with signal 5 in _XReply()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
system idle when crashed
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: notify-osd 0.9.35+
ProcVersionSign
Uname: Linux 4.2.0-41-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Sat Jul 9 13:27:32 2016
DesktopSession: 'ubuntu'
ExecutablePath: /usr/lib/
GtkTheme: 'HighContrast'
IconTheme: 'Adwaita'
InstallationDate: Installed on 2014-04-08 (822 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Gateway DX4860
ProcCmdline: /usr/lib/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=en_CA:en
PATH=(custom, no user)
LANG=en_CA.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.7+7ubuntu4
libgl1-mesa-glx 11.0.2-1ubuntu4
libdrm2 2.4.64-1
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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 08/01/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P02-A1
dmi.board.name: IPISB-VR
dmi.board.vendor: Gateway
dmi.board.version: 1.01
dmi.chassis.type: 3
dmi.chassis.vendor: Gateway
dmi.modalias: dmi:bvnAmerican
dmi.product.name: DX4860
dmi.sys.vendor: Gateway
glxinfo: Error: [Errno 2] No such file or directory: 'glxinfo'
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.