notify-osd crashed with SIGSEGV in bubble_get_id()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
notify-osd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I'm not sure if this is a new crash, it seems like this is an old crash that apport keeps re-reporting to me. Cf. the other notify-osd bug report from me a few hours ago.
ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: notify-osd 0.9.35daily12.
ProcVersionSign
Uname: Linux 3.9.0-2-generic x86_64
ApportVersion: 2.10.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Mon May 20 00:59:18 2013
DesktopSession: 'ubuntu'
ExecutablePath: /usr/lib/
GtkTheme: 'Ambiance'
IconTheme: 'ubuntu-mono-dark'
InstallationDate: Installed on 2010-09-24 (969 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: LENOVO 3249CTO
MarkForUpload: True
ProcCmdline: /usr/lib/
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.7+1ubuntu4
libgl1-mesa-glx 9.1.1-0ubuntu3
libdrm2 2.4.45-1
xserver-
xserver-
SegvAnalysis:
Segfault happened at: 0x411ae6 <bubble_get_id+22>: cmp %rax,(%rdx)
PC (0x00411ae6) ok
source "%rax" ok
destination "(%rdx)" (0xaaaaaaaaaaaa
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: notify-osd
StacktraceTop:
bubble_get_id ()
stack_
dbus_glib_
?? () from /usr/lib/
?? () from /lib/x86_
Title: notify-osd crashed with SIGSEGV in bubble_get_id()
UpgradeStatus: Upgraded to saucy on 2013-05-06 (13 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare src sudo
dmi.bios.date: 08/23/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6QET52WW (1.22 )
dmi.board.name: 3249CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 3249CTO
dmi.product.
dmi.sys.vendor: LENOVO
tags: | removed: need-amd64-retrace |
tags: | added: need-amd64-retrace |
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 #1181324, 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.