Source
r/kde•
RealNC

Log spamming when starting discord through its desktop file

Question

This is some weird behavior that suddenly started happening. When starting discord through its application menu entry, my system log is getting spammed with weird trace messages:

(audio_device_impl.cc:625): SetStereoPlayout(1)
(audio_device_impl.cc:620): output: 1
(audio_mixer_manager_pulse_linux.cc:189): audio_device_impl.cc:613): audio_device_impl.cc:709): SetPlayoutDevice(0)
(audio_device_impl.cc:821): PlayoutIsInitialized

Especially this one is spammed forever with no end, and my system log is now full with it:

(device_info_linux.cc:45): NumberOfDevices

None of this happens when I start discord from the command-line with /usr/bin/discord.

Does someone know what is happening?

Posted Apr 20, 2022, 8:38 PM UTC

95
nalthien•

Hey to folks on this thread - sorry for the pings u/Leeo97one and u/Granat1 -- but, I was able to get the logs to stop so I wanted to make sure you saw it. I believe it's due to GDM and SDDM both directing logging into the systemd journal rather than the intended log files. Discord is trying to collect some data; but, they didn't account for this behavior. Here's how to get Discord to stop spamming your logs:

User Settings > Voice & Video > Scroll to bottom > Disable "Debug Logging"

Discord will need to restart; but, it will no longer be polluting your journal!

5
[deleted]•

[deleted]

2
asday_•

Beautiful this was it, thanks.

1
Warmier•

Was running into this same issue, thanks for the fix!

1
Leeo97one•

OMG, thanks! xD

1
RealNCOP•

Thank you! That was indeed the issue. Never would have expected a debug option to be enabled by default.

1
Leeo97one•

Yup, same for me and I reported it to Discord support.

2
Granat1:arch:•

It's not only spamming the log, it also causes the system to periodically freeze.
Thanks for the tip with running it from a command line!

EDIT:
Ah, I'm on Gnome tho so it's not a problem isolated to KDE or anything like that.
Just discord and its electron…

1
telmer6:kubuntu:•

Managed to crash KWin for me and prevent me from logging in after rebooting. The log file filled 1.1TB on my `/home` drive. 🤦

1
Granat1:arch:•

Oh wow, I actually forgot about this issue.

1
eldorel•

Just discovered that this bug and unplugging a usb webcam before bed bloated my .xsession-errors to 277GB while I slept.

I would have been bigger, but it ran out of space.

1
ttys3-net•

see https://wiki.archlinux.org/title/Discord#Discord_spams_systemd_journal

You may find that Discord creates a lot of messages in your journal in a format like:

(device_info_linux.cc:45): NumberOfDevices To disable the logging that causes this pollution: go to User Settings, select "Voice & Video", scroll to bottom of the screen and disable "Debug Logging".

1