[Unstable Update i686] 2019-08-17 - Another big update

Another very large selection of packages have been updated in arch32 (about 3700 total).

There are a lot of "core" packages updated and rebuilt so this will be hanging out in x32-unstable for a little while - unless there's an overwhelming "actually it's OK" response. :wink:


Available kernels

Series Version PAE
linux316 3.16.72 No
linux44 4.4.189 No
linux49 4.9.189 No
linux414 4.14.139 No
linux419 4.19.67 Yes

Current difference to x32-testing

Full list is available here.


Any problems?

  • No issues, everything went smoothly
  • Yes there was an issue. I was able to resolve it myself. (Please post your solution)
  • Yes I am currently experiencing an issue due to the update. (Please post about it)

0 voters


Is x32-unstable ready to be moved to x32-testing?

This will inform the snap process; there is no set threshold.

  • No or Not yet
  • Yes, x32-unstable should be snapped to x32-testing at this point
  • Other (post)

0 voters

1 Like

Known issues


There's quite a bit of breakage.

Yeah... likely multiple packages still needing to be rebuilt.


Known to-do

what does work:

  • kernel 4.19 boots
  • lxqt and X work in general
  • firefox-nightly runs

what does not work(so far):

  • lxqt can't read the battery information
  • no sound (any application)
  • libreoffice-fresh crashes at startup

I will investigate....

power management(missing battery info):

systemd[1]: Starting Daemon for power management...
upowerd[1073]: /usr/lib/upowerd: error while loading shared libraries: /usr/lib/libgnutls.so.30: cannot make segment writable for relocation: Operation not permitted>
systemd[1]: upower.service: Main process exited, code=exited, status=127/n/a
systemd[1]: upower.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Daemon for power management.

upstream bug in gnutls: =>see https://bbs.archlinux32.org/viewtopic.php?id=2789 comment #11-14
=> fixed with gnutls-3.6.9-1.2

no sound:

pulseaudio[774]: E: [pulseaudio] ltdl-bind-now.c: Modul »/usr/lib/pulse-12.2/modules/module-alsa-card.so« konnte nicht geladen werden: /usr/lib/pulse-12.2/modules/libalsa-util.so: undefined symbol: pa_alsa_ucm_device_update_available
pulseaudio[774]: E: [pulseaudio] module.c: Failed to open module "module-alsa-card".
pulseaudio[774]: E: [pulseaudio] ltdl-bind-now.c: Modul »/usr/lib/pulse-12.2/modules/module-alsa-card.so« konnte nicht geladen werden: /usr/lib/pulse-12.2/modules/libalsa-util.so: undefined symbol: pa_alsa_ucm_device_update_available
pulseaudio[774]: E: [pulseaudio] module.c: Failed to open module "module-alsa-card".

libreoffice-fresh:
problem is the QT5 VCL backend I'm using. Using the GTK3 VCL backend makes libreoffice-fresh work. As you have to set the QT5 backend manually it shouldn't be a problem for most of the users.

2 Likes

That might need a rebuild.

I got the same upower.service and no sound problem. There's no info in the logs except that the service failed.

1 Like

The following downgrades solved my problems:

upower 0.99.10-1.1 -> 0.99.7-1.0
pulseaudio 12.2-2.5 -> 12.2-2.4
libpulse 12.2-2.5 -> 12.2-2.4

These are the packages present on my cache:

[isa@ceci-pc ~]$ ls -la /var/cache/pacman/pkg/ | grep -e pulse -e upower
-rw-r--r-- 1 root root    356168 set 19  2017 libpulse-11.1-1-i686.pkg.tar.xz
-rw-r--r-- 1 root root    356868 jan 15  2019 libpulse-12.2-2.4-i686.pkg.tar.xz
-rw-r--r-- 1 root root    355832 ago 17 18:57 libpulse-12.2-2.5-i686.pkg.tar.xz
-rw-r--r-- 1 root root   1098380 set 19  2017 pulseaudio-11.1-1-i686.pkg.tar.xz
-rw-r--r-- 1 root root   1111228 jan 15  2019 pulseaudio-12.2-2.4-i686.pkg.tar.xz
-rw-r--r-- 1 root root   1098272 ago 17 19:21 pulseaudio-12.2-2.5-i686.pkg.tar.xz
-rw-r--r-- 1 root root    168196 mar 15 23:44 upower-0.99.10-1.0-i686.pkg.tar.xz
-rw-r--r-- 1 root root    168912 ago 17 19:57 upower-0.99.10-1.1-i686.pkg.tar.xz
-rw-r--r-- 1 root root    133308 dez 16  2017 upower-0.99.7-1.0-i686.pkg.tar.xz
-rw-r--r-- 1 root root    135308 out 26  2018 upower-0.99.9-1.0-i686.pkg.tar.xz

Regarding upower, it's strange I had to downgrade to such an old package, since it was working perfectly with 0.99.10-1.0 before the update.

1 Like

Forum kindly sponsored by Bytemark