"Windows 11 Pro" and "Ubuntu 22.04.1 LTS" are installed and up to date on the laptop. There is no hardware problem with the laptop. No sound from operating system "Ubuntu 22.04.1 LTS". But the sound comes from the operating system "Windows 11 Pro" without any problems.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60
Uname: Linux 5.15.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: muhammed 1749 F.... pulseaudio
/dev/snd/controlC1: muhammed 1749 F.... pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 24 22:46:37 2022
InstallationDate: Installed on 2022-10-19 (5 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/28/2021
dmi.bios.release: 87.176
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: TN1V7.10_Monster
dmi.board.asset.tag: Board Asset Tag
dmi.board.name: Huma H5 V3.2
dmi.board.vendor: Monster
dmi.board.version: V20
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Monster
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 6.6
dmi.modalias: dmi:bvnINSYDECorp.:bvrTN1V7.10_Monster:bd12/28/2021:br87.176:efr6.6:svnMONSTER:pnHumaH5V3.2:pvrV10:rvnMonster:rnHumaH5V3.2:rvrV20:cvnMonster:ct10:cvrChassisVersion:skuH5V32TN1156MSCD:
dmi.product.family: HUMA
dmi.product.name: Huma H5 V3.2
dmi.product.sku: H5V32TN1156MSCD
dmi.product.version: V10
dmi.sys.vendor: MONSTER
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2022-10-24T22:36:17.567999
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.