Linux Operating System UBUNTU 25 _ MSI GP70 2PE Leopard _ Troubleshooting at the OS/Application-level why when connected a headset to the MSI GP70 2PE Leopard Laptop , there is no sound coming out from the headset
1. Hi Copilot, there is no sound coming out to my Headset when I connected my Headset to my MSI Laptop GP 70 2PE which is running Linux UBUNTU 25 Operating System . I have a Headset with a male phono jack connected to the female phono jack of my MSI Laptop GP 70 2PE which have a "headset" symbol to it . When I play YouTube , there is no sound or audio coming out to my Headset but there is audio coming out from the speaker of my MSI GP 70 2PE Laptop. Copilot , when I checked the settings on my UBUNTU 25 OS , the "Output Device" is set to "Speakers-built-in Audo" , so , Copilot what could go wrong. THANKS for the answer.
MICROSOFT Copilot Answer
Got it — thanks for laying out the details so clearly. The issue is that Ubuntu is still routing audio to your laptop’s internal speakers instead of switching to the headset jack. Let’s break down what could be going wrong and how to fix it:
🎧 Common Causes
- Output device not switching automatically
Ubuntu sometimes doesn’t detect the headset jack as a separate output device, so it stays on “Speakers – Built-in Audio.” - Jack detection issue
The laptop’s audio chipset (often Realtek on MSI machines) may not properly signal to Ubuntu that headphones are plugged in. - PulseAudio/PipeWire configuration
Ubuntu 25 likely uses PipeWire (or PulseAudio underneath). If the audio server doesn’t register the headset, it won’t appear in the list. - Driver quirks
Older MSI laptops sometimes need extra configuration in ALSA (the low-level sound system) to properly handle headset jacks.
🛠️ Steps to Try
Check Sound Settings
- Go to Settings → Sound → Output.
- See if “Headphones” or “Headset” appears as an option when the jack is plugged in.
- If it doesn’t, unplug/replug the headset and watch if the list changes.
Force Output Device
Check ALSA Mixer
- Run:
alsamixer
- Use arrow keys to navigate and make sure “Headphone” isn’t muted (look for “MM” at the bottom — press
M to unmute).
PipeWire Restart
Kernel/Driver Quirk
✅ Quick Check
Since your laptop plays sound through speakers, the audio system itself works. The missing piece is jack detection. If Ubuntu doesn’t show “Headphones” in the Output Device list when plugged in, that’s the root cause.
Would you like me to walk you through step 2 (forcing the output device manually) in detail? That’s often the fastest way to confirm whether Ubuntu even sees your headset.
2. Yes Copilot , could you please teach me the step 2 (forcing the output device manually) in detail and THANKS Copilot for the answer.
MICROSOFT Copilot Answer
Perfect — let’s go step‑by‑step so you can try forcing the headset output manually in Ubuntu 25. This uses the PulseAudio/PipeWire command line tools (pactl) to override the default sink (output device).
🖥️ Step 2: Forcing the Output Device Manually
1. Open a Terminal
- Press Ctrl + Alt + T to open a terminal window.
2. List All Audio Outputs (Sinks)
Run:
pactl list short sinks
This will show something like:
0 alsa_output.pci-0000_00_1b.0.analog-stereo module-alsa-card.c s16le 2ch 44100Hz RUNNING
1 alsa_output.pci-0000_00_1b.0.analog-headphones module-alsa-card.c s16le 2ch 44100Hz IDLE
- Each line is an audio output device (called a sink).
- Look for one that mentions headphones or analog-headphones.
- The one with speakers or analog-stereo is your internal speakers.
3. Set the Headphones as Default
If you see a sink name like alsa_output.pci-0000_00_1b.0.analog-headphones, copy it and run:
pactl set-default-sink alsa_output.pci-0000_00_1b.0.analog-headphones
4. Move Current Audio Streams
If audio is already playing (like YouTube in your browser), you may need to move the stream to the new sink:
pactl list short sink-inputs
This shows active audio streams. For each stream ID (first column), run:
pactl move-sink-input <ID> alsa_output.pci-0000_00_1b.0.analog-headphones
Example:
pactl move-sink-input 42 alsa_output.pci-0000_00_1b.0.analog-headphones
5. Test
- Play a YouTube video again.
- The sound should now route to your headset instead of the speakers.
🔍 If No Headphones Sink Appears
- That means Ubuntu isn’t detecting the headset jack at all.
- In that case, we’d need to troubleshoot ALSA/driver settings (Step 3 or Step 5 from earlier).
👉 Would you like me to also show you how to make sure the headphone sink appears (using alsamixer and driver tweaks), in case your system doesn’t list it when you run pactl list short sinks?
3. Copilot , when I run the command "pactl list short sinks" .......... I got the message "Connection failure: Connection refused
pa_context_connect() failed: Connection refused" ........... what could go wrong ?
MICROSOFT Copilot Answer
Thanks for sharing that error — it’s a very useful clue. The message
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
means that the PulseAudio/PipeWire sound server isn’t running or isn’t accessible. The pactl tool talks to the audio server, so if the server isn’t active, you’ll get exactly this error.
🔎 What Could Be Wrong
- PipeWire/PulseAudio not running
Ubuntu 25 uses PipeWire (with a PulseAudio compatibility layer). If the service isn’t started, pactl can’t connect. - Service crash or misconfiguration
Sometimes the audio daemon crashes or fails to start after boot. - Wrong tool for your setup
If your system is using PipeWire only, you may need pw-cli or wpctl instead of pactl.
🛠️ How to Fix
1. Restart the Audio Services
Run:
systemctl --user restart pipewire pipewire-pulse
Then try:
pactl list short sinks
2. Check if PipeWire is Running
Run:
systemctl --user status pipewire
You should see it listed as active (running).
If it’s inactive, start it:
systemctl --user start pipewire pipewire-pulse
3. Try the PipeWire Tool
Ubuntu 25 may prefer wpctl (WirePlumber control tool). Run:
wpctl status
This shows all audio devices and which one is the default.
To set headphones as default:
wpctl set-default <ID>
(where <ID> is the number for your headphone device).
4. Reboot
If restarting services doesn’t help, a full reboot often clears up the audio server state.
✅ So the root cause is: your audio server (PipeWire/PulseAudio) isn’t running or accessible, so pactl can’t connect.
Would you like me to walk you through using wpctl instead of pactl? That’s the newer, recommended way on Ubuntu 25 and might be easier to get your headset working.
4. Copilot , when I run the command "wpctl status" ......... I got the message that says ............ "Could not connect to PipeWire" .......... what could go wrong ?
MICROSOFT Copilot Answer
That error tells us something very specific: PipeWire itself isn’t running on your Ubuntu 25 system. Since wpctl talks directly to PipeWire, if the daemon isn’t active, you’ll see “Could not connect to PipeWire.”
🔎 What Could Be Wrong
- PipeWire service not started → It may not be enabled to launch at login.
- PipeWire crashed → Sometimes the audio server fails to start after boot.
- Fallback to ALSA only → If PipeWire isn’t running, Ubuntu may fall back to basic ALSA, which explains why you only see “Speakers – Built-in Audio” and no headphone option.
- Misconfiguration → A missing or broken package can prevent PipeWire from starting.
🛠️ Steps to Fix
1. Check PipeWire Status
Run:
systemctl --user status pipewire
- If it says inactive (dead) or failed, that’s the problem.
2. Start PipeWire Manually
Run:
systemctl --user start pipewire pipewire-pulse
Then check again:
wpctl status
3. Enable PipeWire at Boot
If it wasn’t enabled, fix that with:
systemctl --user enable pipewire pipewire-pulse
4. Verify PipeWire Packages
Make sure the required packages are installed:
sudo apt install pipewire pipewire-audio-client-libraries wireplumber
5. Reboot
After enabling and installing, reboot the laptop. Then run:
wpctl status
You should now see a list of audio devices (sinks), including headphones if detected.
✅ So the root cause is: your audio server (PipeWire) isn’t running, so Ubuntu can’t switch outputs.
Would you like me to walk you through checking the systemctl --user status pipewire output line by line, so we can confirm whether it’s simply inactive or if it’s failing with an error?
5. Copilot , I got this message "pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
Active: inactive (dead)
TriggeredBy: ○ pipewire.socket
Condition: start condition unmet at Mon 2025-12-29 07:29:23 +08; 5min ago
Dec 29 07:06:01 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:09:26 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:09:26 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:22:19 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:22:19 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:29:23 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:29:23 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
lines 1-13...skipping...
○ pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
Active: inactive (dead)
TriggeredBy: ○ pipewire.socket
Condition: start condition unmet at Mon 2025-12-29 07:29:23 +08; 5min ago
Dec 29 07:06:01 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
Dec 29 07:09:26 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
Dec 29 07:09:26 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
Dec 29 07:22:19 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
Dec 29 07:22:19 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
Dec 29 07:29:23 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
Dec 29 07:29:23 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
~
" ........... when I run the command "systemctl --user status pipewire" .........so , what could go wrong ? THANKS.
MICROSOFT Copilot Answer
Great job checking the service status — the message you’re seeing actually explains the situation clearly. Let’s break it down:
🔎 What the Log Means
ConditionUser=!root → PipeWire is designed to run as a regular user service, not as root.- The log says: “PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root)”.
- This means you tried to check or start PipeWire in a context where
systemd thinks you’re root (or not a normal user session). Since PipeWire is a user service, it refuses to start under root.
🛠️ How to Fix
Make sure you’re running commands as your normal user, not with sudo.
Start PipeWire in your user session
systemctl --user start pipewire pipewire-pulse
Then check:
wpctl status
You should now see your audio devices.
Enable PipeWire to start automatically
systemctl --user enable pipewire pipewire-pulse
This ensures it runs every time you log in.
If it still doesn’t start
✅ Summary
The root cause is: PipeWire won’t start because you’re invoking it as root. It must run as your normal user session.
Once you restart it correctly as your user, wpctl status should show sinks (like headphones) and you’ll be able to set them as default.
👉 Do you want me to walk you through the exact sequence of commands (without sudo) so you can try them right away and confirm whether PipeWire comes alive?
6. Copilot, when I run the command "pactl list short sinks" ......... I got the message........ "56 alsa_output.pci-0000_00_1b.0.analog-stereo PipeWire s32le 2ch 48000Hz RUNNING".......what could go wrong?
MICROSOFT Copilot Answer
Thanks for sharing that output — it’s very telling. Let’s break it down:
🔎 What the Output Means
56 alsa_output.pci-0000_00_1b.0.analog-stereo PipeWire s32le 2ch 48000Hz RUNNING
alsa_output.pci-0000_00_1b.0.analog-stereo → This is the only audio sink currently detected. It represents your laptop’s built‑in speakers.PipeWire → Confirms the audio server is running and managing devices.RUNNING → Audio is actively being sent to this sink (your speakers).- No headphone sink listed → Your headset jack is not being recognized as a separate output device.
🛠️ What Could Be Wrong
- Jack detection issue
The system isn’t detecting when headphones are plugged in, so it never creates a “headphones” sink. - Driver/ALSA quirk
On some MSI laptops, the Realtek audio chipset needs extra configuration to expose the headphone jack separately. - Fallback mode
PipeWire may only be seeing one output (speakers), so plugging in headphones doesn’t switch automatically.
✅ Next Steps
1. Check ALSA Mixer
Open a terminal and run:
alsamixer
- Use arrow keys to navigate.
- Look for a Headphone channel.
- If it’s muted (shows
MM at the bottom), press M to unmute.
2. Force Jack Detection via ALSA Options
Edit the ALSA config file:
sudo nano /etc/modprobe.d/alsa-base.conf
Add this line at the end:
options snd-hda-intel model=generic
Save and reboot.
This forces the driver to treat the headphone jack more generically, which often fixes detection issues.
3. Verify After Reboot
Run again:
pactl list short sinks
You should ideally see two sinks:
analog-stereo (speakers)analog-headphones (headset jack)
4. If Still No Headphones Sink
- Check if your headset works on another device (to rule out hardware).
- Try updating audio packages:
sudo apt update
sudo apt upgrade
- Consider installing
pavucontrol (PulseAudio Volume Control) for a more detailed GUI to switch outputs:
sudo apt install pavucontrol
🎯 Summary
Right now, Ubuntu only sees your speakers. The headset jack isn’t being exposed as a separate sink, so audio can’t be routed to it. The fix usually involves unmuting in ALSA or forcing jack detection with a driver option.
👉 Do you want me to walk you through editing alsa-base.conf step‑by‑step, so you can try the driver tweak safely?
7. Copilot , I saw the diagram but how do I look for the Headphone channel ?
MICROSOFT Copilot Answer
Great question — let’s walk through how to actually find the Headphone channel inside alsamixer, since the interface can be a bit confusing at first.
🎧 Step‑by‑Step in alsamixer
- Open alsamixer
alsamixer
You’ll see a colorful bar‑graph interface in the terminal.
- Switch to the Right Sound Card
- Press F6 to select the sound card.
- You’ll see a list (often something like
default, pipewire, pulse, and HDA Intel PCH). - Choose the HDA Intel PCH (or similar — it’s the hardware card for your laptop’s audio).
- Navigate Through Channels
- Use the left/right arrow keys to move across channels.
- Each channel has a label at the bottom (e.g., Master, PCM, Speaker, Headphone).
- The bars above show volume levels.
- Look for “Headphone”
- If your driver exposes it, you’ll see a channel named Headphone.
- If it shows
MM at the bottom, that means it’s muted. - Press M to unmute (it should change to
OO). - Use the up arrow to raise the volume.
- Save and Exit
- Just press Esc to exit — changes are applied immediately.
🔍 If You Don’t See “Headphone”
- That means the driver isn’t exposing the headphone jack separately.
- In that case, Ubuntu only shows “Speakers” as the output, which matches what you saw in
pactl. - The fix is usually adding an ALSA driver option (
model=generic or model=headset) in /etc/modprobe.d/alsa-base.conf.
✅ So: in alsamixer, you’re looking for a channel labeled “Headphone” when you scroll sideways with the arrow keys. If it’s missing, that confirms the driver isn’t detecting your headset jack properly.
Would you like me to show you the exact line to add in alsa-base.conf so that Ubuntu forces the driver to expose the headphone jack? That’s the next logical step if you don’t see “Headphone” in alsamixer.
norizan@nurul555:~$
norizan@nurul555:~$ sudo su
[sudo: authenticate] Password:
root@nurul555:/home/norizan#
root@nurul555:/home/norizan#
root@nurul555:/home/norizan# pactl list short sinks
Command 'pactl' not found, but can be installed with:
apt install pulseaudio-utils
root@nurul555:/home/norizan# apt-get install pulseaudio-utils
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Solving dependencies... Done
The following additional packages will be installed:
libpulsedsp
Suggested packages:
pulseaudio
The following NEW packages will be installed:
libpulsedsp pulseaudio-utils
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 101 kB of archives.
After this operation, 466 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://my.archive.ubuntu.com/ubuntu questing/universe amd64 libpulsedsp amd64 1:17.0+dfsg1-2ubuntu3 [23.6 kB]
Get:2 http://my.archive.ubuntu.com/ubuntu questing/universe amd64 pulseaudio-utils amd64 1:17.0+dfsg1-2ubuntu3 [77.3 kB]
Fetched 101 kB in 2s (50.4 kB/s)
Selecting previously unselected package libpulsedsp:amd64.
(Reading database ... 192518 files and directories currently installed.)
Preparing to unpack .../libpulsedsp_1%3a17.0+dfsg1-2ubuntu3_amd64.deb ...
Unpacking libpulsedsp:amd64 (1:17.0+dfsg1-2ubuntu3) ...
Selecting previously unselected package pulseaudio-utils.
Preparing to unpack .../pulseaudio-utils_1%3a17.0+dfsg1-2ubuntu3_amd64.deb ...
Unpacking pulseaudio-utils (1:17.0+dfsg1-2ubuntu3) ...
Setting up libpulsedsp:amd64 (1:17.0+dfsg1-2ubuntu3) ...
Setting up pulseaudio-utils (1:17.0+dfsg1-2ubuntu3) ...
Processing triggers for man-db (2.13.1-1) ...
root@nurul555:/home/norizan#
root@nurul555:/home/norizan#
root@nurul555:/home/norizan#
root@nurul555:/home/norizan#
root@nurul555:/home/norizan#
root@nurul555:/home/norizan#
root@nurul555:/home/norizan#
root@nurul555:/home/norizan# alsamixer
cannot open mixer: Host is down
root@nurul555:/home/norizan#
root@nurul555:/home/norizan#
root@nurul555:/home/norizan# alsamixer
cannot open mixer: Host is down
root@nurul555:/home/norizan#
root@nurul555:/home/norizan#
root@nurul555:/home/norizan# pactl list short sinks
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
root@nurul555:/home/norizan# systemctl --user restart pipewire pipewire-pulse
root@nurul555:/home/norizan# alsamixer
cannot open mixer: Host is down
root@nurul555:/home/norizan#
root@nurul555:/home/norizan#
root@nurul555:/home/norizan# apt-get alsamixer
E: Invalid operation alsamixer
root@nurul555:/home/norizan#
root@nurul555:/home/norizan# apt-get update
Get:1 http://security.ubuntu.com/ubuntu questing-security InRelease [136 kB]
Get:2 http://security.ubuntu.com/ubuntu questing-security/main amd64 Components [448 B]
Get:3 http://security.ubuntu.com/ubuntu questing-security/restricted amd64 Components [212 B]
Get:4 http://security.ubuntu.com/ubuntu questing-security/universe amd64 Components [6,764 B]
Get:5 http://security.ubuntu.com/ubuntu questing-security/multiverse amd64 Components [212 B]
Hit:6 http://my.archive.ubuntu.com/ubuntu questing InRelease
Hit:7 http://my.archive.ubuntu.com/ubuntu questing-updates InRelease
Hit:8 http://my.archive.ubuntu.com/ubuntu questing-backports InRelease
Fetched 143 kB in 5s (28.0 kB/s)
Reading package lists... Done
root@nurul555:/home/norizan# apt-get upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
root@nurul555:/home/norizan# pactl list short sinks
Connection failure: Connection refused
pa_context_connect() failed: Connection refused
root@nurul555:/home/norizan# systemctl --user restart pipewire pipewire-pulse
root@nurul555:/home/norizan# wpctl status
Could not connect to PipeWire
root@nurul555:/home/norizan# systemctl --user status pipewire
○ pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
Active: inactive (dead)
TriggeredBy: ○ pipewire.socket
Condition: start condition unmet at Mon 2025-12-29 07:22:19 +08; 5min ago
└─ ConditionUser=!root was not met
Dec 29 07:06:01 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:09:26 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:09:26 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:22:19 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:22:19 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
root@nurul555:/home/norizan#
root@nurul555:/home/norizan# systemctl --user start pipewire pipewire-pulse
root@nurul555:/home/norizan# wpctl status
Could not connect to PipeWire
root@nurul555:/home/norizan# systemctl --user enable pipewire pipewire-pulse
Created symlink '/root/.config/systemd/user/default.target.wants/pipewire.service' → '/usr/lib/systemd/user/pipewire.service'.
Created symlink '/root/.config/systemd/user/sockets.target.wants/pipewire.socket' → '/usr/lib/systemd/user/pipewire.socket'.
Created symlink '/root/.config/systemd/user/default.target.wants/pipewire-pulse.service' → '/usr/lib/systemd/user/pipewire-pulse.service'.
Created symlink '/root/.config/systemd/user/sockets.target.wants/pipewire-pulse.socket' → '/usr/lib/systemd/user/pipewire-pulse.socket'.
root@nurul555:/home/norizan# wpctl status
Could not connect to PipeWire
root@nurul555:/home/norizan# systemctl --user enable pipewire pipewire-pulse
root@nurul555:/home/norizan# wpctl status
Could not connect to PipeWire
root@nurul555:/home/norizan# apt install pipewire pipewire-audio-client-libraries wireplumber
pipewire is already the newest version (1.4.7-3ubuntu2).
pipewire set to manually installed.
wireplumber is already the newest version (0.5.10-3).
wireplumber set to manually installed.
Installing:
pipewire-audio-client-libraries
Installing dependencies:
pipewire-jack
Summary:
Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
Download size: 133 kB
Space needed: 613 kB / 203 GB available
Continue? [Y/n] Y
Get:1 http://my.archive.ubuntu.com/ubuntu questing/universe amd64 pipewire-jack amd64 1.4.7-3ubuntu2 [129 kB]
Get:2 http://my.archive.ubuntu.com/ubuntu questing/universe amd64 pipewire-audio-client-libraries all 1.4.7-3ubuntu2 [3,890 B]
Fetched 133 kB in 5s (26.2 kB/s)
Selecting previously unselected package pipewire-jack:amd64.
(Reading database ... 192561 files and directories currently installed.)
Preparing to unpack .../pipewire-jack_1.4.7-3ubuntu2_amd64.deb ...
Unpacking pipewire-jack:amd64 (1.4.7-3ubuntu2) ...
Selecting previously unselected package pipewire-audio-client-libraries.
Preparing to unpack .../pipewire-audio-client-libraries_1.4.7-3ubuntu2_all.deb ...
Unpacking pipewire-audio-client-libraries (1.4.7-3ubuntu2) ...
Setting up pipewire-jack:amd64 (1.4.7-3ubuntu2) ...
Setting up pipewire-audio-client-libraries (1.4.7-3ubuntu2) ...
Processing triggers for man-db (2.13.1-1) ...
root@nurul555:/home/norizan# wpctl status
Could not connect to PipeWire
root@nurul555:/home/norizan#
root@nurul555:/home/norizan# systemctl --user enable pipewire pipewire-pulse
root@nurul555:/home/norizan# wpctl status
Could not connect to PipeWire
root@nurul555:/home/norizan# apt install pipewire pipewire-audio-client-libraries wireplumber
pipewire is already the newest version (1.4.7-3ubuntu2).
pipewire-audio-client-libraries is already the newest version (1.4.7-3ubuntu2).
wireplumber is already the newest version (0.5.10-3).
Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
root@nurul555:/home/norizan# systemctl --user status pipewire
○ pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
Active: inactive (dead)
TriggeredBy: ○ pipewire.socket
Condition: start condition unmet at Mon 2025-12-29 07:29:23 +08; 5min ago
Dec 29 07:06:01 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:09:26 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:09:26 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:22:19 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:22:19 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:29:23 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
Dec 29 07:29:23 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (Conditi>
lines 1-13...skipping...
○ pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
Active: inactive (dead)
TriggeredBy: ○ pipewire.socket
Condition: start condition unmet at Mon 2025-12-29 07:29:23 +08; 5min ago
Dec 29 07:06:01 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
Dec 29 07:09:26 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
Dec 29 07:09:26 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
Dec 29 07:22:19 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
Dec 29 07:22:19 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
Dec 29 07:29:23 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
Dec 29 07:29:23 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Service was skipped because of an unmet condition check (ConditionUser=!root).
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-13/13 (END)...skipping...
○ pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; enabled; preset: enabled)
Active: inactive (dead)
TriggeredBy: ○ pipewire.socket
Condition: start condition unmet at Mon 2025-12-29 07:29:23 +08; 5min ago
Dec 29 07:06:01 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Servic>
Dec 29 07:09:26 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Servic>
Dec 29 07:09:26 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Servic>
Dec 29 07:22:19 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Servic>
Dec 29 07:22:19 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Servic>
Dec 29 07:29:23 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Servic>
Dec 29 07:29:23 nurul555 systemd[5550]: pipewire.service - PipeWire Multimedia Servic>
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-13/13 (END)
______________________________________________________________
After I was informed by MICROSOFT Copilot that the command should be run not in superuser mode but in normal user mode , then the troubleshooting process has to be done in normal user mode , so , commands and tips given by MICROSOFT Copilot , during the troubleshooting process should be type in normal user mode
______________________________________________________________
norizan@nurul555:~$
norizan@nurul555:~$
norizan@nurul555:~$
norizan@nurul555:~$
norizan@nurul555:~$ wpctl status
PipeWire 'pipewire-0' [1.4.7, norizan@nurul555, cookie:3320775013]
└─ Clients:
33. WirePlumber [1.4.7, norizan@nurul555, pid:2631]
37. pipewire [1.4.7, norizan@nurul555, pid:2641]
47. WirePlumber [export] [1.4.7, norizan@nurul555, pid:2631]
59. GNOME Volume Control Media Keys [1.4.7, norizan@nurul555, pid:3006]
60. gnome-shell [1.4.7, norizan@nurul555, pid:2885]
61. GNOME Shell Volume Control [1.4.7, norizan@nurul555, pid:2885]
62. xdg-desktop-portal [1.4.7, norizan@nurul555, pid:3433]
63. Firefox [1.4.7, norizan@nurul555, pid:3727]
64. Mutter [1.4.7, norizan@nurul555, pid:2885]
66. GNOME Settings [1.4.7, norizan@nurul555, pid:4783]
67. GNOME Settings [1.4.7, norizan@nurul555, pid:4783]
86. speech-dispatcher-dummy [1.4.7, norizan@nurul555, pid:6467]
92. Firefox [1.4.7, norizan@nurul555, pid:3727]
98. wpctl [1.4.7, norizan@nurul555, pid:7671]
Audio
├─ Devices:
│ 51. Built-in Audio [alsa]
│ 52. Built-in Audio [alsa]
│
├─ Sinks:
│ * 56. Built-in Audio Analog Stereo [vol: 0.26]
│
├─ Sources:
│ * 57. Built-in Audio Analog Stereo [vol: 1.00]
│
├─ Filters:
│
└─ Streams:
75. GNOME Settings
65. monitor_FR
68. input_FL < ALC892 Analog:capture_FL [active]
70. monitor_FL
73. input_FR < ALC892 Analog:capture_FR [active]
77. GNOME Settings
74. input_FR < ALC892 Analog:monitor_FR [active]
76. input_FL < ALC892 Analog:monitor_FL [active]
78. monitor_FR
79. monitor_FL
81. Firefox
82. output_FL > ALC892 Analog:playback_FL [active]
83. output_FR > ALC892 Analog:playback_FR [active]
87. speech-dispatcher-dummy
88. output_FL > ALC892 Analog:playback_FL [paused]
89. output_FR > ALC892 Analog:playback_FR [paused]
93. GNOME Settings
101. input_FL < speech-dispatcher-dummy:output_FL [init]
102. monitor_FL
103. input_FR < speech-dispatcher-dummy:output_FR [init]
104. monitor_FR
Video
├─ Devices:
│
├─ Sinks:
│
├─ Sources:
│
├─ Filters:
│
└─ Streams:
Settings
└─ Default Configured Devices:
0. Audio/Sink alsa_output.pci-0000_00_1b.0.analog-stereo
norizan@nurul555:~$
norizan@nurul555:~$
norizan@nurul555:~$ pactl list short sinks
56 alsa_output.pci-0000_00_1b.0.analog-stereo PipeWire s32le 2ch 48000Hz RUNNING
norizan@nurul555:~$
norizan@nurul555:~$ alsamixer
norizan@nurul555:~$
PHEW ! It is working at last ! Thank you very much ALLAH for all the knowledge that you have given me !
