Nothing happens. I thought i might have had the wrong hotkeys and had to double check
comments
When it happens can you swap to a different tty by pressing CTRL-ALT-F2 after things stop responding? If you get a terminal with a login screen then that means your desktop environment is hanging, not your computer.
Been running a memtest for two hours. Hopefully done soon 😅
Well, it's not a hard crash. I lose functionality on my taskbar, and can't run any programs 😓
Can't even shut down 😅
The command needs to be run after you crash. It's showing the logs of the last time you boot (That's the "-b -1") which is why you're seeing yesterday's log.
I don't see anything crazy in this output.
You can change the options to trawl the logs if you like. type in "man journalctl" and you'll get a man page entry explaining what each of the options and how to use them.
Here's what I got from that command. Everything below the "Shutting down" command. Lookint through what it provided... there is a LOT in that search that I don't understand. It looks like it recorded it from last night (when I had not experienced the issue) instead of just now.
results
Mar 26 11:50:45 fedora systemd[1]: Stopping systemd-zram-setup@zram0.service - Create swap on /dev/zram0...
Mar 26 11:50:45 fedora kernel: zram0: detected capacity change from 16777216 to 0
Mar 26 11:50:45 fedora systemd[1]: boot.mount: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Unmounted boot.mount - /boot.
Mar 26 11:50:45 fedora systemd[1]: Reached target umount.target - Unmount All Filesystems.
Mar 26 11:50:45 fedora systemd[1]: systemd-fsck@dev-disk-by\x2duuid-48c1277e\x2d11b4\x2d4960\x2da835\x2d0cfa06b830e2.service: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Stopped systemd-fsck@dev-disk-by\x2duuid-48c1277e\x2d11b4\x2d4960\x2da835\x2d0cfa06b830e2.service - File System Check on /dev/disk/by-uuid/48c1277e-11b4-4960-a835-0cfa06b830e2.
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-48c1277e\x2d11b4\x2d4960\x2da835\x2d0cfa06b830e2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: Removed slice system-systemd\x2dfsck.slice - Slice /system/systemd-fsck.
Mar 26 11:50:45 fedora systemd[1]: Stopped target local-fs-pre.target - Preparation for Local File Systems.
Mar 26 11:50:45 fedora kernel: audit: type=1131 audit(1774551045.097:273): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-fsck@dev-disk-by\x2duuid-48c1277e\x2d11b4\x2d4960\x2da835\x2d0cfa06b830e2 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: Stopping lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Mar 26 11:50:45 fedora systemd[1]: systemd-remount-fs.service: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Stopped systemd-remount-fs.service - Remount Root and Kernel File Systems.
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: systemd-tmpfiles-setup-dev.service: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Stopped systemd-tmpfiles-setup-dev.service - Create Static Device Nodes in /dev.
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: systemd-tmpfiles-setup-dev-early.service: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Stopped systemd-tmpfiles-setup-dev-early.service - Create Static Device Nodes in /dev gracefully.
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev-early comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora kernel: audit: type=1131 audit(1774551045.098:274): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora kernel: audit: type=1131 audit(1774551045.098:275): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora kernel: audit: type=1131 audit(1774551045.098:276): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-tmpfiles-setup-dev-early comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: systemd-zram-setup@zram0.service: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Stopped systemd-zram-setup@zram0.service - Create swap on /dev/zram0.
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-zram-setup@zram0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora kernel: audit: type=1131 audit(1774551045.120:277): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-zram-setup@zram0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: Removed slice system-systemd\x2dzram\x2dsetup.slice - Slice /system/systemd-zram-setup.
Mar 26 11:50:45 fedora systemd[1]: lvm2-monitor.service: Deactivated successfully.
Mar 26 11:50:45 fedora systemd[1]: Stopped lvm2-monitor.service - Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: Reached target shutdown.target - System Shutdown.
Mar 26 11:50:45 fedora systemd[1]: Reached target final.target - Late Shutdown Services.
Mar 26 11:50:45 fedora systemd[1]: systemd-poweroff.service: Deactivated successfully.
Mar 26 11:50:45 fedora audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-poweroff comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Mar 26 11:50:45 fedora systemd[1]: Finished systemd-poweroff.service - System Power Off.
Mar 26 11:50:45 fedora systemd[1]: Reached target poweroff.target - System Power Off.
Mar 26 11:50:45 fedora systemd[1]: Shutting down.
Mar 26 11:50:45 fedora audit: BPF prog-id=60 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=59 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=52 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=51 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=55 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=54 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=69 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=68 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=45 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=47 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=46 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=73 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=72 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=48 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=50 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=49 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=67 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=66 op=UNLOAD
Mar 26 11:50:45 fedora audit: BPF prog-id=41 op=UNLOAD
Mar 26 11:50:45 fedora systemd-shutdown[1]: Syncing filesystems and block devices.
Mar 26 11:50:45 fedora systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Mar 26 11:50:45 fedora systemd-udevd[676]: Failed to remove file descriptor "config-serialization" from the store, ignoring: Connection refused
Mar 26 11:50:45 fedora systemd-journald[637]: Received SIGTERM from PID 1 (systemd-shutdow).
Mar 26 11:50:45 fedora systemd-journald[637]: Journal stopped
(END)
😅 sorry if I grabbed too much
I will try these out and report back
Run a memory test, I was having issues like this that turned out to be some RAM that passed self-tests but failed during certain kinds of writes.
What does “journalctl -b -1 -e | less” say when you run it after a crash? Like the last 20 lines.
Also when it crashes can you get to a different tty by pressing ctrl-alt-F2 or is the system completely locked?
I thought the same thing, but couldn't find anything new or unexpected in sysmon 😓
Sat at low cpu and gpu usage.
Sounds like a memory leak to me. To test my theory you could open a memory monitor on your first clean boot (from Terminal you could use the "top" tool). Sort by memory consumption in top. Then note what the largest consumers of RAM are. Check again after about 10 min, and then another 10 min later. Do you see a process that is increasing that you wouldn't expect to be?
I an having a similar problem. Linux mint.
If adding entries to your using fstab you should probably use UUID's instead of device names.
To get the UUID type sudo blkid | grep /dev/sdb2 where /dev/sdb2 is replaced with your partition name. This should give you the UUID for your partition.
Then you can make an entry into your fstab that looks like this.
#/dev/sdb2
UUID=6CE0B016E0AFE514 /mnt/Disk_2 ntfs3 rw,relatime 0 0
The reason you want to use UUID's is because the device name /dev/sda, /dev/sdb etc... can change but the UUID of your partition stays the same.
tmux
I’m so glad it was useful!
Thank you! Super helpful for someone like me just switching over.
BTRFS with snapper snapshots and a grub bootloader hook (which CachyOS can do out of the box) will protect you from the worst of the mistakes you can make
I felt the same way about Bazzite and switched to Fedora. I haven't looked back.
Regular fedora kde is probably best
If you’re going to be doing development, CachyOS is aimed exactly at your use case:
- gaming
- with development
- on nvidia gpu
It has worked fantastically for me. I tried bazzite as well, but put my wife on it rather than use an immutable distro.
I also love bazzite but had to move to something else because I needed to mess with GPU installation. I looked around and landed on CachyOS. It has a lot of the same focus (performance, out of the box gaming, fast setup, Plasma) but it also lets you sudo mess with everything. Obviously, you'll be liable to break things more easily but it was a worthy change for me and my needs
At it's core, Bazzite is Fedora. Nobara is a fork of Fedora with gamers and creatives kept in mind, plus it's not immutable. So using either just Fedora or Nobara with KDE as the desktop environment will give you the same overall feel and let you dial in your audio. As far as the .NET stuff goes, thats all new to me, but I'd think finding an AppImage or Snap with 10 could be a work around, or just waiting until the Flatpak updates would be the move there.
Recently switched to Fedora for similar reasons. So far so good.
But does that include any required deps?
Thank you, yeah that does all sound pretty good, I'm curious if the estimate is accurate now, I suppose only one way to find out.