unity-panel-service crashed with SIGSEGV in ffi_call_unix64()

[Lukasz Grzesik]

Random letters because I don't know why.

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity-services 7.3.0+14.10.20140711-0ubuntu1
Uname: Linux 3.16.0-031600rc4-generic x86_64
.tmp.unity.support.test.0:

ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Sun Jul 20 13:54:54 2014
DistUpgraded: Fresh install
DistroCodename: utopic
DistroVariant: ubuntu
ExecutablePath: /usr/lib/unity/unity-panel-service
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430/5450/5470] [1002:68e0] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:3969]
InstallationDate: Installed on 2014-07-05 (15 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
MachineType: LENOVO 20071
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 PATH=(custom, no user)
 LANGUAGE=pl
 XDG_RUNTIME_DIR=<set>
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-031600rc4-generic root=UUID=3da1b177-6eec-425d-abe3-6f5add956745 ro acpi_osi=Linux pcie_aspm=force acpi_enforce_resources=lax acpi_backlight=vendor quiet splash
SegvAnalysis:
 Segfault happened at: 0x7f0eecfa10fc: mov (%rdi),%rbx
 PC (0x7f0eecfa10fc) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
 g_cclosure_marshal_generic () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: unity-panel-service crashed with SIGSEGV in ffi_call_unix64()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 06/08/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 36CN15WW(V2.01)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Guam
dmi.board.vendor: LENOVO
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnLENOVO:bvr36CN15WW(V2.01):bd06/08/2010:svnLENOVO:pn20071:pvrLenovoG565:rvnLENOVO:rnGuam:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.name: 20071
dmi.product.version: Lenovo G565
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.11+14.10.20140707-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.54-1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.2.3-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.2.3-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Sun Jul 20 12:58:17 2014
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: Output HDMI-0 LVDS VGA-0
xserver.version: 2:1.15.1-0ubuntu8
xserver.video_driver: radeon

[Apport retracing service (apport)]

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 #1300713, 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.