Bug 401124 - clipboard actions pop up cannot be disabled
Summary: clipboard actions pop up cannot be disabled
Status: RESOLVED WORKSFORME
Alias: None
Product: klipper
Classification: Applications
Component: general (show other bugs)
Version: 5.13.5
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-16 21:59 UTC by zeta
Modified: 2019-02-26 00:36 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description zeta 2018-11-16 21:59:56 UTC 
SUMMARY


STEPS TO REPRODUCE
1. copy url
2. choose disable
3. reboot
4. copy url


OBSERVED RESULT

clipboard actions pop up shows again

EXPECTED RESULT

clipboard actions pop should not show


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Debian testing
KDE Plasma Version: 4:5.13.5-1+b1
KDE Frameworks Version: I dont know
Qt Version: I dont know

ADDITIONAL INFORMATION
Comment 1 george fb 2019-01-26 13:24:48 UTC 
Had the same behavior on Solus.
Deleting the ~/.config/klipperrc file fixed it for me.
Comment 2 zeta 2019-02-06 22:48:55 UTC 
This is no longer happening to me. This are my current versions:

Operating System: Debian GNU/Linux 
KDE Plasma Version: 5.14.5
Qt Version: 5.11.3
KDE Frameworks Version: 5.54.0
Kernel Version: 4.19.0-1-amd64

It would be nice to know what caused it.

George, what are your versions?
Comment 3 george fb 2019-02-07 02:14:47 UTC 
KDE Plasma Version: 5.14.5
Qt Version: 5.11.2
KDE Frameworks Version: 5.54.0
Kernel Version: 4.20.2-107.current
Comment 4 Christoph Feck 2019-02-22 17:47:22 UTC 
Can we close this ticket?
Comment 5 zeta 2019-02-26 00:36:48 UTC 
I guess so.

I have noticed that many bugs in KDE get resolved by deleting the config. It would be nice to gain some insight on why and prevent it from happening, because it's not good for the userbase (you can spend a LOT of time configuring KDE)

Anyway, only a developer can know that.

From my user perspective, the bug is fixed.

Ill put it to WORKSFORME, feel free to change to FIXED if you want