OperationalError: Could not decode to UTF-8 column 'newvalue' with text

[jb@…]

Hello,

i have create a new trac site (Trac 0.10.3) and backup (with hotcopy) my old trac database. I had Trac 0.9.pre before.

Now, I have convert the database to sqlite3. (sqlite trac2.db .dump | sqlite3 trac.db)

But now if i open the timeline site, I get the following decode error message:

---

Internal Error
Ticket changes event provider (TicketModule) failed:

OperationalError: Could not decode to UTF-8 column 'newvalue' with text '(In [13269]) L�schrountine fixes #2005'

---

I have test it with the newest trac Version. I get the same error.

Is it a bug, or anybody know a fix for this?

Thanks!

[Christian Boos]

The text:

'(In [13269]) L�schrountine fixes #2005'

is a ticket comment added by the trac-post-commit-hook, which had encoding issues in 0.9.x and early 0.10.x versions of Trac. More specifically, it took the changeset message verbatim, in whatever encoding it was given to the script.

More recent hooks (don't forget to update it btw, always take it from the contrib folder matching the Trac version you're using) don't have this problem as they fetch the changeset directly from the repository.

Now, for the data already in your database, you're a bit out of luck, as Trac can't cope with that badly encoded data. You need to fix the database itself. For example, just dump the db again (sqlite3 trac.db .dump) and use an editor which will show you the encoding issues that you can fix manually, or maybe with a clever use of recode (see its ​info page).

Finally, I'd strongly advise you to upgrade to Trac 0.10.5, as this is the latest stable version and numerous issues have been fixed since 0.10.3.