Bug 1009147

Summary: [abrt] brasero-3.8.0-3.fc20: _g_log_abort: Process /usr/bin/brasero was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Clyde E. Kunkel <clydekunkel7734>
Component: braseroAssignee: Xavier Lamien <lxtnow>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: bitlord0xff, ignatenko, josh, lxtnow
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://bugzilla.gnome.org/show_bug.cgi?id=708419
Whiteboard: abrt_hash:1554ada14f93ca3eb7998c543c4b791a947021d3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-08-27 11:34:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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 Clyde E. Kunkel 2013-09-17 19:14:40 UTC 
Description of problem:
Just clicked on icon in favorites bar.

Version-Release number of selected component:
brasero-3.8.0-3.fc20

Additional info:
reporter:       libreport-2.1.7
backtrace_rating: 4
cmdline:        brasero
crash_function: _g_log_abort
executable:     /usr/bin/brasero
kernel:         3.12.0-0.rc0.git24.1.fc21.x86_64
runlevel:       unknown
type:           CCpp
uid:            1000
var_log_messages: Sep 14 17:28:42 P5K-EWIFI abrt[6845]: Saved core dump of pid 6827 (/usr/bin/brasero) to /var/tmp/abrt/ccpp-2013-09-14-17:28:42-6827 (42090496 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 _g_log_abort at gmessages.c:255
 #5 get_icon_fallback at gtkrecentmanager.c:1960
 #6 brasero_project_type_chooser_build_recent at brasero-project-type-chooser.c:331
 #7 brasero_project_type_chooser_init at brasero-project-type-chooser.c:525
 #8 g_type_create_instance at gtype.c:1868
 #9 g_object_new_internal at gobject.c:1746
 #12 brasero_project_type_chooser_new at brasero-project-type-chooser.c:586
 #13 brasero_project_manager_init at brasero-project-manager.c:838
 #14 g_type_create_instance at gtype.c:1868
 #15 g_object_new_internal at gobject.c:1746
Comment 1 Clyde E. Kunkel 2013-09-17 19:14:43 UTC 
Created attachment 798944 [details]
File: backtrace
Comment 2 Clyde E. Kunkel 2013-09-17 19:14:46 UTC 
Created attachment 798945 [details]
File: cgroup
Comment 3 Clyde E. Kunkel 2013-09-17 19:14:48 UTC 
Created attachment 798946 [details]
File: core_backtrace
Comment 4 Clyde E. Kunkel 2013-09-17 19:14:53 UTC 
Created attachment 798947 [details]
File: dso_list
Comment 5 Clyde E. Kunkel 2013-09-17 19:14:55 UTC 
Created attachment 798948 [details]
File: environ
Comment 6 Clyde E. Kunkel 2013-09-17 19:14:58 UTC 
Created attachment 798949 [details]
File: limits
Comment 7 Clyde E. Kunkel 2013-09-17 19:15:00 UTC 
Created attachment 798951 [details]
File: maps
Comment 8 Clyde E. Kunkel 2013-09-17 19:15:04 UTC 
Created attachment 798952 [details]
File: open_fds
Comment 9 Clyde E. Kunkel 2013-09-17 19:15:07 UTC 
Created attachment 798953 [details]
File: proc_pid_status
Comment 10 Branko Grubić 2013-09-20 08:00:14 UTC 
I think I have same problem with brasero ( brasero-3.8.0-4.fc20.x86_64 ) I reported it upstream, but not sure is problem for upstream or fedora, I'll add link to upstream report ...
Comment 11 Joshua Lock 2013-09-20 09:01:45 UTC 
Hi,

I recently took over maintaining Brasero and pushed a patch which I believe fixes this issue after some recent gtk+ changes:

https://git.gnome.org/browse/brasero/commit/?id=2eb68c9855e202899a3ab71d14d884c80c57b38a

As I didn't take over Brasero maintenance until late in the 3.10 cycle I haven't yet figured out making releases, but I'll try and make one soon with this fix.
Comment 12 Branko Grubić 2014-08-27 11:34:00 UTC 
This is fixed in f20, currently 'brasero-3.10.0-1.fc20.x86_64' works fine.
I'll close this bug.