After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 684938 - gedit and evince hits BadWindow XErrors when run from different "contexts" with GTK 3.6
gedit and evince hits BadWindow XErrors when run from different "contexts" wi...
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Backend: X11
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2012-09-27 09:45 UTC by Sebastien Bacher
Modified: 2012-09-27 12:51 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sebastien Bacher 2012-09-27 09:45:21 UTC 
The issue has been reported on https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1047431

Using GNOME 3.6

"I can reproduce the bug by following these steps:

1) open a file (in gedit) from a command line
2) open a file (in gedit) from nautilus.""

Stacktrace:
https://launchpadlibrarian.net/115064882/Stacktrace.txt

"#0  g_logv (log_domain=0x7fe53cb82f06 "Gdk", log_level=G_LOG_LEVEL_ERROR, format=<optimized out>, args=args@entry=0x7fff961060b8) at /build/buildd/glib2.0-2.33.12/./glib/gmessages.c:974
        domain = 0x0
        data = <optimized out>
        depth = <optimized out>
        log_func = 0x7fe53afb05c0 <g_log_default_handler>
        domain_fatal_mask = <optimized out>
        masquerade_fatal = <optimized out>
        test_level = <optimized out>
        was_fatal = <optimized out>
        was_recursion = <optimized out>
        msg = 0x2b40880 "The program 'gedit' received an X Window System error.\nThis probably reflects a bug in the program.\nThe error was 'BadWindow (invalid Window parameter)'.\n  (Details: serial 246 error_code 3 request_co"...
        msg_alloc = 0x2b40880 "The program 'gedit' received an X Window System error.\nThis probably reflects a bug in the program.\nThe error was 'BadWindow (invalid Window parameter)'.\n  (Details: serial 246 error_code 3 request_co"...
        i = 2

+ Trace 230918

  • #1 g_log
    at /build/buildd/glib2.0-2.33.12/./glib/gmessages.c line 1003
  • #2 _gdk_x11_display_error_event
    at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkdisplay-x11.c line 2417
  • #3 gdk_x_error
    at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkmain-x11.c line 303
  • #4 gdk_x_error
    at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkmain-x11.c line 266
  • #5 _XError
    at ../../src/XlibInt.c line 1583
  • #6 handle_error
    at ../../src/xcb_io.c line 212
  • #7 handle_response
    at ../../src/xcb_io.c line 324
  • #8 _XReply
    at ../../src/xcb_io.c line 626
  • #9 XInternAtom
    at ../../src/IntAtom.c line 181
  • #10 gdk_x11_atom_to_xatom_for_display
    at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkproperty-x11.c line 244
  • #11 gdk_x11_atom_to_xatom_for_display
    at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkproperty-x11.c line 221
  • #12 get_net_supporting_wm_check
    at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkscreen-x11.c line 1284
  • #13 fetch_net_wm_check_window
    at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkscreen-x11.c line 1321
  • #14 gdk_x11_screen_supports_net_wm_hint
    at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkscreen-x11.c line 1402
  • #15 gdk_x11_window_set_user_time
    at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkwindow-x11.c line 3078
  • #16 setup_toplevel_window
    at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkwindow-x11.c line 697
  • #17 _gdk_x11_display_create_window_impl
    at /build/buildd/gtk+3.0-3.5.16/./gdk/x11/gdkwindow-x11.c line 844
  • #18 gdk_window_new
    at /build/buildd/gtk+3.0-3.5.16/./gdk/gdkwindow.c line 1490 






Comment 1


Sebastien Bacher





          2012-09-27 09:47:03 UTC
        



it doesn't happen if gedit is run with "GDK_SYNCHRONIZE=1 gedit"

the issue happens under wmaker as well so it's not wm dependant






Comment 2


Sebastien Bacher





          2012-09-27 09:51:29 UTC
        



looking to when the reports started it seems the issue started with gtk+ 3.5.16