[Desktop-packages] [Bug 1970917] Re: gnome-shell crashes with SIGABRT due to assertion failure "!window->monitor || g_list_find (meta_monitor_manager_get_logical_monitors (monitor_manager), window->mo

2022-10-03 Thread ThatFatPat 
Hi, I recently implemented an additional mode in gnome-remote-desktop
which disables the physical monitors and creates a virtual monitor, so
that no matter your host configuration, the client can view all windows
and in the appropriate resolution.

This bug prevents me from using this mode as approximately 20% of the
times a new RDP connection is initiated, gnome-shell crashes thus
destroying the user session.

I would be really glad to see this fixed, especially as a fix was
already released. Running my own tests, it seems that cherry-picking the
patch onto the current version of mutter passes all tests.

Is there anything I can do to expedite the process?

Thanks in advance!

-- 
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/1970917

Title:
  gnome-shell crashes with SIGABRT due to assertion failure
  "!window->monitor || g_list_find
  (meta_monitor_manager_get_logical_monitors (monitor_manager),
  window->monitor)" in meta_window_update_for_monitors_changed()

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

Bug description:
  gnome-shell crashes with SIGABRT due to assertion failure:

  "!window->monitor || g_list_find
  (meta_monitor_manager_get_logical_monitors (monitor_manager),
  window->monitor)"

  in meta_window_update_for_monitors_changed().

  However a bug in errors.ubuntu.com is hiding it. Sometimes it is
  visible on
  https://errors.ubuntu.com/problem/bc718fcc290d04f4e23c6246836d992f140e7058
  (when the last crash report was from jammy) and sometimes not
  (impish).

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1970917/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1990998] Re: gnome-shell crashes on connection from gnome-remote-desktop in EXTEND mode

2022-09-27 Thread ThatFatPat 
** Also affects: mutter (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  gnome-shell crashes on connection from gnome-remote-desktop in EXTEND
  mode

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  
  Hey all,
  I've encountered a bug in libmutter that crashes GNOME Shell when connecting 
via gnome-remote-desktop in EXTEND mode.

  gnome-shell[1500]: **
  gnome-shell[1500]: 
libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed:
 assertion failed: (!window->monitor || g_list_find 
(meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor))
  gnome-shell[1500]: Bail out! 
libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed:
 assertion failed: (!window->monitor || g_list_find 
(meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor))
  gnome-shell[1500]: GNOME Shell crashed with signal 6

  This statistically crashes the GNOME session on connection from RDP.
  This bug is addressed in 
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2554

  Steps to Reproduce:

  1. Setup Ubuntu machine on low resolution (1280x960)
  2. Setup gnome-remote-desktop to accept connections in 'extend' mode.
  3. Connect from xfreerdp with /dynamic-resolution and /w:, /h: set to a 
resolution much  larger than your current monitor (For example 3840x2160 on a 
1080p screen)
  4. Open multiple windows, shift them around, maximize some.
  5. Disconnect
  6. Reconnect.
  7. Session should crash, resulting in potential used data loss.

  
  NOTE: I couldn't reliably reproduce the bug. Sometimes restarting and trying 
again triggered it.

  Setup:

  lsb_release -a:
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  Codename: jammy

  apt-cache policy mutter:
  mutter:
Installed: 42.2-0ubuntu1
Candidate: 42.2-0ubuntu1
Version table:
   *** 42.2-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   42.0-3ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

  apt-cache policy gnome-shell:
  gnome-shell:
Installed: 42.4-0ubuntu0.22.04.1
Candidate: 42.4-0ubuntu0.22.04.1
Version table:
   *** 42.4-0ubuntu0.22.04.1 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   42.0-2ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages


  ```
  (gdb) bt full
  #0  __pthread_kill_implementation (no_tid=0, signo=6, 
threadid=139943778018752) at ./nptl/pthread_kill.c:44
  tid = 
  ret = 0
  pd = 0x7f47332d65c0

  old_mask = {__val = {2048, 139943866772608, 2064, 129, 
95, 139943865243713, 139943866772704, 0, 7, 139943865090602, 344544753768, 
2048, 94006337625088, 5680105379855955242, 143, 2096}}
  ret = 
  #1  __pthread_kill_internal (signo=6, threadid=139943778018752) at 
./nptl/pthread_kill.c:78
  #2  __GI___pthread_kill (threadid=139943778018752, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
  #3  0x7f47385a3476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
  ret = 
  #4  0x7f47385897f3 in __GI_abort () at ./stdlib/abort.c:79
  save_stage = 1

act = {__sigaction_handler = {sa_handler = 0xed,
  sa_sigaction = 0xed}, sa_mask = {__val = {237, 94006402588640,
  139943881008423, 94006314421680, 140725925571312, 32, 94006337054400,
  0, 6907377910888285440, 1, 18446744073709551488, 61, 214,
  140725925571408, 139943868561280, 139943868561280}}, sa_flags =
  945841363, sa_restorer = 0x557f8e53a6c0}

  sigs = {__val = {32, 139943866772608, 1322117968, 0, 
139943868561280, 6907377910888285440, 94006310750208, 18446744073709551488, 61, 
140725925571304, 237, 1, 94006337054400, 139943865246931, 94006337054400, 
139943880987991}}
  #5  0x7f47394b2b57 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #6  0x7f473950c6ff in g_assertion_message_expr () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #7  0x7f4738873856 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #8  0x7f4739505b10 in g_slist_foreach () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #9  0x7f473884b362 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
  #10 0x7f47395e2d2f in g_closure_invoke () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #11 0x7f47395feb76 in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #12 0x7f4739600554 in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  #13 0x7f47396007a3 in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0

[Desktop-packages] [Bug 1990998] [NEW] gnome-shell crashes on connection from gnome-remote-desktop in EXTEND mode

2022-09-27 Thread ThatFatPat 
Public bug reported:


Hey all,
I've encountered a bug in libmutter that crashes GNOME Shell when connecting 
via gnome-remote-desktop in EXTEND mode.

gnome-shell[1500]: **
gnome-shell[1500]: 
libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed:
 assertion failed: (!window->monitor || g_list_find 
(meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor))
gnome-shell[1500]: Bail out! 
libmutter:ERROR:../src/core/window.c:3730:meta_window_update_for_monitors_changed:
 assertion failed: (!window->monitor || g_list_find 
(meta_monitor_manager_get_logical_monitors (monitor_manager), window->monitor))
gnome-shell[1500]: GNOME Shell crashed with signal 6

This statistically crashes the GNOME session on connection from RDP.
This bug is addressed in 
https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2554

Steps to Reproduce:

1. Setup Ubuntu machine on low resolution (1280x960)
2. Setup gnome-remote-desktop to accept connections in 'extend' mode.
3. Connect from xfreerdp with /dynamic-resolution and /w:, /h: set to a 
resolution much  larger than your current monitor (For example 3840x2160 on a 
1080p screen)
4. Open multiple windows, shift them around, maximize some.
5. Disconnect
6. Reconnect.
7. Session should crash, resulting in potential used data loss.


NOTE: I couldn't reliably reproduce the bug. Sometimes restarting and trying 
again triggered it.

Setup:

lsb_release -a:
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename:   jammy

apt-cache policy mutter:
mutter:
  Installed: 42.2-0ubuntu1
  Candidate: 42.2-0ubuntu1
  Version table:
 *** 42.2-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 42.0-3ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

apt-cache policy gnome-shell:
gnome-shell:
  Installed: 42.4-0ubuntu0.22.04.1
  Candidate: 42.4-0ubuntu0.22.04.1
  Version table:
 *** 42.4-0ubuntu0.22.04.1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
 42.0-2ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages


```
(gdb) bt full
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139943778018752) 
at ./nptl/pthread_kill.c:44
tid = 
ret = 0
pd = 0x7f47332d65c0

old_mask = {__val = {2048, 139943866772608, 2064, 129, 95, 
139943865243713, 139943866772704, 0, 7, 139943865090602, 344544753768, 2048, 
94006337625088, 5680105379855955242, 143, 2096}}
ret = 
#1  __pthread_kill_internal (signo=6, threadid=139943778018752) at 
./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=139943778018752, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
#3  0x7f47385a3476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
ret = 
#4  0x7f47385897f3 in __GI_abort () at ./stdlib/abort.c:79
save_stage = 1

  act = {__sigaction_handler = {sa_handler = 0xed,
sa_sigaction = 0xed}, sa_mask = {__val = {237, 94006402588640,
139943881008423, 94006314421680, 140725925571312, 32, 94006337054400, 0,
6907377910888285440, 1, 18446744073709551488, 61, 214, 140725925571408,
139943868561280, 139943868561280}}, sa_flags = 945841363, sa_restorer =
0x557f8e53a6c0}

sigs = {__val = {32, 139943866772608, 1322117968, 0, 
139943868561280, 6907377910888285440, 94006310750208, 18446744073709551488, 61, 
140725925571304, 237, 1, 94006337054400, 139943865246931, 94006337054400, 
139943880987991}}
#5  0x7f47394b2b57 in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x7f473950c6ff in g_assertion_message_expr () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#7  0x7f4738873856 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#8  0x7f4739505b10 in g_slist_foreach () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#9  0x7f473884b362 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#10 0x7f47395e2d2f in g_closure_invoke () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x7f47395feb76 in  () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#12 0x7f4739600554 in g_signal_emit_valist () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#13 0x7f47396007a3 in g_signal_emit () at 
/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#14 0x7f47388088d0 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#15 0x7f473880fead in meta_monitor_manager_rebuild () at 
/lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7f47388eb789 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7f4738800bc0 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7f47388060b7 in meta_monitor_manager_ensure_configured () at 
/lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7f47388a6f87 in  () at /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7f47388acdc7 in  () at