All went fine: XFCE + BTRFS + linux54 + linux57 great job Manjaro Team 
All good, but still not able to use kernel 5.8 in combination with VirtualBox, and i still can’t find the actual issue. The VM starts and the entire system hangs unrecoverable. Switched to 5.4 because with 5.7 i get a lot of codedumps when using Krita.
systemd-coredump Krita
Process 64882 (krita) of user 1000 dumped core.
Stack trace of thread 64882:
#0 0x00007fcdcb9bb956 n/a (libQt5Widgets.so.5 + 0x1a6956)
#1 0x00007fcdcb9caedb n/a (libQt5Widgets.so.5 + 0x1b5edb)
#2 0x00007fcdcb9caf01 n/a (libQt5Widgets.so.5 + 0x1b5f01)
#3 0x00007fcdcb9cafa6 n/a (libQt5Widgets.so.5 + 0x1b5fa6)
#4 0x00007fcdcb9c0247 n/a (libQt5Widgets.so.5 + 0x1ab247)
#5 0x00007fcdcb9af989 _ZN7QWidgetD2Ev (libQt5Widgets.so.5 + 0x19a989)
#6 0x00007fcdcb9afe9a _ZN7QWidgetD0Ev (libQt5Widgets.so.5 + 0x19ae9a)
#7 0x00007fcdcaf02dde _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2cfdde)
#8 0x00007fcdcb9afc7e _ZN7QWidgetD2Ev (libQt5Widgets.so.5 + 0x19ac7e)
#9 0x00007fcdcba8864e n/a (libQt5Widgets.so.5 + 0x27364e)
#10 0x00007fcdcaf02dde _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2cfdde)
#11 0x00007fcdcb9afc7e _ZN7QWidgetD2Ev (libQt5Widgets.so.5 + 0x19ac7e)
#12 0x00007fcdcba8ad06 n/a (libQt5Widgets.so.5 + 0x275d06)
#13 0x00007fcdcaf02dde _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2cfdde)
#14 0x00007fcdcb9afc7e _ZN7QWidgetD2Ev (libQt5Widgets.so.5 + 0x19ac7e)
#15 0x00007fcdb0c4914a n/a (QtWidgets.abi3.so + 0x34514a)
#16 0x00007fcdb148aa45 n/a (QtCore.abi3.so + 0x20ba45)
#17 0x00007fcdb15929f8 n/a (sip.cpython-38-x86_64-linux-gnu.so + 0x99f8)
#18 0x00007fcdb148a6ed n/a (QtCore.abi3.so + 0x20b6ed)
#19 0x00007fcdb1a07d39 n/a (libpython3.8.so.1.0 + 0x13cd39)
#20 0x00007fcdb19f930d PyObject_Call (libpython3.8.so.1.0 + 0x12e30d)
#21 0x00007fcdb1b1a129 n/a (libpython3.8.so.1.0 + 0x24f129)
#22 0x00007fcdb19d87ce n/a (libpython3.8.so.1.0 + 0x10d7ce)
#23 0x00007fcdb1ce4b73 n/a (kritapykrita.so + 0xfb73)
#24 0x00007fcdb1ce4cfe n/a (kritapykrita.so + 0xfcfe)
#25 0x00007fcdb1ce1f28 n/a (kritapykrita.so + 0xcf28)
#26 0x00007fcdcaf02dde _ZN14QObjectPrivate14deleteChildrenEv (libQt5Core.so.5 + 0x2cfdde)
#27 0x00007fcdcaf0c6a8 _ZN7QObjectD2Ev (libQt5Core.so.5 + 0x2d96a8)
#28 0x00007fcdcaedabf0 _ZN16QCoreApplicationD2Ev (libQt5Core.so.5 + 0x2a7bf0)
#29 0x00007fcdcb970d59 _ZN12QApplicationD2Ev (libQt5Widgets.so.5 + 0x15bd59)
#30 0x00007fcdcd523f93 _ZN19QtSingleApplicationD1Ev (libkritaui.so.18 + 0xf70f93)
#31 0x000055cdcdb86cb6 main (krita + 0x8f9cb6)
#32 0x00007fcdca891023 __libc_start_main (libc.so.6 + 0x27023)
#33 0x000055cdcdb87e1e _start (krita + 0x8fae1e)
Stack trace of thread 64907:
#0 0x00007fcdca963f8d syscall (libc.so.6 + 0xf9f8d)
#1 0x00007fcdcacff4e1 n/a (libQt5Core.so.5 + 0xcc4e1)
#2 0x00007fcdcacff346 _ZN10QSemaphore10tryAcquireEii (libQt5Core.so.5 + 0xcc346)
#3 0x00007fcdcc25de3d _ZN18KisTileDataSwapper3runEv (libkritaimage.so.18 + 0x19be3d)
#4 0x00007fcdcacfcfd6 n/a (libQt5Core.so.5 + 0xc9fd6)
#5 0x00007fcdc8c4346f start_thread (libpthread.so.0 + 0x946f)
#6 0x00007fcdca9693d3 __clone (libc.so.6 + 0xff3d3)
Stack trace of thread 64888:
#0 0x00007fcdca95eabf __poll (libc.so.6 + 0xf4abf)
#1 0x00007fcdc8159630 n/a (libxcb.so.1 + 0xc630)
#2 0x00007fcdc815b2db xcb_wait_for_event (libxcb.so.1 + 0xe2db)
#3 0x00007fcdc4d94ba1 n/a (libQt5XcbQpa.so.5 + 0x65ba1)
#4 0x00007fcdcacfcfd6 n/a (libQt5Core.so.5 + 0xc9fd6)
#5 0x00007fcdc8c4346f start_thread (libpthread.so.0 + 0x946f)
#6 0x00007fcdca9693d3 __clone (libc.so.6 + 0xff3d3)
Stack trace of thread 64906:
#0 0x00007fcdca963f8d syscall (libc.so.6 + 0xf9f8d)
#1 0x00007fcdcacff202 _ZN10QSemaphore7acquireEi (libQt5Core.so.5 + 0xcc202)
#2 0x00007fcdcc23cfab _ZN17KisTileDataPooler11waitForWorkEv (libkritaimage.so.18 + 0x17afab)
#3 0x00007fcdcc23d8ca _ZN17KisTileDataPooler3runEv (libkritaimage.so.18 + 0x17b8ca)
#4 0x00007fcdcacfcfd6 n/a (libQt5Core.so.5 + 0xc9fd6)
#5 0x00007fcdc8c4346f start_thread (libpthread.so.0 + 0x946f)
#6 0x00007fcdca9693d3 __clone (libc.so.6 + 0xff3d3)
Stack trace of thread 64891:
#0 0x00007fcdca95eabf __poll (libc.so.6 + 0xf4abf)
#1 0x00007fcdc82fc120 n/a (libglib-2.0.so.0 + 0x6c120)
#2 0x00007fcdc82fc1f1 g_main_context_iteration (libglib-2.0.so.0 + 0x6c1f1)
#3 0x00007fcdcaf310d0 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2fe0d0)
#4 0x00007fcdcaed757c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2a457c)
#5 0x00007fcdcacfbe62 _ZN7QThread4execEv (libQt5Core.so.5 + 0xc8e62)
#6 0x00007fcdc8c73b28 n/a (libQt5DBus.so.5 + 0x15b28)
#7 0x00007fcdcacfcfd6 n/a (libQt5Core.so.5 + 0xc9fd6)
#8 0x00007fcdc8c4346f start_thread (libpthread.so.0 + 0x946f)
#9 0x00007fcdca9693d3 __clone (libc.so.6 + 0xff3d3)
Will make some tests to see if this is still an issue.
When will there be Manjaro 20.1 Stable Version?
PS: If KDE has better support for High-DPI screens than GNOME, I will prefer it.
1 Like
Hey @bogdancovaciu in case of the VBox issue the 5.8 Kernel will be Supported in the next update:
3 Likes
Wow, FINALLY!
New update, nice thanks Manjaro team
It works here from Phils patches to 5.8 kernel. It’s no kernel for sure. AMD/AMD here.
Printer says:
journalctl -p err -b
colord-sane[902]: io/hpmud/musb.c 2099: Invalid usb_open: Permission denied
Solution:
sudo usermod -a -G lp colord
1 Like
First gen i7 CPU and Nvidia GPU here … that might add some spice to the issue, but in my case the real issues is related to the linux58-virtualbox-host-modules
This update literally removed ALL of my installed applications.
It started with a conflict between nvidia-390xx-utils and nvidia-450xx-utils.
As I only own an old GeForce 550 Ti, I have to stick with the 390 driver version, though.
Unfortunately, the only way to resolve this conflict was removing mhwd-nvidia-450xx. This, unfortunately, also removed my nvidia-390 driver as well, so I had to re-install it after the update.
Because there also was a new kernel version, I then rebooted.
After reboot, I got “Failed to start Light Display Manager” and no graphical desktop.
So I re-installed both xfce and LightDM, but then it complained about lightdm-slick-greeter missing as well. So I had to install that also.
After all that, I could get back to the desktop. Unfortunately, it turned out that ALL of my installed programs (Libre Office, Evolution, Double Commander and so on) were gone.
Now I am in the process of re-installing everything step-by-step. Fortunately, my user settings seem to have been preserved so for example, I have all my mailboxes back in Evolution without the need to re-configure.
Such a behavior on an update reminds me a bit of the Windows 10 horror stories. So please let me kindly ask you to abstain from reproducing such things on Linux even though Microsoft is the market leader and thus, must have done something right 
1 Like
You could delay update, removal, I am sure wouldn’t go without you noticing.
(I update with pacman, so dunno about GUI)
Probably vbox issue with Nvidia driver. Only driver can crash system.
Those craving for VirtualBox, consider trying qtemu-git (AUR) for a proper virtualization alternative without procrapietary VB modules 
Nice Qt interface, looks fine in Plasma DE:
And Gnomers have a “Gnome-way” single-button-powered gnome-boxes, which is even 1000 times simpler to use.
7 Likes
On my intel only laptop - vbox works fine with 5.8.6-1-MANJARO
Cool, but it’s better to use the official packages
Xfce ok + systemd 246 ok + virtualbox ok + kernel 5.8.6 ok + youtube(1080p) + Steam(OpenGl) ok
Wrt VBox and Linux 5.8, I dare to „add up 1+1“ and speculate. The problems of VB 6.1.12 with Kernel 5.8 AFAIK are down to the Linux developers’ quest for security (allocating memory to executable code). So I really hope that Manjaro patches to the kernel (cf. above, someone mentioned @philm patches) if there is s.th. in that direction will be removed when VB 6.1.14 arrives and works. Pls forgive me if I‘m wrong!
1 Like
This is not the driver at all, this is a package required in MHWD…
Also use Timeshift dude, it is the basics to restore a failed update or user error (that I guess is the issue here).
But why was it conflicting with nvidia-390xx?