notify-osd crashed with signal 5 in _XReply()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
...
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: notify-osd 0.9.35+
ProcVersionSign
Uname: Linux 3.13.0-22-generic x86_64
ApportVersion: 2.14-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Apr 4 12:38:22 2014
DesktopSession: 'ubuntu'
ExecutablePath: /usr/lib/
GtkTheme: 'Ambiance'
IconTheme: 'ubuntu-mono-dark'
InstallationDate: Installed on 2014-03-04 (30 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.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=sv
PATH=(custom, no user)
LANG=sv_SE.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.7+1ubuntu8
libgl1-mesa-glx 10.1.0-4ubuntu1
libdrm2 2.4.52-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: Upgraded to trusty on 2014-03-04 (30 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 05/18/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0404
dmi.board.
dmi.board.name: Crosshair V Formula
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
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.
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.