unattended-upgrades crashes with: apt_pkg.Error: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages

Bug #1770224 reported by errors.ubuntu.com bug bridge on 2018-05-09
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apt (Ubuntu)
High
Unassigned

Bug Description

It seems pkgProblemResolver is hitting an internal bug quite frequently with latest u-u:

Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1927, in <module>
    sys.exit(main(options))
  File "/usr/bin/unattended-upgrade", line 1678, in main
    pkg.mark_upgrade(from_user=not pkg.is_auto_installed)
  File "/usr/lib/python3/dist-packages/apt/package.py", line 1483, in mark_upgrade
    self.mark_install(from_user=from_user)
  File "/usr/lib/python3/dist-packages/apt/package.py", line 1475, in mark_install
    fixer.resolve(True)
apt_pkg.Error: E:Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

I believe this should be fixed in apt rather than just catching it in u-u.

More info:

The Ubuntu Error Tracker has been receiving reports about a problem regarding unattended-upgrades. This problem was most recently seen with package version 1.1ubuntu1, the problem page at https://errors.ubuntu.com/problem/49de8d44b4ceccb27b66921173ee7e837e7a1e54 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

Balint Reczey (rbalint) on 2018-05-09
summary: - /usr/bin/unattended-upgrade:apt_pkg.Error:/usr/bin/unattended-
- upgrade@1927:main:mark_upgrade:mark_install
+ unattended-upgrades crashes with: apt_pkg.Error: E:Error,
+ pkgProblemResolver::Resolve generated breaks, this may be caused by held
+ packages
description: updated
affects: unattended-upgrades (Ubuntu) → apt (Ubuntu)
Julian Andres Klode (juliank) wrote :

That backtracr is something completely different. So what is this about, the locking failure or the resolver? Resolver failures are probably not going to be fixable, or only with guessing and extreme caution.

Balint Reczey (rbalint) wrote :

Resolver, just fixed the trace from the error.

description: updated
Julian Andres Klode (juliank) wrote :

This effectively is the "apt needs a new solver" bug

Changed in apt (Ubuntu):
status: New → Triaged
importance: Undecided → High
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers