Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen

[Blake Johal]

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

Title:
  AMD GPUs fail with null pointer dereference when IOMMU enabled,
  leading to black screen

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


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

Re: [Bug 2068738] Re: AMD GPUs fail with null pointer dereference when IOMMU enabled, leading to black screen

[Blake Johal]

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

Title:
  AMD GPUs fail with null pointer dereference when IOMMU enabled,
  leading to black screen

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


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

[Bug 2071360] [NEW] Kernel 5.15.113

[Blake Johal]

Public bug reported:

Kernel 5.15.113 does not load graphic drivers during booting

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

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

Title:
  Kernel 5.15.113

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


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

[Bug 1971007] [NEW] package usrmerge 25ubuntu2 failed to install/upgrade: installed usrmerge package post-installation script subprocess returned error exit status 1

[John Blake]

Public bug reported:

​​  
#1930573 usrmerge error after upgrading from 21.10 to 22.04 LTS

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: usrmerge 25ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-41.46-generic 5.13.19
Uname: Linux 5.13.0-41-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_uvm 
nvidia_drm nvidia_modeset nvidia r8168
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Apr 29 18:35:54 2022
ErrorMessage: installed usrmerge package post-installation script subprocess 
returned error exit status 1
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2
 apt  2.4.5
SourcePackage: usrmerge
Title: package usrmerge 25ubuntu2 failed to install/upgrade: installed usrmerge 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago)

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


** Tags: amd64 apport-package jammy need-duplicate-check uec-images

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

Title:
  package usrmerge 25ubuntu2 failed to install/upgrade: installed
  usrmerge package post-installation script subprocess returned error
  exit status 1

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


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

[Bug 1959725] [NEW] Segfault from Native.sd_journal_get_fd

[Blake Rouse]

Public bug reported:

The version of libsystemd0 Ubuntu 20.04 has the following issue present
in the package:

https://github.com/systemd/systemd/issues/15528
https://github.com/ledbettj/systemd-journal/issues/88

It was fixed here:

https://github.com/systemd/systemd/commit/2b6df46d21abe8a8b7481e420588a9a129699cf9

It would be great to get this fixed in the LTS.

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

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

Title:
  Segfault from Native.sd_journal_get_fd

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


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

[Bug 1949261] [NEW] fatal error on grub install

[bryan blake]

Public bug reported:

doing a fresh install on HP15 laptop with a clean reformat of hard drive
during grub install to sda1 receive fatal errror message

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckMismatches: 
./pool/main/m/mouseemu/mouseemu_0.16-0ubuntu10_amd64.deb
CasperMD5CheckResult: skip
CasperVersion: 1.445.1
Date: Sat Oct 30 13:14:40 2021
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal ubiquity-20.04.15.17 ubuntu

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

Title:
  fatal error on grub install

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


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

[Bug 965791] Re: unetbootin crashed with SIGSEGV in QThreadPrivate::start()

[blake kinley]

** Changed in: unetbootin (Ubuntu)
 Assignee: (unassigned) => blake kinley (bl8k3)

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

Title:
  unetbootin crashed with SIGSEGV in QThreadPrivate::start()

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


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

[Bug 1620628] Re: Only get a grey window

[blake kinley]

** Changed in: unetbootin (Ubuntu)
 Assignee: Gerhard Pirretti (gerhard272) => blake kinley (bl8k3)

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

Title:
  Only get a grey window

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


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

[Bug 1889548] Re: ssh using gssapi will enforce FILE: credentials cache

[Toby Blake]

Hi there,

I'm afraid I haven't had much time to look properly into this recently,
but it remains on my list.

In the meantime, I've submitted an enhancement request upstream:

https://bugzilla.mindrot.org/show_bug.cgi?id=3203

Cheers
Toby


** Bug watch added: OpenSSH Portable Bugzilla #3203
   https://bugzilla.mindrot.org/show_bug.cgi?id=3203

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

Title:
  ssh using gssapi will enforce FILE: credentials cache

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

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

[Bug 1889548] Re: ssh using gssapi will enforce FILE: credentials cache

[Toby Blake]

Hi Christian,

Again, thanks for the above.

https://bugzilla.mindrot.org/show_bug.cgi?id=2775, in particular, looks
interesting, as it seems to be an attempt to bring the relevant ccache
patches up to date for version 8.  e.g. we have been patching our SL
systems additionally for
https://bugzilla.redhat.com/show_bug.cgi?id=1199363.

I'll give this a try and report back.  I'll hold off on reporting this
as a bug upstream until I've tried the patch(es).

Cheers
Toby


** Bug watch added: Red Hat Bugzilla #1199363
   https://bugzilla.redhat.com/show_bug.cgi?id=1199363

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

Title:
  ssh using gssapi will enforce FILE: credentials cache

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

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

[Bug 1889548] Re: ssh using gssapi will enforce FILE: credentials cache

[Toby Blake]

Hi Christian,

Thanks for your reply (and for the links).  I agree that a configurable
option coming from upstream would be the preferred option.  I'll submit
a bug upstream accordingly and note the ID here.

I note there's a patch referenced in the openssh mailing list link,
unfortunately the link is a 404 - I'll see if I can track it down via
other means.  On this topic, we've been using ssh on scientific linux
for a number of years now and that is patched to use the default ccache
name.  It would be interesting to see if it's the same or similar as the
404 patch above.

Depending on the outcome of my upstream bug report, I'll see if I can
port any patches we use to the current ubuntu/upstream code base.

As to your final question re: regression - I don't think so, looking at
the code, but we are only now in the process of converting desktop
machines to ubuntu.

Cheers
Toby

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

Title:
  ssh using gssapi will enforce FILE: credentials cache

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

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

[Bug 1889548] [NEW] ssh using gssapi will enforce FILE: credentials cache

[Toby Blake]

Public bug reported:

Hi,

ssh connections from a client with the following in ssh_config...

GSSAPIAuthentication yes
GSSAPIDelegateCredentials yes

... to an ubuntu 20.04 machine result in KRB5CCNAME being set to
'FILE:/tmp/krb5cc_[uid]_[random]' despite the following in
/etc/krb5.conf:

[libdefaults]
 ...
 default_ccache_name = KEYRING:persistent:%{uid}

This means that we cannot enforce a policy to use KEYRING ccaches across
our systems.  Authentications which go via the pam stack (e.g. login to
the machine at the console or over ssh using a password) can be
configured to use a KEYRING ccache, via libpam-krb5 settings in
/etc/krb5.conf.

The FILE: setting seems to be hard-coded in the openssh code (auth-
krb5.c).  It would be great if ssh(gssapi-with-mic) connections either
(a) set KRB5CCNAME to the default_ccache_name value, if set in
/etc/krb5.conf, or (b) didn't set KRB5CCNAME at all, so the system
default is used.

Many thanks
Toby Blake
School of Informatics
University of Edinburgh

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

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

Title:
  ssh using gssapi will enforce FILE: credentials cache

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

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

[Bug 1873614] Re: Definition of add_mountroot_fail_hook doesnt match lvm2's usage

[Blake Anderson]

Confirmed, I get the message in #1 every boot. 20.04

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

Title:
  Definition of add_mountroot_fail_hook doesnt match lvm2's usage

To manage notifications about this bug go to:
https://bugs.launchpad.net/initramfs-tools/+bug/1873614/+subscriptions

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

[Bug 1875759] [NEW] keeps crashing

[Billy Blake]

Public bug reported:

not sure it's a bug

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-96.97~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.23
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
Date: Tue Apr 28 18:10:36 2020
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 
[1002:9712] (prog-if 00 [VGA controller])
   Subsystem: Toshiba America Info Systems RS880M [Mobility Radeon HD 
4225/4250] [1179:ff1f]
InstallationDate: Installed on 2020-04-19 (9 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: TOSHIBA Satellite L505D
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic 
root=UUID=4e2c2708-04af-4c97-ae5b-247752b16fe1 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/07/2009
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.00
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Base Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: AMD
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.00:bd09/07/2009:svnTOSHIBA:pnSatelliteL505D:pvrPSLV6U-01F009:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone:
dmi.product.family: Type1Family
dmi.product.name: Satellite L505D
dmi.product.version: PSLV6U-01F009
dmi.sys.vendor: TOSHIBA
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Apr 28 17:50:45 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 ubuntu xenial

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

Title:
  keeps crashing

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

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

[Bug 947664] Re: Unpacking linux-headers unbelievably slow in Lubuntu Precise (Beta 1)

[Blake McBride]

I tried it by comparing the same VM with and without that setting. Here
is what I found:

With "Use Host I/O Cache" disabled, booting took 40 seconds.

With "Use Host I/O Cache" enabled, booting took 12 seconds.


With "Use Host I/O Cache" disabled, doing a mini update took a few minutes.

With "Use Host I/O Cache" enabled, doing a mini update occurred nearly
instantaneously.

I'm convinced.

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

Title:
  Unpacking linux-headers unbelievably slow in Lubuntu Precise (Beta 1)

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

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

[Bug 1858309] [NEW] [To Be Filled By O.E.M., Nvidia GPU 92 HDMI/DP, Digital Out, HDMI] Underruns, dropouts or crackling sound, Only started after upgrading from 19.10 to 20.04, amd x570 chipset

[Blake Richard]

Public bug reported:

Working find on Ubuntu 19.10, started having a cracking sound in the
audio immediately after upgrading to 20.04.  Tested in Firefox and
Chrome playing video/audio.

AMD x570 chipset

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  blaker 1659 F pulseaudio
 /dev/snd/pcmC0D7p:   blaker 1659 F...m pulseaudio
 /dev/snd/controlC1:  blaker 1659 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan  4 21:30:04 2020
InstallationDate: Installed on 2019-12-27 (9 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: HDA NVidia - HDA NVidia
Symptom_Jack: Digital Out, HDMI
Symptom_PulseAudioLog: Jan 04 20:52:04 blaker-desktop dbus-daemon[1049]: 
[system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.32' (uid=124 pid=1269 
comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [To Be Filled By O.E.M., Nvidia GPU 92 HDMI/DP, Digital Out, HDMI] 
Underruns, dropouts or crackling sound
UpgradeStatus: Upgraded to focal on 2020-01-05 (0 days ago)
dmi.bios.date: 06/12/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: X570 Pro4
dmi.board.vendor: ASRock
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.:bvrP1.00:bd06/12/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX570Pro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: 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.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  [To Be Filled By O.E.M., Nvidia GPU 92 HDMI/DP, Digital Out, HDMI]
  Underruns, dropouts or crackling sound, Only started after upgrading
  from 19.10 to 20.04, amd x570 chipset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1858309/+subscriptions

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

[Bug 1852851] [NEW] Dell Pen PN579X exhibits upstream linuxwacom eraser bug

[Blake Buhlig]

Public bug reported:

I found the 'Dell Premium Active Pen (PN579X)' that I just received and
as presently sold by Dell elicits the problem described at
https://github.com/linuxwacom/xf86-input-wacom/issues/39.  I generated a
patch file from https://github.com/linuxwacom/xf86-input-
wacom/commit/3b338312eb275f2d9a602805931fa47d863a0209 and applied it to
the source, rebuilt, reinstalled and can confirm that it did resolve the
issue. The upstream fix is based against a newer version of the package.
To backport, I did need to resolve a minor conflict so that would apply
cleanly to the current version in eoan. I uploaded the patchfile as an
attachment.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xserver-xorg-input-wacom 1:0.36.1-0ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-22.24-generic 5.3.7
Uname: Linux 5.3.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 16 06:19:30 2019
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
InstallationDate: Installed on 2019-10-31 (16 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
MachineType: Dell Inc. XPS 13 7390 2-in-1
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-22-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xf86-input-wacom
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/02/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.9
dmi.board.name: 06CDVY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.9:bd08/02/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390 2-in-1
dmi.product.sku: 08B0
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

** Affects: xf86-input-wacom (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan ubuntu

** Attachment added: "patch file applied to the quilt for 
xserver-xorg-input-wacom package"
   
https://bugs.launchpad.net/bugs/1852851/+attachment/5305871/+files/0001-Ignore-ABS_MISC-as-a-source-of-device-type-informati.patch

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

Title:
  Dell Pen PN579X exhibits upstream linuxwacom eraser bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1852851/+subscriptions

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

[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken

[Blake Rouse]

Release 2.4.3 debdiff.

** Description changed:

- Am running an HA MAAS, but every few days named gets stuck on one of the
- region controllers.
+ [Impact]
  
- systemd thinks the service is running, but it doe not respond to any
+  * systemd thinks the service is running, but it does not respond to any
  commands or requests. Also, it doesn't respond to signals other than
  kill -9. service restarts hang, rndc hangs.
  
- I have attached logs and a core dump of named.
+  * being that the deadlock is in bind9 that ships in bionic the issue
+ needs to be backported to 2.4.3 so MAAS from the archive in bionic can
+ handle the deadlock and get bind9 unstuck.
+ 
+  * change in MAAS watches for this case to occur with bind9, then MAAS
+ will force kill the service and restart it.
+ 
+ [Test Case]
+ 
+  * very hard to reproduce but the issue occurs when bind9 deadlocks, it
+ response to nothing over the network or rndc. SIGTERM does not kill it
+ only SIGKILL works to force kill the process and get systemd to restart
+ it.
+ 
+ 
+ [Regression Potential] 
+ 
+  * possible that bind9 will not be started correctly or possible that
+ bind9 will be placed into a forever restart loop

** Patch added: "maas_2.4.3.debdiff"
   
https://bugs.launchpad.net/maas/+bug/1710278/+attachment/5302068/+files/maas_2.4.3.debdiff

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

Title:
  [2.3a1] named stuck on reload, DNS broken

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

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

[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken

[Blake Rouse]

** Changed in: maas (Ubuntu Bionic)
   Status: Confirmed => In Progress

** Changed in: maas (Ubuntu Bionic)
 Assignee: (unassigned) => Blake Rouse (blake-rouse)

** Also affects: maas/2.4
   Importance: Undecided
   Status: New

** Changed in: maas/2.4
   Status: New => Fix Committed

** Changed in: maas/2.4
Milestone: None => 2.4.3

** Changed in: maas/2.4
 Assignee: (unassigned) => Blake Rouse (blake-rouse)

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

Title:
  [2.3a1] named stuck on reload, DNS broken

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

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

[Bug 1848982] [NEW] NVIDIA VER 340.107 crashes steam

[Blake]

Public bug reported:

NVIDIA binary driver VER 340.17 is crashing steam. If I purge all NVIDIA
drivers Steam runs successfully from Nouveau, but seems to have
performance issues in game. Steam support was unhelpful and referred me
to anyone else.

Steam output from terminal is:

Running Steam on ubuntu 18.04 64-bit
STEAM_RUNTIME is enabled automatically
Pins up-to-date!
Installing breakpad exception handler for appid(steam)/version(1570046470)
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Installing breakpad exception handler for appid(steam)/version(1570046470)
Installing breakpad exception handler for appid(steam)/version(1570046470)
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Installing breakpad exception handler for appid(steam)/version(1570046470)
STEAM_RUNTIME_HEAVY: ./steam-runtime-heavy
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
[2019-10-20 23:14:06] Startup - updater built Oct  2 2019 18:45:27
Looks like steam didn't shutdown cleanly, scheduling immediate update check
[2019-10-20 23:14:06] Checking for update on startup
[2019-10-20 23:14:06] Checking for available updates...
[2019-10-20 23:14:06] Downloading manifest: 
client-download.steampowered.com/client/steam_client_ubuntu12
[2019-10-20 23:14:07] Download skipped: /client/steam_client_ubuntu12 version 
1570046470, installed version 1570046470
[2019-10-20 23:14:07] Nothing to do
[2019-10-20 23:14:07] Verifying installation...
[2019-10-20 23:14:07] Performing checksum verification of executable files
[2019-10-20 23:14:07] Verification complete
glXChooseVisual failed
glXChooseVisual failedMain.cpp (332) : Assertion Failed: Fatal Error: 
glXChooseVisual failed
Main.cpp (332) : Assertion Failed: Fatal Error: glXChooseVisual failed
Installing breakpad exception handler for appid(steam)/version(1570046470)
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
[1020/231407.890104:INFO:crash_reporting.cc(242)] Crash reporting enabled for 
process: browser
assert_20191020231407_6.dmp[4562]: Uploading dump (out-of-process)
/tmp/dumps/assert_20191020231407_6.dmp
[1020/231407.906715:WARNING:crash_reporting.cc(281)] Failed to set crash key: 
UserID with value: 0
[1020/231407.906773:WARNING:crash_reporting.cc(281)] Failed to set crash key: 
BuildID with value: 1570042210
[1020/231407.906777:WARNING:crash_reporting.cc(281)] Failed to set crash key: 
SteamUniverse with value: Public
[1020/231407.906780:WARNING:crash_reporting.cc(281)] Failed to set crash key: 
Vendor with value: Valve
assert_20191020231407_6.dmp[4562]: Finished uploading minidump 
(out-of-process): success = yes
assert_20191020231407_6.dmp[4562]: response: 
CrashID=bp-1182d0aa-9897-4e1e-8016-1d5d82191020
assert_20191020231407_6.dmp[4562]: file 
''/tmp/dumps/assert_20191020231407_6.dmp'', upload yes: 
''CrashID=bp-1182d0aa-9897-4e1e-8016-1d5d82191020''

** Affects: nvidia-graphics-drivers-340 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  NVIDIA VER 340.107 crashes steam

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1848982/+subscriptions

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

[Bug 1750371] Re: sudo maas init --mode region fails

[Blake Rouse]

Are you re-initializing or on fresh install you hit this issue?

>From the description of the bug I cannot tell.

** Changed in: maas
   Status: New => Incomplete

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

Title:
  sudo maas init --mode region fails

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

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

[Bug 1847058] Re: MAAS deployment failed with vgchange command

[Blake Rouse]

** Changed in: maas
   Status: New => Invalid

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

Title:
  MAAS deployment failed with vgchange command

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

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

[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken

[Blake Rouse]

We are current working on getting this backported to 2.4.

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

Title:
  [2.3a1] named stuck on reload, DNS broken

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

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

[Bug 1743595] Re: modprobing mlx5_core doesn't bring the interface up

[Blake Rouse]

** Changed in: maas
   Status: New => Invalid

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

Title:
  modprobing mlx5_core doesn't bring the interface up

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

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

[Bug 1594317] Re: Cannot start lxd-bridge.service when MAAS is managing DNS

[Blake Rouse]

** Changed in: maas
   Status: New => Triaged

** Changed in: maas
   Importance: Undecided => Low

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

Title:
  Cannot start lxd-bridge.service when MAAS is managing DNS

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

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

[Bug 1820967] Re: MAAS failing to commission HP ProLiant DL385 G7 (AMD Opteron 6172)

[Blake Rouse]

This seems to be an issue with the kernel and not an issue with MAAS
directly. Which Ubuntu release is set as the commissioning release on
the Global Settings page? If you can provide the full console log of the
boot that would be helpful as well.

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

** Changed in: maas
   Status: New => Invalid

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

Title:
  MAAS failing to commission HP ProLiant DL385 G7 (AMD Opteron 6172)

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

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

[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken

[Blake Rouse]

** Merge proposal linked:
   https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/371218

** Changed in: maas/2.7
   Status: New => In Progress

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

Title:
  [2.3a1] named stuck on reload, DNS broken

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

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

[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken

[Blake Rouse]

Last resolution update:

The bind9 source package should be modified to generate 2 binary
versions of bind9.

bind9 -> standard multi-threaded bind9 (main)
bind9-single -> single-threaded bind9 (universe)

This will allow security updates to still be handled with the source
bind9 package generating both versions of the binary package.

Once bind9-single is in the archive MAAS will update its dependencies to
depend on either bind9 or bind9-single. Allowing bind9-single to be
installed in replace of bind9 and MAAS will not try to pull the default
bind9 when upgraded.

Note: "bind9-single" is just a name I am using for this comment.

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

Title:
  [2.3a1] named stuck on reload, DNS broken

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

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

[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken

[Blake Rouse]

** Changed in: maas/2.7
   Status: Fix Released => New

** Changed in: maas/2.6
 Assignee: (unassigned) => Blake Rouse (blake-rouse)

** Changed in: maas/2.6
Milestone: None => 2.6.1

** Changed in: maas/2.7
Milestone: 2.3.0alpha2 => 2.7.0alpha1

** Changed in: bind9 (Ubuntu)
 Assignee: (unassigned) => Blake Rouse (blake-rouse)

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

Title:
  [2.3a1] named stuck on reload, DNS broken

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

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

[Bug 1831134] Re: Pods Cannot allocate memory, even with memory_over_commit_ratio set 10.0

[Blake Rouse]

No we do not ensure that. We leave that up to the user to define a
proper over-commit ratio for their systems.

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

Title:
  Pods Cannot allocate memory, even with memory_over_commit_ratio set
  10.0

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

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

[Bug 1804861] Re: MTU size defined on /etc/netplan/50-cloud-init.yaml not applied

[Blake Rouse]

** Changed in: maas (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  MTU size defined on /etc/netplan/50-cloud-init.yaml not applied

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

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

[Bug 1822007] Re: Grub fails to request the /grub/grub.cfg over HTTP when booting with UEFI HTTP

[Blake Rouse]

Attached is the packet capture.

** Attachment added: "GRUB2 EFI HTTP Boot Packet Capture"
   
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1822007/+attachment/5254210/+files/grub2-efi.pcap

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

Title:
  Grub fails to request the /grub/grub.cfg over HTTP when booting with
  UEFI HTTP

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

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

[Bug 1787630] Re: [FFe] Include HTTP support in pre-build GRUB module

[Blake Rouse]

I have verified that the proposed package in cosmic works as expected. I
performed the following steps with MAAS.

0) Provide kernel and initrd on an HTTP server on the network.
1) Boot from the network in UEFI mode using grub's grubnet.efi binary.
2) Provided the following config:

linuxefi http:/// 
initrdefi http:///
boot

Grub successfully loaded the kernel and initrd from the HTTP server and
booted the kernel with attached initrd.

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

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

Title:
  [FFe] Include HTTP support in pre-build GRUB module

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

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

[Bug 1822007] Re: Grub fails to request the /grub/grub.cfg over HTTP when booting with UEFI HTTP

[Blake Rouse]

Seems that SUSE supports this in their grub because its well documented
on their site:

https://en.opensuse.org/UEFI_HTTPBoot_Server_Setup

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

Title:
  Grub fails to request the /grub/grub.cfg over HTTP when booting with
  UEFI HTTP

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

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

[Bug 1822007] Re: Grub fails to request the /grub/grub.cfg over HTTP when booting with UEFI HTTP

[Blake Rouse]

This bug blocks the progress of completion of bug:
https://bugs.launchpad.net/maas/+bug/1820983

** Changed in: grub2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Grub fails to request the /grub/grub.cfg over HTTP when booting with
  UEFI HTTP

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

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

[Bug 1822007] [NEW] Grub fails to request the /grub/grub.cfg over HTTP when booting with UEFI HTTP

[Blake Rouse]

Public bug reported:

While implementing the complete UEFI HTTP booting path for MAAS I have
hit a roadblock. Grub2 is loaded but then fails to request the
/grub/grub.cfg as it does when booting with UEFI PXE (aka. TFTP).

The dhcpd.conf has the following in it to tell the UEFI firmware to load
the bootx64.efi (signed-shim) over HTTP.

} elsif option arch = 00:0f {
# uefi_amd64_http
filename "http://192.168.122.2:5248/bootx64.efi;;
option vendor-class-identifier "HTTPClient";
} elsif option arch = 00:10 {
# uefi_amd64_http
filename "http://192.168.122.2:5248/bootx64.efi;;
option vendor-class-identifier "HTTPClient";
} elsif option arch = 00:0B {

This works correctly because the UEFI firmware does load the bootx64.efi
then the shim loads the grubx64.efi over HTTP.

2019-03-27 23:21:59 provisioningserver.rackdservices.http: [info] bootx64.efi 
requested by 192.168.122.193
2019-03-27 23:21:59 provisioningserver.rackdservices.http: [info] grubx64.efi 
requested by 192.168.122.193

No other requests are received from that point forward. Grub2 reports
the following error:

Error: Unexpected network error.

Checking the grub2 environment it does seem wierd that none of the
networking variables are set they are completely blank.

grub_cpu=x86_64
grub_platform=efi
net_default_ip=(null)
net_default_mac=(null)
net_default_server=
package_version=2.02+dfsg1-12ubuntu2
prefix=
pxe_default_server=
root=

** Affects: grub2 (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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

Title:
  Grub fails to request the /grub/grub.cfg over HTTP when booting with
  UEFI HTTP

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

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

[Bug 1787630] Re: [FFe] Include HTTP support in pre-build GRUB module

[Blake Rouse]

I have verified that the proposed package in bionic works as expected. I
performed the following steps with MAAS.

0) Provide kernel and initrd on an HTTP server on the network.
1) Boot from the network in UEFI mode using grub's grubnet.efi binary.
2) Provided the following config:

linuxefi http:/// 
initrdefi http:///
boot

Grub successfully loaded the kernel and initrd from the HTTP server and
booted the kernel with attached initrd.

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

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

Title:
  [FFe] Include HTTP support in pre-build GRUB module

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

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

[Bug 1808635] [NEW] revert to older software

[blake connell]

Public bug reported:

no boot just red squar on screan

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
Uname: Linux 4.4.0-66-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompositorRunning: None
Date: Sat Dec 15 10:16:34 2018
DistUpgraded: 2018-08-28 08:03:16,046 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 NVIDIA Corporation GT200GL [Quadro FX 3800] [10de:05ff] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation GT200GL [Quadro FX 3800] [10de:0661]
InstallationDate: Installed on 2016-09-30 (806 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Hewlett-Packard HP Z400 Workstation
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-66-generic 
root=UUID=2aeb5d71-8879-4ee6-8084-763dda365c5a ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-08-28 (109 days ago)
dmi.bios.date: 07/15/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786G3 v03.57
dmi.board.asset.tag: 2UA935021D
dmi.board.name: 0AE4h
dmi.board.vendor: Hewlett-Packard
dmi.board.version: C
dmi.chassis.asset.tag: 2UA935021D
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786G3v03.57:bd07/15/2013:svnHewlett-Packard:pnHPZ400Workstation:pvr:rvnHewlett-Packard:rn0AE4h:rvrC:cvnHewlett-Packard:ct6:cvr:
dmi.product.name: HP Z400 Workstation
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Tue Aug 28 22:26:33 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  revert to older software

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

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

[Bug 1316648] Re: gedit hangs on start

[Craig Blake]

Sorry I am no longer using Ubuntu so I cannot say if the bug still
exists.

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

Title:
  gedit hangs on start

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

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

[Bug 1801899] Re: cannot install with python3.7 as default async is a reserved keyword

[Blake Rouse]

** Changed in: maas
Milestone: next => 2.5.0rc1

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

Title:
  cannot install with python3.7 as default async is a reserved keyword

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

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

[Bug 1801899] Re: cannot install with python3.7 as default async is a reserved keyword

[Blake Rouse]

** Changed in: maas
 Assignee: (unassigned) => Blake Rouse (blake-rouse)

** Changed in: maas
   Status: Confirmed => In Progress

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

Title:
  cannot install with python3.7 as default async is a reserved keyword

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

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

[Bug 1792905] Re: [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

[Blake Rouse]

Urgency is high, this slows down every booting machine of MAAS by 1:30
seconds, that is a long boot time just to get the OS to install or to
commission the machine.

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

Title:
  [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1792905/+subscriptions

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

[Bug 1792905] Re: [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

[Blake Rouse]

Here is the output log:

http://paste.ubuntu.com/p/KfTWC5ghwR/

You can't really see the iSCSI error in the console log.

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

Title:
  [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

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

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

[Bug 1792905] Re: [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

[Blake Rouse]

** Also affects: open-iscsi
   Importance: Undecided
   Status: New

** No longer affects: open-iscsi

** Also affects: open-iscsi (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [2.5] iSCSI systemd services fails and blocks for 1 min 30 secconds

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

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

[Bug 1776025] [NEW] Fresh Install from persistent USB "alongside Windows 7" crashed

[Blake Tannen]

Public bug reported:

See title.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
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
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  9 14:53:12 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
cdrom-detect/try-usb=true persistent noprompt floppy.allowed_drive_mask=0 
ignore_uuid boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ubiquity-18.04.14 ubuntu

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

Title:
  Fresh Install from persistent USB "alongside Windows 7" crashed

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

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

[Bug 1766886] [NEW] xorg

[Dave Blake]

Public bug reported:

On boot up I get a message alot are getting ,, Graphics need
reconfigured booting in Low Graphics Mode, After log in I get a message
about a system error referencing the file usr/lib/xorg/xorg

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-121.145-generic 4.4.117
Uname: Linux 4.4.0-121-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
BootLog:
 [  OK  ] Started Show Plymouth Boot Screen.
  Starting Hold until boot process finishes up...
  Starting Light Display Manager...
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Apr 25 10:04:36 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.4.0-116-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-119-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-121-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-98-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02aa]
   Subsystem: Dell Mobile 4 Series Chipset Integrated Graphics Controller 
[1028:02aa]
InstallationDate: Installed on 2014-05-05 (1450 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Dell Inc. Inspiron 1545
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-121-generic 
root=UUID=cafde4bc-89e6-47f2-a023-feb7fdcf8f08 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/09/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0G848F
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd04/09/2009:svnDellInc.:pnInspiron1545:pvr:rvnDellInc.:rn0G848F:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Inspiron 1545
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Apr 25 10:00:20 2018
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  xorg

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

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

[Bug 1743249] Re: High IO on the system prevents MAAS to provide PXE config in a timely manner (less than 30 secs)

[Blake Rouse]

** Merge proposal linked:
   https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/341132

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

Title:
  High IO on the system prevents MAAS to provide PXE config in a timely
  manner (less than 30 secs)

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

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

[Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB

[Blake Riley]

I experienced this issue twice in the last 24 hours on 16.04. Both
times, I waited over an hour after the computer froze before performing
a hard reset on the machine. (The expected time for the operation to
complete was under 10 minutes.) In my case, the computer goes directly
from working as expected to being completely unresponsive, freezing all
input (keyboard, mouse, power button) and output (screen, file
transfer).

The bug does not appear consistently, though. After restarting the
computer, performing the same file transfer worked without any issue.

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

Title:
  Ubuntu slows down and hangs while copying file from/to USB

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

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

[Bug 1621615] Re: network not configured when ipv6 netbooted into cloud-init

[Blake Rouse]

** Changed in: maas
   Status: In Progress => Invalid

** Changed in: maas
 Assignee: LaMont Jones (lamont) => (unassigned)

** Changed in: maas
Milestone: 2.1.3 => None

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

Title:
  network not configured when ipv6 netbooted into cloud-init

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1621615/+subscriptions

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

[Bug 1743249] Re: High IO on the system prevents MAAS to provide PXE config in a timely manner (less than 30 secs)

[Blake Rouse]

** Merge proposal linked:
   https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/337233

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

Title:
  High IO on the system prevents MAAS to provide PXE config in a timely
  manner (less than 30 secs)

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

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

Re: [Bug 1743249] Re: Failed Deployment after timeout trying to retrieve grub cfg

[Blake Rouse]

Andres did the testing of the changes and has logs to prove the
improvement.


On Tue, Feb 6, 2018 at 4:43 PM, Jason Hobbs <jason.ho...@canonical.com>
wrote:

> Blake, that's great.  Do you have before and after numbers showing the
> improvement this change made?
>
> Do you have any data or logs that led you to believe this was the
> culprit in the slow responses I saw on my cluster?
>
> On Tue, Feb 6, 2018 at 3:12 PM, Blake Rouse <blake.ro...@canonical.com>
> wrote:
> > Actually caching does make a difference. That method is not just caching
> > the reading of a file, it caches the searching of the file based on the
> > purpose, the reading of that file from disk (sure can be in kernel
> > cache), the parsing of the template by tempita.
> >
> > All of that is redudant work that is being done on every single request.
> > Searching the filesystem and reading the file from cache is all syscalls
> > even if they come from the kernel cache. Since MAAS is async based that
> > means that coroutine will be placed on hold while we wait for the result
> > to be loaded from the kernel into the memory of the process. That gives
> > other coroutines time to do other things, which means that coroutine
> > doesn't get to execute until others are done or blocked by there own
> > async request.
> >
> > Caching this information can greatly improve that by not requiring the
> > coroutine to be pushed back into the eventloop while it is waiting for
> > data from the kernel and without this change when the data comes back it
> > still has to be processed by tempita which will take time and block the
> > eventloop from completing other work.
> >
> > So its not simply that we should use the kernel to cache reads from the
> > disk there is a lot more involved here. We have noticed improvements
> > with this change on systems that are being ran with large number of VM's
> > because of the reduction of IO.
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1743249
> >
> > Title:
> >   Failed Deployment after timeout trying to retrieve grub cfg
> >
> > Status in MAAS:
> >   New
> > Status in grub2 package in Ubuntu:
> >   Fix Released
> >
> > Bug description:
> >   A node failed to deploy after it failed to retrieve a grub.cfg from
> >   MAAS due to a timeout.  In the logs, it's clear that the server tried
> >   to retrieve the grub cfg many times, over about 30 seconds:
> >
> >   http://paste.ubuntu.com/26387256/
> >
> >   We see the same thing for other hosts around the same time:
> >
> >   http://paste.ubuntu.com/26387262/
> >
> >   It seems like MAAS is taking way too long to respond to these
> >   requests.
> >
> >   This is very similar to bug 1724677, which was happening pre-
> >   metldown/spectre. The only difference is we don't see "[critical] TFTP
> >   back-end failed" in the logs anymore.
> >
> >   I connected to the console on this system and it had errors about
> >   timing out retrieving the grub-cfg, then it had an error message along
> >   the lines of "error not an ip" and then "double free".  After I
> >   connected but before I could get a screenshot the system rebooted and
> >   was directed by maas to power off, which it did successfully after
> >   booting to linux.
> >
> >   Full logs are available here:
> >   https://10.245.162.101/artifacts/14a34b5a-9321-4d1a-b2fa-
> >   ed277a020e7c/cpe_cloud_395/infra-logs.tar
> >
> >   This is with 2.3.0-6434-gd354690-0ubuntu1~16.04.1.
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/maas/+bug/1743249/+subscriptions
>
> --
> You received this bug notification because you are subscribed to MAAS.
> https://bugs.launchpad.net/bugs/1743249
>
> Title:
>   Failed Deployment after timeout trying to retrieve grub cfg
>
> Status in MAAS:
>   New
> Status in grub2 package in Ubuntu:
>   Fix Released
>
> Bug description:
>   A node failed to deploy after it failed to retrieve a grub.cfg from
>   MAAS due to a timeout.  In the logs, it's clear that the server tried
>   to retrieve the grub cfg many times, over about 30 seconds:
>
>   http://paste.ubuntu.com/26387256/
>
>   We see the same thing for other hosts around the same time:
>
>   http://paste.ubuntu.com/26387262/
>
>   It seems like MAAS is taking way too long to respond to these
>   requests.
>
>   This is very similar to bug 17

[Bug 1743249] Re: Failed Deployment after timeout trying to retrieve grub cfg

[Blake Rouse]

Actually caching does make a difference. That method is not just caching
the reading of a file, it caches the searching of the file based on the
purpose, the reading of that file from disk (sure can be in kernel
cache), the parsing of the template by tempita.

All of that is redudant work that is being done on every single request.
Searching the filesystem and reading the file from cache is all syscalls
even if they come from the kernel cache. Since MAAS is async based that
means that coroutine will be placed on hold while we wait for the result
to be loaded from the kernel into the memory of the process. That gives
other coroutines time to do other things, which means that coroutine
doesn't get to execute until others are done or blocked by there own
async request.

Caching this information can greatly improve that by not requiring the
coroutine to be pushed back into the eventloop while it is waiting for
data from the kernel and without this change when the data comes back it
still has to be processed by tempita which will take time and block the
eventloop from completing other work.

So its not simply that we should use the kernel to cache reads from the
disk there is a lot more involved here. We have noticed improvements
with this change on systems that are being ran with large number of VM's
because of the reduction of IO.

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

Title:
  Failed Deployment after timeout trying to retrieve grub cfg

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

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

[Bug 1743966] Re: Trusty deployments fail when custom archives are configured

[Blake Rouse]

** Changed in: maas
   Status: New => Triaged

** Changed in: maas
   Importance: Undecided => Critical

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

Title:
  Trusty deployments fail when custom archives are configured

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

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

[Bug 1691729] Re: linux-firmware-raspi2 conflicts with linux-firmware over brcmfmac43430-sdio.bin

[Blake Hannaford]

Jon, 
Does armbian-config work on ubuntu 16.04?Does that command freeze all 
SW or allow you to specify?
THX

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

Title:
  linux-firmware-raspi2 conflicts with linux-firmware over
  brcmfmac43430-sdio.bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1691729/+subscriptions

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

[Bug 1691729] Re: linux-firmware-raspi2 conflicts with linux-firmware over brcmfmac43430-sdio.bin

[Blake Hannaford]

although the "diversion" workaround results in a nice-looking upgrade
output.   The system fails to reboot for me as well.

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

Title:
  linux-firmware-raspi2 conflicts with linux-firmware over
  brcmfmac43430-sdio.bin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware-raspi2/+bug/1691729/+subscriptions

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

[Bug 1742324] Re: Bionic kernel panics in the MAAS ephemeral environment

[Blake Rouse]

This kernel is PXE booting from MAAS. We might be able to modify the
kernel on disk that pxelinux.0 pulls to get you more information.

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

Title:
  Bionic kernel panics in the MAAS ephemeral environment

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

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

[Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Blake Rouse]

** Changed in: systemd (Ubuntu)
   Status: New => Confirmed

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

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

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

[Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Blake Rouse]

The issue is with the systemd resolver not with glibc.

With systemd-resolve IP in /etc/resolv.conf:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.53

$ time ./test not-a-hostname
Trying to resolve: not-a-hostname
getaddrinfo errno: No such file or directory
getaddrinfo() return value: -2 (Name or service not known)

real0m10.076s
user0m0.001s
sys 0m0.000s


Without systemd-resolve in /etc/resolv.conf. I changed it to point to my local 
DNS server directly.

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
#nameserver 127.0.0.53
nameserver 192.168.1.1

$ time ./test not-a-hostname
Trying to resolve: not-a-hostname
getaddrinfo errno: No such file or directory
getaddrinfo() return value: -2 (Name or service not known)

real0m0.097s
user0m0.001s
sys 0m0.000s


** Changed in: glibc (Ubuntu)
   Status: New => Invalid

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

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

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

[Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Blake Rouse]

$ systemd-resolve --status
Global
  DNSSEC NTA: 10.in-addr.arpa
  16.172.in-addr.arpa
  168.192.in-addr.arpa
  17.172.in-addr.arpa
  18.172.in-addr.arpa
  19.172.in-addr.arpa
  20.172.in-addr.arpa
  21.172.in-addr.arpa
  22.172.in-addr.arpa
  23.172.in-addr.arpa
  24.172.in-addr.arpa
  25.172.in-addr.arpa
  26.172.in-addr.arpa
  27.172.in-addr.arpa
  28.172.in-addr.arpa
  29.172.in-addr.arpa
  30.172.in-addr.arpa
  31.172.in-addr.arpa
  corp
  d.f.ip6.arpa
  home
  internal
  intranet
  lan
  local
  private
  test

Link 8 (vethJWPPL8)
  Current Scopes: LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 4 (lxdbr0)
  Current Scopes: LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

Link 3 (eno1)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 192.168.1.1

Link 2 (enp4s0)
  Current Scopes: none
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

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

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

[Bug 1739672] Re: Regression in getaddrinfo(): calls block for much longer on Bionic (compared to Xenial)

[Blake Rouse]

$ time ./test not-a-real-hostname
Trying to resolve: not-a-real-hostname
getaddrinfo errno: No such file or directory
getaddrinfo() return value: -2 (Name or service not known)

real0m10.007s
user0m0.001s
sys 0m0.001s

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

Title:
  Regression in getaddrinfo(): calls block for much longer on Bionic
  (compared to Xenial)

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

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

[Bug 1729925] Re: Update to upstream 2.3.1

[Blake Johnson]

** Tags added: packaging

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

Title:
  Update to upstream 2.3.1

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

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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Blake Rouse]

I have verified that smoser changes do work with MAAS.

Testing steps:

1. Generated xenial amd64 image stream using smosers PPA.
2. Installed MAAS.
3. Removed the workaround in MAAS.
4. Imported the xenial amd64 image with smosers PPA.
5. Entered rescue mode.
6. Pinged google.com. (Worked)
7. Exited rescue mode.
8. Ran internet connectivity test. (Passed)
9. Ran commissioning with SSH.
10. Pinged google.com. (Worked)

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

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

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

[Bug 1726183] [NEW] Xorg crashed with SIGABRT in OsAbort()

[seirra saffron francis diamond blake]

Public bug reported:

after an extended time with no hdmi plugged in i plug in the hdmi and i
receive no signal

ProblemType: Crash
DistroRelease: Ubuntu 17.10
Package: xserver-xorg-core 2:1.19.5-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..24.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:24:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
 GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.7-0ubuntu3
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CrashCounter: 1
Date: Sun Oct 22 21:46:43 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
 nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
ExecutablePath: /usr/lib/xorg/Xorg
GraphicsCard:
 NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3707]
InstallationDate: Installed on 2017-10-20 (2 days ago)
InstallationMedia: Ubuntu-Budgie 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
MachineType: Micro-Star International Co., Ltd MS-7A31
ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
ProcEnviron: PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=3de0f550-b673-4c3d-bf8e-f92a5b2846b8 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: nvidia-graphics-drivers
StacktraceTop:
 OsAbort ()
 ?? ()
 FatalError ()
 ?? ()
 __libc_start_main (main=0x557b26dc5af0, argc=11, argv=0x7fff3b92f9a8, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff3b92f998) at ../csu/libc-start.c:308
Title: Xorg crashed with SIGABRT in OsAbort()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
 
dmi.bios.date: 06/21/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.70
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X370 XPOWER GAMING TITANIUM (MS-7A31)
dmi.board.vendor: Micro-Star International Co., Ltd
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.70:bd06/21/2017:svnMicro-StarInternationalCo.,Ltd:pnMS-7A31:pvr1.0:rvnMicro-StarInternationalCo.,Ltd:rnX370XPOWERGAMINGTITANIUM(MS-7A31):rvr1.0:cvnMicro-StarInternationalCo.,Ltd:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A31
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Oct 23 01:31:33 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2

** Affects: nvidia-graphics-drivers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash artful need-amd64-retrace ubuntu

** Information type changed from Private to Public

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

Title:
  Xorg crashed with SIGABRT in OsAbort()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1726183/+subscriptions

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

[Bug 1707999] Re: pod VM fails to PXE boot after receiving multiple DHCP offers, for different IPs, from the dhcp server

[Blake Rouse]

I have submitted the patch upstream:
https://github.com/ipxe/ipxe/pull/66

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

Title:
  pod VM fails to PXE boot after receiving multiple DHCP offers, for
  different IPs, from the dhcp server

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

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

[Bug 1642298] Re: Grub package upgrades overwrites NVRAM, causing MAAS boot order to be overwritten.

[Blake Rouse]

Rod,

I moved my comment to the other bug. But to respond to your comments.

I think your point about #1 is something that should be solved during
installation. There is no reason the Ubuntu installation cannot be smart
enough to re-order the boot order. I think on fresh install that makes
perfect sense, but on an upgrade of an existing package this should not
occur.

#2 I agree the bootloader would need to be a direct match. GUID and
path.

#3 Yeah using the shimx64 is what you want. My suggestion was more of a
suggestion on how it should work over all. I was being over specific
with grubx64.efi.

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

Title:
  Grub package upgrades overwrites NVRAM, causing MAAS boot order to be
  overwritten.

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

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

[Bug 1714090] Re: grub2 upgrade doesn't preserve current boot order.

[Blake Rouse]

Comment I made on https://bugs.launchpad.net/maas/+bug/1642298. Was
requested to direct it here.

I think this is more of a GRUB issue overall instead of a MAAS issue
directly. True it affects MAAS and we can do the debconf selections to
work around this issue but overall for quality of Ubuntu I do not
believe this is the proper fix.

I will give an example without MAAS.

1. First the user installs Ubuntu on a partition on their local disk, EFI is 
updated so Ubuntu can boot.
2. Second the user installs Windows on another partition. EFI is updates so 
Windows can boot and its first.
3. User reboots into Ubuntu, runs apt-get, and grub updates changing the boot 
order so now that Ubuntu boots first.
4. User reboots their machine and Ubuntu boots but the user expected Windows to 
boot.

Overall this is a bad experience to the user.

I think the grub code should be smart about this:

First check if the grub.efi loader already exists in efibootmgr. If it
does not exists add it to the loader and set it to boot first. If it
does exist record its current place in the boot order, update the loader
and reset the boot order to its previous location.

That change would fix this for any user that uses Ubuntu as well as MAAS
users.

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

Title:
  grub2 upgrade doesn't preserve current boot order.

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

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

[Bug 1642298] Re: Grub package upgrades overwrites NVRAM, causing MAAS boot order to be overwritten.

[Blake Rouse]

I think this is more of a GRUB issue overall instead of a MAAS issue
directly. True it affects MAAS and we can do the debconf selections to
work around this issue but overall for quality of Ubuntu I do not
believe this is the proper fix.

I will give an example without MAAS.

1. First the user installs Ubuntu on a partition on their local disk, EFI is 
updated so Ubuntu can boot.
2. Second the user installs Windows on another partition. EFI is updates so 
Windows can boot and its first.
3. User reboots into Ubuntu, runs apt-get, and grub updates changing the boot 
order so now that Ubuntu boots first.
4. User reboots their machine and Ubuntu boots but the user expected Windows to 
boot.

Overall this is a bad experience to the user.

I think the grub code should be smart about this:

First check if the grub.efi loader already exists in efibootmgr. If it
does not exists add it to the loader and set it to boot first. If it
does exist record its current place in the boot order, update the loader
and reset the boot order to its previous location.

That change would fix this for any user that uses Ubuntu as well as MAAS
users.

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

Title:
  Grub package upgrades overwrites NVRAM, causing MAAS boot order to be
  overwritten.

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

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

[Bug 1711760] Re: [2.3] resolv.conf is not set (during commissioning or testing)

[Blake Rouse]

Scott,

Since we are no longer using iscsi and using the squashfs over HTTP,
would open-iscsi even be used?

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

Title:
  [2.3] resolv.conf is not set (during commissioning or testing)

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

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

[Bug 1712626] Re: Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

[Blake Henderson]

I noticed that the repo now has kernel 4.4.0-93 available- i tried that
but it did not work either - it also seemed to set SMT to 8 which caused
me a few problems until i realized what it did.

I rebooted with kernel 4.4.0.94 and all is well again (after I set SMT
to off)

Hopefully the new kernel will be available in the repo soon.
Also wondering if x86 is experiencing same issue, since I have 6 x86 nova hosts 
to update too.

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

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

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

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

[Bug 1712626] Re: Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

[Blake Henderson]

Added kernel 4.4.0-94-117 to the nova node
I am now able to create VMs on it. 

Fix is successful

ubuntu@rcsnode03:~$ uname -a
Linux rcsnode03 4.4.0-94-generic #117~lp1709784 SMP Wed Aug 23 20:28:29 UTC 
2017 ppc64le ppc64le ppc64le GNU/Linux

ubuntu@rcsnode03:~$ virsh list
 IdName   State

 2 instance-0269  running

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

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

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

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

[Bug 1712626] Re: Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

[Blake Henderson]

I will look into testing it on our nova host.
I tested it on a vm just to ensure it booted ok- no issues.  I will try it on 
the nova host as soon as i can and see if i am able to launch a virtual 
instance.

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

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

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

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

[Bug 1712626] Re: Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

[Blake Henderson]

Also see Bug 1709784  -- seems to be the same issue.

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

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

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

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

[Bug 1712626] Re: Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

[Blake Henderson]

not able to run apport-collect


It appears that the latest upstream stable kernel is v4.4.83 -- I have that 
installed and it is ok- no issues- the problem does not exist in this kernel.

However, a apt update installed 4.4.0-92 - this one did have issues.  I
have 9 more systems to update- it would be better if an apt update
installed 4.4.83- not 4.4.92

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

Title:
  Cannot launch virtual instance on nova host after upgrading to kernel
  4.4.0.92- works with 4.4.0.83

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

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

[Bug 1712626] [NEW] Cannot launch virtual instance on nova host after upgrading to kernel 4.4.0.92- works with 4.4.0.83

[Blake Henderson]

Public bug reported:

Host -- IBM Power 8  822L
OS- Ubuntu 14.04 ppc64el
previous kernel 3.19.0.68
Nova Compute host using kvm - Openstack Liberty

HWE was out of date so needed to update

Steps:

sudo apt-get install linux-generic-lts-xenial linux-image-generic-lts-xenial
sudo init 6
sudo apt update
sudo apt upgrade
sudo init 6

afterwards - system seemed ok - kernel 4.4.0.92 installed

However, launching a Ubuntu VM failed

Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246360] Facility 'TM' unavailable, 
exception at 0xd000189f85a0, MSR=90009033
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246374] Oops: Unexpected facility 
unavailable exception, sig: 6 [#1]
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246379] SMP NR_CPUS=2048 NUMA PowerNV
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246385] Modules linked in: vhost_net 
vhost macvtap macvlan xt_REDIRECT nf_nat_redirect xt_mark xt_nat ip6table_raw 
nf_conntrack_ipv6
 xt_CT xt_mac xt_comment xt_physdev br_netfilter iptable_raw veth xt_CHECKSUM 
iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 
nf_nat nf_conntrac
k_ipv4 nf_defrag_ipv4 xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp 
ebtable_filter ebtables ip6table_filter ip6_tables iptable_filter ip_tables 
x_tables vport_gre ip_gre 
ip_tunnel gre nbd kvm_hv kvm ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core 
ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi openvswitch 
nf_defrag_ipv6 nf_conn
track dm_crypt bridge stp llc dm_multipath uio_pdrv_genirq ipmi_powernv 
ipmi_msghandler uio ibmpowernv powernv_rng vmx_crypto leds_powernv ses 
enclosure bnx2x vxlan ip6_udp_
tunnel udp_tunnel mdio libcrc32c ipr
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246500] CPU: 96 PID: 52779 Comm: 
qemu-system-ppc Not tainted 4.4.0-92-generic #115~14.04.1-Ubuntu
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246506] task: c01e228dcf60 ti: 
c01e229f4000 task.ti: c01e229f4000
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246511] NIP: d000189f85a0 LR: 
d000188a2584 CTR: d000189f84f0
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246516] REGS: c01e229f7840 TRAP: 
0f60   Not tainted  (4.4.0-92-generic)
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246519] MSR: 90009033 
  CR: 28022448  XER: 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] CFAR: d000189f8534 SOFTE: 
1 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR00: d000188a2584 
c01e229f7ac0 d00018a0c7f8 c01c4c68 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR04: c01c5308 
c01e229f7bc0  0004 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR08: 0001 
c01e228dcf60  d000188a7518 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR12: d000189f84f0 
cfb79000 3fff7d74ed40 3fff7d74f3d0 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR16: 3fff7cf5 
 0003 3fff7d750010 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR20: 100c0570 
01000f6ebba0 0080 3fff85644330 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR24:  
3fff7cf30028 d4f6d401 0010 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246534] GPR28:  
c01c4c68 c01c4c68 c01c5308 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246594] NIP [d000189f85a0] 
kvmppc_vcpu_run_hv+0xb0/0x610 [kvm_hv]
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246606] LR [d000188a2584] 
kvmppc_vcpu_run+0x44/0x60 [kvm]
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246610] Call Trace:
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246617] [c01e229f7ac0] 
[c00ca294] recalc_sigpending+0x24/0x90 (unreliable)
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246630] [c01e229f7b70] 
[d000188a2584] kvmppc_vcpu_run+0x44/0x60 [kvm]
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246642] [c01e229f7ba0] 
[d0001889f274] kvm_arch_vcpu_ioctl_run+0x64/0x180 [kvm]
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246653] [c01e229f7be0] 
[d00018893898] kvm_vcpu_ioctl+0x5e8/0x7c0 [kvm]
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246661] [c01e229f7d40] 
[c02ef7d0] do_vfs_ioctl+0x4d0/0x7e0
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246667] [c01e229f7de0] 
[c02efbb4] SyS_ioctl+0xd4/0xf0
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246673] [c01e229f7e30] 
[c0009204] system_call+0x38/0xb4
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246677] Instruction dump:
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246681] e92d02a0 e9290a50 e9290108 
792807e3 41820058 e92d02a0 e9290a50 e9290108 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246690] 792ae8a4 794a1f87 40820508 
e92d02a0 <7d4022a6> f9490ee8 e92d02a0 7d4122a6 
Aug 23 11:38:25 rcsnode03 kernel: [ 3270.246705] ---[ end trace 
df289857e3c4915a ]---

Installing kernel 4.4.0.83 and booting off it resolved issue.

Problem seems to be related to post 4.4.0.83 

Re: [Qemu-devel] [Bug 1711602] Re: --copy-storage-all failing with qemu 2.10

[Eric Blake]

On 08/23/2017 09:55 AM, ChristianEhrhardt wrote:
> Ok, clarified with Stefanha
> It has exactly the same title as a series of 18th August which was related to 
> a similar issue.
> It is about an hour old now on qemu-devel, quoting
> 
> "This fixes the issue reported as
> https://bugs.launchpad.net/bugs/1711602
> 
> Fam Zheng (3):
>   block-backend: Refactor inactivate check
>   block-backend: Allow more "can inactivate" cases
>   mirror: Mark target BB as "force allow inactivate"
> 
> Stefan Hajnoczi (1):
>   block: Update open_flags after ->inactivate() callback"
> 
> 
> I'll prep a build with that and test as well

Here's what is brewing for my pull request, although if you can
successfully test things, I'm happy to add a Tested-by: tag before
actually sending the pull request:

git fetch  git://repo.or.cz/qemu/ericb.git nbd

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.   +1-919-301-3266
Virtualization:  qemu.org | libvirt.org

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

Title:
  --copy-storage-all failing with qemu 2.10

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

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

[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken

[Blake Rouse]

** Changed in: maas/2.2
   Status: New => In Progress

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

Title:
  [2.3a1] named stuck on reload, DNS broken

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

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

[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken

[Blake Rouse]

** Changed in: maas
   Status: Triaged => In Progress

** Changed in: maas
 Assignee: (unassigned) => Blake Rouse (blake-rouse)

** Changed in: maas
Milestone: None => 2.3.0

** Also affects: maas/2.2
   Importance: Undecided
   Status: New

** Changed in: maas/2.2
   Importance: Undecided => Critical

** Changed in: maas/2.2
 Assignee: (unassigned) => Blake Rouse (blake-rouse)

** Changed in: maas/2.2
Milestone: None => 2.2.3

** Merge proposal linked:
   https://code.launchpad.net/~blake-rouse/maas/+git/maas/+merge/329260

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

Title:
  [2.3a1] named stuck on reload, DNS broken

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

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

Re: [Bug 1642298] Re: UEFI Xenial install sets computer to boot from hard disk

[Blake Rouse]

On Wed, Aug 2, 2017 at 9:49 AM, Ryan Harper <1642...@bugs.launchpad.net>
wrote:

> On Wed, Aug 2, 2017 at 8:12 AM, Blake Rouse <blake.ro...@canonical.com>
> wrote:
>
> > update_nvram is now default for curtin and re-ordering is also default
> >
>
> MAAS send update_nvram as True ? or False by default?
>

MAAS sends nothing. The default is True, so MAAS uses the default.


>
>
> > for UEFI installs. I don't think setting grub2/update_nvram in debconf
> > should be a default. To me MAAS should tell curtin to set that debconf
> > as that is overriding a package default.
> >
>
> OK, do we want to re-use the update_nvram curtin config to *ALSO* set the
> debconf value? Or do we need to be able to send/set those values
> independently?
>

You could re-use it but that would mean by default curtin would always set
that for an installed system. By default having curtin update the nvram on
install makes since, even using subiquity. But overriding the packing of
grub of the installed system is more of a MAAS specific case to me, so I
would think it should be its own setting, that MAAS must explicitly set to
True.


>
>
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1642298
> >
> > Title:
> >   UEFI Xenial install sets computer to boot from hard disk
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/curtin/+bug/1642298/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to MAAS.
> https://bugs.launchpad.net/bugs/1642298
>
> Title:
>   UEFI Xenial install sets computer to boot from hard disk
>
> Status in curtin:
>   Confirmed
> Status in MAAS:
>   Invalid
> Status in grub2 package in Ubuntu:
>   Fix Released
> Status in grub2 source package in Trusty:
>   Triaged
> Status in grub2 source package in Xenial:
>   Triaged
> Status in grub2 source package in Yakkety:
>   Triaged
>
> Bug description:
>   [Impact]
>   Typically when you install Ubuntu on an EFI system, it installs a new
> default EFI boot entry that makes the system reboot directly into the OS.
> During MAAS installs, curtin is careful to disable that behavior. MAAS
> requires the default boot entry to remain PXE, so that it can direct the
> system to boot from disk or network as necessary. curtin does this by
> passing --no-nvram to grub-install when installing the bootloader.
>
>   *Update*: newer curtin releases actually allow the creation of a new
>   boot entry, but updates the boot menu to make PXE the default. That
>   change is orthogonal to this bug.
>
>   ***However***, this doesn't stop a new default boot entry from being
>   added after deploy. If the user installs a grub package update or
>   manually runs 'grub-install', booting from disk will become the
>   default, and MAAS will lose control of the system.
>
>   [Proposed Solution (er... glorified workaround)]
>   The GRUB package in zesty now has support for setting the --no-nvram
> flag *persistently*. This is implemented via a debconf template
> (grub2/update_nvram). If curtin sets this flag to "false" during install,
> post-deploy grub updates will also pass the --no-nvram flag when running
> grub-install.
>
>   This isn't a perfect solution - users can still call grub-install
>   manually and omit this flag.
>
>   [Test Case]
>- MAAS deploy an EFI system.
>- After deploy, login and run 'sudo apt --reinstall install
> grub-efi-$(dpkg --print-architecture)
>- Reboot and observe that the system does not PXE boot.
>
>   [Regression Risk]
>- The GRUB implementation does not change the defaults of the package.
> The user would need to opt-in to the "grub2/update_nvram=false". This
> option is also only presented to users who specifically request a low
> debconf priority (e.g. expert mode installs).
>- XXX curtin risk XXX
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/curtin/+bug/1642298/+subscriptions
>

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

Title:
  UEFI Xenial install sets computer to boot from hard disk

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

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

[Bug 1642298] Re: UEFI Xenial install sets computer to boot from hard disk

[Blake Rouse]

update_nvram is now default for curtin and re-ordering is also default
for UEFI installs. I don't think setting grub2/update_nvram in debconf
should be a default. To me MAAS should tell curtin to set that debconf
as that is overriding a package default.

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

Title:
  UEFI Xenial install sets computer to boot from hard disk

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

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

[Bug 1642298] Re: UEFI Xenial install sets computer to boot from hard disk

[Blake Rouse]

dann,

I think you are correct that 'grub2/update_nvram' is still not set by
curtin and an upgrade of grub could break the machine.

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

Title:
  UEFI Xenial install sets computer to boot from hard disk

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

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

[Bug 1642298] Re: UEFI Xenial install sets computer to boot from hard disk

[Blake Rouse]

I think having MAAS tell curtin to set the grub2/update_nvram to False,
works fine. Since the path to the EFI loader should not change this is
acceptable.

Having grub adjust the EFI vars because of an upgrade is really bad in
MAAS case because a following re-deploy will no longer work.

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

Title:
  UEFI Xenial install sets computer to boot from hard disk

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

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

[Bug 1679222] Re: ISCSI target validation fails when target name includes a ':'

[Blake Rouse]

** Changed in: maasrsd
   Status: Triaged => Fix Committed

** Changed in: maasrsd
   Status: Fix Committed => Invalid

** Changed in: maas
   Status: Triaged => Invalid

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

Title:
  ISCSI target validation fails when target name includes a ':'

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

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

[Bug 1676209] Re: VM crashes after saving and restoring with latest kernel

[Blake Cottington]

More info: Host is Server 2016. Guest is Generation 2 type. Dynamic
memory is not enabled.

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

Title:
  VM crashes after saving and restoring with latest kernel

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

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

[Bug 1676209] Re: VM crashes after saving and restoring with latest kernel

[Blake Cottington]

** Attachment added: "Linux4.4.0-71jsalisburyNoCrash.gif"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676209/+attachment/4848321/+files/Linux4.4.0-71jsalisburyNoCrash.gif

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

Title:
  VM crashes after saving and restoring with latest kernel

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

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

[Bug 1676209] Re: VM crashes after saving and restoring with latest kernel

[Blake Cottington]

Hi, I know this isn't my thread but I'm trying to help. I am seeing the
crash of the VM during a Windows Server Backup with the latest kernel
4.4.0-67. I installed the kernel from comment 42 referenced in the other
thread. It did make a difference. I will post screenshots of the
results.

Side note - I am a noob to installing patches like this. I tried using the 3rd 
technique here:
https://wiki.ubuntu.com/Kernel/Dev/KernelTesting

and pointed to: http://kernel.ubuntu.com/~jsalisbury/lp1674635/revert/

then did apt-get update, but I got a message similar to this:
W: The repository '...' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore 
potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration 
details.
E: Failed to fetch ...  404  Not Found
E: Some index files failed to download. They have been ignored, or old ones 
used instead.

So... I did wget and dpkg -i for each of the 12 files in the directory.

** Attachment added: "Linux4.4.0-67Crash.gif"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1676209/+attachment/4848320/+files/Linux4.4.0-67Crash.gif

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

Title:
  VM crashes after saving and restoring with latest kernel

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

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

[Bug 1674384] [NEW] Deprecated use warning

[Joshua Blake]

Public bug reported:

Running on Ubuntu 14.04 LTS, running mhonarc prints to stderr:

defined(%hash) is deprecated at /usr/share/mhonarc/mhamain.pl line 1564.
(Maybe you should just omit the defined()?)
defined(%hash) is deprecated at /usr/share/mhonarc/mhopt.pl line 867.
(Maybe you should just omit the defined()?)

It appears that the deprecation fixes in the last release did not reach
all the places required.

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

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

Title:
  Deprecated use warning

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

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

[Bug 1637733] Re: freeze on login with prime-select intel

[Blake Tregre]

I have the same problem with Gigabyte Aero 14.
NVidia gtx 1060
Kabylake i7 7700HQ
16GB RAM

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

Title:
  freeze on login with prime-select intel

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

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

[Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

[Blake Rouse]

Bob,

This is fixed in MAAS the issue is still in the Xenial images. That is
why cloud-init is still marked Confirmed for Xenial as it has not been
SRU'd.

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

Title:
  Commissioning fails when competing cloud metadata resides on disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1582323/+subscriptions

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

[Bug 1659430] Re: x-staging problem report, redux

[Blake Tregre]

** Attachment added: "dmesg output"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659430/+attachment/4809132/+files/dmesg.txt

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

Title:
  x-staging problem report, redux

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

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

[Bug 1659430] [NEW] x-staging problem report, redux

[Blake Tregre]

Public bug reported:

I previously reported a X freeze and screen powering off bug over here
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1655803.  I had
hoped that some of the fixes in  newer mesa releases would fix it, but
alas I having the same problem on the latest x-staging mesa.  After
15-30 minutes of activity (emacs, terminal, chrome) X freezes, the
screen turns disco colors, and the screen powers down.  My machine is
usually completely hung (can't ssh in or ping), but I was able to ssh in
a collect a few logs (possible redundant, included below) this last
time.  Thanks, I hope this helps.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
BootLog:
 
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Jan 25 13:10:22 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-57-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed
 nvidia-375, 375.26, 4.4.0-57-generic, x86_64: installed
 nvidia-375, 375.26, 4.4.0-59-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT GL [FirePro W9000] 
[1002:6780] (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT GL [FirePro 
W9000] [1002:031e]
MachineType: Dell Inc. Precision WorkStation T7500
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=UUID=4bb35b69-210e-445c-b815-725f1bb7e010 ro radeon.msi=0 quiet splash 
nouveau.blacklist=1 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/21/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 06FW8P
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/21/2011:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA01:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T7500
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.3-1ubuntu3~16.04.02
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.3-1ubuntu3~16.04.02
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Jan 25 12:44:23 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

** Attachment added: "xorg log"
   https://bugs.launchpad.net/bugs/1659430/+attachment/4809108/+files/Xorg.0.log

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

Title:
  x-staging problem report, redux

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

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

[Bug 1655803] [NEW] x-staging problem report

[Blake Tregre]

Public bug reported:

I added the x-staging ppa and upgraded my 16.04 system (equipped with
AMD W9000) to use the mesa drivers in the upcoming release.  After about
15 minutes of emacs, terminal, and chrome usage the screen blanks to
grey with blue squares, then to grey, then powers off.  I'm logging this
here in hopes it will help the upcoming release.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xserver-xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
BootLog:
 
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Jan 11 18:09:18 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-53-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-57-generic, x86_64: installed
 nvidia-375, 375.26, 4.4.0-53-generic, x86_64: installed
 nvidia-375, 375.26, 4.4.0-57-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT GL [FirePro W9000] 
[1002:6780] (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT GL [FirePro 
W9000] [1002:031e]
MachineType: Dell Inc. Precision WorkStation T7500
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic 
root=UUID=4bb35b69-210e-445c-b815-725f1bb7e010 ro radeon.msi=0 quiet splash 
nouveau.blacklist=1 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/21/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 06FW8P
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/21/2011:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA01:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T7500
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.2-1ubuntu1~xenial0
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.2-1ubuntu1~xenial0
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Jan 11 17:55:07 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

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

Title:
  x-staging problem report

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

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

[Bug 655708] Re: [PATCH] ppc: Fix a warning in bcdcfz code and improve BCD_DIG_BYTE macro

[Eric Blake]

On 01/11/2017 12:50 PM, Jose Ricardo Ziviani wrote:
> This commit fixes a warning in the code "(i * 2) ? .. : ..", which
> should be better as "(i) ? .. : ..", and improves the BCD_DIG_BYTE

Could remove the () around i here.

> macro by placing parentheses around its argument to avoid possible
> expansion issues like: BCD_DIG_BYTE(i + j).
> 
> Signed-off-by: Jose Ricardo Ziviani <jos...@linux.vnet.ibm.com>
> ---
>  target/ppc/int_helper.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/target/ppc/int_helper.c b/target/ppc/int_helper.c
> index 24e5964..d889084 100644
> --- a/target/ppc/int_helper.c
> +++ b/target/ppc/int_helper.c
> @@ -2583,9 +2583,9 @@ void helper_vsubecuq(ppc_avr_t *r, ppc_avr_t *a, 
> ppc_avr_t *b, ppc_avr_t *c)
>  #define NATIONAL_NEG0x2D
>  
>  #if defined(HOST_WORDS_BIGENDIAN)
> -#define BCD_DIG_BYTE(n) (15 - (n/2))
> +#define BCD_DIG_BYTE(n) (15 - ((n) / 2))
>  #else
> -#define BCD_DIG_BYTE(n) (n/2)
> +#define BCD_DIG_BYTE(n) ((n) / 2)
>  #endif
>  
>  static int bcd_get_sgn(ppc_avr_t *bcd)
> @@ -2908,7 +2908,7 @@ uint32_t helper_bcdcfz(ppc_avr_t *r, ppc_avr_t *b, 
> uint32_t ps)
>  }
>  
>  for (i = 0; i < 16; i++) {
> -zone_digit = (i * 2) ? b->u8[BCD_DIG_BYTE(i * 2)] >> 4 : zone_lead;
> +zone_digit = (i) ? b->u8[BCD_DIG_BYTE(i * 2)] >> 4 : zone_lead;

Extra (); I'd go with zone_digit = i ? ...

With that tweak,
Reviewed-by: Eric Blake <ebl...@redhat.com>

-- 
Eric Blake   eblake redhat com+1-919-301-3266
Libvirt virtualization library http://libvirt.org

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

Title:
  package smb2www 980804-38 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

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

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

[Bug 1582323] Re: Commissioning fails when competing cloud metadata resides on disk

[Blake Rouse]

** Changed in: maas/2.1
   Importance: Undecided => Critical

** Changed in: maas/2.1
 Assignee: (unassigned) => Andres Rodriguez (andreserl)

** Changed in: maas/trunk
 Assignee: (unassigned) => Andres Rodriguez (andreserl)

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

Title:
  Commissioning fails when competing cloud metadata resides on disk

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1582323/+subscriptions

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

[Bug 1389811] Re: tgtadm: out of memory crash

[Blake Rouse]

Yes this fix should be SRU to Xenial as anyone with lots of MAAS images
comes across this issue.

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

Title:
  tgtadm: out of memory crash

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

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

[Bug 1574113] Re: curtin/maas don't support multiple (derived) archives/repositories with custom keys

[Blake Rouse]

** Also affects: maas/1.9
   Importance: Undecided
   Status: New

** Changed in: maas/1.9
   Status: New => Won't Fix

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

Title:
  curtin/maas don't support multiple (derived) archives/repositories
  with custom keys

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1574113/+subscriptions

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

[Bug 1621901] Re: impitool lacks support for ipv6 addresses

[Blake Rouse]

** Changed in: maas
Milestone: 2.1.1 => 2.1.2

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

Title:
  impitool lacks support for ipv6 addresses

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

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

[Bug 1621615] Re: network not configured when ipv6 netbooted into cloud-init

[Blake Rouse]

** Changed in: maas
Milestone: 2.1.1 => 2.1.2

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

Title:
  network not configured when ipv6 netbooted into cloud-init

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1621615/+subscriptions

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

[Bug 1629972] Re: networking stop incorrectly disconnects from (network) root filesystem

[Blake Rouse]

** Changed in: maas
Milestone: 2.1.1 => 2.1.2

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

Title:
  networking stop incorrectly disconnects from (network) root filesystem

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

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

[Bug 1628535] Re: AH00493: SIGUSR1 received. Doing graceful restart - Apache2 crashes - Can't access maas server URL

[Blake Rouse]

** Changed in: maas
Milestone: 2.1.1 => 2.1.2

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

Title:
  AH00493: SIGUSR1 received.  Doing graceful restart - Apache2 crashes -
  Can't access maas server URL

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

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

[Bug 1636879] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Blake Richards]

Public bug reported:

When I start my system I get this error message. I am not personally
trying to install or upgrade tex-common, so I'm not sure why this is
happening.

I recently upgraded to Ubuntu 16.04.1 LTS, which is when I noticed this
(though I am not 100% confident that it had never occurred before).

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
Uname: Linux 4.4.0-45-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Tue Oct 25 10:50:14 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2011-11-11 (1810 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-10-25 (0 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 need-duplicate-check xenial

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1636879/+subscriptions

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