Bug 429163 - Title of System Monitor Sensor cannot be changed after closing settings with Enter key
Summary: Title of System Monitor Sensor cannot be changed after closing settings with ...
Status: RESOLVED DUPLICATE of bug 424458
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Monitor (show other bugs)
Version: master
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-11-15 17:21 UTC by axel.wikstrom
Modified: 2020-12-19 04:44 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description axel.wikstrom 2020-11-15 17:21:46 UTC
SUMMARY

Title of System Monitor Sensor widget cannot be changed after closing the settings dialog with the Enter key

STEPS TO REPRODUCE
1. Add System Monitor Sensor widget to desktop
2. Open its settings 
3. Type a new title into the "Title" field and press Enter (while focus is still in the text field)


OBSERVED RESULT
When re-opening the widget settings, the Title field is frozen and cannot be edited anymore. Neither can the Display Style be changed. The Title of cannot be changed until you log out and in again. (This does not happen when you close the dialog with the OK button)

EXPECTED RESULT
The Title and other fields should not be frozen/disabled


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 
Arch Linux 
KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.75.0
Qt Version: 5.15.1

ADDITIONAL INFORMATION
Comment 1 Patrick Silva 2020-11-15 22:31:51 UTC
I can reproduce on my Arch Linux too.

KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.1
Comment 2 Nate Graham 2020-11-16 18:58:40 UTC
Feel free to mark the status as CONFIRMED if you can confirm, Patrick. :)
Comment 3 Frank Steinmetzger 2020-12-19 01:58:22 UTC
I just spent more than an hour trying to reliably reproduce this bug and writing up a report. Lastly I found this bug report, so I'll just add my findings below.

Once triggered, this is how the bug manifests itself:

* The dropdown for diagram type does not work anymore, as Axel reported originally. When I open it, it still lists the five types (at one time, they were ordered differently), but once an item is selected and the dropdown closes, the dropdown's value is empty. Pressing apply now does not change the appearance of the actual applet in the panel.
* the dropdown (and sometimes the Title text field) does not accept keyboard focus via Tab, neither do cursor keys work inside the dropdown once it was activated with the mouse.
* the Get New Display Styles first does not work anymore, and later crashes plasma. See below for reproduction details.


My attempts at reproducing it:
I first encountered it when I entered an empty Title string. So I thought the GUI could not handle empty titles. That turned out to be wrong.
Then it also happened when I changed the diagram style. But I could not reproduce it reliably just by changing the style and pressing Apply (which is how I believe I first encountered it, but I'm not 100 % sure anymore).
Eventually I found that the dialog practically always breaks when I change a value and then close the dialog with OK.


Here is the annotated output of plasmashell to reliably reproduce it (lines beginning with # say what I am about to do). Unfortunately, I cannot provide DrConky traces, because I'm also on Arch and without debug info (and DrConky does not trigger anyways):

# first opening of settings dialog of an existing system monitor applet:

Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
QCoreApplication::postEvent: Unexpected null receiver
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.textonly/metadata.desktop"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/metadata.desktop"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.horizontalbars/metadata.desktop"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.barchart/metadata.desktop"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.linechart/metadata.desktop"
QCoreApplication::postEvent: Unexpected null receiver
file:///usr/lib/qt/qml/org/kde/newstuff/qml/QuestionAsker.qml:91:5: QML Connections: Cannot assign to non-existent property "onClosing"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.textonly/metadata.desktop"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.piechart/metadata.desktop"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.horizontalbars/metadata.desktop"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.barchart/metadata.desktop"
kf.coreaddons.desktopparser: Unable to find service type for service "KSysguard/SensorFace" listed in "/usr/share/ksysguard/sensorfaces/org.kde.ksysguard.linechart/metadata.desktop"
file:///usr/lib/qt/qml/org/kde/newstuff/qml/QuestionAsker.qml:91:5: QML Connections: Cannot assign to non-existent property "onClosing"
file:///usr/lib/qt/qml/org/kde/kirigami.2/FormLayout.qml:90:5: QML GridLayout: Binding loop detected for property "width"
file:///usr/lib/qt/qml/org/kde/newstuff/qml/Page.qml:63: TypeError: Cannot read property 'useLabel' of null
file::/ConfigAppearance.qml:125: TypeError: Cannot read property 'length' of undefined
file:///usr/lib/qt/qml/org/kde/newstuff/qml/Page.qml:63: TypeError: Cannot read property 'useLabel' of null

# clicking OK, no messages

# second opening of dialog and open click on Get New Styles:

Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext
QCoreApplication::postEvent: Unexpected null receiver

# pressing Get New Styles repeatedly shows the following error messages each time, but it still works:

file::/ConfigAppearance.qml:162: TypeError: Cannot read property 'availableFacesModel' of null
file::/ConfigAppearance.qml:162: TypeError: Cannot read property 'availableFacesModel' of null

# clicking ok:

file::/ConfigAppearance.qml:41: TypeError: Value is null and could not be converted to an object

# third opening of dialog:

Cyclic dependency detected between "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml" and "file:///usr/lib/qt/qml/org/kde/kirigami.2/styles/org.kde.desktop.plasma/Units.qml"
QQmlEngine::setContextForObject(): Object already has a QQmlContext

# Clicking Get New Styles:

kf.newstuff.core: Using a deprecated location for the knsrc file ""  - please contact the author of the software which provides this file to get it updated to use the new location
kf.newstuff.core: ""  doesn't contain a KNewStuff3 section.
KCrash: Attempting to start /usr/bin/plasmashell
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = plasmashell path = /usr/bin pid = 110524
KCrash: Arguments: /usr/bin/plasmashell
Comment 4 Frank Steinmetzger 2020-12-19 01:59:56 UTC
Oh and I think this is the same problem as in BKO #424458.
Comment 5 Nate Graham 2020-12-19 04:44:06 UTC
Thanks!

*** This bug has been marked as a duplicate of bug 424458 ***