gourmet crashed with ProgrammingError in _handle_dbapi_exception()

Bug #357242 reported by DSHR
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gourmet (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: gourmet

Gourmet does not start on jaunty in german local environment.

Switching to LANG=C I get:

sqlalchemy.exceptions.ProgrammingError: (ProgrammingError) You must not use 8-bit bytestrings unless you use a text_factory that can interpret 8-bit bytestrings (like text_factory = str). It is highly recommended that you instead just switch your application to Unicode strings. u'SELECT keylookup.id, keylookup.word, keylookup.item, keylookup.ingkey, keylookup.count \nFROM keylookup \nWHERE keylookup.ingkey = ? AND keylookup.item = ?' ['pepper, jalape\xc3\xb1o', 'jalape\xc3\xb1o pepper']

Removing .gourmet unfortunately seems not to help ...

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/gourmet
InterpreterPath: /usr/bin/python2.6
Package: gourmet 0.14.5-2ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/gourmet
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=C
PythonArgs: ['/usr/bin/gourmet']
SourcePackage: gourmet
Title: gourmet crashed with ProgrammingError in _handle_dbapi_exception()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin boso6a cdrom dialout lpadmin plugdev sambashare sudo

Revision history for this message
DSHR (s-heuer) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Is this still a problem for you with 0.14.5-2ubuntu1.1 in Jaunty or 0.14.5-2ubuntu2 in Karmic?

visibility: private → public
Changed in gourmet (Ubuntu):
assignee: nobody → Jamie Strandboge (jdstrand)
status: New → Incomplete
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in gourmet (Ubuntu):
assignee: Jamie Strandboge (jdstrand) → nobody
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.