[Stable Update] 2020-03-14 - Kernels, Plasma 5.18.3, KDE Frameworks 5.67, KDE Apps 19.12.3, Firefox, Kodi

Update was successful on majaro KDE.
Pamac did pop up an error, from the pamac log:

Creating temporary files...
Error: command failed to execute correctly
Reloading device manager configuration...

Snippet from pacman.log, I presume this is where a specific error could be found does not show any error.

[2020-03-14T17:02:56+0100] [ALPM] running '30-systemd-sysctl.hook'...
[2020-03-14T17:02:56+0100] [ALPM] running '30-systemd-tmpfiles.hook'...
[2020-03-14T17:02:56+0100] [ALPM] running '30-systemd-udev-reload.hook'...

Systemd log:

14-03-2020 17:02	systemd-tmpfiles	Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted

Permissions seem fine.

-rw-r--r-- 1 root root 4096 14 mrt 17:29 policy

Edit after some searching. Found a post with a similar problem

$ sudo systemd-tmpfiles --create
Failed to write file "/sys/module/pcie_aspm/parameters/policy": Operation not permitted
$ sudo rm /etc/tmpfiles.d/pcie_aspm_performance.conf 
$ sudo systemd-tmpfiles --create
$ 

Error gone

sudo pacman-mirrors -f 5 && sudo pacman -Syyu

Pamac 9.4.0-rc4-1** should not have been part of this as it is broken. 9.4.0-rc4-2 is the fixed one and added to pamac-dev. I'll revert to 9.3.0 for stable release back. Sorry for the issue. Seems I didn't look the list fully thru.

I am also experiencing this, and it does appear to be related to wifi which will not connect until I enter my password

Linux54 - KDE Plasma.
All good.

My firefox kde integration broke. When I click on "save image as" nothing comes up. I am launching with:
/usr/bin/sh -c "GTK_USE_PORTAL=1 /usr/lib/firefox/firefox %u"

When I launch from a terminal with just firefox I get the gtk file browser.
This was working with 5.17.5 so I'm trying to figure out what's going on from this thread:

Updated the laptop (Manjaro Gnome kernel 5.4.x) via TTY without any issues. Everything is running perfectly.

Of course I did my usual Timeshift backup before applying the update just in case something went wrong.

1 Like

Since we can't go back to 9.3.0 series of pamac I've updated it to the latest source. We are sorry if that created some issues on your end. Please report any issues regarding pamac so we can fix them fast.

Update went smoothly on this 13 year old desktop but it did require a reboot from the terminal. After reboot everything works flawlessly. Manjaro KDE, kernel 5.4.x. Thanks to the team for bringing in a stable Plasma 5.18.3!

Check if you have manjaro-kde-settings-19 installed instead of manjaro-kde-settings, if so install the latter one instead.

For the NOOB.... A message about a reboot should be suggested after major system component(s) update(s). This certainly should be a PAMAC feature worth creating. Since Manjaro is now more a business entity, it makes sense to implement.

Remove this if you have the manjaro-kde-settings-19.0 package installed, it was updated to include this setting globally. Using this environment setting twice will break it.

Note: For anyone else like me that had this manually set globally, either remove your modification or don't install the manjaro-kde-settings-19.0 package. I'm not sure about the manjaro-kde-tx-settings package, though it seems to have been updated the same month. The other manjaro-kde-xxx settings packages do not seem to have been updated with this change.

Desktop: Update went smoothly
Laptop: Update hangs after downloading thunderbird "Download of thunderbird (68.6.0-0.1) finished" and nothing is happening, no error message. I tried cancelling and pamac prints Transaction cancelled, but the Apply button does not become active.
After a reboot, I started the upgrade again and it worked.

I think this should be part of this post. I see an update to pacman just hit the servers and after updating, when I hit refresh databases inside of pacman, it does nothing. Anyone else see this happening?

FOR FIREWALLD USERS:

The firewalld package is messed up and will not upgrade properly. You will need to remove, otherwise the system updates will fail with a load of "the file already exists in filesystem" errors.

OK WTF, the filewalld package will no longer install, and no package owns these files. Now to figure out where these came from:

error: failed to commit transaction (conflicting files)
firewalld: /usr/lib/python3.8/site-packages/firewall/__pycache__/__init__.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/__pycache__/client.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/__pycache__/dbus_utils.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/__pycache__/errors.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/__pycache__/functions.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/__pycache__/fw_types.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/config/__pycache__/__init__.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/config/__pycache__/dbus.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/__init__.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/base.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/ebtables.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/fw.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/fw_config.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/fw_direct.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/fw_helper.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/fw_icmptype.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/fw_ifcfg.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/fw_ipset.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/fw_nm.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/fw_policies.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/fw_service.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/fw_transaction.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/fw_zone.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/icmp.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/ipXtables.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/ipset.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/logger.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/modules.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/nftables.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/prog.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/rich.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/__pycache__/watcher.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/io/__pycache__/__init__.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/io/__pycache__/direct.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/io/__pycache__/firewalld_conf.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/io/__pycache__/functions.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/io/__pycache__/helper.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/io/__pycache__/icmptype.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/io/__pycache__/ifcfg.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/io/__pycache__/io_object.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/io/__pycache__/ipset.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/io/__pycache__/lockdown_whitelist.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/io/__pycache__/service.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/core/io/__pycache__/zone.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/server/__pycache__/__init__.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/server/__pycache__/config.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/server/__pycache__/config_helper.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/server/__pycache__/config_icmptype.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/server/__pycache__/config_ipset.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/server/__pycache__/config_service.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/server/__pycache__/config_zone.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/server/__pycache__/decorators.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/server/__pycache__/firewalld.cpython-38.pyc exists in filesystem
firewalld: /usr/lib/python3.8/site-packages/firewall/server/__pycache__/server.cpython-38.pyc exists in filesystem
Errors occurred, no packages were upgraded.

I really wish maintainers would watch for these kinds of issues before releasing their packages.

The text of the names of installed themes/styles is looking distorted, to see it more clearly try to download those attached images and open it with your image viewer with 100% zoom and you will see the problem.

I just noticed that hibernation option is suddenly missing (already did a reboot). It is also gone in the Energy settings ( Manjaro stable KDE). How do I get it back?

Here is serious bug : Firefox upload/browse button does not open file chooser ! but with Chromium it's working, is there any problem with the new 5.18.3 KDE and Firefox?

Already brought up in this thread, and also discussed elsewhere in the forum.
Please search next time.

I just finished the updates today and this is working on my systems just fine.
image

Make sure you have these packages installed:
Plasma-browser-integration
xdg-desktop-portal
xdg-desktop-portal-kde

and that you have the plasma-integration add-on installed in firefox.

NOTE:
You can not have both xdg-desktop-portal-kde and xdg-desktop-portal-gtk both installed.
You also can not have this setting made twice, globally and locally.

@philm, pipewire version 0.3 is required for Firefox to use GTK_USE_PORTAL=1 for KDE's file dialogs with this update.

Forum kindly sponsored by