notify-osd crashed with signal 5 in _XReply()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
This just occurred while Xscreensaver was running and I was away.
ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: notify-osd 0.9.35+
ProcVersionSign
Uname: Linux 3.13.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.13.2-0ubuntu5
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Mar 7 14:01:35 2014
DesktopSession: 'ubuntu'
ExecutablePath: /usr/lib/
GtkTheme: 'Ambiance'
IconTheme: 'buuf3.10'
InstallationDate: Installed on 2014-01-08 (57 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140108)
MachineType: MICRO-STAR INTERNATIONAL CO.,LTD MS-7529
ProcCmdline: /usr/lib/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
LANGUAGE=en_US
PATH=(custom, user)
LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/sda5 ro quiet splash
RelatedPackageV
xserver-xorg 1:7.7+1ubuntu8
libgl1-mesa-glx 10.1.0~rc3-0ubuntu3
libdrm2 2.4.52-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: 03/11/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.8
dmi.board.
dmi.board.name: G31M3-L V2(MS-7529)
dmi.board.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: MS-7529
dmi.product.
dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO.,LTD
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.