Plasma issueshttps://invent.kde.org/groups/plasma/-/issues2021-03-13T22:44:12Zhttps://invent.kde.org/plasma/latte-dock/-/issues/54Plasma TaskManager: Very slow animations when moving window between screens2021-03-13T22:44:12ZChris HarveyPlasma TaskManager: Very slow animations when moving window between screensSince Plasma 5.21 (KDE Neon), I have been having an issue with the animations of Latte Dock when moving a window between screens.
I have two screens, with two latte dock panels on each screen.
I'm also using the Plasma task manager wid...Since Plasma 5.21 (KDE Neon), I have been having an issue with the animations of Latte Dock when moving a window between screens.
I have two screens, with two latte dock panels on each screen.
I'm also using the Plasma task manager widget instead of the Latte Tasks widget.
This issue occurs with the Latte Dock package from the neon repos, and also on the latest master version (commit: 7b817893f0f2f17e939da182d7c91bc59ad87108)
This issue only seems to occur when using latte dock, the standard plasma panels work fine.
See attached videos:
Latte: [latte-issue-2021-03-09_17.21.51.mkv](/uploads/20d5d535da20f267c15d4b96a98e073b/latte-issue-2021-03-09_17.21.51.mkv)
Plasma Panels: [latte-issue-panel-2021-03-09_17.12.08.mkv](/uploads/3ad9a0fdef8ff43bca45ec60b9e4d45a/latte-issue-panel-2021-03-09_17.12.08.mkv)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/latte-dock/-/issues/55Plasma TaskManager: Window titles randomly disappear2021-03-10T10:03:43ZChris HarveyPlasma TaskManager: Window titles randomly disappearI'm using the Plasma task manager with Latte Dock, and since Plasma 5.21, the window titles seem to randomly disappear.
I'm using the latest master version (commit: 7b817893f0f2f17e939da182d7c91bc59ad87108)
This issue only seems to occ...I'm using the Plasma task manager with Latte Dock, and since Plasma 5.21, the window titles seem to randomly disappear.
I'm using the latest master version (commit: 7b817893f0f2f17e939da182d7c91bc59ad87108)
This issue only seems to occur when using Latte Dock, and doesn't occur when using the standard Plasma Panels.
![image](/uploads/705a12ebb6d80703e1d442fd1ab7cc0f/image.png)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/51Fix lockscreen keypad keys still in "held" ui state when you slide finger off...2020-11-20T11:31:23ZDevin LinFix lockscreen keypad keys still in "held" ui state when you slide finger off of itFix it so that the key is immediately unpressed when the finger is not on it.Fix it so that the key is immediately unpressed when the finger is not on it.Devin LinDevin Linhttps://invent.kde.org/plasma/latte-dock/-/issues/57EMFILE file error when running latte-dock and Obsidian2021-04-26T09:12:22ZAlasdair StewartEMFILE file error when running latte-dock and Obsidian**Steps to reproduce**
Have both [Obsidian](obsidian.md) and latte-dock installed
Launch latte-dock then Obsidian
**Expected result**
Obsidian opens.
**Actual result**
“EMFILE: too many open files” message in Obsidian and applicatio...**Steps to reproduce**
Have both [Obsidian](obsidian.md) and latte-dock installed
Launch latte-dock then Obsidian
**Expected result**
Obsidian opens.
**Actual result**
“EMFILE: too many open files” message in Obsidian and application stuck loading.
**Environment**
Operating system: Ubuntu 20.04 with latte-dock from Ubuntu repos
Obsidian version: 0.11.5
I have opened an issue with Obsidian as well. However, I suspect this issue may be caused by latte-dock. No other software causes this problem and if I open Obsidian first then latte-dock there is no error - it's only opening Obsidian when latte-dock is already running that the problem occurs.https://invent.kde.org/plasma/wacomtablet/-/issues/2New release?2023-11-01T17:07:07ZTomasz KloczkoNew release?https://invent.kde.org/system/wacomtablet/-/compare/v3.2.0...master?from_project_id=2659 shows +70 commits added since last release.
Do you have any plans to make new release soon? :thinking:https://invent.kde.org/system/wacomtablet/-/compare/v3.2.0...master?from_project_id=2659 shows +70 commits added since last release.
Do you have any plans to make new release soon? :thinking:https://invent.kde.org/plasma/plasma-mobile/-/issues/52Breeze dark on mobile pin entry screen has very dim icons for cancel and go, ...2020-11-21T20:33:52ZRobert GriffithsBreeze dark on mobile pin entry screen has very dim icons for cancel and go, breeze light is fineBreeze dark on mobile pin entry screen has very dim icons for cancel and go, breeze light is fineBreeze dark on mobile pin entry screen has very dim icons for cancel and go, breeze light is finehttps://invent.kde.org/plasma/latte-dock/-/issues/58Another slider style2021-04-03T05:38:37ZAlexey VarfolomeevAnother slider styleHi Latte devs, maybe better use another style for slider...
If used transparent buttons slider not visible.
Example:
As i know, buttons draw on plasma layr on layer:
normal - it's normal
hover - it's normal+hover
focus - it' presse...Hi Latte devs, maybe better use another style for slider...
If used transparent buttons slider not visible.
Example:
As i know, buttons draw on plasma layr on layer:
normal - it's normal
hover - it's normal+hover
focus - it' pressed+focus
pressed - it's pressed
Hover & Focus can't use non-transparent style and if use non-transparent style this not visible checkbox.
For example,
normal button 0% opacity, color #343434
hover button 30% opacity - this already not visible on LatteDock. I think hover layer is superimposed from below.
![image](/uploads/9bef0214044e86d4a35df98782ed18b8/image.png)
Example 2,
normal button 30% opacity
hover button 30% - all fine, but we have problem with slider on Latte
![image](/uploads/8bef3bbbd8e135d5a5d8a975a2b38c1a/image.png)
Solution, i can draw slider (with full support KDE Color Scheme) and this will be buil-in on latte:
```
<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="38" height="40" version="1.1">
<defs>
<linearGradient id="linearGradient856">
<stop style="stop-color:#000000" offset="0"/>
<stop style="stop-color:#000000;stop-opacity:0" offset="1"/>
</linearGradient>
<radialGradient id="radialGradient858" cx="45.508" cy="142.483" r="2.646" fx="45.508" fy="142.483" gradientTransform="matrix(3.7792896,2.1387021e-6,-4.1657266e-6,3.7792799,-143.98732,-528.48325)" gradientUnits="userSpaceOnUse" xlink:href="#linearGradient856"/>
<radialGradient id="radialGradient862" cx="45.508" cy="142.483" r="2.646" fx="45.508" fy="142.483" gradientTransform="matrix(3.7800064,4.672207e-4,-4.6707341e-4,3.7788149,-161.95588,-508.43939)" gradientUnits="userSpaceOnUse" xlink:href="#linearGradient856"/>
<style id="current-color-scheme" type="text/css">
.ColorScheme-Text { color:#31363b; stop-color:#31363b; } .ColorScheme-Background { color:#eff0f1; stop-color:#eff0f1; } .ColorScheme-Highlight { color:#3daee9; stop-color:#3daee9; } .ColorScheme-ViewText { color:#31363b; stop-color:#31363b; } .ColorScheme-ViewBackground { color:#fcfcfc; stop-color:#fcfcfc; } .ColorScheme-ViewHover { color:#93cee9; stop-color:#93cee9; } .ColorScheme-ViewFocus{ color:#3daee9; stop-color:#3daee9; } .ColorScheme-ButtonText { color:#31363b; stop-color:#31363b; } .ColorScheme-ButtonBackground { color:#eff0f1; stop-color:#eff0f1; } .ColorScheme-ButtonHover { color:#93cee9; stop-color:#93cee9; } .ColorScheme-ButtonFocus{ color:#3daee9; stop-color:#3daee9; }
</style>
</defs>
<g id="latte-slider-enabled">
<rect style="opacity:0.001" width="38" height="20" x="0" y="0"/>
<path fill="currentColor" class="ColorScheme-Highlight" d="m 9.99028,1.00001 c -4.96675,0.005 -8.99023,4.03325 -8.99023,9 0,4.97056 4.02944,9 9,9 h 18 c 0,0 0,-17.99987 0,-18 h -0.01 -17.99 z"/>
<path style="fill:url(#radialGradient858)" d="M 27.980469 0 A 10 10 0 0 0 18 10 A 10 10 0 0 0 28 20 A 10 10 0 0 0 38 10 A 10 10 0 0 0 28 0 A 10 10 0 0 0 27.980469 0 z M 27.990234 1 A 9 9 0 0 1 28 1 A 9 9 0 0 1 37 10 A 9 9 0 0 1 28 19 A 9 9 0 0 1 19 10 A 9 9 0 0 1 27.990234 1 z"/>
<circle fill="currentColor" class="ColorScheme-ButtonBackground" cx="28" cy="10" r="9"/>
</g>
<g id="latte-slider-disabled">
<rect style="opacity:0.001" width="38" height="20" x="0" y="20"/>
<path style="opacity:0.5;fill:currentColor" class="ColorScheme-Text" d="m 9.9999974,20.999944 c 0,0 0,17.999994 0.00983,17.999994 h 17.99343 c 4.968748,0 8.996714,-4.029428 8.996714,-8.999997 0,-4.970568 -4.027966,-8.999997 -8.996714,-8.999997 h -0.0098 -17.983662 -0.00983 z"/>
<path style="fill:url(#radialGradient862)" d="M 9.9804688 20 A 10 10 0 0 0 0 30 A 10 10 0 0 0 10 40 A 10 10 0 0 0 20 30 A 10 10 0 0 0 10 20 A 10 10 0 0 0 9.9804688 20 z M 9.9902344 21 A 9 9 0 0 1 10 21 A 9 9 0 0 1 19 30 A 9 9 0 0 1 10 39 A 9 9 0 0 1 1 30 A 9 9 0 0 1 9.9902344 21 z"/>
<circle fill="currentColor" class="ColorScheme-ButtonBackground" cx="10" cy="30" r="9"/>
</g>
</svg>
```
![image](/uploads/877987b108169072086f07eefc162bab/image.png)https://invent.kde.org/plasma/plasma-mobile/-/issues/53[homescreen] App dock / drawer doesn't save user changes after system update2022-01-01T03:48:54ZRobert Griffiths[homescreen] App dock / drawer doesn't save user changes after system updateIf I add eg discover to the app dock (I mean the bottom row of icons always on display) next to angelfish it will be removed the next time I update. I noticed the app drawer reverts changes aswell, but I'm not so sure when or how often.If I add eg discover to the app dock (I mean the bottom row of icons always on display) next to angelfish it will be removed the next time I update. I noticed the app drawer reverts changes aswell, but I'm not so sure when or how often.https://invent.kde.org/plasma/latte-dock/-/issues/59Latte-dock crashing at boot2021-04-22T07:08:07Zchandan jrLatte-dock crashing at bootLatte-dock is crashing at boot.
It was built with the AUR package with commit b8229ac1
Here are coredumps I took:
Stack trace of thread 693:
#0 0x00007f6703f4fef5 raise (libc....Latte-dock is crashing at boot.
It was built with the AUR package with commit b8229ac1
Here are coredumps I took:
Stack trace of thread 693:
#0 0x00007f6703f4fef5 raise (libc.so.6 + 0x3cef5)
#1 0x00007f6705c79189 _ZN6KCrash19defaultCrashHandlerEi (libKF5Crash.so.5 + 0x4189)
#2 0x00007f6703f4ff80 __restore_rt (libc.so.6 + 0x3cf80)
#3 0x0000556baf7b57e0 n/a (latte-dock + 0x747e0)
#4 0x0000556baf7dfcb5 n/a (latte-dock + 0x9ecb5)
#5 0x0000556baf7ca7b3 n/a (latte-dock + 0x897b3)
#6 0x0000556baf80aa53 n/a (latte-dock + 0xc9a53)
#7 0x0000556baf80c7e4 n/a (latte-dock + 0xcb7e4)
#8 0x0000556baf8267ac n/a (latte-dock + 0xe57ac)
#9 0x0000556baf81bfd4 n/a (latte-dock + 0xdafd4)
#10 0x0000556baf7caf15 n/a (latte-dock + 0x89f15)
#11 0x0000556baf89e8e1 n/a (latte-dock + 0x15d8e1)
#12 0x00007f670497a066 n/a (libQt5DBus.so.5 + 0x21066)
#13 0x00007f670497d65b n/a (libQt5DBus.so.5 + 0x2465b)
#14 0x00007f670497da8b n/a (libQt5DBus.so.5 + 0x24a8b)
#15 0x00007f6704980478 n/a (libQt5DBus.so.5 + 0x27478)
#16 0x00007f67046e6532 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2e2532)
#17 0x00007f67053ff752 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x15a752)
#18 0x00007f67046b9a2a _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x2b5a2a)
#19 0x00007f67046bc523 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5 + 0x2b8523)
#20 0x00007f6704713054 n/a (libQt5Core.so.5 + 0x30f054)
#20 0x00007f6704713054 n/a (libQt5Core.so.5 + 0x30f054)
#21 0x00007f6702b63f9c g_main_context_dispatch (libglib-2.0.so.0 + 0x53f9c)
#22 0x00007f6702bb7a49 n/a (libglib-2.0.so.0 + 0xa7a49)
#23 0x00007f6702b616f1 g_main_context_iteration (libglib-2.0.so.0 + 0x516f1)
#24 0x00007f6704712691 _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e691)
#25 0x00007f67046b83ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43ac)
#26 0x00007f67046c0844 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2bc844)
#27 0x0000556baf77d73b n/a (latte-dock + 0x3c73b)
#28 0x00007f6703f3ab25 __libc_start_main (libc.so.6 + 0x27b25)
#29 0x0000556baf77e03e _start (latte-dock + 0x3d03e)
Stack trace of thread 774:
#0 0x00007f670400308c __read (libc.so.6 + 0xf008c)
#1 0x00007f6702b643cd g_main_context_check (libglib-2.0.so.0 + 0x543cd)
#2 0x00007f6702bb797b n/a (libglib-2.0.so.0 + 0xa797b)
#3 0x00007f6702b616f1 g_main_context_iteration (libglib-2.0.so.0 + 0x516f1)
#4 0x00007f67047126ac _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x30e6ac)
#5 0x00007f67046b83ac _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2b43ac)
#6 0x00007f67044d0d12 _ZN7QThread4execEv (libQt5Core.so.5 + 0xccd12)
#7 0x00007f6704970098 n/a (libQt5DBus.so.5 + 0x17098)
#8 0x00007f67044d1eff n/a (libQt5Core.so.5 + 0xcdeff)
#9 0x00007f670383c299 start_thread (libpthread.so.0 + 0x9299)
#10 0x00007f6704012053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 759:
#0 0x00007f67038489ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
#1 0x00007f6703842260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
#2 0x00007f66fcd04a1c n/a (iris_dri.so + 0x152a1c)
#3 0x00007f66fccfe668 n/a (iris_dri.so + 0x14c668)
#4 0x00007f670383c299 start_thread (libpthread.so.0 + 0x9299)
#5 0x00007f6704012053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 758:
#0 0x00007f67038489ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
#1 0x00007f6703842260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
#2 0x00007f66fcd04a1c n/a (iris_dri.so + 0x152a1c)
#3 0x00007f66fccfe668 n/a (iris_dri.so + 0x14c668)
#4 0x00007f670383c299 start_thread (libpthread.so.0 + 0x9299)
#5 0x00007f6704012053 __clone (libc.so.6 + 0xff053)
Stack trace of thread 757:
#0 0x00007f67038489ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba)
#1 0x00007f6703842260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260)
#2 0x00007f66fcd04a1c n/a (iris_dri.so + 0x152a1c)
#3 0x00007f66fccfe668 n/a (iris_dri.so + 0x14c668)
strange issue is that , I used the same package on garuda linux and it was working, but with arch its crashing.https://invent.kde.org/plasma/plasma-mobile/-/issues/54No notifications in shade2021-03-01T18:18:55ZIvan RancicNo notifications in shadeNotifications are available in pop-up form but are not shown in notification shadeNotifications are available in pop-up form but are not shown in notification shadehttps://invent.kde.org/plasma/latte-dock/-/issues/60window-pin button/icon very small2021-04-06T04:35:20ZAlexey Varfolomeevwindow-pin button/icon very smallFresh plasma version present window-pin icon with 3 sizes 32/16/8.
![image](/uploads/0e6f77c77b261bc21fe6145f5bf4f3b1/image.png)
https://invent.kde.org/frameworks/plasma-framework/-/commit/f363a06ae697c86d0d7448cbb971be02ebfbb402Fresh plasma version present window-pin icon with 3 sizes 32/16/8.
![image](/uploads/0e6f77c77b261bc21fe6145f5bf4f3b1/image.png)
https://invent.kde.org/frameworks/plasma-framework/-/commit/f363a06ae697c86d0d7448cbb971be02ebfbb402https://invent.kde.org/plasma/plasma-mobile/-/issues/55Sound indicator goes full-screen2020-11-24T17:14:51ZIvan RancicSound indicator goes full-screenAfter every restart and then second attempt to adjust sound, sound indicator goes almost full-screenAfter every restart and then second attempt to adjust sound, sound indicator goes almost full-screenhttps://invent.kde.org/plasma/latte-dock/-/issues/61Memory Usage Issues (Master branch)2021-04-03T17:42:35ZZadock MalobaMemory Usage Issues (Master branch)I have two docks in my Desktop and the memory usage needs to be reviewed. [Screenshot_20210403_160630](/uploads/fad0b8caf48bf8fce5196d220e6da6d0/Screenshot_20210403_160630.png)I have two docks in my Desktop and the memory usage needs to be reviewed. [Screenshot_20210403_160630](/uploads/fad0b8caf48bf8fce5196d220e6da6d0/Screenshot_20210403_160630.png)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/latte-dock/-/issues/62Latte Dock offset incorrectly affects where windows can be placed2021-04-24T17:06:42ZZach WhiteLatte Dock offset incorrectly affects where windows can be placedI've setup my Latte Dock to be on the right hand side of my screen, aligned to the top. I've also placed a panel at the top of the screen. Getting this configuration to work is more challenging than it should be.
The non-advanced settin...I've setup my Latte Dock to be on the right hand side of my screen, aligned to the top. I've also placed a panel at the top of the screen. Getting this configuration to work is more challenging than it should be.
The non-advanced settings result in the dock and the panel overlapping in a way they shouldn't:
![Screenshot_20210409_072456](/uploads/040b6a5950c5f300f67f478c4f7f33dd/Screenshot_20210409_072456.png)
If I enable advanced settings I can set an "offset", but only in increments of 2%. Setting that offset to 2% results in the dock being squished against the panel with no margin space. I would prefer the same amount of space between the top icon and the panel as between the dock icons themselves.
![Screenshot_20210409_073014](/uploads/a5164fec03ab0209d6c4f43b0864b505/Screenshot_20210409_073014.png)
If I set the offset to 4% this creates a band of "unusable space" where plasma won't let me place any windows:
![Screenshot_20210409_071706](/uploads/089d5b777dff2de9c89f0b9c2c7da379/Screenshot_20210409_071706.png)
Snapping the window (With Meta+Right) into place will let the window use this unusable space, but the window will be "trapped" inside and unable to move down:
![Screenshot_20210409_071625](/uploads/8ce77bb394a227e0f0a12a69ea8c867b/Screenshot_20210409_071625.png)
**Recommendations**:
I don't think all of these recommendations are necessary, but if one or several of these were implemented I would not be experiencing what I am now.
* Make Latte Dock aware of panels so that 100% width/height means the space available, not the entire screen length.
* Remove the artificial border on the "short side" of latte dock's invisible window
* Allow arbitrary offset and length by making the numbers next to the sliders editable
* Allow increments of 1% for offset and length
* Allow for pixel-specified increments instead of percentagehttps://invent.kde.org/plasma/plasma-mobile/-/issues/57Make Maliit keyboard match dark theme of breeze2021-03-01T18:19:52ZBrian AbertsMake Maliit keyboard match dark theme of breezeThe maliit keyboard currently does not match breeze dark, which makes it look quite odd. Like the pin menu of merge [116](https://invent.kde.org/plasma/plasma-phone-components/-/merge_requests/116), it would be good to have it automatica...The maliit keyboard currently does not match breeze dark, which makes it look quite odd. Like the pin menu of merge [116](https://invent.kde.org/plasma/plasma-phone-components/-/merge_requests/116), it would be good to have it automatically match theme colors.https://invent.kde.org/plasma/latte-dock/-/issues/63Install dependency on libQt5Core.so.5(Qt_5.15)(64bit)2021-04-22T07:04:13ZNiko MaziachviliInstall dependency on libQt5Core.so.5(Qt_5.15)(64bit)RPM built from latest git commit for openSUSE Tumbleweed fails to install with:
`Problem: nothing provides libQt5Core.so.5(Qt_5.15)(64bit) needed by latte-dock-git.20210412.b03be804-0.x86_64`
RPM builds without errors, which made me t...RPM built from latest git commit for openSUSE Tumbleweed fails to install with:
`Problem: nothing provides libQt5Core.so.5(Qt_5.15)(64bit) needed by latte-dock-git.20210412.b03be804-0.x86_64`
RPM builds without errors, which made me think that all dependencies were met.
Let me know if any extra info is needed.
_(repo: https://download.opensuse.org/repositories/home:/cyclingGeorgian:/plasma-looks/openSUSE_Tumbleweed/)_https://invent.kde.org/plasma/plasma-mobile/-/issues/58Deal with lockscreen errors2020-12-05T22:10:24ZDevin LinDeal with lockscreen errorshttps://invent.kde.org/-/snippets/1395https://invent.kde.org/-/snippets/1395Devin LinDevin Lin