Hello,
thanks @Jakob for pointing out the upstream issue.
Is there any plan to backport the fix into Debian stretch?
The issue is quite annoying and downgrading or using the package from
sid/buster feels uncomfortable.
Upstream issue 214 [1] is marked as duplicate of 348. There [2] you can
find
This looks like https://github.com/vgough/encfs/issues/214 which
has been fixed in EncFS v1.9.2, released two days ago.
I'm seeing the same problem following an upgrade today, with version
1.9.1-4. My log message is
Message-ID: <149998600914.4028.4334536845084459008.reportbug@snowball>
X-Mailer: reportbug 7.1.7
Date: Thu, 13 Jul 2017 16:46:49 -0600
Package: encfs
Followup-For: Bug #849850
Jul 13 16
Followup-For: Bug #849850
Package: encfs
Hi Felix and Timo,
I also got the same kind of errors after upgrade to 1.9.1-3.
Using encfs on top of ext4 and using pam_encfs for unlocking.
The segfault happened while heavy read on the disk (after a while doing
a backup).
Now I downgraded to 1.7.4-5
Hi Timo,
I filed a similar report under #849215 but was unable to pin the issue on
the encfs package. What is your underlying file system, please? Also, are
you using pam_encfs.so to mount? Thank you!
Best regards,
Felix
2017-01-01 13:32:15 CET Timo Weingärtner:
> I got errors "transport endpoint not connected" when opening files.
> dmesg had:
>
> encfs[25279]: segfault at 0 ip 7f7213f9bf36 sp 7f72037fd970 error 4
> in libencfs.so.1.9.1[7f7213f42000+75000]
> encfs[1833]: segfault at 0 ip 7f0480488f36
Package: encfs
Version: 1.9.1-3
Severity: important
I got errors "transport endpoint not connected" when opening files.
dmesg had:
encfs[25279]: segfault at 0 ip 7f7213f9bf36 sp 7f72037fd970 error 4 in
libencfs.so.1.9.1[7f7213f42000+75000]
encfs[1833]: segfault at 0 ip 7f0480488f36
7 matches
Mail list logo
