Bug 384776 - org.kde.plasma.lock_logout: hibernate and sleep buttons don't work
Summary: org.kde.plasma.lock_logout: hibernate and sleep buttons don't work
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.10.5
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
: 383638 384814 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-09-16 18:10 UTC by Markus S.
Modified: 2017-10-04 20:26 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus S. 2017-09-16 18:10:32 UTC
Approximately 2 months ago the hibernate and sleep buttons stopped working:
The confirmation dialogue "Do you want to suspend to RAM..." doesn't appear after
clicking the sleep button of the panel, similar for the hibernate button.

Platform: Opensuse tumbleweed

Running lock_logout in plasmoidviewer produces the following messages:

% plasmoidviewer --applet org.kde.plasma.lock_logout
QML debugging is enabled. Only use this in a safe environment.
WARNING: Cannot find style "org.kde.desktop" - fallback: "/usr/lib64/qt5/qml/QtQuick/Controls/Styles/Desktop"
qml: View QML loaded
Toolbox not loading, toolbox package is either invalid or disabled.
qml: New Containment: ContainmentInterface(0x5631a08d98c0)
WARNING: Cannot find style "org.kde.desktop" - fallback: "/usr/lib64/qt5/qml/QtQuick/Controls/Styles/Desktop"
file:///usr/share/plasma/shells/org.kde.plasma.plasmoidviewershell/contents/configuration/AppletConfiguration.qml:171:17: QML Rectangle: Binding loop detected for property "width"
file:///usr/share/plasma/shells/org.kde.plasma.plasmoidviewershell/contents/configuration/AppletConfiguration.qml:171:17: QML Rectangle: Binding loop detected for property "height"
file:///usr/share/plasma/shells/org.kde.plasma.plasmoidviewershell/contents/configuration/AppletConfiguration.qml:171:17: QML Rectangle: Binding loop detected for property "height"
trying to show an empty dialog


qml: +++ new BUtton textsJa,Nein
qml: +++ new BUtton textsJa,Nein
file:///usr/lib64/qt5/qml/org/kde/plasma/components/QueryDialog.qml:92:17: QML Text: Binding loop detected for property "width"
file:///usr/lib64/qt5/qml/org/kde/plasma/components/QueryDialog.qml:92:17: QML Text: Binding loop detected for property "width"
file:///usr/lib64/qt5/qml/org/kde/plasma/components/Dialog.qml:335:9: QML Item: Binding loop detected for property "height"
file:///usr/lib64/qt5/qml/org/kde/plasma/components/Dialog.qml:335:9: QML Item: Binding loop detected for property "height"
file:///usr/lib64/qt5/qml/org/kde/plasma/components/Dialog.qml:301:5: QML Item: Binding loop detected for property "width"
file:///usr/lib64/qt5/qml/org/kde/plasma/components/private/AppManager.js:44: ReferenceError: parent is not defined
file:///usr/lib64/qt5/qml/org/kde/plasma/components/Dialog.qml:151: TypeError: Cannot read property 'mainItem' of null
Comment 1 Kai Uwe Broulik 2017-09-18 13:14:04 UTC
Git commit 7482bef085e67949be14c1d04dd8e532f4cf73e7 by Kai Uwe Broulik.
Committed on 18/09/2017 at 13:11.
Pushed by broulik into branch 'master'.

Pass item to rootObject() since it's now a singleton

The "parent" used to be resolved by the place where the utils.js was imported from.
However, it was changed into a singleton and now this didn't work.

M  +1    -1    src/declarativeimports/plasmacomponents/qml/Dialog.qml
M  +1    -1    src/declarativeimports/plasmacomponents/qml/Sheet.qml
M  +2    -2    src/declarativeimports/plasmacomponents/qml/private/AppManager.js

https://commits.kde.org/plasma-framework/7482bef085e67949be14c1d04dd8e532f4cf73e7
Comment 2 Kai Uwe Broulik 2017-09-18 15:35:06 UTC
*** Bug 384814 has been marked as a duplicate of this bug. ***
Comment 3 Markus S. 2017-09-18 19:50:50 UTC
Thanks for fixing this!
Comment 4 Kai Uwe Broulik 2017-09-18 19:56:09 UTC
Sorry for breaking it in the first place ;)
Comment 5 Christoph Feck 2017-10-04 20:26:47 UTC
*** Bug 383638 has been marked as a duplicate of this bug. ***