Community Packages

Please read this before reporting a bug:
http://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#65643 - [Discord] segfault SGI_video_sync

Attached to Project: Community Packages
Opened by Daniel Mehrmann (Akusari) - Thursday, 27 February 2020, 20:05 GMT
Last edited by Filipe Laíns (FFY00) - Tuesday, 27 October 2020, 01:50 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Filipe Laíns (FFY00)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 11
Private No

Details

Description: Each start of Discord creates some kernel messages and coredumps as described below. The app itself just runs fine so far. This happens since version 0.0.10-1. Version 0.0.9-[1-4] has no such problems.

package version(s) discord 0.0.10-1
Steps to reproduce: Start discord

*** Output of discord ***

Discord 0.0.10
Starting app.
Starting updater.
[Modules] Modules initializing
[Modules] Distribution: remote
[Modules] Host updates: enabled
[Modules] Module updates: enabled
[Modules] Module install path: /home/daniel/.config/discord/0.0.10/modules
[Modules] Module installed file path: /home/daniel/.config/discord/0.0.10/modules/installed.json
[Modules] Module download path: /home/daniel/.config/discord/0.0.10/modules/pending
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230
[Modules] No updates to install
[Modules] Checking for host updates.
[Modules] Host is up to date.
[Modules] Checking for module updates at https://discordapp.com/api/modules/stable/versions.json
[Modules] No module updates available.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230
(electron) 'isAccessibilitySupportEnabled function' is deprecated and will be removed. Please use 'accessibilitySupportEnabled property' instead.
(electron) 'setBadgeCount function' is deprecated and will be removed. Please use 'badgeCount property' instead.
[000:000] [13442] (audio_send_stream.cc:285): Failed to set up send codec state.
[000:026] [13442] (audio_send_stream.cc:285): Failed to set up send codec state.
[000:026] [13442] (audio_device_generic.cc:31): BuiltInAECIsAvailable: Not supported on this platform
[000:062] [13442] (audio_send_stream.cc:285): Failed to set up send codec state.
cord:

*** dmesg: ***

[ 2228.075333] SGI_video_sync[13348]: segfault at e6 ip 000055774867820d sp 00007fad9a0ef840 error 6 in Discord[5577451d7000+53ad000]
[ 2228.075337] Code: 0f 46 d8 89 df e8 43 00 00 00 4c 89 f7 e8 db 01 00 00 41 8b 46 10 41 8b 4e 18 0f b6 c0 c1 e0 0c 0f b6 c9 c1 e1 14 09 c1 09 d9 <c6> 01 00 81 e3 ff 0f 00 00 c6 03 00 bf 01 00 00 00 e8 4d 59 f0 01
[ 2228.385372] SGI_video_sync[13382]: segfault at e6 ip 000055c4aed4020d sp 00007f938f047840 error 6 in Discord[55c4ab89f000+53ad000]
[ 2228.385377] Code: 0f 46 d8 89 df e8 43 00 00 00 4c 89 f7 e8 db 01 00 00 41 8b 46 10 41 8b 4e 18 0f b6 c0 c1 e0 0c 0f b6 c9 c1 e1 14 09 c1 09 d9 <c6> 01 00 81 e3 ff 0f 00 00 c6 03 00 bf 01 00 00 00 e8 4d 59 f0 01
[ 2228.806140] SGI_video_sync[13426]: segfault at e6 ip 000056234018220d sp 00007f9df7db2840 error 6 in Discord[56233cce1000+53ad000]
[ 2228.806144] Code: 0f 46 d8 89 df e8 43 00 00 00 4c 89 f7 e8 db 01 00 00 41 8b 46 10 41 8b 4e 18 0f b6 c0 c1 e0 0c 0f b6 c9 c1 e1 14 09 c1 09 d9 <c6> 01 00 81 e3 ff 0f 00 00 c6 03 00 bf 01 00 00 00 e8 4d 59 f0 01

*** coredumpctl: ***
[...]
Thu 2020-02-27 20:53:17 CET 13311 1000 985 11 present /opt/discord/Discord
Thu 2020-02-27 20:53:17 CET 13359 1000 985 11 present /opt/discord/Discord
Thu 2020-02-27 20:53:18 CET 13391 1000 985 11 present /opt/discord/Discord

*** coredump info 1311 ***
PID: 13311 (Discord)
UID: 1000 (daniel)
GID: 985 (users)
Signal: 11 (SEGV)
Timestamp: Thu 2020-02-27 20:53:17 CET (10min ago)
Command Line: /opt/discord/Discord --type=gpu-process --field-trial-handle=14375939149685482340,18081708819681251533,>
Executable: /opt/discord/Discord
Control Group: /user.slice/user-1000.slice/session-4.scope
Unit: session-4.scope
Slice: user-1000.slice
Session: 4
Owner UID: 1000 (daniel)
Boot ID: f9f4627153d144c3b48c9dd01832504a
Machine ID: 66c6e327b2fa4b29b60fb23c17390c40
Hostname: Homer
Storage: /var/lib/systemd/coredump/core.Discord.1000.f9f4627153d144c3b48c9dd01832504a.13311.15828331970000000000>
Message: Process 13311 (Discord) of user 1000 dumped core.

Stack trace of thread 13348:
#0 0x000055774867820d n/a (Discord + 0x4aab20d)
#1 0x000055774867c026 n/a (Discord + 0x4aaf026)
#2 0x00007fada32bd800 __restore_rt (libpthread.so.0 + 0x14800)
#3 0x00007fada1d492d1 clock_nanosleep@@GLIBC_2.17 (libc.so.6 + 0xc72d1)
#4 0x00007fada1d4ebf7 __nanosleep (libc.so.6 + 0xccbf7)
#5 0x00007fada1d79799 usleep (libc.so.6 + 0xf7799)
#6 0x00007fad9dddbbab n/a (libnvidia-glcore.so.440.59 + 0xe54bab)
#7 0x00007fad9de1cea0 n/a (libnvidia-glcore.so.440.59 + 0xe95ea0)
#8 0x00007fad9de1ea26 n/a (libnvidia-glcore.so.440.59 + 0xe97a26)
#9 0x00007fad9ef7cd9f n/a (libGLX_nvidia.so.0 + 0x7fd9f)
#10 0x00007fad9f2833cf __glDispatchCheckMultithreaded (libGLdispatch.so.0 + 0x413cf)
#11 0x00007fad9f228567 n/a (libGLX.so.0 + 0x19567)
#12 0x00007fad9f2299c6 glXGetFBConfigs (libGLX.so.0 + 0x1a9c6)
#13 0x0000557747bfde77 n/a (Discord + 0x4030e77)
#14 0x0000557747c01a42 n/a (Discord + 0x4034a42)
#15 0x0000557747133d1d n/a (Discord + 0x3566d1d)
#16 0x00005577471337de n/a (Discord + 0x35667de)
#17 0x00005577470ed8ba n/a (Discord + 0x35208ba)
#18 0x00005577471348e9 n/a (Discord + 0x35678e9)
#19 0x0000557747109167 n/a (Discord + 0x353c167)
#20 0x0000557747143f00 n/a (Discord + 0x3576f00)
#21 0x0000557747189ba5 n/a (Discord + 0x35bcba5)
#22 0x00007fada32b246f start_thread (libpthread.so.0 + 0x946f)
#23 0x00007fada1d813d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13311:
#0 0x00007fada1d76abf __poll (libc.so.6 + 0xf4abf)
#1 0x00007fada2e0863b n/a (libxcb.so.1 + 0xc63b)
#2 0x00007fada2e0a08f n/a (libxcb.so.1 + 0xe08f)
#3 0x00007fada2e0a203 xcb_wait_for_reply64 (libxcb.so.1 + 0xe203)
#4 0x00007fada2e6c269 _XReply (libX11.so.6 + 0x41269)
#5 0x00007fad9efa28a2 n/a (libGLX_nvidia.so.0 + 0xa58a2)
#6 0x00007fad9ef4cc9c n/a (libGLX_nvidia.so.0 + 0x4fc9c)
#7 0x00007fad9ef9d8a1 n/a (libGLX_nvidia.so.0 + 0xa08a1)
#8 0x00007fad9ef9dfa8 n/a (libGLX_nvidia.so.0 + 0xa0fa8)
#9 0x00007fad9ef4c424 n/a (libGLX_nvidia.so.0 + 0x4f424)
#10 0x00007fad9ddc24ce n/a (libnvidia-glcore.so.440.59 + 0xe3b4ce)
#11 0x00007fad9ef9ad54 n/a (libGLX_nvidia.so.0 + 0x9dd54)
#12 0x00007fad9ef4c8b8 n/a (libGLX_nvidia.so.0 + 0x4f8b8)
#13 0x00007fad9ddbefdd n/a (libnvidia-glcore.so.440.59 + 0xe37fdd)
#14 0x00007fad9ef4c7ad n/a (libGLX_nvidia.so.0 + 0x4f7ad)
#15 0x00007fad9ef4a90a n/a (libGLX_nvidia.so.0 + 0x4d90a)
#16 0x00007fad9ef78633 n/a (libGLX_nvidia.so.0 + 0x7b633)
#17 0x00007fad9f223c52 n/a (libGLX.so.0 + 0x14c52)
#18 0x00007fad9f22a975 n/a (libGLX.so.0 + 0x1b975)
#19 0x0000557747bfbe77 n/a (Discord + 0x402ee77)
#20 0x0000557748504b86 n/a (Discord + 0x4937b86)
#21 0x000055774850abd3 n/a (Discord + 0x493dbd3)
#22 0x00005577482bc9c0 n/a (Discord + 0x46ef9c0)
#23 0x0000557747133d1d n/a (Discord + 0x3566d1d)
#24 0x00005577471337de n/a (Discord + 0x35667de)
#25 0x00005577470f60c7 n/a (Discord + 0x35290c7)
#26 0x00007fada318751e g_main_context_dispatch (libglib-2.0.so.0 + 0x6a51e)
#27 0x00007fada31892d1 n/a (libglib-2.0.so.0 + 0x6c2d1)
#28 0x00007fada3189311 g_main_context_iteration (libglib-2.0.so.0 + 0x6c311)
#29 0x00005577470edba2 n/a (Discord + 0x3520ba2)
#30 0x00005577471348e9 n/a (Discord + 0x35678e9)
#31 0x0000557747109167 n/a (Discord + 0x353c167)
#32 0x0000557749fba599 n/a (Discord + 0x63ed599)
#33 0x00005577469354d4 n/a (Discord + 0x2d684d4)
#34 0x00005577486ed6ec n/a (Discord + 0x4b206ec)
#35 0x0000557745c08481 n/a (Discord + 0x203b481)
#36 0x00005577451d727b n/a (Discord + 0x160a27b)
#37 0x00007fada1ca9023 __libc_start_main (libc.so.6 + 0x27023)
#38 0x00005577451d702a _start (Discord + 0x160a02a)

Stack trace of thread 13342:
#0 0x00007fada32b901a pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x1001a)
#1 0x000055774717f320 n/a (Discord + 0x35b2320)
#2 0x000055774717fa62 n/a (Discord + 0x35b2a62)
#3 0x00005577470ed8a5 n/a (Discord + 0x35208a5)
#4 0x00005577471348e9 n/a (Discord + 0x35678e9)
#5 0x0000557747109167 n/a (Discord + 0x353c167)
#6 0x0000557747143f00 n/a (Discord + 0x3576f00)
#7 0x0000557747189ba5 n/a (Discord + 0x35bcba5)
#8 0x00007fada32b246f start_thread (libpthread.so.0 + 0x946f)
#9 0x00007fada1d813d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13345:
#0 0x00007fada1d8170e epoll_wait (libc.so.6 + 0xff70e)
#1 0x0000557747221a4b n/a (Discord + 0x3654a4b)
#2 0x000055774721f390 n/a (Discord + 0x3652390)
#3 0x0000557747187a4f n/a (Discord + 0x35baa4f)
#4 0x00005577471348e9 n/a (Discord + 0x35678e9)
#5 0x0000557747109167 n/a (Discord + 0x353c167)
#6 0x0000557747143f00 n/a (Discord + 0x3576f00)
#7 0x0000557747189ba5 n/a (Discord + 0x35bcba5)
#8 0x00007fada32b246f start_thread (libpthread.so.0 + 0x946f)
#9 0x00007fada1d813d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13343:
#0 0x00007fada1d8170e epoll_wait (libc.so.6 + 0xff70e)
#1 0x0000557747221a4b n/a (Discord + 0x3654a4b)
#2 0x000055774721f390 n/a (Discord + 0x3652390)
#3 0x0000557747187b09 n/a (Discord + 0x35bab09)
#4 0x00005577471348e9 n/a (Discord + 0x35678e9)
#5 0x0000557747109167 n/a (Discord + 0x353c167)
#6 0x0000557747138177 n/a (Discord + 0x356b177)
#7 0x0000557747143f00 n/a (Discord + 0x3576f00)
#8 0x0000557747189ba5 n/a (Discord + 0x35bcba5)
#9 0x00007fada32b246f start_thread (libpthread.so.0 + 0x946f)
#10 0x00007fada1d813d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13346:
#0 0x00007fada32b8cf5 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfcf5)
#1 0x000055774717fb0b n/a (Discord + 0x35b2b0b)
#2 0x000055774717f7cf n/a (Discord + 0x35b27cf)
#3 0x00005577485041a0 n/a (Discord + 0x49371a0)
#4 0x00005577483468c4 n/a (Discord + 0x47798c4)
#5 0x00005577483466b8 n/a (Discord + 0x47796b8)
#6 0x000055774832fa2a n/a (Discord + 0x4762a2a)
#7 0x0000557748351f08 n/a (Discord + 0x4784f08)
#8 0x0000557748351daa n/a (Discord + 0x4784daa)
#9 0x0000557745b5bd6d n/a (Discord + 0x1f8ed6d)
#10 0x00005577473b6c2a n/a (Discord + 0x37e9c2a)
#11 0x00005577473bc68a n/a (Discord + 0x37ef68a)
#12 0x00005577473bc242 n/a (Discord + 0x37ef242)
#13 0x00005577473b54ef n/a (Discord + 0x37e84ef)
#14 0x00005577473b5be0 n/a (Discord + 0x37e8be0)
#15 0x00005577473c9d65 n/a (Discord + 0x37fcd65)
#16 0x0000557747133d1d n/a (Discord + 0x3566d1d)
#17 0x00005577471337de n/a (Discord + 0x35667de)
#18 0x00005577470ed8ba n/a (Discord + 0x35208ba)
#19 0x00005577471348e9 n/a (Discord + 0x35678e9)
#20 0x0000557747109167 n/a (Discord + 0x353c167)
#21 0x0000557747143f00 n/a (Discord + 0x3576f00)
#22 0x0000557747189ba5 n/a (Discord + 0x35bcba5)
#23 0x00007fada32b246f start_thread (libpthread.so.0 + 0x946f)
#24 0x00007fada1d813d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13344:
#0 0x00007fada32b901a pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x1001a)
#1 0x000055774717f320 n/a (Discord + 0x35b2320)
#2 0x000055774717fa62 n/a (Discord + 0x35b2a62)
#3 0x000055774713f6c8 n/a (Discord + 0x35726c8)
#4 0x000055774713fc3b n/a (Discord + 0x3572c3b)
#5 0x000055774713f904 n/a (Discord + 0x3572904)
#6 0x0000557747189ba5 n/a (Discord + 0x35bcba5)
#7 0x00007fada32b246f start_thread (libpthread.so.0 + 0x946f)
#8 0x00007fada1d813d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13347:
#0 0x00007fada32b901a pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x1001a)
#1 0x000055774717f320 n/a (Discord + 0x35b2320)
#2 0x000055774717fa62 n/a (Discord + 0x35b2a62)
#3 0x000055774713f6c8 n/a (Discord + 0x35726c8)
#4 0x000055774713f9e8 n/a (Discord + 0x35729e8)
#5 0x000055774713f904 n/a (Discord + 0x3572904)
#6 0x0000557747189ba5 n/a (Discord + 0x35bcba5)
#7 0x00007fada32b246f start_thread (libpthread.so.0 + 0x946f)
#8 0x00007fada1d813d3 __clone (libc.so.6 + 0xff3d3)

*** coredumpctl info 13359 ***
PID: 13359 (Discord)
UID: 1000 (daniel)
GID: 985 (users)
Signal: 11 (SEGV)
Timestamp: Thu 2020-02-27 20:53:17 CET (11min ago)
Command Line: /opt/discord/Discord --type=gpu-process --field-trial-handle=14375939149685482340,18081708819681251533,>
Executable: /opt/discord/Discord
Control Group: /user.slice/user-1000.slice/session-4.scope
Unit: session-4.scope
Slice: user-1000.slice
Session: 4
Owner UID: 1000 (daniel)
Boot ID: f9f4627153d144c3b48c9dd01832504a
Machine ID: 66c6e327b2fa4b29b60fb23c17390c40
Hostname: Homer
Storage: /var/lib/systemd/coredump/core.Discord.1000.f9f4627153d144c3b48c9dd01832504a.13359.15828331970000000000>
Message: Process 13359 (Discord) of user 1000 dumped core.

Stack trace of thread 13382:
#0 0x000055c4aed4020d n/a (Discord + 0x4aab20d)
#1 0x000055c4aed44026 n/a (Discord + 0x4aaf026)
#2 0x00007f9398335800 __restore_rt (libpthread.so.0 + 0x14800)
#3 0x00007f9396dc12d1 clock_nanosleep@@GLIBC_2.17 (libc.so.6 + 0xc72d1)
#4 0x00007f9396dc6bf7 __nanosleep (libc.so.6 + 0xccbf7)
#5 0x00007f9396df1799 usleep (libc.so.6 + 0xf7799)
#6 0x00007f9392e53bab n/a (libnvidia-glcore.so.440.59 + 0xe54bab)
#7 0x00007f9392e94ea0 n/a (libnvidia-glcore.so.440.59 + 0xe95ea0)
#8 0x00007f9392e96a26 n/a (libnvidia-glcore.so.440.59 + 0xe97a26)
#9 0x00007f9393ff4d9f n/a (libGLX_nvidia.so.0 + 0x7fd9f)
#10 0x00007f93942fb3cf __glDispatchCheckMultithreaded (libGLdispatch.so.0 + 0x413cf)
#11 0x00007f93942a0567 n/a (libGLX.so.0 + 0x19567)
#12 0x00007f93942a19c6 glXGetFBConfigs (libGLX.so.0 + 0x1a9c6)
#13 0x000055c4ae2c5e77 n/a (Discord + 0x4030e77)
#14 0x000055c4ae2c9a42 n/a (Discord + 0x4034a42)
#15 0x000055c4ad7fbd1d n/a (Discord + 0x3566d1d)
#16 0x000055c4ad7fb7de n/a (Discord + 0x35667de)
#17 0x000055c4ad7b58ba n/a (Discord + 0x35208ba)
#18 0x000055c4ad7fc8e9 n/a (Discord + 0x35678e9)
#19 0x000055c4ad7d1167 n/a (Discord + 0x353c167)
#20 0x000055c4ad80bf00 n/a (Discord + 0x3576f00)
#21 0x000055c4ad851ba5 n/a (Discord + 0x35bcba5)
#22 0x00007f939832a46f start_thread (libpthread.so.0 + 0x946f)
#23 0x00007f9396df93d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13379:
#0 0x00007f9396df970e epoll_wait (libc.so.6 + 0xff70e)
#1 0x000055c4ad8e9a4b n/a (Discord + 0x3654a4b)
#2 0x000055c4ad8e7390 n/a (Discord + 0x3652390)
#3 0x000055c4ad84fa4f n/a (Discord + 0x35baa4f)
#4 0x000055c4ad7fc8e9 n/a (Discord + 0x35678e9)
#5 0x000055c4ad7d1167 n/a (Discord + 0x353c167)
#6 0x000055c4ad80bf00 n/a (Discord + 0x3576f00)
#7 0x000055c4ad851ba5 n/a (Discord + 0x35bcba5)
#8 0x00007f939832a46f start_thread (libpthread.so.0 + 0x946f)
#9 0x00007f9396df93d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13377:
#0 0x00007f9396df970e epoll_wait (libc.so.6 + 0xff70e)
#1 0x000055c4ad8e9a4b n/a (Discord + 0x3654a4b)
#2 0x000055c4ad8e7390 n/a (Discord + 0x3652390)
#3 0x000055c4ad84fb09 n/a (Discord + 0x35bab09)
#4 0x000055c4ad7fc8e9 n/a (Discord + 0x35678e9)
#5 0x000055c4ad7d1167 n/a (Discord + 0x353c167)
#6 0x000055c4ad800177 n/a (Discord + 0x356b177)
#7 0x000055c4ad80bf00 n/a (Discord + 0x3576f00)
#8 0x000055c4ad851ba5 n/a (Discord + 0x35bcba5)
#9 0x00007f939832a46f start_thread (libpthread.so.0 + 0x946f)
#10 0x00007f9396df93d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13380:
#0 0x00007f9398330cf5 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xfcf5)
#1 0x000055c4ad847b0b n/a (Discord + 0x35b2b0b)
#2 0x000055c4ad8477cf n/a (Discord + 0x35b27cf)
#3 0x000055c4aebcc1a0 n/a (Discord + 0x49371a0)
#4 0x000055c4aea0e8c4 n/a (Discord + 0x47798c4)
#5 0x000055c4aea0e6b8 n/a (Discord + 0x47796b8)
#6 0x000055c4ae9f7a2a n/a (Discord + 0x4762a2a)
#7 0x000055c4aea19f08 n/a (Discord + 0x4784f08)
#8 0x000055c4aea19daa n/a (Discord + 0x4784daa)
#9 0x000055c4ac223d6d n/a (Discord + 0x1f8ed6d)
#10 0x000055c4ada7ec2a n/a (Discord + 0x37e9c2a)
#11 0x000055c4ada8468a n/a (Discord + 0x37ef68a)
#12 0x000055c4ada84242 n/a (Discord + 0x37ef242)
#13 0x000055c4ada7d4ef n/a (Discord + 0x37e84ef)
#14 0x000055c4ada7dbe0 n/a (Discord + 0x37e8be0)
#15 0x000055c4ada91d65 n/a (Discord + 0x37fcd65)
#16 0x000055c4ad7fbd1d n/a (Discord + 0x3566d1d)
#17 0x000055c4ad7fb7de n/a (Discord + 0x35667de)
#18 0x000055c4ad7b58ba n/a (Discord + 0x35208ba)
#19 0x000055c4ad7fc8e9 n/a (Discord + 0x35678e9)
#20 0x000055c4ad7d1167 n/a (Discord + 0x353c167)
#21 0x000055c4ad80bf00 n/a (Discord + 0x3576f00)
#22 0x000055c4ad851ba5 n/a (Discord + 0x35bcba5)
#23 0x00007f939832a46f start_thread (libpthread.so.0 + 0x946f)
#24 0x00007f9396df93d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13359:
#0 0x00007f9396deeabf __poll (libc.so.6 + 0xf4abf)
#1 0x00007f9397e8063b n/a (libxcb.so.1 + 0xc63b)
#2 0x00007f9397e8208f n/a (libxcb.so.1 + 0xe08f)
#3 0x00007f9397e82203 xcb_wait_for_reply64 (libxcb.so.1 + 0xe203)
#4 0x00007f9397ee4269 _XReply (libX11.so.6 + 0x41269)
#5 0x00007f939401a8a2 n/a (libGLX_nvidia.so.0 + 0xa58a2)
#6 0x00007f9393fc4c9c n/a (libGLX_nvidia.so.0 + 0x4fc9c)
#7 0x00007f93940158a1 n/a (libGLX_nvidia.so.0 + 0xa08a1)
#8 0x00007f9394015fa8 n/a (libGLX_nvidia.so.0 + 0xa0fa8)
#9 0x00007f9393fc4424 n/a (libGLX_nvidia.so.0 + 0x4f424)
#10 0x00007f9392e3a4ce n/a (libnvidia-glcore.so.440.59 + 0xe3b4ce)
#11 0x00007f9394012d54 n/a (libGLX_nvidia.so.0 + 0x9dd54)
#12 0x00007f9393fc48b8 n/a (libGLX_nvidia.so.0 + 0x4f8b8)
#13 0x00007f9392e36fdd n/a (libnvidia-glcore.so.440.59 + 0xe37fdd)
#14 0x00007f9393fc47ad n/a (libGLX_nvidia.so.0 + 0x4f7ad)
#15 0x00007f9393fc290a n/a (libGLX_nvidia.so.0 + 0x4d90a)
#16 0x00007f9393ff0633 n/a (libGLX_nvidia.so.0 + 0x7b633)
#17 0x00007f939429bc52 n/a (libGLX.so.0 + 0x14c52)
#18 0x00007f93942a2975 n/a (libGLX.so.0 + 0x1b975)
#19 0x000055c4ae2c3e77 n/a (Discord + 0x402ee77)
#20 0x000055c4aebccb86 n/a (Discord + 0x4937b86)
#21 0x000055c4aebd2bd3 n/a (Discord + 0x493dbd3)
#22 0x000055c4ae9849c0 n/a (Discord + 0x46ef9c0)
#23 0x000055c4ad7fbd1d n/a (Discord + 0x3566d1d)
#24 0x000055c4ad7fb7de n/a (Discord + 0x35667de)
#25 0x000055c4ad7be0c7 n/a (Discord + 0x35290c7)
#26 0x00007f93981ff51e g_main_context_dispatch (libglib-2.0.so.0 + 0x6a51e)
#27 0x00007f93982012d1 n/a (libglib-2.0.so.0 + 0x6c2d1)
#28 0x00007f9398201311 g_main_context_iteration (libglib-2.0.so.0 + 0x6c311)
#29 0x000055c4ad7b5ba2 n/a (Discord + 0x3520ba2)
#30 0x000055c4ad7fc8e9 n/a (Discord + 0x35678e9)
#31 0x000055c4ad7d1167 n/a (Discord + 0x353c167)
#32 0x000055c4b0682599 n/a (Discord + 0x63ed599)
#33 0x000055c4acffd4d4 n/a (Discord + 0x2d684d4)
#34 0x000055c4aedb56ec n/a (Discord + 0x4b206ec)
#35 0x000055c4ac2d0481 n/a (Discord + 0x203b481)
#36 0x000055c4ab89f27b n/a (Discord + 0x160a27b)
#37 0x00007f9396d21023 __libc_start_main (libc.so.6 + 0x27023)
#38 0x000055c4ab89f02a _start (Discord + 0x160a02a)

Stack trace of thread 13376:
#0 0x00007f939833101a pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x1001a)
#1 0x000055c4ad847320 n/a (Discord + 0x35b2320)
#2 0x000055c4ad847a62 n/a (Discord + 0x35b2a62)
#3 0x000055c4ad7b58a5 n/a (Discord + 0x35208a5)
#4 0x000055c4ad7fc8e9 n/a (Discord + 0x35678e9)
#5 0x000055c4ad7d1167 n/a (Discord + 0x353c167)
#6 0x000055c4ad80bf00 n/a (Discord + 0x3576f00)
#7 0x000055c4ad851ba5 n/a (Discord + 0x35bcba5)
#8 0x00007f939832a46f start_thread (libpthread.so.0 + 0x946f)
#9 0x00007f9396df93d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13378:
#0 0x00007f939833101a pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x1001a)
#1 0x000055c4ad847320 n/a (Discord + 0x35b2320)
#2 0x000055c4ad847a62 n/a (Discord + 0x35b2a62)
#3 0x000055c4ad8076c8 n/a (Discord + 0x35726c8)
#4 0x000055c4ad807c3b n/a (Discord + 0x3572c3b)
#5 0x000055c4ad807904 n/a (Discord + 0x3572904)
#6 0x000055c4ad851ba5 n/a (Discord + 0x35bcba5)
#7 0x00007f939832a46f start_thread (libpthread.so.0 + 0x946f)
#8 0x00007f9396df93d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13381:
#0 0x00007f939833101a pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x1001a)
#1 0x000055c4ad847320 n/a (Discord + 0x35b2320)
#2 0x000055c4ad847a62 n/a (Discord + 0x35b2a62)
#3 0x000055c4ad8076c8 n/a (Discord + 0x35726c8)
#4 0x000055c4ad8079e8 n/a (Discord + 0x35729e8)
#5 0x000055c4ad807904 n/a (Discord + 0x3572904)
#6 0x000055c4ad851ba5 n/a (Discord + 0x35bcba5)
#7 0x00007f939832a46f start_thread (libpthread.so.0 + 0x946f)

#8 0x00007f9396df93d3 __clone (libc.so.6 + 0xff3d3)
This task depends upon

Closed by  Filipe Laíns (FFY00)
Tuesday, 27 October 2020, 01:50 GMT
Reason for closing:  Fixed
Additional comments about closing:  Seems to be fixed.
Comment by Daniel Mehrmann (Akusari) - Thursday, 27 February 2020, 20:07 GMT
*** coredumctl info ***

PID: 13391 (Discord)
UID: 1000 (daniel)
GID: 985 (users)
Signal: 11 (SEGV)
Timestamp: Thu 2020-02-27 20:53:17 CET (14min ago)
Command Line: /opt/discord/Discord --type=gpu-process --field-trial-handle=14375939149685482340,18081708819681251533,131>
Executable: /opt/discord/Discord
Control Group: /user.slice/user-1000.slice/session-4.scope
Unit: session-4.scope
Slice: user-1000.slice
Session: 4
Owner UID: 1000 (daniel)
Boot ID: f9f4627153d144c3b48c9dd01832504a
Machine ID: 66c6e327b2fa4b29b60fb23c17390c40
Hostname: Homer
Storage: /var/lib/systemd/coredump/core.Discord.1000.f9f4627153d144c3b48c9dd01832504a.13391.1582833197000000000000.>
Message: Process 13391 (Discord) of user 1000 dumped core.

Stack trace of thread 13426:
#0 0x000056234018220d n/a (Discord + 0x4aab20d)
#1 0x0000562340186026 n/a (Discord + 0x4aaf026)
#2 0x00007f9e01210800 __restore_rt (libpthread.so.0 + 0x14800)
#3 0x00007f9dffc9c2d1 clock_nanosleep@@GLIBC_2.17 (libc.so.6 + 0xc72d1)
#4 0x00007f9dffca1bf7 __nanosleep (libc.so.6 + 0xccbf7)
#5 0x00007f9dffccc799 usleep (libc.so.6 + 0xf7799)
#6 0x00007f9dfbd2ebab n/a (libnvidia-glcore.so.440.59 + 0xe54bab)
#7 0x00007f9dfbd6fea0 n/a (libnvidia-glcore.so.440.59 + 0xe95ea0)
#8 0x00007f9dfbd71a26 n/a (libnvidia-glcore.so.440.59 + 0xe97a26)
#9 0x00007f9dfcecfd9f n/a (libGLX_nvidia.so.0 + 0x7fd9f)
#10 0x00007f9dfd1d63cf __glDispatchCheckMultithreaded (libGLdispatch.so.0 + 0x413cf)
#11 0x00007f9dfd17b567 n/a (libGLX.so.0 + 0x19567)
#12 0x00007f9dfd17c9c6 glXGetFBConfigs (libGLX.so.0 + 0x1a9c6)
#13 0x000056233f707e77 n/a (Discord + 0x4030e77)
#14 0x000056233f70ba42 n/a (Discord + 0x4034a42)
#15 0x000056233ec3dd1d n/a (Discord + 0x3566d1d)
#16 0x000056233ec3d7de n/a (Discord + 0x35667de)
#17 0x000056233ebf78ba n/a (Discord + 0x35208ba)
#18 0x000056233ec3e8e9 n/a (Discord + 0x35678e9)
#19 0x000056233ec13167 n/a (Discord + 0x353c167)
#20 0x000056233ec4df00 n/a (Discord + 0x3576f00)
#21 0x000056233ec93ba5 n/a (Discord + 0x35bcba5)
#22 0x00007f9e0120546f start_thread (libpthread.so.0 + 0x946f)
#23 0x00007f9dffcd43d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13409:
#0 0x00007f9e0120c01a pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x1001a)
#1 0x000056233ec89320 n/a (Discord + 0x35b2320)
#2 0x000056233ec89a62 n/a (Discord + 0x35b2a62)
#3 0x000056233ec496c8 n/a (Discord + 0x35726c8)
#4 0x000056233ec49c3b n/a (Discord + 0x3572c3b)
#5 0x000056233ec49904 n/a (Discord + 0x3572904)
#6 0x000056233ec93ba5 n/a (Discord + 0x35bcba5)
#7 0x00007f9e0120546f start_thread (libpthread.so.0 + 0x946f)
#8 0x00007f9dffcd43d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13407:
#0 0x00007f9e0120c01a pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x1001a)
#1 0x000056233ec89320 n/a (Discord + 0x35b2320)
#2 0x000056233ec89a62 n/a (Discord + 0x35b2a62)
#3 0x000056233ebf78a5 n/a (Discord + 0x35208a5)
#4 0x000056233ec3e8e9 n/a (Discord + 0x35678e9)
#5 0x000056233ec13167 n/a (Discord + 0x353c167)
#6 0x000056233ec4df00 n/a (Discord + 0x3576f00)
#7 0x000056233ec93ba5 n/a (Discord + 0x35bcba5)
#8 0x00007f9e0120546f start_thread (libpthread.so.0 + 0x946f)
#9 0x00007f9dffcd43d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13425:
#0 0x00007f9e0120c01a pthread_cond_timedwait@@GLIBC_2.3.2 (libpthread.so.0 + 0x1001a)
#1 0x000056233ec89320 n/a (Discord + 0x35b2320)
#2 0x000056233ec89a62 n/a (Discord + 0x35b2a62)
#3 0x000056233ec496c8 n/a (Discord + 0x35726c8)
#4 0x000056233ec499e8 n/a (Discord + 0x35729e8)
#5 0x000056233ec49904 n/a (Discord + 0x3572904)
#6 0x000056233ec93ba5 n/a (Discord + 0x35bcba5)
#7 0x00007f9e0120546f start_thread (libpthread.so.0 + 0x946f)
#8 0x00007f9dffcd43d3 __clone (libc.so.6 + 0xff3d3)

Stack trace of thread 13391:
#0 0x000056233ec8ca61 calloc (Discord + 0x35b5a61)
#1 0x0000000003e0000e n/a (n/a + 0x0)
Comment by Filipe Laíns (FFY00) - Thursday, 27 February 2020, 23:29 GMT
I can't reproduce.

Discord uses its own electron so please report this upstream.
Comment by Magnus Boman (katt) - Monday, 02 March 2020, 13:08 GMT
  • Field changed: Percent Complete (100% → 0%)
This is caused by opera-ffmpeg-codecs, using the included ffmpeg works perfect.
Comment by Magnus Boman (katt) - Monday, 02 March 2020, 15:26 GMT
..or so I thought, damned intermittent issues. It worked for a few hours and then back to crashing, just.. how?!
Also slight correction to title, it happens when a video is playing, plays for a few seconds and then the video player crashes.

I don't know what to do about this, I'm sorry.


EDIT: From asking around and testing, this seems to only happen on nvidia, but does not happen on discord-canary.
Comment by Alexander Pavel (SuperIce97) - Saturday, 07 March 2020, 21:46 GMT
I'm having this issue as well. I have an AMD graphics card though, so it's not just nVidia. Discord-canary works fine though
Comment by Alexander Pavel (SuperIce97) - Saturday, 07 March 2020, 21:48 GMT
Actually, it seems like nuking the config directory (~/.config/discord) fixes the problem in the official app as well.
Comment by Magnus Boman (katt) - Sunday, 08 March 2020, 16:05 GMT
Sadly nuking the .config folder does not work for me, on nvidia. Guess I'll stick with discord-canary for a bit longer.
EDIT: An update today (discord-canary) broke it there as well, oh well.. I guess that's what I get for using proprietary software.
Comment by Gustavo Alvarez (sl1pkn07) - Friday, 20 March 2020, 10:48 GMT
i have the same problem with discord-canary

seems is this bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1773289

because:

iscordCanary 0.0.102
Starting app.
Starting updater.
[Modules] Modules initializing
[Modules] Distribution: remote
[Modules] Host updates: enabled
[Modules] Module updates: enabled
[Modules] Module install path: /home/sl1pkn07/.config/discordcanary/0.0.102/modules
[Modules] Module installed file path: /home/sl1pkn07/.config/discordcanary/0.0.102/modules/installed.json
[Modules] Module download path: /home/sl1pkn07/.config/discordcanary/0.0.102/modules/pending
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230
[Modules] No updates to install
[Modules] Checking for host updates.
[Modules] Host is up to date.
[Modules] Checking for module updates at https://discordapp.com/api/modules/canary/versions.json
[Modules] No module updates available.
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230
../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230
(electron) 'isAccessibilitySupportEnabled function' is deprecated and will be removed. Please use 'accessibilitySupportEnabled property' instead.
(electron) 'setBadgeCount function' is deprecated and will be removed. Please use 'badgeCount property' instead.
--snip--
Comment by loqs (loqs) - Friday, 20 March 2020, 20:02 GMT
If you downgrade glibc to 2.30-3 can you still reproduce the issue?
Comment by Gustavo Alvarez (sl1pkn07) - Friday, 20 March 2020, 20:09 GMT
the error

../../sandbox/linux/seccomp-bpf-helpers/sigsys_handlers.cc:**CRASHING**:seccomp-bpf failure in syscall 0230

is gone with glibc 2.30-3

but need more time for test it

EDIT: after reboot, the SGI_Video, the segfault at start and the seccomp-bpf message is gone
Comment by Magnus Boman (katt) - Friday, 20 March 2020, 21:07 GMT
Holy shit, yes! downgrading glibc to 2.30-3 fixes it!
Comment by grayarcher (grayarcher) - Saturday, 21 March 2020, 15:44 GMT
The root cause here is a change in glibc, as noted by the 2.31 release notes:

* System call wrappers for time system calls now use the new time64
system calls when available. On 32-bit targets, these wrappers
attempt to call the new system calls first and fall back to the
older 32-bit time system calls if they are not present. This may
cause issues in environments that cannot handle unsupported system
calls gracefully by returning -ENOSYS. Seccomp sandboxes are
affected by this issue.

Since it's the individual applications like Discord, or any other electron/CEF based/like app that apply the seccomp filter, they will have to adjust their filters. Until that happens, the options are:
- Patch the individual binaries to allow clock_gettime64, similary to how the source code changed in upstream chromium for a previous issue: https://github.com/chromium/chromium/commit/54407b422a9cbf775a68c1d57603c0ecac8ce0d7#diff-76dd4327967fba9837d93a944eeb1165

(A similar change was commited to OpenSSH https://github.com/openssh/openssh-portable/commit/ccd3b247d59d3bde16c3bef0ea888213fbd6da86#diff-5039537cc0e0b50db6f66642be1248fa )
- Downgrade glibc/revert that specific change in glibc
Comment by loqs (loqs) - Saturday, 21 March 2020, 16:10 GMT
Has anyone reported the issue to upstream?
Comment by Domenico Iezzi (nomore66201) - Saturday, 21 March 2020, 16:14 GMT
Bug reporting for desktop clients is currently disabled on Discord Testers channel, don't know why and when it will be re-opened.
Comment by Filipe Laíns (FFY00) - Saturday, 21 March 2020, 16:30 GMT
Thanks for investigating this, I will contact Discord directly.
Comment by Gustavo Alvarez (sl1pkn07) - Sunday, 22 March 2020, 18:39 GMT
discord tester channel is up. i send the bug, but the bug tracking system is a little.... meh

EDIT: oh, with "discord tester channel is down" you refeer you can paste the bugreport in the bug-bot ... interesting
Comment by Mattia Moffa (altermetax) - Tuesday, 21 April 2020, 23:21 GMT
So did the bug ever get reported? I tried to but I still can't write to the #linux-bug-reports channel.
Comment by Filipe Laíns (FFY00) - Tuesday, 21 April 2020, 23:25 GMT
I've reached out to my contact but haven't heard anything back.
Comment by Gustavo Alvarez (sl1pkn07) - Wednesday, 22 April 2020, 14:14 GMT
i have done package discord(canary) with [comunity] electron instead of bundled electron

~~~
prepare() {
sed 's|/usr/share/discord-canary/DiscordCanary|discord-canary|g' -i DiscordCanary/discord-canary.desktop
}

package() {
# Install the main files.
install -dm755 -g 100 "${pkgdir}/opt/discord-canary"
(cd "${srcdir}/DiscordCanary"; for i in $(find resources -type f) ; do install -Dm644 "${i}" "${pkgdir}/opt/discord-canary/${i}"; done)
install -Dm644 "${srcdir}/DiscordCanary/discord-canary.desktop" "${pkgdir}/usr/share/applications/discord-canary.desktop"
install -Dm644 "${srcdir}/DiscordCanary/discord.png" "${pkgdir}/usr/share/pixmaps/discord-canary.png"
(cd /usr/lib/electron; for i in $(find . -type f \( ! -name resources \)); do install -Dm644 "${i}" "${pkgdir}/opt/discord-canary/${i}"; done)

# Exec bit
mv "${pkgdir}/opt/discord-canary/electron" "${pkgdir}/opt/discord-canary/DiscordCanary"
chmod 755 "${pkgdir}/opt/discord-canary/DiscordCanary"

# setuid on chrome-sandbox
chmod u+s "${pkgdir}/opt/discord-canary/chrome-sandbox"

# Main binary
install -d "${pkgdir}/usr/bin"
ln -s "/opt/discord-canary/DiscordCanary" "${pkgdir}/usr/bin/discord-canary"

# License
install -Dm644 "${srcdir}/LICENSE" "${pkgdir}/usr/share/licenses/${pkgname}/LICENSE"

}
~~~

this copy [comunity] electron in the discord installation. is preferable use it instead of make a copy (symlink also not works), but idk how (always run base electron instead run discord with it)

i'm not sure if the distro side can change this and distribute, but as for personal package is done

greetings
Comment by Filipe Laíns (FFY00) - Wednesday, 22 April 2020, 14:56 GMT
I also have a canary PKGBUILD. We usually don't put such versions in the repos, but this in this case, since Discord is not responding, I could do it. Can you confirm it definitely solved the issue?
Comment by Gustavo Alvarez (sl1pkn07) - Wednesday, 22 April 2020, 15:01 GMT
no. only is use discord with external electron instead of bundled, canary or not, the error still persist if use bundled discord electron
Comment by Mattia Moffa (altermetax) - Wednesday, 22 April 2020, 16:09 GMT
I somehow managed to report it to upstream, they said they'll forward this bug report page here to Discord devs. Until it's fixed, even though it's a hack, having the PKGBUILD above (using [community]electron instead of the bundled one) in the repos could help (but for the actual Discord rather than for Canary maybe).
Comment by Mattia Moffa (altermetax) - Thursday, 23 April 2020, 00:39 GMT
They updated me on the situation, looks like they can reproduce the issue and found the culprit for it. Hopefully it will be fixed soon :)
Comment by Léo (Leeo97one) - Tuesday, 28 April 2020, 15:38 GMT
Disabling "Hardware Acceleration" in Discord Appearance settings seems to be another workaround.
Comment by Mattia Moffa (altermetax) - Sunday, 10 May 2020, 12:03 GMT
I'm not entirely sure, but it seems fixed now. Could other people check?
Comment by Magnus Boman (katt) - Sunday, 10 May 2020, 12:09 GMT
Still happens here, tried wiping ~/.config/discord and disabling hardware acceleration, doesn't help. Some videos seem to work, most don't.
Comment by Mattia Moffa (altermetax) - Sunday, 10 May 2020, 12:17 GMT
Happens again here, too. I don't know why it worked for one single run of it.
Comment by Nat Amundsen (osakasys) - Sunday, 17 May 2020, 08:40 GMT
Can confirm this still happens on 0.0.10. I downgraded to 0.0.9 and changed `version` in `/opt/discord/resources/build_info.json` to `0.0.10` in order to get it to launch and the bug does not occur.

On 0.0.10, I get this output a few seconds into a video OR by opening the inspector window when docked at the bottom (bug does not occur when inspector window is its own window). I've attached the crash log as a file to reduce comment space.
Comment by Mattia Moffa (altermetax) - Saturday, 23 May 2020, 13:07 GMT
It doesn't happen to me on the AUR Discord Canary anymore (without changing the PKGBUILD as explained above). It still happens with the official Canary from their website though.
Comment by Mattia Moffa (altermetax) - Wednesday, 16 September 2020, 17:27 GMT
I don't know when, but this appears to have finally been solved. Can anyone else confirm?
Comment by Jimi Bove (Jimi-James) - Wednesday, 16 September 2020, 20:30 GMT
I never stopped using the Discord client for voice chat often, and I can confirm that it's been at least several weeks since my last segfault. I'm in the normal repos--I never switched to any AUR version.
Comment by loqs (loqs) - Thursday, 17 September 2020, 16:31 GMT
If it has been working for several weeks the fix would be in discord 0.0.11-1 as discord 0.0.12-1 was only released a week ago [1].

[1] https://github.com/archlinux/svntogit-community/commit/d8ddba860c5a765428b5eb7236668a094d9e622d
Comment by Daniel Mehrmann (Akusari) - Thursday, 17 September 2020, 22:03 GMT
I don't run Arch with this (reported) hardware configuration any more. So, as the creator of this bug i can't confirm anything. However, it was a shame that this ticket was closed by the package maintainer with the stupid reason that he can't reproduce this bug, which only happend with a special hardware combination (ryzen+nvidia). This is simply a unprofessional behavior.
Comment by Jimi Bove (Jimi-James) - Thursday, 17 September 2020, 22:14 GMT
Oh, excuse me. I can't confirm anything. Your comment about NVidia, when I use AMD, made me realize I had this bug confused with another bug, in which Discord would segfault randomly and often during a voice chat. I assumed that bug was this one because I have been aware of no other Discord bug recently, and I'm genuinely confused as to how I ended up subscribed to this one.
Comment by Mattia Moffa (altermetax) - Saturday, 24 October 2020, 00:46 GMT
So, can this bug be closed? Can anyone still reproduce it?
Comment by Magnus Boman (katt) - Saturday, 24 October 2020, 11:23 GMT
As the one who re-opened this to begin with I feel obliged to comment, I've since moved to the discord_arch_electron for a 10x better experience and can't comment on this one.
Comment by Andres David Ortiz (zany130) - Monday, 26 October 2020, 21:54 GMT
this has been solved at least for me for a while now

Loading...