mate-settings-daemon crashed with SIGSEGV in XKeysymToKeycode()

Bug #1722402 reported by Chris Gregan
54
This bug affects 9 people
Affects Status Importance Assigned to Milestone
mate-settings-daemon (Ubuntu)
Expired
Medium
Unassigned

Bug Description

daemon simply crashes on launch after install.

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: mate-settings-daemon 1.18.1-2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 9 16:43:27 2017
ExecutablePath: /usr/bin/mate-settings-daemon
InstallationDate: Installed on 2016-07-01 (465 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
ProcCmdline: /usr/bin/mate-settings-daemon
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f1641e21f41 <XKeysymToKeycode+33>: cmpq $0x0,0x20(%rax)
 PC (0x7f1641e21f41) ok
 source "$0x0" ok
 destination "0x20(%rax)" (0x00000021) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: mate-settings-daemon
StacktraceTop:
 XKeysymToKeycode () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/mate-settings-daemon/libxrandr.so
 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_with_properties () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: mate-settings-daemon crashed with SIGSEGV in XKeysymToKeycode()
UpgradeStatus: Upgraded to artful on 2017-10-06 (3 days ago)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

Revision history for this message
Chris Gregan (cgregan) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 XKeysymToKeycode (dpy=dpy@entry=0x555a28bc72d0, ks=269025113) at ../../../src/xkb/XKBBind.c:157
 get_keycode_for_keysym_name (name=0x7f1635d9d72e "XF86Display") at msd-xrandr-manager.c:2463
 msd_xrandr_manager_init (manager=0x555a28d2bd90) at msd-xrandr-manager.c:2471
 g_type_create_instance (type=<optimized out>) at ../../../../gobject/gtype.c:1866
 g_object_new_internal (class=class@entry=0x555a28c85150, params=params@entry=0x0, n_params=n_params@entry=0) at ../../../../gobject/gobject.c:1797

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-settings-daemon (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Jean-Baptiste Lallement (jibel) wrote :

Thanks for your report. Does it crahes under xorg? (select ubuntu-xorg in the list of sessions on the login screen)

information type: Private → Public
Changed in mate-settings-daemon (Ubuntu):
status: New → Incomplete
tags: added: wayland
removed: wayland-session
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in mate-settings-daemon (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.