mate-panel crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1569673 reported by Josh Ozooda
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mate-panel (Ubuntu)
New
Undecided
Unassigned

Bug Description

krunner. I purged libkf5runner5, mate-desktop. reinstalled mate desktop. could not login via login page. Login page stalled. Cntl,alt,f1- starx for desktop.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: mate-panel 1.12.2-1
Uname: Linux 4.6.0-040600rc2-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: MATE
Date: Wed Apr 13 13:49:08 2016
ExecutablePath: /usr/bin/mate-panel
InstallationDate: Installed on 2016-04-12 (1 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323.1)
ProcCmdline: mate-panel
SegvAnalysis:
 Segfault happened at: 0x7f21dc42d7e5 <g_type_check_instance_is_fundamentally_a+5>: mov (%rdi),%rax
 PC (0x7f21dc42d7e5) ok
 source "(%rdi)" (0x00000006) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mate-panel
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? ()
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? ()
Title: mate-panel crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Josh Ozooda (a-josh-o) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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

information type: Private → Public
tags: removed: need-amd64-retrace
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.