Plasma issueshttps://invent.kde.org/groups/plasma/-/issues2021-03-29T14:01:22Zhttps://invent.kde.org/plasma/plasma-mobile/-/issues/70homescreen: If two applications have the same name, only one is shown2021-03-29T14:01:22ZDevin Linhomescreen: If two applications have the same name, only one is shownkweather and gnome-weather both have the same .desktop name, and when both are installed, only one of them shows up in the application drawer.kweather and gnome-weather both have the same .desktop name, and when both are installed, only one of them shows up in the application drawer.https://invent.kde.org/plasma/kwin/-/issues/33kwin_wayland coredumps are useless without prior manual intervention2021-04-19T15:37:54ZNate Grahamkwin_wayland coredumps are useless without prior manual interventionWe get bug reports right now that are un-actionable because kwin_wayland coredumps are too large and get truncated, making them un-debuggable when kwin_wayland crashes. Typically one of the following situations arises:
1. User reports b...We get bug reports right now that are un-actionable because kwin_wayland coredumps are too large and get truncated, making them un-debuggable when kwin_wayland crashes. Typically one of the following situations arises:
1. User reports bug on kwin_wayland crashing; backtrace is useless because coredump is truncated
2. User reports bug on some app or Plasma crashing; bug turns out to be caused by KWin crashing; bug triager asks reporter to get a kwin_wayland backtrace with coredumpctl; reporter obliges; backtrace is useless because coredump is truncated
In both cases, the user and bug triager alike end up frustrated, and the bug is not actionable, wasting everyone's time.
Apparently it is possible to fix this by adding `ExternalSizeMax=6G` to `/etc/systemd/coredump.conf`. But since this has to be done ahead of time, *before* the crash, it does not help people reporting an existing crash.
Is there a reason why kwin_wayland coredumps need to be so huge? They are much smaller on X11, so we don't run into this problem there.https://invent.kde.org/plasma/plasma-mobile/-/issues/65GTK Popover menus open but interaction just closes popover2022-04-25T01:06:25ZThe 3DmaNGTK Popover menus open but interaction just closes popoverI am submitting this with the understanding that GTK might not be a top priority this early on for a Qt based environment, but I am reporting anyway so that it is tracked. Hopefully this can be tracked down so that devs can support Plasm...I am submitting this with the understanding that GTK might not be a top priority this early on for a Qt based environment, but I am reporting anyway so that it is tracked. Hopefully this can be tracked down so that devs can support Plasma Mobile with their GTK apps.
With any GTK app I have tried on Plasma Mobile (Manjaro or Arch) that uses GTK popover for a menu, the popover opens however any content in the popover does not function. Touching any buttons, check boxes, links, switches etc. in the popover just closes it with no actions taken.
This does seem to function fine in the KDE Neon builds which are older, so I am not sure what changed between then and current plasma that caused this.
Apps tested that have this issue:
ABV Calc: https://gitlab.com/The3DmaN/abv-calc
GFeeds: https://gitlab.gnome.org/World/gfeeds
![PopoverGTK](/uploads/7b0971ab88ca71fae8c1fa0a74ea698f/PopoverGTK.jpg)https://invent.kde.org/plasma/plasma-pass/-/issues/1Document OATH requirement2023-03-05T22:56:32ZAdriaan de GrootDocument OATH requirementOATH is now required; it isn't mentioned in the README as a dependency, and there's no documentation in the CMakeLists.txt why it's there or what it is for. It would be nice to replace the `find_package(... REQUIRED)` by a non-required f...OATH is now required; it isn't mentioned in the README as a dependency, and there's no documentation in the CMakeLists.txt why it's there or what it is for. It would be nice to replace the `find_package(... REQUIRED)` by a non-required find along with suitable package properties. Then the `feature_summary()` can do the right thing and users / packagers / whoever can deal with it more easily.https://invent.kde.org/plasma/latte-dock/-/issues/45All Firefox windows have same preview if media is playing2021-02-02T19:46:57ZMario SaboAll Firefox windows have same preview if media is playingIf there is a tab in Firefox that is playing media (or it started playing and media is paused currently), all other windows have same preview and title even if that tab is not focused. I provided some screenshots to make it more clear. "...If there is a tab in Firefox that is playing media (or it started playing and media is paused currently), all other windows have same preview and title even if that tab is not focused. I provided some screenshots to make it more clear. "Preview" displayed is not even real preview but thumbnail used to present video (eg. youtube thumbnail). I tested it with Vimeo and it has same problem, but playing video in Facebook doesn't trigger it and it works normal. It seems like it could be Firefox only issue as I tried it in Chromium and it's working normal. I also tried VLC and I can't open multiple windows of VLC but one opened shows correct preview.
I tried to disable that audio indicator but there is no difference.
![Screenshot_20210124_144824](/uploads/f51b1dc203ead85f1ffa27b526c8442d/Screenshot_20210124_144824.png)![Screenshot_20210124_145303](/uploads/4d7e0946d746de91da25b2d20786d2f5/Screenshot_20210124_145303.png)https://invent.kde.org/plasma/libplasma/-/issues/3Dock Case: PopUp placement2022-09-22T15:49:52ZMichail VourlakosDock Case: PopUp placement**Introduction**
As of Plasma 5.21 the applets layout strategy for plasma panels has changed.
In the past, applets received all the panel available space(thickness) and as such were responsible, from implementation point of view, to pr...**Introduction**
As of Plasma 5.21 the applets layout strategy for plasma panels has changed.
In the past, applets received all the panel available space(thickness) and as such were responsible, from implementation point of view, to provide proper padding and margins. It is obvious of course that this strategy did not succeed from HIG point of view and as such a newer and better is now implemented.
The new strategy is that padding and margins for all applets in a panel is provided from its containment. As is the case, Applets can now request only specific roles through https://invent.kde.org/frameworks/plasma-framework/-/blob/master/src/plasma/plasma.h#L58 in order to be provided relevant padding and margins around them.
The main approach is that panel containment view is providing to applets the exact visual space that applet should have and all input/events that occur inside padding are **sunk - adjusted** into applet visual geometry.
**The Issue**
If Docks (in general and Latte also) decide to follow the new strategy then they are in a desperate need for a solution about their applet popup placement.
Current implementation of popup placement found at: https://invent.kde.org/frameworks/plasma-framework/-/blob/master/src/plasmaquick/dialog.cpp#L961 proposes the following:
1. If the parent window does not provide any mask() then popups are positioned by taking into account their parent window geometry [this is the plasma panels case]
2. If the parent window provides mask() then popups are positioned based on their parent QQuickItem and can be placed inside the window geometry [If I remember correctly I had introduced that workaround when Latte first appeared]
Let's see the problem, the following screenshot demonstrates a dock in which yellow rectangles indicate the visual space given to applets and immerse padding has been set in order to demonstrate the area from which input events are sunk into applets. Analog clock is going to be our performer, this is how it looks before triggering its popup:
![image](/uploads/8858b5e2ee358bec6a269e0dcc12f2e1/image.png)
and this is how it looks after triggering its popup:
![image](/uploads/3cccb4d1c06a869ed146a398d487e0a3/image.png)
In second screenshot, popup window is placed at the exact top edge of analog clock as expected though [2] implementation.
**But** the best result would be the following:
![image](/uploads/a93610d713e2ae953c9d124227f77d79/image.png)
So the popup needs to take into account a dock internal minimum geometry in order to be placed correctly.
**The Solution?**
**A.** GTK_FRAME_EXTENTS margins are retrieved and are used in order to discover the dock internal visual geometry, but I dont know if this is possible under wayland world.
**B.** Plasma::Containment can be enhanced to provide a VisualGeometry (QRect) that will be automatically retrieved from Plasma PopUps and be taken into account for their placement. The VisualGeometry will be optional and if it is not provided then the previous [1,2] solutions are used.
**C.**?Michail VourlakosMichail Vourlakoshttps://invent.kde.org/plasma/kscreenlocker/-/issues/1Why is there a so long dealy when I type a wrong password on unlock screen?2022-08-25T20:48:18Zabc defWhy is there a so long dealy when I type a wrong password on unlock screen?There is a similar question on the internet:
https://superuser.com/questions/976907/disable-or-drastically-shorten-pause-on-incorrect-password
It's too long for users, Can you improve it, please?There is a similar question on the internet:
https://superuser.com/questions/976907/disable-or-drastically-shorten-pause-on-incorrect-password
It's too long for users, Can you improve it, please?https://invent.kde.org/plasma/kwin/-/issues/25Better thumbnails2021-06-23T14:53:48ZDavid EdmundsonBetter thumbnailsThumbnailItem is an exported QQuickItem from Scripting used by third party effects such as Parachute/KWinOverview as well as the tabbox and Plasma Mobile's overview page.
The current implementation is dated. The Item, rather than drawin...ThumbnailItem is an exported QQuickItem from Scripting used by third party effects such as Parachute/KWinOverview as well as the tabbox and Plasma Mobile's overview page.
The current implementation is dated. The Item, rather than drawing directly goes through a complex spidery route to tell kwin to paint a window at the same absolute position.
This breaks z-index, clipping, syncing, shadereffects and is generally messy.
Now we have use of shared contexts and we have SceneWindow export a frame texture it should be feasible to do it properly without any performance cost.
A POC is available at `work/new_thumbnail`
Curent state:
- Tabbox seems just as fast and now actually slide in properly!
- We currently lose lanczos and some other visual effects. That is fixable.
- Parachute works...after some modifications. It's not 100% API compatible as they set a property which exists only on QQuickPaintedItem
For now the current scope is the tabbox and some effects, which we need anyway.
But if we can make something super performant, and perform 9-tiling the shadows and decos inside the thumbnail code we will have all the infrastructure in place to evaluate if it can be used as a base for Kwin's main rendering which indirectly solves per-thread compositing #24, and gives us vulkan support.https://invent.kde.org/plasma/plasma-mobile/-/issues/56Add timeout for startup feedback2021-03-09T19:44:39ZDevin LinAdd timeout for startup feedbackThe startup feedback does not detect if an application failed to launch, and just stays there. Add a timeout (maybe 1 minute) of when it will close.The startup feedback does not detect if an application failed to launch, and just stays there. Add a timeout (maybe 1 minute) of when it will close.https://invent.kde.org/plasma/plasma-mobile/-/issues/50Controlling the torch with DBus vs. sysfs2024-02-23T15:56:50ZBernhard RosenkraenzerControlling the torch with DBus vs. sysfsHi,
I've written a small tool that exposes LED controls over D-Bus (similar in intent, but not implementation, to iio-sensor-proxy) so people don't have to mess with the /sys interface directly.
https://github.com/OpenMandrivaSoftware/le...Hi,
I've written a small tool that exposes LED controls over D-Bus (similar in intent, but not implementation, to iio-sensor-proxy) so people don't have to mess with the /sys interface directly.
https://github.com/OpenMandrivaSoftware/ledcontrol
It's tested on PinePhone through qdbus --system at the moment, works for both the flash and the various small LEDs on the front side. It *should* work on any other device as well.
Would it make sense to use that rather than handling /sys files directly to control the torch in Plasma Mobile?
Will provide a patch if people agree it makes sense to do this.https://invent.kde.org/plasma/plasma-mobile/-/issues/49Fix MPRIS controls in notification shade2021-03-01T18:23:14ZDevin LinFix MPRIS controls in notification shadeCurrently the notification shade shows nothing, though it is implemented...Currently the notification shade shows nothing, though it is implemented...https://invent.kde.org/plasma/kdeplasma-addons/-/issues/6Use QLocale2023-10-31T12:47:08ZYunhe Guoi@guoyunhe.meUse QLocaleWhen build the repo, here are a lot of deprecated messages, like:
```
‘Qt::DefaultLocaleShortDate’ is deprecated: Use QLocale
‘Qt::DefaultLocaleLongDate’ is deprecated: Use QLocale
‘Qt::SystemLocaleShortDate’ is deprecated: Use QLocale
...When build the repo, here are a lot of deprecated messages, like:
```
‘Qt::DefaultLocaleShortDate’ is deprecated: Use QLocale
‘Qt::DefaultLocaleLongDate’ is deprecated: Use QLocale
‘Qt::SystemLocaleShortDate’ is deprecated: Use QLocale
‘Qt::SystemLocaleLongDate’ is deprecated: Use QLocale
```
These code need migration before Qt 6 breaks it.Yunhe Guoi@guoyunhe.meYunhe Guoi@guoyunhe.mehttps://invent.kde.org/plasma/kwin/-/issues/21Eliminate the intermediate texture when screencasting windows with sub-surfaces2023-08-29T12:58:27ZVlad ZahorodniiEliminate the intermediate texture when screencasting windows with sub-surfacesCurrently, when a window with sub-surfaces is screencasted, kwin will create an intermediate texture and render the window into it. It would be much better if the window were rendered directly onto the dma-buf texture.Currently, when a window with sub-surfaces is screencasted, kwin will create an intermediate texture and render the window into it. It would be much better if the window were rendered directly onto the dma-buf texture.https://invent.kde.org/plasma/plasma-mobile/-/issues/41[homescreens/folio] Add expandable folders to app drawer and home screen2023-11-14T20:26:03ZIvan Rancic[homescreens/folio] Add expandable folders to app drawer and home screenIt would be a nice extra to make organizing one's apps easier.It would be a nice extra to make organizing one's apps easier.6https://invent.kde.org/plasma/plasma-mobile/-/issues/40Improve notifications on the lockscreen2022-02-12T05:36:19ZDevin LinImprove notifications on the lockscreenLockscreen notifications are quite basic right now.
Next steps for work:
- [ ] Notification images
- [x] Fix notification dismissal
- [ ] Show notifications that are already in the notification history (currently only displays new notif...Lockscreen notifications are quite basic right now.
Next steps for work:
- [ ] Notification images
- [x] Fix notification dismissal
- [ ] Show notifications that are already in the notification history (currently only displays new notifications)
- [x] Notification actions that request an unlock?https://invent.kde.org/plasma/plasma-mobile/-/issues/38Multiple pages for homescreen2021-05-06T12:43:20ZDevin LinMultiple pages for homescreenCurrently there is limited space on the homescreen for plasmoids and apps. The easiest way to add more space is to add the ability to have multiple pages for the homescreen.Currently there is limited space on the homescreen for plasmoids and apps. The easiest way to add more space is to add the ability to have multiple pages for the homescreen.https://invent.kde.org/plasma/plasma-desktop/-/issues/10By having changed Plasma themes, it crashes all my Plasma panel layouts2020-09-25T06:41:57ZHD Scaniahd-scania@users.sf.netBy having changed Plasma themes, it crashes all my Plasma panel layouts```
OS: Artix-runit with kernel 5.9rc6
Plasma: 5.19.5-1
Frameworks: 5.74.0-1
Qt: 5.15.1-1
```
By downloading a few Deepin-like Plasma themes, fine
By closing System Settings, and moving everything from `~/.local/share/plasma` to `/usr/s...```
OS: Artix-runit with kernel 5.9rc6
Plasma: 5.19.5-1
Frameworks: 5.74.0-1
Qt: 5.15.1-1
```
By downloading a few Deepin-like Plasma themes, fine
By closing System Settings, and moving everything from `~/.local/share/plasma` to `/usr/share/plasma`, **CRASHES**
By removing everything from `~/.config/*plasm*`, it still says my "_layouts_" not saved, so **not** showing any backgrounds or panels to change
From now on, only **SDDM and System Settings** are my Qt stuff on Artix **not** affected by that crashhttps://invent.kde.org/plasma/plasma-workspace/-/issues/6Kickoff needs to expose all of the krunner runners that are enabled in the KCM2023-11-28T14:35:06ZAlexander LohnauKickoff needs to expose all of the krunner runners that are enabled in the KCMThere are IMO some things we should discuss:
- Some runners produce a ton if results, for example when I just type "h" the baloo runner shows a ton of entries. Maybe we want to filter this a bit more? It is also notable in KRunner when y...There are IMO some things we should discuss:
- Some runners produce a ton if results, for example when I just type "h" the baloo runner shows a ton of entries. Maybe we want to filter this a bit more? It is also notable in KRunner when you have a lot of other plugins enabled.
- Also the "Software Center" produes a lot of unwanted results, for example:
![image](/uploads/bf1e8ba92f65d6e345e047ef63e05202/image.png)
That could be an annoyance and it changes IMO the behavior of the menu significantly.
Maybe disabling this one by default, unless the user explicitly wants to enable them.
- The informational match is not properly handled, in KRunner and the search plasmoid this would convert the data(QVariant) to a sting an put the value in the UI. But kickoff does nothing with it, to try this out just type `1+1` in kickoff, press enter and all your hard work is gone ;)
- Multiline support, for example
![image](/uploads/84336325bb32d033f53951ba310f9626/image.png)
And in the dictionary runner we should also rethink the usage of text and subtext. Especially considering that the subtext is intended for secondary information.
- Also some runners "feel" like you should be able to add them as favorites, because they behave like applications. Take the virtualbox runner as an example:
![image](/uploads/a88f9c53f566fc98e944c804fa4fcd9b/image.png)
IMO a valid usecase to add sth. like this or lets say a kdevelop workspace to your favorites.
- We have in the GUI the option to "expand search to bookmarks, files and emails" this contradicts the goal of using the entries from krunnerrc here.
- Also when using the krunnerrc config file we would need to communicate to the user that the plugin can be disabled in the KCM. But because of the other KRunner options that could be very confusing.
There are just some thoughts that came to my mind ;-)Alexander LohnauAlexander Lohnauhttps://invent.kde.org/plasma/latte-dock/-/issues/19AutoHide sidebar2020-07-28T18:51:30ZMartijn VogelaarAutoHide sidebarAfter compiling the latest version of latte-dock and fiddling around with the sidebar and sidebar button I was bothered by the fact that I had to click the sidebar button twice(opening and closing) when using the sidebar. I figured it wo...After compiling the latest version of latte-dock and fiddling around with the sidebar and sidebar button I was bothered by the fact that I had to click the sidebar button twice(opening and closing) when using the sidebar. I figured it would be easier if it would hide automatically like the AutoHide type.
My idea was to introduce a new type: AutoHide Sidebar which automatically hides when:
- Certain amount of time has passed and mouse is no longer in the sidebar
- Click happens outside the sidebar
- Click on the original sidebar button
Automatically hiding the sidebar saves time because you do not need to click the sidebar button again which obviously increases efficiency.
Since I've always wanted to try some QML I tried something myself and came up with the following after a night of work:
[simplescreenrecorder-2020-07-26_03.11.32.mkv](/uploads/e7b5e50666f5f41daa819927e5eb0543/simplescreenrecorder-2020-07-26_03.11.32.mkv)
Still a bit buggy but it works. I was wondering what your thoughts on this idea are.https://invent.kde.org/plasma/kwin/-/issues/8Gracefully handle Xwayland crashes2023-08-29T12:58:27ZVlad ZahorodniiGracefully handle Xwayland crashesCurrently, if Xwayland crashes (not due to bugs of course), it will bring the entire session down. Obviously, that's an undesired behavior. We should at least gracefully handle Xwayland crashes and cleanup X11 related stuff. Ultimately, ...Currently, if Xwayland crashes (not due to bugs of course), it will bring the entire session down. Obviously, that's an undesired behavior. We should at least gracefully handle Xwayland crashes and cleanup X11 related stuff. Ultimately, we should restart Xwayland.Vlad ZahorodniiVlad Zahorodnii