On Tue, Jan 25, 2011 at 12:01:02PM -0000, Tomas Cassidy wrote: > Error when closing gourmet (maverick-proposed):
> Ignoring sqlalchemy problem > Traceback (most recent call last): > File "/usr/share/gourmet/gourmet/backends/db.py", line 223, in save > self.db.commit() > File "/usr/lib/python2.6/dist-packages/sqlalchemy/engine/threadlocal.py", > line 78, in commit > trans = self._connections.trans.pop(-1) > IndexError: pop from empty list This is the expected behavior; note that it says 'Ignoring sqlalchemy problem' at the top. Indeed, this is the *improved* behavior resulting from the second patch mentioned in the changelog - without that patch, this would be a crash rather than merely a backtrace message, and the crash also will happen mid-execution (not just at shutdown) due to autosave support. So I would call this a successful verification. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ [email protected] [email protected] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/618643 Title: gourmet crashed with TypeError in __nonzero__() -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
