Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pipewire Restarts Upon HDMI TV Activation on Bookworm #5951

Closed
mghadam opened this issue Feb 13, 2024 · 7 comments
Closed

Pipewire Restarts Upon HDMI TV Activation on Bookworm #5951

mghadam opened this issue Feb 13, 2024 · 7 comments

Comments

@mghadam
Copy link

mghadam commented Feb 13, 2024

Describe the bug

When using the microphone on Google Meet or another meeting platform on Bookworm, if an HDMI device like a TV is turned off/on, PulseWire restarts, causing the microphone/speaker in use to become unavailable. This issue does not occur when using PulseAudio.

Steps to reproduce the behaviour

  1. Open a meeting in Google Meet or Jitsi that utilizes the speakers/microphone connected to a Raspberry Pi.
  2. Turn off/on the TV that is connected to the Raspberry Pi.
  3. After switching the TV back on, the microphone/speaker device becomes unavailable in the meeting platform.

Device (s)

Raspberry Pi 4 Mod. B

System

Raspberry Pi reference 2023-12-05
Generated using pi-gen, https://github.com/RPi-Distro/pi-gen, 70cd6f2a1e34d07f5cba7047aea5b92457372e05, stage5

version 30f0c5e4d076da3ab4f341d88e7d505760b93ad7 (clean) (release) (start)

Linux home.domain.local 6.1.0-rpi8-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux

Logs

Feb 13 08:07:43 home.domain.local sh[963]: Warning: ../src/main.c: 319: Selected output HDMI-A-1 went away
Feb 13 08:07:43 home.domain.local sh[963]: Warning: ../src/main.c: 330: No fallback outputs left. Detaching...
Feb 13 08:07:44 home.domain.local xdg-desktop-portal-wlr[14124]: 2024/02/13 08:07:44 [ERROR] - pipewire: fatal error event from core
Feb 13 08:07:44 home.domain.local xdg-desktop-por[2654]: Caught PipeWire error: connection error
Feb 13 08:07:44 home.domain.local systemd[1304]: Stopping pipewire.service - PipeWire Multimedia Service...
Feb 13 08:07:44 home.domain.local systemd[1304]: Stopped pipewire.service - PipeWire Multimedia Service.
Feb 13 08:07:44 home.domain.local systemd[1304]: xdg-desktop-portal-wlr.service: Main process exited, code=exited, status=1/FAILURE
Feb 13 08:07:44 home.domain.local systemd[1304]: xdg-desktop-portal-wlr.service: Failed with result 'exit-code'.
Feb 13 08:07:44 home.domain.local systemd[1304]: Started pipewire.service - PipeWire Multimedia Service.
Feb 13 08:07:44 home.domain.local systemd[1304]: xdg-desktop-portal-wlr.service: Scheduled restart job, restart counter is at 5.
Feb 13 08:07:44 home.domain.local systemd[1304]: Stopped xdg-desktop-portal-wlr.service - Portal service (wlroots implementation).
Feb 13 08:07:44 home.domain.local systemd[1304]: Starting xdg-desktop-portal-wlr.service - Portal service (wlroots implementation)...
Feb 13 08:07:44 home.domain.local rtkit-daemon[1579]: Successfully made thread 16143 of process 16137 owned by '1000' high priority at nice level -11.
Feb 13 08:07:44 home.domain.local rtkit-daemon[1579]: Supervising 4 threads of 2 processes of 1 users.
Feb 13 08:07:44 home.domain.local xdg-desktop-portal-wlr[16152]: 2024/02/13 08:07:44 [ERROR] - xdpw: Could not find render node
Feb 13 08:07:44 home.domain.local xdg-desktop-portal-wlr[16152]: 2024/02/13 08:07:44 [ERROR] - xdpw: Could not find render node
Feb 13 08:07:45 home.domain.local rtkit-daemon[1579]: Successfully made thread 16144 of process 16137 owned by '1000' RT at priority 20.
Feb 13 08:07:45 home.domain.local rtkit-daemon[1579]: Supervising 5 threads of 2 processes of 1 users.
Feb 13 08:07:45 home.domain.local systemd[1304]: Started xdg-desktop-portal-wlr.service - Portal service (wlroots implementation).
Feb 13 08:07:45 home.domain.local systemd[1304]: Stopping pipewire.service - PipeWire Multimedia Service...
Feb 13 08:07:45 home.domain.local xdg-desktop-por[2654]: Caught PipeWire error: connection error
Feb 13 08:07:45 home.domain.local xdg-desktop-portal-wlr[16152]: 2024/02/13 08:07:45 [ERROR] - pipewire: fatal error event from core
Feb 13 08:07:45 home.domain.local systemd[1304]: Stopped pipewire.service - PipeWire Multimedia Service.
Feb 13 08:07:45 home.domain.local systemd[1304]: xdg-desktop-portal-wlr.service: Main process exited, code=exited, status=1/FAILURE
Feb 13 08:07:45 home.domain.local systemd[1304]: xdg-desktop-portal-wlr.service: Failed with result 'exit-code'.
Feb 13 08:07:46 home.domain.local systemd[1304]: Started pipewire.service - PipeWire Multimedia Service.
Feb 13 08:07:46 home.domain.local systemd[1304]: xdg-desktop-portal-wlr.service: Scheduled restart job, restart counter is at 6.
Feb 13 08:07:46 home.domain.local systemd[1304]: Stopped xdg-desktop-portal-wlr.service - Portal service (wlroots implementation).
Feb 13 08:07:46 home.domain.local systemd[1304]: Starting xdg-desktop-portal-wlr.service - Portal service (wlroots implementation)...
Feb 13 08:07:46 home.domain.local xdg-desktop-portal-wlr[16179]: 2024/02/13 08:07:46 [ERROR] - xdpw: Could not find render node
Feb 13 08:07:46 home.domain.local xdg-desktop-portal-wlr[16179]: 2024/02/13 08:07:46 [ERROR] - xdpw: Could not find render node

Additional context

No response

@mghadam mghadam changed the title Pipewire restarts when hdmi tv is turned on Pipewire Restarts Upon HDMI TV Activation on Bookworm Feb 13, 2024
@apassu
Copy link

apassu commented Feb 14, 2024

I have a very similar problem with quite the same logs.
I have a RPI 4 with an external HDMI monitor (with Alexa builts in the monitor) and when Alexa activates itself there is a crash of pipewire/wireplumber.

SYSTEMS INFO:

Raspberry PI 4
Raspbian 12 (bookworm)
Linux rpi 6.1.0-rpi8-rpi-v8 #1 SMP PREEMPT Debian 1:6.1.73-1+rpt1 (2024-01-25) aarch64 GNU/Linux
HDMI Monitor Samsung Smart Monitor M7 43" (with Alexa built in)

Steps to reproduce the behaviour
The monitor has Alexa built in and when it activates itself there is a crash of pipewire/wireplumber.

LOGS:

2024-02-14T14:13:51.581663+01:00 rpi sh[4488]: Warning: ../src/main.c: 319: Selected output HDMI-A-1 went away
2024-02-14T14:13:51.585451+01:00 rpi sh[4488]: Warning: ../src/main.c: 330: No fallback outputs left. Detaching...
2024-02-14T14:13:52.479597+01:00 rpi wireplumber[5848]: stopped by signal: Terminated
2024-02-14T14:13:52.485894+01:00 rpi systemd[1750]: Stopping wireplumber.service - Multimedia Service Session Manager...
2024-02-14T14:13:52.537204+01:00 rpi wireplumber[5848]: disconnected from pipewire
2024-02-14T14:13:52.574138+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/ldac
2024-02-14T14:13:52.575006+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSink/aptx_hd
2024-02-14T14:13:52.576500+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/aptx_hd
2024-02-14T14:13:52.577591+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSink/aptx
2024-02-14T14:13:52.578691+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/aptx
2024-02-14T14:13:52.580101+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSink/sbc
2024-02-14T14:13:52.581530+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/sbc
2024-02-14T14:13:52.582848+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSink/sbc_xq
2024-02-14T14:13:52.584948+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/sbc_xq
2024-02-14T14:13:52.586777+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/aptx_ll_1
2024-02-14T14:13:52.588349+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/aptx_ll_0
2024-02-14T14:13:52.589798+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
2024-02-14T14:13:52.591290+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
2024-02-14T14:13:52.594042+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/faststream
2024-02-14T14:13:52.596998+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/faststream_duplex
2024-02-14T14:13:52.600100+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSink/opus_05
2024-02-14T14:13:52.601406+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/opus_05
2024-02-14T14:13:52.603212+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSink/opus_05_duplex
2024-02-14T14:13:52.603778+01:00 rpi systemd[1750]: Stopped wireplumber.service - Multimedia Service Session Manager.
2024-02-14T14:13:52.604164+01:00 rpi systemd[1750]: wireplumber.service: Consumed 1.551s CPU time.
2024-02-14T14:13:52.605368+01:00 rpi bluetoothd[911]: Endpoint unregistered: sender=:1.92 path=/MediaEndpoint/A2DPSource/opus_05_duplex
2024-02-14T14:13:52.609849+01:00 rpi systemd[1750]: Stopping pipewire.service - PipeWire Multimedia Service...
2024-02-14T14:13:52.637246+01:00 rpi xdg-desktop-portal-wlr[5866]: 2024/02/14 14:13:52 [ERROR] - pipewire: fatal error event from core
2024-02-14T14:13:52.638465+01:00 rpi xdg-desktop-por[2270]: Caught PipeWire error: connection error
2024-02-14T14:13:52.651400+01:00 rpi systemd[1750]: Stopped pipewire.service - PipeWire Multimedia Service.
2024-02-14T14:13:52.651914+01:00 rpi systemd[1750]: pipewire.service: Consumed 2.980s CPU time.
2024-02-14T14:13:52.685947+01:00 rpi systemd[1750]: Started pipewire.service - PipeWire Multimedia Service.
2024-02-14T14:13:52.692411+01:00 rpi systemd[1750]: Started wireplumber.service - Multimedia Service Session Manager.
2024-02-14T14:13:52.693201+01:00 rpi systemd[1750]: xdg-desktop-portal-wlr.service: Main process exited, code=exited, status=1/FAILURE
2024-02-14T14:13:52.693686+01:00 rpi systemd[1750]: xdg-desktop-portal-wlr.service: Failed with result 'exit-code'.
2024-02-14T14:13:52.880896+01:00 rpi systemd[1750]: xdg-desktop-portal-wlr.service: Scheduled restart job, restart counter is at 22.
2024-02-14T14:13:52.881560+01:00 rpi systemd[1750]: Stopped xdg-desktop-portal-wlr.service - Portal service (wlroots implementation).
2024-02-14T14:13:52.913039+01:00 rpi rtkit-daemon[1336]: Successfully made thread 5946 of process 5938 owned by '1000' high priority at nice level -11.
2024-02-14T14:13:52.914130+01:00 rpi rtkit-daemon[1336]: Supervising 1 threads of 1 processes of 1 users.
2024-02-14T14:13:52.914730+01:00 rpi systemd[1750]: Starting xdg-desktop-portal-wlr.service - Portal service (wlroots implementation)...
2024-02-14T14:13:52.935441+01:00 rpi sh[4488]: Warning: ../src/main.c: 319: Selected output NOOP-1 went away
2024-02-14T14:13:52.967394+01:00 rpi rtkit-daemon[1336]: Successfully made thread 5947 of process 5942 owned by '1000' high priority at nice level -11.
2024-02-14T14:13:52.968354+01:00 rpi rtkit-daemon[1336]: Supervising 2 threads of 2 processes of 1 users.
2024-02-14T14:13:52.979169+01:00 rpi xdg-desktop-portal-wlr[5958]: 2024/02/14 14:13:52 [ERROR] - xdpw: Could not find render node
2024-02-14T14:13:52.980339+01:00 rpi xdg-desktop-portal-wlr[5958]: 2024/02/14 14:13:52 [ERROR] - xdpw: Could not find render node
2024-02-14T14:13:53.017015+01:00 rpi rtkit-daemon[1336]: Successfully made thread 5950 of process 5938 owned by '1000' RT at priority 20.
2024-02-14T14:13:53.017898+01:00 rpi rtkit-daemon[1336]: Supervising 3 threads of 2 processes of 1 users.
2024-02-14T14:13:53.075491+01:00 rpi rtkit-daemon[1336]: Successfully made thread 5948 of process 5942 owned by '1000' RT at priority 20.
2024-02-14T14:13:53.076219+01:00 rpi rtkit-daemon[1336]: Supervising 4 threads of 2 processes of 1 users.
2024-02-14T14:13:53.161644+01:00 rpi systemd[1750]: Started xdg-desktop-portal-wlr.service - Portal service (wlroots implementation).
2024-02-14T14:13:53.203937+01:00 rpi kernel: [17287.577184] vc4-drm gpu: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 7184 (slots)
2024-02-14T14:13:53.341349+01:00 rpi wireplumber[5942]: [4:48:07.398713203] [5942] #33[1;32m INFO #33[1;37mCamera #33[1;34mcamera_manager.cpp:284 #33[0mlibcamera v0.1.0+118-563cd78e
2024-02-14T14:13:53.347852+01:00 rpi kernel: [17287.724462] vc4-drm gpu: swiotlb buffer is full (sz: 524288 bytes), total 32768 (slots), used 7184 (slots)
2024-02-14T14:13:53.547171+01:00 rpi systemd[1750]: Stopping wireplumber.service - Multimedia Service Session Manager...
2024-02-14T14:13:54.554553+01:00 rpi wireplumber[5942]: stopped by signal: Terminated
2024-02-14T14:13:54.566114+01:00 rpi wireplumber[5942]: WpImplMetadata:0x55976ba3f0 Object activation aborted: PipeWire proxy destroyed
2024-02-14T14:13:54.569245+01:00 rpi wireplumber[5942]: failed to activate route-settings metadata: Object activation aborted: PipeWire proxy destroyed
2024-02-14T14:13:54.575536+01:00 rpi wireplumber[5942]: disconnected from pipewire
2024-02-14T14:13:54.625579+01:00 rpi systemd[1750]: Stopped wireplumber.service - Multimedia Service Session Manager.
2024-02-14T14:13:54.627562+01:00 rpi systemd[1750]: wireplumber.service: Consumed 1.398s CPU time.
2024-02-14T14:13:54.632763+01:00 rpi systemd[1750]: Stopping pipewire.service - PipeWire Multimedia Service...
2024-02-14T14:13:54.643623+01:00 rpi xdg-desktop-portal-wlr[5958]: 2024/02/14 14:13:54 [ERROR] - pipewire: fatal error event from core
2024-02-14T14:13:54.647259+01:00 rpi xdg-desktop-por[2270]: Caught PipeWire error: connection error
2024-02-14T14:13:54.662883+01:00 rpi systemd[1750]: Stopped pipewire.service - PipeWire Multimedia Service.
2024-02-14T14:13:54.715623+01:00 rpi systemd[1750]: Started pipewire.service - PipeWire Multimedia Service.
2024-02-14T14:13:54.728564+01:00 rpi systemd[1750]: Started wireplumber.service - Multimedia Service Session Manager.
2024-02-14T14:13:54.732058+01:00 rpi systemd[1750]: xdg-desktop-portal-wlr.service: Main process exited, code=exited, status=1/FAILURE
2024-02-14T14:13:54.733715+01:00 rpi systemd[1750]: xdg-desktop-portal-wlr.service: Failed with result 'exit-code'.
2024-02-14T14:13:54.882785+01:00 rpi systemd[1750]: xdg-desktop-portal-wlr.service: Scheduled restart job, restart counter is at 23.
2024-02-14T14:13:54.885922+01:00 rpi systemd[1750]: Stopped xdg-desktop-portal-wlr.service - Portal service (wlroots implementation).
2024-02-14T14:13:54.931824+01:00 rpi systemd[1750]: Starting xdg-desktop-portal-wlr.service - Portal service (wlroots implementation)...
2024-02-14T14:13:54.940390+01:00 rpi rtkit-daemon[1336]: Successfully made thread 5987 of process 5981 owned by '1000' high priority at nice level -11.
2024-02-14T14:13:54.941011+01:00 rpi rtkit-daemon[1336]: Supervising 1 threads of 1 processes of 1 users.
2024-02-14T14:13:55.023238+01:00 rpi rtkit-daemon[1336]: Successfully made thread 5986 of process 5976 owned by '1000' high priority at nice level -11.
2024-02-14T14:13:55.024609+01:00 rpi rtkit-daemon[1336]: Supervising 2 threads of 2 processes of 1 users.
2024-02-14T14:13:55.034922+01:00 rpi xdg-desktop-portal-wlr[6000]: 2024/02/14 14:13:55 [ERROR] - xdpw: Could not find render node
2024-02-14T14:13:55.036145+01:00 rpi xdg-desktop-portal-wlr[6000]: 2024/02/14 14:13:55 [ERROR] - xdpw: Could not find render node
2024-02-14T14:13:55.108915+01:00 rpi rtkit-daemon[1336]: Successfully made thread 5988 of process 5981 owned by '1000' RT at priority 20.
2024-02-14T14:13:55.110125+01:00 rpi rtkit-daemon[1336]: Supervising 3 threads of 2 processes of 1 users.
2024-02-14T14:13:55.204189+01:00 rpi rtkit-daemon[1336]: Successfully made thread 5989 of process 5976 owned by '1000' RT at priority 20.
2024-02-14T14:13:55.205438+01:00 rpi rtkit-daemon[1336]: Supervising 4 threads of 2 processes of 1 users.
2024-02-14T14:13:55.261598+01:00 rpi systemd[1750]: Started xdg-desktop-portal-wlr.service - Portal service (wlroots implementation).
2024-02-14T14:13:55.485171+01:00 rpi wireplumber[5981]: [4:48:09.544493784] [5981] #33[1;32m INFO #33[1;37mCamera #33[1;34mcamera_manager.cpp:284 #33[0mlibcamera v0.1.0+118-563cd78e
2024-02-14T14:13:56.465094+01:00 rpi wireplumber[5981]: Trying to use legacy bluez5 API for LE Audio - only A2DP will be supported. Please upgrade bluez5.
2024-02-14T14:13:56.500484+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/ldac
2024-02-14T14:13:56.501811+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/aptx_hd
2024-02-14T14:13:56.502440+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aptx_hd
2024-02-14T14:13:56.503315+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/aptx
2024-02-14T14:13:56.504046+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aptx
2024-02-14T14:13:56.506558+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/sbc
2024-02-14T14:13:56.507318+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/sbc
2024-02-14T14:13:56.507910+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/sbc_xq
2024-02-14T14:13:56.508415+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/sbc_xq
2024-02-14T14:13:56.508892+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aptx_ll_1
2024-02-14T14:13:56.509357+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aptx_ll_0
2024-02-14T14:13:56.509850+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_1
2024-02-14T14:13:56.510521+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/aptx_ll_duplex_0
2024-02-14T14:13:56.510963+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/faststream
2024-02-14T14:13:56.511445+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/faststream_duplex
2024-02-14T14:13:56.515440+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/opus_05
2024-02-14T14:13:56.516684+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/opus_05
2024-02-14T14:13:56.517647+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/opus_05_duplex
2024-02-14T14:13:56.518481+01:00 rpi bluetoothd[911]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/opus_05_duplex
2024-02-14T14:13:56.522852+01:00 rpi wireplumber[5981]: WpPortalPermissionStorePlugin:0x55948fa8d0 Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
2024-02-14T14:13:56.587168+01:00 rpi pipewire[5976]: spa.v4l2: '/dev/video14' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
2024-02-14T14:13:56.587832+01:00 rpi pipewire[5976]: spa.v4l2: '/dev/video15' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
2024-02-14T14:13:56.588360+01:00 rpi pipewire[5976]: spa.v4l2: '/dev/video21' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
2024-02-14T14:13:56.588743+01:00 rpi pipewire[5976]: spa.v4l2: '/dev/video22' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
2024-02-14T14:13:56.674206+01:00 rpi pipewire[5976]: spa.v4l2: '/dev/video14' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
2024-02-14T14:13:56.674863+01:00 rpi pipewire[5976]: spa.v4l2: '/dev/video15' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
2024-02-14T14:13:56.675387+01:00 rpi pipewire[5976]: spa.v4l2: '/dev/video21' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
2024-02-14T14:13:56.675888+01:00 rpi pipewire[5976]: spa.v4l2: '/dev/video22' VIDIOC_ENUM_FRAMEINTERVALS: Inappropriate ioctl for device
2024-02-14T14:13:56.708663+01:00 rpi wireplumber[5981]: WpPortalPermissionStorePlugin:0x55948fa8d0 Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
2024-02-14T14:13:56.723855+01:00 rpi wireplumber[5981]: WpPortalPermissionStorePlugin:0x55948fa8d0 Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
2024-02-14T14:13:56.734403+01:00 rpi wireplumber[5981]: WpPortalPermissionStorePlugin:0x55948fa8d0 Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
2024-02-14T14:13:56.742703+01:00 rpi wireplumber[5981]: WpPortalPermissionStorePlugin:0x55948fa8d0 Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
2024-02-14T14:14:02.708043+01:00 rpi bluetoothd[911]: src/profile.c:record_cb() Unable to get Hands-Free Voice gateway SDP record: Host is down

@popcornmix
Copy link
Collaborator

We're investigating something related to this (USB or bluetooth audio may be killed on HDMI hotplug event).
Does:

pkill respawn
pkill wf-panel-pi

stop the unwanted behaviour? (note this is a test rather than a fix - it will kill the wf-panel).
wf-panel-pi does a systemctl --user restart wireplumber.service on a hotplug event, to get the list of hdmi audio devices updated, but that is obviously having an unwanted side effect. We're looking into a way to get wireplumber/pipewire to reenumerate the hdmi audio devices without affecting other devices.

@apassu
Copy link

apassu commented Feb 15, 2024

I tried your commands, the first one is ok but when I launched the second the RPI freezes and became unresponsive.

@mghadam
Copy link
Author

mghadam commented Feb 16, 2024

a similar issue is reported here
raspberrypi/bookworm-feedback#205

@pelwell
Copy link
Contributor

pelwell commented Feb 16, 2024

Yes - as with #5950, this is not a kernel problem. Follow the other issue instead.

@pelwell pelwell closed this as not planned Won't fix, can't repro, duplicate, stale Feb 16, 2024
@apassu
Copy link

apassu commented Feb 17, 2024

Yes - as with #5950, this is not a kernel problem. Follow the other issue instead.

Which one to follow?

@pelwell
Copy link
Contributor

pelwell commented Feb 17, 2024

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants