On Thu, Feb 22, 2024 at 12:05:00PM -0700, Michael Nelson wrote:
>
> Might I suggest the following workflow for testing and production with
> PipeWire:
>
> 1. Open an xterm.
> 2. Run 'pipewire' in the foreground (which will tie up the xterm). E.g.
>
> $ pipewire
>
> (If it exits immediately, then we have a misconfiguration that needs
> to be resolved before we can continue further.)
I ran$ pipewire,
~$ pipewire
[E][10307.406897] mod.protocol-native | [module-protocol-: 731 lock_socket()] server 0x55897f87f4d0: unable to lock lockfile '/run/user/1000/pipewire-0.lock': Resource temporarily unavailable (maybe another daemon is running)
[E][10307.407152] pw.conf | [ conf.c: 594 load_module()] 0x55897f861c80: could not load mandatory module "libpipewire-module-protocol-native": Resource temporarily unavailable
[E][10307.407366] default | [ pipewire.c: 125 main()] failed to create context: Resource temporarily unavailable
C 17:25:34.688325 GLib (null):(null):(null): Failed to set scheduler settings: Operation not permitted
M 17:25:34.713476 wp-device ../lib/wp/device.c:619:wp_spa_device_new_from_spa_factory: SPA handle 'api.libcamera.enum.manager' could not be loaded; is it installed?
M 17:25:34.713499 script/libcamera libcamera.lua:168:chunk: PipeWire's libcamera SPA missing or broken. libcamera not supported.
M 17:25:35.988113 spa.bluez5 ../spa/plugins/bluez5/bluez5-dbus.c:3943:object_manager_handler: Trying to use legacy bluez5 API for LE Audio - only A2DP will be supported. Please upgrade bluez5.
W 17:25:35.994543 m-portal-permissio ../modules/module-portal-permissionstore.c:63:wp_portal_permissionstore_plugin_lookup: <WpPortalPermissionStorePlugin:0x5631a038f780> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
W 17:25:35.999047 m-portal-permissio ../modules/module-portal-permissionstore.c:63:wp_portal_permissionstore_plugin_lookup: <WpPortalPermissionStorePlugin:0x5631a038f780> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Pipewire neverthelews running (perhapos old session)
$ ps x | grep pipewire
3627 pts/15 S<l+ 0:00 pipewire
> Put this xterm aside and leave the pipewire process running in it for
> the duration of your X11 session.
If I just tried to start pipewire that was already running, then
cannot I close the initial term?
This works
$ aplay test.wav
The $ alsaplayer commannd works and opens to Pipewire card abd
chip. I find that $ aplay test.wav regardless of of whether I select
(default) or Default:0. I suppose that they are the same.
I can start audacious and play a CD
> > Yes, I dod, but I worry about the contant of the latter. What I have
> > in 20-pipewire-pulse.conf is:
> >
> > context.exec = [ { path = "/usr/bin/pipewire" args = "-c
> > pipewire-pulse.conf" } ]
> >
> > Is two lines legit here?
>
> This could be a problem! Try making the configuration one long line.
> (That's my bad--my silly editor wrapped the text...)
that I did at the start of this reply
> This is actually a GOOD sign. It means that the ALSA configuration for
> the default mixer is properly set to use PipeWire, but it can't because
> the pipewire process is not running.
>
> What you're looking
> at is your 'grep' process with an *argument* of 'pipewire'.
Yes, that is ovious. I must have been when I wrote it.
> Haines, I believe we're very close to getting this resolved, take heart.
So it seems. I will not kill the xterm in which I tried to open
pipewire. If that effort failed because pipewire was already runnig,
then killing this term shold make no differernce. Bit it did; can't
play audio. If I do $ playwire again, audio is restored.
So it seems ineed to execute playire when I log in to X server
(.fluxboxc/startup for example)
Do you think my problem resolved?
--
Haines Brown
::
Re: [DNG] ALSA: Host is down
