Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: plasmashell not starting (Read 435 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

plasmashell not starting

Did the upgrade to plasma 6.2, plasmashell didn't  start. Starting from terminal got me this:
Code: [Select]
plasmashell: symbol lookup error: /usr/lib/libLayerShellQtInterface.so.6: undefined symbol: _ZN15QtWaylandClient14QWaylandWindow9wlSurfaceEv, version Qt_6_PRIVATE_API

Re: plasmashell not starting

Reply #1 –
I think it's a bug in Qt this also happened to me after the 6.8.0 update. Luckily I still had the previous 6.7.3 version of the qt6 packages, did a downgrade, rebooted and it's working fine.

I hope someone has already reported it and that the Qt devs fix it in the next update.

EDIT: You should downgrade every qt6 related package if you can. Sorry for the bad advice. Also, the morphing tooltips effect (or whatever it's called) isn't working, that's the only weird thing I got after downgrading.

Re: plasmashell not starting

Reply #2 –
Thanks! That worked.
Code: [Select]
pacman -Q | grep ^qt6- | cut -d ' ' -f 1
lists all needed packages, which you can then find with the correct versions in /var/cache/pacman/pkg and do
Code: [Select]
sudo pacman -U filename
Or if you have downgrade from AUR, you can do
Code: [Select]
sudo downgrade `pacman -Q | grep ^qt6- | cut -d ' ' -f 1`
and write 6.7.3 repeatedly, until it finishes

Re: plasmashell not starting

Reply #3 –
 hi,
same here this morning.
sddm screen frozen with X11,, or black screen with wayland.
i started by the obvious, downgrading the kernel to 6.11.2 and nvidia drivers  :P  but no luck
thanks for the suggestion, i downgraded all qt6 packages (to version 6.7.3xxx instead of 6.8xx), and it works again :)

Re: plasmashell not starting

Reply #4 –
Same issue. Sadly I deleted my pacman cache while trying to downgade via the archive, only to see that the archive is broken and 404s when requesting qt6-tools (and possibly others) :\

Any other way I can downgrade? Or maybe fixed packages are already in the testing repos so I can try them out?

Re: plasmashell not starting

Reply #5 –
Yep, after upgrading with the gremlins repos the k* suite of packages is updated to fix the issue.

Re: plasmashell not starting

Reply #6 –
Some pkgs are still in the build queue for gremlins. Once all are done they will be moved to stable/world.

artist
 

Re: plasmashell not starting

Reply #8 –
having issues with plasma aswell, i can use applications (that happen to start on login) but my desktop is black and i cant really do anything, tried downgrading, rebooted, same issue   https://pastebin.com/Damm4K9T most recent system upgrade

Re: plasmashell not starting

Reply #9 –
The KDE packages are being moved to world/stable now. Running pacman -Syu after the mirrors have synced should fix the issue. If not then pls report details and log files.

artist

Re: plasmashell not starting

Reply #10 –
Quote from: nous – on
https://archive.artixlinux.org/packages/q/qt6-tools/
https://archive2.artixlinux.org/packages/q/qt6-tools/

The former contains 6.7.2, the  latter also 6.7.3...

What I tried was pointing my artix mirror to https://archive.artixlinux.org/repos/2024/10/15/ (and earlier, which also failed due to other missing packages). Is this not the way you downgrade packages?

Re: plasmashell not starting

Reply #11 –
Now that the packages are moved to stable i can log in x11 but not in wayland, te monitors do not output anything. This is the "cat ~/.local/share/sddm/wayland-session.log":
Could not create wayland socket

Works now

Re: plasmashell not starting

Reply #13 –
HokariKanae and TheBestKmanEver, thank you for reporting back.

artist

Re: plasmashell not starting

Reply #14 –
For anyone equally screwed as I was:
On boot, in GRUB, highlight your Artix entry and press e to edit the boot line.
Find the row that begins with "linux" and append init=/bin/sh at the end to drop to shell on boot.
Press Ctrl+X to boot.

If that shell is functional for you, run an upgrade to salvage your system.
In my case, I have multiple partitions and those weren't mounted, so the shell wasn't a good one.

In that case, cd /etc/xdg/autostart/ and use the editor of your choice (or echo/cat, strings and >>) to create a new file "emergency-terminal.desktop" with the following contents:
Code: [Select]
[Desktop Entry]
Type=Application
Name=Autostart Terminal for Emergencies
TryExec=xterm
Exec=xterm
StartupNotify=false

X-GNOME-Autostart-Phase=Initialization
X-KDE-autostart-phase=1
Reboot the system.
In my shell, even the reboot was f*cked - if you have magic enabled, you can do
Code: [Select]
echo _reisub > /proc/sysrq-trigger
to trigger the reboot via shell. Otherwise: Power/Reset button.

Let it boot normally and log in at the Plasma login.
It will still be broken, but there should now be a terminal that autostarted on login.
Since you booted and logged in properly, this terminal will be in a coherent state and you can use it to upgrade the system as normal/as directed in previous posts in this thread.

Reboot again after the upgrade, and Plasma should be working again.

Since the terminal will come up again anyway, go ahead and
Code: [Select]
sudo mv /etc/xdg/autostart/emergency-terminal.desktop /etc/xdg/autostart/emergency-terminal.bak
That should disable the autostart, according to the Internet. I haven't rebooted since, so I haven't verified that.
If it still comes up, just delete the file.