> 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/fr/other-resources/life-cycle-policies/remote-desktop-manager/remote-desktop-manager-linux-life-cycle-policy.md).

# Politique de cycle de vie de Remote Desktop Manager Linux

La politique de cycle de vie de Remote Desktop Manager Linux énumère les distributions prises en charge telles qu'Ubuntu, RHEL et Manjaro ainsi que les paquets requis.

Remote Desktop Manager Linux prend en charge un éventail de distributions Linux largement utilisées, dont Ubuntu, RHEL et Manjaro. Ces distributions ont été rigoureusement testées.

Bien que Remote Desktop Manager Linux puisse également fonctionner sur d'autres distributions, celles-ci n'ont pas fait l'objet de tests officiels. Devolutions ne pourra être tenue responsable de toute défaillance, incapacité de fonctionner ou problème de performance découlant de l'utilisation sur des distributions non prises en charge ou désuètes, et se réserve le droit, à sa seule discrétion, de déterminer la date de fin de prise en charge de telles distributions.

Veuillez noter que la disponibilité de certaines bibliothèques ou de certains paquets essentiels à Remote Desktop Manager Linux peut varier d'une distribution Linux à l'autre. Voici une liste des paquets critiques requis pour le bon fonctionnement de Remote Desktop Manager Linux :

* glibc 2.29 ou version plus récente
* libwebkit2gtk-4.0 ou 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 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/fr/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 `automate deployments from our CI pipeline` 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.