desktop: [Bug]: Desktop app hangs after user login through simulated Gitlab SSO.

Checks before filing an issue

Mattermost Desktop Version

5.5.1

Operating System

Fedora 37

Mattermost Server Version

9.1.0

Steps to reproduce

  1. install keycloak
  2. create a realm
  3. create a client
  4. config client add mappers to simulate gitlab
  5. add a user
  6. open desktop app to login with user created in step 5

Expected behavior

desktop load main UI, after user login in browser

Observed behavior

desktop app hangs at: 图片

Please Note: while in browser, I can click Open Mattermost in your browser, then use Mattermost as a user signed in…

Log Output

nothing useful:

[2023-10-25 16:08:46.161] [debug] [ViewManager] focusCurrentView
[2023-10-25 16:08:46.162] [debug] [ServerDropdownView] handleClose
[2023-10-25 16:08:46.163] [debug] [DownloadsDropdown...] handleClose
[2023-10-25 16:08:46.164] [debug] [DownloadsDropdown...] handleClose
[2023-10-25 16:08:46.165] [debug] [DownloadsDropdown...] updateDownloadsDropdownMenuItem {}
[2023-10-25 16:08:46.166] [debug] [DownloadsDropdown...] updateDownloadsDropdown
[2023-10-25 16:08:46.167] [debug] [DownloadsDropdown...] handleClose
[2023-10-25 16:08:46.167] [debug] [DownloadsDropdown...] updateDownloadsDropdownMenuItem {}
[2023-10-25 16:08:46.168] [debug] [DownloadsDropdown...] updateDownloadsDropdown
[2023-10-25 16:08:46.169] [debug] [ServerDropdownView] handleClose
[2023-10-25 16:08:46.170] [debug] [DownloadsDropdown...] handleClose
[2023-10-25 16:08:46.170] [debug] [DownloadsDropdown...] handleClose
[2023-10-25 16:08:46.171] [debug] [DownloadsDropdown...] updateDownloadsDropdownMenuItem {}
[2023-10-25 16:08:46.171] [debug] [DownloadsDropdown...] updateDownloadsDropdown
[2023-10-25 16:08:46.172] [debug] [DownloadsDropdown...] handleClose
[2023-10-25 16:08:46.173] [debug] [DownloadsDropdown...] updateDownloadsDropdownMenuItem {}
[2023-10-25 16:08:46.173] [debug] [DownloadsDropdown...] updateDownloadsDropdown
[2023-10-25 16:08:51.594] [debug] [ViewManager] focusCurrentView
[2023-10-25 16:08:51.883] [debug] [ServerDropdownView] handleClose
[2023-10-25 16:08:51.884] [debug] [DownloadsDropdown...] handleClose
[2023-10-25 16:08:51.884] [debug] [DownloadsDropdown...] handleClose
[2023-10-25 16:08:51.885] [debug] [DownloadsDropdown...] updateDownloadsDropdownMenuItem {}
[2023-10-25 16:08:51.885] [debug] [DownloadsDropdown...] updateDownloadsDropdown
[2023-10-25 16:08:53.949] [debug] [App.Utils] flushCookiesStore
[2023-10-25 16:08:53.950] [debug] [ViewManager] handleSetCurrentViewBounds { x: 0, y: 60, width: 2290, height: 1240 }
[2023-10-25 16:08:53.951] [debug] [ModalManager] handleResizeModal {
  bounds: { x: 0, y: 60, width: 2290, height: 1240 },
  modalQueueLength: 0
}
[2023-10-25 16:08:53.951] [debug] [App] [ServerViewState] getCurrentServer
[2023-10-25 16:08:53.952] [debug] [DownloadsDropdown...] updateWindowBounds
[2023-10-25 16:08:53.952] [debug] [DownloadsDropdown...] updateDownloadsDropdownMenu
[2023-10-25 16:08:53.952] [debug] [DownloadsDropdown...] updateDownloadsDropdownMenuItem {}
[2023-10-25 16:08:53.953] [debug] [DownloadsDropdown...] updateDownloadsDropdown
[2023-10-25 16:08:53.953] [debug] [DownloadsDropdown...] updateWindowBounds
[2023-10-25 16:08:53.954] [debug] [DownloadsDropdown...] updateDownloadsDropdown
[2023-10-25 16:08:54.073] [debug] [App.Initialize] UserActivityMonitor.on(status) { userIsActive: true, idleTime: 0, isSystemEvent: false }
[2023-10-25 16:09:54.141] [debug] [App.Initialize] UserActivityMonitor.on(status) { userIsActive: true, idleTime: 2, isSystemEvent: false }
[2023-10-25 16:10:54.205] [debug] [App.Initialize] UserActivityMonitor.on(status) { userIsActive: true, idleTime: 2, isSystemEvent: false }


### Additional Information

broswer version: google chrome 118.0.5993.88

About this issue

  • Original URL
  • State: closed
  • Created 8 months ago
  • Comments: 15 (7 by maintainers)

Most upvoted comments

@devinbinnie switched to RPM, now it works, but for generic linux install with tar ball, maybe the docs need improvement.

That change fixed it! We’ll implement this workaround until it’s fixed upstream; thank you!