Closed fzwoch closed 1 year ago
#0 0x00007fffeb859715 in () at /lib/x86_64-linux-gnu/libappindicator3.so.1
#1 0x00007ffff7f503b0 in g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#2 0x00007ffff7f63076 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3 0x00007ffff7f69bf5 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4 0x00007ffff7f69dbf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5 0x00007fffeb8584e7 in app_indicator_set_icon_full () at /lib/x86_64-linux-gnu/libappindicator3.so.1
At least a stack trace, although no symbols.
Thread 1 "Discord" received signal SIGSEGV, Segmentation fault.
0x00007fffeb058715 in status_icon_changes (self=0x237751a2f2f0, data=<optimized out>) at ./src/app-indicator.c:1623
1623 ./src/app-indicator.c: No such file or directory.
(gdb) bt
#0 0x00007fffeb058715 in status_icon_changes (self=0x237751a2f2f0, data=<optimized out>) at ./src/app-indicator.c:1623
#1 0x00007ffff7f503b0 in g_closure_invoke () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#2 0x00007ffff7f63076 in () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#3 0x00007ffff7f69bf5 in g_signal_emit_valist () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4 0x00007ffff7f69dbf in g_signal_emit () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5 0x00007fffeb0574e7 in app_indicator_set_icon_full
(self=0x237751a2f2f0, icon_name=0x2377528f90d1 "discord1_4085", icon_desc=0x5555562f83bb "icon") at ./src/app-indicator.c:2021
#6 0x00005555574aeebd in ()
#7 0x0000000000000000 in ()
(gdb) info locals
path = 0x2377532e6000
n_elements = 4096
i = 840704
found = 0
icon = 0x237751ec3c30
priv = <optimized out>
icon_theme = 0x237751cabe40
theme_path = <optimized out>
icon_name = <optimized out>
There has been a Discord update 3 weeks ago. I haven't had a crash since. So I guess it was Discord at fault..
This looks similar to #54.
It has been working fine since the above fix for quite some some. Within the last couple weeks I have seen crashes again:
Not sure if it is the same issue, or another one. Could be a Discord update that does something differently now?
However the time span it starting happening again seems to be in line with the release of
0.5.92
and when the update got pushed to Debian unstable.Unfortunately I don't have any stack traces as of yet.