** Changed in: gnome-remote-desktop (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2033939
Title:
RDP remote desktop connection stopped working using mstsc
gnome-remote-desktop-45 is not compatible with mutter-46. All you need
to do is use a system with the NVIDIA driver, run g-r-d-45 with
mutter-46 and you either run into a black screen, or you might see an
initial frame but no updates (freezed screen).
--
You received this bug notification
To provide some context, when this crash can happen: It can happen, after
attempting to start a remote desktop session, when the screen is locked.
In such case, g-s directly refuses the start request and therefore the lifetime
of the rdpgfx thread in FreeRDP is very short.
The journal message
Note: 2.7.0 does **NOT** contain https://github.com/FreeRDP/FreeRDP/pull/7836
(which should fix
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970994),
because 2.7.0 was released before that MR was created and merged.
So you have to either apply
I don't think a package recommendation is the right thing here. Instead,
the package containing fuse3 and fusermount3 should here be a package
dependency of the gnome-remote-desktop package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
As for the RDP connection problem, please provide enough information.
If you have an updated system, then your FreeRDP build should contain the NTLM
fixes. Jeremy afaik backported them to Ubuntu in
https://bugs.launchpad.net/ubuntu/+source/freerdp2/+bug/1968577.
Meanwhile, FreeRDP-2.7.0 was
To be honest, the issue description is insufficient and the crash file useless.
The stacktrace does not contain any debug symbols and for the "sometimes shows
screen garbage before disconnecting" part, a screenshot would be needed,
because the screen content is not just garbage.
It has a
While the fix here is correct, the assumptions in this issue are wrong.
I wrote an explanation of this issue in
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-
desktop/+bug/1970039/comments/7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yeah, this issue here is a duplicate of the bug mentioned in comment 6. Jeremy
submitted a patch, which sufficiently fixed the issue in
https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1286 (it
should technically check for other aspects too), but for now it is sufficient.
Marco, Jeremy, while this issue is fixed. You need to adjust the .deb pkg to
depend on Fuse3.
Currently, it is not done and therefore crashes for some people:
https://errors.ubuntu.com/problem/a35f108a1822440799804a3dad6f5ef4a53fec4f
This was also reported in https://bugs.debian.org/cgi-
This was fixed in https://bugs.launchpad.net/ubuntu/+source/gnome-
control-center/+bug/1968518
** Changed in: gnome-remote-desktop (Ubuntu Jammy)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Me (upstream g-r-d) already predicted this, as soon as I saw that Ubuntu
ships mixed versions (gnome-control-center-41 (g-c-c) for GNOME 42
(that's unsupported upstream and as seen here breaks things)).
For GNOME 42, we finally switched over to the RDP backend in g-r-d. As a result
the UI in
12 matches
Mail list logo
