The crash happens occasionally on random pages. Upon page reshresh bug vanishes, but it appear on a different page some time later. I.e. it is bohrbug. Running Trac under modwsgi in daemon mode and user trac. I am reporting only two cases that happened during the timespan of aproximately 15 minutes of active use. https://trac.somesite.com/changeset/13307 https://trac.somesite.com/browser/trunk/lib/Job.php 2010-05-13 09:05:17,697 Trac[main] DEBUG: Dispatching <Request "GET u'/browser/trunk/lib/Job.php'"> 2010-05-13 09:05:19,538 Trac[main] ERROR: Internal Server Error: Traceback (most recent call last): File "/usr/lib/python2.5/site-packages/trac/web/main.py", line 450, in _dispatch_request dispatcher.dispatch(req) File "/usr/lib/python2.5/site-packages/trac/web/main.py", line 206, in dispatch resp = chosen_handler.process_request(req) File "/usr/lib/python2.5/site-packages/trac/versioncontrol/web_ui/changeset.py", line 321, in process_request self._render_html(req, repos, chgset, restricted, xhr, data) File "/usr/lib/python2.5/site-packages/trac/versioncontrol/web_ui/changeset.py", line 544, in _render_html for old_node, new_node, kind, change in get_changes(): File "/usr/lib/python2.5/site-packages/trac/versioncontrol/web_ui/changeset.py", line 362, in get_changes for npath, kind, change, opath, orev in chgset.get_changes(): File "/usr/lib/python2.5/site-packages/trac/versioncontrol/cache.py", line 363, in get_changes "ORDER BY path", (str(self.rev),)) File "/usr/lib/python2.5/site-packages/trac/db/util.py", line 64, in execute return self.cursor.execute(sql_escape_percent(sql), args) File "/usr/lib/python2.5/site-packages/trac/db/sqlite_backend.py", line 81, in execute self.rows = PyFormatCursor.fetchall(self) SystemError: ../Objects/tupleobject.c:118: bad argument to internal function 2010-05-13 09:05:19,700 Trac[session] DEBUG: Retrieving session for ID u'daim' 2010-05-13 09:05:19,702 Trac[perm] DEBUG: No policy allowed dima performing EMAIL_VIEW on None 2010-05-13 09:05:20,501 Trac[chrome] DEBUG: Prepare chrome data for request 2010-05-13 09:05:20,534 Trac[perm] DEBUG: No policy allowed dima performing TRAC_ADMIN on None 2010-05-13 09:05:20,785 Trac[perm] DEBUG: No policy allowed dima performing PERMISSION_GRANT on None 2010-05-13 09:05:20,861 Trac[perm] DEBUG: No policy allowed dima performing PERMISSION_REVOKE on None 2010-05-13 09:05:20,871 Trac[perm] DEBUG: No policy allowed dima performing TICKET_ADMIN on None 2010-05-13 09:05:20,872 Trac[perm] DEBUG: No policy allowed dima performing BUILD_ADMIN on None 2010-05-13 09:05:20,873 Trac[perm] DEBUG: No policy allowed dima performing BUILD_MODIFY on None 2010-05-13 09:05:20,880 Trac[browser] DEBUG: Rendering preview of node Job.php@13302 with mime-type text/x-php; charset=UTF-8 2010-05-13 09:05:20,881 Trac[api] DEBUG: Trying to render HTML preview using PygmentsRenderer [lineno]
The report at http://bugs.debian.org/581626 looks like it's a crash in the python interpreter due to something gone awry in sqlite. the PyFormatCursor referenced in the initial bug report inherits from pysqlite2.dbapi2.Cursor: http://www.edgewall.org/docs/tags-trac-0.11.7/epydoc/trac.db.sqlite_backend.PyFormatCursor-class.html And the crash in internal C code appears to be within PyTuple_SetItem (perhaps invoked during pysqlite2.dbapi2.Cursor.fetchall()): http://www.etsimo.uniovi.es/python/dev/src/c/html/tupleobject_8c.html#a14 At any rate, i suspect this bug should be reassigned to either python2.5 or to python-pysqlite2. Are you still able to reproduce this error?
The report at http://bugs.debian.org/581626 looks like it's a crash in the python interpreter due to something gone awry in sqlite. the PyFormatCursor referenced in the initial bug report inherits from pysqlite2.dbapi2.Cursor: http://www.edgewall.org/docs/tags-trac-0.11.7/epydoc/trac.db.sqlite_backend.PyFormatCursor-class.html And the crash in internal C code appears to be within PyTuple_SetItem (perhaps invoked during pysqlite2.dbapi2.Cursor.fetchall()): http://www.etsimo.uniovi.es/python/dev/src/c/html/tupleobject_8c.html#a14 At any rate, i suspect this bug should be reassigned to either python2.5 or to python-pysqlite2. Are you still able to reproduce this error?
No. I am using Trac 0.12 in custom virtualenv installation that's independent of Debian libraries. Even though Martin does a great job in maintaining Trac packages, changing something in Debian requires too much pain, so I decided not to waste time anymore.
No. I am using Trac 0.12 in custom virtualenv installation that's independent of Debian libraries. Even though Martin does a great job in maintaining Trac packages, changing something in Debian requires too much pain, so I decided not to waste time anymore.
No. I am using Trac 0.12 in custom virtualenv installation that's independent of Debian libraries. Even though Martin does a great job in maintaining Trac packages, changing something in Debian requires too much pain, so I decided not to waste time anymore.
Dear submitter, as the package trac has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/948052 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org. Debian distribution maintenance software pp. Scott Kitterman (the ftpmaster behind the curtain)