Skip to content

[Crash]: Mattermost Desktop 5.12.1 completely non-functional on Kubuntu 24.04 (Electron EIO write error) #3461

@skorpions2000

Description

@skorpions2000

Before you file a crash report

Mattermost Desktop Version

Mattermost Desktop 5.12.1

Operating System

Kubuntu 24.04

Mattermost Server Version

9.6.1

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

Mattermost Desktop 5.12.1 consistently crashes on Kubuntu 24.04 with the following error:

Error: EIO: i/o error, write
at Object.writeSync (node:fs:774:3)
at Object.writeFileSync (node:fs:2215:35)
at createLogFile (/opt/Mattermost/resources/app.asar/main.bundle.js:223045:10)


I suspect this is caused by the outdated Electron version (22.x) bundled with 5.12.1. Kubuntu 24.04 ships with Linux Kernel 6.14 and Mesa 24.x (Radeon RX 580). Many Electron-based apps using < v26 show similar behavior on this stack.

✔️ **Works fine in Chrome and other browsers**  
✔️ **Issue does not occur on Windows**  

---

### 🖥️ Operating System
Kubuntu 24.04 LTS x64
Kernel: 6.14.0-24-generic
Mesa: 24.2.8-1ubuntu1~24.04.1
GPU: AMD Radeon RX 580

Log Output

Application: Mattermost 5.12.1 [commit: aa47784
]
Platform: Linux 6.14.0-24-generic x64
Error: EIO: i/o error, write
    at writeSync (node:fs:924:3)
    at SyncWriteStream._write (node:internal/fs/sync_write_stream:27:5)
    at writeOrBuffer (node:internal/streams/writable:572:12)
    at _write (node:internal/streams/writable:501:10)
    at Writable.write (node:internal/streams/writable:510:10)
    at console.value (node:internal/console/constructor:298:16)
    at console.error (node:internal/console/constructor:412:26)
    at t.writeFn (/opt/Mattermost/resources/app.asar/index.js:2:1016445)
    at t (/opt/Mattermost/resources/app.asar/index.js:2:1016285)
    at i.processMessage (/opt/Mattermost/resources/app.asar/index.js:2:997227)

Additional Information

It seems the Linux build lags behind Windows/macOS in updating Electron. Could you consider releasing a 5.x patch with Electron >= v26 or backporting the fix from 6.x nightly?

Meanwhile, is there a known workaround for Linux users to avoid this crash?

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions