I think we definitely should, I've just not gotten around to actually open one yet. There is also the question of which project is actually at fault here. After a bit of digging I have not yet figured out where this would best get fixed. We could file it against libcamera/pipewire I guess.
As I mentioned in report itself I think the proper fix would be monitoring the /dev nodes for ownership changes and updating automatically. I think the problem with the current code structure is that wireplumber loads the pipewire-libcamera plugin, which defers all logic to libcamera. Neither pipewire nor wireplumber are actually aware of the /dev node access since that happens transparently in the library, meanwhile libcamera doesn't really seem to have a mechanism to monitor changes because how would it as a library. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2122049 Title: wireplumber starts before camera is user accessible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-x13s-settings/+bug/2122049/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
