Hello everyone, I’ve had an issue with discord on Arch Linux for a long time, but only now had the time to document the error (had to photograph it with phone and transcribe it).

Its a weird one, buckle up.

At random times, discord crashes which causes my polybar to crash, as well as my sxhkd, which obviously means my computer is practically useless until I hard shutdown using the power button on my case. Whats weird is that sometimes it will go weeks without crashing, and other times it will crash frequently in a short time span (e.g. it crashed a couple times yesterday, and once today).

Here is the error as I photographed it:

And here it is after I manually copied it into a text editor (keep in mind I might have missed a character here or there because of this).

A JavaScript Error occurred in the main process

Uncaught exception:
Error: EROFS: read-only file system, write
	at writeSync (node:fs:923:3)
	at SyncWriteStream._write (node:internal/fs/sync._write_stream:275)
	at writeOrBuffer (node:internal/streams/writable:572:12)
	at _write (node:internal/streams/writable:501:10)
	at Writeable.write (node:internal/streams/writable:510:10)
	at console.value (node:internal/console/constructor:298:16)
	at console.warn (node:internal/console/constructor:405:26)
	at transport.writeFn (/opt/discord/resources/app.asar/node_modules/electron-log/src/node/transports/console.js:45:7)
	at transport (/opt/discord/resources/app.asar/node_modules/electron-log/src/node/transports/console.js:51:15)
	at Logger.processMessage (/opt/discord/resources/app.asar/node_modules/electron-log/src/core/Logger.js:175:11)

Anyone have any idea how I can troubleshoot this?

I also tried checking the following directory but it doesn’t exist on my PC:

/opt/discord/resources/app.asar/node_modules/electron-log/src/core/

I only have the file /opt/discord/resources/app.asar So obviously something is going on there that shouldn’t be happening.

I’ve got no idea how to troubleshoot node apps, so would appreciate any help from those of you who have those skills.

Thanks in advance! Please let me know if you need more info or need me to run commands and show you the output, and Ill do so.

  • gabmus@retrolemmy.com
    link
    fedilink
    arrow-up
    1
    ·
    10 days ago

    Could be drive failure, or maybe your package for discord is broken? I’d try discord flatpak even just as a troubleshooting step, but honestly that’s the preferred way to install these kinds of applications anyway

    • promitheas@programming.devOP
      link
      fedilink
      arrow-up
      1
      ·
      6 days ago

      I dont believe its a drive failure after checking. Its a pretty new NVMe drive:

      $ sudo smartctl -t short /dev/nvme0n1p3
      smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.17.8-arch1-1] (local build)
      Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org
      
      Self-test has begun (NSID 0x1)
      Use smartctl -X to abort test
      
      $ sudo smartctl -H /dev/nvme0n1p3
      smartctl 7.5 2025-04-30 r5714 [x86_64-linux-6.17.8-arch1-1] (local build)
      Copyright (C) 2002-25, Bruce Allen, Christian Franke, www.smartmontools.org
      
      === START OF SMART DATA SECTION ===
      SMART overall-health self-assessment test result: PASSED
      

      Also with nvme-cli:

      $ sudo nvme smart-log /dev/nvme0n1
      Smart Log for NVME device:nvme0n1 namespace-id:ffffffff
      critical_warning			: 0 <<<<======================= Seems good!
      temperature				: 45 °C (318 K, 113 °F)
      available_spare				: 100%
      available_spare_threshold		: 10%
      percentage_used				: 1%
      endurance group critical warning summary: 0
      Data Units Read				: 8034527 (4.11 TB)
      Data Units Written			: 70423529 (36.06 TB)
      host_read_commands			: 58265590
      host_write_commands			: 901798802
      controller_busy_time			: 10039
      power_cycles				: 340
      power_on_hours				: 1500
      unsafe_shutdowns			: 63
      media_errors				: 0
      num_err_log_entries			: 0
      Warning Temperature Time		: 0
      Critical Composite Temperature Time	: 0
      Temperature Sensor 1			: 45 °C (318 K, 113 °F)
      Temperature Sensor 2			: 48 °C (321 K, 118 °F)
      Thermal Management T1 Trans Count	: 0
      Thermal Management T2 Trans Count	: 0
      Thermal Management T1 Total Time	: 0
      Thermal Management T2 Total Time	: 0
      

      As for flatpacks, I’d like to avoid such install methods if possible, at least for now. Whats weird is I don’t think I’ve come across anyone else with this issue, so I doubt its something wrong in general with the packagement process.