Red Hat Bugzilla – Bug 995738
[abrt] transmission-remote-gtk-1.1.1-1.fc19: view_popup_menu: Process /usr/bin/transmission-remote-gtk was killed by signal 11 (SIGSEGV)
Last modified: 2015-02-17 11:42:11 EST
Description of problem:
Typically The bug is that xbutton (close) calls sigsegv upon the procces
This time Daemon have crashed
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 view_popup_menu at trg-tree-view.c:332
#1 col_onButtonPressed at trg-tree-view.c:363
#2 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85
#7 gtk_widget_event_internal at gtkwidget.c:6714
#8 gtk_widget_event at gtkwidget.c:6371
#9 propagate_event_up at gtkmain.c:2393
#10 propagate_event at gtkmain.c:2501
#11 gtk_main_do_event at gtkmain.c:1716
#16 g_main_context_iteration at gmain.c:3762
#17 g_application_run at gapplication.c:1623
Created attachment 785219 [details]
Created attachment 785220 [details]
Created attachment 785221 [details]
Created attachment 785222 [details]
Created attachment 785223 [details]
Created attachment 785224 [details]
Created attachment 785225 [details]
Created attachment 785226 [details]
Created attachment 785227 [details]
Created attachment 785228 [details]
Created attachment 785229 [details]
Hey, I'm the upstream maintainer of this package.
This was reported on the transmission-remote-gtk bug tracker: http://code.google.com/p/transmission-remote-gtk/issues/detail?id=244&can=1&start=200
I think something in GTK changed, this used to work. But anyway, I've added a workaround in git, and I think this will fix it, and be in the next release.
If anyone's interested - I bound a pointer to the GtkTreeViewColumn, on a click signal on the GtkButton inside it, which seems to be invalid in some cases. In particular, when lots of columns have been removed. So I think GTK is recreating columns, but I'm not 100% sure. The workaround is just to use the column title to search through the column infos.
This message is a notice that Fedora 19 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 19. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.
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 19 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.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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.