Debugging the Python process of Duplicity shows no polling or reading
from appropriate number of pipes:
* 1 Thread 0x7f7f510d0740 (LWP 19797) 0x00007f7f50ce9f96 in
futex_abstimed_wait_cancelable (private=0, abstime=0x0, expected=0,
futex_word=0x559f3d5e48f0)
at ../sysdeps/unix/sysv/linux/futex-internal.h:205
2 Thread 0x7f7f4d9b0700 (LWP 19801) 0x00007f7f50a01951 in __GI___poll
(fds=0x559f3d517d30, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
3 Thread 0x7f7f469fd700 (LWP 19802) 0x00007f7f50a01951 in __GI___poll
(fds=0x559f3d5290a0, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
4 Thread 0x7f7f461fc700 (LWP 19960) 0x00007f7f50ceba4a in __waitpid
(pid=19959, stat_loc=0x7f7f461fb534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
5 Thread 0x7f7f3ffff700 (LWP 19962) 0x00007f7f50ceba4a in __waitpid
(pid=19961, stat_loc=0x7f7f3fffe534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
6 Thread 0x7f7f3f7fe700 (LWP 19965) 0x00007f7f50ceba4a in __waitpid
(pid=19964, stat_loc=0x7f7f3f7fd534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
7 Thread 0x7f7f3effd700 (LWP 19967) 0x00007f7f50ceba4a in __waitpid
(pid=19966, stat_loc=0x7f7f3effc534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
8 Thread 0x7f7f3e7fc700 (LWP 19969) 0x00007f7f50ceba4a in __waitpid
(pid=19968, stat_loc=0x7f7f3e7fb534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
9 Thread 0x7f7f3dffb700 (LWP 19971) 0x00007f7f50ceba4a in __waitpid
(pid=19970, stat_loc=0x7f7f3dffa534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
10 Thread 0x7f7f3d7fa700 (LWP 19973) 0x00007f7f50ceba4a in __waitpid
(pid=19972, stat_loc=0x7f7f3d7f9534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
11 Thread 0x7f7f3cff9700 (LWP 19975) 0x00007f7f50ceba4a in __waitpid
(pid=19974, stat_loc=0x7f7f3cff8534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
12 Thread 0x7f7f2bfff700 (LWP 19977) 0x00007f7f50ceba4a in __waitpid
(pid=19976, stat_loc=0x7f7f2bffe534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
13 Thread 0x7f7f2b7fe700 (LWP 19979) 0x00007f7f50ceba4a in __waitpid
(pid=19978, stat_loc=0x7f7f2b7fd534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
14 Thread 0x7f7f2affd700 (LWP 19981) 0x00007f7f50ceba4a in __waitpid
(pid=19980, stat_loc=0x7f7f2affc534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
15 Thread 0x7f7f2a7fc700 (LWP 19983) 0x00007f7f50ceba4a in __waitpid
(pid=19982, stat_loc=0x7f7f2a7fb534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
16 Thread 0x7f7f29ffb700 (LWP 19985) 0x00007f7f50ceba4a in __waitpid
(pid=19984, stat_loc=0x7f7f29ffa534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
17 Thread 0x7f7f297fa700 (LWP 19988) 0x00007f7f50ceba4a in __waitpid
(pid=19987, stat_loc=0x7f7f297f9534, options=0) at
../sysdeps/unix/sysv/linux/waitpid.c:29
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1727653
Title:
error: can't start new thread
To manage notifications about this bug go to:
https://bugs.launchpad.net/duplicity/+bug/1727653/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
