Cairo fails to install on Linux Mint 22

[dagleykd]

Cairo now fails to install on Linux Mint 22 as Mint 22 now uses Pipewire rather than PulseAudio.

'cairo-dock-impulse-plug-in' requires Pulseaudio as a dependency.

Is there a way to remove this or make it separate so that Cairo can properly install under Pipewire-audio-based distros as Cairo will run perfectly without the impulse plugin?

[dkondor]

Hi, thank you for reporting! I'm aware of the issue, but the solution depends on how exactly are you trying to install cairo-dock:

• if installing from the Ubuntu repos (e.g. by using the package manager), you can just leave out cairo-dock-impulse-plug-in without any bad effects; you won't be able to install the cairo-dock package, but this is only a metapackage for convenience, you can get a working dock by manually install all other cairo-dock-* packages (although this is more cumbersome)
• you could try installing the beta version from our PPA: https://launchpad.net/~cairo-dock-team/+archive/ubuntu/weekly -- the impulse plugin here should be possible to install even if using pipewire (but feedback on this would be very much appreciated)
• if there is demand, I could also update the stable PPA (available here but not updated, since the same version is in the official repos)

[dagleykd]

Hi, thank you for reporting! I'm aware of the issue, but the solution depends on how exactly are you trying to install cairo-dock:

* if installing from the Ubuntu repos (e.g. by using the package manager), you can just leave out `cairo-dock-impulse-plug-in` without any bad effects; you won't be able to install the `cairo-dock` package, but this is only a metapackage for convenience, you can get a working dock by manually install all other `cairo-dock-*` packages (although this is more cumbersome)

* you could try installing the beta version from our PPA: https://launchpad.net/~cairo-dock-team/+archive/ubuntu/weekly -- the impulse plugin here should be possible to install even if using pipewire (but feedback on this would be very much appreciated)

* if there is demand, I could also update the stable PPA (available [here](https://launchpad.net/~cairo-dock-team/+archive/ubuntu/ppa) but not updated, since the same version is in the official repos)

Hi, thanks! The issues comes when trying to install the metapackage (I'm on Linux Mint 22 MATE). I did get it working by installing all the cairo-dock-* packages except impulse, as you suggested, but the issue there is that if I run 'sudo apt autoremove' to do some cleaning up, as I often do, it tries to autoremove all the cairo packages I've manually installed...? I'd assume because I didn't install them from the metapackage?

[dagleykd]

Hi, thank you for reporting! I'm aware of the issue, but the solution depends on how exactly are you trying to install cairo-dock:

* if installing from the Ubuntu repos (e.g. by using the package manager), you can just leave out `cairo-dock-impulse-plug-in` without any bad effects; you won't be able to install the `cairo-dock` package, but this is only a metapackage for convenience, you can get a working dock by manually install all other `cairo-dock-*` packages (although this is more cumbersome)

* you could try installing the beta version from our PPA: https://launchpad.net/~cairo-dock-team/+archive/ubuntu/weekly -- the impulse plugin here should be possible to install even if using pipewire (but feedback on this would be very much appreciated)

* if there is demand, I could also update the stable PPA (available [here](https://launchpad.net/~cairo-dock-team/+archive/ubuntu/ppa) but not updated, since the same version is in the official repos)

Hi, thanks! The issues comes when trying to install the metapackage (I'm on Linux Mint 22 MATE). I did get it working by installing all the cairo-dock-* packages except impulse, as you suggested, but the issue there is that if I run 'sudo apt autoremove' to do some cleaning up, as I often do, it tries to autoremove all the cairo packages I've manually installed...? I'd assume because I didn't install them from the metapackage?

Any news on this being solved? I use autoremove all the time to clean up my system, so having it remove Cairo every time I run autoremove and then having to reinstall Cairo would be a huge pain in the butt! :(

[dkondor]

Yes, definitely! I have the packages prepared, but want to do a bit more testing before publishing them. But you can expect them very soon :)

[dkondor]

Hi,

I've released version 3.5.1 which should fix this issue, including packages in our repo: https://launchpad.net/~cairo-dock-team/+archive/ubuntu/ppa

Please feel free to reopen if this is not resolved.

[AxeldeWater]

Do I understand correctly that this version has only been released in the ppa repo, or will it be updated on the Ubuntu repo too? Because at this moment it is still not possible to download that particular version in Linux Mint from the default repositories.

[dkondor]

Yes, it is only in the PPA repo -- that is directly maintained by us. The main Ubuntu repos typically follow the packages released in Debian which is maintained by their devs. So unfortunately it could take some time until the official repositories get updated.

[matttbe]

So unfortunately it could take some time until the official repositories get updated.

Because Cairo-Dock didn't get any new releases for a while, it might take some time for the Debian maintainers to realise there is an update. If you have the opportunity, do not hesitate to ping them, or directly propose an update via the "mentor" website. Especially here, because the watch file is still pointing to Launchpad (or also publish tarballs there?).

One last thing, because it is a switch from v3.4.1+git to v3.5.1, they might not understand the new version only contains fixes. For example, it might be needed to follow the SRU documentation to get an update in Ubuntu 24.04. I guess it should be easy to have this being accepted if this fix installation issues and crashes with newer versions :)

[dkondor]

Do note that there is already a bug in Debian asking to update the package (to 3.5.0 at that time, and probably only for testing): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063022 But there has been no activity for over half year, so I assume the package maintainers don't have the time to look into it.

[AxeldeWater]

I am not too familiar with the Debian bug reporting system, but i read that the severity is denoted with "wishlist" which doesn't equal the urgency for this update.

[matttbe]

I guess it means that if someone else is interested to maintain these packages, Debian devs will be glad to welcome this person as the new maintainer :)