https://bugs.kde.org/show_bug.cgi?id=440082

mins...@protonmail.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mins...@protonmail.com

--- Comment #4 from mins...@protonmail.com ---
Hi,

I found this ticket after I had a similar problem. Not sure how to get a
backtrace when the program hangs, but this is the output when I start the
system settings from the terminal:

$ systemsettings5 --version
systemsettings 5.22.5
$ systemsettings5
kf.coreaddons: A plugin with the keyword "kwinoptions" was already registered.
A keyword must be unique!
kf.coreaddons: Two plugins with the same interface( QObject ) were registered.
Use keywords to identify the plugins.
kf.coreaddons: Two plugins with the same interface( QObject ) were registered.
Use keywords to identify the plugins.
kf.coreaddons: Two plugins with the same interface( QObject ) were registered.
Use keywords to identify the plugins.
QQmlEngine::setContextForObject(): Object already has a QQmlContext
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:279:18: QML
QQuickItem*: Binding loop detected for property "implicitWidth"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:279:18: QML
QQuickItem*: Binding loop detected for property "implicitWidth"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:279:18: QML
QQuickItem*: Binding loop detected for property "implicitWidth"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:279:18: QML
QQuickItem*: Binding loop detected for property "implicitWidth"
file:///usr/lib64/qt5/qml/org/kde/kirigami.2/BasicListItem.qml:279:18: QML
QQuickItem*: Binding loop detected for property "implicitWidth"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
QQmlEngine::setContextForObject(): Object already has a QQmlContext
---------- click on removable storage ----------
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/ldap.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/ldap.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/sieve.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/sieve.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/about.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/about.so'"
kf.coreaddons: no metadata found in
"/usr/lib64/qt5/plugins/kf5/kio/activities.so" "Failed to extract plugin meta
data from '/usr/lib64/qt5/plugins/kf5/kio/activities.so'"
kf.coreaddons: no metadata found in
"/usr/lib64/qt5/plugins/kf5/kio/bookmarks.so" "Failed to extract plugin meta
data from '/usr/lib64/qt5/plugins/kf5/kio/bookmarks.so'"
kf.coreaddons: no metadata found in
"/usr/lib64/qt5/plugins/kf5/kio/filenamesearch.so" "Failed to extract plugin
meta data from '/usr/lib64/qt5/plugins/kf5/kio/filenamesearch.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/filter.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/filter.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/fish.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/fish.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/man.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/man.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/mtp.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/mtp.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/network.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/network.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/nfs.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/nfs.so'"
kf.coreaddons: no metadata found in
"/usr/lib64/qt5/plugins/kf5/kio/recentdocuments.so" "Failed to extract plugin
meta data from '/usr/lib64/qt5/plugins/kf5/kio/recentdocuments.so'"
kf.coreaddons: no metadata found in
"/usr/lib64/qt5/plugins/kf5/kio/settings.so" "Failed to extract plugin meta
data from '/usr/lib64/qt5/plugins/kf5/kio/settings.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/sftp.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/sftp.so'"
kf.coreaddons: no metadata found in
"/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so" "Failed to extract plugin meta
data from '/usr/lib64/qt5/plugins/kf5/kio/thumbnail.so'"
kf.coreaddons: no metadata found in
"/usr/lib64/qt5/plugins/kf5/kio/applications.so" "Failed to extract plugin meta
data from '/usr/lib64/qt5/plugins/kf5/kio/applications.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/desktop.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/desktop.so'"
kf.coreaddons: no metadata found in
"/usr/lib64/qt5/plugins/kf5/kio/videodvd.so" "Failed to extract plugin meta
data from '/usr/lib64/qt5/plugins/kf5/kio/videodvd.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/akonadi.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/akonadi.so'"
kf.coreaddons: no metadata found in "/usr/lib64/qt5/plugins/kf5/kio/pop3.so"
"Failed to extract plugin meta data from
'/usr/lib64/qt5/plugins/kf5/kio/pop3.so'"
---------- now hangs ----------

After some investigation, I found what the problem was in my case. Checking
~/.config/kded_device_automounterrc I found about 15000 entries from docker. No
idea why exactly they where there. I deleted almost everything, leaving only:

[General]
AutomountEnabled=true
AutomountOnPlugin=false

And then the system settings did not hang anymore when clicking on removable
storage. So in my case it was not a real deadlock, but it just took so long to
process all entries that it looked like one (I tested leaving around 2000
entries and after some waiting the system settings managed to open).

I would not really consider this KDE's fault, but maybe there can be something
done to prevent so many entries in that file? Or maybe warn the user that the
dialog is about to load more than 1000 entries so that the user does not think
it is a deadlock?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to