Bug 981440

Summary: [abrt] gnome-terminal-3.8.3-1.fc19: initial_tab_free: Process /usr/bin/gnome-terminal was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Andre Vehreschild <vehre>
Component: gnome-terminalAssignee: Matthias Clasen <mclasen>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6f561f03f41d9afe949c9401fe0702af26c8b9fd
Fixed In Version: gnome-terminal-3.8.4-1.fc19 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-12 03:15:57 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
File: var_log_messages none

Description Andre Vehreschild 2013-07-04 17:12:18 UTC 
Description of problem:
After release upgrade 17 -> 19 Fedora, after login into cinnamon session the gnome-terminal crashed without me doing anything.

Version-Release number of selected component:
gnome-terminal-3.8.3-1.fc19

Additional info:
reporter:       libreport-2.1.5
backtrace_rating: 4
cmdline:        gnome-terminal --sm-client-id 10683864c763c790d136662937276726200000188710045 --sm-client-state-file /home/vehre/.config/session-state/gnome-terminal-1372952595.desktop
crash_function: initial_tab_free
executable:     /usr/bin/gnome-terminal
kernel:         3.9.8-300.fc19.x86_64
runlevel:       N 5
uid:            1000
xsession_errors: 

Truncated backtrace:
Thread no. 1 (5 frames)
 #6 initial_tab_free at terminal-options.c:114
 #7 g_list_foreach at glist.c:949
 #8 initial_window_free at terminal-options.c:132
 #9 g_list_foreach at glist.c:949
 #10 terminal_options_free at terminal-options.c:982
Comment 1 Andre Vehreschild 2013-07-04 17:12:21 UTC 
Created attachment 768918 [details]
File: backtrace
Comment 2 Andre Vehreschild 2013-07-04 17:12:24 UTC 
Created attachment 768919 [details]
File: cgroup
Comment 3 Andre Vehreschild 2013-07-04 17:12:27 UTC 
Created attachment 768920 [details]
File: core_backtrace
Comment 4 Andre Vehreschild 2013-07-04 17:12:30 UTC 
Created attachment 768921 [details]
File: dso_list
Comment 5 Andre Vehreschild 2013-07-04 17:12:32 UTC 
Created attachment 768922 [details]
File: environ
Comment 6 Andre Vehreschild 2013-07-04 17:12:35 UTC 
Created attachment 768923 [details]
File: limits
Comment 7 Andre Vehreschild 2013-07-04 17:12:38 UTC 
Created attachment 768924 [details]
File: maps
Comment 8 Andre Vehreschild 2013-07-04 17:12:41 UTC 
Created attachment 768925 [details]
File: open_fds
Comment 9 Andre Vehreschild 2013-07-04 17:12:44 UTC 
Created attachment 768926 [details]
File: proc_pid_status
Comment 10 Andre Vehreschild 2013-07-04 17:12:47 UTC 
Created attachment 768927 [details]
File: var_log_messages
Comment 11 Fedora Update System 2013-07-08 23:51:46 UTC 
gnome-terminal-3.8.4-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/gnome-terminal-3.8.4-1.fc19
Comment 12 Fedora Update System 2013-07-10 01:30:23 UTC 
Package gnome-terminal-3.8.4-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gnome-terminal-3.8.4-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-12685/gnome-terminal-3.8.4-1.fc19
then log in and leave karma (feedback).
Comment 13 Fedora Update System 2013-07-12 03:15:57 UTC 
gnome-terminal-3.8.4-1.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.