Ubuntu
cups package

package cups-daemon 2.1.3-4 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1

Bug #1671044 reported by John on 2017-03-08

This bug report is a duplicate of: Bug #1642966: package cups-daemon 2.1.3-4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1. Edit Remove

This bug affects 3 people

Affects		Status	Importance	Assigned to	Milestone
	cups (Ubuntu)	Confirmed	Undecided	Unassigned

Bug Description

error while installation wine

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-daemon 2.1.3-4
ProcVersionSignature: Ubuntu 4.8.0-41.44~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-41-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CupsErrorLog:

Date: Wed Mar 8 13:49:06 2017
ErrorMessage: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
InstallationDate: Installed on 2017-03-06 (1 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added.
MachineType: Gigabyte Technology Co., Ltd. GA-970A-UD3
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=9db983ca-3061-4fb4-85e0-1fe61940d5d1 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-41-generic root=UUID=9db983ca-3061-4fb4-85e0-1fe61940d5d1 ro quiet splash vt.handoff=7
RelatedPackageVersions:
dpkg 1.18.4ubuntu1.1
apt 1.2.19
SourcePackage: cups
Title: package cups-daemon 2.1.3-4 failed to install/upgrade: подпроцесс новый сценарий pre-removal возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: GA-970A-UD3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd05/30/2012:svnGigabyteTechnologyCo.,Ltd.:pnGA-970A-UD3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-970A-UD3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-970A-UD3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

Tags:

Revision history for this message

John (sufferingassassin) wrote on 2017-03-08:

AptOrdering.txt Edit (3.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (70.5 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (5.5 KiB, text/plain; charset="utf-8")
Df.txt Edit (700 bytes, text/plain; charset="utf-8")
Dmesg.txt Edit (70.0 KiB, text/plain; charset="utf-8")
DpkgHistoryLog.txt Edit (136.5 KiB, text/plain; charset="utf-8")
DpkgTerminalLog.txt Edit (131.9 KiB, text/plain; charset="utf-8")
HookError_ubuntu.txt Edit (826 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (19.4 KiB, text/plain; charset="utf-8")
KernLog.txt Edit (2.6 KiB, text/plain; charset="utf-8")
Locale.txt Edit (329 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (42.0 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (886 bytes, text/plain; charset="utf-8")
PrintingPackages.txt Edit (1.1 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (9.0 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (4.1 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (4.3 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (191.0 KiB, text/plain; charset="utf-8")

Revision history for this message

Launchpad Janitor (janitor) wrote on 2017-03-27:

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

Changed in cups (Ubuntu):
status:	New → Confirmed

Revision history for this message

Hans Joachim Desserud (hjd) wrote on 2017-03-27:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1676380, so it 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. Feel free to continue to report any other bugs you may find.