desktop: [Crash]: 5.3.1 crashes when trying to share the screen on Linux

Before you file a crash report

Mattermost Desktop Version

5.2.3

Operating System

Fedora 38

Mattermost Server Version

7.8.2

What type of crash did you experience?

System crash (The application quit unexpectedly with no warning, or the operating system reported a crash)

Crash report details

GDB doesn't have any useful information since the cores are to small (not sure why). But the issue occurs reliably on Fedora 38 with Wayland at least.

Log Output

10:26:51.232 › DownloadsManager.init { 'this.json': {}, validatedJSON: {} }
10:26:51.235 › DownloadsManager.saveAll
10:26:51.236 › DownloadsManager.checkForDeletedFiles
10:26:51.346 › Autoupgrade disabled: false
10:26:51.398 › couldn't show XXX___TAB_MESSAGING, not ready
10:26:51.401 › Failed to set new language en-US
10:26:51.402 › Failed to set new language DE
10:26:51.438 › config.autostart has been configured: true
10:26:51.439 › config.autostart has been configured: true
[24662:0428/102704.097676:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 1 times!
[24662:0428/102704.106735:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 2 times!
[24662:0428/102710.336218:ERROR:gl_surface_presentation_helper.cc(260)] GetVSyncParametersIfAvailable() failed for 3 times!
[1]    24623 segmentation fault (core dumped)  ./mattermost-desktop

Additional Information

No response

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Comments: 20 (20 by maintainers)

Commits related to this issue

Most upvoted comments

Hi @devinbinnie, I have built mattermost locally and updated electron to 26.1.0 to include electron/electron#39043 – this makes it behave properly now. Can I submit a PR to raise electron, or do you need to do more before raising the electron version?

Hey, yes I’ve re-opened your PR to upgrade Electron. Sorry I closed it before I saw this (just got back from vacation). In the future please link the PR to the ticket 😃

@devinbinnie This should now be fixable by upgrading electron 😃 If I read it correctly it should be part of v24.6.3: https://github.com/electron/electron/commits/v24.6.3 (latest commit as of now)

Thanks @streamer45, looks like they tried to fix it in v23.1.3 (we’re on 23.3.0 now) but it didn’t work so we’ll likely need to wait for a final fix.