Mutiny layout interface in 16.10

Bug #1608705 reported by APolihron
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Ubuntu MATE
Fix Released
High
Unassigned

Bug Description

I get this error wille swiching to Mutiny layout interface in 16.10
and i will get another error with it Bug #1608706

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: mate-panel 1.14.1-1
ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
Uname: Linux 4.4.0-33-generic x86_64
ApportVersion: 2.20.3-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Aug 2 00:51:54 2016
ExecutablePath: /usr/bin/mate-panel
InstallationDate: Installed on 2016-08-01 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.10 "Yakkety Yak" - Alpha amd64 (20160731)
ProcCmdline: mate-panel
SegvAnalysis:
 Segfault happened at: 0x7f2bd4a62760 <gdk_window_get_user_data>: mov 0x30(%rdi),%rax
 PC (0x7f2bd4a62760) 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

Revision history for this message
APolihron (apolitech) wrote :
information type: Private → Public
description: updated
affects: mate-panel (Ubuntu) → ubuntu-mate
APolihron (apolitech)
summary: - mate-panel crashed with SIGSEGV in gdk_window_get_user_data()
+ Mutiny layout interface in 16.10
Changed in ubuntu-mate:
status: New → Triaged
importance: Undecided → High
assignee: nobody → Martin Wimpress (flexiondotorg)
Revision history for this message
Martin Wimpress  (flexiondotorg) wrote :

This is fixed in Ubuntu MATE 16.10 Beta 1.

Changed in ubuntu-mate:
status: Triaged → Fix Released
Changed in ubuntu-mate:
assignee: Martin Wimpress (flexiondotorg) → nobody
Revision history for this message
Joseph Gan (awakened1712) wrote :

I still have the crash in the final release. Is it the same thing?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.