[Bug 1725416] Re: Elantech touch pad device not detected/working properly

[Daniel van Vugt]

Please also try other kernel versions and tell us if some older or newer kernel 
fixes the problem for you:
  http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D

** Changed in: linux (Ubuntu)
   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/1725416

Title:
  Elantech touch pad device not detected/working properly

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

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

[Bug 1181666] Re: gnome-shell randomly blocks mouse clicks from working in app windows

[Daniel van Vugt]

No, I think that's probably luck or an indirect side-effect.

The issues with clicks being ignored are in the 'mutter' code.

** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu)
   Status: New => Confirmed

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

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

Title:
  gnome-shell randomly blocks mouse clicks from working in app windows

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

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

[Bug 1747557] [NEW] new ssd drive. clean install. acer laptop. PNY 240GB

[Phil Sprute]

Public bug reported:

failed. doing grub update and grub install manually - then doing a
slackware install. my touchpad also does not work correctly in UEFI mode
with "try ubuntu".

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4 [modified: 
lib/partman/automatically_partition/question]
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-lowlatency 4.10.17
Uname: Linux 4.10.0-28-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CasperVersion: 1.376.2
Date: Mon Feb  5 18:15:48 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/ubuntustudio.seed boot=casper quiet splash ---
LiveMediaBuild: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ubiquity-2.21.63.4 ubuntustudio xenial

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

Title:
  new ssd drive. clean install. acer laptop. PNY 240GB

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

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

[Bug 1527013] Re: menu appears at the top left corner

[Simon Quigley]

** Changed in: lxqt-panel (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  menu appears at the top left corner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1527013/+subscriptions

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

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

[Mike Pontillo]

Ah, I see what you mean there; I used the following filter in Wireshark:

udp.dstport == 25305 or udp.srcport == 25305

This is not the behavior I saw if the TFTP request is answered in a
timely manner, so I suspect that the long delay between the initial
request and the answer is causing the timeouts to occur in the TFTP
code, which causes this separate "stacked OACK" bug.

By the time the "stacked OACKs" are sent, it's been over one minute, and
the client isn't listening for a reply any more. So yes, "stacked OACKs"
are a real bug, but right now I think they're just distracting from the
root cause (the long delay).

-- 
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 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

[Joseph Salisbury]

I built the next test kernel, up to the following commit:
7de295e2a47849488acec80fc7c9973a4dca204e

The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1746806

Can you test that kernel and report back if it has the bug or not? I
will build the next test kernel based on your test results.

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

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

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

[Bug 1747553] Re: dhcp allow client-identifier control

[Ryan Harper]

*** This bug is a duplicate of bug 1738998 ***
https://bugs.launchpad.net/bugs/1738998

** This bug has been marked a duplicate of bug 1738998
   netplan does not allow dhcp client identifier type to be specified

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

Title:
  dhcp allow client-identifier control

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

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

[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised

[mirek kodfdf]

I have ELAN fingerprint sensor integrated into touch pad BUT KERNEL can
not even register it to the system.

I'm getting error from the kernel log

- i2c i2c-7 Failed to register i2c client ELAN2210:00 at 0x10 (-16)
- i2c i2c-7 failed to add I2C device ELAN2210:00 from ACPI

So .. my ELAN fingerprint is not visible at all in USB, HARDWARE or PCI
...

Do you have any idea to to fix it IN KERNEL ?

Thanks for any clue ...

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

Title:
  [04f3:0903] Elan Microelectronics Corp fingerprint reader not
  recognised

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

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

[Bug 1741473] Re: package libdrm-common 2.4.83-1~16.04.1 failed to install/upgrade: a tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está no pacote libdrm-amdgpu1:amd64 2.4.81+git201

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: libdrm (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/1741473

Title:
  package libdrm-common 2.4.83-1~16.04.1 failed to install/upgrade: a
  tentar sobre-escrever '/usr/share/libdrm/amdgpu.ids', que também está
  no pacote libdrm-amdgpu1:amd64
  2.4.81+git20170717.ac214017-0ubuntu0ricotz~16.04.1

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

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

Re: [Bug 1742933] Re: Regression in 2018-01-08 updates

[Steve Langasek]

On Mon, Feb 05, 2018 at 11:03:00AM -, Thomas wrote:
> The microcode file found in 3.20180108.0+really20170707ubuntu16.04.1 for
> my Haswell CPU still causes problem that I haven't had before.

> When booting the kernel, it cannot find any partitions. Funiliy, the
> initrd file contains nothing but the microcode file. Reverting manually
> to a known-good initrd file (also containing nothing but the microcode
> file) fixes it.

The initrd file is a concatenation of two archives, one of which is the
microcode only, the other contains the normal initrd contents.

It is exceedingly unlikely that the problem you're experiencing is in any
way connected to a microcode update.

You can introspect the initrd on disk with the command:

  (cpio -t; zcat | cpio -t) < /boot/initrd.img

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

Title:
  Regression in 2018-01-08 updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1742933/+subscriptions

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

[Bug 1747553] [NEW] dhcp allow client-identifier control

[Ryan Harper]

*** This bug is a duplicate of bug 1738998 ***
https://bugs.launchpad.net/bugs/1738998

Public bug reported:

In some cases, users of DHCP want to specify the client identifier.
Under networkd, this can be toggled between mac and the RFC client id,
from systemd-networkd documentation

ClientIdentifier=
The DHCPv4 client identifier to use. Either "mac" to use the MAC address of the 
link or "duid" (the default, see below) to use an RFC4361-compliant Client ID.

** Affects: nplan (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/1747553

Title:
  dhcp allow client-identifier control

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

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

[Bug 1747554] [NEW] cloud-init status in bionic stack traces

[Ryan Harper]

Public bug reported:

1. root@b2:~# lsb_release -rd
Description:Ubuntu Bionic Beaver (development branch)
Release:18.04

2. root@b2:~# apt-cache policy cloud-init
cloud-init:
  Installed: 17.2-13-g6299e8d0-0ubuntu1
  Candidate: 17.2-13-g6299e8d0-0ubuntu1
  Version table:
 *** 17.2-13-g6299e8d0-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

3. cloud-init status should give me status on if it's running or
finished, etc

4. cloud-init stack traces
(neipa) ~ % lxc launch ubuntu-daily:bionic b2 
Creating b2
Starting b2
(neipa) ~ % lxc exec b2 /bin/bash
root@b2:~# systemctl status
● b2
State: initializing
 Jobs: 62 queued
   Failed: 0 units
Since: Tue 2018-02-06 00:58:41 UTC; 9s ago
   CGroup: /
   ├─123 /bin/bash
   ├─133 systemctl status
   ├─134 pager
   ├─init.scope
   │ └─1 /sbin/init
   └─system.slice
 ├─systemd-networkd-wait-online.service
 │ └─120 /lib/systemd/systemd-networkd-wait-online
 ├─systemd-resolved.service
 │ └─121 /lib/systemd/systemd-resolved
 ├─systemd-udevd.service
 │ └─52 /lib/systemd/systemd-udevd
 ├─systemd-journald.service
 │ └─51 /lib/systemd/systemd-journald
 └─systemd-networkd.service
   └─119 /lib/systemd/systemd-networkd
root@b2:~# set -o vi
root@b2:~# ^Cstemctl status
root@b2:~# cloud-init status
Traceback (most recent call last):
  File "/usr/bin/cloud-init", line 11, in 
load_entry_point('cloud-init==17.2', 'console_scripts', 'cloud-init')()
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 859, in main
get_uptime=True, func=functor, args=(name, args))
  File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2279, in 
log_time
ret = func(*args, **kwargs)
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/status.py", line 55, in 
handle_status_args
status, status_detail, time = _get_status_details(init.paths)
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/status.py", line 114, in 
_get_status_details
CLOUDINIT_DISABLED_FILE, paths)
  File "/usr/lib/python3/dist-packages/cloudinit/cmd/status.py", line 96, in 
_is_cloudinit_disabled
return (is_disabled, reason)
UnboundLocalError: local variable 'reason' referenced before assignment
root@b2:~# cloud-init status

** Affects: cloud-init (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/1747554

Title:
  cloud-init status in bionic stack traces

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

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

[Bug 1527013] Re: menu appears at the top left corner

[Simon Quigley]

** Also affects: lxqt-panel (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: lubuntu-next

** Changed in: lxqt-panel (Ubuntu)
   Status: New => In Progress

** Changed in: lxqt-panel (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: lxqt-panel (Ubuntu)
   Importance: Undecided => High

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

Title:
  menu appears at the top left corner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxqt-panel/+bug/1527013/+subscriptions

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

[Bug 1700092] Re: Text is tiny on HiDPI screens

[Bug Watch Updater]

** Changed in: gedit
   Status: Confirmed => Fix Released

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

Title:
  Text is tiny on HiDPI screens

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

[Steve Langasek]

On Tue, Feb 06, 2018 at 12:11:21AM -, Mike Pontillo wrote:
> Steve, can you be more specific about which packet capture showed the
> "stacked OACK" behavior?

This was the first packet capture that Jason posted, in comment #30.  The
udp retransmits shown in packets 6262-6268 each receive an answering packet
in 6270-6271,6273-6277, in addition to 6269 as an answer to 6261.  For
whatever reason, wireshark here does not decipher these duplicate OACK
packets as OACK, but an examination of the raw packets shows that's clearly
what they are.

> I looked at a packet capture Andres pointed me to, and don't see the
> "stacked OACKs" you describe. Each TFTP transaction (per RFC 1350) is
> indicated by the (source port, dest port) tuple, and I see that MAAS
> correctly OACKs each individual transaction (per RFC 2347) - not the
> retry packets within the same transaction.

Packets 6269-6271,6273-6277 are all answers to the same port on the client.
They don't have the same source port, because MAAS has allocated a separate
source port for each of these.  It's not acking a separate individual
transaction, it's MAAS /creating/ a separate transaction (with the
allocation of a separate source port) for each one.

RFC2347 does not speak to this; the discussion of the port negotiation is in
RFC1350 §4:

   In order to create a connection, each end of the connection chooses a
   TID for itself, to be used for the duration of that connection.  The
   TID's chosen for a connection should be randomly chosen, so that the
   probability that the same number is chosen twice in immediate
   succession is very low.  Every packet has associated with it the two
   TID's of the ends of the connection, the source TID and the
   destination TID.  These TID's are handed to the supporting UDP (or
   other datagram protocol) as the source and destination ports.  A
   requesting host chooses its source TID as described above, and sends
   its initial request to the known TID 69 decimal (105 octal) on the
   serving host.  The response to the request, under normal operation,
   uses a TID chosen by the server as its source TID and the TID chosen
   for the previous message by the requestor as its destination TID.
   The two chosen TID's are then used for the remainder of the transfer.

MAAS responds to 8 udp retransmits on srcport=25305, dstport=69 by sending 8
independent OACK packets back to dstport=25305 each from a different source
port.

Since Andres confirms that these duplicate acks still only result in one
database query, this may be a negligible bug if the only impact is duplicate
small udp packets.  OTOH, depending on how MAAS implements this, it could
also result in port exhaustion on the server if unanswered OACKs are allowed
to linger.

-- 
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 1747505] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From brsri...@in.ibm.com 2018-02-05 19:29 EDT---
*** Bug 164283 has been marked as a duplicate of this bug. ***

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

Title:
  [Ubuntu 18.04][WSP/DD2.1] Bionic netinstall failed on Witherspoon/4GPU
  system

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

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

[Bug 1746310] Re: Drop fonts-symbola from platform?

[Simon Quigley]

I agree with Gunnar, I'm -1 with both my Lubuntu and Kubuntu hats on if
this means a regression for Qt-based desktops.

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

Title:
  Drop fonts-symbola from platform?

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

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

Re: [Bug 1604750] Re: Byobu not clearing update numbers after updates

[Mark Kelly]

Hi,

Yes, the cache file is at:

$BYOBU_RUN_DIR/cache.$BYOBU_BACKEND/updates-available

-mark

On Mon, Feb 5, 2018 at 1:29 AM jokrebel <1604...@bugs.launchpad.net>
wrote:

> Hi again,
>
> "Next time it happens, before you issue the --reinstall command, can you
> check the cache file and tell me if it has the 2 2 (or whatever the
> number your status shows) or a 0 0 in it ?"
>
> of cause i will do, but can you tell me exactly the name of the file and
> the path where to find?
>
> thanks a lot
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1604750
>
> Title:
>   Byobu not clearing update numbers after updates
>
> Status in byobu:
>   Confirmed
> Status in byobu package in Ubuntu:
>   Confirmed
> Status in Fedora:
>   New
>
> Bug description:
>   I am running byobu on Debian Testing and, as of the last week or two,
>   byobu has started not clearing the update counter even after updates.
>   Even exiting byobu completely and starting a new session does not
>   clear the indicator, only updating do it.  Sometimes, and this is not
>   consistent, running an `apt-get update` causes the indicator to clear
>   itself.
>
>   ~$ uanme -a
>   Linux enekk 4.6.0-1-amd64 #1 SMP Debian 4.6.3-1 (2016-07-04) x86_64
> GNU/Linux
>   ~$ byobu -v
>   byobu version 5.87
>   Screen version 4.04.00 (GNU) 19-Jun-16
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/byobu/+bug/1604750/+subscriptions
>

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

Title:
  Byobu not clearing update numbers after updates

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

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

[Bug 1717495] Re: Display not coming up correctly when running 64bit Iso under Virtualbox

[Simon Quigley]

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

** No longer affects: lubuntu-next

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

Title:
  Display not coming up correctly when running 64bit Iso under
  Virtualbox

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

[Jason Hobbs]

On Mon, Feb 5, 2018 at 3:45 PM, Andres Rodriguez
 wrote:
> @Jason,
>
> On Mon, Feb 5, 2018 at 3:38 PM, Jason Hobbs 
> wrote:
>
>> On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez
>>  wrote:
>> > No new data was provided to mark this New in MAAS:
>> >
>> > 1. Changes to the storage seem to have improved things
>>
>> Yes, it has.  That doesn't change whether or not there is a bug in
>> MAAS.  Can you please address the critical log errors that I mentioned
>> in comment #36?  This seems like enough to establish something is
>> going wrong in MAAS.
>>
>
> The tftp issue shows no evidence this is causing any booting failures. We
> have seen this issue before and confirmed that it doesn't cause boot
> issues. See [1]. If you want to try it, it is available in
> ppa:maas/proposed.
>
> [1].https://bugs.launchpad.net/maas/+bug/1376483

It's been "Fixed" multiple times before, in your link above and also
in bug 1724677, but we still see them, very suspiciously around the
time of failures.  I'm not convinced these are actually understood.
Do you have a specific commit  or some idea of what change that
addresses these in 2.4?

> As far as the postgresql logs with "maas@maasdb ERROR: could not serialize
> access due to concurrent update" that is  *not* a bug in MAAS or an issue.
> That's perfectly normal messages with the isolation level the MAAS DB is
> running with. This basically means something else is trying to update the
> db while something else is updating it, and MAAS already handles this by
> doing retries.

That is just one type of db error in the log.  There are many more.
Here's one that says there was a deadlock detected. That's not normal
OK behavior is it?

http://paste.ubuntu.com/26527181/

>> > 2. No tests have been run with fixed grub that have caused boot
>> failures.
>>
>> The comments from #56 were testing with the fixed grub - sorry if that
>> wasn't clear.
>>
>> > 3. AFAIK, the VM config has not changed to use less CPU to compare
>> results and whether this config change causes the bugs in question.
>>
>> The CPU load data from comments #48 and #50 shows that CPU load is not
>> the problem.  The max load average was under 12 on a 20 thread system.
>> That means there was lots of free CPU time, and that this workload is
>> not CPU bound.
>>
>
> CPU load is not CPU utilization. We know that at the time there's 6 other
> VM's with 150%+ CPU usage are writing to the disk because they are being
> deployed and/or configured (e.g. software installation).  Correct me if
> wrong, but this can cause the prioritization of whatever is writing to disk
> over anything else, like the MAAS processes access for resources.

The 150%+ number you are seeing is that process using all of 1 core
(hyperthread) and 50% of another (it's a multithreaded process).  This
does not mean the process is using 150% of the entire CPU capacity.

We don't just have load average - we also have a breakdown of CPU
utilization from top, every 5 seconds:

%Cpu(s): 23.5 us,  6.3 sy,  0.0 ni, 62.9 id,  7.2 wa,  0.0 hi,  0.1 si,
0.0 st

The top man page has more to say about this line, but have a look at
the 'id' number. It's the % of cpu time spent in the idle process
(nothing to do) in the sample period (5 seconds in the above logs).

The lowest that number ever goes in the logs I posted is 52%, meaning
over any 5 second period, we never use more than half of the available
CPU capacity.

> That being said, because CPU load doesn't show high we are making the
> *assumption* that it is not impacting MAAS, but again, this is an
> assumption. Making the requested change for having at least 4 CPUs (ideally
> 6) would allow us to determining what are the effects and see whether
> there's any difference on behavior and would help identify what other
> issues.
>
> Without having the comparison then we are making it more difficult to
> isolate the problem.

To improve performance the typical pattern is 1) identify the
bottleneck 2) eliminate that as the bottleneck 3) repeat.

We have not identified CPU as a bottleneck.  The top data says it is
not!

In the absence of data showing the CPU as being the bottleneck,
reducing CPU usage doesn't help identify the performance blocker,
because it may just move the bottleneck.  For example, it may cause
the processes that are doing disk I/O to not get scheduled to run as
much, which may then reduce the amount of disk I/O they can do, which
may alleviate the issue, but not because MAAS was CPU starved before
and now isn't.  Better to reduce the storage contention in the first
place, if the data shows that storage contention is the bottleneck.

In this case we had data from iotop that indicated storage contention
as the bottleneck, and reducing it seems to have alleviated the
problem, as we haven't hit the failure since then. We're going to take
more steps to alleviate storage contention even more soon, by making
sure 

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

[Jason Hobbs]

@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 request for grub.cfg- was coming from (packets 2 through 38).

On Mon, Feb 5, 2018 at 6:11 PM, Mike Pontillo
 wrote:
> Steve, can you be more specific about which packet capture showed the
> "stacked OACK" behavior?
>
> I looked at a packet capture Andres pointed me to, and don't see the
> "stacked OACKs" you describe. Each TFTP transaction (per RFC 1350) is
> indicated by the (source port, dest port) tuple, and I see that MAAS
> correctly OACKs each individual transaction (per RFC 2347) - not the
> retry packets within the same transaction. Subsequently (in the same
> second, after the client ACKs the data packet) it re-requests the same
> file (which is the bug in grub that I understand is fixed), and then the
> client starts a new transaction and MAAS correctly issues another OACK.
>
> --
> 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:
>   In Progress
>
> 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 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 1747329] Re: Workaround needed to boot from USB stick - "gfxboot.c32: not a COM32R image"

[Simon Quigley]

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

** No longer affects: lubuntu-next

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

Title:
  Workaround needed to boot from USB stick - "gfxboot.c32: not a COM32R
  image"

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

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

[Bug 1746310] Re: Drop fonts-symbola from platform?

[Gunnar Hjalmarsson]

If qt does not support fonts-noto-color-emoji, replacing would be a
regression, especially for Kubuntu, and may not be a good idea. I
understand that the packages don't conflict to each other. What's the
drawback with keeping it as is for now, and install both packages in
Ubuntu?

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

Title:
  Drop fonts-symbola from platform?

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

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

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

[Mike Pontillo]

Steve, can you be more specific about which packet capture showed the
"stacked OACK" behavior?

I looked at a packet capture Andres pointed me to, and don't see the
"stacked OACKs" you describe. Each TFTP transaction (per RFC 1350) is
indicated by the (source port, dest port) tuple, and I see that MAAS
correctly OACKs each individual transaction (per RFC 2347) - not the
retry packets within the same transaction. Subsequently (in the same
second, after the client ACKs the data packet) it re-requests the same
file (which is the bug in grub that I understand is fixed), and then the
client starts a new transaction and MAAS correctly issues another OACK.

-- 
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 1747545] Re: plymouthd crashed with SIGSEGV in script_obj_deref_direct()

[Apport retracing service]

*** This bug is a duplicate of bug 1580078 ***
https://bugs.launchpad.net/bugs/1580078

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1580078, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1747545/+attachment/5049444/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1747545/+attachment/5049447/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1747545/+attachment/5049455/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1747545/+attachment/5049457/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1747545/+attachment/5049458/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1747545/+attachment/5049459/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1747545/+attachment/5049460/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1580078

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  plymouthd crashed with SIGSEGV in script_obj_deref_direct()

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

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

[Bug 1747544] [NEW] /usr/bin/searchmonkey:*** Error in `searchmonkey': realloc(): invalid pointer: ADDR ***

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
searchmonkey.  This problem was most recently seen with package version 
0.8.1-9, the problem page at 
https://errors.ubuntu.com/problem/b754475bac88e5b0cc2e93a5d638a3b1b10852a4 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful utopic vivid wily xenial zesty

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

Title:
  /usr/bin/searchmonkey:*** Error in `searchmonkey': realloc(): invalid
  pointer: ADDR ***

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

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

[Bug 1747543] [NEW] [Hyper-V] linux-azure: PCI: hv: Do not sleep in compose_msi_msg()

[Joshua R. Poulson]

Public bug reported:

Part of the transparent SR-IOV series appears to be missing from 4.13.

PCI: hv: Do not sleep in compose_msi_msg()

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80bfeeb9dd6b54ac108c884c792f0fc7d4912bee

The setup of MSI with Hyper-V host was sleeping with locks held.  This
error is reported when doing SR-IOV hotplug with kernel built with lockdep:

BUG: sleeping function called from invalid context at 
kernel/sched/completion.c:93
in_atomic(): 1, irqs_disabled(): 1, pid: 1405, name: ip
3 locks held by ip/1405:
   #0:  (rtnl_mutex){+.+.+.}, at: [] rtnetlink_rcv+0x1b/0x40
   #1:  (>request_mutex){+.+...}, at: [] 
__setup_irq+0xb3/0x720
   #2:  (_desc_lock_class){-.-...}, at: [] 
__setup_irq+0xe5/0x720
   irq event stamp: 3476
   hardirqs last  enabled at (3475): [] 
get_page_from_freelist+0x225/0xc90
   hardirqs last disabled at (3476): [] 
_raw_spin_lock_irqsave+0x27/0x90
   softirqs last  enabled at (2446): [] 
ixgbevf_configure+0x380/0x7c0 [ixgbevf]
   softirqs last disabled at (2444): [] 
ixgbevf_configure+0x35d/0x7c0 [ixgbevf]

The workaround is to poll for host response instead of blocking on
completion.

Please add this to linux-azure on 4.13.

** Affects: linux-azure (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Changed in: linux-azure (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/1747543

Title:
  [Hyper-V] linux-azure: PCI: hv: Do not sleep in compose_msi_msg()

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

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

[Bug 159356] Re: System freeze on high memory usage

[Iiridayn]

** Also affects: linux (Arch Linux)
   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/159356

Title:
  System freeze on high memory usage

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

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

[Bug 1747507] Re: starting VMs causing retpoline4 to reboot

[Bryan Quigley]

Might be related, might not.  This is displayed before the reboot.

host doesn't support requested feature: CPUID.01H:ECX.vmx [bit 5]

I did downgrade from the testing qemu packages, maybe that changed my
VMs, but that still shouldn't cause a host reboot (or kvm with no
options).

** Attachment added: "Warning.png"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747507/+attachment/5049442/+files/Warning.png

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

Title:
  starting VMs causing retpoline4 to reboot

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

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

[Bug 1733276] Re: Cannot resize partitions on NVME devices due to bad device name parsing

[Eric Desrochers]

attachment: console_log.png

** Attachment added: "console_log.png"
   
https://bugs.launchpad.net/ubuntu/artful/+source/partman-partitioning/+bug/1733276/+attachment/5049440/+files/console_log.png

** Description changed:

  [Impact]
  
  It is not possible to resize NVME partitions in the Ubiquity installer.
  NVME devices have an unusual device format, specifically e.g. /dev/nvme0n1p1 
that has two 'sections' that potentially look like partitions.
  
  Based on the error message, it seems that this device name is being
  parsed incorrectly and it attempts to use the device path /dev/nvme0n1
  instead of /dev/nvme0n1p1
  
  ** See attachment (screenshot) took in action :
  - resize.png
  - resize_impossible.png
+ - console_log.png
  
  [Test Case]
  
  To test component(s) in -proposed
  
  https://wiki.ubuntu.com/Testing/EnableProposed
  [Section: Installation testing using -proposed]
  
  In order to install successfully from these images, you will normally
  need to tell the installer to fetch its own components from -proposed as
  well, which is not the default. To do this, add the following boot
  parameter:
  
  apt-setup/proposed=true
  
  
  You can test this using qemu and a virtual NVME device. If you toggle
  the same device/partition between a virtual SCSI/IDE and an NVME device
  - the issue appears and disappears.
  
  Commands you can use to replicate the issue - unpack netboot.tar.gz into
  the local directory and then
  
  dd if=/dev/zero of=nvme.disk bs=1M count=16384
  
  NVME:
  qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw -device 
nvme,drive=drv0,serial=foo -enable-kvm -smp 2 -m 1024 -kernel 
xenial/ubuntu-installer/amd64/linux -initrd 
xenial/ubuntu-installer/amd64/initrd.gz
  
  SCSI:
  qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drv0,id=virtio-disk0,bootindex=1
 -enable-kvm -smp 2 -m 1024 -kernel ubuntu-installer/amd64/linux -initrd 
ubuntu-installer/amd64/initrd.gz
  
  [Regression Potential]
  
   * Low risk of regression, with this patch, partman, will be more robust and 
align with what disk_name() in the kernel does 
(linux.git/tree/block/partition-generic.c). It is sufficient to check
  whether the last character is a digit.
  
  * The patch may also fixes (or at least prevent for the future) other
  potential similar devices issue and not explicitly fixing and/or benefit
  NVMe device types.
  
  [Other Info]
  
  * Debian upstream bug :
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820818
  
  * Debian upstream fix :
  
https://anonscm.debian.org/cgit/d-i/partman-partitioning.git/commit/?id=01087125e07a7b22da589e8116f9ef7a26275006
  
  * Commit [01087125]
  Make get_real_device() both simpler and more generic (See: #820818).
  Looking at the implementation of the disk_name() function in the kernel
  (linux.git/tree/block/partition-generic.c), it is sufficient to check
  whether the last character is a digit.
  
  * $ git describe --contains 01087125e07a7b22da589e8116f9ef7a26275006
  116~2
  
  * $ rmadison partman-partitioning
   partman-partitioning | 85ubuntu2| precise/main/debian-installer
   partman-partitioning | 99ubuntu1| trusty/main/debian-installer
   partman-partitioning | 110ubuntu4.1 | xenial-updates/main/debian-installer
   partman-partitioning | 114ubuntu2   | zesty/main/debian-installer
   partman-partitioning | 114ubuntu2   | artful/main/debian-installer
   partman-partitioning | 120ubuntu1   | bionic/main/debian-installer
  
  [Original Description]
  
  It is not possible to resize NVME partitions in the Ubiquity installer.
  This appears to affect multiple filesystem types including NTFS and
  ext4.
  
  NVME devices have an unusual device format, specifically e.g.
  /dev/nvme0n1p1 that has two 'sections' that potentially look like
  partitions.
  
  Based on the error message, it seems that this device name is being
  parsed incorrectly and it attempts to use the device path /dev/nvme0n1
  instead of /dev/nvme0n1p1
  
  You can test this using qemu and a virtual NVME device.  If you toggle
  the same device/partition between a virtual SCSI/IDE and an NVME device
  - the issue appears and disappears.
  
  Commands you can use to replicate the issue - unpack netboot.tar.gz into
  the local directory and then
  
  dd if=/dev/zero of=nvme.disk bs=1M count=16384
  
  NVME:
  qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw -device 
nvme,drive=drv0,serial=foo -enable-kvm -smp 2 -m 1024 -kernel 
xenial/ubuntu-installer/amd64/linux -initrd 
xenial/ubuntu-installer/amd64/initrd.gz
  
  SCSI:
  qemu-system-x86_64 -drive file=nvme.disk,if=none,id=drv0,format=raw  -device 
virtio-blk-pci,scsi=off,bus=pci.0,addr=0x7,drive=drv0,id=virtio-disk0,bootindex=1
  -enable-kvm -smp 2 -m 1024 -kernel ubuntu-installer/amd64/linux -initrd 
ubuntu-installer/amd64/initrd.gz

-- 
You received this bug 

[Bug 1746126] Re: [MIR] mtd-utils (WIP)

[Balint Reczey]

** Description changed:

  [Availability]
  Currently in universe
  
  [Rationale]
  mtd-utils is a new dependency of flash-kernel (main)
  
  [Security]
  There are no outstanding nor historical security issues.
  
  [Quality Assurance]
  
  There are a low number of outstanding bugs against the package and is well 
maintained.
  https://bugs.launchpad.net/ubuntu/+source/mtd-utils (1)
  https://tracker.debian.org/pkg/mtd-utils (10)
  
  There is one important bug in Debian but it does not affect Ubuntu since 
Ubuntu supports only the Linux kernel:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745187
  mtd-utils: Please use arch:linux-any
  
  The outstanding bugs don't affect flash-kernel's mtd-utils usage.
  
  The package does deal with exotic hardware, too, if rare SoC variants
  count as such.
  
- ! Test suite is not enabled yet, it is in progress.
+ The tests are run in Ubuntu builds.
+ 
+ I forwarded the patch fixing the tests upstream:
+ http://lists.infradead.org/pipermail/linux-mtd/2018-February/079074.html
  
  [Dependencies]
  
  All in main (libc6 (>= 2.14), liblzo2-2, libuuid1 (>= 2.16), zlib1g (>=
  1:1.1.4))
  
  [Standards Compliance]
  
  Debhelper compat version is 9.
  
  Generally FHS compliant, with the exception explained here:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=589228
  mtd-utils: possible FHS violation, as mkfs.jffs2 and mkfs.ubifs are not in 
/sbin
  
  There are minor Debian Policy compliance issues reported by Lintian:
  https://lintian.debian.org/maintainer/riku.voi...@linaro.org.html#mtd-utils
  It lists many missing man pages and 
priority-extra-is-replaced-by-priority-optional
  
  [Maintenance]
  
- Packaging is minimal, most likely it will be maintained in syncs from Debian.
+ Packaging is minimal, most likely it will be maintained in syncs from
+ Debian after the next upstream release.
+ 
  The package will be maintained by the Foundations Team.
  
  [Background]
  
  Description: Memory Technology Device Utilities
-  Utilities for manipulating memory technology devices, such as flash
-  memory, Disk-On-Chip, or ROM.  Includes mkfs.jffs2, a tool to create
-  JFFS2 (journaling flash file system) filesystems.
+  Utilities for manipulating memory technology devices, such as flash
+  memory, Disk-On-Chip, or ROM.  Includes mkfs.jffs2, a tool to create
+  JFFS2 (journaling flash file system) filesystems.

** Summary changed:

- [MIR] mtd-utils (WIP)
+ [MIR] mtd-utils

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

Title:
  [MIR] mtd-utils

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mtd-utils/+bug/1746126/+subscriptions

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

[Bug 1426981] Re: crash on reinstallation

[DexterF]

Everything is fine with disk space. 4GB machine with 250 SSD and I get the 
exact same thing.
What should be mentioned is that I wanted to install over an existing partition 
scheme

Samsung 840 EVO 250GB SSD sata
Once formated with opensuse leap 42.3 installer
509MB sda1 boot format
ext part
40GB sda5 root format
160GB sda6 home keep
8GB swap 

but the installer miscalculates boot to be 533MB. it then gets stuck
with the error the OP mentioned. I retried settign size to a sfea value
at 488, I recreated this partition with gparted beforehand, always stuck
at creating /boot on sda1.

So there is your bug, and it is valid.

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

Title:
  crash on reinstallation

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

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

[Bug 1257547] Re: [bcm5974] Apple touchpad fails to respond, dmesg contains multiple mesages of form: bcm5974: bad trackpad package, length: 8

[Christopher M. Penalver]

Stefan Bethge, the issue you are reporting is an upstream one. Could you
please report this problem following the instructions verbatim at
https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing
list (TO Henrik Rydberg, and Dmitry Torokhov CC linux-input)?

Please provide a direct URL to your post to the mailing list when it
becomes available so that it may be tracked.

Thank you for your help.

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

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

Title:
  [bcm5974] Apple touchpad fails to respond, dmesg contains multiple
  mesages of form: bcm5974: bad trackpad package, length: 8

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

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

[Bug 799605] Re: pam-auth-update creates a 'common-account' that fails with cached logins

[Reinhard Mayr]

This helped me on 16.04: http://kennywest.blogspot.co.at/2007/04
/pamccreds-howto.html

>> QUOTE
Update /etc/pam.d/common-auth:

auth sufficient pam_unix.so
auth [authinfo_unavail=ignore success=1 default=die] pam_ldap.so use_first_pass
auth [default=done] pam_ccreds.so action=validate use_first_pass
auth [default=done] pam_ccreds.so action=store use_first_pass
auth [default=done] pam_ccreds.so action=update use_first_pass

Update /etc/pam.d/common-account:

account sufficient pam_unix.so nullok_secure
account sufficient pam_ldap.so
account required pam_permit.so
<< QUOTE

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

Title:
  pam-auth-update creates a 'common-account' that fails with cached
  logins

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpam-ccreds/+bug/799605/+subscriptions

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

[Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

[Christopher M. Penalver]

** Attachment removed: ""nouveau" related entries in "kern.log""
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1649566/+attachment/5049298/+files/nouveau.log

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

Title:
  [GeForce 7025 / nForce 630a] System freeze

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

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

[Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[ryan eckenrode]

I can confirm this fix worked for me.

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/laptop-mode-tools/+bug/1726930/+subscriptions

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

[Bug 1743427] Re: Black screen with iMac 2011 and ATI Radeon 6970M

[Christopher M. Penalver]

Hans Matros, to see if this is resolved upstream, could you use the
latest kernel 4.15.1 without the WORKAROUND?

If it has boot issues, please provide details via
https://wiki.ubuntu.com/DebuggingKernelBoot .

Also, when providing dmesg, please don't grep/cut/snip logs. Post them
in full.

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

Title:
  Black screen with iMac 2011 and ATI Radeon 6970M

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

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

[Bug 1638525] Re: Needs merge of ubuntu delta

[Dimitri John Ledkov]

Transition went fine in Debian, and we are doing it too. So, closing
this bug and removing the tag.

** Tags removed: block-proposed

** Changed in: openssl1.0 (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: openssl1.0 (Ubuntu Zesty)
   Status: Confirmed => Fix Released

** No longer affects: openssl1.0 (Ubuntu Zesty)

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

Title:
  Needs merge of ubuntu delta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl1.0/+bug/1638525/+subscriptions

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

[Bug 1733032] Re: touchpad disable while typing, disable tap-to-click don't work in 17.10

[Jonathan Kamens]

Logging into Ubuntu (i.e., not "Ubuntu on Xorg"), the "Disable While
Typing" Touchpad setting in gnome-tweak-tool now appears to work.
Furthermore, tapping to click does _not_ work, i.e., the behavior I want
is present by default as far as I can tell. In fact, I can't figure out
any way to cause tapping the touchpad to generate a click. So either the
behavior has changed in an update since I reported this bug, or I was
using Xorg but thought I was using Wayland.

Logging into Ubuntu on Xorg, without anything special in any of my X
server config files, the "Disable While Typing" setting in gnome-tweak-
tool doesn't do anything, and tap to click is enabled and there's no way
I can find to disable it. So that appears to be a bug in GNOME, not a
bug in libinput. There should be a way to disable tap to click, and the
"Disable While Typing" setting should be obeyed. If it's not, then I
believe that means GNOME isn't populating that setting through to the X
server the way it needs to be, which doesn't sound like a libinput bug.

Logging into Ubuntu on Xorg, these lines added to the "libinput touchpad
catchall" section of /usr/share/X11/xorg.conf.d/40-libinput.conf appear
to have no effect, even though Xorg.0.log confirms that section is being
applied:

Option "Tapping" "false"
Option "DisableWhileTyping" "true"
Option "PalmDetection" "true"

Perhaps this is a libinput bug, or perhaps the synaptics sections that
are being applied to the device after the libinput sections are
overriding the libinput settings?

Again logging into Ubuntu on Xorg, if I add this to my X config then tap
to click is gone and it seems like there is _some_ protection against
brushing against the trackpad, although there still isn't full disable
by typing:

Section "InputClass"
  Identifier "disable touchpad tap to click, enable palm detection"
  Driver "synaptics"
  MatchIsTouchpad "on"
  MatchDevicePath "/dev/input/event*"
  Option "MaxTapTime" "0"
  Option "PalmDetect" "on"
EndSection

So, the potential issues that _I_ see here are that the Disable While
Typing setting does not work in "Ubuntu on Xorg", and that the libinput
options I'm configuring into my X server don't appear to take effect.
Should I indeed open a libinput bug about that, or re-open the bug I
opened and closed but clarify in the re-opened bug that it only applies
to Xorg, not to Wayland?

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

Title:
  touchpad disable while typing, disable tap-to-click don't work in
  17.10

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

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

[Bug 1743427] Re: Black screen with iMac 2011 and ATI Radeon 6970M

[Christopher M. Penalver]

** Description changed:

- Dear community!
+ Using Ubuntu 16.04 through 17.10, when I boot the screen is black, ping
+ and ssh to the host does not work, and the fan is running. Same problem
+ with kernel 4.14 and 4.15RC7.
  
- I have installed Ubuntu 17.10 (also tried 17.04 and 16.04), and the
- system gets a black screen on boot with all tested Ubuntu versions. Also
- ping and ssh to the host does not work. The fan's are running, the
- screen is black and nothing more.
+ WORKAROUND: Use kernel parameter:
+ nomodeset
  
- When i insert in Grub nomodeset, the system can boot.
- 
- I have also tested Kernel 4.14 and 4.15RC7.
- 
- Hardware Information:
- 
- 00:02.0 Display controller: Intel Corporation 2nd Generation Core
- Processor Family Integrated Graphics Controller (rev 09)
- 
- 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
- [AMD/ATI] Blackcomb [Radeon HD 6970M/6990M]
- 
- 
- Thanks for help or any hint.
- 
- Best regards,
- 
- Hans
- --- 
+ ---
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  christian   1756 F pulseaudio
-  /dev/snd/controlC1:  christian   1756 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  christian   1756 F pulseaudio
+  /dev/snd/controlC1:  christian   1756 F pulseaudio
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=/dev/mapper/storage-swap
  InstallationDate: Installed on 2018-01-15 (0 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 
(20180108.1)
  MachineType: Apple Inc. iMac12,2
  Package: linux (not installed)
  ProcEnviron:
-  LANGUAGE=
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-25-generic.efi.signed 
root=/dev/mapper/storage-root ro rootflags=subvol=@ nomodeset
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  PulseList:
-  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
-  No PulseAudio daemon running, or not running as session daemon.
+  Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
+  No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-4.13.0-25-generic N/A
-  linux-backports-modules-4.13.0-25-generic  N/A
-  linux-firmware 1.169.1
+  linux-restricted-modules-4.13.0-25-generic N/A
+  linux-backports-modules-4.13.0-25-generic  N/A
+  linux-firmware 1.169.1
  Tags:  artful
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
-  
+ 
  _MarkForUpload: True
  dmi.bios.date: 08/08/17
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: IM121.88Z.004D.B00.1708080012
  dmi.board.name: Mac-942B59F58194171B
  dmi.board.vendor: Apple Inc.
  dmi.board.version: iMac12,2
  dmi.chassis.type: 13
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-942B59F58194171B
  dmi.modalias: 
dmi:bvnAppleInc.:bvrIM121.88Z.004D.B00.1708080012:bd08/08/17:svnAppleInc.:pniMac12,2:pvr1.0:rvnAppleInc.:rnMac-942B59F58194171B:rvriMac12,2:cvnAppleInc.:ct13:cvrMac-942B59F58194171B:
  dmi.product.family: iMac
  dmi.product.name: iMac12,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

** Tags added: kernel-bug-exists-upstream-4.15-rc7 xenial zesty

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

Title:
  Black screen with iMac 2011 and ATI Radeon 6970M

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

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

[Bug 1746357] Re: Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

[Christopher M. Penalver]

Bib, the issue you are reporting is an upstream one. Could you please report 
this to them via https://bugs.freedesktop.org/enter_bug.cgi?product=DRI :
Component: DRM/Radeon

Please post a link to the upstream report here so that it may be
tracked.

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

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

Title:
  Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

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

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

Re: [Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

[David JM Emmett]

Given that the c5 instances are Skylake, and I read somewhere that
there’s some special edge-case for Skylake and later CPUs, is this
reproducible on proper hardware, or is it limited to KVM (prior to AWS’s
c5s, the hypervisors were xen).

I’ve got a couple of Skylake machines available, and will install sssd
and see what happens.

Cheers,
David

> On 5 Feb 2018, at 21:59, Paul Friel <1746...@bugs.launchpad.net> wrote:
> 
> @jsalisbury: I installed that kernel and rebooted using a c5.xl, it
> froze.  I booted into a c4.xl and it booted fine, disabled the apparmor
> service and rebooted into a c5.xl and it booted fine.  Re-enabled
> apparmor and rebooted into the c5.xl again and it froze on boot.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1746806
> 
> Title:
>  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU
> 
> Status in cloud-images:
>  New
> Status in linux package in Ubuntu:
>  Confirmed
> Status in linux-aws package in Ubuntu:
>  Confirmed
> Status in sssd package in Ubuntu:
>  Confirmed
> 
> Bug description:
>  After upgrading to the Ubuntu EC2 AMI from 20180126 (specifically
>  ami-79873901 in us-west-2) we have seen sssd hard locking c5 and m5
>  EC2 instances after starting the service and CPU goes to 100%.
> 
>  We do not experience this issue with t2 or c4 instance types and we do
>  not see this issue on any instance types using Ubuntu Cloud images
>  from 20180109 or before. I have verified that this is kernel related
>  as I booted an image that we created using the Ubuntu cloud image from
>  20180109 which works fine on a c5. I then did a "apt update && apt
>  install --only-upgrade linux-aws && systemctl disable sssd", rebooted
>  the server, verified I was on the new kernel and started sssd with
>  "systemctl start sssd" and the EC2 instance froze and Cloudwatch CPU
>  usage for that instance went to 100%.
> 
>  I haven't been able to find much in the syslog, kern.log, journalctl
>  logs, etc. The only thing I have been able to find is that when this
>  happens I tend to see "^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@" in
>  the syslog and sssd log files.  I have attached several log files and
>  the output of a "apport-bug /usr/sbin/sssd". Let me know if you need
>  anything else to help track this down.
> 
>  Thanks,
>  Paul
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-images/+bug/1746806/+subscriptions

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

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

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

[Bug 1231364] Re: firewalls not shown in network topology

[Akihiro Motoki]

*** This bug is a duplicate of bug 1231330 ***
https://bugs.launchpad.net/bugs/1231330

** This bug has been marked a duplicate of bug 1231330
   pluggable mechanism of network topology to support more types of resources

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

Title:
  firewalls not shown in network topology

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron-fwaas-dashboard/+bug/1231364/+subscriptions

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

[Bug 1257547] Re: [bcm5974] Apple touchpad fails to respond, dmesg contains multiple mesages of form: bcm5974: bad trackpad package, length: 8

[Stefan Bethge]

The issue is still happening with upstream kernel, tags added.

** Tags added: kernel-bug-exists-upstream-4.15.1

** Tags added: kernel-bug-exists-upstream

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

Title:
  [bcm5974] Apple touchpad fails to respond, dmesg contains multiple
  mesages of form: bcm5974: bad trackpad package, length: 8

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

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

[Bug 1746357] Re: Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

[Christopher M. Penalver]

** Tags removed: kernel-bug-exists-upstream-4.15
** Tags added: kernel-bug-exists-upstream-4.15.1

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

Title:
  Boot loop MSI A88XM35 AMD APU A8-5600K (Aruba HD7560D)

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

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

[Bug 1721355] Re: gcc -v gives strange output for OFFLOAD_TARGET_DEFAULT

[Laurent Bonnaud]

valgrind finds some uses of uninitialised memory:

$ valgrind gcc -v
==496== Memcheck, a memory error detector
==496== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==496== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
==496== Command: gcc -v
==496==
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
==496== Conditional jump or move depends on uninitialised value(s)
==496==at 0x4C32D48: __strlen_sse2 (vg_replace_strmem.c:460)
==496==by 0x4E918C4: vfprintf (vfprintf.c:1643)
==496==by 0x4E927D5: buffered_vfprintf (vfprintf.c:2330)
==496==by 0x4E8FAA5: vfprintf (vfprintf.c:1301)
==496==by 0x4F61295: __vfprintf_chk (vfprintf_chk.c:33)
==496==by 0x428CCD: vfprintf (stdio2.h:127)
==496==by 0x428CCD: fnotice(_IO_FILE*, char const*, ...) (diagnostic.c:1427)
==496==by 0x407F06: env_manager::xput(char const*) (gcc.c:119)
==496==by 0x40A604: xputenv (gcc.c:2700)
==496==by 0x40A604: driver::maybe_putenv_OFFLOAD_TARGETS() const 
(gcc.c:7764)
==496==by 0x403A5C: driver::main(int, char**) (gcc.c:7295)
==496==by 0x403D53: main (gcc-main.c:46)
==496==
OFFLOAD_TARGET_DEFAULT=1
==496== Conditional jump or move depends on uninitialised value(s)
==496==at 0x4C37CE0: putenv (vg_replace_strmem.c:1996)
==496==by 0x40A604: xputenv (gcc.c:2700)
==496==by 0x40A604: driver::maybe_putenv_OFFLOAD_TARGETS() const 
(gcc.c:7764)
==496==by 0x403A5C: driver::main(int, char**) (gcc.c:7295)
==496==by 0x403D53: main (gcc-main.c:46)
==496==
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
7.2.0-8ubuntu3.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-7 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu 
--enable-libstdcxx-debug --enable-libstdcxx-time=yes 
--with-default-libstdcxx-abi=new --enable-gnu-unique-object 
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie 
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto 
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3.1)
==496==
==496== HEAP SUMMARY:
==496== in use at exit: 180,029 bytes in 57 blocks
==496==   total heap usage: 201 allocs, 144 frees, 202,427 bytes allocated
==496==
==496== LEAK SUMMARY:
==496==definitely lost: 4,272 bytes in 7 blocks
==496==indirectly lost: 0 bytes in 0 blocks
==496==  possibly lost: 0 bytes in 0 blocks
==496==still reachable: 175,757 bytes in 50 blocks
==496== suppressed: 0 bytes in 0 blocks
==496== Rerun with --leak-check=full to see details of leaked memory
==496==
==496== For counts of detected and suppressed errors, rerun with: -v
==496== Use --track-origins=yes to see where uninitialised values come from
==496== ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 0 from 0)

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

Title:
  gcc -v gives strange output for OFFLOAD_TARGET_DEFAULT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-7/+bug/1721355/+subscriptions

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

[Bug 1721355] Re: gcc -v gives strange output for OFFLOAD_TARGET_DEFAULT

[Laurent Bonnaud]

I found how to reproduce this:

MALLOC_PERTURB_=117 gcc -v

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

Title:
  gcc -v gives strange output for OFFLOAD_TARGET_DEFAULT

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-7/+bug/1721355/+subscriptions

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

[Bug 1747535] [NEW] php-horde-crypt unit tests don't work with gpg2

[Nish Aravamudan]

Public bug reported:

Waiting on upstream confirmation: https://bugs.horde.org/ticket/14780

** Affects: php-horde-crypt (Ubuntu)
 Importance: Undecided
 Assignee: Nish Aravamudan (nacc)
 Status: New

** Changed in: php-horde-crypt (Ubuntu)
 Assignee: (unassigned) => Nish Aravamudan (nacc)

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

Title:
  php-horde-crypt unit tests don't work with gpg2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-horde-crypt/+bug/1747535/+subscriptions

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

[Bug 1747426] Re: Vagrant <2.x can no longer fetch box metadata from Hashicorp

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~daniel-thewatkins/ubuntu/+source/vagrant/+git/vagrant/+merge/337189

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

Title:
  Vagrant <2.x can no longer fetch box metadata from Hashicorp

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

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

[Bug 1747507] Re: starting VMs causing retpoline4 to reboot

[Bryan Quigley]

** Description changed:

  Using 4.13.0-33.36~retpoline4  kernel test kernel from ppa
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/.
  
  CPU: AMD Ryzen 7 1700 Eight-Core Processor
  Ubuntu: 17.10.
  
  Steps to reproduce (has occurred both times I tried it):
- 1. Run virsh start  (or start VM from GUI)
- Machine reboots 
+ 1.  Just run kvm with no options (or virsh start <> or start VM from GUI)
+ Machine reboots
  
- Going back to 4.13.0-32 has virsh working again
+ Going back to 4.13.0-32 has virsh working again. qemu-system-x86_64
+ command works fine.

** Description changed:

  Using 4.13.0-33.36~retpoline4  kernel test kernel from ppa
  https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/spectre/.
  
  CPU: AMD Ryzen 7 1700 Eight-Core Processor
  Ubuntu: 17.10.
  
  Steps to reproduce (has occurred both times I tried it):
  1.  Just run kvm with no options (or virsh start <> or start VM from GUI)
  Machine reboots
  
  Going back to 4.13.0-32 has virsh working again. qemu-system-x86_64
- command works fine.
+ command works fine unless you use the enable kvm command.

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

Title:
  starting VMs causing retpoline4 to reboot

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

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

[Bug 1747333] Re: apparmor rules deny lease backup

[Seth Arnold]

These are not AppArmor messages. AppArmor messages clearly say
apparmor="DENIED" or apparmor="ALLOWED" or similar.

Audit message 1702 is generated when an application trips a link restriction 
denial:
https://github.com/torvalds/linux/blob/master/kernel/audit.c#L2254

The "linkat" version of the message comes from:
https://github.com/torvalds/linux/blob/master/fs/namei.c#L968

If you want to enable the unsafe hardlink behaviour you can set a sysctl
to do so. (This is a homework problem left for the reader.)

Audit message 1302 reports a filename:
https://github.com/torvalds/linux/blob/master/include/uapi/linux/audit.h#L89

Since this is the next audit record after the 1702 message, I believe
this is just reporting *which* file was involved in the previous unsafe
link behaviour.

Thanks

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

Title:
  apparmor rules deny lease backup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1747333/+subscriptions

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

[Bug 1733032] Re: touchpad disable while typing, disable tap-to-click don't work in 17.10

[Jonathan Kamens]

Actually, I think opening a libinput bug is premature, for reasons I
will explain below. I'm going to close that other bug until I can
quantify better what is going on.

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

Title:
  touchpad disable while typing, disable tap-to-click don't work in
  17.10

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

[Steve Langasek]

On Mon, Feb 05, 2018 at 09:27:15PM -, Andres Rodriguez wrote:
> MAAS already has a mechanism to collapse retries into the initial request.

Are we certain that this is working correctly?  If so, why are packet
captures showing that MAAS is sending stacked tftp OACK responses, 1:1 for
the duplicate incoming requests?

It's clear to me that MAAS's handling at the wire level is incorrect - 10
retries of the same tftp request should result in a single OACK, not 10 of
them (unless MAAS receives a retry *after* it has sent its OACK).  I don't
know if that also means that MAAS is inefficiently translating these into
database requests on the backend.  It had been suggested in this bug log and
on IRC that MAAS *was* sending duplicate db requests for each of these
packets; OTOH the timing of the stacked responses shows no latency in
between them that would imply additional db round-trips.

I think someone needs to directly inspect the behavior of a running MAAS
server in this scenario to be sure.

> In this case, it is the rack that grabs the requests and makes a request to
> the region. If retries come within the time that the rack is waiting for a
> response from the region, these request get "ignored" and the Rack will
> only answer the first request.

That is absolutely contradicted by the packet captures.  The rack does not
ignore the additional requests, it answers *ALL* of the requests.  It's only
the *client* that consolidates the duplicate responses from MAAS.  (And
then, because of a grub bug higher up the stack, re-requests the same file
that it has already received.)

-- 
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 1543899] Re: update-apt-xapian-index crashed with UnicodeDecodeError in record(): 'utf-8' codec can't decode byte 0xe3 in position 349: invalid continuation byte

[QkiZ]

Did you try to install a version from Debian?

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

Title:
  update-apt-xapian-index crashed with UnicodeDecodeError in record():
  'utf-8' codec can't decode byte 0xe3 in position 349: invalid
  continuation byte

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

[Andres Rodriguez]

@Jason,

The pcap exactly shows the behavior I was hoping to see, which is grub
tries to get X config first, and since it didn't get a response, it moves
on and tries to get Y config.

On Mon, Feb 5, 2018 at 4:45 PM, Jason Hobbs 
wrote:

> On Mon, Feb 5, 2018 at 3:27 PM, Andres Rodriguez
>  wrote:
> > @Steve,
> >
> > MAAS already has a mechanism to collapse retries into the initial
> request.
> > In this case, it is the rack that grabs the requests and makes a request
> to
> > the region. If retries come within the time that the rack is waiting for
> a
> > response from the region, these request get "ignored" and the Rack will
> > only answer the first request. This is what the logs show after testing
> > with fixed grub, where grub makes multiple requests and MAAS answers
> > seconds after does requests, but only answers once. This is because the
> > requests were collapsed on the maas side.
> >
> > If, however, the retries come in after the region has answered the rack,
> > they these requests will be served.
>
> This is not true.  MAAS is responding to every single 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/spearow-fall-back-to-default-amd64.pcap
>
> Jason
>
> >
> > On Mon, Feb 5, 2018 at 2:34 PM, Steve Langasek <
> steve.langa...@canonical.com
> >> wrote:
> >
> >> Jason's feedback was that, after making the changes to the storage
> >> configuration of his environment, deploying the test grubx64.efi doesn't
> >> have any effect on the MAAS server's response time to tftp requests.  So
> >> at this point it's not at all clear that the grub change, while correct,
> >> helps with this high-level symptom.
> >>
> >> It has also been suggested that each udp retry is generating a separate
> >> database query from MAAS.  That is absolutely a MAAS bug if true, and
> >> not something that can or should be fixed in GRUB.
> >>
> >> ** Changed in: grub2 (Ubuntu)
> >>Importance: Critical => Medium
> >>
> >> --
> >> 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
> >>
> >> To manage notifications about this bug go to:
> >> https://bugs.launchpad.net/maas/+bug/1743249/+subscriptions
> >>
> >> Launchpad-Notification-Type: bug
> >> Launchpad-Bug: product=maas; milestone=2.4.x; status=Incomplete;
> >> importance=Undecided; assignee=None;
> >> Launchpad-Bug: distribution=ubuntu; sourcepackage=grub2; component=main;
> >> status=In Progress; importance=Medium; assignee=mathieu...@gmail.com;
> >> Launchpad-Bug-Tags: cdo-qa cdo-qa-blocker foundations-engine patch
> >> Launchpad-Bug-Information-Type: Public
> >> Launchpad-Bug-Private: no
> >> Launchpad-Bug-Security-Vulnerability: no
> >> Launchpad-Bug-Commenters: andreserl blake-rouse cgregan jason-hobbs
> vorlon
> >> Launchpad-Bug-Reporter: Jason Hobbs (jason-hobbs)
> >> Launchpad-Bug-Modifier: Steve Langasek (vorlon)
> >> Launchpad-Message-Rationale: Subscriber (MAAS)
> >> Launchpad-Message-For: andreserl
> >>
> >
> >
> > --
> > Andres Rodriguez (RoAkSoAx)
> > Ubuntu Server Developer
> > MSc. Telecom & Networking
> > Systems Engineer
> >
> > --
> > 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:
> >   In Progress
> >
> > 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-
> >   

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

[Andres Rodriguez]

I think there's a misunderstanding on how the network boot process happens:
Let's look at pxe linux first. Pxe linux does this:

1. tries UUID first # if no answer, it moves on
2. Tries mac # if no answer, it moves on
3. tries full IP address # if no answer, it moves on
4. tries partial IP address # if no answer, it moves on
5. does 4
6. does 4
[...]
7. boots default.

This can be seen in here:

/mybootdir/pxelinux.cfg/b8945908-d6a6-41a9-611d-74a6ab80b83d
/mybootdir/pxelinux.cfg/01-88-99-aa-bb-cc-dd
/mybootdir/pxelinux.cfg/C0A8025B
/mybootdir/pxelinux.cfg/C0A8025
/mybootdir/pxelinux.cfg/C0A802
/mybootdir/pxelinux.cfg/C0A80
/mybootdir/pxelinux.cfg/C0A8
/mybootdir/pxelinux.cfg/C0A
/mybootdir/pxelinux.cfg/C0
/mybootdir/pxelinux.cfg/C
/mybootdir/pxelinux.cfg/default


That said, in the case of grub, this behavior is similar. You have
described this behavior in comment #16. So what is it that's happening:

1. grub is trying grub.cfg- address multiple times, but since it
doesn't get a response, it gives it.
2. Once it gives up, grub.cfg-default-amd64 is tried instead.

That said, the requests are handled completely different. The -
requests actually accesses the *node* object in the database  by searching
it with the mac address where the request is made. With this node object,
we generate the config file.

In comparison, the -default-amd64 does *not* access the node object. It
just access two config settings and the db query is *much* cheaper. Also,
we have to keep in mind that after grub has done many retries, this returns
rather fast in comparison because it is not only cheaper, but at that point
MAAS may be with way less load of queued DB requests. Either way, grub
giving up means that it wont expect for the initial request, but it will
expect a new response for the new file it asked for.

That said, this is working *exactly* as expected, because this effectively
tells grub "if config for your MAC address was not returned, you can safely
assume you are an unknown machine to MAAS", hence grub requests a different
config file to start the enlistment process.

So this is *not* a race condition in MAAS. This is working as designed and
is expected. The problem here is that MAAS takes too long to answer the
initial request, which causes grub to timeout and move on to request a
different config file.

On Mon, Feb 5, 2018 at 4:30 PM, Jason Hobbs 
wrote:

> 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
> config only after it receives the tftp request for it is susceptible to
> a race condition where grub times out before MAAS can respond.
>
> That design is not the only possible design.  All the information
> required for the interface specific grub.cfg is available before the
> machine ever powers on, and could be made available on the rack
> controllers at that time too.
>
> Doing so would eliminate that race condition, or at least reduce the
> opportunity greatly, as we see MAAS has no problems immediately
> responding and serving files that it doesn't need to dynamically
> generate at request time.
>
> There is still some question around what in the environment is
> contributing to MAAS not responding faster, and what MAAS is doing while
> it takes 60+ seconds to respond to the request, but that doesn't change
> the fact that the current MAAS design is racy (and that's a bug).
>
> Whatever we change in the environment to reduce the likelihood of
> hitting this issue there doesn't solve the underlying race condition in
> MAAS, and leaves open the possibility of hitting the issue other places
> too.
>
> --
> 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
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1743249/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=maas; milestone=2.4.x; status=New;
> importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=grub2; component=main;
> status=In Progress; importance=Medium; assignee=mathieu...@gmail.com;
> Launchpad-Bug-Tags: cdo-qa cdo-qa-blocker foundations-engine patch
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: andreserl blake-rouse cgregan jason-hobbs vorlon
> Launchpad-Bug-Reporter: Jason Hobbs (jason-hobbs)
> Launchpad-Bug-Modifier: Jason Hobbs (jason-hobbs)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>


-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

-- 
You 

[Bug 1711407] Re: unregister_netdevice: waiting for lo to become free

[Dan Streetman]

Here is another Artful debug kernel, with just slightly more debug info; it may 
help a little while I work on adding more significant debug to track where the 
dst refcnt is getting leaked.  Same PPA:
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1711407

New kernel version is 4.13.0-32.35+hf1711407v20180205b1.

Thanks again for testing these debug kernels!

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

Title:
  unregister_netdevice: waiting for lo to become free

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

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

[Bug 1746806] Re: sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

[Paul Friel]

@jsalisbury: I installed that kernel and rebooted using a c5.xl, it
froze.  I booted into a c4.xl and it booted fine, disabled the apparmor
service and rebooted into a c5.xl and it booted fine.  Re-enabled
apparmor and rebooted into the c5.xl again and it froze on boot.

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

Title:
  sssd appears to crash AWS c5 and m5 instances, cause 100% CPU

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

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

[Bug 1747527] [NEW] High CPU Usage under Plasma

[Aldric Degorre]

Public bug reported:

Since Firefox was updated to version 58.0.1+build1-0ubuntu0.16.04.1
(xenial-updates), I noticed a consistent high CPU usage while Firefox
was running under plasma (both by firefox and plasmashell processes).

After a little inquiry, I tend to believe this is due to a global menu
protocol compatibility issue (I use Plasma 5.12/Neon with global menu
bar enabled).

Facts that led me to that conclusion:
1 - Since Firefox 58 (xenial-updates, obviously patched for Unity global menu), 
Plasma's menu bar now displays a (surprisingly working) menu for Firefox. 
Previous implementations did not work at all (menus would show but not open 
when clicked).
2 - With current Firefox (xenial-updates), either disabling the global menu in 
Plasma, or disabling it in Firefox (setting ui.use_unity_menubar=false in 
about:config), makes CPU usage go down to normal levels.
3 - Before, I had been using Firefox 58beta (from webupd8 repository), which 
did not have this CPU issue... but no global menu either.

Also, FYI:
- A few months ago (until it was fixed), similar behaviour was exhibited by 
other pieces of software such as visual-studio-code and atom editor (both based 
on electron framework). They would hog a full CPU core, as long as they 
attempted to work with Plasma's global menu, but behave normally when global 
menu was disabled (either in plasma or in the incriminated editor).

This latter fact proves it is possible for a piece of software to be
compatible with both global menu implementations. Current status of
Firefox in Ubuntu is actually very encouraging, as the global menu is
now fully working even in Plasma. There only remains this CPU issue.

Although Canonical does not officially endorse any KDE flavor of Ubuntu
anymore, it would be much appreciated by Kubuntu and Neon users if this
remaining little issue could be fixed!

** Affects: firefox (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/1747527

Title:
  High CPU Usage under Plasma

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

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

[Bug 1747170] Re: installer no ipv4 dhcp

[Jb]

this is the contents of /var/log/syslog right after the installer fails
to get an ipv4 address from dhcp

** Attachment added: "syslog.dhcpv4.failed.txt"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1747170/+attachment/5049437/+files/syslog.dhcpv4.failed.txt

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

Title:
  installer no ipv4 dhcp

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

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

[Bug 1733032] Re: touchpad disable while typing, disable tap-to-click don't work in 17.10

[Jonathan Kamens]

Filed https://bugs.freedesktop.org/show_bug.cgi?id=104956.


** Bug watch added: freedesktop.org Bugzilla #104956
   https://bugs.freedesktop.org/show_bug.cgi?id=104956

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

Title:
  touchpad disable while typing, disable tap-to-click don't work in
  17.10

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

[Jason Hobbs]

On Mon, Feb 5, 2018 at 3:27 PM, Andres Rodriguez
 wrote:
> @Jason,
>
>
> On Mon, Feb 5, 2018 at 3:38 PM, Jason Hobbs 
> wrote:
>
>> On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez
>>  wrote:
>> > No new data was provided to mark this New in MAAS:
>> >
>> > 1. Changes to the storage seem to have improved things
>>
>> Yes, it has.  That doesn't change whether or not there is a bug in
>> MAAS.  Can you please address the critical log errors that I mentioned
>> in comment #36?  This seems like enough to establish something is
>> going wrong in MAAS.
>>
>>
> The bugs you have raised in #36 have already been fixed.

Where?

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

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

[Steve Langasek]

On Mon, Feb 05, 2018 at 08:40:56PM -, Jason Hobbs wrote:
> @Steve - I don't think it helps with the problem of MAAS taking a long
> time to respond to the grub.cfg request.  However, it may help with the
> part of this bug where grub is hitting an error and asking for keyboard
> input.  https://imgur.com/a/as8Sx

> Maybe that should be a separate bug?  It seems like grub should never
> ask for user keyboard input on a server.

Perhaps that bug is fixed as a side effect of the grub change.

But what do you think the correct behavior should be when grub cannot find
the file that it needs in order to boot?  Should grub enter a boot loop,
retrying endlessly?  Should it try to halt the system?  Why is either of
these options more correct than putting the machine to a console prompt?

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

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

[Andres Rodriguez]

@Jason,

On Mon, Feb 5, 2018 at 3:38 PM, Jason Hobbs 
wrote:

> On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez
>  wrote:
> > No new data was provided to mark this New in MAAS:
> >
> > 1. Changes to the storage seem to have improved things
>
> Yes, it has.  That doesn't change whether or not there is a bug in
> MAAS.  Can you please address the critical log errors that I mentioned
> in comment #36?  This seems like enough to establish something is
> going wrong in MAAS.
>

The tftp issue shows no evidence this is causing any booting failures. We
have seen this issue before and confirmed that it doesn't cause boot
issues. See [1]. If you want to try it, it is available in
ppa:maas/proposed.

[1].https://bugs.launchpad.net/maas/+bug/1376483

As far as the postgresql logs with "maas@maasdb ERROR: could not serialize
access due to concurrent update" that is  *not* a bug in MAAS or an issue.
That's perfectly normal messages with the isolation level the MAAS DB is
running with. This basically means something else is trying to update the
db while something else is updating it, and MAAS already handles this by
doing retries.


> > 2. No tests have been run with fixed grub that have caused boot
> failures.
>
> The comments from #56 were testing with the fixed grub - sorry if that
> wasn't clear.
>
> > 3. AFAIK, the VM config has not changed to use less CPU to compare
> results and whether this config change causes the bugs in question.
>
> The CPU load data from comments #48 and #50 shows that CPU load is not
> the problem.  The max load average was under 12 on a 20 thread system.
> That means there was lots of free CPU time, and that this workload is
> not CPU bound.
>

CPU load is not CPU utilization. We know that at the time there's 6 other
VM's with 150%+ CPU usage are writing to the disk because they are being
deployed and/or configured (e.g. software installation).  Correct me if
wrong, but this can cause the prioritization of whatever is writing to disk
over anything else, like the MAAS processes access for resources.

That being said, because CPU load doesn't show high we are making the
*assumption* that it is not impacting MAAS, but again, this is an
assumption. Making the requested change for having at least 4 CPUs (ideally
6) would allow us to determining what are the effects and see whether
there's any difference on behavior and would help identify what other
issues.

Without having the comparison then we are making it more difficult to
isolate the problem.

>
> Jason
>
>
> ** Changed in: maas
>Status: Incomplete => New
>
> --
> 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
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1743249/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=maas; milestone=2.4.x; status=New;
> importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=grub2; component=main;
> status=In Progress; importance=Medium; assignee=mathieu...@gmail.com;
> Launchpad-Bug-Tags: cdo-qa cdo-qa-blocker foundations-engine patch
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: andreserl blake-rouse cgregan jason-hobbs vorlon
> Launchpad-Bug-Reporter: Jason Hobbs (jason-hobbs)
> Launchpad-Bug-Modifier: Jason Hobbs (jason-hobbs)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>


-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

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

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

[Jason Hobbs]

On Mon, Feb 5, 2018 at 3:27 PM, Andres Rodriguez
 wrote:
> @Steve,
>
> MAAS already has a mechanism to collapse retries into the initial request.
> In this case, it is the rack that grabs the requests and makes a request to
> the region. If retries come within the time that the rack is waiting for a
> response from the region, these request get "ignored" and the Rack will
> only answer the first request. This is what the logs show after testing
> with fixed grub, where grub makes multiple requests and MAAS answers
> seconds after does requests, but only answers once. This is because the
> requests were collapsed on the maas side.
>
> If, however, the retries come in after the region has answered the rack,
> they these requests will be served.

This is not true.  MAAS is responding to every single 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/spearow-fall-back-to-default-amd64.pcap

Jason

>
> On Mon, Feb 5, 2018 at 2:34 PM, Steve Langasek > wrote:
>
>> Jason's feedback was that, after making the changes to the storage
>> configuration of his environment, deploying the test grubx64.efi doesn't
>> have any effect on the MAAS server's response time to tftp requests.  So
>> at this point it's not at all clear that the grub change, while correct,
>> helps with this high-level symptom.
>>
>> It has also been suggested that each udp retry is generating a separate
>> database query from MAAS.  That is absolutely a MAAS bug if true, and
>> not something that can or should be fixed in GRUB.
>>
>> ** Changed in: grub2 (Ubuntu)
>>Importance: Critical => Medium
>>
>> --
>> 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
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/maas/+bug/1743249/+subscriptions
>>
>> Launchpad-Notification-Type: bug
>> Launchpad-Bug: product=maas; milestone=2.4.x; status=Incomplete;
>> importance=Undecided; assignee=None;
>> Launchpad-Bug: distribution=ubuntu; sourcepackage=grub2; component=main;
>> status=In Progress; importance=Medium; assignee=mathieu...@gmail.com;
>> Launchpad-Bug-Tags: cdo-qa cdo-qa-blocker foundations-engine patch
>> Launchpad-Bug-Information-Type: Public
>> Launchpad-Bug-Private: no
>> Launchpad-Bug-Security-Vulnerability: no
>> Launchpad-Bug-Commenters: andreserl blake-rouse cgregan jason-hobbs vorlon
>> Launchpad-Bug-Reporter: Jason Hobbs (jason-hobbs)
>> Launchpad-Bug-Modifier: Steve Langasek (vorlon)
>> Launchpad-Message-Rationale: Subscriber (MAAS)
>> Launchpad-Message-For: andreserl
>>
>
>
> --
> Andres Rodriguez (RoAkSoAx)
> Ubuntu Server Developer
> MSc. Telecom & Networking
> Systems Engineer
>
> --
> 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:
>   In Progress
>
> 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 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:

[Bug 1610286] Re: [MIR] libapache2-mod-auth-mellon, liblasso3

[Corey Bryant]

Tests have been enabled during build in lasso 2.5.0-5ubuntu1.

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

Title:
  [MIR] libapache2-mod-auth-mellon, liblasso3

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

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

[Bug 1747523] [NEW] support thunderx2 vendor pmu events

[dann frazier]

Public bug reported:

[Impact]
ThunderX2 vendor pmu events are not supported.

[Test Case]
Successful output:
$ sudo perf list | grep thunderx2
thunderx2 imp def:
$

[Regression Risk]
TBD

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

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

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

** Changed in: linux (Ubuntu Bionic)
   Status: New => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  support thunderx2 vendor pmu events

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

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

[Bug 1747276] Re: Firefox/Thunderbird busy wait at startup

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: thunderbird (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/1747276

Title:
  Firefox/Thunderbird busy wait at startup

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

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

[Bug 1747276] Re: Firefox/Thunderbird busy wait at startup

[madbiologist]

** Tags added: bionic

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

Title:
  Firefox/Thunderbird busy wait at startup

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

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

[Bug 1747276] Re: Firefox/Thunderbird busy wait at startup

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: firefox (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/1747276

Title:
  Firefox/Thunderbird busy wait at startup

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

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

[Bug 1498664] Re: Unity control center cannot detect Wacom CTH-661 tablet

[Phsyron]

How is basic device support "low" priority? how is the official work-
around to revert to a 3-year-old kernel version? either you want to
support wacom tablets, at which point this is *high* priority, or you
don't, at which point having "Wacom Tablet" as a first-level option
under system settings is probably not a great idea, considering it has
*literaly* no functionality.

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

Title:
  Unity control center cannot detect Wacom CTH-661 tablet

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

[Andres Rodriguez]

@Jason,


On Mon, Feb 5, 2018 at 3:38 PM, Jason Hobbs 
wrote:

> On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez
>  wrote:
> > No new data was provided to mark this New in MAAS:
> >
> > 1. Changes to the storage seem to have improved things
>
> Yes, it has.  That doesn't change whether or not there is a bug in
> MAAS.  Can you please address the critical log errors that I mentioned
> in comment #36?  This seems like enough to establish something is
> going wrong in MAAS.
>
>
The bugs you have raised in #36 have already been fixed.


> > 2. No tests have been run with fixed grub that have caused boot
> failures.
>
> The comments from #56 were testing with the fixed grub - sorry if that
> wasn't clear.
>
> > 3. AFAIK, the VM config has not changed to use less CPU to compare
> results and whether this config change causes the bugs in question.
>
> The CPU load data from comments #48 and #50 shows that CPU load is not
> the problem.  The max load average was under 12 on a 20 thread system.
> That means there was lots of free CPU time, and that this workload is
> not CPU bound.
>
> Jason
>
>
> ** Changed in: maas
>Status: Incomplete => New
>
> --
> 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
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1743249/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=maas; milestone=2.4.x; status=New;
> importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=grub2; component=main;
> status=In Progress; importance=Medium; assignee=mathieu...@gmail.com;
> Launchpad-Bug-Tags: cdo-qa cdo-qa-blocker foundations-engine patch
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: andreserl blake-rouse cgregan jason-hobbs vorlon
> Launchpad-Bug-Reporter: Jason Hobbs (jason-hobbs)
> Launchpad-Bug-Modifier: Jason Hobbs (jason-hobbs)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>


-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

-- 
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 1743249] Re: Failed Deployment after timeout trying to retrieve grub cfg

[Jason Hobbs]

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
config only after it receives the tftp request for it is susceptible to
a race condition where grub times out before MAAS can respond.

That design is not the only possible design.  All the information
required for the interface specific grub.cfg is available before the
machine ever powers on, and could be made available on the rack
controllers at that time too.

Doing so would eliminate that race condition, or at least reduce the
opportunity greatly, as we see MAAS has no problems immediately
responding and serving files that it doesn't need to dynamically
generate at request time.

There is still some question around what in the environment is
contributing to MAAS not responding faster, and what MAAS is doing while
it takes 60+ seconds to respond to the request, but that doesn't change
the fact that the current MAAS design is racy (and that's a bug).

Whatever we change in the environment to reduce the likelihood of
hitting this issue there doesn't solve the underlying race condition in
MAAS, and leaves open the possibility of hitting the issue other places
too.

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

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

[Andres Rodriguez]

@Steve,

MAAS already has a mechanism to collapse retries into the initial request.
In this case, it is the rack that grabs the requests and makes a request to
the region. If retries come within the time that the rack is waiting for a
response from the region, these request get "ignored" and the Rack will
only answer the first request. This is what the logs show after testing
with fixed grub, where grub makes multiple requests and MAAS answers
seconds after does requests, but only answers once. This is because the
requests were collapsed on the maas side.

If, however, the retries come in after the region has answered the rack,
they these requests will be served.


On Mon, Feb 5, 2018 at 2:34 PM, Steve Langasek  wrote:

> Jason's feedback was that, after making the changes to the storage
> configuration of his environment, deploying the test grubx64.efi doesn't
> have any effect on the MAAS server's response time to tftp requests.  So
> at this point it's not at all clear that the grub change, while correct,
> helps with this high-level symptom.
>
> It has also been suggested that each udp retry is generating a separate
> database query from MAAS.  That is absolutely a MAAS bug if true, and
> not something that can or should be fixed in GRUB.
>
> ** Changed in: grub2 (Ubuntu)
>Importance: Critical => Medium
>
> --
> 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
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/maas/+bug/1743249/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: product=maas; milestone=2.4.x; status=Incomplete;
> importance=Undecided; assignee=None;
> Launchpad-Bug: distribution=ubuntu; sourcepackage=grub2; component=main;
> status=In Progress; importance=Medium; assignee=mathieu...@gmail.com;
> Launchpad-Bug-Tags: cdo-qa cdo-qa-blocker foundations-engine patch
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: andreserl blake-rouse cgregan jason-hobbs vorlon
> Launchpad-Bug-Reporter: Jason Hobbs (jason-hobbs)
> Launchpad-Bug-Modifier: Steve Langasek (vorlon)
> Launchpad-Message-Rationale: Subscriber (MAAS)
> Launchpad-Message-For: andreserl
>


-- 
Andres Rodriguez (RoAkSoAx)
Ubuntu Server Developer
MSc. Telecom & Networking
Systems Engineer

-- 
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 1101647] Re: ID 138a:003d Validity Sensors, Inc.

[Paul]

The bug also affects me. I found a solution featuring an automatic
install script, but libpam-fprintd is quite buggy, at least for me.

https://github.com/PetreBoboc/vfs495_ubuntu

It does also work with my VFS 471 and possibly with the VFS 491.

Would it be possible to link/integrate fprint to/into fingerprint-gui?
The authentication itself seems to work quite reliably, it's the PAM-
module that is causing problems.

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

Title:
  ID 138a:003d Validity Sensors, Inc.

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

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

[Bug 1747499] Re: 98-reboot-required and Interaction with livepatch

[Steve Langasek]

The position of the Security Team has been consistent that kernel live
patching allows users to defer reboots, it does not allow users to avoid
them.  Because not all security fixes are included in live patches, and
because correlating the live patch CVEs to the kernel deb CVEs requires
knowledge that's external to the packages themselves, hiding the 'reboot
required' message will give users a false sense of security about their
system.

Cc:ing Tyler for any further comment.

Whatever our policy is going to be here, it should be consistent across
the board for both desktop and server (which may fall out naturally from
changes to update-notifier, but maybe not).

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

Title:
  98-reboot-required and Interaction with livepatch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1747499/+subscriptions

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

[Bug 1731940] Re: [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at all

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (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/1731940

Title:
  [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at
  all

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

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

[Bug 1736116] Re: Host with kernel 4.13 freezes when starting a VM with VirtualBox

[nor]

@Lonnie Lee #39

Thank You, you made my day !!!

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

Title:
  Host with kernel 4.13 freezes when starting a VM with VirtualBox

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

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

[Bug 1747521] Re: gvfsd-mtp crashed with SIGSEGV

[Apport retracing service]

*** This bug is a duplicate of bug 1706097 ***
https://bugs.launchpad.net/bugs/1706097

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1706097, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1747521/+attachment/5049427/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1747521/+attachment/5049429/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1747521/+attachment/5049432/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1747521/+attachment/5049433/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1747521/+attachment/5049434/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1747521/+attachment/5049435/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1747521/+attachment/5049436/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1706097
   gvfsd-mtp crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  gvfsd-mtp crashed with SIGSEGV

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

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

[Bug 1746807] Re: 18.04 daily installer fails missing kernel

[Jb]

Lubuntu Alternate 20180205 = fails

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

Title:
  18.04 daily installer fails missing kernel

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

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

[Bug 1747170] Re: installer no ipv4 dhcp

[Jb]

retest:

bionic server daily 20180205 = still no ipv4 dhcp

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

Title:
  installer no ipv4 dhcp

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

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

[Bug 1747518] Re: package grub-common 2.02~beta3-4ubuntu7.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package grub-common 2.02~beta3-4ubuntu7.1 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/grub2/+bug/1747518/+subscriptions

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

[Bug 1747518] [NEW] package grub-common 2.02~beta3-4ubuntu7.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Kocsis Antal]

Public bug reported:

I don't know

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: grub-common 2.02~beta3-4ubuntu7.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Mon Feb  5 21:50:38 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2018-02-02 (3 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=a9aa11f1-4335-4484-9e40-d03d7d271c2b ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.5.1
SourcePackage: grub2
Title: package grub-common 2.02~beta3-4ubuntu7.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package artful

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

Title:
  package grub-common 2.02~beta3-4ubuntu7.1 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/grub2/+bug/1747518/+subscriptions

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

[Bug 1746900] Re: linux: 3.13.0-142.191 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/certification-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1746901
  derivatives:
- kernel-stable-phase-changed:Friday, 02. February 2018 14:33 UTC
- kernel-stable-phase:Uploaded
- 
  -- swm properties --
  boot-testing-requested: true
  phase: Uploaded
+ kernel-stable-phase-changed:Monday, 05. February 2018 21:01 UTC
+ kernel-stable-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: 1746901
  derivatives:
  -- swm properties --
  boot-testing-requested: true
- phase: Uploaded
- kernel-stable-phase-changed:Monday, 05. February 2018 21:01 UTC
- kernel-stable-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux: 3.13.0-142.191 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1746900/+subscriptions

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

[Bug 1684240] Re: Lagging square around mouse pointer

[Scott Deagan]

I experienced this bug on both my laptops (both with Nvidia 9xx series
GPUs) with KDE Neon (developer stable), but not on my desktop PC. All
are running the latest proprietary Nvidia 390 drivers.

I observed today that the problem only occurs when the Nvidia GPU is in
use (sudo prime-select nvidia). The problem disappears if I switch to
the Intel GPU (sudo prime-select intel).

Interestingly, the problem does not occur on my laptops when running
Kubuntu 17.10, regardless of the GPU in use.

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

Title:
  Lagging square around mouse pointer

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

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

[Bug 1736145] Re: Ubuntu16.04.03: ISAv3 initialize MMU registers before setting partition table

[Joseph Salisbury]

SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089997.html

** Description changed:

+ == SRU Justification ==
+ Kexec can leave MMU registers set, PIDR in particular, when booting the
+ new kernel. The boot sequence does not zero PIDR ever, and it only gets
+ changed as CPUs first switch to userspace processes. This can leave a
+ window where speculative accesses from a CPU to quadrant 0 can pick up
+ translations in the partition table that may be set up for processes
+ running on other CPUs. These cached translations will not be involved in
+ the invalidation protocol, so we can end with stable TLB and PWC.
+ 
+ This commit was included in mailine as of v4.15-rc5 and fixes commit
+ 7e381c0ff618.
+ 
+ == Fix ==
+ commit 371b80447ff33ddac392c189cf884a5a3e18faeb
+ Author: Nicholas Piggin 
+ Date:   Wed Dec 6 18:21:14 2017 +1000
+ 
+ powerpc/64s: Initialize ISAv3 MMU registers before setting partition
+ table
+ 
+ == Regression Potential ==
+ Low. This fix is specific to powerpc.  It has also been cc'd to upstream 
stable, 
+ so it has had additional upstream review.
+ 
+ 
+ ==Original Bug Description: ==
  == Comment: #0 - Breno Leitao  - 2017-12-04 05:50:27 ==
  kexec can leave MMU registers set, PIDR in particular, when booting the
  new kernel. The boot sequence does not zero PIDR ever, and it only gets
  changed as CPUs first switch to userspace processes. This can leave a
  window where speculative accesses from a CPU to quadrant 0 can pick up
  translations in the partition table that may be set up for processes
  running on other CPUs. These cached translations will not be involved in
  the invalidation protocol, so we can end with stable TLB and PWC.
  
- 
  We need to have this patch included in Ubuntu kernel.
  https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-December/166424.html
  
  We do not have commit id, but once we have, I will post here. There is
  no need to include the patch prior to upstream acceptance.
  
  == Comment: #2 - VIPIN K. PARASHAR  - 2017-12-04 
06:57:52 ==
  (In reply to comment #0)
- > 
+ >
  > We need to have this patch included in Ubuntu kernel.
  > https://lists.ozlabs.org/pipermail/linuxppc-dev/2017-December/166424.html
- > 
+ >
  > We do not have commit id, but once we have, I will post here. There is no
  > need to include the patch prior to upstream acceptance.
  >
  
  .. Patch subject reads as follows:
  
  [PATCH] powerpc/64s: ISAv3 initialize MMU registers before setting
  partition table

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

Title:
  Ubuntu16.04.03: ISAv3 initialize MMU registers before setting
  partition table

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1736145/+subscriptions

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

[Bug 1746628] Re: New walinuxagent upstream version: 2.2.21

[Launchpad Bug Tracker]

This bug was fixed in the package walinuxagent - 2.2.21-0ubuntu1

---
walinuxagent (2.2.21-0ubuntu1) bionic; urgency=medium

  * New upstream release (LP: #1746628).
  * debian/patches/disable_import_test.patch: refreshed patch.

 -- Łukasz 'sil2100' Zemczak   Mon, 05 Feb
2018 17:25:14 +0100

** Changed in: walinuxagent (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  New walinuxagent upstream version: 2.2.21

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

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

[Bug 1747513] [NEW] OpenVswitch 2.8.0 Stuck on boot

[Jose Phillips]

Public bug reported:

When upgrade openvswitch from 2.5 to 2.8 based on "Xenial-Pike"
Repository of openstack the computer got stuck on boot .

the way to recover back is booting on safe mode deleting conf.db and
after that i can boot to the server again but when neutron-openvswitch-
agent reconfigure OVS is unable to restart the server again.

** Affects: openvswitch (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/1747513

Title:
  OpenVswitch 2.8.0 Stuck on boot

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

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

[Bug 1746340] Re: Samsung SSD corruption (fsck needed)

[Lucas Zanella]

I searched and found nothing.

So, even with APST disabled my ssd will fail on linux. What should I do?
Does it work normally for other people when they disable it?

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

Title:
  Samsung SSD corruption (fsck needed)

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

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

[Bug 1521173] Re: AER: Corrected error received: id=00e0

[Thorsten Munsch]

Still present in (X)ubuntu 17.10 with kernel 4.13.0-32-generic.

The trigger is the onboard Realtek network chip on my Gigabyte GA-AB350
Gaming 3 (AMD Ryzen) mainboard:

+-01.3-[01-05]--+-00.0  Advanced Micro Devices, Inc. [AMD] USB 3.1 XHCI 
Controller
   |   +-00.1  Advanced Micro Devices, Inc. [AMD] Device 
43b7
   |   \-00.2-[02-05]--+-00.0-[03]00.0  Realtek 
Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet 
Controller
   |   +-01.0-[04]--
   |   \-04.0-[05]--

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

Title:
  AER: Corrected error received: id=00e0

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

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

[Bug 1744722] Re: Unknown bad source brings up during 'zesty' to 'artful' upgrade and It break the process

[ZdravkoG]

Hi @Julian Andres Klode,

It seems I didn't read carefully Your additions to the bug description.
Especially the line:

"Now run do-release-upgrade --proposed and check that it does not do
that."

Thanks to @Brian Murray for the note.
So, if there is someone still running Ubuntu 17.04 and want to upgrade to 
17.10, can open a terminal window and run the command:

  do-release-upgrade --proposed

Just to be clear. Thanks.

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

Title:
  Unknown bad source brings up during 'zesty' to 'artful' upgrade and It
  break the process

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

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

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

[Jason Hobbs]

@Steve - I don't think it helps with the problem of MAAS taking a long
time to respond to the grub.cfg request.  However, it may help with the
part of this bug where grub is hitting an error and asking for keyboard
input.  https://imgur.com/a/as8Sx

Maybe that should be a separate bug?  It seems like grub should never
ask for user keyboard input on a server.

-- 
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 1743249] Re: Failed Deployment after timeout trying to retrieve grub cfg

[Jason Hobbs]

On Mon, Feb 5, 2018 at 11:58 AM, Andres Rodriguez
 wrote:
> No new data was provided to mark this New in MAAS:
>
> 1. Changes to the storage seem to have improved things

Yes, it has.  That doesn't change whether or not there is a bug in
MAAS.  Can you please address the critical log errors that I mentioned
in comment #36?  This seems like enough to establish something is
going wrong in MAAS.

> 2. No tests have been run with fixed grub that have caused boot
failures.

The comments from #56 were testing with the fixed grub - sorry if that
wasn't clear.

> 3. AFAIK, the VM config has not changed to use less CPU to compare
results and whether this config change causes the bugs in question.

The CPU load data from comments #48 and #50 shows that CPU load is not
the problem.  The max load average was under 12 on a 20 thread system.
That means there was lots of free CPU time, and that this workload is
not CPU bound.

Jason


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

-- 
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 1521173] Re: AER: Corrected error received: id=00e0

[Thorsten Munsch]

I noticed weird network problems on this system aswell, when plugging in
a USB3 external harddisk and on Friday even when I just plugged in my
mobile phone just to load the battery.

Don't know if this is connected in some way. Yesterday I updated the
UEFI/BIOS and will watch if this is still happening.

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

Title:
  AER: Corrected error received: id=00e0

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

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

[Bug 1735159] Re: powerpc/powernv: Flush console before platform error reboot

[Joseph Salisbury]

SRU request submitted for Artful:
https://lists.ubuntu.com/archives/kernel-team/2018-February/089995.html

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

Title:
  powerpc/powernv: Flush console before platform error reboot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1735159/+subscriptions

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

[Bug 1616332] Re: gnome-software using hundreds of MB of memory when not in use

[Traumflug]

> explain yourselves Ubuntu

Never seen Ubuntu explaining anything, helping people with debugging or
something like this in the last five years. Eventually the problem will
go away some way or another, but even this event most likely won't get
reported. So, don't expect too much.

That said, clicking on "This bug affects xxx people, but not you" just
under the bug title and adding one selfs to the list of affected people
raises bug "heat", which I believe does make a distinction.

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

Title:
  gnome-software using hundreds of MB of memory when not in use

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

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

[Bug 1744711] Re: Update gnome-terminal to 3.28 (vte 0.52)

[Egmont Koblinger]

** Patch added: "gnome-terminal-3.27.90 revert-pcre2.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+attachment/5049415/+files/revert-pcre2.patch

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

Title:
  Update gnome-terminal to 3.28 (vte 0.52)

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

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

[Bug 1744711] Re: Update gnome-terminal to 3.28 (vte 0.52)

[Egmont Koblinger]

As per bug 1745825, I've dropped the code that decides whether to
show/hide the "Use transparency from system theme" checkbox, it is now
always shown.

It shouldn't be that hard to bring it back. It'd need to be done
manually; methods that received an extra parameter by this part of the
patch now take different parameters in upstream, so the patch doesn't
apply automatically.

As this part of the code might cause a crash, I'm personally not
motivated at all to bring back that crash, I vote for this patch which
eliminates it. And as per that bug, bringing back this feature and
fixing the bug in the same time is really nontrivial.

** Patch added: "gnome-terminal-3.27.90 0001-Restore-transparency.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+attachment/5049413/+files/0001-Restore-transparency.patch

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

Title:
  Update gnome-terminal to 3.28 (vte 0.52)

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

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

[Bug 1744711] Re: Update gnome-terminal to 3.28 (vte 0.52)

[Egmont Koblinger]

** Patch added: "gnome-terminal-3.27.90 60_add_lp_handler.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1744711/+attachment/5049414/+files/60_add_lp_handler.patch

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

Title:
  Update gnome-terminal to 3.28 (vte 0.52)

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

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

[Bug 1746726] Re: linux-azure: 4.13.0-1009.12 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: Confirmed => Incomplete

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

Title:
  linux-azure: 4.13.0-1009.12 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1746726/+subscriptions

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