为什么这么多true crashes

刚才偶然打开 crashes processes viewer 发现一堆true进程错误啊

       PID: 5936 (true)
       UID: 1000 (ethan)
       GID: 1001 (ethan)
    Signal: 12 (SYS)
 Timestamp: Thu 2025-12-18 16:39:37 CST (4min 15s ago)

Command Line: /usr/bin/true
Executable: /usr/bin/true
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-firefox-1157c08f21ce4c70ab253dcf9e5c005a.scope
Unit: user@1000.service
User Unit: app-firefox-1157c08f21ce4c70ab253dcf9e5c005a.scope
Slice: user-1000.slice
Owner UID: 1000 (ethan)
Boot ID: f216ef9899f24062aad4e6dff3a10611
Machine ID: dfd2c6b3eef9478e8e3740ebdb992f09
Hostname: aosc-3a4000itx
Storage: /var/lib/systemd/coredump/core.true.1000.f216ef9899f24062aad4e6dff3a10611.5936.1766047177000000.zst (present)
Size on Disk: 17.3K
Message: Process 5936 (true) of user 1000 dumped core.

我们暂未找到详细的原因,但根据图中提到的 firefox 判断,有可能是沙盒基于 SIGSYS 的工作机制在 mips 上实现不完整导致。

您好,该问题我们已归因并推送了 Core 13.0.1 更新作为紧急修复

1-2 小时后更新系统即可,感谢理解

哪里哪里,受宠若惊,感谢白总和诸位的无私奉献。

刚更新了,但好像firefox直接无法启动了:joy:

抱歉我好像还传不了文件?

麻烦再更新一下,您可能没收到 Core 13.0.1

那天我记得同时收到了core 13.0.0 和 13.0.1.
不过刚才再更新收到了core 13.0.2 和 13.0.1.
更新好了不过好像问题又回去了…

       PID: 1629 (true)
       UID: 1000 (ethan)
       GID: 1001 (ethan)
    Signal: 12 (SYS)
 Timestamp: Mon 2025-12-22 12:21:01 CST (12s ago)

Command Line: /usr/bin/true
Executable: /usr/bin/true
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-firefox-8c7b8cc82b0448008f5c2aa3d8ae7386.scope
Unit: user@1000.service
User Unit: app-firefox-8c7b8cc82b0448008f5c2aa3d8ae7386.scope
Slice: user-1000.slice
Owner UID: 1000 (ethan)
Boot ID: ebe2ce8e54ef45109c12f7e5a56b2ea1
Machine ID: dfd2c6b3eef9478e8e3740ebdb992f09
Hostname: aosc-3a4000itx
Storage: /var/lib/systemd/coredump/core.true.1000.ebe2ce8e54ef45109c12f7e5a56b2ea1.1629.1766377261000000.zst (present)
Size on Disk: 17.2K
Message: Process 1629 (true) of user 1000 dumped core.

system log 重复以下段落

12/22/25 12:28 PM org_kde_powerdevil Starting libddcutil. library built Aug 21 2025 at 02:18:00. stdout_stderr_redirected=true
12/22/25 12:28 PM org_kde_powerdevil org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed Charge thresholds are not supported by the kernel for this hardware
12/22/25 12:28 PM org_kde_powerdevil org.kde.powerdevil: org.kde.powerdevil.backlighthelper.brightness failed
12/22/25 12:28 PM org_kde_powerdevil ddca_get_display_info_list2 called before ddca_init2() or ddca_init(). Performing default initialization
12/22/25 12:28 PM libddcutil Initializing libddcutil. ddcutil version: 2.2.1, shared library: /usr/lib/libddcutil.so.5.3.0
12/22/25 12:28 PM libddcutil [ 3252] Unexpected architecture mips64.
12/22/25 12:28 PM libddcutil [ 3252] (i2c_detect_x37) Extra x37 sleep: Sleeping for 400 milliseconds
12/22/25 12:28 PM libddcutil [ 3252] (i2c_detect_x37) Extra x37 sleep: Sleeping for 400 milliseconds
12/22/25 12:28 PM libddcutil [ 3252] (i2c_detect_x37) Extra x37 sleep: Sleeping for 400 milliseconds
12/22/25 12:28 PM systemd plasma-powerdevil.service: start operation timed out. Terminating.
12/22/25 12:28 PM systemd plasma-powerdevil.service: Failed with result ‘timeout’.
12/22/25 12:28 PM systemd Failed to start plasma-powerdevil.service - Powerdevil.
12/22/25 12:28 PM systemd plasma-powerdevil.service: Consumed 4.735s CPU time, 13.2M memory peak.
12/22/25 12:28 PM systemd plasma-powerdevil.service: Scheduled restart job, restart counter is at 86.
12/22/25 12:28 PM systemd Starting plasma-powerdevil.service - Powerdevil…