Package: ansible-mitogen Version: 0.3.4-1 Severity: important Hi,
when ansible-mitogen and python3-mitogen 0.3.4-1 are installed, I cannot run ansible against my fleet any more. The run asks for the become password as usual, and then aborts with "sudo password is required". A -vvv output of the failing case is attached. Things start to go bad around line 1540 when the first call to sudo is issued and sudo replies with its password prompt. Going back to ansible-mitogen and python3-mitogen 0.3.3-9 from bookworm fixes the issue for me. A -vvv output of the successful case is also attached. In the successful case, the interesting parts also happen aronud line 1540, and there is really not much difference between the success and failure case other than the failure. Filing this bug as important as the current mitogen version is completely ununseable at least for me. otoh, noone has filed a bug report yet so the package is probably not failing for everyone. If I can help with anything to debug, run test cases etc, please let me know. Greetings Marc -- System Information: Debian Release: trixie/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.4.7-zgws1 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages ansible-mitogen depends on: ii ansible 7.7.0+dfsg-1 ii ansible-core 2.14.8-1 ii python3 3.11.4-5 ii python3-mitogen 0.3.4-1 ansible-mitogen recommends no packages. ansible-mitogen suggests no packages. -- no debconf information
