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 Desktop
Packages, which is subscribed to pygobject in Ubuntu.
https://bugs.launchpad.net/bugs/1050358
Title:
emesene crashed with SIGSEGV in tupledealloc.24592()
Status in “emesene” package in Ubuntu:
Confirmed
Status in “pygobject” package in Ubuntu:
Confirmed
Status in “pygobject-2” package in Ubuntu:
Confirmed
Bug description:
When I try to connect to my msn account emesene crash
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: emesene 2.12.5+dfsg-1ubuntu2
ProcVersionSignature: Ubuntu 3.5.0-14.16-generic 3.5.3
Uname: Linux 3.5.0-14-generic x86_64
ApportVersion: 2.5.1-0ubuntu7
Architecture: amd64
CrashCounter: 1
Date: Thu Sep 13 13:12:08 2012
ExecutablePath: /usr/share/emesene/emesene/emesene
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/bin/emesene -s
SegvAnalysis:
Segfault happened at: 0x4b6058: mov 0x98(%r13),%eax
PC (0x004b6058) ok
source "0x98(%r13)" (0x00000098) not located in a known VMA region (needed
readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: emesene
StacktraceTop:
?? ()
?? ()
?? () from /usr/lib/python2.7/dist-packages/glib/_glib.so
?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: emesene crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to quantal on 2012-04-26 (139 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/emesene/+bug/1050358/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
