[Stable Update] 2017-07-27 - Kernels, VirtualBox, Deepin, Mesa

update
stable

#1

Hi community,

we have updated most of our kernels, added the latest mesa and virtualbox release, worked on deepin and xfce-gtk3. As usual we ship all upstream packages provided by Arch Linux.

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


Current supported Kernels

  • linux310 3.10.106
  • linux312 3.12.74 [EOL]
  • linux316 3.16.46
  • linux318 3.18.62 [EOL]
  • linux41 4.1.42
  • linux44 4.4.78
  • linux48 4.8.17 [EOL]
  • linux49 4.9.39
  • linux410 4.10.17 [EOL]
  • linux411 4.11.12 [EOL]
  • linux412 4.12.3
  • linux413 4.13-rc2
  • linux-RT-LTS 4.9.35_rt25 (x86_64)
  • linux-RT 4.11.8_rt5 (x86_64)

Package Updates (Tue Jul 25 11:27:51 CEST 2017)

  • stable community i686: 365 new and 355 removed package(s)
  • stable community x86_64: 389 new and 362 removed package(s)
  • stable core i686: 17 new and 17 removed package(s)
  • stable core x86_64: 19 new and 17 removed package(s)
  • stable extra i686: 289 new and 294 removed package(s)
  • stable extra x86_64: 305 new and 295 removed package(s)
  • stable multilib x86_64: 10 new and 10 removed package(s)

A detailed list of all package changes can be found here.


  • 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:


#2

why does

sudo mhwd-kernel -l

still show all kernels, which are EOL (even on the unstable branch)?
when will EOL kernels be removed from MHWD (how long after they became EOL)?


#3

OK i update the system this morning , It seems " all "okay but when I suspend the computer and wake up from suspend the system freezes With the kernel 4.12 I returned to the 4.9 works well .


#4

yes this updates fixed 1 issue but not an other one .
Fix = kde plasma hangs on games or TS3 or Steam when starting
Not fixed = Notification in plasma still 1px width

Edit: bottom right corner


#5

Two machines updated, so far so good. KDE edition. Update with CLI.


#6

All is good, Xfce, 4.12 kernel.

Not even any subversive colour changes to be seen. :wink:


#7

Hello,
Just installed the latest update and the system boots to black screen with single blinking cursor.
I got into the system with ctl-alt-f3,
sudo pacman -Syu shows all is up to date
sudo pacman -Sy shows conflict: manjaro-system-20170406-5
after update, conflict continues to show
There is no error filed, just the black screen and cursor.
I also tried booting from live disk = same result
I also tried Manjaro advanced options fallback, note: kernel for both fallback and regular boot was 4.9.39-1-Manjaro x64
My GPU is Nvidia 1070
I’ve used Manjaro for several months w/o a problem. Any ideas as to a solution?


#8

Hi @philm

All OK in 3 computers.

I installed new kernel version 4.12 from Manjaro Settings Manager and the version is 4.12.2-1 not 4.12.3. I run the pacman commands for regenerate the mirrors and check updates and there aren’t updates for 4.12.3.

Good job.

Edit
Today 28/7 I have received the new updates and all OK.


#9

Did your update complete successfully with no errors? You can check by scrolling to the bottom of /var/log/pacman.log. Also check for .pacnew file pacman messages, which are conf files that may need to be manually integrated (pacman doesn’t clobber conf files).

What display driver

mhwd -li

What errors are being logged?

journalctl -p err -b

Any xorg errors in /var/log?

Kernel updates included, could be initramfs issue, you could try

sudo mkinitcpio -P

You could try installing kernel 4.12 and booting into this

sudo mhwd-kernel -i linux412

#10

No problem on KDE


#11

Smooth update without issues, thank you!

P.S. @philm : I’ve notice that guayadeque has been removed from our repository. I’m still using it, despite the recent graphical issue, and maybe other users are doing it, so, could you reintroduce it in our repos (maybe mentioning the bug in the description). It’s still a great music player, still usable in most of its features.


#12

ha, Virtualbox is out of date already. :smiley:


#13

5.1.26 was only just released upstream - Arch don’t have it yet so :stuck_out_tongue:


#14

Hahaha, well it was just funny when I upgraded and then the new virtualbox started up with a message announcing a new version was available. :grin:


#15

No update errors were noted upon update completion.

/var/log/pacman.log: At the end: Alpha running 'textinfo -install hook… ^@ many of the ^@
one line said: image generation successful. the last line says: synchronizing package lists

display driver: video-nvidia version: 2017.03.12 freedriver: False Type: PCI

Logged Errors:

journalctl - p err -b: -- Logs begin at Tue 2017-07-04 11:42:37 EDT, end at Thu 2017-07-27 16:07:29 EDT. --
Jul 27 16:01:47 bill-pc kernel: ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failu
Jul 27 16:01:47 bill-pc kernel: ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (2017
Jul 27 16:01:47 bill-pc kernel: ACPI Exception: AE_NOT_FOUND, (SSDT:xh_rvp08) while loading ta
Jul 27 16:01:47 bill-pc kernel: ACPI Error: 1 table load failures, 8 successful (20170303/tbxf
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
Jul 27 16:01:48 bill-pc systemd-udevd[238]: Invalid rule /etc/udev/rules.d/80-canon_mfp.rules:
lines 1-34

Xorg errors: didn’t see any

sudo mkinitcpio -P: I just noticed it was P and not p, I will try -P after this message is sent.

sudo mhwd -kernel -i linux412: This got my system running again. I hope to be able to update beyond this point, in the future.

Thanks for the help.


#16

After the update I cannot open a picture at all with Gwenview.
Opening with the terminal results this:

[me@meHP Schreibtisch]$ gwenview
QApplication: invalid style override passed, ignoring it.
kf5.kwidgetsaddons: Invalid pixmap specified.
QTimeLine::setDuration: cannot set duration <= 0
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "mtp"
kf5.kwidgetsaddons: Invalid pixmap specified.
QTimeLine::setDuration: cannot set duration <= 0
kf5.kwidgetsaddons: Invalid pixmap specified.
QTimeLine::setDuration: cannot set duration <= 0
kf5.kwidgetsaddons: Invalid pixmap specified.
QTimeLine::setDuration: cannot set duration <= 0
kf5.kio.core: Refilling KProtocolInfoFactory cache in the hope to find "mtp"
kf5.kwidgetsaddons: Invalid pixmap specified.
QTimeLine::setDuration: cannot set duration <= 0
KServiceTypeTrader: serviceType "ThumbCreator" not found
KServiceTypeTrader: serviceType "ThumbCreator" not found
KServiceTypeTrader: serviceType "ThumbCreator" not found

I uninstalled Gwenview and then installed it again. Same problem.
What to do?
Thx for help.


#17

I remember mentions of some scheduler issues with the 4.12 kernel because the default scheduler changed. Has that been resolved?


#18

Append: Note: the Logged Errors file sent was after the kernel update was applied, I had noted these other errors earlier, when I first looked up the journalctl -p err -b file: see below:
Failed to insert ‘nvidia’: Exec formaterror
Failed to start kernel modules
Invalid rules /etc/udev/rules … systemd devd[225] there were a few of these.


#19

-question about vbox , does it work with linux13rc2 ?

i have this error with only kernel 4.13rc2

[Firmware Bug]: TSC DEADLINE disabled due to Errata ; pleaze update microcode to version 0xb2 ( or later )
( CPU is skylake 6700K )

vbox not loaded
and

error on Lightdm ( exit 1 , maybe vbox not loaded ) 
and Dunst notification deamon failed

#20

And this all worked before the update?
How long had it been since your last update?
Did you reboot after the update? (you should always reboot after a kernel update).
What Kernel?
What DE?