gpclient hangs after browser MFA

[renmq]

Describe the bug
after running "sudo -E gpclient connect --browser-default z.z.z.z" GP portal's MFA page (/tmp/gpauth.html) launches. And I can finish authentication (user+password+phone text). But webpage just stops there and ask me to launch PANGui. gpclient output says "If it hangs, please check the logs at /tmp/gpcallback.log for more information" but /tmp/gpcallback.log doesn't exist...only /tmp/gpcallback.port is there.

Expected behavior
gpclient to receive gpcallback

Logs
[2024-11-26T18:59:07Z INFO gpclient::cli] gpclient started: 2.3.9 (2024-11-02)
[2024-11-26T18:59:07Z INFO gpapi::portal::prelogin] Portal prelogin with user_agent: PAN GlobalProtect
[2024-11-26T18:59:07Z INFO gpapi::portal::prelogin] Perform prelogin, user_agent: PAN GlobalProtect
[2024-11-26T18:59:07Z INFO gpauth::cli] gpauth started: 2.3.9 (2024-11-02)
[2024-11-26T18:59:07Z INFO gpapi::process::browser_authenticator] Launching browser: /usr/bin/google-chrome-stable
[2024-11-26T18:59:07Z INFO gpauth::cli] Please continue the authentication process in the default browser
[2024-11-26T18:59:07Z INFO gpauth::cli] Listening authentication data on port 40789
[2024-11-26T18:59:07Z INFO gpauth::cli] If it hangs, please check the logs at /tmp/gpcallback.log for more information

Environment:

• OS: [e.g. Ubuntu 24.04 LTS]

• Desktop Environment: xfce4

• Output of ps aux | grep 'gnome-keyring\|kwalletd5' | grep -v grep: [Required for secure store error]

• lightdm 4105 0.0 0.0 313884 9024 ? Ssl Nov24 0:00 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/124/keyring
  keplerc+ 12024 0.0 0.0 313752 8064 ? Sl Nov24 0:00 /usr/bin/gnome-keyring-daemon --start --foreground --components=secrets
  keplerc+ 12026 0.0 0.0 461372 9792 ? SLsl Nov24 0:00 /usr/bin/gnome-keyring-daemon --foreground --components=pkcs11,secrets --control-directory=/run/user/1000/keyring

• Is remote SSH? No

[yuezk]

@renmq looks like you installed the official client, which will conflict with this client because both registered the same MIME scheme. Try the solutions linked to see if it works for you.

#425 (comment)