You are not logged in.
I use extra/plasma-vault 6.0.5-1
When I try to launch the Vault plasmoid by clicking on it on the systemtray, I get this error :
> Sorry! There was an error loading Vaults.
together with this message:
>file:///usr/share/plasma/plasmoids/org.kde.plasma.vault/contents/ui/main.qml:102:36: Cannot assign object of type "QQC2.Action" to property of type "Action_QMLTYPE_132*" as the former is neither the same as the latter nor a sub-class of it.
As a result, I can't access any of my Vaults.
My data :
Operating System: Arch Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.0.0
Qt Version: 6.7.1
Kernel Version: 6.9.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor
Memory: 15.5 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2
Thanks for any information
Last edited by jimarch (2024-06-02 08:43:09)
Offline
Your system isn't fully up to date. My info:
Operating System: Arch Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.2-arch1-1 (64-bit)
Graphics Platform: X11
Try updating again. Try a different, perhaps more up-to-date mirror.
Offline
I run into the same problem, not only the plasma-vault shows error, but kdeconnect also have a similar error message:
file:///usr/share/plasma/plasmoids/org.kde.plasma.vault/contents/ui/main.qml:102:36: Cannot assign object of type "QQC2.Action" to property of type "Action_QMLTYPE_100*" as the former is neither the same as the latter nor a sub-class of it.
file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/main.qml:50:25: Type FullRepresentation unavailable
file:///usr/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/FullRepresentation.qml:63:32: Cannot assign object of type "Action" to property of type "Action_QMLTYPE_100*" as the former is neither the same as the latter nor a sub-class of it.
My system info shows that:
Operating System: Arch Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.6.32-1-lts (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 3600 6-Core Processor
Memory: 15.5 GiB of RAM
Graphics Processor: AMD Radeon RX 6700 XT
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7B89
System Version: 1.0
This should not be a partial upgrade problem.
Offline
Try
rm -r ~/.cache/plasmashell/qmlcache
Offline
Moderator Notes::
@arojas : Lck0427 wanted to reply "Tried, not working."
@Lck0427 : you hit report instead of reply (happens to all of us occasionally).
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
I have carefully updated my system, checking all the dates of the soft taken on AUR and eliminating all the obsolete GIT source files.
I applied the order proposed by Arojas
I have restarted the system several times, without any changes.
Like Lck0427, kdeconnect is also affected by the same difficulty...
This is the current state of my system :
Operating System: Arch Linux
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.2.0
Qt Version: 6.7.1
Kernel Version: 6.9.2-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 2600X Six-Core Processor
Memory: 15.5 Gio of RAM
Graphics Processor: NVIDIA GeForce GTX 1650 SUPER/PCIe/SSE2
What to do?
Offline
As a result, I can't access any of my Vaults.
If you use cryfs for as your cryptographic engine you should be able to decrypt with cli so all is not lost.
Offline
@d_fajardo : Thank you very much.
For information, my problems with Vault and Kdeconnect date of May 25th, when passing 6.0.4-1 -> 6.0.5-1.
My system was unaffected by any problems prior to that date.
Offline
News on this problem!
I just discovered that when I log in with another user’s account, on the same system of course,
[I have in my family two other people who also use this computer],
Vault and Kdeconnect work perfectly ...
So I have somewhere in my config or cache files or elsewhere? (but not in the system partition) a config that prevents me from running Vault and Kdeconnect...
Any idea where to look??
I have already applied the order proposed by Arojas
rm -r ~/. cache/plasmashell/qmlcache
but unsuccessfully
Offline
I had the same problem a few days ago after updating to 6.0.5 version of kde apps.
It turned out to be a config problem, not a cache problem.
I still had a kde4 directory (in ~/.config) : problem disappeared after deleting it.
How did I find out it was the problem ? Well I logged out of kde, moved ~/.config to ~/.config.backup and logged in again. Problem had vanished. Then slowly I reincorporated subdirectories from ~/.config.backup (each time logging out and in again) until I found that kde4 directory was the culprit.
I had never removed this kde4 directory because I thought that either it was still usefull or it wasn't and in this latter case it shouldn't have any impact except for wasting a small amount of disk space. Obviously I was wrong.
Offline
YES ! a priori, I solved my problem
After a laborious search, and by comparing the installations of the different users of my computer, I found the faulty file which is:
. config/plasma-org.kde.plasma.desktop-appletsrc
by deleting it, I was able to recover access to Vault and KDEConnect
If it can help others, do not hesitate ;-)
@daysfled
Thanks for the suggestion but I did not have a KDE4 directory in my installation. the problem came from elsewhere.
Offline
YES ! a priori, I solved my problem
After a laborious search, and by comparing the installations of the different users of my computer, I found the faulty file which is:
. config/plasma-org.kde.plasma.desktop-appletsrc
by deleting it, I was able to recover access to Vault and KDEConnect
If it can help others, do not hesitate ;-)
Had the same issue with kde vault (even though i don't use it?) and did what you did but i noticed it forced me to re-setup my desktop setup/settings. Anyone aware of a way to fix that doesn't requore having to re-setup things from scratch?
Offline
@stearic
Yes, the command actually clears desktop setup/settings...
And that’s its purpose. Which is a lesser evil when everything is completely or partially blocked.
As a precaution, you must always make a copy of the files you erase in order to restore the file in case of plasma corruption...
or if the desired effect is not the right one.
Offline
Had the same error with the weather widget, clearing the file `~/.config/plasma-org.kde.plasma.desktop-appletsrc` as @jimarch suggested made it work - but as @stearic pointed out, you have to redo your panel setup afterwards.
Offline
In my case somehow I failed to install both cryfs and/or encfs from extra. Once I installed those, I was able to open my vaults.
Offline