notify-osd crashed with signal 5 in _XReply()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I opened Kerbal Space Program when this crash occurred. The program is running fine. This error also occurs if I try to change the framerate limit setting.
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: notify-osd 0.9.35daily12.
ProcVersionSign
Uname: Linux 3.8.0-30-generic x86_64
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 7 19:49:52 2013
DesktopSession: 'ubuntu'
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/
GtkTheme: 'Ambiance'
IconTheme: 'ubuntu-mono-dark'
InstallationDate: Installed on 2012-10-19 (323 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: Hewlett-Packard HP ProBook 4430s
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.7+1ubuntu4
libgl1-mesa-glx 9.2.0~git201307
libdrm2 2.4.46+
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 raring on 2013-04-27 (133 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sbuild sudo vboxusers video wireshark
dmi.bios.date: 09/18/2012
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SRR Ver. F.29
dmi.board.name: 167E
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 22.24
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP ProBook 4430s
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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.