[Stable Update] 2020-10-01 - Kernels, Mesa, KDE-Framework, Deepin, Systemd, Pamac, Xorg-Server, Qt

Try restart failed service “sudo systemctl restart SERVICENAME”

if fails execute systemctl status SERVICENAME to show error or find it in journalctl.

hi,
I have the same problem. I want to try ‘pamac install plasma’ but cannot know how can I remove discover from the optional dependency list.

edit: removing the eventcalendar widget fixes as @Void says fixes the problem. its working 69th version may be installed from aur.

KDE Plasma will not start. Hybrid AMD/NVIDIA graphics. SDDM starts fine, then when attempting to login, xorg seems to crash and I get dropped back into SDDM. Reverted to an earlier snapshot, holding off on upgrading for now.
My .local/share/plasma contains look-and-feel and plasmoids, but both are empty.

journalctl -b here: https://paste.centos.org/view/e12b16f6

From systemctl —failed I got

0 loaded units listed

Systemctl status

https://paste.centos.org/view/b4e5dedf

For journalctl after update and first restart.

https://paste.centos.org/view/bba8559c

Manjaro Cinnamon went well. I can’t see any problems right now. Thank you for all the work.

I have decided to use Pamac GUI consequently for my updates and to give a feedback, if I have the time to do so. In my opinion a user-friendly OS like Manjaro has to work with this application without any hiccups in the “stable branch”, otherwise the whole conception and the claim to be user-friendly would not make sense. Therefore it is of the highest possible importance that we all have a careful look around here.

1 Like

0 services failed.
Did you reboot and login in plasma and you can’t connect to the net?
If issue continued maybe you need ask in suppor section.

Got this weird left popup shadow glitch in Plasma again, the same as described in KDE bug #417606. Solved by removing ~/.cache/plasma*. The same artifact in Latte Dock seemed to require quitting Latte and removing ~/.cache/lattedock/*.

I could connect using cable. No Wi-Fi after update.
No graphical screen is showing. I rebooted many times. On the main session here it’s supposed to show KDE login, nothing is displayed and laptop keep showing manufacturer logo. I can login only in terminal switching to session 2

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.

1 Like

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.

6 Likes

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.

2 Likes

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!

5 Likes

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.

2 Likes

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 :slight_smile:

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.
:grimacing:
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. :slight_smile:

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
exit

then reboot

2 Likes

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.