> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/resources/es/other-resources/life-cycle-policies/remote-desktop-manager/remote-desktop-manager-linux-life-cycle-policy.md).

# Política de ciclo de vida de Remote Desktop Manager Linux

La política de ciclo de vida de Remote Desktop Manager Linux enumera las distribuciones compatibles, como Ubuntu, RHEL y Manjaro, y los paquetes necesarios.

Remote Desktop Manager Linux es compatible con una amplia variedad de distribuciones de Linux de uso extendido, entre ellas Ubuntu, RHEL y Manjaro. Estas distribuciones se han probado exhaustivamente.

Aunque Remote Desktop Manager Linux también puede funcionar en otras distribuciones, estas no se han sometido a pruebas oficiales. Devolutions no será responsable de ningún fallo, imposibilidad de ejecución o problema de rendimiento derivado del uso en distribuciones no compatibles u obsoletas, y se reserva el derecho, a su entera discreción, de determinar la fecha de finalización del soporte para dichas distribuciones.

Tenga en cuenta que la disponibilidad de determinadas bibliotecas o paquetes que son esenciales para Remote Desktop Manager Linux puede variar entre las distintas distribuciones de Linux. A continuación se ofrece una lista de los paquetes críticos necesarios para el correcto funcionamiento de Remote Desktop Manager Linux:

* glibc 2.29 o posterior
* libwebkit2gtk-4.0 o libwebkit2gtk-4.1
* ca-certificates
* libsecret-1-0
* gnome-keyring
* libvte-2.91


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/resources/es/other-resources/life-cycle-policies/remote-desktop-manager/remote-desktop-manager-linux-life-cycle-policy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.