Unexpected prompts during system update (lib32-jack and missing AUR packages)

Hey everyone,

I ran my usual system update today and noticed a couple of things I haven’t seen before. I’m not sure if these are something to worry about or if I can safely proceed with the update. Hoping someone can shed some light on what’s going on.


What happened

When I kicked off the update, I was prompted twice to choose a provider for lib32-jack:

:: There are 2 providers available for lib32-jack:
:: Repository multilib
    1) lib32-jack2 2) lib32-pipewire-jack 

Enter a number (default=1): 
==> 1
:: There are 2 providers available for lib32-jack:
:: Repository multilib
    1) lib32-jack2 2) lib32-pipewire-jack 

Enter a number (default=1): 
==> 1

I just went with the default (1 / lib32-jack2) both times, but I’m not sure why it’s asking me at all and why twice. How do I determine which one I need to install?


Right after that, I also got this notice:

-> Packages not in AUR: iptables-nft  kinit  quazip-qt5

Again, something I haven’t seen before. I’m not sure if these packages were previously in the AUR and got removed, or if something else is going on.


Full update output

Here’s the complete output for context:

:: Synchronizing package databases...
 endeavouros is up to date
 core is up to date
 extra is up to date
 multilib is up to date
 home_maxrd2_Arch is up to date
:: Searching AUR for updates...
:: There are 2 providers available for lib32-jack:
:: Repository multilib
    1) lib32-jack2 2) lib32-pipewire-jack 

Enter a number (default=1): 
==> 1
:: There are 2 providers available for lib32-jack:
:: Repository multilib
    1) lib32-jack2 2) lib32-pipewire-jack 

Enter a number (default=1): 
==> 1
:: Searching databases for updates...
 -> Packages not in AUR: iptables-nft  kinit  quazip-qt5
:: 25 dependencies will also be installed for this operation.
    core/glib2-devel             -> 2.88.0-1
    (make dependency of lib32-gst-plugins-base-libs, lib32-gstreamer)
    extra/lib32-rust-libs        -> 1:1.94.1-1
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    extra/meson                  -> 1.10.2-1
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    extra/qt6-wayland            -> 6.11.0-1
    extra/wayland-protocols      -> 1.48-1
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    extra/xorg-server-xvfb       -> 21.1.21-1
    multilib/lib32-aalib         -> 1.4rc5-5
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-cdparanoia    -> 10.2-5
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-flac          -> 1.5.0-1
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-jack2         -> 1.9.22-2
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-libavc1394    -> 0.5.4-5
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-libcaca       -> 0.99.beta20-2
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-libdv         -> 1.0.0-9
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-libiec61883   -> 1.2.0-5
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-libpulse      -> 17.0+r98+gb096704c0-1
    (make dependency of lib32-gst-plugins-base-libs, lib32-gstreamer)
    multilib/lib32-libraw1394    -> 2.1.2-5
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-libshout      -> 1:2.4.6-4
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-libsoup3      -> 3.6.6-2
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-libvpx        -> 1.16.0-2
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-opus          -> 1.6.1-1
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-sdl2-compat   -> 2.32.66-1
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-taglib        -> 2.1.1-1
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-twolame       -> 0.4.0-3
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-v4l-utils     -> 1.32.0-1
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)
    multilib/lib32-wavpack       -> 5.9.0-1
    (make dependency of lib32-gstreamer, lib32-gst-plugins-base-libs)

:: 193 packages to upgrade/install.
193  core/ding-libs                     0.6.2-2             -> 0.7.0-1
192  core/glib2                         2.86.5-1            -> 2.88.0-1
[... full list continues ...]
  1  aur/visual-studio-code-bin         1.114.0-1           -> 1.115.0-1

Is it safe to go ahead and apply this update? Any help or clarification is appreciated. Thanks in advance! :folded_hands:

Not sure what this repository is but that might cause some strange things I think.

Thanks for the suggestion! I removed the home_maxrd2_Arch repository since I haven’t been using the package I installed from there anyway. Unfortunately the output of my update hasn’t changed though, everything looks the same besides that repo no longer showing up. So the lib32-jack prompts and the “Packages not in AUR” notice are still there.

(The repo was for https://subtitlecomposer.kde.org/)

This ones could be orphans you can check with

yay -Yc

I ran yay -Yc as suggested and it found a few orphans that I went ahead and removed, including quazip-qt5 which was one of the packages showing up in the “not in AUR” notice:

yay -Yc
checking dependencies...

Package (3)             Old Version  Net Change

eos-reboot-recommended  26.3-1        -0,01 MiB
libkdcraw5              25.12.3-1     -0,13 MiB
quazip-qt5              1.5-1         -0,37 MiB

Total Removed Size:  0,51 MiB

:: Do you want to remove these packages? [Y/n] Y

So that takes care of quazip-qt5.


Found the answer for iptables-nft as well! There was an Arch Linux news post about it from April 5th 2026:

The old iptables-nft package name is replaced by iptables, and the legacy backend is available as iptables-legacy.

When switching packages (among iptables-nft, iptables, iptables-legacy), check for .pacsave files in /etc/iptables/ and restore your rules if needed:

  • /etc/iptables/iptables.rules.pacsave

  • /etc/iptables/ip6tables.rules.pacsave

Most setups should work unchanged, but users relying on uncommon xtables extensions or legacy-only behavior should test carefully and use iptables-legacy if required.

So iptables-nft was simply renamed/replaced by iptables in the official repos, which is why it shows up as “not in AUR”… but not sure what I should do there? Do I need to manually run sudo pacman -S iptables to sort this out, or will it be handled automatically as part of the regular system update?

I also checked on kinit and it turns out it is not required by anything on my system:

pacman -Qi kinit | grep "Required By"
Required By     : None

kinit was part of KDE Frameworks 5… Since it is no longer in the AUR and not required by anything, it was probably just a leftover from my old KDE 5 install, as my system has been running for many years…

I went ahead and removed it with:

sudo pacman -Rns kinit

No issues so far!

Yes the only package I could find was kinit5 so that makes sense.
You could also check for e.g. lib32-jack with

locate lib32-jack

When I got the update for iptables I got a prompt if iptables should replace iptables-nft and answered yes.

Thanks! Running locate lib32-jack returns nothing, so it is not installed on my system at all. That explains the provider prompt, it is being pulled in as a new dependency for lib32-gstreamer and lib32-gst-plugins-base-libs.

Since I am using PipeWire as my audio system I should probably choose lib32-pipewire-jack instead of the default lib32-jack2 right?

That looks about right yes because the lib32-jack2 is from 2024, not using any of this myself thought, so not sure.

I did some more digging and found the AUR comments for proton-ge-custom-bin which explains a lot of what is going on with my update!

It turns out that lib32-gst-plugins-base-libs was recently dropped from the official Arch multilib repository and is now only available as an AUR package. This is why it is being built from source and pulling in a large number of extra dependencies, including lib32-jack, which is the cause of the provider prompt I was getting.

According to the AUR comments this is a known issue and most of these extra dependencies are actually optional and not strictly necessary for Proton GE to work. There is also a note that the lib32-jack2 dependency should not be getting pulled in for PipeWire users, which explains why I was getting prompted.

Since I confirmed I am using PipeWire I will be selecting lib32-pipewire-jack (option 2) instead of the default lib32-jack2 when prompted.

So to summarize what I found about the “Packages not in AUR” notice and the other unexpected messages:

  • iptables-nft Replaced by iptables, pacman should handle the transition automatically during the update
  • kinit Leftover from my old KDE 5 install, already removed it with sudo pacman -Rns kinit
  • lib32-jack provider prompt Caused by proton-ge-custom-bin pulling in lib32-gst-plugins-base-libs from the AUR, selecting lib32-pipewire-jack is the right choice for PipeWire users

Everything looks safe to update! Thanks @keescase for your help.