jdrch

Were there any special settings you had to use in Clonezilla to get this to work? I'm trying to migrate to a larger SSD on my OpenIndiana Hipster machine and this post is literally my only hope that that might work. UDPATE Clonezilla definitely does not work with OpenIndiana Hipster.

Were there any special settings you had to use in Clonezilla to get this to work? I'm trying to migrate to a larger SSD on my OpenIndiana Hipster machine and this post is literally my only hope that that might work.

Update: console mode fixed the issue. Thanks so much for your assistance and for developing this wonderful tool!

http://luckybackup.sourceforge.net/manual.html#cronItTroubleshoot (paragraph No.2) Thanks! To make it easier for myself I just decided to run luckyBackup in console mode instead, which, according to the documentation, will eliminate the need for display permissions anyway. Also, I've done all my configuration in GUI superuser mode, which I hope helps.

I'm trying to get luckyBackup to run in silent mode on Debian Buster in KDE. Crontab entry is: 0 7 * * * env DISPLAY=:0 /usr/bin/luckybackup --silent --skip-critical /root/.luckyBackup/profiles But the default-LastCronLog.log file in /root/.luckyBackup/logs says: No protocol specified qt.qpa.screen: QXcbConnection: Could not connect to display :0 Could not connect to any X display. Any ideas? Also, where is the crontab that luckyBackup writes to located?

I'm requesting that the export entry function be returned to its rightful place in the entry right-click menu. All actions that can be performed on an entry as a whole should be accessible from a right-click (not saying that should be the only way to access them.) The current method of hiding (some of) them (including Export) behing the Entry top level menue is confusing and non-intuitive.

There's a new KeePass plugin that may solve this problem as far as one-way, Parent -> Multiple Children database change propagation is concerned. Check out KeePassSubsetExport, which allows multiple Child databases with unique, separate passwords, names, folder structures, and paths to be automatically exported on each Parent database save operation. Also, because the settings for the plugin live within the KeePass database itself, if the database is synced across machines with the same folder structure...

I would certainly like to see such a plugin, but its not something I can do. Thanks for your efforts so far :) It's arguable that in many cases where "normal user"/"average person" databases are administered by a technically adept admin, the other (read: average/normal) users never edit their databases anyway. Ergo, Child -> Parent sync might not have as strong a use case as we might think (This is actually sad from an infosec perspective, but that's a separate discussion.)