Bug 1133549

Summary: report-gtk killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Igor Gnatenko <ignatenko>
Component: libreportAssignee: Jakub Filak <jfilak>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: abrt-devel-list, dvlasenk, ignatenko, jberan, jfilak, mmilata, mtoman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ed54ca633a1d4328d3c7c0eeb235894b669e5369
Whiteboard: abrt_hash:877c0400a0410d687601c183f9aad5182ee7dc85
Fixed In Version: libreport-2.2.3-6.fc22 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-09-04 05:29:10 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
complete backtrace none

Description Igor Gnatenko 2014-08-25 12:52:18 UTC 
Version-Release number of selected component:
libreport-gtk-2.2.3-5.fc22

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        report-gtk -- /var/tmp/abrt/ccpp-2014-08-25-11:37:24-20176
crash_function: strlen
executable:     /usr/bin/report-gtk
kernel:         3.17.0-0.rc1.git3.1.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 strlen at /lib64/libc.so.6
 #1 select_next_page_no.isra
 #2 on_btn_repeat_cb
 #3 _g_closure_invoke_va at /lib64/libgobject-2.0.so.0
 #6 gtk_button_do_release at /lib64/libgtk-3.so.0
 #7 gtk_real_button_released at /lib64/libgtk-3.so.0
 #12 ffi_call_unix64 at /lib64/libffi.so.6
 #13 ffi_call at /lib64/libffi.so.6
 #14 g_cclosure_marshal_generic_va at /lib64/libgobject-2.0.so.0
 #15 _g_closure_invoke_va at /lib64/libgobject-2.0.so.0
Comment 1 Igor Gnatenko 2014-08-25 12:52:22 UTC 
Created attachment 930454 [details]
File: backtrace
Comment 2 Igor Gnatenko 2014-08-25 12:52:23 UTC 
Created attachment 930455 [details]
File: cgroup
Comment 3 Igor Gnatenko 2014-08-25 12:52:25 UTC 
Created attachment 930456 [details]
File: core_backtrace
Comment 4 Igor Gnatenko 2014-08-25 12:52:26 UTC 
Created attachment 930457 [details]
File: dso_list
Comment 5 Igor Gnatenko 2014-08-25 12:52:28 UTC 
Created attachment 930458 [details]
File: environ
Comment 6 Igor Gnatenko 2014-08-25 12:52:29 UTC 
Created attachment 930459 [details]
File: exploitable
Comment 7 Igor Gnatenko 2014-08-25 12:52:31 UTC 
Created attachment 930460 [details]
File: limits
Comment 8 Igor Gnatenko 2014-08-25 12:52:33 UTC 
Created attachment 930461 [details]
File: maps
Comment 9 Igor Gnatenko 2014-08-25 12:52:34 UTC 
Created attachment 930462 [details]
File: open_fds
Comment 10 Igor Gnatenko 2014-08-25 12:52:35 UTC 
Created attachment 930463 [details]
File: proc_pid_status
Comment 11 Igor Gnatenko 2014-08-25 12:52:37 UTC 
Created attachment 930464 [details]
File: var_log_messages
Comment 12 Jakub Filak 2014-08-25 13:27:33 UTC 
Hello, thank you for taking the time to report this crash. Unfortunately, the backtrace is not very helpful because the backtrace has been generated without appropriate debuginfo packages. Could you please try to install the required debuginfo packages and generate the backtrace manually? Please follow the instractions at http://fedoraproject.org/wiki/StackTraces . The core dump file is store in /var/tmp/abrt/$dumpdir/coredump.
Comment 13 Igor Gnatenko 2014-08-26 06:22:38 UTC 
Created attachment 930746 [details]
complete backtrace

ok.
Comment 14 Jakub Filak 2014-08-26 09:43:05 UTC 
Thank you for the complete backtrace! Now I know where this crash occurred but I cannot reproduce it. Do you know how to reproduce this crash?

I have run the following scenario:

1. start the reporting from the GUI
2. wrote a comment, reviewed data
3. started uploading the data to Bugzilla
4. the previous step failed, so I reconfigured the application and clicked 'Repeat' button
5. a Bugzilla bug was created
Comment 15 Igor Gnatenko 2014-08-26 09:48:23 UTC 
I've tried to report bug which can't be reported. I tried emergency IIRC. Anyway I can't reproduce.
Comment 16 Jakub Filak 2014-08-26 11:29:29 UTC 
Thank you very much indeed!

Upstream commit https://github.com/abrt/libreport/commit/8bea4c9b68fcdb62879b603ba5c2914b6cd8c33a fixes this bug.