update-manager crashed after purging padoka PPA and trying to install an update. Depends in _show_transaction(): zlib1g (>= 1:1.1.4) but 1:1.2.11.dfsg-0ubuntu2 is installed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
update-manager (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
Not sure exactly what I am doing the crash took me here, but I ran into this error when I was trying to get steam to work and it was missing libGL.so.1. I saw in the terminal that it was complaining about a file that the padoka PPA installed, so I purged it and then went to update and thats when update-manager crashed. I ran whatever it said and everything seems to be working for me now.
Ubuntu 17.10
ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: update-manager 1:17.10.11
ProcVersionSign
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 19 16:05:36 2017
ExecutablePath: /usr/bin/
GsettingsChanges:
b'com.
b'com.
b'com.
b'com.
b'com.
InstallationDate: Installed on 2017-10-19 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
InterpreterPath: /usr/bin/python3.6
PackageArchitec
ProcCmdline: /usr/bin/python3 /usr/bin/
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2
PythonArgs: ['/usr/
PythonDetails: /home/richard/
SourcePackage: update-manager
Title: update-manager crashed with Depends in _show_transacti
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
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 #1341176, 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.