gnome-tweak-tool crashed with SIGSEGV in gtk_expander_set_label_widget()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-tweak-tool (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
the crash happens when select "Keybord & Mouse" > "Additional Layout Options" > "Key Sequence to kill the X server" and check "Ctrl + Alt + Backspace"
the crash only happened the first time... later work ok.
> lsb_release -rd
Description: Ubuntu 17.10
Release: 17.10
> apt-cache policy gnome-tweak-tool
gnome-tweak-tool:
Installed: 3.26.2.1-1ubuntu1
Candidate: 3.26.2.1-1ubuntu1
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: gnome-tweak-tool 3.26.2.1-1ubuntu1
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 21 22:08:06 2017
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2017-10-21 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
InterpreterPath: /usr/bin/python3.6
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/bin/
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonDetails: /home/nelson/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/home/
SegvAnalysis:
Segfault happened at: 0x7f57ac2fb7bf: mov 0x8(%r13),%rdi
PC (0x7f57ac2fb7bf) ok
source "0x8(%r13)" (0xffffffffffff
destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gnome-tweak-tool
StacktraceTop:
?? () from /usr/lib/
gtk_expander_
gtk_expander_
ffi_call_unix64 () from /usr/lib/
ffi_call () from /usr/lib/
Title: gnome-tweak-tool crashed with SIGSEGV in gtk_expander_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1724358, 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.