Debian Patches
Status for kde-spectacle/4:6.3.5-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| upstream_dd1892d8_VideoPlatformWayland-Don-t-use-QtConcurrent-for-creating-KPipeWire-stream.patch | [PATCH] VideoPlatformWayland: Don't use QtConcurrent for creating KPipeWire stream This was done to hide the latency of querying VAAPI, but means that the KPipeWire stream lives in the QtConcurrent thread which lacks an event loop, meaning any event processing the KPipeWire stream does breaks. Since the KPipeWire stream no longer queries VAAPI on creation, we can now safely do this on the same thread as the VideoPlatform. |
Arjen Hiemstra <ahiemstra@heimr.nl> | no | 2024-10-08 | ||
| upstream_f7e5e541_VideoPlatformWayland-Update-to-changed-KPipeWire-API.patch | [PATCH] VideoPlatformWayland: Update to changed KPipeWire API setActive() has been replaced with a more explicit start()/stop() API, so use that. In addition, forward the Rendering state to VideoPlatform. |
Arjen Hiemstra <ahiemstra@heimr.nl> | no | 2024-10-08 | ||
| upstream_805ae503_SpectacleCore-Update-system-tray-based-on-VideoPlatform-recordingState.patch | [PATCH] SpectacleCore: Update system tray based on VideoPlatform::recordingState Rather than the binary "recording", use the new recordingState property and also handle the "rendering" state. |
Arjen Hiemstra <ahiemstra@heimr.nl> | no | 2024-10-08 | ||
| upstream_007c3bc8_VideoPlatformWayland-Clear-node-when-starting-a-new-recording.patch | [PATCH] VideoPlatformWayland: Clear node when starting a new recording | Noah Davis <noahadvs@gmail.com> | no | 2025-04-18 | ||
| upstream_6d6d5875_Set-rendering-message-for-system-tray-icon-tooltip.patch | [PATCH] Set rendering message for system tray icon tooltip | Noah Davis <noahadvs@gmail.com> | no | 2025-04-22 | ||
| upstream_1572f19b_Change-rendering-notification-icon-to-process-working-symbolic.patch | [PATCH] Change rendering notification icon to process-working-symbolic | Noah Davis <noahadvs@gmail.com> | no | 2025-04-22 | ||
| upstream_7b731475_VideoPlatform-Remove-setRecording-store-recorded-time.patch | [PATCH] VideoPlatform: Remove setRecording, store recorded time setRecording is obsolete now that we have setRecordingState. We store the recorded time now since we may want to access the recorded time while rendering or finished. |
Noah Davis <noahadvs@gmail.com> | no | 2025-04-22 | ||
| relax-interplasma-versioned-deps.patch | no | |||||
| upstream_b63c01d0_videoplatform-Add-RecordingState-property.patch | [PATCH] videoplatform: Add RecordingState property This indicates what state the video platform is in currently and allows other bits of the UI to react accordingly. Most importantly this adds a "Rendering" state that corresponds to KPipeWire's Rendering state, which indicates we're finishing the recording process but haven't fully finished yet. |
Arjen Hiemstra <ahiemstra@heimr.nl> | no | 2024-10-08 | ||
| upstream_29d52422_Fix-export-notifications-keeping-spectacle-from-closing.patch | [PATCH] Fix export notifications keeping spectacle from closing They won't emit KNotification::closed to let spectacle exit if they just expire, but calling KNotification::close removes them from history. Neither are desirable. I found out that letting spectacle close anyway when the last notification should have expired keeps the notifications in history. We use a QTimer as an additional way to let spectacle exit now. |
Noah Davis <noahadvs@gmail.com> | no | 2025-05-06 | ||
| upstream_98eb3ba7_Use-transient-notifications-for-recording-rendering-notifications.patch | [PATCH] Use transient notifications for recording/rendering notifications Transient notifications are supposed to be kept out of history. |
Noah Davis <noahadvs@gmail.com> | no | 2025-05-06 | ||
| upstream_d5541b1e_Close-recording-rendering-notifications-when-changing-recording-states.patch | [PATCH] Close recording/rendering notifications when changing recording states | Noah Davis <noahadvs@gmail.com> | no | 2025-05-06 | ||
| upstream_b437ca39_ImagePlatformKWin-Clip-sub-image-ROI-for-combined-image-to-prevent-OpenCV-assert-crash.patch | [PATCH] ImagePlatformKWin: Clip sub image ROI for combined image to prevent OpenCV assert crash The possibility should be completely prevented now. |
Noah Davis <noahadvs@gmail.com> | no | upstream | 2025-05-09 | |
| upstream_64e46b80_Workaround-QWindow-screen-being-wrong-with-some-fractional-DPR-screen-layout-combinations.patch | [PATCH] Workaround QWindow::screen being wrong with some fractional DPR screen layout combinations Caused the selection editor to select on the wrong screen. (cherry picked from commit f407154111eb6fd3f8c0cc3d80eb3e6c0a241be7) |
Noah Davis <noahadvs@gmail.com> | no | upstream | 2025-05-30 |