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 789054 - Firefox crashes @gdk_window_begin_move_drag() on WM without _NET_WM_MOVERESIZE
Firefox crashes @gdk_window_begin_move_drag() on WM without _NET_WM_MOVERESIZE
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Backend: X11
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
: 791517 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2017-10-16 12:38 UTC by Martin Stransky
Modified: 2017-12-29 17:32 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Simple testcase (804 bytes, text/x-csrc)
2017-10-16 12:38 UTC, Martin Stransky 		Details

Description Martin Stransky 2017-10-16 12:38:24 UTC 
Created attachment 361671 [details]
Simple testcase

Due to bug at emulate_move_drag() in gdk_x11_window_begin_move_drag() Firefox crashes on WM without _NET_WM_MOVERESIZE set. You just need to call gdk_window_begin_move_drag() twice.

I can reproduce that on icewm/Fedora 26:
Gdk:ERROR:gdkwindow-x11.c:5165:create_moveresize_window: assertion failed: (mv_resize->moveresize_emulation_window == NULL)

backtrace:

+ Trace 238067

  • #2 g_assertion_message
  • #3 g_assertion_message_expr
    at gtestutils.c line 2456
  • #4 create_moveresize_window
    at gdkwindow-x11.c line 5165
  • #5 emulate_move_drag
    at gdkwindow-x11.c line 5325
  • #6 gdk_x11_window_begin_move_drag
    at gdkwindow-x11.c line 5388
  • #7 gdk_window_begin_move_drag_for_device
    at gdkwindow.c line 11220
  • #8 gdk_window_begin_move_drag
    at gdkwindow.c line 11250 

Mozilla bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1186967
Comment 1 Matthias Clasen 2017-12-15 20:33:17 UTC 
*** Bug 791517 has been marked as a duplicate of this bug. ***
Comment 2 Daniel Boles 2017-12-19 15:49:39 UTC 
Is this fixed by https://git.gnome.org/browse/gtk+/commit/?h=gtk-3-22&id=e834a2b089085c1c63a4e4b6e06fd84f48cc030e or was that just a partial or temporary fix?
Comment 3 Matthias Clasen 2017-12-29 17:32:31 UTC 
should be fixed by that, indeed. please reopen if not