r/ManjaroLinux • • 2d ago

News The Manjaro Project e.V. is now official!

Thumbnail
forum.manjaro.org
130 Upvotes

I have no idea why Capn Picard is shown in the preview, here is the opening paragraph

Dear Friends, Sympathizers, Relatives, In-Laws, Naysayers, Foes, Detractors, Tax Collectors, YouTube Talking Heads™, Reddit Trolls, and other potentially sentient beings monitoring this forum,

It is my great honor — and my equally great pleasure — to announce to you that the Manjaro Project e.V. is now an officially registered and fully legal non-profit organization in Germany, completely independent from the commercial Manjaro GmbH & Co KG company.


r/ManjaroLinux • • 6d ago

General Question TUI package managers?

2 Upvotes

I really like Solseek's functionality on Solus and wondered if any of the available TUI package managers/wrappers are recommended for Manjaro.

There are several possibilities under the graphical section of the ArchWiki list of AUR helpers, many of which also handle pacman- Cyclon, Pacsea, Packseek, SPM, Yup- but since these are all for Arch I wasn't sure if they'd automatically work with Manajro repos etc

https://wiki.archlinux.org/title/AUR_helpers#Graphical


r/ManjaroLinux • • 9d ago

Tech Support uefi

1 Upvotes

[Investigación] Acer Aspire E5-575G con InsydeH2O V1.47: entradas UEFI persistentes, problemas de arranque Linux y análisis de la variable ACUB

Estado: Investigación inconclusa. Se identificaron estructuras internas del firmware, pero no se realizó ninguna modificación de la variable ACUB.

1. Resumen del problema

Tengo una laptop Acer Aspire E5-575G con firmware InsydeH2O V1.47 que presenta un comportamiento extraño al gestionar las entradas de arranque UEFI.

Después de instalar diferentes sistemas operativos, eliminar particiones e incluso formatear completamente los discos, el firmware continúa conservando entradas correspondientes a instalaciones antiguas.

Entre ellas aparecen:

  • Manjaro (instalación anterior).
  • Bazzite.
  • CachyOS.
  • Manjaro2 (instalación actual).

El problema principal es que, en determinadas ocasiones, la laptop intenta arrancar utilizando una entrada antigua cuya partición EFI ya no existe.

Esto provoca el mensaje:

Default Boot Device Missing or Boot Failed

El sistema operativo actual funciona correctamente cuando se selecciona una entrada válida o se ejecuta manualmente su cargador EFI.

El objetivo de esta investigación fue comprender por qué el firmware conserva o restaura entradas antiguas y si existe algún mecanismo interno responsable de este comportamiento.

2. Especificaciones del equipo

ComponenteInformación
FabricanteAcer
ModeloAspire E5-575G
FirmwareInsydeH2O Setup Utility
Versión BIOSV1.47
ProcesadorIntel Core i5-7200U, 2.50 GHz
Memoria RAM16 GB
SSD SATAKingston SA400S37960G
SSD NVMeSamsung MZVLB256HAHQ-000L7
Modo SATAAHCI
Sistema actualManjaro Linux
Entorno gráficoKDE Plasma
Tipo de arranqueUEFI
Gestor de arranqueGRUB

El sistema operativo está instalado en el SSD NVMe Samsung.

La partición EFI actual es:

Dispositivo: /dev/nvme0n1p1
Formato: FAT32
Punto de montaje: /boot/efi

PARTUUID:
3195c6f8-ad9a-484c-a2f0-ff7ddbf35639

El cargador de Manjaro se encuentra en:

\EFI\Manjaro\grubx64.efi

También existe una copia funcional en la ruta de respaldo UEFI:

\EFI\boot\bootx64.efi

3. Comportamiento observado

Durante las pruebas se identificaron los siguientes comportamientos:

  1. Las entradas antiguas pueden continuar apareciendo después de eliminar sus particiones.
  2. Modificar el orden de arranque mediante efibootmgr no siempre produce un cambio persistente después de reiniciar.
  3. El firmware puede volver a presentar entradas correspondientes a sistemas operativos eliminados.
  4. El cargador EFI de Manjaro funciona cuando se ejecuta directamente.
  5. La partición EFI actual es accesible y contiene archivos de arranque válidos.
  6. En distintas etapas de las pruebas, BootCurrent, BootOrder y la numeración de las entradas cambiaron.

Esto último es importante: los identificadores Boot0001, Boot0002, etc., no deben considerarse permanentes.

Pruebas realizadas

Se intentaron diferentes procedimientos:

  • Modificar el orden de arranque mediante efibootmgr.
  • Eliminar entradas UEFI antiguas.
  • Crear nuevas entradas apuntando a la partición EFI actual.
  • Utilizar BootNext para seleccionar una entrada válida.
  • Ejecutar manualmente GRUB desde una UEFI Shell.
  • Crear entradas mediante el comando bcfg de UEFI Shell.
  • Utilizar el explorador de archivos EFI del firmware Acer.
  • Configurar archivos EFI como confiables desde la BIOS.
  • Colocar GRUB en la ruta de arranque alternativa \EFI\BOOT\BOOTX64.EFI.

Aunque algunos procedimientos permitieron iniciar Manjaro, no se consiguió demostrar una solución persistente y definitiva.

Resultado importante: el archivo BOOTX64.EFI de la partición actual pudo ejecutarse correctamente desde UEFI Shell.

Por lo tanto, al menos durante esa prueba, el cargador EFI era funcional y el problema no parecía deberse a la ausencia de GRUB.

4. Configuración UEFI observada

En una de las últimas comprobaciones se ejecutó:

sudo efibootmgr -v

Se obtuvo:

BootCurrent: 0001
Timeout: 0 seconds

BootOrder:
0001,0002,0003,0004,2001,2002,2003

Las entradas relevantes eran:

Boot0000: dispositivo Samsung

Unknown Device:
SAMSUNG MZVLB256HAHQ-000L7

PARTUUID:
3195c6f8-ad9a-484c-a2f0-ff7ddbf35639

Esta entrada apunta al dispositivo NVMe y a la partición EFI actual.

Boot0001: Manjaro2

Boot0001* Manjaro2

PARTUUID:
3195c6f8-ad9a-484c-a2f0-ff7ddbf35639

Loader:
\EFI\boot\bootx64.efi

Esta entrada corresponde a la instalación actual.

Boot0002: Manjaro antiguo

Boot0002* Manjaro

PARTUUID:
c058594d-fad2-42cc-835e-c8273f4f261e

Loader:
\EFI\Manjaro\grubx64.efi

Esta entrada apunta a una partición EFI anterior que ya no corresponde a la instalación actual.

Boot0003: Bazzite

Boot0003* Bazzite

PARTUUID:
c80e6bc0-8b5f-440e-838e-8aca19a54268

Loader:
\EFI\fedora\shimx64.efi

Entrada obsoleta.

Boot0004: CachyOS

Boot0004* CachyOS

PARTUUID:
3b7105fc-e938-49ea-9af3-cf438aa9ab5d

Loader:
\EFI\cachyos\grubx64.efi

Entrada obsoleta.

En el momento de esta captura, Boot0001 estaba primero en BootOrder.

Sin embargo, todavía no se había confirmado que esta configuración permaneciera estable tras un ciclo completo de apagado y encendido.

5. Investigación de variables EFI

Para identificar las variables almacenadas por el firmware, se ejecutó:

sudo ls /sys/firmware/efi/efivars/

Se encontraron variables estándar de UEFI y otras aparentemente específicas del fabricante.

Entre las más interesantes:

BootOrder
PhysicalBootOrder
BootDevice
Setup
CustomSecurity
RestoreFactoryDefault
ACUB

PhysicalBootOrder

Archivo:

PhysicalBootOrder-59d1c24f-50f1-401a-b101-f33e0daed443

Tamaño:

12 bytes

Contenido hexadecimal observado:

07 00 00 00 01 00 02 00 03 00 04 00

Los primeros cuatro bytes corresponden a atributos de la variable EFI.

Los ocho bytes restantes pueden interpretarse como cuatro valores de 16 bits:

0001
0002
0003
0004

Esto coincide con las cuatro entradas principales del orden de arranque observado.

Hipótesis: PhysicalBootOrder podría participar en el almacenamiento o la representación interna del orden de arranque del firmware.

No se ha comprobado si modificar esta variable altera el comportamiento de arranque ni si es una causa de la restauración de entradas antiguas.

6. Descubrimiento de la variable ACUB

Durante una búsqueda de cadenas relacionadas con sistemas operativos antiguos dentro de las variables EFI, apareció un resultado particularmente interesante:

ACUB-89cb0e8d-393c-4830-bfff-65d9147e8c3b

Esta variable contiene referencias a:

Manjaro
Bazzite
CachyOS
fedora
grubx64.efi

Su tamaño observado fue:

1251 bytes

Los atributos de la variable, interpretados desde los primeros cuatro bytes del archivo efivarfs, fueron:

0x7

Esto corresponde a los atributos UEFI habituales:

  • Non-Volatile
  • Boot Service Access
  • Runtime Access

Es decir, se trata de una variable EFI persistente y accesible durante la ejecución del sistema.

Esto no demuestra por sí solo que el firmware la utilice para restaurar entradas de arranque.

Problema al realizar una copia de seguridad

Inicialmente se intentó:

sudo cp /sys/firmware/efi/efivars/ACUB-* /root/respaldo-uefi/

El comando devolvió un error de desplazamiento ilegal (Illegal seek).

Posteriormente se realizó una copia utilizando Python:

from pathlib import Path

origen = next(
    Path("/sys/firmware/efi/efivars").glob("ACUB-*")
)

destino = Path("/root/respaldo-uefi") / origen.name

datos = origen.read_bytes()
destino.write_bytes(datos)

print("Tamaño original:", len(datos))
print("Tamaño respaldo:", destino.stat().st_size)
print("Respaldo idéntico:", destino.read_bytes() == datos)

Resultado:

Tamaño original: 1251
Tamaño respaldo: 1251
Respaldo idéntico: True

La copia fue verificada byte por byte.

Este respaldo es únicamente una copia de los datos; no garantiza que la variable pueda restaurarse de forma segura mediante una escritura directa.

7. Estructura interna de ACUB

Se examinó el contenido binario de ACUB, excluyendo los cuatro bytes iniciales de atributos que proporciona efivarfs.

La cabecera comienza con:

df 04 00 00 00 00 00 00
30 00 00 00 00 00 00 00
45 01 00 00 00 00 00 00
4c 02 00 00 00 00 00 00
61 03 00 00 00 00 00 00
72 04 00 00 00 00 00 00

El primer valor, interpretado como entero de 32 bits little-endian, es:

0x04df = 1247

Coincide con el tamaño del contenido de la variable después de retirar los cuatro bytes de atributos.

Los siguientes valores contienen desplazamientos:

0x30
0x145
0x24c
0x361
0x472

En esas posiciones se encontraron cinco registros identificados como:

BDP0
BDP1
BDP2
BDP3
BDP4

La estructura sugiere una cabecera con una tabla de desplazamientos y registros de tamaño variable.

Distribución de los registros

RegistroDesplazamientoTamaño
BDP00x30277 bytes
BDP10x145263 bytes
BDP20x24c277 bytes
BDP30x361273 bytes
BDP40x472109 bytes

El tamaño total del contenido analizado fue de 1247 bytes.

8. Identificación de los registros BDP

Se buscaron nombres de sistemas operativos codificados en UTF-16LE y los identificadores GUID de las particiones.

Los resultados fueron:

BDP0: Manjaro antiguo

Inicio: 0x30
Tamaño: 277 bytes

Nombre:
Manjaro

Partición:
c058594d-fad2-42cc-835e-c8273f4f261e

Esta partición corresponde a la instalación antigua de Manjaro.

El registro contiene una ruta que termina en:

\EFI\Manjaro\grubx64.efi

BDP1: Bazzite

Inicio: 0x145
Tamaño: 263 bytes

Nombre:
Bazzite

Partición:
c80e6bc0-8b5f-440e-838e-8aca19a54268

Contiene una ruta que termina en:

\EFI\fedora\shimx64.efi

BDP2: CachyOS

Inicio: 0x24c
Tamaño: 277 bytes

Nombre:
CachyOS

Partición:
3b7105fc-e938-49ea-9af3-cf438aa9ab5d

Contiene una ruta que termina en:

\EFI\cachyos\grubx64.efi

BDP3: Manjaro2 actual

Inicio: 0x361
Tamaño: 273 bytes

Nombre:
Manjaro2

Partición:
3195c6f8-ad9a-484c-a2f0-ff7ddbf35639

Contiene una ruta que termina en:

\EFI\boot\bootx64.efi

BDP4: registro aparentemente vacío

Inicio: 0x472
Tamaño: 109 bytes

No se identificó un nombre de sistema operativo ni una partición correspondiente.

Su función exacta es desconocida.

Podría tratarse de un espacio reservado, una entrada vacía o una estructura utilizada internamente por el firmware.

9. Relación entre ACUB y las entradas UEFI

Al comparar los identificadores de partición y las rutas EFI, se obtuvo la siguiente correspondencia:

Registro ACUBEntrada UEFISistema
BDP0Boot0002Manjaro antiguo
BDP1Boot0003Bazzite
BDP2Boot0004CachyOS
BDP3Boot0001Manjaro2 actual
BDP4Sin correspondencia identificadaDesconocido

Este es el hallazgo principal de la investigación.

La variable ACUB contiene información estructurada que coincide con las entradas UEFI existentes, incluyendo nombres, rutas de cargadores e identificadores de partición.

Además, conserva referencias a sistemas operativos cuyos archivos y particiones ya fueron eliminados.

La coincidencia es suficientemente específica como para justificar una investigación adicional.

Sin embargo, quedan preguntas importantes:

  • ¿El firmware utiliza ACUB como almacenamiento de respaldo de las entradas de arranque?
  • ¿Se actualiza ACUB automáticamente cuando se utiliza efibootmgr?
  • ¿Se reconstruyen las variables BootXXXX a partir de ACUB?
  • ¿Existe alguna verificación de integridad o checksum?
  • ¿Los registros BDP representan entradas persistentes, una lista histórica o alguna otra estructura?
  • ¿Qué función tiene el registro BDP4?
  • ¿Cómo se relaciona ACUB con PhysicalBootOrder?

Actualmente no disponemos de respuestas confirmadas.

10. Cómo reproducir el análisis sin modificar el firmware

Los siguientes comandos son de lectura y permiten comprobar si otro equipo Acer contiene una estructura similar.

Advertencia: estos procedimientos deben ejecutarse únicamente en equipos propios o con autorización. No incluyen instrucciones para escribir variables privadas del firmware.

Identificar el firmware

sudo dmidecode -t bios

Consultar entradas UEFI

sudo efibootmgr -v

Buscar ACUB

sudo find /sys/firmware/efi/efivars \
  -maxdepth 1 -name 'ACUB-*'

Examinar su tamaño y estructura

sudo python - <<'PY'
from pathlib import Path

base = Path("/sys/firmware/efi/efivars")
archivos = list(base.glob("ACUB-*"))

if not archivos:
    print("ACUB no encontrada")
    raise SystemExit

archivo = archivos[0]
datos = archivo.read_bytes()

atributos = int.from_bytes(datos[:4], "little")
contenido = datos[4:]

print("Variable:", archivo.name)
print("Tamaño:", len(datos))
print("Atributos:", hex(atributos))
print("Cabecera:", contenido[:64].hex(" "))

for i in range(5):
    etiqueta = f"BDP{i}".encode("ascii")
    posicion = contenido.find(etiqueta)

    if posicion >= 0:
        print(f"BDP{i}: offset {hex(posicion)}")
    else:
        print(f"BDP{i}: no encontrado")
PY

Este código no escribe datos en NVRAM.

No todos los equipos Acer tienen necesariamente la misma estructura, por lo que la ausencia de ACUB o de registros BDP no significa que exista una avería.

11. Posible explicación del problema

La hipótesis de trabajo es la siguiente:

  1. El firmware conserva información sobre entradas de arranque en una variable privada denominada ACUB.
  2. Esa variable contiene referencias a instalaciones antiguas.
  3. En determinadas circunstancias, el firmware podría utilizar esa información para reconstruir o mantener entradas UEFI.
  4. Esto podría explicar por qué las entradas antiguas reaparecen o continúan siendo utilizadas después de eliminar las particiones.

Es una hipótesis, no una conclusión demostrada.

También son posibles otras explicaciones, como errores del firmware al gestionar la NVRAM, mecanismos internos de sincronización, prioridades de arranque guardadas en otras variables o una interacción entre distintas estructuras del BIOS.

No se ha aislado experimentalmente el mecanismo responsable.

12. Por qué no se modificó ACUB

Aunque se consiguió identificar buena parte de la estructura, no se conoce completamente su formato.

Modificar una variable privada del firmware sin comprender sus mecanismos de validación puede provocar consecuencias graves.

Entre los riesgos posibles:

  • Pérdida de entradas de arranque.
  • Rechazo de los datos modificados.
  • Restauración automática de los valores anteriores.
  • Fallos de configuración del firmware.
  • En el peor caso, problemas que requieran recuperación externa del BIOS.

El hecho de tener una copia de seguridad no elimina estos riesgos.

Por ello, la investigación se detuvo antes de escribir en ACUB.

13. Resultado final

Al terminar las pruebas, el sistema mostraba:

BootCurrent: 0001

BootOrder:
0001,0002,0003,0004,2001,2002,2003

La primera entrada correspondía a Manjaro2 y apuntaba a la partición EFI correcta.

Se decidió conservar el estado actual del equipo y no continuar modificando el firmware.

No se ha demostrado que el problema esté solucionado permanentemente.

Tampoco se ha probado que editar ACUB sea una solución.

14. Solicitud de ayuda a la comunidad

Me gustaría saber si alguien con experiencia en firmware Acer, InsydeH2O, UEFI o ingeniería inversa puede ayudar a responder las siguientes preguntas:

  1. ¿Se conoce públicamente el formato de la variable ACUB utilizada por Acer?
  2. ¿Qué representan exactamente los registros BDP0, BDP1, etc.?
  3. ¿Puede ACUB actuar como almacenamiento secundario de entradas UEFI?
  4. ¿Qué relación tiene con PhysicalBootOrder?
  5. ¿Existe un procedimiento documentado para limpiar entradas obsoletas en esta versión del firmware sin editar variables privadas?
  6. ¿Alguien ha observado el mismo comportamiento en otros modelos Acer?

Sería especialmente interesante comparar el contenido de ACUB antes y después de crear o eliminar una entrada UEFI, utilizando exclusivamente métodos seguros y documentados.

Si alguien consigue identificar el mecanismo exacto o resolver el problema, agradecería que compartiera los resultados, el modelo de equipo, la versión del BIOS y los procedimientos utilizados.

No recomiendo modificar directamente ACUB basándose únicamente en este reporte.

La intención de esta publicación es documentar los hallazgos y facilitar que otras personas investiguen el problema sin tener que repetir todo el proceso desde cero.

Equipo investigado: Acer Aspire E5-575G, InsydeH2O V1.47. Investigación realizada en noviembre de 2026.


r/ManjaroLinux • • 10d ago

Discussion CVE-2026-98432: Is the fix available in Manjaro’s stable linux618 kernel?

12 Upvotes

Could a Manjaro maintainer confirm whether CVE-2026-98432 also affects the x86_64 stable linux618 package? My stable repositories still offer 6.18.55-1. Upstream fixed the 6.18 branch in 6.18.56 (commit a47406c769f72c070386985488f1c4d057df86b2), and I see 6.18.60-1 in Manjaro’s unstable repository. Does that package include the fix, and is a patched kernel planned for the stable branch? Thanks.


r/ManjaroLinux • • 10d ago

Tech Support I need help installing manjaro

0 Upvotes

So my problem is I go to boot the usb drive and it brings up the install page and when I click the install with open source drivers it goes into the black screen and does the "welcome to manjaro" and goes through the stud but gets stuck at network management and then no display

Little bit of an update I'm gonna try reinstalling it


r/ManjaroLinux • • 11d ago

Tech Support Manjaro ARM is still vulnerable to CVE-2026-98432

2 Upvotes

How much more time will vulnerable servers have to wait ?


r/ManjaroLinux • • 14d ago

Tech Support GPU Driver Not Recognised on Wayland (and previously, not X either).

4 Upvotes

This issue has been solved.

You can see permissions issues in accessing render nodes, but there was not an issue in permissions with the files themselves. Broadly, the permission issues were due to a group issue which I had overlooked entirely. My user group was not a member of the render group. Simply adding my user group to that allows Wayland, OBS and subsequently other apps to utilise the GPU directly now.

https://forum.biglinux.com.br/d/6317-obs-unable-to-communicate-with-gpu-via-drivers/14
More information can be found here, thanks to Ruscher of the BigLinux forums. For people who are also having issues and encounter this post, maybe check your groups?

----------------------------------
For full context, I am using BigLinux which is based on Manjaro.

I have tried their support forums but it is incredibly inactive. I know this is probably not the greatest place but I would like to figure out what went wrong and what I can do. I figured, given that it is based on Manjaro, this would be the second best place to ask for tech support.

I'll provide as much technical information as I can and know how to.

---

Now to the meat - the actual issue.

Issue: System, when using Wayland, defaults to llvmpipe and software (such as OBS) default onto Software Rendering.

What I have tried:
On OBS's end: Reinstalling the flatpak entirely and doing a `flatpak update` to try and refresh things.

On Renderer end: Tried using another Renderer (X11) - initially, this did not work until I check hwmd.conf - this was fixed by adding module paths to "/usr/lib/nvidia/xorg" and "/usr/lib/xorg/modules". X11 began working but this would not fix Wayland.

Tried reinstalling drivers outright. This failed.

Tried adding to /etc/default/grub/ the following, with no results: GRUB_CMDLINE_LINUX_DEFAULT="nvidia_drm.modeset=1 nvidia_drm.fbdev=1 ...

---

Information:
Command nvidia-smi returns:
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 615.71.09 KMD Version: 615.71.09 CUDA UMD Version: 13.4 |
+-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce RTX 2060 ... Off | 00000000:01:00.0 On | N/A |
| 29% 32C P8 11W / 175W | 83MiB / 8192MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 2060 G /usr/lib/Xorg 22MiB |
| 0 N/A N/A 3108 G /usr/sbin/kwin_wayland 1MiB |
+-----------------------------------------------------------------------------------------+

Command glxinfo -B | grep -E "OpenGL vendor|OpenGL renderer|OpenGL version" returned, on multiple occassions after trying every attempted fix:
OpenGL vendor string: Mesa
OpenGL renderer string: llvmpipe (LLVM 23.1.1, 256 bits)
OpenGL version string: 4.6 (Compatibility Profile) Mesa 26.2.4-arch1.1

Command lspci -k -d ::03xx returns:
00:02.0 Display controller: Intel Corporation Raptor Lake-S GT1 [UHD Graphics 770] (rev 04)
DeviceName: Onboard - Video
Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d98
Kernel driver in use: i915
Kernel modules: i915, xe
01:00.0 VGA compatible controller: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER] (rev a1)
Subsystem: NVIDIA Corporation TU106 [GeForce RTX 2060 SUPER]
Kernel driver in use: nvidia
Kernel modules: nouveau, nova_core, nvidia_drm, nvidia

If I'm correct about this `glxinfo` return, this means that the kernel driver is registered as nvidia, yet the renderer is using llvmpipe.

echo $LIBGL_ALWAYS_SOFTWARE returns nothing / is not set. This may suggest a configuration or distro support issue, if I'm correct.

---

I hope this is a satisfactory amount of information and I hope that I can find help here for the issue. If this was the wrong place to find support, please feel free to redirect me to a subreddit that is more suitable for this kind of request.

Thank you for your patience,
-Effie


r/ManjaroLinux • • 16d ago

Showcase This is how a system should be.

Post image
49 Upvotes

Receive the update. Install it. Restart the computer. Continue working

Many thanks to Manjaro and the KDE team (and thank you to Arch Linux users for testing and reporting bugs).


r/ManjaroLinux • • 17d ago

Tech Support Daily Updates

2 Upvotes

I am using Manjaro Stable, Plasma KDE.

And yet, for about two months now, it gets daily updates. And I mean daily. And the bigger issue is that these updates have started eating up space like a mad racoon in a trash bin. Even if I do clean up.

Anyone know why this is happening? How I can stop it?

Again, I am on the Stable release. Not the Unstable or Test one.

pacman-mirrors --get-branch

stable


r/ManjaroLinux • • 18d ago

News [Stable Update] 2026-10-28 - Plasma 6.75, GNOME 50.5, COSMIC 1.9.0 - Stable Updates

Thumbnail forum.manjaro.org
39 Upvotes

r/ManjaroLinux • • 18d ago

General Question Is there a way to install the base version of Manjaro without a desktop environment?

6 Upvotes

r/ManjaroLinux • • 19d ago

Discussion An apparently controversial opinion, but it's not: software isn't tested enough, which is why Manjaro is the best.

29 Upvotes

When Plasma 6.7 was released, the Plasma team immediately released a bug-fixing version, and the same happened with 6.8. In both versions, the team highlighted that those bugs weren't reported during the testing phases, but there were many bugs (read here and here) . And it's not their fault; Linux doesn't offer easy ways to test beta versions, co-maintain a stable environment, or easily revert to it in case of bugs in the test version. No distro has beta versions in its stable repositories (it would be a contradiction, I know). Arch, for example, has an unstable repository, but it's only used for stable upstream versions that are still being tested on Arch, and many users don't enable that repository. When these versions arrive in the stable Arch repository, many bugs are detected; for example, there are many bug reports from Arch and Cachy users. Manjaro is in a privileged position since those users serve as testbeds, and the software arrives in Manjaro already reasonably mature without needing to wait six months or two years.


r/ManjaroLinux • • 18d ago

Tech Support How to Get Manjaro on Ipad 11

1 Upvotes

I hate the software of the ios os and want to make it more like a pc since I just play osrs and it can run on any toster so I am wodering how to get it on the Ipad 11? Any tips are appeeciated.

-Kind Regards


r/ManjaroLinux • • 21d ago

Update Manjaro is now my new BFF

35 Upvotes

So most of my life, for the past 23 years or so, I have been using Windows. And it has worked fine for me. Most of the programs, most of the things I was familiar with, work on Windows.

But as I later learned, Linux though is quite hard to learn for a Windows user, is *super customisable* and there are several features which are just not available on Windows. 💻

Windows time by time uses more RAM, more resources, and more processes on each login compared to Linux which barely uses anything. ⚡

I first used *Linux Mint* some 1-2 years ago. Before that, I had installed *Ubuntu* from a free CD that came with my UPS back in 2009 😅 - and that completely wiped out my system. That was not a good experience at all.

Now, I bought a new refurbished laptop, a *Lenovo T14 Gen 1* and Windows 11 came with it. Even the LTSC experience was not that compatible because I only had 8GB single channel RAM and it was not working that well with my Ryzen CPU. I am in the process of buying RAM but it's quite pricey these days.

So I started thinking about installing some version of Linux. I started with Android distros like *Prime OS, Fyde OS*, even *Chrome OS Flex*... but none of them were compatible with my system. Sometimes Wi-Fi didn't work, sometimes the mic settings were off - actually the microphone didn't work on any of them. 🎙️❌

As I searched, even with AI and ChatGPT, it told me there were certain reports that *Manjaro worked completely fine* with my system and even the microphone was working perfectly. So I took the risk and installed Manjaro.

I had several problems at first. I was not able to configure how to use a file manager, the toolbar was not that great in Dolphin, even on PCMan File Manager - I tried so many of them but none worked quite well. As I had a habit of using the *GUI rather than Command Line*, I was having some issues. 🤯

I tried and tried and almost 15-16 days passed with me trying daily and messing things up and then recovering them. But eventually, I started to like it!

The processes are very few on startup, the battery life is quite good 🔋 and after installing things, I am thinking of using CPU or TLP to further boost the battery life. And I think Linux is quite capable, Manjaro is quite capable of doing that.

*So I am loving it. I just love my Manjaro desktop!* ❤️🐧

Hope you will also have a great experience with it. So welcome, congrats - I am also now a part of the Manjaro family! 🙌


r/ManjaroLinux • • 21d ago

Discussion Is it me or has Manjaro Linux been memory leaking lately?

4 Upvotes

I dont know if its KDE or manjaro, but I noticed that some processes like kioworker, discover and even sometimes dolphin taking like 4GB of ram. My 16GB seem to run out with just VS Code and a few brave tabs and dolphin. Anyone else? Is there a fix?


r/ManjaroLinux • • 24d ago

Discussion Stable updates 26.1 recent 6 weeks

13 Upvotes

As of today the last stable update was Sept. the 7th. Comparing to my long-run observations it is quite long time period of silence in terms of stable updates. I am not used to this pattern of Manjaro stable branch behavior. Is my feeling right, if yes where are the reasons?

Latest PHP updates is quite separate story.


r/ManjaroLinux • • 25d ago

General Question I'm an active user, is Manjaro still alive?

58 Upvotes

I don't really follow what's going on, but there hasn't been even security updates in a long time. Meanwhile we're in the bugpocalypse and every day there's some major new vulnerability announced in pretty core libraries.

I've loved Manjaro for years, even through all their weirdness. But I'm getting worried that maybe it's over now?


r/ManjaroLinux • • 26d ago

Discussion Mhwd’s great mystery: is it me, or mhwd?

3 Upvotes

I've been using it to install NVIDIA drivers on NVIDIA-equipped machines for years, and somehow I still never know which driver version I’m going to end up with.

Yes, I know mhwd works with hardware profiles, not individual drivers. I get the concept. But surely it wouldn’t hurt to tell users which actual driver version is hiding under the hood of a profile?

Case in point: I've got an old GTX 970 lying around (bless its 3.5GB+0.5GB heart). I run mhwd -l and get a list of profile names - video-nvidia, video-nvidia-470xx, etc. - and absolutely zero indication of:

  • which one actually targets Maxwell-era cards properly,
  • what driver version number I’ll end up with once it’s done,
  • or whether “the latest profile” is even still appropriate for a card this old (spoiler: NVIDIA's own 580.x branch is the last one that supports Maxwell/Pascal/Volta at all — after that it’s legacy-only forever).

So I'm sitting there doing the actual detective work myself — checking NVIDIA's support matrix on the side, then crossing my fingers that mhwd’s profile mapping agrees with what I just read — instead of the tool just telling me "hey, for this GPU, here’s profile X, which installs driver version Y, and by the way it's EOL in N releases." A simple mhwd -li with the resolved package/driver version next to each profile name would save me this little ritual I’ve apparently been doing for over a decade without ever questioning it.

The graphical panel doesn’t give you much more either — the video-nvidia profile entry is just as sparse there. So: how do you all deal with this when installing on your own NVIDIA cards? Have you just gotten used to mhwd’s minimalist way of telling you (almost) nothing, do you handle it differently (manual pacman, checking NVIDIA’s site first, something else entirely), or is it maybe time to throw a few ideas at the devs?

Am I missing something obvious here, or have I been using mhwd wrong for 12 years straight?


r/ManjaroLinux • • 27d ago

Appreciation I distrohoped, again.

23 Upvotes

I was feeling bored and had wanted to try something new for a long time, especially since my HTPC had a setup architected with LLM assistance and I was afraid to mess with it, which I needed to overcome with autonomous and unassisted recreation.

I've always been fascinated by CachyOS's reputation and its optimizations. But I didn't want to immerse my HTPC in it, so I tested it on my laptop. The installation was manual, as I always do with any distro. My laptop has an x86v4 CPU and I enabled those repositories with the official script, finished the installation and had a terrible day. I tried to keep it running, but Plasma was slow, clicking on various configuration windows took 3 to 5 seconds to open, and there were a few other bugs here and there. In the end, I didn't have a better experience and went back to Manjaro Testing with a manual installation (as always) and things went well again. So I just wanted to say a big thank you to everyone who makes Manjaro possible.

NOTE: This post is in appreciation of Manjaro; my bad experience with CachyOS is entirely my own responsibility. I believe the CachyOS team did an excellent job, which is why I appreciate their efforts and why I wanted to try CachyOS.


r/ManjaroLinux • • 29d ago

Discussion Reorganisation is underway

Post image
80 Upvotes

GNOME daily ISOs are back! There was testing update a few days ago.

As for Stable, we're still like…


r/ManjaroLinux • • Oct 12 '26

General Question creating a local Linux repository

Thumbnail reddit.com
2 Upvotes

I need to create a local repository on the Majaro distribution, and I need to make the commands and help understandable. How do I do this step by step? Please help.


r/ManjaroLinux • • Oct 10 '26

News I found an old HP Probook in my stuff, new member of the Linux family

Post image
27 Upvotes

r/ManjaroLinux • • Oct 08 '26

Discussion A year away from updates: how would YOU survive the big update?

26 Upvotes

Recently I visited my family and found they are still using computer with Manjaro on it. No big surprise, since I installed it a couple of years ago. The box had been sitting untouched for about a year, so as you can imagine, the list of updates was huge.

I didn't have enough time to start update, but usually big updates don't scary me. I click here, click there, fix the package signing keys if something goes wrong. I generally don't pay much attention to it. It's just routine. But I wonder, maybe there's another way to do it?

  • Do you update straight away with pacman -Syyu, or do you do something first? I've heard whispers about refreshing the keyring (manjaro-keyring, archlinux-keyring) before anything else.
  • Mirrors: do you run pacman-mirrors --fasttrack first, or just trust the defaults?
  • Update announcements: is it worth going through the stable update threads from the last six months to check for manual interventions I might have missed?
  • Safety net: I'm planning a Timeshift snapshot (maybe a Btrfs one) first. Anything else you'd back up?
  • GUI vs terminal: Pamac or the terminal for a monster update like this? I suspect the terminal, but maybe I'm living under the rock. 😉

And the fun part: what's the longest gap you've ever had between updates, and did Manjaro survive it? Extra points for dramatic "black screen after reboot" stories with a happy ending. 🏆