[Stable Update x32] 2018-01-17 - KDE, GCC, Flash, Deepin, lots of other stuff too

update
stable
manjaro32

#1

Hello i686ers!

This is a relatively large set of updates which includes an updated KDE, GCC and Flash plugins, plus the return of Deepin to i686. PHP 7.1 packages are also now available in addition to PHP 7.2.


Main changes

  • KDE updated to 17.12.1
  • GCC updated to 7.2.1+20171224
  • Deepin packages are back
  • Flash 28.0.0.137

Available kernels

Series Version
linux316 3.16.53
linux41 4.1.48
linux44 4.4.111
linux49 4.9.76
linux414 4.14.13

archlinux32

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.

Why aren’t the available packages/package versions the same as x86_64?

archlinux32 packages are based on Arch packages but may need editing to build correctly. Builds of less-popular packages are lower priority.

Manjaro-specific packages may lag behind x86_64 because there aren’t as many packagers. 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 updated the preview installer images:

There will be a new release as soon as I refresh myself on 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 (when necessary)
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 (when necessary)
Sync Snap New testing, update unstable
etc. etc. etc. etc.

Full list of changes

The full update list can be found 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



#2

Known issues and solutions

This is a wiki post; please edit as necessary


LibreOffice Writer won’t open, provides no output in terminal

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.

What about Meltdown?

Meltdown is “fixed” by the KPTI patches for x86_64. The patches do not currently work for i686. If you’re running a 32-bit Intel system you are vulnerable to Meltdown.
Yet, there’s an experimental support that will take its way into the kernel:
http://lkml.iu.edu/hypermail/linux/kernel/1801.2/00657.html

What about Spectre?

Spectre is “fixed” by microcode updates. Specific/individual updates from the CPU manufacturers are needed for specific/individual CPU families/models. Not all CPUs have updates yet. Some CPUs will never get an update.

When will this all be fixed?

Possibly never.
Update: Look for edit above.

Where can I read more?



#3

everything seems good :smiley:


#4

I really wonder if x32 will ever be patched from meltdown…
This also conserns virtualisation…


This brings memory to what happened to x16, it had an even worse vulnerabilities after it became legacy by x32…
Update: look above(wiki post)


#5

More technically, every Intel processor which implements out-of-order execution is potentially affected, which is effectively every processor since 1995 (except Intel Itanium and Intel Atom before 2013).
https://meltdownattack.com/#faq-systems-meltdown


#6

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