/usr/share/oneconf/oneconf-query:SystemError:/usr/bin/oneconf-query@245:async_update:update:update:compute_local_packagelist:__init__:open

[errors.ubuntu.com bug bridge]

The Ubuntu Error Tracker has been receiving reports about a problem regarding oneconf. This problem was most recently seen with version 0.3.7, the problem page at https://errors.ubuntu.com/problem/0d46e08ac7a927459ebaf8436dc8de6692abeee5 contains more details.

[Brian Murray (brian-murray)]

Here's the Traceback:

Traceback (most recent call last):
  File "/usr/bin/oneconf-query", line 245, in <module>
    oneconf.async_update()
  File "/usr/lib/python3/dist-packages/oneconf/directconnect.py", line 80, in async_update
    self.update()
  File "/usr/lib/python3/dist-packages/oneconf/directconnect.py", line 73, in update
    self.PackageSetHandler().update()
  File "/usr/lib/python3/dist-packages/oneconf/packagesethandler.py", line 63, in update
    newpkg_list = self.distro.compute_local_packagelist()
  File "/usr/lib/python3/dist-packages/oneconf/distributor/Ubuntu.py", line 42, in compute_local_packagelist
    with apt.Cache() as apt_cache:
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 107, in __init__
    self.open(progress)
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 153, in open
    self._records = apt_pkg.PackageRecords(self._cache)
SystemError: E:Could not open file /var/lib/apt/lists/ve.archive.ubuntu.com_ubuntu_dists_trusty_restricted_i18n_Translation-es - open (2: No such file or directory)

It seems like it could a bug in oneconf or python-apt.

[Launchpad Janitor (janitor)]

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

[Bruno Nova (brunonova)]

I received a similar error a few days ago.
It's a very strange error, because the file that was mentioned actually exists in my computer.
Unless that file was momentarily missing due to a repository update, and exactly when oneconf decided to sync. If that's how this works, of course.

The best and easiest way to fix this bug would probably be to just add a try...except block around one of the lines in the traceback.

[Sebastien Bacher (seb128)]

That seems a frequent e.u.c issue, I reported it to Debian python-apt on https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800501 and the maintainer replied

"You're probably opened the cache without holding a lock, and an update ran in parallel. That's really the only possible explanation I could think of."