[Stable Update] 2016-11-07 - Mesa, Linux49, Plasma, LibreOffice, Pamac



With the update the KDE dashboard is slow, the issue shows with each alternative.
I try all the dashboard alternative and with “Application Launcher” shows a continuous “application updated” message.
I can’t clic the shortcuts.
This issue happens some time ago… I can’t remember/find the workaround.

For any help to fix this Thanks!


Everything works fine except Libreoffice Calc. When i write anything in a cell the backspace is moving but not deleting the letters.Any help about this?



I had problem after updating my system, my wifi wasn’t working after doing some research in this forum I found the solution, just disable the random mac address like what the OP said:

sudo vi /etc/NetworkManager/NetworkManager.conf

and add:


and then:

killall -SIGHUP NetworkManager


Cannot reproduce this in libreoffice-still. Are you using the fresh-branch of libreoffice? I switched to still because of bugs like this in libreoffice calc.


Thank you for your responce. I found the solution and everything is ok


when you find solution. it’s always good to post it. like this other don’t have to search for it. :wink:


Kicad: segfault in libgobject-2.0.so.0.5000.1 after the last update

Kicad start but when i try to open schematic, pcb design or any other option, Kicad closes suddenly and in the everything.log appear the next messages:

Nov 10 11:29:39 manjaro kernel: kicad[5427]: segfault at 21 ip 00007fcb256ae678 sp 00007ffd5b0e10b0 error 4 in libgobject-2.0.so.0.5000.1[7fcb2568d000+51000]
Nov 10 11:30:07 manjaro kernel: kicad[5459]: segfault at 21 ip 00007f9573dfd678 sp 00007fff512c8480 error 4 in libgobject-2.0.so.0.5000.1[7f9573ddc000+51000]
Nov 10 11:30:33 manjaro kernel: kicad[5492]: segfault at a ip 00007f199a299678 sp 00007fffac90b5c0 error 4 in libgobject-2.0.so.0.5000.1[7f199a278000+51000]
Nov 10 11:31:36 manjaro kernel: kicad[5752]: segfault at 25 ip 00007fd0243a1678 sp 00007fff9efce350 error 4 in libgobject-2.0.so.0.5000.1[7fd024380000+51000]
Nov 10 11:31:52 manjaro kernel: kicad[5785]: segfault at 25 ip 00007f71617bc678 sp 00007ffef1b06c10 error 4 in libgobject-2.0.so.0.5000.1[7f716179b000+51000]


You are right.The solution was to uncomment “#export SAL_USE_VCLPLUGIN=gtk” in two files “libreoffice-fresh.sh” and libreoffice-fresh.csh which are in the folder etc/profile.d


Mesa 13.0.0! Finally OpenGL 4.3 works with the xf86-ati-driver on my Radeon 250E! Dolphin 5.0 performance skyrocketed! :smile:

$ glxinfo | grep version
server glx version string: 1.4
client glx version string: 1.4
GLX version: 1.4
    Max core profile version: 4.3
    Max compat profile version: 3.0
    Max GLES1 profile version: 1.1
    Max GLES[23] profile version: 3.1
OpenGL core profile version string: 4.3 (Core Profile) Mesa 13.0.0
OpenGL core profile shading language version string: 4.30
OpenGL version string: 3.0 Mesa 13.0.0
OpenGL shading language version string: 1.30
OpenGL ES profile version string: OpenGL ES 3.1 Mesa 13.0.0
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10


Kicad: segfault in libgobject-2.0.so.0.5000.1 after the last update

Only fail in x86_64, in x86 Kicad work without problem.


Update went well…except for one thing: on Plasma5 with Akonadi, mysqld uses up to 2GB RAM ! This tends to slow down my computer quite a bit while using it with heavy tasks.

After some searches, it seems jemalloc 4.3.0 introduced a regression which is corrected in 4.3.1.

EDIT: It’s getting worse, mysqld uses up to 3GB RAM now. Is it possible to push jemalloc 4.3.1 sooner as a patch ?


I had a small nasty issue which isn’t strictly related to Manjaro. I’m using Infinality from the Infinality-bundle Arch repository. After update, my font settings were somehow screwed up, and fonts looked ugly. At least I solved by uninstalling, reinstalling and reconfiguring Infinality again:

pacman -S --asdeps freetype2 cairo fontconfig
pacman -S infinality-bundle
fc-presets set



The same issue here.



Moved to here : [Stable Update] 2016-11-19 - Mesa, LibDRM, Kernels, KDE Framework, Grub, Firefox

This thread is of an older release.

[Stable Update] 2016-11-19 - Mesa, LibDRM, Kernels, KDE Framework, Grub, Firefox

update went well for me as usual but ever since then

     systemd-analyze blame
     30.480s updatedb.service
     20.166s man-db.service

those two have been taking longer than usual jacking up my desktop loading time.


Those should be running periodically as scheduled by systemd.
There is no reason they should run on every boot unless they were not able to run for a long time, such as if you turn your machine off each night.


systemctl list-timers --all

to see a list of all these things, and you will notice that quite a few of them are scheduled to run at midnight. If you go days before letting the machine run at that time, and/or you did a lot of updates in the interval, both updatedb and man.db will have a lot of work to to.

for how you might reschedule these to occur when you are out to lunch or something.


mines seem to run in the afternoon …

n/a n/a Fri 2016-11-18 18:44:31 EST 3h 41min ago systemd-readahead-done.timer systemd-readahead-done.service
Sat 2016-11-19 00:00:00 EST 1h 33min left Fri 2016-11-18 13:43:57 EST 8h ago logrotate.timer logrotate.service
Sat 2016-11-19 00:00:00 EST 1h 33min left Fri 2016-11-18 13:43:57 EST 8h ago man-db.timer man-db.service
Sat 2016-11-19 00:00:00 EST 1h 33min left Fri 2016-11-18 13:43:57 EST 8h ago shadow.timer shadow.service
Sat 2016-11-19 00:00:00 EST 1h 33min left Fri 2016-11-18 13:43:57 EST 8h ago updatedb.timer updatedb.service
Sat 2016-11-19 18:58:52 EST 20h left Fri 2016-11-18 18:58:52 EST 3h 27min ago systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service
Thu 2016-12-01 00:00:00 EST 1 weeks 5 days left Tue 2016-11-01 17:39:04 EDT 2 weeks 3 days ago pamac-cleancache.timer pamac-cleancache.service
Thu 2016-12-01 00:00:00 EST 1 weeks 5 days left Tue 2016-11-01 17:39:04 EDT 2 weeks 3 days ago pamac-mirrorlist.timer pamac-mirrorlist.service

i have never seen those two come up at the top in my systemd-analyze till the last update though


Description=Daily man-db cache update


i suppose if i change persistent to = false then i would just manualy update it when i want to instead if it misses its run time


No, persistent refers to this scheduled task, meaning the task stays in the schedule after it runs so as to be available next day, etc.
There are other options that allow you to set a time of day.
See the wiki link I posted.