> 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/other-resources/life-cycle-policies/remote-desktop-manager/remote-desktop-manager-linux-life-cycle-policy.md). # Remote Desktop Manager Linux life cycle policy The Remote Desktop Manager Linux life cycle policy lists supported distributions such as Ubuntu, RHEL, and Manjaro and required packages. Remote Desktop Manager Linux supports a range of widely-used Linux distributions, including Ubuntu, RHEL, and Manjaro. These distributions have been thoroughly tested. While Remote Desktop Manager Linux may also function on other distributions, they have not undergone official testing. Devolutions shall not be liable for any failure, inability to perform, or performance issues arising due to the use on unsupported or outdated distributions, and reservices the right, at its sole discretion, to determine the support end date for such distributions. Please be aware that the availability of certain libraries or packages that are essential for Remote Desktop Manager Linux may vary across different Linux distributions. Below is a list of critical packages required for the proper functioning of Remote Desktop Manager Linux: * glibc 2.29 or later * libwebkit2gtk-4.0 or 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/other-resources/life-cycle-policies/remote-desktop-manager/remote-desktop-manager-linux-life-cycle-policy.md?ask=&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.