Red Hat Bugzilla – Bug 974488
[abrt] unison240-2.40.102-2.fc18: gtk_tree_model_get_valist: Process /usr/bin/unison-2.40 was killed by signal 11 (SIGSEGV)
Last modified: 2014-12-25 23:51:17 EST
Version-Release number of selected component:
runlevel: N 5
var_log_messages: Jun 14 10:48:43 desktop abrt: Saved core dump of pid 14141 (/usr/bin/unison-2.40) to /var/tmp/abrt/ccpp-2013-06-14-10:48:42-14141 (39792640 bytes)
Thread no. 1 (10 frames)
#0 gtk_tree_model_get_valist at gtktreemodel.c:1470
#1 gtk_tree_model_get at gtktreemodel.c:1432
#2 combo_box_row_separator_func at gtkfilechooserbutton.c:2365
#3 tree_column_row_is_sensitive at gtkcombobox.c:1904
#4 gtk_combo_box_list_button_released at gtkcombobox.c:4160
#5 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
#10 gtk_widget_event_internal at gtkwidget.c:5017
#11 gtk_widget_event at gtkwidget.c:4814
#12 gtk_propagate_event at gtkmain.c:2490
#13 gtk_main_do_event at gtkmain.c:1685
Created attachment 761184 [details]
Created attachment 761185 [details]
Created attachment 761186 [details]
Created attachment 761187 [details]
Created attachment 761188 [details]
Created attachment 761189 [details]
Created attachment 761190 [details]
Created attachment 761191 [details]
Created attachment 761192 [details]
When creating a profile, in the "directory selection" step changing "local directory" dropdown the program crashes.
reason: Process /usr/bin/unison-2.40 was killed by signal 11 (SIGSEGV)
runlevel: N 5
that used to work in f17, didn't it?
(In reply to Gregor Tätzner from comment #11)
> that used to work in f17, didn't it?
Thanks for reply!
I work with f18.
*** Bug 975672 has been marked as a duplicate of this bug. ***
Same problem on a F18 installation here...
*** Bug 1013009 has been marked as a duplicate of this bug. ***
creating a new profile using the K desktop environment. This doesn't happen when using the gnome desktop.
reason: Process /usr/bin/unison-gtk-2.40 was killed by signal 11 (SIGSEGV)
runlevel: N 5
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.
Still broken in f19. I don't have an f20 machine handy to test right now.
Still broken in F20
Program received signal SIGSEGV, Segmentation fault.
0x000000341e435a12 in gtk_tree_model_get_valist ()