Your message dated Sun, 17 Mar 2024 19:51:07 +0100 with message-id <[email protected]> and subject line Problems upgrading from Debian 10 to 11: xrdp has caused the Debian Bug report #1001539, regarding Problems upgrading from Debian 10 to 11: xrdp to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 1001539: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001539 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: xorgxrdp Version: 0.2.12 After upgrading from Debian 10 to Debian 11, xrdp stopped working. Someone else has a very good description of the problem here: https://c-nergy.be/blog/?p=17113 Essentially, the problem is fixed by upgrading xorgxrdp to a version newer than 0.2.12 from upstream. When I compiled the latest xrdp/xorgxrdp from the latest sources, xrdp worked again. Please can debian release a more up to date version of xorgxrdp? The latest is 0.2.17 Extract from the URL above: Root Cause of the issue We had to look a little bit further in order to find out what it’s really causing the issue. Based the the bug/issue reported to the team behind xrdp software (see https://github.com/neutrinolabs/xorgxrdp/issues/156), the problem is only present when using the xorgxrdp package version 0.2.12. Previous version of Debian (Debian 10) was using the package version 0.2.9 and we didn’t encountered the issue…Debian 11 is shipping with the problematic version (i.e. 0.2.12) and this explain why the connection is failing. The only fix proposed by xRDP team is basically to upgrade the xorgxrdp package to a more recent version which is exactly what’s happening when you are performing the custom installation….
--- End Message ---
--- Begin Message --- it's been some time since this has been fixed upstream, thus closing this bug also
--- End Message ---
