Bug#1109065: gnome-remote-desktop: blank screen after connecting to Mac Mini M2

[Daniel]

Le 11/07/2025 à 17:56, Simon McVittie a écrit :
> Control: retitle -1 gnome-remote-desktop: blank screen after 
> connecting to Mac Mini M2
> Control: reassign -1 gnome-remote-desktop
> Control: affects -1 + asahi-platform
> Control: severity -1 normal
>
> On Fri, 11 Jul 2025 at 16:22:49 +0200, Daniel wrote:
>> Le 11/07/2025 à 16:11, Simon McVittie a écrit :
>>> What I should have asked at the beginning is:
>>>
>>> Is there a user-visible symptom that you are reporting, like some 
>>> program crashing or taking a long time to start, that is in some way 
>>> related to the warning you have quoted?
>>
>> That's the logs I get when I try to connect to gnome-remote-desktop. 
>> On the client I'm asked to enter user, password and domain, once done 
>> I get a blank screen and those logs appear on the server.
>
> OK, if the user-visible symptom is "I try to remote-control my 
> computer with gnome-remote-desktop and the result is a blank screen", 
> please start with that. Package maintainers cannot know that you are 
> using gnome-remote-desktop unless you tell us!
If you read carefully the logs I sended at the time I opened this bug, 
g-r-d is clearly mentioned as well as the linux kernel version 
indicating asahi
>
> Please try upgrading to the remote desktop server to 
> gnome-remote-desktop 48.1-4 (currently in unstable but not in testing) 
> which is known to fix a bad interaction with newer versions of Mesa, 
> then reboot the remote desktop server and try connecting to it again.

This after trying remmina from Ubuntu 24.04.

dh at apple ~ $ systemctl status gnome-remote-desktop
● gnome-remote-desktop.service - GNOME Remote Desktop
      Loaded: loaded 
(/usr/lib/systemd/system/gnome-remote-desktop.service; enabled; preset: 
enabled)
      Active: active (running) since Fri 2025-07-11 18:16:49 CEST; 7min ago
  Invocation: 80894c50e6d846c49cdab9a709139bf6
    Main PID: 810 (gnome-remote-de)
       Tasks: 4 (limit: 4508)
      Memory: 40M (peak: 45.6M)
         CPU: 42ms
      CGroup: /system.slice/gnome-remote-desktop.service
              └─810 /usr/libexec/gnome-remote-desktop-daemon --system

juil. 11 18:16:48 apple systemd[1]: Starting 
gnome-remote-desktop.service - GNOME Remote Desktop...
juil. 11 18:16:49 apple gnome-remote-de[810]: Init TPM credentials 
failed because No TPM device found, using GKeyFile as fallback
juil. 11 18:16:49 apple systemd[1]: Started gnome-remote-desktop.service 
- GNOME Remote Desktop.
juil. 11 18:17:04 apple gnome-remote-de[810]: RDP server started
juil. 11 18:17:45 apple gnome-remote-de[810]: [RDP] Client did not 
advertise support for the Graphics Pipeline, closing connection
juil. 11 18:17:45 apple gnome-remote-de[810]: [RDP] Network or 
intentional disconnect, stopping session
juil. 11 18:17:45 apple gnome-remote-desktop-daemon[810]: [18:17:45:387] 
[810:00001e20] [ERROR][com.freerdp.api] - 
[rdp_peer_handle_state_demand_active]: 
[CONNECTION_STATE_CAPABILITIES_EXCHANGE_DEMAND_ACTIVE] 
freerdp_peer::Capabilities() callback failed
juil. 11 18:17:45 apple gnome-remote-desktop-daemon[810]: [18:17:45:387] 
[810:00001e20] [ERROR][com.freerdp.core.transport] - 
[transport_check_fds]: transport_check_fds: transport->ReceiveCallback() 
- STATE_RUN_FAILED [-1]

Test trom MBA M1 under Trixie Asahi Linux ask me to enter credentials 
and then got a blankscreen. Attached you will fing logs from this second 
attempt.

>
> If that is not successful, please describe the steps to reproduce the 
> problem you are seeing, without assuming that the package maintainers 
> know everything about your computer. You must have done some 
> configuration to make your computer offer remote desktop access - 
> please describe how you achieved that. The reason I ask for this is 
> that there is more than one way to use gnome-remote-desktop.

install xtask-cinnamon-desktop
tried X11vnc wich was working

Now knowing that trixie is Wayland only, I installed gnome
install xtask-gnome-desktop

 From here nothing more that trying to connect from 2 others notebook in 
RDP knowing that Debian removed VNC from g-r-d
I tried wayvnc+wayfire and could not get it work, always getting "wayvnc 
virtual pointer protocol not supported by compositor"

>
> Remote-controlling a GNOME system with gnome-remote-desktop is not the 
> typical configuration: the typical configuration is to plug in a 
> screen and keyboard, and use it locally.
Sure. On this computer I installed X11Vnc, Meshcentral and Rustdesk, all 
running well under X11. Rustdesk is running also under Wayland
> You also seem to be using gnome-remote-desktop in a less-common way 
> where you are creating a "headless" UI session, rather than sharing an 
> existing GUI session.
If you tell it, I believe you. I didn't do anything more that the steps 
above as far as I remember.
>
> If you are reporting a bug and you want it to be solvable, please 
> always start with:
>
> - what you did (how you configured the system), and especially anything
>   that you did that is unusual, like:
>     - installing on Apple hardware using an unofficial version of Debian;
>     - using gnome-remote-desktop rather than a locally connected screen
>       and keyboard
> - what you expected to happen
> - what actually happened
>
> The warning message logged by xdg-desktop-portal does not necessarily 
> have anything to do with you seeing a blank screen. It is potentially 
> useful information, but also potentially misleading, so we should 
> start by getting the full facts.
>
> So let's start again: if you had provided that information at the 
> beginning, what would you have said?
Trying to use g-r-d finish with a blank screen on the client and those 
are the logs I see (those sended on original message)
>
> Also please note that the "Bananas" port for Apple M1/M2 hardware is 
> not an official part of Debian, and relies on components that are not 
> part of Debian. I don't know how much of it is expected to work, and 
> probably some of it is known not to be ready at the moment. If you are 
> not already an experienced Debian user, I would recommend trying it on 
> x86 hardware (like an old laptop) first.

I use Asahi/Linux Debian on an MBA M1 since 2 and  a half year, was 
under bookworm at first, now Ttrixie. If you check actual stand of 
bananas, a debian-installer is existing. I'm connected to the team via 
#debian-bananas and doing some tests -I'm not the only one- for them. So 
no, will not change to x86-hardware. Anyway, I write this message and 
all others before with a Dell XPS 13 7390 Ubuntu 24.04

If you really fill that this case shouldn't be, feel free to close this 
bug, I can live with.

Thanks for your help

>
> Because gnome-remote-desktop interacts with video rendering, it is 
> dependent on the unofficial kernel and Mesa graphics stack provided by 
> "Bananas", which is not part of Debian.
>
> Other log messages that could be particularly relevant include:
>
>> juil. 10 18:39:18 apple gnome-remote-desktop-daemon[16112]: 
>> [18:39:18:988] [16112:000458c4] [WARN][com.freerdp.core.server] - 
>> [WTSReceiveChannelData]: unknown channelId 1006 ignored
> ...
>> juil. 10 18:39:34 apple gnome-remote-de[16112]: [DaemonSystem] 
>> Aborting handover, removing remote client with remote id 
>> /org/gnome/RemoteDesktop/Client/972001666
>> juil. 10 18:39:34 apple gnome-remote-desktop-daemon[16112]: 
>> [18:39:34:766] [16112:00003ef0] [ERROR][com.freerdp.core.peer] - 
>> [rdp_set_error_info]: ERRINFO_CB_CONNECTION_CANCELLED [0x00010409]
>
> (note for cc'd maintainers: there is a more full log in a previous 
> message on the bug)
>
>     smcv