Version-Release number of selected component: ibus-1.5.10-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/libexec/ibus-ui-gtk3 crash_function: _gdk_x11_display_error_event executable: /usr/libexec/ibus-ui-gtk3 kernel: 3.18.9-200.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: [System Logs]:\n-- Logs begin at 五 2015-02-27 18:44:31 HKT, end at 二 2015-03-17 08:42:15 HKT. -- Truncated backtrace: Thread no. 1 (10 frames) #2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2539 #5 handle_error at xcb_io.c:213 #6 handle_response at xcb_io.c:325 #7 _XEventsQueued at xcb_io.c:364 #8 XPending at Pending.c:55 #9 gdk_check_xpending at gdkeventsource.c:266 #10 gdk_event_source_check at gdkeventsource.c:303 #11 g_main_context_check at gmain.c:3622 #14 gtk_main at gtkmain.c:1207 #15 application_run at application.c:199 Potential duplicate: bug 1114580
Created attachment 1002573 [details] File: backtrace
Created attachment 1002574 [details] File: cgroup
Created attachment 1002576 [details] File: core_backtrace
Created attachment 1002577 [details] File: dso_list
Created attachment 1002578 [details] File: environ
Created attachment 1002579 [details] File: limits
Created attachment 1002580 [details] File: maps
Created attachment 1002581 [details] File: open_fds
Created attachment 1002582 [details] File: proc_pid_status
I cannot reproduce your backtrace. Are you still able to see your backtrace? (In reply to Vladimir Netanyahu from comment #1) > Created attachment 1002573 [details] > File: backtrace > #0 g_logv (log_domain=0x7f3984904dce "Gdk", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7ffc2b26c790) at gmessages.c:1046 > msg = 0x1d90ad0 "The program 'ibus-ui-gtk3' received an X Window System error.\nThis probably reflects a bug in the program.\nThe error was 'BadWindow (invalid Window parameter)'.\n (Details: serial 916 error_code 3 req"... > msg_alloc = 0x1d90ad0 "The program 'ibus-ui-gtk3' received an X Window System error.\nThis probably reflects a bug in the program.\nThe error was 'BadWindow (invalid Window parameter)'.\n (Details: serial 916 error_code 3 req"... > #1 0x00007f398284fbaf in g_log (log_domain=log_domain@entry=0x7f3984904dce "Gdk", log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x7f3984920bcc "%s") at gmessages.c:1079 > #2 0x00007f39848d92fd in _gdk_x11_display_error_event (display=display@entry=0x1b24000, error=error@entry=0x7ffc2b26c930) at gdkdisplay-x11.c:2539 > buf = "BadWindow (invalid Window parameter)", '\000' <repeats 27 times> > #3 0x00007f39848e1cd1 in gdk_x_error (xdisplay=0x1b16a20, error=0x7ffc2b26c930) at gdkmain-x11.c:302 > #4 0x00007f39839df4dd in _XError (dpy=dpy@entry=0x1b16a20, rep=rep@entry=0x1c5a620) at XlibInt.c:1463 > #5 0x00007f39839dc427 in handle_error (dpy=0x1b16a20, err=0x1c5a620, in_XReply=<optimized out>) at xcb_io.c:213 > #6 0x00007f39839dc4e5 in handle_response (dpy=dpy@entry=0x1b16a20, response=0x1c5a620, in_XReply=in_XReply@entry=0) at xcb_io.c:325 > #7 0x00007f39839dce95 in _XEventsQueued (dpy=dpy@entry=0x1b16a20, mode=mode@entry=2) at xcb_io.c:364 > #8 0x00007f39839ce7d7 in XPending (dpy=0x1b16a20) at Pending.c:55 > #9 0x00007f39848dec7c in gdk_check_xpending (display=<optimized out>) at gdkeventsource.c:266 > #10 gdk_event_source_check (source=0x1b39f00) at gdkeventsource.c:303 > #11 0x00007f3982848551 in g_main_context_check (context=context@entry=0x1b11130, max_priority=2147483647, fds=fds@entry=0x1b60e70, n_fds=n_fds@entry=3) at gmain.c:3622 > #12 0x00007f3982848ad3 in g_main_context_iterate (context=0x1b11130, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3778 > #13 0x00007f3982848ec2 in g_main_loop_run (loop=0x1b669f0) at gmain.c:3975 > #14 0x00007f3984d35055 in gtk_main () at gtkmain.c:1207 > #15 0x0000000000409fae in application_run (self=<optimized out>) at application.c:199 > #16 0x000000000040a318 in application_main (argv=<optimized out>, argv_length1=1) at application.c:269 > #17 0x0000000000409750 in main (argc=<optimized out>, argv=<optimized out>) at application.c:278
If you can reproduce your problem, please comment here again.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days