[Stable Update] 2019-05-17 - Kernels, Grub, KDE, Deepin, Gnome, XFCE, LibreOffice, Bash, Systemd

Hello community,

I am happy to announce another Stable Update!

This update holds the following changes:

  • We ship another set of kernel point releases, including both our realtime kernels,
  • Browsers palemoon, chromium and falkon got updated
  • Also our system backup tool backintime got renewed, which was much requested
  • Following Archlinux we are finally deprecating qt4. No reason to worry if you are still using and legacy qt4 dependent application, as of course you can just keep your qt4 installed, for now.
  • Calamares got updated and rebuild against kpmcore 4.0
  • Grub package got redesigned to support also 32bit UEFI installs. Hopefully the languages bug is also solved by this.
  • KDE-Dev ISO got updated and therefore all KDE-Git packages aswell
  • Latest addition to KDE-Dev is a new notification system. You can try it with our ISO.
  • Most of our Kernels got updated. Some might had noticed that dmesg is now restricted to root. To rave you can go here.
  • We added linux52 in its current git snapshot. Few extramodules build, but not all yet!
  • XFCE-GTK3 got renewed packages. The issue with Nvidia and XFWM4-GTK3 got fixed.
  • Also Gnome got updated to 3.32.2 plus needed Gnome-Extensions.
  • Plasma is now at 5.15.5
  • KDE Apps is now at 19.04.1
  • LibreOffice is now att 6.1.6
  • Bash got some security fixes
  • Systemd got updated to its latest stable updates
  • Deepin has newer packages to provide a better experience
  • Mesa is now at 19.0.4
  • For all using Haskell, you find now the latest updates in our repos.

Give us the usual feedback and let us know what you think about this update.


Current supported Kernels

  • linux316 3.16.67
  • linux318 3.18.139 [EOL]
  • linux44 4.4.179 (no legacy nvidia-340 module!)
  • linux49 4.9.175
  • linux414 4.14.118
  • linux419 4.19.42
  • linux420 4.20.17 [EOL]
  • linux50 5.0.15
  • linux51 5.1.1 (few extramodules build, but not all yet!)
  • linux51 5.2-rc0 (few extramodules build, but not all yet!)
  • linux419-rt 4.19.37_rt19
  • linux50-rt 5.0.14_rt9

Package Updates (Wed May 15 06:17:42 CEST 2019)

  • stable community x86_64: 1722 new and 1725 removed package(s)
  • stable core x86_64: 40 new and 38 removed package(s)
  • stable extra x86_64: 834 new and 921 removed package(s)
  • stable multilib x86_64: 26 new and 47 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:

36 Likes

Security Issue

Zombieload Attack

With all current supported kernels you are vunerable to the new reported MDS Issue. Upstream released already needed patches for the following kernel series: 5.1, 5.0, 4.19, 4.14 and 4.9. We will try to provide them as soon as possible, after internal testings.

Affected are Intel CPUs. Here the list of non affected CPUs:

  • Processors from AMD, Centaur and other non Intel vendors
  • Older processor models, where the CPU family is < 6
  • Some Atoms (Bonnell, Saltwell, Goldmont, GoldmontPlus)
  • Intel processors which have the ARCH_CAP_MDS_NO bit set in the IA32_ARCH_CAPABILITIES MSR.

Contain patches that have only seen the "public eye" for about 5 minutes. So be forewarned, they might break things, they might not build, but hopefully they fix things. Odds are upstream will be fixing a number of small things in this area for the next few weeks as things shake out on real hardware and workloads. So don't think you are done updating your kernel, you never are done with that, at least on Intel CPUs. Intel will additionally provide needed microcode updates to fix things from their end too.

Additional information about this issue can be found here.

8 Likes

Known issues and solutions

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


Linux 5.1 - Critical bug found, may lead to data loss

May 21st, 2019: A critical bug has been found in Linux 5.1. It is related to TRIM commands issued on SSDs. Official announcement here.

It is unclear who is affected exactly, as information given on sources doesn't match well. However, if you use an SSD, you are unsure if you are affected or not and you do not want to take any chance, we strongly recommend you to switch to another kernel such as Linux 5.0 or Linux 4.19 immediately for now.

If you do not use Linux 5.1 and planned to do jump on it, of course, we recommend not to use Linux 5.1 for now.

May 22, 2018: We added a patch in order to solve this issue in our linux51 5.1.4-1 package. For now, it is only in Testing and Unstable.

The content of that patch is available on our Gitlab: https://gitlab.manjaro.org/packages/core/linux51/blob/master/0001-dm-make-sure-to-obey-max_io_len_target_boundary.patch

May 26, 2019: linux51 5.1.4-1 is now on Stable, released in an update set published today. See announcement here. Please update your system.


signature from "Helmut Stult (schinfo) <helmut.stult@schinfo.de>" is marginal trust

Update manjaro-keyring first. For more options read this thread:


Linux 5.1 - Which extra modules are currently missing?

As said in the announcement, while the newest Linux version has been released in this update set, not every extra modules are currently available in our official repositories. Before jumping on Linux 5.1, please verify if you do not need any of those missing extra modules on your system.

(Last verification: May 18, 2019)
The following extra modules are missing:

  • Catalyst drivers (linux51-catalyst);
  • Legacy NVIDIA 340.XX drivers (linux51-nvidia-340xx);
  • Legacy NVIDIA 390.xx drivers (linux51-nvidia-390xx);
  • Solaris Porting Layer (linux51-spl);
  • Drivers for ZFS (linux51-zfs): does not build on Linux 5.1 currently.

The following extra modules are available:

  • ACPI call (linux51-acpi_call);
  • BBSwitch (linux51-bbswitch);
  • Broadcom wireless driver (linux51-broadcom-wl);
  • NDIS wrapper (linux51-ndiswrapper);
  • Current NVIDIA drivers (linux51-nvidia);
  • NVIDIA backlight (linux51-nvidiabl);
  • Realtek 8168 drivers (linux51-r8168);
  • Realtek 8732bu drivers (linux51-rtl8732bu);
  • Thinkpad SMAPI (linux51-tp_smapi);
  • SCSI emulation (linux51-vhba-module);
  • VirtualBox guest modules (linux51-virtualbox-guest-modules);
  • VirtualBox host modules (linux51-virtualbox-host-modules).

Small cleanup of Manjaro official repositories

Please note that the following packages got removed from our repositories.

  • chromium-chromevox
  • gimp-gtk3
  • pamac-classic
  • pamac-dev
  • pamac-dev-tray-appindicator

Items from previous update sets

COMMAND-NOT-FOUND error during update/installation

During upgrade/installation the package command-not-found tries to sync its database with a mirror that seems to be currently (or permanently ?) offline, resulting in an error message

(1/1) installing command-not-found                                     [########################################] 100%
Could not download catalog file ... aborting
error: command failed to execute correctly

I (oberon) have already opened an issue upstream about the problem.


Kaffeine: Digital television doesn't work anymore

Unfortunately, this functionality of Kaffeine is currently broken with v4l-utils 1.16.5-1.

It has already been reported to the Arch Linux bugtracker, see this: https://bugs.archlinux.org/task/62402

According to this ticket, Manjaro and Arch Linux are not the only distros affected by a similar issue.

As a temporary workaround, you may try to downgrade the v4l-utils package from 1.16.5-1 to 1.16.3-1. You may do so graphically with Pamac (with Install Local Package on /var/cache/pacman/pkg/v4l-utils-1.16.3-1-x86_64.pkg.tar.xz) using or with the command-line interface with pamac install /var/cache/pacman/pkg/v4l-utils-1.16.3-1-x86_64.pkg.tar.xz, sudo pacman -U /var/cache/pacman/pkg/v4l-utils-1.16.3-1-x86_64.pkg.tar.xz or any equivalent.

Please note that this is merely a temporary workaround and not a definitive solution. Do not keep this package downgraded forever as keeping downgraded packages for too long may become an issue in itself.

The KDE Updates Can Cause The Screenlocker To Crash

If you update from within a GUI session and use screenlock (e.g. it kicks in while the large update is being processed), it will crash the screenlocker.

To restore access, press CTRL+ALT+F2 to switch to another tty and log in with your username.

Then type in the following and press enter:

loginctl unlock-session 2

Press CTRL+ALT+F1 to switch back to a now unlocked KDE desktop.


XPlayer removal

Because XPlayer doesn't work anymore alongside GStreamer 1.16.0, the following packages got removed from official repositories: xplayer and xplayer-plparser. Upstream is aware of the issue, but we do not know when it will be fixed. Those packages may come back eventually.

We suggest using alternatives such as VLC media player (package: vlc).

TLP 1.2.1, .pacnew file: Merges may be needed

TLP 1.2.1 got released in [Stable Update] 2019-04-20 update set, replacing TLP 1.1. Therefore, if you have customized your configuration file for TLP (/etc/default/tlp), a .pacnew file will be created when the tlp package will be upgraded. This .pacnew file is the new default configuration file provided by the package. Your old configuration file won't be edited or replaced automatically; by default, your old configuration file will be kept as it is and you will have to merge relevant part the new configuration file manually with a text editor. Guidance can't really be more precise since each person has its own configuration.

You may use a tool such as Meld (package: meld) in order to compare your old configuration file with the .pacnew file and see the differences more easily.

If you haven't modified your configuration file for TLP, normally, you will automatically go on the new configuration file for TLP provided in the package without any manual intervention needed.

If you use the current version of TLPUI (tlpui r109.703bade-1), it may complain with the following error with some settings: "expected item missing in config file." It is most likely because some new parameters introduced with TLP 1.2.1 are not in /etc/default/tlp. To get rid of those messages, you will need to do some merges between your old configuration files and the .pacnew files and manually add all those new settings, even if you end up using the default value for those settings.


TLPUI cannot be launched

There was a bug in a previous version of TLPUI (confirmed on tlpui r89.d6363f0-1) that changed the permissions of /etc/default/tlp to 600 (rw-------). The default permissions for this file is 644 (rw-r--r--).

It is most likely that TLPUI doesn't launch because it doesn't have the right permissions for /etc/default/tlp. TLPUI must be allowed to read that file in order to launch.

First, verify if the permissions of /etc/default/tlp are set correctly. You may verify that with ls -l /etc/default/tlp in a terminal. Here's an example of how the output will look like:

$ ls -l /etc/default/tlp
-rw-r--r-- 1 root root 14238 Apr 11 15:26 /etc/default/tlp

If you have -rw------- instead of -rw-r--r--, change the permissions of that file so this file becomes readable to the group and others too. You may do so in the terminal with sudo chmod 644 /etc/default/tlp.

Once it is done, TLPUI should work properly.


MComix 1.2.1: Can't launch after the upgrade

This is a known issue that is due to breaking changes introduced in python2-pillow 6.0.0 (see this document). It is a package imported from Arch Linux and the issue has already been reported on Arch Linux side. See this ticket on the bug tracker: https://bugs.archlinux.org/task/62242

A true fix requires to do modifications in the source code of MComix.

Since python2-pillow (and python-pillow) is used by many programs, similar problems may happen with other software too.


"Spring cleanup" on Arch Linux: impact on Manjaro

Recently, Arch Linux did a "spring cleanup" of their Community repository (see the full discussion on the mailing list and seach for "spring"). Many package got removed from the Arch Linux official repositories and dropped to the AUR. Therefore, it means that many packages that were in our repositories because they were imported from Arch Linux got removed from our repositories too. Here's a non-exhaustive list of packages that got removed:

  • cherrytree - Hierarchical note taking application featuring rich text and syntax highlighting
  • docky - Full fledged dock application that makes opening common applications and managing windows easier and quicker
  • mate-menu - Advanced menu for MATE Panel, a fork of MintMenu (Not to be confused with mate-menus)
  • medit - GTK+ text editor
  • thermald - The Linux Thermal Daemon program from 01.org
  • wine-staging-nine has been removed / replaced with wine-nine. In case it is installed, it should be removed manually. http://archlinux.2023198.n4.nabble.com/Removing-wine-staging-nine-replaced-with-wine-nine-td4722447.html

If you want to continue to use those packages, you will have to use the AUR from now on.

You may try to do a package request in this category, but note that there is a high chance that your demand will be refused.


Gnome 3.32: Two extensions removed from our repos.

We have dropped two packages that shipped additional extensions for Gnome: gnome-shell-extension-topicons-plus-huttli and gnome-shell-extension-taskbar. We won't maintain Topicons Plus and Taskbar anymore.

Those extensions are not in active development anymore and may not work properly (or not work at all) on Gnome 3.32. Notably, it has been reported that using Topicons Plus on Gnome 3.32 may leads to very high CPU usage.

We strongly recommend you to disable those extensions if they are enabled (Tweaks > Extensions) and remove those packages with your favorite package manager. To prevent potential problems with the next version of Gnome, you may do those steps (or at least the first one) before upgrading your system.


Gnome 3.32: Various problems

There is currently several problems with Gnome 3.32. Here is what we know so far.

1. Possibility of broken extensions
Broken extensions is something to expect when transitioning between major versions of Gnome, especially if you are using extensions that are not shipped by default on Manjaro Gnome. If you have a broken extension taken from somewhere else than Manjaro official repositories, you will have to contact the maintainer on the source you have taken the extension from to get more support. You may also want to report the problem to the developer(s) of the extension (if not the same person/group).

It is possible that extensions become so broken on Gnome 3.32 that it makes Gnome Shell crash completely when trying to log in, thus making Gnome completely unusable. For example, we have a report of such issue with a third-party extension (that doesn't come from Manjaro's official repositories) called Extensions.

To decrease the risk of breakage (especially if running Gnome extensions that does not come from Manjaro official repositories) and make the upgrade smoother, you can disable all Gnome extensions (Tweaks > Extensions) before upgrading your system, then enable them one by one only after being logged in a completely new session on Gnome 3.32.

2. Using world clocks can break Gnome Shell completely
If you have configured world clocks in Gnome, it may make Gnome Shell segfaults and crashes when trying to log in for a graphical session, making Gnome unusable. If it happens, you will need to reset your parameters for world clocks with the following command (do it in TTY): dbus-launch gsettings reset org.gnome.clocks world-clocks.
See this Arch Linux thread and this ticket from upstream.

3. Gnome Shell may crash completely when resuming from sleep if you use Wayland
If you are using Wayland (instead of X.org), Gnome Shell may crash when resuming from sleep. Upstream is aware of this issue. As a workaround, you may use X.org instead of Wayland for now.

4. Miscellaneous
Some programs don't get focused after being launched. Reported to upstream and confirmed for distributions other than Manjaro too. (Should be fixed by now.)


My icon theme is not applied anymore for programs like Gnome Terminal, System Monitor, Gnome Screenshot, Gnome Disks, File Roller, etc.

With version 3.32 of these programs, upstream changed the icon used for many programs part of the Gnome Applications. Instead of using a generic icon shared by many programs, they chose to ship a new icon and use it. Therefore, launchers located in /usr/share/applications (.desktop files) for those programs has been modified to use the new icon instead of the generic one. Here's an example with Gnome Terminal.

Before
Icon=utilities-terminal

After
Icon=org.gnome.Terminal

Since your icon theme most likely doesn't have an icon named org.gnome.X, it falls back to the hicolor theme instead. This is why the icon changed after the system upgrade and "your theme is not applied anymore for those programs."

There is nothing you can really do for now, except living with it for a while. Icon theme designers will have to adapt their theme to the changes made by Gnome developers.


Yaourt: Rest in peace

Yaourt has been removed from our repositories completely. We won't maintain the yaourt package anymore, which means that you will not receive any updates from us for this package. A very old package named yaourt-gui-manjaro has been removed at the same time too.

If you are still using Yaourt, we strongly encourage you to switch to an alternative like Pamac CLI (package: pamac-cli), Trizen (package: trizen), Yay (package: yay) or Pacaur (package: pacaur); and uninstall Yaourt from your system.

In addition to that, we have dropped support for several packages that depended on yaourt: allservers, pacli and pacli-jwm. Those packages has been removed from the official repositories completely.


"Replace pamac with extra/pamac-gtk? [Y/n]"

Accept the replacement. The original pamac package is now split into three packages: pamac-gtk, pamac-cli and pamac-common.


vlc-nightly has been dropped

The vlc-nightly package, which was really useful in a time when VLC 3 was not officially out yet, has been dropped on our side and is not in the official repositories anymore. If you still have this package and you want the latest stable version of VLC media player, simply install the vlc package (the vlc-nightly package should be removed at the same time, in the same transaction).

Otherwise, you can continue to use vlc-nightly from the AUR (but you'll have to compile it yourself).


"NOTE, 4.20.17 was the last maintenance release by Greg Kroah-Hartman.; It is recommend to move on to linux50-series." What should I do?

Linux 4.20 (which is not an LTS kernel) is now marked as End Of Life (EOL), so if you want to continue to use an non-LTS kernel, you should consider using Linux 5.0, and also uninstall kernel 4.20 soon.

Keeping EOL kernel installed on your system for too long can lead up to problems for future upgrades (especially if using NVIDIA drivers). When using non-LTS kernel, you must do maintenance/cleanup more often.


" Replace xorg-mkfontdir with extra/xorg-mkfontscale? [Y/n]"

Accept the replacement.


Linux kernel 5.0.X available. Early problems reported.

The newest kernel series is now available for everyone. Please note that some issues has been reported with version 5.0.1 such as having a long delay at shutdown and losing sound output when using suspend. It is still available for the early adopters. You are free to install and use it or not.

As reported by some users, if you use WireGuard, you may have to manually run sudo dkms autoinstall in a terminal to get the kernel module working properly with Linux 5.0.1.
More info about dkms autoinstall (and DKMS in general) here.


Kodi 18.1: extensions may not work properly.

Kodi 18.1 is now available in our repositories. Since this is a major version change, extensions for Kodi (if you use some) may stop working properly. Developers of those extensions will need to make them compatible with Kodi 18.

If Kodi 18.1 doesn't work properly for you and you absolutely need to use your extensions, you may use the old kodi package in /var/cache/pacman/pkg in order to downgrade Kodi to version 17.6. Please note that it is a temporary workaround and that the software provided in the old kodi package may stop working properly in the future too. You should not keep the downgrade forever.


ProjectM: projectm-pulseaudio v.s. projectm-qt, file conflict with /usr/share/pixmaps/prjm16-transparent.svg

Starting with version 3.1.0 of ProjectM, there are now only three packages instead of six and the QT part has been merged to the projectm-pulseaudio package.

Remove the projectm-qt package before upgrading your system.

4 Likes

Thanks for the update!
Works fine on my new laptop: linux50+Intel UHD 620+cinnamon

Smoooooth. Thank you!

Why no kernel 5.1.2? It includes the important new CPU bug fixes!

This grub stuff makes me dreary.

Here is new /etc/default/grub.pacnew

Summary
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=menu
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT= "quiet udev.log_priority=3 audit=0"
GRUB_CMDLINE_LINUX=""

# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter 
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx" 
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper 
# modes only.  Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
**#GRUB_THEME="/path/to/gfxtheme"**

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

Here is current /etc/default/grub

Summary
GRUB_DEFAULT=saved
GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=menu
GRUB_DISTRIBUTOR='Manjaro'
GRUB_CMDLINE_LINUX_DEFAULT=**"quiet resume=UUID=fb682fe4-0003-474d-b7d0-cdc1951af7e8"**
GRUB_CMDLINE_LINUX=""

# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true

# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"

# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y

# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console

# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto

# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep

# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true

# Uncomment and set to the desired menu colors.  Used by normal and wallpaper
# modes only.  Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"

# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
**GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"**

# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"

I mark as bold text differences, is it a safe to override changes? Looks like I should keep UUID from old grub, correct?

P.S. ok, bold text doesn't work with preformatted text

new:

GRUB_CMDLINE_LINUX_DEFAULT= "quiet udev.log_priority=3 audit=0"
#GRUB_THEME="/path/to/gfxtheme"

old:

GRUB_CMDLINE_LINUX_DEFAULT=**"quiet resume=UUID=fb682fe4-0003-474d-b7d0-cdc1951af7e8"
GRUB_THEME="/usr/share/grub/themes/manjaro/theme.txt"

That's right, add resume=UUID=fb682fe4-0003-474d-b7d0-cdc1951af7e8 to the line "quiet udev.log_priority=3 audit=0" (between the "" ).

@philm, @jonathon i don't understand why this seems to have now affected the forum page code. Pls see my pic... i had not noticed that new script yesterday, & i don't understand how a kernel/cpu hazard & mitigation somehow is relevant to html/css code...?

1 Like

No problem here :+1:

Thanks to the Manjaro-team

regards
caho

See here

And don't need " udev.log_priority=3 audit=0" . Never needed, actually.

1 Like

wow, wow, running to remove those lines which I added 1 minute ago

1 Like

Everything went smooth on both KDE and i3 for me. Also glad to see those vulnerabilities have already been patched on upstream. My friend IRL texted me an article about that earlier this week. I look forward to seeing the patches hit the stable branch. :slight_smile:

It is not a new script. The read picture of a hand holding a CPU is simply linked directrly form zombieloadattack.com. In your uMatrix screenshot, you can see the 1 in the image column for zombieloadattack.com. This means this sides loads a image from zombieloadattack.com. Nothing more.

3 Likes

I'm having trust issues with a guy named Helmut Stult even though I imported his PGP key.

:: Import PGP key 4096R/F66AD0FF0E57C561615A0901CEE477135C5872B0, "Helmut Stult (schinfo) helmut@manjaro.org", created: 2018-02-15? [Y/n]
(152/152) checking package integrity [######################] 100%
error: pamac-common: signature from "Helmut Stult (schinfo) helmut.stult@schinfo.de" is marginal trust
:: File /var/cache/pacman/pkg/pamac-common-7.4.0-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: pamac-cli: signature from "Helmut Stult (schinfo) helmut.stult@schinfo.de" is marginal trust
:: File /var/cache/pacman/pkg/pamac-cli-7.4.0-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: pamac-gtk: signature from "Helmut Stult (schinfo) helmut.stult@schinfo.de" is marginal trust
:: File /var/cache/pacman/pkg/pamac-gtk-7.4.0-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
error: failed to commit transaction (invalid or corrupted package)
Errors occurred, no packages were upgraded.

This guide should help: Issues with "signature is marginal trust" or "invalid or corrupted package"

4 Likes

no problems here

4.19 (LTS)
Nvidia prop.
Xfce4

all smooth :+1:t4:

Thanks! Worked like a charm.

Hi everyone,
updating my manjaro XFCE today I was presented with a conflicting files error message:

error: failed to commit transaction (conflicting files)
node-gyp: /usr/lib/node_modules/node-gyp/node_modules/form-data/yarn.lock exists in filesystem
Errors occurred, no packages were upgraded.

Any suggestions?

Removing the lock file should work.