[Stable Update] 2019-12-29 - Kernels, KDE Apps 19.12, Xorg-Stack, Mesa, Qt5

[SOLVED]
During the download of all the packages, I get the following error:
"Checking integrity...
Error: qt5-webengine: signature from "Antonio Rojas arojas@archlinux.org" is invalid
Error: virtualbox-guest-iso: signature from "Christian Hesse (Arch Linux Package Signing) arch@eworm.de" is invalid
Failed to commit transaction:"
What do I do?
invalid or corrupted package:

Try

Thanks! Sorry for being such a noob, but is this what Yay uses for building and without it set (default is commented) Yay does not store them at all?

@freggel.doe
I followed your instructions and all is well now. Runs like a charm. Thank you very much and a Happy New Year to you and all in our community.

makepkg apparently defaults to current directory. Which is --builddir or AURDEST in yay. Which defaults to yay cache directory $HOME/.cache/yay. And that one can be configured in $XDG_CONFIG_HOME/yay/config.json (buildDir)

1 Like

Still have some trouble with i915 graphic card (Intel HD 630) even after this kernel update.
This problem has been talk about here : https://linuxreviews.org/Kernel_5.4.1_And_5.3.14_Are_Released_Making_Linux_Users_With_Intel_iGPUs_Finally_Able_To_Use_5.3-Series_Kernels
I had some hope about this new kernel will fix it but after switching to it, still have crashes.

Here the kind of error I got with kernel 5.4 :

janv. 02 11:39:37 mat250-laptop kernel: i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0
janv. 02 11:39:37 mat250-laptop kernel: GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
janv. 02 11:39:37 mat250-laptop kernel: Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
janv. 02 11:39:37 mat250-laptop kernel: drm/i915 developers can then reassign to the right component if it's not a kernel issue.
janv. 02 11:39:37 mat250-laptop kernel: The GPU crash dump is required to analyze GPU hangs, so please always attach it.
janv. 02 11:39:37 mat250-laptop kernel: GPU crash dump saved to /sys/class/drm/card0/error
janv. 02 11:39:37 mat250-laptop kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
janv. 02 11:39:37 mat250-laptop kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
janv. 02 11:39:37 mat250-laptop kernel: i915 0000:00:02.0: Resetting chip for hang on rcs0
janv. 02 11:39:37 mat250-laptop kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
janv. 02 11:39:37 mat250-laptop kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
janv. 02 11:39:43 mat250-laptop kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
janv. 02 11:39:51 mat250-laptop kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
janv. 02 11:39:53 mat250-laptop kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
janv. 02 11:39:55 mat250-laptop kernel: i915 0000:00:02.0: Resetting rcs0 for hang on rcs0

That kind of problem seems like a very likely problem after you deleted all "orphans". Deleting orphans assumes the dependencies capture all the packages you are actually using, which is often not the case, especially with AUR packages.

If you deleted a package you actually needed, go through the list all the packages you just deleted and see if any of them might possibly be used by Cura.

OK I,'ll try it, although I allready reinstalled the program...

This is an inherently risky command, why do you suggest it as a generic solution?
Breakage is very likely especially loss of added functionality, at the very least add another t to pacman (pacman -Qqdtt) so you keep optional dependencies.

See correction below by @freggel.doe

1 Like

This is wrong actually: pacman -Qdt will take optional dependencies into account while pacman -Qdtt will ignore them (and list more packages as "orphans").

1 Like

Thanks for the correction!

1 Like

Yep, seems there are still some issues open with this matter ...

I got this at the end of the update:

WARNING: CPU random generator seem to be failing, disable hardware random number generation
WARNING: RDRND generated: 0xffffffff 0xffffffff 0xffffffff 0xffffffff

What shall I do here?
And why does it say this now and not in previous updates? I didn't change the CPU.

inxi
System:
  Host: runlikehell Kernel: 4.19.88-1-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 9.2.0 Desktop: Xfce 4.14.1 tk: Gtk 3.24.12 wm: xfwm4 dm: LightDM 
  Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: Gigabyte model: X570 GAMING X v: x.x serial: <filter> 
  UEFI [Legacy]: American Megatrends v: F3 date: 06/13/2019 
CPU:
  Topology: 8-Core model: AMD Ryzen 7 3700X bits: 64 type: MT MCP arch: Zen 
  L2 cache: 4096 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm 
  bogomips: 115034 
  Speed: 2176 MHz min/max: 2200/3600 MHz Core speeds (MHz): 1: 2176 2: 2130 
  3: 2723 4: 1968 5: 3704 6: 2140 7: 2126 8: 2960 9: 3267 10: 2018 11: 3564 
  12: 2152 13: 2118 14: 2711 15: 2144 16: 2118 

This is a known issue with AMD RDRAND/RDSEED instruction that can cause some issue with any software that uses said instruction and back then can make your system unbootable especially with some old version of systemd.
You need to update your motherboard firmware to a newer version since I see that you're still using a really old firmware based on the date from your inxi output. Also make sure that AMD microcode (amd-ucode) is installed and is properly loaded by your boot manager.
If you don't have amd-ucode installed, you need to install it now and excute grub-mkconfig -o /boot/grub/grub.cfg to update grub configuration file so it will load the microcode properly.

EDIT: Yup, you really need to update the motherboard firmware right now. You're using the very first public release of the firmware for the motherboard and you're 4 firmware release behind.

1 Like

Mmm :thinking:
I have a little problem with KDE: when I switch window with Alt+Tab appears a notification:

    The Window Switcher installation is broken, resources are missing.
Contact your distribution about this.

Thanks for the detailed explanation. There was no amd-ucode so I installed it and called grub-mkconfig and also updated the BIOS.

However, I noticed that I also have intel-ucode installed. According to this the AMD-stuff is loaded. Now I don't know if intel-ucode serves any purpose or actually may cause some misbehaviour at some point. Do you know that?

I had no idea this Alt+Tab feature existed, thanks. I really need to pull out my KDE manual and go at it one day. :open_mouth::face_with_hand_over_mouth:

Works with my KDE install with the latest updates applied.

You can safely remove intel-ucode since you're using amd-ucode.

I was late in updating and only did so last night. Seemed to go smoothly. Logged in today and all was fine, up until Dolphin crashed.

So I restarted and now Manjaro is a "clean install" downloads and pictures folders are empty, themes have been reset, shortcuts gone...

Only thing that remained is a profile picture I had... Oh and Login screen picture remained as well. But firefox data etc all is gone and it's frustrating.

Forum kindly sponsored by