https://bugs.kde.org/show_bug.cgi?id=518187
Bug ID: 518187
Summary: Marknote eats data on switch between focus mode.
Classification: Applications
Product: Marknote
Version First 1.5.2
Reported In:
Platform: Bazzite
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: General
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected], [email protected]
Target Milestone: ---
SUMMARY
Marknote shortly after opening my decently filled markdown file will quickly
erase data upon each new autosave.
STEPS TO REPRODUCE
1. Open a large markdown file, maybe 8KB or so, containing many triple
backticks, lists, headers, etc, you name it.
2. Open Marknote to the file or folder (beware: Marknote immediately opens
files upon entering a folder).
3. Find a section to observe the missing data (you should see blank lines).
4. Toggle focus mode, editor mode, or both.
5. You may continue toggling this mode until the data is no longer coherent or
is sufficiently destroyed.
6. Observe that your data is now gone and the file has been shrunk and modified
on disk.
OBSERVED RESULT
Loss of data. Approximately 35% in my case.
EXPECTED RESULT
Regardless of visual or editing bugs there should be no modification of
unmodified data. Opening a file editor to view a file should in no case start
owning and modifying my files.
SOFTWARE/OS VERSIONS
Linux bazzite 6.17.7-ba25.fc43.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Jan 19
05:47:43 UTC 2026 x86_64 GNU/Linux
Marknote 1.5.2
ADDITIONAL INFORMATION
The file contains no credentials but still sensitive data so I will not be
sharing it.
I believe the following issues are related:
- modifies the content of a file on simple read
https://bugs.kde.org/show_bug.cgi?id=516824
- When opening a note, the last modified time is updated, even if the note is
not edited. https://bugs.kde.org/show_bug.cgi?id=514101
- Text formatting changes when changing which note is active and there's
corruption occurring. https://bugs.kde.org/show_bug.cgi?id=513811
On that note this issue has been in the program for multiple releases (1.3.0 to
1.5.1). A data corruption bug should be a complete show stopper. This displays
extreme negligence in the issue reviewing process.
Finally in addition to all that has been said and observed above I have checked
version 1.5.1 `ea438668ce8bb24f1b0d6716598d4f9fb23669a6` to head
`1ffa39b72c878793a3602cfbf89cbb9b1dd92061` and found no fixes.
--
You are receiving this mail because:
You are watching all bug changes.
