Bug 693908 - segfault starting up evolution
Summary: segfault starting up evolution
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: evolution-data-server
Version: 6.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Matthew Barnes
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-05 21:19 UTC by Dennis Gregorovic
Modified: 2013-08-12 11:05 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-12 11:05:14 UTC
Target Upstream Version:


Attachments (Terms of Use)
stacktrace from gdb (12.76 KB, text/plain)
2011-04-05 21:19 UTC, Dennis Gregorovic
no flags Details

Description Dennis Gregorovic 2011-04-05 21:19:02 UTC
Created attachment 490084 [details]
stacktrace from gdb

Description of problem:
When starting evolution, there is a segfault almost immediately

Version-Release number of selected component (if applicable):
evolution-2.28.3-10.el6.x86_64
evolution-data-server-2.28.3-10.el6.x86_64

How reproducible:
every time

Steps to Reproduce:
1. start evolution
2.
3.
  
Actual results:
segfault

Expected results:
no segfault

Additional info:
This just started happening today.  No relevant local changes that I'm aware of.

Comment 2 RHEL Program Management 2011-04-05 21:23:41 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 3 Milan Crha 2013-05-09 13:11:05 UTC
No exact hit upstream, though the vee_rebuild_folder() looks known.

Thread 17 (Thread 0x7fffc1f9c700 (LWP 4348)):
#0  IA__g_str_hash (v=0x0) at gstring.c:99
#1  0x000000363ba2adf5 in g_hash_table_lookup_node_for_insertion (hash_table=0x7fffb8167400 = {...}, key=0x0, value=0x1, keep_new_key=0) at ghash.c:268
#2  g_hash_table_insert_internal (hash_table=0x7fffb8167400 = {...}, key=0x0, value=0x1, keep_new_key=0) at ghash.c:863
#3  0x0000003e1d05146c in vee_rebuild_folder (vf=0x97a980, source=0x7fffb4006d70, ex=<value optimized out>) at camel-vee-folder.c:1159
#4  0x0000003e1d051d7d in vee_add_folder (vf=<value optimized out>, sub=<value optimized out>) at camel-vee-folder.c:1937
#5  0x0000003e1d04931b in camel_store_get_folder (store=0x846600, folder_name=<value optimized out>, flags=0, ex=0xd9ea00) at camel-store.c:351
#6  0x00007fffedd6b7ee in mail_tool_uri_to_folder (uri=<value optimized out>, flags=0, ex=0xd9ea00) at mail-tools.c:345
#7  0x00007fffedd6e292 in vfolder_adduri_exec (m=0xd9e9e0) at mail-vfolder.c:265
#8  0x00007fffedd6715f in mail_msg_proxy (msg=0xd9e9e0) at mail-mt.c:522
#9  0x000000363ba6360b in g_thread_pool_thread_proxy (data=<value optimized out>) at gthreadpool.c:265
#10 0x000000363ba62074 in g_thread_create_proxy (data=0xd85d00) at gthread.c:635
#11 0x00007ffff79c47e1 in start_thread (arg=0x7fffc1f9c700) at pthread_create.c:301
#12 0x00007ffff75178ed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Comment 5 Milan Crha 2013-06-13 16:10:20 UTC
Dennis, do you still see this, please? The best, if you could try with rebased 2.32.3 packages. They are currently only in brew, but will be shortly available in Matthew's repository, whose baseurl is
   http://mbarnes.fedorapeople.org/evolution-232-testing/

Comment 6 Dennis Gregorovic 2013-08-12 10:02:26 UTC
(In reply to Milan Crha from comment #5)
> Dennis, do you still see this, please? The best, if you could try with
> rebased 2.32.3 packages. They are currently only in brew, but will be
> shortly available in Matthew's repository, whose baseurl is
>    http://mbarnes.fedorapeople.org/evolution-232-testing/


Hi.  I'm currently running a fresh RHEL 6.4 install.  I am no longer hitting this segfault and I don't think I have a way to reproduce it at this point.

-- Dennis

Comment 7 Milan Crha 2013-08-12 11:05:14 UTC
Thanks for the update. I'm closing this, but if you'll face it again, with 2.32.3+, then feel free to reopen, or file a new bug. Thanks in advance.


Note You need to log in before you can comment on or make changes to this bug.