notify-osd crashed with signal 5 in _XReply()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
15.10 failed on bootup
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: notify-osd 0.9.35+
ProcVersionSign
Uname: Linux 4.2.0-16-generic x86_64
ApportVersion: 2.19.1-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Oct 18 08:20:16 2015
DesktopSession: 'ubuntu'
ExecutablePath: /usr/lib/
GtkTheme: 'Ambiance-Blue'
IconTheme: 'MBuntu-OS-Y'
InstallationDate: Installed on 2015-04-04 (196 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
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+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: Upgraded to wily on 2015-10-16 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 07/11/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: Z77 Extreme3
dmi.board.vendor: ASRock
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: To Be Filled By O.E.M.
dmi.product.
dmi.sys.vendor: To Be Filled By O.E.M.
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.