Swayfx and scenefx are in conflict. Remove scenefx?

BluishHumility · 15 June 2025 02:48

Sway users will see a package replacement prompt when next updating:

:: swayfx-0.5.1-3.3 and scenefx-0.2.1-4 are in conflict. Remove scenefx? [y/N]

TL;DR

Yes, respond “y” to the prompt and remove the scenefx package.

What happened?

In the aftermath of the wlroots package maintainers deciding to switch to a versioned packaging scheme, the SceneFX project (a dependency of SwayFX which replaces the wlroots scene API) has ended up going to a versioned package scheme as well. See this related issue:

github.com/wlrfx/scenefx

installing scenefx (0.3-1) breaks dependency 'libscenefx-0.2.so=libscenefx-0.2.so-64' required by swayfx

opened 08:14AM - 09 Jun 25 UTC

closed 03:32AM - 13 Jun 25 UTC

martinstark

(unsure if posting this here or in the swayfx repo is more appropriate) This is… the third time in a fairly short period where scenefx/swayfx breaks their own dependency chains while doing a full system upgrade (I'm not ungrateful, thank you for your awesome work maintaining this, I just wanted to make it clear that this seems to be a reoccurring issue): ![Image](https://github.com/user-attachments/assets/8146a4ff-3e2c-4925-ae12-9c61d624f408) Wanted to drop this here in case more people run into it... I haven't had time to look at a solution yet, suggestions welcome. I guess uninstalling and reinstalling is the solution this time as well. Trying to install `swayfx` on its own: ```bash paru swayfx 4 aur/swayfx-nvidia 1.0.8-1 [+0 ~0.00] Helper files to make swayfx a better experience for us poor NVIDIA users. 3 aur/swayfx-i3-style-fullscreen-git r7079.9fee0ce0-2 [+1 ~0.87] SwayFX: Sway, but with eye candy! 2 aur/swayfx-git r7069.03a07969-2 [+4 ~0.01] SwayFX: Sway, but with eye candy! 1 aur/swayfx 0.5.1-1 [+36 ~4.06] [Installed: 0.5-1] SwayFX: Sway, but with eye candy! :: Packages to install (eg: 1 2 3, 1-3): 1 :: Resolving dependencies... :: Calculating conflicts... :: Calculating inner conflicts... Aur (2) scenefx-0.3-1 swayfx-0.5.1-1 :: Proceed to review? [Y/n]: Y :: Downloading PKGBUILDs... PKGBUILDs up to date nothing new to review fetching devel info... ==> Making package: scenefx 0.3-1 (mån 9 jun 2025 10:15:40) ==> Retrieving sources... -> Found scenefx-0.3.tar.gz ==> Validating source files with sha512sums... scenefx-0.3.tar.gz ... Skipped ==> Making package: scenefx 0.3-1 (mån 9 jun 2025 10:15:41) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found scenefx-0.3.tar.gz ==> Validating source files with sha512sums... scenefx-0.3.tar.gz ... Skipped ==> Removing existing $srcdir/ directory... ==> Extracting sources... -> Extracting scenefx-0.3.tar.gz with bsdtar ==> Sources are ready. scenefx-0.3-1: parsing pkg list... :: scenefx-0.3-1 is up to date -- skipping build loading packages... resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: installing scenefx (0.3-1) breaks dependency 'libscenefx-0.2.so=libscenefx-0.2.so-64' required by swayfx loading packages... resolving dependencies... looking for conflicting packages... error: failed to prepare transaction (could not satisfy dependencies) :: installing scenefx (0.3-1) breaks dependency 'libscenefx-0.2.so=libscenefx-0.2.so-64' required by swayfx error: packages failed to build: swayfx-0.5.1-1 ``` Ref 1: https://github.com/WillPower3309/swayfx/issues/384 Ref 2: https://github.com/wlrfx/scenefx/issues/121

Unfortunately, this solution does not work well for our implementation of SwayFX because when the dependency changes to a new package that doesn’t exist in any repo (the new packages are only added to the AUR), Pacman can’t reconcile the dependency and the automated build routine fails over and over until some kind of intervention occurs.

To resolve this issue, scenefx will now be statically linked to the Chaotic repo version of swayfx. feat(swayfx): update interfere, static link scenefx · chaotic-aur/packages@d6c9ff9 · GitHub. In other words, scenefx will be effectively bundled with the Chaotic version of the swayfx package when it is built (using whatever version of scenefx and related libraries that happen to be required at the time).

Since we don’t need to pull it in separately anymore, the scenefx package has been dropped from the Chaotic repo and should be uninstalled when updating to the new version of swayfx.

gabegie · 15 June 2025 09:55

 update
:: Synchronisation des bases de données de paquets…
 garuda est à jour
 core est à jour
 extra est à jour
 multilib est à jour
 chaotic-aur est à jour

--> Refreshing mirrorlists using rate-mirrors, please be patient..🍵

:: Synchronisation des bases de données de paquets…
téléchargement de garuda…
téléchargement de core…
téléchargement de extra…
téléchargement de multilib…
téléchargement de chaotic-aur…
spawn pacman -Su
:: Starting full system upgrade...
warning: snapper-tools: local (1.3.1-1.6) is newer than chaotic-aur (1.3.1-1)
resolving dependencies...
looking for conflicting packages...
:: swayfx-0.5.1-3.3 and scenefx-0.3-1 are in conflict. Remove scenefx? [y/N] y

Unexpected user input required. Try again without --noconfirm⏎

Ok with pacman -Syu

dr460nf1r3 · 15 June 2025 10:22

This should be handled automatically in the new garuda-update:

BluishHumility · 15 June 2025 10:44

It works fine with garuda-update as well, however as your error message indicates you cannot pass the --noconfirm flag if user interaction is required.

If you are not sure why this flag has been set, probably you are updating from RANI.

That’s perfect, great idea! I will mark this the “solution”, thank you!

BluishHumility · 17 June 2025 10:45

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.