gsd-wacom crashed with SIGSEGV in g_type_check_value()

Bug #1765795 reported by Marc MICHEL
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
New
Undecided
Unassigned

Bug Description

...

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 20 19:11:23 2018
ExecutablePath: /usr/lib/gnome-settings-daemon/gsd-wacom
InstallationDate: Installed on 2018-04-07 (13 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
ProcCmdline: /usr/lib/gnome-settings-daemon/gsd-wacom
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f81f2050454 <g_type_check_value+164>: testb $0x4,0x16(%rbx)
 PC (0x7f81f2050454) ok
 source "$0x4" ok
 destination "0x16(%rbx)" (0x00000016) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-settings-daemon
StacktraceTop:
 g_type_check_value () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 gtk_css_provider_load_from_file () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gsd-wacom crashed with SIGSEGV in g_type_check_value()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Marc MICHEL (mmarc6930) 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 #1763316, 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
Revision history for this message
Juan Diego Pérez Bohórquez (juan1198) wrote :

Is there already a solution to this problem?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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