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

Issues & Assistance Sway
1

Hello today trying to update the system I received this message:

error: failed to prepare transaction (could not satisfy dependencies)
:: installing scenefx (0.2-1) breaks dependency ‘libscenefx.so=1-64’ required by swayfx

> System:
  Kernel: 6.13.2-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
    root=UUID=33c2c6c5-fd95-416e-a2c9-37cd5e17856c rw rootflags=subvol=@
    quiet loglevel=3 nvidia_drm.modeset=1 nvidia_drm.fbdev=1 hush ibt=off
  Desktop: Sway v: 0.4 with: waybar tools: swayidle avail: swaylock vt: 1
    lm: greetd Distro: Garuda base: Arch Linux
Machine:
  Type: Laptop System: Razer product: Blade 18 - RZ09-0509 v: 10.04
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Razer model: KI8100 v: 4 serial: <superuser required>
    part-nu: RZ09-0509TFK3 uuid: <superuser required> UEFI: Razer v: 1.04
    date: 05/06/2024
Battery:
  ID-1: BAT0 charge: 96.9 Wh (100.0%) condition: 96.9/91.7 Wh (105.7%)
    volts: 17.4 min: 15.4 model: Razer Blade type: Unknown serial: <filter>
    status: not charging cycles: 6
CPU:
  Info: model: Intel Core i9-14900HX bits: 64 type: MST AMCP arch: Raptor Lake
    gen: core 14 level: v3 note: check built: 2022+ process: Intel 7 (10nm)
    family: 6 model-id: 0xB7 (183) stepping: 1 microcode: 0x12C
  Topology: cpus: 1x dies: 1 clusters: 12 cores: 24 threads: 32 mt: 8 tpc: 2
    st: 16 smt: enabled cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32
    KiB, 16x64 KiB L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
  Speed (MHz): avg: 906 min/max: 800/5600:5800:4100 scaling:
    driver: intel_pstate governor: powersave cores: 1: 906 2: 906 3: 906 4: 906
    5: 906 6: 906 7: 906 8: 906 9: 906 10: 906 11: 906 12: 906 13: 906 14: 906
    15: 906 16: 906 17: 906 18: 906 19: 906 20: 906 21: 906 22: 906 23: 906
    24: 906 25: 906 26: 906 27: 906 28: 906 29: 906 30: 906 31: 906 32: 906
    bogomips: 154828
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities: <filter>
Graphics:
  Device-1: Intel Raptor Lake-S UHD Graphics vendor: Razer USA driver: i915
    v: kernel alternate: xe arch: Xe process: Intel 10nm built: 2020-21 ports:
    active: eDP-2 empty: DP-4,HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:a788
    class-ID: 0300
  Device-2: NVIDIA AD104M [GeForce RTX 4080 Max-Q / Mobile]
    vendor: Razer USA driver: nvidia v: 570.86.16 alternate: nouveau,nvidia_drm
    non-free: 550/565.xx+ status: current (as of 2025-01) arch: Lovelace
    code: AD1xx process: TSMC n4 (5nm) built: 2022+ pcie: gen: 4
    speed: 16 GT/s lanes: 16 ports: active: none empty: DP-1, DP-2, DP-3,
    HDMI-A-1, eDP-1 bus-ID: 01:00.0 chip-ID: 10de:27e0 class-ID: 0300
  Device-3: Luxvisions Innotech Integrated Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-8:3 chip-ID: 30c9:009e
    class-ID: fe01 serial: <filter>
  Display: wayland server: Xwayland v: 24.1.5 compositor: Sway v: 0.4
    driver: gpu: i915 display-ID: 1
  Monitor-1: eDP-2 model: BOE Display 0x0c87 built: 2023 res:
    mode: 2560x1600 hz: 300 scale: 100% (1) dpi: 168 gamma: 1.2
    size: 388x242mm (15.28x9.53") diag: 457mm (18") ratio: 16:10
    modes: 2560x1600
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 1 drv: iris gbm: drv: iris surfaceless: drv: nvidia
    wayland: drv: iris x11: drv: iris
  API: OpenGL v: 4.6.0 compat-v: 4.6 vendor: intel mesa v: 24.3.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (RPL-S)
    device-ID: 8086:a788 memory: 15.13 GiB unified: yes
  API: Vulkan v: 1.4.303 layers: 11 device: 0 type: integrated-gpu
    name: Intel Graphics (RPL-S) driver: N/A device-ID: 8086:a788
    surfaces: xcb,xlib,wayland device: 1 type: discrete-gpu name: NVIDIA
    GeForce RTX 4080 Laptop GPU driver: N/A device-ID: 10de:27e0
    surfaces: xcb,xlib,wayland device: 2 type: cpu name: llvmpipe (LLVM
    19.1.7 256 bits) driver: N/A device-ID: 10005:0000
    surfaces: xcb,xlib,wayland
  Info: Tools: api: eglinfo, glxinfo, vulkaninfo
    gpu: nvidia-settings,nvidia-smi wl: kanshi, nwg-displays, swaymsg, wdisplays
    x11: xdpyinfo, xprop, xrandr
Audio:
  Device-1: Intel Raptor Lake High Definition Audio vendor: Razer USA
    driver: sof-audio-pci-intel-tgl alternate: snd_hda_intel, snd_soc_avs,
    snd_sof_pci_intel_tgl bus-ID: 00:1f.3 chip-ID: 8086:7a50 class-ID: 0401
  Device-2: NVIDIA AD104 High Definition Audio vendor: Razer USA
    driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:22bc class-ID: 0403
  Device-3: Razer USA BlackShark V2 HS 2.4
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-2.1:4 chip-ID: 1532:0565 class-ID: 0300
    serial: <filter>
  API: ALSA v: k6.13.2-zen1-1-zen status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8125 2.5GbE vendor: Razer USA driver: r8169 v: kernel
    pcie: gen: 2 speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 55:00.0
    chip-ID: 10ec:8125 class-ID: 0200
  IF: enp85s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 7 AX1775 /AX1790 /BE20 /BE401/BE1750 2x2
    driver: iwlwifi v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 1 link-max:
    gen: 4 speed: 16 GT/s bus-ID: 56:00.0 chip-ID: 8086:272b class-ID: 0280
  IF: wlp86s0f0 state: up mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 1-14:7 chip-ID: 8087:0036 class-ID: e001
  Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 5.4
    lmp-v: 13 status: discoverable: no pairing: no class-ID: 6c010c
Drives:
  Local Storage: total: 4.57 TiB used: 550.87 GiB (11.8%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:2 vendor: Samsung
    model: MZVL21T0HCLR-00B00 size: 953.87 GiB block-size: physical: 512 B
    logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
    fw-rev: GXA7801Q temp: 32.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Samsung model: SSD 990 PRO 4TB
    size: 3.64 TiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 4B2QJXD7 temp: 31.9 C
    scheme: GPT
Partition:
  ID-1: / raw-size: 195.31 GiB size: 195.31 GiB (100.00%)
    used: 49.12 GiB (25.1%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:8
  ID-2: /boot/efi raw-size: 100 MiB size: 96 MiB (96.00%)
    used: 50.4 MiB (52.5%) fs: vfat dev: /dev/nvme0n1p2 maj-min: 259:4
  ID-3: /home raw-size: 195.31 GiB size: 195.31 GiB (100.00%)
    used: 49.12 GiB (25.1%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:8
  ID-4: /var/log raw-size: 195.31 GiB size: 195.31 GiB (100.00%)
    used: 49.12 GiB (25.1%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:8
  ID-5: /var/tmp raw-size: 195.31 GiB size: 195.31 GiB (100.00%)
    used: 49.12 GiB (25.1%) fs: btrfs dev: /dev/nvme0n1p6 maj-min: 259:8
Swap:
  Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 30.98 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 32
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 44.2 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 30.98 GiB used: 3.79 GiB (12.2%)
  Processes: 556 Power: uptime: 27m states: freeze,mem,disk suspend: s2idle
    avail: deep wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.33 GiB services: upowerd Init: systemd
    v: 257 default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 2079 libs: 534 tools: octopi,pacseek,paru
    Compilers: clang: 19.1.7 gcc: 14.2.1 Shell: garuda-inxi default: fish
    v: 3.7.1 running-in: kitty inxi: 3.3.37
Garuda (2.6.26-1.1):
  System install date:     2025-01-22
  Last full system update: 2025-02-13
  Is partially upgraded:   No
  Relevant software:       snapper NetworkManager dracut nvidia-dkms
  Windows dual boot:       Probably (Run as root to verify)
  Failed units:
1 Like
2

Wait for the fix or open issue on GitHub.

6 Likes
3

It looks more like a packaging issue to me.
Strange, both packages were updated on the same day, same maintainer I think.
Maybe just try again in a few hours.
And both packages have the same versions in the chaotic-AUR but with an earlier date.
Maybe a rebuild is needed?

6 Likes
4

Here is the relevant issue:

It looks like they fixed it a couple days ago in this commit:

The AUR package is not yet benefiting from this fix because they didn’t tag a point release for it. I left a comment in the issue requesting they add one; hopefully that is helpful rather than annoying. It looks like the person who added the commit to fix it also maintains the AUR package (PKGBUILD - aur.git - AUR Package Repositories), so maybe this will be a nice quick one.

5 Likes
5

je n’ai pas compris comment corriger mon problème d’update mais vous êtes géniaux, aux plaisirs (vous assurrer)

1 Like
6

Ce n’est pas encore réglé ! Nous devons attendre. Je pense que la solution a été marquée par accident.

As an update, one of the package maintainers has mentioned they will see if the PKGBUILD can be updated with a patch to get this resolved until they can tag a point release.

WillPower3309 on Feb 14, 2025

@ErikReider can you guys tag a point release for this when you get a chance, so we can get the fix in the AUR package?

We need #106 in too, I’ll see if we can include a patch for the pkgbuild in the meantime

If they can sneak in a patch for the PKGBUILD, we can request a rebuild in the Chaotic-AUR and that should help resolve the issue.

5 Likes
7

I have been keeping an eye on this PKGBUILD, but unfortunately there have not been any changes yet so we will just have to wait.

If anyone needs to take a system update in the meantime (for example, you need to install a new package), as a temporary workaround you can replace swayfx with regular sway.

An easy way to do this is add sway as an argument to garuda-update, and then enter y to confirm the package replacement like this:

❯ garuda-update sway
:: Synchronizing package databases...
 garuda is up to date
 core is up to date
 extra is up to date
 multilib is up to date
 chaotic-aur is up to date
spawn pacman -Su sway
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
:: sway-1:1.10.1-2 and swayfx-0.4-3.3 are in conflict. Remove swayfx? [y/N] y

Obviously this will break the swayfx-specific options in the Sway config, but since they are all together in a single file you can just move the file out of ~/.config/sway/config.d. For example, you can move the file to ~/.config/sway for now like this:

mv ~/.config/sway/config.d/swayfx ~/.config/sway/

Once it is out of ~/.config/sway/config.d, it will no longer be read as part of the Sway config and should prevent getting errors when you reload Sway.

After the scenefx issue is resolved, switching back will be a simple matter of re-installing swayfx and moving the swayfx config back to ~/.config/sway/config.d.

3 Likes
8

Here is another topic related to this issue, which sheds a little more light on what is happening here:

TL;DR:

LAURAilway on Feb 19, 2025 · edited by LAURAilway

I presume that there were incompatibilities between scenefx-2.0 and swayfx-0.4(the current version), so they made scenefx-0.2.1 able to be installed alongside the 0.1 version (see here) and pointed the deps of swayfx specifically to that package until the rebase (0.5, I think) is fully released.

WillPower3309 on Feb 19, 2025 · Owner

Yup, this was the case. I’ll try to sort out this packaging issue

The package the upgrade is attempting to install (scenefx-0.2.1) is actually the incorrect package for our version of swayfx. The version we want is actually already installed (scenefx-0.1-2). The fact that these are two different packages (as opposed to two different versions of the same package) is causing some issues when Pacman attempts to reconcile the dependencies.

In this case, another way to work around the issue so the system can be updated normally is to ignore the scenefx package.

garuda-update -- --ignore=scenefx

Note that ignoring a package during an upgrade like this is generally not advised because it can result in a partial upgrade. This specific situation with scenefxis a unique case where Pacman believes we should be installing something we should not be, due to a packaging error.

It sounds like @WillPower3309 is going to take another look at sorting this out, so hopefully this whole thing will be resolved soon.

5 Likes
9

Thank, since Sunday i launch update normally and after error with IgnorePkg = scenefx

10

upd works :slight_smile:

11

Thx, all works

12

One of the Chaotic maintainers added an interfere to swayfx to trick it into using the new version of scenefx.

I have mixed feelings about this intervention, because the SwayFX developer confirmed that there are incompatibilities between scenefx-2.0 and swayfx-0.4 (that is the whole reason they made the scenefx-0.2.1 package). :grimacing:

I guess we will have to try it out and see how it goes. :crossed_fingers: YOLO! :joy:

5 Likes
13

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