Ubuntu
update-manager package

update-manager crashed with apt_pkg.Error in _open_cache(): E:The repository 'http://ppa.launchpad.net/ehoover/compholio/ubuntu artful Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., E:The repository 'http://ppa.launchpad.net/ehoover/compholio/ubuntu zesty Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., E:The repository 'https://dl.winehq.org/wine-builds/ubuntu artful Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., E:The repository 'http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu artful Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., E:The repository 'http://ppa.launchpad.net/ubuntugis/ubuntugis-unstable/ubuntu zesty Release' does not have a Release file., W:Updating from such a repository can't be done securely, and is therefore disabled by default., W:See apt-secure(8) manpage for repository creation and user configuration details., E:The repository 'http://ppa.launchpad.net/wine/wine-builds/ubuntu artful Release' does not have a Release file.

Bug #1703137 reported by niltomar freitas on 2017-07-08

This bug report is a duplicate of: Bug #1317164: Show reason of TransactionFailed and let the user try again instead of crashing. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	update-manager (Ubuntu)	New	Medium	Unassigned

Bug Description

travou no envio de informações

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: update-manager 1:17.04.3
ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
Uname: Linux 4.10.0-22-generic i686
ApportVersion: 2.20.5-0ubuntu5
Architecture: i386
CrashCounter: 1
CurrentDesktop: GNOME
Date: Sat Jul 8 16:08:02 2017
ExecutablePath: /usr/bin/update-manager
GsettingsChanges:
b'com.ubuntu.update-manager' b'first-run' b'false'
b'com.ubuntu.update-manager' b'launch-time' b'int64 1499540802'
InstallationDate: Installed on 2017-05-14 (54 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release i386 (20170412)
InterpreterPath: /usr/bin/python3.5
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/bin/update-manager --no-update --no-focus-on-map
PythonArgs: ['/usr/bin/update-manager', '--no-update', '--no-focus-on-map']
SourcePackage: update-manager
UpgradeStatus: Upgraded to artful on 2017-06-13 (25 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Tags:

Revision history for this message

niltomar freitas (niltomarfreitas) wrote on 2017-07-08:

Aptdaemon.txt Edit (16.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (13.5 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt.txt Edit (1.4 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt.txt Edit (30.6 KiB, text/plain; charset="utf-8")
JournalErrors.txt Edit (26.7 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (943 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (308 bytes, text/plain; charset="utf-8")
Title.txt Edit (1.6 KiB, text/plain; charset="utf-8")
Traceback.txt Edit (2.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2017-07-11: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1694054, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.