notify-osd crashed with signal 5 in _XReply()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I got this crash when I clicked to unplug an ebook whose drive was connected through USB.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: notify-osd 0.9.35+
ProcVersionSign
Uname: Linux 3.19.0-7-generic x86_64
NonfreeKernelMo
ApportVersion: 2.16.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Mar 8 17:29:16 2015
DesktopSession: 'ubuntu'
ExecutablePath: /usr/lib/
GtkTheme: 'Ambiance'
IconTheme: 'ubuntu-mono-dark'
InstallationDate: Installed on 2013-11-28 (464 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. Latitude E6530
ProcCmdline: /usr/lib/
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.7+7ubuntu2
libgl1-mesa-glx 10.5.0~rc3-0ubuntu1
libdrm2 2.4.59-0ubuntu1
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 vivid on 2015-03-05 (3 days ago)
UserGroups: adm cdrom dip kismet lp lpadmin plugdev sambashare saned scanner sudo vboxusers video
dmi.bios.date: 08/27/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 07Y85M
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude E6530
dmi.product.
dmi.sys.vendor: Dell Inc.
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.