[Stable Update] 2017-05-19 - Kernels, LibreOffice, Mesa, Thunderbird, Cinnamon



nope - just the most recent one in stable. 4.9.28-1-MANJARO is the recommended LTS


The Update itself works fine.

But Kernel 4.11.1 are not Booting with Catalyst Drivers.
When I switch to “video-ati” the System Uninstalls all Xorg Packages too, BUT no other Packages was installed, so the System is without Xorg Server and not Bootable at this Point.

When I install Xorg and make a Reboot, it hangs at the same Step. (Switching from Plymouth to Login Screen.

At this Point The System is not Bootable anymore.

With a Live-USB Stick I was able to get back to old State: Kernel 4.10 + Catalyst.



It’s already in unstable branch now! :slight_smile:


It used to be fairly perilous, i was always anxious, but since January perhaps not any more.

Upgrading is one of those activities I am looking forward to no matter how crazy that might sound.

Although I am still a true definition of a noob, I have gathered 4 or 5 commands that are required, 2 or 3 that may save my life,
and with this arsenal plus suggestions from Phil in post #1 as well as all the input from our dear users -

I have never felt safer in my entire life, ie. from 2000 when my Dad bought my 1st desktop PC with W 98.

Manjaro is #1

p.s. I have never upgraded any of my windows systems aside from SP upgrades.


Since this update Octopi no longer detects/shows AUR packages needing update.
Oddly enough Octopi Notifier warns there are AUR updates available.

[Stable Update] 2017-06-06 - Plasma 5, Boost, Deepin, Mesa, GCC

After the update Steam no longer works with firejail due to this bug.
Otherwise a smooth update.


Oops, function keys from screen brightness doesn’t work any longer. Sound does work, but that’s the only function.


I can confirm this on KDE Edition.


I’m on KDE also. Is anyone having the same problem on other editions?


xps9550 KDE plasma, smooth update


With the Mate desktop this update is causing the Clearlooks-Phenix theme (a theme meant to work with GTK+ 3) to render icons incorrectly. Icons in the notification area in the panel render much larger than all the rest of the icons in the panel (and force the panel to expand to a larger size). This also happens with the TraditionalOK theme (a Clearlooks style them), which is part of the default Mate themes packages. This was an issue in LMDE Mate, after some recent Mate updates, but was fixed. Looking at the Arch repos, it seems like I have the most recent Mate packages, including mate-panel. So not sure what’s going on and why Manjaro is having a problem, where LMDE is not.


The same happened to my system after updating. I have the Cinnamon Version. I can still change brightness via the applet.


I am also having this problem


Suddenly I discovered that ibus doesn’t work on some kde/qt applications like kate, but some of them (like KWrite) still works which is strange. Not sure if it’s related to the update.

Edit: The problem was caused by firejail.


Indeed, applet works fine


I ment changing to brightness with the battery indicator works fine :wink:


No update issues here although I am curious why gcc was not updated to version 7.1.


Because it is currently still in Arch Testing. We will ship it as soon as it moves to Arch stable - this will likely make a pile of rebuild necessary also … … :stuck_out_tongue:


This affects me too. KDE Edition here. :slight_smile:


Other major problems:

  • Plasma takes a very long time to load. It had never taken so much time before.

  • MEGAsync doesn’t work anymore. It says:

    MEGAprivate ERROR DUMP
    Application: MEGAsync
    Version code: 3001.0
    Module name: megasync
    Operating system: Linux
    System version: #1 SMP PREEMPT Sun May 14 13:45:56 UTC 2017
    System release: 4.10.16-1-MANJARO
    System arch: x86_64
    Error info:
    Segmentation fault (11) at address 0x32
    /usr/bin/megasync() [0x5ca52a]
    /usr/bin/megasync() [0x5ca52a]
    /usr/lib/libssl.so.1.1(+0x2777e) [0x7ff771dd277e]
    /usr/lib/libssl.so.1.1(+0x39f0b) [0x7ff771de4f0b]
    /usr/lib/libssl.so.1.1(+0x3770f) [0x7ff771de270f]
    /usr/lib/libssl.so.1.1(SSL_do_handshake+0x41) [0x7ff771ddae91]
    /usr/lib/libcurl.so.4(+0x5d90c) [0x7ff77673090c]
    /usr/lib/libcurl.so.4(+0x5e822) [0x7ff776731822]
    /usr/lib/libcurl.so.4(+0x610ab) [0x7ff7767340ab]
    /usr/lib/libcurl.so.4(+0x13452) [0x7ff7766e6452]
    /usr/lib/libcurl.so.4(+0x3b04e) [0x7ff77670e04e]
    /usr/lib/libcurl.so.4(+0x3c708) [0x7ff77670f708]
    /usr/lib/libcurl.so.4(curl_multi_socket_action+0x17) [0x7ff77670f7f7]
    /usr/bin/megasync() [0x5c8657]
    /usr/bin/megasync() [0x5d03a4]
    /usr/bin/megasync() [0x52ed3d]
    /usr/bin/megasync() [0x5be0d9]
    /usr/bin/megasync() [0x5be168]
    /usr/lib/libQt5Core.so.5(+0xad6d8) [0x7ff7739d06d8]
    /usr/lib/libpthread.so.0(+0x72e7) [0x7ff77370a2e7]
    /usr/lib/libc.so.6(clone+0x3f) [0x7ff772b8f54f]

I must say that the 2017-05-12 update had never been shown as available by Octopi notifier, so maybe I have made two updates at once.

Anybody can please help me solve these problems?


megasync is an AUR package. It depends on openssl which was recently updated.
It might be enough to rebuild megasync - which simply means reinstalling it with yaourt.
If you still have problems you should report the issue to the maintainer.