There is 1 open security issue in sid.
There is 1 open security issue in forky.
commit 494a478453c0204a4535163b8ceee33fb0e570f1
Author: Daniel van Vugt <daniel.van.vugt@canonical.com>
Date: Wed Feb 4 14:38:22 2026 +0800
debian/control: Recommend libmutter, but it's not a strict dependency
gnome-remote-desktop has no build-time or load-time dependencies on
any mutter code. It only has a runtime assumption that some display
server will be running that speaks a similar version of the DBus
protocol it relies on.
Certainly bumping the libmutter version from 17 (GNOME 49) to 18
(GNOME 50) only brings minimal additions to the protocol. And while the
protocol XMLs say:
> This API is private and not intended to be used outside of the integrated
> system that uses libmutter. No compatibility between versions are
> promised.
we can judge on a version-to-version basis what level of dependency is
really required.
This helps to avoid archive-wide blockages where we are needlessly waiting
for gnome-remote-desktop to be updated before a new libmutter can be
released.
There is 1 open security issue in trixie.
You can find information about how to handle this issue in the security team's documentation.
There is 1 open security issue in bookworm.
You can find information about how to handle this issue in the security team's documentation.
Automatic checks made by the Debian l10n team found some issues with the translations contained in this package. You should check the l10n status report for more information.
Issues can be things such as missing translations, problematic translated strings, outdated PO files, unknown languages, etc.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/g/gnome-remote-desktop.png){kind=link}