Red Hat Bugzilla – Bug 892727
[abrt] ibus-184.108.40.20621109-8.fc18: _gdk_x11_display_error_event: Process /usr/libexec/ibus-ui-gtk3 was killed by signal 5 (SIGTRAP)
Last modified: 2014-01-22 15:21:55 EST
Description of problem:
Logged in to KDE as me (non-root) remotely using NX.
Version-Release number of selected component:
Thread no. 1 (10 frames)
#2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2416
#6 handle_error at xcb_io.c:212
#7 handle_response at xcb_io.c:324
#10 _cairo_xlib_shm_surface_flush at cairo-xlib-surface-shm.c:640
#11 _cairo_xlib_surface_get_shm at cairo-xlib-surface-shm.c:982
#12 _cairo_xlib_surface_map_to_image at cairo-xlib-surface.c:1388
#13 _cairo_surface_map_to_image at cairo-surface.c:637
#14 render_pattern at cairo-xlib-source.c:296
#15 _cairo_xlib_source_create_for_pattern at cairo-xlib-source.c:1102
#17 composite_aligned_boxes at cairo-traps-compositor.c:1272
Created attachment 674175 [details]
Created attachment 674176 [details]
Created attachment 674177 [details]
Created attachment 674178 [details]
Created attachment 674179 [details]
Created attachment 674180 [details]
Created attachment 674181 [details]
Created attachment 674182 [details]
Created attachment 674183 [details]
Created attachment 674184 [details]
In case it's relevant:
This doesn't happen to me when I log in to KDE normally on the console. Only when I login via NX, and don't own the console. It would have been showing gdm at the time.
(In reply to comment #11)
> In case it's relevant:
> This doesn't happen to me when I log in to KDE normally on the console. Only
> when I login via NX, and don't own the console. It would have been showing
> gdm at the time.
Probably I guess the problem is in NX client.
I cannot reproduce your problem since I don't have NX.
Would it be reasonable to change the component to freenx-server instead?
It seems like this would be what was "in control" when ibus reported the exception?
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.
Still happens in current Fedora releases?
No; it looks like it's stopped happening for me. I totally forgot about this report.