mate-tweak crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()

Bug #1756801 reported by thedano
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mate-tweak (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

Changing layouts between Pantheon and Traditional, mate-tweak closed itself.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: mate-tweak 18.04.14-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Sun Mar 18 22:56:45 2018
ExecutablePath: /usr/bin/mate-tweak
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: mate-tweak
ProcEnviron:

Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
SegvAnalysis:
 Segfault happened at: 0x7fe750c20c31 <g_type_check_instance_is_fundamentally_a+49>: movzbl 0x14(%rdx),%eax
 PC (0x7fe750c20c31) ok
 source "0x14(%rdx)" (0x100000014) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: mate-tweak
StacktraceTop:
 g_type_check_instance_is_fundamentally_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_ref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_weak_ref_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: mate-tweak crashed with SIGSEGV in g_type_check_instance_is_fundamentally_a()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
thedano (revjasper) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x28c12b0, fundamental_type=fundamental_type@entry=80) at ../../../../gobject/gtype.c:4026
 g_object_ref (_object=0x28c12b0) at ../../../../gobject/gobject.c:3204
 g_weak_ref_get (weak_ref=<optimized out>) at ../../../../gobject/gobject.c:4379
 g_settings_backend_invoke_closure (user_data=0x7fe74001ae00) at ../../../../gio/gsettingsbackend.c:263
 g_main_dispatch (context=0x2512c60) at ../../../../glib/gmain.c:3177

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in mate-tweak (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Martin Wimpress  (flexiondotorg) wrote :

This was fixed in mate-tweak (18.04.6-1)

information type: Private → Public
Revision history for this message
Martin Wimpress  (flexiondotorg) wrote :

Oh, I see this was encountered using 18.04.14.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mate-tweak (Ubuntu):
status: New → Confirmed
no longer affects: glib2.0 (Ubuntu)
Revision history for this message
Martin Wimpress  (flexiondotorg) wrote :

Ubuntu MATE 18.04 and MATE Tweak 18.04 are both EOL and no longer supported.

Changed in mate-tweak (Ubuntu):
status: Confirmed → Won't Fix
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.