You are not logged in.
I've been running discord with no issue until today. After upgrading to kernel 6.13 I am getting the following in the output when starting discord (package, not flatpak):
16:58:49.577 › [injectMediaEngine] Potentially corrupt installation: /home/user/.config/discord/0.0.82/modules/discord_voice/discord_voice.node: cannot enable executable stack as shared object requires: Invalid argument
The discord application launches but there's no microphone or audio, a red banner says that the installation might be corrupt, and of course reinstalling it doesn't do anything. The list of updated packages is as follows:
[2025-02-03T16:29:59+0100] [ALPM] upgraded glibc (2.40+r66+g7d4b6bcae91f-1 -> 2.41+r2+g0a7c7a3e283a-1)
[2025-02-03T16:30:00+0100] [ALPM] upgraded gcc-libs (14.2.1+r134+gab884fffe3fc-2 -> 14.2.1+r730+gc061ad5a36ba-1)
[2025-02-03T16:30:00+0100] [ALPM] upgraded libelf (0.192-2 -> 0.192-3)
[2025-02-03T16:30:01+0100] [ALPM] upgraded nvidia-utils (565.77-3 -> 570.86.16-2)
[2025-02-03T16:30:01+0100] [ALPM] upgraded libsysprof-capture (47.2-1 -> 47.2-2)
[2025-02-03T16:30:01+0100] [ALPM] upgraded alligator (24.12.1-1 -> 24.12.1-2)
[2025-02-03T16:30:01+0100] [ALPM] upgraded binutils (2.43_1+r171+g01da089627be-1 -> 2.43_1+r186+g61f8adadd6db-1)
[2025-02-03T16:30:01+0100] [ALPM] upgraded debuginfod (0.192-2 -> 0.192-3)
[2025-02-03T16:30:01+0100] [ALPM] upgraded elfutils (0.192-2 -> 0.192-3)
[2025-02-03T16:30:01+0100] [ALPM] upgraded libtool (2.5.4+r1+gbaa1fe41-1 -> 2.5.4+r1+gbaa1fe41-2)
[2025-02-03T16:30:01+0100] [ALPM] upgraded francis (24.12.1-1 -> 24.12.1-2)
[2025-02-03T16:30:01+0100] [ALPM] upgraded mpfr (4.2.1-4 -> 4.2.1-5)
[2025-02-03T16:30:02+0100] [ALPM] upgraded gcc (14.2.1+r134+gab884fffe3fc-2 -> 14.2.1+r730+gc061ad5a36ba-1)
[2025-02-03T16:30:02+0100] [ALPM] upgraded shiboken6 (6.8.1.1-3 -> 6.8.2-1)
[2025-02-03T16:30:02+0100] [ALPM] upgraded pyside6 (6.8.1.1-3 -> 6.8.2-1)
[2025-02-03T16:30:02+0100] [ALPM] upgraded freecad (1.0.0-3 -> 1.0.0-5)
[2025-02-03T16:30:02+0100] [ALPM] upgraded kalk (24.12.1-2 -> 24.12.1-3)
[2025-02-03T16:30:02+0100] [ALPM] upgraded kasts (24.12.1-1 -> 24.12.1-2)
[2025-02-03T16:30:02+0100] [ALPM] upgraded kclock (24.12.1-1 -> 24.12.1-2)
[2025-02-03T16:30:02+0100] [ALPM] upgraded koko (24.12.1-1 -> 24.12.1-2)
[2025-02-03T16:30:02+0100] [ALPM] upgraded kongress (24.12.1-1 -> 24.12.1-2)
[2025-02-03T16:30:02+0100] [ALPM] upgraded kweather (24.12.1-1 -> 24.12.1-2)
[2025-02-03T16:30:02+0100] [ALPM] upgraded lib32-glibc (2.40+r66+g7d4b6bcae91f-1 -> 2.41+r2+g0a7c7a3e283a-1)
[2025-02-03T16:30:03+0100] [ALPM] upgraded lib32-gcc-libs (14.2.1+r134+gab884fffe3fc-2 -> 14.2.1+r730+gc061ad5a36ba-1)
[2025-02-03T16:30:03+0100] [ALPM] upgraded lib32-nvidia-utils (565.77-1 -> 570.86.16-1)
[2025-02-03T16:30:03+0100] [ALPM] upgraded libkolabxml (1.3.1-2 -> 1.3.1-4)
[2025-02-03T16:30:03+0100] [ALPM] upgraded libxnvctrl (565.57.01-1 -> 570.86.16-1)
[2025-02-03T16:30:04+0100] [ALPM] upgraded linux (6.12.10.arch1-1 -> 6.13.1.arch1-1)
[2025-02-03T16:30:06+0100] [ALPM] upgraded linux-headers (6.12.10.arch1-1 -> 6.13.1.arch1-1)
[2025-02-03T16:30:06+0100] [ALPM] upgraded nvidia-dkms (565.77-3 -> 570.86.16-2)
[2025-02-03T16:30:06+0100] [ALPM] upgraded nvidia-settings (565.57.01-1 -> 570.86.16-1)
[2025-02-03T16:30:06+0100] [ALPM] upgraded opencl-nvidia (565.77-3 -> 570.86.16-2)
[2025-02-03T16:30:06+0100] [ALPM] upgraded plasmatube (24.12.1-1 -> 24.12.1-2)
[2025-02-03T16:30:06+0100] [ALPM] upgraded postgresql-libs (17.2-1 -> 17.2-2)
[2025-02-03T16:30:06+0100] [ALPM] upgraded python-certifi (2024.12.14-1 -> 2025.01.31-1)
[2025-02-03T16:30:06+0100] [ALPM] upgraded python-ytmusicapi (1.9.1-1 -> 1.10.1-1)
[2025-02-03T16:30:06+0100] [ALPM] upgraded rsync (3.4.1-1 -> 3.4.1-2)
[2025-02-03T16:30:07+0100] [ALPM] upgraded signal-desktop (7.40.0-1 -> 7.40.1-1)
[2025-02-03T16:30:07+0100] [ALPM] upgraded valgrind (3.24.0-1 -> 3.24.0-2)
[2025-02-03T16:30:07+0100] [ALPM] upgraded virtualbox-host-modules-arch (7.1.6-1 -> 7.1.6-4)
I am not sure if it's the kernel update, or glibc, or something else. I tried switching to the flatpak version but that has never worked for me on hyprland+wayland, it just segfaults. Anyone else having the same issue?
EDIT: The tar.gz version from discord.com exhibits the exact same behavior.
Last edited by Dividebysandwich (2025-02-03 16:17:25)
Offline
Perhaps you missed reading the news?
https://archlinux.org/
Specifically:
Glibc 2.41 corrupting Discord installation
Offline
*facepalm* Indeed, I did not think to check the main news. Sorry for that.
Offline
Offline
omfg -_- I'm about 1 hour debugging discord and didn't read the news lol thanks for the post and the answer guys!
Offline
Thanks for bringing this up. I also faced that bug
Offline
I would encourage everyone to subscribe to the arch-announce mailing list or RSS/ATOM news feeds. When things are posted to the news, it's for a reason.
Online
Is anyone still having the same issue after installing the `discord-canary` package?
Edit: in case anyone also did the dumb thing I did, discord and discord canary don't actually conflict, the binary is `discord-canary` and I was still launching the `discord` binary.
Last edited by Typology (2025-02-03 19:06:03)
Offline
I would encourage everyone to subscribe to the arch-announce mailing list or RSS/ATOM news feeds. When things are posted to the news, it's for a reason.
Will do. I am not used to news announcements on websites in general being useful
Last edited by Dividebysandwich (2025-02-04 13:37:49)
Offline