[Touch-packages] [Bug 1467202] Re: package cups-daemon 2.0.2-1ubuntu3.1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1467202

Title:
  package cups-daemon 2.0.2-1ubuntu3.1 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in cups package in Ubuntu:
  Expired

Bug description:
  i can't install anything

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: cups-daemon 2.0.2-1ubuntu3.1
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Fri Jun 19 23:32:21 2015
  DuplicateSignature: package:cups-daemon:2.0.2-1ubuntu3.1:el subproceso 
instalado el script post-installation devolvió el código de salida de error 1
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2015-05-06 (45 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: ASUSTeK COMPUTER INC. X450LN
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=8a1ccaaf-6376-4e87-97ba-60f3b593aeaf ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-21-generic 
root=UUID=8a1ccaaf-6376-4e87-97ba-60f3b593aeaf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: cups
  Title: package cups-daemon 2.0.2-1ubuntu3.1 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: Upgraded to vivid on 2015-05-08 (43 days ago)
  dmi.bios.date: 05/21/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X450LN.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X450LN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX450LN.208:bd05/21/2014:svnASUSTeKCOMPUTERINC.:pnX450LN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX450LN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X450LN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1467202/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1468561] Re: package cups-daemon 2.0.3-2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1468561

Title:
  package cups-daemon 2.0.3-2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in cups package in Ubuntu:
  Expired

Bug description:
  Installing on Trusty Tahr

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: cups-daemon 2.0.3-2
  ProcVersionSignature: Error: [Errno 2] No such file or directory: 
'/proc/version_signature'
  Uname: Linux 4.0.0-pf5+ i686
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: i386
  CupsErrorLog:
   
  Date: Thu Jun 25 01:58:34 2015
  DuplicateSignature: package:cups-daemon:2.0.3-2:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-06-22 (2 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: Hewlett-Packard HP ENVY m6 Notebook PC
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.0.0-pf5+ 
root=UUID=3bb9bad1-95f6-4ea2-a616-39fa2aff9b69 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.0.0-pf5+ 
root=UUID=3bb9bad1-95f6-4ea2-a616-39fa2aff9b69 ro quiet splash vt.handoff=7
  SourcePackage: cups
  Title: package cups-daemon 2.0.3-2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 18A5
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 73.50
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd01/21/2013:svnHewlett-Packard:pnHPENVYm6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn18A5:rvr73.50:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY m6 Notebook PC
  dmi.product.version: 088B1130591620100
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-07-22T23:14:46

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1468561/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1268597] Re: doesn't see printers from 1.6 servers

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1268597

Title:
  doesn't see printers from 1.6 servers

Status in cups package in Ubuntu:
  Expired

Bug description:
  On current LTS (Precise) CUPS does not see printers advertised from
  CUPS 1.6 systems.  Yes, I understand that the whole CUPS browse
  feature went away in CUPS 1.6, but that means that current LTS has a
  functionality hole/regression where CUPS 1.6 servers are concerned.

  Fedora has dealt with this for example by supplying cups-browsed.

  Ubuntu, current-LTS should do the same or similar.  LTS systems should
  not be broken simply because other machines it used to get printers
  from upgraded to CUPS 1.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1268597/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1280681] Re: NetworkShare: wrong printing result from windows 7 Samsung SCX-3400

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1280681

Title:
  NetworkShare: wrong printing result from windows 7 Samsung SCX-3400

Status in cups package in Ubuntu:
  Expired

Bug description:
  Hi,

  I have a dual boot machine (Ubuntu 12.04.4, Windows 7). I have
  attached a Samsung SCX-3400 to this machine (server) via USB. It was
  detected and suggested the Samsung SCX.3200 driver. The test page was
  printed out well. I tired to share this printer, I followed the ubuntu
  howto guides. I was able to see it from a lapot(client, windows 7) via
  samba and add it, or via the
  http://x.y.z.n:631/printers/Samsung-3400-SCX way. I was able to start
  printing from windows, printing had happend, but the result was wrong.
  It is someting the follwoing:

  -12345@PJL COMMENT "Usernam: windows_username"
  @PJL COMMENT USERNAME="X"
  @PJL COMMENT DOCNAME="YY"
  @PJL SET COPIES=1
  
  ...

  I've tried out to print from windos to windows and it was working. 
  After I tried to reinstall the printer under ubuntu with the Samsung Unified 
Driver for Linux, but the result is the same: can be seen from windows, start 
printing but the result is wrong.
   
  What can I do to share this printer the right way to get the right 

  Thanks and regards,
  Mark

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu8
  ProcVersionSignature: Ubuntu 3.11.0-17.31~precise1-generic 3.11.10.3
  Uname: Linux 3.11.0-17-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Sat Feb 15 22:21:56 2014
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Lpstat: device for SCX-3400-Series: 
usb://Samsung/SCX-3400%20Series?serial=Z6RRBFEC201095V=1
  MachineType: Gigabyte Technology Co., Ltd. GA-MA785GMT-UD2H
  MarkForUpload: True
  Papersize: letter
  PpdFiles: SCX-3400-Series: Samsung SCX-3400 Series
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-17-generic 
root=UUID=089cc211-9d8a-4bfc-aaf4-92b95fb25515 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F10b
  dmi.board.name: GA-MA785GMT-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF10b:bd07/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA785GMT-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA785GMT-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-MA785GMT-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1280681/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1261000] Re: package cups-daemon 1.7.0~rc1-0ubuntu5.1 failed to install/upgrade: Package is in a very bad inconsistent state - you should reinstall it before attempting configura

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1261000

Title:
  package cups-daemon 1.7.0~rc1-0ubuntu5.1 failed to install/upgrade:
  Package is in a very bad inconsistent state - you should  reinstall it
  before attempting configuration.

Status in cups package in Ubuntu:
  Expired

Bug description:
  This was an automatic error generated during software update.

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: cups-daemon 1.7.0~rc1-0ubuntu5.1
  ProcVersionSignature: Ubuntu 3.11.0-15.22-generic 3.11.10
  Uname: Linux 3.11.0-15-generic x86_64
  NonfreeKernelModules: nvidia ohci_pci
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Dec 14 08:50:39 2013
  DuplicateSignature: package:cups-daemon:1.7.0~rc1-0ubuntu5.1:Package is in a 
very bad inconsistent state - you should  reinstall it before attempting 
configuration.
  ErrorMessage: Package is in a very bad inconsistent state - you should  
reinstall it before attempting configuration.
  InstallationDate: Installed on 2013-01-11 (336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  Lpstat: device for HP-Officejet-6700: hp:/net/Officejet_6700?zc=HP6C3BE594E3E4
  Lsusb:
   Bus 001 Device 003: ID 04b8:011b Seiko Epson Corp. GT-9300UF [Perfection 
2400 PHOTO]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0763:0150 Midiman M-Audio Uno
   Bus 002 Device 002: ID 046d:c018 Logitech, Inc. Optical Wheel Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Compaq-Presario KQ513AAR-ABA SR5510F
  MarkForUpload: True
  Papersize: letter
  PpdFiles: HP-Officejet-6700: HP Officejet 6700, hpcups 3.13.3
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=b59ff550-9ef4-432f-b3f8-a3958019342e ro quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-15-generic 
root=UUID=b59ff550-9ef4-432f-b3f8-a3958019342e ro quiet splash
  SourcePackage: cups
  Title: package cups-daemon 1.7.0~rc1-0ubuntu5.1 failed to install/upgrade: 
Package is in a very bad inconsistent state - you should  reinstall it before 
attempting configuration.
  UpgradeStatus: Upgraded to saucy on 2013-10-22 (52 days ago)
  dmi.bios.date: 06/10/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.27
  dmi.board.name: Iris8
  dmi.board.vendor: ECS
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.27:bd06/10/2008:svnCompaq-Presario:pnKQ513AAR-ABASR5510F:pvr:rvnECS:rnIris8:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: KQ513AAR-ABA SR5510F
  dmi.sys.vendor: Compaq-Presario

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1261000/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1477002] Re: Working printer not printing

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1477002

Title:
  Working  printer not printing

Status in cups package in Ubuntu:
  Expired

Bug description:
  Print Jobs get pending or paused

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.6
  ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
  Uname: Linux 3.13.0-57-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CupsErrorLog:
   E [22/Jul/2015:12:12:19 +0530] [Job 73] Stopping unresponsive job.
   E [22/Jul/2015:13:02:16 +0530] [Job 82] Stopping unresponsive job.
   E [22/Jul/2015:13:46:08 +0530] [Job 82] Stopping unresponsive job.
  CurrentDesktop: Unity
  Date: Wed Jul 22 13:46:44 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-11-04 (260 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat: device for HP_LaserJet_1020: hp:/usb/HP_LaserJet_1020?serial=FN0BRGG
  Lsusb:
   Bus 001 Device 011: ID 03f0:2b17 Hewlett-Packard LaserJet 1020
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 413c:2107 Dell Computer Corp. 
   Bus 002 Device 002: ID 04ca:0061 Lite-On Technology Corp. 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Kobian PNMCP73V
  Papersize: a4
  PpdFiles: HP_LaserJet_1020: HP LaserJet 1020, hpcups 3.14.3, requires 
proprietary plugin
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-57-generic 
root=UUID=aeacc5b2-89c8-4b7a-94ad-fcd6e38d603b ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/23/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: PNMCP73V
  dmi.board.vendor: Kobian
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Kobian
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd10/23/2007:svnKobian:pnPNMCP73V:pvr1.0:rvnKobian:rnPNMCP73V:rvr1.0:cvnKobian:ct3:cvr1.0:
  dmi.product.name: PNMCP73V
  dmi.product.version: 1.0
  dmi.sys.vendor: Kobian

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1477002/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1268369] Re: package cups 1.6.1-0ubuntu11.4 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1268369

Title:
  package cups 1.6.1-0ubuntu11.4 failed to install/upgrade: le sous-
  processus script post-installation installé a retourné une erreur de
  sortie d'état 1

Status in cups package in Ubuntu:
  Expired

Bug description:
  I was installing upgrading from Ubuntu 12.04 to 12.10 when I Had to
  rebbot before entire completion of the process I think.

  This might be the cause of the problem.

  After the first reboot (after the tentative of upgrade) I had no
  launcher nor upper icons on the screen.

  I rebooted in fail-safe mode and :
  1- rebuilt the grub
  2- repaired the broken paqquets

  I must say I'm quite new on Ubuntu (3 weeks).

  Hope this will help.

  Regards

  ProblemType: Package
  DistroRelease: Ubuntu 12.10
  Package: cups 1.6.1-0ubuntu11.4
  ProcVersionSignature: Ubuntu 3.8.0-35.50~precise1-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Sun Jan 12 22:09:50 2014
  DuplicateSignature: package:cups:1.6.1-0ubuntu11.4:le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Transport endpoint is not connected
  MachineType: Hewlett-Packard HPE-430fr
  MarkForUpload: True
  Papersize: a4
  PpdFiles: Deskjet-F4100-series: HP Deskjet f4100 Series, hpcups 3.12.2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-35-generic 
root=UUID=27b8a339-acc6-440b-b04b-498c67e1483d ro recovery nomodeset
  SourcePackage: cups
  Title: package cups 1.6.1-0ubuntu11.4 failed to install/upgrade: le 
sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.13
  dmi.board.name: 2A9C
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: CZC043013F
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.13:bd10/06/2010:svnHewlett-Packard:pnHPE-430fr:pvrxxx0204GR0:rvnMSI:rn2A9C:rvr1.0:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HPE-430fr
  dmi.product.version: xxx0204GR0
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1268369/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1397491] Re: /etc/init.d/cups restart or stop failure

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1397491

Title:
  /etc/init.d/cups restart or stop failure

Status in cups package in Ubuntu:
  Expired

Bug description:
  I've observed on several occasions that i've been unable to get the
  cups daemon to respond to changes in configuration files and have been
  unable to log in as administrator via the web interface when i know
  that i should be able to; even though i did "/etc/init.d/cups
  restart". Finally figured it out! I did "/etc/init.d/cups stop" and
  using ps noticed 4 or 5 cupsd processes running! After killing all
  these off (oddly enough, a new one was spawned in their place), i did
  "/etc/init.d/cups start" and all was well!

  Based on my web search (which lead me to try this) this problem has
  been around for several years... sigh.

  Thanks to whoever might bring sanity to this.

  # lsb_release -rd
  Description:  Ubuntu 14.04.1 LTS
  Release:  14.04
  # apt-cache policy cups
  cups:
Installed: 1.7.2-0ubuntu1.2
Candidate: 1.7.2-0ubuntu1.2
Version table:
   *** 1.7.2-0ubuntu1.2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
  100 /var/lib/dpkg/status
   1.7.2-0ubuntu1 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1397491/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1475916] Re: package cups-core-drivers (not installed) failed to install/upgrade: package cups-core-drivers is not ready for configuration cannot configure (current status `half-

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1475916

Title:
  package cups-core-drivers (not installed) failed to install/upgrade:
  package cups-core-drivers is not ready for configuration  cannot
  configure (current status `half-installed')

Status in cups package in Ubuntu:
  Expired

Bug description:
  When i turn on my computer

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: cups-core-drivers (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19
  Uname: Linux 3.13.0-53-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  Date: Sun Jul 12 08:36:04 2015
  DuplicateSignature: package:cups-core-drivers:(not installed):package 
cups-core-drivers is not ready for configuration  cannot configure (current 
status `half-installed')
  ErrorMessage: package cups-core-drivers is not ready for configuration  
cannot configure (current status `half-installed')
  InstallationDate: Installed on 2015-05-23 (55 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat: Error: [Errno 2] No such file or directory: 'lpstat'
  MachineType: Dell Inc. Inspiron 1545
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/vmlinuz-3.13.0-53-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-53-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  Title: package cups-core-drivers (not installed) failed to install/upgrade: 
package cups-core-drivers is not ready for configuration  cannot configure 
(current status `half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/27/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0U315R
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/27/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0U315R:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1545
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1475916/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1411431] Re: Make cupsd determine language based on LANG enviroment variable (at least) if nothing is set up in cupsd.conf

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1411431

Title:
  Make cupsd determine language based on LANG enviroment variable (at
  least) if nothing is set up in cupsd.conf

Status in cups package in Ubuntu:
  Expired

Bug description:
  If the environment variable `LANG` is set and there's no language
  related option set in `cupsd.conf`, there's no reason to not let
  `cupsd` determine it's language based on the variable. IMO the default
  setting in `cupsd.conf` could be that `cupsd`'s language setting is
  determined based on LANG, too.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.5-3ubuntu2
  ProcVersionSignature: Error: [Errno 2] Datei oder Verzeichnis nicht gefunden: 
'/proc/version_signature'
  Uname: Linux 3.18.2-031802-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan 15 23:02:22 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-01-03 (12 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  KernLog:
   
  Lpstat: device for PDF: cups-pdf:/
  MachineType: LENOVO 20221
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/PDF.ppd'] failed with exit code 2: grep: /etc/cups/ppd/PDF.ppd: 
Permission denied
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.18.2-031802-generic 
root=UUID=733be919-1a8c-447d-ae30-c7b1cc533a1b ro recovery rootflags=subvol=@
  SourcePackage: cups
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 71CN51WW(V1.21)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: 3193WIN8 STD MLT
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad Z500 Touch
  dmi.modalias: 
dmi:bvnLENOVO:bvr71CN51WW(V1.21):bd07/12/2013:svnLENOVO:pn20221:pvrLenovoIdeaPadZ500Touch:rvnLENOVO:rnINVALID:rvr3193WIN8STDMLT:cvnLENOVO:ct10:cvrLenovoIdeaPadZ500Touch:
  dmi.product.name: 20221
  dmi.product.version: Lenovo IdeaPad Z500 Touch
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1411431/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1448437] Re: package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1448437

Title:
  package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade:
  Unterprozess installiertes post-installation-Skript gab den Fehlerwert
  1 zurück

Status in cups package in Ubuntu:
  Expired

Bug description:
  

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: cups-daemon 2.0.2-1ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sat Apr 25 13:07:51 2015
  DuplicateSignature: package:cups-daemon:2.0.2-1ubuntu3:Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: MSI MS-7698
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=3da65b78-a364-489f-b0e7-11677d09169b ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=3da65b78-a364-489f-b0e7-11677d09169b ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: cups
  Title: package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: 
Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: E350IA-E45 (MS-7698)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.5:bd04/22/2011:svnMSI:pnMS-7698:pvr1.0:rvnMSI:rnE350IA-E45(MS-7698):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7698
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-06-17T22:24:48.517392

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1448437/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1432414] Re: printing service not available after recent upgrade

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1432414

Title:
  printing service not available after recent upgrade

Status in cups package in Ubuntu:
  Expired
Status in ssl-cert package in Ubuntu:
  Expired

Bug description:
  Prior to a recent update, the wireless printer worked fine, now the
  system settings printing configuration says that "Printing service not
  available. Start the service on this computer or connect to another
  server." The "Start Service" button is greyed out leaving just the
  "Connect" button. When clicked it brings up a dialog asking where the
  cups server is located, default is localhost, and an unchecked
  checkbox for "Require encryption." Click the "Continue" button and get
  an error message: "There was an error during the CUPS operation:
  'failed to connect to server'."

  Looking at the cups error log, this message is printed:
  E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.crt" is a bad symlink - 
No such file or directory
  E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.key" is a bad symlink - 
No such file or directory

  It seems the ssl-cert package's snakeoil certs were removed by
  something, reinstalling that package restored the ssl files the above
  links point to.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.5-3ubuntu3.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CupsErrorLog:
   E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.crt" is a bad symlink - 
No such file or directory
   E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.key" is a bad symlink - 
No such file or directory
  CurrentDesktop: Unity
  Date: Sun Mar 15 14:46:34 2015
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: System76, Inc. Wild Dog Performance
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-7520.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-7520.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=968bc182-d0be-4b2c-9558-2a6d5af9b400 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2306
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: wilp11
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2306:bd10/09/2014:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp11:rvnASUSTeKCOMPUTERINC.:rnH97-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrwilp11:
  dmi.product.name: Wild Dog Performance
  dmi.product.version: wilp11
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1432414/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1432414] Re: printing service not available after recent upgrade

2018-10-17 Thread Launchpad Bug Tracker
[Expired for ssl-cert (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ssl-cert (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1432414

Title:
  printing service not available after recent upgrade

Status in cups package in Ubuntu:
  Expired
Status in ssl-cert package in Ubuntu:
  Expired

Bug description:
  Prior to a recent update, the wireless printer worked fine, now the
  system settings printing configuration says that "Printing service not
  available. Start the service on this computer or connect to another
  server." The "Start Service" button is greyed out leaving just the
  "Connect" button. When clicked it brings up a dialog asking where the
  cups server is located, default is localhost, and an unchecked
  checkbox for "Require encryption." Click the "Continue" button and get
  an error message: "There was an error during the CUPS operation:
  'failed to connect to server'."

  Looking at the cups error log, this message is printed:
  E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.crt" is a bad symlink - 
No such file or directory
  E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.key" is a bad symlink - 
No such file or directory

  It seems the ssl-cert package's snakeoil certs were removed by
  something, reinstalling that package restored the ssl files the above
  links point to.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: cups 1.7.5-3ubuntu3.1
  ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CupsErrorLog:
   E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.crt" is a bad symlink - 
No such file or directory
   E [15/Mar/2015:09:26:48 -0400] "/etc/cups/ssl/server.key" is a bad symlink - 
No such file or directory
  CurrentDesktop: Unity
  Date: Sun Mar 15 14:46:34 2015
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: System76, Inc. Wild Dog Performance
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-7520.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-7520.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-31-generic 
root=UUID=968bc182-d0be-4b2c-9558-2a6d5af9b400 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2306
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: wilp11
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2306:bd10/09/2014:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp11:rvnASUSTeKCOMPUTERINC.:rnH97-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrwilp11:
  dmi.product.name: Wild Dog Performance
  dmi.product.version: wilp11
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1432414/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1459305] Re: log to journald by default

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1459305

Title:
  log to journald by default

Status in cups package in Ubuntu:
  Expired

Bug description:
  For quite some time now CUPS support structured logging to journald,
  see http://cyberelk.net/tim/2013/10/25/cups-adding-support-for-system-
  journal/

  With the move to systemd stack it would be beneficial to switch to
  cups logging to journald by default so the additional information
  could be stored in structured and secure manner.

  The only required change is to replace following lines in /etc/cups
  /cups-files.conf:

  AccessLog journal
  ErrorLog journal
  PageLog journal

  Users wishing to preserve old behavior with insecure logging would
  utilize standard dpkg request about configuration change on upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1459305/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1311294] Re: /etc/init.d/cups restart | stop -- is not killing cups processes and fails to completely restart or stop cups. Could be the dbus notifier is ignoring the request

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1311294

Title:
  /etc/init.d/cups restart | stop  -- is not killing cups processes and
  fails to completely restart or stop cups.  Could be the dbus notifier
  is ignoring the request

Status in cups package in Ubuntu:
  Expired

Bug description:
  After changing cupsd.conf had to kill all cups processes by hand to
  have the change take effect.

  joebrown@sol:~$ ps aux|grep cups
  root 24107  0.0  0.0  73072  3180 ?Ss   14:38   0:00 
/usr/sbin/cups-browsed
  root 25828  0.2  0.1 155664  4116 ?Ssl  15:31   0:00 
/usr/sbin/cupsd -C /etc/cups/cupsd.conf
  root 25838  0.0  0.0 148600  4012 ?Ssl  15:31   0:00 
/usr/sbin/cupsd -F
  lp   25844  0.0  0.0  52420  1780 ?S15:31   0:00 
/usr/lib/cups/notifier/dbus dbus:// 
  lp   25848  0.0  0.0  52420  1776 ?S15:31   0:00 
/usr/lib/cups/notifier/dbus dbus:// 
  joebrown 25872  0.0  0.0  13644   908 pts/1S+   15:33   0:00 grep 
--color=auto cups
  joebrown@sol:~$ sudo restart cups
  cups start/running, process 25893
  joebrown@sol:~$ ps aux|grep cups
  root 24107  0.0  0.0  73072  3180 ?Ss   14:38   0:00 
/usr/sbin/cups-browsed
  root 25828  0.2  0.1 155664  4128 ?Ssl  15:31   0:00 
/usr/sbin/cupsd -C /etc/cups/cupsd.conf
  lp   25844  0.0  0.0  52420  1780 ?S15:31   0:00 
/usr/lib/cups/notifier/dbus dbus:// 
  root 25893  1.7  0.0 148480  3812 ?Ssl  15:33   0:00 
/usr/sbin/cupsd -F
  lp   25900  0.0  0.0  52420  1776 ?S15:33   0:00 
/usr/lib/cups/notifier/dbus dbus:// 
  joebrown 25910  0.0  0.0  13644   904 pts/1S+   15:33   0:00 grep 
--color=auto cups

  -- one dbus notifier process id changed???  Isn't there only supposed
  to be one?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: cups 1.7.0~rc1-0ubuntu5.2
  ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: amd64
  Date: Tue Apr 22 15:28:14 2014
  InstallationDate: Installed on 2013-11-21 (151 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Lpstat: device for ClaimsPrinter: socket://192.168.96.207
  MachineType: Dell Inc. PowerEdge 2900
  MarkForUpload: True
  Papersize: letter
  PpdFiles:
   HP-LaserJet-P4014-2: HP LaserJet P4010 Series Postscript (recommended)
   ClaimsPrinter: Generic PCL 5c LF Printer - CUPS+Gutenprint v5.2.9
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to saucy on 2013-11-22 (151 days ago)
  dmi.bios.date: 03/26/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.7
  dmi.board.name: 0TM757
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 17
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.7:bd03/26/2007:svnDellInc.:pnPowerEdge2900:pvr:rvnDellInc.:rn0TM757:rvrA00:cvnDellInc.:ct17:cvr:
  dmi.product.name: PowerEdge 2900
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1311294/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1336822] Re: CUPS ignores page output order for some Brother printers

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1336822

Title:
  CUPS ignores page output order for some Brother printers

Status in cups package in Ubuntu:
  Expired

Bug description:
  Printer I am using is DCP197C.

  1. Install drivers from 
http://support.brother.com/g/s/id/linux/en/download_prn.html#DCP-197C
  (both lpr and cupswrapper are required)
  2. Try to print a document with multiple pages
  3. Document is output in wrong order (last page prints last instead of first, 
so you have to rearrange the printed document by hand)
  4. Run system-config-printer and change 'Reverse Printing' to 'On' in printer 
options
  5. Do a test print to find this has no effect
  6. In 'Job options', click 'More' under common options and change 'Output 
order' to 'Reverse'
  7. Do a test print to find this has no effect

  The only workaround I have found, which was really not obvious at all,
  was to edit /etc/cups/printers.conf, and add

  Option outputorder normal

  before the closing  tag of the relevant printer.

  I have only tested this under DCP197C but I expect similar printers in
  the series (including DCP195C) would also suffer from this problem.
  Perhaps it is caused by the recently introduced introduction of using
  PDF as the default job format instead of postscript

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2
  Uname: Linux 3.13.0-30-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jul  2 15:55:27 2014
  InstallationDate: Installed on 2014-06-30 (2 days ago)
  InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  Lpstat: device for DCP197C: usb://Brother/DCP-197C?serial=BROG0F178003
  MachineType: Packard Bell BV IMEDIA B2217 UK
  Papersize: a4
  PpdFiles: DCP197C: Brother DCP-197C CUPS
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic 
root=UUID=c1bfcc97-458f-491b-a61e-9c364bf5e152 ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: PBDV10.P18
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MCP73VT-PM
  dmi.board.vendor: Packard Bell BV
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Packard Bell BV
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrPBDV10.P18:bd09/10/2008:svnPackardBellBV:pnIMEDIAB2217UK:pvrPTU050Y007:rvnPackardBellBV:rnMCP73VT-PM:rvr1.0:cvnPackardBellBV:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: IMEDIA B2217 UK
  dmi.product.version: PTU050Y007
  dmi.sys.vendor: Packard Bell BV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1336822/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1351036] Re: Printer starts job from beginning after system suspend/resume

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1351036

Title:
  Printer starts job from beginning after system suspend/resume

Status in cups package in Ubuntu:
  Expired

Bug description:
  While I was printing a 40 pages job on a Canon Pixma 2450 the system
  suspended and the printer stopped in the middle of a page. After
  resume, I had to start the printer in the "Printer" dialog (control
  panel), because it was paused. Immediatly the printer started the job
  ("in progress") from the first page instead of the last page sent to
  the printer.

  I think cups should either prevent system suspend or continue at the
  last page (double-page if duplex enabled) after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jul 31 22:05:15 2014
  InstallationDate: Installed on 2014-06-29 (32 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Lpstat: device for Pixma: dnssd://Canon%20MG4200%20series._ipp._tcp.local/
  MachineType: Sony Corporation VPCSE2M9E
  Papersize: a4
  PpdFiles: Pixma: Canon MG4200 series - CUPS+Gutenprint v5.2.10-pre2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic 
root=UUID=13b2eae0-0ebf-4623-add9-47dfd649e9d9 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R2087H4
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR2087H4:bd06/15/2012:svnSonyCorporation:pnVPCSE2M9E:pvrC60A4NZ8:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: VPCSE2M9E
  dmi.product.version: C60A4NZ8
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1351036/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1426245] Re: package cups 1.5.3-0ubuntu8.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1, routine dist-upgrade fails becau

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1426245

Title:
  package cups 1.5.3-0ubuntu8.6 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1,
  routine dist-upgrade fails because there is no existing cupsd.conf

Status in cups package in Ubuntu:
  Expired

Bug description:
  C [27/Feb/2015:09:18:06 +0200] Unable to open /etc/cups/cupsd.conf: No
  such file or directory

  The system is a clean 12.04 LTS, there probably never was need for
  this file.

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: cups 1.5.3-0ubuntu8.6
  ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66
  Uname: Linux 3.2.0-76-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.8
  AptOrdering: cups: Configure
  Architecture: amd64
  Date: Fri Feb 27 09:18:06 2015
  DpkgTerminalLog:
   Setting up cups (1.5.3-0ubuntu8.6) ...
   start: Job failed to start
   invoke-rc.d: initscript cups, action "start" failed.
   dpkg: error processing cups (--configure):
subprocess installed post-installation script returned error exit status 1
  DuplicateSignature: package:cups:1.5.3-0ubuntu8.6:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100427.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: 
Connection refused
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 003: ID 04f2:b15e Chicony Electronics Co., Ltd
  MachineType: Hewlett-Packard HP EliteBook 8440p
  MarkForUpload: True
  Papersize: letter
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-76-generic 
root=UUID=0f2443c2-f077-49b4-939b-f51e6e22d04b ro i915.modeset=1
  SourcePackage: cups
  Title: package cups 1.5.3-0ubuntu8.6 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to precise on 2014-01-19 (403 days ago)
  dmi.bios.date: 09/13/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CCU Ver. F.24
  dmi.board.name: 172A
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 30.34
  dmi.chassis.asset.tag: CZC0487PDG
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CCUVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8440p:pvr:rvnHewlett-Packard:rn172A:rvrKBCVersion30.34:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8440p
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.cups.cups.files.conf: [deleted]
  modified.conffile..etc.cups.cupsd.conf: [deleted]
  modified.conffile..etc.cups.cupsd.conf.default: [deleted]
  modified.conffile..etc.cups.snmp.conf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1426245/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1418326] Re: "lpr -p -P PDF" (prettyprint) hangs print job with sample string

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1418326

Title:
  "lpr -p -P PDF" (prettyprint) hangs print job with sample string

Status in cups package in Ubuntu:
  Expired

Bug description:
  
  $ echo '// static' | lpr -p -P PDF# Fails somewhere - print job hangs

  $ lpstat -o PDF
  PDF-169 dave  1024   Thu 05 Feb 2015 03:45:14 GMT

  $ lpstat -t#  [output snipped] ...
  printer PDF is idle.  enabled since Thu 05 Feb 2015 03:45:14 GMT
  loadFile failed: temp file: not a PDF file
  PDF-169 dave  1024   Thu 05 Feb 2015 03:45:14 GMT

  # CUPS reports "Filter failed" in web interface:
  # PDF-169  Unknown  Withheld  1k  1 stopped  "Filter failed"

  # RESET (remove job)
  $ lprm -P PDF; lpstat -o PDF
  $

  Here are a few examples which *do not* cause a problem:

  $ echo '// tatic' | lpr -p -P PDF
  $ lpstat -o PDF
  $

  $ echo '// stati' | lpr -p -P PDF
  $ lpstat -o PDF
  $

  $ echo '/ static' | lpr -p -P PDF
  $ lpstat -o PDF
  $

  $ echo ' static' | lpr -p -P PDF
  $ lpstat -o PDF
  $

  $ echo '/static' | lpr -p -P PDF
  $ lpstat -o PDF
  $

  $ echo 'static' | lpr -p -P PDF
  $ lpstat -o PDF
  $

  $ echo '  //   static' | lpr -p -P PDF
  $ lpstat -o PDF
  $

  
  Now I'm bored ;-)

  $ echo '//   static' | lpr -p -P PDF
  $ lpstat -o PDF
  PDF-175 dave  1024   Thu 05 Feb 2015 04:31:25 GMT
  $

  I hope there are some clues, there.  I'm assuming you will get my
  system info from the "ubuntu-bug cups" I did.

  Dave

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
  Uname: Linux 3.13.0-45-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Feb  5 03:56:02 2015
  InstallationDate: Installed on 2014-09-08 (149 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Lpstat:
   device for EPSON_XP-312: 
dnssd://EPSON%20XP-312%20313%20315%20Series._ipp._tcp.local/
   device for PDF: cups-pdf:/
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  Papersize: a4
  PpdFiles:
   PDF: Generic CUPS-PDF Printer
   EPSON_XP-312: Epson XP-312 313 315 Series - epson-inkjet-printer 
1.0.0-1lsb3.2 (Seiko Epson Corporation LSB 3.2)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic 
root=UUID=ec73b7e0-d4a3-4a87-852b-085668e2b46b ro quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1708:bd04/10/2013:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97R2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1418326/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1429444] Re: printing webpages in landscape prints a cropped portrait instead

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1429444

Title:
  printing webpages in landscape prints a cropped portrait instead

Status in cups package in Ubuntu:
  Expired

Bug description:
  Steps to reproduce:

  1. Open this Google map in a web browser: 
https://www.google.com/maps/place/SpringHill+Suites+Florence/@34.1885035,-79.8385784,16z/data=!4m9!1m6!2m5!1shotels!3m3!1shotels!2sFlorence,+SC!3s0x885566d61ff10fe9:0xac3c3b81f5d91e2a!3m1!1s0x:0x0f6c640354e822a9
  2. Do a print preview.
  3. Switch to landscape mode. Note how the print preview appears.
  4. Print.

  Expected result:

  The printer prints as shown in the print preview.

  Actual result:

  The printer prints landscape content, but oriented portrait the paper,
  with the right portion of the content cropped. (See attached photo.)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.5
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Sat Mar  7 14:00:54 2015
  Lpstat: device for MFCJ825DW: dnssd://Brother%20MFC-J825DW._ipp._tcp.local/
  Lsusb:
   Bus 001 Device 004: ID 045e:0728 Microsoft Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
   Bus 002 Device 003: ID 0461:4d16 Primax Electronics, Ltd 
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Papersize: letter
  PpdFiles: MFCJ825DW: Brother MFC-J825DW CUPS
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-46-generic 
root=UUID=cb832714-a26f-4f20-a85f-de2b92164bcb ro
  SourcePackage: cups
  UpgradeStatus: Upgraded to trusty on 2014-05-30 (281 days ago)
  dmi.bios.date: 02/10/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FHm
  dmi.board.name: M57SLI-S4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFHm:bd02/10/2010:svn:pn:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM57SLI-S4:rvrx.x:cvn:ct3:cvr:
  mtime.conffile..etc.cups.cupsd.conf: 2015-03-07T13:12:49.170536

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1429444/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1484213] Re: package cups 2.0.2-1ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1484213

Title:
  package cups 2.0.2-1ubuntu3.2 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in cups package in Ubuntu:
  Expired

Bug description:
  It just appeared after sudo apt-get install virtualbox

  ProblemType: Package
  DistroRelease: Ubuntu Kylin 14.10
  Package: cups 2.0.2-1ubuntu3.2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sun Aug  9 15:12:40 2015
  DuplicateSignature: package:cups:2.0.2-1ubuntu3.2:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-04-01 (133 days ago)
  InstallationMedia: Ubuntu-Kylin 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Acer Aspire E5-511
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=dd7f283a-4a5f-4982-aa97-423878f612e3 ro locale=zh_CN quiet splash 
init=/lib/systemd/systemd
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic 
root=UUID=dd7f283a-4a5f-4982-aa97-423878f612e3 ro locale=zh_CN quiet splash 
init=/lib/systemd/systemd
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: cups
  Title: package cups 2.0.2-1ubuntu3.2 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2014
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.03
  dmi.board.name: Aspire E5-511
  dmi.board.vendor: Acer
  dmi.board.version: V1.03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAcer:bvrV1.03:bd05/16/2014:svnAcer:pnAspireE5-511:pvrV1.03:rvnAcer:rnAspireE5-511:rvrV1.03:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-511
  dmi.product.version: V1.03
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1484213/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1484607] Re: package cups-daemon 1.7.5-3ubuntu3.2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le co

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1484607

Title:
  package cups-daemon 1.7.5-3ubuntu3.2 failed to install/upgrade: le
  paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

Status in cups package in Ubuntu:
  Expired

Bug description:
  I suppose it is because I manually  (and incorrectly) installed 32 bit
  driver for  Epson acculaser C 1100.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: cups-daemon 1.7.5-3ubuntu3.2
  ProcVersionSignature: Ubuntu 3.16.0-44.59-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-44-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: amd64
  Date: Tue Aug 11 16:12:03 2015
  DpkgHistoryLog:
   Start-Date: 2015-08-11  16:11:46
   Commandline: /usr/sbin/synaptic
   Install: liblqr-1-0:amd64 (0.4.2-1ubuntu1, automatic), libwmf-bin:amd64 
(0.2.8.4-10.3ubuntu1.14.10.1, automatic), python-numpy:amd64 (1.8.2-1ubuntu1, 
automatic), perlmagick:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), 
libmagickcore5-extra:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), inkscape:amd64 
(0.48.5-2ubuntu1), libgsl0ldbl:amd64 (1.16+dfsg-2, automatic), 
libmagickwand5:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), imagemagick:amd64 
(6.7.7.10+dfsg-4ubuntu1, automatic), libgnomevfs2-extra:amd64 (2.24.4-6ubuntu1, 
automatic), libmagickcore5:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), 
libmagick++5:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic), 
imagemagick-common:amd64 (6.7.7.10+dfsg-4ubuntu1, automatic)
  DuplicateSignature: package:cups-daemon:1.7.5-3ubuntu3.2:le paquet est dans 
un état vraiment incohérent; vous devriez  le réinstaller avant de tenter de le 
configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2015-07-04 (40 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  Lpstat: device for EPSON-AL-C1100: 
usb://EPSON/AL-C1100?serial=31PF2PZ19022650913
  MachineType: LENOVO 10117
  Papersize: a4
  PpdFiles: EPSON-AL-C1100: EPSON AL-C1100, ESC/PageS Filter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic.efi.signed 
root=UUID=507dcaf9-8dce-4a45-9d98-fa888e417136 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-44-generic.efi.signed 
root=UUID=507dcaf9-8dce-4a45-9d98-fa888e417136 ro quiet splash vt.handoff=7
  SourcePackage: cups
  Title: package cups-daemon 1.7.5-3ubuntu3.2 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I7KT32AUS
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058 STD or WIN
  dmi.chassis.type: 3
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvrI7KT32AUS:bd12/26/2013:svnLENOVO:pn10117:pvrLenovoH535:rvnLENOVO:rn:rvr31900058STDorWIN:cvnLENOVO:ct3:cvr:
  dmi.product.name: 10117
  dmi.product.version: Lenovo H535
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.init.d.cups: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1484607/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1480560] Re: package cups-common 2.0.2-1ubuntu3 failed to install/upgrade: el paquete cups-common no está listo para configurarse no se puede configurar (estado actual `half-ins

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1480560

Title:
  package cups-common 2.0.2-1ubuntu3 failed to install/upgrade: el
  paquete cups-common no está listo para configurarse  no se puede
  configurar (estado actual `half-installed')

Status in cups package in Ubuntu:
  Expired

Bug description:
  It said, cup package was wrong. And I unisntall it.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: cups-common 2.0.2-1ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CupsErrorLog: E [01/Aug/2015:09:27:01 -0500] Filter "rastertopwg" not found.
  Date: Sat Aug  1 09:24:17 2015
  Dependencies:
   
  DpkgHistoryLog:
   Start-Date: 2015-08-01  09:24:03
   Commandline: /usr/sbin/synaptic
   Remove: cups-driver-gutenprint:amd64 (5.2.10-3build1), lubuntu-desktop:amd64 
(0.59), printer-driver-gutenprint:amd64 (5.2.10-3build1)
   Purge: cups-client:amd64 (2.0.2-1ubuntu3.2), cups:amd64 (2.0.2-1ubuntu3.2), 
cups-ppdc:amd64 (2.0.2-1ubuntu3.2)
  DuplicateSignature: package:cups-common:2.0.2-1ubuntu3:el paquete cups-common 
no está listo para configurarse  no se puede configurar (estado actual 
`half-installed')
  ErrorMessage: el paquete cups-common no está listo para configurarse  no se 
puede configurar (estado actual `half-installed')
  InstallationDate: Installed on 2015-07-29 (3 days ago)
  InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lpstat: Error: [Errno 2] No existe el archivo o el directorio: 'lpstat'
  MachineType: Acer, inc. Aspire 4520
  PackageArchitecture: all
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=896108a8-acf9-4c09-9290-817f63831aa9 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-15-generic 
root=UUID=896108a8-acf9-4c09-9290-817f63831aa9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: cups
  Title: package cups-common 2.0.2-1ubuntu3 failed to install/upgrade: el 
paquete cups-common no está listo para configurarse  no se puede configurar 
(estado actual `half-installed')
  UdevLog: Error: [Errno 2] No existe el archivo o el directorio: 
'/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/14/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3632
  dmi.board.name: Mono
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.3632:bd05/14/2008:svnAcer,inc.:pnAspire4520:pvrNotApplicable:rvnAcer,Inc.:rnMono:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 4520
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1480560/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1490182] Re: package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: 子进程 已安装 post-installation 脚本 返回错误状态 1

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1490182

Title:
  package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: 子进程 已安装
  post-installation 脚本 返回错误状态 1

Status in cups package in Ubuntu:
  Expired

Bug description:
  ...
   python3-pyqt5
   python3-pyqt5-dbg
  由于出现了太多错误,处理过程被中止了。
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: cups-daemon 2.0.2-1ubuntu3
  ProcVersionSignature: Error: [Errno 2] 没有那个文件或目录: '/proc/version_signature'
  Uname: Linux 4.1.2-040102-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.13
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sun Aug 30 02:34:04 2015
  DuplicateSignature: package:cups-daemon:2.0.2-1ubuntu3:子进程 已安装 
post-installation 脚本 返回错误状态 1
  ErrorMessage: 子进程 已安装 post-installation 脚本 返回错误状态 1
  InstallationDate: Installed on 2014-12-27 (245 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20141208)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  MachineType: Dell Inc. Inspiron 5521
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.1.2-040102-generic 
root=UUID=f9a69626-dd71-4ae7-ae13-35c241035346 ro splash quiet 
plymouth:debug=1=1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.1.2-040102-generic 
root=UUID=f9a69626-dd71-4ae7-ae13-35c241035346 ro splash quiet 
plymouth:debug=1=1
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.1ubuntu2.10
  SourcePackage: cups
  Title: package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: 子进程 已安装 
post-installation 脚本 返回错误状态 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/29/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0N5YWG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A11
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd08/29/2013:svnDellInc.:pnInspiron5521:pvrA11:rvnDellInc.:rn0N5YWG:rvrA00:cvnDellInc.:ct8:cvrA11:
  dmi.product.name: Inspiron 5521
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2014-12-08T14:37:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1490182/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1490248] Re: package cups-bsd 1.7.2-0ubuntu1.6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1490248

Title:
  package cups-bsd 1.7.2-0ubuntu1.6 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in cups package in Ubuntu:
  Expired

Bug description:
  ???

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: cups-bsd 1.7.2-0ubuntu1.6
  ProcVersionSignature: Ubuntu 3.16.0-46.62~14.04.1-generic 3.16.7-ckt15
  Uname: Linux 3.16.0-46-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.12
  Architecture: amd64
  CupsErrorLog:
   
  Date: Sun Aug 30 10:43:30 2015
  DuplicateSignature: package:cups-bsd:1.7.2-0ubuntu1.6:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-07-29 (31 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  KernLog:
   
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: System manufacturer System Product Name
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-46-generic 
root=UUID=d5392a51-41dd-4cd6-b989-8037c91c2220 ro quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-46-generic 
root=UUID=d5392a51-41dd-4cd6-b989-8037c91c2220 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: cups
  Title: package cups-bsd 1.7.2-0ubuntu1.6 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2301
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A77T
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2301:bd11/29/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A77T:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1490248/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1495971] Re: Samsung ML-1250 prints only first job and then disconnects

2018-10-17 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1495971

Title:
  Samsung ML-1250 prints only first job and then disconnects

Status in cups package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  We have:

  lsusb
  Bus 004 Device 009: ID 04e8:300e Samsung Electronics Co., Ltd Laser Printer

  Just connected printer and started to print first job:

  tail -f /var/log/syslog
  Sep 15 14:50:18 desktop udev-configure-printer: URI matches without serial 
number: usb://Samsung/ML-1250
  Sep 15 14:50:18 desktop udev-configure-printer: No serial number URI matches 
so using those without
  Sep 15 14:50:18 desktop udev-configure-printer: URI of detected printer: 
usb://Samsung/ML-1250, normalized: samsung ml 1250
  Sep 15 14:50:18 desktop udev-configure-printer: URI of print queue: 
usb://HP/LaserJet%201200?serial=00CNCF203187, normalized: laserjet 1200 serial 
00cncf203187
  Sep 15 14:50:18 desktop udev-configure-printer: About to add queue for 
usb://Samsung/ML-1250
  Sep 15 14:50:20 desktop udev-add-printer: add_queue: 
URIs=['usb://Samsung/ML-1250']
  Sep 15 14:50:20 desktop udev-add-printer: D-Bus method call failed: 
org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.redhat.NewPrinterNotification was not provided by any .service files
  Sep 15 14:50:23 desktop udev-add-printer: PPD: 
foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/Samsung-ML-1250-pxlmono.ppd; 
Status: 0
  Sep 15 14:50:24 desktop colord: Profile added: ML-1250-Gray..
  Sep 15 14:50:24 desktop colord: Device added: cups-ML-1250
  Sep 15 14:53:51 desktop kernel: [22676.268686] usblp0: removed
  Sep 15 14:54:03 desktop kernel: [22688.117044] usblp 4-2:1.0: usblp0: USB 
Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04E8 pid 0x300E
  Sep 15 14:54:03 desktop kernel: [22688.117121] usblp0: removed
  Sep 15 14:54:03 desktop kernel: [22688.228040] usb 4-2: reset full-speed USB 
device number 4 using uhci_hcd
  Sep 15 14:54:03 desktop kernel: [22688.348039] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:03 desktop kernel: [22688.572040] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:04 desktop kernel: [22688.788044] usb 4-2: reset full-speed USB 
device number 4 using uhci_hcd
  Sep 15 14:54:04 desktop kernel: [22688.908039] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:04 desktop kernel: [22689.132029] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:04 desktop kernel: [22689.348038] usb 4-2: reset full-speed USB 
device number 4 using uhci_hcd
  Sep 15 14:54:05 desktop kernel: [22689.756029] usb 4-2: device not accepting 
address 4, error -71
  Sep 15 14:54:05 desktop kernel: [22689.868029] usb 4-2: reset full-speed USB 
device number 4 using uhci_hcd
  Sep 15 14:54:05 desktop kernel: [22690.276040] usb 4-2: device not accepting 
address 4, error -71
  Sep 15 14:54:05 desktop kernel: [22690.276130] usblp: can't set desired 
altsetting 0 on interface 0
  Sep 15 14:54:05 desktop kernel: [22690.276265] usb 4-2: USB disconnect, 
device number 4
  Sep 15 14:54:05 desktop udev-configure-printer: remove 
/devices/pci:00/:00:1a.1/usb4/4-2
  Sep 15 14:54:05 desktop udev-configure-printer: URI of detected printer: 
usb://Samsung/ML-1250, normalized: samsung ml 1250
  Sep 15 14:54:05 desktop udev-configure-printer: URI of print queue: 
usb://HP/LaserJet%201200?serial=00CNCF203187, normalized: laserjet 1200 serial 
00cncf203187
  Sep 15 14:54:05 desktop udev-configure-printer: URI of print queue: 
usb://Samsung/ML-1250, normalized: samsung ml 1250
  Sep 15 14:54:05 desktop udev-configure-printer: Queue 
ipp://localhost:631/printers/ML-1250 has matching device URI
  Sep 15 14:54:05 desktop udev-configure-printer: Disabled printer 
ipp://localhost:631/printers/ML-1250 as the corresponding device was unplugged 
or turned off
  Sep 15 14:54:05 desktop kernel: [22690.388029] usb 4-2: new full-speed USB 
device number 5 using uhci_hcd
  Sep 15 14:54:05 desktop kernel: [22690.508023] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:06 desktop kernel: [22690.732024] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:06 desktop kernel: [22690.948037] usb 4-2: new full-speed USB 
device number 6 using uhci_hcd
  Sep 15 14:54:06 desktop kernel: [22691.068035] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:06 desktop kernel: [22691.292039] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:06 desktop kernel: [22691.508031] usb 4-2: new full-speed USB 
device number 7 using uhci_hcd
  Sep 15 14:54:07 desktop kernel: [22691.916031] usb 4-2: device not accepting 
address 7, error -71
  Sep 15 14:54:07 desktop kernel: [22692.028039] usb 4-2: new 

[Touch-packages] [Bug 1495971] Re: Samsung ML-1250 prints only first job and then disconnects

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1495971

Title:
  Samsung ML-1250 prints only first job and then disconnects

Status in cups package in Ubuntu:
  Expired
Status in linux package in Ubuntu:
  Expired

Bug description:
  We have:

  lsusb
  Bus 004 Device 009: ID 04e8:300e Samsung Electronics Co., Ltd Laser Printer

  Just connected printer and started to print first job:

  tail -f /var/log/syslog
  Sep 15 14:50:18 desktop udev-configure-printer: URI matches without serial 
number: usb://Samsung/ML-1250
  Sep 15 14:50:18 desktop udev-configure-printer: No serial number URI matches 
so using those without
  Sep 15 14:50:18 desktop udev-configure-printer: URI of detected printer: 
usb://Samsung/ML-1250, normalized: samsung ml 1250
  Sep 15 14:50:18 desktop udev-configure-printer: URI of print queue: 
usb://HP/LaserJet%201200?serial=00CNCF203187, normalized: laserjet 1200 serial 
00cncf203187
  Sep 15 14:50:18 desktop udev-configure-printer: About to add queue for 
usb://Samsung/ML-1250
  Sep 15 14:50:20 desktop udev-add-printer: add_queue: 
URIs=['usb://Samsung/ML-1250']
  Sep 15 14:50:20 desktop udev-add-printer: D-Bus method call failed: 
org.freedesktop.DBus.Error.ServiceUnknown: The name 
com.redhat.NewPrinterNotification was not provided by any .service files
  Sep 15 14:50:23 desktop udev-add-printer: PPD: 
foomatic-db-compressed-ppds:0/ppd/foomatic-ppd/Samsung-ML-1250-pxlmono.ppd; 
Status: 0
  Sep 15 14:50:24 desktop colord: Profile added: ML-1250-Gray..
  Sep 15 14:50:24 desktop colord: Device added: cups-ML-1250
  Sep 15 14:53:51 desktop kernel: [22676.268686] usblp0: removed
  Sep 15 14:54:03 desktop kernel: [22688.117044] usblp 4-2:1.0: usblp0: USB 
Bidirectional printer dev 4 if 0 alt 0 proto 2 vid 0x04E8 pid 0x300E
  Sep 15 14:54:03 desktop kernel: [22688.117121] usblp0: removed
  Sep 15 14:54:03 desktop kernel: [22688.228040] usb 4-2: reset full-speed USB 
device number 4 using uhci_hcd
  Sep 15 14:54:03 desktop kernel: [22688.348039] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:03 desktop kernel: [22688.572040] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:04 desktop kernel: [22688.788044] usb 4-2: reset full-speed USB 
device number 4 using uhci_hcd
  Sep 15 14:54:04 desktop kernel: [22688.908039] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:04 desktop kernel: [22689.132029] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:04 desktop kernel: [22689.348038] usb 4-2: reset full-speed USB 
device number 4 using uhci_hcd
  Sep 15 14:54:05 desktop kernel: [22689.756029] usb 4-2: device not accepting 
address 4, error -71
  Sep 15 14:54:05 desktop kernel: [22689.868029] usb 4-2: reset full-speed USB 
device number 4 using uhci_hcd
  Sep 15 14:54:05 desktop kernel: [22690.276040] usb 4-2: device not accepting 
address 4, error -71
  Sep 15 14:54:05 desktop kernel: [22690.276130] usblp: can't set desired 
altsetting 0 on interface 0
  Sep 15 14:54:05 desktop kernel: [22690.276265] usb 4-2: USB disconnect, 
device number 4
  Sep 15 14:54:05 desktop udev-configure-printer: remove 
/devices/pci:00/:00:1a.1/usb4/4-2
  Sep 15 14:54:05 desktop udev-configure-printer: URI of detected printer: 
usb://Samsung/ML-1250, normalized: samsung ml 1250
  Sep 15 14:54:05 desktop udev-configure-printer: URI of print queue: 
usb://HP/LaserJet%201200?serial=00CNCF203187, normalized: laserjet 1200 serial 
00cncf203187
  Sep 15 14:54:05 desktop udev-configure-printer: URI of print queue: 
usb://Samsung/ML-1250, normalized: samsung ml 1250
  Sep 15 14:54:05 desktop udev-configure-printer: Queue 
ipp://localhost:631/printers/ML-1250 has matching device URI
  Sep 15 14:54:05 desktop udev-configure-printer: Disabled printer 
ipp://localhost:631/printers/ML-1250 as the corresponding device was unplugged 
or turned off
  Sep 15 14:54:05 desktop kernel: [22690.388029] usb 4-2: new full-speed USB 
device number 5 using uhci_hcd
  Sep 15 14:54:05 desktop kernel: [22690.508023] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:06 desktop kernel: [22690.732024] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:06 desktop kernel: [22690.948037] usb 4-2: new full-speed USB 
device number 6 using uhci_hcd
  Sep 15 14:54:06 desktop kernel: [22691.068035] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:06 desktop kernel: [22691.292039] usb 4-2: device descriptor 
read/64, error -71
  Sep 15 14:54:06 desktop kernel: [22691.508031] usb 4-2: new full-speed USB 
device number 7 using uhci_hcd
  Sep 15 14:54:07 desktop kernel: [22691.916031] usb 4-2: device not accepting 
address 7, error -71
  Sep 15 14:54:07 desktop kernel: [22692.028039] usb 4-2: new 

[Touch-packages] [Bug 1491004] Re: 8 sec delay on every submitted raw printer job to Citizen CT-S310II

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1491004

Title:
  8 sec delay on every submitted raw printer job to Citizen CT-S310II

Status in cups package in Ubuntu:
  Expired

Bug description:
  Citizen CT-S310II on a 14.04 system for every submitted raw printer job 
introduces 8 sec. delay.
  Bug can be repeated by issuing:
  lpr -o raw test.txt

  Workaround, same as for Zebra's printers, solved in 
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1001028 forcing 
uni-directional mode:
  sudo lpadmin -p CITIZEN-CT-S310II -o usb-unidir-default=true

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1491004/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1516410] Re: package cups-common 2.0.2-1ubuntu3.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1516410

Title:
  package cups-common 2.0.2-1ubuntu3.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in cups package in Ubuntu:
  Expired

Bug description:
  This problem is strange. I keep seeing it after I have force installs
  of the upgrades and updates.

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: cups-common 2.0.2-1ubuntu3.2
  ProcVersionSignature: Ubuntu 3.19.0-33.38-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-33-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.7
  Architecture: amd64
  CupsErrorLog:
   E [15/Nov/2015:07:45:08 -0800] Unknown directive JobPrivateAccess on line 88 
of /etc/cups/cupsd.conf.
   E [15/Nov/2015:07:45:08 -0800] Unknown directive JobPrivateValues on line 89 
of /etc/cups/cupsd.conf.
   E [15/Nov/2015:07:45:08 -0800] Unknown directive SubscriptionPrivateAccess 
on line 90 of /etc/cups/cupsd.conf.
   E [15/Nov/2015:07:45:08 -0800] Unknown directive SubscriptionPrivateValues 
on line 91 of /etc/cups/cupsd.conf.
  Date: Sun Nov 15 09:07:50 2015
  Dependencies:
   
  DpkgTerminalLog:
   dpkg: error processing package cups-common (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  DuplicateSignature: package:cups-common:2.0.2-1ubuntu3.2:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-10-10 (35 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  Lpstat: device for Samsung-M288x-Series: 
dnssd://Samsung%20M288x%20Series%20(SEC30CDA7334F8A)._printer._tcp.local/
  MachineType: MSI MS-7693
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: Samsung-M288x-Series: Samsung M288x Series PXL
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic.efi.signed 
root=UUID=e699cd80-60f5-41c8-9840-87a0884cec4a ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-33-generic.efi.signed 
root=UUID=e699cd80-60f5-41c8-9840-87a0884cec4a ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4.2
  SourcePackage: cups
  Title: package cups-common 2.0.2-1ubuntu3.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/12/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V22.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: 970 GAMING (MS-7693)
  dmi.board.vendor: MSI
  dmi.board.version: 4.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 4.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV22.3:bd05/12/2015:svnMSI:pnMS-7693:pvr4.0:rvnMSI:rn970GAMING(MS-7693):rvr4.0:cvnMSI:ct3:cvr4.0:
  dmi.product.name: MS-7693
  dmi.product.version: 4.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1516410/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1516352] Re: printer does not print

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1516352

Title:
  printer does not print

Status in cups package in Ubuntu:
  Expired

Bug description:
  printer does not print. the printer is correctly recognized, but when
  a print job is launched it seems it is starting but it never
  completes. the problem started with ubuntu 14.04. I am running the
  latest version of cups. Tried to install and re-install the printer,
  but the problem persists

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.6
  ProcVersionSignature: Ubuntu 3.13.0-68.111-generic 3.13.11-ckt27
  Uname: Linux 3.13.0-68-generic i686
  ApportVersion: 2.14.1-0ubuntu3.18
  Architecture: i386
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Sun Nov 15 09:51:14 2015
  InstallationDate: Installed on 2014-12-25 (324 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  Lpstat: device for HP_Deskjet_3050_J610_series: 
dnssd://Deskjet%203050%20J610%20series%20%5BFA990C%5D._pdl-datastream._tcp.local/
  MachineType: Hewlett-Packard Compaq Presario CQ60 Notebook PC
  Papersize: a4
  PpdFiles: HP_Deskjet_3050_J610_series: HP Deskjet 3050 j610 Series, hpcups 
3.14.3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-68-generic 
root=UUID=3526e498-e91a-48c8-9222-a6671999a2e7 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2008
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.32
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3612
  dmi.board.vendor: Wistron
  dmi.board.version: 09.48
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Wistron
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.32:bd11/20/2008:svnHewlett-Packard:pnCompaqPresarioCQ60NotebookPC:pvrF.32:rvnWistron:rn3612:rvr09.48:cvnWistron:ct10:cvrChassisVersion:
  dmi.product.name: Compaq Presario CQ60 Notebook PC
  dmi.product.version: F.32
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1516352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1530388] Re: printer is not receiving print jobs hp laaserjet 1020 usb port

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1530388

Title:
  printer is not receiving print jobs hp laaserjet 1020 usb port

Status in cups package in Ubuntu:
  Expired

Bug description:
  Second version of Ubuntu I have encountered this with.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: cups 2.1.0-4ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: Unity
  Date: Thu Dec 31 12:18:38 2015
  EcryptfsInUse: Yes
  Lpstat: device for HP-LaserJet-1020: serial:/dev/ttyS0?baud=115200
  MachineType: System76, Inc. Wild Dog Pro
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP-LaserJet-1020.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HP-LaserJet-1020.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-22-generic 
root=UUID=cc2bc49b-f220-42e5-9813-74773bab5dab ro quiet splash
  SourcePackage: cups
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/19/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H170-D3HP-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: wilp12
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd10/19/2015:svnSystem76,Inc.:pnWildDogPro:pvrwilp12:rvnGigabyteTechnologyCo.,Ltd.:rnH170-D3HP-CF:rvrx.x:cvnSystem76,Inc.:ct3:cvrwilp12:
  dmi.product.name: Wild Dog Pro
  dmi.product.version: wilp12
  dmi.sys.vendor: System76, Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1530388/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1526586] Re: package cups 1.7.2-0ubuntu1.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 255

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1526586

Title:
  package cups 1.7.2-0ubuntu1.6 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 255

Status in cups package in Ubuntu:
  Expired

Bug description:
  package cups 1.7.2-0ubuntu1.6

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.6
  ProcVersionSignature: Ubuntu 3.16.0-56.75~14.04.1-generic 3.16.7-ckt20
  Uname: Linux 3.16.0-56-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CupsErrorLog:
   E [15/Dec/2015:16:55:57 -0500] Unknown directive BrowseAddress on line 26 of 
/etc/cups/cupsd.conf.
   E [15/Dec/2015:21:43:25 -0500] Unknown directive BrowseAddress on line 26 of 
/etc/cups/cupsd.conf.
  Date: Tue Dec 15 18:32:21 2015
  DuplicateSignature: package:cups:1.7.2-0ubuntu1.6:subprocess installed 
post-installation script returned error exit status 255
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 255
  InstallationDate: Installed on 2015-12-14 (1 days ago)
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: CLEVO CO. W3x0ET
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-56-generic 
root=UUID=745ad80f-aed0-474c-bc18-145f14bf7672 ro quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-56-generic 
root=UUID=745ad80f-aed0-474c-bc18-145f14bf7672 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.5
   apt  1.0.1ubuntu2.10
  SourcePackage: cups
  Title: package cups 1.7.2-0ubuntu1.6 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 255
  UpgradeStatus: Upgraded to trusty on 2015-12-14 (1 days ago)
  dmi.bios.date: 08/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: W3x0ET
  dmi.board.vendor: CLEVO CO.
  dmi.board.version: N/A
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 9
  dmi.chassis.vendor: CLEVO CO.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd08/13/2012:svnCLEVOCO.:pnW3x0ET:pvrN/A:rvnCLEVOCO.:rnW3x0ET:rvrN/A:cvnCLEVOCO.:ct9:cvrN/A:
  dmi.product.name: W3x0ET
  dmi.product.version: N/A
  dmi.sys.vendor: CLEVO CO.
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.apparmor.d.usr.sbin.cupsd: 2015-06-04T08:59:13
  mtime.conffile..etc.cups.cups.files.conf: 2015-06-04T08:58:57
  mtime.conffile..etc.cups.cupsd.conf: 2015-12-13T23:17:55.445426
  mtime.conffile..etc.default.cups: 2015-12-13T23:17:45.805425
  mtime.conffile..etc.init.cups.conf: 2015-06-04T08:59:12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1526586/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1527249] Re: cups-client_1.7.2-0ubuntu1.7 can't find remote cups server

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1527249

Title:
  cups-client_1.7.2-0ubuntu1.7 can't find remote cups server

Status in cups package in Ubuntu:
  Expired

Bug description:
  Hi
  I use i386 kubuntu 14.04.
  Today I updated my system including security patch of cups-client, 
cups-common, libcups2, cups-bsd etc.

  After update printing to a remote cups server doesn't work (no cups
  localy installed).

  Normaly the system find in /home//.cups/client.conf the remote
  cups server and all accessible printers.

  After update, this was broken, lpstat -a ( or -v) doesn't get any
  printer.

  So I reinstalled Version 1.7.2-0ubuntu1.6 ( 
libcups2_1.7.2-0ubuntu1.6_i386.deb libcupsimage2_1.7.2-0ubuntu1.6_i386.deb 
cups-client_1.7.2-0ubuntu1.6_i386.deb cups-common_1.7.2-0ubuntu1.6_all.deb 
cups-bsd_1.7.2-0ubuntu1.6). 
  Now everything work again.

  Please look into it.

  Thanks in advance.

  Volker

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1527249/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1529696] Re: AppArmor problem with Brother binary drivers for MFC-9340CDW

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1529696

Title:
  AppArmor problem with Brother binary drivers for MFC-9340CDW

Status in cups package in Ubuntu:
  Expired

Bug description:
  Seeing "denied" in logs for AppArmor/cups when using the Brother
  binary drivers for MFC-9340CDW.  Possibly related - printer
  intermittently prints in duplicate or triplicate.  Just recently set
  "aa-complain cups" to see if it temporarily resolves.  This in Trusty.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1529696/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1523395] Re: package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: 子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1523395

Title:
  package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: 子程序 已安裝的
  post-installation script 傳回了錯誤退出狀態 1

Status in cups package in Ubuntu:
  Expired

Bug description:
  設定 snmpd (5.7.2~dfsg-8.1ubuntu5) ...
  update-rc.d: warning:  stop runlevel arguments (1) do not match snmpd 
Default-Stop values (0 1 6)
  /usr/sbin/invoke-rc.d: 1: /usr/sbin/invoke-rc.d: /sbin/runlevel: not found
   * Starting network management services:  
  設定 kamailio-snmpstats-modules:i386 (4.2.0-2ubuntu1) ...
  設定 git-man (1:2.1.4-2.1) ...
  設定 git (1:2.1.4-2.1) ...
  設定 libalgorithm-c3-perl (0.09-1) ...
  設定 libcgi-pm-perl (4.09-2) ...
  設定 libclass-c3-perl (0.26-1) ...
  設定 libclass-c3-xs-perl (0.13-2build1) ...
  設定 libcpan-meta-perl (2.142690-1) ...
  設定 libparams-util-perl (1.07-2build1) ...
  設定 libsub-install-perl (0.928-1) ...
  設定 libdata-optlist-perl (0.109-1) ...
  設定 libmro-compat-perl (0.12-1) ...
  設定 libsub-exporter-perl (0.986-1) ...
  設定 libdata-section-perl (0.26-1) ...
  設定 libfcgi-perl (0.77-1) ...
  設定 libmodule-build-perl (0.421000-2) ...
  設定 libmodule-signature-perl (0.73-1ubuntu0.14.04.1) ...
  設定 libpackage-constants-perl (0.04-1) ...
  設定 libregexp-common-perl (2013031301-1) ...
  設定 libpod-readme-perl (0.11-1) ...
  設定 libtext-template-perl (1.46-1) ...
  設定 libsoftware-license-perl (0.103010-3) ...
  設定 rename (0.20-3) ...
  update-alternatives: using /usr/bin/file-rename to provide /usr/bin/rename 
(rename) in auto mode
  設定 libcgi-fast-perl (1:2.04-1) ...
  Processing triggers for libc-bin (2.19-0ubuntu6.6) ...
  Processing triggers for initramfs-tools (0.103ubuntu15) ...
  update-initramfs: Generating /boot/initrd.img-3.13.0-71-generic
  Processing triggers for libapache2-mod-php5 (5.6.4+dfsg-4ubuntu6) ...
  Processing triggers for ureadahead (0.100.0-19) ...
  ureadahead will be reprofiled on next reboot

  處理時發生錯誤:
   cups-daemon
   cups-core-drivers
   cups
   fontconfig

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: cups-daemon 2.0.2-1ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-71.114-generic 3.13.11-ckt29
  Uname: Linux 3.13.0-71-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CupsErrorLog:
   
  Date: Mon Dec  7 16:40:33 2015
  DuplicateSignature: package:cups-daemon:2.0.2-1ubuntu3:子程序 已安裝的 
post-installation script 傳回了錯誤退出狀態 1
  ErrorMessage: 子程序 已安裝的 post-installation script 傳回了錯誤退出狀態 1
  InstallationDate: Installed on 2014-02-25 (649 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad 
file descriptor
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  Papersize: a4
  PpdFiles: VMware_Virtual_Printer: Generic PostScript Printer 
Foomatic/Postscript (recommended)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=f076311e-7033-49a8-aafc-835926a912b2 ro quiet splash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-71-generic 
root=UUID=f076311e-7033-49a8-aafc-835926a912b2 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.1ubuntu2.10
  SourcePackage: cups
  Title: package cups-daemon 2.0.2-1ubuntu3 failed to install/upgrade: 子程序 已安裝的 
post-installation script 傳回了錯誤退出狀態 1
  UpgradeStatus: Upgraded to trusty on 2015-12-04 (3 days ago)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd07/31/2013:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  modified.conffile..etc.default.cups:
   # Cups configure options
   
   # LOAD_LP_MODULE: enable/disable to load "lp" parallel printer driver module
   # LOAD_LP_MODULE has migrated to /etc/modules-load.d/cups-filters.conf
   # LOAD_LP_MODULE=yes
  mtime.conffile..etc.default.cups: 2015-12-04T15:55:49.732866

To manage notifications about this bug go to:

[Touch-packages] [Bug 1532551] Re: no response from printer

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1532551

Title:
  no response from printer

Status in cups package in Ubuntu:
  Expired

Bug description:
  I have a very old dot-matrix printer, Epson LX-400 model  P70RA.   I am 
attempting to link it from a USB port on a laptop running a Lubuntu version of 
Ubuntu 14.04.   I have been trying to use a ppd file
   /etc/cups/ppd/Epson-LX-300plus-ibmpro.ppd
  which I have seen recommended.My output from  lsusb  is

  
  Bus 001 Device 002: ID 04f2:b128 Chicony Electronics Co., Ltd 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 005 Device 002: ID 067b:2305 Prolific Technology, Inc. PL2305 Parallel 
Port
  Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

  usb_printerid /dev/usb/lp0 
   gives unreadable output after
  GET_DEVICE_ID string:

  lpinfo  givesnetwork lpd
  network socket
  network ipp
  network ipps
  network https
  network ipp14
  network http
  direct usb://Unknown/Printer
  network smb

  lsb_release -rd
  gives

  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  I am afraid I do not know what you mean by "package" but I have been
  attempting to use  lpadmin  following instructions on the Web.

  Thank you for your attention, David Fremlin

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: cups 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.13.0-74.118-generic 3.13.11-ckt30
  Uname: Linux 3.13.0-74-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Sun Jan 10 12:46:41 2016
  Lpstat: device for EpsonLX300: /dev/usb/lp0
  MachineType: TOSHIBA TOSHIBA NB200
  Papersize: a4
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Epson-LX-300plus-ibmpro.ppd', '/etc/cups/ppd/EpsonLX300.ppd'] 
failed with exit code 2: fgrep: /etc/cups/ppd/Epson-LX-300plus-ibmpro.ppd: 
Permission denied
   EpsonLX300: Epson LX-300+ Foomatic/ibmpro (recommended)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-74-generic 
root=UUID=5798558c-27fe-4876-9223-1b5ee61274a4 ro splash quiet
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2009
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: V1.20
  dmi.board.name: KAVAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnTOSHIBA:bvrV1.20:bd04/07/2009:svnTOSHIBA:pnTOSHIBANB200:pvrPLL25E-00500GEN:rvnTOSHIBA:rnKAVAA:rvr1.00:cvnTOSHIBA:ct10:cvrN/A:
  dmi.product.name: TOSHIBA NB200
  dmi.product.version: PLL25E-00500GEN
  dmi.sys.vendor: TOSHIBA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1532551/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1538656] Re: package cups-core-drivers 1.7.2-0ubuntu1.7 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

2018-10-17 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1538656

Title:
  package cups-core-drivers 1.7.2-0ubuntu1.7 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in cups package in Ubuntu:
  Expired

Bug description:
  Unable to install new software from ubuntu software center.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: cups-core-drivers 1.7.2-0ubuntu1.7
  ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CupsErrorLog: E [27/Jan/2016:22:06:37 +0530] Unable to bind socket for 
address [v1.::1]:631 - Cannot assign requested address.
  Date: Wed Jan 27 22:25:14 2016
  DuplicateSignature: package:cups-core-drivers:1.7.2-0ubuntu1.7:package is in 
a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-01-27 (0 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: LENOVO 20351
  Papersize: a4
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=45b5c04a-f062-4b7b-9b0e-f4398b67a599 ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=45b5c04a-f062-4b7b-9b0e-f4398b67a599 ro quiet splash vt.handoff=7
  SourcePackage: cups
  Title: package cups-core-drivers 1.7.2-0ubuntu1.7 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UdevLog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9ACN32WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A2
  dmi.board.vendor: LENOVO
  dmi.board.version: NANANANANO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9ACN32WW:bd07/20/2015:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrNANANANANODPK:cvnLENOVO:ct10:cvrLenovoG50-70:
  dmi.product.name: 20351
  dmi.product.version: Lenovo G50-70
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1538656/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1798369] Re: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock"

2018-10-17 Thread Ubuntu Foundations Team Bug Bot
** Tags added: ubiquity-18.10.12

** Tags added: cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1798369

Title:
  Reinstall Ubuntu (with preserving existing data) shows error message
  due to "Could not get lock /target/var/cache/apt/archives/lock"

Status in APT:
  New
Status in ubiquity:
  New
Status in apt package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  New

Bug description:
  When trying to reinstall an existing Ubuntu cosmic installation using
  latest 18.10 desktop images, the install shows an error dialog around
  the end of the installation with an "Error restoring installed
  applications". Looking at the syslog such a traceback can be seen:

  apt_pkg.Error: E:Could not get lock
  /target/var/cache/apt/archives/lock - open (11: Resource temporarily
  unavailable), E:Unable to lock directory
  /target/var/cache/apt/archives/

  After reproducing this on a live session, after chrooting into /target
  indeed any apt-get install operations result in the same lock-file
  error. The whole syslog of the reinstall attached to the bug.

  Test case:
   * Download latest cosmic image
   * Install cosmic on the whole disk (can be on a VM)
   * (optional) Boot into the system and leave a file in the home directory (to 
leave a trace, just in case)
   * Reboot and install cosmic using the first option in ubiquity: Reinstall 
Ubuntu
   * Finish configuration

  The install itself doesn't fail, but around the end of the
  installation process the error dialog appears. System is still
  bootable but left with old packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1798369/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1611523] Re: ibus-setup fails with local python3

2018-10-17 Thread Kal Sze
I agree that the full path to the system python3 should be specified. I
use pyenv to install multiple local versions of python2 and python3. And
this was breaking silently for me (couldn't open the preferences gui
from the ibus menu).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/1611523

Title:
  ibus-setup fails with local python3

Status in ibus package in Ubuntu:
  Invalid

Bug description:
  If a user has installed a local python3 (e.g. Anaconda) ibus-setup may
  fail to run because of a missing library:

  Traceback (most recent call last):
File "/usr/share/ibus/setup/main.py", line 31, in 
  from gi.repository import GLib
  ImportError: No module named 'gi'

  This error can be avoided if ibus-setup explicitly executes the system
  python3 rather than the first python3 found in $PATH, by changing:

exec python3 /usr/share/ibus/setup/main.py $@

  to:

exec /usr/bin/python3 /usr/share/ibus/setup/main.py $@

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ibus 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Aug  9 14:17:20 2016
  InstallationDate: Installed on 2016-06-24 (45 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1611523/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1798400] Re: Regression: cannot use impress remote over bluetooth with ubuntu bionic

2018-10-17 Thread Daniel van Vugt
I agree this is most likely a LibO bug, as is:
https://bugzilla.redhat.com/show_bug.cgi?id=1581879

** Also affects: libreoffice (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: libreoffice (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1581879
   Importance: Unknown
   Status: Unknown

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1798400

Title:
  Regression: cannot use impress remote over bluetooth with ubuntu
  bionic

Status in bluez package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in libreoffice package in Fedora:
  Unknown

Bug description:
  Trying to use the impress remote
  (https://wiki.documentfoundation.org/Impress_Remote) over bluetooth
  with libreoffice over ubuntu bionic fails.

  The handset errors out that it cannot connect with Libreoffice on the
  computer even if the bluetooth adapter on the handset and on the
  computer are correctly paired.

  This does not seem to be an issue in the Libreoffice or in the impress
  remote code:

  - I have tested also past LibO versions
  - The Impress remote codebase has not changed recently

  This used to work on the same hardware (headset and laptop) with
  ubuntu 16.04.

  Hence the issue seems to be in a regression in the ubuntu bluetooth
  stack.

  To replicate:

  1) Install Libreoffice on Ubuntu bionic (either from the ubuntu repo
  or with the deb packages from the document fundation)

  2) Assure that your computer has bluetooth

  3) Install impress remote on an android handset (either from the play
  store of via fdroid)

  4) Assure that "remote control" is enabled in impress
  Tools>Options>Impress>General

  5) Pair the bluetooth adapters in the laptop and in the computer

  6) Open a presentation on the laptop

  7) Open the remote on the handset, got to the bluetooth pane see the
  computer there, touch it

  8) See the impress remote erroring out

  Most likely you will also get a bluetooth error on dmesg

  RFCOMM server failed for LibreOffice Impress Remote: rfcomm_bind:
  Address already in use (98)

  Same issue was reported for fedora

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Oct 17 16:57:29 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-12-12 (1769 days ago)
  InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Notebook W740SU
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/zagar_ssd--vg-root ro quiet splash 
resume=/dev/zagar_ssd-vg/swap_1 acpi_backlight=vendor vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-06-08 (131 days ago)
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.5
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W740SU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.5:bd10/02/2013:svnNotebook:pnW740SU:pvrNotApplicable:rvnNotebook:rnW740SU:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: W740SU
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:C2:C6:1A:28:71  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN ISCAN 
RX bytes:245088 acl:15156 sco:0 events:1266 errors:0
TX bytes:15571 acl:402 sco:1 commands:131 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1798400/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1792544] Re: demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2 (10.x)

2018-10-17 Thread Jeremy Bicha
libpam-mount 2.16-9 uses pcre2 (for real this time)

** Changed in: libpam-mount (Ubuntu)
   Status: Incomplete => Triaged

** Also affects: vte2.91 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: vte2.91 (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to grep in Ubuntu.
https://bugs.launchpad.net/bugs/1792544

Title:
  demotion of pcre3 (8.x) a.k.a pcre (without the 3) in favor of pcre2
  (10.x)

Status in aide package in Ubuntu:
  Incomplete
Status in apache2 package in Ubuntu:
  New
Status in apr-util package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in exim4 package in Ubuntu:
  Incomplete
Status in freeradius package in Ubuntu:
  Incomplete
Status in git package in Ubuntu:
  Triaged
Status in glib2.0 package in Ubuntu:
  Incomplete
Status in grep package in Ubuntu:
  Incomplete
Status in haproxy package in Ubuntu:
  Triaged
Status in libpam-mount package in Ubuntu:
  Triaged
Status in libselinux package in Ubuntu:
  Triaged
Status in nginx package in Ubuntu:
  Incomplete
Status in nmap package in Ubuntu:
  Incomplete
Status in pcre3 package in Ubuntu:
  Confirmed
Status in php7.2 package in Ubuntu:
  Won't Fix
Status in php7.3 package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Incomplete
Status in python-pyscss package in Ubuntu:
  Incomplete
Status in quagga package in Ubuntu:
  Incomplete
Status in rasqal package in Ubuntu:
  Incomplete
Status in slang2 package in Ubuntu:
  Incomplete
Status in sssd package in Ubuntu:
  Incomplete
Status in vte2.91 package in Ubuntu:
  Triaged
Status in wget package in Ubuntu:
  Incomplete
Status in zsh package in Ubuntu:
  Incomplete

Bug description:
  demotion of pcre3 in favor of pcre2. These packages need analysis what
  needs to be done for the demotion of pcre3:

  Packages which are ready to build with pcre2 should be marked as
  'Triaged', packages which are not ready should be marked as
  'Incomplete'.

  aide
  apache2
  apr-util
  clamav
  exim4
  freeradius
  git
  glib2.0
  grep
  haproxy
  libpam-mount
  libselinux
  nginx
  nmap
  php7.2
  postfix
  python-pyscss
  quagga
  rasqal
  slang2
  sssd
  wget
  zsh

  --

  For clarification: pcre2 is actually newer than pcre3.  pcre3 is just
  poorly named (according to jbicha).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aide/+bug/1792544/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1797872] Re: ntpd keeps Soliciting pool server

2018-10-17 Thread Paul Gear
Hi Manuel, ntpd keeps printing "Soliciting pool server" in syslog
because it can't contact any of the ntp servers in the pool.  This is
most likely a local configuration problem on your machine or network, or
your service provider's network.

Here are some commands that should help work out where the problem lies.

# Check whether your system can resolve DNS names correctly:
dig 0.ubuntu.pool.ntp.org

# Check whether you can ask for time from these hosts:
ntpdate -d 0.ubuntu.pool.ntp.org

To run the above commands successfully, you'll need the dnsutils and
ntpdate packages installed.  Here's what a successful run might look
like (abbreviated): https://pastebin.ubuntu.com/p/zmzgj4nrwS/

If the dig fails, you've got a problem with DNS resolution.  Check for a
broken local DNS resolver or upstream DNS server.

If the dig succeeds but the ntpdate fails, you might have an outbound
firewall blocking access or connection tracking problem in that
firewall.

If both of the above succeed, but NTP still fails, your problem is
likely a firewall blocking outbound NTP access.

The firewalls might be on your local machine, your local network, or
your ISP's network (unfortunately, the last is more common that it
should be).

Other causes might be a local apparmor profile override which prevents
ntpd from doing DNS lookups.

Hope this helps you track it down!

** Changed in: ntp (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/1797872

Title:
  ntpd keeps Soliciting pool server

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  ntpd keeps printing "Soliciting pool server" in the syslog (once every
  5 seconds).

  $ ntpq -c pe
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   0.ubuntu.pool.n .POOL.  16 p-   6400.0000.000   0.000
   1.ubuntu.pool.n .POOL.  16 p-   6400.0000.000   0.000
   2.ubuntu.pool.n .POOL.  16 p-   6400.0000.000   0.000
   3.ubuntu.pool.n .POOL.  16 p-   6400.0000.000   0.000
   ntp.ubuntu.com  .POOL.  16 p-   6400.0000.000   0.000

  $ sudo ntpq -c rv
  associd=0 status=c016 leap_alarm, sync_unspec, 1 event, restart,
  version="ntpd 4.2.8p4@1.3265-o Fri Jul  6 20:10:51 UTC 2018 (1)",
  processor="x86_64", system="Linux/4.15.0-33-generic", leap=11,
  stratum=16, precision=-24, rootdelay=0.000, rootdisp=0.360, refid=INIT,
  reftime=.  Thu, Feb  7 2036  6:28:16.000,
  clock=df6ee808.934d239d  Mon, Oct 15 2018 11:18:48.575, peer=0, tc=3,
  mintc=3, offset=0.00, frequency=6.224, sys_jitter=0.00,
  clk_jitter=0.000, clk_wander=0.000

  
  I have changed nothing in the default configuration of ntp or the firewall.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.9
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Oct 15 11:17:45 2018
  InstallationDate: Installed on 2018-04-20 (177 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: ntp
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1797872/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm

2018-10-17 Thread Andrew Schulman
> Disabling the key "/org/gnome/desktop/lockdown/disable-lock-screen" in
dconf-editor solved the problem.

I'm not sure what you mean by disabling. If you mean set it to false,
false is already the default value. It was at its default for me. I
tried overriding it and setting it to false, but that didn't help. So
this solution doesn't work for me.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1715435

Title:
  Can't lock screen with keyboard shortcuts when using lightdm

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen.
  Additionally, if I wait a very long time the screen does not lock
  either.

  Switching from LightDM to GDM3 fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.25.91-0ubuntu3
  ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8
  Uname: Linux 4.12.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Wed Sep  6 09:17:35 2017
  DisplayManager: lightdm
  InstallationDate: Installed on 2016-01-22 (592 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1715435/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1794957] Please test proposed package

2018-10-17 Thread Brian Murray
Hello Julian, or anyone else affected,

Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.6 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1794957

Title:
  pipelining on archive.u.c aborts after 101 packages

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Downloading many packages on archive.ubuntu.com or some other mirrors seems 
to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1 
(commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure 
with a 200 response as meaning that the server does not support pipelining, 
hence disabling it for any further downloads.

  With high speed connections at higher latency, this can cause a severe
  reduction in usable bandwidth. For example, I saw speeds drop from 40
  MB/s to 15 MB/s due to this.

  The fix ensures that we continue pipelining if the previous connection
  to the server successfully retrieved at least 3 files with pipelining
  enabled.

  [Test case]
  Pick a package that would cause a large number (200/300 packages of packages 
to be installed). I used plasma-desktop and xubuntu-desktop, for example. Run 
apt install -d $package. Ensure that after the first 101 packages the progress 
does not slow down - you should not see a lot "working" in the progress output. 
The speed should be substantially higher.

  Don't run in a container setup by cloud-init, as cloud-init disables
  pipelining; or remove /etc/apt/apt.conf.d/90cloud-init-pipelining (see
  bug 1794982).

  Requirements:
  * High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is 
enough)
  * Not a terribly slow CPU, as we'd get slowed down by hashing otherwise

  [Regression potential]
  This fix is isolated to code enabling/disabling pipelining on subsequent 
connections. It could cause more pipelining to be tried on servers who are not 
particularly good at it, but can deal with 3 items correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1795614] Please test proposed package

2018-10-17 Thread Brian Murray
Hello Julian, or anyone else affected,

Accepted packagekit into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/packagekit/1.1.9-1ubuntu2.18.04.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1795614

Title:
  packagekit frontend locking

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  Fix Committed
Status in packagekit source package in Bionic:
  Fix Committed
Status in packagekit source package in Cosmic:
  Fix Released

Bug description:
  [SRU Notes]

  [rbasak] Requires apt 1.2.28 (Xenial) and 1.6.5 (Bionic), both of
  which are currently in proposed. Do not release to updates without
  releasing the newer apt first.

  [Impact]
  PackageKit needs an adjustment for frontend locking, so it does not release 
the frontend lock during dpkg invocations, but only the normal dpkg lock.

  Frontend locking prevents race conditions between multiple dpkg
  frontends, which can cause other frontends to be interrupted while
  they are installing stuff - the frontend loses the dpkg lock between
  dpkg runs and the system ends up in a partially configured state.

  See bug 1781169 for more details on frontend locking.

  [Test case]
  1. Install a package
  2. Modify prerm to sleep
  3. Remove package via pkcon and check that packagekitd process holds 
lock-frontend and dpkg holds lock (we release lock by closing the lock files, 
so just check if the files are open).

  [Regression potential]
  Changing the code to call UnLockInner() vs UnLock() makes it do less steps 
and only release "lock" as before, and not "lock-frontend". That should not be 
causing any regressions.

  The patch also adds a call to LockInner() after the dpkg execution to
  make it reacquire "lock", this could fail. It should not have much
  impact however, as it only affects a single transaction AFAICT. It
  does reduce the risk of some frontend not implementing frontend
  locking from racing while we still hold the frontend lock, though.

  [Other info]
  This is part of a wider series of SRUs for frontend locking

  - dpkg (bug 1796081)
  - apt (bug 1781169)
  - python-apt (bug 1795407)
  - packagekit (bug 1795614)
  - unattended-upgrades (bug 1789637)
  - aptdaemon (no bug filed yet)

  Further details about frontend locking can be found in
  https://lists.debian.org/debian-dpkg/2017/01/msg00044.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1795614/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1790613] Re: Regression: packagekit crashes updating itself to a new version

2018-10-17 Thread Brian Murray
Hello Rik, or anyone else affected,

Accepted packagekit into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/packagekit/1.1.9-1ubuntu2.18.04.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: packagekit (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1790613

Title:
  Regression: packagekit crashes updating itself to a new version

Status in packagekit package in Ubuntu:
  Fix Released
Status in plasma-discover package in Ubuntu:
  Confirmed
Status in packagekit source package in Bionic:
  Fix Committed
Status in plasma-discover source package in Bionic:
  Confirmed

Bug description:
  [Impact]
  Bionic: 18.04
  Version: 1.1.9-1ubuntu2 upgrading itself to 1.1.9-1ubuntu2.18.04.1

  Updating with pkcon upgrade or plasma-discover crashes packagekit mid
  transaction, requiring user intervention on the command line.

  In plasma-discover the gui reports the crash briefly, but then stalls
  in apparent mid update, requiring the user to force close it and again
  resolve the issue on the command line.

  Example transactions:

  $ pkcon update
  Getting updates   [=]
  Finished  [=]
  Loading cache [=]
  Testing changes   [=]
  Finished  [ ] (0%)
  The following packages have to be updated:
   gir1.2-packagekitglib-1.0-1.1.9-1ubuntu2.18.04.1.amd64 GObject introspection 
data for the PackageKit GLib library
   libpackagekit-glib2-18-1.1.9-1ubuntu2.18.04.1.amd64Library for accessing 
PackageKit using GLib
   packagekit-1.1.9-1ubuntu2.18.04.1.amd64Provides a package management 
service
   packagekit-tools-1.1.9-1ubuntu2.18.04.1.amd64  Provides PackageKit 
command-line tools
  Proceed with changes? [N/y] y

    [=]
  Updating packages [=]
  Waiting for authentication[=]
  Loading cache [=]
  Running   [=]
  Installing packages   [ ] (80%)  The daemon 
crashed mid-transaction!

  $ sudo apt-get upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  and obviously after that doing anything meaningful with packagekit
  like installing a package fails

  $pkcon install kaffeine
  Resolving [=]
  Testing changes   [=]
  Finished  [ ] (0%)
  The following packages have to be installed:
   kaffeine-2.0.14-1.amd64versatile media player for KDE
  Proceed with changes? [N/y] y

    [=]
  Installing[=]
  Waiting for authentication[=]
  Waiting for package manager lock[=]
  Finished  [=]
  Fatal error: E: dpkg was interrupted, you must manually run 'dpkg --configure 
-a' to correct the problem.

  [Test case]
  Upgrade packagekit using pkcon, make sure it does not "crash".

  [Regression potential]
  It could only lead to old packagekitd processes not restarting. packagekit 
will still be told to restart itself like before, the restart being added was 
unintended.

  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-06-26 (69 days 

[Touch-packages] [Bug 1796808] Re: frontend locking regression: dpkg::post-invoke scripts can't install packages

2018-10-17 Thread Brian Murray
Hello Julian, or anyone else affected,

Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.6 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apt (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1796808

Title:
  frontend locking regression: dpkg::post-invoke scripts can't install
  packages

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The switch to frontend locking in 1.2.28/1.6.5/1.7~ caused scripts registered 
in

  DPkg::Pre-Install-Pkgs
  DPkg::Pre-Invoke
  DPkg::Post-Invoke

  To be run with the frontend lock held. This caused problems with some
  installer packages like libdvd-pkg which install a locally built
  package in such a hook.

  To reduce the impact, a fix has been applied in 1.7.0 which exports
  the DPKG_FRONTEND_LOCKED variable when running those scripts, allowing
  dpkg to be run from those scripts.

  [Test case]
  Make sure that the test-frontend-lock test run by autopkgtest succeeds. This 
checks that:

  (1) the variable is correctly exported to those scripts
  (2) the frontend lock is still held
  (3) dpkg can be run from the post-invoke script

  [Regression potential]
  Depending on the script (for example, if the script starts a daemon manually 
or something like that), DPKG_FRONTEND_LOCKED might leak to other processes 
which might survive the apt call and thus revert surviving process to not using 
frontend locking.

  [Other info]
  This fix is for backwards compatibility only. Starting with the dd cycle, it 
will be dropped for the Pre-Install-Pkgs and Pre-Invoke scripts. Potentially 
for post-invoke as well, if we find a better solution for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796808/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1794053] Please test proposed package

2018-10-17 Thread Brian Murray
Hello Julian, or anyone else affected,

Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.6 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1794053

Title:
  pkgCacheFile unlocks in destructor even if it did not acquire lock

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Triaged
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Closing a cache file unlocks the system (loses the lock). This randomly 
breaks ubuntu-make, for example.

  [Test case]
  The following Python code fails, but should succeed, as it locks first, opens 
a cache and closes it, and then unlocks.

  
  import apt_pkg, os, gc

  apt_pkg.init()
  apt_pkg.pkgsystem_lock()

  os.system("ls -l /proc/%d/fd" % os.getpid())
  apt_pkg.Cache()

  gc.collect()

  os.system("ls -l /proc/%d/fd" % os.getpid())

  apt_pkg.pkgsystem_unlock()

  [Regression potential]
  This fixes a regression introduced in 2001 by 

  commit b2e465d6d32d2dc884f58b94acb7e35f671a87fe
  Author: Arch Librarian 
  Date:   Mon Sep 20 16:56:32 2004 +

  Join with aliencode
  Author: jgg
  Date: 2001-02-20 07:03:16 GMT
  Join with aliencode

  The fix is to only UnLock from the cache file if the cache file locked
  before. It's unclear how far code relies on that regression. That
  said, any potential regression should be easily noticable, as it would
  be a case of not unlocking where we were unlocking before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794053/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1790671] Re: /usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy

2018-10-17 Thread Brian Murray
Hello errors.ubuntu.com, or anyone else affected,

Accepted packagekit into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/packagekit/1.1.9-1ubuntu2.18.04.3
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1790671

Title:
  
/usr/lib/packagekit/packagekitd:11:std::__cxx11::basic_string:AptIntf::providesCodec:backend_what_provides_thread:pk_backend_job_thread_setup:g_thread_proxy

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  pkcon what-provides and other tools querying codecs do not work, they crash 
(unless you happen to be lucky with your apt cache). Also, cancalled 
transactions crash as well, even if you're lucky with your apt cache, as the 
"matcher" object is deleted twice.

  There are two reasons: A duplicate delete statement in providesCodec
  entered when cancelling the lookup, and a invalid pointer dereference
  in there.

  [Test case]
  The daemon should not crash as below, but should print a useful message.

  $ lxc launch -e ubuntu:bionic bbb
  $ lxc exec bbb apt update
  $ lxc exec bbb -- apt  -y  install packagekit
  $ lxc exec bbb pkcon what-provides  "gstreamer1.0(decoder-audio/ac3)"
  [...] The daemon crashed mid-transaction!

  (empty lxd container seems to be able to reproduce easily)

  This only tests the pointer dereference, I don't have a test for the
  duplicate. But the code is obviously correct:

   for ... [
 if (m_cancel) {
   // here used to be "delete matcher" - that's deleted
   break;
 }
   }
   delete matcher;

  That is, matcher is always deleted once now, and was always deleted
  twice when cancelling before.

  [Regression potential]
  I don't think it's possible to have a regression here, given the nature of 
the fix, but if there were one, we'd see different behavior in codec lookup.

  For the duplicate delete on cancelled transactions, you'd be looking
  at memory leaks if there were a regression.

  [Other info]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
packagekit.  This problem was most recently seen with package version 
1.1.10-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/46649a8a55e07e74b9d522c9bc9d71a74905ccc2 
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/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1790671/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1787120] Please test proposed package

2018-10-17 Thread Brian Murray
Hello Julian, or anyone else affected,

Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.6 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1787120

Title:
  apt show fails to show large records

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Bionic:
  Fix Committed
Status in apt package in Debian:
  Confirmed

Bug description:
  [Impact]
  apt show can't show records that are larger than 32 KB, e.g. records with 
long lists of provides

  [Test case]
  A test case is provided in autopkgtest, hence validates automatically. See 
https://salsa.debian.org/apt-team/apt/commit/409ceec9ed30cbebd8ece1ef7ce667ab5a32f9df
 for details.

  [Other info]
  This is a duplicate of Debian bug #905527.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787120/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1781169] Re: apt frontend locking

2018-10-17 Thread Brian Murray
Hello Julian, or anyone else affected,

Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.6 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-failed-bionic
** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1781169

Title:
  apt frontend locking

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, 
offering a short window for other clients to acquire the lock. This implements 
/var/lib/dpkg/lock-frontend which will be acquired earlier and not released by 
apt for dpkg to run.

  dpkg will try to acquire the frontend lock as well, unless told not to
  do so via an environment variable, which apt does; hence concurrent
  runs of dpkg without other locking can't happen.

  [Test case]
  Run strace apt install $something and check that lock-frontend is acquired at 
the beginning and not released until the end.

  [Regression potential]
  Frontend locking failures are in English, as there are no translations yet. 
More locks also mean more potential for locking to go wrong across programs, 
but since we don't have any waiting locks we at least won't deadlock.

  [Other info]
  This is part of a wider series of SRUs for frontend locking

  - dpkg (bug 1796081)
  - apt (bug 1781169)
  - python-apt (bug 1795407)
  - packagekit (bug 1795614)
  - unattended-upgrades (bug 1789637)
  - aptdaemon (no bug filed yet)

  Further details about frontend locking can be found in
  https://lists.debian.org/debian-dpkg/2017/01/msg00044.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1794053] Please test proposed package

2018-10-17 Thread Brian Murray
Hello Julian, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.29 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1794053

Title:
  pkgCacheFile unlocks in destructor even if it did not acquire lock

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Triaged
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Closing a cache file unlocks the system (loses the lock). This randomly 
breaks ubuntu-make, for example.

  [Test case]
  The following Python code fails, but should succeed, as it locks first, opens 
a cache and closes it, and then unlocks.

  
  import apt_pkg, os, gc

  apt_pkg.init()
  apt_pkg.pkgsystem_lock()

  os.system("ls -l /proc/%d/fd" % os.getpid())
  apt_pkg.Cache()

  gc.collect()

  os.system("ls -l /proc/%d/fd" % os.getpid())

  apt_pkg.pkgsystem_unlock()

  [Regression potential]
  This fixes a regression introduced in 2001 by 

  commit b2e465d6d32d2dc884f58b94acb7e35f671a87fe
  Author: Arch Librarian 
  Date:   Mon Sep 20 16:56:32 2004 +

  Join with aliencode
  Author: jgg
  Date: 2001-02-20 07:03:16 GMT
  Join with aliencode

  The fix is to only UnLock from the cache file if the cache file locked
  before. It's unclear how far code relies on that regression. That
  said, any potential regression should be easily noticable, as it would
  be a case of not unlocking where we were unlocking before.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794053/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies

2018-10-17 Thread Brian Murray
Hello Ian, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.29 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done-xenial
** Tags added: verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1698159

Title:
  linux-cloud-tools version specific packages are being removed by
  unattended-upgrade's  Remove-Unused-Dependencies

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Triaged
Status in unattended-upgrades source package in Trusty:
  New
Status in apt source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Xenial:
  New
Status in apt source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  When running kernel version 4.4.0-78 (for example) and the unattended-upgrade 
packages installs a new kernel 4.4.0-79 (for example) the 
linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic packages are 
removed by the Remove-Unused-Dependencies rule, because unlike "normal" kernel 
packages they are not excluded by /etc/apt/apt.conf.d/01autoremove-kernels.

  The linux-cloud-tools package has the hyper-v integration services
  daemons in it, so it's deletion leaves some of the integration not
  working.

  Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other
  hyper-v users aren't caught out by this?

  Thanks,

  Ian.

  [Test case]

  Make sure that linux-cloud-tools for protected kernels are listed in
  APT::NeverAutoRemove, for example, on cosmic:

 "^linux-cloud-tools-4\.17\.0-9-generic$";
 "^linux-cloud-tools-4\.18\.0-7-generic$";

  Those are in 01autoremove-kernels

  [Regression Potential]
  some linux-cloud-tools will linger around, so it takes more space.

  [Other info]

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 15 15:27:35 2017
  InstallationDate: Installed on 2016-04-25 (415 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  modified.conffile..etc.update-motd.d.90-updates-available: [deleted]
  modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted]
  modified.conffile..etc.update-motd.d.98-reboot-required: [deleted]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1698159/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1781169] Re: apt frontend locking

2018-10-17 Thread Brian Murray
Hello Julian, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.29 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-failed verification-failed-xenial
** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1781169

Title:
  apt frontend locking

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  apt acquires /var/lib/dpkg/lock but has to release it while running dpkg, 
offering a short window for other clients to acquire the lock. This implements 
/var/lib/dpkg/lock-frontend which will be acquired earlier and not released by 
apt for dpkg to run.

  dpkg will try to acquire the frontend lock as well, unless told not to
  do so via an environment variable, which apt does; hence concurrent
  runs of dpkg without other locking can't happen.

  [Test case]
  Run strace apt install $something and check that lock-frontend is acquired at 
the beginning and not released until the end.

  [Regression potential]
  Frontend locking failures are in English, as there are no translations yet. 
More locks also mean more potential for locking to go wrong across programs, 
but since we don't have any waiting locks we at least won't deadlock.

  [Other info]
  This is part of a wider series of SRUs for frontend locking

  - dpkg (bug 1796081)
  - apt (bug 1781169)
  - python-apt (bug 1795407)
  - packagekit (bug 1795614)
  - unattended-upgrades (bug 1789637)
  - aptdaemon (no bug filed yet)

  Further details about frontend locking can be found in
  https://lists.debian.org/debian-dpkg/2017/01/msg00044.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1781169/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1794957] Please test proposed package

2018-10-17 Thread Brian Murray
Hello Julian, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.29 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1794957

Title:
  pipelining on archive.u.c aborts after 101 packages

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Downloading many packages on archive.ubuntu.com or some other mirrors seems 
to close the connection after every 100 or so packages. APT prior to 1.7.0~rc1 
(commit df696650b7a8c58bbd92e0e1619e956f21010a96), treats a connection closure 
with a 200 response as meaning that the server does not support pipelining, 
hence disabling it for any further downloads.

  With high speed connections at higher latency, this can cause a severe
  reduction in usable bandwidth. For example, I saw speeds drop from 40
  MB/s to 15 MB/s due to this.

  The fix ensures that we continue pipelining if the previous connection
  to the server successfully retrieved at least 3 files with pipelining
  enabled.

  [Test case]
  Pick a package that would cause a large number (200/300 packages of packages 
to be installed). I used plasma-desktop and xubuntu-desktop, for example. Run 
apt install -d $package. Ensure that after the first 101 packages the progress 
does not slow down - you should not see a lot "working" in the progress output. 
The speed should be substantially higher.

  Don't run in a container setup by cloud-init, as cloud-init disables
  pipelining; or remove /etc/apt/apt.conf.d/90cloud-init-pipelining (see
  bug 1794982).

  Requirements:
  * High speed, medium-high latency connection (e.g. 400 Mbit/s at 30 ms RTT is 
enough)
  * Not a terribly slow CPU, as we'd get slowed down by hashing otherwise

  [Regression potential]
  This fix is isolated to code enabling/disabling pipelining on subsequent 
connections. It could cause more pipelining to be tried on servers who are not 
particularly good at it, but can deal with 3 items correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1794957/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1787120] Please test proposed package

2018-10-17 Thread Brian Murray
Hello Julian, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.29 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1787120

Title:
  apt show fails to show large records

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Bionic:
  Fix Committed
Status in apt package in Debian:
  Confirmed

Bug description:
  [Impact]
  apt show can't show records that are larger than 32 KB, e.g. records with 
long lists of provides

  [Test case]
  A test case is provided in autopkgtest, hence validates automatically. See 
https://salsa.debian.org/apt-team/apt/commit/409ceec9ed30cbebd8ece1ef7ce667ab5a32f9df
 for details.

  [Other info]
  This is a duplicate of Debian bug #905527.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1787120/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1796808] Re: frontend locking regression: dpkg::post-invoke scripts can't install packages

2018-10-17 Thread Brian Murray
Hello Julian, or anyone else affected,

Accepted apt into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.2.29 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: apt (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1796808

Title:
  frontend locking regression: dpkg::post-invoke scripts can't install
  packages

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  The switch to frontend locking in 1.2.28/1.6.5/1.7~ caused scripts registered 
in

  DPkg::Pre-Install-Pkgs
  DPkg::Pre-Invoke
  DPkg::Post-Invoke

  To be run with the frontend lock held. This caused problems with some
  installer packages like libdvd-pkg which install a locally built
  package in such a hook.

  To reduce the impact, a fix has been applied in 1.7.0 which exports
  the DPKG_FRONTEND_LOCKED variable when running those scripts, allowing
  dpkg to be run from those scripts.

  [Test case]
  Make sure that the test-frontend-lock test run by autopkgtest succeeds. This 
checks that:

  (1) the variable is correctly exported to those scripts
  (2) the frontend lock is still held
  (3) dpkg can be run from the post-invoke script

  [Regression potential]
  Depending on the script (for example, if the script starts a daemon manually 
or something like that), DPKG_FRONTEND_LOCKED might leak to other processes 
which might survive the apt call and thus revert surviving process to not using 
frontend locking.

  [Other info]
  This fix is for backwards compatibility only. Starting with the dd cycle, it 
will be dropped for the Pre-Install-Pkgs and Pre-Invoke scripts. Potentially 
for post-invoke as well, if we find a better solution for it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1796808/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

2018-10-17 Thread Brian Murray
** Tags added: bugpattern-written

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1773859

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  In Progress
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial.

  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]
   
   * original bug report

  
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1728502] Re: package systemd-sysv 232-21ubuntu7.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

** This bug is no longer a duplicate of bug 1728365
   package systemd-sysv 232-21ubuntu7.1 failed to install/upgrade: subprocess 
installed post-removal script returned error exit status 2
** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1728502

Title:
  package systemd-sysv 232-21ubuntu7.1 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm not sure

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: systemd-sysv 232-21ubuntu7.1
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Mon Oct 30 15:10:51 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
  InstallationDate: Installed on 2014-02-21 (1347 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4.6~17.04.1
  SourcePackage: systemd
  Title: package systemd-sysv 232-21ubuntu7.1 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728502/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1728365] Re: package systemd-sysv 232-21ubuntu7.1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1728365

Title:
  package systemd-sysv 232-21ubuntu7.1 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I have this bug

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd-sysv 232-21ubuntu7.1
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Sun Oct 29 15:33:20 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
  InstallationDate: Installed on 2015-05-22 (891 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.2.25
  SourcePackage: systemd
  Title: package systemd-sysv 232-21ubuntu7.1 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728365/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1782965] Re: package systemd-sysv 237-3ubuntu10.2 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1782965

Title:
  package systemd-sysv 237-3ubuntu10.2 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Maybe it occured in upgrade to
  18.04 from 16LTS.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.2
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jul 22 13:40:12 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2014-03-09 (1595 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Build amd64 LIVE Binary 
20131024-17:53
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.2 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-07-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782965/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1786151] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1786151

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Error occurred during upgrade from 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Aug  8 23:30:59 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2014-04-06 (1585 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-09 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1786151/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1768704] Re: package systemd-sysv 234-2ubuntu12.3 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1768704

Title:
  package systemd-sysv 234-2ubuntu12.3 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  fallo durante la actualizacion

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: systemd-sysv 234-2ubuntu12.3
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Wed May  2 22:17:43 2018
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
  InstallationDate: Installed on 2013-05-31 (1797 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: systemd
  Title: package systemd-sysv 234-2ubuntu12.3 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 2
  UpgradeStatus: Upgraded to artful on 2018-05-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1768704/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1760132] Re: package systemd-sysv 237-3ubuntu6 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

** This bug is no longer a duplicate of bug 1756755
   package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed 
systemd-shim package post-removal script subprocess returned error exit status 2
** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1760132

Title:
  package systemd-sysv 237-3ubuntu6 failed to install/upgrade: installed
  systemd-shim package post-removal script subprocess returned error
  exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu Bionic Beaver (development branch) 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Fri Mar 30 11:56:50 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-03-31 (1824 days ago)
  InstallationMedia: Ubuntu-GNOME 13.04 "Raring Ringtail" - Alpha amd64 
(20130328)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu6 failed to install/upgrade: installed 
systemd-shim package post-removal script subprocess returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-03-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1760132/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1785052] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

** This bug is no longer a duplicate of bug 1756755
   package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed 
systemd-shim package post-removal script subprocess returned error exit status 2
** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1785052

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  The error appeared on reboot after update from 16.04 to 18.04

  During the version update something went wrong. 
  A message about systemd-sysv 237-3ubuntu10.3 appeared, with the additional 
info that the system could be instable and that the tool will run a 
"dpkgsomethingelse -a".

  I launched the update software and i see a notification that asserts
  that is not possible to install all updates and invite to run a
  partial update.

  Partial version update -> 1 package is going to be removed -> systemd-shim - 
shim for systemd
  Then:
  Could not install 'systemd-shim'
  The upgrade will continue but the 'systemd-shim' package may not be in a 
working state. Please consider submitting a bug report about it.
  installed systemd-shim package post-removal script subprocess returned error 
exit status 2

  FIX THAT WORKED FOR ME:
  --
  cd /usr/share/dbus-1/system-services/
  sudo mv org.freedesktop.systemd1.service org.freedesktop.systemd1.service.bak
  Then Run Update -> Run Partial Upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Aug  2 11:21:11 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-11-09 (1726 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1785052/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1767851] Re: package systemd-sysv 234-2ubuntu12.3 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1767851

Title:
  package systemd-sysv 234-2ubuntu12.3 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  after trying to upgrade from 16.04 to 18.04 Ive got 17.10 and now im
  stuck with a system error

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: systemd-sysv 234-2ubuntu12.3
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  Date: Sun Apr 29 13:37:56 2018
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
  InstallationDate: Installed on 2013-04-28 (1827 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: systemd
  Title: package systemd-sysv 234-2ubuntu12.3 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1767851/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1782967] Re: package systemd-sysv 237-3ubuntu10.2 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

** This bug is no longer a duplicate of bug 1782965
   package systemd-sysv 237-3ubuntu10.2 failed to install/upgrade: installed 
systemd-shim package post-removal script subprocess returned error exit status 2
** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1782967

Title:
  package systemd-sysv 237-3ubuntu10.2 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Maybe it happend to upgrade 16LTS to 18LTS.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.2
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Sun Jul 22 13:40:12 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2014-03-09 (1595 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Build amd64 LIVE Binary 
20131024-17:53
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.2 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-07-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1782967/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1756755] Re: package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1756755

Title:
  package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed
  systemd-shim package post-removal script subprocess returned error
  exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Upgrading from xenial to bionic failed the removal of systemd-shim.
  I think the messages were the same as the following, that I can reproduce by 
running "apt upgrade" from the upgraded system:

  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Mar 18 22:52:00 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-01-11 (1892 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5rc1, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu4 failed to install/upgrade: installed 
systemd-shim package post-removal script subprocess returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-03-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1756755/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1777998] Re: package systemd-sysv 237-3ubuntu10 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1777998

Title:
  package systemd-sysv 237-3ubuntu10 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Yes, it has failed to update with the rest of the entire upgrade..
  Dominick R. Colom

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Wed Jun 20 21:56:06 2018
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
  InstallationDate: Installed on 2013-11-20 (1674 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-06-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1777998/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1788002] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1788002

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  error message 18.04 installation failed. message scrolled away before
  detail could b copied. lots of warning/failed messages having to do
  with 'frontend.'

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Mon Aug 20 08:46:27 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2012-08-26 (2185 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788002/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1787025] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1787025

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ocorreu na instalação

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Aug 14 11:19:54 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-12-03 (1715 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1787025/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1788015] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1788015

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  One of those error messages may the correct one, but I'm not nearly
  computer literate to understand any of this.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Aug 20 10:35:29 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2014-01-09 (1684 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788015/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1788868] Re: installed systemd-shim package post-removal script subprocess returned error exit status 2cess returned error exit status 2grade: installed systemd-shim package post

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1788868

Title:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2cess returned error exit status 2grade: installed
  systemd-shim package post-removal script subprocess returned error
  exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  erreur sur mise à jour partielle

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Aug 22 11:44:47 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2014-01-03 (1693 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788868/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1787843] Re: tengo un problema de arranque de equipo, despues de instalar la ultima version de ubuntu

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1787843

Title:
  tengo un problema de arranque de equipo, despues de instalar la ultima
  version de ubuntu

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Instale la nueva version de Ubuntu, pero al reiniciarse se me quedaba 
ploqueado, lo intente a traves del BIOS pidiendole que me reparase lo que podia 
haber mal y en apariencias fue bien (eso fue ayer), hoy lo vuelvo a encender y 
me vuelve a pasar lo mismo le pido que me identifique el problema y me dice que 
es un problema al instalar el software y que esta en el paquete : systemd-shim 
9-1bzr4ubuntu1 y hasta ahi se, me podrian ayudar?
  Agracias

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Fri Aug 17 02:50:45 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2015-09-11 (1073 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release i386 
(20131017)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1787843/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1788259] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1788259

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  instalation problem

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Aug 21 12:25:12 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788259/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1788144] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1788144

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  I was upgrading from 16.04 LTS to 18.04, 
  First error reported was the installation failure of "systemd-shim" package.
  The following errors seemed to related.

  18.04 got installed and running, but there may be related issues, I am
  not aware of yet.

  Release:

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Aug 21 11:37:16 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-07-27 (1850 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788144/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1787238] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1787238

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  plusieurs applications n'ont pas été chargées et ne se sont pas
  installées correctement lors de la mise à niveau d'ubuntu mais je n'ai
  pas les compétences techniques pour décrire davantage les
  problèmes

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Aug 15 06:11:15 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2014-03-05 (1624 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-15 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1787238/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1788140] Re: The following crashed when I logged into Ubuntu..that's all..package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-remo

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1788140

Title:
  The following crashed when I logged into Ubuntu..that's all..package
  systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed
  systemd-shim package post-removal script subprocess returned error
  exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Tried to upgrade from 16.04 to 18.04. Upgrade seemed to be successful
  despite all the errors and a message stating that the upgrade failed.

  Then when I logged into Ubuntu 18.04 the following crash report was
  generated:

  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Aug 21 08:40:41 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-06-14 (1893 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788140/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1786990] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1786990

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  nouvelle mise à jour d'Ubuntu échouée

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Aug 14 15:20:07 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-04-09 (1953 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1786990/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1788391] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1788391

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Error appered after Upgrade from 16.4 LTS to 18.4 LTS

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Wed Aug 22 13:40:02 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-12-21 (1704 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788391/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1789880] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1789880

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  No idea

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Aug 30 10:56:28 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-11-12 (1751 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-30 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1789880/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1789630] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1789630

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 failed to upgrade from 16.04 - resulting in black screen
  GUI failure

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Tue Aug 28 21:00:00 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-01-10 (2056 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1789630/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1788854] Re: After update from xubuntu i686 version 16.04 to i686 18.04 package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-remova

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1788854

Title:
  After update from xubuntu i686 version 16.04 to i686 18.04 package
  systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed
  systemd-shim package post-removal script subprocess returned error
  exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  I had 32-bits OS of Xubuntu from 16.04, and answered yes to be upgraded into 
18.04 on my HP EliteBook 6930p laptop.
  Severals error came up after the reboot.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Thu Aug 23 22:30:08 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2014-01-22 (1674 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release i386 (20131016)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1788854/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1789260] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1789260

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  While upgrading from 16.04.x LTS to 18.04.1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Aug 27 18:40:56 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2012-10-13 (2143 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1789260/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1789723] Re: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1789723

Title:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ver 18 install failed at the clean up stage.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Wed Aug 29 13:36:29 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-09-08 (1816 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1789723/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1790476] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1790476

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  I cannot declare something

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Mon Sep  3 12:07:29 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2016-12-07 (634 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-09-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790476/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1793916] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1793916

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  During upgrade received following errors:
  1. installed systemd-shim package post-removal script subprocess returned 
error exit status 2
  2. could not install 
'/var/cache/apt/archives/systemd-sysv_237-3ubuntu10.3_amd64.deb
  3. Could not install upgrades - The upgrade has aborted your system could be 
in an unusable state. A recovery will run now (dpkg -configure -a)
  4. The upgrade has completed but there were errors during the upgrade process
  5. lsb_release -a resulted in Ubuntu 18.04.1 LTS

  Then no GUI when boot
  So did:
  sudo apt purge gdm gdm3
  sudo apt install gdm3 ubuntu-desktop
  systemctl restart gdm

  And received:
  The system is runnin in low graphics mode.
  But still no GUI

  Then did:
  sudo apt-get install lightdm
  sudo dpkg-reconfigure lightdm

  And then got a working GUI.
  Then followed errors and request for bug report

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Sat Sep 22 11:19:55 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-04-01 (1999 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-09-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1793916/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1790309] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1790309

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  failed during installation, no info displayed.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Fri Aug 31 22:54:05 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2010-03-16 (3091 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-09-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790309/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1793383] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1793383

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Automatic.
  It seems toi have happened before the ubuntu LTS version upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Wed Sep 12 19:45:41 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-01-14 (2074 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1793383/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1792241] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1792241

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  I don know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Wed Sep 12 22:09:42 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2014-02-24 (1661 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-09-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1792241/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1790408] Re: updated 16.04 to 18.04 in my Virtualbox. After 2nd reboot this exc appeared

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1790408

Title:
  updated 16.04 to 18.04 in my Virtualbox. After 2nd reboot this exc
  appeared

Status in systemd package in Ubuntu:
  New

Bug description:
  Can't say much more, the information:
  This Ubuntu runs in a VirtualBox 5.2.0 r118431 (Qt5.6.2)
  A default Ubuntu with nearly no additional stuff installed, which I use for 
quite some time now. Updated it today from 16.04 LTS to 18.04.1 LTS, because 
the OS suggested it.
  A few (2 or 3) errors appeared during the updated, but I had no other choice 
than "continue".
  After update to 18.04 finished I did a reboot. Logged in as "ubu", which was 
created during update.
  Installing a German keyboard also resulted in an error.
  I did another reboot and logged in as "Ubuntu user", which is the user 
account I used in 16.04
  After logging in, the "system error" message popped up and requested me to 
report it.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Sun Sep  2 16:12:47 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-08-24 (1835 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-09-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790408/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1791717] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1791717

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Failed during upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Mon Sep 10 09:18:00 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2015-06-19 (1179 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1791717/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1794043] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1794043

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  upgrade from ubuntu 16.10 to new LTS 18.10.04 i think

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.4.0-135.161-generic 4.4.140
  Uname: Linux 4.4.0-135-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  Date: Mon Sep 24 05:49:36 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2014-11-29 (1394 days ago)
  InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-09-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1794043/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1796375] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1796375

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  slows computer

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Sun Sep 30 11:40:26 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-12-13 (1757 days ago)
  InstallationMedia: This
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-10-01 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796375/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1796707] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1796707

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  upgrade from 16.04 to 18.04 identified this bug during the
  installation process. Reported an unstable installation.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic i686
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: i386
  Date: Mon Oct  8 10:16:43 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-07-19 (1907 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796707/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1796671] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-10-17 Thread Brian Murray
*** This bug is a duplicate of bug 1773859 ***
https://bugs.launchpad.net/bugs/1773859

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 1773859, 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.  Please continue to report any other bugs you may
find.

** This bug has been marked a duplicate of bug 1773859
   upgrades to 18.04 fail

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1796671

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  install error i guess

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: i386
  Date: Sun Oct  7 17:23:55 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-12-01 (1771 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-10-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1796671/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

2018-10-17 Thread Brian Nelson
Eric,

The 'recommendation' for masking dev-hugepages you site from that wiki
page is clearly just an example of how you could disable one of the
various mounts described there. I don't think it's a recommendation to
fix anything in particular.

FWIW: Masking dev-hugepages doesn't seem to help much for me. Masking
tmp seems to let the system boot up, but still the other mount services
fail and systemd status is red 'degraded.'

I've ended up masking all affected mounts (per comment 12 and 14) with
the addition of masking run-rpc_pipefs.mount too. This lets the systemd
boot up to green 'running' state.

I'm still having problems logging into Gnome with a user with NFS home.
I'm not sure if that's related to this issue or something else though.
Still looking at that.


I think you're on the right track in comment 27. I get the feeling that 
somewhere along the line a result  of 'this is already mounted' changed from a 
success to a failure in systemd, possibly due to the change in mount.c you 
pasted.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1755863

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1755863/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1798457] Re: Provide curtin-requirements and server-ship-live seeds

2018-10-17 Thread Dimitri John Ledkov
** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Adam Conrad (adconrad)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1798457

Title:
  Provide curtin-requirements and server-ship-live seeds

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Provide curtin-requirements and server-ship-live seeds

  and make cdimage use them for server live images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1798457/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1798457] Re: Provide curtin-requirements and server-ship-live seeds

2018-10-17 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/+merge/356996

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/+merge/356997

** Branch linked: lp:~xnox/ubuntu-cdimage/dd-server-ship-live

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/platform/+merge/356999

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1798457

Title:
  Provide curtin-requirements and server-ship-live seeds

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Provide curtin-requirements and server-ship-live seeds

  and make cdimage use them for server live images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1798457/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


[Touch-packages] [Bug 1798457] [NEW] Provide curtin-requirements and server-ship-live seeds

2018-10-17 Thread Dimitri John Ledkov
Public bug reported:

Provide curtin-requirements and server-ship-live seeds

and make cdimage use them for server live images.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1798457

Title:
  Provide curtin-requirements and server-ship-live seeds

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Provide curtin-requirements and server-ship-live seeds

  and make cdimage use them for server live images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1798457/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp


  1   2   >