Audio not enabled in gorilla

[bobbicat]

I somehow got banned from Kubuntu Forums and have been unable to see how this issue was progressing. I just recently managed to regain access to the Forum.
My workaround eventually was to uninstall Gorilla and reinstall Focal. I come here now to see if any progress has been made with this issue.

[bobbicat]

I've tried a fresh install of gorilla. I now get a number of problems. The original sound issue is not resolved either.
Sound from the live usb seems to function fine as far as I can see but somehow becomes disabled when the O.S. is installed to P.C.
There is also a crash that occurs during and towards the end of installation.
In addition my nVidia graphics card and the O.S. don't seem to be able to get along.
All in all Gorilla installation breaks, becoming unusable.
I'll try and read up on any comments around but it looks like I will be continuing to use Kubuntu Fossa for now.

The above applies to Kubuntu. I haven't had the same problems with Ubuntu Gorilla.

Maybe if I install Ubuntu Gorilla and apply the Kubuntu desktop over it?

As mentioned in the last post getting banned here has been something that keeps occurring.
I am unaware of any reason why it should be happening but I believe Snowhog has been looking into the matter.

Losing access to the forum has meant a loss of continuity in my posts and I have lost direction with my install of Gorilla.
I will probably come back to this but for now I'll wait and see if Forum access has become stable before I do any more.

I must admit to not being happy with this Forum or Kubuntu Gorilla, I do hope that will change.

[MountainLake]

Hi,

I am requesting your help regarding a problem I have after upgrading to Kubuntu 20.10 from the previous version.

My upgrade went flawlessly except for one problem where the sound from an external monitor (LG) that is also a TV (inbuilt speakers), which goes through an HDMI connection was not recognized anymore.

However, the sound from the Lenovo laptop (model number 330S-15ARR) was recognized as well as the sound from the headphones was recognized as well.

Since my skills with computers is not good, I had to turn to the Internet forums and found most of the instructions for help is for Ubuntu, not Kubuntu. I thought it would not matter if I use the same instructions (command lines) and perhaps that is where I made a serious mistake.

Following these command lines, I have now created a big problem that is quite the reverse now, in the sense, the laptop speakers and the headphones are not recognized anymore and there is no sound in the laptop speakers. However, the external monitor connected through HDMI has a good sound output. In addition, it has stopped recognizing the mike both internal as well as inline mikes that are in the cord of headphones.

When I disconnect the external monitor that also has inbuilt speakers, the laptop still does not play any sound on Kubuntu (speaker work on Windows).

In addition, the system monitor has changed to the GNOME system monitor. This happened by mistake after I ran some command lines from an Ubuntu forum instead of a Kubuntu forum.

The loudspeaker icon on the bottom right of the taskbar has disappeared, making increasing and decreasing/muting the volume difficult. The function buttons that increased, decreased and muted the volume from the keyboard have now stopped working on Kubuntu 20.10 (they work on Windows). Please can you help me restore the former sound settings so that it was great like before the upgrade.

This laptop which is connected to the external monitor via HDMI is dual-booted. On the Windows side, the laptop's speakers & headphones and any integrated mikes are all recognized and work well like they used to like in the previous version of Kubuntu.

Please could you help? IÂ’d be very grateful.

Thank you very much! Happy new year!

Sound devices are not properly recognized after install, or after release upgrade to Kubuntu Groovy Gorilla 2010.

There is a work-around for this problem elsewhere on these forums and one other user that I know who has this bug/difficulty.

I will try to find if a bug has been reported.

Please use this thread if you have this problem or have anything to add to the discussion.

I will report any findings I have on this thread.

[bobbicat]

Hi Mountain Lake,

The solution for this problem appears to be in the pipeline. I imagine once it has been worked through it will appear as an update in the repositories.
I enabled the 'proposed repository' through settings and sound does become enabled after an update, so there does appear to be a fix.

Please uderstand that the material in the 'proposed repository' is still being tested and might be subject to further bugs. It is released under proposed so that users can check out and report any problems , it is more in the nature of a beta release. There could well be other parts of the system in there for testing too so it is well to be aware of this and you should anticipate possible fails. However this does mean that when testing is complete a good release will appear amongst updates. This could take anything from a day or two up to a week or even a month.

As things stand I have two installations of Kubuntu on my PC. I am using Focal Fossa Kubuntu 20.04 which is stable for me as my everyday version.
I also have Kubuntu Gorilla installed, which I am using to keep an eye on its stability and for testing. At the moment and at times I have enabled the proposed repository on Gorilla. I have also installed and re-installed it a number of times. Usually by this stage I would be using Gorilla as my main OS but I'll be leaving it a bit longer this time.

I am not an advanced Linux user but I have had Kubuntu as my main OS almost all the time it has been available, so I would say I was 'experienced'.
Incidentally I found that the sound problem did not appear on Ubuntu Gorilla, only on the Kubuntu version. In addition many people are having no problems, so although you are not alone in being unfortunate, that indicates to me that there is a hardware compatibility problem. I'm sure your hardware is sound and the answer will be appearing shortly.
If sound is a major issue then reinstall Focal Fossa for now, otherwise just wait it out.

I hope what I have added here is of some use to you.

...and BTW a very happy new year to you too

[jglen490]

In looking at this thread, again, the recurring theme is that different hardware (PC, laptop, internal sound devices, connection types) have different results.

This is to be expected. Each piece of hardware has a driver. To understand a specific problem requires understanding of the underlying components and the OS version being applied.

This information was asked about by member claydoh in post #9 of this thread. No one is born with a complete understanding of any OS, it requires learning and sharing of information. Not being "geekish" is not an excuse, anybody can learn a few commands. No one on this or any other forum has mind-reading skills.

If you don't know how to do something, ask. You will be given an answer. Keep asking until you understand.

[MountainLake]

Thanks, your response is helpful. Regarding reinstalling Gorilla: I have a lot of tweaks and passwords saved, I might end up in worse situation.

I feel I will report this as a bug so they get my feedback and inputs on this regression. I have Kubuntu Gorilla on 2 other laptops that work flawlessly. I guess this new version could not recognize the external monitor as far as sound is concerned and the rest of my problems were 'self-induced'.
Thanks again.

[jglen490]

You are free to report this situation using the bug reports, one thing to remember is that you will be asked for hardware details as well as the OS version.

There are several ways to get hardware info, one of the best is the

inxi

command line utility. So open a konsole and enter:

inxi - Fxxxz

.

If inxi is not installed, then in konsole enter this to install inxi:

sudo apt install inxi

then answer the prompts and when the install is finished enter the query above.

[MountainLake]

inxi

Thanks for the command lines. Here's the output:

S:~$ inxi
CPU: Quad Core AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx (-MT MCP-) speed/min/max: 2553/1600/2000 MHz
Kernel: 5.8.0-34-generic x86_64 Up: 4h 14m Mem: 3496.5/6892.4 MiB (50.7%) Storage: 238.47 GiB (48.6% used) Procs: 342
Shell: Bash inxi: 3.1.07


Could you please give me the link or website where I could report my problem? Thanks.

You are free to report this situation using the bug reports, one thing to remember is that you will be asked for hardware details as well as the OS version.

There are several ways to get hardware info, one of the best is the

inxi

command line utility. So open a konsole and enter:

inxi - Fxxxz

.

If inxi is not installed, then in konsole enter this to install inxi:

sudo apt install inxi

then answer the prompts and when the install is finished enter the query above.

[MountainLake]

Could you please give me the Command lines to check my audio settings?

The reasons I ask is that I had done Internet searches earlier and visited random websites where I feel the instructions may have been for GNOME (Ubuntu) instead of KDE.
I feel I may be able to change the settings back to how it was and that might solve the problem by restoring the audio to the laptop speakers.

Thanks for the command lines. Here's the output:

S:~$ inxi
CPU: Quad Core AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx (-MT MCP-) speed/min/max: 2553/1600/2000 MHz
Kernel: 5.8.0-34-generic x86_64 Up: 4h 14m Mem: 3496.5/6892.4 MiB (50.7%) Storage: 238.47 GiB (48.6% used) Procs: 342
Shell: Bash inxi: 3.1.07


Could you please give me the link or website where I could report my problem? Thanks.

[jglen490]

First, it appears that I mistyped the inxi command. To get all of the info, enter

inxi -Fxxxz

such that the dash is right next to the F.

The Ubuntu Launchpad site is correct for Kubuntu, also. The differences between Ubuntu and Kubuntu are nearly zero with respect to code base, except for the desktop environment (KDE/Plasma). You need to identify Kubuntu, in case there are KDE or Plasma issues.

[MountainLake]

System: Kernel: 5.8.0-34-generic x86_64 bits: 64 compiler: gcc v: 10.2.0 Desktop: KDE Plasma 5.19.5 tk: Qt 5.14.2
wm: kwin_x11 dm: SDDM Distro: Ubuntu 20.10 (Groovy Gorilla)
Machine: Type: Laptop System: LENOVO product: 81FB v: Lenovo ideapad 330S-15ARR serial: <filter> Chassis: type: 10
v: Lenovo ideapad 330S-15ARR serial: <filter>
Mobo: LENOVO model: LNVNB161216 v: SDK0J40700WIN serial: <filter> UEFI: LENOVO v: 7WCN38WW date: 11/04/2019
Battery: ID-1: BAT1 charge: 27.1 Wh condition: 28.8/30.0 Wh (96%) volts: 8.1/7.4 model: LENOVO BASE-BAT type: Li-poly
serial: <filter> status: Unknown cycles: 20
CPU: Info: Quad Core model: AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx bits: 64 type: MT MCP arch: Zen
L2 cache: 2048 KiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 31943
Speed: 1510 MHz min/max: 1600/2000 MHz boost: enabled Core speeds (MHz): 1: 2123 2: 1581 3: 1406 4: 1481 5: 1390
6: 1394 7: 1597 8: 1574
Graphics: Device-1: AMD Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] vendor: Lenovo driver: amdgpu v: kernel
bus ID: 04:00.0 chip ID: 1002:15dd
Device-2: Chicony Integrated Camera type: USB driver: uvcvideo bus ID: 3-1:2 chip ID: 04f2:b61e serial: <filter>
Display: x11 server: X.Org 1.20.9 compositor: kwin_x11 driver: amdgpu FAILED: ati unloaded: fbdev,modesetting,vesa
resolution: 1920x1080~60Hz s-dpi: 96
OpenGL: renderer: AMD RAVEN (DRM 3.38.0 5.8.0-34-generic LLVM 11.0.0) v: 4.6 Mesa 20.2.1 direct render: Yes
Audio: Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio vendor: Lenovo
driver: snd_hda_intel v: kernel bus ID: 04:00.1 chip ID: 1002:15de
Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A bus ID: 04:00.5
chip ID: 1022:15e2
Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio vendor: Lenovo driver: snd_hda_intel v: kernel
bus ID: 04:00.6 chip ID: 1022:15e3
Sound Server: ALSA v: k5.8.0-34-generic
Network: Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter vendor: Lenovo driver: ath10k_pci v: kernel
bus ID: 01:00.0 chip ID: 168c:0042
IF: wlp1s0 state: up mac: <filter>
Device-2: Qualcomm Atheros type: USB driver: btusb bus ID: 3-2:3 chip ID: 0cf3:e500
Drives: Local Storage: total: 238.47 GiB used: 115.89 GiB (48.6%)
ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM256GDHTNG-8310A size: 238.47 GiB speed: 15.8 Gb/s lanes: 2
serial: <filter> rev: 80070C00 scheme: GPT
Partition: ID-1: / size: 66.30 GiB used: 46.61 GiB (70.3%) fs: ext4 dev: /dev/nvme0n1p6
Swap: ID-1: swap-1 type: file size: 2.00 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
Sensors: System Temperatures: cpu: 43.1 C mobo: N/A gpu: amdgpu temp: 43.0 C
Fan Speeds (RPM): N/A
Info: Processes: 330 Uptime: 7m Memory: 6.73 GiB used: 2.57 GiB (38.1%) Init: systemd v: 246 runlevel: 5 Compilers:
gcc: 10.2.0 alt: 10/9 Packages: 2609 apt: 2586 flatpak: 12 snap: 11 Shell: Bash v: 5.0.17 running in: konsole
inxi: 3.1.07

First, it appears that I mistyped the inxi command. To get all of the info, enter

inxi -Fxxxz

such that the dash is right next to the F.

The Ubuntu Launchpad site is correct for Kubuntu, also. The differences between Ubuntu and Kubuntu are nearly zero with respect to code base, except for the desktop environment (KDE/Plasma). You need to identify Kubuntu, in case there are KDE or Plasma issues.

[MountainLake]

The following command has temporarily brought back sound to my laptop speakers: ~$ Exec=killall pulseaudio; pulseaudio -k ; rm -r ~/.config/pulse/* . I think it may be a temporary fix.

~$ Exec=killall pulseaudio; pulseaudio -k ; rm -r ~/.config/pulse/*
E: [pulseaudio] pid.c: Daemon already running.
E: [pulseaudio] main.c: pa_pid_file_create() failed.

[jglen490]

That probably is temporary, and is important information for a bug report.

[MountainLake]

Thanks
Please can you give me the website for reporting this bug.

[bobbicat]

Thanks
Please can you give me the website for reporting this bug.

Hi, MountainLake

if you enter:

ubuntu-bug -s audio

into the console, on the device with the problem, that will automatically start sound tests, collect info and start a bug report.
All you need to do is follow through the on screen instructions that will appear.
You will need to create a Ubuntu One account, which will require an email address, but that is straightforward and the opportunity to create it will appear as you work through the bug report.
The whole thing will only take a few minutes and more or less takes care of itself, sending a report to the correct place for you.

entering:

ubuntu-bug -help

will provide some other options but they probably won't be needed by you here.

If you want some background on bug reporting you could try reading through this interesting webpage:

https://wiki.kubuntu.org/Kubuntu/Bugs/Reporting