Hi, in my custom plasmoid, when I access a plasmoid.config value from the config dialogue without having used it from the plasmoid before, the plasmoid subsequently fails to access plasmoid.configuration. See https://github.com/Fuchs/hoppla-sa/commit/0bc8ca22e966f438453d2a34f34cce7836502425#diff-52c7b097dabe3c69cef049acf7f74fdb which fixes it in my case. Before that commit, one could 1) reload plasma 2) right click the plasmoid and open the configuration dialogue 3) save config, close config dialogue 4) open the plasmoid by clicking on it 5) subsequent access to plasma.configuration will fail, leading to the plasmoid not being able to read out the URL and thus contact the Hue bridge
Can you define: "subsequent access to plasma.configuration will fail?" as in the object is null? Or it gets unexpected values, or it crashes?
(In reply to David Edmundson from comment #1) > Can you define: > "subsequent access to plasma.configuration will fail?" > > > as in the object is null? Or it gets unexpected values, or it crashes? It doesn't crash (as in: plasma), however, when I tried to use trim on the variable later on (see the code) it was undefined, when I tried to print plasmoid.configuration to get some debug info it basically did nothing / stopped there.
(In reply to David Edmundson from comment #1) > Can you define: > "subsequent access to plasma.configuration will fail?" > > > as in the object is null? Or it gets unexpected values, or it crashes? David does the extra info in comment 2 assist in diagnosing this?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!