Version-Release number of selected component: gtkhash-0.6.0-1.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: gtkhash crash_function: g_thread_abort kernel: 3.6.6-1.fc17.i686.PAE truncated backtrace: :Thread no. 1 (8 frames) : #3 g_thread_abort at gthread-posix.c:76 : #4 g_mutex_lock at gthread-posix.c:209 : #5 g_main_context_acquire at gmain.c:2624 : #6 g_main_context_push_thread_default at gmain.c:660 : #7 g_simple_async_result_complete at gsimpleasyncresult.c:766 : #8 complete_in_idle_cb_for_thread at gsimpleasyncresult.c:835 : #14 gtk_main at gtkmain.c:1257 : #15 gui_run at ../../src/gui.c:438
Created attachment 648017 [details] File: environ
Created attachment 648018 [details] File: backtrace
Created attachment 648019 [details] File: limits
Created attachment 648020 [details] File: smolt_data
Created attachment 648021 [details] File: cgroup
Created attachment 648022 [details] File: executable
Created attachment 648023 [details] File: maps
Created attachment 648024 [details] File: dso_list
Created attachment 648025 [details] File: proc_pid_status
Created attachment 648026 [details] File: open_fds
Created attachment 648027 [details] File: var_log_messages
Thanks for submitting this crash report. Do you recall what you did when grsync crashed? Can you reproduce the crash reliably? If so, how?
(In reply to comment #12) > Thanks for submitting this crash report. Do you recall what you did when > grsync crashed? Can you reproduce the crash reliably? If so, how? Hello Christoph. Regarding your question, the answer is no I don't remember what caused grsync to crash. I can't reproduce the crash reliably. Sorry.
Thanks for your feedback. Unfortunately the backtrace is not complete. Can you please run debuginfo install gtkhash and then regenerate the backtrash with the ABRT tool locally?
(In reply to comment #14) > debuginfo install gtkhash Sorry, it's debuginfo-install gtkhash
Please reopen this report if you have a complete backtrace.