AFter full system update, on reboot sddm freezes

So i did a yay -Syu today, and after reboot sddm never goes anywhere, the turning circle stops moving and that’s it.
The tty’s work tho, so i managed to figure out that it seems that Qt isn’t launching.

Aug 27 15:43:23 sol systemd-coredump[15788]: [🡕] Process 15786 (plasma-discover) of user 1000 dumped core.

                                         Stack trace of thread 15786:
                                         #0  0x00007fbc43af6d22 raise ( + 0x3cd22)
                                         #1  0x00007fbc43ae0862 abort ( + 0x26862)
                                         #2  0x00007fbc43f2e94e _ZNK14QMessageLogger5fatalEPKcz ( + 0x9094e)
                                         #3  0x00007fbc44536c05 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv ( + 0x130c05)
                                         #4  0x00007fbc445370f9 _ZN22QGuiApplicationPrivate21createEventDispatcherEv ( + 0x1310f9)
                                         #5  0x00007fbc44167fab _ZN23QCoreApplicationPrivate4initEv ( + 0x2c9fab)
                                         #6  0x00007fbc4453a0b7 _ZN22QGuiApplicationPrivate4initEv ( + 0x1340b7)
                                         #7  0x00007fbc4517071e _ZN19QApplicationPrivate4initEv ( + 0x16071e)
                                         #8  0x000055ae3cfd708a n/a (plasma-discover + 0x1508a)
                                         #9  0x00007fbc43ae1b25 __libc_start_main ( + 0x27b25)
                                         #10 0x000055ae3cfd7e7e _start (plasma-discover + 0x15e7e)

set mark: …skipping…

Anyone got any helpful ideas for me here? I’m kind of at my wits end.

Hi @powernub, and welcome!

Try logging into the TTY and running/updating/syncing with pamac.

sudo pamac checkupdates && sudo pamac update -a

I don’t know if it’ll work or not, but it might, since pamac is Manjaro-orientated and contains a lot of customizations for Manjaro. See: Why pamac over pacman?

oh and the problem does not seem to be plasma-dicover, since ost of the coredumps in the logs (one for each sddm restart (Autologin is on!))

Aug 27 16:51:24 sol systemd-coredump[16157]: [🡕] Process 16153 (kglobalaccel5) of user 1000 dumped core.

                                         Stack trace of thread 16153:
                                         #0  0x00007f36d185bd22 raise ( + 0x3cd22)
                                         #1  0x00007f36d1845862 abort ( + 0x26862)
                                         #2  0x00007f36d1c9394e _ZNK14QMessageLogger5fatalEPKcz ( + 0x9094e)
                                         #3  0x00007f36d229bc05 _ZN22QGuiApplicationPrivate25createPlatformIntegrationEv ( + 0x130c05)
                                         #4  0x00007f36d229c0f9 _ZN22QGuiApplicationPrivate21createEventDispatcherEv ( + 0x1310f9)
                                         #5  0x00007f36d1eccfab _ZN23QCoreApplicationPrivate4initEv ( + 0x2c9fab)
                                         #6  0x00007f36d229f0b7 _ZN22QGuiApplicationPrivate4initEv ( + 0x1340b7)
                                         #7  0x00007f36d22a00dc _ZN15QGuiApplicationC1ERiPPci ( + 0x1350dc)
                                         #8  0x0000563cfc2380a8 n/a (kglobalaccel5 + 0x20a8)
                                         #9  0x00007f36d1846b25 __libc_start_main ( + 0x27b25)
                                         #10 0x0000563cfc23845e n/a (kglobalaccel5 + 0x245e)

Aug 27 16:51:24 sol systemd[652]: Failed to start KDE Global Shortcuts Server.
Aug 27 16:51:24 sol kglobalaccel5[16174]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

                                      Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.

i will try that now.

pamac should never be used with sudo. It has its own built-in authentication support. :slight_smile:

1 Like

So that core dump seems to have been a false track. I now have removed almost everything from the AUR, and had a pacman -Syuu complete successfully, created a new user to login with, but still after entering the password on sddm’s login prompt, absolutely nothing happens.

When i try to call plasmashell from a console, however, i get the following:
plasmashell: symbol lookup error: /usr/lib/ undefined symbol: _ZN4KJob14percentChangedEPS_mNS_14QPrivateSignalE
Tbh, i have no idea what that means. Anyone?

Hi @powernub,

Did you try the commands I specified?

Note: They’re pamac, not pacman.


They’d be:

pamac checkupdates && pamac update -a

yes, i did that yesterday, and it kicked me off to just how effed up the system was in regards to AUR-sourced stuff that system parts depended on. will do it again now, for good measure, but now it is just three AUR pkgs left that it’s reinstalling.

Ok, now it just says “nothing left to do”.

Did you check for and merge any .pacnew files?

You can check for any with:

sudo find /etc/ -name '*.pacnew'

And merge said files, removing the .pacnew files afterward.

If that’s not it, then I honestly don’t know. :man_shrugging:

1 Like

there are a lot of *.pacnew files there. But i would much rather try to pinpoint the problem my GUI has, do you have any suggestions on where to look for hints?
I am not getting error messages via journalctl, the xorg log looks inconspicious as well. There must be some way of figuring out what happens or rather, doesn’t happen correctly when starting plasmashell, but i am not knowledgeable enough to make sense of that pne error message i am getting when starting plasmashell form the console:

plasmashell: symbol lookup error: /usr/lib/ undefined symbol: _ZN4KJob14percentChangedEPS_mNS_14QPrivateSignalE

That’s why it is important to merge the .pacnew files. They might contain a setting, or value or something neccesary with the upgrade.

Part of a good upgrade is handling any .pacnew files. And since there is a lot, it would seem you’ve not dealt with them for quite some time.

a Misconfiguration (so an umerged or many unmerged .pacnew files) can easily cause the GUI to malfunction, so they need to be sorted out first.

1 Like

they are mostly fstab, sudoers, resolv.conf, hosts, gshadow, and libvirt stuff. but i will look into the more arcane stuff i dont know there. however, all of that still seems to be just shooting for a lucky find, wouldn’t it make more sense to try and figure out what goes wrong in the first place?

It would, and that’s part of it, IMHO.

It’s referencing a file and uable to find it, so can’t use it, so throws the error. And I am too stupid to know where specifically, so if someone knows, or you’re able to find out it’s cool. But I honestly don’t think it’d make a difference.

Fact of the matter is, whether on purpose, because of ignorance or by accident, you’ve got many .pacnew files hanging around any or many of which can cause an, or the error. And it should be resolved.

I, personally, am unable to tell you where the error comes from, so if you want something more specific, I won’t be able to help you.

(I’m not even sure I’m right and will be able to help as is. But I AM sure the .pacnew files needs to be handled sooner rather than later.)

1 Like