Bug 408989 - klipper should not record selection changes to notification history
Summary: klipper should not record selection changes to notification history
Status: RESOLVED FIXED
Alias: None
Product: klipper
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: 5.16.1
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-21 12:14 UTC by Till Schäfer
Modified: 2024-06-10 19:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In: 5.16.3
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Till Schäfer 2019-06-21 12:14:04 UTC
Klipper currently records all change notifications (i.e., using the actions "Next/Previous History Item") to the notification history. This should not be the case, as the Klipper content could be easily looked up in Klipper itself. Furthermore, this behavior contradicts the "clear history" feature of Klipper. This is problematic, since privacy sensetive informations may still reside in the notification history after clearing the Klipper history.
Comment 1 Kai Uwe Broulik 2019-07-04 13:21:11 UTC
Git commit 120aed57ced1530d85e4d522cfb3697fbce605fc by Kai Uwe Broulik.
Committed on 04/07/2019 at 13:19.
Pushed by broulik into branch 'Plasma/5.16'.

Keep Klipper notifications out of notification history

This makes Klipper identify as org.kde.klipper to the notification service even when running inside of Plasma and installs a rule
to disable it from history by default.
FIXED-IN: 5.16.3

Differential Revision: https://phabricator.kde.org/D21963

M  +2    -0    klipper/klipper.cpp
M  +4    -0    libnotificationmanager/plasmanotifyrc

https://commits.kde.org/plasma-workspace/120aed57ced1530d85e4d522cfb3697fbce605fc