This bug was fixed in the package aptdaemon - 1.1.1+bzr982-0ubuntu33 --------------- aptdaemon (1.1.1+bzr982-0ubuntu33) groovy; urgency=medium
* Update crash handler to use the changed apport function. (LP: #1700810) -- Brian Murray <br...@ubuntu.com> Mon, 11 May 2020 15:10:33 -0700 ** Changed in: aptdaemon (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1700810 Title: aptdaemon's crash.py file is not working Status in aptdaemon package in Ubuntu: Fix Released Status in aptdaemon source package in Xenial: In Progress Status in aptdaemon source package in Bionic: In Progress Status in aptdaemon source package in Eoan: In Progress Status in aptdaemon source package in Focal: In Progress Bug description: [Impact] aptdaemon ships its own crash handler which is not working and subsequently crash reports are not being created about aptdaemon. Given that aptdaemon is the package manager behind update-manager it'd be good to get crash reports from it. [Test Case] 1) cd / 2) Run 'sudo python3 aptdaemon.crash' 3) Look for a crash file in /var/crash named '_usr_sbin_aptd.0.crash' With the current version aptdaemon no crash file will be created. With the version of aptdaemon from -proposed. there will be a crash file and if you view it you will see "Title: test" and "Traceback: testtrace" in the file. [Regression Test Case] After creating a .crash file with the version of aptdaemon from -proposed run 'sudo python3 aptdaemon.crash' again. You should receive a 'FileExistsError' traceback from apport. [Regression Potential] Aptdaemon is being updated to use a function that was renamed in apport so there is little chance of regression. However, we are removing a file exists check (which should now be handled by apport) so we should double check that an existing crash file doesn't get overwritten. [Original Description] aptdaemon includes a file named crash.py which is supposed to create apport problem reports for a given crash. However, searching through bug attachments for aptdaemon bug reports I don't see any with the key "TransactionRole" in any recent bug reports. $ grep -r TransactionRole * bug-1058886/Description.txt:TransactionRole: role-commit-packages bug-1158395/Description.txt:TransactionRole: role-install-file bug-1166875/Description.txt:TransactionRole: role-remove-packages bug-1201054/Description.txt:TransactionRole: role-commit-packages bug-1237851/Description.txt:TransactionRole: role-commit-packages bug-1279716/Description.txt:TransactionRole: role-commit-packages bug-1293334/Description.txt:TransactionRole: role-pk-query bug-1297434/Description.txt:TransactionRole: role-install-file bug-1301063/Description.txt:TransactionRole: role-install-packages bug-1306498/Description.txt:TransactionRole: role-pk-query bug-1380290/apport_crash.log:TransactionRole: role-pk-query It seems likely that either "trans" is null, or something is wrong with aptdaemon's crash handler. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1700810/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp