[Bug 1721319] Re: On-screen keyboard pops up with touchscreen even when physical keyboard present

2020-02-10 Thread Daniel van Vugt
** Tags added: fixed-in-3.35.91 fixed-upstream

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

Title:
  On-screen keyboard pops up with touchscreen even when physical
  keyboard present

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

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

[Bug 1725180] Re: Shell animations are not smooth

2020-02-10 Thread Daniel van Vugt
^^^
That's only the window spread performance fix that has landed (to be released 
in 3.35.91). Not everything yet.

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

Title:
  Shell animations are not smooth

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

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

[Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data

2020-02-10 Thread Nivedita Singhvi
We have narrowed it down to a flaw in a specific configuration setting
on this NIC, so we're comparing the good and bad configurations now.

Primary port: enp94s0f0
Secondary port: enp94s0f1d1


A] Good config for fault-tolerance (active-backup) bonding mode:
--
Primary port = active interface; Secondary port = backup

B] Bad config for fault-tolerance (active-backup) bonding mode:
--
Primary port = backup interface; Secondary port = active


We are consistently able to reproduce a drop rate difference
with UDP pkts, for the above good/bad cases:


Good Case UDP MTR Test Result
-
mtr --no-dns --report --report-cycles 60 --udp -s 1428 $DEST
Start: 2020-02-10T10:14:01+
HOST: hostname Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- nn.nn.nnn.nnn  0.0%600.3   0.2   0.2   0.3   0.0


Bad Case UDP MTR Test Result
---
mtr --no-dns --report --report-cycles 60 --udp -s 1428 $DEST
Start: 2020-02-10T14:10:52+
HOST: hostname Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- nn.nn.nnn.nnn  8.3%600.3   0.3   0.2   0.4   0.0

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

Title:
  BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be
  dropping data

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

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

[Bug 1862734] Re: Failed to suspend once ever paired with BLE devices: PM: Device 0000:00:14.0 failed to suspend async: error -16

2020-02-10 Thread You-Sheng Yang
** Description changed:

- TBD
+ Similar to bug 1858776 and bug 1850738, Intel(R) Wireless-AC 9560
+ 160MHz, REV=0x354 [8086:02f0] subsystem [8086:4034] btusb may fail
+ system suspend with following error messages in dmesg:
  
+ [4.880979] Bluetooth: hci0: Bootloader revision 0.1 build 0 week 30 2018
+ [4.881987] Bluetooth: hci0: Device revision is 2
+ [4.881988] Bluetooth: hci0: Secure boot is enabled
+ [4.881989] Bluetooth: hci0: OTP lock is enabled
+ [4.881990] Bluetooth: hci0: API lock is enabled
+ [4.881991] Bluetooth: hci0: Debug lock is disabled
+ [4.881992] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
+ [4.883480] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-1.sfi
+ ...
+ [   71.387652] PM: suspend entry (s2idle)
+ [   71.387655] PM: Syncing filesystems ... done.
+ [   71.395449] Freezing user space processes ... 
+ [   71.770699] Bluetooth: hci0: advertising data len corrected
+ [   72.330683] (elapsed 0.920 seconds) done.
+ [   72.330689] OOM killer disabled.
+ [   72.330690] Freezing remaining freezable tasks ... (elapsed 0.014 seconds) 
done.
+ [   72.345132] printk: Suspending console(s) (use no_console_suspend to debug)
+ [   72.399557] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16
+ [   72.399566] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16
+ [   72.399730] PM: Device :00:14.0 failed to suspend async: error -16
+ [   72.425583] PM: Some devices failed to suspend, or early wake event 
detected
+ [   72.486631] Bluetooth: hci0: advertising data len corrected
+ [   72.611800] OOM killer enabled.
+ [   72.611802] Restarting tasks ... done.
+ [   72.629308] thermal thermal_zone5: failed to read out thermal zone (-61)
+ [   72.663376] PM: suspend exit
+ [   72.663413] PM: suspend entry (s2idle)
+ 
+ This can be fixed by upgrading intel/ibt-19-0-1.sfi to REL0318 from
+ upstream commit c0ca980cee32.
+ 
+ ---
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.173.14
  ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21
  Uname: Linux 5.0.0-1037-oem-osp1 x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  u  1583 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  u  1583 F pulseaudio
  Date: Tue Feb 11 02:05:47 2020
  Dependencies:
-  
+ 
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-arya+X37
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-arya+X37
  InstallationDate: Installed on 2020-01-06 (35 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
  MachineType: Dell Inc. Latitude 7410
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 
root=UUID=fd4c84f6-205f-4fb2-9225-bb232ba08e38 ro quiet splash vt.handoff=1
  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-5.0.0-1037-oem-osp1 N/A
-  linux-backports-modules-5.0.0-1037-oem-osp1  N/A
-  linux-firmware   1.173.14
+  linux-restricted-modules-5.0.0-1037-oem-osp1 N/A
+  linux-backports-modules-5.0.0-1037-oem-osp1  N/A
+  linux-firmware   1.173.14
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.4.7
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.7:bd12/30/2019:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7410
  dmi.product.sku: 09BE
  dmi.sys.vendor: Dell Inc.

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

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

** Changed in: linux-firmware (Ubuntu Disco)
   Status: New => Won't Fix

** Changed in: linux-firmware 

[Bug 1861184] Re: bionic/linux-gcp: 5.0.0-1030.31 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
*** This bug is a duplicate of bug 1862213 ***
https://bugs.launchpad.net/bugs/1862213

** This bug has been marked a duplicate of bug 1862213
   bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

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

Title:
  bionic/linux-gcp: 5.0.0-1030.31 -proposed tracker

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

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

[Bug 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-bionic

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1861192
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 11. February 2020 04:07 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Tuesday, 11. February 2020 07:47 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building
- replaces: bug 1861184
+   promote-to-proposed: Pending -- ready for review
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1862212
  variant: debs

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

Title:
  bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

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

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

[Bug 1862056] Re: Theme: use other exported colors

2020-02-10 Thread Frederik Feichtmeier
** Attachment added: "Bildschirmfoto-20200211084652-1252x893.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1862056/+attachment/5327256/+files/Bildschirmfoto-20200211084652-1252x893.png

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

Title:
  Theme: use other exported colors

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

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

[Bug 1862056] Re: Theme: use other exported colors

2020-02-10 Thread Frederik Feichtmeier
Hey! Awesome it got fixed to fast, just received the update in 20.04
daily :) Cheers!

I will try to get this into upstream, since it makes more sense for them
too!

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

Title:
  Theme: use other exported colors

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

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

[Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers

2020-02-10 Thread Christian Ehrhardt 
We have a new MP that fixes things for real in Focal.

The former SRUs already have been set to verification-failed and can be
cancelled from -proposed if it helps to clear up things.

** Changed in: rsyslog (Ubuntu Disco)
   Status: Fix Committed => Triaged

** Changed in: rsyslog (Ubuntu Bionic)
   Status: Fix Committed => Triaged

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

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

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

[Bug 1862224] Re: xenial/linux-gcp: 4.15.0-1054.58 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-xenial

** Tags added: block-proposed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1861165
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Holding before Promote to Proposed
- phase-changed: Tuesday, 11. February 2020 03:42 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Tuesday, 11. February 2020 07:32 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait
- replaces: bug 1861160
+   promote-to-proposed: Pending -- ready for review
  trackers:
xenial/linux-gcp/gcp-kernel: bug 186
xenial/linux-gcp/gke-kernel: bug 1862223
  variant: debs

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

Title:
  xenial/linux-gcp: 4.15.0-1054.58 -proposed tracker

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

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

[Bug 1861160] Re: xenial/linux-gcp: 4.15.0-1053.57 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
*** This bug is a duplicate of bug 1862224 ***
https://bugs.launchpad.net/bugs/1862224

** This bug has been marked a duplicate of bug 1862224
   xenial/linux-gcp: 4.15.0-1054.58 -proposed tracker

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

Title:
  xenial/linux-gcp: 4.15.0-1053.57 -proposed tracker

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

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

[Bug 1862736] [NEW] sof driver fails and print lots of errors in the dmesg (focal)

2020-02-10 Thread Hui Wang
Public bug reported:

Because we introduced this commit from stable patches, but only
backporting this commit is not enough.

Author: Ranjani Sridharan 
Date:   Mon Nov 4 14:48:12 2019 -0800

ASoC: SOF: topology: set trigger order for FE DAI link

BugLink: https://bugs.launchpad.net/bugs/1858428

[ Upstream commit 5eee2b3f60065a2530d13f28e771be48b989eb4c ]

Set trigger order for FE DAI links to SND_SOC_DPCM_TRIGGER_POST
to trigger the BE DAI's before the FE DAI's. This prevents the
xruns seen on playback pipelines using the link DMA.

Signed-off-by: Ranjani Sridharan 
Signed-off-by: Pierre-Louis Bossart 
Link: 
https://lore.kernel.org/r/20191104224812.3393-3-ranjani.sridha...@linux.intel.com
Signed-off-by: Mark Brown 
Signed-off-by: Sasha Levin 
Signed-off-by: Seth Forshee 

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Hui Wang (hui.wang)
 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/1862736

Title:
  sof driver fails and print lots of errors in  the dmesg (focal)

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

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

[Bug 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1861192
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 11. February 2020 04:07 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building
  replaces: bug 1861184
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1862212
  variant: debs

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

Title:
  bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

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

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

[Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers

2020-02-10 Thread Christian Ehrhardt 
** Changed in: rsyslog (Ubuntu)
   Status: Fix Released => In Progress

** Also affects: rsyslog (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: rsyslog (Ubuntu Eoan)
   Status: New => Triaged

** Changed in: rsyslog (Ubuntu Eoan)
   Importance: Undecided => Low

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

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

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

[Bug 1721319] Re: On-screen keyboard pops up with touchscreen even when physical keyboard present

2020-02-10 Thread Bug Watch Updater
** Changed in: gnome-shell
   Status: New => 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/1721319

Title:
  On-screen keyboard pops up with touchscreen even when physical
  keyboard present

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

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

[Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

2020-02-10 Thread Balint Kovacs
Hi all,

thanks for the fixes in Eoan. Unfortunately we have a product based on
disco and cannot move forward at this time. Being a networking shop,
this issue has a serious effect on us and we would like to avoid moving
to something like ifupdown2 within our stable branch.

For our users the real impact of the bug is not that that the interface
that we are currently reconfiguring is suffering a downtime, but the
fact that _all_ interfaces have their aliases removed if networkd is
restarted. The proposed KeepConfiguration solution kind of beats the
purpose of reconfiguring the interfaces, as old addresses are kept and
need to be handled manually. Also it interferes with how DHCP works. I
believe this might be an issue for others as well.

>From our point of view the ideal solution would be a combination of the
keepalived patch that detects VIP removal and systemd version 244 that
already supports "networkctl reconfigure" and "networkctl reload".

Is there any chance that v244 is backported to bionic? It is already
included in focal and debian stable backports, but unfortunately I am
not familiar enough with systemd development to tell what the impact of
this would be.

As for keepalived, in bug #1819074 there was an ongoing investigation on
the patch, that implements the keepalived transition on removing the
VIP. We have traced back this functionality to this patch:

https://github.com/acassen/keepalived/commit/0b1528c76d3fe8d1c5765841df86c59570a036da

It was born before v1.3.6 was released, so we hope that it is self-
contained enough for a backport if v2.0 of keepalived is not included in
bionic-backports.

Best,
Balint

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-keepalived/+bug/1815101/+subscriptions

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

[Bug 1862734] Re: Failed to suspend once ever paired with BLE devices: PM: Device 0000:00:14.0 failed to suspend async: error -16

2020-02-10 Thread You-Sheng Yang
** Tags added: oem-priority originate-from-1858770 somerville

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

Title:
  Failed to suspend once ever paired with BLE devices: PM: Device
  :00:14.0 failed to suspend async: error -16

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1862734/+subscriptions

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

[Bug 1831940] Re: hibernation support for linux-aws

2020-02-10 Thread Andrea Righi
** Description changed:

  Additional AWS-specific and mainline patches are required to support
  hibernation across the various types of AWS instances.
  
  The following patch sets for linux-aws-xenial and linux-aws-bionic
  provide the necessary functionality, and should only impact the
  hibernation and resume paths.
  
  [linux-aws-xenial]
  
  UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore
  UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake
  UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation.
  UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in 
xen_restore_pirqs.
  radix-tree: delete radix_tree_locate_item()
  mm: rid swapoff of quadratic complexity
  sched/wait: Fix abort_exclusive_wait(), it should pass TASK_NORMAL to 
wake_up()
  sched/wait: Avoid abort_exclusive_wait() in ___wait_event()
  sched/wait: Avoid abort_exclusive_wait() in __wait_on_bit_lock()
  sched/wait: Introduce init_wait_entry()
  sched/wait: Standardize wait_bit_queue naming
  sched/wait: Introduce wait_var_event()
  mm: swapoff: shmem_unuse() stop eviction without igrab()
  UBUNTU SAUCE [aws]: mm: aggressive swapoff
  UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled
  NVMe: Allow request merges
  PM / hibernate: Do not free preallocated safe pages during image restore
  PM / hibernate: Recycle safe pages after image restoration
  PM / hibernate: Simplify mark_unsafe_pages()
  UBUNTU: [Config] aws: disable CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS
  UBUNTU SAUCE [aws] PM / hibernate: set image_size to total RAM size by default
  UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing
  UBUNTU SAUCE [aws] mm, page_alloc: disable fair zone allocation policy on 
hibernate
  
- 
  [linux-aws-bionic]
  
  UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore
  UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake
  UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation.
  UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in 
xen_restore_pirqs.
  mm: rid swapoff of quadratic complexity
  sched/wait: Introduce wait_var_event()
  mm: swapoff: shmem_unuse() stop eviction without igrab()
  UBUNTU SAUCE [aws]: mm: aggressive swapoff
  netlink: Don't shift on 64 for ngroups
+ 
+ [linux-aws-edge-bionic]
+ 
+ UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in 
xen_restore_pirqs.
+ UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation.
+ UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore
+ UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake
+ UBUNTU SAUCE [aws]: PM / hibernate: set image_size to 0 by default
+ UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled
+ UBUNTU SAUCE [aws]: mm: swap: improve swap readahead heuristic
+ UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing
+ PM / hibernate: memory_bm_find_bit(): Tighten node optimisation
+ mm: rid swapoff of quadratic complexity
+ mm: refactor swap-in logic out of shmem_getpage_gfp

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

Title:
  hibernation support for linux-aws

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

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

[Bug 1862734] [NEW] Failed to suspend once ever paired with BLE devices: PM: Device 0000:00:14.0 failed to suspend async: error -16

2020-02-10 Thread You-Sheng Yang
Public bug reported:

TBD

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-firmware 1.173.14
ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21
Uname: Linux 5.0.0-1037-oem-osp1 x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  u  1583 F pulseaudio
Date: Tue Feb 11 02:05:47 2020
Dependencies:
 
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-arya+X37
InstallationDate: Installed on 2020-01-06 (35 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20190418-12:10
MachineType: Dell Inc. Latitude 7410
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 
root=UUID=fd4c84f6-205f-4fb2-9225-bb232ba08e38 ro quiet splash vt.handoff=1
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.
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-1037-oem-osp1 N/A
 linux-backports-modules-5.0.0-1037-oem-osp1  N/A
 linux-firmware   1.173.14
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 0.4.7
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr0.4.7:bd12/30/2019:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 7410
dmi.product.sku: 09BE
dmi.sys.vendor: Dell Inc.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: linux-firmware (Ubuntu)
 Importance: Undecided
 Assignee: You-Sheng Yang (vicamo)
 Status: New


** Tags: amd64 apport-bug bionic oem-priority originate-from-1858770 somerville

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

Title:
  Failed to suspend once ever paired with BLE devices: PM: Device
  :00:14.0 failed to suspend async: error -16

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1862734/+subscriptions

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

[Bug 1845800] Re: xiccd consumes 100% CPU

2020-02-10 Thread Jarno Suni
I have this bug in Xubuntu 18.04.

** 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/1845800

Title:
  xiccd consumes 100% CPU

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

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

[Bug 1862733] Re: crash

2020-02-10 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: 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/1862733

Title:
  crash

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

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

[Bug 1861122] Re: xenial/linux: 4.4.0-174.204 -proposed tracker

2020-02-10 Thread Po-Hsu Lin
** Tags added: regression-testing-passed

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

Title:
  xenial/linux: 4.4.0-174.204 -proposed tracker

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

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

[Bug 1862733] [NEW] crash

2020-02-10 Thread Betros Abraha
Public bug reported:

crach

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
Uname: Linux 5.3.0-28-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Feb 10 22:43:21 2020
DistUpgraded: 2020-01-15 21:02:05,550 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.116, 5.3.0-28-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:2286]
InstallationDate: Installed on 2020-01-16 (26 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
MachineType: LENOVO 20Q0002EUS
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=125967d5-379e-4de9-aa68-c6208d80892a ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2020-01-16 (26 days ago)
dmi.bios.date: 01/03/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: N2JET84W (1.62 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20Q0002EUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN2JET84W(1.62):bd01/03/2020:svnLENOVO:pn20Q0002EUS:pvrThinkPadX390:rvnLENOVO:rn20Q0002EUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X390
dmi.product.name: 20Q0002EUS
dmi.product.sku: LENOVO_MT_20Q0_BU_Think_FM_ThinkPad X390
dmi.product.version: ThinkPad X390
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Wed Jan 15 20:25:03 2020
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  crash

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

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

[Bug 1861063] Re: Dualshock4 controller doesn't stay connected

2020-02-10 Thread Goran Josic
Thank you for the info Bastian. Now all we can do is wait for the
bugfix.

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

Title:
  Dualshock4 controller doesn't stay connected

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

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

[Bug 1861192] Re: disco/linux: 5.0.0-41.45 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 30. January 2020 14:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-5.0: bug 1861179
bionic/linux-azure: bug 1862405
bionic/linux-bluefield: bug 1861188
-   bionic/linux-gcp: bug 1861184, bug 1862213
+   bionic/linux-gcp: bug 1862213, bug 1861184
bionic/linux-gke-5.0: bug 1861187
bionic/linux-oem-osp1: bug 1861178
bionic/linux-oracle-5.0: bug 1861190
  variant: debs

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

Title:
  disco/linux: 5.0.0-41.45 -proposed tracker

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

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

[Bug 1861122] Re: xenial/linux: 4.4.0-174.204 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 30. January 2020 14:52 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
-   regression-testing: Ongoing -- testing in progress
verification-testing: Ongoing -- testing in progress
  trackers:
trusty/linux-aws: bug 1861119
trusty/linux-lts-xenial: bug 1861121
xenial/linux-aws: bug 1861107
xenial/linux-cascade: bug 1861109
xenial/linux-fips: bug 1861116
xenial/linux-kvm: bug 1861110
xenial/linux-raspi2: bug 1861113
xenial/linux-snapdragon: bug 1861115
xenial/linux/caracalla-kernel: bug 1861103
xenial/linux/pc-kernel: bug 1861104
xenial/linux/stlouis-kernel: bug 1861105
  variant: debs

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

Title:
  xenial/linux: 4.4.0-174.204 -proposed tracker

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

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

[Bug 1801282] Re: [VROC]Call trace during IO on IMSM RAID 5 (fio performance check)

2020-02-10 Thread quanxian
if reproduce, just reopen it.

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

Title:
  [VROC]Call trace during IO on IMSM RAID 5 (fio performance check)

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

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

[Bug 1861122] Re: xenial/linux: 4.4.0-174.204 -proposed tracker

2020-02-10 Thread Po-Hsu Lin
4.4.0-174.204 - generic
Regression test CMPL, RTB.

56 / 59 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, 
ubuntu_xfstests_xfs
Issue to note in amd64:
  ubuntu_kernel_selftests - script permission issue in net (bug 1861973)
  ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) vmx 
(bug 1821394)
  ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

51 / 54 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, 
ubuntu_xfstests_xfs
Issue to note in arm64:
  hwclock - issue for HP m400 (bug 1716603)
  ubuntu_ecryptfs - proxy issue (RT#123768)
  ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) script 
permission issue in net (bug 1861973)
  ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427)
  ubuntu_kvm_unit_tests - gicv2-mmio on X-ARM64 (bug 1828165) gicv2-mmio-3p 
(bug 1828027) gicv2-mmio-up (bug 1828026) pmu on ms10-34-mcdivittB0-kernel (bug 
1751000)
  ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454)
  ubuntu_lxc - failed to fetch GPG key, probably FW issue
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

50 / 54 tests were run, missing: ubuntu_kvm_unit_tests, ubuntu_xfstests_btrfs, 
ubuntu_xfstests_ext4, ubuntu_xfstests_xfs
Issue to note in i386:
  ubuntu_kernel_selftests - script permission issue in net (bug 1861973)
  ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

52 / 55 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, 
ubuntu_xfstests_xfs
Issue to note in ppc64le (P8):
  ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 
320M on Xenial P8 (bug 1813863)
  ubuntu_ecryptfs - faild to fork child for file-concurrent.sh and 
directory-concurrent.sh.ext3
  ubuntu_fan_smoke_test - failed to fetch file from ports.ubuntu.com, probably 
FW issue
  ubuntu_kernel_selftests - script permission issue in net (bug 1861973)
  ubuntu_ltp_syscalls - fallocate04, fallocate05, fsetxattr01, fdatasync03, 
fgetxattr01, fremovexattr01, fremovexattr02, fsync01, fsync04, fanotify13, 
fanotify14, fanotify15, lremovexattr01, msync04, preadv03, preadv03_64, 
preadv203, preadv203_64, pwritev03, pwritev03_64, setxattr01, sync03, syncfs01, 
sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) 
fanotify10 (bug 1802454) move_pages12 (bug 1831043)
  ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

Issue to note in s390x (Ubuntu on LPAR):
  libhugetlbfs - failed 5 (Address is not hugepage, Heap not on hugepages) 
killed by signal 1 bad config 1
  ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452)
  ubuntu_kernel_selftests - test_bpf in net (bug 1768452) script permission 
issue in net (bug 1861973)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454)
  ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

Issue to note in s390x (zVM):
  libhugetlbfs - failed 5 (Address is not hugepage, Heap not on hugepages) 
killed by signal 1 bad config 1
  ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452)
  ubuntu_kernel_selftests - test_bpf in net (bug 1768452) script permission 
issue in net (bug 1861973)
  ubuntu_kvm_smoke_test - uvtool issue (bug 1729854)
  ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705)
  ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454)
  ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904)
  ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 
1854298)

Note:
  * Missing s390x KVM because of bug 1859656

** Changed in: kernel-sru-workflow/regression-testing
   Status: In Progress => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin 
(cypressyew)

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

Title:
  xenial/linux: 4.4.0-174.204 -proposed tracker

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

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

[Bug 1862729] [NEW] [Sound]-ALC282-no output only on Internal speakers

2020-02-10 Thread Guicar
Public bug reported:

Laptop is Teclast F5
No sound on internal speaker only,whatever kernel used. Sound is ok with 
headphone or Hdmi. Speakers are working under Windows and are not is a muted 
state. This was checked with alsa mixer.

pacmd list sink

Memory blocks currently allocated: 249, size: 1,2 Mio.
Memory blocks allocated during the whole lifetime: 591245, size: 1,4 Gio.
Memory blocks imported from other processes: 69, size: 796,9 Kio.
Memory blocks exported to other processes: 0, size: 0 B.
Total sample cache size: 0 B.
Default sample spec: s16le 2ch 44100Hz
Default channel map: front-left,front-right
Default sink name: alsa_output.pci-_00_0e.0.analog-stereo
Default source name: alsa_input.pci-_00_0e.0.analog-stereo
Memory blocks of type POOL: 178 allocated/427449 accumulated.
Memory blocks of type POOL_EXTERNAL: 2 allocated/63673 accumulated.
Memory blocks of type APPENDED: 0 allocated/0 accumulated.
Memory blocks of type USER: 0 allocated/0 accumulated.
Memory blocks of type FIXED: 0 allocated/127519 accumulated.
Memory blocks of type IMPORTED: 69 allocated/36277 accumulated.
29 module(s) loaded.
index: 0
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Lennart Poettering"
  module.description = "Automatically restore the volume/mute state of devices"
  module.version = "11.1"
index: 1
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Lennart Poettering"
  module.description = "Automatically restore the volume/mute/device state of 
streams"
  module.version = "11.1"
index: 2
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Lennart Poettering"
  module.description = "Automatically restore profile of cards"
  module.version = "11.1"
index: 3
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Lennart Poettering"
  module.description = "Augment the property sets of streams with additional 
static information"
  module.version = "11.1"
index: 4
 name: 
 argument: <>
 used: -1
 load once: no
 properties:

index: 5
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Michael Terry"
  module.description = "When a sink/source is added, switch to it or 
conditionally switch to it"
  module.version = "11.1"
index: 6
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Lennart Poettering"
  module.description = "Detect available audio hardware and load matching 
drivers"
  module.version = "11.1"
index: 7
 name: 
 argument: 
 used: 6
 load once: no
 properties:
  module.author = "Lennart Poettering"
  module.description = "ALSA Card"
  module.version = "11.1"
index: 8
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Frédéric Dalleau, Pali Rohár"
  module.description = "Policy module to make using bluetooth devices 
out-of-the-box easier"
  module.version = "11.1"
index: 9
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "João Paulo Rechi Vita"
  module.description = "Detect available Bluetooth daemon and load the 
corresponding discovery module"
  module.version = "11.1"
index: 10
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "João Paulo Rechi Vita"
  module.description = "Detect available BlueZ 5 Bluetooth audio devices and 
load BlueZ 5 Bluetooth audio drivers"
  module.version = "11.1"
index: 11
 name: 
 argument: <>
 used: -1
 load once: no
 properties:
  module.author = "Lennart Poettering"
  module.description = "Native protocol (UNIX sockets)"
  module.version = "11.1"
index: 12
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Lennart Poettering"
  module.description = "GConf Adapter"
  module.version = "11.1"
index: 13
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Lennart Poettering"
  module.description = "Automatically restore the default sink and source"
  module.version = "11.1"
index: 14
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Lennart Poettering"
  module.description = "When a sink/source is removed, try to move its streams 
to the default sink/source"
  module.version = "11.1"
index: 15
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Colin Guthrie"
  module.description = "Garde toujours au moins une destination même si elle 
est vide"
  module.version = "11.1"
index: 16
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Lennart Poettering"
  module.description = "Automatically set device of streams based on intended 
roles of devices"
  module.version = "11.1"
index: 17
 name: 
 argument: <>
 used: -1
 load once: yes
 properties:
  module.author = "Lennart Poettering"
  module.description = "When a sink/source is idle for too long, suspend it"
  module.version = "11.1"
index: 18
 

[Bug 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

2020-02-10 Thread Mark - Syminet
Got bit by this as well, recall fixing it a few years ago but must have
clobbered my changes on upgrade bionic -> eoan?  Having VirtualBox
installed broke it, fix was to comment out this line in
/lib/systemdd/system/systemd-timesyncd.service.d and restart systemd:

ConditionFileIsExecutable=!/usr/sbin/VBoxService

Don't recall being asked about a config file change during upgrade
although maybe it did and didn't remember.  Further info here:

https://askubuntu.com/questions/940311/time-in-ubuntu-16-04-not-
updating-from-internet#1005355

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

Title:
  systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
  installed

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

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

[Bug 1801281] Re: [VROC] raid10 Call trace while entering S4 and rebuild is in progress

2020-02-10 Thread quanxian
once it is reproduced, reopen it.

** Changed in: intel
   Status: New => Won't Fix

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

Title:
  [VROC] raid10 Call trace while entering S4 and rebuild is in progress

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

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

[Bug 1801282] Re: [VROC]Call trace during IO on IMSM RAID 5 (fio performance check)

2020-02-10 Thread quanxian
** Changed in: intel
   Status: New => Won't Fix

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

Title:
  [VROC]Call trace during IO on IMSM RAID 5 (fio performance check)

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

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

[Bug 1862714] Re: package libdleyna-core-1.0-5 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdleyna-core-1.0.so.5.0.0', which is also in package libdleyn

2020-02-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: dleyna-core (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/1862714

Title:
  package libdleyna-core-1.0-5 (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu
  /libdleyna-core-1.0.so.5.0.0', which is also in package libdleyna-
  core-1.0-3:amd64 0.6.0-1

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

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

[Bug 1861136] Re: bionic/linux-snapdragon: 4.15.0-1072.79 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861165
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Ready for Promote to Proposed
  phase-changed: Monday, 10. February 2020 17:41 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- ready for review
  trackers:
bionic/linux-snapdragon/dragonboard-kernel: bug 1861135
  variant: debs

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

Title:
  bionic/linux-snapdragon: 4.15.0-1072.79 -proposed tracker

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

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

[Bug 1861190] Re: bionic/linux-oracle-5.0: 5.0.0-1011.16 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861192
  packages:
lrm: linux-restricted-modules-oracle-5.0
main: linux-oracle-5.0
meta: linux-meta-oracle-5.0
signed: linux-signed-oracle-5.0
- phase: Testing
- phase-changed: Monday, 03. February 2020 23:23 UTC
+ phase: Signoff
+ phase-changed: Tuesday, 11. February 2020 05:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
+   promote-to-updates: Holding -- security signoff not verified
security-signoff: Stalled -- waiting for signoff
-   verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  bionic/linux-oracle-5.0: 5.0.0-1011.16 -proposed tracker

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

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

[Bug 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1861192
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 11. February 2020 04:07 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,signed:depwait
  replaces: bug 1861184
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1862212
  variant: debs

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

Title:
  bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

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

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

[Bug 1861190] Re: bionic/linux-oracle-5.0: 5.0.0-1011.16 -proposed tracker

2020-02-10 Thread Khaled El Mously
There are 4 bugs that are unverified against the master 5.0 tracking bug, and 
all of them don't affect this kernel. 
Manually setting VT to "Fix Released"


** Changed in: kernel-sru-workflow/verification-testing
   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/1861190

Title:
  bionic/linux-oracle-5.0: 5.0.0-1011.16 -proposed tracker

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

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

[Bug 1859561] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/Unstable] UBUNTU: SAUCE: Use native backlight on Lenovo E41-25/45

2020-02-10 Thread AaronMa
** Tags removed: verification-needed-bionic verification-needed-eoan
** Tags added: verification-done-bionic verification-done-eoan

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

Title:
  [SRU][B/OEM-B/OEM-OSP1/D/E/Unstable] UBUNTU: SAUCE: Use native
  backlight on Lenovo E41-25/45

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1859561/+subscriptions

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

[Bug 1862725] Missing required logs.

2020-02-10 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1862725

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

** 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/1862725

Title:
  Flip bionic/linux-oracle from 4.15 to 5.0

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

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

[Bug 1862224] Re: xenial/linux-gcp: 4.15.0-1054.58 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1861165
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 11. February 2020 03:42 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait
  replaces: bug 1861160
  trackers:
xenial/linux-gcp/gcp-kernel: bug 186
xenial/linux-gcp/gke-kernel: bug 1862223
  variant: debs

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

Title:
  xenial/linux-gcp: 4.15.0-1054.58 -proposed tracker

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

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

[Bug 1862546] Re: Sync qalculate-gtk 3.3.0-1 (universe) from Debian experimental (main) - Multiple bugs, instabilities and superseded data combined in outdated package of qalculate

2020-02-10 Thread Mathew Hodson
** Changed in: qalculate-gtk (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Sync qalculate-gtk 3.3.0-1 (universe) from Debian experimental (main)
  - Multiple bugs, instabilities and superseded data combined in
  outdated package of qalculate

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

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

[Bug 1862504] Re: Sync ruby-sinatra 2.0.8.1-1 (universe) from Debian unstable (main)

2020-02-10 Thread Mathew Hodson
** Changed in: ruby-sinatra (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync ruby-sinatra 2.0.8.1-1 (universe) from Debian unstable (main)

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

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

[Bug 1862725] [NEW] Flip bionic/linux-oracle from 4.15 to 5.0

2020-02-10 Thread Khaled El Mously
Public bug reported:

https://canonical.my.salesforce.com/5003z23pO6v

** Affects: kernel-sru-workflow
 Importance: Undecided
 Assignee: Khaled El Mously (kmously)
 Status: New

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

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

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

** Also affects: linux (Ubuntu Bionic)
   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/1862725

Title:
  Flip bionic/linux-oracle from 4.15 to 5.0

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

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

[Bug 1862723] Re: 18.04 can't auto load ub_iverbs (18.04.3 hwe can) for Mellanox PMD nics

2020-02-10 Thread Zhanglei Mao
in 18.04 ga-kenrel, the mellanox nic PMD would fail. after manually load
ib_uverbs, then it works fine.

2019-12-02T15:49:57.243Z|00306|netdev|WARN|dpdk-360bbd6: could not set 
configuration (Invalid argument)
2019-12-02T15:49:57.262Z|00307|dpdk|INFO|EAL: PCI device :3b:00.0 on NUMA 
socket 0
2019-12-02T15:49:57.262Z|00308|dpdk|INFO|EAL:   probe driver: 15b3:1015 net_mlx5
2019-12-02T15:49:57.262Z|00309|dpdk|ERR|net_mlx5: cannot list devices, is 
ib_uverbs loaded?
2019-12-02T15:49:57.262Z|00310|dpdk|ERR|EAL: Driver cannot attach the device 
(:3b:00.0)

In 18.04.3 hwe-kernel, the ib_uverbs is depened by ib_core which can
auto load.

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

Title:
  18.04 can't auto load ub_iverbs  (18.04.3 hwe can)  for Mellanox PMD
  nics

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

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

[Bug 1862723] [NEW] 18.04 can't auto load ub_iverbs (18.04.3 hwe can) for Mellanox PMD nics

2020-02-10 Thread Zhanglei Mao
Public bug reported:

18.04 ga-kernel to load ib_uverbs model which required by Mellanox PMD (
18.04.3 hwe can auto load via model depends)

** Affects: 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/1862723

Title:
  18.04 can't auto load ub_iverbs  (18.04.3 hwe can)  for Mellanox PMD
  nics

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

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

[Bug 1861165] Re: bionic/linux: 4.15.0-87.87 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Monday, 03. February 2020 22:37 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws: bug 1861141
bionic/linux-fips: bug 1861152
bionic/linux-gke-4.15: bug 1861145
bionic/linux-ibm-gt: bug 1861149
bionic/linux-kvm: bug 1861146
bionic/linux-oem: bug 1862013
bionic/linux-oracle: bug 1861151
bionic/linux-raspi2: bug 1861134
bionic/linux-snapdragon: bug 1861136
bionic/linux/pc-kernel: bug 1861130
bionic/linux/pc-lowlatency-kernel: bug 1861132
xenial/linux-azure: bug 1862408
-   xenial/linux-gcp: bug 1862224, bug 1861160
+   xenial/linux-gcp: bug 1861160, bug 1862224
xenial/linux-hwe: bug 1861164
  variant: debs

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

Title:
  bionic/linux: 4.15.0-87.87 -proposed tracker

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

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

[Bug 1862722] Re: call trace during crash kernel boot on Huawei server for 18.04 ga-kernel

2020-02-10 Thread Zhanglei Mao
root@node1:~# dmesg |grep -i crash
[0.00] Command line: BOOT_IMAGE=/vmlinuz-4.15.0-72-generic 
root=UUID=d9281738-de5a-4564-852e-f07c29ea4817 ro default_hugepagesz=1GB 
hugepagesz=1GB hugepages=192 transparent_hugepage=never 
solcpus=4-13,32-41,18-27,46-55 console=tty0 console=ttyS0 crashkernel=2G-:536M
[0.00] Reserving 536MB of memory at 32MB for crashkernel (System RAM: 
261726MB)
[0.00] Kernel command line: BOOT_IMAGE=/vmlinuz-4.15.0-72-generic 
root=UUID=d9281738-de5a-4564-852e-f07c29ea4817 ro default_hugepagesz=1GB 
hugepagesz=1GB hugepages=192 transparent_hugepage=never 
solcpus=4-13,32-41,18-27,46-55 console=tty0 console=ttyS0 crashkernel=2G-:536M
[   40.151040] megaraid_sas :1c:00.0: firmware crash dump   : no
root@node1:~# echo c >  /proc/sysrq-trigger 

OOM as below:

[   62.038374] Kernel panic - not syncing: Out of memory and no killable 
processes...
[   62.038374]
[   62.166809] CPU: 0 PID: 310 Comm: bcache_writebac Not tainted 
4.15.0-72-generic #81-Ubuntu
[   62.275904] Hardware name: Huawei 2288H V5/BC11SPSCB0, BIOS 6.72 04/30/2019
[   62.369545] Call Trace:
[   62.409415]  dump_stack+0x63/0x8e
[   62.459411]  panic+0xe4/0x254
[   62.505216]  ? dump_header+0x18e/0x285
[   62.560348]  out_of_memory+0x3b4/0x4e0
[   62.615663]  __alloc_pages_slowpath+0xa53/0xe00
[   62.680115]  __alloc_pages_nodemask+0x29a/0x2c0
[   62.744505]  alloc_pages_current+0x6a/0xe0
[   62.803676]  bio_alloc_pages+0x42/0x90
[   62.858710]  read_dirty+0x211/0x370 [bcache]
[   62.919965]  bch_writeback_thread+0x518/0x5a0 [bcache]
[   62.991622]  kthread+0x121/0x140
[   63.040709]  ? read_dirty+0x370/0x370 [bcache]
[   63.104073]  ? kthread_create_worker_on_cpu+0x70/0x70
[   63.174627]  ret_from_fork+0x35/0x40
[   63.227373] Kernel Offset: 0x1be0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[   63.512588] ---[ end Kernel panic - not syncing: Out of memory and no 
killable processes...
[   63.512588] 

--
call trace when memory set 576M or 1024M,  below is only one of cpu's call 
trace. 

-
[ 2407.794096] [ cut here ]
[ 2407.855674] sched: Unexpected reschedule of offline CPU#12!
[ 2407.928663] WARNING: CPU: 25 PID: 859240 at 
/build/linux-E6MDAa/linux-4.15.0/arch/x86/kernel/smp.c:128 
native_smp_send_reschedule+0x3a/0x40
[ 2408.091827] Modules linked in: vsock_diag vsock sctp_diag sctp dccp_diag 
dccp tcp_diag udp_diag raw_diag inet_diag unix_diag ip6t_REJECT nf_reject_ipv6 
nf_log_ipv6 xt_hl ip6t_rt ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common 
xt_LOG xt_limit xt_addrtype xt_conntrack binfmt_misc veth ip6table_nat 
ipt_MASQUERADE nf_nat_masquerade_ipv4 xt_CHECKSUM xt_comment xt_tcpudp 
iptable_nat iptable_mangle ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter br_netfilter openvswitch nsh nf_conntrack_ipv6 nf_nat_ipv6 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_defrag_ipv6 nf_nat nf_conntrack 
8021q garp mrp bonding bridge stp llc nls_iso8859_1 intel_rapl skx_edac 
x86_pkg_temp_thermal coretemp kvm_intel kvm irqbypass intel_cstate 
intel_rapl_perf joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler
[ 2408.996649]  ioatdma mei_me mei lpc_ich shpchp dca acpi_power_meter mac_hid 
sch_fq_codel sunrpc ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi 
scsi_transport_iscsi ib_uverbs ip_tables x_tables autofs4 btrfs zstd_compress 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib ses enclosure ib_core 
bcache scsi_transport_sas crct10dif_pclmul crc32_pclmul hid_generic 
ghash_clmulni_intel mlx5_core pcbc usbhid aesni_intel mlxfw i40e aes_x86_64 
devlink crypto_simd glue_helper ptp cryptd megaraid_sas pps_core hid
[ 2409.673608] CPU: 25 PID: 859240 Comm: bash Tainted: G  D W
4.15.0-72-generic #81-Ubuntu
[ 2409.790640] Hardware name: Huawei 2288H V5/BC11SPSCB0, BIOS 6.72 04/30/2019
[ 2409.883892] RIP: 0010:native_smp_send_reschedule+0x3a/0x40
[ 2409.959545] RSP: 0018:9e6aff0c33f0 EFLAGS: 00010082
[ 2410.032027] RAX:  RBX: 9e3b00be5940 RCX: 0006
[ 2410.127442] RDX: 0007 RSI: 0086 RDI: 9e6aff0d6490
[ 2410.222848] RBP: 9e6aff0c33f0 R08: 10c3 R09: 00cdcdcd
[ 2410.318270] R10: 9e6aff0c33d0 R11:  R12: 9e3b00be646c
[ 2410.413691] R13: 0004 R14: 0046 R15: 00021840
[ 2410.509055] FS:  7f3782413740() GS:9e6aff0c() 
knlGS:
[ 2410.615957] CS:  0010 DS:  ES:  CR0: 80050033
[ 2410.694883] CR2:  CR3: 002386e38002 CR4: 007606e0
[ 2410.790525] DR0:  DR1:  DR2: 
[ 2411.064749]  
[ 2411.099165]  try_to_wake_up+0x3ea/0x4a0
[ 2411.346254]  __wake_up_locked+0x16/0x20
[ 

[Bug 1862722] [NEW] call trace during crash kernel boot on Huawei server for 18.04 ga-kernel

2020-02-10 Thread Zhanglei Mao
Public bug reported:

To configure kernel crash dump, if memory is less than 576M, it would
get oom and to configure crashkernel=2G-:576M, it would get call trace.

** Affects: 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/1862722

Title:
  call trace during crash kernel boot on Huawei server for 18.04 ga-
  kernel

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

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

[Bug 1862720] Re: kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel

2020-02-10 Thread Tom Reynolds
"I/O error, dev sdb, sector 82830936 flags 0" would seem to suggest this
is a hardware error (physically defective storage media sdb), have you
ruled this out, yet?

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

Title:
  kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel

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

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

[Bug 1862720] Missing required logs.

2020-02-10 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1862720

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** 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/1862720

Title:
  kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel

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

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

[Bug 1862720] [NEW] kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel

2020-02-10 Thread Zhanglei Mao
Public bug reported:

coping data get io error

[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Started Availability of block devices.
[  185.379378] kdump-tools[1695]: Starting kdump-tools:  * running makedumpfile 
-c -d 31 /proc/vmcore /var/crash/201912310519/dump-incomplete
Copying data  :[  421.979156] 
print_req_error: I/O error, dev sdb, sector 82830936 flags 0
 [ 54.8 %] |[  422.081318] bcache: bch_count_io_errors() sdb1: IO error on 
reading from cache, recovering.

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


** Tags: 18.04.3 hwe-kernel

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

Title:
  kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel

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

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

[Bug 1862720] Re: kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel

2020-02-10 Thread Zhanglei Mao
ubuntu@infra1:~$ sudo lsblk
NAME  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0   7:00  93.1G  0 loop 
/var/lib/lxd/storage-pools/default
sda 8:00   1.1T  0 disk
├─sda1  8:10   512M  0 part /boot/efi
└─sda2  8:20   1.1T  0 part
  ├─infra1--vg-root   253:00   1.1T  0 lvm  /
  └─infra1--vg-swap_1 253:10   976M  0 lvm  [SWAP]
sdb 8:16   0 557.9G  0 disk
sdc 8:32   0 557.9G  0 disk
ubuntu@infra1:~$ df -h
Filesystem   Size  Used Avail Use% Mounted on
udev 126G 0  126G   0% /dev
tmpfs 26G  2.4M   26G   1% /run
/dev/mapper/infra1--vg-root  1.1T  313G  729G  31% /
tmpfs126G   54M  126G   1% /dev/shm
tmpfs5.0M 0  5.0M   0% /run/lock
tmpfs126G 0  126G   0% /sys/fs/cgroup
/dev/sda1511M  6.1M  505M   2% /boot/efi
tmpfs100K 0  100K   0% /var/lib/lxd/shmounts
tmpfs100K 0  100K   0% /var/lib/lxd/devlxd
/dev/loop094G  6.2G   86G   7% 
/var/lib/lxd/storage-pools/default
tmpfs 26G 0   26G   0% /run/user/1000
ubuntu@infra1:~$ cd /var/crash/
ubuntu@infra1:/var/crash$ ls -lhs
total 8.7M
8.7M -rw-r- 1 bind bind 8.7M Dec 24 05:39 _usr_sbin_named.115.crash
ubuntu@infra1:/var/crash$ 

root@node1:~# kdump-config show
DUMP_MODE:kdump
USE_KDUMP:1
KDUMP_SYSCTL: kernel.panic_on_oops=1
KDUMP_COREDIR:/var/crash
crashkernel addr: 0x400
   /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.0.0-37-generic
kdump initrd:
   /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-5.0.0-37-generic
current state:ready to kdump

kexec command:
  /sbin/kexec -p --command-line="BOOT_IMAGE=/vmlinuz-5.0.0-37-generic 
root=UUID=d9281738-de5a-4564-852e-f07c29ea4817 ro default_hugepagesz=1GB 
transparent_hugepage=never solcpus=4-13,32-41,18-27,46-55 console=tty0 
console=ttyS0 systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb 
ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img 
/var/lib/kdump/vmlinuz
root@node1:~# dmesg |grep -i crash
[0.00] Command line: BOOT_IMAGE=/vmlinuz-5.0.0-37-generic 
root=UUID=d9281738-de5a-4564-852e-f07c29ea4817 ro default_hugepagesz=1GB 
hugepagesz=1GB hugepages=192 transparent_hugepage=never 
solcpus=4-13,32-41,18-27,46-55 console=tty0 console=ttyS0 crashkernel=2G-:512M
[0.02] Reserving 512MB of memory at 64MB for crashkernel (System RAM: 
261726MB)
[1.921643] Kernel command line: BOOT_IMAGE=/vmlinuz-5.0.0-37-generic 
root=UUID=d9281738-de5a-4564-852e-f07c29ea4817 ro default_hugepagesz=1GB 
hugepagesz=1GB hugepages=192 transparent_hugepage=never 
solcpus=4-13,32-41,18-27,46-55 console=tty0 console=ttyS0 crashkernel=2G-:512M
[   73.044719] pstore: Using crash dump compression: deflate
[   79.287259] megaraid_sas :1c:00.0: firmware crash dump   : no
root@node1:~# 

[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Started Availability of block devices.
[  185.379378] kdump-tools[1695]: Starting kdump-tools:  * running makedumpfile 
-c -d 31 /proc/vmcore /var/crash/201912310519/dump-incomplete
Copying data  :[  421.979156] 
print_req_error: I/O error, dev sdb, sector 82830936 flags 0
 [ 54.8 %] |[  422.081318] bcache: bch_count_io_errors() sdb1: IO error on 
reading from cache, recovering.
C[  422.203707] Read-error on swap-device (8:0:4709320)
opying data [  422.284891] print_req_error: I/O error, dev sdb, sector 
61463240 flags 0
[  422.386425] bcache: bch_count_io_errors() sdb1: IO error on 
reading from cache, recovering.
[  422.508953] Read-error on swap-device (8:0:2743136)
 : [ 55.2 %] \  [  422.589689] print_req_error: I/O error, dev sdb, sector 
4070592 flags 80700
eta: 19s[  422.695501] bcache: bch_count_io_errors() sdb1: IO error on 
reading from cache, recovering.
Copying data   [  422.818144] print_req_error: I/O error, dev sdb, sector 
4070744 flags 80700
[  422.924145] bcache: bch_count_io_errors() sdb1: IO error on 
reading from cache, recovering.
[  423.047007] print_req_error: I/O error, dev sda, sector 
23649960 flags 80700
   : [ 55.6 %] -[  423.154494] print_req_error: I/O error, dev sda, sector 
23650112 flags 80700
  eta: 1[  423.263750] print_req_error: I/O error, dev sdb, sector 
65443209 flags 1001
Copying data [  423.367832] bcache: bch_count_io_errors() sdb1: IO error on 
writing btree.
[  423.473080] print_req_error: I/O error, dev sdb, sector 
4070712 flags 0
[  423.575254] bcache: bch_count_io_errors() sdb1: IO error on 
reading from cache, recovering.
 : [ 56.0 %][  423.698447] print_req_error: I/O error, dev sda, 

[Bug 1856008] Re: openssh-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is not installed

2020-02-10 Thread Launchpad Bug Tracker
[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]

** Changed in: openssh (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  openssh-server: Depends: openssh-client (= 1:8.0p1-6build1) but it is
  not installed

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

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

[Bug 1856081] Re: /usr/lib/ubuntu-advantage/apt-esm-hook causes Seg Fault

2020-02-10 Thread Launchpad Bug Tracker
[Expired for ubuntu-advantage-tools (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  /usr/lib/ubuntu-advantage/apt-esm-hook causes Seg Fault

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

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

[Bug 1856189] Re: Trying to delete a printer will fill up the filesystem with logmessages

2020-02-10 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Trying to delete a printer will fill up the filesystem with
  logmessages

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

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

[Bug 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-lrm
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-lrm
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Fix Committed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1861192
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Packaging
- phase-changed: Tuesday, 11. February 2020 03:22 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Tuesday, 11. February 2020 04:07 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-lrm: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,signed:depwait
  replaces: bug 1861184
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1862212
  variant: debs

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

Title:
  bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

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

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

[Bug 1862312] Re: Segmentation fault (kernel oops) with memory-hotplug in ubuntu_kernel_selftests on Bionic kernel

2020-02-10 Thread Po-Hsu Lin
Issue NOT spotted on 4.15 GKE (4.15.0-1051.54), X-4.15 GCP
(4.15.0-1053.57)

Spotted on B-4.15 AWS (4.15.0-1059.61) with instance r5.large

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

Title:
  Segmentation fault (kernel oops) with memory-hotplug in
  ubuntu_kernel_selftests on Bionic kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862312/+subscriptions

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

[Bug 1861141] Re: bionic/linux-aws: 4.15.0-1059.61 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861165
  packages:
lrm: linux-restricted-modules-aws
main: linux-aws
meta: linux-meta-aws
  phase: Testing
  phase-changed: Monday, 03. February 2020 23:56 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
+   regression-testing: Stalled -- testing FAILED
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-aws-fips: bug 1861139
bionic/linux-aws/aws-kernel: bug 1861138
xenial/linux-aws-hwe: bug 1861140
  variant: debs

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

Title:
  bionic/linux-aws: 4.15.0-1059.61 -proposed tracker

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

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

[Bug 1861457] Re: pyroute2 0.5.2 doesn't support neutron-common 14.0.4

2020-02-10 Thread Jason Hobbs
I tested with the package from stein-proposed (python3-pyroute2
0.5.4-0ubuntu0.19.04.1~cloud1) and got successful results. The issue I
was seeing in bug 1862200 is no longer occurring. I'm marking this
verification-stein-done.

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

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

Title:
  pyroute2 0.5.2 doesn't support neutron-common 14.0.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-neutron-gateway/+bug/1861457/+subscriptions

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

[Bug 1861141] Re: bionic/linux-aws: 4.15.0-1059.61 -proposed tracker

2020-02-10 Thread Po-Hsu Lin
Marked as Incomplete for possible regression (bug 1862312)

** Changed in: kernel-sru-workflow/regression-testing
   Status: Fix Released => Incomplete

** Tags removed: regression-testing-passed

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

Title:
  bionic/linux-aws: 4.15.0-1059.61 -proposed tracker

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

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

[Bug 1862224] Re: xenial/linux-gcp: 4.15.0-1054.58 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Fix Committed => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1861165
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Packaging
- phase-changed: Tuesday, 11. February 2020 02:56 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Tuesday, 11. February 2020 03:42 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
main:building,signed:depwait
  replaces: bug 1861160
  trackers:
xenial/linux-gcp/gcp-kernel: bug 186
xenial/linux-gcp/gke-kernel: bug 1862223
  variant: debs

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

Title:
  xenial/linux-gcp: 4.15.0-1054.58 -proposed tracker

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

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

[Bug 1860387] Re: [Asus ZenBook UX534FTC, Realtek ALC294, Mic, Internal] No sound at all

2020-02-10 Thread Po-Hsu Lin
Hi,
please follow instructions here:
https://wiki.ubuntu.com/Kernel/KernelBootParameters
https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter

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

Title:
   [Asus ZenBook UX534FTC, Realtek ALC294, Mic, Internal] No sound at
  all

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

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

[Bug 1862714] Re: package libdleyna-core-1.0-5 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libdleyna-core-1.0.so.5.0.0', which is also in package libdleyn

2020-02-10 Thread Alex Murray
Fixed it for now by doing:

sudo apt purge dleyna-server libdleyna-core-1.0-3 libdleyna-core-1.0-5
sudo apt install dleyna-server

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

Title:
  package libdleyna-core-1.0-5 (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu
  /libdleyna-core-1.0.so.5.0.0', which is also in package libdleyna-
  core-1.0-3:amd64 0.6.0-1

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

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

[Bug 1861147] Re: No fc connect after update from 4.15.0-72 to 4.15.0-76

2020-02-10 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: 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/1861147

Title:
  No fc connect after update from 4.15.0-72 to 4.15.0-76

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

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

[Bug 1861202] Re: bionic/linux-gcp-5.3: 5.3.0-1012.13~18.04.1 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: In Progress => Fix Released

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1861205
  packages:
lrm: linux-restricted-modules-gcp-5.3
main: linux-gcp-5.3
meta: linux-meta-gcp-5.3
signed: linux-signed-gcp-5.3
  phase: Testing
  phase-changed: Wednesday, 05. February 2020 12:42 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  bionic/linux-gcp-5.3: 5.3.0-1012.13~18.04.1 -proposed tracker

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

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

[Bug 1862407] Re: trusty/linux-azure: 4.15.0-1070.75~14.04.1 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
+ boot-testing-requested: true
  kernel-stable-master-bug: 1862408
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Holding before Promote to Proposed
  phase-changed: Monday, 10. February 2020 23:28 UTC
  reason:
-   promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait
+   promote-to-proposed: Holding -- master bug not ready for proposed
  variant: debs

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

Title:
  trusty/linux-azure: 4.15.0-1070.75~14.04.1 -proposed tracker

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

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

[Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

2020-02-10 Thread Hui Wang
For 18.04 and 19.10, the alsa-lib only supports ucm, Intel audio team
write the ucm confs and this is sth I plan to SRU to Eoan and Bionic in
this bug.

For 20.04, we choose alsa-lib-1.2.1.2, it supports ucm2, and upstream
writes the ucm2 confs based on the Intel audio team's work, we use
#1862505 to track it.

So the ucm for bionic and eoan is not backported from ucm2 of 1.2.1.2,
it is maintained by Intel: https://github.com/thesofproject/alsa-ucm-
conf.git

the ucm2 for focal is maintained by upstream: https://github.com/alsa-
project/alsa-ucm-conf.git, it is written based on the Intel's work.

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

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

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

[Bug 1862708] Re: tracing doesn't work on focal

2020-02-10 Thread Seth Arnold
** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

2020-02-10 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  kernel-stable-master-bug: 1861192
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
- phase: Ready for Packaging
- phase-changed: Thursday, 06. February 2020 17:12 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 11. February 2020 03:22 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-lrm: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  replaces: bug 1861184
  trackers:
bionic/linux-gcp/gcp-kernel: bug 1862212
  variant: debs

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

Title:
  bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

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

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

[Bug 1862717] Re: Automatic crash report bug reports opened in gedit rather than the browser

2020-02-10 Thread Alex Murray
Relevant parts from journalctl:

Feb 11 13:03:53 slate systemd[6652]: Starting Notification regarding a crash 
report...
Feb 11 13:03:53 slate update-notifier-crash[260823]: /usr/bin/whoopsie
Feb 11 13:03:54 slate update-notifier-crash[260837]: /var/crash/libdleyna-core-1
Feb 11 13:04:19 slate systemd[6652]: update-notifier-crash.service: Succeeded.
Feb 11 13:04:19 slate systemd[6652]: Started Notification regarding a crash 
report.
Feb 11 13:05:51 slate polkitd(authority=local)[2853]: Operator of 
unix-session:2 successfully authenticated as unix-user:amurray to gain ONE-SHOT 
authorization for action com.ubuntu.apport.apport-gtk-root for 
unix-process:6652:3047 [/lib/systemd/systemd --user] (>
Feb 11 13:05:51 slate pkexec[264867]: pam_unix(polkit-1:session): session 
opened for user root by (uid=1000)
Feb 11 13:05:51 slate pkexec[264867]: amurray: Executing command [USER=root] 
[TTY=unknown] [CWD=/home/amurray] [COMMAND=/usr/share/apport/apport-gtk]
Feb 11 13:05:51 slate systemd[6652]: Starting Notification regarding a crash 
report...
Feb 11 13:05:51 slate update-notifier-crash[265049]: /usr/bin/whoopsie
Feb 11 13:05:51 slate systemd[6652]: update-notifier-crash.service: Succeeded.
Feb 11 13:05:51 slate systemd[6652]: Started Notification regarding a crash 
report.
Feb 11 13:05:57 slate systemd[6652]: Starting Notification regarding a crash 
report...
Feb 11 13:05:57 slate update-notifier-crash[265340]: /usr/bin/whoopsie
Feb 11 13:05:58 slate systemd[6652]: update-notifier-crash.service: Succeeded.
Feb 11 13:05:58 slate systemd[6652]: Started Notification regarding a crash 
report.
Feb 11 13:06:13 slate systemd[6652]: Starting Notification regarding a crash 
report...
Feb 11 13:06:13 slate update-notifier-crash[265816]: /usr/bin/whoopsie
Feb 11 13:06:14 slate systemd[6652]: update-notifier-crash.service: Succeeded.
Feb 11 13:06:14 slate systemd[6652]: Started Notification regarding a crash 
report.
Feb 11 13:06:17 slate whoopsie[5815]: [13:06:17] Parsing 
/var/crash/libdleyna-core-1.0-5.0.crash.
Feb 11 13:06:17 slate systemd[6652]: Starting Notification regarding a crash 
report...
Feb 11 13:06:17 slate whoopsie[5815]: [13:06:17] Uploading 
/var/crash/libdleyna-core-1.0-5.0.crash.
Feb 11 13:06:17 slate update-notifier-crash[265873]: /usr/bin/whoopsie
Feb 11 13:06:17 slate systemd[6652]: update-notifier-crash.service: Succeeded.
Feb 11 13:06:17 slate systemd[6652]: Started Notification regarding a crash 
report.
Feb 11 13:06:20 slate whoopsie[5815]: [13:06:20] Sent; server replied with: No 
error
Feb 11 13:06:20 slate whoopsie[5815]: [13:06:20] Response code: 200
Feb 11 13:06:20 slate whoopsie[5815]: [13:06:20] Reported OOPS ID 
4948a47e-4c77-11ea-a966-fa163e983629
Feb 11 13:06:20 slate systemd[6652]: Starting Notification regarding a crash 
report...
Feb 11 13:06:20 slate update-notifier-crash[265936]: /usr/bin/whoopsie
Feb 11 13:06:20 slate systemd[6652]: update-notifier-crash.service: Succeeded.
Feb 11 13:06:20 slate systemd[6652]: Started Notification regarding a crash 
report.
Feb 11 13:06:24 slate sudo[266010]: root : TTY=unknown ; PWD=/root ; 
USER=amurray ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus ; 
COMMAND=/usr/bin/xdg-open 
https://bugs.launchpad.net/ubuntu/+source/dleyna-core/+filebug/4bc4c494-4c77-11ea-b34a-00>
Feb 11 13:06:24 slate sudo[266010]: pam_unix(sudo:session): session opened for 
user amurray by (uid=0)
Feb 11 13:06:28 slate dbus-daemon[6678]: [session uid=1000 pid=6678] Activating 
service name='org.gnome.gedit' requested by ':1.258' (uid=1000 pid=266018 
comm="gio open https://bugs.launchpad.net/ubuntu/+source; label="unconfined")
Feb 11 13:06:28 slate dbus-daemon[6678]: [session uid=1000 pid=6678] 
Successfully activated service 'org.gnome.gedit'
Feb 11 13:06:31 slate gedit[266061]: can't init metadata tree 
/home/amurray/.local/share/gvfs-metadata/http:uri=https%3A%2F%2Fbugs.launchpad.net%2Fubuntu%2F+source%2Fdleyna-core%2F+filebug%2F4bc4c494-4c77-11ea-b34a-002481e7f48a%3Ffield.title%3Dpackage+libdleyna-c>
Feb 11 13:06:31 slate sudo[266010]: pam_unix(sudo:session): session closed for 
user amurray

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

Title:
  Automatic crash report bug reports opened in gedit rather than the
  browser

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

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

[Bug 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

2020-02-10 Thread Khaled El Mously
** Summary changed:

- bionic/linux-gcp:  -proposed tracker
+ bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-lrm
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-lrm
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El 
Mously (kmously)

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

Title:
  bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker

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

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

[Bug 1862708] UdevDb.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1862708/+attachment/5327198/+files/UdevDb.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] PulseList.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327196/+files/PulseList.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] RfKill.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1862708/+attachment/5327197/+files/RfKill.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] WifiSyslog.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327199/+files/WifiSyslog.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] Card0.Codecs.codec.2.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Card0.Codecs.codec.2.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327185/+files/Card0.Codecs.codec.2.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] ProcModules.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327195/+files/ProcModules.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] Card1.Amixer.values.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Card1.Amixer.values.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327186/+files/Card1.Amixer.values.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] PciMultimedia.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327192/+files/PciMultimedia.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] Card0.Amixer.values.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Card0.Amixer.values.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327183/+files/Card0.Amixer.values.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] Lspci.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1862708/+attachment/5327188/+files/Lspci.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] ProcInterrupts.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327194/+files/ProcInterrupts.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] ProcCpuinfoMinimal.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327193/+files/ProcCpuinfoMinimal.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] Lsusb-v.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327191/+files/Lsusb-v.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] Lsusb-t.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327190/+files/Lsusb-t.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] CurrentDmesg.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327187/+files/CurrentDmesg.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] Lsusb.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1862708/+attachment/5327189/+files/Lsusb.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] Card0.Codecs.codec.0.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "Card0.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327184/+files/Card0.Codecs.codec.0.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862715] Re: mac mini late 2009 usb 2.0 devices detected as 1.0, run slow

2020-02-10 Thread Andrew M.
this apparently affects only a few devices, let me collect more info and
reopen

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

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

Title:
  mac mini late 2009 usb 2.0 devices detected as 1.0, run slow

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

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

[Bug 1862708] ArecordDevices.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "ArecordDevices.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327181/+files/ArecordDevices.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862712] Re: change the ASoC card name and card longname to meet the requirement of alsa-lib-1.2.1 (Focal)

2020-02-10 Thread Hui Wang
** Description changed:

- In the ubuntu-20.04, we integrate the alsa-lib-1.2.1.2, and the ucm for
- this version is alsa-ucm-conf-1.2.1.2, in this package, the ucm2 folder
- is named by changed card name and longname (patches are in the
- v5.5-rc1).
+ In the ubuntu-20.04, we integrate the alsa-lib-1.2.1.2, and from the
+ alsa-lib-1.2.1, the ucm is put into a standalone package alsa-ucm-conf,
+ and from the 1.2.1, the alsa-lib supports the ucm2.
  
- To make the focal kernel work with alsa-lib-1.2.1.2, we need to backport
- those patches.
+ In the alsa-ucm-conf-1.2.1.2, the ucm2 folders are named by new
+ card name or longname, kernel-v5.5-rc1 has patches to change those
+ names to new names. now we backport them to focal kernel.
+ 
+ [Impact]
+ booting with the focal kernel, the audio driver can't find the ucm2
+ confs, that is becuase alsa-lib-1.2.1 requires new cardname and long
+ name, but focal kernel provides the old card names.
+ 
+ [Fix]
+ backport 3 patches from v5.5-rc1.
+ 
+ 
+ [Test Case]
+ install the 20.04 daily build image, install the linux-firmware and
+ alsa-ucm-conf, booting with the kernel which have those 3 patches,
+ the alsa-lib could find the correct ucm2 confs.
+ 
+ [Regression Risk]
+ It is low risk to focal.
+ If users install focal kernel to bionic or disco, it will break
+ the audio since the ucm in the bionic and disco still follow the old
+ card name and longname, we need to link a new copy ucm named by new
+ cardname or longname in the bionic and disco.

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

Title:
  change the ASoC card name and card longname to meet the requirement of
  alsa-lib-1.2.1 (Focal)

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

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

[Bug 1862708] CRDA.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1862708/+attachment/5327182/+files/CRDA.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862708] Re: tracing doesn't work on focal

2020-02-10 Thread Seth Arnold
apport information

** Tags added: apport-collected

** Description changed:

  Hello, while investigating bug 1861359 I tried to use kprobe-perf to
  troubleshoot and found that tracing doesn't work on focal:
  
  # kprobe-perf -s 'p:shrink_node'
  ERROR: func shrink_node not in 
/sys/kernel/debug/tracing/available_filter_functions.
  Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to 
override.
  # ls -l /sys/kernel/debug/tracing/available_filter_functions
  ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No 
such file or directory
  # find /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing
  /sys/kernel/debug/tracing/instances
  /sys/kernel/debug/tracing/trace_stat
  /sys/kernel/debug/tracing/per_cpu
  /sys/kernel/debug/tracing/per_cpu/cpu7
  /sys/kernel/debug/tracing/per_cpu/cpu6
  /sys/kernel/debug/tracing/per_cpu/cpu5
  /sys/kernel/debug/tracing/per_cpu/cpu4
  /sys/kernel/debug/tracing/per_cpu/cpu3
  /sys/kernel/debug/tracing/per_cpu/cpu2
  /sys/kernel/debug/tracing/per_cpu/cpu1
  /sys/kernel/debug/tracing/per_cpu/cpu0
  /sys/kernel/debug/tracing/options
  
  
  I'm guessing this is due to lockdown:
  
  # dmesg | grep -C2 -i lockdown
  [0.00] efi:  TPMFinalLog=0x9ff92000  SMBIOS=0x9f05d000  SMBIOS 
3.0=0x9f05a000  ACPI=0x9fffe000  ACPI 2.0=0x9fffe014  ESRT=0x9eee7000  
MEMATTR=0x99c76018  TPMEventLog=0x931f7018 
  [0.00] secureboot: Secure boot enabled
  [0.00] Kernel is locked down from EFI Secure Boot mode; see man 
kernel_lockdown.7
  [0.00] SMBIOS 3.0.0 present.
  [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 
11/25/2019
  --
  [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter
  [0.534731] clocksource: Switched to clocksource tsc-early
  [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534737] Could not create tracefs 'available_events' entry
  [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534741] Could not create tracefs 'set_event' entry
  [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534743] Could not create tracefs 'available_tracers' entry
  [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534745] Could not create tracefs 'current_tracer' entry
  [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534746] Could not create tracefs 'tracing_cpumask' entry
  [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534747] Could not create tracefs 'trace_options' entry
  [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534748] Could not create tracefs 'trace' entry
  [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534750] Could not create tracefs 'trace_pipe' entry
  [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534751] Could not create tracefs 'buffer_size_kb' entry
  [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534752] Could not create tracefs 'buffer_total_size_kb' entry
  [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534754] Could not create tracefs 'free_buffer' entry
  [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534755] Could not create tracefs 'trace_marker' entry
  [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534783] Could not create tracefs 'trace_marker_raw' entry
  [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534784] Could not create tracefs 'trace_clock' entry
  [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534785] Could not create tracefs 'tracing_on' entry
  [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534786] Could not create tracefs 'timestamp_mode' entry
  [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534788] Could not create tracefs 'buffer_percent' entry
  [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534817] Could not create tracefs 'print-parent' entry
  [0.534817] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534818] Could not create tracefs 'sym-offset' entry
  [0.534819] Lockdown: swapper/0: use of tracefs is restricted; see man 
kernel_lockdown.7
  [0.534819] Could not create tracefs 'sym-addr' entry
  [0.534820] 

[Bug 1862708] AplayDevices.txt

2020-02-10 Thread Seth Arnold
apport information

** Attachment added: "AplayDevices.txt"
   
https://bugs.launchpad.net/bugs/1862708/+attachment/5327180/+files/AplayDevices.txt

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

Title:
  tracing doesn't work on focal

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

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

[Bug 1862717] [NEW] Automatic crash report bug reports opened in gedit rather than the browser

2020-02-10 Thread Alex Murray
Public bug reported:

If a crash report is triggered automatically (say from a program crash
etc) then the Apport UI pops up asking whether to report this - if I
choose to proceed, after about 30 seconds gedit pops up with a HTML
document showing 'OpenID transaction in progress' - which is the
login.launchpad.net openid page. Looking at the gedit document title
this shows the URL which should have got loaded by firefox - and so it
appears that gedit has been spawned instead of firefox to handle the
xdg-open call to report the bug.

>From journalctl I can see that it is root spawning this xdg-open call:

Feb 11 13:06:24 slate sudo[266010]: root : TTY=unknown ; PWD=/root ;
USER=amurray ; ENV=DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
; COMMAND=/usr/bin/xdg-open https://bugs.launchpad.net/ubuntu/+source
/dleyna-core/+filebug/4bc4c494-4c77-11ea-b34a-
002481e7f48a?field.title=package+libdleyna-
core-1.0-5+%28not+installed%29+failed+to+install%2Fupgrade%3A+trying+to+overwrite+%27%2Fusr%2Flib%2Fx86_64
-linux-gnu%2Flibdleyna-core-1.0.so.5.0.0%27%2C+which+is+also+in+package
+libdleyna-core-1.0-3%3Aamd64+0.6.0-1

And so I wonder if it is something to do with root's configuration for
preferred applications (or not...)

This does not occur when running ubuntu-bug from a terminal (since I
assume in this case, the xdg-open call ends up coming from the users'
own session).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: apport 2.20.11-0ubuntu16
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportLog:
 
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 11 13:34:42 2020
InstallationDate: Installed on 2019-11-18 (84 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to focal on 2020-01-22 (19 days ago)

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


** Tags: amd64 apport-bug focal

** Attachment added: "gedit with the crash report"
   
https://bugs.launchpad.net/bugs/1862717/+attachment/5327200/+files/Screenshot%20from%202020-02-11%2013-42-40.png

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

Title:
  Automatic crash report bug reports opened in gedit rather than the
  browser

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

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

[Bug 1855992] Re: Enable GVE network driver for GCP kernels

2020-02-10 Thread Khaled El Mously
** Changed in: linux-gcp (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Changed in: linux-gcp (Ubuntu Bionic)
   Status: New => 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/1855992

Title:
  Enable GVE network driver for GCP kernels

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

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

[Bug 1862312] Re: Segmentation fault (kernel oops) with memory-hotplug in ubuntu_kernel_selftests on Bionic kernel

2020-02-10 Thread Po-Hsu Lin
Thanks! I will try, but this issue was not spotted in our general kernel
testing with the node we use (node rizzo). Thus it might take some time
to find out an affected node first.

You can run this with the source tree:
$ make -C tools/testing/selftests TARGETS=memory-hotplug run_tests

Ref: https://www.kernel.org/doc/html/v4.15/dev-tools/kselftest.html

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

Title:
  Segmentation fault (kernel oops) with memory-hotplug in
  ubuntu_kernel_selftests on Bionic kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862312/+subscriptions

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

[Bug 1862715] Re: mac mini late 2009 usb 2.0 devices detected as 1.0, run slow

2020-02-10 Thread Andrew M.
** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862715/+attachment/5327176/+files/dmesg.txt

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

Title:
  mac mini late 2009 usb 2.0 devices detected as 1.0, run slow

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

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

[Bug 1862716] [NEW] maven is not able to resolve dependencies and is not able to read or transfer artifacts while building android source code (cyanogenmod 13)

2020-02-10 Thread Ved Malandkar
Public bug reported:

I was building cyanogenmod 13 for my Blu Studio G2. First, I ran lunch 
cm_d5170_blu_gmo-userdebug, this told the source code to build for 
cm_d5170_blu_gmo-userdebug whenever a command like make or something similar 
was ran. Then, I ran brunch cm_d5170_blu_gmo-userdebug, this ran the make 
command on the source code. The command gave this error output when it had to 
run maven (I was expecting this to download whatever the command wanted):
--
[ERROR] Plugin org.apache.maven.plugins:maven-dependency-plugin:2.10 or one of 
its dependencies could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-dependency-plugin:jar:2.10: Could not transfer 
artifact org.apache.maven.plugins:maven-plugins:pom:27 from/to central 
(https://repo.maven.apache.org/maven2): Transfer failed for 
https://repo.maven.apache.org/maven2/org/apache/maven/plugins/maven-plugins/27/maven-plugins-27.pom:
 Received fatal alert: protocol_version -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
--

Ubuntu Version: Ubuntu Focal Fossa (20.04 LTS)
maven:
  Installed: 3.6.3-1
  Candidate: 3.6.3-1
  Version table:
 *** 3.6.3-1 500
500 http://us.archive.ubuntu.com/ubuntu focal/universe amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu focal/universe i386 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: maven 3.6.3-1
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu16
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 10 21:33:38 2020
InstallationDate: Installed on 2020-01-27 (14 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: maven
UpgradeStatus: Upgraded to focal on 2020-02-09 (1 days ago)

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


** Tags: amd64 apport-bug focal

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

Title:
  maven is not able to resolve dependencies and is not able to read or
  transfer artifacts while building android source code (cyanogenmod 13)

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

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

[Bug 1854841] Re: [SRU] Update to containerd 1.3.1

2020-02-10 Thread Launchpad Bug Tracker
This bug was fixed in the package containerd - 1.3.2-0ubuntu1

---
containerd (1.3.2-0ubuntu1) focal; urgency=medium

  [ Tianon Gravi ]
  * Use "sed" to adjust upstream's service file ExecStart value
  * Update to 1.3.2 upstream release

  [ Michael Hudson-Doyle ]
  * d/patches/preserve-debug-info.patch: generate binaries with debug info in
them so we still get ddebs.

 -- Michael Hudson-Doyle   Tue, 11 Feb 2020
12:29:51 +1300

** Changed in: containerd (Ubuntu)
   Status: Triaged => 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/1854841

Title:
  [SRU] Update to containerd 1.3.1

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

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

  1   2   3   4   5   6   >