[Stable Update x32] 2018-01-09 - Kernels, many (many) upstream packages updated

Hello i686ers!

This set of updates bumps kernels 4.4, 4.9 and 4.14 to include the current KPTI fixes. More is sure to come with the next kernel updates.

However, the main thing of note is the number of upstream changes with a huge number of core packages updated, and another load of packages rebuilt due to MESA, Xorg, Python, Ruby, Qt5 and Haskell updates.

This is a large set of updates.

Main changes

  • Updated kernels, extramodules rebuilt as necessary
  • Firefox and Thunderbird updates
  • Many, many upstream changes, including:
    • systemd
    • xorg-server
    • mesa
    • KDE
    • LibreOffice

Available kernels

Series Version
linux316 3.16.52
linux41 4.1.48
linux44 4.4.110
linux49 4.9.75
linux414 4.14.12


If you find manjaro32 useful please consider donating to, or helping out with, archlinux32. It's a small team taking on a huge project and any help will no doubt be very much appreciated.

How do I get it?

These steps should no longer be necessary

If you're already running a 32-bit installation, and haven't already migrated, you should shortly get a manjaro-system update which will transition you to the new setup (it should automate the following steps).

Otherwise, edit your /etc/pacman-mirrors.conf and change (or set):

Branch = x32-stable

making sure there is no comment marker (#) at the start of the line. Then, update your mirror list, install the keyring package, and update:

pacman-mirrors -c all
pacman -Sy archlinux32-keyring-transition
pacman -S archlinux32-keyring
pacman -Syu

archlinux32-keyring-transition is signed by the Arch devs and allows you to install archlinux32-keyring which contains the keys that sign all archlinux32 packages.

archlinux32-keyring replaces archlinux32-keyring-transition.

What about package updates?

Manjaro-specific packages may lag behind x86_64 because there aren't as many packagers. I may also trim the supported package list to save effort, depending on frequency of updates to packages and packagers who volunteer to help out. If you notice an important package is lagging please report it; at the moment it's only me packaging for i686:

I'm only packaging current LTS kernels. Any marked as EOL are dropped. I'll not be building the mainline kernel.

What about security updates?

I cannot guarantee timely security updates on x32-stable. If this is critical for you I recommend you switch to x32-testing or cherry-pick those packages from x32-testing or x32-unstable as they become available.

Something broke. Isn't this meant to be stable?

"Stable" means "infrequently changing", not "everything will work perfectly all the time". If you want it to mean everything works, you need to help test the things you're interested in.

What about installer images?

Phil very kindly spun some preview installer images:

This stable update set will form the basis for the 17.1.1 release once I work out how to do it. :slight_smile:

What about x32-testing and x32-unstable?

These are already available, and I recommend you use x32-testing if you can to make sure testing is done.

x32-unstable should be used by anyone who wants to try and find any issues before they impact other people. If you have multiple/many machines you really should run one of those on x32-unstable.

The update announcement process will look something like:

Unstable Testing Stable Announcement threads
Sync New unstable
Sync Snap New testing, update unstable
Sync Update unstable
... ...
Sync Snap New testing, update unstable
... ... ...
Snap New stable, close testing and unstable
Sync New unstable
Sync Snap New testing, update unstable
etc. etc. etc. etc.

Full list of changes

The list of changes is once again too long to post, so 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


Known issues and solutions

This is a wiki post; please edit as necessary.

libQt5Core.so.5: cannot open shared object file: No such file or directory

This is an issue with Qt 5.10 and kernel 3.16. Switch to at least kernel 4.1 (ideally 4.4+ for KPTI patches, if these are indeed needed for 32-bit systems).

LibreOffice Writer won't open

This is a long-standing LibreOffice bug; to fix it you need to disable Java. Start LibreOffice with libreoffice --safe-mode, choose "Continue in Safe Mode", then go to Tools, Options, Libreoffice->Advanced, and untick "Use a Java runtime environment".

You only have to do this once; afterwards Writer should start as normal.

1 Like

only the LibreOffice Writer issue, solved as suggested


A bit off-topic, I can make some new ISO but I'm not sure I can build and test install all by the end of this weekend

1 Like

If you want to give it a go then absolutely go ahead - but keep in mind that images are also distributed signed with a PGP signature of a Manjaro Team member so we couldn't immediately distribute yours... :slightly_frowning_face:

Sure, I' had build a full Mate ISO but haven't tested yet, it took so long to build on my old notebook, about 1h and 30'

For iso distributions that's ok :wink:

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

Forum kindly sponsored by