Otherwise the user needs to manually tab over to the Unlock button
first, which is annoying. And they may not even think to do it at all.
The `forceActiveFocus()` is because the stack view does not manually pass focus
to the item you push onto it; this needs to be handled manually.
BUG: 454707
The delimiter might change if the settings are changed.
By having a member variable, we still avoid re-creating the same regex for every time the runner is queried.
BUG: 454596
`wallpaper.configuration.Image` has string type, and assigning a string
value from QML to a url in C++ will truncate the string at the hash char.
This changes `image` data type to string to fix the bug.
BUG: 454692
FIXED-IN: 5.26
When running this:
~/kde/usr/lib/libexec/kscreenlocker_greet --testing --theme ~/kde/src/plasma-workspace/lookandfeel
it used to generate error like this:
/usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/UserList.qml:61:9: Unable to assign [undefined] to bool
Because not every users list model provides all the properties that
delegate expected.
This is not a public header, so we don't care about compatibility. SDDM
does not use standard Qt roles like DisplayRole or DecorationRole, so
there's little reason for this sessions model to redefine them either.
We should better align this model class with SDDM::UserModel to reduce
confusion. Enum classes might be better for some tasks, but they aren't
widely used for Qt model roles, and they require extra casts without
added safety benefits.
Caused by the context menu and the associated widget being set to the
same object, leading to an access after destruction.
Application: Klipper (klipper), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = 0x0}
#8 QObject::disconnect (member=0x0, ...)
#9 KStatusNotifierItem::~KStatusNotifierItem () at knotifications/src/kstatusnotifieritem.cpp:71
#10 KlipperTray::~KlipperTray () at plasma-workspace/klipper/tray.h:13
So that the "Apply" and "Defaults" buttons work properly.
Mostly this involves just setting appropriate object names
for the GUI controls, with some special handling for the
radio button sets.
When the lockscreen is in the screensaver mode we want the keyboard key
pressed to wake the screen to go to the password box textfield. This did
work correctly, but a code path also reset it when we get the first
prompt.
In the (currently hypothetical) case of multiple prompts we would want
to clear anything in the prompt.
This uses the existing boolean flag to handle that appropriately.
BUG: 454108
Some actions, such as middle click to mute, trigger only on press. Some applets
also need a pressed-click because of some legacy autoclose on focus change
bug.
Unfortunately, QML does not disambiguate the "pressed" property and "pressed(mouse)"
signal with argument, so this has to be done awkwardly through QMetaObject on C++ side.
BUG: 426646
BUG: 452893
FIXED-IN: 5.25.0
Calling dataChanged() with an invalid QModelIndex() triggered an assertion
inside QConcatenateTablesProxyModel (my Qt is built with assertions):
ASSERT: "from.isValid()" in file $HOME/cheri/qt5/qtbase/src/corelib/itemmodels/qconcatenatetablesproxymodel.cpp, line 623
We can not use the required properties, because it breaks the property binding.
ec79af7396 apparently fixes that, however
it is not released as part of Qt6 or is part of the KDE patch collection.
This reverts commit f3293bc59e.
BUG: 453226