Thank you for reporting this bug to Ubuntu.
Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in.


** Changed in: xwayland (Ubuntu)
       Status: Confirmed => Won't Fix

** Changed in: xwayland (Ubuntu Groovy)
       Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1909678

Title:
  Ubuntu 20.10 Desktop on Pi4B - screen-freeze after idling at login-
  screen

Status in linux-raspi package in Ubuntu:
  Invalid
Status in xwayland package in Ubuntu:
  Won't Fix
Status in linux-raspi source package in Groovy:
  Invalid
Status in xwayland source package in Groovy:
  Won't Fix
Status in linux-raspi source package in Hirsute:
  Invalid
Status in xwayland source package in Hirsute:
  Invalid

Bug description:
  It is the same bug already described here:
  https://askubuntu.com/questions/1300689/problem-with-usb-keyboard-and-
  mouse-on-raspberry-pi-4b-with-ubuntu-20-10

  My system:
  Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 
2020 aarch64 aarch64 aarch64 GNU/Linux

  I'm using
  - Raspberry Pi4B 8GB
  - Logitech MK120 Keyboard and Mouse (wired).

  How I could reproduce the mentioned crash:
  - Boot and wait (don't touch mouse/keyboard) at login-screen for five minutes
  - After five minutes, screen will turn black
  - If you move the mouse then, screen will be back again but frozen 
(mouse/keyboard not working).

  - restarting gdm.service via ssh is possible: sudo systemctl restart 
gdm.service
  - restarting it via Alt+SysRq+k is possible, but login after that fails for 
some reason

  
  Workaround:
  In /etc/gdm3/custom.conf, change #WaylandEnable=false to WaylandEnable=false
  as described here: 
https://unix.stackexchange.com/questions/460041/xwayland-crashes-frequently

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1909678/+subscriptions


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

Reply via email to