Plasma issueshttps://invent.kde.org/groups/plasma/-/issues2023-06-24T19:43:20Zhttps://invent.kde.org/plasma/breeze/-/issues/15breeze dark theme has white topbar2023-06-24T19:43:20Zabhishek kumarbreeze dark theme has white topbarmy theme is `Breeze dark`
## Problem
white topbar on dark breeze theme
![image](/uploads/daeac09a6dd4e929e6bf23286139400e/image.png)
due to white topbar button is not visible may be due to font color issue
![image](/uploads/47366c8525c04...my theme is `Breeze dark`
## Problem
white topbar on dark breeze theme
![image](/uploads/daeac09a6dd4e929e6bf23286139400e/image.png)
due to white topbar button is not visible may be due to font color issue
![image](/uploads/47366c8525c04b0ddfd9d46681bd9770/image.png)https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/issues/10Proposal: Add option to automatically enable "do not disturb" when screencasting2023-06-22T09:33:55ZDominique HummelProposal: Add option to automatically enable "do not disturb" when screencastingA common use for screencasting is presenting the screen contents to someone live. In such a setting, it is usually undesirable to have random notifications pop up during presentation, either because they can be distracting, or because of...A common use for screencasting is presenting the screen contents to someone live. In such a setting, it is usually undesirable to have random notifications pop up during presentation, either because they can be distracting, or because of privacy reasons.
Therefore, I propose to add the option for users to enable automatic toggling of the "DND" mode when screencasting is active. The functionality would work as follows:
1. Screencast begins
2. Is DND active right now? If yes, do nothing. If no, continue to step 3.
3. Enable DND
4. Screencast ends
5. Disable DND (only if it was enabled in step 3)
Of course, this should be a toggle, so users can still allow notifications to appear in case they need to (e.g. they are testing a notification and want to record it using something like OBS that makes use of the screencast portal).
I'd love to get started on this, just want to make sure that this is something worth pursuing first.https://invent.kde.org/plasma/kwin/-/issues/168Port internal windows to GraphicsBuffer2023-08-07T13:33:36ZVlad ZahorodniiPort internal windows to GraphicsBufferInternal windows are fed differently than regular windows, but they're not that different. If internal windows use GraphicsBuffer, we could simplify SurfacePixmap code (merge _internal and _wayland code paths) and perhaps even decouple i...Internal windows are fed differently than regular windows, but they're not that different. If internal windows use GraphicsBuffer, we could simplify SurfacePixmap code (merge _internal and _wayland code paths) and perhaps even decouple it from SurfaceItem, so it can be reused in QtQuick.6https://invent.kde.org/plasma/plasma-workspace/-/issues/75Porting away from PlasmaExtras.Heading2023-10-04T20:06:29ZNate GrahamPorting away from PlasmaExtras.HeadingWith https://invent.kde.org/frameworks/kirigami/-/merge_requests/1120 and https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/801, we don't have to use the PlasmaExtras version of anything in Kirigami as long as it doesn'...With https://invent.kde.org/frameworks/kirigami/-/merge_requests/1120 and https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/801, we don't have to use the PlasmaExtras version of anything in Kirigami as long as it doesn't internally use any components that use SVG styling. At this point that's just PlasmaExtras.Heading, so let's port away from it.
Merge Requests and commits for this work:
- https://invent.kde.org/frameworks/plasma-framework/-/commit/bb7cee60554d86aeca2653b0e5a730925b76af3b
- https://invent.kde.org/frameworks/plasma-framework/-/commit/191288e4f26ecb54ce74b003370ef426acbed091
- https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2999
- https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1574
- https://invent.kde.org/plasma/kdeplasma-addons/-/commit/051ee88139ddccb28bf38f9036588446b0b1800d
- https://invent.kde.org/plasma/plasma-sdk/-/commit/20accc05f6af673b535679363c9464a97747e45c
- https://invent.kde.org/plasma/kscreenlocker/-/merge_requests/158
- https://invent.kde.org/plasma/kscreen/-/commit/45cee20f12d2c37d847d8b2e7fa4bd9b80ae6ec6
- https://invent.kde.org/plasma/kwin/-/commit/fb6edd72e8491b81abbe321da1e687e95aa84f1c
- https://invent.kde.org/plasma/powerdevil/-/commit/80a8f8bdd55215f667b1d4f63c378ebcfb2bc6c0
To be able to use Kirigami components that are the same as their PlasmaExtras versions except for the fact that they use SVG-themed components (such as `PlaceholderMessage`), we will need a bit more work; that's TBD.6https://invent.kde.org/plasma/plasma-workspace/-/issues/74Porting away from PlasmaCore.Units, PlasmaCore.Theme, and PlasmaCore.ColorScope2023-11-03T21:39:31ZNate GrahamPorting away from PlasmaCore.Units, PlasmaCore.Theme, and PlasmaCore.ColorScopeWe don't have to use these because they have Kirigami equivalents now, and have been removed in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/854.
Here are the MRs porting away from them:
- https://invent.kde.org/...We don't have to use these because they have Kirigami equivalents now, and have been removed in https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/854.
Here are the MRs porting away from them:
- https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/819
- https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1574
- https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1604
- https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3045
- https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3210
- https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/418
- https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/428
- https://invent.kde.org/plasma/plasma-sdk/-/merge_requests/84
- https://invent.kde.org/plasma/plasma-sdk/-/merge_requests/91
- https://invent.kde.org/plasma/plasma-nm/-/merge_requests/264
- https://invent.kde.org/plasma/plasma-pa/-/merge_requests/186
- https://invent.kde.org/plasma/plasma-pa/-/merge_requests/196
- https://invent.kde.org/plasma/bluedevil/-/merge_requests/132
- https://invent.kde.org/plasma/plasma-vault/-/merge_requests/30
- https://invent.kde.org/plasma/kscreen/-/merge_requests/219
- https://invent.kde.org/plasma/milou/-/merge_requests/63
- https://invent.kde.org/plasma/milou/-/merge_requests/68
- https://invent.kde.org/plasma/plasma-welcome/-/merge_requests/98
- https://invent.kde.org/plasma/polkit-kde-agent-1/-/merge_requests/28
- https://invent.kde.org/plasma/powerdevil/-/merge_requests/2126https://invent.kde.org/plasma/powerdevil/-/issues/20powerdevil & apparmor.d2023-06-15T16:54:58Zcherkab cherifpowerdevil & apparmor.dso as to strenghten my system security i installed apparmor.d ( AUR softwar on manjaro ).
since "Failed to start Powerdevil" (log)
impossible to get access to the power manager module (see below my screen shot)
![Screenshot_powerdevil...so as to strenghten my system security i installed apparmor.d ( AUR softwar on manjaro ).
since "Failed to start Powerdevil" (log)
impossible to get access to the power manager module (see below my screen shot)
![Screenshot_powerdevil](/uploads/81bd5c8ad8de1bcb6115dd4e60e2e2cd/Screenshot_powerdevil.png)https://invent.kde.org/plasma/ocean-sound-theme/-/issues/5Follow sound naming spec2023-07-04T21:37:08ZGuilherme Marçal SilvaFollow sound naming specThe files in this theme should be renamed following the freedesktop sound naming spec.
v0.3 draft: http://0pointer.de/public/sound-naming-spec.html
0.2: https://specifications.freedesktop.org/sound-naming-spec/sound-naming-spec-latest.h...The files in this theme should be renamed following the freedesktop sound naming spec.
v0.3 draft: http://0pointer.de/public/sound-naming-spec.html
0.2: https://specifications.freedesktop.org/sound-naming-spec/sound-naming-spec-latest.html
----
Early mapping between the current sound names, Oxygen sounds, and the spec:
**New:**
Plug_device - device-added
Unplug_device - device-removed
Power_plug - power-plug
Power_unplug - power-unplug
Volume_change - audio-volume-change
Low_battery - battery-caution
Critical_battery - battery-low
SMS_notification - message-new
Generic_beep - bell-window-system
completion-partial
Trash - trash-empty
**Sounds with Oxygen counterparts:**
**Original Blue Ocean name - Oxygen - Spec**
Error - Oxygen-Sys-App-Error - dialog-error
Error_serious - Oxygen-Sys-App-Error-Serious - dialog-error-serious (not in spec but it allows naming more specific sounds)
Information_dialog - Oxygen-Sys-App-Message - dialog-information
Question-warning_dialog - Oxygen-Sys-Question - dialog-question
Generic_positive - Oxygen-Sys-App-Positive - outcome-success
Generic_negative - Oxygen-Sys-App-negative - outcome-failure
dialog-warning - Oxygen-Sys-Warning - dialog-warning
Log_out - Oxygen-Sys-Log-Out - desktop-logout
Log_out_short - Oxygen-Sys-Log-Out - service-logout
Login - Oxygen-Sys-Log-In - desktop-login
? - Oxygen-Im-Phone-Ring - phone-incoming-call
? - Oxygen-Sys-List-Match-No - completion-fail
? - Oxygen-Sys-List-End - completion-rotation
? - Oxygen-Sys-List-Match-Multiple - completion-success
**Issues:**
- [x] Plasma uses Oxygen-Sys-App-Positive and Oxygen-Sys-App-Negative in many places for positive and negative actions. There's no equivalent to that on the spec. What do we do? - **Solution**: Name them outcome-success and outcome-failure
- [x] There's no equivalent to SMS_notification on the spec, maybe we could rename it as 'message-new-sms', which is similar to 'message-new-email' but is not present explicitly on the spec? - **Solution:** rename to more generic 'message-new'.
- [x] Oxygen has Oxygen-Sys-Special. The only place where it's listed is under Accessibility notifications (SySe>Notifications>Application-specific settings> Accessibility), but the sounds are disabled by default. I checked all repositories under #6 but only KAccess uses them. Do we need a replacement for it or do we use another sound for that instead (e.g. beep sound)? - **Solution:** Replace it with the system bell sound.
@mart @ngraham (please tag more people that might be interested if you know any)https://invent.kde.org/plasma/plasma-workspace/-/issues/73[Enhancement] Make Klipper standalone application2023-06-12T18:50:03ZAvid Seeker[Enhancement] Make Klipper standalone applicationMany users don't feel comfortable having a program in the background saving their clipboard content. There were many forum posts asking for a way to uninstall or completely disable Klipper. E.g: this [post](https://askubuntu.com/question...Many users don't feel comfortable having a program in the background saving their clipboard content. There were many forum posts asking for a way to uninstall or completely disable Klipper. E.g: this [post](https://askubuntu.com/questions/1032985/remove-klipper-from-kubuntu) says:
> "Klipper" is part of the plasma-workspace package and cannot be uninstalled without removing all of KDE.
The current way to disable Klipper is through `System Tray settings > General > Extra Items`, but even with that, `pgrep klipper` shows that Klipper still runs in the background. Second problem is user needs to switch to Plasma session just to disable it.
Edit: Bugzilla bug report: https://bugs.kde.org/show_bug.cgi?id=470947https://invent.kde.org/plasma/krdp/-/issues/3Server crashed when client disconnected2023-06-14T16:11:22ZNate GrahamServer crashed when client disconnectedAfter terminating the Microsoft Remote Desktop client connection described in https://invent.kde.org/ahiemstra/krdp/-/issues/2, the server immediately crashed. Backtrace of the crashing thread:
```
Application: krdpserver (krdpserver), ...After terminating the Microsoft Remote Desktop client connection described in https://invent.kde.org/ahiemstra/krdp/-/issues/2, the server immediately crashed. Backtrace of the crashing thread:
```
Application: krdpserver (krdpserver), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr<char []> = {get() = 0x0}
[KCrash Handler]
#0 __pthread_kill_implementation
(threadid=<optimized out>, signo=signo@entry=11, no_tid=no_tid@entry=0)
at pthread_kill.c:44
#1 0x00007fd1ad8b08b3 in __pthread_kill_internal (signo=11, threadid=<optimized out>)
at pthread_kill.c:78
#2 0x00007fd1ad85fabe in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#3 0x00007fd18b2e2916 in KCrash::defaultCrashHandler(int) (sig=11)
at /home/nate/kde/src/kcrash/src/kcrash.cpp:616
#4 0x00007fd1ad85fb70 in <signal handler called> () at /lib64/libc.so.6
#5 memcpy
(__len=8, __src=0x5f, __dest=<synthetic pointer>, __dest=<optimized out>, __src=<optimized out>, __len=<optimized out>) at /usr/include/bits/string_fortified.h:29
#6 av_freep (arg=0x5f) at libavutil/mem.c:249
#7 0x00007fd1ab1548f6 in av_packet_free_side_data (pkt=pkt@entry=0x7fd14e2fc030)
at libavcodec/avpacket.c:191
#8 0x00007fd1ab155045 in av_packet_unref (pkt=0x7fd14e2fc030)
at libavcodec/avpacket.c:424
#9 0x00007fd1ab200623 in avcodec_receive_packet
(avctx=0x7fd16c104fc0, avpkt=0x7fd14e2fc030) at libavcodec/encode.c:526
#10 0x00007fd1af34ac91 in PipeWireReceiveEncodedThread::run() (this=0x7fd16c1d27d0)
at /home/nate/kde/src/kpipewire/src/pipewireproduce.cpp:587
#11 0x00007fd1ae30214a in operator() (__closure=<optimized out>)
at /usr/src/debug/qt6-qtbase-6.5.1-1.fc38.x86_64/src/corelib/thread/qthread_unix.cpp:321
#12 (anonymous namespace)::terminate_on_exception<QThreadPrivate::start(void*)::<lambda()> > (t=<optimized out>)
at /usr/src/debug/qt6-qtbase-6.5.1-1.fc38.x86_64/src/corelib/thread/qthread_unix.cpp:257
#13 QThreadPrivate::start(void*) (arg=0x7fd16c1d27d0)
at /usr/src/debug/qt6-qtbase-6.5.1-1.fc38.x86_64/src/corelib/thread/qthread_unix.cpp:280
#14 0x00007fd1ad8ae907 in start_thread (arg=<optimized out>) at pthread_create.c:444
#15 0x00007fd1ad934870 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81
```https://invent.kde.org/plasma/krdp/-/issues/1No feedback that automatic certificate generation of certificate has completed2023-06-12T11:14:12ZNate GrahamNo feedback that automatic certificate generation of certificate has completed```
krdpserver -u test -p test
Could not find certificate and certificate key, generating temporary certificate...
```
The trailing ellipses suggests that it's an ongoing process that will take some time, b...```
krdpserver -u test -p test
Could not find certificate and certificate key, generating temporary certificate...
```
The trailing ellipses suggests that it's an ongoing process that will take some time, but then it just sits there, never telling you when it's completed.
However, it has in fact already completed.
There needs to be some kind of additional message saying something like "Certificate generation completed; ready to accept connections."https://invent.kde.org/plasma/ksshaskpass/-/issues/1Unable to do a `git commit` without the key being added beforehand2023-06-06T20:24:17ZGuilherme SilvaUnable to do a `git commit` without the key being added beforehandI recently switched to KDE Plasma, but when I was using GNOME, what I'll describe used to work flawlessly:
Currently, I'm not able to just log into my desktop and do a `git commit`, for example. This is the error I get:
```
$ git commi...I recently switched to KDE Plasma, but when I was using GNOME, what I'll describe used to work flawlessly:
Currently, I'm not able to just log into my desktop and do a `git commit`, for example. This is the error I get:
```
$ git commit -m 'foo' --allow-empty
error: Couldn't find key in agent?
fatal: failed to write commit object
```
I understand the error message (I think, lol): I must `ssh-add` my key first. Alternatively, I can do a `git fetch` and then KSSHAskPass will prompt me for the password and the key is added to the agent. But that's a little annoying/tedious, to be honest.
On GNOME, this was somehow done automatically: On any git operation that needed authentication, the password prompt would *always* pop up first, so errors like the one I mentioned above never happened to me.
Is it possible to achieve the same with KSSHAskPass (or any other tool, really)? I.e., can I just login, do a `git commit` and make KSSHAskPass prompt me for my password?
Thank you!https://invent.kde.org/plasma/latte-dock/-/issues/126latte does not build on KDE neon unstable (Qt 6 Preview)2023-05-24T15:17:17ZLeonard Hasselmannlatte does not build on KDE neon unstable (Qt 6 Preview)SUMMARY
On the current (05/24/23) snapshot of KDE neon Unstable latte won't build due to cmake errors
```
CMake Error at CMakeLists.txt:39 (find_package):
By not providing "FindLibTaskManager.cmake" in CMAKE_MODULE_PATH this
projec...SUMMARY
On the current (05/24/23) snapshot of KDE neon Unstable latte won't build due to cmake errors
```
CMake Error at CMakeLists.txt:39 (find_package):
By not providing "FindLibTaskManager.cmake" in CMAKE_MODULE_PATH this
project has asked CMake to find a package configuration file provided by
"LibTaskManager", but CMake did not find one.
Could not find a package configuration file provided by "LibTaskManager"
with any of the following names:
LibTaskManagerConfig.cmake
libtaskmanager-config.cmake
Add the installation prefix of "LibTaskManager" to CMAKE_PREFIX_PATH or set
"LibTaskManager_DIR" to a directory containing one of the above files. If
"LibTaskManager" provides a separate development package or SDK, be sure it
has been installed.
```
All packages from the INSTALLATION.md are installed.
OBSERVED RESULT
build error
EXPECTED RESULT
build
SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.27.80
KDE Frameworks Version: 5.240.0
Qt Version: 6.5.0https://invent.kde.org/plasma/plasma-workspace/-/issues/71Plasma/5.27 CI broken2023-06-10T21:26:27ZStefan BrünsPlasma/5.27 CI brokenCI seems to use the wrong layer-shell version (5.27.80 instead of 5.27.5):
https://invent.kde.org/plasma/plasma-workspace/-/jobs/965296#L2752
```
/usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: /builds/plasma...CI seems to use the wrong layer-shell version (5.27.80 instead of 5.27.5):
https://invent.kde.org/plasma/plasma-workspace/-/jobs/965296#L2752
```
/usr/lib64/gcc/x86_64-suse-linux/13/../../../../x86_64-suse-linux/bin/ld: /builds/plasma/plasma-workspace/_install/lib64/libLayerShellQtInterface.so.5.27.80: undefined reference to `QtWaylandClient::QWaylandWindow::handleExpose(QRegion const&)@Qt_5.15.8_PRIVATE_API'
collect2: error: ld returned 1 exit status
make[2]: *** [ksplash/ksplashqml/CMakeFiles/ksplashqml.dir/build.make:146: bin/ksplashqml] Error 1
make[1]: *** [CMakeFiles/Makefile2:11823: ksplash/ksplashqml/CMakeFiles/ksplashqml.dir/all] Error 2
```
This then affects all projects dependent on plasma-workspace >= 5.27.5, last built version of plasma-workspace is 5.27.4.Ben CooksleyBen Cooksleyhttps://invent.kde.org/plasma/libplasma/-/issues/15Plasmoid API changes2023-08-16T13:29:52ZMarco MartinPlasmoid API changesPorting guide: https://invent.kde.org/documentation/develop-kde-org/-/merge_requests/291
API changes made in: https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/778
Repos that need to adapt to it:
- https://invent.kde....Porting guide: https://invent.kde.org/documentation/develop-kde-org/-/merge_requests/291
API changes made in: https://invent.kde.org/frameworks/plasma-framework/-/merge_requests/778
Repos that need to adapt to it:
- https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2896
- https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1505
- https://invent.kde.org/plasma/kdeplasma-addons/-/merge_requests/386
- https://invent.kde.org/plasma/plasma-sdk/-/merge_requests/71
- https://invent.kde.org/plasma/plasma-vault/-/merge_requests/28
- https://invent.kde.org/plasma/plasma-pa/-/merge_requests/177
- https://invent.kde.org/plasma/bluedevil/-/merge_requests/126
- https://invent.kde.org/plasma/plasma-nm/-/merge_requests/249
- https://invent.kde.org/plasma/kscreen/-/merge_requests/213
- https://invent.kde.org/plasma/milou/-/merge_requests/61
- https://invent.kde.org/plasma/plasma-nano/-/merge_requests/39
- https://invent.kde.org/utilities/print-manager/-/merge_requests/42https://invent.kde.org/plasma/discover/-/issues/24rpm-ostree-backend doesn't support some valid ostree image reference formats2023-12-12T17:26:14ZJoseph Martinrpm-ostree-backend doesn't support some valid ostree image reference formatsOriginally reported to the ublue here: https://github.com/ublue-os/main/issues/132
OSTree native containers can be specified in a number of ways, and it appears that Discover only currently works if the image reference begins with `ostr...Originally reported to the ublue here: https://github.com/ublue-os/main/issues/132
OSTree native containers can be specified in a number of ways, and it appears that Discover only currently works if the image reference begins with `ostree-unverified-registry`. However, it may also start with a number of other things including `ostree-unverified-image`, `ostree-image-signed`, `ostree-remote-image`, `ostree-remote-registry`. When attempting to start Discover with ostree referencing an image that starts in one of these other ways, Discover currently crashes.
Example output when it crashes:
```
$ plasma-discover
rpm-ostree-backend: Invalid reference for OCI container ostree format: "ostree-unverified-image:docker://ghcr.io/ublue-os/kinoite-nvidia:38"
1pm-ostree-backend: Starting transaction to check for updates
rpm-ostree-backend: Error: Can not start a transaction for resource with an invalid format. Please file a bug.
org.kde.plasma.libdiscover: transaction not part of the model RpmOstreeTransaction(0x55a798d95d40)
KCrash: Application 'plasma-discover' crashing...
The Wayland connection experienced a fatal error: Bad file descriptor
``Timothée RavierTimothée Ravierhttps://invent.kde.org/plasma/plasma-workspace/-/issues/70secondary calendar date & time for tooltip & date time format string2023-05-17T17:28:54ZMahdi Firouzjahsecondary calendar date & time for tooltip & date time format stringif we enable a secondary calendar a tooltip that shows the date in that calendar will be available inside the calendar, I mean when we hover over a date inside the calendar. also there is a log format of current date in secondary calenda...if we enable a secondary calendar a tooltip that shows the date in that calendar will be available inside the calendar, I mean when we hover over a date inside the calendar. also there is a log format of current date in secondary calendar format, in the agenda subtitle(as shown in in the screenshot bellow).
but there should be a posseblity for tooltip to show date in secondary calendar when we hover over the clock plus it would be very useful if we could have a chance to enter a custom date format in order to have date in secondary calendar beside/bellow the click.(currently it only accepts qt.date format string and date is in Gregorian)
also it would be easier to add a second text box to specify the locale format and then using JS `Date().toLocaleDateString()` which will enable user to have more control on what he want to see, e.g: `new Date().toLocaleDateString('fa-IR',{year:'numeric',month:'2-digit',day:'2-digit',formatMatcher:'basic'})`
![Screenshot_20230517_112017](/uploads/df633fbb59092ab70be20c08eeba9909/Screenshot_20230517_112017.png)
![Screenshot_20230517_111101](/uploads/dddc449f4abccf39e7ac5a019fc52fa5/Screenshot_20230517_111101.png)https://invent.kde.org/plasma/kwin/-/issues/154Broken ownership in buttonsrebind and sticky keys plugin2023-11-20T13:05:34ZNicolas FellaBroken ownership in buttonsrebind and sticky keys pluginThe buttons rebind and sticky keys plugin have a class that extends from both `KWin::Plugin` and `KWin::InputEventFilter`.
Plugin instances are owned by PluginManager. InputEventFilters are deleted by InputRedirection. This can cause do...The buttons rebind and sticky keys plugin have a class that extends from both `KWin::Plugin` and `KWin::InputEventFilter`.
Plugin instances are owned by PluginManager. InputEventFilters are deleted by InputRedirection. This can cause double deletes of the object.
Noticed this while working on an autotest for sticky keys. The fact that this doesn't seem to blow up right now seems just coincidentalhttps://invent.kde.org/plasma/plasma-workspace/-/issues/68Redesign per-event config in notifications KCM2023-07-28T19:41:47ZNicolas FellaRedesign per-event config in notifications KCMCurrently the notifications KCM has the "Configure Events..." button that opens a dialog window with fine-grained settings.
That dialog is kind of odd UX-wise. This was mostly laziness during the KCM QML port by keeping the existing dia...Currently the notifications KCM has the "Configure Events..." button that opens a dialog window with fine-grained settings.
That dialog is kind of odd UX-wise. This was mostly laziness during the KCM QML port by keeping the existing dialog from KNotifyConfig. Another part of the reason was that the dialog was somewhat complex with lots of types of possible actions.
We recently slimmed down these actions so only "Show a message in a popup" and "Play a sound" remain.
We should fold the UI for these into the main KCM view and get rid of the extra dialog
@teams/vdghttps://invent.kde.org/plasma/ocean-sound-theme/-/issues/3REUSE compliance2023-06-28T22:14:35ZNate GrahamREUSE complianceWe'll want this sound theme to be REUSE-compliant. That means adding a `.license` file next to every file in the repo (following the pattern you can see in https://invent.kde.org/plasma/oxygen-sounds/-/tree/master/sounds), or else having...We'll want this sound theme to be REUSE-compliant. That means adding a `.license` file next to every file in the repo (following the pattern you can see in https://invent.kde.org/plasma/oxygen-sounds/-/tree/master/sounds), or else having a `.reuse/dep5` file that lists the licenses of everything there (following the pattern you can see in https://invent.kde.org/plasma/plasma-welcome/-/blob/master/.reuse/dep5).https://invent.kde.org/plasma/ocean-sound-theme/-/issues/2Consistent naming with old `oxygen-sounds` repo2023-06-13T19:23:42ZNate GrahamConsistent naming with old `oxygen-sounds` repoThe sounds that live in the ["Oxygen Sounds" repo](https://invent.kde.org/plasma/oxygen-sounds/-/tree/master/sounds) are unfortunately all prefixed with `Oxygen-`. In [the spec](http://0pointer.de/public/sound-theme-spec.html) I see no m...The sounds that live in the ["Oxygen Sounds" repo](https://invent.kde.org/plasma/oxygen-sounds/-/tree/master/sounds) are unfortunately all prefixed with `Oxygen-`. In [the spec](http://0pointer.de/public/sound-theme-spec.html) I see no mention of any kind of naming standardization, so I guess we're in the clear, even though this prefix is really not ideal.
To avoid having to change the name of every single sound in all KDE software that is requested, could you mirror the naming scheme used by the `oxygen-sounds` repo in this one? That way this sound theme will be a drop-in replacement for `oxygen-sounds` with no drama.