Thanks for the pointer Alex--I wasn't sure what the problem was--but I do know databases.
I compared the old database to a new one on a clean install. Apparently it's not just sqlite2 vs sqlite3--there's also a table used by the new version that must be created. I have a quick work-around below--but the real solution would probably for the gnome-rdp people to detect the database version and perform an update from within gnome-rdp. Workaround: Make sure gnome-rdp is closed. Open up a terminal and run the following commands: killall gnome-rdp.exe mv .gnome-rdp.db .gnome-rdp-backup.db sqlite .gnome-rdp-backup.db .dump | sqlite3 .gnome-rdp.db sqlite3 .gnome-rdp.db "CREATE TABLE appOptions (name VARCHAR(300) PRIMARY KEY, value VARCHAR(300));" An explanation: The first line will make sure gnome-rdp is not running. The next line moves the database named '.gnome-rdp.db' to '.gnome-rdp- backup.db' because we need a backup in case there's something I missed, so we can restore it later. The third line tells the old sqlite 2.x to open the backup database and dump out it's contents--then pipe it into the new sqlite3 database. The last line tells sqlite3 to create a table called appOptions in the database. This is apparently required by the newer version of gnome- rdp. -- Error:file is encrypted or is not a database https://bugs.launchpad.net/bugs/314777 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
