[Stable Update] 2017-09-08 - Mesa, Kernels, PulseAudio, LibreOffice, KDE Apps, Cinnamon

update
stable

#1

Hi community,

with the huge Perl rebuild, Perl uses now the new toolchain and binary modules got moved to versioned path plus a hook to warn about outdated modules on update got added. Also we have now the final release of kernel v4.13 plus updated other kernel series as well. Latest LibreOffice, KDE Apps v17.08.1, Cinnamon v3.4.6 and Pulseaudio v11.0 refreshes some our editions.

More fixes went to our Mesa-Stack to stabilize KDE even more. We also worked on the new LTS-Kernel v4.14 added needed fixes to Calamares.

Please report back and give us feedback for given changes made to our repositories.

Best, Philip
Manjaro Project Lead


Current supported Kernels

  • linux310 3.10.107
  • linux312 3.12.74 [EOL]
  • linux316 3.16.47
  • linux318 3.18.70 [EOL]
  • linux41 4.1.43
  • linux44 4.4.87
  • linux48 4.8.17 [EOL]
  • linux49 4.9.48
  • linux410 4.10.17 [EOL]
  • linux411 4.11.12 [EOL]
  • linux412 4.12.11
  • linux413 4.13.0
  • linux414 4.14-rc0 (x86_64)
  • linux-RT-LTS 4.9.47_rt37 (x86_64)
  • linux-RT 4.11.12_rt13 (x86_64)

Package Updates (Fri Sep 8 07:30:11 CEST 2017)

  • stable community i686: 487 new and 481 removed package(s)
  • stable community x86_64: 525 new and 518 removed package(s)
  • stable core i686: 20 new and 20 removed package(s)
  • stable core x86_64: 22 new and 20 removed package(s)
  • stable extra i686: 754 new and 747 removed package(s)
  • stable extra x86_64: 770 new and 747 removed package(s)
  • stable multilib x86_64: 13 new and 13 removed package(s)

  • 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


Check if your mirror has already synced:


Manjaro v17.0.3 released
AUR install packages with Perl broken again
Manjaro-Deepin 17.0.4
#2

Well, I lolled at the video. Let’s see if I’m still laughing after the update :wink:


#3

Does this mean there will be new ISOs?


#4

Smooth update on KDE. Welcome 17.0.4 !!


#5

check mirrors , they have not been updated


#6

Smooth update on 4 machines. Pacman on CLI. Cinnamon.


#7

i have installed 4 manjaro DE , one disks each
@philm , @gohlip
since 17.0.2 there is a big time to wait for any update concerns config.cfg
i have 24 000 debug lines in journalctl with
Grub2 - Os-prober - Mount and parsing

many minutes to wait for ending , sometime this is aborted


#8

If they are all on the same machine you should investigate creating a separate partition for your pacman package cache, within each Manjaro system mount this partition to /var/cache/pacman/pkg.

@eugen-b pointed this out in another thread, really good idea, saves downloading the same packages 4 times during updates. Make sure you back it up regularly though.

I have a USB VM with multiple Manjaro systems on separate partitions, I’ll be re-installing them all again soon with 17.0.3 and manjaro-architect, will be using this method.


#9

this is not a trouble , i have free space on each disks,
and a good internet connection.


#10

Here everything runs again flawlessly. :slight_smile:


#11

Smooth update. Made the switch from kernel 4.12.11 to 4.13.0, so far without any problems. Thanks for the hard work folks :slight_smile:


#12

OK on Gnome, thanks.


#13

i got this:

(2/9) Warn about old perl modules
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
        LANGUAGE = "de",
        LC_ALL = (unset),
        LC_MEASUREMENT = "de_AT.UTF-8",
        LC_PAPER = "de_AT.UTF-8",
        LC_MONETARY = "de_AT.UTF-8",
        LC_NAME = "de_AT.UTF-8",
        LC_ADDRESS = "de_AT.UTF-8",
        LC_NUMERIC = "de_AT.UTF-8",
        LC_MESSAGES = "de_DE.UTF-8",
        LC_TELEPHONE = "de_AT.UTF-8",
        LC_IDENTIFICATION = "de_AT.UTF-8",
        LC_TIME = "de_AT.UTF-8",
        LANG = "de_DE.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").

#14

Virtualbox has a problem. Running: # modprobe vboxdrv fails. Running virtualbox gives message to run # /sbin/vboxconfig as root.

Here is the entire terminal output:

# pacman -U *
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (3) linux49-virtualbox-host-modules-5.1.26-5  qt5-x11extras-5.9.1-2
             virtualbox-5.1.26-1

Total Installed Size:  99.22 MiB

:: Proceed with installation? [Y/n] y
(3/3) checking keys in keyring                     [######################] 100%
(3/3) checking package integrity                   [######################] 100%
(3/3) loading package files                        [######################] 100%
(3/3) checking for file conflicts                  [######################] 100%
(3/3) checking available disk space                [######################] 100%
:: Processing package changes...
(1/3) installing linux49-virtualbox-host-modules   [######################] 100%
===> You must load vboxdrv module before starting VirtualBox:
===> # modprobe vboxdrv
(2/3) installing qt5-x11extras                     [######################] 100%
(3/3) installing virtualbox                        [######################] 100%
Optional dependencies for virtualbox
    vde2: Virtual Distributed Ethernet support
    virtualbox-guest-iso: Guest Additions CD image
    virtualbox-ext-vnc: VNC server support
    virtualbox-sdk: Developer kit
:: Running post-transaction hooks...
(1/5) Updating icon theme caches...
(2/5) Updating system user accounts...
(3/5) Arming ConditionNeedsUpdate...
(4/5) Updating the desktop file MIME type cache...
(5/5) Updating the MIME type database...
# modprobe vboxdrv
modprobe: ERROR: could not insert 'vboxdrv': Exec format error

Running virtualbox gives message to run ‘sbin/vboxconfig’ as root:

# /sbin/vboxconfig
bash: /sbin/vboxconfig: No such file or directory

Have confirmed all users are members of vboxusers group.

VBOX was working for the previous kernel?!?

The problem was resolved as follows:

# pacman -R linux49-virtualbox-host-modules qt5-x11extras virtualbox

Then installed virtualbox via pamac. Problem solved. Everything works now! This kernel appears to have an updated linux49-virtualbox-host-modules (5.1.2.204)


#15

is that ed sheeran? first GoT, now manjaro. when will it end? :stuck_out_tongue:


#16

Another perfect update on my machine - no surprises there!

Big thanks to Phil & core team, plus everyone who took the time to test this one upstream.

More power to you all!

Ruziel :slight_smile:


#17

Can you check if any of your other OS’s has /etc/lsb-release?

If there are some without, add entries in /etc/lsb-release as outlined here asd see if this helps. Let us know.

Good luck.

[edit] since there are 4 disks, try making them active (click on any partition there) before doing grub-update and see if that helps also. A spinning disk sometimes ‘sleep’ if inactive.


#18

the other os have /etc/lsb-release

  1. Manjaro Xfce
  2. Debian
  3. Manjaro i3
  4. Manjaro KDE
  5. Manjaro Gnome

all are in EFI with each theirs own /boot/efi

the trouble came with grub2 & os-prober & mount ,
because i have debug lines in journalctl ( more than 24 000 lines )
easy to see with htop

remark : each DE Manjaro create the same boot-id , so we have 4 boot-id ( for each disk)
there are not sleeping disks , all are SSD

cat /etc/lsb-release
DISTRIB_ID=ManjaroLinux
DISTRIB_RELEASE=17.0.4
DISTRIB_CODENAME=Gellivara
DISTRIB_DESCRIPTION="Manjaro Linux"

lsb_release
LSB Version:	n/a

#19

Anyone else having a problem with VBOX, other that @aaa?

I am on a schedule and need to have VBOX running perfectly right now…


#20

Thank you @philm and Manjaro team. Everything working fine in XFCE environment.

All the best.