Bug 1039234

Summary: [abrt] alpine-2.10-4.fc19: fs_give: Process /usr/bin/alpine was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Paul DeStefano <paul.destefano-redhat2>
Component: alpineAssignee: Joshua Daniel Franklin <joshuadfranklin>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: jima, joshuadfranklin, pwouters, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9d103d4314de3dabf64bc8aa6d0512e0574b23d5
Whiteboard: abrt_hash:6bd3a98ca6462b1122ccbeb80bda1bede406d860
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-07 14:25:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status none

Description Paul DeStefano 2013-12-07 07:50:14 UTC 
Description of problem:
This occured immediately after disconnecting from an IMAP server with which reALPINE had lost contact.  I received several messages that the server couldn't be reached and would I like to drop the connection.  I finally responded 'y', it disconnected, and then crashed before I could try to reopen the folder.

Version-Release number of selected component:
alpine-2.10-4.fc19

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
crash_function: fs_give
executable:     /usr/bin/alpine
kernel:         3.11.4-201.fc19.x86_64
runlevel:       N 5
type:           CCpp

Truncated backtrace:
Thread no. 1 (2 frames)
 #5 fs_give at fs_unix.c:68
 #6 index_lister at mailindx.c:789
Comment 1 Paul DeStefano 2013-12-07 07:50:18 UTC 
Created attachment 833824 [details]
File: backtrace
Comment 2 Paul DeStefano 2013-12-07 07:50:20 UTC 
Created attachment 833825 [details]
File: cgroup
Comment 3 Paul DeStefano 2013-12-07 07:50:22 UTC 
Created attachment 833826 [details]
File: core_backtrace
Comment 4 Paul DeStefano 2013-12-07 07:50:23 UTC 
Created attachment 833827 [details]
File: dso_list
Comment 5 Paul DeStefano 2013-12-07 07:50:25 UTC 
Created attachment 833828 [details]
File: environ
Comment 6 Paul DeStefano 2013-12-07 07:50:26 UTC 
Created attachment 833829 [details]
File: limits
Comment 7 Paul DeStefano 2013-12-07 07:50:28 UTC 
Created attachment 833830 [details]
File: maps
Comment 8 Paul DeStefano 2013-12-07 07:50:29 UTC 
Created attachment 833831 [details]
File: open_fds
Comment 9 Paul DeStefano 2013-12-07 07:50:31 UTC 
Created attachment 833832 [details]
File: proc_pid_status
Comment 10 Joshua Daniel Franklin 2013-12-07 14:25:45 UTC 
Unfortunately as far as I know alpine will crash if the IMAP connection is lost so I'm closing as WONTFIX. 

If you'd like to work on this as a feature for alpine, you could probably use netem packet loss simulation even with a local IMAP server: 
http://www.linuxfoundation.org/collaborate/workgroups/networking/netem 

If you get it working, the patches would be best submitted upstream to comp.mail.pine
Comment 11 Paul DeStefano 2014-01-01 19:26:34 UTC 
Hi Josh,

Hmm, I don't know why you say that.  That's quite untrue; Alpine will *not* crash if IMAP connection is lost.

Alpine just notifies you that it has lost contact with the IMAP server and gives you a chance to disconnect and close the folder every 30 seconds.  Otherwise, it just keeps retrying whatever it was doing.  I mentioned that in my bug report.  This situation is not unexpected.

In any case, I've experienced countless IMAP server failures while using Alpine and never noticed any correlation between them and crashes.  Maybe a particular IMAP server, but not merely loosing connections.