Red Hat Bugzilla – Bug 990607
[abrt] xfce4-terminal-0.6.2-1.fc19: handle_error: Process /usr/bin/xfce4-terminal was killed by signal 5 (SIGTRAP)
Last modified: 2015-02-18 09:03:31 EST
Description of problem:
Shortly after starting up xfe terminal, and opening new windows, some of the open terminals crash
Version-Release number of selected component:
runlevel: N 5
Thread no. 1 (10 frames)
#4 handle_error at xcb_io.c:213
#5 handle_response at xcb_io.c:325
#7 XGetWindowProperty at GetProp.c:69
#8 fetch_net_wm_check_window at gdkevents-x11.c:2671
#9 gdk_x11_screen_supports_net_wm_hint at gdkevents-x11.c:2852
#10 gdk_x11_window_set_user_time at gdkwindow-x11.c:3741
#11 setup_toplevel_window at gdkwindow-x11.c:637
#12 _gdk_window_impl_new at gdkwindow-x11.c:821
#13 gdk_window_new at gdkwindow.c:1456
#14 gtk_window_realize at gtkwindow.c:4843
Created attachment 781160 [details]
Created attachment 781161 [details]
Created attachment 781162 [details]
Created attachment 781163 [details]
Created attachment 781164 [details]
Created attachment 781165 [details]
Created attachment 781166 [details]
Created attachment 781167 [details]
Created attachment 781168 [details]
Created attachment 781169 [details]
Only some of them crash?
Can you see any pattern between the ones that do crash and the ones that don't?
Just happened to me - fresh Fedora 19 x64 install, installed Xfce, opened a terminal the first time, saw crash notification.
Terminal still opened successfully (perhaps an immediate respawn?), but I had a notification of the crash, which resolved to this bugzilla entry.
happened again, reproducible.
I have a multi-monitor setup and prefer to have two independent X sessions (nvidia calls it "Separate X Sessions" in their settings utility). This works partially under Xfce4; many things are broken, but I am able to get the basic functionality of the desktop that I require.
Xfce seems 'confused' about the independent sessions, and that is where the broken things come it. I won't list all the the issues here, but this terminal bug is one of them. If I choose 'Open Terminal Here' from the desktop popup menu on one screen (screen0), it opens a terminal. If I then go to the other screen and choose 'Open Terminal Here' from the desktop popup menu on that screen (screen1), the first terminal on screen0 closes and I get a new terminal on screen1.
If I repeatedly choose 'Open Terminal Here' from the desktop popup menu on one screen, I get a new terminal window each time, and the existing ones stay open. As soon as I choose 'Open Terminal Here' from the desktop popup menu on the other screen, all the terminals on the initial screen close, and I get one new terminal on the current screen.
When the previous screens terminal(s) close(s), that will produce the stack trace in this bug.
This is the binary only non free nvidia driver?
Not sure there's too much we can do about that setup.
Looks like this may be these upstream bugs:
You may be able to work around it by calling "xfce4-terminal --disable-server" to avoid the server instance.
"This is the binary only non free nvidia driver?"
Nope, also happens on my ATI card with the non-free driver.
I got this alert with Fedora 20. I used muffin instead of xfwm4, maybe that caused xfce4-terminal to get confused.
$ lspci |grep -i vga
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7640G]
$ grep -i drv /var/log/Xorg.0.log
[ 16023.165] (II) Loading /usr/lib64/xorg/modules/drivers/ati_drv.so
[ 16023.174] (II) Loading /usr/lib64/xorg/modules/drivers/radeon_drv.so
[ 16023.184] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so
[ 16023.191] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so
[ 16023.201] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so
[ 16023.911] (II) Loading /usr/lib64/xorg/modules/input/evdev_drv.so
[ 16024.016] (II) Loading /usr/lib64/xorg/modules/input/synaptics_drv.so
Never seen any crash again. Seems to be fixed with Xfce 4.11.
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.