Entity-body was not a well-formed JSON document when updating bug description

Looks similar to bug 331990, but I'd expect to get repeated failures if that was the case.

I've just hit this too.

As a workaround, add /+edit to the end of the bug url and you get a non-ajax form.

This one needs to get some attention. It's raising it's ugly head more often now. I'll try to look at it end of this week or first of next.

Maybe (just guessing from the cases where I've seen it) this is related to having non-ascii characters in the string?

I had the same problem trying to trim done the description in https://bugs.edge.launchpad.net/ubuntu/+bug/429420.

This also showed some issues with the inline editing of long descriptions:
- After enabling I had to scroll down to the place where I wanted to edit (I wanted to delete from the midth till the end)
- After done with editing I had to scroll up again to reach the confirm/cancel buttons again
After confirming the edit, the whole description got a red border and a spinning icon (waiting to finish the request). As it still wasn't finished a few seconds, I scrolled down again (don't know why) just to see a way to small error message at the bottom.

The confirm/cancel buttons should be at the bottom of the form as one usually adds/edits at the bottom of longer descriptions and that way a possible error message doesn't get displayed off-screen.

And please make the error message larger, I don't want to use a magnifier to read it.

Just in case you need more examples of this bug, I get this too when I try to edit the description of bug 435099

I have this bug too with the description of https://bugs.launchpad.net/gconjugo/+bug/435643

Please come up with a better interim solution than hand editing urls. Until the ajax form is reliable there should at the very least be a link the the form that works.

Another work around is that you can right click the edit icon and open in new window or new tab to edit the description.

Just happened to me again. And entering +edit page showed me another bug: bug 439449

Another one to add: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/440575
I used the ubuntu-bug tool to report that bug. Additionally, reloading the page does not fix it.

Just came to file a dup of this...

After some days working this out, I now realize intellectronica has already fixed this in lazr.restful but his fix is not in use in Launchpad. leonardr will take up the work of getting the correct revisions into the lazr.restful egg used by Launchpad, and I'm closing this bug as a dupe of the original inline editing non-ascii bug, which has intellectronica's fix.

So the fix should be applied during this 3.1.10 cycle, and hopefully, quite soon.