[Bug 1901648] Re: docker.io package: cannot stat /var/lib/docker.migrating/*

2020-10-28 Thread Eric Johnson
This should probably be filed under the docker.io package instead of
ubuntu-release-upgrader.

** Package changed: ubuntu-release-upgrader (Ubuntu) => docker.io
(Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901648

Title:
  docker.io package: cannot stat /var/lib/docker.migrating/*

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1901648/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1901648] [NEW] docker.io package: cannot stat /var/lib/docker.migrating/*

2020-10-26 Thread Eric Johnson
Public bug reported:

I was running 20.04 and had the docker.io package installed. ZFS root.
I ran do-release-upgrade to upgrade to 20.10. At the end of the upgrade, it 
said it errored on package docker.io

Setting up docker.io (19.03.13-0ubuntu3) ...
mv: cannot stat '/var/lib/docker.migrating/*': No such file or directory
dpkg: error processing package docker.io (--configure):
 installed docker.io package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 docker.io

I've tried 'apt-get install docker.io', it recognizes that it's not
fully installed, but runs into the same error.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubuntu-release-upgrader-core 1:20.10.12
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: skip
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 26 21:59:44 2020
InstallationDate: Installed on 2020-07-16 (103 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: release-upgrade
UpgradeStatus: Upgraded to groovy on 2020-10-26 (0 days ago)
VarLogDistupgradeXorgFixuplog:
 INFO:root:/usr/bin/do-release-upgrade running
 INFO:root:No xorg.conf, exiting

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug dist-upgrade groovy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901648

Title:
  docker.io package: cannot stat /var/lib/docker.migrating/*

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1901648/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788627] Re: package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1

2018-08-25 Thread Ryan Eric Johnson
Ok, this then appears related to another issue that I have been having.
The whiptail dialog has not been appearing when the SecureBoot prompts
have been displaying. I do not know how the DEBIAN_FRONTEND environment
variable has been set to noninteractive. I have never set this variable
and I cannot find anywhere where this is being set on my system.

I got through the installation of the dkms modules by killing the
whiptail process that did not show any dialog. Then I signed the modules
myself with my own key.

I searched for a solution to the whiptail problem but could not find
anything relevant. Perhaps I should just create a question on the
forums. How can I ensure that these dialogs appear properly?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788627

Title:
  package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade:
  installed shim-signed package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1788627/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1788627] [NEW] package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: installed shim-signed package post-installation script subprocess returned error exit status 1

2018-08-23 Thread Ryan Eric Johnson
Public bug reported:

Ubuntu Release
Description:Ubuntu 18.04.1 LTS
Release:18.04

Package installed
shim-signed:
  Installed: 1.34.9.2+13-0ubuntu2
  Candidate: 1.34.9.2+13-0ubuntu2
  Version table:
 *** 1.34.9.2+13-0ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1.34.9+13-0ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

Expected behaviour
Expect triggers to process without error.

Actual behaviour
While processing triggers, errors:

Processing triggers for shim-signed (1.34.9.2+13-0ubuntu2) ...
Running in non-interactive mode, doing nothing.
--- /var/lib/shim-signed/dkms-list  2018-08-23 09:15:24.219075416 -0500
+++ /var/lib/shim-signed/dkms-list.new  2018-08-23 09:15:24.231077094 -0500
@@ -1,2 +1,3 @@
 /var/lib/dkms
+/var/lib/dkms/rtl8812au
 /var/lib/dkms/virtualbox
dpkg: error processing package shim-signed (--configure):
 installed shim-signed package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 shim-signed
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: shim-signed 1.34.9.2+13-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
.proc.sys.kernel.moksbstate_disabled: Error: [Errno 2] No such file or 
directory: '/proc/sys/kernel/moksbstate_disabled'
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Aug 23 09:15:31 2018
EFITables:
 Aug 23 07:19:06 Buddhacarita kernel: efi: EFI v2.31 by INSYDE Corp.
 Aug 23 07:19:06 Buddhacarita kernel: efi:  ESRT=0x9f5dcc18  ACPI=0x9fbfe000  
ACPI 2.0=0x9fbfe014  SMBIOS=0x9fabef98 
 Aug 23 07:19:06 Buddhacarita kernel: secureboot: Secure boot enabled
 Aug 23 07:19:06 Buddhacarita kernel: esrt: Reserving ESRT space from 
0x9f5dcc18 to 0x9f5dcc50.
ErrorMessage: installed shim-signed package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2018-04-29 (115 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
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
SecureBoot: 6   0   0   0   1
SourcePackage: shim-signed
Title: package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade: 
installed shim-signed package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shim-signed (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788627

Title:
  package shim-signed 1.34.9.2+13-0ubuntu2 failed to install/upgrade:
  installed shim-signed package post-installation script subprocess
  returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1788627/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1732790] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of pac

2017-11-16 Thread Ryan Eric Johnson
moved '/lib/udev/hwdb.d/20-sane.hwdb' to /tmp
then got this error:

Unpacking libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) over 
(1.0.27-1~experimental2ubuntu1) ...
dpkg: error processing archive 
/var/cache/apt/archives/libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb 
(--unpack):
 trying to overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is 
different from other instances of package libsane1:i386
dpkg-deb: error: subprocess paste

moved that file to /tmp and install went ahead OK

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732790

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1732790/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1732790] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of pac

2017-11-16 Thread Ryan Eric Johnson
I am wondering if this has something to do with a recent printer driver
installation. Canon Pixma MX492

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732790

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1732790/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1732790] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other instances of p

2017-11-16 Thread Ryan Eric Johnson
Public bug reported:

package failed to update

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libsane1 1.0.27-1~experimental2ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.4
Architecture: amd64
Date: Thu Nov 16 12:06:02 2017
ErrorMessage: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', which 
is different from other instances of package libsane1:i386
InstallationDate: Installed on 2017-06-29 (140 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
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: sane-backends
Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to 
install/upgrade: trying to overwrite shared '/lib/udev/hwdb.d/20-sane.hwdb', 
which is different from other instances of package libsane1:i386
UpgradeStatus: Upgraded to artful on 2017-10-19 (28 days ago)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1732790

Title:
  package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to
  install/upgrade: trying to overwrite shared
  '/lib/udev/hwdb.d/20-sane.hwdb', which is different from other
  instances of package libsane1:i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1732790/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 551950] Re: gnome-bluetooth cannot use pin = 1234

2017-08-19 Thread Eric Johnson
I can also report that in 16.04 LTS that selecting a fixed pin is not an
option in the GUI. I originally posted a question on AskUbuntu and found
my way here.

AskUbuntu Question: https://askubuntu.com/questions/947255/missing-pin-
options-from-bluetooth-pairing-gui

I've attached an image I made combining the two screenshots. The top
half is the buggy version missing the options under the Fixed PIN
category and the bottom half is the complete and correct version.
Unfortunately I do not know what version the good screenshot came from
and I don't have enough rep on SO to post a comment to ask.

I will also join the bug report on gnome-bluetooth too.

** Attachment added: "Screenshot of GUI missing options"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/551950/+attachment/4935410/+files/bugreport.png

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/551950

Title:
  gnome-bluetooth cannot use pin = 1234

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/551950/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1486299] [NEW] fglrx-updates-core 2:15.200-0ubuntu4: fglrx-updates-core kernel module failed to build: No immediate effects. Error appeared upon latest updates.

2015-08-18 Thread Ryan Eric Johnson
Public bug reported:

Please e-mail for further data requests.

ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: fglrx-updates-core 2:15.200-0ubuntu4
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
NonfreeKernelModules: fglrx
.tmp.unity.support.test.0:
 
ApportVersion: 2.17.2-0ubuntu1.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
DKMSKernelVersion: 3.19.0-26-generic
Date: Tue Aug 18 20:01:09 2015
DistUpgraded: 2015-04-26 01:55:21,099 DEBUG enabling apt cron job
DistroCodename: vivid
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Cayman PRO [Radeon HD 6950] [1002:6719] 
(prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:0b00]
InstallationDate: Installed on 2014-11-27 (264 days ago)
InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1)
MachineType: System manufacturer P5K Premium
PackageVersion: 2:15.200-0ubuntu4
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=b48cca6b-a5d3-497d-819f-d199497e1ea7 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.17.25ubuntu1
 apt  1.0.9.7ubuntu4.1
SourcePackage: fglrx-installer-updates
Title: fglrx-updates-core 2:15.200-0ubuntu4: fglrx-updates-core kernel module 
failed to build
UpgradeStatus: Upgraded to vivid on 2015-04-26 (114 days ago)
dmi.bios.date: 06/26/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0204
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5K Premium
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0204:bd06/26/2007:svnSystemmanufacturer:pnP5KPremium:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPremium:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5K Premium
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.1+15.04.20150410.1-0ubuntu1
version.fglrx-installer: fglrx-installer N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.5.2-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.5.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.17.1-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0-1ubuntu2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917-1~exp1ubuntu2.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2build1
xserver.bootTime: Wed Aug 12 17:44:26 2015
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.1-0ubuntu3
xserver.video_driver: fglrx

** Affects: fglrx-installer-updates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package compiz-0.9 ubuntu vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1486299

Title:
  fglrx-updates-core 2:15.200-0ubuntu4: fglrx-updates-core kernel module
  failed to build: No immediate effects. Error appeared upon latest
  updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fglrx-installer-updates/+bug/1486299/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs