Plasma Workspace merge requestshttps://invent.kde.org/plasma/plasma-workspace/-/merge_requests2024-03-25T20:32:52Zhttps://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4117applets/brightness: consistently allow setting screen brightness to 0%2024-03-25T20:32:52ZNatalie Clariusnatalie_clarius@yahoo.deapplets/brightness: consistently allow setting screen brightness to 0%Screen brightness had been artificially capped to 1% to prevent people from accidentally turning off their screen.
However this makes a useful actual minimum brightness on many screens inaccessible, and was inconsistent in behavior betw...Screen brightness had been artificially capped to 1% to prevent people from accidentally turning off their screen.
However this makes a useful actual minimum brightness on many screens inaccessible, and was inconsistent in behavior between the slider and the scroll action.
Introduce a Plasmoid configuration to deliberately and consistently allow setting screen brightness to the actual minimum.
Also remove the internal configure action, because there is no brightness KCM, so the default configuration action is unneeded and confusing.
![Screenshot_20240322_025248](/uploads/00567ccbff7df9b75ea7c6c8015e5a5e/Screenshot_20240322_025248.png)
BUG: 484033
BUG: 4834906.1https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4038[kcms/users] Show confirmation dialog before clearing fingerprints2024-03-11T14:05:33ZArthur Zamarinarthurzam@gentoo.org[kcms/users] Show confirmation dialog before clearing fingerprintsIt is very easy to accidentally click on the clear all fingerprints button, resulting in the loss of all fingerprints, which can take long minutes to re-enroll. Showing a simple confirmation dialog before should help prevent this.It is very easy to accidentally click on the clear all fingerprints button, resulting in the loss of all fingerprints, which can take long minutes to re-enroll. Showing a simple confirmation dialog before should help prevent this.6.1https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4021kcms/notifications: Exit System Notifications page on invalid source2024-03-08T22:03:50ZIsmael Asensiokcms/notifications: Exit System Notifications page on invalid sourceWhen the model resets (by pressing the Defaults or Reset buttons),
the app notification gets also reset and de-assigned from any
application (invalid rootIndex).
For the System Notifications page, with no application list, this
just sho...When the model resets (by pressing the Defaults or Reset buttons),
the app notification gets also reset and de-assigned from any
application (invalid rootIndex).
For the System Notifications page, with no application list, this
just shows a misleading placeholder text, because we cannot select
any app here. So let's go back to the main page.
It would be better not to reset the full model, or not to deselect
the app, but for now let's avoid presenting a "broken" UI.
BEFORE:
![Screenshot_20240308_110214](/uploads/fcae3083d1de6a1ca96dc3fa8426e3db/Screenshot_20240308_110214.png)6.1Ismael AsensioIsmael Asensiohttps://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3791applets/devicenotifier: show pid for blocking apps2024-02-05T17:17:29ZFushan Wenapplets/devicenotifier: show pid for blocking appsSo users can more easily kill those processes.So users can more easily kill those processes.6.1https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3687applets/clipboard: Return to Clipboard on EditPage Header2023-12-20T14:57:39ZShubham Aroraapplets/clipboard: Return to Clipboard on EditPage HeaderI have almost every time clicked the back button besides the applet name thinking it will take me back to clipboard list page but takes me back to hidden icons page.
Aligns header UI with barcode page.
![image](/uploads/5ced1fbba12b963...I have almost every time clicked the back button besides the applet name thinking it will take me back to clipboard list page but takes me back to hidden icons page.
Aligns header UI with barcode page.
![image](/uploads/5ced1fbba12b963c657c75690ff64d91/image.png)6Shubham AroraShubham Arorahttps://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3244runners/powerdevil: make suspend descriptions more user friendly2023-12-06T03:31:48ZNatalie Clariusnatalie_clarius@yahoo.derunners/powerdevil: make suspend descriptions more user friendlyThis may be less technically accurate but arguably more understandable for the average user.
@teams/usabilityThis may be less technically accurate but arguably more understandable for the average user.
@teams/usability6https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3077Add KDED module for adjusting the system time zone based on location2023-08-25T16:46:01ZKai Uwe BroulikAdd KDED module for adjusting the system time zone based on locationWe don't need accurate location data, so it just talks to the KDE geoip endpoint
directly and adjusts the timezone accordingly.
It does that only on a network with full connectivity (ie. not behind a portal),
that is not metered and not...We don't need accurate location data, so it just talks to the KDE geoip endpoint
directly and adjusts the timezone accordingly.
It does that only on a network with full connectivity (ie. not behind a portal),
that is not metered and not connected to a VPN (to avoid using the VPN gateway's
timezone inadvertendly) and only a maximum of once every hour.
The module is off-by-default to not do unsolicited network requests
and a UI to enable it (in date time KCM and/or digital clock applet settings)
is tbd.
---
@vkrause @sitter @leinir
Fixes people running around at Akademy with the wrong time on their laptops.
Since there is no UI yet, after installing, load the module manually:
```
$ qdbus org.kde.kded6 /kded org.kde.kded6.loadModule geotimezoned
```
or enable autoloading and restart KDED:
```
$ qdbus org.kde.kded6 /kded org.kde.kded6.setModuleAutoloading geotimezoned true
```
There’s a logging category `org.kde.plasma.geotimezoned` you can enable for more verbose output.
* TODO a setting in the UI to enable it6https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2780applets/manage-inputmethod: make it all about the virtual keyboard2024-01-30T16:19:47ZNate Grahamapplets/manage-inputmethod: make it all about the virtual keyboardThis widget has a bit of an identity crisis at the moment. It's called
"Input Method" but it's meant to control a virtual keyboard; its
iconography and subtitles are specific to virtual keyboards, its
"configure" action takes you to a KC...This widget has a bit of an identity crisis at the moment. It's called
"Input Method" but it's meant to control a virtual keyboard; its
iconography and subtitles are specific to virtual keyboards, its
"configure" action takes you to a KCM called "Virtual Keyboard". All
of this would be very weird and out-of-place if used to control
anything that *isn't* a virtual keyboard.
The widget also has a rather complicated interaction paradigm, doing no
fewer than five possible things when clicked on, depending on the state:
- No virtual keyboard configured -> open the Virtual Keyboard KCM
- Virtual keyboard enabled and hidden -> disable it so it won't appear
automatically when an input field supporting the textinput protocol
is focused with a touch event
- Virtual keyboard disabled and hidden -> enable it
- Virtual keyboard enabled and visible -> hide it
- Virtual keyboard enabled and hidden and a text field that doesn't
support the textinput protocol is focused -> show it if tapped with a
touchscreen, otherwise do nothing
This is very complex! And it doesn't do what is arguably the most common
thing to want to do: just show the virtual keyboard when tapped or
clicked.
This commit changes the widget to be a focused virtual keyboard
shower-and-hider. Now, either clicking or tapping on it shows the
virtual keyboard if it's hidden, and hides it when it's visible. No more
weird experience of being unable to open the virtual keyboard with a
click no matter what you do.
This commit requires
https://invent.kde.org/plasma/kwin/-/merge_requests/3895 to work and
uses new icons added in
https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/256.
BUG: 466948
FIXED-IN: 6.0
| When the virtual keyboard is hidden | When the virtual keyboard is shown |
| ----------------------------------- | ---------------------------------- |
| ![When_the_VK_is_hidden](/uploads/08aff9160e0949f55dbd00589209e809/When_the_VK_is_hidden.jpg) | ![When_the_VK_is_shown](/uploads/5edae473600de6bdb37f6eccb754a39b/When_the_VK_is_shown.jpg) |
CC @teams/usability @marcdeop @apol6https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2745Draft: Don't show unnecessary auth dialog when LUKS password is found in wallet2023-03-14T19:37:16ZNate GrahamDraft: Don't show unnecessary auth dialog when LUKS password is found in walletCurrently when mounting a LUKS-encrypted volume, if a saved password is
found in KWallet, the auth dialog still appears, but it has the password
field pre-populated. This is a bit odd and doesn't match what typically
happens when there's...Currently when mounting a LUKS-encrypted volume, if a saved password is
found in KWallet, the auth dialog still appears, but it has the password
field pre-populated. This is a bit odd and doesn't match what typically
happens when there's a saved password: it's simply sent along, without
showing a dialog at all. This commit does that here too for a smoother
workflow.
BUG: 467098
FIXED-IN: 6.0
---
Draft because this is buggy and I've reached my limit of understanding of DBus and need help. Bugs:
1. When `decryptVolume()` is run after accepting the dialog, everything works. But when it's called before the dialog is created, after checking KWallet and finding a saved password, the DBus call it runs doesn't receive a reply. Log says:
```
kf.solid.backends.udisks2: Failed to call the SolidUiServer, D-Bus said: QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
```
2. Canceling the password dialog make it spin in the tray widget
(Also this is not actually intended for 5.27; I just developed against that for now since I don't have a Plasma 6 dev environment set up yet)6https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2662Draft: kcms/users: Totally new unseen before UI for deleting users2024-03-11T14:05:35Zivan tkachenkoDraft: kcms/users: Totally new unseen before UI for deleting usersDeleting users is a scary process. It doesn't help that currently all it
takes is a double-misclick to remove a user from the system altogether
with all their files: the confirmation menu appears right on top of the
"Delete User…" button...Deleting users is a scary process. It doesn't help that currently all it
takes is a double-misclick to remove a user from the system altogether
with all their files: the confirmation menu appears right on top of the
"Delete User…" button, with the most dangerous option showing up
straight under your cursor.
Hence, let's add some safety straps: full-sized modal dialogs,
attention-drawing blurry background, extra step that require explicit
user consent, and of course some unskippable timers.
Totally not inspired by a certain gaeming platform. No way.
Note: Draft status is because this patch incorporates too much in one
chunk. It should be split and polished. Also actual deletion of users
is disabled, and replaced by a fake (random) status response, for
convenience of testers. So feel free to check it out, and don't worry
about your data!
Requires these icons: https://invent.kde.org/frameworks/breeze-icons/-/merge_requests/2476ivan tkachenkoivan tkachenkohttps://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2459Add zsh completions (compdef) for plasmawindowed2022-12-23T02:14:16Zivan tkachenkoAdd zsh completions (compdef) for plasmawindowedTaking this chance to factor out plasma_packages completions after all.
It may be quite specific, but it's already needed in 3 places.
---
Technically, plasmawindowed can take any number of arguments, not just 1. But I'm having hard ti...Taking this chance to factor out plasma_packages completions after all.
It may be quite specific, but it's already needed in 3 places.
---
Technically, plasmawindowed can take any number of arguments, not just 1. But I'm having hard times explaining it to zsh _arguments. The trick that worked with `-e` option for konsole isn't applicable for positional arguments, it seems.5.27ivan tkachenkoivan tkachenkohttps://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2419Draft: batterymonitor: Active status on inhibitions2022-12-07T19:15:07ZNicolai WeitkemperDraft: batterymonitor: Active status on inhibitionsWith this one, I'm not sure if the average user would find this useful or rather distracting:
If there are any inhibitions, like VLC playing, OBS recording or when in a Zoom meeting, the _batterymonitor_ applet would become active.
On my...With this one, I'm not sure if the average user would find this useful or rather distracting:
If there are any inhibitions, like VLC playing, OBS recording or when in a Zoom meeting, the _batterymonitor_ applet would become active.
On my PC (which doesn't have a battery), this results in the applet appearing in each of these circumstances and disappearing when all inhibitions are gone.
I personally like this, because nothing else (e.g. the icon itself) conveys information about inhibitions – otherwise I could just set the applet to always be visible.
Alternative approaches include adding a separate applet for inhibitions or making the behaviour user-configurable.5.27https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2384applets/mediacontroller: Increase visibility of the Raise action2023-07-16T01:08:30ZIsmael Asensioapplets/mediacontroller: Increase visibility of the Raise actionLet the `raise` action show on the systray header and make its
text more clear.
Follow-up to: !2366
Alternative to: !1000
![mediacontroller-action-raise](/uploads/0b8807e69551969bc2ae831032a259b0/mediacontroller-action-raise.png)
So...Let the `raise` action show on the systray header and make its
text more clear.
Follow-up to: !2366
Alternative to: !1000
![mediacontroller-action-raise](/uploads/0b8807e69551969bc2ae831032a259b0/mediacontroller-action-raise.png)
Some concerns to be addressed/considered before merging this:
@nicolasfella:
> What exactly happens on open is up to the player. It could be that your player simply doesn't implement it at all
>
> Even if it is implemented activation can't work as expected on Wayland because the interface is missing a way to pass an activation token: https://gitlab.freedesktop.org/mpris/mpris-spec/-/issues/18
@ngraham:
> Still, the fact that it doesn't work at least for Elisa will become more obvious with the UI to trigger this feature no longer hidden only in a context menu. So we should put some work into fixing it, yeah.
>
> Hiding on Wayland would be an option, albeit a sad one.6Ismael AsensioIsmael Asensiohttps://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2157[applet/appmenu] Don't reset menu when popups become focused to avoid extra f...2022-10-12T18:11:40Zivan tkachenko[applet/appmenu] Don't reset menu when popups become focused to avoid extra flickeringTest plan:
a) receive a notification while an app with a menu is active, select
text on the notification twice (there seems to be a bug in task manager
that it only updates currently active window on a second click).
Expected result: m...Test plan:
a) receive a notification while an app with a menu is active, select
text on the notification twice (there seems to be a bug in task manager
that it only updates currently active window on a second click).
Expected result: menu should stay.
b) Put a Global Menu widget on a desktop, open an app which has a menu.
Click on a menu.
Expected result: now it is possible to interact with it without a menu
instantly disappearing.
c) Open an app which has a menu on one virtual desktop, then switch to
another virtual desktop which doesn't have any windows open (so that
the Plasma desktop becomes focused).
Excepted result: menu should disappear.
d) Open some apps with menus on two different activities. Focus them on
both activities. Switch between activities via shortcut (not via pager
which might take the focus away).
Expected result: menu updates correctly.
e) Open an app with a menu on one activity, leave other activity empty.
Focus that app, and switch via shortcut as in previous test case.
Expected result: menu hides on an empty activity, but comes back on the
other one.
f) Open a single window with a menu on an otherwise empty desktop.
Minimize the window.
Expected result: menu hides when the window is minimized, and only
the desktop remains.
BUG: 404857<br/>
CCBUG: 444587<br/>
CCBUG: 449781<br/>
BUG: 449251
---
There were some other "preliminary" fixes along the way. Hopefully, altogether they will provide a smoother menu experience.5.26ivan tkachenkoivan tkachenkohttps://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2066Draft: kcms/nightcolor: New timings control UI2023-11-22T21:32:28ZBharadwaj RajuDraft: kcms/nightcolor: New timings control UIA new unified widget to see and edit Night Color times. Visual instead of purely text-based.
![image](/uploads/ea037c488cfb2637c2e2608401d9d7df/image.png)
**TODO**:
- [x] Make sure it works in RTL mode. Right now there are some calcul...A new unified widget to see and edit Night Color times. Visual instead of purely text-based.
![image](/uploads/ea037c488cfb2637c2e2608401d9d7df/image.png)
**TODO**:
- [x] Make sure it works in RTL mode. Right now there are some calculations in `HandleOnlySlider` which appear to be LTR-assuming.
- [ ] Implement some of the remaining constraints from old TimeField code, like max 700 min transition time, non-overlap, etc.
- [x] Make dragging increment in steps of 1 or 5, not 35.27https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2001Notifications KCM: Link "System notifications" from main page2024-03-04T16:34:27ZKai Uwe BroulikNotifications KCM: Link "System notifications" from main pageIt's an implementation detail that generic notification sounds for
message boxes are in a "Plasma Workspace" category. Nobody finds this.
Instead, link them from the KCM main page.
---
![Screenshot_20220808_185806](/uploads/6918f33e4e...It's an implementation detail that generic notification sounds for
message boxes are in a "Plasma Workspace" category. Nobody finds this.
Instead, link them from the KCM main page.
---
![Screenshot_20220808_185806](/uploads/6918f33e4e840ae0a3d9ebeddb5af2b2/Screenshot_20220808_185806.png)
(I noticed and fixed the missing colon after I took the screenshot ;)5.26Kai Uwe BroulikKai Uwe Broulikhttps://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1429[applet/clipboard] Add overflow button to support Touch screen2022-10-13T16:25:02ZTranter Madi[applet/clipboard] Add overflow button to support Touch screen![image](/uploads/a5b65dc8d463f2df06f9367284b956cd/image.png)![image](/uploads/a5b65dc8d463f2df06f9367284b956cd/image.png)5.27https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/1365Draft: Keyboard shortcuts to opens news windows of taskmanager tasks2023-07-24T19:32:07ZLoucura PTDraft: Keyboard shortcuts to opens news windows of taskmanager tasksMeta+Shift+<0..9> shortcuts by default, **but these defaults are not working yet**!
---
Plasma already has Meta+<0..9> keyboard shortcuts to "activate" the applications in the taskbar/task manager. But if an application is the taskbar ...Meta+Shift+<0..9> shortcuts by default, **but these defaults are not working yet**!
---
Plasma already has Meta+<0..9> keyboard shortcuts to "activate" the applications in the taskbar/task manager. But if an application is the taskbar already has a window open, that shortcut will show and focus that window, and not open a new window (which is OK).
These Meta+Shift+<0..9> shortcuts would allow opening a new window when there is already a window open of that application using only the keyboard (in the icon-only task manager). Windows and some other Linux desktops also have these shortcuts.
---
This merge request is to help fix [this feature request](https://bugs.kde.org/show_bug.cgi?id=444279), and **depends** on [this merge request for plasma-desktop](https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/803).
With these changes, the Meta+Shift+1..9 shortcuts actually appear in the Keyboard Shortcuts settings, but the default shortcuts are not working.
If I then manually assign the combination Meta+Shift+1 in the Keyboard Shortcuts settings, it actually shows as Meta+! (for my keyboard), and then the shortcut works.
I'm not knowledgeable enough in Qt/KDE to fix that.5.26