Damn. The latest update messed up my system. I could login via GUI login screen, but my background is black, I can’t see my panel and even after I installed plasma (as suggested above), after restart nothing has changed.
systemctl --failed
… returns 0.
In your the journalctl log i found 2 things
oct 01 19:06:51 rodrigo-pc systemd-coredump[1072]: Process 1066 (sddm-greeter) of user 969 dumped core.
Stack trace of thread 1066:
#0 0x00007fa604342615 raise (libc.so.6 + 0x3d615)
#1 0x00007fa60432b862 abort (libc.so.6 + 0x26862)
#2 0x00007fa6047569ac _ZNK14QMessageLogger5fatalEPKcz (libQt5Core.so.5 + 0x919ac)
#3 0x00007fa60476d387 n/a (libQt5Core.so.5 + 0xa8387)
#4 0x00007fa605c17452 _ZN19QQuickWindowPrivateC1Ev (libQt5Quick.so.5 + 0x24f452)
#5 0x00007fa605c8960a _ZN17QQuickViewPrivateC1Ev (libQt5Quick.so.5 + 0x2c160a)
#6 0x00007fa605c8a641 _ZN10QQuickViewC1EP7QWindow (libQt5Quick.so.5 + 0x2c2641)
#7 0x0000560df6f755d5 _ZN4SDDM10GreeterApp16addViewForScreenEP7QScreen (sddm-greeter + 0x375d5)
#8 0x0000560df6f76334 _ZN4SDDM10GreeterApp7startupEv (sddm-greeter + 0x38334)
#9 0x00007fa6049a510f _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e010f)
#10 0x00007fa6049787ba _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b37ba)
#11 0x00007fa60497b2a3 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b62a3)
#12 0x00007fa6049d1cf4 n/a (libQt5Core.so.5 + 0x30ccf4)
#13 0x00007fa6032d0bfc g_main_context_dispatch (libglib-2.0.so.0 + 0x52bfc)
#14 0x00007fa6033221f9 n/a (libglib-2.0.so.0 + 0xa41f9)
#15 0x00007fa6032cf421 g_main_context_iteration (libglib-2.0.so.0 + 0x51421)
#16 0x00007fa6049d1331 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c331)
#17 0x00007fa60497713c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
#18 0x00007fa60497f5c4 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2ba5c4)
#19 0x0000560df6f57bf1 main (sddm-greeter + 0x19bf1)
#20 0x00007fa60432d152 __libc_start_main (libc.so.6 + 0x28152)
#21 0x0000560df6f57f1e _start (sddm-greeter + 0x19f1e)
Stack trace of thread 1068:
#0 0x00007fa6043fa46f __poll (libc.so.6 + 0xf546f)
#1 0x00007fa603322188 n/a (libglib-2.0.so.0 + 0xa4188)
#2 0x00007fa6032cf421 g_main_context_iteration (libglib-2.0.so.0 + 0x51421)
#3 0x00007fa6049d1331 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30c331)
#4 0x00007fa60497713c _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b213c)
#5 0x00007fa604792c32 _ZN7QThread4execEv (libQt5Core.so.5 + 0xcdc32)
#6 0x00007fa600a9a098 n/a (libQt5DBus.so.5 + 0x17098)
#7 0x00007fa604793e0f n/a (libQt5Core.so.5 + 0xcee0f)
#8 0x00007fa603ec93e9 start_thread (libpthread.so.0 + 0x93e9)
#9 0x00007fa604405293 __clone (libc.so.6 + 0x100293)
Stack trace of thread 1067:
#0 0x00007fa6043fa46f __poll (libc.so.6 + 0xf546f)
#1 0x00007fa6059aa63b n/a (libxcb.so.1 + 0xc63b)
#2 0x00007fa6059ac37b xcb_wait_for_event (libxcb.so.1 + 0xe37b)
#3 0x00007fa600bb1c51 n/a (libQt5XcbQpa.so.5 + 0x5dc51)
#4 0x00007fa604793e0f n/a (libQt5Core.so.5 + 0xcee0f)
#5 0x00007fa603ec93e9 start_thread (libpthread.so.0 + 0x93e9)
#6 0x00007fa604405293 __clone (libc.so.6 + 0x100293)
oct 01 19:07:00 rodrigo-pc FAHClient[1146]: 17:07:00:ERROR:No compute devices matched GPU #0 {
oct 01 19:07:00 rodrigo-pc FAHClient[1146]: 17:07:00:ERROR: "vendor": 4318,
oct 01 19:07:00 rodrigo-pc FAHClient[1146]: 17:07:00:ERROR: "device": 7309,
oct 01 19:07:00 rodrigo-pc FAHClient[1146]: 17:07:00:ERROR: "type": 2,
oct 01 19:07:00 rodrigo-pc FAHClient[1146]: 17:07:00:ERROR: "species": 5,
oct 01 19:07:00 rodrigo-pc FAHClient[1146]: 17:07:00:ERROR: "description": "GP107M [GeForce GTX 1050 Mobile]"
oct 01 19:07:00 rodrigo-pc FAHClient[1146]: 17:07:00:ERROR:}. You may need to update your graphics drivers.
for the second problem try “lspci” to find graphic card bus id and add in your xorg config BusID “PCI:[your graphic card bus id]” ’ in Device secction.
the first problem i don’t how to fix it, sorry.
If anyone else has the issue with plasmashell starting and stopping, check if they have the plasmoid “eventcalendar”. Deleting it fixed the problem for me.
.local/share/plasma/plasmoids/org.kde.plasma.eventcalendar
Update:
I went to the panel widget installing tool thing and there was an option to “update” Event Calendar. I did it, and now event calendar seems to work fine.
That was done with org.kde.plasma.eventcalendar still deleted.
Looks like it works still after a restart.
Hey, I had the same problem and I think I found the solution. It seems event calendar is causing the crash. I eliminated it from ~/.local/share/plasma/plasmoids and started plasmashell without problem this time. I then added the normal digital clock plasmoid in order to have something that tells me the time.
We saw this problem when the gnome-terminal package hit Testing. Its not a manjaro problem - it seems to be a gnome issue hitting multiple distros.
The solution for now is to go to Preferences -> Colors and uncheck “use colors from system theme”. You can then adjust your background. I hope this helps!
I can confirm this resolves my issue described above. Just delete the eventcalendar plasmoid and you could still reinstall it at the end of your manjaro update (restart).
Why could eventcalendar create such a big issue?
On a side note, the recent update also gave me headache with Compositor and Latte-dock which is luckily easy to resolve:
System settings > Display configuration > Compositor > uncheck Allow applications to block compositing.
Update (239 packages including a new kernel) installed without a hitch.
Manjaro 20.1, Ryzen TR 3960X, 64GB, AMD Radeon RX5600XT on a Gigabyte Aorus Master rev 1.
Hi there,
hadn’t updated for about two months. Went mostly fine. Ran the update in the Octopi terminal. The screensaver seems to have crashed during the update, locking the session, but thankfully displaying a message informing me how to work around this issue (switch to another tty, log in, loginctl unlock-session 2 , and switch back to gfx tty.
It asked me to replace two packages:
:: Replace calibre-common with community/calibre? [Y/n] y
:: Replace libutil-linux with core/util-linux-libs? [Y/n] y
Other than that, I got a couple of warnings about dependency cycles:
warning: dependency cycle detected:
warning: smbclient will be installed before its cifs-utils dependency
warning: dependency cycle detected:
warning: perl-libwww will be installed before its perl-html-parser dependency
warning: dependency cycle detected:
warning: ruby-irb will be installed before its ruby dependency
warning: dependency cycle detected:
warning: ruby-reline will be installed before its ruby dependency
Error:
(1/2) removing calibre-common
rmdir: failed to remove ‘/usr/lib/calibre/’: Directory not empty
error: command failed to execute correctly
And a couple of warnings about directory permission mismatches
warning: directory permissions differ on /var/lib/AccountsService/icons/
filesystem: 755 package: 775
warning: directory permissions differ on /var/lib/dhcpcd/
filesystem: 700 package: 755
warning: directory permissions differ on /usr/share/hplip/base/pycache/
filesystem: 700 package: 755
warning: directory permissions differ on /usr/share/hplip/base/pexpect/pycache/
filesystem: 777 package: 755
warning: directory permissions differ on /usr/share/hplip/prnt/pycache/
filesystem: 777 package: 755
I was informed that a few isysctl settings were not applied, although I don’t remember manually setting anything in this area.
( 5/30) Applying kernel sysctl settings…
Not setting net/ipv4/conf/all/rp_filter (explicit setting exists).
Not setting net/ipv4/conf/default/rp_filter (explicit setting exists).
Not setting net/ipv4/conf/all/accept_source_route (explicit setting exists).
Not setting net/ipv4/conf/default/accept_source_route (explicit setting exists).
Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists).
Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists).
System seems to work ok. Will test reboot after I post this message 
This was the first time in 2 years that an update caused problems.
Update went through normally, restarting the computer as well, the desktop started and when I was about to do something, black screen with my mouse cursor in the middle.
I could also solve it by deleting the plasma folder.
Solved by removing the plasma folder in ~/.local/share
sudo rm -R plasma
Many thanks to the developers for this update.
This finally fixed No irq handler for vector / Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0 for me. 
see this
boot on USB iso manjaro
do chroot ( sudo manjaro-chroot -a )
check list kernels installed & files /etc/mkinitcpio.d/*.preset
i think you should remove 5.7.preset
and then redo mkinitcpio for others
sudo manjaro-chroot -a
ls /etc/mkinitcpio.d/*.preset
mhwd-kernel -li
rm /etc/mkinitcpio.d/<name57>.preset
mkinitcpio -P
update-grub
exitthen reboot
Having a login-loop problem with GDM post-update. I can get past it by alt-ctrl-F2-ing into a terminal, logging in, and then running startx, which starts gnome just fine. I ran pacdiff before the reboot, so it’s nothing to do with any pacnew files. And I didn’t have any remarkable errors or warnings in pacman.log, Thoughts? Should I reinstall GDM?
One update: systemctl status gdm shows the error gkr-pam: unable to locate daemon control file
P.S. This issue is just on my gnome tablet. My desktop running i3 seems to have no issues.
I used Event Calendar in a Latte dock, so after the update that crashed instead of Plasmashell. I have deleted the local version under ~/.local/share and installed v69 from the AUR, but Latte still crashes…
Edit to add that it works as expected without the Event Calendar widget.
Another edit to specify that I can install v69 from the AUR, add it to my Latte dock and change settings, and Latte crashes only after a reboot.
This issue with Event Calendar is wierd. I haven’t updated Manjaro yet because I’m not near that computer but Event Calendar is working fine on my Arch machine and my EndeavourOS machine. 
At least I’ll be warned when I update on Monday! 
Not familiar with Latte, but see the logs to make sure it is loading the addon from /usr/share/plasma/plasmoids/org.kde.plasma.eventcalendar, or if there are other issues with it other than the ones mentioned above.
System settings > Display configuration > Compositor > uncheck ‘Allow applications to block compositing’. Additionally try to change the Rendering backend to OpenGL 3.1.
Seems to be fine on my side, on Manjaro Cinnamon.
Thanks for replying. latte-dock seems to leave no traces itself in the logs (checked the journal logs via the KSystemlog app that comes with KDE, as well as by running latte in the terminal), so I cannot say for sure where it is loading the widget from, but it has to be the one in /usr/share/plasma/ because I deleted the other version in ~. I tried adding the widget to the dock and changing settings or leaving the defaults before terminating the dock, in both cases it cannot start again. I have also tried creating a regular plasma panel and leaving the widget there, and that seems to work fine even after restarting plasmashell. So the problem is related to Latte.
@Jazz Latte works just fine in my case without the widget, and I don’t see how these compositor settings can help. I did try to change them just in case but there was no difference.
That makes some sense to me: something about using event calendar with Latte. I don’t use Latte hence no problems. Sorry I can’t offer a solution, I’m just tracking the thread before I update on Monday.
Will it update without any errors?