GNOME Bugzilla – Bug 583007
vcard import into ldap -- freeze
Last modified: 2018-12-12 14:49:24 UTC
Steps to reproduce: Importing a vcard file into an LDAP address book will freeze evolution and CPU goes to 100%. LDAP contact search works. Stack trace: The last few lines of (CAMEL_DEBUG=all evolution >& evo.log) show: (evolution:9453): libebook-WARNING **: invalid escape, passing it through (evolution:9453): libebook-WARNING **: invalid escape, passing it through (evolution:9453): libebook-WARNING **: invalid escape, passing it through and two or three contacts will successfully show up in LDAP. The program doesn't actually crash, so there's no crash info here. Other information: vcard from Gmail. Evolution 2.26.1 OpenLDAP 2.4.15 Ubuntu Jaunty - Linux yonas-laptop 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:57:59 UTC 2009 i686 GNU/Linux
Please start evolution and evolution-data-server in separate terminals under gdb, when it hangs do ctrl+c and then 't a a bt' and paste the traces of both terminals here. see http://live.gnome.org/GettingTraces/Details#gdb-not-yet-running for details about how to do this
How do I start them separately in Ubuntu Jaunty? I don't see evolution-data-server as a program.
Created attachment 134846 [details] `gdb evolution` + 't a a bt'
Comment on attachment 134846 [details] `gdb evolution` + 't a a bt' evolution + data-server (NOT SEPARATE)
You should be able to start evolution-data-server from usr/lib/evolution-data-server/evolution-data-server-2.26 Can you please provide the traces of eds now, it could be possible that eds is crashing and due to which evolution hangs. TIA
I'm creating the log file right now, but I noticed evolution will not freeze when running evolution-data-server separately as root.
Created attachment 137271 [details] GDB - EDS GDB of Evolution Data Server
Created attachment 137272 [details] GDB - Evolution GDB of Evolution
Yonas, are you running evolution as root ? Because eds should be started in same user where you will run evolution. Attached traces in comment#7 point towards libxml related problem though it can be on evolution side also.
Akhil, I'm not running eds as root, but I noticed that when I do run it as root, the problem doesn't occur.
Why would running eds as root solve the problem, though? My guess is that it has to do with permissions and OpenLDAP.
Another interesting thing, the bug still shows up with: sudo /usr/lib/evolution/evolution-data-server-2.26 but does not show up with: su /usr/lib/evolution/evolution-data-server-2.26 ------------------------ I think when eds is run via 'sudo', it does not connect to the non-root user's evolution process, because `evolution --force-shutdown` will not kill eds.
Is anyone going to look at this?
Thanks for a bug report. I'm closing this as obsolete, but feel free to reopen or comment in case you can reproduce with the current 3.30.x stable series.