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
Created attachment 930454 [details] File: backtrace
Created attachment 930455 [details] File: cgroup
Created attachment 930456 [details] File: core_backtrace
Created attachment 930457 [details] File: dso_list
Created attachment 930458 [details] File: environ
Created attachment 930459 [details] File: exploitable
Created attachment 930460 [details] File: limits
Created attachment 930461 [details] File: maps
Created attachment 930462 [details] File: open_fds
Created attachment 930463 [details] File: proc_pid_status
Created attachment 930464 [details] File: var_log_messages
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.
Created attachment 930746 [details] complete backtrace ok.
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
I've tried to report bug which can't be reported. I tried emergency IIRC. Anyway I can't reproduce.
Thank you very much indeed! Upstream commit https://github.com/abrt/libreport/commit/8bea4c9b68fcdb62879b603ba5c2914b6cd8c33a fixes this bug.