After emerging and starting gnome-rdp-0.3.0.5 I get the following message on my console: Unhandled Exception: Mono.Data.Sqlite.SqliteException: SQLite error no such table: session at Mono.Data.Sqlite.SQLite3.Prepare (Mono.Data.Sqlite.SqliteConnection cnn, System.String strSql, Mono.Data.Sqlite.SqliteStatement previous, UInt32 timeoutMS, System.String& strRemain) [0x00000] in <filename unknown>:0 at Mono.Data.Sqlite.SqliteCommand.BuildNextCommand () [0x00000] in <filename unknown>:0 ~/.gnome-rdp.db was created at first lunch. Doing "file ~/.gnome-rdp.db" results in .gnome-rdp.db: empty ls -la shows the following: -rw-r--r-- 1 user group 0 Feb 2 01:42 .gnome-rdp.db So it looks like there is a mistake in creating the database-file Creating the db-file with sqlitebrowser and creating the "session"-table with a field called "id" presents a new error, which tells that the field "protocol" is missing. In the offical Bugtracker of gnome-rdp on https://bugs.launchpad.net/ubuntu/+source/gnome-rdp/ I could not find a related bug-report. I am running gentoo with arch ~x86 revdep-rebuild does not show any open dependencies so I think the mistake is located in (build of) gnome-rdp. I hope someone can fix it :-) Greetings Malte PS.: Installing the old version 0.2.3-r1, creating the db (and entering a connection) and upgrading to 0.3.0.5 starts gnome-rdp but it does not show the Connection created before an also does not allow to add a new connection.
Thanks for the detailed bugreport! I did not have the problem as I updated from 0.2* and did not use the database... I'll probably ask upstream as we do not have any specific patch on sqlite support in this version, and it seems to at least partially work
With 0.3.5, old ~/.gnome-rdp.db seems not used. All my previous connections are not displayed and new ones are stored in .conf plain files in ~/.config/GnomeRDP. I don't know if there's a way to use or migrate previous sqlite database.
(In reply to comment #2) > I don't know if there's a way to use or migrate previous sqlite database. Apparently not. I have added a new version to tree which fixes the crash at startup with "legacy sqlite DB". So you will have to manually migrate settings, but at least this version works OK Thanks for the report!
