[SOLVED] Discord 1:0.0.133-1 crashes on startup

lesio · 2026-04-15 18:29:59

I recently did a system upgrade, and ever since, Discord seems to crash every time I launch it, immediately after the main window appears.

I'm given this error:

Uncaught exception:
TypeError: _analytics$getDesktop3.call(...).trackMainWindowDocumentLoad is not a function
at WebContents.<anonymous> (home/lesio/.config/discord/0.0.133/modules/discord_desktop_core/core.asar/app/mainScreen.js:480:278)
at Object.onceWrapper (node:events:634:26)
at WebContents.emit (node:events:531:35)
at WebContents.emit (node:domain:489:12)
at emitter.emit (/opt/discord/resources/app.asar/node_modules/@sentry/electron/main/integrations/electron-breadcrumbs.js:73:20)

in a dialog box that closes after I press Ok.

Does anyone have a clue as to why this is happening, or how I could fix it?

Some system details, in case they're relevant...
KDE Plasma version 6.6.4
linux kernel version 6.19.11
AMD Radeon RX 9060 XT gpu

Last edited by lesio (2026-04-15 21:18:37)

seth · 2026-04-15 20:08:10

KDE Plasma version 6.6.4

Since the crash seems to query the main screen

kscreen-doctor

and try the behavior w/ a different environment (some boring X11/openbox or icewm session)

lesio · 2026-04-15 20:25:47

i installed icewm and tried to open discord in a session there, but I got the same issue unfortunately.
did you want me to do something in particular with kscreen-doctor? doing just that (on my plasma session ofc) doesn't seem to generate any output for me

seth · 2026-04-15 20:29:29

Mostly interested what and how many outputs are there, but actually see https://bbs.archlinux.org/viewtopic.php?pid=2294481

lesio · 2026-04-15 20:39:58

in case you meant kscreen-doctor -o (sorry, i'm still pretty new to linux, don't mean to be difficult lol):

Output: 1 DP-1 d0cf046b-52ea-4456-bfb2-166a70ba8014
	enabled
	connected
	priority 1
	DisplayPort
	replication source:0
	Modes:  1:1920x1080@60.00!  2:1920x1080@144.00*  3:1920x1080@119.98  4:1920x1080@99.93  5:1920x1080@84.90  6:1920x1080@60.00  7:1920x1080@59.94  8:1920x1080@50.00  9:1680x1050@59.95  10:1280x1024@75.03  11:1280x1024@60.02  12:1440x900@59.89  13:1280x960@60.00  14:1280x800@59.81  15:1152x864@75.00  16:1280x720@60.00  17:1280x720@60.00  18:1280x720@59.94  19:1280x720@50.00  20:1024x768@75.03  21:1024x768@70.07  22:1024x768@60.00  23:832x624@74.55  24:800x600@75.00  25:800x600@72.19  26:800x600@60.32  27:800x600@56.25  28:720x576@50.00  29:720x576@50.00  30:720x480@60.00  31:720x480@60.00  32:720x480@59.94  33:720x480@59.94  34:640x480@75.00  35:640x480@66.67  36:640x480@60.00  37:640x480@59.94  38:640x480@59.94  39:720x400@70.08  40:1280x1024@143.79  41:1024x768@143.87  42:1280x800@143.84  43:1600x900@59.95  44:1600x900@143.93  45:1368x768@59.88  46:1368x768@143.77  47:1280x720@143.67 
	Custom modes: None
	Geometry: 0,0 1920x1080
	Scale: 1
	Rotation: 1
	Overscan: 0
	Vrr: Automatic
	RgbRange: Automatic
	HDR: incapable
	Wide Color Gamut: incapable
	ICC profile: none
	Color profile source: sRGB
	Color power preference: prefer accuracy
	Brightness control: supported, set to 45% and dimming to 100%
	DDC/CI: disallowed
	Color resolution: automatic (16), range: [8; 16] bits per color
	Allow EDR: unsupported
	Sharpness control: unsupported
	Automatic brightness: unsupported
Output: 2 HDMI-A-1 105ca258-ac8b-45c6-a8a3-ffcd54fdd0ac
	enabled
	connected
	priority 2
	HDMI
	replication source:0
	Modes:  48:1920x1080@60.00*!  49:1920x1080@60.00  50:1920x1080@59.94  51:1920x1080@59.99  52:1920x1080@50.00  53:1600x1200@60.00  54:1680x1050@59.88  55:1280x1024@75.03  56:1280x1024@60.02  57:1440x900@59.90  58:1280x960@60.00  59:1366x768@59.79  60:1152x864@75.00  61:1280x720@60.00  62:1280x720@60.00  63:1280x720@59.94  64:1280x720@50.00  65:1024x768@75.03  66:1024x768@70.07  67:1024x768@60.00  68:832x624@74.55  69:800x600@75.00  70:800x600@72.19  71:800x600@60.32  72:800x600@56.25  73:720x576@50.00  74:720x576@50.00  75:720x480@60.00  76:720x480@60.00  77:720x480@59.94  78:720x480@59.94  79:720x480@59.94  80:640x480@75.00  81:640x480@72.81  82:640x480@66.67  83:640x480@60.00  84:640x480@59.94  85:640x480@59.94  86:720x400@70.08  87:1280x800@59.81  88:1600x900@59.95  89:1368x768@59.88 
	Custom modes: None
	Geometry: 1920,0 1920x1080
	Scale: 1
	Rotation: 1
	Overscan: 0
	Vrr: incapable
	RgbRange: Automatic
	HDR: incapable
	Wide Color Gamut: incapable
	ICC profile: none
	Color profile source: sRGB
	Color power preference: prefer accuracy
	Brightness control: supported, set to 50% and dimming to 100%
	Color resolution: automatic (16), range: [8; 16] bits per color
	Allow EDR: unsupported
	Sharpness control: unsupported
	Automatic brightness: unsupported

lesio · 2026-04-15 20:44:21

oops, replied before i saw your post. since that other topic got dustbinned, i figured i should start a new topic to see if i could get any help.
in the other thread, the OP mentions that this is probably a discord issue, but i actually also recently tried the discord_arch_electron (also version 1:0.0.133-1) package from the AUR and it seems to start just fine, so i'm unsure if it's actually a discord issue

EDIT: i did some basic searching and i'm pretty sure i'm just highlighting my own ignorance here... i'm thinking the AUR package probably works BECAUSE it replaces the version of electron that discord depends on, which is where the issue probably is, and so it probably really is discord's fault, and nothing anyone here can do anything about. i don't really know that that's what is happening, but if i'm anywhere near the mark, sorry for not connecting the dots sooner.

Last edited by lesio (2026-04-15 21:02:09)

seth · 2026-04-15 21:05:23

The other thread wrote:

Deleting ~/.config/discord/0.0.133/modules and letting Discord re-download did not fix.
…
When I installed this update this morning (8 hrs ago), it went without issues, no crashes.

Does regenerating the modules fix it for you?
google has exactly two hits for "trackMainWindowDocumentLoad" - these two threads …

lesio · 2026-04-15 21:17:19

... yes, it fixes it. sorry, i get too into my own head sometimes. all i had to do was delete the folder and relaunch discord. thank you for the help!

seth · 2026-04-15 21:26:23

\o/

Nothing to be sorry about
Ftr. I assume what happened was some temporary issue at discord that got silently fixed w/o a version update but a fistful of users will have downloaded the bogus module into the local cache.

pokemonpasta · 2026-04-16 10:30:40

Hey all I'm running into this issue my end and I'm unsure the steps OP took to fix this. Simply deleting the folder and relaunching discord isn't working for me - it brings me back to the same error - is that the correct process?

I tried the discord_arch_electron package which works, but I don't seem to be able to install vencord onto it, it's giving me a typescript error when I launch it after patching.

seth wrote:

Does regenerating the modules fix it for you?

Is this just redownloading the module by launching discord or is there another step involved

seth · 2026-04-16 12:47:28

ls -lR ~/.config/discord/

lesio · 2026-04-16 16:25:15

i have a friend who was having similar issues with vencord even after regenerating modules, and what fixed it was some combination of these steps (in order, loosely):
- uninstalling the extra/discord package
- clearing paccache
- deleting ~/.config/discord and ~/.config/discord/0.0.133/modules
- deleting /opt/discord (!)
- reinstalling discord
- reinstalling vencord

that's what it took for them, hopefully it will also fix it for you. also, should i remove the [SOLVED] from the title? i don't know forum etiquette very well yet

Last edited by lesio (2026-04-16 16:26:23)

seth · 2026-04-16 19:37:25

should i remove the [SOLVED] from the title?

The problem /is/ solved for you?
Then not.
Deleting and re-installing discord was probably just something you implicitly did when testing discord_arch_electron ?

pokemonpasta · 2026-04-18 20:13:50

lesio wrote:

i have a friend who was having similar issues with vencord even after regenerating modules, and what fixed it was some combination of these steps (in order, loosely):
- uninstalling the extra/discord package
- clearing paccache
- deleting ~/.config/discord and ~/.config/discord/0.0.133/modules
- deleting /opt/discord (!)
- reinstalling discord
- reinstalling vencord
that's what it took for them, hopefully it will also fix it for you. also, should i remove the [SOLVED] from the title? i don't know forum etiquette very well yet

thank you, this fixed it for me!

Arch Linux

#1 2026-04-15 18:29:59

[SOLVED] Discord 1:0.0.133-1 crashes on startup

#2 2026-04-15 20:08:10

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

#3 2026-04-15 20:25:47

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

#4 2026-04-15 20:29:29

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

#5 2026-04-15 20:39:58

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

#6 2026-04-15 20:44:21

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

#7 2026-04-15 21:05:23

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

#8 2026-04-15 21:17:19

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

#9 2026-04-15 21:26:23

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

#10 2026-04-16 10:30:40

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

#11 2026-04-16 12:47:28

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

#12 2026-04-16 16:25:15

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

#13 2026-04-16 19:37:25

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

#14 2026-04-18 20:13:50

Re: [SOLVED] Discord 1:0.0.133-1 crashes on startup

Board footer