notify-osd crashed with signal 5 in _XReply()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
in steam play
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: notify-osd 0.9.35+
ProcVersionSign
Uname: Linux 3.16.0-18-generic x86_64
ApportVersion: 2.14.7-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Oct 2 11:08:56 2014
DesktopSession: 'ubuntu'
ExecutablePath: /usr/lib/
GtkTheme: 'Ambiance'
IconTheme: 'Faenza-Ambiance'
InstallationDate: Installed on 2014-09-29 (2 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
MachineType: LENOVO 20B7000CGE
ProcCmdline: /usr/lib/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=de_DE
PATH=(custom, no user)
LANG=de_DE.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.7+7ubuntu2
libgl1-mesa-glx 10.3.0-0ubuntu2
libdrm2 2.4.56-1
xserver-
xserver-
Signal: 5
SourcePackage: notify-osd
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
_XReply () from /usr/lib/
XSync () from /usr/lib/
?? () from /usr/lib/
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/02/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: GJET61WW (2.11 )
dmi.board.
dmi.board.name: 20B7000CGE
dmi.board.vendor: LENOVO
dmi.board.version: 0B98401 PRO
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 20B7000CGE
dmi.product.
dmi.sys.vendor: LENOVO
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 #1206754, 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.