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.