[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-04 Thread Jon Brase
I have encountered this issue trying a fresh install of Kubuntu 20.04.1.
The entire reason that I tried a fresh install is that trying to upgrade
my existing system from Ubuntu Mate 18.04 to 20.04 resulted in the
upgrade finishing with errors and leaving my system in an unusable state
(fortunately, I have a full backup, so rolling back a failed upgrade is
painless, other than the time consumed). I don't know if the root cause
of both issues is the same or not.

My graphics card is an NVidia GeForce GTX 750 Ti. /var/log/syslog from
the failed ground-up installation is attached (I attempted installing
twice in the live session with failures both times). I will attempt to
find time to retry the upgrade and attach the syslog from that so we can
see if the root cause is the same (I have already rolled the filesystem
back from backup for the previous attempts, so I don't have a syslog for
them).

The end result is that I have no upgrade path from 18.04 to 20.04.

-- 
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/1871268

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  

[Touch-packages] [Bug 1871268] Re: Installation fails when "Install Third-Party Drivers" is selected

2020-10-04 Thread Jon Brase
** Attachment added: "The attachment for my comment above does not seem to have 
taken. This is /var/log/syslog for a failed ground-up Kubuntu 20.04 
installation"
   
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1871268/+attachment/5417422/+files/syslog

-- 
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/1871268

Title:
  Installation fails when  "Install Third-Party Drivers" is selected

Status in GLibC:
  New
Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Confirmed
Status in glibc package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  Confirmed
Status in glibc source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Confirmed
Status in glibc source package in Focal:
  Invalid

Bug description:
  Please use the latest daily installer images if you would like to enable 
third-party drivers during installation:
  http://www.cdimage.ubuntu.com/focal/daily-live/current/

  [Original Bug Text]

  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
  /plugininstall.py: Downloads verified successfully
  ubiquity: Error in function: install
  /plugininstall.py: Exception during installation:
  /plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , 
E:Could not perform immediate configuration on 'libgcc-s1:i386'. Please see man 
5 apt.conf under APT::Immediate-Configure for details. (2)
  /plugininstall.py:

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubiquity 20.04.9
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CasperVersion: 1.442
  Date: Mon Apr  6 20:17:07 2020
  InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
  LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   LANGUAGE=es_EC.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_EC.UTF-8
   LC_NUMERIC=C.UTF-8
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1871268/+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 1897339] [NEW] Documentation missing for "ip tuntap"

2020-09-25 Thread Jon Brase
Public bug reported:

Ubuntu 18.04.5
iproute2 4.15.0-2ubuntu1.2
iproute2-doc 4.15.0-2ubuntu1.2


Most of the subcommands for /sbin/ip are documented in a manpage with a name of 
the form "ip-$SUBCOMMAND(8)", for example "ip address" is documented at 
"ip-address(8)".

However, ip tuntap seems to be completely undocumented, other than the
one-line description given in ip(8): "tuntap - manage TUN/TAP devices."
No manpage is pulled in with the iproute2 package, as with the other ip
manpages, nor with the iproute2-doc package. This also seems to be the
case with "ip mrule".

Expected behavior: Some package can be installed that contains a manpage
covering "ip tuntap".

Actual behavior: No manpage for "ip tuntap" exists in either the package
that contains the /sbin/ip binary, nor the corresponding -doc package.

** Affects: iproute2 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Documentation missing for "ip tuntap"

Status in iproute2 package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04.5
  iproute2 4.15.0-2ubuntu1.2
  iproute2-doc 4.15.0-2ubuntu1.2

  
  Most of the subcommands for /sbin/ip are documented in a manpage with a name 
of the form "ip-$SUBCOMMAND(8)", for example "ip address" is documented at 
"ip-address(8)".

  However, ip tuntap seems to be completely undocumented, other than the
  one-line description given in ip(8): "tuntap - manage TUN/TAP
  devices." No manpage is pulled in with the iproute2 package, as with
  the other ip manpages, nor with the iproute2-doc package. This also
  seems to be the case with "ip mrule".

  Expected behavior: Some package can be installed that contains a
  manpage covering "ip tuntap".

  Actual behavior: No manpage for "ip tuntap" exists in either the
  package that contains the /sbin/ip binary, nor the corresponding -doc
  package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1897339/+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 1511875] Re: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container

2017-02-04 Thread Jon Brase
As an update to my comment above, while the release upgrader hung and
did not finish the upgrade, it *did* disable all my ppa's and switch
over to the Xenial repositories, which ended up leaving my system broken
next time I tried pulling in updates (thinking the upgrade had failed
completely and the system was still using Trusty repositories). I'm not
sure what packages are at Xenial versions and what packages are at still
at Trusty versions, there seems to be a mix.

So it seems I can't expect Ubuntu to upgrade between LTS versions
without barfing all over itself. Gee, what fun.

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

Title:
  Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container

Status in lxc package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  When I try to upgrade from 15.10 Wily to 16.04 Xenial (actual
  development version) within an LXC container, the upgrade script hangs
  at the message „Calculating the changes”.

  Steps to reproduce:
  1. Make an LXC container with Wily (quickest option is to use lxc-create -t 
download, choose ubuntu, wily, amd64/i386).
  2. Boot up the container, log in, „apt-get -y install 
ubuntu-release-upgrader-core”.
  3. Start the upgrade with „do-release-upgrade -d”.

  You will see that the upgrade process will hang at the message
  „Calculating the changes”.

  The process which hangs: „/usr/bin/python3 /tmp/ubuntu-release-
  upgrader-1mpotr5d/xenial --mode=server --frontend=DistUpgradeViewText
  --devel-release”

  With strace, it is revealed that the process hangs at a „futex” system call:
  futex(0x7f419c10, FUTEX_WAIT_PRIVATE, 0, NULL

  This system call never returns, the process must be interrupted with
  CTRL-C or kill.

  Upgrading to any previous release within an LXC container works
  without problems, therefore I consider it as a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1511875/+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 1511875] Re: Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container

2016-11-29 Thread Jon Brase
I'm running into the same thing trying to upgrade from 14.04 to 16.04.

After Googling around about the issue, this link at first looked like a
promising lead, as I'm running into this on Haswell hardware and I have
Core2 hardware that was unaffected:

https://groups.google.com/forum/#!topic/mechanical-sympathy/QbmpZxp6C64

So I tried using a custom-compiled 4.4 series kernel to see if that
resolved the issue, and it does cause the upgrade to stop hanging in the
futex wait channel, but, unfortunately, does not cause the upgrade to
stop hanging. On the 4.4 kernel, system monitor shows the process to be
in waiting channel 0 instead of the futex wait channel, but gdb shows
the process to be hung in "sem_wait()".

I am running into this on bare hardware, not a container or VM.

Given that I'm seeing it on a Haswell machine but my Core2 laptop did
not experience the hang, and given that using a newer kernel version
changed the specifics of how the hang is occuring, it seems to be
related to the kernel bug discussed at the Google Groups link above, but
the kernel bug can't be the whole story, or else the new kernel would
have fixed it.

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

Title:
  Can't upgrade from 15.10 Wily to 16.04 Xenial in LXC container

Status in lxc package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  When I try to upgrade from 15.10 Wily to 16.04 Xenial (actual
  development version) within an LXC container, the upgrade script hangs
  at the message „Calculating the changes”.

  Steps to reproduce:
  1. Make an LXC container with Wily (quickest option is to use lxc-create -t 
download, choose ubuntu, wily, amd64/i386).
  2. Boot up the container, log in, „apt-get -y install 
ubuntu-release-upgrader-core”.
  3. Start the upgrade with „do-release-upgrade -d”.

  You will see that the upgrade process will hang at the message
  „Calculating the changes”.

  The process which hangs: „/usr/bin/python3 /tmp/ubuntu-release-
  upgrader-1mpotr5d/xenial --mode=server --frontend=DistUpgradeViewText
  --devel-release”

  With strace, it is revealed that the process hangs at a „futex” system call:
  futex(0x7f419c10, FUTEX_WAIT_PRIVATE, 0, NULL

  This system call never returns, the process must be interrupted with
  CTRL-C or kill.

  Upgrading to any previous release within an LXC container works
  without problems, therefore I consider it as a regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1511875/+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