mate-tweak crashed with SIGSEGV in settings_backend_path_changed()

Bug #1757576 reported by Pepe Lebuntu
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
mate-tweak (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I'm just trying out mate 18.04 beta.

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: mate-tweak 18.04.12-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.389
Date: Thu Mar 22 00:24:49 2018
ExecutablePath: /usr/bin/mate-tweak
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180307.1)
PackageArchitecture: all
ProcCmdline: mate-tweak
ProcEnviron:

Python3Details: /usr/bin/python3.6, Python 3.6.4+, 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: 0x7f65e1a02aff: mov 0x18(%rax),%rdi
 PC (0x7f65e1a02aff) ok
 source "0x18(%rax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: mate-tweak
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-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
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: mate-tweak crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Pepe Lebuntu (majagray75) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 settings_backend_path_changed (target=0x1aff610, backend=<optimized out>, path=0x7f65d0015090 "/", origin_tag=0x0) at ../../../../gio/gsettings.c:460
 g_settings_backend_invoke_closure (user_data=0x1ad9100) at ../../../../gio/gsettingsbackend.c:267
 g_main_dispatch (context=0x179fec0) at ../../../../glib/gmain.c:3177
 g_main_context_dispatch (context=context@entry=0x179fec0) at ../../../../glib/gmain.c:3830
 g_main_context_iterate (context=0x179fec0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../../glib/gmain.c:3903

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
summary: - mate-tweak crashed with SIGSEGV in g_main_context_dispatch()
+ mate-tweak crashed with SIGSEGV in settings_backend_path_changed()
tags: removed: need-amd64-retrace
information type: Private → Public
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
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1757576

tags: added: iso-testing
no longer affects: glib2.0 (Ubuntu)
Norbert (nrbrtx)
Changed in mate-tweak (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for mate-tweak (Ubuntu) because there has been no activity for 60 days.]

Changed in mate-tweak (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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