Virgin/Clean install of Eoan Desktop install in a KVM virtual machine.
Install package cqrlog, which has a long startup time and usually causes the "not responding" dialog to raise, but can be dismissed.
Under Eoan, the "CQRLOG is not responding" dialog cannot be dismissed - both "Force Quit" and "Wait" are greyed out and cannot be selected.
gnome-shell then runs to 100% cpu utilisation (one thread/core) and repeatedly logs:
gnome-shell[4157]: JS ERROR: TypeError: null has no properties#012_addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13#012vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9
in syslog.
Killing gnome-shell clears the "not responding" dialog.
Not this is a virgin install to debug this problem, no extensions or anything else installed (except mariadb-server and cqrlog).
I have this problem as well.
Virgin/Clean install of Eoan Desktop install in a KVM virtual machine.
Install package cqrlog, which has a long startup time and usually causes the "not responding" dialog to raise, but can be dismissed.
Under Eoan, the "CQRLOG is not responding" dialog cannot be dismissed - both "Force Quit" and "Wait" are greyed out and cannot be selected.
gnome-shell then runs to 100% cpu utilisation (one thread/core) and repeatedly logs:
gnome-shell[4157]: JS ERROR: TypeError: null has no properties# 012_addWindowEf fect@resource: ///org/ gnome/shell/ ui/closeDialog. js:74:13# 012vfunc_ show@resource: ///org/ gnome/shell/ ui/closeDialog. js:145: 9
in syslog.
Killing gnome-shell clears the "not responding" dialog.
Not this is a virgin install to debug this problem, no extensions or anything else installed (except mariadb-server and cqrlog).