Ubuntu
aptdaemon package

  1. Bug #441686
  2. Comment #9

Comment 9 for bug 441686

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

I tried to reproduce this bug by starting a package installation, and then entering at a terminal

    sudo pkill -SEGV aptd

Doing that, I didn't get the "Task cannot be monitored or controlled" alert at all. Instead I got these two Apport alerts: one "internal error" for aptd itself, and one "The application Ubuntu Software Center has closed unexpectedly" (an example of bug 1033902).

How can I trigger the "Task cannot be monitored or controlled" alert reliably?

It's possible those two Apport alerts may be combined into one or even zero (merged with a later alert). So I think it may still be appropriate for the Python aptdaemon client to be responsible for showing an error message in this situation. If it is, what can we suggest as ways to solve the problem?