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 {} \;

Makes sense. But for an Arc B580 you’d probably want 6.12 or newer (according to https://www.phoronix.com/review/intel-arc-b580-gpu-compute). Unfortunately Linux Mint is not that great for running the very latest hardware (and especially GPUs).

Is there a particular reason that you want to update your kernel? Generally, the best idea as a new user is to stick with the default kernel that your distro provides What Stable Kernel Should I Use. Given your hardware, I’d expect that kernel 6.8 should work fine for you.

Linux Mint switched to the HWE kernel with version 22. Theferore, the kernel should be updated to 6.11 with the release of Ubuntu 24.04.2 (planned in a week).

Sorry to hear that Linux Mint is not working well for you. Unfortunately, things can sometimes still be rough when it comes to hardware support. I have personally also had issues with Nvidia GPUs and Bluetooth. Often this is because the manufacturers only provide drivers for Windows and Linux drivers need to be created by the community.

Regarding Nvidia and secure boot. I’ve had the same issue (on both Mint and other distros). After some frustrations (including a BIOS update) I finally gave up and disabled secure boot. Since then, I haven’t had any issues with my dual boot with Win 10 (but I probably won’t buy another Nvidia GPU). What makes you say that Windows requires Secure Boot?

No I didn’t. When I installed Linux mint the first time I was able to fix everything. I needed to reinstall it and that is where this controller issue started

This seems quite weird. Are you perhaps missing a package (e.g. steam-devices)?

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.

Given that you installed Linux on a separate drive, it’s likely that the Windows bootloader is perfectly fine but your BIOS chooses to prioritize the Linux disk. I would check if you can still select the Windows drive / installation in the BIOS / boot media selection.

Typically, Fedora should also add the Windows installation to its bootloader (https://docs.fedoraproject.org/en-US/quick-docs/grub2-bootloader/#_adding_other_operating_systems_to_the_grub2_menu). It uses os-prober to find other operating systems. Can you post the output of sudo os-prober?

Edit: The output of lsblk -f would also be useful (though you may want to anonymize it first).

We use Alma Linux at work and it’s fine, I suppose. I see two main reasons why you’d choose an EL linux distro:

1. You have (professional) software that officially supports it. RHEL’s release model makes it an attractive target for proprietary software and many vendors choose to support it.
2. You need/want very long support cycles. You can run 10-year-old software even though you probably shouldn’t.

Apart from those, it’s a competent distro, Red Hat know what they’re doing. If you want the equivalent to an Ubuntu LTS / Debian in the Fedora world, it get’s the job done. I quite like their approach of keeping the core OS stable while updating drivers, tools, and compilers (e.g., the kernel version number has very little meaning in RHEL).

Is the experience very different from Fedora?

Yes. the age of the core packages is very noticeable. The number of fully supported packages is also very small and you need to go to EPEL very quickly (at which point you’re no longer getting enterprise support…). On the plus side, it’s much more stable than Fedora in my experience.

Edit: My main recommendation for a stable distro would probably be Debian unless one of the above points applies.

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.

It sounds like the criterion is “is newer microcode available”. So it doesn’t look like a marketing strategy to sell new CPUs.

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.

This seems very one-sided. Sure, the disclosure was not handled perfectly. However, this post completely ignores the terrible response by the CUPS team.

The point on NAT is certainly fair and prevented this from being a much bigger issue. Still, many affected systems were reachable from the internet.

Lastly, the author tries to downplay the impact of an arbitrary execution vulnerabilty because app armour might prevent it from fully compromising the system. Sure, so I guess we don’t need to fix any of those vulnerabilities /s.

This article is conflating terms that I need help distinguishing between. The other commenter mentioned that Ubuntu is a type of Debian but this article lists Debian and Ubuntu as distributions.

I’d say that the article is correct in calling them separate distributions.They are certainly related (both part of the Debian family), but I think most people would consider them to be separate distributions. Software built for Ubuntu 24.04 may work on Debian 12, but it might also not. For a beginner, I think it’s most useful to consider them to be separate things.

I think when I messed it up, it worked when I tried switching to the proprietary drivers for the second time. I think you can try that without much risk.

In my case I ended up disabling Secure Boot anyway because it just got too annoying (a BIOS update breaking it was the final straw for me). The security benefit after you’ve enrolled a MOK seems dubious anyway. It would be nice if distros could ship signed kernels with the open-source Nvidia driver but I guess that’s not happening.