I need some help to evaluate the health of my system

General system Newbie
1

Running

journalctl -p err..alert

for showing “error, critical and alert priority messages” (journalctl) produces litteraly hundreds of lines that I am admittedly in need of assistance to interpret. If you could just skim through it and give some advice I’ll be most grateful.

Here it is: https://clbin.com/8ZSho

I had some issues with Bluetooth yesterday, but I “happened” to resolve it.

2

One concerning thing I see there is that gnome-shell seems to be regularly dumping core.

2 Likes
3

Yes, that one attracted my attention too. Do you have some ideas how I could troubleshoot that? What are the consequence of this for the overall functioning the system? I mean, without having run the command line above, I wouldn’t have noticed anything at all. Everything seems to be running smoothly.

4

I just checked my KDE and it has hundreds of errors also but different. I didn’t have very many the last time i checked but it was kernels ago.

https://clbin.com/4Z3Wn

5

Try KDE Plasma :rofl:

6

You Know very well my posture by now. In any turn of events I:

image

:wink:

1 Like
7

Looks like you are missing packages needed by libvirtd. You should probably fix that…

8

How do i know what is needed?

9

@dalto,
Is there any way to monitor what gets logged in the journals in real-time with journalctl or something else. Like what you get from dmesg -w for kernel messages.

10

libvirtd[625]: ebtables not available

11

I see that but why is it about firewall?

12

ebtables seems to be provided by iptables-nft.

pacman -Ss iptables-nft
core/iptables-nft 1:1.8.7-1
Linux kernel packet control tool (using nft interface)

13

journalctl -f

1 Like
14

Nice, thanks!

By the way, I rebooted the system somewhat more than an hour ago and filtering the output from
journalctl -p err..alert for the last boot shows only the following so far:

-- Journal begins at Sun 2021-08-08 10:36:04 CEST, ends at Mon 2021-08-09 22:55:10 CEST. --
Aug 09 21:35:50 enos-gnome kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.LPC0.EC0], AE_NOT_FOUND (20210331/dswload2-162)
Aug 09 21:35:50 enos-gnome kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210331/psobject-220)
Aug 09 21:35:50 enos-gnome systemd-udevd[475]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
Aug 09 21:35:50 enos-gnome systemd-udevd[466]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".
Aug 09 21:35:50 enos-gnome systemd-udevd[468]: vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl".
Aug 09 21:35:50 enos-gnome systemd-udevd[522]: vboxdrv: /usr/lib/udev/rules.d/60-vboxdrv.rules:1 Only network interfaces can be renamed, ignoring NAME="vboxdrv".
Aug 09 21:35:50 enos-gnome systemd-udevd[503]: vboxnetctl: /usr/lib/udev/rules.d/60-vboxdrv.rules:3 Only network interfaces can be renamed, ignoring NAME="vboxnetctl".
Aug 09 21:35:50 enos-gnome systemd-udevd[502]: vboxdrvu: /usr/lib/udev/rules.d/60-vboxdrv.rules:2 Only network interfaces can be renamed, ignoring NAME="vboxdrvu".
Aug 09 21:35:50 enos-gnome kernel: acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517
Aug 09 21:35:51 enos-gnome systemd-udevd[487]: zram0: /etc/udev/rules.d/99-zram.rules:1 Failed to write ATTR{/sys/devices/virtual/block/zram0/disksize}, ignoring: Device or resource busy
Aug 09 21:36:05 enos-gnome gdm-password][1360]: gkr-pam: unable to locate daemon control file
Aug 09 21:36:08 enos-gnome systemd[1374]: Failed to start Application launched by gnome-session-binary.
Aug 09 21:36:08 enos-gnome systemd[1374]: Failed to start Application launched by gnome-session-binary.
Aug 09 21:36:09 enos-gnome gdm-launch-environment][985]: GLib-GObject: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 09 21:36:14 enos-gnome pulseaudio[1541]: org.freedesktop.DBus.Properties.Get /org/bluez/hci0/dev_C0_28_8D_92_DF_CF/sep1/fd0 Volume failed: org.freedesktop.DBus.Error.InvalidArgs: No such property 'Volume'
Aug 09 21:36:51 enos-gnome kernel: ucsi_acpi USBC000:00: PPM init failed (-110)

In the logs I postet in the OP, gnome-shell dumped core almost immediately after boot.

What does

 zram0: /etc/udev/rules.d/99-zram.rules:1 Failed to write ATTR{/sys/devices/virtual/block/zram0/disksize}, ignoring: Device or resource busy

mean? Does it mean that zram is not setup or functioning properly. I have had an unresolved issue to set up a combination of zram and regular swap partition on this system.