[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1105161: marked as done (freerdp3-x11: freerdp3 needlessly prompts for domain even when it is already provided by param /u)



Your message dated Tue, 9 Sep 2025 15:36:54 +0300
with message-id <7c5c2d56-971b-4300-863c-9f9329688709@tls.msk.ru>
and subject line Re: Bug#1105161: freerdp3-x11: freerdp3 needlessly prompts for domain even when it is already provided by param /u
has caused the Debian Bug report #1105161,
regarding freerdp3-x11: freerdp3 needlessly prompts for domain even when it is already provided by param /u
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 owner@bugs.debian.org
immediately.)


-- 
1105161: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105161
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: freerdp3-x11
Version: 3.10.3+dfsg-1~bpo12+1
Severity: minor
X-Debbugs-Cc: e.batek+debian@itkaufmann.at

Dear Maintainer,

When I provide the domain to FreeRDP 3 through the username parameter `/u` (e.g. `/u:user@domain.tld`), it needlessly prompts for a domain (on the command-line).
Luckily, this prompt can be confirmed with no input and FreeRDP will use the domain provided by the username.

FreeRDP 2 doesn’t exhibit this behavior.

Example:

```
xfreerdp3 /u:Administrator@example.com /v:rdp.example.com
```

Further findings:
Providing a password through parameter `/p` seems to suppress the domain prompt.


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

Kernel: Linux 6.1.0-34-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages freerdp3-x11 depends on:
ii  libc6                 2.36-9+deb12u10
ii  libfreerdp-client3-3  3.10.3+dfsg-1~bpo12+1
ii  libfreerdp3-3         3.10.3+dfsg-1~bpo12+1
ii  libwinpr3-3           3.10.3+dfsg-1~bpo12+1
ii  libx11-6              2:1.8.4-2+deb12u2
ii  libxcursor1           1:1.2.1-1
ii  libxext6              2:1.3.4-1+b1
ii  libxfixes3            1:6.0.0-2
ii  libxi6                2:1.8-1+b1
ii  libxinerama1          2:1.1.4-3
ii  libxrandr2            2:1.5.2-2+b1
ii  libxrender1           1:0.9.10-1.1

freerdp3-x11 recommends no packages.

freerdp3-x11 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
On Mon, 12 May 2025 17:51:26 +0000 akallabeth+debian@posteo.net wrote:
Hi,

this is not a bug but a feature.
Microsoft uses both kinds of syntax in combination, so you could also have to enter

domain\user@otherdomain

and that will work.
FreeRDP2 did not properly parse that and you rely on that behavior.

FreeRDP3 correctly parses that and does not touch user@otherdomain and lets the remote handle that.

For your usecase, just do

xfreerdp3 /u:user@domain /d: /v:rdp.example.com

and it will only prompt for password.
So let's close this bug report based on the above :)

Thanks,

/mjt

--- End Message ---

Reply to: