Bug 1238515

Summary: [abrt] gnome-terminal: g_settings_schema_get_value(): gnome-terminal-server killed by SIGTRAP
Product: [Fedora] Fedora Reporter: Shantanu <shantanu.mg>
Component: gnome-terminalAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: debarshir, glongwave, mclasen, sjchavan03.77, z304332501, zeenix
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/574a188da6834e6f1e819d12413367802672acbf
Whiteboard: abrt_hash:6733c5beaf3a44063c499db708d6e3877988019e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-26 09:37:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Shantanu 2015-07-02 03:18:28 UTC 
Description of problem:
i was installing software update by restarting it stuck on 55% then i directly power offed computer.the next day when i started it i tried to open terminal but bug occured server killed by sigtrap.and terminal does not open anymore.i cant even install other terminal.it doesnt work even if i enter correct password.i cant program now.

Version-Release number of selected component:
gnome-terminal-3.10.2-1.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-terminal-server
crash_function: g_settings_schema_get_value
executable:     /usr/libexec/gnome-terminal-server
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
var_log_messages: [System Logs]:\n-- Logs begin at Fri 2015-06-26 17:17:14 IST, end at Wed 2015-07-01 07:12:46 IST. --

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 g_settings_schema_get_value at gsettingsschema.c:640
 #3 g_settings_schema_key_init at gsettingsschema.c:805
 #4 g_settings_get_value at gsettings.c:1074
 #5 g_settings_get_boolean at gsettings.c:1780
 #6 update_color_scheme at terminal-screen.c:994
 #7 terminal_screen_profile_changed_cb at terminal-screen.c:907
 #8 terminal_screen_set_profile at terminal-screen.c:1086
 #9 terminal_screen_new at terminal-screen.c:622
 #10 terminal_factory_impl_create_instance at terminal-gdbus.c:456
 #11 ffi_call_unix64 at ../src/x86/unix64.S:76

Potential duplicate: bug 919715
Comment 1 Shantanu 2015-07-02 03:18:32 UTC 
Created attachment 1045331 [details]
File: backtrace
Comment 2 Shantanu 2015-07-02 03:18:34 UTC 
Created attachment 1045332 [details]
File: cgroup
Comment 3 Shantanu 2015-07-02 03:18:36 UTC 
Created attachment 1045333 [details]
File: core_backtrace
Comment 4 Shantanu 2015-07-02 03:18:38 UTC 
Created attachment 1045334 [details]
File: dso_list
Comment 5 Shantanu 2015-07-02 03:18:39 UTC 
Created attachment 1045335 [details]
File: environ
Comment 6 Shantanu 2015-07-02 03:18:40 UTC 
Created attachment 1045336 [details]
File: limits
Comment 7 Shantanu 2015-07-02 03:18:43 UTC 
Created attachment 1045337 [details]
File: maps
Comment 8 Shantanu 2015-07-02 03:18:44 UTC 
Created attachment 1045338 [details]
File: open_fds
Comment 9 Shantanu 2015-07-02 03:18:46 UTC 
Created attachment 1045339 [details]
File: proc_pid_status
Comment 10 Jan Kurik 2015-12-22 11:30:32 UTC 
This bug is currently assigned to an unsupported release. If you think this bug is still valid and should remain open, please re-assign it to a supported release (F22, F23) or to rawhide.

Bugs which will be assigned to an unsupported release are going to be closed as EOL (End Of Life) on January 26th, 2016.
Comment 11 ChangBo Guo(gcb) 2016-01-10 13:27:14 UTC 
I met the same issues as Shantanu described. Is there any workaround for this. It's really a critical bug for user.
Comment 12 Debarshi Ray 2016-01-15 12:41:23 UTC 
(In reply to Shantanu from comment #0)
> Description of problem:
> i was installing software update by restarting it stuck on 55% then i
> directly power offed computer.the next day when i started it i tried to open
> terminal but bug occured server killed by sigtrap.

Maybe something got corrupted when you forced the restart.

> and terminal does not open
> anymore.i cant even install other terminal.it doesnt work even if i enter
> correct password.i cant program now.

What do you mean by "can't even install other terminal"?

> Additional info:
> reporter:       libreport-2.2.3
> backtrace_rating: 4
> cmdline:        /usr/libexec/gnome-terminal-server
> crash_function: g_settings_schema_get_value
> executable:     /usr/libexec/gnome-terminal-server
> kernel:         3.11.10-301.fc20.x86_64
> runlevel:       N 5
> type:           CCpp
> uid:            1000
> var_log_messages: [System Logs]:\n-- Logs begin at Fri 2015-06-26 17:17:14
> IST, end at Wed 2015-07-01 07:12:46 IST. --
> 
> Truncated backtrace:
> Thread no. 1 (10 frames)
>  #2 g_settings_schema_get_value at gsettingsschema.c:640
>  #3 g_settings_schema_key_init at gsettingsschema.c:805
>  #4 g_settings_get_value at gsettings.c:1074
>  #5 g_settings_get_boolean at gsettings.c:1780
>  #6 update_color_scheme at terminal-screen.c:994
>  #7 terminal_screen_profile_changed_cb at terminal-screen.c:907
>  #8 terminal_screen_set_profile at terminal-screen.c:1086
>  #9 terminal_screen_new at terminal-screen.c:622
>  #10 terminal_factory_impl_create_instance at terminal-gdbus.c:456
>  #11 ffi_call_unix64 at ../src/x86/unix64.S:76

Does it work if you reset your user settings by deleting ~/.config/dconf/user (after taking a backup)?