EDIT: The problem has been solved. @Sill identified the problem here and @cfabbro found a work-around here. Crisis averted!

I listen to some internet radio stations on my computer, but a couple of them aren't working any more: they appear to play, but there's no sound coming from my computer's speakers.

It is only two stations. I've tested other internet radio stations I listen to, and they still work: I can hear them. I can play and hear YouTube videos. I can stream Spotify on my computer. I can play and hear my music files stored on my computer's hard drive. So I know my speakers work. I know Chrome works as a music player for other sources, including other internet radio stations. It's just these two radio stations.

One of them is this radio station. Also this radio station. I know their digital streams are working, because I can listen to them via an internet radio app on my phone. So I know their digital signals are being sent out. But, while my phone app can play them, my computer browser can't play them.

I've tested both non-working stations in Chrome and Internet Explorer. They both don't work in Chrome, but this station also doesn't work in IE.

I'm using Chrome 80.0.3987.122. And I'm running Windows 7.

This problem only started a couple of days ago.

What's going on? How do I fix this?

So my friend has a computer she put together, and after replacing what feels like every single part on the rig, multiple trips to the repair shop, and calling a priest wrestling the demons out of it, it is randomly cutting power and we think the replacement power supply might be just as busted as the last one. Are there decent odds of that being an issue, or could it be something that we are overlooking?

EDIT: So, I had a car issue pop up and I won't be able to to take a look at at it tonight. Will download the tools you all mentioned to a jump drive and will keep you posted.

Was there, stayed up the whole time. Really thinking it might be a bad power switch that stuck, so it would turn off randomly. Thanks for all your help.

FINAL EDIT: So I narrowed it down to the Graphics Card and/or the Cooling System. Running the Heaven Benchmark on Extreme pretty reliably cleans it's clock, especially turning it off and then turning it on again. This happens on the latest Windows Updates, with latest Nvidia Drivers. (RTX 2080) Pulling the card and running the benchmark anyway causes the same issue, and this time it powered on and then back off in a loop. CPU-Z stress caused it to crash, so I'm assuming it's the cooler. Thanks again.

EDIT: SOLVED

It looks like it was much simple than I thought and someone solved it on Reddit already. I won't delete, just leave the link if someone is interested.

Runtime Environment

• OS: MX Linux 18
• Result of Y: 4.19.0-5-amd64
• dotfiles
• i3 version: 4.13
• ~/.config/i3
• GNU Emacs: 27.0.50
• ~/.emacs.d

Issue

Sometimes I use "whereis" (aliased for "wh", but it doesn't make any difference...) for my own scripts.

I usually copy their paths manually (using tmux) and paste to the command line resulting in something like this:

nvim /home/my_username/my_scripts_folder/my_script

Could I make that into a single command?

Thanks in advance!

edit: Problem solved, davidb informed me about the vulnerability in version 3.0.4, and that it is fixed in the new version 3.0.6. Somehow Spyhunter thinks i still use 3.0.4, which in turn is the actual problem i had with Spyhunter, not VLC.

Spyhunter 5 has been bothering me about potential data leaks from vlc media player. The vulnerability is generally based on publicly available information.
It would be a shame if i have to switch, been using vlc for as long as i remember. It is probably the best media player out there, but i hate sharing my personal data in any way or form.

Spyhunter msg:

• Severity: Medium, VLC media player (Version 3.0.4)
  • The CAF demuxer in modules/demux/cad.c in VideoLan media player 3.0.4 may read memory from an uninitialized pointer when processing magic cookies in Caf files, because a ReadKukiChunk() cast converts a return value to an unsigned int, even if that value is negative. This could result in a denial of service and/or potential infoleak.

Is this even anything to care about? I have updated VLC including removing cashe and still get the alert. Is a rollback another option perhaps?

I'm here staring at my inbox for the third time trying to figure out how the hell the sorting in it works. It isn't alphabetically by subject or user, it isn't the recency of the first message (nor is it the recency of the latest message), and it isn't the number of messages. Testing it now, it also isn't the most recent you've opened, so I have no idea how this works or how to look for anything, not that it's big enough to matter much yet.

Am I missing something obvious? I feel so lost.