GNOME Bugzilla – Bug 256479
'load images only if sender in addressbook' / hang ...
Last modified: 2009-02-12 11:24:31 UTC
Browsing mails and junking them at the same time (although may be unrelated) I occasionally get an odd hang; whereby the evolution GUI remains responsible, I can select other mails in the mail list - but þe preview 'sticks' with a single mail, and simply won't update. Most odd; I can't see any particular pattern to the mails than hang it. It _looks_ from the stack-trace as if it's some e-book problem (to me) - and Michael says it's related to this setting. The bug showed up for me (the first time) about mid-last week; at the earliest ~29th March. Thread 3 - looks like it never gets signalled. (gdb) t a a bt
+ Trace 45712
Thread 11 (Thread 573451 (LWP 31623))
Thread 10 (Thread 327689 (LWP 22311))
Thread 9 (Thread 311304 (LWP 22310))
Thread 7 (Thread 81926 (LWP 22266))
Thread 5 (Thread 49156 (LWP 22264))
Thread 4 (Thread 32771 (LWP 22263))
Thread 3 (Thread 16386 (LWP 22262))
note that thread 3 isn't the main thread, does it need to run in that? chris said the sync api should be ok to call from any thread. PS it should happen for any mail that has remote http images in it with that setting turned on. since mail formatting is done from another thread, the rest of the app will continue to function.
*** bug 257523 has been marked as a duplicate of this bug. ***
The duplicate has some fairly extensive information.
*** bug 257780 has been marked as a duplicate of this bug. ***
Since the duplicate explains that by removing the offending Adressbook sources you can fix the problem, I have a question. How? Whenever I try to delete I get a message that says Error removing address book: e_book_load_uri: no factories available for uri `ldap://ldap.yahoo.com:389/??one' What does this mean, and how do I remove these sources anyway? Should I open another bug or are these two subjects related (they seem to be)?
It shouldn't need to run on the main thread unless some gui auth has to be done.
*** bug 257429 has been marked as a duplicate of this bug. ***
*** bug 258540 has been marked as a duplicate of this bug. ***
Going to mark this as fixed, as (in the information listed in the duplicate), it's most likely caused by a non-responsive ldap server (http://bugzilla.ximian.com/show_bug.cgi?id=58495, which is now fixed.)
As of evolution1.5-1.5.7.0.200405171248-0, this is not fixed. I don't have any LDAP sources and it does hang with some messages.
I still get this with evolution1.5-1.5.8.0.200405260833
And 1.5.8 duplicates too
*** bug 259210 has been marked as a duplicate of this bug. ***
*** bug 259432 has been marked as a duplicate of this bug. ***
Works for me in 1.5.9.1.
I am seeing this issue in 1.5.8 with no ldap sources.
*** bug 259496 has been marked as a duplicate of this bug. ***
bug 259496 has an excellent backtrace. Blame e-d-s
ok i've committed some code which does two things: - it only queries addressbooks that are part of your 'autocomplete' list rather than every addressbook available. - if it still gets stuck, which seems to be very backend related, you can hit the 'cancel' button, and it should clean up and reset itself.
This bug seems to exist in 2.8.1 still. Since my LDAP server is hosed at the moment and I have been hitting this bug on every single message in my INBOX with an image in it, I have finally come to the conclusion that this problem is that a message has a URL to an image in it, and the setting to allow image loading only when the sender is in an address book is set and some LDAP connected address books are not available. Hitting cancel does NOT restore working order to the preview pane as comment #19 suggests it should. Do we re-open this bug or start a new bug?
Please re-open.
(In reply to comment #22) > Please re-open. > I don't seem to have any knobs or buttons to reopen bugs in my bugzilla view. Perhaps somebody else does?
re-opened.
Is bug 361145 a dup of this? The behavior seems similar and I've attached some debug stack traces there.
Yes, it looks the same - albeit newer :-) feel free to mark the best dup wrt. traces etc. as you like.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 361145 ***