Data loss by running multiple instances
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
RedNotebook |
Fix Released
|
Medium
|
Jendrik Seipp | ||
Debian |
New
|
Undecided
|
Unassigned |
Bug Description
If Rednotebook is configured to automatically start at login ("[x] Load RedNotebook at system start" [de="RedNotebook beim Systemstart laden"]), multiple instances will run in subsequent sessions (likely caused by KDE's session management). Accordingly, two icons will be displayed in system tray area. However, this is likely to be hidden or overlooked.
If you don't realize this, at the end of your session that instance of RedNotebook which closes last will silently overwrite the whole journal. As multiple instances running on the same journal won't update each other and even don't notice updated yournal files (as kate would do, for instance), there is no warning at all. At worst, all of your editing work of the complete session might irrevocably be thrashed.
Therefore, RedNotebook should either generally refuse to operate in multiple instances on the same dataDir, or at least have a configuration option to prevent this behaviour.
checkForNewVers
closeToTray=1
cloudIgnoreList
cloudIncludeLis
cloudTabActive=0
dataDir=
dateTimeString=%A, %x %X
leftDividerPosi
mainFontSize=-1
mainFrameHeight=768
mainFrameMaximi
mainFrameWidth=1176
mainFrameX=125
mainFrameY=164
rightDividerPos
spellcheck=0
useWebkit=1
userDir=
weekNumbers=0
Thanks for reporting this. I have already begun working on this. You can find the work in the linked branch.