Bug 1159414

Summary: [abrt] claws-mail: g_slist_find(): claws-mail killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Raphael Groner <projects.rg>
Component: claws-mailAssignee: Andreas Bierfert <andreas.bierfert>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: andreas.bierfert, kupo, ssorce
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7ba9305c14bd1f9bbf534596e52e0c93aa71e65a
Whiteboard: abrt_hash:da5aebd36084d1d9d16a8eec6b85a8d8fcf57f7f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-01 09:22:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Raphael Groner 2014-10-31 20:31:45 UTC 
Description of problem:
unsubscribe from a folder named 'Unbekannt' (english: 'unknown')

Version-Release number of selected component:
claws-mail-3.10.1-1.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        claws-mail
crash_function: g_slist_find
executable:     /usr/bin/claws-mail
kernel:         3.16.6-203.fc20.x86_64
type:           CCpp

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_slist_find at gslist.c:727
 #1 flag_ok at imap.c:4977
 #2 imap_get_flags_thread at imap.c:5121
 #3 imap_get_flags at imap.c:5330
 #4 syncronize_flags at folder.c:1933
 #5 folder_item_scan_full at folder.c:2333
 #6 folderview_check_new at folderview.c:1117
 #7 inc_all_account_mail at inc.c:362
 #8 inc_autocheck_func at inc.c:1497
 #14 gtk_main at gtkmain.c:1257
Comment 1 Raphael Groner 2014-10-31 20:31:50 UTC 
Created attachment 952591 [details]
File: backtrace
Comment 2 Raphael Groner 2014-10-31 20:31:52 UTC 
Created attachment 952592 [details]
File: cgroup
Comment 3 Raphael Groner 2014-10-31 20:31:56 UTC 
Created attachment 952593 [details]
File: core_backtrace
Comment 4 Raphael Groner 2014-10-31 20:31:58 UTC 
Created attachment 952594 [details]
File: dso_list
Comment 5 Raphael Groner 2014-10-31 20:32:00 UTC 
Created attachment 952595 [details]
File: environ
Comment 6 Raphael Groner 2014-10-31 20:32:01 UTC 
Created attachment 952596 [details]
File: exploitable
Comment 7 Raphael Groner 2014-10-31 20:32:03 UTC 
Created attachment 952597 [details]
File: limits
Comment 8 Raphael Groner 2014-10-31 20:32:08 UTC 
Created attachment 952598 [details]
File: maps
Comment 9 Raphael Groner 2014-10-31 20:32:10 UTC 
Created attachment 952599 [details]
File: open_fds
Comment 10 Raphael Groner 2014-10-31 20:32:13 UTC 
Created attachment 952600 [details]
File: proc_pid_status
Comment 11 Michael Schwendt 2014-10-31 22:00:00 UTC 
> unsubscribe from a folder named 'Unbekannt' (english: 'unknown')

Please, at least try to give a few more details. What did happen beyond the crash? Did unsubscribing work? If it didn't, did you try again? What did happen then? Is the problem reproducible with different folders?

Note that upstream doesn't like bug reports, which are not reproducible. So, unreproducible crashes due to side-effects (such as memory corruption and race conditions) probably won't be looked at and will only vanish eventually as a result of rewriting/changing/fixing/developing Claws Mail further.
Comment 12 Raphael Groner 2014-10-31 22:31:42 UTC 
Unfortunately, I can not reproduce any similiar crash so far, did subscribe and unsubscribe several times to try to enforce a crash, but no success. Maybe it depends on a special environment state, as you've guessed already.

As far as I remember, the database of subscriptions got corrupt over all my individually configured accounts. I use at the same server account several different locally configured (virtual) accounts, each has other subscriptions to folders and an own unique sender address, web.de allows such a configuration via imap.

Please keep my bug open, hopefully some other user could reproduce in near future. I can understand that it's obviously a real configuration and environment state thingy. Therefore, should not be need to report at upstream for now.
Comment 13 Raphael Groner 2015-04-01 09:22:40 UTC 
Never seen this again. Closing, please reopen if needed.