[Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize

@wenchien: Ok, thank you for the info. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1483101 Title: Broadcom bluetooth modules sometimes fail to initialize To manage notifications about this bug

[Bug 1483101] Re: Broadcom bluetooth modules sometimes fail to initialize

The error message appears again in Ubuntu 18.04, kernel 4.15.0-22-generic, with module 0a5c:216c. I already posted this on https://askubuntu.com/questions/1043171/broadcom-bcm43242a0-bluetooth-adapter-not-detected-in-ubuntu-18-04 Is it possible that the fix got lost in a newer kernel version? --

[Bug 1774666] Re: Bond interfaces stuck at 1500 MTU on Bionic

Subscribed to Canonical Field High SLA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774666 Title: Bond interfaces stuck at 1500 MTU on Bionic To manage notifications about this bug go to:

[Bug 1774666] Re: Bond interfaces stuck at 1500 MTU on Bionic

This is causing test failures for us, because containers deployed by juju that are bound to a space that sits on top of the bond have the corrent mtu (9000) but the bond's mtu is stuck at (1500), so packets are being dropped. curtin config for the machine: http://paste.ubuntu.com/p/8tMR2YBGYm/

[Bug 1774666] Re: Bond interfaces stuck at 1500 MTU on Bionic

We are seeing this in our test runs as well. ** Tags added: cdo-qa foundations-engine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774666 Title: Bond interfaces stuck at 1500 MTU on Bionic To

[Bug 1662552] Re: snaps don't work with NFS home

The issue appears larger than just NFS mounted $HOME. After I used the workaround provided to get the filebot snap to run with an NFS mounted $HOME, I was unable to use it to manipulate any files in my NFS mounted media library. I gave up and just loaded the deb package. Should this be reported

[Bug 1774902] [NEW] kubuntu - can't login with NFS $HOME

Public bug reported: If $HOME is an NFS mount, startkde show a write error and fails to start ksmserver. Xsession: X session started for kelleher at Fri Jun 1 20:45:36 EDT 2018 localuser:kelleher being added to access control list openConnection: connect: No such file or directory cannot

[Bug 1774833] [NEW] package runit 2.1.2-3ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Public bug reported: error while installing git apt install git-all ProblemType: Package DistroRelease: Ubuntu 16.04 Package: runit 2.1.2-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-43-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18

[Bug 1772947] Re: You have enabled the binary log, but you haven't provided the mandatory server-id.

After testing with the new version of the charm, we're not seeing this anymore. Looks fixed to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1772947 Title: You have enabled the binary log, but

[Bug 1607345] Re: Collect all logs needed to debug curtin/cloud-init for each deployment

** Tags added: cdo-qa foundations-engine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1607345 Title: Collect all logs needed to debug curtin/cloud-init for each deployment To manage notifications

[Bug 1772490] Re: 'Deploying' timed out after 40 minutes / Failedbcache: register_bcache() error

*** This bug is a duplicate of bug 1768893 *** https://bugs.launchpad.net/bugs/1768893 ** This bug has been marked a duplicate of bug 1768893 installation on several nodes failed with errors relating to dmsetup remove of ceph devices. -- You received this bug notification because you

Re: [Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

gt; Looks like the ls -aLR contains more data; we can compare bionic. > > On Tue, May 22, 2018 at 6:53 PM, Jason Hobbs <jason.ho...@canonical.com> > wrote: >> cd /sys/bus/pci/devices && grep -nr . * >> >> xenial: >> http://paste.ubuntu.com/p/F5qyvN

Re: [Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

cd /sys/bus/pci/devices && grep -nr . * xenial: http://paste.ubuntu.com/p/F5qyvN2Qrr/ On Tue, May 22, 2018 at 5:27 PM, Jason Hobbs <jason.ho...@canonical.com> wrote: > Do you really want a tar? How about ls -alR? xenial: > > http://paste.ubuntu.com/p/wyQ3kTsyBB/ > >

Re: [Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

Do you really want a tar? How about ls -alR? xenial: http://paste.ubuntu.com/p/wyQ3kTsyBB/ On Tue, May 22, 2018 at 5:14 PM, Jason Hobbs <jason.ho...@canonical.com> wrote: > ok; looks like that 4.15.0-22-generic just released and wasn't what I > used in the first reproduction... I

Re: [Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

quot; > pid=91949 comm="(y-helper)" flags="ro, remount, bind" > > > xenial.log:May 22 15:15:10 aurorus kernel: [ 918.311740] audit: > type=1400 audit(1527002110.131:109): apparmor="DENIED" > operation="file_mmap" > namespace="root//lxd-juju-

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

marked new on nova-compute-charm due to rharper's comment #18, and new on libvirt because I've posted all the requested logs now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771662 Title:

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

@rharper, here are the logs you requested from the xenial deploy. ** Attachment added: "xenial-logs-1771662.tgz" https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5142976/+files/xenial-logs-1771662.tgz ** Changed in: charm-nova-compute Status: Invalid => New **

[Bug 1772686] [NEW] installer crashed on GRUB2 install

Public bug reported: said it cannot install GRUB2 to / and will not boot... and now i'm here :) 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

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

Christian, thanks for digging in. Yes, I really just setup base openstack and hit this condition. I'm not doing anything to setup devices as passthrough or anything along those lines, and I'm not trying to start instances. -- You received this bug notification because you are a member of Ubuntu

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

all of /var/log and /etc from the bionic deploy. ** Attachment added: "bionic-var-log-and-etc.tgz" https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5141000/+files/bionic-var-log-and-etc.tgz -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

@rharper here are the logs you asked for from the bionic deploy ** Attachment added: "bionic-logs.tgz" https://bugs.launchpad.net/charm-nova-compute/+bug/1771662/+attachment/5140998/+files/bionic-logs.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

@rharper still working on getting the other stuff you've asked for, but here is the uname -a output from xenial vs bionic: http://paste.ubuntu.com/p/rJDpK5SyW9/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

steve captured what I meant in #8 better than I did: 17:46 < slangasek> one could as accurately say "I'm suspicious this is related to us replacing the whole networking stack in Ubuntu" ;-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

This looks like it is specific to this hardware and the way it does VFs and PFs, so I'm removing field-high. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771662 Title: libvirtError: Node device

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

given it works with the same libvirt and kernel on 16.04 but not 18.04, I'm suspicious of netplan here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771662 Title: libvirtError: Node device not

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

The deploy works fine with juju 2.4 beta 2 and xenial/queens. package versions: http://paste.ubuntu.com/p/PF7Jb7gxnX/ we do see this in nova-compute.log, but it's not fatal: http://paste.ubuntu.com/p/Dh4ZGVTtH8/ -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1771662] Re: libvirtError: Node device not found: no node device with matching name

** Description changed: After deploying openstack on arm64 using bionic and queens, no hypervisors show upon. On my compute nodes, I have an error like: 2018-05-16 19:23:08.165 282170 ERROR nova.compute.manager libvirtError: Node device not found: no node device with matching name

[Bug 1579652] Re: snap ignores the proxy environment variables

I got this to work: http://paste.ubuntu.com/p/K8VncJv4vp/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1579652 Title: snap ignores the proxy environment variables To manage notifications about

[Bug 1767693] Re: 18.04 GNOME displays at 60fps even if the monitor is set to 144hz

Seems related to https://bugzilla.gnome.org/show_bug.cgi?id=781296 There are hardcoded values at 60fps / 60hz / 16667. I rebuilt mutter and clutter with values at 144fps / 144hz / 6944, so far it seems to have helped but it's still not as smooth as other desktops. ** Bug watch added: GNOME Bug

[Bug 1767264] Re: Window manager refresh rate is different from monitor refresh rate

Also posted in #1767693 : Seems related to https://bugzilla.gnome.org/show_bug.cgi?id=781296 There are hardcoded values at 60fps / 60hz / 16667. I rebuilt mutter and clutter with values at 144fps / 144hz / 6944, so far it seems to have helped but it's still not as smooth as other desktops. **

[Bug 1770032] [NEW] r-cran-rjava depends on non existant r-api-3.4 package

Public bug reported: The r-cran-rjava package depends on the non existent r-api-3.4 package in Ubuntu 18.04 (bionic beaver) ** Affects: rjava (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1769322] Re: Trackpoint reacts jumpy and isn't precise when moved a short distance

Having the same issue, my cursor jumps when moving short distances. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1769322 Title: Trackpoint reacts jumpy and isn't precise when moved a short

[Bug 1753376] Re: Freecad's start workbench points to missing webgui -> almost empty gui

Same here, at first you are met with a very sparse window, but FreeCad is thankfully usable if you use the view drop down and select a workbench ** Attachment added: "Screenshot from 2018-05-08 11-56-56.png"

[Bug 1723362] Re: gnome-software spams error messages to journald and causes 100% CPU usage

This also affects me, May 5 17:45:33 hulk gnome-software[8798]: g_byte_array_remove_range: assertion 'index_ + length <= array->len' failed May 5 17:45:33 hulk gnome-software[8798]: Ignoring unexpected response May 5 17:45:33 hulk gnome-software[8798]: g_byte_array_remove_range: assertion

[Bug 1767544] Re: While running the Orca screen reader, system hangs while gnome-control-center is open

On my computer, Orca tried to read part of the Wi-Fi settings screen before it locked up and exhibited the same behavior that was described in Jeremy's audio recording. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1315342] Re: Stop appending 3rd party PPA names with warnings

> The ammendments "# disabled on upgrade to trusty" is a comment and subsequently has not effect on the entry. Nope, it makes the name of every PPA in the software properties dialog the same: 'disabled on upgrade to bionic'. Extremely annoying and difficult to manage. -- You received this bug

[Bug 1768967] Re: Screen randomly flips 180 degrees

** Summary changed: - Screen randomly flips 180 degreese twice + Screen randomly flips 180 degrees ** Description changed: - I'm running Ubuntu 18.04 on an HP 350 G1 laptop. Randomly, the screen - will become flipped, go black for a second, and then return to normal. + I'm running Ubuntu 18.04

[Bug 1768967] [NEW] Screen randomly flips 180 degreese twice

Public bug reported: I'm running Ubuntu 18.04 on an HP 350 G1 laptop. Randomly, the screen will become flipped, go black for a second, and then return to normal. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17

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

This started to affect our solutions-qa test runs yesterday/last night at some point - we can no longer deploy bionic on uefi systems: We're not using dkms packages at all; here is the failed install log from maas: http://paste.ubuntu.com/p/NVdV4tZvJW/ ** Changed in: shim-signed (Ubuntu)

[Bug 1765726] Re: libgoo-canvas-perl [needs-packaging]

Sounds like shutter would be a prime candidate for someone to make a snap of? Isn't this the whole reason snaps were created? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765726 Title:

[Bug 1766013] [NEW] package virtualbox-dkms 5.2.10-dfsg-2 failed to install/upgrade: installed virtualbox-dkms package post-installation script subprocess returned error exit status 1

Public bug reported: Happened during upgrade 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: virtualbox-dkms 5.2.10-dfsg-2 ProcVersionSignature: Ubuntu 4.15.0-17.18-generic 4.15.17 Uname: Linux 4.15.0-17-generic x86_64 NonfreeKernelModules: vboxpci vboxnetadp vboxnetflt vboxdrv

[Bug 1764937] [NEW] WARNING: Goo::Canvas/libgoo-canvas-perl is missing --> drawing tool will be disabled!

Public bug reported: Unable to use editor portion of shutter. The only candidate for libgoocanvas is libgoocanvas2-perl, which is not providing necessary components. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: shutter 0.94-1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15

[Bug 1743231] Re: ImportError: No module named backports.ssl_match_hostname

Hi. We investigated a similar issue in Debian [1] Make sure you have this package installed: https://packages.ubuntu.com/artful/python-backports.ssl-match-hostname If you still get the error: A temporary fix is to create an empty file called __init__.py in

[Bug 1764766] [NEW] cryptsetup completion missing commands

Public bug reported: Basic luks commands are missing, such as luksOpen, luksClose from completion, that were there in previous versions. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bash-completion 1:2.8-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux

[Bug 1759920] Re: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux-image-4.13.0-37-generic)

Is there any issue with removing the intel-microcode package with the -38 kernel? The intel-microcode package does not seem to get installed on a fresh 16.04.4 system and the Spectre/Meltdown checker referenced earlier shows no vulnerability as the mitigation is all done in the kernel. -- You

[Bug 1759445] Re: kernel panic when trying to reboot in bionic

After updating firmware on the servers, we can't reproduce it at all anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759445 Title: kernel panic when trying to reboot in bionic To manage

[Bug 1748876] Re: One by Wacom (medium tablet) not reported by libwacom

In addition to the Linux 4.16 requirement pointed out by Michael, Ubuntu will need to update libwacom to at least version 0.28 for the device to appear in the control panel. Until Ubuntu includes updates, you can build libwacom from source[1][2] as well as get the "input-wacom" kernel backports

[Bug 1759445] Re: kernel panic when trying to reboot in bionic

So far we've only been able to produce this by doing bionic deploys. One thing that stands out in the rsyslog for bionic deploys is this failure: http://paste.ubuntu.com/p/y8xXc7PYjp/ Apr 2 17:48:35 leafeon blkdeactivate[1782]: /sbin/blkdeactivate: line 345: /bin/sort: No such file or

[Bug 759725] Re: The kernel is no longer readable by non-root users

Does this mean there is now no non-root way to extract files from filesystem images? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/759725 Title: The kernel is no longer readable by non-root users

[Bug 1759445] Re: kernel panic when trying to reboot in bionic

We reproduced it again... looking to try the testing now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759445 Title: kernel panic when trying to reboot in bionic To manage notifications about

[Bug 1759445] Re: kernel panic when trying to reboot in bionic

We can no longer reproduce this. ** Changed in: linux (Ubuntu Bionic) Status: Triaged => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759445 Title: kernel panic when trying to

[Bug 1759445] Re: kernel panic when trying to reboot in bionic

** Tags added: foundations-engine -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759445 Title: kernel panic when trying to reboot in bionic To manage notifications about this bug go to:

[Bug 1759445] Re: Bionic due to kernel panic

This bug is a kernel panic when rebooting at the end of a MAAS deployment of bionic; there is no way to run apport-collect. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Summary changed: - Bionic due to kernel panic + kernel panic when trying to reboot in bionic --

[Bug 1756633] Re: Backport request, 16.04 LTS (w/ Spectre/Meltdown fixups)

@sdeziel -- I have tested on an Ivy Bridge era (i5-3427U) and Apollo Lake era (N3350) system thus far. The former is covered by the Intel 20180312 release, the latter is not. If time permits I'll also test on a Skylake system. Everything seems to be working properly w/r2 updated microcode query

[Bug 1640635] Re: cloud-init creates /etc/network/interfaces.d/50-cloud-init.cfg even if /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg present

Additional nuance: On a netplan enabled system also using cloud-init (+ curtin), the same assertion is made regarding how to disable network functionality tied to cloud-init is mentioned in /etc/netplan/50-cloud-init.yaml ("… disable via stanza in

[Bug 1640635] Re: cloud-init creates /etc/network/interfaces.d/50-cloud-init.cfg even if /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg present

** Also affects: netplan 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/1640635 Title: cloud-init creates /etc/network/interfaces.d/50-cloud-init.cfg even

[Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices

linuxcub, my apologies for not replying sooner -- I don't think I got a notification of your messages for some reason... Its odd that installing/reinstalling portions of Ubuntu seem to fix the issue. It looks like the Bionic beta only relased IOSs for Kubuntu, Budgie, Kylin, MATE, and Xubuntu. I

[Bug 1710296] Re: script hangs and never finishes

this issue persist jason@server03:~$ pgrep check-new-re 765 1925 1952 3852 4072 5238 5467 5646 6464 6753 9409 12877 14336 15288 16599 17057 18756 20018 20029 20174 20255 20726 22315 22523 22855 24292 24876 25964 26093 27981 28489 29387 30350 32556 jason@server03:~$ pgrep check-new-re | wc -l 34

[Bug 1756633] [NEW] Backport request, 16.04 LTS (w/ Spectre/Meltdown fixups)

Public bug reported: Once the post Spectre/Meltdown situation has stabilized, it would be appreciated if that edition of Intel CPU microcode is backported into Xenial / 16.04 LTS. Thanks :-) ** Affects: intel-microcode (Ubuntu) Importance: Undecided Status: New -- You received

[Bug 1435695] Re: intel-microcode could use better docs about upstream versions per CPU

~ 2 years later ... :-) For item 2, Intel now* documents what CPU family and stepping(s) are covered by each "Intel Processor Microcode" data file bundle. However, it would be better just point to the authoritative location, rather than engaging in lots of copy-pasta (yes pun) from the upstream

[Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed

I haven't tried 4.16 but it is present in mainline 4.15.8 ** Changed in: linux (Ubuntu) Status: Invalid => Confirmed ** Changed in: systemd (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

Re: [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

Ok, that's not much of a workaround then :). On Thu, Mar 8, 2018 at 3:52 AM, Dan Watkins <daniel.watk...@canonical.com> wrote: > On Wed, Mar 07, 2018 at 11:42:29PM -0000, Jason Hobbs wrote: >> Is there a workaround for this? I can just rm /etc/resolv.conf and >> create it wit

[Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

Is there a workaround for this? I can just rm /etc/resolv.conf and create it with the contents I want, right? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750884 Title: [2.4, bionic]

[Bug 1753525] Re: Wacom tablet not recognized in Settings > Devices

The "stylus not recognized" part of this issue is almost certainly https://bugzilla.gnome.org/show_bug.cgi?id=793499. No access to the pad device on the other hand is not an issue I'm familiar with. The old unity-control-center bug that OP linked do was due to an issue with GNOME not being

[Bug 1575887] Re: Intuos Art / Intuos Draw 2015 isn't detected by the wacom properties window

linuxcub, the "Stylus not recognized" is actually a different issue than the one described here. The upstream bug filed for that particular issue can be found at https://bugzilla.gnome.org/show_bug.cgi?id=793499 You should file a new issue against Ubuntu 18.04 (specifically the ) which references

[Bug 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

Add me to the List of People with this problem, nvidia 384.111 worked great until this kernel now same problem as original poster. Had to go back to 112 to get it to work. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1750927] [NEW] package android-androresolvd 1.3-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

Public bug reported: ../ ProblemType: Package DistroRelease: Ubuntu 16.04 Package: android-androresolvd 1.3-1 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic i686 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: i386 Date: Wed Feb 21 14:10:12 2018

[Bug 1750886] Re: Audio clips after kernel update

OK, I went back to the xenial 108 kernel again and the issue came back.. I tested further and found that only certain applications are exhibiting this. For example, it's happening in VLC and Chrome, but not in audio played by FF. Going to close this as it looks like it's probably not a kernel

[Bug 1750886] Re: Audio clips after kernel update

Also happening on 4.4.108-0404108-generic mainline kernel :/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750886 Title: Audio clips after kernel update To manage notifications about this bug go

[Bug 1750886] Re: Audio clips after kernel update

Also happening on 4.4.110-0404110-generic mainline kernel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1750886 Title: Audio clips after kernel update To manage notifications about this bug go

[Bug 1750886] Re: Audio clips after kernel update

Tested and reproduced on mainline kernel linux- image-4.4.116-0404116-generic . Incidentally, issue does not occur in the HWE kernel, 4.13.0-32-generic. ** Tags added: kernel-bug-exists-upstream ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug

[Bug 1750886] [NEW] Audio clips after kernel update

Public bug reported: After updating to 4.4.0-112 on xenial, getting constant buffer underruns in pulseaudio, causing frequent clips where the audio cuts out for a fraction of a second. Booting back into 4.4.0-108 consistently resolves this issue. This issue is reproducible on 4 different audio

[Bug 1750379] Re: Distortion Realtek ALC887

This started affecting me with the kernel update to 4.4.0-112-generic on xenial. I booted the old kernel and the issue went away. Tried a few times back and forth and the 4.4.0-112 kernel consistently has the sound dropouts, while 4.4.0-108 does not. Also tested with 3 different audio cards (by

[Bug 1576420] Re: [H55M-D2H, Realtek ALC887, Green Line Out, Rear] Underruns, dropouts or crackling sound

This started affecting me with the kernel update to 4.4.0-112-generic on xenial. I booted the old kernel and the issue went away. Tried a few times back and forth and the 4.4.0-112 kernel consistently has the sound dropouts, while 4.4.0-108 does not. Also tested with 3 different audio cards (by

[Bug 1415924] Re: Vital config file not included in package

I'm setting this to confirmed because following the steps from the link in the description resolves the issue for me. I'm using Artful Aardvark (17.10). ** Changed in: gnome-xcf-thumbnailer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member

[Bug 1749890] [NEW] Cannot connect to WebDAV (Owncloud): "Not a WebDAV enabled share"

Public bug reported: Under 17.04, I had added an Owncloud account to the Gnome Online Accounts under Gnome 3. This created an entry in Nautilus' sidebar that allowed me to remotely browse my Owncloud account. Since upgrading to 17.10, clicking on the entry just brings up an error dialog: Unable

[Bug 1676912] Re: Kernel 4.9+ regression: Suspend - Freezing of tasks failed

Yea except "4.9+" meant it was still present in 4.10 (and 13 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/1676912 Title: Kernel 4.9+ regression: Suspend - Freezing of tasks failed To

[Bug 1747927] Re: when net booting servers with MAAS, grub should never wait for user input to reboot

. Jason On Wed, Feb 7, 2018 at 11:30 AM, Steve Langasek <steve.langa...@canonical.com> wrote: > As I asked in https://bugs.launchpad.net/maas/+bug/1743249/comments/65: > > What do you think the correct behavior should be when grub cannot find > the file that it needs in order to

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

Ok - I filed a few more bugs to cover the aspects of this failure other than the slow response for grub.cfg. bug 1747927 - grub should not hang waiting for user input when booting from MAAS. bug 1747928 - When a known server in Deploying state boots to the enlisting environment, it should not

[Bug 1747927] Re: when net booting servers with MAAS, grub should never wait for user input to reboot

** Summary changed: - when net booting servers, grub should never wait for user input to reboot + when net booting servers with MAAS, grub should never wait for user input to reboot -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1747927] [NEW] when net booting servers, grub should never wait for user input to reboot

Public bug reported: In bug 1743249, grub sometimes would hang waiting for user input on the keyboard. This is never an appropriate action for a net booting server, at least not one booting under MAAS direction. It may be appropriate to pause for 30 seconds or something so someone can see the

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

Andres, there is more to this bug than just the slow grub response. MAAS could do more after the fact to recover in this situation. For example, once a machine boots to the ephemeral environment, it has plenty of time to talk to MAAS and find out it's not actually supposed to be enlisting, and

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

getting hung up. Jason On Tue, Feb 6, 2018 at 5:09 PM, Jason Hobbs <jason.ho...@canonical.com> wrote: > dm-delay looks very interesting along those lines. > > https://www.enodev.fr/posts/emulate-a-slow-block-device-with-dm-delay.html > > https://www.kernel.org/doc/Docume

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

dm-delay looks very interesting along those lines. https://www.enodev.fr/posts/emulate-a-slow-block-device-with-dm- delay.html https://www.kernel.org/doc/Documentation/device-mapper/delay.txt On Tue, Feb 6, 2018 at 5:06 PM, Jason Hobbs <jason.ho...@canonical.com> wrote: > On Tue, Fe

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

inlien: > > > On Tue, Feb 6, 2018 at 5:17 PM, Jason Hobbs <jason.ho...@canonical.com> > wrote: > >> Andres, it was a single test in both cases, and in both cases there was >> almost no delay from MAAS. It's not significant enough to call it >> positive results.

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

Andres, it was a single test in both cases, and in both cases there was almost no delay from MAAS. It's not significant enough to call it positive results. Since neither of you answered yes, I'll assume the answer was no to my question of whether there was anything in my logs or data that showed

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

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 wrote:

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

The patch from #84 is adding a cache for reading the template file on the rack controller. I don't understand why this change is being made. This file will almost certainly be in the page cache anyhow as these systems have a lot of free ram. Usually it's best to just let the page cache do its

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

Anyhow, I tested with the patch from #84 as requested, here are the results: http://paste.ubuntu.com/26531873/ We're still seeing some retries with it, same as before. But, I think the test is of limited value. It didn't make things worse but we don't have any evidence from the test that it

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

send updates to which racks for *dhcp* changes, so this is not at > all related to the RPC boot requests for pxe. > > On Tue, Feb 6, 2018 at 11:43 AM, Jason Hobbs <jason.ho...@canonical.com> > wrote: > >> Can you please comment on the deadlock detected error from th

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

On Tue, Feb 6, 2018 at 10:40 AM, Andres Rodriguez <andres...@ubuntu-pe.org> wrote: > On Tue, Feb 6, 2018 at 11:24 AM, Jason Hobbs <jason.ho...@canonical.com> > wrote: > >> On Mon, Feb 5, 2018 at 4:07 PM, Andres Rodriguez >> <andres...@ubuntu-pe.org> wrote:

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

Can you please comment on the deadlock detected error from the db log in posted in #36 http://paste.ubuntu.com/26530761/ That is not expected behavior is it? Also the fact that MAAS thinks its losing rack/region connections seems like it could be related to this behavior. -- You received this

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

doing retries, although in neither case did it take very long. http://paste.ubuntu.com/26530737/ So it seems that changing the CPU limits for the VMs doesn't change the results drastically, which lines up with the data showing CPU utilization never gets over 50%. Jason On Mon, Feb 5, 2018

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

design - the MAC specific file has to be generated before grub times out. It could instead be generated before the node ever starts booting, allowing it to be served just as fast as the -default-amd64 file is, eliminating that race condition. Jason > On Mon, Feb 5, 2018 at 4:30 PM, Jason Hobb

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

+1 Mike. I agree it's a bug, but it there isn't real evidence that it's what causes the long delay. On Mon, Feb 5, 2018 at 7:12 PM, Mike Pontillo wrote: > Ah, I see what you mean there; I used the following filter in Wireshark: > > udp.dstport == 25305 or

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

On Mon, Feb 5, 2018 at 3:45 PM, Andres Rodriguez <andres...@ubuntu-pe.org> wrote: > @Jason, > > On Mon, Feb 5, 2018 at 3:38 PM, Jason Hobbs <jason.ho...@canonical.com> > wrote: > >> On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez >> <andres...@ubuntu-pe

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

@Mike, you can see the stacked response behavior in https://bugs.launchpad.net/maas/+bug/1743249/+attachment/5046952/+files/spearow-fall-back-to-default-amd64.pcap You can tell packet 90573 is a response to the requests for grub.cfg- because its destination port (25305) is the src port the

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

On Mon, Feb 5, 2018 at 3:27 PM, Andres Rodriguez <andres...@ubuntu-pe.org> wrote: > @Jason, > > > On Mon, Feb 5, 2018 at 3:38 PM, Jason Hobbs <jason.ho...@canonical.com> > wrote: > >> On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez >> <and

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

request grub makes for the file - the tcpdump logs show it. And these are not "read 4 times" requests - they are retries because grub didn't get a response. This pcap shows MAAS responding to every request for grub.cfg-: https://bugs.launchpad.net/maas/+bug/1743249/+attachment/5046952/+files/

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

The packetdump (comment #35) of MAAS not responding to grub's request for the mac specific grub.cfg before grub times out, and then responding immediately to the generic-amd64 grub cfg, clearly shows a race condition in MAAS. MAAS's design of dynamically generating the interface specific grub

<    1   2   3   4   5   6   7   8   9   10   >