notify-osd crashed with signal 5 in _XReply()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I hit ALT+F2 to restart Unity 7.4.0 on Ubuntu 16.04 beta 2, and this error appeared.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: notify-osd 0.9.35+
ProcVersionSign
Uname: Linux 4.4.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Apr 5 09:47:23 2016
DesktopSession: 'ubuntu'
ExecutablePath: /usr/lib/
GtkTheme: 'Ambiance'
IconTheme: 'ubuntu-mono-dark'
InstallationDate: Installed on 2016-03-27 (8 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
MachineType: Micro-Star International Co., Ltd. GT80 2QD
ProcCmdline: /usr/lib/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=en_US
PATH=(custom, no user)
LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.7+13ubuntu3
libgl1-mesa-glx 11.1.2-1ubuntu2
libdrm2 2.4.67-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: 10/14/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E1812IMS.119
dmi.board.
dmi.board.name: MS-1812
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:0.C
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: GT80 2QD
dmi.product.
dmi.sys.vendor: Micro-Star International Co., Ltd.
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.