I reported a related crash in bug#1069163. Checking today I find the
same behavior reported there; no mention of tupledealloc in the
stacktrace.
What is new is a stacktrace reported when I start emesene from a
terminal, which I didn't see before it crashed originally. Now it says:
~$ emesene
Exception in thread Thread-3:
Traceback (most recent call last):
File "/usr/lib/python2.7/threading.py", line 552, in __bootstrap_inner
self.run()
File "/usr/share/emesene/emesene/e3/base/Logger.py", line 881, in run
self.logger = Logger(self.path, self.db_name)
File "/usr/share/emesene/emesene/e3/base/Logger.py", line 363, in __init__
self._load_events()
File "/usr/share/emesene/emesene/e3/base/Logger.py", line 395, in _load_events
self.execute(Logger.SELECT_EVENTS)
File "/usr/share/emesene/emesene/e3/base/Logger.py", line 597, in execute
self.cursor.execute(query, args)
OperationalError: no such table: d_event
Segmentation fault (core dumped)
Hope that helps, if only to establish that the two reports are or are not
related!
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1050358
Title:
emesene crashed with SIGSEGV in tupledealloc.24592()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emesene/+bug/1050358/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
