[SOLVED] My neon just went BOOM and I can't fix it

[Don B. Cilly]

Neon Testing, Plasma 5.17.90.
I had to get up at 3:30 AM (reasons irrelevant). Started the computer.
Everything is missing, panel, analog clock, wallpaper. Only the conky and Latte Dock. Right-clicking (or long-clicking) on the desktop does nothing.
I have no panel so I can't get to System Settings.
Good thing I have the Dock so I can run some things... but System Settings isn't there. If I try anything from Latte like Add Widgets or Configure, it disappears, so no luck there.
I have Konsole though. If I type systemsettings5 I get:
systemsettings5: symbol lookup error: /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kirigami/org.kde.desktop.so: undefined symbol: _ZN8Kirigami13PlatformTheme24setActiveBackgroundCo lorERK6QColor
Hotkeys do nothing.

I tried re-updating and rebooting, no luck.
What would Linus do?

[SpecialEd]

>>>>>
What would Linus do?

Restore from his backups.

[kubicle]

Everything is missing, panel, analog clock, wallpaper. Only the conky and Latte Dock. Right-clicking (or long-clicking) on the desktop does nothing.

This sounds like plasmashell is not running. First try running plasmashell from krunner (or konsole if you wish to see possible error messages).

You can also run some basic package fixing commands:

sudo dpkg --configure -a
sudo apt -f install
sudo apt update && sudo apt full-upgrade

The systemsettings5 error seems like a problem with qt libs

[Don B. Cilly]

Plasmashell from konsole gives me 168 lines (I pasted them into kate) of
org.kde.plasma: invalid metadata "/usr/lib/x86_64-linux-gnu/qt5/plugins/[assorted-stuff].so"
The .so files are there, but not human-readable.

And some other stuff like:
plasmashell: symbol lookup error: /usr/lib/x86_64-linux-gnu/qt5/plugins/kf5/kirigami/org.kde.desktop.so: undefined symbol: _ZN8Kirigami13PlatformTheme24setActiveBackgroundCo lorERK6QColor

sudo apt -f install says

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

The 4 not upgraded are wine conflicts.
apt list --upgradable
Listing... Done
wine-stable/bionic 5.0.0~bionic amd64 [upgradable from: 4.0.3~bionic]
wine-stable-amd64/bionic 5.0.0~bionic amd64 [upgradable from: 4.0.3~bionic]
wine-stable-i386/bionic 5.0.0~bionic i386 [upgradable from: 4.0.3~bionic]
winehq-stable/bionic 5.0.0~bionic amd64 [upgradable from: 4.0.3~bionic]

sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Starting pkgProblemResolver with broken count: 0
Starting 2 pkgProblemResolver with broken count: 0
Done
0 upgraded, 0 newly installed, 0 to remove and 4 not upgraded.

sudo apt update && sudo apt full-upgrade says:

Starting pkgProblemResolver with broken count: 1
Starting 2 pkgProblemResolver with broken count: 1
Investigating (0) wine-stable:amd64 < 4.0.3~bionic -> 5.0.0~bionic @ii umU Ib >
Broken wine-stable:amd64 Depends on wine-stable-i386:amd64 < none @un H > (= 5.0.0~bionic)
Considering wine-stable-i386:i386 0 as a solution to wine-stable:amd64 1
Holding Back wine-stable:amd64 rather than change wine-stable-i386:amd64
Investigating (0) winehq-stable:amd64 < 4.0.3~bionic -> 5.0.0~bionic @ii umU Ib >
Broken winehq-stable:amd64 Depends on wine-stable:amd64 < 4.0.3~bionic | 5.0.0~bionic @ii umH > (= 5.0.0~bionic)
Considering wine-stable:amd64 1 as a solution to winehq-stable:amd64 0
Holding Back winehq-stable:amd64 rather than change wine-stable:amd64
Try to Re-Instate (1) wine-stable:amd64
Try to Re-Instate (1) winehq-stable:amd64
Done
Calculating upgrade... Done
The following packages have been kept back:
wine-stable winehq-stable
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded

Dmesg gives no obvious errors... except maybe the last line, but that is long after boot. The last line at boot - Btrfs loaded - I don't understand, since I don't have any btrfs partitions, but then.
[Fri Jan 24 09:48:50 2020] Btrfs loaded, crc32c=crc32c-intel
[Fri Jan 24 10:11:04 2020] perf: interrupt took too long (2526 > 2500), lowering kernel.perf_event_max_sample_rate to 79000

Restoring from backup... what? The whole system? Not really up-to-date, except /home, and even that... :·/
/usr/lib/x86_64-linux-gnu/qt5/plugins/ ?
Some metadata directory under /home?

[kubicle]

Could be that there is a version mismatch between qt5/kf5/plasma (Neon testing is volatile, and should be used for testing only for this reason).

Do you remember any (significant) upgrades prior to this, you can check your apt history (by reading /var/log/apt/history.log) for recent upgrades.

[acheron]

The reason for the 'boom' is an issue after switching the job that builds kirigami from frameworks. The new one is not copying the .debs from unstable to testing repos as it should, while other parts of frameworks the built against it do copy ok.

Hence the symbol lookup error. Parts of your frameworks built against code changes in kirigami that the debs you have do not include.

It will get sorted soon I hope.

[Don B. Cilly]

The last upgrade before the crash was pretty big. ~180 MB. Yesterday, Start-Date: 2020-01-23 18:21:38
The one just after the crash (this morning, Start-Date: 2020-01-24 03:41:37) was equally big. Didn't fix it.
The string qt5 is not in the log. The string kf5 is in a lot of packages.

[EDIT] Times are in CET (as in Rome-Paris-Madrid ;·).

[Don B. Cilly]

The reason for the 'boom' is an issue after switching the job that builds kirigami from frameworks. ...
It will get sorted soon I hope.

You mean all the trillions of people ;·) using neon Testing are presently testing the solidity of the walls with their foreheads?
Well, in that case, it should be fixed soon.
The devs are probably facing heavily armed mobs outside their places...

[claydoh]

Testing Edition64-bit
Featuring pre-release KDE software built the same day from bugfix branches. Good for testing. There is no QA. Will contain bugs.

[Don B. Cilly]

Yeah, well, I know that. I'm not complaining, am I? This is more of a tarantula than a bug though... :·)
Still... they haven't fixed it... yet :·/

~$ sudo apt update && sudo apt full-upgrade
Reading package lists... Done
Building dependency tree       
Reading state information... Done
...
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
~$
~$ foxtrot uniform charlie kilo
Error: no swearing is allowed in this konsole.
~$ :·(

[acheron]

It might be possible in the short term to work around the problem by upgrading your kirigami .debs manually using the ones here:

https://archive.neon.kde.org/unstabl...n/k/kirigami2/

[Don B. Cilly]

I got three. For amd64.
Kirigami2-dev and qml-module complain about depending on libkf5kirigami and won't install and libkf5kirigami complains that it breaks package qml-module - and won't install.
Any tips on what I should do with them?
And if I could install them, I would just reboot and see? Anything else?

[acheron]

I got three. For amd64.
Kirigami2-dev and qml-module complain about depending on libkf5kirigami and won't install and libkf5kirigami complains that it breaks package qml-module - and won't install.
Any tips on what I should do with them?
And if I could install them, I would just reboot and see? Anything else?

I just tried this on today's testing ISO that would not start. Plasmashell crashes on start.

do

dpkg --list | grep kirigami

to see what you have installed

Download the corresponding debs from the link I gave to a new folder, and in that folder do

dpkg -i *.deb

You have to install all the debs in one command like that, because they depend on each other at that exact build version.

After that, I could start the ISO ok.

[Don B. Cilly]

You have to install all the debs in one command like that, because they depend on each other at that exact build version.

Bingo. That worked perfectly. Thank you.
Boy, having the dock and no Plasma was like working with Unity. 'Orrible

[acheron]

This should, in theory, be fixed without needing a workaround now,