Plasma issueshttps://invent.kde.org/groups/plasma/-/issues2024-02-23T15:31:52Zhttps://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/kwin/-/issues/206Architecture discussion for brightness control in KWin2024-03-20T16:01:49ZAnurag ThakurArchitecture discussion for brightness control in KWinAs part of my SoK project, I am creating this issue to discuss the proposed architecture for implementing brightness control in KWin
## Current Status
The current architecture looks like this:
```mermaid
graph TB
Action -- "DBus" -->...As part of my SoK project, I am creating this issue to discuss the proposed architecture for implementing brightness control in KWin
## Current Status
The current architecture looks like this:
```mermaid
graph TB
Action -- "DBus" --> Kact
Enum -- "DBus" --> plasma-workspace/applets/brightness
subgraph plasma-workspace/applets/brightness
Action[User Action]
end
subgraph powerdevil/daemon
Kact("KAuth Action (backlightbrightness.cpp)")
Enum("Screen Enumeration (backlighthelper_linux.cpp)")
end
```
## Proposals
There are a few different ways we could implement brightness control in KWin:
### Wayland only (1)
If X11 support can be dropped, we could move the brightness handling code to kwin completely. the architecture could look like this:
```mermaid
graph TB
Action -- "DBus/Wayland API" --> HDR
Enum -- "DBus/Wayland API" --> plasma-workspace/applets/brightness
HDR --> Kact
subgraph plasma-workspace/applets/brightness
Action[User Action]
end
subgraph kwin/new_code
HDR("HDR handling")
Kact("KAuth/logind/sysfs call")
Enum("Screen Enumeration")
end
```
#### Benefits
- Simple architecture
- No code duplication
#### Drawbacks
- No X11 support
- More code changes required
### Wayland + X11 (2)
If X11 support needs to be retained, we need to support the scenario where a different window manager is used, so brightness control can't depend on KWin. Xaver proposed that we use the existing backlight helper from powerdevil and use a new wayland protocol for communication between kwin and powerdevil as DBus may not be responsive enough.
The architecture could look like this:
```mermaid
graph TB
Action -- "DBus" --> Kact
Enum -- "DBus" --> plasma-workspace/applets/brightness
Kact -- "Yes\n\nWayland Protocol" --> HDR
Kact -- "No (X11)" --> X11
HDR -- "Wayland Protocol" --> Help
subgraph plasma-workspace/applets/brightness
Action[User Action]
end
subgraph powerdevil/daemon
Kact{"Kwin present?"}
Enum("Screen Enumeration (backlighthelper_linux.cpp)")
X11("Existing code")
Help("Backlight Helper")
end
subgraph Kwin
HDR("HDR etc. handling")
end
```
#### Benefits
- Less code changes required
- Support for X11 retained
#### Drawbacks
- Complicated architecture
- Possible performance penalty
### Wayland + X11 (3)
Alternatively, KWin can provide the DBus interface for the brightness applet on wayland and powerdevil can continue to provide it on X11.
```mermaid
graph TB
Action -- "DBus" --> Chk
Chk -- "Wayland" --> Kwin
Chk -- "X11" --> Control
Kwin --> ncnt
Enum -- "DBus (X11)" --> plasma-workspace/applets/brightness
Enum2 -- "DBus (Wayland)" --> plasma-workspace/applets/brightness
subgraph plasma-workspace/applets/brightness
Action[User Action]
Chk{"Session Type"}
end
subgraph kwin
Kwin("DBus API provider")
ncnt("HDR handling + backlight control")
Enum2("Screen Enumeration")
end
subgraph powerdevil
Control("Existing control")
Enum("Screen Enumeration")
end
```
#### Benefits
- Basically (1) with X11 support retained
- Kwin code can be improved independently of powerdevil and X11
- Later if X11 support is dropped, it would become the same as (1)
#### Drawbacks
- Slight code duplication
- More code changes required
Please share your insights and mention if I missed/misunderstood anything.https://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/plasma-mobile/-/issues/312actiondrawer: Landscape clock text seems to turn black instead of go opaque a...2024-03-16T03:36:06ZDevin Linactiondrawer: Landscape clock text seems to turn black instead of go opaque as drawer is open/closed![image](/uploads/a3e1cd7fd4a529e8d724fc8f4e8b2ada/image.png)![image](/uploads/a3e1cd7fd4a529e8d724fc8f4e8b2ada/image.png)https://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.cpphttps://invent.kde.org/plasma/plasma-mobile/-/issues/308quicksettings/dockedmode: Toggling docked mode seems to crash the shell (or k...2024-02-23T15:32:36ZDevin Linquicksettings/dockedmode: Toggling docked mode seems to crash the shell (or kwin?)Experienced on pmOS nightlyExperienced on pmOS nightlyhttps://invent.kde.org/plasma/plasma-workspace/-/issues/115RFC: replace "icon spacing" settings in Icon Task Manager and System Tray wit...2024-02-17T19:51:04ZJin Lium.liu.jin@gmail.comRFC: replace "icon spacing" settings in Icon Task Manager and System Tray with a panel-level "density" settingThe main problem with the current setting: in the default panel (as in the screenshot in https://kde.org), the user would perceive Kickoff and Icon Task Manager as a single row of icons, instead of two applets. But if the user change the...The main problem with the current setting: in the default panel (as in the screenshot in https://kde.org), the user would perceive Kickoff and Icon Task Manager as a single row of icons, instead of two applets. But if the user change the icon spacing setting, the spacing between the Kickoff icon and the rest of icons becomes uneven.
So I propose lifting the setting up into the panel config dialog. All applets in the panel should set their margin according to the panel setting (supposedly implemented in some common code). And containers like Task Manager and System Tray should also set their internal margins.
Moreover, when the panel is full, it could reduce the density (just like Task Manager currently does), so all applets shrink simultaneously. Thus, while the user-facing "density" setting probably has only three options, e.g. Compact, Normal, Spacious, the actual setting passed to applets should be in px.https://invent.kde.org/plasma/krdp/-/issues/15Needs porting to FreeRDP 3.x2024-02-09T12:04:48ZNeal GompaNeeds porting to FreeRDP 3.xI had assumed based on 4ff283a7afdcf4fed67450aeb1739463f4a59488 that KRdp builds with FreeRDP 3, but that is apparently not the case currently.
Fedora is switching to FreeRDP 3 for Fedora 40, but it currently fails to build with [my com...I had assumed based on 4ff283a7afdcf4fed67450aeb1739463f4a59488 that KRdp builds with FreeRDP 3, but that is apparently not the case currently.
Fedora is switching to FreeRDP 3 for Fedora 40, but it currently fails to build with [my commit](https://invent.kde.org/ngompa/krdp/-/commit/2ac6b00d376c9f15fedca71b0268c6d33fe9bc92) to bump to FreeRDP 3.
Here's a full build log from the Fedora Rawhide package build: [80f8d261.txt](/uploads/d7b25c343ffa370901c0badf4885ff6f/80f8d261.txt)https://invent.kde.org/plasma/kwin/-/issues/203Rename night color to night light2024-02-27T20:55:55ZVlad ZahorodniiRename night color to night lightNight Light goes under three names currently:
- ColorCorrect
- NightColor
- NightLight
it's messy, it would be great to clean things up a bit.
Changing the class names shouldn't be a problem. Changing the d-bus interface can be consid...Night Light goes under three names currently:
- ColorCorrect
- NightColor
- NightLight
it's messy, it would be great to clean things up a bit.
Changing the class names shouldn't be a problem. Changing the d-bus interface can be considered as an api breaking change and it is preferred to avoid such changes in minor releases if possible.
The types can be renamed later, but the d-bus interfaces may need to be renamed in 6.0 to avoid breaking API in 6.1.https://invent.kde.org/plasma/kwin/-/issues/202Requirements for dropping Xorg support2024-03-19T18:01:32ZXaver HuglRequirements for dropping Xorg supportWith #139 we won't be as restricted by Xorg anymore - both architecturally and in terms of bugfixes for Xwayland triggering regressions on Xorg (like with https://invent.kde.org/plasma/kwin/-/commit/3a28c02f287f4acdde77508aa716ca01a3be75...With #139 we won't be as restricted by Xorg anymore - both architecturally and in terms of bugfixes for Xwayland triggering regressions on Xorg (like with https://invent.kde.org/plasma/kwin/-/commit/3a28c02f287f4acdde77508aa716ca01a3be7514) - but we'll still have to maintain kwin_x11, and keep the APIs shared with kwin_wayland in sync, like effects and scripts (or force them to support only one or the other). This will likely work out okay for a while, but doing it forever is not great.
As a way out of that, at some point in the future we will completely freeze kwin_x11, and eventually drop it entirely. This issue serves as a list of user facing problems that at least kind of work on Xorg and need be taken care of before that can happen:
- [ ] explicit sync for NVidia: !4693, [xserver!967](https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/967), [wayland-protocols!90](https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/90)
- [ ] old NVidia GPUs on legacy driver branches that don't support gbm:
- [ ] With driver version 470, we can at least start a working session by using dumb buffers and CPU rendering. Maybe show some warning that the driver isn't supported anymore, and that the user should switch to Nouveau?
- [ ] For even older stuff, we can't show anything in a Wayland session - SDDM probably needs to keep a fallback to Xorg for a while, and warn the user about the incompatibilities there
- [ ] plasmashell could still support Xorg with other WMs
- [ ] screen sharing for Xwayland apps: Xwayland video bridge should be shipped by default in distros, and possibly integrated into Plasma directly
- [ ] the upstream color management protocol needs to implemented (not just a snapshot like https://invent.kde.org/plasma/kwin/-/merge_requests/5060), and at least some of the more common apps relying on color management should be ported to use it
- [ ] accessibility. Don't know exactly what's still missing, please add sub-items here as appropriate!
- [ ] task automation (which has overlap with accessibility). At least the common stuff should imo be covered, like triggering key sequences with a keyboard shortcut. There's some existing stuff for this too:
- [ ] KWin scripts for this exist. I don't know if any are sufficient though
- [ ] ydotool exists as well, but it requires root access
- [ ] many things can be done through AT-SPI2
- [ ] support for libei / input leap
- [ ] session restoration
- [ ] (good) unattended remote desktop solutionhttps://invent.kde.org/plasma/plasma-mobile/-/issues/307taskswitcher: KWin effects seem to be extremely slow on the pinephone2024-03-16T17:19:29ZDevin Lintaskswitcher: KWin effects seem to be extremely slow on the pinephoneThe task switcher is considerably slower than other parts of the shell on the Pinephone (~5fps). I suspect that it's related to how it's a KWin effect.The task switcher is considerably slower than other parts of the shell on the Pinephone (~5fps). I suspect that it's related to how it's a KWin effect.6https://invent.kde.org/plasma/plasma-mobile/-/issues/306homescreens/folio: Wallpaper blur causes extreme lag on the pinephone2024-03-07T13:10:37ZDevin Linhomescreens/folio: Wallpaper blur causes extreme lag on the pinephoneWhile it seems to work fine on SDM845 devices, the wallpaper blur seems to cause extreme lag on the pinephone
https://invent.kde.org/plasma/plasma-mobile/-/blob/90e31aff0639c56cc6afbfe916f7401ee4dce203/containments/homescreens/folio/pac...While it seems to work fine on SDM845 devices, the wallpaper blur seems to cause extreme lag on the pinephone
https://invent.kde.org/plasma/plasma-mobile/-/blob/90e31aff0639c56cc6afbfe916f7401ee4dce203/containments/homescreens/folio/package/contents/ui/main.qml#L426https://invent.kde.org/plasma/plasma-mobile/-/issues/305quicksettings: Holding to open settings app doesn't show app launch screen2024-02-07T03:50:15ZDevin Linquicksettings: Holding to open settings app doesn't show app launch screen6https://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/