I recommend that route as well.

Since you don’t know much, stick to native services. In most cases those are already preconfigured if native service package is available.

You don’t specify.

Do you use containers or not? It sounds like you are trying to start a rootless container.

Otherwise, you are over complicating things.

Add to that need to use machinectl to establish normal user session with DBus in it.

But that only makes sense for rootless containers. User management in rootless container and users in roootful containers can get complicated fast and depends on how image is built.

All these downvotes really prove your point.

I think I might switch to that.

I used Firefox for cross-platform password management. That’s the biggest impact on me.

What’s wrong with Chromium? License or Google backing?

The issue you have is most likely a BIOS artifact. New drive makes bios think you have EFI based system vs old drive was BIOS.

You are not likely to get accurate help here.

You don’t need to make drastic moves destroying data, but playing with BIOS settings may help.

You may need to identify your system capabilities, to troubleshoot effectively. Here is one way to do that:

https://wiki.archlinux.org/title/Installation_guide#Verify_the_boot_mode

I am not saying to install Arch. Just a way to identify your system.

One easiest way to get your old disc back is to wipe out formatting data on new disk. Be warned that running wipefs on wrong drive will loose all of your old disk data in less than one second. So, identify your disc with absolute certainty using lsblk, you may need options to lsblk.

Every BIOS is a bit different.

Some have option to boot using Old style partition scheme. Make sure it is on.

You can always boot any Linux distro you are most familiar with from USB and copy boot partition from old to new disc.

It is not that hard if you are familiar with command line level partition tools.

Arch Linux installer is great for that purpose simply because it is the main installation mode.

You can jump to command line tooling from Fedora installer easily as well.

That’s all the distro experience I have.

It is “the way” when you have more complicated disk setups like encryption, raid, mapper, etc.

Is dbus still available on non-systemd?

It is probably the best solution to the low memory problem, but it is also the least common and may be the most difficult.

Fedora.

It seems to be easy to manage and fast to install.

SUSE is slow to run and self-update.

Debian is far behind and Ubuntu seems to always have an issue during or right after installation.

I don’t understand why Mint is chosen by people.

2 years old need to learn interaction with other people.

That’s how they learn language.

So, spend time with them, not the screen. Screen time will come by itself.

In fact there’s data of development delays if kids are exposed to screen at early ages. That is because our eyes like movement, but screen picture doesn’t provide meaningful world context. Especially games.

Only personal interaction gives words in meaningful action context.

My wife is speech pathologist, so I am sharing what I wax told.

We have a friend, who didn’t listen to no screen time. Kid is delayed in development. It is serious staff and yet so simple to prevent.

Give your kids all the time you can in 1st several years.

I used Arch for years, but found that I got everything at the same speed from Fedora for fraction of effort.

Fedora

SSDs die suddenly.

I use kvm switch and run into this issue.

I am currently on Fedora 41, Gnome. I’ve seen this issue when running Arch on the same hardware without kvm switch to the point that I disabled suspend.

The fix for me is Ctrl-Alt-F1. It simply brings display manager’s login screen. Gnome on Fedora 41 uses gdm.

The rationale here is simple: the display manager should be resetting screen to display login screen.

I switched to XFS.

The most important feature to me is support for file deduction which is supported by XFS through reflink. BTRFS supports reflinks as well.

Snapshot in BTRFS seems like the most desirable feature, but in real life I ended up not using it.

I usually prefer drive mirror setup, but it can give its own headaches.

These days I simply have 2 disks and nightly rsync job copies content of one drive to another. This protects from drive failure.

Rclone job sends most important data to offsite backup.

The biggest loss is missing data checksums, but it is a unique feature of BTRFS that most filesystems manage without.

I don’t have setup to expand partition beyond one drive. It comes with its own headache. I simply use large enough disks.

He was running long installation process from command line and lock warning was probably appropriate.

He was probably supposed to mark downloaded .run file executable. Instead he went to collect errors.

~/projs

I like ~/w or ~/p options