| 2018-05-09 17:12:02 |
errors.ubuntu.com bug bridge |
bug |
|
|
added bug |
| 2018-05-09 17:12:03 |
errors.ubuntu.com bug bridge |
bug |
|
|
added subscriber Balint Reczey |
| 2018-05-09 17:13:37 |
Balint Reczey |
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 |
|
| 2018-05-09 17:16:12 |
Balint Reczey |
description |
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/. |
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 1822, in main
options.dry_run)
File "/usr/bin/unattended-upgrade", line 1399, in do_auto_remove
res, error = cache_commit(cache, logfile_dpkg, verbose)
File "/usr/bin/unattended-upgrade", line 513, in cache_commit
res = cache.commit(install_progress=iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 565, in commit
res = self._fetch_archives(fetcher, pm)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 385, in _fetch_archives
raise LockFailedException("Failed to lock %s" % lockfile)
apt.cache.LockFailedException: Failed to lock /var/cache/apt/archives/lock
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/. |
|
| 2018-05-09 17:16:19 |
Balint Reczey |
affects |
unattended-upgrades (Ubuntu) |
apt (Ubuntu) |
|
| 2018-05-17 15:52:52 |
Balint Reczey |
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 1822, in main
options.dry_run)
File "/usr/bin/unattended-upgrade", line 1399, in do_auto_remove
res, error = cache_commit(cache, logfile_dpkg, verbose)
File "/usr/bin/unattended-upgrade", line 513, in cache_commit
res = cache.commit(install_progress=iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 565, in commit
res = self._fetch_archives(fetcher, pm)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 385, in _fetch_archives
raise LockFailedException("Failed to lock %s" % lockfile)
apt.cache.LockFailedException: Failed to lock /var/cache/apt/archives/lock
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/. |
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/. |
|
| 2018-08-22 10:03:42 |
Julian Andres Klode |
apt (Ubuntu): status |
New |
Triaged |
|
| 2018-08-22 10:03:48 |
Julian Andres Klode |
apt (Ubuntu): importance |
Undecided |
High |
|
