GNOME Bugzilla – Bug 321975
Deskbar crashes when typing text and evolution handler enabled
Last modified: 2005-11-22 11:39:48 UTC
Steps to reproduce: 1. Enable evolution 2. Type some text 3. At first character, segfault Stack trace: Backtrace was generated from '/usr/libexec/deskbar-applet' (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 46912509739776 (LWP 9689)] [New Thread 1082399072 (LWP 9691)] [Thread debugging using libthread_db enabled] [New Thread 46912509739776 (LWP 9689)] [New Thread 1082399072 (LWP 9691)] [Thread debugging using libthread_db enabled] [New Thread 46912509739776 (LWP 9689)] [New Thread 1082399072 (LWP 9691)] [New Thread 1082132832 (LWP 9690)] 0x00002aaaaadefeba in waitpid () from /lib/tls/libpthread.so.0
+ Trace 64159
Other information: evolution-2.4.1 eds 1.4.1.1 (libebook-1.2 1.4.1.1) python 2.4.2 deskbar 0.8.6 64 bits AMD
The trace may, or may not be related to bug #321869
<-- actual reporter, just subscribing
ahh, we forgot to mention that the crash only occurs when working as non-root user! With root everything seems to work!
steps to reproduce the error: (0. enable the evolution handler) 1. create a new addressbook in evolution 2. create a new contact 3. enable the new addressbook for autocompletion 4. type a letter into the deskbar-applet boom.
I can reproduce here. Nigel: can you try to fix that ?
OK, I fixed *a* bug - a crasher when the user has more than one address book that has auto-complete enabled. All my prior testing has only been with the one address book. This may explain the "works with root, not with regular user" behavior. But I still have another unresolved crasher bug #322119. Anyway, I've committed a fix for the first whilst I'm still gnawing on this other related bug. Please verify if the "steps to reproduce" given above still cause a crash. If they still do, please attach another stack trace (if it differs from the original report), and re-open this bug.
*** Bug 321869 has been marked as a duplicate of this bug. ***