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

update
stable

#21

Then take a snapshot before applying the update.

Worst case you restore from the snapshot, although I have had no vbox issues (running multiple).


#22

Thanks for the suggestion, but…
host is manjaro, client is win… :wink:
I need to be able to load win right now…


#23

Since this update I have no sound.

There is no output device, I think it is a pulseaudio problem. Seeking to rectify.


#24

All fine on my system!


#25

Smooth update on XFCE on desktop and laptop. No issues as of yet.


#26

stephane, I did my update-grub shown here and it took less than 3 minutes (3 disks), from manjaro updated to 17.0.3.

[pop@Sun ~]$ LANG=C
[pop@Sun ~]$ sudo update-grub
Generating grub configuration file ...
Found background: /usr/share/grub/background.png
Found Intel Microcode image
Found linux image: /boot/vmlinuz-manjaro
Found initrd image: /boot/initramfs-manjaro.img
Found linux image: /boot/vmlinuz-4.13-x86_64
Found initrd image: /boot/initramfs-4.13-x86_64.img
Found initrd fallback image: /boot/initramfs-4.13-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.12-x86_64
Found initrd image: /boot/initramfs-4.12-x86_64.img
Found initrd fallback image: /boot/initramfs-4.12-x86_64-fallback.img
Found Ubuntu Artful Aardvark (development branch) (17.10) on /dev/sda1
Found Ubuntu Artful Aardvark (development branch) (17.10) on /dev/sda2
Found KaOS (rolling) on /dev/sda3
Found Ubuntu Aardvark (17.10) on /dev/sda4
Found Manjaro Linux (17.0.3) on /dev/sda6
Found Manjaro Linux (17.0.3) on /dev/sdb10
Found KaOS (rolling) on /dev/sdb11
Found Mageia 6 (6) on /dev/sdb2
Found Ubuntu Artful Aardvark (development branch) (17.10) on /dev/sdb3
Found Manjaro Linux (17.0.1) on /dev/sdb7
Found Manjaro Linux (17.0.3) on /dev/sdb8
Found Manjaro Linux (17.0.3) on /dev/sdb9
Found Manjaro Linux (17.0.3) on /dev/sdc11
Found Manjaro Linux (17.0.3) on /dev/sdc12
Found Ubuntu Artful Aardvark (development branch) (17.10) on /dev/sdc8
Found openSUSE Tumbleweed on /dev/sdc9
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
[pop@Sun ~]$ 

And in my old laptop (bios-legacy) it took slightly more than 4 minutes (1 disk).

I’ll post here when I get to the laptop later.

[pop@Nine ~]$ sudo update-grub
Generating grub configuration file ...
Found background: /usr/share/grub/background.png
Found Intel Microcode image
Found linux image: /boot/vmlinuz-manjaro
Found initrd image: /boot/initramfs-manjaro.img
Found linux image: /boot/vmlinuz-4.13-x86_64
Found initrd image: /boot/initramfs-4.13-x86_64.img
Found initrd fallback image: /boot/initramfs-4.13-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.12-x86_64
Found initrd image: /boot/initramfs-4.12-x86_64.img
Found initrd fallback image: /boot/initramfs-4.12-x86_64-fallback.img
Found Windows 7 on /dev/sda1
Found Manjaro Linux (17.0.3) on /dev/sda11
Found Linux Mint 17.2 Rafaela (17.2) on /dev/sda12
Found Manjaro Linux (17.0.3) on /dev/sda13
Found KaOS (rolling) on /dev/sda15
Found Windows 10 on /dev/sda2
Found Ubuntu Artful Aardvark (development branch) (17.10) on /dev/sda3
Found Manjaro Linux (16.10) on /dev/sda7
Found Manjaro Linux (17.0.3) on /dev/sda8
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
[pop@Nine ~]$ 

I normally disable os-prober in all my OS’s (I use my own grub) so my normal update-grub is quick (15 secs in the uefi system). But I can test it out with it enabled.
Knowing you do not have grub-customizer or grub-repair installed, I don’t know what else can help improve the time for update-grub [1], but I get the feeling it is faster in Kubuntu’s ‘update-grub’. I’ll post the time from Kubuntu here when I boot up to Kubuntu.

From Kubuntu in same system for UEFI, it is slightly less than 2 minutes.

Cheers.

[1] - If the time is too long and as you say all has /etc/ls-release and no grub-customizer or grub-repair, maybe try to reinstall grub (sudo pacman -S grub); maybe it might help.


#27

Yes, already online.


#28

Try disabling secure boot in UEFI, and see if Virtualbox loads your Win client.


#29

the iso manjaro 17.0.4 not exit ?


#30

Thank you very much, i just upgraded and i can confirm everything works ok!!!

Great job once more!!!


#31

Pamac wasn’t showing any updates from ‘community’, even after forcing resync and refresh from the command line.
Was forced to use pacman -Syyu this time. (The recommended method I know. I just think that the GUI updater should work as well, or why is it even there)

Update went well from command line - Cinnamon.


#32

after reboot and install new kernel , i lost on 4 DE launch of Grub
very difficult to understand what failed ( no prompt no return no message )
only welcome to grub and nothing else minutes later

after a moment i downgrade Grub & Prober
but it is not a good idea , because i have remote versions too

downgrade grub
   1) grub-2:2.02-2-x86_64.pkg.tar.xz (distant)
   2) grub-2:2.02-1-x86_64.pkg.tar.xz (distant)
   3) grub-1:2.02.rc2-1-x86_64.pkg.tar.xz (distant)
   4) grub-1:2.02.rc1-1-x86_64.pkg.tar.xz (distant)
   5) grub-1:2.02.beta3-6-x86_64.pkg.tar.xz (distant)
   6) grub-1:2.02.beta3-5-x86_64.pkg.tar.xz (distant)
   7) grub-1:2.02.beta3-4-x86_64.pkg.tar.xz (distant)
   8) grub-1:2.02.beta3-3-x86_64.pkg.tar.xz (distant)
   9) grub-1:2.02.beta3-2-x86_64.pkg.tar.xz (distant)
  10) grub-1:2.02.beta3-1-x86_64.pkg.tar.xz (distant)
  11) grub-1:2.02.beta2-6-x86_64.pkg.tar.xz (distant)
  12) grub-1:2.02.beta2-5-x86_64.pkg.tar.xz (distant)
  13) grub-1:2.02.beta2-4-x86_64.pkg.tar.xz (distant)
  14) grub-1:2.02.beta2-3-x86_64.pkg.tar.xz (distant)
  15) grub-1:2.02.beta2-2-x86_64.pkg.tar.xz (distant)
  16) grub-1:2.02.beta2-1-x86_64.pkg.tar.xz (distant)
  17) grub-1:2.02.beta1-1-x86_64.pkg.tar.xz (distant)
  18) grub-1:2.00.1282.g5ae5c54-1-x86_64.pkg.tar.xz (distant)
  19) grub-1:2.00.963.g93c1207-1-x86_64.pkg.tar.xz (distant)
  20) grub-1:2.00.900.gbca274b-1-x86_64.pkg.tar.xz (distant)
  21) grub-2.02.0-3-x86_64.pkg.tar.xz (local)
  22) grub-2.02.0-2-x86_64.pkg.tar.xz (local)
  23) grub-2.00.5086-1-x86_64.pkg.tar.xz (distant)

grub-2:2.02-2-x86_64.pkg.tar.xz (distant)
grub-2.02.0-3-x86_64.pkg.tar.xz (local) ( <-- the good version !)

so its ended with
pacman -Syyu
a warning about version Grub
and
pacman -S grub

and a restore grub EFI to be ok
OS-PROBER is desactived for GRUB now!


#33

No mesa 17.2! When can we expect this one to land?
Ive been hanging out months for this update as it should fix Dawn Of War 3 and stellaris amonst other games


#34

@philm
i have this error about firmware with version 4.13.0

sept. 09 00:29:00 mjro kernel: [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0xb2 (or later)


#35

Since updating urxvt doesn’t launch anymore, giving:

urxvt: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory

libperl.so is present at /usr/lib/perl5/core_perl/CORE/libperl.so


#36

Looks like your system update is incomplete. Or are you using any special version of urxvt?
For me rxvt-unicode 9.22-5 is working fine together with perl 5.26.0-4.


#37

I am unable to boot into Linux 4.13, the bootup process hangs directly after “Started udev Coldplug all devices”. Also, I just noticed that despite running a Ryzen processor grub tries to boot intel-ucode.img with initrd. I tried deleting the line and kernel 4.12 booted up just fine.


#38

Good sized update (around 500Mb), went smoothly. UNTIL reboot.
THEN, I noticed that for the 1st time in quite a while it screwed the pooch with my grub menu, and I had to resort to grub customizer to restore it back the way it is SUPPOSED to be.

But, other than that, smooth update none the less.


#39

That’s perhaps (most likely), as you noted, it shared the same bootloader-id.
I too have many Manjaro’s (and other multiple same OS distro) and only one ‘manjaro’ bootorder in the UEFI system. [1] [2]

It isn’t a problem for me (I have my own grub) and since you have 4 disk and each their own $esp, another way to handle this is for you to boot the bootorder of the respective disk (not ‘manjaro’ bootorder) as long as you set the respective core.efi to the $esp’s /boot/bootx64.efi.

Also note in other bootloaders (rEFInd, systemd-boot or EFIstub (Mac)), it will be a nightmare for multiple same distro OS’s, impossible to boot the OS that gets overridden (except through grub).

Cheers.

[1] - In bios-legacy, a reminder that we can have only one default grub. If that isn’t a problem, it shouldn’t be a problem in UEFI.

[2] - We can created a new bootloader id by “grub-install --bootloader-id=manjarokde” but that will be lost upon a system ‘grub-install’ and needs to be re-done.


#40

All OK. :slight_smile:
HP Z400, KDE, kernel 4.12, ZFS kmod, VirtualBox.