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

[Scott Moser]

this started happening today (after a reboot that admittedly probably skipped many intermediate versions from last "known working").

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity-services 7.3.1+14.10.20140915-0ubuntu2
ProcVersionSignature: Ubuntu 3.16.0-22.29-generic 3.16.4
Uname: Linux 3.16.0-22-generic x86_64
ApportVersion: 2.14.7-0ubuntu6
Architecture: amd64
CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,snap,commands,mousepoll,grid,move,place,imgpng,session,vpswitch,resize,regex,gnomecompat,unitymtgrabhandles,wall,resizeinfo,animation,workarounds,fade,scale,expo,ezoom,unityshell]
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue Oct 14 12:45:26 2014
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationDate: Installed on 2011-10-19 (1091 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 PATH=(custom, user)
 LANGUAGE=en_US
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7ffb4fdb01f5 <strrchr+37>: movdqu (%rdi),%xmm0
 PC (0x7ffb4fdb01f5) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 strrchr () at ../sysdeps/x86_64/strrchr.S:32
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: unity-panel-service crashed with SIGSEGV in strrchr()
UpgradeStatus: Upgraded to utopic on 2013-05-20 (512 days ago)
UserGroups: adm admin cdrom dialout fuse kvm libvirtd lpadmin plugdev sambashare sbuild

[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 #1332968, 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.