Package: gnome-remote-desktop
Version: 0.1.9-5
Severity: important

Dear Maintainer,

Since the update to Bullseye I've been unable to use remote desktop.
Besides an issue for multiple daemons to open a port (vino-server used
to take the next available ports when running multiple sessions), I've
also been unable to get it to even display something remotely. I get a
blank screen, and although I can move the mouse it's limited to the
first monitor only (I fear even if the display problem was fixed I would
still get issues...)

Today I really needed it and while looking into the old package realized
it's still these, and simply running:

/usr/libexec/vino-server --sm-disable

Got me remote desktop back. Now I've added it as a startup app for my
sessions, replacing the new gnome package.

TBH I'm not sure I'm even reporting at the right place, I'm going to ask
Gnome to fix all their issue overnight, but the switch was sudden and
broke a woring component.

I think there should be a way to select the remote desktop server to use
with Gnome, and it should be sufficiently advertised for normal users to
find it.

Note that I'm still using Xorg - Wayland has caused many issues in the
past... I'm still getting recoverable gnome-shell issues that would log
me out under Wayland (pretty rare though), and it doesn't behaves with
other applications I have to use for work.

Also I don't expect to be able to access backgrounded sessions, except
by doinf a chvt from the shell first. But by having a remote desktop
session per gnome session I can always connect to an active one.

   * What led up to the situation?

   Upgrade to Bullseye

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

   Disabling remote desktop in Gnome Settings and Starting the old
   vino-server instead.

   * What was the outcome of this action?

   Working remote desktop

   * What outcome did you expect instead?

   Ideally, gnome-remote-desktop should work like vino-server did, but I
   would have at least expected to have the choice if there were known
   issues.


-- System Information:
Debian Release: 11.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 
'stable-debug'), (500, 'proposed-updates-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.10.0-14-amd64 (SMP w/4 CPU threads)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-remote-desktop depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.38.0-2
ii  gnome-shell                                  3.38.6-1~deb11u1
ii  libc6                                        2.31-13+deb11u3
ii  libcairo2                                    1.16.0-5
ii  libfreerdp2-2                                2.3.0+dfsg1-2+deb11u1
ii  libglib2.0-0                                 2.66.8-1
ii  libmutter-7-0                                3.38.6-2~deb11u2
ii  libnotify4                                   0.7.9-3
ii  libpipewire-0.3-0                            0.3.19-4
ii  libsecret-1-0                                0.20.4-2
ii  libvncserver1                                0.9.13+dfsg-2
ii  libwinpr2-2                                  2.3.0+dfsg1-2+deb11u1
ii  pipewire                                     0.3.19-4

gnome-remote-desktop recommends no packages.

gnome-remote-desktop suggests no packages.

-- no debconf information

Reply via email to