Bug#974172: libmutter-7-0: Cannot unlock screen with Wayland on arm64, keybard and mouse unresponsive

2020-11-17 Thread Simon McVittie
Control: forwarded -1 https://gitlab.gnome.org/GNOME/mutter/-/issues/1536 On Mon, 16 Nov 2020 at 17:39:41 -0600, Evan McGinnis wrote: > I observed this issue as well and have bisected it. > 209b1ba383f59e1b398d3331d9fd9fcb7f0284a1 seems to be the culprit Thanks, I've sent this upstream (see link

Bug#974172: libmutter-7-0: Cannot unlock screen with Wayland on arm64, keybard and mouse unresponsive

2020-11-16 Thread Evan McGinnis
Hi Galí, Simon I observed this issue as well and have bisected it. https://salsa.debian.org/gnome-team/mutter/-/commit/209b1ba3 209b1ba383f59e1b398d3331d9fd9fcb7f0284a1 seems to be the culprit Anything before that commit functions properly on my aarch64 machine. PS. sorry for the resend--

Bug#974172: libmutter-7-0: Cannot unlock screen with Wayland on arm64, keybard and mouse unresponsive

2020-11-16 Thread Gali Drudis-Sole
On Fri, Nov 13, 2020 at 1:54 PM Simon McVittie wrote: > Control: retitle -1 libmutter-7-0: Cannot unlock screen with Wayland on > arm64, keybard and mouse unresponsive > > On Thu, 12 Nov 2020 at 00:20:03 +0100, Gali Drudis-Sole wrote: > > On Wed, 11 Nov, 2020 at 10:32, Simon McVittie wrote: > >

Bug#974172: libmutter-7-0: Cannot unlock screen with Wayland on arm64, keybard and mouse unresponsive

2020-11-13 Thread Simon McVittie
Control: retitle -1 libmutter-7-0: Cannot unlock screen with Wayland on arm64, keybard and mouse unresponsive On Thu, 12 Nov 2020 at 00:20:03 +0100, Gali Drudis-Sole wrote: > On Wed, 11 Nov, 2020 at 10:32, Simon McVittie wrote: > This works fine for me, and presumably other GNOME users, so