Version-Release number of selected component: evolution-3.6.3-2.fc18 Additional info: backtrace_rating: 4 cmdline: evolution crash_function: smb_iconv executable: /usr/bin/evolution kernel: 3.7.5-201.fc18.x86_64 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 smb_iconv at ../lib/util/charset/iconv.c:120 #1 convert_string_talloc_handle at ../lib/util/charset/convert_string.c:421 #2 convert_string_talloc at ../lib/util/charset/convert_string.c:541 #3 ndr_pull_charset at ../librpc/ndr/ndr_string.c:593 #4 ndr_pull_dcerpc_bind_ack at default/librpc/gen_ndr/ndr_dcerpc.c:422 #6 ndr_pull_dcerpc_payload at default/librpc/gen_ndr/ndr_dcerpc.c:2925 #7 ndr_pull_ncacn_packet at default/librpc/gen_ndr/ndr_dcerpc.c:3159 #8 ncacn_pull at ../source4/librpc/rpc/dcerpc.c:691 #9 dcerpc_recv_data at ../source4/librpc/rpc/dcerpc.c:1060 #10 sock_process_recv at ../source4/librpc/rpc/dcerpc_sock.c:123
Created attachment 694836 [details] File: backtrace
Created attachment 694837 [details] File: cgroup
Created attachment 694838 [details] File: core_backtrace
Created attachment 694839 [details] File: dso_list
Created attachment 694840 [details] File: environ
Created attachment 694841 [details] File: limits
Created attachment 694842 [details] File: maps
Created attachment 694843 [details] File: open_fds
Created attachment 694844 [details] File: proc_pid_status
Created attachment 694845 [details] File: var_log_messages
Thanks for a bug report. I see this crashed when evolution-mapi was trying to connect to your Exchange server. Does it do that every time, or it was an occasional crash? The function it crashes in suggest some issue in a string encoding conversion, deep in samba code.
Hi Milan, if I remember correctly it crashed only once, however I've decided to report this bug. May I help you providing some other kind of useful information? Thanks.
Hi, thanks for the update, I appreciate you filled the bug. The hard thing is that some bugs are quite hard to reproduce, like this one, which happen only occasionally or rather rarely. The reproducibility is the main key to get bugs fixed. I see this happened during Login phase, when evolution-mapi was logging in to the server, where I may expect consistent behaviour (on the first look, I thought that the server returned some string in an encoding different that it should, thus the samba code broke on it, but it should be reproducible at least on your side, when connecting to the same server). If you do not mind, I would close this for now, and let's wait whether there will be more duplicates either from you or from other users, hopefully with found reproducibility steps. Or just look around what you did and what evolution did; for example, as this is on login, maybe you got disconnected unexpectedly from your Exchange server and evolution-mapi tried to reconnect (this is not fully noticeable, as evolution-mapi does that in the background, but maybe something like that is involved. The backtrace itself doesn't suggest exactly this issue, though.
Hi Milan, OK I agree with you so I'll close this bug for while, and if I find the way to reproduce it I'll reopen. Cheers.