I restored my notes folder from backup (thankyou simple backup!), and attempted to re-sync, got an error, killed tomboy and ran from terminal, got the following output after manually kicking off a sync. Perhaps it is related:
tim@atom:~$ tomboy
[INFO 21:16:16.365] Initializing Mono.Addins
[ERROR 21:16:28.442] Caught exception. Message: The remote server returned an error: (503) Service Temporarily Unavailable.
[ERROR 21:16:28.447] Stack trace for previous exception: at System.Net.HttpWebRequest.CheckFinalStatus (System.Net.WebAsyncResult result) [0x00000] in <filename unknown>:0
at System.Net.HttpWebRequest.SetResponseData (System.Net.WebConnectionData data) [0x00000] in <filename unknown>:0
[ERROR 21:16:28.450] Rest of stack trace for above exception: at System.Environment.get_StackTrace()
at Tomboy.WebSync.Api.OAuth.MakeWebRequest(RequestMethod method, System.String url, System.Collections.Generic.List`1 parameters, System.String postData)
at Tomboy.WebSync.Api.OAuth.WebRequest(RequestMethod method, System.String url, System.String postData)
at Tomboy.WebSync.Api.OAuth.Get(System.String uri, IDictionary`2 queryParameters)
at Tomboy.WebSync.Api.RootInfo.GetRoot(System.String rootUri, IWebConnection connection)
at Tomboy.WebSync.WebSyncServer.BeginSyncTransaction()
at Tomboy.Sync.SyncManager.SynchronizationThread()
at System.Threading.Thread.StartInternal()
[ERROR 21:16:28.451] Synchronization failed with the following exception: The remote server returned an error: (503) Service Temporarily Unavailable.
at System.Net.HttpWebRequest.CheckFinalStatus (System.Net.WebAsyncResult result) [0x00000] in <filename unknown>:0
at System.Net.HttpWebRequest.SetResponseData (System.Net.WebConnectionData data) [0x00000] in <filename unknown>:0
Looks like the ubuntu one server has gone walkies. I'm guessing either that triggers this horrific bug, or something the server did before it went down completely triggered the bug. Either way, this is still a really nasty data loss bug. Such a shame, because generally I <3 tomboy. I seem to be having a bad time with OSS recently.
I restored my notes folder from backup (thankyou simple backup!), and attempted to re-sync, got an error, killed tomboy and ran from terminal, got the following output after manually kicking off a sync. Perhaps it is related:
tim@atom:~$ tomboy Net.HttpWebRequ est.CheckFinalS tatus (System. Net.WebAsyncRes ult result) [0x00000] in <filename unknown>:0 Net.HttpWebRequ est.SetResponse Data (System. Net.WebConnecti onData data) [0x00000] in <filename unknown>:0 Environment. get_StackTrace( ) WebSync. Api.OAuth. MakeWebRequest( RequestMethod method, System.String url, System. Collections. Generic. List`1 parameters, System.String postData) WebSync. Api.OAuth. WebRequest( RequestMethod method, System.String url, System.String postData) WebSync. Api.OAuth. Get(System. String uri, IDictionary`2 queryParameters) WebSync. Api.RootInfo. GetRoot( System. String rootUri, IWebConnection connection) WebSync. WebSyncServer. BeginSyncTransa ction() Sync.SyncManage r.Synchronizati onThread( ) Threading. Thread. StartInternal( ) Net.HttpWebRequ est.CheckFinalS tatus (System. Net.WebAsyncRes ult result) [0x00000] in <filename unknown>:0 Net.HttpWebRequ est.SetResponse Data (System. Net.WebConnecti onData data) [0x00000] in <filename unknown>:0
[INFO 21:16:16.365] Initializing Mono.Addins
[ERROR 21:16:28.442] Caught exception. Message: The remote server returned an error: (503) Service Temporarily Unavailable.
[ERROR 21:16:28.447] Stack trace for previous exception: at System.
at System.
[ERROR 21:16:28.450] Rest of stack trace for above exception: at System.
at Tomboy.
at Tomboy.
at Tomboy.
at Tomboy.
at Tomboy.
at Tomboy.
at System.
[ERROR 21:16:28.451] Synchronization failed with the following exception: The remote server returned an error: (503) Service Temporarily Unavailable.
at System.
at System.
(Tomboy:4272): GLib-CRITICAL **: g_source_remove: assertion `tag > 0' failed
Looks like the ubuntu one server has gone walkies. I'm guessing either that triggers this horrific bug, or something the server did before it went down completely triggered the bug. Either way, this is still a really nasty data loss bug. Such a shame, because generally I <3 tomboy. I seem to be having a bad time with OSS recently.