Plasma issueshttps://invent.kde.org/groups/plasma/-/issues2024-03-23T19:38:55Zhttps://invent.kde.org/plasma/plasma-desktop/-/issues/113Make important desktop functionality not depend on the presence of applets2024-03-23T19:38:55ZBharadwaj RajuMake important desktop functionality not depend on the presence of appletsA lot of what we consider baseline features in a modern desktop — volume keys, media keys, clipboard management, notifications — are handled by the applets in Plasma.
This implementation detail creates a very common pathway for users to...A lot of what we consider baseline features in a modern desktop — volume keys, media keys, clipboard management, notifications — are handled by the applets in Plasma.
This implementation detail creates a very common pathway for users to break their systems by removing applets because they don't use the applets themselves, not knowing that those applets are the sole providers of related functionality in Plasma.
Proposal: we move appropriate parts of the applets into KDED services.
Applets which need this treatment:
- [x] Media Player applet provides media keys ([bug 409190](https://bugs.kde.org/show_bug.cgi?id=409190), [bug 460771](https://bugs.kde.org/show_bug.cgi?id=460771))
- [x] Audio Volume applet provides volume keys ([bug 391578](https://bugs.kde.org/show_bug.cgi?id=391578), plasma-pa!221)
- [ ] Clipboard applet provides clipboard management ([bug 443036](https://bugs.kde.org/show_bug.cgi?id=443036))
- [ ] Notifications applet provides notifications (this might be difficult)
Former metabug about this on Bugzilla: https://bugs.kde.org/show_bug.cgi?id=4430366.1https://invent.kde.org/plasma/plasma-mobile/-/issues/337volume: Port away from registering volume keys now that it's done in a kded s...2024-03-23T01:24:29ZDevin Linvolume: Port away from registering volume keys now that it's done in a kded service automaticallySee https://invent.kde.org/plasma/plasma-pa/-/merge_requests/221See https://invent.kde.org/plasma/plasma-pa/-/merge_requests/2216.1https://invent.kde.org/plasma/discover/-/issues/16Assign apps a safety rating using an at-a-glance "safety scorecard"2024-03-22T21:18:25ZNate GrahamAssign apps a safety rating using an at-a-glance "safety scorecard"This idea was inspired by something I saw in https://www.youtube.com/watch?v=j0IhajCNs14, which is quite a relevant take on Linux app deployment.
Anyway, the idea is to replace the current mishmash of metadata relating to an app's licen...This idea was inspired by something I saw in https://www.youtube.com/watch?v=j0IhajCNs14, which is quite a relevant take on Linux app deployment.
Anyway, the idea is to replace the current mishmash of metadata relating to an app's license and permissions with a simple "Safety scorecard" UI, with expanded information available on a separate page/sheet for people who want to know all the nitty-gritty details. License and permissions are quite technical and my sense is that most users don't really want to dive into this stuff; they would benefit from a higher level safety scorecard that provides at-a-glance information. If we do this, we could relocate the sections about the app's license and permissions to the nerdy expanded view, saving space on the main page and making its information simpler and more relevant.
In essence, we would rate apps on a scale of safety from 0 to 3 points:
- 3 points: Maximum safety
- 2 points: Safe*
- 1 point: Possibly unsafe
- 0 points: Unsafe
Points would be awarded like so:
- +1 point: all licenses are FOSS (0 points if the app has any proprietary licenses)
- +1 point: sandboxed (0 points if it's not sandboxed, or if it's got such broad perimssions that the sandbox is effectively escaped, e.g. full read/write filesystem access in a Flatpak)
- +1 point: packaged by the developer, a member of the developer's organization like the KDE release team, or a trustworthy 3rd-party packager like the user's distro (0 points if the app has been packaged by a random person in a PPA, OBS repo, Flathub package from an internet rando not endorsed by the developer, etc)
Over time we could potentially refine this and add more criteria too.
For apps listed as "Probably Unsafe" or "Unsafe," the simple view would list the factors in a short bulleted list that are causing Discover to rate the app badly.
---
*The reason for 2 out of 3 points being listed as "Safe" is that you really need a combination of at least 2 of the above issues to result in a real problem. For example if an app is not sandboxed, but it's FOSS and packaged by a trustworthy packager, the fact that it has full access to your system is probably not a significant issue. Likewise, a proprietary app that's sandboxed and packaged by someone trustworthy has been checked out and at least contains a means for the user to restrict its activities via the sandbox.
@teams/vdghttps://invent.kde.org/plasma/plasma-nm/-/issues/7Add secret service support2024-03-22T14:20:33ZAndreas SchneiderAdd secret service supportPlease add secret service support that a password manager other than kwallet could be used. This could be done using https://github.com/frankosterfeld/qtkeychain which supports kwalletd and secret service.
See also:
* https://github.com...Please add secret service support that a password manager other than kwallet could be used. This could be done using https://github.com/frankosterfeld/qtkeychain which supports kwalletd and secret service.
See also:
* https://github.com/keepassxreboot/keepassxc/issues/3679
* https://invent.kde.org/office/kmymoney/-/merge_requests/170
* https://specifications.freedesktop.org/secret-service/https://invent.kde.org/plasma/plasma-desktop/-/issues/124Plasma 6: Weird flickering/artifacts below/in task manager2024-03-22T11:28:06ZGuy ChaitPlasma 6: Weird flickering/artifacts below/in task managerIssue demo:
![Screencast_20240322_114512](/uploads/2126a1d4dd5dd6d61593bdaf45b65ea9/Screencast_20240322_114512.webm)
I just noticed it also happens in a very small portion in the middle of the right border.
It also seems to only be ...Issue demo:
![Screencast_20240322_114512](/uploads/2126a1d4dd5dd6d61593bdaf45b65ea9/Screencast_20240322_114512.webm)
I just noticed it also happens in a very small portion in the middle of the right border.
It also seems to only be happening in my primary, left monitor.
I suspect it might be related to my exotic(?) resolution setup:
![image](/uploads/256b7cda97ff3a49dd686e262a1e0d76/image.png){height=250px}
PS, please consider mirroring (is bidirectional possible? IDK) the actual issues page(?) to GitHub, it was really hard getting even to this (probably wrong, according to the huge red sign, but I got tired) location.
Also thank you for your hard work, the fractional scaling is amazing and I really enjoy it (and the new UI)!https://invent.kde.org/plasma/plasma-mobile/-/issues/46Add split-screen option2024-03-21T19:31:01ZIvan RancicAdd split-screen optionSo, something like in Android. Activated perhaps by double tap on app switcher button. Once first app has taken upper half of the screen, lower half can show a grid of apps user commonly used in split-screen mode and "below" that, by swi...So, something like in Android. Activated perhaps by double tap on app switcher button. Once first app has taken upper half of the screen, lower half can show a grid of apps user commonly used in split-screen mode and "below" that, by swiping u on the grid, can bring up standard app drawer with the rest of the apps.6.2https://invent.kde.org/plasma/plasma-mobile/-/issues/319actiondrawer: Unable to scroll on landscape quick settings panel2024-03-21T18:21:27ZDevin Linactiondrawer: Unable to scroll on landscape quick settings panelWhen the quick settings overflow in the landscape quick settings panel, it is not possible to scroll in order to see all of the quick settings, the parent flicking item eats the eventWhen the quick settings overflow in the landscape quick settings panel, it is not possible to scroll in order to see all of the quick settings, the parent flicking item eats the event6https://invent.kde.org/plasma/plasma-mobile/-/issues/322kcms/cellularnetwork: Add 5G support2024-03-21T18:21:27ZDevin Linkcms/cellularnetwork: Add 5G supportRequires upgrading many interfaces in [modemmanager-qt](https://invent.kde.org/frameworks/modemmanager-qt) to the latest API version.Requires upgrading many interfaces in [modemmanager-qt](https://invent.kde.org/frameworks/modemmanager-qt) to the latest API version.6.1https://invent.kde.org/plasma/plasma-mobile/-/issues/336kcms/wifi: Support WPA32024-03-21T18:21:27ZDevin Linkcms/wifi: Support WPA3There is now a WPA3 enum entry
Bug: https://bugs.kde.org/show_bug.cgi?id=483729There is now a WPA3 enum entry
Bug: https://bugs.kde.org/show_bug.cgi?id=4837296.1https://invent.kde.org/plasma/plasma-mobile/-/issues/315kded/autodetectapn: Run when SIM is swapped2024-03-21T18:21:27ZDevin Linkded/autodetectapn: Run when SIM is swappedThis isn't a high priority item because from my knowledge, we can't hotswap SIMs in any of the supported phones right now, but we eventually should have `kded/autodetectapn` run when a new SIM is detected. Currently it just runs on sessi...This isn't a high priority item because from my knowledge, we can't hotswap SIMs in any of the supported phones right now, but we eventually should have `kded/autodetectapn` run when a new SIM is detected. Currently it just runs on session launch.https://invent.kde.org/plasma/plasma-mobile/-/issues/328shortcuts: Steam deck hardware volume buttons and media keys are not mapped2024-03-21T18:21:27Zted changshortcuts: Steam deck hardware volume buttons and media keys are not mappedHi,
I notice the media volume controls do not work. I think its not device specific because my deck and trackpoint have media keys. These keys do not work on both devices.
```
Device: AT Translated Set 2 keyboard
Kernel: ...Hi,
I notice the media volume controls do not work. I think its not device specific because my deck and trackpoint have media keys. These keys do not work on both devices.
```
Device: AT Translated Set 2 keyboard
Kernel: /dev/input/event0
Group: 8
Seat: seat0, default
Capabilities: keyboard
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock: n/a
Left-handed: n/a
Nat.scrolling: n/a
Middle emulation: n/a
Calibration: n/a
Scroll methods: none
Click methods: none
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: n/a
Rotation: 0.0
```
```
event0 KEYBOARD_KEY +25.596s KEY_VOLUMEDOWN (114) pressed
event0 KEYBOARD_KEY +25.811s KEY_VOLUMEDOWN (114) released
event0 KEYBOARD_KEY +26.314s KEY_VOLUMEUP (115) pressed
event0 KEYBOARD_KEY +26.510s KEY_VOLUMEUP (115) released
```
```
zypper info plasma6-mobile
Repository 'packman-essentials' is out-of-date. You can run 'zypper refresh' as root to update it.
Loading repository data...
Reading installed packages...
Information for package plasma6-mobile:
---------------------------------------
Repository : KDE Frameworks and Plasma (openSUSE_Tumbleweed)
Name : plasma6-mobile
Version : 6.0.1-kf.1.1
Arch : x86_64
Vendor : obs://build.opensuse.org/KDE
Installed Size : 5.8 MiB
Installed : Yes
Status : out-of-date (version 6.0.0-kf.2.1 installed)
Source package : plasma6-mobile-6.0.1-kf.1.1.src
Upstream URL : https://www.kde.org/
Summary : Plasma shell for mobile devices
Description :
Plasma shell for mobile devices.
```6https://invent.kde.org/plasma/plasma-mobile/-/issues/229navigationpanel: Show close keyboard button when keyboard is open in gesture-...2024-03-21T18:21:27ZDevin Linnavigationpanel: Show close keyboard button when keyboard is open in gesture-only modeThis allows us to use the keyboard without needing the swipe down gesture.This allows us to use the keyboard without needing the swipe down gesture.6.1https://invent.kde.org/plasma/plasma-mobile/-/issues/236[navigationpanel] Switch to gesture only mode by default2024-03-21T18:21:27ZDevin Lin[navigationpanel] Switch to gesture only mode by defaultI think for Plasma 6 we should switch to gesture mode by default, because:
- It takes up screen real estate
- Buttons can be accidentally pressed
- The navigation bar being a different colour from apps (especially ones with graphics in t...I think for Plasma 6 we should switch to gesture mode by default, because:
- It takes up screen real estate
- Buttons can be accidentally pressed
- The navigation bar being a different colour from apps (especially ones with graphics in the footer) looks really ugly
However, in order for this to happen, we need gestures to be better, which means these should be resolved:
- https://invent.kde.org/plasma/plasma-mobile/-/issues/186
- https://invent.kde.org/plasma/plasma-mobile/-/issues/1736.1https://invent.kde.org/plasma/plasma-mobile/-/issues/343taskswitcher: Sort by most recently used2024-03-21T18:21:27ZDevin Lintaskswitcher: Sort by most recently usedThis feature has been missing since we moved the task switcher to KWin.This feature has been missing since we moved the task switcher to KWin.6.1https://invent.kde.org/plasma/plasma-mobile/-/issues/335startupfeedback: Use neutral color background in dark schemes2024-03-21T18:21:27ZDevin Linstartupfeedback: Use neutral color background in dark schemesCurrently it always detects a color from the application icon that is being opened. This sometimes chooses an extremely light color which looks really bright at night. Use a neutral dark background instead when our color scheme is dark.Currently it always detects a color from the application icon that is being opened. This sometimes chooses an extremely light color which looks really bright at night. Use a neutral dark background instead when our color scheme is dark.6.1https://invent.kde.org/plasma/plasma-mobile/-/issues/330startupfeedback: Pressing home button while it is open causes homescreen to o...2024-03-21T18:21:26ZDevin Linstartupfeedback: Pressing home button while it is open causes homescreen to open app drawerWe expect to go to the original state (pages), not the second home state.We expect to go to the original state (pages), not the second home state.6.1https://invent.kde.org/plasma/plasma-mobile/-/issues/338startupfeedback: Disappears when quicksettings drawer starts opening2024-03-21T18:21:26ZOMG! Its... Bugsbanestartupfeedback: Disappears when quicksettings drawer starts openingWhen opening an app, if I start opening the quick settings drawer from the top of the screen, the startup feedback instantly disapears. If I wait, the app still opens, but this it isn't clear this is still happening without the feedback....When opening an app, if I start opening the quick settings drawer from the top of the screen, the startup feedback instantly disapears. If I wait, the app still opens, but this it isn't clear this is still happening without the feedback.
See the attached video, showing opening Tokodon and then immediately starting to pull down to open the quicksettings drawer![StartupFeedbackNoMo](/uploads/3efedfdf40639a774216f48d3aee28e8/StartupFeedbackNoMo.mp4)6.1https://invent.kde.org/plasma/plasma-mobile/-/issues/214lookandfeel/logout: Draw above lockscreen2024-03-21T18:21:26ZDevin Linlookandfeel/logout: Draw above lockscreenUse the new lockscreen protocol to draw the logout popup over the lockscreen.
See https://invent.kde.org/andreyev/lockscreenoverlaytest/-/tree/qml-engineUse the new lockscreen protocol to draw the logout popup over the lockscreen.
See https://invent.kde.org/andreyev/lockscreenoverlaytest/-/tree/qml-engine6.1https://invent.kde.org/plasma/plasma-mobile/-/issues/334lockscreen: Restore passwordless logins2024-03-21T18:21:26ZDevin Linlockscreen: Restore passwordless loginsIt was disabled in the Plasma 6 porting because the implementation didn't seem to work, need to reinvestigate adding it backIt was disabled in the Plasma 6 porting because the implementation didn't seem to work, need to reinvestigate adding it back6.1https://invent.kde.org/plasma/plasma-mobile/-/issues/326quicksettings: Panel window doesn't move to the correct screen when containme...2024-03-21T18:21:26Zted changquicksettings: Panel window doesn't move to the correct screen when containment is movedHi everyone,
I notice the drop down menu does not change positions after choosing the default display. You need to relogin to change where the Quick Settings Panel drops down.
Steps to reproduce the bug.
1. Plug in an external monitor
...Hi everyone,
I notice the drop down menu does not change positions after choosing the default display. You need to relogin to change where the Quick Settings Panel drops down.
Steps to reproduce the bug.
1. Plug in an external monitor
2. Open kde plasma mobile quick settings panel to confirm the location
3. Open the display settings.
4. Change the default display.
5. Pull down the quick setting menu on the new display.
Observed behavior.
The drop menu position does not change after switching the default display and clicking apply. I notice the top status bar does move to the default screen. The quick settings drop down will move to the default display location once you log out and log back in.
Expected behavior.
The drop down menu can be move any time the user changes the default display in the settings menu.
KDE 6 plasma mobile
Information for package plasma6-mobile:
---------------------------------------
Repository : KDE Frameworks and Plasma (openSUSE_Tumbleweed)
Name : plasma6-mobile
Version : 6.0.1-kf.1.1
Arch : x86_64
Vendor : obs://build.opensuse.org/KDE
Installed Size : 5.8 MiB
Installed : Yes
Status : out-of-date (version 6.0.0-kf.2.1 installed)
Source package : plasma6-mobile-6.0.1-kf.1.1.src
Upstream URL : https://www.kde.org/
Summary : Plasma shell for mobile devices
Description :
Plasma shell for mobile devices.6.1