所以我运行这个命令sudo journalctl -p 3 -xb
来检查错误,我收到了很多这样的错误。如何解决这些问题?
Jul 17 13:46:27 tanuj kernel: x86/cpu: SGX disabled by BIOS.
Jul 17 13:46:27 tanuj kernel: integrity: Problem loading X.509 certificate -65
Jul 17 13:46:45 tanuj gnome-session-binary[448]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jul 17 13:46:45 tanuj gnome-session-binary[448]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Jul 17 13:47:26 tanuj gdm-password][752]: gkr-pam: unable to locate daemon control file
Jul 17 13:47:36 tanuj systemd[765]: Failed to start Application launched by gnome-session-binary.
░░ Subject: A start job for unit UNIT has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ A start job for unit UNIT has finished with a failure.
░░ The job identifier is 442 and the job result is failed.
Jul 17 13:47:39 tanuj gdm-launch-environment][425]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Jul 17 13:47:50 tanuj systemd-coredump[1407]: [
答案1
有很多不同的错误,不仅仅是一个,很难说你这边发生了什么。这些错误中的任何一个真的困扰您吗?如果没有,则无需担心,将它们视为信息性消息。大多数现代功能齐全的桌面操作系统都会在运行时转储大量错误,并且当今没有任何复杂的软件是真正万无一失的。修复所有错误需要更多时间,同时您需要放弃更紧迫的问题。
如果你运行dmesg -t --level=alert,crit,err,warn
你会看到更多来自内核的错误。并不一定意味着您的系统上出现了故障。