Thank you for a fast reply.
On 14.06.23 18:06, Dylan Aïssi wrote:
What is the actual error you are facing?
If you wish to know which problems the computer has, then there are
some, which may or may not be related. For example, gnome now started
using X11 instead of Wayland on my machine after the upgrade of Debian
stable from v11 to v12. Further, I failed to set up any television
application and to watch TV in Linux using a PCIe DVB tuner card so far.
Moreover, audacity sometimes failed to record voice at proper speed (and
sometimes succeeded). Finally, the machine had WiFi problems of various
kinds (first connection took long after boot and connection got dropped
long after boot). Though these problems do not look as if they were
related to a camera or video recording at a first glance or directly,
there are tons of error/failure/warning/missing/“cannot” messages in the
log, and I start processing them beginning with the earlier ones so as
to avoid considering followup errors (because later issues sometimes
disappear after earlier issues get resolved).
"PipeWire's libcamera SPA missing or broken. libcamera not supported" is only
a log message (not even a warning) saying indeed the plugin provided by
pipewire-libcamera is not installed. SPA is for "Simple Plugin API" is the
pipewire's plugin API. If you don't know what is libcamera then you
probably don't need to install pipewire-libcamera. I can add it in suggested
package of wireplumber though, but again this is not an error only a log
message.
Got it, thank you a lot! If you do think that pipewire-libcamera is
indeed related, please feel free to add it as a suggested package. On my
machine, the messages
SPA handle 'api.libcamera.enum.manager' could not be loaded; is it
installed?
PipeWire's libcamera SPA missing or broken. libcamera not supported.
are not normally displayed but bold or semi-bold. Moreover, they follow
a yellow-colored
Failed to set scheduler settings: Operation not permitted.
(in my case, the part after the colon is “Die Operation ist nicht
erlaubt” in German). See the attached screenshot. I thought,
hypothetically, these three messages might be related.
Unfortunately, the manpage of journalctl doesn't explicitly say what
yellow and (semi-)bold emphasis mean; instead we only see a generic term
“highlighted” (which may or may not refer to yellow, (semi-)bold, and
blue). So I didn't really know whether the two (semi-)bold messages
were really good or bad (and if they were bad, how bad). Probably, the
programmers wanted the reader to notice such emphasized messages.
However, when I noticed them, I didn't really know how bad it was and
what to do next.
Gratefully,
AlMa
