Cava module does not work or show up on Hyprland.

[SherLock707]

Adding cava module in config does not add it to waybar.

[manfred3000]

Without any logs whatsoever, a wild guess would be that the waybar package you've installed is built without cava support...

[SherLock707]

@manfred3000 I tried git version of waybar package and regular one from extra repo : Waybar 0.9.24-2

Where can I find waybar package built with cava?

[manfred3000]

I tried git version of waybar

Simply build it with -Dcava=enabled

[SherLock707]

Is there a package built with cava enabled for Arch?

[manfred3000]

You and Holmes don't have much in common, do you?

If you're using Arch Linux, do it the arch way - don't use AUR helpers until you've learned how to use makepkg. That being said, edit the PKGBUILD with the change mentioned above and rebuild waybar.

You haven't provided any logs yet, so we're still wild guessing what the actual issue might be so we're just eliminating one thing at a time...

[SherLock707]

Ah, @manfred3000 , your wisdom echoes through the Arch corridors. While I appreciate the counsel on the Arch way, sometimes a shortcut is just what the doctor ordered, even if it's not the "official" prescription.

As for makepkg, I assure you, I'm not dodging the learning curve; I'm simply savoring the convenience of a pre-packaged solution when it's readily available in the extra repo.

Now, let's set aside our detective banter for a moment and focus on the matter at hand. Here's the requested log:

[2023-12-30 15:15:36.431] [info] Using configuration file /home/###/.config/waybar/config [2023-12-30 15:15:36.431] [info] Including resource file: ~/.config/waybar/modules [2023-12-30 15:15:36.432] [info] Unable to receive desktop appearance: [2023-12-30 15:15:36.432] [info] Using CSS file /home/###/.config/waybar/style.css [2023-12-30 15:15:36.438] [warning] module cava: Unknown module: cava [2023-12-30 15:15:36.440] [info] Hyprland IPC starting

Even Holmes took a shortcut or two when the game was afoot!

I stumbled upon the cava module in the wiki. However, the mystery that perplexes me is why it's not enabled by default.

Could you shed some light on this choice?

[manfred3000]

[2023-12-30 15:15:36.438] [warning] module cava: Unknown module: cava

So yes, your build doesn't support cava

Could you shed some light on this choice?

Every Arch package provides a PKGBUILD, but the shortcuts you've taken so far lead you astray... ; )

[Zenith-the-realest]

[2023-12-30 15:15:36.438] [warning] module cava: Unknown module: cava

So yes, your build doesn't support cava

Could you shed some light on this choice?

Every Arch package provides a PKGBUILD, but the shortcuts you've taken so far lead you astray... ; )

I've also been trying to enable cava on my waybar - I have edited the PKGBUILD after cloning the git and enabling "Dcava", then building the package. Running waybar still says cava is an unknown module. Could you lend further support?

[manfred3000]

I've also been trying to enable cava on my waybar - I have edited the PKGBUILD after cloning the git and enabling "Dcava", then building the package. Running waybar still says cava is an unknown module. Could you lend further support?

This obviously isn't a waybar issue and shouldn't be discussed here...

[Zenith-the-realest]

I'm confused - how is it not a waybar issue when waybar doesn't recognise the module? Could you be a little less cryptic?

[khaneliman]

I'm confused - how is it not a waybar issue when waybar doesn't recognise the module? Could you be a little less cryptic?

Because the source code works, this is a packaging distribution issue.

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=waybar-git specifically disables cava in the PKGBUILD. You need to override that setting, I see there's a couple different Arch packages that pass -Dcava=enabled. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=waybar-cava looks like it does (as well as other modules)

[Zenith-the-realest]

I have overrided this setting already, and even used waybar-cava, yet cava still does not work.

[maxawake]

Why is it not build in natively anyways? I would really like to use the cava feature but also have the benefits or a AUR helper updating to lasted stable releases.

[LukashonakV]

Hi @Zenith-the-realest ,please provide

• waybar config
• waybar -l trace

---

@pepperonipizzah, please do the same

@maxawake , waybar itself provides a full list of functionalities, including cava. Then, each OS distribution team decides which functionality will be provided in theirs package managers. Arch distribution team decided not to turn on cava by default . The reason is that libcava itself is a fork of cava applications and is not distributed by the cava application owner. I had a try to have an agreement with @karlstav and even provided necessary PR to repackage the cava application as a shared library. But he was aware of such massive changes and proposed to do the fork, which actually is done.

[jd-becerra]

I'm confused - how is it not a waybar issue when waybar doesn't recognise the module? Could you be a little less cryptic?

Because the source code works, this is a packaging distribution issue.

https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=waybar-git specifically disables cava in the PKGBUILD. You need to override that setting, I see there's a couple different Arch packages that pass -Dcava=enabled. https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=waybar-cava looks like it does (as well as other modules)

Hello, I want to add that the version you provide of the waybar-cava package has an error when building because it doesn't recognize the command "gdbus-codegen" on Arch, easily fixed by installig the "glib2-devel" package. The same is needed if you want to build Waybar from the official Github repository. Just mentioning this for anyone that wants to build it as well

[wolf-yuan-6115]

https://gitlab.archlinux.org/archlinux/packaging/packages/waybar/-/blob/main/PKGBUILD?ref_type=heads#L80

Waybar in extra repo explicitly disabled cava using -Dcava=disabled. But since I don't have an Arch GitLab account, can someone try to open an issue on their GitLab?