ວິທີແກ້ໄຂບັນຫາລະບົບສຽງ

Hank Lee, ກຸ່ມ The Music and Audio SIG Version F40 Last review: 2025-06-06
ໜ້ານີ້ລວມເອົາເຕັກນິກການແກ້ໄຂບັນຫາພື້ນຖານບາງຢ່າງເພື່ອຊ່ວຍຈຳກັດສາເຫດຕົ້ນຕໍຂອງບັນຫາ. ພ້ອມທັງອະທິບາຍເຖິງຂໍ້ມູນທີ່ຄວນປະກອບເຂົ້າໃນເວລາລາຍງານຂໍ້ຜິດພາດ (bug) ທີ່ກ່ຽວກັບສຽງ.

ບົດນຳ

ບັນຫາສຽງໃນ Fedora Linux ສາມາດເກີດຈາກຫຼາຍປັດໄຈ, ລວມທັງໂປຣໄຟລ໌ສຽງ, ຂັ້ນຕອນການຈັບຄູ່, ຄວາມເຂົ້າກັນໄດ້ຂອງອຸປະກອນ ຫຼື ການຕັ້ງຄ່າທີ່ຜິດພາດຂອງຜູ້ໃຊ້. ບັນຫາທົ່ວໄປທີ່ຜູ້ໃຊ້ອາດຈະພົບເຫັນມີ:

  • ບໍ່ມີສຽງອອກ ຫຼື ສຽງເຂົ້າ

  • ມີພຽງແຕ່ “Dummy Output” ເທົ່ານັ້ນທີ່ສະແດງໃຫ້ໃຊ້

  • ບໍ່ກວດພົບໄມໂຄຣໂຟນ

  • ອຸປະກອນສຽງຫາຍໄປຫຼັງຈາກການອັບເດດ

  • ການເຊື່ອມຕໍ່ສຽງ Bluetooth ຂັດຂ້ອງ

ຄູ່ມືນີ້ໃຫ້ວິທີການເທື່ອລະຂັ້ນຕອນໃນການວິນິດໄສ ແລະ ແກ້ໄຂບັນຫາສຽງເຫຼົ່ານີ້. ມັນລວມມີທັງການແກ້ໄຂບັນຫາທົ່ວໄປ ແລະ ການແກ້ໄຂສະເພາະສຳລັບບັນຫາທີ່ກ່ຽວກັບສຽງເຂົ້າ, ເຊັ່ນ: ໄມໂຄຣໂຟນຫາຍໄປ ຫຼື ອຸປະກອນຮັບສຽງບໍ່ເຮັດວຽກ.

ການວິນິດໄສບັນຫາ

  • ການກວດສອບວ່າບັນຫາເກີດຈາກ kernel, PipeWire ຫຼື ແອັບພລິເຄຊັນສະເພາະໃດໜຶ່ງ.

  • ການເກັບກຳບັນທຶກ (logs) ແລະ ຂໍ້ມູນລະບົບ.

ກວດເບິ່ງວ່າ Kernel driver ໃດທີ່ຖືກນຳໃຊ້ໂດຍອຸປະກອນ PCI

ເພື່ອສະແດງ kernel drivers ທີ່ຈັດການແຕ່ລະອຸປະກອນ, ໃຫ້ໃຊ້ຄຳສັ່ງ lspci (List PCI) ພ້ອມກັບຕົວເລືອກ -k. ໃຫ້ຄົ້ນຫາບັນຫາທີ່ເຄີຍພົບເຫັນສະເພາະກັບຊື່ຂອງໄດຣເວີ ແລະ ລຸ້ນຮາດແວຂອງທ່ານ ກ່ອນທີ່ຈະລາຍງານບັນຫາໄປຍັງ Ask Fedora.

$ sudo lspci -k

ໄດຣເວີຮາດແວໃໝ່ໆຈະຖືກອັບເດດຢ່າງຕໍ່ເນື່ອງ. ຖ້າທ່ານເຫັນອຸປະກອນສະແດງເປັນບໍ່ຮູ້ຈັກ (unknown), ໃຫ້ຄົ້ນຫາໃນຖານຂໍ້ມູນ PCI device ID ຂອງທ່ານ.

$ sudo lspci -Q

ແລະ ອັບເດດຖານຂໍ້ມູນ PCI ID ໃນເຄື່ອງຂອງທ່ານ ໂດຍການແລ່ນຄຳສັ່ງ update-pciids.

$ sudo update-pciids

ເຟີມແວ ALSA

ແພັກເກດເຟີມແວ ALSA ລວມມີເຟີມແວສຳລັບຊາວຄາດ (sound cards) ຕ່າງໆຈາກພາກສ່ວນທີສາມ.

ກວດເບິ່ງວ່າເຟີມແວໃດກຳລັງຖືກນຳໃຊ້ ໂດຍການແລ່ນຄຳສັ່ງລຸ່ມນີ້.

$ sudo dnf list alsa-firmware

ເຟີມແວ ALSA ປົກກະຕິຈະສະແດງເປັນ <alsa-firmware.noarch>.

ຖ້າເຟີມແວປົກກະຕິບໍ່ສະແດງໃນຜົນໄດ້ຮັບ, ໃຫ້ຕິດຕັ້ງ alsa-firmware.

$ sudo dnf install alsa-firmware

ຖ້າມີເຟີມແວອື່ນຖືກຕິດຕັ້ງໄວ້, ໃຫ້ເພີ່ມພວກມັນເຂົ້າໃນ blocklist ໃນໄດເຣັກທໍຣີການຕັ້ງຄ່າສຳລັບ modprobe.

/etc/modprobe.d/*.conf

ເພີ່ມແຖວນີ້ລົງໃນໄຟລ໌ການຕັ້ງຄ່າ.

blacklist <ຊື່ໂມດູນທີ່ຕ້ອງການບລັອກ>

ເຄື່ອງມື dracut ຈະສ້າງອິມເມດເບື້ອງຕົ້ນທີ່ kernel ໃຊ້ສຳລັບການໂຫຼດໂມດູນອຸປະກອນ block ລ່ວງໜ້າ. ຕົວເລືອກ -f ຈະຂຽນທັບໄຟລ໌ initramfs ທີ່ມີຢູ່ແລ້ວ.

$ sudo dracut -f

ຣີສະຕາດ (Reboot) ຄອມພິວເຕີຂອງທ່ານເພື່ອໃຫ້ການປ່ຽນແປງມີຜົນ.

$ sudo reboot

ຂໍ້ມູນຮາດແວ

ມັນເປັນປະໂຫຍດສະເໝີທີ່ຈະປະກອບຂໍ້ມູນລາຍລະອຽດກ່ຽວກັບຮາດແວສຽງຂອງທ່ານ ເມື່ອລາຍງານຂໍ້ຜິດພາດທີ່ກ່ຽວກັບສຽງ. ເພື່ອສ້າງຂໍ້ມູນນີ້, ໃຫ້ແລ່ນຄຳສັ່ງນີ້:

$ alsa-info.sh --no-upload

ມັນຈະສ້າງໄຟລ໌ທີ່ບັນຈຸຂໍ້ມູນລະອຽດກ່ຽວກັບຮາດແວສຽງຂອງທ່ານດ້ວຍຊື່ /tmp/alsa-info.txt. ໃຫ້ແນບໄຟລ໌ນີ້ໃສ່ໃນການລາຍງານຂໍ້ຜິດພາດ (bug report) ຂອງທ່ານ.

ມັນແມ່ນ PipeWire ບໍ່?

PipeWire ແມ່ນເຊີບເວີແບ່ງປັນມີເດຍ, ເຊິ່ງເປັນໂຄງສ້າງມັນຕິມີເດຍລະດັບຕໍ່າທີ່ມີຈຸດປະສົງເພື່ອ;

  • ປັບປຸງການຈັດການສຽງ ແລະ ວິດີໂອໃນ Linux

  • ຮອງຮັບການເຮັດວຽກສຳລັບຜູ້ໃຊ້ທຸກຄົນໃນທຸກລະດັບ

  • ໃຫ້ການຮອງຮັບສຳລັບແອັບພລິເຄຊັນທີ່ອີງໃສ່ PulseAudio, JACK (JACK Audio Connection Kit), ALSA ແລະ GStreamer

ການກວດສອບພອດຕ່າງໆດ້ວຍຮູບພາບ

Qpwgraph ແມ່ນໂປຣແກຣມຈັດການກຣາຟທີ່ສ້າງມາສຳລັບ PipeWire ໂດຍສະເພາະ.

ການກວດສອບພອດດ້ວຍຮູບພາບໂດຍໃຊ້ Qpwgraph ຈະຊ່ວຍໃຫ້ເຫັນເສັ້ນທາງການເຊື່ອມຕໍ່ທັງໝົດລະຫວ່າງແອັບພລິເຄຊັນ ແລະ ອຸປະກອນ ແລະ ສາມາດປ່ຽນເສັ້ນທາງໄດ້ຕາມທີ່ຕ້ອງການ. ຕົວຢ່າງ: ຖ້າມີຫຼາຍແອັບພລິເຄຊັນ ແລະ ອຸປະກອນເຊື່ອມຕໍ່ ແລະ ຕັດການເຊື່ອມຕໍ່ດັ່ງລຸ່ມນີ້,

  • Firefox: ແອັບພລິເຄຊັນປະຊຸມວິດີໂອທີ່ໃຊ້ໂປຣໂຕຄອນ WebRTC

  • VLC: ໂປຣແກຣມຫຼິ້ນມີເດຍ

  • OBS Studio: ສຳລັບຖ່າຍທອດສົດ (live stream) ແລະ ບັນທຶກວິດີໂອ

  • USB soundcards ຫຼື ມິກເຊີ (mixers): ອຸປະກອນຕ່າງໆ

ມັນຈະເປັນປະໂຫຍດຫຼາຍໃນການຮຽນຮູ້ວິທີທີ່ພອດເຊື່ອມຕໍ່ກັບແອັບພລິເຄຊັນ ແລະ ອຸປະກອນໃນຮູບແບບກຣາຟິກ.

ພອດມີການກຳນົດທິດທາງ, ເຊິ່ງສາມາດເປັນໄດ້ທັງ:

  • ພອດຕົ້ນທາງ ຫຼື Source ports (output). ຈະຢູ່ທາງຂວາສຸດຂອງ node, ພວກມັນເຮັດໜ້າທີ່ສ້າງກະແສສຽງ/ວິດີໂອ/midi.

  • ພອດປາຍທາງ ຫຼື Sink ports (input). ຈະຢູ່ທາງຊ້າຍສຸດຂອງ node, ພວກມັນເຮັດໜ້າທີ່ຮັບກະແສສຽງ/ວິດີໂອ/midi.

ພອດຍັງແບ່ງອອກເປັນຫຼາຍປະເພດ:

  • ສຽງ (ສີມາດຕະຖານ: ສີຂຽວ)

  • ວິດີໂອ (ສີມາດຕະຖານ: ສີຟ້າ)

  • PipeWire/JACK MIDI (ສີມາດຕະຖານ: ສີແດງ)

  • ALSA MIDI (ສີມາດຕະຖານ: ສີມ່ວງ)

ພອດທີ່ເປັນປະເພດດຽວກັນ ແຕ່ມີທິດທາງກົງກັນຂ້າມກັນ ສາມາດເຊື່ອມຕໍ່ກັນໄດ້.

ກວດເບິ່ງເອກະສານຕົ້ນສະບັບສຳລັບຄູ່ມືຜູ້ໃຊ້ທີ່ Qpwgraph User Guide.

ການແກ້ໄຂບັນຫາສຽງເຂົ້າ (Audio Input)

ປະຕິບັດຕາມຂັ້ນຕອນເຫຼົ່ານີ້ເພື່ອແກ້ໄຂບັນຫາສຽງເຂົ້າສ່ວນໃຫຍ່.

ຂັ້ນຕອນການແກ້ໄຂ:

ຂັ້ນຕອນທີ 1: ຕິດຕັ້ງ PipeWire ແລະ ແພັກເກດທີ່ກ່ຽວຂ້ອງຄືນໃໝ່

ກວດສອບໃຫ້ແນ່ໃຈວ່າອົງປະກອບທີ່ຈຳເປັນຂອງ PipeWire ຖືກຕິດຕັ້ງ ແລະ ເຮັດວຽກຢ່າງຖືກຕ້ອງ.

$ sudo dnf reinstall pipewire pipewire-pulseaudio pipewire-alsa wireplumber

ຫຼັງຈາກນັ້ນໃຫ້ຣີສະຕາດ (reboot) ລະບົບຂອງທ່ານ.

ຂັ້ນຕອນທີ 2: ກວດສອບສະຖານະບໍລິການສຽງ

Check whether the PipeWire and WirePlumber user services are running:

$ systemctl --user status pipewire
$ systemctl --user status pipewire-pulse
$ systemctl --user status wireplumber

To ensure all services are active and enabled on login for the current user, run:

$ systemctl --user enable --now pipewire.socket pipewire-pulse.socket wireplumber.service

To enable these user services system-wide (for all users) and avoid creating per-user overrides under ~/.config/systemd/user/, run:

$ sudo systemctl --user enable --now pipewire.socket pipewire-pulse.socket wireplumber.service

ຂັ້ນຕອນທີ 3: ກວດສອບສິດທິຂອງຜູ້ໃຊ້

ກວດເບິ່ງວ່າບັນຊີຜູ້ໃຊ້ຂອງທ່ານຢູ່ໃນກຸ່ມທີ່ຖືກຕ້ອງແລ້ວບໍ່:

$ groups

ຖ້າບໍ່ມີກຸ່ມ audio, ໃຫ້ເພີ່ມເຂົ້າໄປ:

$ sudo usermod -aG audio $USER

ຂັ້ນຕອນທີ 4: ຣີເຊັດໄຟລ໌ການຕັ້ງຄ່າ

ຖ້າການຕັ້ງຄ່າສຽງມີບັນຫາ, ທ່ານສາມາດຣີເຊັດມັນໄດ້ໂດຍການຍ້າຍໂຟນເດີການຕັ້ງຄ່າເກົ່າ:

$ mv ~/.config/pulse ~/.config/pulse_backup
$ mv ~/.config/pipewire ~/.config/pipewire_backup

ຫຼັງຈາກນັ້ນໃຫ້ຣີສະຕາດ (reboot) ລະບົບຂອງທ່ານ.

ຂັ້ນຕອນທີ 5: ກວດສອບຮາດແວ

ຖ້າທ່ານກຳລັງໃຊ້ໄມໂຄຣໂຟນພາຍນອກ, ໃຫ້ລອງຖອດແລ້ວສຽບໃໝ່ ຫຼື ທົດສອບກັບອຸປະກອນອື່ນ ເພື່ອຕັດບັນຫາທີ່ອາດເກີດຈາກຮາດແວອອກ.

ການວິນິດໄສ ແລະ ແກ້ໄຂບັນຫາສຽງ Bluetooth

ບັນຫາສຽງ Bluetooth ມັກຈະຖືກຈັດຢູ່ໃນໜຶ່ງໃນສາມໝວດໝູ່ຄື: ການກວດພົບອຸປະກອນ, ການຈັບຄູ່ ຫຼື ໂປຣໄຟລ໌ສຽງຫາຍໄປ. ສ່ວນນີ້ຈະໃຫ້ຄຳແນະນຳແບບເປັນຂັ້ນຕອນເພື່ອກວດສອບວ່າບັນຫາຂອງທ່ານຢູ່ໃນຂັ້ນຕອນໃດ ແລະ ວິທີການແກ້ໄຂມັນ.

ໝວດໝູ່ທີ 1: ບໍ່ກວດພົບອຸປະກອນ

ອາການ

  • Bluetooth audio device does not appear in bluetoothctl or GNOME Settings.

  • No MAC address shown even while device is in pairing mode.

This usually means the Linux Bluetooth stack never received an advertisement packet from the device. Common causes include:

  • The Bluetooth adapter (HCI device) is not fully initialized or supported.

  • The device uses a newer Bluetooth version or chipset that requires kernel or firmware support not yet available.

ການກວດສອບ

Use btmon to monitor Bluetooth traffic and look for LE Advertising Report event. When a Bluetooth device is detected properly, you will see lines like:

$ sudo btmon
  Bluetooth monitor ver 5.81
  LE Advertising Report (0x02)
    Num reports: 1
    Event type: Connectable undirected - ADV_IND (0x00)
    Address type: Random (0x01)
    Address: C4:9D:61:BC:E7:09 (Static)
    Data length: 25
    16-bit Service UUIDs (partial): 1 entry
    Unknown (0xfd2a)
    Company: Sony Corporation (301)
    Data[17]: 13000130ed000000004001fffd1c91351c
    RSSI: -40 dBm (0xd8)

  • LE Advertising Report indicates the device is actively broadcasting (advertising).

  • Address is the MAC address of the detected device.

  • RSSI: Signal strength; a negative value of -40 dBm, means the device is nearby.

As a next step, run the bluetoothctl show command to display the current status and configuration of the Bluetooth adapter. It provides information such as adapter name, power status (on/off), discoverability (whether other devices can see it), and pairability.

$ bluetoothctl show
  Controller A0:C5:89:3B:26:52 (public)
  Manufacturer: 0x0002 (2)
  Version: 0x08 (8)
  Name: hanku
  Alias: hanku
  Class: 0x007c010c (8126732)
  Powered: yes
  PowerState: on
  Discoverable: yes
  DiscoverableTimeout: 0x000000b4 (180)
  Pairable: yes

This is useful for checking if your Bluetooth adapter is properly initialized and ready for scanning, pairing, or connecting to devices.

If there is a problem, the output of bluetoothctl show or btmon may reveal signs like the adapter being powered off, not discoverable, or missing from the index entirely. For example, in btmon, if no LE Advertising Report appears, it may indicate the Bluetooth device is not broadcasting or not being detected.

To continue, start the Bluetooth control tool to list Bluetooth devices and their statuses.

$ bluetoothctl
  Agent registered
  [CHG] Device 40:19:20:19:69:9F RSSI: 0xffffffb9 (-71)
  [CHG] Device 28:6B:B4:40:2F:87 RSSI: 0xffffffbd (-67)
  [CHG] Device 28:6B:B4:4C:82:E5 RSSI: 0xffffffb9 (-71)
  [WF-C710N]> scan on
  SetDiscoveryFilter success
  Discovery started
  [DEL] Device C4:9D:61:BC:E7:09 LE_WF-C710N
  [NEW] Device C4:9D:61:BC:E7:09 LE_WF-C710N
  [WF-C710N]>

Here’s a summary of what’s happening in your bluetoothctl session:

  • Agent registered: A Bluetooth agent (for pairing/authentication) has been successfully registered.

  • [CHG] Device …​ RSSI: 0xffffffb9 (-71): RSSI (signal strength) for a known device has changed. The value 0xffffffb9 is just a signed hex representation of -71 dBm — a moderate signal.

  • [WF-C710N]> scan on → You’ve started device discovery (scanning). WF-C710N is the device name, typically set by the manufacturer.

  • SetDiscoveryFilter success → Any filters for discovery (For example, only LE devices) were successfully applied. LE means Low Energy, which is common for Bluetooth audio devices.

  • Discovery started → The adapter began scanning for nearby devices.

  • [DEL] Device C4:9D:61:BC:E7:09 LE_WF-C710N → The device was removed from the internal cache/list temporarily — possibly due to reappearance or profile update.

  • [NEW] Device C4:9D:61:BC:E7:09 LE_WF-C710N → The device reappeared during scanning and is now listed as newly discovered.

If the device never appears in scans (no MAC shown), this is often not solvable by user-level configuration or re-pairing, and may indicate hardware or firmware-level incompatibility.

ຄຳແນະນຳ

  • Test the device on other operating systems (Ubuntu LTS, Windows, macOS) to confirm functionality.

  • Search bug trackers (For example, kernel.org, Fedora Bugzilla, bluez mailing list) for known issues related to the specific device or chipset.

  • If no workaround exists, consider using another headset known to work well with Linux.

ຄຳເຫັນ

  • In community forums, it’s helpful to distinguish device detection issues from pairing or profile switching problems. Many Bluetooth devices work well under Linux. However, some may exhibit issues—such as failing to pair or not switching audio profiles—because of unsupported codecs. Understanding the differences between these issue types helps users know what to expect and makes it easier for contributors to improve guidance and support.

ໝວດໝູ່ທີ 2: ການຈັບຄູ່ລົ້ມເຫຼວ ຫຼື ບໍ່ສົມບູນ

ອາການ

  • Device is visible but cannot be paired or consistently fails to connect

  • Authorization timeouts or connection errors

ການກວດສອບ

  • Use bluetoothctl for manual steps.

$ bluetoothctl

Example bluetoothctl prompt commands:

  power on
  agent on
  default-agent
  scan on
  pair <MAC>
  trust <MAC>
  connect <MAC>

ວິທີແກ້ໄຂ

  • Remove device and retry pairing.

$ bluetoothctl remove <MAC>

  • Restart Bluetooth service.

$ sudo systemctl restart bluetooth

For some devices, make sure to hold the pairing button until rapid blinking starts.

ໝວດໝູ່ທີ 3: ໂປຣໄຟລ໌ສຽງຫາຍໄປ ຫຼື ລົ້ມເຫຼວ

ອາການ

  • The device is paired but no usable audio profile (for example, A2DP, HSP) is shown or active.

  • Only HSP/HFP is available, A2DP (Advanced Audio Distribution Profile) is missing.

ການກວດສອບ

  • Confirm PipeWire is used.

$ pactl info | grep Server

Example Output:

Server String: /run/user/1000/pulse/native
Server Protocol Version: 35
Server Name: PulseAudio (on PipeWire 1.4.2)
Server Version: 15.0.0

This output shows that the system is using the PulseAudio compatibility layer on top of PipeWire. To further inspect the audio setup, the command pactl list cards short provides a concise summary of all audio cards recognized by PulseAudio. It’s useful for quickly identifying available audio devices without diving into detailed properties.

$ pactl list cards short

Example Output:

42 alsa_card.pci-0000_00_1f.3 alsa
1092 bluez_card.14_06_A7_04_73_78 module-bluez5-device.c

The absence of Bluetooth-related cards (in the format bluez_card.XX_XX_XX_XX_XX_XX) in the output of the pactl list cards short command indicates that one or more issues may be present.

Next, the command below filters the output of pactl list cards to only show lines containing either profile or name, ignoring case;

$ pactl list cards | grep -i 'profile\|name:'

Example Output:

Name: alsa_card.pci-0000_00_1f.3
api.acp.auto-profile = "false"
Name: bluez_card.14_06_A7_04_73_78
bluez5.profile = "off"
Active Profile: a2dp-sink
  Part of profile(s): headset-head-unit-cvsd, headset-head-unit
  Part of profile(s): a2dp-sink-sbc, a2dp-sink-sbc_xq, a2dp-sink
  Part of profile(s): headset-head-unit-cvsd, headset-head-unit

Line-by-Line Explanation:

  • Name: alsa_card.pci-0000_00_1f.3 → This is a built-in or PCI-based audio card managed by ALSA.

  • api.acp.auto-profile = "false" → ACP (Advanced Configuration Profile) is disabled for this card; it won’t automatically switch profiles.

  • Name: bluez_card.14_06_A7_04_73_78 → This is a Bluetooth audio device, identified by its MAC address.

  • bluez5.profile = "off" → In PipeWire (especially with WirePlumber), this value can be outdated or not reflect the actual active state, since profiles can be switched dynamically and not always update the stored property.

  • Active Profile: a2dp-sink → This indicates that the A2DP (Advanced Audio Distribution Profile) is currently active, allowing high-quality audio streaming. It also supports HSP/HFP (headset mode) and multiple SBC-based A2DP variations. This structure helps PipeWire choose or switch profiles depending on use case (for example, music vs. calls)

If there is no Bluetooth audio card (for example, bluez_card) present and no Bluetooth-related active profile (such as a2dp-sink or headset-head-unit), this indicates a problem in the audio system, whether PulseAudio or PipeWire.

ຄຳແນະນຳ

  • Test on a clean and latest Fedora system, preferably without having installed multiple conflicting Bluetooth/audio tools.

  • Make sure the Bluetooth audio device is in proper pairing mode—usually indicated by rapid blinking—by following the manufacturer’s instructions.

  • Avoid tweaking or reinstalling PipeWire/WirePlumber based on general forum advice, unless logs show actual service failure.

ຕົວເລືອກການແກ້ໄຂຂໍ້ຜິດພາດ (Debugging) ຂອງ PipeWire

ການແກ້ໄຂຂໍ້ຜິດພາດ (Debugging) ມັກຈະເລີ່ມຕົ້ນຫຼັງຈາກທີ່ກວດພົບ bug ແລ້ວ, ແລະ ຈະໄດ້ຜົນດີທີ່ສຸດເມື່ອຜູ້ໃຊ້ຄຸ້ນເຄີຍກັບສະພາບການທີ່ເຮັດໃຫ້ເກີດ bug ນັ້ນ.

PipeWire ມີຕົວເລືອກການແກ້ໄຂຂໍ້ຜິດພາດຂອງຕົນເອງ. ກະລຸນາເບິ່ງເອກະສານຕົ້ນສະບັບທີ່ PipeWire debugging.

ຕ້ອງການຄວາມຊ່ວຍເຫຼືອເພີ່ມເຕີມບໍ່?

ຖ້າຂັ້ນຕອນຂ້າງເທິງບໍ່ສາມາດແກ້ໄຂບັນຫາຂອງທ່ານໄດ້, ໃຫ້ເຂົ້າໄປທີ່ຊຸມຊົນຂອງ Fedora:

Contributions and feedback help improve Fedora documentation for everyone.

Want to help? Learn how to contribute to Fedora Docs ›