KMail requires it, and I think it doesn’t support sqlite anymore.
I only see kmail depending on some akonadi and pim packages … which I would assume is the reason for the ‘depend’ … and so may similarly be functional with whatever can operate akonadi … in this case posteegresql seems like a likely choice.
But IANAA. (I am not an akonadi-user) 
1 Like
Still, I would like to know why everything worked fine up until Monday, and why it suddenly won’t work at all anymore now, even though nothing had changed to my settings.
Finding the root cause of the problem should be the goal for fixing what went wrong without having to nuke everything related to Plasma in my main account. 
I guess you have no timeshift backup from the time before the issue occurred?
1 Like
As the matter of fact, I think I do, but given that I hadn’t changed anything to my settings and hadn’t installed anything, I considered it pointless to try that.
I’ll look into it right away. 
If nothing else, it should possibly show you the cause if updating again…
1 Like
Well, I’ve restored only my $HOME from the backup, but it’s no use. It’s still the same thing. So whatever the cause may be, it must be something from outside of my home directory. 
Well, if you can make sense of that, I cannot, and like I said, I hadn’t changed anything in my $HOME.
[nx-74205:/dev/pts/1][/home/aragorn]
[aragorn] > journalctl -xe | grep plasmashell
Aug 02 11:10:41 nx-74205 plasmashell[2019]: Checking screens: available: (QScreen(0x55b0ce368300, name="DP-1")) redundant: QHash() fake: QSet() all: (QScreen(0x55b0ce368300, name="DP-1"))
Aug 02 11:10:41 nx-74205 plasmashell[2019]: Checking screens: available: (QScreen(0x55b0ce368300, name="DP-1")) redundant: QHash() fake: QSet() all: (QScreen(0x55b0ce368300, name="DP-1"))
Aug 02 11:10:41 nx-74205 dbus-daemon[1903]: [session uid=1000 pid=1903] Activating via systemd: service name='org.kde.ActivityManager' unit='plasma-kactivitymanagerd.service' requested by ':1.17' (uid=1000 pid=2019 comm="/usr/bin/plasmashell --no-respawn")
Aug 02 11:10:41 nx-74205 plasmashell[2019]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Aug 02 11:10:41 nx-74205 plasmashell[2019]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
Aug 02 11:10:41 nx-74205 plasmashell[2019]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Aug 02 11:10:41 nx-74205 plasmashell[2019]: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
Aug 02 11:10:41 nx-74205 plasmashell[2019]: kf.plasma.quick: Applet preload policy set to 1
Aug 02 11:10:41 nx-74205 dbus-daemon[1903]: [session uid=1000 pid=1903] Activating via systemd: service name='org.kde.ksystemstats' unit='plasma-ksystemstats.service' requested by ':1.17' (uid=1000 pid=2019 comm="/usr/bin/plasmashell --no-respawn")
Aug 02 11:10:42 nx-74205 plasmashell[2019]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/ThumbnailStrip.qml"
Aug 02 11:10:42 nx-74205 plasmashell[2019]: Cyclic dependency detected between "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml" and "file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/NotificationHeader.qml"
Aug 02 11:10:42 nx-74205 plasmashell[2019]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:407: TypeError: Cannot read property 'Window' of null
Aug 02 11:10:42 nx-74205 plasmashell[2019]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:43:5: QML MouseArea: Cannot anchor to an item that isn't a parent or sibling.
Aug 02 11:10:42 nx-74205 plasmashell[2019]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemmonitor/contents/ui/main.qml:43:5: QML MouseArea: Cannot anchor to an item that isn't a parent or sibling.
Aug 02 11:10:43 nx-74205 plasmashell[2019]: qt.svg: link #g14830 is undefined!
Aug 02 11:10:43 nx-74205 plasmashell[2019]: qt.svg: link #g14830 is undefined!
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///home/aragorn/.local/share/plasma/plasmoids/org.kde.plasma.volumewin7mixer/contents/ui/MediaController.qml:202:4: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///home/aragorn/.local/share/plasma/plasmoids/org.kde.plasma.volumewin7mixer/contents/ui/InputManager.qml:6:2: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///home/aragorn/.local/share/plasma/plasmoids/org.kde.plasma.volumewin7mixer/contents/ui/DynamicFilterModel.qml:30:34: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///home/aragorn/.local/share/plasma/plasmoids/org.kde.plasma.volumewin7mixer/contents/ui/DynamicFilterModel.qml:30:34: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///home/aragorn/.local/share/plasma/plasmoids/org.kde.plasma.volumewin7mixer/contents/ui/DynamicFilterModel.qml:30:34: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///home/aragorn/.local/share/plasma/plasmoids/org.kde.plasma.volumewin7mixer/contents/ui/DynamicFilterModel.qml:30:34: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///home/aragorn/.local/share/plasma/plasmoids/org.kde.plasma.volumewin7mixer/contents/ui/DynamicFilterModel.qml:30:34: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///home/aragorn/.local/share/plasma/plasmoids/org.kde.plasma.volumewin7mixer/contents/ui/Mpris2DataSource.qml:159:31: QML Connections: Implicitly defined onFoo properties in Connections are deprecated. Use this syntax instead: function onFoo(<arguments>) { ... }
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:47: TypeError: Cannot read property 'location' of null
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:48: TypeError: Cannot read property 'location' of null
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:49: TypeError: Cannot read property 'location' of null
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:46: TypeError: Cannot read property 'location' of null
Aug 02 11:10:43 nx-74205 plasmashell[2019]: qt.svg: <input>:65:6: Could not resolve property: #b
Aug 02 11:10:43 nx-74205 plasmashell[2019]: qt.svg: <input>:65:6: Could not resolve property: #c
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:301: TypeError: Cannot read property 'Window' of null (exception occurred during delayed function evaluation)
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
Aug 02 11:10:43 nx-74205 plasmashell[2019]: qml: PlasmaExtras.ScrollArea is deprecated. Use PlasmaComponents3.ScrollView instead.
Aug 02 11:10:43 nx-74205 plasmashell[2019]: file:///usr/lib/qt/qml/org/kde/plasma/extras/PlaceholderMessage.qml:238:5: QML Heading: Binding loop detected for property "verticalAlignment"
I’ve also already run a consistency check on my akonadi data, and it gave me a healthy report, so it’s not that either. KMail also works perfectly fine.
My CPU temperature is going sky-high again, so I’m going to switch back to my other account for now…
I have just checked, my output does not have this:
Aug 02 11:10:41 nx-74205 plasmashell[2019]: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
And according to this:
Found a solution which said to remove kactivitymanagerd folder.
rm -rf .local/share/kactivitymanagerdSo mods you can close the thread now, ty.
So, you could try that…
1 Like
I will try that this evening — thank you. I’m going to go to bed now, because I’ve been up all night and it’s closing in on noon over here right now.
1 Like
I very much doubt that the mariadb issue is anything to do with your problem. Every report I’ve seen indicates that this is purely a cosmetic reporting issue and doesn’t lead to a rise in cpu temperature like real cpu load would. I’m running mariadb myself all day every day and my cpu temp right now is 35C which is idle temp.
kactivitymanagerd seems like a good lead. There are reports of it going berserk, seems to be related to it’s (sqlite) database becoming corrupted for unknown reasons. You can try either deleting the whole ~/.local/share/kactivitymanagerd/ folder as suggested above or just ~/.local/share/kactivitymanagerd/resources/ as in this post.
1 Like
Then it is likely not kmanagerd.
sqlite? the binary contains a lot of quirks but if a process has gone rogue and hammered the deb file - it is possible the database is damaged.
But I am 
about the about the fact that nothing was changed.
My apology - I missed this in the descriptions
It was as understand - a temporary start of an USB based system - and a subseqent restart after testing was done.
I assume you can get into a TTY or a live system.
There was a recent mitigation added - but that was for AMD - so likely not the issue.
I don’t really know why I am suggesting this - perhaps the mention of spectre-meltdown-checker - what if you boot to the grub menu - then edit and add mitigations=off to kernel command line?
So - although you have restored your home without success - it is an issue with a Plasma service.
You already mentioned plasmashell as the likely offender - so perhaps going over the relevant rc files in .config will reveal a damaged file?
My old friend Midnight Commander has sometimes helped me deduct whether a configuration file was corrupted.
Perhaps checking the log would clarify that …
1 Like
I don’t see how new user = no problem, restore old user = problem, proves that the issue is outside of $HOME. Proves the opposite if anything.
2 Likes
I’ve deleted it, but still no change.
Correct.
Yes, no problem there.
But if that is the cause, then why is my second user account — from which I’m typing this — not affected?
I still say try the ‘configuration related’ steps:
(I will augment them this time so that everything is backed up)
cd ~/.config
for j in plasma*; do mv -- "$j" "${j%}.bak"; done
mv Trolltech.conf Trolltech.conf.bak
kbuildsycoca5 --noincremental
cd ~
Reboot.
See if its ‘fixed’ … if so … start moving your configurations back one-by-one … find the culprit.
1 Like
Your trick worked, albeit that I did get a semi-lockup again when dragging icons from the ordered list to the favorites section in the Application Dashboard. It froze for like 25 seconds each time, but simply right-clicking the icons and then choosing “Add to Favorites” worked without a problem.
And of course, the 100% IO wait is back again because I am now in my main account, where I am using akonadi. But so far, everything works normally again, except for one thing: the AltGr key does not work the way it should, while it does in my other account.
I’ve always had the keyboard daemon disabled — so that section does not work. AltGr does work, but it’s completely mapped the wrong way. Its characters do not correspond to what it says on my keyboard anymore. It’s like my keyboard type has changed.
Wait, let me check my locale settings. 
Edit: I just don’t get it. In my test account, I have the correct keyboard layout, and in this account, it has changed somehow. I have no alternative keyboard layouts defined, but if I enable that setting and click on the preview for my Belgian keyboard, it shows an incorrect layout, while in my other account, it shows the correct one.
This is starting to take on surreal proportions. In both accounts, there is no special keyboard layout defined, so they’re using the default keyboard layout. And yet it’s a different layout between both accounts.
Sigh, the crap just never ends. 
I suppose a check could be
locale -a
And a few home config files may be at play:
cat ~/.xbindkeysrc
cat ~/.Xmodmap
showkey may also show something … must be run from tty:
showkey --scancodes
1 Like
[nx-74205:/dev/pts/1][/home/aragorn]
[aragorn] > cat ~/.config/plasma-localerc
[Formats]
LANG=en_US.UTF-8
LC_COLLATE=nl_BE.UTF-8
LC_MEASUREMENT=nl_BE.UTF-8
LC_MONETARY=nl_BE.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_PAPER=en_GB.UTF-8
LC_TELEPHONE=en_GB.UTF-8
LC_TIME=en_GB.UTF-8
useDetailed=true
[Translations]
LANGUAGE=en_US
[nx-74205:/dev/pts/1][/home/aragorn]
[aragorn] > cat ~/.Xmodmap
cat: /home/aragorn/.Xmodmap: No such file or directory
[nx-74205:/dev/pts/1][/home/aragorn]
[aragorn] > cat ~/.xbindkeysrc
cat: /home/aragorn/.xbindkeysrc: No such file or directory
[nx-74205:/dev/pts/1][/home/aragorn]
[aragorn] > locale -a
C
C.utf8
C.UTF-8
en_AU.utf8
en_GB.utf8
en_US.utf8
nl_BE.utf8
POSIX
[nx-74205:/dev/pts/1][/home/aragorn]
[aragorn] >
Edit 1: This is once again a Plasma thing, because my keyboard layout is correct in a character-mode login tty.
Edit 2: I have found the problem. 
It was ~/.local/share/kded5/keyboard/session/layout_memory.xml. I replaced it with the one from my old home directory, and now my keyboard layout is correct again.
So, that’s a problem I have managed to solve myself, but the main issue was that my normal account was completely non-functional, and it was @cscs who helped me solve that. Therefore, I award the 
to him. 
Nevertheless, I wish to thank everyone who pitched in. 
1 Like
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.