libcamera: update to 0.7.0; pipewire: update to 1.6.2; wireplumber: update to 0.5.13

[Rutpiv]

Testing the changes

• I tested the changes in this PR: briefly

Local build testing

• I built this PR locally for my native architecture (x86_64)
• I built this PR locally for these architectures using specific masterdirs:
  • x86_64-musl
  • i686
• I built this PR locally for these architectures (crossbuilds):
  • aarch64
  • aarch64-musl
  • armv7l
  • armv7l-musl
  • armv6l
  • armv6l-musl

[oreo639]

Btw, there are reports that wireplumber 0.5.13 causes crashes with libgnome-volume-control.
https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/890
https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/merge_requests/31

I'll investigate when I have the time.

[Rutpiv]

Thanks for the heads-up.

I will take a look at the wireplumber 0.5.13 issue with libgnome-volume-control as well and report back if I find anything relevant.

Also, it seems libcamera has been updated again upstream. I’ll check the new release and update the PR accordingly if needed.

In the meantime, I’ll temporarily convert this PR to draft and mark it as WIP. Once we have a proper solution or clearer direction regarding the wireplumber issue, I’ll move it back to a normal PR.

[Rutpiv]

After investigating the wireplumber 0.5.13 crash reports, it turns out the fix is already present upstream in libgnome-volume-control (gvc) and has landed in the master branches of gnome-shell and gnome-control-center, but not yet in a stable GNOME release.

Since gvc is vendored in both components, updating only parts of the stack could lead to inconsistent behavior or require temporary backports that will soon become obsolete.

Given that wireplumber/pipewire/libcamera updates are not urgent for Void at the moment, I suggest waiting for the next coordinated GNOME stable release that includes the updated vendored gvc, updating the GNOME stack as a whole, and then proceeding with this PR.

This is even more relevant considering Void is still on the GNOME 48.x stack, while upstream is already at 49.x and GNOME 50 is currently in beta. It seems more appropriate to handle this as part of the next coordinated GNOME stack update rather than carrying a short-lived backport.

This approach avoids temporary backports and keeps the GNOME stack consistent. That said, this is just a suggestion on how we could proceed. I’m open to other approaches if you think a different solution would be more appropriate.

[Jaymz665]

At the same time, I have VoidLinux and phosh on my smartphone, apparently 5.12 has a problem that has been fixed here. https://codetest.hyprland.org/fdo-mirrors/wireplumber/commit/278541f637a12536f66b15acbeac5fadeb13dab3 I think I'll check it out.

[Jaymz665]

At the same time, I have VoidLinux and phosh on my smartphone, apparently 5.12 has a problem that has been fixed here. https://codetest.hyprland.org/fdo-mirrors/wireplumber/commit/278541f637a12536f66b15acbeac5fadeb13dab3 I think I'll check it out.

Unfortunately, this did not fix my problem. But it didn't bring any new problems.

[oreo639]

Hello, sorry for the long delay, I got super busy.

The gnome issue should be fixed now:
70c90a8
d21b994

[Rutpiv]

Thanks for the update and for addressing the GNOME side of the issue.

I saw the changes bringing the fixed gvc version into the templates, which makes sense given the vendored copies situation.

I was a bit short on time recently (work and exam week), but I'm now testing the new libcamera release locally. Next step will be updating pipewire, which is the last remaining piece of this PR.

Once that's done I'll push the changes and run another round of tests.

[Rutpiv]

Unfortunately, this did not fix my problem. But it didn't bring any new problems.

Thanks for testing and reporting back.

It might be worth checking again once the updated stack from this PR lands. I'm currently testing a newer libcamera release and will update pipewire next, so it would be interesting to see if the issue you're seeing with wireplumber on Phosh is still present with the newer versions.

[Rutpiv]

Update:

Tested locally, everything looks fine.

Rebuilt for all architectures mentioned in the PR description, all builds completed successfully.

Removing [WIP] and marking this PR as ready for review.