gnome-terminal-server crashed with SIGSEGV in g_type_check_instance_is_a() while editing shortcuts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-terminal (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
1)
Description: Ubuntu Zesty Zapus (development branch)
Release: 17.04
2)
gnome-terminal:
Installed: 3.20.2-1ubuntu5
3)
Open gnome-terminal, open menu Edit->Preferences, open Shortcuts tab, scroll to the end, change key for Help-Contents
Change the shortcut several times, using various combinations of Ctrl, Alt, Shift, "Win" (Super_L" keys with letters W/E/Q... or Function keys like F1,F2
3)
Expected: changed shortcut and working gnome-terminal
4)
After several changes gnome-terminal closes with SIGSEGV and apport.
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu5
ProcVersionSign
Uname: Linux 4.10.0-8-generic x86_64
ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CurrentDesktop: MATE
Date: Thu Feb 23 09:49:49 2017
ExecutablePath: /usr/lib/
ExecutableTimes
InstallationDate: Installed on 2017-02-22 (1 days ago)
InstallationMedia: Ubuntu-MATE 17.04 "Zesty Zapus" - Alpha amd64 (20170125)
ProcCmdline: /usr/lib/
ProcCwd: /home/user
RetraceOutdated
no debug symbol package found for libepoxy0
no debug symbol package found for libwayland-cursor0
no debug symbol package found for libharfbuzz0b
Signal: 11
SourcePackage: gnome-terminal
StacktraceTop:
g_type_
gtk_widget_
window_
gtk_window_
gtk_window_
Title: gnome-terminal-
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 #1438014, 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.