| Summary: | note can create only one unique sticky note | ||
|---|---|---|---|
| Product: | [Unmaintained] kdeplasma-addons | Reporter: | jms <jms.gentoo> |
| Component: | notes | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | kde, kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.17.0 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | plasma-org.kde.plasma.desktop-appletsrc | ||
|
Description
jms
2019-10-16 20:48:29 UTC
Can you make a screencast of this, please. I think OP's reporting a wishlist item for two notes to share the same file, rather than a bug. Upon close reading I think a bug is being reported here whereby all notes inappropriately share the same content. I can't reproduce the issue, though. (In reply to Nate Graham from comment #3) > Upon close reading I think a bug is being reported here whereby all notes > inappropriately share the same content. I can't reproduce the issue, though. yep that's it. my install is less than 3 weeks old all shiny and supposedly not yet messed up. only upgraded from previous framework/plasma/app. did not try to add multiple notes before upgrade. I ll try a screencast Please also attach your ~/.config/plasma-org.kde.plasma.desktop-appletsrc Created attachment 123260 [details]
plasma-org.kde.plasma.desktop-appletsrc
(In reply to Kai Uwe Broulik from comment #1) > Can you make a screencast of this, please. here you are https://youtu.be/SWXous-yY9Q do you need more infos? ok so there was a bug but not from note. for info this bug came from amd ryzen and how it set uuid. see for info https://www.reddit.com/r/kde/comments/cff976/are_keyboard_shortcuts_broken_on_51631/euvol55/ all uuid created are the same. doing a bios update (or microcode) will solve the problem. Works for me Wow, would I would never guessed that. We do use UUIDs in the note filename. Thanks for following up on that. |