[01:41] <OvenWerks> HaraldArtner[m]: we need a lot more info than what you have given.
[19:15] <LuizGustavoVeiga> Hi! Ubuntu Studio 22.04 LTS has no sound.
[19:16] <arraybolt3[m]> Luiz Gustavo Veiga: Can you open a terminal and run "lspci | nc termbin.com 9999", then send the link it spits out? This will tell me details about your system's hardware.
[19:17] <LuizGustavoVeiga> Are the other users with this problem?
[19:17] <arraybolt3[m]> Luiz Gustavo Veiga: My main desktop with Ubuntu Studio 22.04 has audio functioning perfectly well, so it's almost certainly a hardware-based issue.
[19:18] <arraybolt3[m]> However, it may be resolvable. It depends on what exactly your hardware is.
[19:19] <LuizGustavoVeiga> My notebook: HP Pavillion g4.
[19:21] <arraybolt3[m]> OK, I have an idea, hold on one moment...
[19:23] <arraybolt3[m]> Luiz Gustavo Veiga: OK, can you open a terminal and run this command for me? "dmesg | grep sof | nc termbin.com 9999", then send the link that spits out? This will show me some of your system logs, including info about whether or not your sound card has the proper firmware installed.
[19:24] <LuizGustavoVeiga> run this command on konsole?
[19:24] <arraybolt3[m]> Luiz Gustavo Veiga: Yes.
[19:26] <LuizGustavoVeiga> This was not possible.
[19:27] <LuizGustavoVeiga> Konsole did not work with this command.
[19:27] <arraybolt3[m]> Luiz Gustavo Veiga: Did you accidentally leave the quote marks on the outside? The command you type should look exactly like this:
[19:28] <arraybolt3[m]> `dmesg | grep sof | nc termbin.com 9999`
[19:28] <LuizGustavoVeiga> I'll try again.
[19:28] <arraybolt3[m]> (Hopefully that renders right since you're on Matrix, if not I'll put it in again without formatting.)
[19:31] <LuizGustavoVeiga> This returned: dmesg : read kernel buffer failed
[19:31] <arraybolt3[m]> Luiz Gustavo Veiga: Odd. Then try `sudo dmesg | grep sof | nc termbin.com 9999` instead (this one will ask for a password so it can get access to the logs I'm looking for).
[19:32] <LuizGustavoVeiga> i think there is a configuration problem on alsa or jack.
[19:32] <arraybolt3[m]> Luiz Gustavo Veiga: Maybe. Are any sound devices showing up in your system tray when you click the speaker icon?
[19:33] <LuizGustavoVeiga> https://termbin.com/w2op
[19:33] <LuizGustavoVeiga> This link returned.
[19:34] <arraybolt3[m]> Hmm. Okay, looks like it's not a missing firmware issue. OK, let me keep digging...
[19:34] <LuizGustavoVeiga> Ok.
[19:35] <LuizGustavoVeiga> I tried all what I could but now I need help.
[19:35] <arraybolt3[m]> Trying to find the sound card that ships with your system appears to be harder than I thought. Can you go to that Konsole window again and run "lspci | nc termbin.com 9999" so I can get the exact sound device name?
[19:36] <LuizGustavoVeiga> https://termbin.com/nrp1
[19:37] <arraybolt3[m]> Hmm. OK, looking...
[19:38] <LuizGustavoVeiga> 👍️
[19:41] <arraybolt3[m]> Luiz Gustavo Veiga: Well this is weird, from what I'm seeing, there's no particular incompatibilities with your sound device, it should just work. Have you tweaked anything related to the sound (starting JACK for instance)?
[19:42] <LuizGustavoVeiga> I tried to force reload alsa, pulse audio and jack.
[19:43] <LuizGustavoVeiga> None of these worked.
[19:43] <arraybolt3[m]> Luiz Gustavo Veiga: You might hate me for this, but can you try booting another distro (like Lubuntu 22.04) and tell me if the sound works there?
[19:44] <arraybolt3[m]> (If so, there's something amiss in Ubuntu Studio's audio config on your system. If not, then there's something amiss with Linux and your sound card, in which case we end up getting to have a lot of <sarcasm>fun</sarcasm>.)
[19:44] <LuizGustavoVeiga> The system looks like no identify internal speakers.
[19:44] <arraybolt3[m]> Crud. Hey, wait, I have an idea. Can you run these two commands real quick:
[19:45] <arraybolt3[m]> systemctl --user stop pulseaudio.service
[19:45] <arraybolt3[m]> Er, no...
[19:45] <arraybolt3[m]> systemctl --user stop pulseaudio.socket
[19:45] <arraybolt3[m]> systemctl --user stop pulseaudio
[19:45] <arraybolt3[m]> systemctl --user start pulseaudio
[19:45] <arraybolt3[m]> (So three commands, but whatever.)
[19:45] <arraybolt3[m]>  * `systemctl --user stop pulseaudio.socket`
[19:46] <LuizGustavoVeiga> I had sound in the beggining but this was fading and ... pooof! 
[19:46] <arraybolt3[m]>  * `systemctl --user stop pulseaudio`
[19:46] <arraybolt3[m]>  * `systemctl --user start pulseaudio`
[19:46] <LuizGustavoVeiga> The sound disapeared!
[19:46] <arraybolt3[m]> Luiz Gustavo Veiga: OK, so then it probably is a config issue. Try those three lines and see if that fixes it.
[19:49] <LuizGustavoVeiga> Nothing!
[19:50] <arraybolt3[m]> Crud. You still have an Ubuntu Studio live USB or DVD sitting around, right?
[19:50] <LuizGustavoVeiga> 😬
[19:50] <arraybolt3[m]> Luiz Gustavo Veiga: LOL
[19:50] <LuizGustavoVeiga> No, I don't have it today.
[19:51] <LuizGustavoVeiga> I'll need an installer disk.
[19:51] <arraybolt3[m]> Luiz Gustavo Veiga: Do you have *any* live Linux USB laying around? Or the bandwidth to download Lubuntu 22.04 or something like that?
[19:51] <LuizGustavoVeiga> Yes, I have.
[19:51] <OvenWerks> cd /tmp && wget https://community.ardour.org/files/adevices.sh && bash ./adevices.sh |pastebinit
[19:51] <OvenWerks> That is all one line
[19:51] <LuizGustavoVeiga> Can I use a pendrive?
[19:51] <arraybolt3[m]> Luiz Gustavo Veiga: Whatever OvenWerks says, do that - he's one of the developers.
[19:52] <OvenWerks> I think there is something you can put on the end to get another paste site
[19:52] <arraybolt3[m]> He wants you to run the command he posted in Konsole.
[19:52] <arraybolt3[m]> OvenWerks: I always do "nc termbin.com 9999" for that.
[19:53] <arraybolt3[m]> So `cd /tmp && wget https://community.ardour.org/files/adevices.sh && bash ./adevices.sh | nc termbin.com 9999` should work too.
[19:53] <OvenWerks> feel free to change things out
[19:53] <LuizGustavoVeiga> Please, put light on my way! I am beginner in Linux. How can I learn command lines?
[19:53] <OvenWerks>  :)
[19:53] <arraybolt3[m]> Luiz Gustavo Veiga: cd: Change directory. Basically the terminal equivalent of moving around in the file manager.
[19:53] <LuizGustavoVeiga> Is there a correct way to begin?
[19:53] <LuizGustavoVeiga> A book, for example?
[19:54] <OvenWerks> In general I normally run my mouse across it to highlight it and then middle click in the terminal.
[19:55] <arraybolt3[m]> Luiz Gustavo Veiga: I learned by experimenting around and looking stuff up on Stack Overflow any time I needed help. Quick primer - use "apropos <search term>" to look for commands, use "man <program name>" to get help, and some programs will allow you to pipe the output from other programs into them - use "<command 1> | <command 2>" to do that. That should get you started.
[19:55] <arraybolt3[m]> (Replace the placeholders as appropriate.)
[19:55] <LuizGustavoVeiga> I tried to look at  man db but it is enormous!
[19:56] <LuizGustavoVeiga> I am using Ubuntu Studio.
[19:56] <arraybolt3[m]> Yeah, just "apropos" will allow you to search stuff. Just be very careful with commands that delete files, do NOT run random script snippets from off the Internet unless they're from someone you trust, and keep fiddling until it works.
[19:57] <OvenWerks> it should, you don't want to use man to go through everything, just commands you want to know about right now
[19:57] <arraybolt3[m]> (OvenWerks is a developer, so pretty much anything he tells you to run is going to be safe to run, and if you want to make sure he's a developer, you can check the Ubuntu Studio Development IRC logs.)
[19:57] <LuizGustavoVeiga> I think I need to learn the syntaxe first.
[19:58] <OvenWerks> most commands also accept --help but then there are some that have no man page and --help doesn't work (like jack_control)
[19:58] <LuizGustavoVeiga> It should there be a way to build command lines from simple to advanced.
[19:59] <arraybolt3[m]> Luiz Gustavo Veiga: Basically, put the program name first. Then each piece of data you want to feed to the program, put after that. The man pages or help info from each program will tell you what data it expects and how it wants it formatted.
[19:59] <OvenWerks> if you like you can break that down into separate lines
[19:59] <OvenWerks> cd /tmp
[19:59] <OvenWerks> wget http://jackaudio.org/downloads/adevices.sh
[19:59] <arraybolt3[m]> (cd /tmp: Move to the /tmp directory.)
[19:59] <OvenWerks> bash ./adevices.sh
[19:59] <LuizGustavoVeiga> Ok!
[20:00] <arraybolt3[m]> (wget http://jackaudio...: Download the file adevices.sh from http://jackaudio.org/downloads.)
[20:00] <OvenWerks> then highlight the whole output and paste
[20:00] <LuizGustavoVeiga> I'm going to do it.
[20:00] <arraybolt3[m]> (bash ./adevices.sh: Run the ./adevices.sh script using the Bash shell.)
[20:00] <arraybolt3[m]> (Hopefully I didn't just muddy things up to kingdom come with my command explanations...)
[20:01] <LuizGustavoVeiga> Thank you for your help!
[20:02] <LuizGustavoVeiga> Bye!