Ubuntu Desktop on Raspberry Pi Feedback

I’m experiencing very hard mouse (usb) lag after latest updates. Please fix this ASAP. It’s not working old fix with cmdline mousepoll

Running Ubuntu Desktop 20.10 on Raspberry Pi 4B 8GB, i have problems with freezes.

First, I can reproduce this type of freeze. I’m using Logitech MK120 Keyboard and Mouse (wired).

The bigger problem for me are such freezes when I’m logged in. It happens in both of my desktops, ubuntu and lxqt. After 1 or 2 hours (often during CPU/GPU-heavy work), the system freezes, which means:

  • Screen freezes (just shows the same picture. mouse-curser not moving, keyboard not working)
  • Keyboard not responding (e.g. Num-LED not changing when pressing Num)
  • Changing to another tty via e.g. Ctrl+Alt+F3 is not working anymore
  • BUT: System in the background still works. I can still hear audio (of a movie for example). Other tasks like ffmpeg-downloads are still working.

I added kernel.sysrq = 1 in /etc/sysctl.d/99-sysctl.conf and tried several things during such freezes.

During the login-screen-freeze, Alt+SysRq+k does something. I can use mouse and keyboard again and try to login. But if I do that via lxqt-desktop, it shows the desktop for a second and then brings back the login-screen (where I suddenly only can choose ubuntu-desktop). Login then leads to a black screen with blinking white dash. Alt+SysRq+k again brings me back to the start with a working login-screen and all available desktops. Login then works.

During a freeze when already working in a desktop-environment, Alt+SysRq+k isn’t changing much. I can hear the audio stopping. But the system is “too frozen” to be able to kill x-server. I also tried killing it via ssh - no chance. Alt+SysRq+reisub works to do a Pi-restart.
These freezes occur during typing, during mouse-clicking, but also when doing nothing with mouse and keyboard (like watching a video).

A journalctl-log of the freeze (occured at 00:08:something when typing with my keyboard) during ubuntu-desktop session is given here (I tried Alt+SysRq+k at 00:10:something without success):


[...]
Dez 26 00:07:31 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null
                                                     _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28
                                                     vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14
Dez 26 00:07:36 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null
                                                     _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28
                                                     vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14
Dez 26 00:07:41 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null
                                                     _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28
                                                     vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14
Dez 26 00:07:46 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null
                                                     _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28
                                                     vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14
Dez 26 00:07:48 myRaspi dbus-daemon[4131]: [session uid=1000 pid=4131] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.2' (uid=1000 pid=4128 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
Dez 26 00:07:48 myRaspi systemd[4119]: Starting Tracker metadata database store and lookup manager...
Dez 26 00:07:48 myRaspi dbus-daemon[4131]: [session uid=1000 pid=4131] Successfully activated service 'org.freedesktop.Tracker1'
Dez 26 00:07:48 myRaspi systemd[4119]: Started Tracker metadata database store and lookup manager.
Dez 26 00:07:49 myRaspi dbus-daemon[4131]: [session uid=1000 pid=4131] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.2' (uid=1000 pid=4128 comm="/usr/libexec/tracker-miner-fs " label="unconfined")
Dez 26 00:07:49 myRaspi systemd[4119]: Starting Tracker metadata extractor...
Dez 26 00:07:49 myRaspi tracker-extract[179165]: Set scheduler policy to SCHED_IDLE
Dez 26 00:07:49 myRaspi tracker-extract[179165]: Setting priority nice level to 19
Dez 26 00:07:49 myRaspi dbus-daemon[4131]: [session uid=1000 pid=4131] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract'
Dez 26 00:07:49 myRaspi systemd[4119]: Started Tracker metadata extractor.
Dez 26 00:07:51 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null
                                                     _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28
                                                     vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14
Dez 26 00:08:00 myRaspi systemd[4119]: tracker-extract.service: Succeeded.
Dez 26 00:08:01 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null
                                                     _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28
                                                     vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14
Dez 26 00:08:06 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null
                                                     _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28
                                                     vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14
Dez 26 00:08:11 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null
                                                     _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28
                                                     vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14
Dez 26 00:08:16 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null
                                                     _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28
                                                     vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14
Dez 26 00:08:20 myRaspi tracker-store[179156]: OK
Dez 26 00:08:20 myRaspi systemd[4119]: tracker-store.service: Succeeded.
Dez 26 00:08:21 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null
                                                     _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28
                                                     vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14
Dez 26 00:08:22 myRaspi /usr/libexec/gdm-x-session[165062]: (EE) event1  - Logitech USB Keyboard: client bug: event processing lagging behind by 13ms, your system is too slow
Dez 26 00:08:23 myRaspi /usr/libexec/gdm-x-session[165062]: (EE) event1  - Logitech USB Keyboard: client bug: event processing lagging behind by 22ms, your system is too slow
Dez 26 00:10:02 myRaspi rsyslogd[823]: [origin software="rsyslogd" swVersion="8.2006.0" x-pid="823" x-info="https://www.rsyslog.com"] rsyslogd was HUPed
Dez 26 00:10:35 myRaspi kernel: INFO: task Xorg:165062 blocked for more than 120 seconds.
Dez 26 00:10:35 myRaspi kernel:       Tainted: G         C  E     5.8.0-1010-raspi #13-Ubuntu
Dez 26 00:10:35 myRaspi kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dez 26 00:10:35 myRaspi kernel: Xorg            D    0 165062 165060 0x00000001
Dez 26 00:10:35 myRaspi kernel: Call trace:
Dez 26 00:10:35 myRaspi kernel:  __switch_to+0xfc/0x12c
Dez 26 00:10:35 myRaspi kernel:  __schedule+0x2a8/0x72c
Dez 26 00:10:35 myRaspi kernel:  schedule+0x84/0x120
Dez 26 00:10:35 myRaspi kernel:  schedule_timeout+0xc8/0x100
Dez 26 00:10:35 myRaspi kernel:  wait_for_completion+0x8c/0x12c
Dez 26 00:10:35 myRaspi kernel:  __flush_work.isra.0+0x80/0xa0
Dez 26 00:10:35 myRaspi kernel:  __cancel_work_timer+0xcc/0x1e0
Dez 26 00:10:35 myRaspi kernel:  cancel_delayed_work_sync+0x20/0x30
Dez 26 00:10:35 myRaspi kernel:  v3d_clock_up_get+0x58/0xa0 [v3d]
Dez 26 00:10:35 myRaspi kernel:  v3d_job_init+0xc4/0xe0 [v3d]
Dez 26 00:10:35 myRaspi kernel:  v3d_submit_cl_ioctl+0xac/0x740 [v3d]
Dez 26 00:10:35 myRaspi kernel:  drm_ioctl_kernel+0xd0/0x120 [drm]
Dez 26 00:10:35 myRaspi kernel:  drm_ioctl+0x1e8/0x460 [drm]
Dez 26 00:10:35 myRaspi kernel:  ksys_ioctl+0xb4/0xf4
Dez 26 00:10:35 myRaspi kernel:  __arm64_sys_ioctl+0x2c/0xbc
Dez 26 00:10:35 myRaspi kernel:  el0_svc_common.constprop.0+0x84/0x200
Dez 26 00:10:35 myRaspi kernel:  do_el0_svc+0x30/0xa0
Dez 26 00:10:35 myRaspi kernel:  el0_svc+0x18/0x50
Dez 26 00:10:35 myRaspi kernel:  el0_sync_handler+0x98/0x354
Dez 26 00:10:35 myRaspi kernel:  el0_sync+0x17c/0x180
Dez 26 00:10:35 myRaspi kernel: INFO: task kworker/1:1:171257 blocked for more than 120 seconds.
Dez 26 00:10:35 myRaspi kernel:       Tainted: G         C  E     5.8.0-1010-raspi #13-Ubuntu
Dez 26 00:10:35 myRaspi kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dez 26 00:10:35 myRaspi kernel: kworker/1:1     D    0 171257      2 0x00000028
Dez 26 00:10:35 myRaspi kernel: Workqueue: events dbs_work_handler
Dez 26 00:10:35 myRaspi kernel: Call trace:
Dez 26 00:10:35 myRaspi kernel:  __switch_to+0xfc/0x12c
Dez 26 00:10:35 myRaspi kernel:  __schedule+0x2a8/0x72c
Dez 26 00:10:35 myRaspi kernel:  schedule+0x84/0x120
Dez 26 00:10:35 myRaspi kernel:  schedule_timeout+0x88/0x100
Dez 26 00:10:35 myRaspi kernel:  wait_for_completion_timeout+0x8c/0x110
Dez 26 00:10:35 myRaspi kernel:  mbox_send_message+0xac/0x130
Dez 26 00:10:35 myRaspi kernel:  rpi_firmware_transaction+0x6c/0x110
Dez 26 00:10:35 myRaspi kernel:  rpi_firmware_property_list+0xc4/0x184
Dez 26 00:10:35 myRaspi kernel:  rpi_firmware_property+0x7c/0x120
Dez 26 00:10:35 myRaspi kernel:  raspberrypi_fw_get_rate+0x50/0x8c
Dez 26 00:10:35 myRaspi kernel:  clk_recalc+0x40/0xac
Dez 26 00:10:35 myRaspi kernel:  clk_change_rate+0xf0/0x520
Dez 26 00:10:35 myRaspi kernel:  clk_core_set_rate_nolock.part.0+0xe0/0xf0
Dez 26 00:10:35 myRaspi kernel:  clk_core_set_rate_nolock+0xa0/0x200
Dez 26 00:10:35 myRaspi kernel:  clk_set_rate+0x44/0x18c
Dez 26 00:10:35 myRaspi kernel:  dev_pm_opp_set_rate+0x4b0/0x620
Dez 26 00:10:35 myRaspi kernel:  set_target+0x4c/0x94
Dez 26 00:10:35 myRaspi kernel:  __target_index+0xd0/0x1e4
Dez 26 00:10:35 myRaspi kernel:  __cpufreq_driver_target+0x108/0x13c
Dez 26 00:10:35 myRaspi kernel:  od_update+0xe8/0x130
Dez 26 00:10:35 myRaspi kernel:  od_dbs_update+0x54/0xb4
Dez 26 00:10:35 myRaspi kernel:  dbs_work_handler+0x4c/0x8c
Dez 26 00:10:35 myRaspi kernel:  process_one_work+0x1d8/0x4a0
Dez 26 00:10:35 myRaspi kernel:  worker_thread+0x74/0x3c0
Dez 26 00:10:35 myRaspi kernel:  kthread+0x138/0x14c
Dez 26 00:10:35 myRaspi kernel:  ret_from_fork+0x10/0x34
Dez 26 00:10:35 myRaspi kernel: INFO: task kworker/0:1:178168 blocked for more than 120 seconds.
Dez 26 00:10:35 myRaspi kernel:       Tainted: G         C  E     5.8.0-1010-raspi #13-Ubuntu
Dez 26 00:10:35 myRaspi kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Dez 26 00:10:35 myRaspi kernel: kworker/0:1     D    0 178168      2 0x00000028
Dez 26 00:10:35 myRaspi kernel: Workqueue: events v3d_clock_down_work [v3d]
[...]

if you are using a proper power supply of at least 3A (the pi4 needs a lot more current than all former pi’s) and are sure it isnt a power issue (note that additional USB hubs like the one in your KBD also draw extra power), you should file a bug against the kernel:

https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+filebug

1 Like

Thank you for the quick reply.
I’m using the official power supply, so I don’t think power supply is the problem. Temperature shouldn’t be a problem too.
I filed two bug reports.
One for the login-freeze.
Another one for the freeze during desktop-session.

2 Likes

A post was split to a new topic: Pi 4 too slow

I’m reviewing Ubuntu 20.10 on pi400 from purely a consumer perspective. Not having access to (DRM) streaming video services, such as Netflix and Amazon Prime, out of the box with Firefox is problematic. Getting it to run at all, is a bit beyond the average user.

1 Like

Any more news on the possibility of flavour pi images? - for Ubuntu Budgie we are definitely interested and have our own testing image created from the ubuntu pi image - certainly would be great to formalise this officially.

2 Likes

Most other flavors are complaining about even more testing workload and the lack of testers & people to get involved. You won’t see a Pi image from Xubuntu since i asked them a while ago.

I’ve been testing Ubuntu 20.10 desktop on a Pi 400 and I really enjoy it. It is a bit sluggish, but it is a great start. I do have two questions:

  • I am not able to update mesa using PPAs (kisak PPA for example). I understand the V3D mesa driver is constantly improving and updating it may help with responsiveness, but I can’t figure out how. Anyone was able to update to a newer version of mesa?
  • Is there a plan to have box86 in the repositories for running x86 code? People using raspberry OS have had great success running old x86 programs and games with box86, but I don’t find a straightforward way of installing it on Ubuntu.

Thanks!

Also, another thing I noticed is that some snaps don’t work. Vice-jz and dosbox-staging for example both fail to load (which is a shame because a Pi 400 running commodore emulation is very fitting).

For the snaps you should report the issues to the respective publishers … typically you can find that info via snap info <packagename> in the contact field or somewhere in the description text (sometimes it also helps to write a post in the “snap” category on https://forum.snapcraft.io but not all snap developers read that)

Hi, I have a Raspberry Pi 400.

…in the tutorial for installing Ubuntu Desktop on Raspberry Pi 4/400 - under the section

Boot your Desktop
Duration: 2:00

Ensure your HDMI screen and a USB keyboard are plugged in before powering the Pi. You will be able to see the boot process on screen and, eventually, the first run wizard.

… at this point I was asked to enter the Ubuntu user/password … maybe you can include some info in the tutorial as to what to do if this message is received …

As of writing I am unsure how to proceed…

Thank you.

We do not provide support here on Discourse but it’s basically the same as you would set up a Ubuntu install. User = your username of choice and Password = your password of choice to be able to log in and install updates and software.

Here’s where you can find support:

1 Like