[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_find_wind
Thanks, those stack traces are exactly what we needed. I can't find any other reports of those crashes, but that's likely just because nobody else had debugged it with GDK_SYNCHRONIZE yet... Next please report the bug to the developers at https://gitlab.gnome.org/GNOME/gtk/-/issues and remember to attach the full stack traces from comments #25 and #28. ** Summary changed: - GDK/GTK app crash when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_find_window) + GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_find_window) ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => New ** Changed in: thunar (Ubuntu) Status: Incomplete => New ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Medium ** Changed in: gtk+3.0 (Ubuntu) Status: New => Triaged ** Changed in: thunar (Ubuntu) Importance: Undecided => Medium ** No longer affects: thunar (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1911036 Title: GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_find_window) Status in gtk+3.0 package in Ubuntu: Triaged Bug description: For many months now, whenever any mouse drag is attempted in an application using the gtk tool kit, the application immediately crashes. I've noticed this at least in Firefox and thunar. It also occurs when displaying these applications from a Virtualbox machine or from another server running something other than Ubuntu. The VM was running CentOS 8 and the remote server was running Mageia. Both Firefox and thunar run fine with Mageia's Xorg. It seems like the issue may be with the Xorg server on Ubuntu. I tried setting the GDK_SYNCHRONIZE variable to various settings but was unable to produce further debug output. The only other debug output I was able to gather is when running thunar with the --gtk- debug parameter (attached). I also tried running thunar with GDB but without recompiling it, it doesn't produce much information other than it's stopping in glib. Let me know what other information I can provide. (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ExceptionHandler::GenerateDump cloned child 110611 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. [1]+ Trace/breakpoint trap (core dumped) firefox (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) $ ldd /bin/thunar linux-vdso.so.1 (0x7ffc0c8cc000) libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 (0x7fdbb548c000) libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 (0x7fdbb544f000) libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 (0x7fdbb5442000) libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 (0x7fdbb5437000) libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000) libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000) libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 (0x7fdbb53f3000) libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 (0x7fdbb4c42000) libg
[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_find_wind
** Summary changed: - GDK/GTK app crash when performing drag operation + GDK/GTK app crash when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_find_window) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1911036 Title: GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_find_window) Status in gtk+3.0 package in Ubuntu: Triaged Bug description: For many months now, whenever any mouse drag is attempted in an application using the gtk tool kit, the application immediately crashes. I've noticed this at least in Firefox and thunar. It also occurs when displaying these applications from a Virtualbox machine or from another server running something other than Ubuntu. The VM was running CentOS 8 and the remote server was running Mageia. Both Firefox and thunar run fine with Mageia's Xorg. It seems like the issue may be with the Xorg server on Ubuntu. I tried setting the GDK_SYNCHRONIZE variable to various settings but was unable to produce further debug output. The only other debug output I was able to gather is when running thunar with the --gtk- debug parameter (attached). I also tried running thunar with GDB but without recompiling it, it doesn't produce much information other than it's stopping in glib. Let me know what other information I can provide. (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) ExceptionHandler::GenerateDump cloned child 110611 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. Exiting due to channel error. [1]+ Trace/breakpoint trap (core dumped) firefox (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 8) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Trace/breakpoint trap (core dumped) $ ldd /bin/thunar linux-vdso.so.1 (0x7ffc0c8cc000) libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 (0x7fdbb548c000) libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 (0x7fdbb544f000) libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 (0x7fdbb5442000) libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 (0x7fdbb5437000) libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000) libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000) libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 (0x7fdbb53f3000) libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 (0x7fdbb4c42000) libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 (0x7fdbb4b3d000) libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x7fdbb4b13000) libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 (0x7fdbb49f) libgdk_pixbuf-2.0.so.0 => /lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000) libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 (0x7fdbb49b4000) libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 (0x7fdbb4996000) libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x7fdbb4947000) libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x7fdbb4766000) libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7fdbb4706000) libglib-2.0.so.0 => /lib/x86_64-li
