[SOLVED] Plasma won't start after upgrading kwayland-server 5.20->5.21

yolorkit · 2021-03-26 10:09:49

Maybe its because kwin is still 5.20.5 ? When i downgrade just kwayland-server it starts as it normally would even though i don't use wayland session.

There are still some 5.20.5 packages probably causing problems:
local/kde-gtk-config 5.20.5-2.0 (plasma)
local/kdecoration 5.20.5-1.0 (plasma)
local/kwayland-server 5.20.5-1.0 (plasma)
local/kwin 5.20.5-1.0 (plasma)
local/plasma-desktop 5.20.5-2.0 (plasma)
local/plasma-pa 5.20.5-1.0 (plasma)

Last edited by levi (2021-04-08 13:21:12)

levi · 2021-03-26 17:55:46

That's a reasonable suggestion, but it ought to be possible to get logs out of this thing to indicate at the very least the first thing that's causing it to fall over. The exact location of logs might differ depending on how you're starting plasma; are you starting it from a display manager or are you starting it manually after logging in?

abaumann · 2021-03-28 08:23:23

I fear a lot of things got into disorder: glib2 cannot be built currently because of expired PGP keys:

/usr/bin/gtk-query-immodules-3.0: symbol lookup error: /usr/lib/libpango-1.0.so.0: undefined symbol: g_memdup2

Gnome is in a major release update.

kde-cli-tools always get into a cycle with plasma-workspace.

yolorkit · 2021-03-29 08:39:35

levi wrote:

That's a reasonable suggestion, but it ought to be possible to get logs out of this thing to indicate at the very least the first thing that's causing it to fall over. The exact location of logs might differ depending on how you're starting plasma; are you starting it from a display manager or are you starting it manually after logging in?

Hi, i'm starting it from display manager.

levi · 2021-03-29 11:21:21

Okay, I'd expect those logs to be available under journalctl

yolorkit · 2021-03-30 08:56:48

Hi, here is the output of journalctl -xe

levi · 2021-03-30 14:09:03

Okay, I see errors like:

kwin_x11[875]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 630, resource id: 8388613, major code: 18 (ChangeProperty), minor code: 0

and then later

plasmashell[912]: file:///usr/share/plasma/packages/org.kde.desktoptoolbox/contents/ui/ToolBoxButton.qml:217: TypeError: Cannot call method 'action' of null

Do you have that file, and what does it look like?
Other files are in places like:

file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml
file:///usr/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml
ile:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml
file:///usr/lib/qt/qml/org/kde/plasma/core/private/DefaultToolTip.qml

before everything starts falling over:

Process 3836 (kglobalaccel5) of user 1000 dumped core.

I was hoping we'd see it trying to load a shared library under the wrong name or something simpler like that, but it's possible it's not been well tested with duff qml files and fails ungracefully under such situations.

yolorkit · 2021-03-31 10:21:44

Here is zip archive with those 5 qml files

yolorkit · 2021-04-08 11:16:04

With recent update that had newer kwin it works.

Arch Linux

#1 2021-03-26 10:09:49

[SOLVED] Plasma won't start after upgrading kwayland-server 5.20->5.21

#2 2021-03-26 17:55:46

Re: [SOLVED] Plasma won't start after upgrading kwayland-server 5.20->5.21

#3 2021-03-28 08:23:23

Re: [SOLVED] Plasma won't start after upgrading kwayland-server 5.20->5.21

#4 2021-03-29 08:39:35

Re: [SOLVED] Plasma won't start after upgrading kwayland-server 5.20->5.21

#5 2021-03-29 11:21:21

Re: [SOLVED] Plasma won't start after upgrading kwayland-server 5.20->5.21

#6 2021-03-30 08:56:48

Re: [SOLVED] Plasma won't start after upgrading kwayland-server 5.20->5.21

#7 2021-03-30 14:09:03

Re: [SOLVED] Plasma won't start after upgrading kwayland-server 5.20->5.21

#8 2021-03-31 10:21:44

Re: [SOLVED] Plasma won't start after upgrading kwayland-server 5.20->5.21

#9 2021-04-08 11:16:04

Re: [SOLVED] Plasma won't start after upgrading kwayland-server 5.20->5.21

Board footer