Version-Release number of selected component: python-2.7.3-7.2.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/system-config-samba crash_function: map_eval kernel: 3.6.6-1.fc17.i686.PAE truncated backtrace: :Thread no. 1 (10 frames) : #0 map_eval at ../sigscheme/src/eval.c:555 : #2 call_closure at ../sigscheme/src/eval.c:184 : #3 call at ../sigscheme/src/eval.c:283 : #4 scm_eval at ../sigscheme/src/eval.c:499 : #5 scm_s_letstar at ../sigscheme/src/syntax.c:611 : #6 call at ../sigscheme/src/eval.c:420 : #7 scm_eval at ../sigscheme/src/eval.c:499 : #8 scm_s_letstar at ../sigscheme/src/syntax.c:611 : #9 call at ../sigscheme/src/eval.c:420 : #10 scm_eval at ../sigscheme/src/eval.c:499
Created attachment 650231 [details] File: core_backtrace
Created attachment 650232 [details] File: environ
Created attachment 650233 [details] File: limits
Created attachment 650234 [details] File: backtrace
Created attachment 650235 [details] File: cgroup
Created attachment 650236 [details] File: smolt_data
Created attachment 650237 [details] File: xsession_errors
Created attachment 650238 [details] File: executable
Created attachment 650239 [details] File: maps
Created attachment 650240 [details] File: dso_list
Created attachment 650241 [details] File: proc_pid_status
Created attachment 650242 [details] File: var_log_messages
Created attachment 650243 [details] File: open_fds
Created attachment 650244 [details] File: build_ids
Thanks for filing this bug report. How reproducible is this problem? Looking at attachment 650234 [details] I see that the segmentation fault happened deep within sigscheme (frames 0-38); frame 38 is within uim_scm_callf() with proc == "reset-handler". The frames directly above that were within gtk_im_context_reset called from a GtkEntry widget. Looking higher up in the stack I see repeated calls to gtk_entry_preedit_changed_cb() and a very deep stack (2047 frames deep), so this looks like an infinite recursion calling from GtkEntry into an Input Method. Looking at I see that the following libraries were mapped into memory: /usr/lib/gtk-2.0/2.10.0/immodules/im-uim.so /usr/lib/libuim-scm.so.0.1.0 (amongst others). Reassigning from "python" to "uim" in the hope that the uim maintainer will be able to correctly determine the component at fault here. Hope this is helpful
Indded, that looks like happening at uim. then, additional question from me except how to reproduce this issue is, what the engine do you use? since it was from uim, I guess it shouldn't be the sort of issues that happened at the startup time or with no actions. What did you do at it happened?
Hm, okay. I managed to reproduce. that looks strange to me though. How to reproduce: 1. install uim, uim-gtk2 and other IM (like ibus) 2. run system-config-samba 3. click + icon at the toolbar Additional information: this only happens when no GTK_IM_MODULE is set. it even works with GTK_IM_MODULE=uim.
*** Bug 885361 has been marked as a duplicate of this bug. ***
*** Bug 907988 has been marked as a duplicate of this bug. ***
*** Bug 904864 has been marked as a duplicate of this bug. ***
uim-1.8.4-3.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/uim-1.8.4-3.fc18
uim-1.8.4-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/uim-1.8.4-3.fc17
Package uim-1.8.4-3.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing uim-1.8.4-3.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-2786/uim-1.8.4-3.fc17 then log in and leave karma (feedback).
uim-1.8.4-3.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
uim-1.8.4-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.