Grafana.com login flow is broken with grafana v11

[rvdwijngaard]

Grafana Kiosk is experiencing an issue where it hangs at the login page with the "Sign in with Grafana.com" button after the latest Grafana v11.1.0-70958 (8c2a382788) update. This configuration was working correctly previously, but the recent update has caused the problem. When the "Sign in with Grafana.com" button is clicked, the login flow continues as expected.

I run grafana-kiosk with the following configuration:

grafana-kiosk --URL=https://my_hosted_grafana_url --login-method=gcom --username=user --password=password --kiosk-mode=full --playlists --autofit=true --lxde

Grafana-kiosk produces the following output:

2024/05/29 14:14:00 No config specified, using environment and args
2024/05/29 14:14:00 AutoFit: true
2024/05/29 14:14:00 LXDEEnabled: false
2024/05/29 14:14:00 LXDEHome: /home/pi
2024/05/29 14:14:00 Mode: disabled
2024/05/29 14:14:00 WindowPosition: 0,0
2024/05/29 14:14:00 WindowSize:
2024/05/29 14:14:00 ScaleFactor: 1.0
2024/05/29 14:14:00 URL: https://my_grafana_url
2024/05/29 14:14:00 LoginMethod: gcom
2024/05/29 14:14:00 Username: username
2024/05/29 14:14:00 Password: *redacted*
2024/05/29 14:14:00 IgnoreCertificateErrors: false
2024/05/29 14:14:00 IsPlayList: false
2024/05/29 14:14:00 UseMFA: false
2024/05/29 14:14:00 Fieldname AutoLogin: false
2024/05/29 14:14:00 Fieldname Username: username
2024/05/29 14:14:00 Fieldname Password: password
2024/05/29 14:14:00 DISPLAY= :0
2024/05/29 14:14:00 XAUTHORITY= /run/user/1001/gdm/Xauthority
2024/05/29 14:14:00 method  gcom
2024/05/29 14:14:00 Launching GCOM login kiosk
2024/05/29 14:14:00 Using temp dir: /tmp/chromedp-kiosk2668850559
2024/05/29 14:14:04 Sleeping 2000 MS before navigating to url
2024/05/29 14:14:06 KioskMode: Disabled
2024/05/29 14:14:06 Navigating to  https://my_grafana_url?autofitpanels
2024/05/29 14:14:08 waiting for login dialog
2024/05/29 14:14:08 gcom login dialog detected
2024/05/29 14:14:08 gcom button clicked

I experience this issue on all devices with different operating systems (Raspbian GNU/Linux 11 (bullseye) armv7l, arch linux and windows)

[briangann]

have reproduced this error, a fix is in progress