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
Created attachment 2044165 [details] File: proc_pid_status
Created attachment 2044166 [details] File: maps
Created attachment 2044167 [details] File: limits
Created attachment 2044168 [details] File: cgroup
Created attachment 2044169 [details] File: environ
Created attachment 2044170 [details] File: open_fds
Created attachment 2044171 [details] File: mountinfo
Created attachment 2044172 [details] File: os_info
Created attachment 2044173 [details] File: cpuinfo
Created attachment 2044174 [details] File: core_backtrace
Created attachment 2044175 [details] File: exploitable
Created attachment 2044176 [details] File: dso_list
Created attachment 2044177 [details] File: backtrace
This is a duplicate of #2302132 *** This bug has been marked as a duplicate of bug 2302132 ***