Bug 1766849 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(initially reported [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1725245#c20))

I had the firefox snap crash 3 times yesterday, while running it from the candidate channel (100.0-1) in a wayland session (Ubuntu 22.04). These crashes didn't trigger the crash reporter.
The last time I happened to be running it from a terminal, and I got this:

(firefox:80147): Gdk-WARNING **: 21:44:48.720: The program 'firefox' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue'.
  (Details: serial 980422 error_code 2 request_code 53 (core protocol) minor_code 0)
  (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.)

FWIW, I never saw this kind of crash when it was running natively under Wayland, for the past few months (it was only recently reverted to using xwayland because of bug 1725245).
Revision 1 by
on 
(initially reported [here](https://bugzilla.mozilla.org/show_bug.cgi?id=1725245#c20))

I had the firefox snap crash 3 times yesterday, while running it from the candidate channel (100.0-1) in a wayland session (Ubuntu 22.04). These crashes didn't trigger the crash reporter.
The last time I happened to be running it from a terminal, and I got this:

    (firefox:80147): Gdk-WARNING **: 21:44:48.720: The program 'firefox' received an X Window System error.
    This probably reflects a bug in the program.
    The error was 'BadValue'.
      (Details: serial 980422 error_code 2 request_code 53 (core protocol) minor_code 0)
      (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.)

FWIW, I never saw this kind of crash when it was running natively under Wayland, for the past few months (it was only recently reverted to using xwayland because of bug 1725245).

Back to Bug 1766849 Comment 0