(P.S. I had just rebooted a minute or two earlier, so rebooting
is obviously not going to help.)
Michael F. Stemper wrote:
(P.S. I had just rebooted a minute or two earlier, so rebooting
is obviously not going to help.)
If I'm understanding this rebooting report correctly;
- everything had been working correctly for a year
- you rebooted
- a minute or two later nothing was working
I highly recommend rebooting. There's the possibility of a 'spurious' reboot result.
Mike Easter wrote:
Michael F. Stemper wrote:
(P.S. I had just rebooted a minute or two earlier, so rebooting
is obviously not going to help.)
If I'm understanding this rebooting report correctly;
- everything had been working correctly for a year
- you rebooted
- a minute or two later nothing was working
I highly recommend rebooting. There's the possibility of a 'spurious'
reboot result.
Well, I just rebooted and it had no effect on the issue.
(To be clear, I had rebooted multiple times throughout the
previous year, not just the one time immediately before
the problem.)
Thursday morning, I fired up discord for a chat with my son, as
I do every week. I couldn't hear him and he couldn't hear me.
Going to Settings/Voice & Video, I found that the drop-downs for
"INPUT DEVICE" and "OUTPUT DEVICE" showed "No Input Devices" and
"No Output Devices", respectively, as well as being greyed out.
Not only it didn't recognize my USB headphone/mic unit, but
it didn't recognize the mic in my webcam. This even though it
recognized the camera part of my webcam.
This is a laptop, so it also has built-in mic and speakers. They
didn't show up either. Strictly "No Input Devices" and "No Output
Devices".
All of the devices appeared in and were accessible by the desktop's
"Sound Settings" panel. I could send test sounds to my headphones
and see the VU meter change when tapping the mic.
I've been using discord for weekly calls for over a year and prior
to this week it always recognized my hardware just fine.
Have any other discord (on Ubuntu) users encountered this? Does
anybody have any suggestions on how to trouble-shoot?
(P.S. I had just rebooted a minute or two earlier, so rebooting
is obviously not going to help.)
Michael F. Stemper wrote:
Mike Easter wrote:
Michael F. Stemper wrote:
I see.
The point I was trying to make is that any given boot or reboot can result in something being 'wrong' but the 'wrongness' isn't 'real' or ongoing, but spurious.
In any case, you've clarified that the condition isn't just due to a spurious re/boot.
Further troubleshooting is necessary.
On 25/06/2022 12.43, Mike Easter wrote:
Michael F. Stemper wrote:
Mike Easter wrote:
Michael F. Stemper wrote:
[discord not recognizing any mics or speakers]
I see.I highly recommend rebooting. There's the possibility of a 'spurious' reboot result.
Well, I just rebooted and it had no effect on the issue.
(To be clear, I had rebooted multiple times throughout the
previous year, not just the one time immediately before
the problem.)
The point I was trying to make is that any given boot or reboot can result in something being 'wrong' but the 'wrongness' isn't 'real' or ongoing, but spurious.
In any case, you've clarified that the condition isn't just due to a spurious re/boot.
Further troubleshooting is necessary.
Better than syslog, I just captured some of the copious stderr
from discord. This looks as if it might be a clue:
[2022-06-28 08:19:13.155] [9647] (audio_device_impl.cc:299): PulseAudio support is enabled.
[2022-06-28 08:19:13.155] [9647] (audio_mixer_manager_pulse_linux.cc:57): AudioMixerManagerLinuxPulse created
[2022-06-28 08:19:13.155] [9647] (audio_device_pulse_linux.cc:81): AudioDeviceLinuxPulse created
[2022-06-28 08:19:13.155] [9647] (audio_device_impl.cc:304): Linux PulseAudio APIs will be utilized
[2022-06-28 08:19:13.155] [9647] (audio_device_impl.cc:345): AttachAudioBuffer
[2022-06-28 08:19:13.155] [9647] (audio_device_buffer.cc:180): SetRecordingSampleRate(0)
[2022-06-28 08:19:13.155] [9647] (audio_device_buffer.cc:186): SetPlayoutSampleRate(0)
[2022-06-28 08:19:13.155] [9647] (audio_device_buffer.cc:200): SetRecordingChannels(0)
[2022-06-28 08:19:13.155] [9647] (audio_device_buffer.cc:206): SetPlayoutChannels(0)
[2022-06-28 08:19:13.155] [9647] (audio_engine.cpp:48): Creating audio engine: standard
[2022-06-28 08:19:13.155] [9647] (audio_device_impl.cc:365): Init
shm_open() failed: No such file or directory
[2022-06-28 08:19:13.162] [9647] (audio_device_pulse_linux.cc:1625): failed to connect to PulseAudio sound server
[2022-06-28 08:19:13.162] [9647] (audio_device_pulse_linux.cc:144): failed to initialize PulseAudio
[2022-06-28 08:19:13.162] [9647] (audio_device_impl.cc:374): Audio device initialization failed.
[2022-06-28 08:19:13.162] [9647] (audio_coding.cpp:143): Using software Opus decoder
I know that pulse is running because I can see it in top.
Where do I go from here?
Michael F. Stemper wrote:
Mike Easter wrote:
Michael F. Stemper wrote:
I see.I highly recommend rebooting. There's the possibility of a 'spurious' reboot result.
Well, I just rebooted and it had no effect on the issue.
(To be clear, I had rebooted multiple times throughout the
previous year, not just the one time immediately before
the problem.)
The point I was trying to make is that any given boot or reboot can result in something being 'wrong' but the 'wrongness' isn't 'real' or ongoing, but spurious.
In any case, you've clarified that the condition isn't just due to a spurious re/boot.
Further troubleshooting is necessary.
On 6/28/2022 9:24 AM, Michael F. Stemper wrote:
On 25/06/2022 12.43, Mike Easter wrote:
Michael F. Stemper wrote:
Mike Easter wrote:
Michael F. Stemper wrote:
[discord not recognizing any mics or speakers]
I see.I highly recommend rebooting. There's the possibility of a 'spurious' reboot result.
Well, I just rebooted and it had no effect on the issue.
(To be clear, I had rebooted multiple times throughout the
previous year, not just the one time immediately before
the problem.)
The point I was trying to make is that any given boot or reboot can result in something being 'wrong' but the 'wrongness' isn't 'real' or ongoing, but spurious.
In any case, you've clarified that the condition isn't just due to a spurious re/boot.
Further troubleshooting is necessary.
Better than syslog, I just captured some of the copious stderr
from discord. This looks as if it might be a clue:
[2022-06-28 08:19:13.162] [9647] (audio_device_pulse_linux.cc:1625): failed to connect to PulseAudio sound server
[2022-06-28 08:19:13.162] [9647] (audio_device_pulse_linux.cc:144): failed to initialize PulseAudio
[2022-06-28 08:19:13.162] [9647] (audio_device_impl.cc:374): Audio device initialization failed.
[2022-06-28 08:19:13.162] [9647] (audio_coding.cpp:143): Using software Opus decoder
I know that pulse is running because I can see it in top.
Where do I go from here?
Run the non-Snap version.
On 28/06/2022 08.33, Paul wrote:
On 6/28/2022 9:24 AM, Michael F. Stemper wrote:
On 25/06/2022 12.43, Mike Easter wrote:
Michael F. Stemper wrote:
Mike Easter wrote:
Michael F. Stemper wrote:
[discord not recognizing any mics or speakers]
I see.I highly recommend rebooting. There's the possibility of a 'spurious' reboot result.
Well, I just rebooted and it had no effect on the issue.
(To be clear, I had rebooted multiple times throughout the
previous year, not just the one time immediately before
the problem.)
The point I was trying to make is that any given boot or reboot can result in something being 'wrong' but the 'wrongness' isn't 'real' or ongoing, but spurious.
In any case, you've clarified that the condition isn't just due to a spurious re/boot.
Further troubleshooting is necessary.
Better than syslog, I just captured some of the copious stderr
from discord. This looks as if it might be a clue:
[2022-06-28 08:19:13.162] [9647] (audio_device_pulse_linux.cc:1625): failed to connect to PulseAudio sound server
[2022-06-28 08:19:13.162] [9647] (audio_device_pulse_linux.cc:144): failed to initialize PulseAudio
[2022-06-28 08:19:13.162] [9647] (audio_device_impl.cc:374): Audio device initialization failed.
[2022-06-28 08:19:13.162] [9647] (audio_coding.cpp:143): Using software Opus decoder
I know that pulse is running because I can see it in top.
Where do I go from here?
Run the non-Snap version.
How do I do that?
mstemper@parvicursor$ sudo apt-get install discord
Reading package lists... Done
Building dependency tree
Reading state information... Done
No apt package "discord", but there is a snap with that name.
Try "snap install discord"
E: Unable to locate package discord
mstemper@parvicursor$
On 6/29/2022 9:34 AM, Michael F. Stemper wrote:
On 28/06/2022 08.33, Paul wrote:
On 6/28/2022 9:24 AM, Michael F. Stemper wrote:
On 25/06/2022 12.43, Mike Easter wrote:
Michael F. Stemper wrote:
Mike Easter wrote:
Michael F. Stemper wrote:
[discord not recognizing any mics or speakers]
I see.I highly recommend rebooting. There's the possibility of a 'spurious' reboot result.
Well, I just rebooted and it had no effect on the issue.
(To be clear, I had rebooted multiple times throughout the
previous year, not just the one time immediately before
the problem.)
The point I was trying to make is that any given boot or reboot can result in something being 'wrong' but the 'wrongness' isn't 'real' or ongoing, but spurious.
In any case, you've clarified that the condition isn't just due to a spurious re/boot.
Further troubleshooting is necessary.
Better than syslog, I just captured some of the copious stderr
from discord. This looks as if it might be a clue:
[2022-06-28 08:19:13.162] [9647] (audio_device_pulse_linux.cc:1625): failed to connect to PulseAudio sound server
[2022-06-28 08:19:13.162] [9647] (audio_device_pulse_linux.cc:144): failed to initialize PulseAudio
[2022-06-28 08:19:13.162] [9647] (audio_device_impl.cc:374): Audio device initialization failed.
[2022-06-28 08:19:13.162] [9647] (audio_coding.cpp:143): Using software Opus decoder
I know that pulse is running because I can see it in top.
Where do I go from here?
Run the non-Snap version.
How do I do that?
This is the URL of the download. It would help if this was
the same release as the one in the Snap.
https://dl.discordapp.net/apps/linux/0.0.18/discord-0.0.18.tar.gz
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 546 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 01:25:35 |
| Calls: | 10,385 |
| Calls today: | 2 |
| Files: | 14,057 |
| Messages: | 6,416,578 |