Red Hat Bugzilla – Bug 977010
[abrt] gnome-terminal-3.8.3-1.fc19: update_edit_menu_cb: Process /usr/libexec/gnome-terminal-server was killed by signal 11 (SIGSEGV)
Last modified: 2016-01-15 12:31:25 EST
Description of problem:
had 8 tabs open, was not even looking at that window, was not focused
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#0 update_edit_menu_cb at terminal-window.c:986
#1 request_targets_received_func at gtkclipboard.c:1292
#2 selection_received at gtkclipboard.c:939
#6 g_signal_emit_by_name at gsignal.c:3424
#7 gtk_selection_retrieval_report at gtkselection.c:2983
#8 _gtk_selection_notify at gtkselection.c:2787
#9 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130
#10 _g_closure_invoke_va at gclosure.c:840
#13 gtk_widget_event_internal at gtkwidget.c:6714
#14 gtk_widget_event at gtkwidget.c:6371
Created attachment 764105 [details]
Created attachment 764106 [details]
Created attachment 764107 [details]
Created attachment 764108 [details]
Created attachment 764109 [details]
Created attachment 764110 [details]
Created attachment 764111 [details]
Created attachment 764112 [details]
Created attachment 764113 [details]
Created attachment 764114 [details]
Thread 1 (Thread 0x7fb3b42e4a00 (LWP 11516)):
#0 update_edit_menu_cb (clipboard=0xbf2ec0, targets=0x100b800, n_targets=10, window=0x0) at terminal-window.c:986
priv = <optimized out>
action = <optimized out>
can_paste = <optimized out>
can_paste_uris = <optimized out>
window=0x0 is totally impossible here; the code makes sure it's always a valid TerminalWindow (adding a ref, even!). No idea what's going on here.
(In reply to Christian Persch (GNOME) from comment #11)
> Thread 1 (Thread 0x7fb3b42e4a00 (LWP 11516)):
> #0 update_edit_menu_cb (clipboard=0xbf2ec0, targets=0x100b800,
> n_targets=10, window=0x0) at terminal-window.c:986
> priv = <optimized out>
> action = <optimized out>
> can_paste = <optimized out>
> can_paste_uris = <optimized out>
> window=0x0 is totally impossible here; the code makes sure it's always a
> valid TerminalWindow (adding a ref, even!). No idea what's going on here.
Someone pointed out in RHEL bug that these patches should help:
Something clipboard related could well be the cause, it would explain why the window was not even being used, and I do play with the clipboard a lot whilst testing xpra.
So can we move forward with getting these upstream commits into Fedora (and RHEL)?
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.