On Thu, Feb 22, 2024 at 06:00:36PM -0500, Haines Brown via Dng wrote:
> 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)

The presence of the lockfile indicates that pipewire is indeed already
running, yes.

> So it seems ineed to execute pipewire when I log in to X server
> (.fluxboxc/startup for example)

Yep, that sounds like a good idea.

> Do you think my problem resolved?

Sounds it. If I were you, I'd make the change to .fluxboxrc/startup and
then do a clean reboot to see if you still have audio. That way you
won't be confused when you *do* eventually reboot. (After a kernel
upgrade, for instance.)

Good hunting,