Aptdaemon crashes when there are any non-PEP-440 packages on the system due to setuptools 66.x.x

I opened bug #2008898 which may be a duplicate.

Status changed to 'Confirmed' because the bug affects multiple users.

Is this still an issue? I don't see it happening anymore.

@amberella-777 that is probably because you do not have any python packages whose version pkg_resources considers "invalid". In my case, it currently stumbles on `syncthing` package (from a third party repo)

Apr 11 20:01:01 pccross org.debian.apt[6869]: 20:01:01 AptDaemon [INFO]: Initializing daemon
Apr 11 20:01:01 pccross org.debian.apt[6869]: /usr/lib/python3/dist-packages/aptdaemon/worker/pkworker.py:35: PyGIWarning: PackageKitGlib was imported without specifying a version first. Use gi.require_version('PackageKitGlib', '1.0') before import to ensure that the right version gets loaded.
Apr 11 20:01:01 pccross org.debian.apt[6869]: from gi.repository import PackageKitGlib as pk
Apr 11 20:01:01 pccross org.debian.apt[6869]: Traceback (most recent call last):
Apr 11 20:01:01 pccross org.debian.apt[6869]: File "/usr/lib/python3/dist-packages/aptdaemon/core.py", line 1462, in __init__
Apr 11 20:01:01 pccross org.debian.apt[6869]: from .worker.pkworker import AptPackageKitWorker
Apr 11 20:01:01 pccross org.debian.apt[6869]: File "/usr/lib/python3/dist-packages/aptdaemon/worker/pkworker.py", line 43, in <module>
Apr 11 20:01:01 pccross org.debian.apt[6869]: from ..pkutils import (bitfield_add, bitfield_remove, bitfield_summarize,
Apr 11 20:01:01 pccross org.debian.apt[6869]: ModuleNotFoundError: No module named 'aptdaemon.pkutils'
Apr 11 20:01:01 pccross org.debian.apt[6869]: During handling of the above exception, another exception occurred:
Apr 11 20:01:01 pccross org.debian.apt[6869]: Traceback (most recent call last):
Apr 11 20:01:01 pccross org.debian.apt[6869]: File "/usr/sbin/aptd", line 39, in <module>
Apr 11 20:01:01 pccross org.debian.apt[6869]: aptdaemon.core.main()
Apr 11 20:01:01 pccross org.debian.apt[6869]: File "/usr/lib/python3/dist-packages/aptdaemon/core.py", line 2193, in main
Apr 11 20:01:01 pccross org.debian.apt[6869]: daemon = AptDaemon(options, bus=bus)
Apr 11 20:01:01 pccross org.debian.apt[6869]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 11 20:01:01 pccross org.debian.apt[6869]: File "/usr/lib/python3/dist-packages/aptdaemon/core.py", line 1466, in __init__
Apr 11 20:01:01 pccross org.debian.apt[6869]: self.worker = AptWorker(options.chroot, load_plugins)
Apr 11 20:01:01 pccross org.debian.apt[6869]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 11 20:01:01 pccross org.debian.apt[6869]: File "/usr/lib/python3/dist-packages/aptdaemon/worker/aptworker.py", line 205, in __init__
Apr 11 20:01:01 pccross org.debian.apt[6869]: self._load_plugins(["modify_cache_after", "modify_cache_before",
Apr 11 20:01:01 pccross org.debian.apt[6869]: File "/usr/lib/python3/dist-packages/aptdaemon/worker/__init__.py", line 191, in _load_plugins
Apr 11 20:01:01 pccross org.debian.apt[6869]: dists, errors = pkg_resources.working_set.find_plugins(env)
Apr 11 20:01:01 pccross org.debian.apt[6869]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Apr 11 20:01:01 pccross org.debian.apt[6869]: File "/usr/lib/python3/dist-packages/pkg_resources/__init__.py", line 907, in find_plugins
Apr 11 20:01:01 pccross org.debian.apt[6869]: env = Environment(self.entries)
Apr ...

@crosser thanks for the explanation. I'm running SyncThing in a snap.
https://gitlab.com/arubislander/syncthing-snap

For reference, I've submitted a pull request to syncthing-gtk to make their version PEP-440 compliant https://github.com/kozec/syncthing-gtk/pull/600.

I still think that it is wrong if any unrelated python package that is not fully standards compliant breaks the process of upgrade for the whole system.

In my case, rmlint-gui package was the culprit. Removed it and now I can use Software Updater (no more aptd crashes).

There is a main ticket for fixing those non-PEP-440 packages: bug #1991606

This bug was cited as justification for bug 1991606, so to help with understanding that, please could someone post steps to reproduce on a clean Ubuntu installation? Which Ubuntu releases are affected?

In particular, where did the affected /usr/lib/python3/dist-packages/pkg_resources/* come from? Is that from a package shipped by Ubuntu, and in which case, what versions are affected?

Interesting thing, adding back the rmlint-gui package (which was identified like one of the culprits, see #8) and I cannot reproduce the issue. Maybe it is gone?
Later Edit: after a reboot, the problem appears once more. I will create a new comment with steps to reproduce.

Steps to reproduce:

1. Install Ubuntu 23.04
2. Perform all required updates using Software Updater.
3. 'sudo apt install rmlint-gui'
4. Reboot (without reboot the bug did not reproduce)
5. Launch Software Updater
6. It will crash, see logs (08:38:56) related to apt daemon.
7. sudo apt remove rmlint-gui
8. Launch Software Updater
9. Success, see logs (08:40:20)

rmlint-gui is comming from universe repo, this is true, but the Software Updater should not crash.

@bdrung:

> There is a main ticket for fixing those non-PEP-440 packages: bug #1991606

this is not the point! Obviously non-PEP-440 compliant packages _in the distro_ must be fixed, independently of broken aptdaemon.

The point is that if somebody includes a third party repo, or installs a not-from-repo python package system-wide, and that package happens to be non-compliant, _it breaks distro upgrade process_. In my pretty firm opinion, it should no be this way.

I understand and agree with the wish to put more order in python packaging. Setuptools refuse to create a non-compliant package? That would be totally fair. But in this case, _uses_ who have no power to fix the problem, and may not even know what's going on, are taken hostage.

Status changed to 'Confirmed' because the bug affects multiple users.