几天前，我发现我的笔记本电脑有问题。当我尝试关闭笔记本电脑时，出现了关机屏幕。几秒钟后，这个屏幕就冻结了，什么也没发生。
我尝试关闭笔记本电脑并等待大约一个小时，但不幸的是这个问题仍然存在。我也尝试了关闭解决方案，但仍然无法解决问题。我尝试通过删除 ubuntu 重新安装干净的操作系统，但问题仍未解决。
我在 Acer Nitro AN515-57 上运行 ubuntu。以下日志来自全新安装的 ubuntu。
- 使用命令
sudo journalctl -b -1 -e，我多次发现此行：
august 14 09:31:24 user gnome-shell[1707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
august 14 09:31:24 user gnome-shell[1707]: == Stack trace for context 0x55ac7e4d9490 ==
august 14 09:31:24 user gnome-shell[1707]: The offending signal was notify on NMDeviceEthernet 0x55ac80430330.
august 14 09:31:24 user gnome-shell[1707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
august 14 09:31:24 user gnome-shell[1707]: The offending signal was notify on NMDeviceWifi 0x55ac804343b0.
august 14 09:31:24 user gnome-shell[1707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
august 14 09:31:24 user gnome-shell[1707]: The offending signal was notify on NMActiveConnection 0x55ac8043c180.
august 14 09:31:24 user gnome-shell[1707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
august 14 09:31:24 user gnome-shell[1707]: The offending signal was state-changed on NMDeviceEthernet 0x55ac80430330.
august 14 09:31:24 user gnome-shell[1707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
august 14 09:31:24 user gnome-shell[1707]: The offending signal was state-changed on NMDeviceWifi 0x55ac804343b0.
august 14 09:31:24 user gnome-shell[1707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
august 14 09:31:24 user gnome-shell[1707]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ac7ec25b80.
august 14 09:31:24 user gnome-shell[1707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
august 14 09:31:24 user gnome-shell[1707]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ac7ec25b80.
august 14 09:31:24 user gnome-shell[1707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked.
august 14 09:31:24 user gnome-shell[1707]: The offending signal was destroy on Gjs_ui_appDisplay_FolderGrid 0x55ac7ec25b80.
- 我也在内核日志中发现了这一点：
Aug 15 10:20:26 user kernel: [ 1.299204] ACPI Error: Field [AFU0] Base+Offset+Width 512+0+1 is beyond end of region [COMP] (length 512) (20221020/exfldio-163)
Aug 15 10:20:26 user kernel: [ 1.299222]
Aug 15 10:20:26 user kernel: [ 1.299223] No Local Variables are initialized for Method [_STA]
Aug 15 10:20:26 user kernel: [ 1.299223]
Aug 15 10:20:26 user kernel: [ 1.299224] No Arguments are initialized for method [_STA]
Aug 15 10:20:26 user kernel: [ 1.299224]
Aug 15 10:20:26 user kernel: [ 1.299225] ACPI Error: Aborting method \AFUB._STA due to previous error (AE_AML_REGION_LIMIT) (20221020/psparse-529)
您知道导致该问题的原因是什么吗？如果知道，您能帮我解决这个问题吗？
我提前感谢所有愿意帮助我的人。
编辑：我找到了问题的答案。我将 ubuntu 操作系统版本更新为最新的 23.04。