Soplos Linux

Hi Dan,

Thank you so much for the kind words! We're really glad you're enjoying Soplos, especially coming from so many years on Debian Stable with Xfce. If any questions come up or you find anything to improve, we're here.

Best regards

Me alegro que se solucionara
Ya hemos agregado los firmwares corregidos para próximas ISOs

Revisa los permisos desde Flatseal, pero me parece que deben ser todos Flatpks.

Yo de juegos ni idea casi jajaja

Hi, Dan669.

Thanks for your feedback and for explaining your use case in detail. You're right that keeping several kernel versions can be very useful as a fallback if an update causes any issues.

You can currently manage this directly using the existing Soplos Linux tools, without having to create additional APT rules:

• Soplos Kernel Installer: you can individually uninstall any kernels you no longer want to keep.
• Soplos Sys Cleaner: you can also remove unwanted kernels by running it as root.

This allows you to keep your current kernel and the two previous versions you want to retain as backups, removing only the others.

I also appreciate your suggestion to add an option for setting the number of kernels to keep. It's an interesting idea that I'll take into consideration when evaluating potential improvements to Soplos Welcome.

Thanks again for using Soplos Linux and for sharing your suggestions!

Los kernels de Soplos y los parches de Soplos admiten Hardware muy antiguo, respecto a la gráfica ya no es problema de kernel, en todo caso de drivers, pero me encargo de que los parches que hago para nvidia funcionen con drivers antiguos y gráficas antiguas.

De hecho te estoy escribiendo desde mi viejo MSI que tiene unos 10 o 12 años con una GTX 960M y lo hago desde Tyson con los drivers 580 y el recién llegado kernel 7.2.10

Hola Raúl,

Gracias por volver a probar y por contarnos lo que hiciste. Te aclaramos un par de cosas para que no pierdas tiempo con polkit.

El origen del problema era fish: su conflicto con zsh dejaba las actualizaciones a medias, y por eso Bienvenida mostraba el error aunque después cargara la lista de paquetes. En una instalación de serie de Tyron la actualización desde Bienvenida funciona sin tocar nada de polkit.

En cuanto al helper: con la versión de polkit que lleva Tyron (127), polkit-agent-helper-1 ya no necesita el bit SUID. Los permisos 0755 son los normales, y la autenticación va por un socket de systemd. El mensaje needs to be setuid root solo aparece cuando el sistema recurre al método antiguo, y eso no ocurre en una instalación limpia. El chmod 4755 que aplicaste lo fuerza, pero no es la solución de fondo.

Para dejarlo en el estado normal:

sudo dpkg --configure -a
sudo apt update
sudo apt full-upgrade
systemctl status polkit-agent-helper.socket

Si el último comando no muestra active (listening), pégalo aquí. Y si has modificado a mano algo de polkit, PAM o systemd, dínoslo, porque sería lo primero que miraríamos.

Gracias por tu ayuda.

Un saludo,

P.D. He intentado replicar el fallo que dices de pkexec en 8 ordenadores diferentes con Tyron y no he logrado replicar el fallo que dices de polkit. De hecho lo he revisado y está todo correcto.

Polkit 127 ya no necesita el helper con SUID. Recomienda un servicio polkit-agent-helper activado por socket y, según el parche que introdujo el cambio, si el socket AF_UNIX no está presente, el agente lanza el helper clásico. Eso encaja con todo lo que se ha visto...

Hi masterpier,

Great that it's working for you on Tyson, and thanks for sharing your impressions on performance and KDE!

About the welcome screen script: it installs exactly the same package (soplos-vmware-modules) as doing it from the terminal, and it has worked fine for other users. Most likely your system just needed updating before using it. It's always a good idea to do that before installing anything from the welcome screen:

sudo apt update
sudo apt full-upgrade

If it fails again after updating, let us know what message it showed and we'll take a look.

Thanks for your feedback and for supporting the project.

Best regards,
The Soplos Linux Team

Hi masterpier,

We're really glad VMware is running better and that Soplos has won you over enough to replace Nobara! Thanks for letting us know and for all the feedback you've given us, it has helped us improve.

If anything else comes up, we're here.

Best regards,

Hi masterpier,

Thanks for the kind words! Right now we have a Telegram group, but it's Spanish-speaking only. We had also thought about creating a Discord, but the problem is that Discord doesn't index problems and their solutions, and when someone searches for an error online they're most likely to end up on a forum. That's why, for now, the forum is our main support hub.

Thanks for the suggestion and for supporting the project.

Best regards,

Здравствуйте,

Большое спасибо за ваш интерес и за время, потраченное на воссоздание утилиты. Видно, что вы вложили много сил, и интерфейс получился практически таким же, как у Soplos Packager, который тоже работает на всех 8 языках дистрибутива.

Если захотите попробовать, мы можем передать вам текущую версию Soplos Packager. На следующей неделе мы подготовим её для вас, чтобы вы могли её проверить. Если у вас будут предложения или вы найдёте ошибки, мы с радостью прочитаем их здесь, в теме.

Кроме того, мы ищем решение для обмена кодом с участниками, которые не пользуются GitHub, например через сервис передачи файлов вроде WeTransfer или TransferNow. Как только оно будет готово, мы сообщим вам.

Спасибо и всего доброго,
Команда Soplos Linux

Hola Ignacio,

Gracias por avisarnos. El botón no hace nada por un fallo nuestro: la app de bienvenida sigue apuntando al paquete firmware-ralink, que Debian ya eliminó de Testing. El firmware de Ralink está ahora dentro de firmware-mediatek. Es firmware privativo, pero Soplos ya trae activado el componente non-free-firmware, así que basta con instalarlo a mano:

sudo apt update
sudo apt install firmware-mediatek

Después reinicia el equipo para que el kernel lo cargue. Corregiremos la app de bienvenida para que apunte al paquete correcto.

Gracias y saludos,
El equipo de Soplos Linux

Hi masterpier,

Glad it's solved! Thanks for letting us know and for telling us what caused it: it may help other users who run into the same login loop.

If anything else comes up, we're here.

Best regards,
The Soplos Linux Team

Hi masterpier,

Soplos already ships with zram preconfigured: it's compressed swap in RAM, so your system already has swap even though the installer didn't let you create a partition. You can check it with:

swapon --show
zramctl

If you still want a swap file on top of zram, for example for extra headroom, first check which filesystem your root uses, because the method differs:

findmnt -no FSTYPE /

If it's ext4, for example with 8 GB:

sudo fallocate -l 8G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab

If it's btrfs, don't use fallocate; create it like this instead:

sudo btrfs filesystem mkswapfile --size 8G /swapfile
sudo swapon /swapfile
echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab

If something fails, paste the output here and we'll take a look.

Thanks and best regards,
The Soplos Linux Team

Hi masterpier,

Thanks for letting us know. That loop back to GDM usually has a specific cause, and we can narrow it down from a TTY. Press Ctrl + Alt + F3 at the login screen, log in with your user and try this:

1. Check that the disk hasn't filled up, neither space nor inodes:

df -h
df -i

2. Look at the errors from the current boot:

journalctl -b -p err --no-pager | tail -n 60

3. Check that your home folder and its files belong to your user and not to root:

ls -ld ~ ~/.profile ~/.cache ~/.local

4. See which snaps you have installed. If you suspect one of them, you can remove it from the TTY:

snap list
sudo snap remove NAME

5. To rule out a damaged profile, create a test user, log out and try to log in with it:

sudo adduser test

If it works with the new user, the problem is in your profile. Please paste the output of steps 1 to 4 here and we'll take a look.

Thanks and best regards,
The Soplos Linux Team

Te entiendo perfectamente.

Ya nos contarás si te funciona

Hi masterpier,

Great that it's working for you! Thanks for testing the package and for the feedback.

There's no need to include it in the next ISO: the package is already in the repositories, so anyone who needs it can install it with:

sudo apt install soplos-vmware-modules

If it ever breaks after a kernel update, let us know and we'll look into it.

Thanks for your patience.

Hi masterpier,

Good news — we've just built a package that solves exactly this.

soplos-vmware-modules is a .deb we're working on that automates the whole process: it compiles vmmon and vmnet against all your installed Soplos kernels, configures the vmware.service systemd unit, sets up module autoloading at boot, and includes a kernel hook so every time a new kernel is installed the modules are rebuilt automatically — no manual steps needed.

If you want to test it before it hits the repos, you can grab the .deb directly and install it with:

sudo apt install ./soplos-vmware-modules_1.0.0_amd64.deb

You'll need VMware Workstation already installed (the .bundle from Broadcom), and kernel headers for your kernel (linux-headers-$(uname -r)). The rest is handled automatically.

Let us know if it works for you — your feedback would be very helpful before we push it to the repository.

https://www.transfernow.net/dl/202610069v7JueT7

Hi masterpier,

Thanks for letting us know how it went. virt-manager (QEMU/KVM) is a solid option in the meantime, and it's well integrated with the system.

About that VMware error, here's the usual reason behind it: vmmon and vmnet are kernel modules that VMware ships as source code and compiles on your own machine against the kernel you're running. The Linux kernel doesn't keep a stable internal interface for modules built outside of it, so any change in the kernel's internals can break them. These two modules also touch low-level parts (memory management, CPU virtualization, networking) that change often between kernel versions, and VMware doesn't update them quickly. The result is that with recent kernels the build often fails until the community patches it, and this happens on other distros too, not just Soplos.

When the build fails, the module is never loaded and /dev/vmmon doesn't exist, which is exactly what your error says. KVM, which virt-manager uses, is part of the kernel itself, so it doesn't have this problem.

Thanks as well for the screenshot and the feedback.

Здравствуйте,

Спасибо за ваше сообщение и за потраченное время.

Процесс сборки: не совсем так. Мы работаем с Soplos ISO Builder и другими собственными инструментами разработки дистрибутива, хотя в некоторых версиях действительно используется grub-mkrescue.

Репозитории: и репозитории, и программы Soplos Linux рассчитаны на Debian Testing, а не на Stable или Sid. Поэтому при использовании в Trixie адаптировать пакеты — это нормально.

Клавиатуры: в live-сессии заранее настроены все 8 раскладок, чтобы пользователи каждого из 8 родных языков, которые поддерживает дистрибутив, сразу находили свою раскладку. Покупать 8 клавиатур не нужно.

Ваша работа: спасибо, что предлагаете поделиться ею. Чтобы сохранять порядок в проекте, мы принимаем код только через GitHub. Если захотите, вы можете создать бесплатный аккаунт и предложить свой вариант в наших репозиториях (github.com/SoplosLinux) или описать основные идеи вашего метода прямо в этой теме.

Спасибо и всего доброго,
Команда Soplos Linux

Hi Steven,

Thanks for taking the time to test several ISOs and for the screenshots! They've been very helpful.

The current version is 2026.10 (October), and we recommend downloading it from our CDNs. On the official website you can also find SourceForge and Torrent options. Regarding what you mention about SourceForge: each ISO lives on its own page, not in a single bucket, which is why the "Download" button may give you a different ISO than the one you're after. The safest way is to open the page of the edition you want, go to Files and pick the ISO manually, or simply use the CDNs.

About the error: apt-get returning code 100 while installing soplos-welcome points to a connection failure during the installation. We also can't rule out a BIOS clock desync, which can cause this same error. Please try the following:

1. Check that the BIOS date and time are correct, and fix them if they aren't.
2. Make sure you have a stable internet connection throughout the whole installation. If possible, use a wired connection instead of Wi-Fi.
3. Install again with the 2026.10 ISO downloaded from the CDNs and let us know how it goes.

Thanks and best regards,
The Soplos Linux Team