You are not logged in.

Pages: 1

#1 2020-12-29 13:12:24

archuser7465
Member
Registered: 2020-06-06
Posts: 3

Discord crashes when trying to screen share

I can't share my screen on discord without it crashing... The weird thing is it works fine if I run discord via cli.
What I tried:
- turning discord's hardware acceleration on/off
- starting discord without picom
- ...

Some helpful information about my system:
I'm using dwm, picom and I launch discord with rofi.
In nvidia-settings I have force full composition enabled (this helped me fix screen tearing).

$ uname -r
5.9.14-arch1-1

$ lspci -k | grep -A 2 -E "(VGA|3D)"
01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1)
	Subsystem: Micro-Star International Co., Ltd. [MSI] Device 3354
	Kernel driver in use: nvidia

$ discord --version
Discord 0.0.13
(node:35746) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Starting app.
Starting updater.
[Modules] Modules initializing
[Modules] Distribution: remote
[Modules] Host updates: enabled
[Modules] Module updates: enabled
[Modules] Module install path: /home/branco/.config/discord/0.0.13/modules
[Modules] Module installed file path: /home/branco/.config/discord/0.0.13/modules/installed.json
[Modules] Module download path: /home/branco/.config/discord/0.0.13/modules/pending

$ nvidia-smi
Tue Dec 29 14:04:54 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 455.45.01    Driver Version: 455.45.01    CUDA Version: 11.1     |

$ journalctl -r
Dec 29 14:07:39 arch audit: BPF prog-id=16 op=UNLOAD
Dec 29 14:07:39 arch audit: BPF prog-id=17 op=UNLOAD
Dec 29 14:07:39 arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@2-38222-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? >
Dec 29 14:07:40 arch kernel: audit: type=1334 audit(1609247259.791:211): prog-id=16 op=UNLOAD
Dec 29 14:07:40 arch kernel: audit: type=1334 audit(1609247259.791:210): prog-id=17 op=UNLOAD
Dec 29 14:07:40 arch kernel: audit: type=1131 audit(1609247259.774:209): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-coredump@2-38222-0 comm="systemd" exe="/usr/lib/system>
Dec 29 14:07:39 arch systemd[1]: systemd-coredump@2-38222-0.service: Succeeded.
Dec 29 14:07:39 arch systemd-coredump[38223]: Process 32185 (Discord) of user 1000 dumped core.

                                              Stack trace of thread 38216:
                                              #0  0x00007f71ef1e25df _XReply (libX11.so.6 + 0x415df)
                                              #1  0x00007f71ef1cefc3 XListExtensions (libX11.so.6 + 0x2dfc3)
                                              #2  0x0000557e2397ac8b n/a (Discord + 0x4981c8b)
                                              #3  0x0000557e22cef743 n/a (Discord + 0x3cf6743)
                                              #4  0x0000557e22d00254 n/a (Discord + 0x3d07254)
                                              #5  0x0000557e22cfffe2 n/a (Discord + 0x3d06fe2)
                                              #6  0x0000557e22cc16b1 n/a (Discord + 0x3cc86b1)
                                              #7  0x0000557e22d00844 n/a (Discord + 0x3d07844)
                                              #8  0x0000557e22cda81e n/a (Discord + 0x3ce181e)
                                              #9  0x0000557e22d16227 n/a (Discord + 0x3d1d227)
                                              #10 0x0000557e22d4f3e5 n/a (Discord + 0x3d563e5)
                                              #11 0x00007f71ef6403e9 start_thread (libpthread.so.0 + 0x93e9)
                                              #12 0x00007f71edfe8293 __clone (libc.so.6 + 0x100293)

                                              Stack trace of thread 32195:
                                              #0  0x00007f71edfe85de epoll_wait (libc.so.6 + 0x1005de)
                                              #1  0x0000557e22e537ea n/a (Discord + 0x3e5a7ea)
                                              #2  0x0000557e22e5102b n/a (Discord + 0x3e5802b)
                                              #3  0x0000557e22d5aee3 n/a (Discord + 0x3d61ee3)
                                              #4  0x0000557e22d00844 n/a (Discord + 0x3d07844)
                                              #5  0x0000557e22cda81e n/a (Discord + 0x3ce181e)
                                              #6  0x0000557e221d3dc4 n/a (Discord + 0x31dadc4)
                                              #7  0x0000557e22d16227 n/a (Discord + 0x3d1d227)
                                              #8  0x0000557e22d4f3e5 n/a (Discord + 0x3d563e5)
                                              #9  0x00007f71ef6403e9 start_thread (libpthread.so.0 + 0x93e9)
                                              #10 0x00007f71edfe8293 __clone (libc.so.6 + 0x100293)

                                              Stack trace of thread 32192:
                                              #0  0x00007f71edfb4eef wait4 (libc.so.6 + 0xcceef)
                                              #1  0x0000557e22d4af3d n/a (Discord + 0x3d51f3d)
                                              #2  0x0000557e22d48540 n/a (Discord + 0x3d4f540)
                                              #3  0x0000557e22d4f3e5 n/a (Discord + 0x3d563e5)
                                              #4  0x00007f71ef6403e9 start_thread (libpthread.so.0 + 0x93e9)
                                              #5  0x00007f71edfe8293 __clone (libc.so.6 + 0x100293)

                                              Stack trace of thread 32186:
                                              #0  0x00007f71edfdd46f __poll (libc.so.6 + 0xf546f)
                                              #1  0x0000557e22507952 n/a (Discord + 0x350e952)
                                              #2  0x0000557e22d4f3e5 n/a (Discord + 0x3d563e5)
                                              #3  0x00007f71ef6403e9 start_thread (libpthread.so.0 + 0x93e9)
                                              #4  0x00007f71edfe8293 __clone (libc.so.6 + 0x100293)

                                              Stack trace of thread 32207:

Offline

#2 2021-01-31 23:13:10

tassilobalbo
Member
Registered: 2021-01-31
Posts: 1

Re: Discord crashes when trying to screen share

I'm having the same problem on my system for a very long time

Offline

#3 2021-02-05 17:03:19

Galestrike
Member
Registered: 2021-02-05
Posts: 1

Re: Discord crashes when trying to screen share

I've been having this issue as of recently with AwesomeWM and I think I just found a quick solution. Screen sharing has always working in other WMs like GNOME and Plasma, even in Wayland with NVIDIA proprietary graphics, just not on Awesome for me. I recently just solved this because you can only screen share windows that are open on the current tag. Hopefully this gets you a bit closer to figuring out your problem but it seems like a window manager problem to me.

Offline

#4 2021-03-11 12:26:24

ankkax_
Member
Registered: 2021-03-11
Posts: 1

Re: Discord crashes when trying to screen share

Hi, I had same problem I just had to register to the forum to answer you, I installed   discord_arch_electron from AUR. and screensharing seems to works now I don't know why.

Offline

#5 2021-03-12 08:35:39

nunopenim
Member
From: Portugal
Registered: 2021-03-06
Posts: 22

Re: Discord crashes when trying to screen share

In my installation, I fixed this by disabling Wayland. I know it might not be ideal... but it works.

Check my GitHub here: github.com/nunopenim

I apologize in advance if some of my comments or replies don't make any sense, English is not my main language, although I try! Thank you for understanding, you can also point out stuff I misspell or just doesn't sound right.

Offline

#6 2021-04-22 11:39:17

kgofhedgehogs
Member
Registered: 2021-04-22
Posts: 1

Re: Discord crashes when trying to screen share

I have exactly the same problem on BSPWM. discord_arch_electron works as a solution too, but it has some performance issues for me. The workaround I found is that the discord shouldn't be the only window on the current desktop at the moment when you click "share your screen" button

Offline

#7 2021-06-11 00:43:44

rcorre
Member
Registered: 2015-11-27
Posts: 65

Re: Discord crashes when trying to screen share

I use dwm, and Galestrike's workaround worked for me. If I try to screenshare in "maximized" mode, where only Discord is visible (even if other windows are open on the same workspace), it crashes.
If I switch to a tiled layout and have discord visible next to something else, I can start a share just fine.
Once it is started, I can switch back to maximized without crashing.

Offline

Pages: 1

Board footer

Powered by FluxBB