Plasma shows “Failed to connect to PipeWire”

Support Sound
1

Hi, i have a problem:
the journal shows constant errors like:

oct 16 15:44:02 manjaro plasmashell[2377]: kpipewire_logging: error: “Failed to connect to PipeWire” 0
oct 16 15:44:02 manjaro plasmashell[2377]: received error while creating the stream “Failed to connect to PipeWire” Media monitor will not work.
oct 16 15:44:07 manjaro plasmashell[2377]: pw.context: 0x55c805b6a610: no modules loaded from context.modules
oct 16 15:44:07 manjaro plasmashell[2377]: pw.core: 0x55c8000065b0: can’t find protocol ‘PipeWire:Protocol:Native’: Operation not supported
oct 16 15:44:07 manjaro plasmashell[2377]: kpipewire_logging: error: “Failed to connect to PipeWire” 0
oct 16 15:44:07 manjaro plasmashell[2377]: received error while creating the stream “Failed to connect to PipeWire” Media monitor will not work.
oct 16 15:44:07 manjaro plasmashell[2377]: pw.context: 0x55c805b6a610: no modules loaded from context.modules
oct 16 15:44:07 manjaro plasmashell[2377]: pw.core: 0x55c8000065b0: can’t find protocol ‘PipeWire:Protocol:Native’: Operation not supported
oct 16 15:44:07 manjaro plasmashell[2377]: kpipewire_logging: error: “Failed to connect to PipeWire” 0
oct 16 15:44:07 manjaro plasmashell[2377]: received error while creating the stream “Failed to connect to PipeWire” Media monitor will not work

Mod edit (scotty65): added line breaks to the above code so that each log entry is on a separate line

Sometimes Plasma didn’t start after reboot, and I had to run:

plasmashell --replace >/dev/null 2>&1 &

Now the desktop works fine, but these messages keep flooding the journal.
I’ve tried several fixes (including suggestions from ChatGPT and other forums), but nothing changed.

Everything seems to work perfectly (audio, video, desktop effects, etc.),
but I would really like to stop these messages or understand what’s causing them.

My system:

      ~  inxi -Fazy                                                                                                                                           127 ✘ 
System:
  Kernel: 6.12.48-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=e8ad0b83-8ba5-4838-bd74-fb0464854b35 rw
    resume=UUID=f868137e-dac2-4bd8-b260-70ad9aef5f1d udev.log_priority=3
    optimus-manager.startup=hybrid nvidia_drm.modeset=1
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.18.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: PCSpecialist product: GM6PX0X v: Standard
    serial: <superuser required>
  Mobo: TongFang model: GM6PX0X v: Standard serial: <superuser required>
    part-nu: 0001 uuid: <superuser required> UEFI: American Megatrends LLC.
    v: N.1.09A02 date: 05/15/2023
Battery:
  ID-1: BAT0 charge: 97.1 Wh (98%) condition: 99.1/99.1 Wh (100%) volts: 16.47
    min: 15.48 model: standard type: Li-ion serial: <filter> charging:
    status: not charging cycles: N/A
CPU:
  Info: model: 13th Gen Intel Core i9-13900HX bits: 64 type: MST AMCP
    arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+
    process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183) stepping: 1
    microcode: 0x12F
  Topology: cpus: 1x dies: 1 clusters: 12 cores: 24 threads: 32 mt: 8 tpc: 2
    st: 16 smt: enabled cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32
    KiB, 16x64 KiB L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
  Speed (MHz): avg: 1256 min/max: 800/5200:5400:3900 scaling:
    driver: intel_pstate governor: powersave cores: 1: 1256 2: 1256 3: 1256
    4: 1256 5: 1256 6: 1256 7: 1256 8: 1256 9: 1256 10: 1256 11: 1256 12: 1256
    13: 1256 14: 1256 15: 1256 16: 1256 17: 1256 18: 1256 19: 1256 20: 1256
    21: 1256 22: 1256 23: 1256 24: 1256 25: 1256 26: 1256 27: 1256 28: 1256
    29: 1256 30: 1256 31: 1256 32: 1256 bogomips: 154880
  Flags-basic: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: indirect_target_selection status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional;
    PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
  Type: vmscape mitigation: IBPB before exit to userspace
Graphics:
  Device-1: Intel Raptor Lake-S UHD Graphics vendor: AIstone Global
    driver: i915 v: kernel alternate: xe arch: Xe process: Intel 10nm
    built: 2020-21 ports: active: none off: eDP-1 empty: DP-1, DP-2, HDMI-A-1,
    HDMI-A-2, HDMI-A-3, HDMI-A-4 bus-ID: 00:02.0 chip-ID: 8086:a788
    class-ID: 0300
  Device-2: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile]
    vendor: AIstone Global driver: nvidia v: 580.82.09
    alternate: nouveau,nvidia_drm non-free: 550-580.xx+
    status: current (as of 2025-08) arch: Lovelace code: AD1xx
    process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4 speed: 16 GT/s lanes: 8
    ports: active: none off: DP-3,HDMI-A-5 empty: DP-4,eDP-2 bus-ID: 01:00.0
    chip-ID: 10de:28a0 class-ID: 0300
  Device-3: Trust USB Camera driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:3 chip-ID: 145f:0203
    class-ID: 0102 serial: <filter>
  Device-4: Chicony FHD Webcam driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-5:4 chip-ID: 04f2:b7c2
    class-ID: 0e02 serial: <filter>
  Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: modesetting,nvidia dri: iris
    gpu: i915,nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4520x1920 s-dpi: 110 s-size: 1045x444mm (41.14x17.48")
    s-diag: 1135mm (44.7")
  Monitor-1: not-matched mapped: DP-0 pos: primary,bottom-r res:
    mode: 3440x1440 hz: 160 scale: 100% (1) dpi: 109
    size: 800x330mm (31.5x12.99") diag: 865mm (34.07") modes: N/A
  Monitor-2: not-matched mapped: HDMI-0 pos: top-left res: mode: 1920x1080
    hz: 60 scale: 177% (0.5625) to: 1080x1920 dpi: 94
    size: 521x293mm (20.51x11.54") diag: 598mm (23.53") modes: N/A
  Monitor-3: eDP-1 mapped: eDP-1-1 note: disabled model: BOE Display 0x0a3b
    built: 2021 res: 1920x1080 dpi: 189 gamma: 1.2 size: 344x215mm (13.54x8.46")
    diag: 406mm (16") ratio: 16:10 modes: 2560x1600
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 2 drv: iris device: 3 drv: swrast gbm: drv: nvidia
    surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 580.82.09
    glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 4060 Laptop
    GPU/PCIe/SSE2 memory: 7.81 GiB
  API: Vulkan v: 1.4.321 layers: 7 device: 0 type: discrete-gpu name: NVIDIA
    GeForce RTX 4060 Laptop GPU driver: nvidia v: 580.82.09
    device-ID: 10de:28a0 surfaces: N/A device: 1 type: integrated-gpu
    name: Intel Graphics (RPL-S) driver: mesa intel v: 25.2.3-arch1.2
    device-ID: 8086:a788 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Raptor Lake High Definition Audio vendor: AIstone Global
    driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
    bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0403
  Device-2: NVIDIA AD107 High Definition Audio vendor: AIstone Global
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 8
    bus-ID: 01:00.1 chip-ID: 10de:22be class-ID: 0403
  Device-3: Trust USB Camera driver: snd-usb-audio,uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-3:3 chip-ID: 145f:0203
    class-ID: 0102 serial: <filter>
  API: ALSA v: k6.12.48-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.4.8 status: active (process) with:
    1: pipewire-pulse status: active 2: wireplumber status: active
    3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Raptor Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:7a70 class-ID: 0280
  IF: wlo1 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: AIstone Global driver: r8169
    v: kernel pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 3a:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp58s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: docker0 state: down mac: <filter>
  IF-ID-2: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
  Info: services: NetworkManager,wpa_supplicant
Bluetooth:
  Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-14:10 chip-ID: 8087:0033
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Drives:
  Local Storage: total: 1.86 TiB used: 728.86 GiB (38.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Solidgm model: SSDPFKNU020TZ
    size: 1.86 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 002C temp: 30.9 C scheme: GPT
Partition:
  ID-1: / raw-size: 120 GiB size: 117.81 GiB (98.17%) used: 93.97 GiB (79.8%)
    fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 301 MiB size: 300.4 MiB (99.79%)
    used: 308 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 1.34 TiB size: 1.31 TiB (98.35%)
    used: 634.89 GiB (47.2%) fs: ext4 dev: /dev/nvme0n1p4 maj-min: 259:4
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 49.5 C mobo: N/A gpu: nvidia temp: 41 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 64 GiB note: est. available: 62.53 GiB used: 5.94 GiB (9.5%)
  Processes: 547 Power: uptime: 12m states: freeze,mem,disk suspend: s2idle
    avail: deep wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend,
    test_resume image: 24.98 GiB services: org_kde_powerdevil,
    power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
    tool: systemctl
  Packages: 1842 pm: pacman pkgs: 1768 libs: 425 tools: pamac,yay pm: flatpak
    pkgs: 60 pm: snap pkgs: 14 Compilers: clang: 20.1.8 gcc: 15.2.1 Shell: Zsh
    v: 5.9 running-in: kitty inxi: 3.3.39

Any ideas or workarounds would be greatly appreciated.

2

My only suggestion is don’t use ChatGPT for this type of questions. When it doesn’t know something, it creates a false answer that sounds plausible instead of admitting that it doesn’t know.

2 Likes
3

Did you install pipewire via the meta package manjaro-pipewire? (I had to do so to get everything working.)

2 Likes
4

Thanks for reply @jofi. Now I did but I continue with the same error in the journal :frowning: Or maybe I need to remove others pipewire installed?

Thanks again

5

Normally not - there is the legacy pipewire-media-session package though. This shouldn’t be installed.

6

Thanks, I have checked and I don’t have pipewire-media-sessionbut the error continue in the journal :frowning:

7

Does the issue also occur on a Plasma Wayland session? With Nvidia seeming to no longer be an issue with Plasma Wayland, you should probably look at making the switch before Stable branch updates to Plasma 6.4 (or 6.5), as it will automatically default to Wayland with no X11 session available. You may find that you encounter no issues with pipewire on Wayland.

Plasma 6.4/6.5 users wanting to run Plasma on X11 will have to manually install a new package: plasma-x11-session:

pamac install plasma-x11-session

or

sudo pacman -Syu plasma-x11-session

Note: plasma-x11-session is not available for Plasma 6.3, so Stable branch users won’t be able to install it until Plasma 6.4 arrives in the Stable repos.

You can change your Plasma session from X11 to Wayland by selecting the session type at the login screen (Wayland is now KDE’s default for Plasma).

If you have set up autologin to skip the password screen, you can change to a Wayland session by opening System Settings → Colors & Themes → Login Screen (SDDM) → Behavior.

To see if your current session is running on X11 or Wayland, run the following command in a terminal:

echo $XDG_SESSION_TYPE

For those curious about how Wayland differs from X11:

The more correct method for reloading Plasma on a systemd-based system such as Manjaro is:

systemctl restart --user plasma-plasmashell
2 Likes
8

Thanks for your detailed reply.
I switched to Wayland, but I still have the same problem.
Sometimes the desktop starts normally (Plasma loads fine, but the journal log keeps showing the error), and other times I get a black background and the taskbar doesn’t appear.

I was trying to remember if I changed something a few weeks ago, and I realized that I used to have PulseAudio. Everything was working fine until one day my microphone stopped being detected and people couldn’t hear me.

To fix that, I installed PipeWire — maybe that’s what caused all these issues, but I’m not sure what steps I should take to completely remove PipeWire and reinstall PulseAudio properly.

I didn’t want to ask ChatGPT again because last time it told me to install PipeWire when I explained my problem (I know… bad idea :sweat_smile:).

Thanks for your help, and I really hope we can find a solution!

9

I changed to Wayland and software like Flameshot, RustDesk, Zoom (sharing screen) is not working good or it’s not working. Now I remember why I was using x11 :frowning: :frowning: :frowning:

10

Did you check whether microphone and camera work, too? Did you check

systemctl --user status pipewire
systemctl --user status wireplumber

Since it’s an error message there must be something that doesn’t work - perhaps this will point to the right direction?

11

This suggests that there is an incorrect configuration file or maybe modules missing. What does pw-config paths -n client.conf output?

12 
sudo pacman -S manjaro-pulse

If memory serves (sometimes it doesn’t) you should be prompted automatically to uninstall Pipewire when running this command.

@nikgnomic can likely give more complete answers for your audio related questions the next time he is online.

Regards.

13

Hi,

I wonder whether you could read these posts in order to solve the problem.

Although I think it may be usefull.

‘https://forum.manjaro.org/t/kpipewire-message-spamming-log/162761’

‘https://forum.manjaro.org/t/plasma-6-fails-on-running-different-builtin-applications/161941/7’

Regards,

14 
systemctl --user status pipewire
● pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: enabled)
Active: active (running) since Sat 2025-10-18 14:55:43 CEST; 13min ago
Invocation: 3a1587424b6349cab0bdbd6685fd7491
TriggeredBy: ● pipewire.socket
Main PID: 2123 (pipewire)
Tasks: 3 (limit: 76562)
Memory: 13.5M (peak: 15.6M)
CPU: 784ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─2123 /usr/bin/pipewire

oct 18 14:55:43 manjaro systemd\[1723\]: Started PipeWire Multimedia Service.systemctl --user status wireplumber
● wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
Active: active (running) since Sat 2025-10-18 14:55:43 CEST; 13min ago
Invocation: 0985ed585189401b85abb9b7ba89e420
Main PID: 2126 (wireplumber)
Tasks: 6 (limit: 76562)
Memory: 30.9M (peak: 30.9M)
CPU: 692ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
└─2126 /usr/bin/wireplumber

oct 18 14:55:43 manjaro systemd\[1723\]: Started Multimedia Service Session Manager.
oct 18 14:55:43 manjaro wireplumber\[2126\]: wireplumber: Old configuration file detected: /home/diego/.config/wireplumber/main.lua.d/98-fix-internal-mic.lua
oct 18 14:55:43 manjaro wireplumber\[2126\]: wireplumber: Old configuration file detected: /home/diego/.config/wireplumber/main.lua.d/99-disable-camera.lua
oct 18 14:55:43 manjaro wireplumber\[2126\]: wireplumber: Lua configuration files are NOT supported in WirePlumber 0.5. You need to port them to the new format if you want>
→ See https://pipewire.pages.freedesktop.org/wireplumber/daemon/configuration/migration.html
oct 18 14:55:44 manjaro wireplumber\[2126\]: wp-device: SPA handle ‘api.libcamera.enum.manager’ could not be loaded; is it installed?
oct 18 14:55:44 manjaro wireplumber\[2126\]: s-monitors-libcamera: PipeWire’s libcamera SPA plugin is missing or broken. Some camera types may not be supported.
oct 18 14:55:44 manjaro wireplumber\[2126\]: wp-event-dispatcher: <WpAsyncEventHook:0x564df1da6700> failed: failed to activate item: Object activation aborted: proxy destr>

Thanks for your reply.

systemctl --user status pipewire
pipewire.service - PipeWire Multimedia ServiceLoaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: enabled)
Active: active (running) since Sat 2025-10-18 14:55:43 CEST; 13min ago
Invocation: 3a1587424b6349cab0bdbd6685fd7491
TriggeredBy: pipewire.socketMain PID: 2123 (pipewire)
Tasks: 3 (limit: 76562)Memory: 13.5M (peak: 15.6M)
CPU: 784ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
└─2123 /usr/bin/pipewireoct 18 14:55:43 manjaro systemd[1723]: Started PipeWire Multimedia Service.

systemctl --user status wireplumber
wireplumber.service - Multimedia Service Session ManagerLoaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
Active: active (running) since Sat 2025-10-18 14:55:43 CEST; 13min ago
Invocation: 0985ed585189401b85abb9b7ba89e420Main PID: 2126 (wireplumber)
Tasks: 6 (limit: 76562)
Memory: 30.9M (peak: 30.9M)CPU: 692ms
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
└─2126 /usr/bin/wireplumberoct 18 14:55:43 manjaro systemd[1723]: Started Multimedia Service Session Manager.
oct 18 14:55:43 manjaro wireplumber[2126]: wireplumber: Old configuration file detected: /home/diego/.config/wireplumber/main.lua.d/98-fix-internal-mic.lua
oct 18 14:55:43 manjaro wireplumber[2126]: wireplumber: Old configuration file detected: /home/diego/.config/wireplumber/main.lua.d/99-disable-camera.lua
oct 18 14:55:43 manjaro wireplumber[2126]: wireplumber: Lua configuration files are NOT supported in WirePlumber 0.5. You need to port them to the new format if you want>→
See oct 18 14:55:44 manjaro wireplumber[2126]: wp-device: SPA handle ‘api.libcamera.enum.manager’ could not be loaded; is it installed?
oct 18 14:55:44 manjaro wireplumber[2126]: s-monitors-libcamera: PipeWire’s libcamera SPA plugin is missing or broken. Some camera types may not be supported.
oct 18 14:55:44 manjaro wireplumber[2126]: wp-event-dispatcher: WpAsyncEventHook:0x564df1da6700 failed: failed to activate item:
Object activation aborted: proxy destr>Both services show as active (running) and no errors appear there.`

I also tested my microphone and camera — both seem to work fine.
The only issue is that Plasma sometimes starts with a black background (no panel or taskbar), and the journal keeps showing the same repeated error messages related to PipeWire and I’m obsessive trying to remove the error :melting_face:

Everything else (audio, video, desktop effects) works perfectly.
That’s why I’m wondering if this could be just a false log error or some leftover configuration from when I switched from PulseAudio to PipeWire.

Here you have the output:

pw-config paths -n client.conf 
{
“config.path”: “/home/diego/.config/pipewire/client.conf”
}

Thanks for try to help. I cannot enter to this links.
Maybe it’s a private page? I can see “Page not found” :frowning:

Thank you all for trying to help me.

Mod edit: Post formatting tidy-up.

15

Hi @ZeR0ByTe ,

I agree with you, the links are not reachable from. I found the posts when I searched in the browser

arch wiki kpipewire_logging: error: "Failed to connect to PipeWire" 0

Maybe, these have been removed.

I searched in the forum and find these posts, I hope it help. There is an post not answered with the same problem above.

https://forum.manjaro.org/t/stable-update-2024-05-13-kernels-plasma-6-gnome-46-lxqt-2-0-nvidia-pacman/161404/140

Regards,

Mod edit:- Corrected borked URL. No charge.

16

Could be a false error log - Plasma has lots of smaller and bigger issues (the more so if one uses Activities).

One more thing you could try is to install pipewire-libcamera.

17

Pipewire/wireplumber is driving me insane with "Failed to connect PipeWire context" - Help - KDE Discuss

KSystemLog keeps giving these warnings:

kpipewire_logging: error: "Failed to connect to PipeWire" 0
kwin_screencast: Failed to connect PipeWire context

:white_check_mark: Solved by jamal-ali1989 in post 6

I have found the solution. The problem was that I had an unnecessary line on .bashrc file. Removing it fixed the problem. The culprit was export PIPEWIRE_RUNTIME_DIR=/run/user/1000/pipewire

ben2talk

This particular variable should be set automatically by systemd or PipeWire itself - when the session starts - via pipewire.service

The runtime directory is dynamically managed by the system… so I imagine that was a rather unfortunate ‘fix’.

PipeWire - Troubleshooting - No sound devices show up in KDE Plasma

PipeWire clients (including the desktop environment) may rely on the XDG_RUNTIME_DIR environment variable to connect to the PipeWire daemon. If you experience no sound devices immediately after login, it may be because this variable has manually been set to the wrong path.

Although this be resolved by manually restarting PipeWire, other issues can still occur such as being unable to screen share in Chromium (with pipewire context failed). XDG_RUNTIME_DIR is automatically set by pam_systemd(8), so you should remove any instances of it being set in your initialization files.

Wireplumber 0.5.12 Documentation - Migrating configuration from 0.4

The configuration file format has changed in version 0.5. No automatic migration of old configuration files is performed, so you will have to manually update them. This document describes the changes and how to update your configuration.

In WirePlumber 0.4, there used to be a .conf file, typically wireplumber.conf, using the SPA-JSON format, that would list some Lua scripts in the wireplumber.components section. These scripts were of type config/lua and they were called by default main.lua, policy.lua and bluetooth.lua.

The system also supported fragments of these scripts to be placed in directories called main.lua.d, policy.lua.d and bluetooth.lua.d respectively, in the same locations.

:white_exclamation_mark:Attention
Starting with WirePlumber 0.5, Lua “configuration” files are no longer supported.

If you had custom Lua configuration scripts in the standard configuration directories, such as “main.lua.d”, “policy.lua.d” or “bluetooth.lua.d”, you need to port them.

Configuration files /home/diego/.config/wireplumber/main.lua.d/98-fix-internal-mic.lua and home/diego/.config/wireplumber/main.lua.d/99-disable-camera.lua should be either ported or deleted to avoid further errors

18

Thanks, I did that, but I still get the same error in the journal.

oct 18 19:33:05 manjaro plasmashell[7375]: pw.core: 0x55fe817d77c0: can’t find protocol ‘PipeWire:Protocol:Native’: Operation not supported
oct 18 19:33:05 manjaro plasmashell[7375]: kpipewire_logging: error: “Failed to connect to PipeWire” 0
oct 18 19:33:05 manjaro plasmashell[7375]: received error while creating the stream “Failed to connect to PipeWire” Media monitor will not work.
oct 18 19:33:10 manjaro plasmashell[7375]: pw.context: 0x55fe7684b280: no modules loaded from context.modules
oct 18 19:33:10 manjaro plasmashell[7375]: pw.core: 0x55fe817d77c0: can’t find protocol ‘PipeWire:Protocol:Native’: Operation not supported
oct 18 19:33:10 manjaro plasmashell[7375]: kpipewire_logging: error: “Failed to connect to PipeWire” 0
oct 18 19:33:10 manjaro plasmashell[7375]: received error while creating the stream “Failed to connect to PipeWire” Media monitor will not work.
oct 18 19:33:10 manjaro plasmashell[7375]: pw.context: 0x55fe7684b280: no modules loaded from context.modules
oct 18 19:33:10 manjaro plasmashell[7375]: pw.core: 0x55fe817d77c0: can’t find protocol ‘PipeWire:Protocol:Native’: Operation not supported
oct 18 19:33:10 manjaro plasmashell[7375]: kpipewire_logging: error: “Failed to connect to PipeWire” 0
oct 18 19:33:10 manjaro plasmashell[7375]: received error while creating the stream “Failed to connect to PipeWire” Media monitor will not work.

It’s very weird because sometimes when I restart my laptop, the desktop initializes perfectly (everything works fine, but the journal keeps showing the same message every second), and other times it starts with a black background. :frowning:

Maybe someone could guide me on how to completely uninstall everything related to PipeWire and reinstall PulseAudio instead.
I could ask ChatGPT, but I don’t want to mess something up or create conflicts if I don’t remove everything properly first.

I really don’t know what else to try anymore… I’m frustrated :frowning:

Thanks for your help!

19

Nope, just remove the extraneous ' from the end of the URL (caused by the lack of a space between the URL and the end quote).

20

PipeWire is a multimedia server (video and audio) and cannot be uninstalled completely on KDE.

Metapackage manjaro-pulse installs 3 packages to replace pipewire-pulse and pipewire-alsa that can also be installed discretely:

pamac install pulseaudio pulseaudio-alsa pulseaudio-bluetooth

But further intervention is likely to be needed to get PulseAudio working and stop error messages from kpipewire

Previous post suggests that switching audio servers will not prevent error messages from kpipewire and package cannot be removed

I suggest:

  1. Switch to testing branch

    sudo pacman-mirrors --api --set-branch

  2. Update system to get latest version of kpipewire (6.4.5-2)

  3. Check journal for kpipewire_logging errors

  4. If kpipewire errors persist, contact Matrix - KDE User Help or Help - KDE Discuss