Thanks for the bug report. I can see there's a NULL buffer pointer being
used:
#6 0x00007fd7f5397e21 in meta_drm_buffer_ensure_fb_id (error=0x7ffdfdc4e138,
buffer=0x0) at ../src/backends/native/meta-drm-buffer.c:75
#7 meta_onscreen_native_swap_buffers_with_damage (onscreen=<optimized out>,
rectangles=0x7ffdfdc4e330, n_rectangles=0, frame_info=0x60f29e6f4560,
user_data=0x60f29e6f1da0) at ../src/backends/native/meta-onscreen-native.c:1491
which seems most likely related to secondary GPU support.
** Tags added: noble
** Changed in: mutter (Ubuntu)
Assignee: (unassigned) => Daniel van Vugt (vanvugt)
** Changed in: mutter (Ubuntu)
Importance: Undecided => Medium
** Changed in: mutter (Ubuntu)
Status: Incomplete => Triaged
** Tags added: hybrid multigpu nvidia wayland wayland-session
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2142741
Title:
Mutter crash observed with wayland + multi-vgpu at launch
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2142741/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
