Bug 2304747

Summary: [abrt] isync: sync_chans(): mbsync killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Timothy Fry <tim>
Component: isyncAssignee: Fabian Affolter <mail>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 40CC: lkundrak, mail, me, tim
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/aee28e820cbe0eb43138db04b4e5bd4a6edbee7
Whiteboard: abrt_hash:4984fb877ee1505035f0f68b8079fe57a2cd566c;VARIANT_ID=workstation;
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-08-19 20:15: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: proc_pid_status
none
File: maps
none
File: limits
none
File: cgroup
none
File: environ
none
File: open_fds
none
File: mountinfo
none
File: os_info
none
File: cpuinfo
none
File: core_backtrace
none
File: exploitable
none
File: dso_list
none
File: backtrace none

Description Timothy Fry 2024-08-13 21:30:04 UTC 
Description of problem:
Installed isync, completed .mbsyncrc per docs, called mbsync -a, and encountered a segfault.

Version-Release number of selected component:
isync-1.4.4-8.fc40

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         mbsync killed by SIGSEGV
journald_cursor: s=bf901180977c476aa87033662f586493;i=15442;b=3fb5504d98b244898a376666ad9b5047;m=7c0888d2b;t=61f96fbc37be6;x=6ad0fc1a1397ca03
executable:     /usr/bin/mbsync
cmdline:        /usr/bin/mbsync tim@timothyfry
rootdir:        /
uid:            1000
kernel:         6.9.9-200.fc40.x86_64
package:        isync-1.4.4-8.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: sync_chans
comment:        Installed isync, completed .mbsyncrc per docs, called mbsync -a, and encountered a segfault.

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 sync_chans at /usr/src/debug/isync-1.4.4-8.fc40.x86_64/src/main.c:906
 #1 imap_list_store_p3 at /usr/src/debug/isync-1.4.4-8.fc40.x86_64/src/drv_imap.c:3408
 #3 imap_list_store_p2 at /usr/src/debug/isync-1.4.4-8.fc40.x86_64/src/drv_imap.c:3402
 #4 done_imap_cmd at /usr/src/debug/isync-1.4.4-8.fc40.x86_64/src/drv_imap.c:326
 #5 imap_socket_read at /usr/src/debug/isync-1.4.4-8.fc40.x86_64/src/drv_imap.c:1750
 #6 event_wait at /usr/src/debug/isync-1.4.4-8.fc40.x86_64/src/util.c:831
 #7 main_loop at /usr/src/debug/isync-1.4.4-8.fc40.x86_64/src/util.c:903
Comment 1 Timothy Fry 2024-08-13 21:30:07 UTC 
Created attachment 2044165 [details]
File: proc_pid_status
Comment 2 Timothy Fry 2024-08-13 21:30:09 UTC 
Created attachment 2044166 [details]
File: maps
Comment 3 Timothy Fry 2024-08-13 21:30:10 UTC 
Created attachment 2044167 [details]
File: limits
Comment 4 Timothy Fry 2024-08-13 21:30:11 UTC 
Created attachment 2044168 [details]
File: cgroup
Comment 5 Timothy Fry 2024-08-13 21:30:13 UTC 
Created attachment 2044169 [details]
File: environ
Comment 6 Timothy Fry 2024-08-13 21:30:14 UTC 
Created attachment 2044170 [details]
File: open_fds
Comment 7 Timothy Fry 2024-08-13 21:30:16 UTC 
Created attachment 2044171 [details]
File: mountinfo
Comment 8 Timothy Fry 2024-08-13 21:30:17 UTC 
Created attachment 2044172 [details]
File: os_info
Comment 9 Timothy Fry 2024-08-13 21:30:19 UTC 
Created attachment 2044173 [details]
File: cpuinfo
Comment 10 Timothy Fry 2024-08-13 21:30:21 UTC 
Created attachment 2044174 [details]
File: core_backtrace
Comment 11 Timothy Fry 2024-08-13 21:30:22 UTC 
Created attachment 2044175 [details]
File: exploitable
Comment 12 Timothy Fry 2024-08-13 21:30:23 UTC 
Created attachment 2044176 [details]
File: dso_list
Comment 13 Timothy Fry 2024-08-13 21:30:25 UTC 
Created attachment 2044177 [details]
File: backtrace
Comment 14 Fabio Alessandro Locati 2024-08-19 20:15:40 UTC 
This is a duplicate of #2302132

*** This bug has been marked as a duplicate of bug 2302132 ***