[Stable Update] 2018-12-14 - Kernels, Nvidia, Deepin, Cinnamon, Pamac, Browsers, Thunderbird, Wine

update
stable

#1

Hi community,

Welcome to another stable update.

So what do we have with this one?

  • We updated most of our Kernels
  • Nvidia 415.22 got added
  • The Matcha theme got further fixes and updates
  • Added the latest browsers like Palemoon, Firefox and Opera
  • Deepin and Cinnamon updates
  • Pamac got released as v7.3.2
  • Thunderbird got updated to v60.3.3
  • Wine 4.0 comes along. Test the first release candidate
  • all the regular haskell, php and python updates

We hope with all these changes Manjaro to be more efficient for you all.


#ManjaroBook - shipping worldwide since this Winter!

manjarobook

We are happy to announce our partnership with LINUX-SERVICE.BE BVBA from Belgium. With them we established a wider range of laptops and PCs optimized for Manjaro - starting from 390 €- available to be shipped worldwide. All models are customizable as you may need them. Check out our new line-up in the shop.


Manjaro v18.0.1 RC2 released!

If you are curious about the latest Manjaro-Illyria 18.0.1 release, you now have the opportunity to download XFCE Edition with the latest 4.13 packages, aswell as our most recent styling efforts. Our KDE fans may try our KDE Edition with the latest KDE v5.14 instead. And our GNOME fans may try our Gnome Edition with the latest GNOME v3.30.


Current supported Kernels

  • linux316 3.16.61
  • linux318 3.18.128 [EOL]
  • linux44 4.4.166
  • linux49 4.9.144
  • linux414 4.14.87
  • linux417 4.17.19 [EOL]
  • linux418 4.18.20 [EOL]
  • linux419 4.19.8
  • linux414-rt 4.14.78_rt47
  • linux416-rt 4.16.18_rt11
  • linux418-rt 4.18.16_rt9

Sync Package Updates (Sun Dec 9 13:45:39 CET 2018)

  • stable community x86_64: 726 new and 717 removed package(s)
  • stable core x86_64: 23 new and 23 removed package(s)
  • stable extra x86_64: 216 new and 221 removed package(s)
  • stable multilib x86_64: 14 new and 19 removed package(s)

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

  • No issue, 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:


Display resolution different between "live" and "installed" XFCE
#2

Known issues and solutions

This is a wiki post; please edit as necessary.
Please, consider subscribing to the Stable Updates Announcements RSS feed

“warning: systemd: local (239.303-1) is newer than core (239.6-2)” What do I do?

As said in this announcement, systemd packages has been downgraded to an older version. Hence, as long as the version installed on your system will be on a higher version, you’ll receive a warning.

If you already have systemd 239.303 on your system and you have no problem with it, you can just ignore the warning and continue to use systemd 239.303. There’s no need to do any action.

If you are still interested to downgrade systemd to 239.6, you can do the downgrade with pamac upgrade --enable-downgrade or sudo pacman -Syyuu.


Items from previous update sets

How do I do updates via TTY-terminal?

  • Press CTRL+ALT+F2 (or F3, F4, F5, F6) to go into a pure command line interface.
  • Log in with your credentials.
  • Once logged in, you’ll have access to a CLI shell, like if you were using a terminal. Use pamac upgrade or sudo pacman -Syyu (or other equivalent command) to update your system.

To go back to your regular desktop, press CTRL+ALT+F7. On some systems, it can be CTRL+ALT+F1 instead.


i3 changed its default config path

It seems that (from version >= 4.16) i3 is looking for its configuration in ~/.config/i3/config instead of ~/.i3/config.
Copy your config to the new path and all should work as before. (reported from an i3-gaps user).


I can’t open Nemo with elevated privileges (as root)

Workaround found: Use the dbus-x11 package instead of the regular dbus package. This package is available in the official repositories and provides dbus compiled without the --without-x option.

To replace dbus with dbus-x11 package, simply install dbus-x11 with your favorite package manager: dbus will be replaced by dbus-x11.


Pamac: “Failed to commit transaction - Transaction not prepared” at the end

So far, it has only been a false alarm: updates are applied successfully.


AMD-Ucode introduction

Unless you’ve already done this previously, All users of AMD-APUs/CPUs should install this update like this:

sudo pacman -Syyu
sudo pacman -S amd-ucode
sudo pacman -R intel-ucode
sudo update-grub

Step 3 is optional.


Rebuilding fontconfig cache: failed to write cache

Please ignore this message. Upstream already works on a solution. More about the issue here.


LibreOffice has no window decoration in KDE

New line export SAL_USE_VCLPLUGIN=gtk3_kde5, once merged into existing /etc/profile.d/libreoffice-fresh.sh , fixes a moderately longterm issue. If it doesn’t work for you, you may use gtk instead of gtk3_kde5 as UI framework.


Installing glibc (2.28-4) breaks the dependency “glibc=2.27” required by lib32-glibc

Install the update either:

  • from terminal: sudo pacman -Syu or;
  • with Octopi instead of Pamac.

Something using Perl/Python/glibc broke

Rebuilds needed!

  • If it’s an AUR package, try to reinstall it from AUR. It most likely needs to be rebuilt.
  • If it’s a repo package, please report and check back regularly for updates.

I’ve lost a Thunderbird addon/feature

Thunderbird 60 disables incompatible addons by default. There’s an about:config switch should you want to force-enable the addon, but many addons simply will not work with the newer Quantum-based Thunderbird.

Read more about Thunderbird 60 here: Thunderbird 60


Firefox - WebGL not working anymore

You may try the following solution:

Open about:config and set security.sandbox.content.read_path_whitelist to /sys/.


libutf8proc>=2.1.1-3 update may require manual intervention

This should normally be automatically fixed via manjaro-system update.

The libutf8proc package prior to version 2.1.1-3 had an incorrect soname link. This has been fixed in 2.1.1-3, so the upgrade will need to overwrite the untracked soname link created by ldconfig. If you get an error

libutf8proc: /usr/lib/libutf8proc.so.2 exists in filesystem

when updating, use


pacman -Suy --overwrite usr/lib/libutf8proc.so.2

to perform the upgrade.


Pamac: “Invalid or corrupted package.”

If you receive an “Invalid or corrupted package.” error message with Pamac and if the details contains an output similar to the following:

Details
Synchronizing package databases...
Starting full system upgrade...

Preparing...
Resolving dependencies...
Checking inter-conflicts...
Downloading...
Downloading manjaro-system-20180716-1-any.pkg.tar.xz...
Checking keyring...
Checking integrity...
Loading packages files...
Checking file conflicts...
Checking available disk space...
Upgrading manjaro-system (20180702-1 -> 20180716-1)...
==> Fix libutf8proc upgrade ...
resolving dependencies...
looking for conflicting packages...

Packages (1) libutf8proc-2.1.1-4

Total Download Size:   0.05 MiB
Total Installed Size:  0.32 MiB
Net Upgrade Size:      0.00 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
downloading libutf8proc-2.1.1-4-x86_64.pkg.tar.xz...
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
upgrading libutf8proc...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
Running post-transaction hooks...
Arming ConditionNeedsUpdate...
Warning: lock file missing /var/lib/pacman/db.lck
Starting full system upgrade...
Resolving dependencies...
Checking inter-conflicts...
Error: could not open file /var/lib/pacman/local/libutf8proc-2.1.1-2/files: No such file or directory
Warning: could not fully load metadata for package libutf8proc-2.1.1-2

Failed to prepare transaction:
invalid or corrupted package

Try the following steps: close Pamac window first, then launch it again and start the update procedure again. It should continue from where it left off.


Issues with folder view widget in KDE v5.13

KDE introduced a new setting for icon sizes. Now you’re able to define also the size for your panel. If you have a high-DPI display, you may want to increase the value. This will fix the display issue with given widget.

icon-kde-513

Pulseaudio changes

With this update we have a /etc/pulse/default.pa.pacnew. It may be necessary to merge (some lines related to “GSettings” in /etc/pulse/default.pa ) if ‘default.pa’ has been customised.

File conflict engrampa.tap

thunar-archive-plugin: /usr/lib/xfce4/thunar-archive-plugin/engrampa.tap exists in filesystem (owned by engrampa-thunar-plugin)

thunar-archive-plugin has added native support for the Engrampa archive manager. engrampa-thunar-plugin is no longer needed. Remove engrampa-thunar-plugin to continue with the update.


Black screen while updating and other stuff
#3

@philm
some of the german repos have chromium at 71.0.3578.80 (like alpix and moson) instead of 71.0.3578.98 (which is right in ragenetwork), so pamac shows a warning about different versions between the installed one (.98) and the one in the extra repository (.80)


#4

Problem on two computers
A small report

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1)
linux419-nvidia-390xx-390.87-7

Dez 14 21:40:02 StudioMB kernel: ------------[ cut here ]------------
Dez 14 21:40:02 StudioMB kernel: Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
Dez 14 21:40:02 StudioMB kernel: WARNING: CPU: 5 PID: 741 at mm/usercopy.c:83 usercopy_warn+0x7d/0xa0
Dez 14 21:40:02 StudioMB kernel: Modules linked in: bnep nls_iso8859_1 nls_cp437 vfat fat input_leds joydev hid_logitech_hidpp intel_rapl hid_logitech_dj mousedev hid_cherry hid_generic btusb btrtl btbcm x86_pkg_temp_thermal btintel blu>
Dez 14 21:40:02 StudioMB kernel:  uinput nvidia_drm(POE) nvidia_modeset(POE) drm_kms_helper drm agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nvidia(POE) ipmi_devintf ipmi_msghandler vboxpci(OE) vboxnetflt(OE) vboxnetadp(OE) vbo>
Dez 14 21:40:02 StudioMB kernel: CPU: 5 PID: 741 Comm: Xorg Tainted: P           OE     4.19.8-2-MANJARO #1
Dez 14 21:40:02 StudioMB kernel: Hardware name: ASUS All Series/X99-DELUXE II, BIOS 1802 09/05/2017
Dez 14 21:40:02 StudioMB kernel: RIP: 0010:usercopy_warn+0x7d/0xa0
Dez 14 21:40:02 StudioMB kernel: Code: ab 89 41 51 4d 89 d8 48 c7 c0 c5 91 aa 89 49 89 f1 48 89 f9 48 0f 45 c2 48 c7 c7 f0 a4 ab 89 4c 89 d2 48 89 c6 e8 7d 4f e1 ff <0f> 0b 48 83 c4 18 c3 48 c7 c6 26 79 aa 89 49 89 f1 49 89 f3 eb 96
Dez 14 21:40:02 StudioMB kernel: RSP: 0018:ffffb7ec42517b60 EFLAGS: 00010286
Dez 14 21:40:02 StudioMB kernel: RAX: 0000000000000000 RBX: ffff9a39c2d9dcb0 RCX: 0000000000000000
Dez 14 21:40:02 StudioMB kernel: RDX: 0000000000000007 RSI: ffffffff89aa7926 RDI: 00000000ffffffff
Dez 14 21:40:02 StudioMB kernel: RBP: 0000000000000003 R08: 0000000000000001 R09: 00000000000004cc
Dez 14 21:40:02 StudioMB kernel: R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000001
Dez 14 21:40:02 StudioMB kernel: R13: ffff9a39c2d9dcb3 R14: 0000000000000000 R15: ffff9a39c2d9dcf8
Dez 14 21:40:02 StudioMB kernel: FS:  00007f4354594e00(0000) GS:ffff9a39efb40000(0000) knlGS:0000000000000000
Dez 14 21:40:02 StudioMB kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dez 14 21:40:02 StudioMB kernel: CR2: 00007f4350c50d20 CR3: 0000000403ff8003 CR4: 00000000003606e0
Dez 14 21:40:02 StudioMB kernel: DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
Dez 14 21:40:02 StudioMB kernel: DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] [10de:1200] (rev a1)
linux419-nvidia-390xx-390.87-7

Dez 14 20:38:19 hometheater kernel: ------------[ cut here ]------------
Dez 14 20:38:19 hometheater kernel: Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'nvidia_stack_cache' (offset 11440, size 3)!
Dez 14 20:38:19 hometheater kernel: WARNING: CPU: 6 PID: 568 at mm/usercopy.c:83 usercopy_warn+0x7d/0xa0
Dez 14 20:38:19 hometheater kernel: Modules linked in: bnep nls_iso8859_1 nls_cp437 vfat fat snd_hda_codec_hdmi intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp cxd2099 snd_hda_codec_realtek joydev snd_hda_codec_generic iTCO_wd>
Dez 14 20:38:19 hometheater kernel:  pcspkr videodev mei_me media i2c_i801 mei lpc_ich evdev mac_hid pcc_cpufreq wmi uinput nvidia_drm(POE) nvidia_modeset(POE) drm_kms_helper drm agpgart syscopyarea sysfillrect sysimgblt fb_sys_fops nvi>
Dez 14 20:38:19 hometheater kernel: CPU: 6 PID: 568 Comm: Xorg Tainted: P           OE     4.19.8-2-MANJARO #1
Dez 14 20:38:19 hometheater kernel: Hardware name: System manufacturer System Product Name/P8Z68-V PRO GEN3, BIOS 3802 01/15/2015
Dez 14 20:38:19 hometheater kernel: RIP: 0010:usercopy_warn+0x7d/0xa0
Dez 14 20:38:19 hometheater kernel: Code: 0b ac 41 51 4d 89 d8 48 c7 c0 c5 91 0a ac 49 89 f1 48 89 f9 48 0f 45 c2 48 c7 c7 f0 a4 0b ac 4c 89 d2 48 89 c6 e8 7d 4f e1 ff <0f> 0b 48 83 c4 18 c3 48 c7 c6 26 79 0a ac 49 89 f1 49 89 f3 eb 96
Dez 14 20:38:19 hometheater kernel: RSP: 0018:ffff912042867b60 EFLAGS: 00010286
Dez 14 20:38:19 hometheater kernel: RAX: 0000000000000000 RBX: ffff89e37865acb0 RCX: 0000000000000000
Dez 14 20:38:19 hometheater kernel: RDX: 0000000000000007 RSI: ffffffffac0a7926 RDI: 00000000ffffffff
Dez 14 20:38:19 hometheater kernel: RBP: 0000000000000003 R08: 0000000000000001 R09: 0000000000000445
Dez 14 20:38:19 hometheater kernel: R10: 0000000000000001 R11: 0000000000000000 R12: 0000000000000001
Dez 14 20:38:19 hometheater kernel: R13: ffff89e37865acb3 R14: 0000000000000000 R15: ffff89e37865acf8
Dez 14 20:38:19 hometheater kernel: FS:  00007f8b8c713e00(0000) GS:ffff89e38eb80000(0000) knlGS:0000000000000000
Dez 14 20:38:19 hometheater kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dez 14 20:38:19 hometheater kernel: CR2: 00007f8b88dd4d20 CR3: 00000003f8dd2002 CR4: 00000000000606e0


#5

chromium 71.0.3578.98-0 got removed by this update. It was not added to testing branch. @jonathon: needs to be readded.


#6

All i get is:

error: failed to commit transaction (conflicting files)
glbinding: /usr/bin/glinfo exists in filesystem (owned by mesa-demos)
Errors occurred, no packages were upgraded.

And does not update?

If i try to remove mesa-demos (32 and 64) i get a warning “inxi optionally requires mesa-demos: inxi -G glx info”

So is it safe for me to remove mesa-demos?

Removed mesa-demos and update installed fine, rebooted then tried to re-install mesa-demos but i now get “conflicting files:
mesa-demos: /usr/bin/glinfo already exists in filesystem” and it fails to install.

What will i do without “glxgears”:open_mouth:


#7

Updated without issues this time!


#8
warning: ca-certificates-mozilla: local (3.40.1-1) is newer than core (3.40-2)
warning: cryptsetup: local (2.0.6-1) is newer than core (2.0.5-1)
warning: gcc: local (8.2.1+20181127-1) is newer than core (8.2.1+20180831-1)
warning: gcc-libs: local (8.2.1+20181127-1) is newer than core (8.2.1+20180831-1)
warning: lib32-gcc-libs: local (8.2.1+20181127-1) is newer than core (8.2.1+20180831-1)
warning: linux414: local (4.14.87-1) is newer than core (4.14.85-1)
warning: mhwd-nvidia: local (1:415.22-1) is newer than core (1:415.18-1)
warning: nss: local (3.40.1-1) is newer than core (3.40-2)
warning: openssl-1.0: local (1.0.2.q-1) is newer than core (1.0.2.p-1)
warning: perl: local (5.28.1-1) is newer than core (5.28.0-1)
warning: sqlite: local (3.26.0-1) is newer than core (3.25.3-1)

Is it safe to ignore these warnings?
Since they are a lot of warnings, I’m afraid that these may break my system or something like that.


#9

That’s odd, you actually have the current version for each of them. It’s weird that you have such warnings.


#10

At the end of upgrading my KDE Lappy via Pamac, when i reviewed the transcript/log prior to rebooting [ie, i have not yet rebooted it], i saw this:

Upgrading libvirt (4.8.0-2 -> 4.9.0-1)...
Configuring libvirt...
>>> You may need to run 'rm -rf ~/.libvirt'

May need to? How would i know / what signs should i seek in order to know if i should do this or not?

Given that the purpose of this package is described as:

libvirt

API for controlling virtualization engines (openvz,kvm,qemu,virtualbox,xen,etc)

…is the answer to my question simply that i will otherwise discover that my VB VMs won’t run properly, or even maybe not run at all?


#11

Hi, i am getting these errors during update :

(62/62) checking for file conflicts                                                              [#########################################################] 100%
error: failed to commit transaction (conflicting files)
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/__pycache__/pyproject.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__init__.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/__init__.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/autocompletion.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/base_command.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/cmdoptions.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/main_parser.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/parser.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/__pycache__/status_codes.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/autocompletion.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/base_command.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/cmdoptions.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/main_parser.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/parser.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/cli/status_codes.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/models/__pycache__/candidate.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/models/__pycache__/format_control.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/models/__pycache__/link.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/models/candidate.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/models/format_control.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/models/link.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/pyproject.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/req/__pycache__/constructors.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/req/constructors.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/utils/__pycache__/compat.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/utils/__pycache__/models.cpython-37.pyc exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/utils/compat.py exists in filesystem
python-pip: /usr/lib/python3.7/site-packages/pip/_internal/utils/models.py exists in filesystem
Errors occurred, no packages were upgraded.
Error installing repo packages

any ideas what i should do?


#12

Smooth sailing after the update and reboot :sunglasses:


#13

libvirt shouldn’t be required by virtualbox. Were you playing with virt-manager or something similar at some point in the past?

I wouldn’t expect it to be a major issue but you could always take a look at what brought libvirt in as a dependency.

EDIT: It is probably also a dependency of gnome-boxes if you use that.


#14

just dropping by to say thanks for the updates :slight_smile:
no problems so far on XFCE.


#15

Ta heaps for your reply. Indeed i’ve now found more info since my other post:

  1. Post-reboot of Lappy, my one-only VB VM still runs just fine.
  2. My Tower [to which i’ve not yet applied this update] also has libvirt… [golly!]
  3. Looking in Pamac i’ve solved the mystery i think. libvirt is a dependency for libvirt-glib, which in turn is a dependency for gnome-boxes. Why in hades do my KDE machines both have gnome-boxes installed? --> because [you might remember from a slew of relatively recent posts elsewhere from me] over the past ~month’ish i [foolishly?] decided to install GNOME as a 2nd DE in both computers, & gnome-boxes simply came along for the ride. Given i have no need for g-b, & given it seems not to be needed by any other package, i think my logical next step might be simply to uninstall g-b, which should then also remove those other two packages.
  4. I should not have wasted the forum’s time by posting, but instead should have been more diligent in my investigation. I’m off to the Naughty Corner now…

EDIT: Oh you rascal - you edited your post just before i added mine!! :laughing:


#16

search python-pip


#17

I’ve updated my KDE+GNOME Lappy, my Xfce & Cinnamon & KDE & enlightenment VMs … all good. Was getting ready to update my primary pc [KDE+GNOME Tower], when i noticed the ambient light fading prematurely [Sat arvo, here]. Looked at the weather radar map & saw why:

Summary

20181215_004

My arrow shows the thunderstorm’s trajectory, & i live immediately below the pic’s bottom rhs corner.

Discretion being the better part of valour, some say, so i shan’t risk a power-cut mid update… looks like it’s necessarily deferred til tomorrow, for safety’s sake. Rats.


#18

This time without any problems.
Lesson learned … updated after booting into text mode.
Kernel 4.19 / Cinnamon / new systemd version


#19

Smooth update.
Reminder: After updating to php-7.3 all AUR php extensions have to be rebuilt (e.g. php-redis, php-imagick, …)


#20

I also have this issue.

one solution would be to uninstall python-pip like:

sudo pacman -R python-pip

But that would remove python packages that you may need as well.

I started a thread for this issue too: