dev/loop5 squashfs 183M 183M 0 100% /var/lib/snapd/snap/storage-explorer/30 dev/loop2 squashfs 66M 66M 0 100% /var/lib/snapd/snap/gtk-common-themes/1519 Total used free shared buff/cache available * Hardware Virtualization Support (grep -Eq '(vmx|svm)' /proc/cpuinfo & echo Yes || echo No):Ġ9:01:45 up 18 min, 1 user, load average: 2,38, 2,21, 1,62 * 64-bit Support (grep -q ' lm ' /proc/cpuinfo & echo Yes || echo No): * CPU Model (grep 'model name' /proc/cpuinfo | awk -F: '' | uniq -c |Ĩ Intel(R) Core(TM) i7-7820HQ CPU 2.90GHz * SELinux Errors (selinuxenabled & journalctl -since yesterday |grep avc: | grep -Eo comm="+" | sort |uniq -c |sort -rn): Memory protection checking: actual (secure) Gnome-classic, gnome-classic-xorg, gnome, * Desktop(s) Installed (ls -m /usr/share/xsessions/ | sed 's/\.desktop//g' ): * Desktop(s) Running (ps -eo comm= | grep -E '(gnome-session|startkde|startactive|xfce.?-session|fluxbox|blackbox|hackedbox|ratpoison|enlightenment|icewm-session|od-session|wmaker|wmx|openbox-lxde|openbox-gnome-session|openbox-kde-session|mwm|e16|fvwm|xmonad|sugar-session|mate-session|lxqt-session|cinnamon|lxdm-session)' ): My /var/log/journal folder is now 3.4GB, but I’m not sure if this is “normal” or was this big before.Īny idea what I can do? I’d love to report this issue somehow. When I try to journalctl -b -1 and go the end of the logs, it’s just stuck and I have to Ctrl + C. But now I don’t know what caused the issue and - more importantly - how to report the issue. So I force-rebooted in the hope that the update has already gone through. I tried to view the logs via journalctl -f, but at some point is said something like “broken journal entry”. Switching to a TTY with top I saw that gnome-shell and systemd-journal both used about 100% CPU. I just ran dnf update and Gnome froze entirely.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |