Debian Patches

Status for plasma-workspace/4:6.3.6-2

Patch Description Author Forwarded Bugs Origin Last update
fix-incorrect-libplasma-dependency-version.patch no
relax-interplasma-versioned-deps.patch no
upstream_e4e0dee5_libkmpris-allow-MultiplexerModel-to-show-actual-player-name.patch [PATCH] libkmpris: allow MultiplexerModel to show actual player name
The lock screen needs it to show the actual player name instead of
"Choose player automatically"		 Fushan Wen <qydwhotmail@gmail.com> no 2025-03-24
upstream_4f9b1a69_Fix-Scroll-Wheel-issue-in-AllApps-submenu-of-Application-Dashboard.patch [PATCH] Fix Scroll Wheel issue in AllApps submenu of Application Dashboard

Scroll with mouse wheel was problematic in AllApps subsection. It worked
partially, abruptly stopping when hovering over app icons, or just
during mouse wheel scrolling.

The problem is that QQuick WheelInterceptor::findwheelArea() never entered
into its if statement because there are 3 children elements of QML parent,
and their z axis values are 1, 0, 0 respectfully.		 Tomislav Pap <bad63r@gmail.com> no upstream 2025-03-24
upstream_f17c2546_applets-systemtray-Open-context-menu-on-click-when-ItemIsMenu.patch [PATCH] applets/systemtray: Open context menu on click when ItemIsMenu

As per StatusNotifierItem spec:

> The item only support the context menu, the visualization should
prefer showing the menu or sending ContextMenu() instead of Activate()		 Kai Uwe Broulik <kde@privat.broulik.de> no 2025-03-22
upstream_cf206f9d_applets-notifications-never-use-scientific-notation-for-large-numbers.patch [PATCH] applets/notifications: never use scientific notation for large numbers

Normal people don't know how to read it.		 Nate Graham <nate@kde.org> no upstream 2025-03-29
upstream_73875471_applets-appmenu-Fix-displaying-menu-of-the-previous-active-window.patch [PATCH] applets/appmenu: Fix displaying menu of the previous active window

We need to break the DBusMenuImporter::menuUpdated() signal connection
when the active window changes. Otherwise, it's possible that the
menuUpdated signal will be emitted and the menu will be marked as
available.		 Vlad Zahorodnii <vlad.zahorodnii@kde.org> no upstream 2025-04-18
upstream_5d008e00_applets-appmenu-Store-dbus-menu-importer-in-a-std-unique-ptr.patch [PATCH] applets/appmenu: Store dbus menu importer in a std::unique_ptr

The code is simpler this way.		 Vlad Zahorodnii <vlad.zahorodnii@kde.org> no 2025-04-23
upstream_fbb2e6d3_users-kcm-Fix-issue-in-sorting-user-list.patch [PATCH] users kcm: Fix issue in sorting user list
If two users are logged in, the sorting order is not stable, both should be sorted before the other

Use partition instead of sorting, since we only care about having moved logged in users up front.

Found by: Kamil Kaznowski		 Sune Vuorela <sune@vuorela.dk> no 2025-02-13
upstream_8e6b79da_containmentlayoutmanager-don-t-enter-edit-mode-without-activefocus.patch [PATCH] containmentlayoutmanager: don't enter edit mode without activefocus

ItemContainer enters edit mode on pressAndHold for desktop widgets not
set to immutable. This causes a problem with menus that open on press -
the container will not receive further mouse events that now go to the
menu, so it still considers itself pressed and unmoved the whole time,
and goes into edit mode after a while, exiting the menu. This makes
on-press menus in desktop widgets borderline unusable, and even if the
user manages to be quick enough to activate the desired entry during the
pressAndHold duration, it'll still enter edit mode unless the user also
does a full click on the applet afterward.

We can circumvent this particular case relatively easily by listening to
the container's activefocus changes - the popup opening does not cause
a focusOut event, but it does take activeFocus away from the container,
so if we stop the timer in that case, it works out as it should.



(cherry picked from commit 3d9dd7fe1a664b6b4f20523d6c4425eb57dc6b4c)		 Christoph Wolk <cwo.kde@posteo.net> no 2025-06-03
upstream_e2ae8f54_libtaskmanager-fix-move-to-activity-when-on-almost-all-activities.patch [PATCH] libtaskmanager: fix "move to activity" when on almost all activities

Using the task manager to move windows to other activities works in
most circumstances, but fails under one condition: when a window is
already on all activities except the one that is being moved to, the
window instead ends up on all activities, and has to be moved to that
activity again to be only on that workspace. This is usually a rare edge
case, but very commonly happens when using exactly two activities,
namely always when moving a window from one activity to the other.

This is the result of some unusual api implementation details of
the activity list for that window empty. Moving a window to a different
activity in libtaskmanager is done by first adding the window to the
activity list using the plasma wayland protocol. If the list on the kwin
side is now full, it'll flip it over into the empty list (i.e. all
activities). Next libtaskmanager tries to remove the other activities
from the list, this fails because the list is already empty (and kwin
doesn't handle this because "this use case is not important enough to
handle here").

Luckily enough, this use case is trivially easy to handle here, all we
need to do is remove existing activities first, then add the new one.
This will also briefly put it on all activities, but adding new
activities works (and puts it only on that activity), it's only
removing them that fails.



(cherry picked from commit 99f9dc95226719c2be53fd86a4a0a3bae88d0aa2)		 Christoph Wolk <cwo.kde@posteo.net> no upstream 2025-06-05
upstream_ab55c53e_applets-kicker-fix-filenames-containing-in-history.patch [PATCH] applets/kicker: fix filenames containing # in history
Kicker takes the resource name as provided by PlasmaActivities.Stats and
interprets it as an URL, setting the 'file' url scheme if necessary.
This fails when the filenames contain a '#' character, as QUrl will
interpret them as url fragments if not percent-encoded (which they are
not for local files, but are for remote urls). This makes display and
opening of such files fail in both Kicker and Kickoff.

Instead, we test whether it's an absolute path (the local history
entries are) and if so, use QUrl.fromLocalFile to get the correct url.
This is also what PlasmaActivities.Stats does in ResultSet (which is
what the Task Manager uses, so everything works there already, but we
want a real model here).



(cherry picked from commit c6c0a68416b5042032853a6f673bddbe475567b7)		 Christoph Wolk <cwo.kde@posteo.net> no upstream 2025-06-05
upstream_d286dce3_Klipper-Remove-local-Configure-Klipper-action.patch [PATCH] Klipper: Remove local Configure Klipper action
This action would cause the shortcuts configuration menu to show
both local and global shortcuts, which makes no sense due to
Klipper being a globally accessed application.

This action is only used in cases where Klipper will be it's own
application with a normal window, similar to applications like Dolphin,
Kate, etc.. But Klipper is never used this way.

Currently only place where you can use this action is the configuration
menu itself, where it does nothing, since the menu is already open.

So let's just remove it. This also makes sure users do not accidentally
select "Shortcut/Alternate" instead of "Global Shortcut/Alternate"
for their shortcuts. See the related bug for context.



(cherry picked from commit 1d3fe2ac0c0e640f0b66ec1e1d34f0e0196bbd7d)		 Akseli Lahtinen <akselmo@akselmo.dev> no upstream 2025-06-19
upstream_9abfdd26_kcm-users-refine-deleting-logged-in-user-UX.patch [PATCH] kcm/users: refine "deleting logged-in user" UX
Right now there are two problems:
1. Deleting a logged-in user shows no warning about this.
2. Asking to delete the files of a logged-in user fails silently
(AccountsService simply won't do it).

This commit solves both problems: now the user sees a warning dialog
when they try to delete another logged-in user, and it also prevents
them from trying to delete a logged-in user's files, instead redirecting
them to just delete the account but not the files.

To achieve this, I needed to change what the `loggedIn` property does,
because previously it was inaccurate, returning whether the queried user
is the currently logged-in user. Now it returns whether the quaried user
is logged in, and I added a new `isMe` property to hold whether the
queried user is the currently logged-in user.		 Nate Graham <nate@kde.org> no upstream 2025-03-14
upstream_c9ee2931_kcm-regionandlang-add-locale-C-to-mapping-and-always-set-LANG-and-LC-.patch [PATCH] kcm_regionandlang: add locale C to mapping and always set LANG and LC_*


Add locale C to glibc mappings so that locale C is actually saved to config file

Also set LC_* whenever LANG is set, this ensure LC_* are always up to date. In previous logic, LC_* can become out of sync if user change LANG to something else than changed it back.		 Han Young <hanyoung@protonmail.com> no upstream 2025-02-22
upstream_a83c4e5f_applets-devicenotifier-check-if-device-has-been-added-before.patch [PATCH] applets/devicenotifier: check if device has been added before

Skip device if applet already has device with similar udi		 Bohdan Onofriichuk <bogdan.onofriuchuk@gmail.com> no upstream 2025-05-05
upstream_2c27c9db_applets-notifications-don-t-allow-horizontal-scrolling.patch [PATCH] applets/notifications: don't allow horizontal scrolling
Notification bodies have their width constrained by the notification and
the horizontal scrollbar forced off, but they can still be scrolled with
a horizontal wheel, touchpad, or similiar. This is surprising and
pointless.

Instead explicitly set the contentWidth, which is otherwise ultimately
based on the underlying TextEdit (and that's the width it would have on
a single line without wrapping).		 Christoph Wolk <cwo.kde@posteo.net> no 2025-05-08
upstream_9e0939c1_Warn-user-about-full-storage-in-any-device-partition.patch [PATCH] Warn user about full storage in any device/partition
Currently, we only check for home and / partitions to be full
when warning user. With this commit we instead check for all
partitions / devices that are mounted and not read only.		 =?UTF-8?q?Niccol=C3=B2=20Venerandi?= <niccolo@venerandi.com> no 2025-03-24
upstream_6d12cde3_wallpapers-image-Fix-thumbnails-not-matching-output-size.patch [PATCH] wallpapers/image: Fix thumbnails not matching output size
The `Screen` is an attached property and it never changes, we need to
monitor screen size changes instead.



(cherry picked from commit d6436e077c05abd100d905aaa73222a48ca1695f)

7678dfa9 wallpapers/image: Fix thumbnails not matching output size
5f4d8bc8 Apply 1 suggestion(s) to 1 file(s)		 Vlad Zahorodnii <vlad.zahorodnii@kde.org> no upstream 2025-05-16
upstream_8845c001_shell-Osd-Fix-missing-RTL.patch [PATCH] shell/Osd: Fix missing RTL PlasmaCore.Dialog does not set LayoutMirroring for us, so we need to do it ourselves. Oliver Beard <olib141@outlook.com> no upstream 2025-05-09
upstream_142caad0_applets-notification-fix-fullRepresentation-only-widgets.patch [PATCH] applets/notification: fix fullRepresentation-only widgets
The fullRepresentation has a little efficiency trick: it unloads the
model while it is not expanded, so the ListView does not need to be
updated while it is not visible. In general this is fine, but it
interacts very badly with attempts to put the fullRepresentation
directly on the desktop (or in a very large panel) and the auto-closing
functionality of the notification applet. When the notification history
ever becomes empty, it tries to close the fullRepresentation by setting
expanded to false, which by itself does not do any harm either (the
fullRepresentation stays a fullRepresentation), but it does unload the
model, so the history never updates again (unless the user manually
resizes it to become too small for the fullRepresentation then back
again, which resets it to its proper expanded state).

Instead, we modify closePlasmoid() to only set expanded to false if the
widget is below either switchWidth or switchHeight.		 Christoph Wolk <cwo.kde@posteo.net> no upstream 2025-05-10
upstream_d4df9b5f_applets-systemmonitor-handle-null-faceController.patch [PATCH] applets/systemmonitor: handle null faceController
When initially adding a systemmonitor widget to a panel, faceController
can still be null, causing several TypeErrors.

Instead, use optional chaining and default values to prevent these
errors until the faceController is loaded.		 Christoph Wolk <cwo.kde@posteo.net> no 2025-03-25
upstream_b9bc83c6_applets-systemmonitor-skip-configure-button-on-sensorless-faces.patch [PATCH] applets/systemmonitor: skip configure button on sensorless faces

Some faces don't need sensors as they have their data included already,
namely Process Table and Application Table. The applet does not take
this into account and keeps showing the "Configure" button.

Instead, don't show that button if one of these faces is the current
face.



(cherry picked from commit 184e883786520d6a7494b4db69dad29d69ff63a6)		 Christoph Wolk <cwo.kde@posteo.net> no upstream 2025-05-17
upstream_45784326_libtaskmanager-show-Comment-for-launcher-icons-when-appropriate.patch [PATCH] libtaskmanager: show Comment for launcher icons when appropriate

Right now, launcher icons get a caption equal to the app's GenericName,
if one is set in the metadata. If not, it gets no caption.

This differs from what Kicker and Kickoff Manager do: a more complex
behavior to show the Comment if the app has no GenericName or if its
GenericName is equal to its Name. Let's replicate the same logic here.



(cherry picked from commit ae39f3219d6fc849fe8de0d1c165a572598082fe)		 Nate Graham <nate@kde.org> no upstream 2025-05-22
upstream_e9fd71d9_wallpapers-image-don-t-crash-when-removing-usr-share.patch [PATCH] wallpapers/image: don't crash when removing /usr/share
we delay addSourceModel when the source model is fully loaded,
but it might take a long time (ie adding /usr/share)

if then we remove it before it's done, we will have either an assert or a crash
in qconcatenatetablesmodel (depending if Qt asserts are turned on)

we can safely call addsourceModel immediately, so rowsInserted will be
forwarded as they come in

BUG:503593


(cherry picked from commit f584f1beb3aaafe36c328a761b8eea02b46f20c4)

f584f1be wallpapers/image: don't crash when removing /usr/share		 Marco Martin <notmart@gmail.com> no 2025-05-28
upstream_88911e82_shell-Rearrange-the-teardown-order.patch [PATCH] shell: Rearrange the teardown order
At the moment, the ShellCorona is destroyed after the QApplication object.
Destroying something after the application object can lead to
unexpected results because most of the code is written with an assumption
that the app object and the associated objects, e.g. the qpa, are still
valid when the cleanup code runs.

This change puts the ShellCorona on the stack so the destruction order
looks as follows:

- destroy ShellCorona
- destroy QApplication



(cherry picked from commit e2326d7f9e752eb18411ef4c0bcd53b8f34e02c6)		 Vlad Zahorodnii <vlad.zahorodnii@kde.org> no 2025-05-28
upstream_01978f58_Do-not-track-cache-partitions-with-freespacenotifier.patch [PATCH] Do not track cache partitions with freespacenotifier
BUG:504423


(cherry picked from commit f4a08099d0aae466f06f0094498cc593c8ce4532)

e033ef89 Do not track cache partitions with freespacenotifier
5203019a Apply 1 suggestion(s) to 1 file(s)		 =?UTF-8?q?Niccol=C3=B2=20Venerandi?= <niccolo@venerandi.com> no 2025-05-29
upstream_f1605df4_Do-not-show-logout-screen-when-in-lockscreen-screensaver.patch [PATCH] Do not show logout screen when in lockscreen / screensaver
BUG:504575


(cherry picked from commit ba7a8c16b7934fa23d3a44bb38667554e39996b7)		 =?UTF-8?q?Niccol=C3=B2=20Venerandi?= <niccolo@venerandi.com> no 2025-06-02
upstream_a4e153b3_kcms-feedback-remove-little-hover-icons.patch [PATCH] kcms/feedback: remove little hover icons
These icons have an unclear purpose since they have no text, and the
same icons are not repeated elsewhere in the KCM's UI to provide some
clue as to their meaning or purpose. They only appear on hover and
can't be accessed on touch at all; let's just remove them to prevent
user confusion.

The backend code providing icons in the model is preserved in case we
ever want to do something else with icons in the future.



(cherry picked from commit 3c277146c4ec44cde54988dcd6c70b17442ad5e9)		 Nate Graham <nate@kde.org> no upstream 2025-06-20
upstream_d1896f5a_applets-kicker-resolve-non-existing-files-to-their-url.patch [PATCH] applets/kicker: resolve non-existing files to their url
Kicker's PAStats-based favorites do some normalization to, among others,
resolve symlinked files to their resolved path to reduce duplicates.
However, if the file doesn't exist, it essentially just gives up. This
is a problem when trying to remove favorites that were deleted: while
the un-favoriting in PAStats succeeds, kicker can't remove it from its
own model because it can't identify the file by its url if it doesn't
exist. So removed favorites confusingly stick around until the next
plasmashell restart.

Instead, we take the base url in that case - as the entries already have
gone through the process, the url is their real url anyway.



(cherry picked from commit da244b8764cde5509598965f24804bbaa5e0939f)		 Christoph Wolk <cwo.kde@posteo.net> no upstream 2025-06-23
upstream_b2e80af5_Only-resize-width-to-fit-date-elements-if-they-are-visible.patch [PATCH] Only resize width to fit date elements if they are visible
BUG:505614		 =?UTF-8?q?Niccol=C3=B2=20Venerandi?= <niccolo@venerandi.com> no 2025-06-17
upstream_ec837446_Do-not-emit-OOM-notifications-on-systemd-services-reload.patch [PATCH] Do not emit OOM notifications on systemd services reload
When systemd services are reloaded, systemd emits all PropertiesChanged signals for all units.

Comparing with the original signals these have a null MainPID, so we can use that to identify them and not emit a notification.



(cherry picked from commit ce33b24d4f1b5711f7585b33822ab87f2f43af0b)

ce33b24d Do not emit OOM notifications on systemd services reload		 Antonio Rojas <arojas@archlinux.org> no upstream 2025-07-05

All known versions for source package 'plasma-workspace'

Links