How to fix an alsa audio driver failure?

ator-dev

I'm using GDNative fairly extensively in my project, as the pathfinding model I'm using (my own version of all-pairs-shortest-path) needs to be as fast as possible and I decided using C++ would help with that. I only recently realised that I could build and test the code at the same time by simply pressing F5 in VSCode, running SCons and then immediately running the game with the new native code, allowing me to develop it much more easily. While this is mostly fine, two errors/warnings are constantly appearing in the output:

I've spent several hours searching through the forums a similar question has appeared on before, and have found that no-one else's solution works for my problem. Also, as far as I can tell, the others with this problem were getting it while running their project in Godot, whereas my problem only occurs while running it in VSCode.

Does anyone have any idea of how I could fix this, or what the issue might be? Thanks in advance, Dominic

Edit: I'm using Ubuntu by the way.

ator-dev

In case anyone has the same problem and finds this later on: I've now found out what the issue was. I was using the snap version of VSCode, since at the time I installed it I was new to Ubuntu and hadn't yet realised that snaps aren't that great (despite being the option that the system basically forces on you in 20.04). For some reason, the snap VSCode's terminal works almost unnoticeably differently from the normal terminal, but doesn't work correctly with Godot and pulse audio - to fix this, I simply uninstalled it and replaced it with the VSC debian, which now has exactly the behaviour I'd expect.

Still not sure why Ubuntu is promoting snaps so much when they're not fully reliable yet (there are other examples of them not working properly), but I'd recommend sticking to the older debians for now (;

Calyad

@Dominic said: In case anyone has the same problem and finds this later on: I've now found out what the issue was. I was using the snap version of VSCode, since at the time I installed it I was new to Ubuntu and hadn't yet realised that snaps aren't that great (despite being the option that the system basically forces on you in 20.04). For some reason, the snap VSCode's terminal works almost unnoticeably differently from the normal terminal, but doesn't work correctly with Godot and pulse audio - to fix this, I simply uninstalled it and replaced it with the VSC debian, which now has exactly the behaviour I'd expect.

@Dominic, I am having this issue! But I do not understand what you did to fix it.

(I was developing my game on a Windows 7 computer. It broke, and I got a new computer, but am running Ubuntu instead of Windows. So I am so new to Ubuntu that I am not sure what is happening, and I am getting several errors that I was not getting before.)

I hate to ask this, but your post is the only one I can find after hours of looking, myself. Can you please explain what you did with a bit more detail? I assume I just need to go to "Ubuntu Software" and install one thing, and uninstall another, but I am afraid of breaking anything.

Calyad

Well, I feel like a moron.

I was using the 3.1.2 version of Godot from the Ubuntu Software area.
I just uninstalled it and got the latest (3.2.something) directly from Godot, and everything is perfect. Derp.

ator-dev

@Calyad Sorry I didn't reply earlier, I only just noticed your comment. Glad to hear you fixed it! In case you're interested, however, here's some information on my experience with Ubuntu relating to this (anyone else seeing this, please correct me if I'm wrong): - As of 20.04 LTS (possibly for some time before as well), Ubuntu's software centre is a Snap application which can be used as a user-friendly interface to install other snaps only. I uninstalled this for a number of reasons - firstly, I much prefer the terminal for doing things like installing and removing software, and secondly, I don't like snaps much in any case. I now use APT for basically everything, which is used for Debian applications. - (Just a note - although Debians are currently a better option at the moment in my opinion, and I think the terminal is much better supported and easier to use than software centres, this is entirely subjective. One of the reasons I like Ubuntu is you can kind of approach it any way you want.) - My problem (with the alsa error) only occurred in VSCode's terminal when debugging Godot along with GDNative C++, and then only because I was using the Snap install of VSC. Since getting a newer version of the engine fixed your problem I'm assuming it happened in slightly different circumstances, so you probably don't need to take the steps I did. - If you ever do use GDNative (assuming you aren't already), I highly recommend using VSCode's debugger to run Godot when testing your native code as it makes things so much easier. In that case, you'll probably start getting my issue, in which case you should simply follow these steps if you don't have the APT version: 1. Uninstall VSC, if you already have the snap version. 2. Add the Microsoft VSCode repository via the terminal (you can look up instructions for this, but make sure you're adding a trustworthy repository - in this case, it will come from "microsoft.com" of course. 3. Install the VSC Debian with something like "sudo apt install code" in the terminal again.

Hope this helps!