GNOME Bugzilla – Bug 617720
evolution crashed after clearing search bar
Last modified: 2013-09-13 01:03:36 UTC
evolution 2.31.2 I configured google address book. After it fetched all the contacts, i searched for a contact. CPU for e-addressbook-factory went high for sometime and when UI became active, i looked but it didn't complete search as i could see all the contacts so i cleared off the search bar and evolution crashed. I did notice a warning on evolution terminal (bug-buddy:18798): libebook-WARNING **: e-book.c:2245: cannot get book from factory: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. System: Linux 2.6.31.12-0.2-default #1 SMP 2010-03-16 21:25:39 +0100 i686 X Vendor: The X.Org Foundation X Vendor Release: 10605000 Selinux: No Accessibility: Disabled GTK+ Theme: Gilouche Icon Theme: Gilouche GTK+ Modules: canberra-gtk-module, gnomebreakpad Memory status: size: 259817472 vsize: 259817472 resident: 55156736 share: 26562560 rss: 55156736 rss_rlim: 18446744073709551615 CPU usage: start_time: 1273039658 rtime: 1318 utime: 1244 stime: 74 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/home/lakhil/opt/gnome3/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0xb2ffeb70 (LWP 18797)] [New Thread 0xb1dffb70 (LWP 18765)] [New Thread 0xb37ffb70 (LWP 18756)] [New Thread 0xb4197b70 (LWP 18755)] [New Thread 0xb4998b70 (LWP 18754)] [New Thread 0xb5199b70 (LWP 18753)] 0xffffe430 in __kernel_vsyscall ()
+ Trace 221719
Thread 1 (Thread 0xb5a73860 (LWP 18750))
Inferior 1 [process 18750] will be detached. Quit anyway? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (83 sec old) --------------------- (evolution-alarm-notify:2559): libecal-WARNING **: e-cal.c:404: e-d-s proxy died (evolution-alarm-notify:2559): libecal-WARNING **: e-cal.c:404: e-d-s proxy died (evolution-alarm-notify:2559): libecal-WARNING **: e-cal.c:404: e-d-s proxy died (evolution-alarm-notify:2559): libecal-WARNING **: e-cal.c:404: e-d-s proxy died (evolution-alarm-notify:2559): libecal-WARNING **: e-cal.c:404: e-d-s proxy died (evolution-alarm-notify:2559): libecal-WARNING **: e-cal.c:404: e-d-s proxy died ** (nm-applet:2564): WARNING **: Unhandled setting secret type (write) '802-1x/private-key' : 'GArray_guchar_' ** (nm-applet:2564): WARNING **: Unhandled setting secret type (write) '802-1x/phase2-private-key' : 'GArray_guchar_'
I'm wondering what circumstance could cause this. I was unable to reproduce it, because my google address book is pretty small. This one is most related, I believe: > libebook-WARNING **: e-book.c:2245: cannot get book from > factory: Did not receive a reply. The backtrace of e-addressbook-factory process should show us why it time-outed. Could you try with actual master (there were changes in ema to not block main thread of a factory while fetching contacts recently), and catch the backtrace of the factory, please? Thanks in advance.
I cann't reproduce.