Dear Maintainer, purging tenshi failed on a VM running Debian Testing (not the one this report is being written on) as follows: Removing tenshi (0.13-2) ... Stopping log monitor: tenshi. Purging configuration files for tenshi (0.13-2) ... Removing tenshi system user..userdel: user tenshi is currently used by process 2501 dpkg: error processing package tenshi (--purge): subprocess installed post-removal script returned error exit status 8 Afterwards there seems to be no more process of the user tenshi running and there's no more process with process id 2501. Maybe because of this: E: Sub-process /usr/bin/dpkg returned an error code (1) Failed to perform requested operation on package. Trying to recover: Press Return to continue. (i.e. there was no hint what was tried to being recovered, but I suspect it's tenshi's postrm script or such. So I suspect this is mostly an ordering issue in the postrm (or prerm) script. The user tenshi is though left on the system and tenshi seems not fully purged: # env COLUMNS=80 dpkg -l tenshi Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description +++-==============-============-============-================================= pc tenshi 0.13-2 all log monitoring and reporting tool #
tags 754922 + moreinfo Hi Axel, I am unfortunately unable to reproduce this bug. I have tested this on my local machine (Debian/testing) and my development machine (Debian/unstable). Also, it seems that the latest piuparts tests did not detect the described behavior [1]. The daemon is stopped just before removing the user; which should not cause problems as the daemon should be the only process running under the "tenshi" user. May be could you give some more details about your installation, that would help be debug this issue? Thanks, Ignace M [1] https://piuparts.debian.org/sid/pass/tenshi_0.13-2.log
Hello, Failing to have more info, and being unable to reproduce this bug (see latest piuparts also), I am reducing the severity to important. Please follow-up should you not approve this. Thanks. Ignace M