Kagi is doing something similar. Both for ente and notesnook.

kagi.com/specials

Damn, I was hoping for Tuta managing Ente in EU, and same plan same price for everything both product suites offer. Like a Libre Google One, or an actual competitor to Proton.

I know, I know, eggs in one basket, and all... I just want a simple way to migrate fast and then go from there.

How?

Hong Kong has also proposed new offences under the real-name registration system to criminalise the improper use of SIMs registered in another person’s name

Is no id card required for registration?

!surrealmemes@lemmy.dbzer0.com

All 4s are welcome to the second hell here

Feeling like a leprhacahhn

8

One thing that I did when distro hopping was to have /home be separate like you have, but I would back it up elsewhere and let it be a clean start which I could bring over what I wanted from the backup.

It was easier than hunting down which dotfile the new distro didn't like.

the /var/log/ folder would be the best place to start.

1. When a random freeze occurs note the time. Try to be as accurate and close to the time it happened as you can, including day, hour, and minute.\
   A. If possible, do this for multiple instances of this happening
2. Check various log files starting with syslog and look at the times noted above. Look for any relevant errors being thrown by the system at these times.

1) Would be good to know the hardware you're working, especially if it's a laptop and the model.
2) What kind of freeze is this? Black screen, frozen graphics, mouse frozen...etc. Also whether is time-bssed, and how long it takes to freeze.
3) As a test, boot, and play music continuously until it freezes. Does the sound stop as well?

In all practical reality, Linux takes A LOT to topple over like this. It certainly would fair better than Windows with wonky hardware, but if it's a laptop for example, maybe your fans aren't working and therefore it's a heat. Just try and define what kind of freeze it is first.

Command line is your friend. It might not seem like it at first, but it is very helpful.

Use the journalctl command in a terminal.

Command Purpose Example
journalctl -u [SERVICE] View logs for a specific systemd unit/service. journalctl -u nginx.service
journalctl -b Show logs from the current boot. journalctl -b
journalctl -b -[N] Show logs from a previous boot (ee.g., -1 for the last boot). journalctl -b -1
journalctl --list-boots List all recorded boot sessions. journalctl --list-boots
journalctl -p [PRIORITY] Filter by priority level or a range. Levels are 0 (emerg) to 7 (debug). journalctl -p err..warning (shows errors, critical, alerts, and warnings)
journalctl --since="[TIME]" --until="[TIME]" Filter by time range. Supports absolute (YYYY-MM-DD HH:MM:SS) and relative times (1 hour ago, yesterday). journalctl --since "20 min ago"
journalctl -n [LINES] Show only the last N entries. journalctl -n 20
journalctl -k Show only kernel messages (equivalent to dmesg output). journalctl -k
I spent a couple of days trying to figure out why I couldn't install any variant of Arch Linux or Fedora Linux on my laptop. That command helped me narrow things down.

Maybe easier to another suggestion, you're probably using a systemd based distros -

journalctl -b -1 will show you the logs from the previous boot, so you could check that after resetting to see if anything was logged

For some other ideas to narrow down where the issue is...

If you're stuck in the frozen state, you can Ctrl+alt+delete 7+ times quickly to tell systemd to try to restart the system. If this works, it means init was still able to process messages

If that doesn't work, you could enable Magic Sysrq Key (if disabled in your distro), and then use the key sequence REISUB to try to see if the kernel is still responding and can reset the system

Explain how "freezed" are the system
- is the freeze sudden or does the system gets progressively slower?
- does the mouse cursor respond?
- does the audio keep playing in the background? does it repeat a short time interval over and over again?
- does the system respond to ping requests?
- does the system accept incoming ssh connections?
- how random is it? what time interval?
- is the location random (think consistent wifi / bluetooth devices nearby)
- is the freeze happening after going to sleep / hibernation / screen blank?
- does this happen if you aggressively open a lot of apps at the same time? Try it.

What to do before next system freeze
- update and upgrade the system
- create a working directory somewhere where you write down your findings. Does not have to be pretty or anything. Just for your own convenience.
- Configure REISUB. check files in /etc/sysctl.d/*.conf and look for kernel.sysrq=0. Change it to 1.
- Enable ctrl+alt+del spam reboot. Update /etc/systemd/system.conf so that you have a line looking like this:

CtrlAltDelBurstAction=reboot-force

• Reboot
• Try spamming ctrl+alt+del quickly. Does the system reboot?
• On next boot try switching to a random tty ctrl+alt+fN where N in {1..12}. You should see a login prompt. Try the REISUB sequence. Press and hold alt+print screen (might require some fn key combination on a laptop) then press, hold and release following letters one at a time: R E I S U B. You should see kernel messages appear on the screen each time you press a button. Don't try to press them all at once or type them before the output is finished. Your system should reboot after this. Does it work?
• make sure you can ping your computer from another computer.
• Configure TCPKeepAlive=no for my-faulty-pc in your ssh config before connecting to avoid having the connection dropped. then run ssh my-faulty-pc journalctl -b0 -k -f > waiting_for_crash.log on another system that will capture the log

reproduce
Here is the easiest part. Make the system hang. Preferably with reproducible steps.

System is now freezed
- Go quickly through the first list
- from the remote host that monitors the logs through ssh. You can close the ssh connection and inspect some of the last lines in the file. Don't upload it anywhere before sanitizing it to avoid doxing yourself.
- from the remote system try ssh and pinging.
- on the frozen host try ctrl+alt+del burst first
- then try REISUB combo if the burst didn't work.

What to do now
This part depends a bit on what the outcomes were. At least we'll know how "deep" the hang is and where it's worth modifying stuff.

You say in your post that you've tried ctrl+alt+del spam. But did you check that it works when the system is working as intended?

Edit: minor typo

this is important, and will help you find solutions much more specific than just "system freeze"

• Right after a crash, once you reboot, run journalctl -b -1 and scroll to the bottom. Look for any big red text, all of that will be very helpful to diagnose this issue

Otherwise,

• Does it freeze permanently, requiring a reboot, or for a few seconds?
  
  • If it's just for a few seconds, and you're on an AMD system, it would sound like an fTPM stutter. A BIOS update would likely fix that, it was a widespread issue.

  
  

• Are you using an AMD or NVIDIA GPU?
• Do you play any games or use any software that uses OpenGL? (Blender and minecraft are some I've had problems in before)

Which distro are you on?

Was there a kernel update recently by chance? Have you tried falling back to an earlier version? Got any timeshift backups?