Thanks, mvo and Elias, for the bug report (and, of course, we are sorry
it took us that long to get to it).
Unfortunately, the backtrace is incomplete -- there is a suggestion we
are looping trying to acquire a lock, but no real data on who is doing
that. Could you please repeat it with debug symbols for (at least)
libglib and e-d-s?
Question: was e-d-s already running on login (in other words, did you
log out Gnome and log in again)? Does it happen when you log out, or
only during login? Is Evo itself auto-started on login?
** Changed in: evolution-data-server (Ubuntu)
Importance: Undecided => Medium
Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
