[Stable Update i686] 2018-07-26 - KDE applications, Pulseaudio, VirtualBox, Chromium

update
stable
manjaro32

#1

Hello i686ers!

Main updates of note are the KDE applications, Pulseaudio, VirtualBox, WINE.

Also, kernels.

Kernel 4.1 has become EOL so will be dropped “soon”. If you’re using it, switch up to kernel 4.4.


Anyone who would like to help out testing the upstream packages, please read the archlinux32 thread for details about how they automate their testing process and how to get involved:

https://bbs.archlinux32.org/viewtopic.php?id=171

(running this in an archlinux32 VM would be fine, there will hopefully be a way of doing this directly from within manjaro32 in the future)


Available kernels

Series Version
linux316 3.16.56
linux41 4.1.52 [EOL]
linux44 4.4.143
linux49 4.9.115
linux414 4.14.58

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:

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.

Full list of changes

It’s a long list, so it’s 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



[Testing Update i686] 2018-07-19 to 26 - KDE applications, Pulseaudio, VirtualBox
Problem updating Python 2
#2

Known issues and solutions

This is a wiki post; please edit as necessary.




#3

@jonathon @eugen-b

Hi guys

I can’t update to 2018-07-26

I’ve tried them tho;

sudo pacman-mirrors -g
sudo pacman -Syyu
sudo pacman-mirrors -f 3
sudo pacman -Syu

:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
:: Starting full system upgrade...
there is nothing to do

What could possibly go wrong? :thinking:


#4

I may or may not have forgotten to snap the packages over from x32-testing until about 15 minutes ago. :kissing:

Give it a little while longer for packages to propagate to mirrors.


#5

Waiting :sunglasses:


#6

Update on 1 Machine and 1 VB without Problems.

DK3


#7

The problem with Samba share that is mounted with cifs. Each time i write in Samba share my system crashes.
The last good kernel on Manjaro is linux414-4.14.50-1-i686.pkg.tar.xz, everything works fast an reliable.
Starting with linux414-4.14.51-1-i686.pkg.tar.xz writing to Samba share became painfully slow.
Starting with linux414-4.14.56-1-i686.pkg.tar.xz writing(and sometimes reading) causes system to crash.

Is it Arch problem or is it mainstream?


[Stable Update i686] 2018-08-04 - OpenJDK 10, Chromium, Racket
#8

The Manjaro kernels are not the same as the Arch kernels, but it could well be an issue with the upstream 4.14.56 kernel. I don’t have the spare capacity to track this one down so if you can identify the change in the intervening kernels it’s then possible to be reported and/or fixed.

You could try compiling an upstream kernel from source, without the Manjaro patches and configuration tweaks, to narrow it down a little.


#9

I guess i have to try.


#10

You can test arch kernel 4.14 by installing different versions of linux-lts.


#11

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