Mate-panel crashed when changing theme from Ambiant-MATE to BlackMATE.
Redmond menu appears normally(except Shutdown button is missing) but when you place mouse pointer over menu the Shutdown button appears and the Accessories category disappears(menu scrolls up) until you place mouse over Education category and then the menu scrolls down so Accessories appears and Shutdown disappears again.
I have not rebooted since changing theme so I'm unsure that this issue would be fixed by rebooting.
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: mate-panel 1.15.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
CurrentDesktop: MATE
Date: Wed Sep 14 21:50:20 2016
ExecutablePath: /usr/bin/mate-panel
InstallationDate: Installed on 2016-09-14 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160913)
ProcCmdline: mate-panel
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, user)
XDG_RUNTIME_DIR=<set>
LANG=en_GB.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7f78193ae2f0 <gdk_window_get_user_data>: mov 0x30(%rdi),%rax
PC (0x7f78193ae2f0) ok
source "0x30(%rdi)" (0x00000030) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mate-panel
StacktraceTop:
gdk_window_get_user_data () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
?? ()
?? ()
?? ()
?? ()
Title: mate-panel crashed with SIGSEGV in gdk_window_get_user_data()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1597080, 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.