cinnamon-settings.py crashed with SIGSEGV in xkl_engine_constructor()

Bug #1720246 reported by BobDodds
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
cinnamon (Ubuntu)
In Progress
Medium
Unassigned

Bug Description

in artful 17.10, tried to Remove.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: cinnamon-common 3.4.6-1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 28 17:42:30 2017
ExecutablePath: /usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py
InstallationDate: Installed on 2017-09-26 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170720)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python2 /usr/share/cinnamon/cinnamon-settings/cinnamon-settings.py keyboard
Python3Details: /usr/bin/python3.6, Python 3.6.3rc1, python3-minimal, 3.6.2-1ubuntu4
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1
SegvAnalysis:
 Segfault happened at: 0x7fe4bda8c9c1: mov 0x10(%rax),%rax
 PC (0x7fe4bda8c9c1) ok
 source "0x10(%rax)" (0xffffffee23b8d010) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: cinnamon
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libxklavier.so.16
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 xkl_engine_get_instance () from /usr/lib/x86_64-linux-gnu/libxklavier.so.16
Title: cinnamon-settings.py crashed with SIGSEGV in g_object_new_valist()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
BobDodds (bobdodds) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 xkl_engine_constructor (type=<optimized out>, n_construct_properties=<optimized out>, construct_properties=<optimized out>) at xklavier.c:669
 g_object_new_with_custom_constructor (n_params=1, params=0x7fff5fcaab90, class=0x55a525602610) at ../../../../gobject/gobject.c:1699
 g_object_new_internal (class=class@entry=0x55a525602610, params=params@entry=0x7fff5fcaab90, n_params=n_params@entry=1) at ../../../../gobject/gobject.c:1779
 g_object_new_valist (object_type=94167784783040, first_property_name=first_property_name@entry=0x7fe4bda967ff "display", var_args=var_args@entry=0x7fff5fcaace0) at ../../../../gobject/gobject.c:2104
 g_object_new (object_type=<optimized out>, first_property_name=first_property_name@entry=0x7fe4bda967ff "display") at ../../../../gobject/gobject.c:1624

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 cinnamon (Ubuntu):
importance: Undecided → Medium
summary: - cinnamon-settings.py crashed with SIGSEGV in g_object_new_valist()
+ cinnamon-settings.py crashed with SIGSEGV in xkl_engine_constructor()
tags: removed: need-amd64-retrace
information type: Private → Public
tags: added: wayland
removed: wayland-session
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in cinnamon (Ubuntu):
status: New → Confirmed
Changed in cinnamon (Ubuntu):
status: Confirmed → In Progress
Revision history for this message
Fantu (fantonifabio) wrote :

why this was marked as "in progress"? Trace don't have full symbols and I cannot understand from the present data what could be the cause, I not understand why is marked wayland (cinnamon don't have wayland support now), is there something more expert that can explain what he discovered about this please? to understand at least if is an issue related to cinnamon, not solved or solved in new version.
Ubuntu 17.10 reached EOL and I suppose that this can be keep only if is a cinnamon issue, still present and not solved

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.