[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

2023-01-16 Thread Daniel van Vugt
mutter (43.2-4ubuntu1) lunar; urgency=medium


** Changed in: mutter (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1994519

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #18 0x7f920aea42a0 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #19 

[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

2022-11-23 Thread Łukasz Spintzyk
Hi Daniel,
Do you know when this updated 43.1 mutter may land in Ubuntu kinetic?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1994519

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #18 0x7f920aea42a0 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #19 0x7f920aea8694 in  () at 

[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

2022-11-08 Thread Łukasz Spintzyk
mutter-43.1 was released. When approximately it is expected to be
available in Ubuntu packages?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1994519

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #18 0x7f920aea42a0 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #19 0x7f920aea8694 in  () at 

[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

2022-11-02 Thread Daniel van Vugt
OK then we are only waiting for version 43.1 to reach kinetic.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1994519

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #18 0x7f920aea42a0 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #19 0x7f920aea8694 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  

[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

2022-11-02 Thread Łukasz Spintzyk
gnome-42 branch does not reproduce this bug.
This is happening on main branch which has 43.0 version. There is no gnome-43 
branch yet.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1994519

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #18 0x7f920aea42a0 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #19 

[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

2022-11-02 Thread Daniel van Vugt
I suggest the best way to get the fix into jammy is to propose a cherry
pick upstream to the 'gnome-42' branch (hoping for version 42.7)

** Changed in: mutter (Ubuntu)
   Status: In Progress => Fix Committed

** Tags added: fixed-in-mutter-43.1 fixed-upstream

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1994519

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Committed

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  

[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

2022-11-02 Thread Łukasz Spintzyk
Hi,

I am DisplayLink developer.
This is already fixed and merged in here:
https://gitlab.gnome.org/GNOME/mutter/-/commit/c57a500ccbd16694e7cbb3408b1da5dc8efb44ba

Can you please cherry-pick that fix?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1994519

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #18 0x7f920aea42a0 

[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

2022-11-01 Thread Bug Watch Updater
** Changed in: mutter
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1994519

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  Fix Released
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #18 0x7f920aea42a0 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #19 0x7f920aea8694 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #20 

[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

2022-11-01 Thread Daniel van Vugt
** Changed in: mutter (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1994519

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  In Progress

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #18 0x7f920aea42a0 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #19 0x7f920aea8694 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #20 

[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

2022-10-31 Thread Bug Watch Updater
** Changed in: mutter
   Status: Unknown => New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1994519

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #18 0x7f920aea42a0 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #19 0x7f920aea8694 in  () at /lib/x86_64-linux-gnu/libwayland-server.so.0
  #20 0x7f920aea70fa in 

[Desktop-packages] [Bug 1994519] Re: DisplayLink display is black on plug-in and mutter crash after moving cursor on DisplayLink display.

2022-10-31 Thread Daniel van Vugt
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2481
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2481

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1994519

Title:
  DisplayLink display is black on plug-in and mutter crash after moving
  cursor on DisplayLink display.

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  New

Bug description:
  
  This is recent regression with reproduction rate 100%.
  This is regression mutter-43, Ubuntu 22.04 works fine.

  Bug is raised on Gnome/mutter:
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2481
  Fix is under review:
  https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2676

  
  ### Steps to reproduce

  1. Login
  2. Attach DisplayLink device with display connected
  3. Notice that display is visible in Display Preferences but display stays 
blank.
  4. Move cursor over DisplayLink display.
  5. Mutter crashes.

  
  ### What happened

  Mutter crashes, user is asked to log-in again.

  ### What did you expect to happen

  Mutter does not crash.

  ### Relevant logs, screenshots, screencasts etc.
  Crash in line:
  
https://gitlab.gnome.org/GNOME/mutter/-/blob/main/src/backends/native/meta-renderer-native.c#L226

  Crash backtrace:
  ```
  Thread 1 "gnome-shell" received signal SIGSEGV, Segmentation fault.
  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) at 
../src/backends/native/meta-renderer-native.c:204
  204   render_device = renderer_gpu_data->render_device;
  (gdb) bt
  #0  0x7f9209c35329 in meta_gbm_device_from_gpu (gpu_kms=0x55eb13bc9e00) 
at ../src/backends/native/meta-renderer-native.c:204
  #1  0x7f9209c06674 in create_cursor_drm_buffer (gpu_kms=0x55eb13bc9e00, 
device_file=0x55eb15eaa860, pixels=0x7f91b4bb9700 "", width=24, height=24, 
stride=96, cursor_width=64, cursor_height=64, format=875713089, 
error=0x7ffda9443108) at 
../src/backends/native/meta-cursor-renderer-native.c:1329
  #2  0x7f9209c068b9 in load_cursor_sprite_gbm_buffer_for_gpu 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
pixels=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, 
gbm_format=875713089) at 
../src/backends/native/meta-cursor-renderer-native.c:1399
  #3  0x7f9209c06f98 in load_scaled_and_transformed_cursor_sprite 
(native=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00, 
relative_scale=1, relative_transform=META_MONITOR_TRANSFORM_NORMAL, 
data=0x7f91b4bb9700 "", width=24, height=24, rowstride=96, gbm_format=875713089)
  at ../src/backends/native/meta-cursor-renderer-native.c:1574
  #4  0x7f9209c07293 in realize_cursor_sprite_from_wl_buffer_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, 
sprite_wayland=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1670
  #5  0x7f9209c07788 in realize_cursor_sprite_for_gpu 
(renderer=0x55eb1617f580, gpu_kms=0x55eb13bc9e00, cursor_sprite=0x55eb1918fb00) 
at ../src/backends/native/meta-cursor-renderer-native.c:1836
  #6  0x7f9209c077cf in realize_cursor_sprite (renderer=0x55eb1617f580, 
cursor_sprite=0x55eb1918fb00, gpus=0x55eb16345a20 = {...}) at 
../src/backends/native/meta-cursor-renderer-native.c:1854
  #7  0x7f9209c05dd4 in meta_cursor_renderer_native_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/native/meta-cursor-renderer-native.c:1087
  #8  0x7f9209aac8fa in meta_cursor_renderer_update_cursor 
(renderer=0x55eb1617f580, cursor_sprite=0x55eb1918fb00) at 
../src/backends/meta-cursor-renderer.c:413
  #9  0x7f9209aaca07 in meta_cursor_renderer_force_update 
(renderer=0x55eb1617f580) at ../src/backends/meta-cursor-renderer.c:448
  #10 0x7f9209bc4dc6 in update_cursor_sprite_texture 
(cursor_surface=0x55eb1924d880) at 
../src/wayland/meta-wayland-cursor-surface.c:79
  #11 0x7f9209bc512a in meta_wayland_cursor_surface_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-cursor-surface.c:179
  #12 0x7f9209be3774 in meta_wayland_surface_role_apply_state 
(surface_role=0x55eb1924d880, pending=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:1938
  #13 0x7f9209be14b6 in meta_wayland_surface_apply_state 
(surface=0x55eb16305e60, state=0x55eb1918d410) at 
../src/wayland/meta-wayland-surface.c:882
  #14 0x7f9209be19c7 in meta_wayland_surface_commit 
(surface=0x55eb16305e60) at ../src/wayland/meta-wayland-surface.c:1038
  #15 0x7f9209be1e9f in wl_surface_commit (client=0x55eb191d7150, 
resource=0x55eb191f1eb0) at ../src/wayland/meta-wayland-surface.c:1191
  #16 0x7f9209d1ae2e in  () at /lib/x86_64-linux-gnu/libffi.so.8
  #17 0x7f9209d17493 in  () at