Most Frequently Reported Bugs in Trac

We have lots of tickets and lots of users, so it's not unlikely that sometimes a bug will be reported twice, or thrice, or … dozens of times for some!

Here's a short list of the issues with a pathologically high duplicate rate:

• #5028: TracError: Unsupported version control system "svn"
  search:'!TracError: Unsupported version control system "svn"'
  

This is not even a bug, rather an installation issue. The error means that for some reason, the Python bindings to the Subversion libraries couldn't be found or loaded. The TracSubversion page provides detailed troubleshooting information. In Trac 0.11, if this problem happens, it will only be reported as a warning for non-repository related pages. It's planned to improve the error message even further (#6796)

• #3446: Rate of database is locked errors is too high
  search:"OperationalError: database is locked"
  

This used to be a plague with the SQLite database backend, but it seems that things improved over time and this once #1 duplicate bug is less frequent those days. A more scary variant of #3446 is #4929, where the lock situation seems to persist and needs a server restart (rare).

• #4311: Attaching files won't work with Trac < 0.10.4 and Python 2.5
  search:"'cStringIO.StringO' object has no attribute 'len'"
  

This was a simple compatibility issue with Python 2.5, which was reported and fixed. It's surprising how people keep using old versions of the software and keep re-discovering the same bug over and over…