Red Hat Bugzilla – Bug 1292979
[abrt] swami: g_type_fundamental(): swami killed by SIGSEGV
Last modified: 2016-12-20 12:10:10 EST
Version-Release number of selected component:
cmdline: swami -p
runlevel: N 5
Thread no. 1 (10 frames)
#0 g_type_fundamental at gtype.c:4005
#2 swamigui_new_item at /usr/src/debug/swami-2.0.0/src/swamigui/patch_funcs.c:418
#3 swamigui_item_menu_callback_activate at /usr/src/debug/swami-2.0.0/src/swamigui/SwamiguiItemMenu.c:431
#8 gtk_widget_activate at gtkwidget.c:5048
#9 gtk_menu_shell_activate_item at gtkmenushell.c:1303
#10 gtk_menu_shell_button_release at gtkmenushell.c:730
#11 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
#16 gtk_widget_event_internal at gtkwidget.c:5017
#17 gtk_widget_event at gtkwidget.c:4814
#18 gtk_propagate_event at gtkmain.c:2501
Created attachment 1107501 [details]
Created attachment 1107502 [details]
Created attachment 1107503 [details]
Created attachment 1107504 [details]
Created attachment 1107505 [details]
Created attachment 1107506 [details]
Created attachment 1107507 [details]
Created attachment 1107508 [details]
Created attachment 1107509 [details]
Created attachment 1107510 [details]
Created attachment 1107511 [details]
Created attachment 1107512 [details]
Created attachment 1107513 [details]
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. 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 EOL if it remains open with a Fedora 'version'
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.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 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 this bug is closed as described in the policy above.
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.
Ran into this as well -
Though I didn't track down the actual bug, it looks like the
dependency libraries have shifted out from underneath the package -
I started to attempt a rebuild from the srpm, but cross checking the SRPM
sources against upstream before I started this shows that the package itself
is wildly out of date - For example:
The package is based on SVN? sources, but the project switched to GIT some
time ago, and also the older sources used autotools for the build
whereas currently the project has switched to cmake based builds.
Following the from source build instructions on the upstream site yielded
a working swami on Fedora 24 after installing needed -devel packages, minor
environment settings, etc though I did this a few weeks a go in a pinch and didn't report findings here, so I might have forgotton some small things.
Someone who is mildly comfortable with from-source builds should probably
not have any trouble here.
I've saved my shell history and will probably attempt another,
cleaner run at some point whenever I move over to fedora 25, at which
point I should be able to provide clean steps - from there, someone with
good package knowledge might be able to assist with a git+cmake based update
to the spec.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.