I wanted to write the same thing. E.g., you can run this in bash to set the permissions for all .conf files to 600:

find /mnt/the/directory -iname "*.conf" -exec chmod 600 {} \;

Yes, I would recommend creating a backup (perhaps on your phone or a different computer over the network) and then upgrading to 21 and then 22. IMHO Mint has steadily gotten better and there is typically no reason to stay on an older version.

It sounds like Proton VPN (or its repo) is causing issues for you. Given that it’s a paid service, you can probably contact their support.

Alternatively, you can also look for the repo file in /etc/yum.repos.d, something like /etc/yum.repos.d/file_name.repo, for Proton VPN. You can then disable it by renaming it to .repo.disabled and try again (sudo dnf upgrade in the terminal). Note: This is not really a permanent solution, as it will disable updates for Proton VPN.

Nice, congrats on getting it to work! :) Native Debian packages are also nice. It can just get difficult if you want the latest stuff.

I used the docker compose template from https://hub.docker.com/_/drupal and mostly changed the image:

# Drupal with PostgreSQL
#
# Access via "http://localhost:8080"
#   (or "http://$(docker-machine ip):8080" if using docker-machine)
#
# During initial Drupal setup,
# Database type: PostgreSQL
# Database name: postgres
# Database username: postgres
# Database password: example
# ADVANCED OPTIONS; Database host: postgres

version: '3.1'

services:

  drupal:
    # image: drupal:10-apache
    # image: drupal:10.3.7-apache-bookworm
    # image: drupal:10.3.6-apache-bookworm
    image: drupal:11.0.5-apache-bookworm
    # image: drupal:10-php8.3-fpm-alpine
    ports:
      - 8080:80
    volumes:
      - /var/www/html/modules
      - /var/www/html/profiles
      - /var/www/html/themes
      # this takes advantage of the feature in Docker that a new anonymous
      # volume (which is what we're creating here) will be initialized with the
      # existing content of the image at the same location
      - /var/www/html/sites
    restart: always
    environment:
      PHP_MEMORY_LIMIT: "1024M"

  postgres:
    image: postgres:16
    environment:
      POSTGRES_PASSWORD: example
    restart: always

The details for the v11 image are here: https://hub.docker.com/layers/library/drupal/11.0.5-apache-bookworm/images/sha256-0e41e0173b4b5d470d30e2486016e1355608ab40651549e3e146a7334f9c8f77?context=explore

Yes, the docker images don’t use the sury.org php packages (they use the php docker image).

“11.0.5-apache-bookworm” also seems to work, maybe you can try that version?

I wanted to recommend using a Docker container but I ran into the same issue with the default config for “drupal:10-apache” (aka “drupal:10.3.7-apache-bookworm”). Opening “node/add/article” results in the OOM error. Downgrading to “drupal:10.3.6-apache-bookworm” resolved the issue. Looks like a Drupal regression to me. Maybe you can also try an older version of Drupal 11?

If you don’t want to reinstall the OS, you can probably use Clonezilla: https://clonezilla.org/show-live-doc-content.php?topic=clonezilla-live/doc/03_Disk_to_disk_clone

Maybe you need to update the drive ids for your bootloader (grub) afterwards, not sure about that.

Edit: Maybe the advanced “-g auto” option does that for you.

It seems that 18.04 was the last release for 32-bit x86 (i386): https://askubuntu.com/questions/1376090/latest-version-of-ubuntu-for-i386-architecture-32-bit

But you could just go for Debian which still supports it.

Did you perform a full shutdown of Windows (Windows doesn’t fully release the partition on a normal shutdown)?

Edit: adding some context. I am planning to setup a dev machine that I will connect to remotely and would like to babysit very little while having stable and fresh packages. In the Ubuntu world we would go to an LTS release but on the RPM/Dnf world is there any other distro apart from CentOS Stream? And also is CentOS Stream comparable to an LTS release at all considering that they do not have release number?

Wanting both stable and fresh packages is unfortunately somewhat difficult in my experience. I think the primary choice within the Fedora ecosystem is if you want to have fresh packages (Fedora) or if you prefer a slower update cycle and more stable packages (RHEL/Alma/Rocky). In the second case you can also choose if you wish to pay Red Hat for support (RHEL) or not (Alma or Rocky).

One thing that’s quite different in RHEL vs Ubuntu/Debian ist that it gets minor releases that include substantial new features. For example you’ll get new compilers, python versions, drivers, … CentOS Stream gets those slightly ahead of RHEL/Alma/Rocky (a cynical person might say that CentOS Stream is a rolling beta for RHEL). But, IMHO that’s not really a strong reason to use CentOS Stream.

If you’d go with an Ubuntu LTS release, then I’d look into RHEL/Alma/Rocky.

This “new law” was passed more than a year ago… But, it’s still a step in the right direction.

That looks like a software issue… I would try a different distro or a different version of Ubuntu (e.g. 22.04).

You could also try to switch the kernel version. Ubuntu 22.04 currently supports two different versions: 5.15 and 6.5, you could switch to the other one and see if the problem also occurs there.

That looks quite weird… RHEL 9.2 was patched in February. RHEL 7 and RHEL 8 have now been patched too, but RHEL 9 (9.3) is still vulnerable?

Given that Fedora is a distro that aims to be on the frontier of new features and technologies, the inclusion of KDE seems like a much better fit than Gnome.