*** This bug is a duplicate of bug 538140 ***
    https://bugs.launchpad.net/bugs/538140

The whole discussion seems to date back, but I get the same error as described 
above.
Trying to sync tomboy, I get the following error.   

[ERROR 17:58:06.973] Synchronization failed with the following exception: 
Unexpected character '<' at [2:0]
  at Hyena.Json.Tokenizer.UnexpectedCharacter (Char ch) [0x00000] in <filename 
unknown>:0 
  at Hyena.Json.Tokenizer.InnerScan () [0x00000] in <filename unknown>:0 
  at Hyena.Json.Tokenizer.Scan () [0x00000] in <filename unknown>:0 
  at Hyena.Json.Deserializer.CheckScan (TokenType expected, Boolean eofok) 
[0x00000] in <filename unknown>:0 
  at Hyena.Json.Deserializer.Deserialize () [0x00000] in <filename unknown>:0 
  at Tomboy.WebSync.Api.UserInfo.ParseJson (System.String jsonString) [0x00000] 
in <filename unknown>:0 
  at Tomboy.WebSync.Api.UserInfo.GetUser (System.String userUri, IWebConnection 
connection) [0x00000] in <filename unknown>:0 
  at Tomboy.WebSync.WebSyncServer.BeginSyncTransaction () [0x00000] in 
<filename unknown>:0 
  at Tomboy.Sync.SyncManager.SynchronizationThread () [0x00000] in <filename 
unknown>:0 

(Tomboy:24206): GLib-CRITICAL **: g_source_remove: assertion `tag > 0'
failed

I can't connect my problem with bug #538140. The output I get in the
console is the one pasted above (not the one in #538140) and in the GUI
error message the "Details" window is empty.

So this bug seems like the closest match to what I get. However, in my
case, removing .config/tomboy doesn't help.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/500975

Title:
  Synchronization failed with the following exception: Unexpected
  character '<' at [1:1]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntuone-servers/+bug/500975/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to