Hi, > Are you sure that all those bugs can be closed? Have you tested your > version regarding all those reported issues you are closing? If yes. > Then... > > Personally, I like to name what I close. I.e. give a short description > how an issue was fixed. If I don't know how it was fixed but that it > was fixed, then... well. > > Syntactically, the way you mass close those open bugs is correct > (greppable), but also a little rude. But well, be it like that on such > a code monster. That's because most or all of these bugs are VNC-related issues. The new xrdp version discourages the use of VNC as backend to the local X server as we now have xorgxrdp. Some of them might still exist when using VNC, but they are in fact issues with VNC and not specific to xrdp. I can understand that people who used xrdp i nearlier versions related them to xrdp because xrdp did the VNC stuff silently. I think they should be closed now because xrdp, used in the encouraged and default way, does not show them anymore. Another way would be to reassign them to some vnc server package, but I think that we should neither put too much time in wrangling VNC bugs to find out which bugs are still valid, nor should we just reassign them to other packages without verifying they are still relevant. xrdp, as a remote desktop solution, does not show these bugs anymore, unless actively forced to use VNC perhaps, and if people do so, then they do it actively and know that they are just testing VNC. They should just file a bug against the VNC server they use for any bug that is still relevant to VNC. Cheers, Nik -- PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 Dominik George · Mobil: +49-151-61623918 Teckids e.V. · FrOSCon e.V. · OpenRheinRuhr e.V. Fellowship of the FSFE · Piratenpartei Deutschland Opencaching Deutschland e.V. · Debian Contributor LPIC-3 Linux Enterprise Professional (Security)
Attachment:
signature.asc
Description: This is a digitally signed message part.