Bug 1036374

Summary: [abrt] gnome-terminal-3.8.4-1.fc19: _g_utf8_normalize_wc: Process /usr/libexec/gnome-terminal-server was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Serge Pavlovsky <pal666>
Component: gnome-terminalAssignee: Matthias Clasen <mclasen>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: mclasen, zeenix
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/43ceba844828eb9bb555beae84245b675f23197a
Whiteboard: abrt_hash:de8ff4a5fa5967dd26525f9ccc957da85008726d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-17 19:28:58 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages
none
dconf dump /org/gnome/terminal/ none

Description Serge Pavlovsky 2013-12-01 17:34:11 UTC 
Version-Release number of selected component:
gnome-terminal-3.8.4-1.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/libexec/gnome-terminal-server
crash_function: _g_utf8_normalize_wc
executable:     /usr/libexec/gnome-terminal-server
kernel:         3.11.4-201.fc19.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _g_utf8_normalize_wc at gunidecomp.c:374
 #1 g_utf8_collate at gunicollate.c:114
 #2 terminal_profiles_compare at terminal-profiles-list.c:260
 #3 g_list_sort_merge at glist.c:1066
 #4 g_list_sort_real at glist.c:1112
 #6 g_list_sort at glist.c:1149
 #7 terminal_profiles_list_ref_children at terminal-profiles-list.c:110
 #8 terminal_window_update_set_profile_menu at terminal-window.c:534
 #9 terminal_window_profile_list_changed_cb at terminal-window.c:1621
 #14 terminal_settings_list_update_list at terminal-settings-list.c:449
Comment 1 Serge Pavlovsky 2013-12-01 17:34:18 UTC 
Created attachment 831243 [details]
File: backtrace
Comment 2 Serge Pavlovsky 2013-12-01 17:34:21 UTC 
Created attachment 831244 [details]
File: cgroup
Comment 3 Serge Pavlovsky 2013-12-01 17:34:25 UTC 
Created attachment 831245 [details]
File: core_backtrace
Comment 4 Serge Pavlovsky 2013-12-01 17:34:28 UTC 
Created attachment 831246 [details]
File: dso_list
Comment 5 Serge Pavlovsky 2013-12-01 17:34:31 UTC 
Created attachment 831247 [details]
File: environ
Comment 6 Serge Pavlovsky 2013-12-01 17:34:33 UTC 
Created attachment 831248 [details]
File: exploitable
Comment 7 Serge Pavlovsky 2013-12-01 17:34:38 UTC 
Created attachment 831249 [details]
File: limits
Comment 8 Serge Pavlovsky 2013-12-01 17:34:44 UTC 
Created attachment 831250 [details]
File: maps
Comment 9 Serge Pavlovsky 2013-12-01 17:34:47 UTC 
Created attachment 831251 [details]
File: open_fds
Comment 10 Serge Pavlovsky 2013-12-01 17:34:50 UTC 
Created attachment 831252 [details]
File: proc_pid_status
Comment 11 Serge Pavlovsky 2013-12-01 17:34:54 UTC 
Created attachment 831253 [details]
File: var_log_messages
Comment 12 Christian Persch 2013-12-02 10:49:01 UTC 
Can you please attach the output of this command as a file (not in a comment):

dconf dump /org/gnome/terminal/
Comment 13 Serge Pavlovsky 2013-12-02 13:25:23 UTC 
Created attachment 831574 [details]
dconf dump /org/gnome/terminal/
Comment 14 Christian Persch 2013-12-02 17:07:17 UTC 
Thanks. It disproves my guess at what might have been wrong, however.  Were there any messages in the journal from gnome-terminal-server prior to the crash? (journalctl _EXE=/usr/libexec/gnome-terminal-server) Attachment 831253 [details] seems to consist only of abrt output...
Comment 15 Serge Pavlovsky 2013-12-03 15:05:14 UTC 
-- Logs begin at Пн 2013-10-07 16:04:45 EEST, end at Вт 2013-12-03 17:03:00 EET. --
Comment 16 Fedora End Of Life 2015-01-09 20:44:58 UTC 
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 17 Fedora End Of Life 2015-02-17 19:28:58 UTC 
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.