Thank you, Michael. Unfortunately, the stacktrace is still incomplete --
Although it looks like we are looping in pthread_mutex_lock (which calls
__pthread_lock, which may go into a spinloop), we still do not know
which e-d-s module initiated the call, nor when. Could you please
install e-d-s-dbgsym (in fact, please install all corresponding e-d-s
dbgsym packages, see below for a list of potential packages) )and repeat
the bt with a 'thread apply all bt full'?
This is still very weird... a loop at this point suggests something else
is broken at a basic level... or some structures are being overlaid.
E-D-S builds the following packages; some of them will be installed,
please install the corresponding dbgsym packages (and please adjust
version info as needed):
evolution-data-server
libcamel1.2-10
libebook1.2-9
libecal1.2-7
libedata-book1.2-2
libedata-cal1.2-6
libedataserver1.2-9
libedataserverui1.2-8
libegroupwise1.2-13
libexchange-storage1.2-3
libgdata-google1.2-1
libgdata1.2-1
** Changed in: evolution-data-server (Ubuntu)
Status: New => Incomplete
--
Hangs on login and uses 100% cpu
https://bugs.launchpad.net/bugs/151536
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
