Ubuntu
evolution package

LDAP Autocomplete freezing Evolution

Bug #175925 reported by Dave Smith
4
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Low
Basilio Kublik

Bug Description

Binary package hint: evolution

I'm having difficulties using LDAP as the Auto Complete. After running for a time, today it has been over 24 hours, the LDAP auto complete freezes Evolution while I'm addressing a new email, or replying to one.

The following shows on the console... I'm not entirely sure which pieces are relevant:

(evolution:15484): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed
fff
fff
fff
fff
fff

(evolution:15484): Gdk-CRITICAL **: gdk_window_get_origin: assertion `GDK_IS_WINDOW (window)' failed

(evolution:15484): libebook-WARNING **: corba exception._major = 2

(evolution:15484): libebook-WARNING **: EBookView: Exception while releasing BookView

(evolution:15484): libebook-WARNING **: corba exception._major = 2

(evolution:15484): libebook-WARNING **: EBookView: Exception while releasing BookView

(evolution:15484): libebook-WARNING **: corba exception._major = 2

(evolution:15484): libebook-WARNING **: EBookView: Exception while releasing BookView

(evolution:15484): libebook-WARNING **: corba exception._major = 2

(evolution:15484): libebook-WARNING **: EBookView: Exception while releasing BookView

index:0
index:0

(evolution:15484): libebook-WARNING **: corba exception._major = 2

(evolution:15484): libebook-WARNING **: EBookView: Exception while releasing BookView

(evolution:15484): libebook-WARNING **: e_book_dispose: Exception releasing remote book interface!

fff

I don't know what the fff statements mean, but they appear to coincide with temporary freezes of evolution and high CPU usage. I think the LDAP auto complete is no longer working after those ebook messages.

Any idea on how to progress to fix the problem? I'm using Ubuntu's 2.12.1 Evolution package.

Revision history for this message
Dave Smith (dave2006) wrote :

Wait, autocomplete did resume operation on a new message. Does the above say anything about Auto complete freezing evolution??

Revision history for this message
Basilio Kublik (sourcercito) wrote :

Hi Dave
i wasn't able to reproduce this issue, does this also happen to you with a new user account, and configure evolution with same settings you have in your preset user account.

Thanks in advance.

Changed in evolution:
assignee: nobody → sourcercito
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Iulian Udrea (iulian) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem. Also please try to reproduce this bug with the latest version of Evolution. If you still get this, please reopen. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New".

Thank you.

Changed in evolution:
status: Incomplete → Invalid
Revision history for this message
Pete Goodall (pgoodall) wrote :

I am requesting you re-open this bug. I'm currently using evolution-2.21.92-0ubuntu1 on an up-to-date Ubuntu Hardy system, and this bug is rendering Evolution useless. Hopefully I can supply you with sufficient information.

I have an LDAP address book source configured and have autocompletion set to pull from this data source. Auto-completion works just fine when I start typing a name, but if I have to edit what I have typed (i.e. press backspace once to delete the last character) the UI becomes completely unresponsive for about three to five minutes. When I look at the system monitor I can see the evolution-data-server is eating up about 50% of my CPU.

It seems that the auto-completion process is blocking the UI, and it should not. What debugging information do you need? Should I install the debug packages and run from the command line? Is there any particular environment variable I need to pass when running Evolution (i.e. VERBOSE_DEBUG=1)? Please let me know and I will get you the information as soon as possible.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.