Xwayland crashed with SIGABRT in OsAbort() from ... from FatalError("wl_surface@429: error 2: Failed to create a texture for surface 429: Failed to create texture 2d due to size/format constraints\n")

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1745799, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

I do not think this is a duplicate of bug #1745799.
At this comment I will try to give a code to solve this bug.
My symbol Xwaylnd-crash shows the next trace:
 #6 0x0062b600 in FatalError (f=0x63704e "%s") at ../../../../os/log.c:1015
         args = 0xbf9c7844 "\\x\234\277"
         args2 = 0xbf9c7844 "\\x\234\277"
         beenhere = 1
 #7 0x004b6296 in xwl_log_handler (format=0xb7dc71ea "%s@%u: error %d: %s\n", args=0xbf9c7994 "\027uܷ\255\001") at ../../../../../hw/xwayland/xwayland.c:1137
         msg = "wl_surface@429: error 2: Failed to create a texture for surface 429: Failed to create texture 2d due to size/format constraints\n", '\000' <repeats 127 times>
 #8 0xb7dc5fef in wl_log (fmt=0xb7dc71ea "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404

Problem can be solved by using slicing at shm_buffer_attach() at src/wayland/meta-wayland-buffer.c, if size of texture is too large for graphics card. Code for freeing the bitmap is now positioned after the if.

This results into the following code:
  texture = COGL_TEXTURE (cogl_texture_2d_new_from_bitmap (bitmap));
  cogl_texture_set_components (COGL_TEXTURE (texture), components);

  if (!cogl_texture_allocate (COGL_TEXTURE (texture), error))
    {
      g_clear_pointer (&texture, cogl_object_unref);
      texture = COGL_TEXTURE (cogl_texture_2d_sliced_new_from_bitmap (bitmap, COGL_TEXTURE_MAX_WASTE));
      cogl_texture_set_components (COGL_TEXTURE (texture), components);
      if (!cogl_texture_allocate (COGL_TEXTURE (texture), error))
        g_clear_pointer (&texture, cogl_object_unref);
    }

  wl_shm_buffer_end_access (shm_buffer);

  cogl_object_unref (bitmap);

  buffer->texture = texture;

This code is working and makes it possible to login with wayland with dual screen without any monitors.xml-config on small/old graphic cards.

Slicing is causing next message:
Oct 13 15:51:36 Gert2 gnome-shell[1994]: Skipping layers 1..n of your pipeline since the first layer is sliced. We don't currently support any multi-texturing with sliced textures but assume layer 0 is the most important to keep

Sorry,
Code was not quite complete.
It misses freeing the error.
New version:
 texture = COGL_TEXTURE (cogl_texture_2d_new_from_bitmap (bitmap));
  cogl_texture_set_components (COGL_TEXTURE (texture), components);

  if (!cogl_texture_allocate (COGL_TEXTURE (texture), error))
    {
      g_clear_pointer (&texture, cogl_object_unref);
      cogl_error_free (*error);
      *error = NULL;
      texture = COGL_TEXTURE (cogl_texture_2d_sliced_new_from_bitmap (bitmap, COGL_TEXTURE_MAX_WASTE));
      cogl_texture_set_components (COGL_TEXTURE (texture), components);
      if (!cogl_texture_allocate (COGL_TEXTURE (texture), error))
        g_clear_pointer (&texture, cogl_object_unref);
    }

  wl_shm_buffer_end_access (shm_buffer);

  cogl_object_unref (bitmap);

  buffer->texture = texture;

As stated above this bug report is not a duplicate and contains working code to solve the bug.
Using this code doesn ot give any risk to the main stream of the code, it only handles an exception.
I thought it might be a pleasure to get a solution for a problem.
PLease do something with it.

This is not a duplicate. It is a crash at OsAbort, but that is the only coincidence with #1745799.
The cause is different.
It contains a working solution.
PLease do something with it and do not mark it as duplicate.

Because this bug no longer is marked as duplicate of #1745799, I now add the bug-fix (tested by me for a long time) to this bug.

The attachment "Patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

Gert,

Could you please propose your patch to the mutter developers directly?

  https://gitlab.gnome.org/GNOME/mutter/merge_requests

Or if that's too much work, just start by reporting this bug to the mutter developers here:

  https://gitlab.gnome.org/GNOME/mutter/issues

Issue https://gitlab.gnome.org/GNOME/mutter/issues/453 is added to mutter

Fixed in mutter 3.32.0