Also confirmed on Artful and Zesty!
** Tags removed: verification-needed verification-needed-zesty
** Tags added: verification-done verification-done-zesty
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
Tested on Xenial and Trusty and the test-case passes fine.
** Tags removed: verification-needed-trusty verification-needed-xenial
** Tags added: verification-done-trusty verification-done-xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
As far as I can tell the patch is applicable without change to all
shipped versions of the fuse-umfuse-ext2 codebase from Trusty onward
(including Artful). I'm not sure which earlier releases it applies to,
but I guess those are all EOL.
--
You received this bug notification because you are a me
Ah, I've found the upstream! It's https://sourceforge.net/p/view-
os/code/HEAD/tree/trunk/fuse-modules/fuse-umfuse-ext2/ but it's not been
touched since 2013, and it does contain the deadlock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
[Impact]
* Any attempt to create/overwrite symlinks in a partition mounted by
fuseext2 causes the fuseext2 process to deadlock, preventing the mounted
filesystem from being used at all until the userspace process is killed
and the filesystem is remounted.
[Test Case]
* dd if=/dev/zero of=parti
Bringing the proposed fix over from bazaar.
** Patch added: "prevent-deadlock-in-symlink.diff"
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1674868/+attachment/4941476/+files/prevent-deadlock-in-symlink.diff
--
You received this bug notification because you are a member of
Public bug reported:
Trying to create a symlink in a filesystem mounted by fuseext2 causes
the fuseext2 userspace process to deadlock before responding to the fuse
request. This is simply due to a code bug in fuse-ext2/op_link.c (lines
104 and 109) where the code calls FUSE_EXT2_LOCK rather than
Agreed, latest packages on toolchain-r are working correctly. Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1513565
Title:
libpython2.7 uses the 3.x name for ConfigParser
To manage notific
See my first comment, this is specific to the toolchain-r version of
libpython-minimal (the issue was introduced in
https://launchpadlibrarian.net/221233027/python2.7_2.7.10-3~14.04_2.7.10-4~14.04.diff.gz).
A clean trusty is not affected.
Is there a way to raise bugs against a PPA? If so I couldn
I've noticed that I'm using libpython2.7-minimal from the ubuntu-
toolchain-r PPA so I'm re-raising this issue in that PPA instead.
** Changed in: python2.7 (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Public bug reported:
Installing a minimal virtualenv on Trusty Tahr (using libpython-minimal
2.7.10-4~14.04), I ran into crashes because:
File "/usr/lib/python2.7/ssl.py", line 491, in inner
import configparser
ImportError: No module named configparser
Looking at the code in ss
11 matches
Mail list logo
