Plasma issueshttps://invent.kde.org/groups/plasma/-/issues2024-03-02T02:52:19Zhttps://invent.kde.org/plasma/kwin/-/issues/211Revert this commit in 6.1 branch when DnD custom cursor is not fixed in Wayla...2024-03-02T02:52:19ZJin Lium.liu.jin@gmail.comRevert this commit in 6.1 branch when DnD custom cursor is not fixed in Wayland by thenhttps://invent.kde.org/plasma/kwin/-/commit/53863609288e7eee6a44feea37af3777e54f0bab
It's reverted in 6.0 but not master.https://invent.kde.org/plasma/kwin/-/commit/53863609288e7eee6a44feea37af3777e54f0bab
It's reverted in 6.0 but not master.6.1https://invent.kde.org/plasma/plasma-welcome/-/issues/28Private module for built-in content2024-03-10T23:41:48ZOliver BeardPrivate module for built-in contentWe should use a separate private module for built-in content, so that distro pages can't access them or confuse their types.
Everything in common would be in `org.kde.plasma.welcome` and everything else would be in `org.kde.plasma.welco...We should use a separate private module for built-in content, so that distro pages can't access them or confuse their types.
Everything in common would be in `org.kde.plasma.welcome` and everything else would be in `org.kde.plasma.welcome.private`. The module would be created via CMake.6.1Oliver BeardOliver Beardhttps://invent.kde.org/plasma/kwin/-/issues/209Tracking render time with multi-gpu transfers2024-03-08T15:12:13ZXaver HuglTracking render time with multi-gpu transfersI found good solutions for this while typing this up; still creating the issue so that I don't forget to actually implement it.
With multi gpu transfers, we currently track the render time by doing two render time queries:
- one for com...I found good solutions for this while typing this up; still creating the issue so that I don't forget to actually implement it.
With multi gpu transfers, we currently track the render time by doing two render time queries:
- one for compositing on the primary GPU: `primary gpu end time - compositing start time`
- one for copying the result to the secondary gpu: `secondary gpu end time - copy start time`
However, `copy start time` is almost always in between `compositing start time` and `primary gpu end time`, and more towards the start than towards the end. This can result in big overestimation of the actual time until rendering is complete, which negatively affects latency.
Directly just doing the desired `secondary gpu end time - compositing start time` calculation is also not trivially possible, as the clocks are not compatible. As potential solutions, we could
- do a more complex render time tracking thing where we track the fence of the last render job on the CPU side. This would be renderer agnostic (working for Vulkan too), but doing it accurately would require yet another thread
- record `GL_TIME_ELAPSED` for the second job, instead of timestamps; adding that to `primary gpu end time` should effectively always yield correct results
- convert all the timestamps into a common time base, `CLOCK_MONOTONIC`. This shouldn't be too complicated afaict6.1https://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/318actiondrawer: Unable to scroll on notification list2024-03-08T21:31:02ZDevin Linactiondrawer: Unable to scroll on notification listScrolling up on the notification list closes the action drawerScrolling up on the notification list closes the action drawer6https://invent.kde.org/plasma/kwin/-/issues/208Fractional scaling meetup notes2024-02-28T15:15:11ZVlad ZahorodniiFractional scaling meetup noteshttps://invent.kde.org/plasma/plasma-mobile/-/issues/316homescreens/folio: Move HomeScreenState away from singleton2024-03-21T18:21:26ZDevin Linhomescreens/folio: Move HomeScreenState away from singletonCurrently [HomeScreenState](https://invent.kde.org/plasma/plasma-mobile/-/blob/master/containments/homescreens/folio/homescreenstate.h?ref_type=heads) is a singleton, which is problematic because it is shared across all screens (causing ...Currently [HomeScreenState](https://invent.kde.org/plasma/plasma-mobile/-/blob/master/containments/homescreens/folio/homescreenstate.h?ref_type=heads) is a singleton, which is problematic because it is shared across all screens (causing many issues for external screens). We can keep the models as singletons, but we should have a separate HomeScreenState per containment instance.6.1https://invent.kde.org/plasma/plasma-pass/-/issues/5Add appstream file2024-02-25T13:23:03ZDaniel Vrátildvratil@kde.orgAdd appstream fileWithout appstream info, it won't be findable in Discover.
Make sure to release afterwards.Without appstream info, it won't be findable in Discover.
Make sure to release afterwards.Daniel Vrátildvratil@kde.orgDaniel Vrátildvratil@kde.orghttps://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/kwin/-/issues/207Drop Workspace::deletedRemoved2024-02-23T09:48:56ZVlad ZahorodniiDrop Workspace::deletedRemoved`Window::destroyed` should provide the same semantics.`Window::destroyed` should provide the same semantics.https://invent.kde.org/plasma/plasma-mobile/-/issues/314taskswitcher: Gestures in gesture only mode need too much "distance"2024-03-01T11:50:25ZLuis Büchitaskswitcher: Gestures in gesture only mode need too much "distance"on portrait I need to swipe up fairly far to get into the task switcher (otherwise I just go to homescreen), on landscape the gesture is almost unusable, I need to swipe almost the entire landscape height (width of the display) to get in...on portrait I need to swipe up fairly far to get into the task switcher (otherwise I just go to homescreen), on landscape the gesture is almost unusable, I need to swipe almost the entire landscape height (width of the display) to get into the task switcher.
Tested on a original pinephone on postmarketOS with plasma mobile nightly6.1https://invent.kde.org/plasma/plasma-mobile/-/issues/313taskswitcher: Gesture only mode only works after using action drawer once2024-02-23T15:31:52ZLuis Büchitaskswitcher: Gesture only mode only works after using action drawer onceAs mentioned in https://invent.kde.org/plasma/plasma-mobile/-/merge_requests/451, the gesture only mode only works after each reboot after using the action drawer at least once. Dropping it down even in the "small" view is enough for ges...As mentioned in https://invent.kde.org/plasma/plasma-mobile/-/merge_requests/451, the gesture only mode only works after each reboot after using the action drawer at least once. Dropping it down even in the "small" view is enough for gestures to work afterwards.6.1https://invent.kde.org/plasma/plasma-workspace/-/issues/117Follow-up from "[kcms/users] Fix sizing in fingerprint dialog"2024-02-20T23:11:26ZNate GrahamFollow-up from "[kcms/users] Fix sizing in fingerprint dialog"The following discussion from !3928 should be addressed:
- [ ] @ngraham started a [discussion](https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3928#note_875971): (+4 comments)
> Since internally this component has ...The following discussion from !3928 should be addressed:
- [ ] @ngraham started a [discussion](https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3928#note_875971): (+4 comments)
> Since internally this component has an icon that could benefit from being displayed at a standard size, I'm not convinced about these hardcoded implicit sizes set here. I'd prefer for the component to internally set an implicit size that's based on the size of the icon, plus the size of the progress circle, plus optionally any needed exterior padding.6Nicolas FellaNicolas Fellahttps://invent.kde.org/plasma/kwin/-/issues/205Drop support of modifier-only shortcuts and migrate config2024-03-28T16:14:47ZYifan ZhuDrop support of modifier-only shortcuts and migrate configSupport of modifier-only shortcuts in being implemented in kglobalacceld in
- https://invent.kde.org/plasma/kglobalacceld/-/merge_requests/44
- https://invent.kde.org/plasma/kwin/-/merge_requests/5251
- https://invent.kde.org/frameworks...Support of modifier-only shortcuts in being implemented in kglobalacceld in
- https://invent.kde.org/plasma/kglobalacceld/-/merge_requests/44
- https://invent.kde.org/plasma/kwin/-/merge_requests/5251
- https://invent.kde.org/frameworks/kguiaddons/-/merge_requests/115
- https://invent.kde.org/frameworks/kwindowsystem/-/merge_requests/148
So we should consider
- [ ] dropping that functionality from kwin and moving it where it better belongs (https://invent.kde.org/plasma/kwin/-/merge_requests/5268)
- [ ] and migrating all existing modifier-only shortcuts
~~Note: https://invent.kde.org/plasma/kglobalacceld/-/merge_requests/44 doesn't work on X11 yet, I will need to look into that.~~ Everything should be working!
BUG: 371560
Related by technically independent: turning on multi-key shortcuts by default in
- https://invent.kde.org/frameworks/kglobalaccel/-/merge_requests/105
- https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/20606.1Yifan ZhuYifan Zhuhttps://invent.kde.org/plasma/kwin/-/issues/204[Log] systemd-coredump kwin_wayland2024-02-20T01:42:47ZRustmilian[Log] systemd-coredump kwin_wayland23:51:57.852 UTC systemd-coredump@0-1187-0.service Process 751 (kwin_wayland) of user 1000 dumped core.
```
Stack trace of thread 751:
#0 0x0000789da5aab32c n/a (libc.so.6 + 0x8d32c)
#1 0x0000789da5a5a6c8 raise (libc.so.6 + 0x3c6c8)
#2...23:51:57.852 UTC systemd-coredump@0-1187-0.service Process 751 (kwin_wayland) of user 1000 dumped core.
```
Stack trace of thread 751:
#0 0x0000789da5aab32c n/a (libc.so.6 + 0x8d32c)
#1 0x0000789da5a5a6c8 raise (libc.so.6 + 0x3c6c8)
#2 0x0000789da5a424b8 abort (libc.so.6 + 0x244b8)
#3 0x0000789da7b8afee n/a (libepoxy.so.0 + 0xbbfee)
#4 0x0000789da7b8e9d2 n/a (libepoxy.so.0 + 0xbf9d2)
#5 0x0000789da8631ae7 n/a (libkwin.so.5 + 0x431ae7)
#6 0x0000789da8633919 _ZN4KWin9EglDmabufD1Ev (libkwin.so.5 + 0x433919)
#7 0x0000789da8634e71 _ZN4KWin18AbstractEglBackendD2Ev (libkwin.so.5 + 0x434e71)
#8 0x0000789da857677d n/a (libkwin.so.5 + 0x37677d)
#9 0x0000789da83c061b _ZN4KWin10Compositor4stopEv (libkwin.so.5 + 0x1c061b)
#10 0x0000789da83b9198 _ZN4KWin10Compositor12reinitializeEv (libkwin.so.5 + 0x1b9198)
#11 0x0000789da6ac8e27 n/a (libQt5Core.so.5 + 0x2c8e27)
#12 0x0000789da851213a _ZN4KWin9Workspace15slotReconfigureEv (libkwin.so.5 + 0x31213a)
#13 0x0000789da6ac8e27 n/a (libQt5Core.so.5 + 0x2c8e27)
#14 0x0000789da6aca95f _ZN6QTimer7timeoutENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2ca95f)
#15 0x0000789da6abb8de _ZN7QObject5eventEP6QEvent (libQt5Core.so.5 + 0x2bb8de)
#16 0x0000789da61578ff _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1578ff)
#17 0x0000789da6a93ef8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x293ef8)
#18 0x0000789da6ae255b _ZN14QTimerInfoList14activateTimersEv (libQt5Core.so.5 + 0x2e255b)
#19 0x0000789da6ae2a41 _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e2a41)
#20 0x00005b69019c9ed2 n/a (kwin_wayland + 0x137ed2)
#21 0x0000789da6a92c04 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x292c04)
#22 0x0000789da6a940a3 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2940a3)
#23 0x00005b69018e540b n/a (kwin_wayland + 0x5340b)
#24 0x0000789da5a43cd0 n/a (libc.so.6 + 0x25cd0)
#25 0x0000789da5a43d8a __libc_start_main (libc.so.6 + 0x25d8a)
#26 0x00005b69018e7015 n/a (kwin_wayland + 0x55015)
Stack trace of thread 766:
#0 0x0000789da5b190bf __poll (libc.so.6 + 0xfb0bf)
#1 0x0000789da476c2f6 n/a (libglib-2.0.so.0 + 0xb82f6)
#2 0x0000789da470c162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x0000789da6ae2d0c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e2d0c)
#4 0x0000789da6a92c04 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x292c04)
#5 0x0000789da68ef576 _ZN7QThread4execEv (libQt5Core.so.5 + 0xef576)
#6 0x0000789da8911a9a n/a (libQt5DBus.so.5 + 0x17a9a)
#7 0x0000789da68eb79a n/a (libQt5Core.so.5 + 0xeb79a)
#8 0x0000789da5aa955a n/a (libc.so.6 + 0x8b55a)
#9 0x0000789da5b26a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 790:
#0 0x0000789da5b190bf __poll (libc.so.6 + 0xfb0bf)
#1 0x0000789da476c2f6 n/a (libglib-2.0.so.0 + 0xb82f6)
#2 0x0000789da470c162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x0000789da6ae2d0c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e2d0c)
#4 0x0000789da6a92c04 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x292c04)
#5 0x0000789da68ef576 _ZN7QThread4execEv (libQt5Core.so.5 + 0xef576)
#6 0x0000789da68eb79a n/a (libQt5Core.so.5 + 0xeb79a)
#7 0x0000789da5aa955a n/a (libc.so.6 + 0x8b55a)
#8 0x0000789da5b26a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 787:
#0 0x0000789da5aa5ebe n/a (libc.so.6 + 0x87ebe)
#1 0x0000789da5aa8750 pthread_cond_wait (libc.so.6 + 0x8a750)
#2 0x0000789d9da8686c n/a (radeonsi_dri.so + 0x8686c)
#3 0x0000789d9da9e83c n/a (radeonsi_dri.so + 0x9e83c)
#4 0x0000789da5aa955a n/a (libc.so.6 + 0x8b55a)
#5 0x0000789da5b26a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 805:
#0 0x0000789da5b190bf __poll (libc.so.6 + 0xfb0bf)
#1 0x0000789da476c2f6 n/a (libglib-2.0.so.0 + 0xb82f6)
#2 0x0000789da470c162 g_main_context_iteration (libglib-2.0.so.0 + 0x58162)
#3 0x0000789da6ae2d0c _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2e2d0c)
#4 0x0000789da6a92c04 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x292c04)
#5 0x0000789da68ef576 _ZN7QThread4execEv (libQt5Core.so.5 + 0xef576)
#6 0x0000789da78c5a20 n/a (libQt5Qml.so.5 + 0x2c5a20)
#7 0x0000789da68eb79a n/a (libQt5Core.so.5 + 0xeb79a)
#8 0x0000789da5aa955a n/a (libc.so.6 + 0x8b55a)
#9 0x0000789da5b26a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 801:
#0 0x0000789da5aa5ebe n/a (libc.so.6 + 0x87ebe)
#1 0x0000789da5aa8750 pthread_cond_wait (libc.so.6 + 0x8a750)
#2 0x0000789d9da8686c n/a (radeonsi_dri.so + 0x8686c)
#3 0x0000789d9da9e83c n/a (radeonsi_dri.so + 0x9e83c)
#4 0x0000789da5aa955a n/a (libc.so.6 + 0x8b55a)
#5 0x0000789da5b26a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 788:
#0 0x0000789da5aa5ebe n/a (libc.so.6 + 0x87ebe)
#1 0x0000789da5aa8750 pthread_cond_wait (libc.so.6 + 0x8a750)
#2 0x0000789d9da8686c n/a (radeonsi_dri.so + 0x8686c)
#3 0x0000789d9da9e83c n/a (radeonsi_dri.so + 0x9e83c)
#4 0x0000789da5aa955a n/a (libc.so.6 + 0x8b55a)
#5 0x0000789da5b26a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 789:
#0 0x0000789da5aa5ebe n/a (libc.so.6 + 0x87ebe)
#1 0x0000789da5aa8750 pthread_cond_wait (libc.so.6 + 0x8a750)
#2 0x0000789d9da8686c n/a (radeonsi_dri.so + 0x8686c)
#3 0x0000789d9da9e83c n/a (radeonsi_dri.so + 0x9e83c)
#4 0x0000789da5aa955a n/a (libc.so.6 + 0x8b55a)
#5 0x0000789da5b26a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 785:
#0 0x0000789da5aa5ebe n/a (libc.so.6 + 0x87ebe)
#1 0x0000789da5aa8750 pthread_cond_wait (libc.so.6 + 0x8a750)
#2 0x0000789d9da8686c n/a (radeonsi_dri.so + 0x8686c)
#3 0x0000789d9da9e83c n/a (radeonsi_dri.so + 0x9e83c)
#4 0x0000789da5aa955a n/a (libc.so.6 + 0x8b55a)
#5 0x0000789da5b26a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 800:
#0 0x0000789da5aa5ebe n/a (libc.so.6 + 0x87ebe)
#1 0x0000789da5aa8750 pthread_cond_wait (libc.so.6 + 0x8a750)
#2 0x0000789d9da8686c n/a (radeonsi_dri.so + 0x8686c)
#3 0x0000789d9da9e83c n/a (radeonsi_dri.so + 0x9e83c)
#4 0x0000789da5aa955a n/a (libc.so.6 + 0x8b55a)
#5 0x0000789da5b26a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 784:
#0 0x0000789da5aa5ebe n/a (libc.so.6 + 0x87ebe)
#1 0x0000789da5aa8750 pthread_cond_wait (libc.so.6 + 0x8a750)
#2 0x0000789d9da8686c n/a (radeonsi_dri.so + 0x8686c)
#3 0x0000789d9da9e83c n/a (radeonsi_dri.so + 0x9e83c)
#4 0x0000789da5aa955a n/a (libc.so.6 + 0x8b55a)
#5 0x0000789da5b26a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 786:
#0 0x0000789da5aa5ebe n/a (libc.so.6 + 0x87ebe)
#1 0x0000789da5aa8750 pthread_cond_wait (libc.so.6 + 0x8a750)
#2 0x0000789d9da8686c n/a (radeonsi_dri.so + 0x8686c)
#3 0x0000789d9da9e83c n/a (radeonsi_dri.so + 0x9e83c)
#4 0x0000789da5aa955a n/a (libc.so.6 + 0x8b55a)
#5 0x0000789da5b26a3c n/a (libc.so.6 + 0x108a3c)
Stack trace of thread 804:
#0 0x0000789da5aa5ebe n/a (libc.so.6 + 0x87ebe)
#1 0x0000789da5aa8a65 pthread_cond_timedwait (libc.so.6 + 0x8aa65)
#2 0x0000789da68f34b4 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xf34b4)
#3 0x0000789da68f05ea n/a (libQt5Core.so.5 + 0xf05ea)
#4 0x0000789da68eb79a n/a (libQt5Core.so.5 + 0xeb79a)
#5 0x0000789da5aa955a n/a (libc.so.6 + 0x8b55a)
#6 0x0000789da5b26a3c n/a (libc.so.6 + 0x108a3c)
ELF object binary architecture: AMD x86-64
```https://invent.kde.org/plasma/plasma-mobile/-/issues/311Rotating the screen messes up keyboard placement and sizing2024-02-20T16:09:09ZBart RibbersRotating the screen messes up keyboard placement and sizingIf you just hold the phone in it's default orientation, everything is fine. But if you rotate the phone to landscape and open the keyboard, the keyboard appears partially over the panel with the main controls (close, home, etc). If you t...If you just hold the phone in it's default orientation, everything is fine. But if you rotate the phone to landscape and open the keyboard, the keyboard appears partially over the panel with the main controls (close, home, etc). If you then rotate back to portrait with the keyboard still open the entire keyboard will be placed a bit to the left, appearing outside of the screen on the left side and having a gap where you can see the wallpaper on the right side.https://invent.kde.org/plasma/plasma-workspace/-/issues/116Sort appium tests by creating folders2024-03-14T15:44:03ZFushan WenSort appium tests by creating foldersWith more and more appium tests being added, it's necessary to sort them so people will not get lost.
- applets
- kcms
- ...With more and more appium tests being added, it's necessary to sort them so people will not get lost.
- applets
- kcms
- ...Fushan WenFushan Wenhttps://invent.kde.org/plasma/kscreenlocker/-/issues/12Screenlocker is busted in plasma 6 RC22024-02-14T06:29:26ZPetar MargeticScreenlocker is busted in plasma 6 RC2I'm using **plasma 6 RC 2** and I've noticed that **screen locker on X11** isn't working as it's supposed to. Once triggered, it will blank out the screen. Mouse cursor remains visible on it. It takes a long while for it to display the p...I'm using **plasma 6 RC 2** and I've noticed that **screen locker on X11** isn't working as it's supposed to. Once triggered, it will blank out the screen. Mouse cursor remains visible on it. It takes a long while for it to display the password prompt. Once the password is entered, it doesn't respond to ENTER/RETURN on the keyboard, only by clicking on the arrow symbol next to the password field can one get back to the desktop. Once the password is entered, desktop is displayed for split second and once again bla![2024-02-14_14-21-03-_00.00.350-00.37.683_-audio](/uploads/426bd3357dd5548afe099494204022cb/2024-02-14_14-21-03-_00.00.350-00.37.683_-audio.webm)ked for a long while, with mouse cursor again being visible.
Attached you will find a video showcasing the above described issues.https://invent.kde.org/plasma/plasma-mobile/-/issues/310navigationpanel: Close keyboard button icon doesn't change2024-03-14T19:21:44ZDevin Linnavigationpanel: Close keyboard button icon doesn't changeThe icon here doesn't seem to change: https://invent.kde.org/plasma/plasma-mobile/-/blob/master/containments/taskpanel/package/contents/ui/NavigationPanelComponent.qml#L88
The button when clicked does close the keyboard, but the icon re...The icon here doesn't seem to change: https://invent.kde.org/plasma/plasma-mobile/-/blob/master/containments/taskpanel/package/contents/ui/NavigationPanelComponent.qml#L88
The button when clicked does close the keyboard, but the icon remains the "x" icon (not the "down" icon).6https://invent.kde.org/plasma/plasma-mobile/-/issues/309mmplugin: Deduplicate code from kcms/cellularnetwork2024-02-12T20:02:12ZDevin Linmmplugin: Deduplicate code from kcms/cellularnetworkThere is a lot of shared code, let's de-duplicate it
https://invent.kde.org/plasma/plasma-mobile/-/blob/master/components/mmplugin/signalindicator.cpp
https://invent.kde.org/plasma/plasma-mobile/-/blob/master/kcms/cellularnetwork/modem...There is a lot of shared code, let's de-duplicate it
https://invent.kde.org/plasma/plasma-mobile/-/blob/master/components/mmplugin/signalindicator.cpp
https://invent.kde.org/plasma/plasma-mobile/-/blob/master/kcms/cellularnetwork/modem.cpp