date:20200422

The Error Tracker bucket last shows this happening on Ubuntu 16.04 LTS.
Is anybody experiencing this on a recent release of Ubuntu?

** Changed in: apport (Ubuntu)
Milestone: ubuntu-15.10 => None

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

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

Title:
  Apport-kde crash when reporting bugs

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Incomplete
Status in apport source package in Vivid:
  Won't Fix

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.17-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/1b2e1c9cdac684074f5f97db85ae78c1b8a2b3ac
  contains more details.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874178] Re: Unlocking existing session needs two attempts after selecting Switch User

2020-04-22 Thread Sean Davis

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

** Changed in: lightdm (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Unlocking existing session needs two attempts after selecting Switch
  User

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  This has been occurring during the Xubuntu post-install test. It's not
  the same as Bug #1776475, as it's not necessary to have logged in as
  another user (or even for another user to exist) for the problem to
  happen.

  My sequence of actions is:

  *Create new user.
  *Open a program (usually Thunar or Terminal).
  *Lock session.
  *Click on "Switch User". <-- This is all that's necessary to trigger it.
  *Enter password to unlock my own session.
  *Then there's a delay and screen goes black, then the unlock prompt appears 
again.
  *The second time, my session unlocks.

  This particular report is from a QEMU/KVM vm, but it's also been
  happening on a bare-metal install.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 22 15:30:29 2020
  InstallationDate: Installed on 2020-04-22 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1858802] Re: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device

2020-04-22 Thread Bug Watch Updater

** Changed in: util-linux (Debian)
   Status: New => Confirmed

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

Title:
  libblkid: no bcache UUID due to ambivalent detection of bcache and
  xfs_external_log for regular xfs in bcache backing device

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in util-linux source package in Bionic:
  Fix Released
Status in util-linux source package in Disco:
  Won't Fix
Status in util-linux source package in Eoan:
  Fix Released
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users with an XFS filesystem on top of bcache
     (this is seen on some ceph, cloud deployments)
     might fail to reference the bcache device by
     UUID or other udev properties.

   * The journal of the regular XFS filesystem in
     the bcache device is incorrectly detected as
     an XFS external log; so two superblocks are
     detected (bcache and xfs_external_log).

   * Thus blkid fails with ambivalent superblocks
     detected then doesn't provide the usual udev
     properties (UUID, etc.)

   * The fix improves the probe function for XFS
     external log so it detects it's regular XFS
     and bails out.

  [Test Case]

   * See test steps detailed in comment #7 and later.
     - Create an XFS filesystem with the journal/log
   in the beginning of the bcache device (< 256K).
     - Stop the bcache device.
     - Run '$ blkid -o udev -p $BCACHE_BACKING_DEVICE'.

     $ sudo make-bcache -B $BACKING_DEV
     $ sudo mkfs.xfs -d agsize=16m -l agnum=0 -f $BCACHE_DEV
     $ echo 1 | sudo tee /sys/block/$(basename $BCACHE_DEV)/bcache/stop
     $ sudo blkid -o udev -p $BACKING_DEV

  [Regression Potential]

   * The patch only changes the detection function
     for XFS external log to be more general about
     the sector where the magic of regular XFS may
     be found (which is shifted inside the bcache.)

   * It still checks at sector zero (the only one
     checked previously), so this behavior didn't
     change.

   * Possible regressions are actual XFS external
     log devices that are not anymore detected as
     such. (Although that would probably indicate
     a different bug in libblkid.)

  [Other Info]
   * upstream commit:
     
https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874353] [NEW] there is no linux-raspi apport package hook

Public bug reported:

ubuntu@ubuntu:~$ ls /usr/share/apport/package-hooks/ | grep linux
source_linux-5.4.py
source_linux-meta-oem-osp1.py
source_linux-meta-oem.py
source_linux-meta.py
source_linux-oem-5.4.py
source_linux-oem-osp1.py
source_linux-oem.py
source_linux-signed-5.4.py
source_linux-signed-oem-5.4.py
source_linux-signed-oem-osp1.py
source_linux-signed-oem.py
source_linux-signed.py
source_linux.py

On a Raspberry Pi this is my kernel image.
ii  linux-raspi5.4.0.1008.8  arm64  
  Complete Raspberry Pi Linux kernel and headers

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


** Tags: rls-ff-incoming

** Tags added: rls-ff-incoming

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

Title:
  there is no linux-raspi apport package hook

Status in apport package in Ubuntu:
  New

Bug description:
  ubuntu@ubuntu:~$ ls /usr/share/apport/package-hooks/ | grep linux
  source_linux-5.4.py
  source_linux-meta-oem-osp1.py
  source_linux-meta-oem.py
  source_linux-meta.py
  source_linux-oem-5.4.py
  source_linux-oem-osp1.py
  source_linux-oem.py
  source_linux-signed-5.4.py
  source_linux-signed-oem-5.4.py
  source_linux-signed-oem-osp1.py
  source_linux-signed-oem.py
  source_linux-signed.py
  source_linux.py

  On a Raspberry Pi this is my kernel image.
  ii  linux-raspi5.4.0.1008.8  arm64
Complete Raspberry Pi Linux kernel and headers

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 280533] Re: procps failed to install/upgrade :unable to make backup link of `./bin/ps' before installing new version: Operation not permitted

2020-04-22 Thread Jorge Delgado

The command that allowed it for me was: chattr -sia /bin/ps

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

Title:
  procps failed to install/upgrade :unable to make backup link of
  `./bin/ps' before installing new version: Operation not permitted

Status in procps package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: procps

  When I install new packages, I get the following error message:
  E: /var/cache/apt/archives/procps_1%3a3.2.7-5ubuntu3_amd64.deb: unable to 
make backup link of `./bin/ps' before 
  installing new version

  ProblemType: Package
  Architecture: amd64
  Date: Wed Oct  8 22:35:55 2008
  DistroRelease: Ubuntu 8.04
  ErrorMessage: unable to make backup link of `./bin/ps' before installing new 
version
  Package: procps 1:3.2.7-5ubuntu3 [modified: bin/ps usr/bin/top]
  PackageArchitecture: amd64
  SourcePackage: procps
  Title: package procps 1:3.2.7-5ubuntu3 [modified: bin/ps usr/bin/top] failed 
to install/upgrade: unable to make backup link of `./bin/ps' before installing 
new version
  Uname: Linux 2.6.24-20-generic x86_64

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Touch-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

2020-04-22 Thread Javier

I could solve it with these links, it was difficult for me, now I no longer
use that Ultrabox, but you can:

drivers - Bluetooth Broadcom 43142 isn't working - Ask Ubuntu

networking - ubuntu 14.04 bluetooth BCM43142 no discovery (tx timeout) -
Ask Ubuntu


Regards

El mié., 24 jul. 2019 a las 19:09, Brad Figg ()
escribió:

> ** Tags added: cscc
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1743336).
> https://bugs.launchpad.net/bugs/1366418
>
> Title:
>   Bluetooth BCM43142A0 doesn’t work
>
> Status in bluez package in Ubuntu:
>   Invalid
> Status in linux package in Ubuntu:
>   Fix Committed
> Status in linux-firmware package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
>   (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
>   displayed in the menu bar, if I open the bluetooth UI and switch on,
>   nothing happens and the result of “hcitool dev” is empty.
>
>   I have tried to install the windows driver with ndiswrapper, and the
>   bluetooth device seems to be detected as an usb bluetooth device but
>   still not working. I then add the device to the bluetooth usb device
>   and was able to activate bluetooth in the UI but it does not detect
>   any other devices (I’ve tested with a smartphone).
>
>   The driver I have installed can be found in asus page =>
>   http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
>   Select Windows OS, then “bluetooth” section, take the Broadcom driver
>   (should be the first one).
>
>   If you extract this archive, you will find a file named “bcbtums-
>   win8x64-brcm.inf” which I installed using the following command:
>
>   ndiswrapper -i bcbtums-win8x64-brcm.inf
>
>   Then, the result of “ndiswrapper -l” is:
>
>   bcbtums-win8x64-brcm : driver installed
> device (04CA:2006) present
>
>   in usb-devices, I find a device which was not present before
>   installation (I might have activated btusb before on this paste):
>
>   T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
>   D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
>   P:  Vendor=04ca ProdID=2006 Rev=01.12
>   S:  Manufacturer=Broadcom Corp
>   S:  Product=BCM43142A0
>   S:  SerialNumber=B8EE6593D989
>   C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
>   I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
>   I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
>   I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
>   I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
>
>   then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
>   can switch usb on, but no device will be detected and I’ve found this
>   in the dmesg:
>
>   [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout
>
>   which looks pretty much like a “bluetooth not working” message which I
>   don’t understand in details.
>
>   I leave here my full dmesg:
>
>   [0.253889] NetLabel:  domain hash size = 128
>   [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
>   [0.253901] NetLabel:  unlabeled traffic allowed by default
>   [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
>   [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
>   [0.255995] Switched to clocksource hpet
>   [0.260468] AppArmor: AppArmor Filesystem Enabled
>   [0.260488] pnp: PnP ACPI init
>   [0.260500] ACPI: bus type PNP registered
>   [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been
> reserved
>   [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01
> (active)
>   [0.260642] pnp 00:01: [dma 4]
>   [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
>   [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
>   [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
>   [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
>   [0.260927] system 00:04: [io  0x] has been reserved
>   [0.260928] system 00:04: [io  0x] has been reserved
>   [0.260930] system 00:04: [io  0x] has been reserved
>   [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
>   [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
>   [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
>   [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
>   [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
>   [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
>   [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02
> (active)
>   [0.260969] pnp 00:05: Plug and Play ACPI device, IDs

Re: [Touch-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

2020-04-22 Thread Javier

I could solve it with these links, it was difficult for me, now I no longer
use that Ultrabox, but you can:

drivers - Bluetooth Broadcom 43142 isn't working - Ask Ubuntu

networking - ubuntu 14.04 bluetooth BCM43142 no discovery (tx timeout) -
Ask Ubuntu


Regards

El mié., 24 jul. 2019 a las 19:09, Brad Figg ()
escribió:

> ** Tags added: cscc
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1743336).
> https://bugs.launchpad.net/bugs/1366418
>
> Title:
>   Bluetooth BCM43142A0 doesn’t work
>
> Status in bluez package in Ubuntu:
>   Invalid
> Status in linux package in Ubuntu:
>   Fix Committed
> Status in linux-firmware package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
>   (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
>   displayed in the menu bar, if I open the bluetooth UI and switch on,
>   nothing happens and the result of “hcitool dev” is empty.
>
>   I have tried to install the windows driver with ndiswrapper, and the
>   bluetooth device seems to be detected as an usb bluetooth device but
>   still not working. I then add the device to the bluetooth usb device
>   and was able to activate bluetooth in the UI but it does not detect
>   any other devices (I’ve tested with a smartphone).
>
>   The driver I have installed can be found in asus page =>
>   http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
>   Select Windows OS, then “bluetooth” section, take the Broadcom driver
>   (should be the first one).
>
>   If you extract this archive, you will find a file named “bcbtums-
>   win8x64-brcm.inf” which I installed using the following command:
>
>   ndiswrapper -i bcbtums-win8x64-brcm.inf
>
>   Then, the result of “ndiswrapper -l” is:
>
>   bcbtums-win8x64-brcm : driver installed
> device (04CA:2006) present
>
>   in usb-devices, I find a device which was not present before
>   installation (I might have activated btusb before on this paste):
>
>   T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
>   D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
>   P:  Vendor=04ca ProdID=2006 Rev=01.12
>   S:  Manufacturer=Broadcom Corp
>   S:  Product=BCM43142A0
>   S:  SerialNumber=B8EE6593D989
>   C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
>   I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
>   I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
>   I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
>   I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
>
>   then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
>   can switch usb on, but no device will be detected and I’ve found this
>   in the dmesg:
>
>   [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout
>
>   which looks pretty much like a “bluetooth not working” message which I
>   don’t understand in details.
>
>   I leave here my full dmesg:
>
>   [0.253889] NetLabel:  domain hash size = 128
>   [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
>   [0.253901] NetLabel:  unlabeled traffic allowed by default
>   [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
>   [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
>   [0.255995] Switched to clocksource hpet
>   [0.260468] AppArmor: AppArmor Filesystem Enabled
>   [0.260488] pnp: PnP ACPI init
>   [0.260500] ACPI: bus type PNP registered
>   [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been
> reserved
>   [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01
> (active)
>   [0.260642] pnp 00:01: [dma 4]
>   [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
>   [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
>   [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
>   [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
>   [0.260927] system 00:04: [io  0x] has been reserved
>   [0.260928] system 00:04: [io  0x] has been reserved
>   [0.260930] system 00:04: [io  0x] has been reserved
>   [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
>   [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
>   [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
>   [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
>   [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
>   [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
>   [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02
> (active)
>   [0.260969] pnp 00:05: Plug and Play ACPI device, IDs

Re: [Touch-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

2020-04-22 Thread Javier

I could solve it with these links, it was difficult for me, now I no longer
use that Ultrabox, but you can:

drivers - Bluetooth Broadcom 43142 isn't working - Ask Ubuntu

networking - ubuntu 14.04 bluetooth BCM43142 no discovery (tx timeout) -
Ask Ubuntu


Regards


El mié., 22 abr. 2020 a las 19:10, Gannet (<1366...@bugs.launchpad.net>)
escribió:

> Kubuntu 20.04 LTS
> HP ProBook 455 G3
>
> $ dmesg | grep -i error
> [   20.229516] bluetooth hci0: Direct firmware load for
> brcm/BCM43142A0-0a5c-216d.hcd failed with error -2
> [ 1242.727869] bluetooth hci0: Direct firmware load for
> brcm/BCM43142A0-0a5c-216d.hcd failed with error -2
> [ 5759.316789] bluetooth hci0: Direct firmware load for
> brcm/BCM43142A0-0a5c-216d.hcd failed with error -2
>
> ** Tags added: focal
>
> ** Changed in: linux-firmware (Ubuntu)
>Status: Incomplete => Confirmed
>
> ** Changed in: bluez (Ubuntu)
>Status: Invalid => Confirmed
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1743336).
> https://bugs.launchpad.net/bugs/1366418
>
> Title:
>   Bluetooth BCM43142A0 doesn’t work
>
> Status in bluez package in Ubuntu:
>   Confirmed
> Status in linux package in Ubuntu:
>   Fix Committed
> Status in linux-firmware package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
>   (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
>   displayed in the menu bar, if I open the bluetooth UI and switch on,
>   nothing happens and the result of “hcitool dev” is empty.
>
>   I have tried to install the windows driver with ndiswrapper, and the
>   bluetooth device seems to be detected as an usb bluetooth device but
>   still not working. I then add the device to the bluetooth usb device
>   and was able to activate bluetooth in the UI but it does not detect
>   any other devices (I’ve tested with a smartphone).
>
>   The driver I have installed can be found in asus page =>
>   http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
>   Select Windows OS, then “bluetooth” section, take the Broadcom driver
>   (should be the first one).
>
>   If you extract this archive, you will find a file named “bcbtums-
>   win8x64-brcm.inf” which I installed using the following command:
>
>   ndiswrapper -i bcbtums-win8x64-brcm.inf
>
>   Then, the result of “ndiswrapper -l” is:
>
>   bcbtums-win8x64-brcm : driver installed
> device (04CA:2006) present
>
>   in usb-devices, I find a device which was not present before
>   installation (I might have activated btusb before on this paste):
>
>   T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
>   D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
>   P:  Vendor=04ca ProdID=2006 Rev=01.12
>   S:  Manufacturer=Broadcom Corp
>   S:  Product=BCM43142A0
>   S:  SerialNumber=B8EE6593D989
>   C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
>   I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
>   I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
>   I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
>   I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
>
>   then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
>   can switch usb on, but no device will be detected and I’ve found this
>   in the dmesg:
>
>   [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout
>
>   which looks pretty much like a “bluetooth not working” message which I
>   don’t understand in details.
>
>   I leave here my full dmesg:
>
>   [0.253889] NetLabel:  domain hash size = 128
>   [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
>   [0.253901] NetLabel:  unlabeled traffic allowed by default
>   [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
>   [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
>   [0.255995] Switched to clocksource hpet
>   [0.260468] AppArmor: AppArmor Filesystem Enabled
>   [0.260488] pnp: PnP ACPI init
>   [0.260500] ACPI: bus type PNP registered
>   [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been
> reserved
>   [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01
> (active)
>   [0.260642] pnp 00:01: [dma 4]
>   [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
>   [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
>   [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
>   [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
>   [0.260927] system 00:04: [io  0x] has been reserved
>   [0.260928] system 00:04: [io  0x] has been reserved
>   [0.260930] system 00:04: [io  0x] has

[Touch-packages] [Bug 1874178] Re: Unlocking existing session needs two attempts after selecting Switch User

2020-04-22 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1874178

** Tags added: iso-testing

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

Title:
  Unlocking existing session needs two attempts after selecting Switch
  User

Status in lightdm package in Ubuntu:
  New

Bug description:
  This has been occurring during the Xubuntu post-install test. It's not
  the same as Bug #1776475, as it's not necessary to have logged in as
  another user (or even for another user to exist) for the problem to
  happen.

  My sequence of actions is:

  *Create new user.
  *Open a program (usually Thunar or Terminal).
  *Lock session.
  *Click on "Switch User". <-- This is all that's necessary to trigger it.
  *Enter password to unlock my own session.
  *Then there's a delay and screen goes black, then the unlock prompt appears 
again.
  *The second time, my session unlocks.

  This particular report is from a QEMU/KVM vm, but it's also been
  happening on a bare-metal install.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Apr 22 15:30:29 2020
  InstallationDate: Installed on 2020-04-22 (0 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200421)
  ProcEnviron:
   LANGUAGE=en_NZ:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia

** Branch linked: lp:~kubuntu-dev/ubuntu-seeds/kubuntu.focal

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

Title:
  ubuntu-drivers changes kernel flavour when installing nvidia

Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  $ dpkg-query -W linux-image-*
  linux-image-5.4.0-25-generic  5.4.0-25.29
  linux-image-generic-hwe-20.04 5.4.0.25.31

  $ ubuntu-drivers list
  nvidia-driver-390
  nvidia-driver-435
  nvidia-driver-440

  
  $ sudo ubuntu-drivers install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-kernel-common-440
nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 
screen-resolution-extra xserver-xorg-video-nvidia-440
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-25-lowlatency
  Recommended packages:
libnvidia-compute-440:i386 libnvidia-decode-440:i386 
libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 
libnvidia-gl-440:i386
  The following NEW packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-driver-440
nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime 
nvidia-settings nvidia-utils-440 screen-resolution-extra 
xserver-xorg-video-nvidia-440
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

  I was expecting for it to pick linux-modules-nvidia-440-generic-
  hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04

  As if it sorted things and picked last one?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874333] Re: Titlebar buttons are placed in the wrong place

2020-04-22 Thread Paul White

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

** This bug has been marked a duplicate of bug 1873638
   Titlebar buttons incorrectly placed when set to appear on the left

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

Title:
  Titlebar buttons are placed in the wrong place

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  Titlebar buttons in the Ubuntu Settings app on Ubuntu 20.04 are placed
  in the wrong place when the placement is set to the left side.

  I've attached the image describing the issue.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874340] Re: Ubuntu Settings app on doesn't collapse to hanheld size

2020-04-22 Thread Paul White

** Package changed: ubuntu-settings (Ubuntu) => gnome-control-center
(Ubuntu)

** Tags added: focal

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

Title:
  Ubuntu Settings app on doesn't collapse to hanheld size

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  Ubuntu Settings app is supposed to collapse the sidebar when scaling the down 
the window on the x axis.
  On Ubuntu 20.04 that seems to be broken.

  I've attached the image describing the issue.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1867375] Re: systemd-networkd: UseRoutes behavior change with introduction of UseGateway param

** Merge proposal linked:
   
https://code.launchpad.net/~ddstreet/ubuntu/+source/systemd/+git/systemd/+merge/382806

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

Title:
  systemd-networkd: UseRoutes behavior change with introduction of
  UseGateway param

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Confirmed
Status in netplan.io source package in Focal:
  New
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  the networkd UseRoutes parameter allowed ignoring all routes provided
  by a dhcp4 server, including the route via the dhcp4-provided gateway.
  This was the behavior of networkd until recently, and in Focal the
  UseRoutes parameter does *not* prevent networkd from adding the route
  via the dhcp4-provided gateway.  This is now controlled with a new
  parameter, UseGateway.

  The systemd in Focal unfortunately has part of the upstream code; it
  no longer ignores the gateway route when UseRoutes=false is specified,
  but also it does not include the UseGateway parameter.

  Before Focal, networkd did not allow ignoring dhcpv4 routes and the
  gateway separately; the UseRoutes= parameter either used, or ignored,
  both.  This is why upstream added the UseGateway= paramter, which
  should be backported to allow control of ignoring the dhcpv4 routes
  and gateway separately.

  [test case]

  In Focal, bug 1872589 has a good test case netplan config, but a very
  quick test can be done with the networkd config:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  this results in the system incorrectly setting a route via the default
  gateway:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  Before Focal, the above test case shows "correct" behavior, but there
  is no way to ignore the dhcpv4 routes but use the dhcpv4 gateway.
  This pre-Focal, the test case would be to use the UseGateway=
  parameter, e.g.:

  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  UseGateway=true

  which *should* result in the default gateway being configured:

  root@lp1867375-f:~# ip r
  default via 10.202.51.1 dev eth0 proto dhcp src 10.202.51.86 metric 100
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.86
  10.202.51.1 dev eth0 proto dhcp scope link src 10.202.51.86 metric 100

  [regression potential]

  Any regression would likely involve incorrect setting, or ignoring, of
  dhcpv4-provided routes, and/or incorrect setting, or ignoring, of the
  dhcpv4-provided gateway.

  [scope]

  One possible direction is this upstream PR
  https://github.com/systemd/systemd/pull/15443

  If accepted, that (and previous commits adding UseGateway= parameter)
  would need to be applied to Debian and all Ubuntu releases; Focal,
  Eoan, Bionic, and Xenial.

  [other info]

  to properly support separation of 'routes' and 'gateways' received via
  dhcp4, SRU releases should also support the UseGateway parameter,
  which is what this bug was originally opened requesting.

  [original description]

  requesting backport of PR https://github.com/systemd/systemd/pull/14983 which 
fixes the issue described in
  https://github.com/systemd/systemd/issues/14982 to 18.04 (bionic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1867375/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  Definition of add_mountroot_fail_hook doesnt match lvm2's usage

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Package lvm2 contains a init-premount script named /usr/share
  /initramfs-tools/scripts/init-premount/lvm2

  In this script there is the function call:
  add_mountroot_fail_hook "20-lvm2"

  Which is defined in /usr/share/initramfs-tools/scripts/functions

  In focal's 0.136ubuntu6 , this is defined as:

  add_mountroot_fail_hook()
  {
  mkdir -p /tmp/mountroot-fail-hooks.d
  ln -s "$0" /tmp/mountroot-fail-hooks.d/"$0"
  }

  The final line of the function will execute as
  ln -s "/scripts/lvm2" /tmp/mountroot-fail-hooks.d/"/scripts/lvm2"

  And fail, because directory /tmp/mountroot-fail-hooks.d/scripts does
  not exist.

  It is clear from lvm2's invocation that it expects the symlink to be
  named "20-lvm2" , and if we look at bionic's 0.130ubuntu3.6 that is
  the case:

  add_mountroot_fail_hook()
  {
  mkdir -p /tmp/mountroot-fail-hooks.d
  ln -s "$0" /tmp/mountroot-fail-hooks.d/"$1"
  }

  focal's version needs to be updated to either support the "$1"
  argument or strip the directory from "$0".

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-22 Thread Matthew Ruffell

** Description changed:

  BugLink: https://bugs.launchpad.net/bugs/1872863
  
  [Impact]
  
  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.
  
  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.
  
  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in
  LP #1378648 due to bochs-drm causing problems in a PowerKVM machine.
  This problem appears to be fixed now, and bochs-drm has been re-enabled
  for Disco and up, in LP #1795857 and has been proven safe.
  
  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.
  
  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.
  
  [Fix]
  
  I noticed on Focal, if you boot, the framebuffer is initially efifb:
  
  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device
  
  This soon changes to bochs-drm about a second later:
  
  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48
  
  On bionic, the framebuffer never changes from efifb, since the bochs-drm
  kernel module is not built, and it is also present on the module banlist
  in /etc/modprobe.d/blacklist-framebuffer.conf
  
  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.
  
  [Testcase]
  
  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In the
  "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64:
  /usr/share/OVMF/OVMF_CODE.secboot.fd".
  
  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you have
  grub2 2.02-2ubuntu8.15 installed.
  
  Shut the VM down, and set the video device to VGA. Or VGA=std if you use
  the QEMU command line.
  
  Start the VM up, and the screen will be garbled. See attached picture.
  
  If you install my test packages, which are available here:
  
  https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test
  
  Instructions to install (on a bionic system):
  
  1) sudo add-apt-repository ppa:mruffell/sf272653-test
  2) sudo apt-get update
  3) sudo apt install linux-image-unsigned-4.15.0-96-generic 
linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic 
linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod
  4) sudo reboot
  5) uname -rv
  4.15.0-96-generic #97+TEST272653v20200409b1-Ubuntu SMP Thu Apr 9 04:09:18 UTC 
2020
  
  If you reboot, the screen will be perfectly readable, since the bochs-
  drm driver will be in use.
  
  [Regression Potential]
  
  We are enabling a display driver on Bionic which was previously
  disabled, so there will be some virtual machines making the jump to
  using bochs-drm since it would now be available.
  
  I don't think that this is a bad thing, and in many ways will probably
  end up improving some user's experience. Although there are two
  scenarios where a regression could happen:
  
  1 - frequently gamers use GPU passthrough to their kvm based virtual
  machines, and I have seen them expect,

[Touch-packages] [Bug 1874340] [NEW] Ubuntu Settings app on doesn't collapse to hanheld size

2020-04-22 Thread Kristijan Žic 

Public bug reported:

Ubuntu Settings app is supposed to collapse the sidebar when scaling the down 
the window on the x axis.
On Ubuntu 20.04 that seems to be broken.

I've attached the image describing the issue.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "bitmap2.png"
   
https://bugs.launchpad.net/bugs/1874340/+attachment/5358161/+files/bitmap2.png

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

Title:
  Ubuntu Settings app on doesn't collapse to hanheld size

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  Ubuntu Settings app is supposed to collapse the sidebar when scaling the down 
the window on the x axis.
  On Ubuntu 20.04 that seems to be broken.

  I've attached the image describing the issue.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1366418] Re: Bluetooth BCM43142A0 doesn’t work

2020-04-22 Thread Gannet

Kubuntu 20.04 LTS
HP ProBook 455 G3

$ dmesg | grep -i error
[   20.229516] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-0a5c-216d.hcd failed with error -2
[ 1242.727869] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-0a5c-216d.hcd failed with error -2
[ 5759.316789] bluetooth hci0: Direct firmware load for 
brcm/BCM43142A0-0a5c-216d.hcd failed with error -2

** Tags added: focal

** Changed in: linux-firmware (Ubuntu)
   Status: Incomplete => Confirmed

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

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

Title:
  Bluetooth BCM43142A0 doesn’t work

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Fix Committed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  I’ve installed ubuntu 14.04 and my computer’s builtin bluetooth
  (computer is an Asus x550ln) doesn’t work at all. Bluetooth is not
  displayed in the menu bar, if I open the bluetooth UI and switch on,
  nothing happens and the result of “hcitool dev” is empty.

  I have tried to install the windows driver with ndiswrapper, and the
  bluetooth device seems to be detected as an usb bluetooth device but
  still not working. I then add the device to the bluetooth usb device
  and was able to activate bluetooth in the UI but it does not detect
  any other devices (I’ve tested with a smartphone).

  The driver I have installed can be found in asus page =>
  http://www.asus.com/fr/Notebooks_Ultrabooks/X550LN/HelpDesk_Download/
  Select Windows OS, then “bluetooth” section, take the Broadcom driver
  (should be the first one).

  If you extract this archive, you will find a file named “bcbtums-
  win8x64-brcm.inf” which I installed using the following command:

  ndiswrapper -i bcbtums-win8x64-brcm.inf

  Then, the result of “ndiswrapper -l” is:

  bcbtums-win8x64-brcm : driver installed
device (04CA:2006) present

  in usb-devices, I find a device which was not present before
  installation (I might have activated btusb before on this paste):

  T:  Bus=02 Lev=01 Prnt=01 Port=05 Cnt=02 Dev#=  3 Spd=12  MxCh= 0
  D:  Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=04ca ProdID=2006 Rev=01.12
  S:  Manufacturer=Broadcom Corp
  S:  Product=BCM43142A0
  S:  SerialNumber=B8EE6593D989
  C:  #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
  I:  If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
  I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
  I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

  then, “echo "04ca 2006" > /sys/bus/usb/drivers/btusb/new_id”, and I
  can switch usb on, but no device will be detected and I’ve found this
  in the dmesg:

  [2200.843126] Bluetooth: hci0 command 0x1003 tx timeout

  which looks pretty much like a “bluetooth not working” message which I
  don’t understand in details.

  I leave here my full dmesg:

  [0.253889] NetLabel:  domain hash size = 128
  [0.253890] NetLabel:  protocols = UNLABELED CIPSOv4
  [0.253901] NetLabel:  unlabeled traffic allowed by default
  [0.253959] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0, 0, 0, 0, 0, 0
  [0.253965] hpet0: 8 comparators, 64-bit 14.318180 MHz counter
  [0.255995] Switched to clocksource hpet
  [0.260468] AppArmor: AppArmor Filesystem Enabled
  [0.260488] pnp: PnP ACPI init
  [0.260500] ACPI: bus type PNP registered
  [0.260592] system 00:00: [mem 0xfed4-0xfed44fff] has been reserved
  [0.260596] system 00:00: Plug and Play ACPI device, IDs PNP0c01 (active)
  [0.260642] pnp 00:01: [dma 4]
  [0.260658] pnp 00:01: Plug and Play ACPI device, IDs PNP0200 (active)
  [0.260678] pnp 00:02: Plug and Play ACPI device, IDs INT0800 (active)
  [0.260782] pnp 00:03: Plug and Play ACPI device, IDs PNP0103 (active)
  [0.260924] system 00:04: [io  0x0680-0x069f] has been reserved
  [0.260927] system 00:04: [io  0x] has been reserved
  [0.260928] system 00:04: [io  0x] has been reserved
  [0.260930] system 00:04: [io  0x] has been reserved
  [0.260932] system 00:04: [io  0x1c00-0x1cfe] has been reserved
  [0.260934] system 00:04: [io  0x1d00-0x1dfe] has been reserved
  [0.260935] system 00:04: [io  0x1e00-0x1efe] has been reserved
  [0.260937] system 00:04: [io  0x1f00-0x1ffe] has been reserved
  [0.260939] system 00:04: [io  0x1800-0x18fe] could not be reserved
  [0.260941] system 00:04: [io  0x164e-0x164f] has been reserved
  [0.260943] system 00:04: Plug and Play ACPI device, IDs PNP0c02 (active)
  [0.260969] pnp 00:05: Plug and Play ACPI device, IDs PNP0b00 (active)
  [0.261012] system 00:06: [io  0x1854-0x1857] has been reserved
  [0.261014] system

[Touch-packages] [Bug 1874337] [NEW] resolvconf should never touch /etc/resolv.conf in Ubuntu; all DNS configuration from resolvconf, ifupdown, and dhclient should always be fed directly to systemd-re

2020-04-22 Thread Steve Langasek

Public bug reported:

systemd-resolved is a standard component of Ubuntu in 20.04.  We should
not have packages in the archive - some of which may be installed on
users' systems as a result of upgrading from previous releases - that
cause the handling of DNS resolution to diverge from the default.

This means that:

- the dhclient hook that picks up DNS settings should only feed settings 
directly to resolved, and not via resolvconf.
- resolvconf must not change the target of /etc/resolv.conf and on upgrade must 
correct it.
- resolvconf must feed its settings reliably into resolved rather than pulling 
resolved settings into resolvconf.
- systemd should not ship a dhclient hook at all because dhclient is not used 
by any systems that use netplan for network management, it is only needed for 
compatibility on upgrade with ifupdown; so move the hook to the ifupdown 
package.

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

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

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

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

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

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

Title:
  resolvconf should never touch /etc/resolv.conf in Ubuntu; all DNS
  configuration from resolvconf, ifupdown, and dhclient should always be
  fed directly to systemd-resolved.

Status in ifupdown package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-resolved is a standard component of Ubuntu in 20.04.  We
  should not have packages in the archive - some of which may be
  installed on users' systems as a result of upgrading from previous
  releases - that cause the handling of DNS resolution to diverge from
  the default.

  This means that:

  - the dhclient hook that picks up DNS settings should only feed settings 
directly to resolved, and not via resolvconf.
  - resolvconf must not change the target of /etc/resolv.conf and on upgrade 
must correct it.
  - resolvconf must feed its settings reliably into resolved rather than 
pulling resolved settings into resolvconf.
  - systemd should not ship a dhclient hook at all because dhclient is not used 
by any systems that use netplan for network management, it is only needed for 
compatibility on upgrade with ifupdown; so move the hook to the ifupdown 
package.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874333] [NEW] Titlebar buttons are placed in the wrong place

2020-04-22 Thread Kristijan Žic 

Public bug reported:

Titlebar buttons in the Ubuntu Settings app on Ubuntu 20.04 are placed
in the wrong place when the placement is set to the left side.

I've attached the image describing the issue.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Image describing the issue"
   https://bugs.launchpad.net/bugs/1874333/+attachment/5358154/+files/bitmap.png

** Description changed:

- Titlebar buttons are placed in the wrong place when the placement is set
- to the left side.
+ Titlebar buttons in the Ubuntu Settings app are placed in the wrong
+ place when the placement is set to the left side.
  
  I've attached the image describing the issue.

** Description changed:

- Titlebar buttons in the Ubuntu Settings app are placed in the wrong
- place when the placement is set to the left side.
+ Titlebar buttons in the Ubuntu Settings app on Ubuntu 20.04 are placed
+ in the wrong place when the placement is set to the left side.
  
  I've attached the image describing the issue.

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

Title:
  Titlebar buttons are placed in the wrong place

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  Titlebar buttons in the Ubuntu Settings app on Ubuntu 20.04 are placed
  in the wrong place when the placement is set to the left side.

  I've attached the image describing the issue.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-22 Thread Matthew Ruffell

** Description changed:

  BugLink: https://bugs.launchpad.net/bugs/1872863
  
  [Impact]
  
  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.
  
  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.
  
  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in
  LP #1378648 due to bochs-drm causing problems in a PowerKVM machine.
  This problem appears to be fixed now, and bochs-drm has been re-enabled
  for Disco and up, in LP #1795857 and has been proven safe.
  
  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.
  
  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.
  
  [Fix]
  
  I noticed on Focal, if you boot, the framebuffer is initially efifb:
  
  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device
  
  This soon changes to bochs-drm about a second later:
  
  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48
  
  On bionic, the framebuffer never changes from efifb, since the bochs-drm
  kernel module is not built, and it is also present on the module banlist
  in /etc/modprobe.d/blacklist-framebuffer.conf
  
  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.
  
  [Testcase]
  
  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In the
  "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64:
  /usr/share/OVMF/OVMF_CODE.secboot.fd".
  
  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you have
  grub2 2.02-2ubuntu8.15 installed.
  
  Shut the VM down, and set the video device to VGA. Or VGA=std if you use
  the QEMU command line.
  
  Start the VM up, and the screen will be garbled. See attached picture.
  
  If you install my test packages, which are available here:
  
  https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test
  
  Instructions to install (on a bionic system):
  
  1) sudo add-apt-repository ppa:mruffell/sf272653-test
  2) sudo apt-get update
  3) sudo apt install linux-image-unsigned-4.15.0-96-generic 
linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic 
linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod
  4) sudo reboot
  5) uname -rv
  4.15.0-96-generic #97+TEST272653v20200409b1-Ubuntu SMP Thu Apr 9 04:09:18 UTC 
2020
  
  If you reboot, the screen will be perfectly readable, since the bochs-
  drm driver will be in use.
  
  [Regression Potential]
  
  We are enabling a display driver on Bionic which was previously
  disabled, so there will be some virtual machines making the jump to
  using bochs-drm since it would now be available.
  
  I don't think that this is a bad thing, and in many ways will probably
  end up improving some user's experience. Although there are two
  scenarios where a regression could happen:
  
  1 - frequently gamers use GPU passthrough to their kvm based virtual
  machines, and I have seen them expect,

[Touch-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module

2020-04-22 Thread Dan Streetman

** Tags added: sts-sponsor-ddstreet

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

Title:
  QEMU/KVM display is garbled when booting from kernel EFI stub due to
  missing bochs-drm module

Status in kmod package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  BugLink: https://bugs.launchpad.net/bugs/1872863

  [Impact]

  A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the
  kernel EFI stub whenever EFI is enabled. This causes problems for
  QEMU/KVM virtual machines which use the VGA=std video device, as the
  efifb driver yields an unreadable garbled screen. See the attached
  image.

  The correct framebuffer driver to use in this situation is bochs-drm,
  and modprobing it from a HWE kernel fixes the issues.

  bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled
  in LP #1378648 due to bochs-drm causing problems in a PowerKVM
  machine. This problem appears to be fixed now, and bochs-drm has been
  re-enabled for Disco and up, in LP #1795857 and has been proven safe.

  This has also come up again in LP #1823152, as well as chatter on LP
  #1795857 to get this enabled on Bionic.

  The customer which is experiencing this issue cannot switch to VGA=qxl
  as a workaround, and must use VGA=std, hence I suggest we re-enable
  bochs-drm for Bionic.

  [Fix]

  I noticed on Focal, if you boot, the framebuffer is initially efifb:

  [ 0.603716] efifb: probing for efifb
  [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k
  [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1
  [ 0.603736] efifb: scrolling: redraw
  [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
  [ 0.604462] Console: switching to colour frame buffer device 100x37
  [ 0.605829] fb0: EFI VGA frame buffer device

  This soon changes to bochs-drm about a second later:

  [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
0: 0xc000 -> 0xc0ff
  [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 
2: 0xc1c8c000 -> 0xc1c8cfff
  [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100)
  [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA
  [ 0.939085] Console: switching to colour dummy device 80x25
  [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console
  [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5.
  [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000.
  [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized
  [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB
  [ 0.942081] [TTM] Initializing pool allocator
  [ 0.942089] [TTM] Initializing DMA pool allocator
  [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 
GB/10.0 GiB)
  [ 0.944019] [drm] Found EDID data blob.
  [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on 
minor 0
  [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device
  [ 0.947712] Console: switching to colour frame buffer device 128x48

  On bionic, the framebuffer never changes from efifb, since the bochs-
  drm kernel module is not built, and it is also present on the module
  banlist in /etc/modprobe.d/blacklist-framebuffer.conf

  bochs-drm needs to be enabled to be built in the kernel config, and
  removed from the module blacklist in kmod.

  [Testcase]

  Create a new QEMU/KVM virtual machine, I used virt-manager. Before you
  install the OS, check the box to modify settings before install. In
  the "Overview" tab, enable EFI by setting the firmware to "UEFI
  x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd".

  Set the video device to qxl while you install Bionic. Once the install
  is done, reboot, do a "apt update" and "apt upgrade", to ensure you
  have grub2 2.02-2ubuntu8.15 installed.

  Shut the VM down, and set the video device to VGA. Or VGA=std if you
  use the QEMU command line.

  Start the VM up, and the screen will be garbled. See attached picture.

  If you install my test packages, which are available here:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test

  Instructions to install (on a bionic system):

  1) sudo add-apt-repository ppa:mruffell/sf272653-test
  2) sudo apt-get update
  3) sudo apt install linux-image-unsigned-4.15.0-96-generic 
linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic 
linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod
  4) sudo reboot
  5) uname -rv
  4.15.0-96-generic #97+TEST272653v20200409b1-Ubuntu SMP Thu Apr 9 04:09:18 UTC 
2020

  If you reboot, the screen will be perfectly readable, since the bochs-
  drm driver will be in use.

  [Regression Potential]

  We are

[Touch-packages] [Bug 1873794] Re: Unattended upgrades fixes missing from security repo

2020-04-22 Thread Marc Deslauriers

The -security pocket gets security fixes only.
The -updates pocket gets security fixes, and also bug fixes.

This is a bug fix, which is why it is in the -updates pocket only.

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

Title:
  Unattended upgrades fixes missing from security repo

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Eoan:
  Fix Released

Bug description:
  Critical unattended upgrades fixes are missing from the bionic
  security repo, which means that if you are using an installation of
  Ubuntu using only 'bionic' and 'bionic-security' you can stop
  unattended-upgrades from working just by doing a 'rmdir
  /var/cache/apt/archives/partial'.

  This is because the 'rootdir' parameter on the main function is set to
  "" rather than "/" - which disables the required directories and files
  check.

  I'm presuming here that the *-updates pocket is still 'recommended'
  rather than 'required'.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 12:44:35 2020
  InstallationDate: Installed on 2016-04-28 (1452 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (610 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-09-17T10:50:46.904847

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872146] Re: Audio on Headphones stopped working

2020-04-22 Thread Shaun

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

HI

I did sudo apt-get install --reinstall alsa-base pulseaudio
sudo alsa force-reload

Did a restart and it sems to be working now.

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

Title:
  Audio on Headphones stopped working

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Audio via my headphones worked yesterday, Today no such luck.

  When I plug in my headphone, Plasma picks it up but no sound.

  Bluetooth headset still works.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Apr 10 23:03:09 2020
  InstallationDate: Installed on 2020-04-05 (5 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 327362] Re: Some ISPs have .local domain which disables avahi-daemon

2020-04-22 Thread Magnus

That's great!

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

Title:
  Some ISPs have .local domain which disables avahi-daemon

Status in Release Notes for Ubuntu:
  Fix Released
Status in avahi package in Ubuntu:
  Confirmed
Status in avahi source package in Karmic:
  Won't Fix

Bug description:
  Binary package hint: avahi-daemon

  After a fresh install of Jaunty Alpha 3 avahi did not work and as a
  result of that - not Bonjour in Pidgin, and some network discovery
  stuff.

  I have been looking for a solution, but still - after the fresh
  install, when I used Intrepid, it worked fine.

  During boot I see some error with avahi-daemon (do quick to actually read), 
and I think that it is the same thing as I get when trying to startup 
avahi-damon:
  daniel@daniel-laptop:~$ sudo /etc/init.d/avahi-daemon start
   * Starting Avahi mDNS/DNS-SD Daemon avahi-daemon 
   
   * avahi-daemon disabled because there is a unicast .local domain

  And after login there is a notify regarding the same matter.

  This same things is confirmed on my finances netbook. 
  We used the Alternative Jaunty CD for install (due to that the install 
crashed when the installing user already existed in /home, on the desktop CD)

  Awesome work - keep it up! ;)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1866974] Re: The Diffie-Hellman prime sent by the server is not acceptable

2020-04-22 Thread Neil Green

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

Want to add my thanks as well Simon, I'm still getting a warning abut a
wildcard cert, but it's at least functional now!

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

Title:
  The Diffie-Hellman prime sent by the server is not acceptable

Status in evolution package in Ubuntu:
  Confirmed
Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  I can no longer connect to my ISP mail server.
  Works in previous version 19.10

  "The reported error was “Failed to get capabilities: Error performing
  TLS handshake: The Diffie-Hellman prime sent by the server is not
  acceptable (not long enough).”."

  I've tried finding a workaround but so far no luck.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: evolution 3.35.92-1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 11 11:07:01 2020
  InstallationDate: Installed on 2020-03-03 (7 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  SourcePackage: evolution
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874262] Re: User session does not start: Problem with chrome-remote-desktop

2020-04-22 Thread El jinete sin cabeza

** Summary changed:

- User session does not start: xkbcomp "Internal error: Could not resolve 
keysym Invalid"
+ User session does not start: Problem with chrome-remote-desktop

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

Title:
  User session does not start: Problem with chrome-remote-desktop

Status in gdm3 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  New

Bug description:
  https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14
  https://gitlab.gnome.org/GNOME/gdm/-/issues/593

  ---

  Today I tried to log into my ubuntu session with my personal account
  through Xorg and Xwayland. And I couldn't, I had to install lightdm
  and to be able to enter.

  In my experience, I found this message ($journalctl):
  Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum 
keycode 569, clipping.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes 
above 255.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not 
resolve keysym Invalid
  Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not 
fatal to the X server

  Attached log of the attempt to log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.6.6-050606-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 09:54:26 2020
  InstallationDate: Installed on 2018-12-02 (506 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873794] Re: Unattended upgrades fixes missing from security repo

2020-04-22 Thread Neil Wilson

If the fix is not in the security pocket, how does it get sorted if the
updates pocket is turned off?

I understood *-updates are only supposed to be recommended.


As I mentioned if you build an image with a tool like 'mkosi' which utilises 
debootstrap and then cleans the cache, the partial directory is missing in the 
resulting image.

Under the Debian file system layout /var is supposed to be volatile. You
can't rely on anything being there.

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

Title:
  Unattended upgrades fixes missing from security repo

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Eoan:
  Fix Released

Bug description:
  Critical unattended upgrades fixes are missing from the bionic
  security repo, which means that if you are using an installation of
  Ubuntu using only 'bionic' and 'bionic-security' you can stop
  unattended-upgrades from working just by doing a 'rmdir
  /var/cache/apt/archives/partial'.

  This is because the 'rootdir' parameter on the main function is set to
  "" rather than "/" - which disables the required directories and files
  check.

  I'm presuming here that the *-updates pocket is still 'recommended'
  rather than 'required'.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 12:44:35 2020
  InstallationDate: Installed on 2016-04-28 (1452 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (610 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-09-17T10:50:46.904847

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873794] Re: Unattended upgrades fixes missing from security repo

2020-04-22 Thread Mike Salvatore

** Information type changed from Private Security to Public Security

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

Title:
  Unattended upgrades fixes missing from security repo

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Eoan:
  Fix Released

Bug description:
  Critical unattended upgrades fixes are missing from the bionic
  security repo, which means that if you are using an installation of
  Ubuntu using only 'bionic' and 'bionic-security' you can stop
  unattended-upgrades from working just by doing a 'rmdir
  /var/cache/apt/archives/partial'.

  This is because the 'rootdir' parameter on the main function is set to
  "" rather than "/" - which disables the required directories and files
  check.

  I'm presuming here that the *-updates pocket is still 'recommended'
  rather than 'required'.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 20 12:44:35 2020
  InstallationDate: Installed on 2016-04-28 (1452 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (610 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-09-17T10:50:46.904847

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia

This bug was fixed in the package ubuntu-drivers-common - 1:0.8.1

---
ubuntu-drivers-common (1:0.8.1) focal; urgency=medium

  [ Alberto Milone ]
  * UbuntuDrivers/detect.py,
UbuntuDrivers/kerneldetection.py,
tests/test_ubuntu_drivers.py,
ubuntu-drivers:
- Add tests for the -generic-hwe-20.04 flavour and for
  the -oem-20.04 linux flavour.
- Add detection logic to get the linux metapackage and
  linux-modules for -hwe-20.04 (LP: #1873867).
- List the modules provider when it is either a dkms package
  or a linux-modules package.
- Install linux-modules packages when available.
  This makes the NVIDIA drivers work with Secure Boot.

  [ Dimitri John Ledkov ]
  * UbuntuDrivers/detect.py,
UbuntuDrivers/kerneldetection.py:
- Use exact matching in find_reverse_deps() with both
  installed and candidate.

 -- Alberto Milone   Tue, 21 Apr 2020
21:14:15 +0200

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  ubuntu-drivers changes kernel flavour when installing nvidia

Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  $ dpkg-query -W linux-image-*
  linux-image-5.4.0-25-generic  5.4.0-25.29
  linux-image-generic-hwe-20.04 5.4.0.25.31

  $ ubuntu-drivers list
  nvidia-driver-390
  nvidia-driver-435
  nvidia-driver-440

  
  $ sudo ubuntu-drivers install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-kernel-common-440
nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 
screen-resolution-extra xserver-xorg-video-nvidia-440
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-25-lowlatency
  Recommended packages:
libnvidia-compute-440:i386 libnvidia-decode-440:i386 
libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 
libnvidia-gl-440:i386
  The following NEW packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-driver-440
nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime 
nvidia-settings nvidia-utils-440 screen-resolution-extra 
xserver-xorg-video-nvidia-440
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

  I was expecting for it to pick linux-modules-nvidia-440-generic-
  hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04

  As if it sorted things and picked last one?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1817077] Re: package linux-image-4.15.0-44-generic (not installed) failed to install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with return code 128

2020-04-22 Thread Lucas Kanashiro

@dbalde, send messages here in English please. I could translate you
comment but your attachment make me think whether it is just a spam
message.

Anyway, you did not provide much more info, so I'll follow @cpaelzer and
mark grub-legacy-ec2 as invalid again. If you have information to
provide please do it and we can reconsider it.

** Changed in: grub-legacy-ec2 (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package linux-image-4.15.0-44-generic (not installed) failed to
  install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2
  exited with return code 128

Status in debconf package in Ubuntu:
  Confirmed
Status in grub-legacy-ec2 package in Ubuntu:
  Invalid

Bug description:
  I applied an system update and was presented with this error after the
  next login.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-44-generic (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  Date: Thu Feb 14 00:00:24 2019
  ErrorMessage: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with 
return code 128
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lspci:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  ProcFB: 0 hyperv_fb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic 
root=UUID=36f6b4c3-1f42-11e9-99c9-00155d195067 ro
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.8
  RfKill:
   
  SourcePackage: grub-legacy-ec2
  Title: package linux-image-4.15.0-44-generic (not installed) failed to 
install/upgrade: run-parts: /etc/kernel/postrm.d/x-grub-legacy-ec2 exited with 
return code 128
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/26/2012
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v1.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v1.0
  dmi.chassis.asset.tag: 0298-0271-9062-6147-4258-1509-89
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v1.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev1.0:bd11/26/2012:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev1.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev1.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev1.0:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.version: Hyper-V UEFI Release v1.0
  dmi.sys.vendor: Microsoft Corporation

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia

2020-04-22 Thread Dimitri John Ledkov

I am very happy with the new  ubuntu-drivers-common and l-r-m in
proposed! Installed all the right things, with latelink=false on the
host system, and latelink=true in target.

Just need all of these to migrate, respin, retest, ship.

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

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

Title:
  ubuntu-drivers changes kernel flavour when installing nvidia

Status in linux package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  $ dpkg-query -W linux-image-*
  linux-image-5.4.0-25-generic  5.4.0-25.29
  linux-image-generic-hwe-20.04 5.4.0.25.31

  $ ubuntu-drivers list
  nvidia-driver-390
  nvidia-driver-435
  nvidia-driver-440

  
  $ sudo ubuntu-drivers install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-kernel-common-440
nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 
screen-resolution-extra xserver-xorg-video-nvidia-440
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-25-lowlatency
  Recommended packages:
libnvidia-compute-440:i386 libnvidia-decode-440:i386 
libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 
libnvidia-gl-440:i386
  The following NEW packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-driver-440
nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime 
nvidia-settings nvidia-utils-440 screen-resolution-extra 
xserver-xorg-video-nvidia-440
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

  I was expecting for it to pick linux-modules-nvidia-440-generic-
  hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04

  As if it sorted things and picked last one?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1860926] Re: Ubuntu 20.04 Systemd fails to configure bridged network

2020-04-22 Thread keestux

This may be the same bug as
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1872185

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

Title:
  Ubuntu 20.04  Systemd fails to configure bridged network

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  [impact]

  A bridged interface with static ipv4 address and gateway configuration
  will fail to properly add the route via the gateway, leaving the
  system without a globally working network.

  [test case]

  On a Focal system, remove all network configuration and create this
  netplan:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  Replace the interface name 'enp4s0' with the actual interface name on
  the test system.

  Reboot the system, and check the route to the gateway, which will be
  missing:

  root@lp1860926-f:~# ip r
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  The route is expected to be present, e.g.:

  ubuntu@lp1860926-e:~$ ip r
  default via 192.168.0.1 dev br0 proto static
  192.168.0.0/24 dev br0 proto kernel scope link src 192.168.0.4

  [regression potential]

  Not SRU - N/A

  [scope]

  This is not reproducable on Eoan or Bionic; this is needed only for
  Focal.

  [original description]

  Freshly installed Ubuntu 20.04 fully patched to days date with static
  IP address works fine and survives a reboot

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  however when converted to a bridged network for kvm

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp4s0:
    dhcp4: false
    bridges:
  br0:
    interfaces: [enp4s0]
    dhcp4: no
    addresses: [192.168.0.4/24]
    gateway4: 192.168.0.1
    nameservers:
  search: [mydomain]
  addresses: [192.168.0.1,192.168.0.2,192.168.0.3]

  will not survive a reboot and required systemd-network to be restarted or
  @reboot /usr/sbin/netplan apply
  added to the crontab

  after a reboot the network can not b eaccseed and a
  systemctl status systemd-networkd produces

  systemd-networkd.service - Network Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:36:28 UTC; 2min 27s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 979 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 4.1M
   CGroup: /system.slice/systemd-networkd.service
   └─979 /lib/systemd/systemd-networkd

  Jan 26 16:38:02 firebolt systemd-networkd[979]: rtnl: received neighbor for 
link '5' we don't know about, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: rtnl: received 
neighbor message with invalid family, ignoring.
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Gained carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0: Link UP
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Link DOWN
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Lost carrier
  Jan 26 16:38:02 firebolt systemd-networkd[979]: virbr0-nic: Kernel removed an 
address we don't remember: fe80::5054:ff:fed9:7e26/64 (valid forever), ignoring.

  systemctl restart systemd-networkd resolved the issue and a

  systemctl status systemd-network producessystemd-networkd.service - Network 
Service
   Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Sun 2020-01-26 16:39:28 UTC; 41s ago
  TriggeredBy: ● systemd-networkd.socket
     Docs: man:systemd-networkd.service(8)
     Main PID: 1650 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 57662)
   Memory: 1.6M
   CGroup: /system.slice/systemd-networkd.service
   └─1650 /lib/systemd/systemd-networkd

  Jan 26 16:39:28 firebolt

[Touch-packages] [Bug 1871960] Re: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to install/upgrade: pre-dependency problem - not installing libpam-modules:amd64

** Changed in: libgtk3-perl (Ubuntu Focal)
   Status: Confirmed => Invalid

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

Title:
  package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to
  install/upgrade: pre-dependency problem - not installing libpam-
  modules:amd64

Status in libgtk3-perl package in Ubuntu:
  Invalid
Status in pango1.0 package in Ubuntu:
  Fix Released
Status in libgtk3-perl source package in Focal:
  Invalid
Status in pango1.0 source package in Focal:
  Fix Released

Bug description:
  I was updating ubuntu to the 20.04 version. Not all packages were
  updated. I receive new errors every few seconds. what should I do?

  Thanks
  safi

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.1.8-3.6ubuntu2.18.04.1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  Date: Fri Apr 10 00:36:08 2020
  ErrorMessage: pre-dependency problem - not installing libpam-modules:amd64
  InstallationDate: Installed on 2019-12-28 (102 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.1ubuntu1
  SourcePackage: pam
  Title: package libpam-modules 1.1.8-3.6ubuntu2.18.04.1 failed to 
install/upgrade: pre-dependency problem - not installing libpam-modules:amd64
  UpgradeStatus: Upgraded to focal on 2020-04-09 (0 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1219529] Re: df -x tmpfs fails to exclude udev (/dev)

2020-04-22 Thread Bryce Harrington

20.04's coreutils still has the behavior described in this bug.  /dev is
listed as type 'udev' by df but df -x udev does not exclude it; df -x
devtmpfs does.

I wonder if one way to at least resolve the confusion might be to make
the code that prints the table display devtmpfs devices as 'devtmpfs'.
An obvious alternative would be to make '-x udev' be handled like '-x
udev -x devtmpfs'.  Another alternative would be to overload '-x tmpfs'
to exclude also udev and devtmpfs.  It's not clear what the best
solution would be.

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

Title:
  df -x tmpfs fails to exclude udev (/dev)

Status in coreutils:
  New
Status in coreutils package in Ubuntu:
  Triaged

Bug description:
  The command:

  $ /bin/df -x tmpfs

  should exclude all filesystems of type tmpfs. The udev filesystem
  mounted at /dev is of this type:

  $ stat -f /dev
File: "/dev"
  ID: 0Namelen: 255 Type: tmpfs
  Block size: 4096   Fundamental block size: 4096
  Blocks: Total: 4109101Free: 4109098Available: 4109098
  Inodes: Total: 4109101Free: 4108501

  However, df still displays this filesystem:

  $ df -l -x tmpfs
  Filesystem  1K-blocks  Used  Available Use% Mounted on
  ...
  udev 1643640412   16436392   1% /dev
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: coreutils 8.20-3ubuntu5
  ProcVersionSignature: Ubuntu 3.8.0-29.42-generic 3.8.13.5
  Uname: Linux 3.8.0-29-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.3
  Architecture: amd64
  Date: Sun Sep  1 15:05:40 2013
  InstallationDate: Installed on 2013-08-31 (0 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 843306] Re: df ignores fs type none in options

2020-04-22 Thread Bryce Harrington

Modern df lists the actual fs types for those 'none' devices.  E.g.
udev, tmpfs, et al.   I'm guessing the reason that '-x none' was not
excluding them in this old df version was because the type wasn't
literally 'none' but perhaps \0 or else was just not being displayed.

In any case, I no longer am reproducing this very old bug, so am closing
it out as fixed.

** Changed in: coreutils (Ubuntu)
   Status: New => Fix Released

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

Title:
  df ignores fs type none in options

Status in coreutils package in Ubuntu:
  Fix Released

Bug description:
  df appears to ignore the filesystem type "none" when specifying
  options on the command line. Some example output:

  gecko@magina ~> df
  Filesystem   1K-blocks  Used Available Use% Mounted on
  /dev/sda2 16018264   5669900   9534672  38% /
  none   2020908   652   2020256   1% /dev
  none   202863268   2028564   1% /dev/shm
  none   2028632   440   2028192   1% /var/run
  none   2028632 0   2028632   0% /var/lock
  /dev/sdb6457072296  42896024 390958336  10% /home
  [four different "none" systems]

  gecko@magina ~> df -x none
  Filesystem   1K-blocks  Used Available Use% Mounted on
  /dev/sda2 16018264   5669900   9534672  38% /
  none   2020908   652   2020256   1% /dev
  none   202863268   2028564   1% /dev/shm
  none   2028632   440   2028192   1% /var/run
  none   2028632 0   2028632   0% /var/lock
  /dev/sdb6457072296  42896032 390958328  10% /home
  [would expect "none" systems not to appear]

  gecko@magina ~> df -t none
  df: no file systems processed
  [would expect only "none" systems to appear]

  
  I have no idea on whether this behaviour is intentional, however I do know 
that it causes a minor bug to appear in the munin package - the df plugin is 
unable to ignore a bunch of filesystems even though it is configured to do so 
by default.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: coreutils 8.5-1ubuntu6
  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
  Uname: Linux 2.6.38-10-generic x86_64
  Architecture: amd64
  Date: Tue Sep  6 23:48:25 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   LANG=en_GB.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to natty on 2011-08-04 (33 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1495711] Re: df only shows one mountpoint

2020-04-22 Thread Bryce Harrington

I'm not able to reproduce this on focal, with multiple nfs mount points
mounted.

If it is still reproducible on newer versions of Ubuntu, can you provide
the full output of df, as well as log files /etc/fstab and /etc/exports
from the nfs server?  The output of dmesg (from boot) from the client
may also give clues.

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

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

Title:
  df only shows one mountpoint

Status in coreutils package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 14.04.3 LTS
  Release:  14.04
  coreutils:
Installed: 8.21-1ubuntu5.1
Candidate: 8.21-1ubuntu5.1
Version table:
   *** 8.21-1ubuntu5.1 0
  500 http://nl.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   8.21-1ubuntu5 0
  500 http://nl.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  It seems like df only shows one nfs mountpoint while more are mounted.

  root@klondike:~# mount | grep nfs
  192.168.1.2:/volume1/test1 on /test1 type nfs 
(rw,vers=4,addr=192.168.1.2,clientaddr=192.168.1.10)
  192.168.1.2:/volume1/test2 on /test2 type nfs 
(rw,vers=4,addr=192.168.1.2,clientaddr=192.168.1.10)
  192.168.1.2:/volume1/test3 on /test3 type nfs 
(rw,vers=4,addr=192.168.1.2,clientaddr=192.168.1.10)
  192.168.1.2:/volume1/test4 on /test4 type nfs 
(rw,vers=4,addr=192.168.1.2,clientaddr=192.168.1.10)

  root@klondike:~# df -h | grep ^192.168.1.2
  192.168.1.2:/volume1/test2  8.1T  1.4T  6.8T  17% /test2

  root@klondike:~# cat /etc/fstab | grep ^192.168.1.2
  192.168.1.2:/volume1/test1 /test1 nfs vers=4,auto 0 0
  192.168.1.2:/volume1/test2 /test2 nfs vers=4,auto 0 0
  192.168.1.2:/volume1/test3 /test3 nfs vers=4,auto 0 0
  192.168.1.2:/volume1/test4 /test4 nfs vers=4,auto 0 0

  root@klondike:~# cat /proc/mounts  | grep ^192.168.1.2
  192.168.1.2:/volume1/test1 /test1 nfs4 
rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.2
 0 0
  192.168.1.2:/volume1/test2 /test2 nfs4 
rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.2
 0 0
  192.168.1.2:/volume1/test3 /test3 nfs4 
rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.2
 0 0
  192.168.1.2:/volume1/test4 /test4 nfs4 
rw,relatime,vers=4.0,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=192.168.1.10,local_lock=none,addr=192.168.1.2
 0 0

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870410] Re: wireless does not work on boot on RPi 3s

This bug was fixed in the package systemd - 245.4-4ubuntu3

---
systemd (245.4-4ubuntu3) focal; urgency=medium

  * dhcp: Allow setting request options again
link_configure() may be called multiple times on a link causing request 
options
set multiple times. (LP: #1870410)
File: debian/patches/dhcp-Allow-setting-request-options-again.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4c48893eb04b01a2ec62d2d2823a79a9f5cb2b80
  * Don't try calling NULL callback in bus_wait_for_units_clear.
This fixes a crash most frequently occurring in the Unity session
(LP: #1870930)
File: 
debian/patches/shared-Don-t-try-calling-NULL-callback-in-bus_wait_for_un.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b2ec1a3367cef401f8de745fecc9c385f020be78

 -- Balint Reczey   Wed, 22 Apr 2020 11:04:26 +0200

** Changed in: systemd (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  wireless does not work on boot on RPi 3s

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  I've setup a wireless config in /etc/netplan/config.yaml and it does
  not activate on boot. I have to run 'sudo netplan apply' to get my
  wireless connected. This works fine on an RPi4 but not an RPi3B.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
  Uname: Linux 5.4.0-1006-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: armhf
  Date: Thu Apr  2 19:02:27 2020
  Lspci:
   
  Lsusb:
   Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
   |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
   |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, 
Driver=smsc95xx, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870930] Re: systemctl crashed with SIGSEGV

This bug was fixed in the package systemd - 245.4-4ubuntu3

---
systemd (245.4-4ubuntu3) focal; urgency=medium

  * dhcp: Allow setting request options again
link_configure() may be called multiple times on a link causing request 
options
set multiple times. (LP: #1870410)
File: debian/patches/dhcp-Allow-setting-request-options-again.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4c48893eb04b01a2ec62d2d2823a79a9f5cb2b80
  * Don't try calling NULL callback in bus_wait_for_units_clear.
This fixes a crash most frequently occurring in the Unity session
(LP: #1870930)
File: 
debian/patches/shared-Don-t-try-calling-NULL-callback-in-bus_wait_for_un.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=b2ec1a3367cef401f8de745fecc9c385f020be78

 -- Balint Reczey   Wed, 22 Apr 2020 11:04:26 +0200

** Changed in: systemd (Ubuntu Focal)
   Status: Confirmed => Fix Released

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

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)

2020-04-22 Thread Dominik

It also affects Linux Mint 19.3. 
I had problems with audio also, so i had to add two lines:

echo "options snd-hda-intel dmic_detect=0" | sudo tee -a 
/etc/modprobe.d/alsa-base.conf
echo "blacklist snd_soc_skl" | sudo tee -a /etc/modprobe.d/blacklist.conf

After executing these two commands audio is present again but still no
success with internal microphone. Fortunately i have detachable
microphone in my Creative Fatality headphones so after i have inserted
this microphone in microphone socket, microphone has appeared inside
pavucontrol and i am now able to record voice using this site: https
://online-voice-recorder.com/pl/ for example.

I have noticed that there are more discussions about this problem:
- https://online-voice-recorder.com/pl/
- https://github.com/thesofproject/linux/issues/1877

P.S. I have also tried to manually remap pins using: hdajackretask but
with no success.

** Bug watch added: github.com/thesofproject/linux/issues #1877
   https://github.com/thesofproject/linux/issues/1877

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

Title:
  Alsa not detecting internal microphone [ALC255] (Realtek)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer
  Aspire VN7-792G and noticed, that the internal microphone doesn't
  work. The computer has been released a couple of months ago and it's
  Intel Skylake -based with a Sunrise Point -based motherboard.

  INFO: The problem exists in Ubuntu 15.10 too, only microphone jack
  detected. Currently using Ubuntu 16.04 for proper hardware support.

  Alsa reports the audio device to be:

  Card: HDA Intel PCH
  Chip: Intel Skylake HDMI

  The speakers are working fine, but both alsamixer and pavucontrol
  (Pulseaudio Volume Control) raport the unplugged external microphone
  connector as the only sound input.

  I have tried many of the alsa model configurations (options snd-hda-
  intel model=something) without success, alsa finds only the microphone
  jack, which works fine when I plug an external microphone in it.

  Here's some info:

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H
  HD Audio (rev 31)

  cat /proc/asound/cards:

  0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0x8432 irq 128

  And a clip from dmesg | grep snd:

  [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0
  [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [3.047514] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x1a

  One problem is that I can't find any model options (options snd-hda-
  intel model=something) or other parameters for the card's model
  (ALC255), I suppose this issue is relatively new.

  /Dennis
  --- 
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dennis 1180 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2015-11-11 (23 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20151110)
  Package: alsa-driver (not installed)
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Tags:  xenial
  Uname: Linux 4.2.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/25/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.02
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Aspire VN7-792G
  dmi.board.vendor: Acer
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02:
  dmi.product.name: Aspire VN7-792G
  dmi.product.version: V1.02
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   :

[Touch-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

2020-04-22 Thread suKo

Using an NVIDIA GTX 1080 on 20.04 with the latest daily image I can
confirm this bug still exists. Removing the "splash" option from the
/etc/default/grub file variable GRUB_CMDLINE_LINUX_DEFAULT seems to fix
the issue. I too encountered this with automatic boot enabled, and it
also occurs no matter which version of the NVIDIA driver I use (except
for the FOSS driver). Unusually, this does not occur on my laptop which
also has an NVIDIA GPU (in this case, a 1650).

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in gdm3 source package in Eoan:
  Confirmed
Status in gnome-session source package in Eoan:
  Confirmed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau:

[Touch-packages] [Bug 1873867] Re: ubuntu-drivers changes kernel flavour when installing nvidia

2020-04-22 Thread Steve Langasek

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

Title:
  ubuntu-drivers changes kernel flavour when installing nvidia

Status in linux package in Ubuntu:
  Incomplete
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Fix Committed
Status in linux source package in Focal:
  Incomplete
Status in nvidia-graphics-drivers-440 source package in Focal:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Committed
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  $ dpkg-query -W linux-image-*
  linux-image-5.4.0-25-generic  5.4.0-25.29
  linux-image-generic-hwe-20.04 5.4.0.25.31

  $ ubuntu-drivers list
  nvidia-driver-390
  nvidia-driver-435
  nvidia-driver-440

  
  $ sudo ubuntu-drivers install
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following additional packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-kernel-common-440
nvidia-kernel-source-440 nvidia-prime nvidia-settings nvidia-utils-440 
screen-resolution-extra xserver-xorg-video-nvidia-440
  Suggested packages:
fdutils linux-doc | linux-source-5.4.0 linux-tools 
linux-headers-5.4.0-25-lowlatency
  Recommended packages:
libnvidia-compute-440:i386 libnvidia-decode-440:i386 
libnvidia-encode-440:i386 libnvidia-ifr1-440:i386 libnvidia-fbc1-440:i386 
libnvidia-gl-440:i386
  The following NEW packages will be installed:
libnvidia-cfg1-440 libnvidia-common-440 libnvidia-compute-440 
libnvidia-decode-440 libnvidia-encode-440 libnvidia-extra-440 
libnvidia-fbc1-440 libnvidia-gl-440 libnvidia-ifr1-440
linux-image-5.4.0-25-lowlatency linux-modules-5.4.0-25-lowlatency 
linux-modules-nvidia-440-5.4.0-25-lowlatency 
linux-modules-nvidia-440-lowlatency-hwe-20.04 nvidia-compute-utils-440 
nvidia-driver-440
nvidia-kernel-common-440 nvidia-kernel-source-440 nvidia-prime 
nvidia-settings nvidia-utils-440 screen-resolution-extra 
xserver-xorg-video-nvidia-440
  0 upgraded, 22 newly installed, 0 to remove and 0 not upgraded.

  I was expecting for it to pick linux-modules-nvidia-440-generic-
  hwe-20.04 not linux-modules-nvidia-440-lowlatency-hwe-20.04

  As if it sorted things and picked last one?

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870410] Re: wireless does not work on boot on RPi 3s

2020-04-22 Thread Steve Langasek

** Changed in: systemd (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  wireless does not work on boot on RPi 3s

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  I've setup a wireless config in /etc/netplan/config.yaml and it does
  not activate on boot. I have to run 'sudo netplan apply' to get my
  wireless connected. This works fine on an RPi4 but not an RPi3B.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
  Uname: Linux 5.4.0-1006-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: armhf
  Date: Thu Apr  2 19:02:27 2020
  Lspci:
   
  Lsusb:
   Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
   |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
   |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, 
Driver=smsc95xx, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874262] Re: User session does not start: xkbcomp "Internal error: Could not resolve keysym Invalid"

2020-04-22 Thread El jinete sin cabeza

https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14

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

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

** Description changed:

+ https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14
  https://gitlab.gnome.org/GNOME/gdm/-/issues/593
  
  ---
  
  Today I tried to log into my ubuntu session with my personal account
  through Xorg and Xwayland. And I couldn't, I had to install lightdm and
  to be able to enter.
  
  In my experience, I found this message ($journalctl):
  Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum 
keycode 569, clipping.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes 
above 255.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not 
resolve keysym Invalid
  Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not 
fatal to the X server
  
  Attached log of the attempt to log in.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.6.6-050606-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 09:54:26 2020
  InstallationDate: Installed on 2018-12-02 (506 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

** Bug watch added: gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues #14
   https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14

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

Title:
  User session does not start: xkbcomp "Internal error: Could not
  resolve keysym Invalid"

Status in gdm3 package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  New

Bug description:
  https://gitlab.freedesktop.org/xorg/app/xkbcomp/-/issues/14
  https://gitlab.gnome.org/GNOME/gdm/-/issues/593

  ---

  Today I tried to log into my ubuntu session with my personal account
  through Xorg and Xwayland. And I couldn't, I had to install lightdm
  and to be able to enter.

  In my experience, I found this message ($journalctl):
  Apr 22 09:06:44 romanescu gnome-shell [3651]: The XKEYBOARD keymap compiler 
(xkbcomp) reports:
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Warning: Unsupported maximum 
keycode 569, clipping.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> X11 cannot support keycodes 
above 255.
  Apr 22 09:06:44 romanescu gnome-shell [3651]:> Internal error: Could not 
resolve keysym Invalid
  Apr 22 09:06:44 romanescu gnome-shell [3651]: Errors from xkbcomp are not 
fatal to the X server

  Attached log of the attempt to log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  Uname: Linux 5.6.6-050606-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 09:54:26 2020
  InstallationDate: Installed on 2018-12-02 (506 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872259] Re: software-properties-gtk crashed with gi.repository.GLib.GError in init(): g-io-error-quark: Se alcanzó el tiempo de expiración (24)

2020-04-22 Thread Mike Salvatore

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  software-properties-gtk crashed with gi.repository.GLib.GError in
  __init__(): g-io-error-quark: Se alcanzó el tiempo de expiración (24)

Status in software-properties package in Ubuntu:
  New

Bug description:
  livepatch

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashCounter: 1
  CurrentDesktop: Budgie:GNOME
  Date: Sat Apr 11 20:23:24 2020
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2020-04-11 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Beta amd64 
(20200409)
  InterpreterPath: /usr/bin/python3.8
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk --open-tab=4
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=es_CO:es
   LANG=es_CO.UTF-8
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonArgs: ['/usr/bin/software-properties-gtk', '--open-tab=4']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with gi.repository.GLib.GError in 
__init__(): g-io-error-quark: Se alcanzó el tiempo de expiración (24)
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

2020-04-22 Thread Matěj Valášek

Is normal that, when is music(sound) play to external speakers and I
connect wired headset,music is still playing into the external speakers
and into the headset?

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

Title:
  External audio device shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker, or none at
  all.

Status in gnome-control-center:
  Unknown
Status in PulseAudio:
  New
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  In Progress
Status in gnome-control-center source package in Focal:
  Invalid
Status in pulseaudio source package in Focal:
  In Progress

Bug description:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

  1. Connect an audio interface. I tried with BT headphones and speakers as 
well as a USB microphone/output.
  2. Make sure it's the one selected as "Output device"
  3. Click "Test"
  -> the test sound outputs from the internal laptop speakers (NOK)
  4. Select "Speakers - Built-in Audio" as Output device and click "Test"
  -> the test sound outputs from the internal laptop speakers (OK)
  5. Try to switch back to the BT device and click Test
  -> same result as in step 3

  Tested with 2 different BT devices (one headset and one speaker) as
  well as a USB audio interface (Zoom H2N microphone).

  Attached are btmon logs captured during the procedure described above,
  and pactl logs capture after step 7.

  I was previously using 19.04 and 19.10 on this device and never
  experienced this kind of issue.

  Up to this morning, it was harder to connect the BT device, but once
  connected, the sound would output on it as expected. Now, the BT
  connection seems to work better, but I can't output the sound to the
  BT device...

  I tried to reboot the device, and also to suspend/resume, but in each
  case, the BT device can connect back, but the sound is still output
  from the internal laptop speakers, even when the BT device is selected
  in the Sound settings.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1566 F pulseaudio
   /dev/snd/pcmC0D0c:   pieq   1566 F...m pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  5 22:15:50 2020
  InstallationDate: Installed on 2020-01-17 (48 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.14.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7370
  dmi.product.sku: 07E9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1866194/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870410] Re: wireless does not work on boot on RPi 3s

@daniel-thewatkins I used a config very similar to
https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1870346/comments/4 , so LP: #1870346 may be fixed as well with
systemd 245.4-4ubuntu3.

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

Title:
  wireless does not work on boot on RPi 3s

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  I've setup a wireless config in /etc/netplan/config.yaml and it does
  not activate on boot. I have to run 'sudo netplan apply' to get my
  wireless connected. This works fine on an RPi4 but not an RPi3B.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
  Uname: Linux 5.4.0-1006-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: armhf
  Date: Thu Apr  2 19:02:27 2020
  Lspci:
   
  Lsusb:
   Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
   |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
   |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, 
Driver=smsc95xx, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870410] Re: wireless does not work on boot on RPi 3s

2020-04-22 Thread Dan Watkins

How does this relate to bug 1870346?

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

Title:
  wireless does not work on boot on RPi 3s

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  I've setup a wireless config in /etc/netplan/config.yaml and it does
  not activate on boot. I have to run 'sudo netplan apply' to get my
  wireless connected. This works fine on an RPi4 but not an RPi3B.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
  Uname: Linux 5.4.0-1006-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: armhf
  Date: Thu Apr  2 19:02:27 2020
  Lspci:
   
  Lsusb:
   Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
   |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
   |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, 
Driver=smsc95xx, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1759014] Re: Netplan has no way to control DHCP client

2020-04-22 Thread Franco

I'm using the version  0.98-0ubuntu1~18.04.1, and the bug is NOT fixed
using this:

network:
  version: 2
  renderer: NetworkManager
  ethernets:
# === fibertel ===
enp1s0:
  dhcp4: yes
  dhcp4-overrides:
use-dns: no  
  dhcp6: no
  nameservers:
addresses: 
[1.1.1.1,8.8.8.8,208.67.222.222,1.0.0.1,8.8.4.4,208.67.220.220]

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

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released
Status in netplan.io source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873989] Re: Please remove wallpaper from Ubuntu

** No longer affects: ubuntu-meta (Ubuntu)

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

Title:
  Please remove wallpaper from Ubuntu

Status in wallpaper package in Ubuntu:
  Fix Released

Bug description:
  Ancient Ubuntu-only package with no rdeps that FTBFS on rebuild. No
  new upstream release since 2002 (https://www.cgarbs.de/stuff.en.html).
  Appears to just check if a given image(s) can be used as wallpaper -
  doesn't seem to merit inclusion as a package to me (the Bash script is
  available on the developer's site if people want it).

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]

2020-04-22 Thread Kai-Heng Feng

This requires another system to use SSH client to connect to the
affected system.

However, that's another bug so I'll just enable those configs for now.

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

Title:
  ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to
  submit batchbuffer: Input/output error]

Status in linux package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't 
recognize graphic driver.
  - run udo apt-get install xserver-xorg-video-intel
  0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 24 14:29:01 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd]
  InstallationDate: Installed on 2020-01-24 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub
   Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. T100HAN
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T100HAN.221
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T100HAN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T100HAN
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872146] Re: Audio on Headphones stopped working

2020-04-22 Thread Shaun

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

Still seems to be the same.

I booted from a Manjaro USB Pendrive.
The sounds works then on all devices.

Back in Kubuntu 20.04 only normal speakers works and Bluetooth HEadsets.

Any audio via my Headphone Jack does not.

Any info I can get.

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

Title:
  Audio on Headphones stopped working

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Audio via my headphones worked yesterday, Today no such luck.

  When I plug in my headphone, Plasma picks it up but no sound.

  Bluetooth headset still works.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.18
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Fri Apr 10 23:03:09 2020
  InstallationDate: Installed on 2020-04-05 (5 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200404)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

** Tags added: id-5e861a6d29650f3423a935c0

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

Title:
  initramfs unpacking failed

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  "initramfs unpacking failed: Decoding failed",  message appears on
  boot up.

  If I "update-initramfs" using gzip instead of lz, then boot up passes
  without decoding failed message.

  ---

  However, we currently believe that the decoding error reported in
  dmesg is actually harmless and has no impact on usability on the
  system.

  Switching from lz4 to gzip compression, simply papers over the
  warning, without any benefits, and slows down boot.

  Kernel should be fixed to correctly parse lz4 compressed initrds, or
  at least lower the warning, to not be user visible as an error.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1871153] Re: /usr/bin/unattended-upgrade:apt.cache.CacheClosedException:/usr/bin/unattended-upgrade@2512:main:run:do_auto_remove:cache_commit:commit:_fetch_archives

** Tags added: id-5e8dd41b421c45209b1bd8e6

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

Title:
  /usr/bin/unattended-upgrade:apt.cache.CacheClosedException:/usr/bin
  /unattended-
  upgrade@2512:main:run:do_auto_remove:cache_commit:commit:_fetch_archives

Status in python-apt package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2512, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1986, in main
  res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2307, in run
  kernel_pkgs_kept_installed) = do_auto_remove(
File "/usr/bin/unattended-upgrade", line 1876, in do_auto_remove
  res, error = cache_commit(cache, logfile_dpkg, verbose)
File "/usr/bin/unattended-upgrade", line 861, in cache_commit
  res = cache.commit(install_progress=iprogress)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 678, in commit
  res = self._fetch_archives(fetcher, pm,
File "/usr/lib/python3/dist-packages/apt/cache.py", line 466, in 
_fetch_archives
  raise CacheClosedException(
  apt.cache.CacheClosedException: Cache object used after close() called

  ---

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870410] Re: wireless does not work on boot on RPi 3s

** Tags added: id-5e864eb1a142ba01fba1ebaa

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

Title:
  wireless does not work on boot on RPi 3s

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  I've setup a wireless config in /etc/netplan/config.yaml and it does
  not activate on boot. I have to run 'sudo netplan apply' to get my
  wireless connected. This works fine on an RPi4 but not an RPi3B.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
  Uname: Linux 5.4.0-1006-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: armhf
  Date: Thu Apr  2 19:02:27 2020
  Lspci:
   
  Lsusb:
   Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
   |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
   |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, 
Driver=smsc95xx, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1871149] Re: False apt_pkg.CacheMismatchError

** Tags added: id-5e8dd41b421c45209b1bd8e6

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

Title:
  False apt_pkg.CacheMismatchError

Status in python-apt package in Ubuntu:
  Incomplete

Bug description:
  Python-apt throws CacheMismatchError which is almost certainly false:

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2512, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1986, in main
  res = run(options, rootdir, mem_log, logfile_dpkg,
File "/usr/bin/unattended-upgrade", line 2398, in run
  new_pending_autoremovals = get_auto_removable(cache)
File "/usr/bin/unattended-upgrade", line 1789, in get_auto_removable
  return {pkg.name for pkg in cache
File "/usr/bin/unattended-upgrade", line 1790, in 
  if pkg.is_auto_removable}
File "/usr/lib/python3/dist-packages/apt/package.py", line 1269, in 
is_auto_removable
  self._pcache._depcache.is_garbage(self._pkg))
  apt_pkg.CacheMismatchError: Object of different cache passed as argument to 
apt_pkg.DepCache method

  The relevant code in u-u:

  def get_auto_removable(cache):


  # type: (apt.Cache) -> AbstractSet[str]   


  return {pkg.name for pkg in cache 


  if pkg.is_auto_removable}

  ---

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870073] Re: python-debian ftbfs in focal

** Tags added: id-5e860f388380e0127875bf4f

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

Title:
  python-debian ftbfs in focal

Status in python-debian package in Ubuntu:
  Fix Released

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963359
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18963359/+files/buildlog_ubuntu-focal-amd64.python-debian_0.1.36build1_BUILDING.txt.gz

  the failure is this:

  /bin/sh: 1: lib/debian/doc-debtags: not found

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1868246] Re: No network after subiquity LPAR installation on s390x with VLAN

** Tags added: id-5e8b82987d7c24699ed2aa56

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

Title:
  No network after subiquity LPAR installation on s390x with VLAN

Status in cloud-init:
  Invalid
Status in subiquity:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  I tried today an subiquity LPAR installation using the latest ISO (March 19) 
that includes the latest 20.03 subiquity.
  The installation itself completed fine, but after the post-install reboot the 
system didn't had a network active - please note that the LPAR is connected to 
a VLAN.

  $ ip a   
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
defaul
  t qlen 1000   
  
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 
  
  inet 127.0.0.1/8 scope host lo
  
 valid_lft forever preferred_lft forever
  
  inet6 ::1/128 scope host  
  
 valid_lft forever preferred_lft forever
  
  2: encc000:  mtu 1500 qdisc noop state DOWN group 
default q
  len 1000  
  
  link/ether a2:8d:91:85:12:e3 brd ff:ff:ff:ff:ff:ff
  
  3: enP1p0s0:  mtu 1500 qdisc noop state DOWN group 
default 
  qlen 1000 
  
  link/ether 82:0c:2d:0c:b8:70 brd ff:ff:ff:ff:ff:ff
  
  4: enP1p0s0d1:  mtu 1500 qdisc noop state DOWN group 
defaul
  t qlen 1000   
  
  link/ether 82:0c:2d:0c:b8:71 brd ff:ff:ff:ff:ff:ff
  
  5: enP2p0s0:  mtu 1500 qdisc noop state DOWN group 
default 
  qlen 1000 
  
  link/ether 82:0c:2d:0c:b7:00 brd ff:ff:ff:ff:ff:ff
  
  6: enP2p0s0d1:  mtu 1500 qdisc noop state DOWN group 
defaul
  t qlen 1000   
  
  link/ether 82:0c:2d:0c:b7:01 brd ff:ff:ff:ff:ff:ff   

  Wanting to have a look at the netplan config it turned out that there is no 
yaml file:
  $ ls -l /etc/netplan/
  total 0  

  Adding one manually and applying it worked fine.

  So looks like the installer does not properly generate or copy a
  01-netcfg.yaml to /etc/netplan.

  Please see below the entire steps as well as a compressed file with
  the entire content of /var/log

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1871145] Re: apt.Cache.clear() -> apt.Cache._depcache.init() raises Error

** Tags added: id-5e8dd41b421c45209b1bd8e6

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

Title:
  apt.Cache.clear() -> apt.Cache._depcache.init() raises Error

Status in python-apt package in Ubuntu:
  Opinion
Status in unattended-upgrades package in Ubuntu:
  Opinion

Bug description:
  Unattended-upgrades 2.1 triggers the following crash in python-apt:

File "/usr/bin/unattended-upgrade", line 1706, in try_to_upgrade
  cache.mark_upgrade_adjusted(pkg, from_user=not pkg.is_auto_installed)
File "/usr/bin/unattended-upgrade", line 438, in mark_upgrade_adjusted
  self.call_adjusted(apt.package.Package.mark_upgrade, pkg, **kwargs)
File "/usr/bin/unattended-upgrade", line 397, in call_adjusted
  self.clear()
File "/usr/lib/python3/dist-packages/apt/cache.py", line 700, in clear
  self._depcache.init()
  apt_pkg.Error: E:The package intellij-idea-ultimate needs to be reinstalled, 
but I can't find an archive for it.

  I think .clear() should not raise an error, but if it should u-u can
  catch that.

  ---

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870408] Re: casper-md5check should leave a breadcrumb which apport, ubiquity, subiquity could use

** Tags added: id-5e876fef4565976edcab3a7c

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

Title:
  casper-md5check should leave a breadcrumb which apport, ubiquity,
  subiquity could use

Status in subiquity:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in casper package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  New

Bug description:
  casper-md5check should leave a breadcrumb which apport & ubiquity can
  pick up. (subiquity too)

  There will be a file called:

  /run/casper-md5check.json

  If it does not exist, or is empty the check did not run enough to
  validate anything. Treat as skip.

  If it has content it will have:
  {
 "checksum_missmatch" : [
"./pics/red-upperleft.png",
"./pics/red-lowerleft.png"
 ],
 "result" : "fail"
  }

  optional checksum_missmatch key, which will have a list of strings
  that are files that failed md5sum.

  result key, which can have string values "pass" "fail" "skip".

  One can use python's json or yaml safe_load to parse the file into a
  dictionary.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870088] Re: xz-utils ftbfs in focal

** Tags added: id-5e860f0035274f449718d6fe

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

Title:
  xz-utils ftbfs in focal

Status in xz-utils package in Ubuntu:
  Confirmed
Status in xz-utils source package in Focal:
  Confirmed
Status in xz-utils package in Debian:
  New

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988321/+files/buildlog_ubuntu-focal-amd64.xz-utils_5.2.4-1_BUILDING.txt.gz

  dh build --parallel 
  make[2]: Leaving directory '/<>'
 dh_testroot -O--parallel
 dh_prep -O--parallel
 debian/rules override_dh_auto_install
  make[2]: Entering directory '/<>'
  dh_auto_install --builddirectory debian/xzdec-build
  dh_auto_install --builddirectory debian/normal-build
  dh_auto_install --builddirectory debian/static-build
  set -e; arch=$(dpkg-architecture -qDEB_HOST_MULTIARCH); \
  install -d debian/tmp/lib/$arch; \
  mv debian/tmp/usr/lib/$arch/liblzma.so.* debian/tmp/lib/$arch/; \
  dso=$(basename $(readlink debian/tmp/usr/lib/$arch/liblzma.so)); \
  ln -s -f /lib/$arch/$dso debian/tmp/usr/lib/$arch/liblzma.so
  mv: cannot stat 'debian/tmp/usr/lib/x86_64-linux-gnu/liblzma.so.*': No such 
file or directory
  make[2]: *** [debian/rules:34: override_dh_auto_install] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [debian/rules:4: install] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:4: binary] Error 2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1871639] Re: /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-upgrade@2512:main:run:do_install

** Tags added: id-5e8dd41b421c45209b1bd8e6

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

Title:
  /usr/bin/unattended-upgrade:AssertionError:/usr/bin/unattended-
  upgrade@2512:main:run:do_install

Status in unattended-upgrades package in Ubuntu:
  Fix Released

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1871615] Re: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of file on stdin at conffile prompt

** Tags added: id-5e8f70fa4445877284ded0cb

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

Title:
  package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in apparmor package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  I have no definite idea what happened, it just popped up randomly.

  I can only assume it was trying to show the usual update notification

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.13.3-7ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  AptOrdering:
   apparmor:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Apr  8 13:57:33 2020
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2020-03-25 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=66ca0e88-1f73-48ce-a0ae-cfa14442ffe1 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.1ubuntu1
  SourcePackage: apparmor
  Syslog:
   Apr  8 13:04:35 sebipc dbus-daemon[1090]: [system] AppArmor D-Bus mediation 
is enabled
   Apr  8 13:04:44 sebipc dbus-daemon[1479]: [session uid=125 pid=1479] 
AppArmor D-Bus mediation is enabled
   Apr  8 13:05:16 sebipc dbus-daemon[2072]: [session uid=1000 pid=2072] 
AppArmor D-Bus mediation is enabled
   Apr  8 13:55:52 sebipc dbus-daemon[2072]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/" 
interface="org.freedesktop.DBus.Introspectable" member="Introspect" mask="send" 
name="com.canonical.Unity" pid=11890 
label="snap.telegram-desktop.telegram-desktop" peer_pid=2359 
peer_label="unconfined"
   Apr  8 13:55:53 sebipc dbus-daemon[2072]: apparmor="DENIED" 
operation="dbus_method_call"  bus="session" path="/org/freedesktop/ScreenSaver" 
interface="org.freedesktop.ScreenSaver" member="GetSessionIdleTime" mask="send" 
name="org.freedesktop.ScreenSaver" pid=11890 
label="snap.telegram-desktop.telegram-desktop" peer_pid=2462 
peer_label="unconfined"
  Title: package apparmor 2.13.3-7ubuntu4 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apparmor.d.abstractions.base: 2020-03-26T13:00:28.401582

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1871633] Re: /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-upgrade@2512:main:run:mark_upgrade_adjusted:call_adjusted

** Tags added: id-5e8dd41b421c45209b1bd8e6

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

Title:
  /usr/bin/unattended-upgrade:NoAllowedOriginError:/usr/bin/unattended-
  upgrade@2512:main:run:mark_upgrade_adjusted:call_adjusted

Status in unattended-upgrades package in Ubuntu:
  Fix Released

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874247] [NEW] Don't work wired connection regression focal

2020-04-22 Thread Igor Zubarev

Public bug reported:

After upgrade to focal I can't connect to wired network. It was ok in
19.10 before

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia wl
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 22 15:44:52 2020
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
IpRoute:
 default via 192.168.1.254 dev wlp7s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp7s0 scope link metric 1000 
 192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.67 metric 600
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Don't work wired connection regression focal

Status in network-manager package in Ubuntu:
  New

Bug description:
  After upgrade to focal I can't connect to wired network. It was ok in
  19.10 before

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia wl
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 22 15:44:52 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.254 dev wlp7s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp7s0 scope link metric 1000 
   192.168.1.0/24 dev wlp7s0 proto kernel scope link src 192.168.1.67 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used

2020-04-22 Thread Ubuntu Foundations Team Bug Bot

** Tags added: patch

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

Title:
  explicit key offered after all agent keys, auth can fail before
  explicit key used

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  A user creates an ssh key and specifies it on the cmdline with 'ssh -i
  new_key user@host'.  The connection fails with the message "Too many
  authentication failures" displayed to the user.

  This would lead the user to believe that they failed to put the public
  portion of the new key on the destination and it will probably be hard
  for the average user to debug this.

  The root of this issue is that the user has a number of keys in
  ~/.ssh/ registered with their ssh agent.  The ssh command is offering
  each of these keys from the agent to the remote system before trying
  the explicit key from the command line.  There are enough agent keys
  to reach the failure limit (usually 5 keys) with the remote before
  they get to the explicit key.

  The solution today for the user is to head down into the ssh_config
  man page to find '-o IdentitiesOnly=yes' to skip the agent keys and
  only use the specified key.  But they're unlikely to do this because
  '-i' in the ssh man page doesn't suggest this and they'd only look for
  this if they actually understood the root cause of the problem, which
  is a bit cruel.

  We should consider changing the order of the keys offered to the
  remote to use explicit keys first followed by agent keys.  It would
  seem to me that this would honor the users intent of explicitly
  specifying a key to use.

  The current order makes this difficult for anyone fielding a user's
  authentication failure report as they must double check that ssh
  managed to actually try the key the user specified before it raised an
  error message about authentication failures.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

** Tags added: id-5e988df7fb344884f67bc04f

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: thermald.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel thermald[1256]: [WARN]Terminating ...
  Apr 08 06:09:19 Keschdeichel avahi-daemon[1204]: Got SIGTERM, quitting.
  Apr 08 06:09:19 Keschdeichel systemd[1]: udisks2.service: Unexpected error 
response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel ModemManager[1308]:   Caught signal, 
shutting down...
  Apr 08 06:09:19 Keschdeichel systemd[1]: switcheroo-control.service: 
Unexpected error response from

[Touch-packages] [Bug 1870930] Re: systemctl crashed with SIGSEGV

** Tags added: id-5e988b1f5904c96643cb5442

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

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872560] Re: heap-based buffer overflow in bson.c

2020-04-22 Thread Ubuntu Foundations Team Bug Bot

The attachment "bson-fix-overflow.patch" seems to be a patch. If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
heap-based buffer overflow in bson.c

Status in whoopsie package in Ubuntu:
New

Bug description:
Hi,

I have found a security issue on whoopsie 0.2.69 and earlier.

@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]

const uint32_t len = strlen( name ) + 1;

- Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value.
- Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.

@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]

b->data = bson_realloc( b->data, new_size );

- Unexpected small memory region is allocated due to above integer
overflow.

@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]

bson_append( b, name, len );

- Memory corruption happens when unexpected small memory region is
allocated.

$ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
$ cat fake.crash
AAA … AA : B

2) Trigger the whoopsie to read the fake.crash file
- Just create 'fake.upload' file by touch command.
- Or launch apport-gtk gui or apport-bug cli application.

3) Check out the result
- After a while, the whoopsie has been killed by segmentation fault.

Sincerely,

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872902] Re: Upgrade to Focal now removes chrony

** Tags added: id-5e988a9a09d61740cd5889de

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

Title:
  Upgrade to Focal now removes chrony

Status in Release Notes for Ubuntu:
  New
Status in apt package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Invalid
Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in apt source package in Focal:
  Invalid
Status in chrony source package in Focal:
  Invalid
Status in ntp source package in Focal:
  Invalid
Status in systemd source package in Focal:
  Invalid
Status in ubuntu-release-upgrader source package in Focal:
  Triaged

Bug description:
  Due to changes in systemd for bug 1849156 this issue now happens.

  On an upgrade for people that had chrony installed on a do-release upgrade it 
now will:
  Calculating the changes
MarkInstall systemd-timesyncd:amd64 < none -> 245.4-4ubuntu1 @un uN Ib > 
FU=1
 Removing: chrony
  MarkDelete chrony:amd64 < 3.2-4ubuntu4.2 -> 3.5-6ubuntu3 @ii umU Ib > FU=0

  That isn't what users want, those who had chrony installed would want
  to get chrony upgraded and systemd-timesyncd (which now is a separate
  pacakge) not installed.

  I'd ask you to revise the dependencies that got changes in systemd
  245.4-2ubuntu1 so that on an upgrade from e.g. Bionic chrony stays
  installed as that was an opt-in chances are quite high people would
  want to keep it that way.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874142] Re: lvm2-lvmlocking.service incorrectly uses nonexistent option --lock-opt autowait

2020-04-22 Thread WGH

https://www.redhat.com/archives/lvm-devel/2020-April/msg00017.html fixed
upstream, but still affects both Ubuntu 18.04 and 20.04
(/lib/systemd/system/lvm2-lvmlocking.service and
/lib/systemd/system/lvmlocks.service correspondingly)

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

Title:
  lvm2-lvmlocking.service incorrectly uses nonexistent option --lock-opt
  autowait

Status in lvm2 package in Ubuntu:
  New

Bug description:
  The lvm2-lvmlocking.service systemd unit installed by lvm2-lockd
  package has the following line:

  # start lockspaces and wait for them to finish starting
  ExecStart=@SBINDIR@/lvm vgchange --lock-start --lock-opt autowait

  This is unfortunately wrong: the autowait option was dropped in this
  commit: https://www.redhat.com/archives/lvm-
  devel/2015-July/msg00091.html, and attempting to specify it causes the
  opposite effect: no waiting is done at all.

  It should've said --lock-opt auto.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870811] Re: compile auto test failure, and root-unittest failure, is extremely noisy

2020-04-22 Thread Dan Streetman

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

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

Title:
  compile auto test failure, and root-unittest failure, is extremely
  noisy

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Won't Fix
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  failure in the compile-time tests (also run from the root-unittest
  autopkgtest) prints out the entire meson testlog.txt, which shows the
  output of all tests, including passed ones, not just the failed test
  output.  This makes it extremely difficult to find the output of the
  failed test(s) and creates a massive log to download.

  [test case]

  see any failed build, e.g.
  
https://launchpadlibrarian.net/471257226/buildlog_ubuntu-eoan-amd64.systemd_245.218-g69d06b7acf+19.10.20200328163536_BUILDING.txt.gz

  [regression potential]

  any regression would likely occur during test failure, likely
  resulting in lack of details of the test failure; or, a regression
  caused by the additional meson parameter could cause build failure.

  [scope]

  Xenial does not use meson, so can not be adjusted.  This is needed in
  Bionic and later.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873989] Re: Please remove wallpaper from Ubuntu

2020-04-22 Thread Matthias Klose

Removing packages from focal:
wallpaper 0.1-1ubuntu1 in focal
wallpaper 0.1-1ubuntu1 in focal amd64
wallpaper 0.1-1ubuntu1 in focal arm64
wallpaper 0.1-1ubuntu1 in focal armhf
wallpaper 0.1-1ubuntu1 in focal i386
wallpaper 0.1-1ubuntu1 in focal ppc64el
wallpaper 0.1-1ubuntu1 in focal riscv64
wallpaper 0.1-1ubuntu1 in focal s390x
Comment: LP: #1873989; remove, no rdeps
1 package successfully removed.


** Changed in: wallpaper (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please remove wallpaper from Ubuntu

Status in ubuntu-meta package in Ubuntu:
  New
Status in wallpaper package in Ubuntu:
  Fix Released

Bug description:
  Ancient Ubuntu-only package with no rdeps that FTBFS on rebuild. No
  new upstream release since 2002 (https://www.cgarbs.de/stuff.en.html).
  Appears to just check if a given image(s) can be used as wallpaper -
  doesn't seem to merit inclusion as a package to me (the Bash script is
  available on the developer's site if people want it).

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1862657] Re: systemd autopkgtest 'logind' fails when running with linux-kvm

2020-04-22 Thread Dan Streetman

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

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

Title:
  systemd autopkgtest 'logind' fails when running with linux-kvm

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Eoan:
  In Progress
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  the logind autopkgtest tries to access /sys/power/state, but because
  linux-kvm has CONFIG_PM unset, there is no /sys/power/state file

  [test case]

  check autopkgtest, e.g.:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/s/systemd/20200210_144351_da247@/log.gz

  autopkgtest [13:48:53]: test logind: ---]
  autopkgtest [13:48:53]: test logind:  - - - - - - - - - - results - - - - - - 
- - - -
  logind   FAIL stderr: grep: /sys/power/state: No such file or 
directory
  autopkgtest [13:48:53]: test logind:  - - - - - - - - - - stderr - - - - - - 
- - - -
  grep: /sys/power/state: No such file or directory

  [regression potential]

  regressions would likely involve incorrectly skipped logind test.

  [scope]

  this fails for all releases; Xenial, Bionic, Eoan, and Focal.

  [other info]

  it's unclear if linux-kvm should have CONFIG_PM (and other config)
  enabled or not.

  However, it's not the intention of systemd's autopkgtests to look for
  missing config in the kernel; the test already skips if 'mem' isn't in
  /sys/power/state, so it should also skip if /sys/power/state isn't
  present at all.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1860432] Re: juju agent fails to start on focal

There seems to be nothing related to fix in systemd.

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

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

Title:
  juju agent fails to start on focal

Status in juju:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Focal:
  Invalid

Bug description:
  during bootstrap, add-machine, deploy Juju fails on Focal due to
  systemd not finding the service.


  ll /etc/systemd/system
  jujud-machine-1.service -> 
/lib/systemd/system/jujud-machine-1/jujud-machine-1.service

  
  which is linked and calls

  ExecStart=/lib/systemd/system/jujud-machine-1/exec-start.sh

  
  The fact that it's in a jujud-machine-1 folder vs /system itself appears to 
be causing systemd to not be able to run it.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870410] Re: wireless does not work on boot on RPi 3s

2020-04-22 Thread Dave Jones

Confirmed test build in the PPA in comment 13 (245.4-4ubuntu3) fixes the
issue on both archs (armhf and arm64) on the Pi 3B, 3A+, and 3B+ (re-
tested 4B as well to ensure nothing broken, and it's still working).

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

Title:
  wireless does not work on boot on RPi 3s

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  I've setup a wireless config in /etc/netplan/config.yaml and it does
  not activate on boot. I have to run 'sudo netplan apply' to get my
  wireless connected. This works fine on an RPi4 but not an RPi3B.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
  Uname: Linux 5.4.0-1006-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: armhf
  Date: Thu Apr  2 19:02:27 2020
  Lspci:
   
  Lsusb:
   Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
   |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
   |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, 
Driver=smsc95xx, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

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

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

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

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

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Confirmed

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

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

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

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870410] Re: wireless does not work on boot on RPi 3s

2020-04-22 Thread Łukasz Zemczak

** Changed in: systemd (Ubuntu Focal)
   Importance: High => Critical

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

Title:
  wireless does not work on boot on RPi 3s

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  I've setup a wireless config in /etc/netplan/config.yaml and it does
  not activate on boot. I have to run 'sudo netplan apply' to get my
  wireless connected. This works fine on an RPi4 but not an RPi3B.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
  Uname: Linux 5.4.0-1006-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: armhf
  Date: Thu Apr  2 19:02:27 2020
  Lspci:
   
  Lsusb:
   Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
   |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
   |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, 
Driver=smsc95xx, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used

2020-04-22 Thread Christian Ehrhardt 

I have a PPA at:
https://launchpad.net/~paelzer/+archive/ubuntu/bug-872145-ssh-prefer-user-configured-key

I have tested and the "IdentityFile" directive in /etc/ssh/ssh_config
does not count as "user defined". I'd have preferred if that would count
as well, but for now at least preferring the "-i" is better than nothing
and it seems to not need a major overhaul.

But other than that, this seems to work.
Former:
$ ssh -i /tmp/testkey -v horsea "echo 1" |& grep "Will attempt"
debug1: Will attempt key: /home/paelzer/.ssh/id_rsa RSA ... agent
debug1: Will attempt key: ubuntu@cpaelzer-bastion RSA ... agent
debug1: Will attempt key: paelzer@lap RSA ... agent
debug1: Will attempt key: paelzer@swarm.n RSA ... agent
debug1: Will attempt key: /tmp/testkey RSA ... explicit

Becomes:
$ ssh -i /tmp/testkey -v horsea "echo 1" |& grep "Will attempt"
debug1: Will attempt key: /tmp/testkey RSA ... explicit
debug1: Will attempt key: /home/paelzer/.ssh/id_rsa RSA ... agent
debug1: Will attempt key: ubuntu@cpaelzer-bastion RSA ... agent
debug1: Will attempt key: paelzer@lap RSA ... agent
debug1: Will attempt key: paelzer@swarm.n RSA ... agent


@Rob - could you give the PPA a try and report for your case the following once 
for the old and once for the PPAs ssh binary?
 $ ssh -i  -v  "echo 1" |& grep "Will attempt"

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

Title:
  explicit key offered after all agent keys, auth can fail before
  explicit key used

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  A user creates an ssh key and specifies it on the cmdline with 'ssh -i
  new_key user@host'.  The connection fails with the message "Too many
  authentication failures" displayed to the user.

  This would lead the user to believe that they failed to put the public
  portion of the new key on the destination and it will probably be hard
  for the average user to debug this.

  The root of this issue is that the user has a number of keys in
  ~/.ssh/ registered with their ssh agent.  The ssh command is offering
  each of these keys from the agent to the remote system before trying
  the explicit key from the command line.  There are enough agent keys
  to reach the failure limit (usually 5 keys) with the remote before
  they get to the explicit key.

  The solution today for the user is to head down into the ssh_config
  man page to find '-o IdentitiesOnly=yes' to skip the agent keys and
  only use the specified key.  But they're unlikely to do this because
  '-i' in the ssh man page doesn't suggest this and they'd only look for
  this if they actually understood the root cause of the problem, which
  is a bit cruel.

  We should consider changing the order of the keys offered to the
  remote to use explicit keys first followed by agent keys.  It would
  seem to me that this would honor the users intent of explicitly
  specifying a key to use.

  The current order makes this difficult for anyone fielding a user's
  authentication failure report as they must double check that ssh
  managed to actually try the key the user specified before it raised an
  error message about authentication failures.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used

2020-04-22 Thread Christian Ehrhardt 

Without checking deeper I'm unsure if keys listed in e.g.
/etc/ssh/ssh_config are considered as "userprovided" but lets give this
a shot.

Gladly the debug already contains "explicit" if id->userprovided is
true.

I usually get:
debug1: Will attempt key: /home/paelzer/.ssh/id_rsa RSA ... agent
debug1: Will attempt key: ubuntu@cpaelzer-bastion RSA ... agent
debug1: Will attempt key: paelzer@lap RSA ... agent
debug1: Will attempt key: pael...@swarm.naarz.dyndns.org RSA ... agent
debug1: Will attempt key: /home/paelzer/.ssh/id_dsa
debug1: Will attempt key: /home/paelzer/.ssh/id_ecdsa
debug1: Will attempt key: /home/paelzer/.ssh/id_ecdsa_sk
debug1: Will attempt key: /home/paelzer/.ssh/id_ed25519
debug1: Will attempt key: /home/paelzer/.ssh/id_ed25519_sk
debug1: Will attempt key: /home/paelzer/.ssh/id_xmss

with an -i set to a key that is in the agent, the defaults vanish.
And since the key is listed & in the agent it is preferred already

debug1: Will attempt key: /home/paelzer/.ssh/id_rsa.n RSA ... explicit agent
debug1: Will attempt key: /home/paelzer/.ssh/id_rsa RSA ... agent
debug1: Will attempt key: ubuntu@cpaelzer-bastion RSA ... agent
debug1: Will attempt key: paelzer@lap RSA ... agent

But if I create a new key and add it it is NOT preferrd (this is the bug in
discussion here)
debug1: Will attempt key: /home/paelzer/.ssh/id_rsa RSA ... agent
debug1: Will attempt key: ubuntu@cpaelzer-bastion RSA ... agent
debug1: Will attempt key: paelzer@lap RSA ... agent
debug1: Will attempt key: pael...@swarm.naarz.dyndns.org RSA ... agent
debug1: Will attempt key: /tmp/testkey RSA ... explicit

The explicit one is down below in the order since it isn't in the agent.

A final solution might want to insert them somewhere else than the very
top and/or might want to do similar with certificates. But for the test
the attached patch could be enough.

** Patch added: "experimental-1872145.debdiff"

https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1872145/+attachment/5357863/+files/experimental-1872145.debdiff

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

Title:
explicit key offered after all agent keys, auth can fail before
explicit key used

Status in openssh package in Ubuntu:
Triaged

Bug description:
A user creates an ssh key and specifies it on the cmdline with 'ssh -i
new_key user@host'. The connection fails with the message "Too many
authentication failures" displayed to the user.

This would lead the user to believe that they failed to put the public
portion of the new key on the destination and it will probably be hard
for the average user to debug this.

The root of this issue is that the user has a number of keys in
~/.ssh/ registered with their ssh agent. The ssh command is offering
each of these keys from the agent to the remote system before trying
the explicit key from the command line. There are enough agent keys
to reach the failure limit (usually 5 keys) with the remote before
they get to the explicit key.

The solution today for the user is to head down into the ssh_config
man page to find '-o IdentitiesOnly=yes' to skip the agent keys and
only use the specified key. But they're unlikely to do this because
'-i' in the ssh man page doesn't suggest this and they'd only look for
this if they actually understood the root cause of the problem, which
is a bit cruel.

We should consider changing the order of the keys offered to the
remote to use explicit keys first followed by agent keys. It would
seem to me that this would honor the users intent of explicitly
specifying a key to use.

The current order makes this difficult for anyone fielding a user's
authentication failure report as they must double check that ssh
managed to actually try the key the user specified before it raised an
error message about authentication failures.

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872560] Re: heap-based buffer overflow in bson.c

2020-04-22 Thread Seong-Joong Kim

I would like to update the contents of 'Attack Scenario'.

from:
$ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash

to:
$ python -c "print('A' * 0xFFFE + ' : ' + 'B')" > /var/crash/fake.crash

Segfault can arise when the following requirements are met, as I mentioned 
above.
- length of ‘value’ in .crash file => 0 < {length of ‘value’} < 1024
- length of ‘key’ in .crash file => UINT32_MAX - {length of ‘value’} - 7 < 
{length of ‘key’} < UINT32_MAX

Please check this issue.

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

Title:
  heap-based buffer overflow in bson.c

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  ## Vulnerability in whoopsie
  - whoopsie 0.2.69 and earlier have a heap-based buffer overflow 
vulnerability. 
  - An attacker can cause a denial of service (memory corruption and 
application crash) via a crafted .crash file.

  
  ## Basic
  When a program has been crashed, Linux system tries to create a '.crash' file 
on '/var/crash/' directory with python script located in 
'/usr/share/apport/apport'. 
  The file contains a series of system crash information including core dump, 
syslog, stack trace, memory map info, etc.
  After the creation of '.crash' file, whoopsie extracts the above information 
from the '.crash' file and encodes it into binary json (bson) format.
  Lastly, whoopsie forwards the data to a remotely connected Ubuntu Error 
Report system.

   
  ## Vulnerability
  Unfortunately, we have found a heap-based buffer overflow vulnerability 
during the encoding, when whoopsie attempts to bsonify with crafted crash file.
  The data in '.crash' file is stored in key-value form and the whoopsie 
separately measures the length of 'key' and 'value' to allocate memory region 
during the encoding. 
  A heap-based buffer overflow can occur when an integer overflow happens on a 
variable that contains length of 'key'. 
  FYI, a issue to that raised by 'value' is well covered by performing 
exception handling.

  
@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]

  const uint32_t len = strlen( name ) + 1;

  - Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value. 
  - Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.

  
@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]

  b->data = bson_realloc( b->data, new_size );

  - Unexpected small memory region is allocated due to above integer
  overflow.

  
@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]

  bson_append( b, name, len );

  - Memory corruption happens when unexpected small memory region is
  allocated.

  
  ## Attack Scenario
  1) Create a fake.crash file
  - '.crash' file is composed of the following format: 'key : value'.
  - To cause the overflow attack, the size of 'key' should be in double amount 
of INT32_MAX.
  - The size of 'value' doesn’t matter, but not zero length.

  $ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
  $ cat fake.crash
  AAA … AA : B

  
  2) Trigger the whoopsie to read the fake.crash file
  - Just create 'fake.upload' file by touch command.
  - Or launch apport-gtk gui or apport-bug cli application.

  3) Check out the result
  - After a while, the whoopsie has been killed by segmentation fault.

  Sincerely,

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

2020-04-22 Thread thrantir

I got this issue on Ubuntu 20.04 too... on this laptop I had a similar
problem on the 19.10, the touchpad didn't work at all after resum from
suspend, i used to fix that calling

sudo rmmod i2c_hid
sudo modprobe i2c_hid

and it works too on this issue on 20.04, shall we provide some more
informations to solve the problem at its root?

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

Title:
  Two-finger scrolling and click-and-drag no longer works after resuming
  from suspend

Status in Linux:
  Confirmed
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Invalid

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1765832] Re: Two finger scrolling not working after suspend

2020-04-22 Thread thrantir

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

I got this issue on Ubuntu 20.04 too... on this laptop I had a similar
problem on the 19.10, the touchpad didn't work at all after resum from
suspend, i used to fix that calling

sudo rmmod i2c_hid
sudo modprobe i2c_hid

and it works too on this issue on 20.04, shall we provide some more
informations to solve the problem at its root?

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

Title:
  Two finger scrolling not working after suspend

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When waking up my laptop, two finger scrolling is not working anymore.

  Running:

  $ modprobe -r psmouse
  $ modprobe psmouse

  restores the functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Apr 20 08:23:33 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.10, 4.15.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 5500 [17aa:2227]
  InstallationDate: Installed on 2018-04-10 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180408)
  MachineType: LENOVO 20BTS09800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N14ET26W (1.04 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BTS09800
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN14ET26W(1.04):bd01/23/2015:svnLENOVO:pn20BTS09800:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTS09800:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 3rd
  dmi.product.name: 20BTS09800
  dmi.product.version: ThinkPad X1 Carbon 3rd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872560] Re: heap-based buffer overflow in bson.c

2020-04-22 Thread Seong-Joong Kim

** Information type changed from Private Security to Public Security

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

Title:
heap-based buffer overflow in bson.c

Status in whoopsie package in Ubuntu:
New

Bug description:
Hi,

I have found a security issue on whoopsie 0.2.69 and earlier.

@[bson.c:663][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n663]

const uint32_t len = strlen( name ) + 1;

- Integer overflow occurs when length of ‘name’ exceeds INT32_MAX value.
- Here, ‘name’ indicates the ‘key’ data in ‘.crash’ file.

@[bson.c:627][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n627]

b->data = bson_realloc( b->data, new_size );

- Unexpected small memory region is allocated due to above integer
overflow.

@[bson.c:680][https://git.launchpad.net/ubuntu/+source/whoopsie/tree/lib/bson/bson.c?h=applied/0.2.69#n680]

bson_append( b, name, len );

- Memory corruption happens when unexpected small memory region is
allocated.

$ python -c "print('A' * 0x + ' : ' + 'B')" > /var/crash/fake.crash
$ cat fake.crash
AAA … AA : B

2) Trigger the whoopsie to read the fake.crash file
- Just create 'fake.upload' file by touch command.
- Or launch apport-gtk gui or apport-bug cli application.

3) Check out the result
- After a while, the whoopsie has been killed by segmentation fault.

Sincerely,

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1872145] Re: explicit key offered after all agent keys, auth can fail before explicit key used

2020-04-22 Thread Christian Ehrhardt 

There are plenty of workarounds and the internet is full of this issue.
-
https://serverfault.com/questions/36291/how-to-recover-from-too-many-authentication-failures-for-user-root
- https://www.tecmint.com/fix-ssh-too-many-authentication-failures-error/
-
https://superuser.com/questions/187779/too-many-authentication-failures-for-username
- https://blog.jasonmeridth.com/posts/ssh-too-many-authentication-failures/
-
https://security.stackexchange.com/questions/65120/ssh-always-too-many-authentication-failures
- https://www.unixtutorial.org/ssh-too-many-authentication-failures

Workarounds range from "set to PW auth only" via "disable the agent" to "don't
use an agent".
But they are all just workarounds, even those modifying
"PreferredAuthentications" can't set "commandline before agent" as "publickey"
is just one entry in that list - there just is no differentiation between
coming from agent or commandline in this argument.

In fact the issue is so common, there must be an official discussion
with the ssh community somewhere. I just haven't found it yet for all
the help-forums that are higher in the search results.

If forcing the search engines a bit the results are manyfold but old and new
all just refer to the workarounds as far as I could see:
- https://lists.mindrot.org/pipermail/openssh-unix-dev/2003-December/019931.html
- https://lists.mindrot.org/pipermail/openssh-unix-dev/2016-April/035029.html
- ...

There are many "related but not entirely the same" upstream bugs:
- https://bugzilla.mindrot.org/show_bug.cgi?id=1499
- https://bugzilla.mindrot.org/show_bug.cgi?id=1937
...
But none I could find asked for the simple suggestion here of letting the "-i"
to be "in front" of the agent-identities.

This issue is old as I mentioned…
There might be other launchpad bugs as well, but just to show how old this is
of 2003 and still open
=> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=203700

In the code they register -i/configured keys in readconf.c:add_identity_file.
There the code even differs between those picked up by default config vs those
specified by the user.
For any key in options->identity_files[n]
options->identity_file_userprovided[n] will be != 0 if provided by the user.

In sshconnect2.c:pubkey_prepare then it builds the list of keys to present.
Per function header that is:
1551 * try keys in the following order:
1552 * »1. certificates listed in the config file
1553 * »2. other input certificates
1554 *»·3. agent keys that are found in the config file
1555 *»·4. other agent keys
1556 *»·5. keys that are only listed in the config file

That flag is carried over when building the list:
1595 »···»···id->userprovided = options.identity_file_userprovided[i];
1596 »···»···TAILQ_INSERT_TAIL(, id, next);
The same is true for "certificates" in the list called "preferred"

Agent keys are in the list "agent".
If a key from the "agent" is equal to one in "files" it is dequeued from
"files" and inserted at the tail of "preferred".
Then the remaining agent keys are transferred to "preferred".
This makes the prio list mentioned above.

Eventually it Tail-appends the rest of the "files" list to "preferred"
That list is then filtered for the PubkeyAcceptedKeyTypes option and used.

The end result is in the list "preferred" and what is listed in order in "ssh
-v" as:
Will attempt key: ...

This surely needs an upstream discussion, but we could make a PoC for it
- try it with a few people here and then go for upstream.

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

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

** Bug watch added: Debian Bug tracker #203700
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=203700

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

** Changed in: openssh (Ubuntu)
Importance: Undecided => Wishlist

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

Title:
explicit key offered after all agent keys, auth can fail before
explicit key used

Status in openssh package in Ubuntu:
Triaged

This would lead the user to believe that they failed to put the public
portion of the new key on the destination and it will probably be hard
for the average user to debug this.

[Touch-packages] [Bug 1870410] Re: wireless does not work on boot on RPi 3s

A test build of systemd with the fix is building in:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3801

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

Title:
  wireless does not work on boot on RPi 3s

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  I've setup a wireless config in /etc/netplan/config.yaml and it does
  not activate on boot. I have to run 'sudo netplan apply' to get my
  wireless connected. This works fine on an RPi4 but not an RPi3B.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
  Uname: Linux 5.4.0-1006-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: armhf
  Date: Thu Apr  2 19:02:27 2020
  Lspci:
   
  Lsusb:
   Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
   |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
   |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, 
Driver=smsc95xx, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870930] Re: systemctl crashed with SIGSEGV

A test build of systemd with the fix is building in:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3801

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

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1874021] Re: avahi-browse -av is empty, mdns not working in arduino ide

2020-04-22 Thread Trent Lloyd

OK thanks for the updates. So I can see a lot of mDNS packets in the
lp1874021.pcap capture from various sources. I can see some printers,
google cast, sonoff, etc. Curiously though when you do the avahi cache
dump it isn't seeing any of these.

Wireshark is showing malformed packets for many of the responses
strangely, the IP and UDP headers indicate a different length to that of
the actual dta. Not sure if this is an issue with wireshark, the
wireless driver or whatever mDNS implementations are replying. May need
further looking at.

But it's curious though that avahi is showing absoultely no cached
services, and that it works on ethernet, given that the lp1874021.pcap
seems to show plenty of actual mDNS packets coming and going.


Could you try start Avahi (on wireless) using --debug

(1) override the systemd config with this command:
systemctl edit avahi-daemon.service

Once the editor opens, add the following 3 lines then save and squit:

[Service]
ExecStart=
ExecStart=/usr/sbin/avahi-daemon -s --debug

Then restart avahi-daemon: sudo systemctl restart avahi-daemon.service

Lastly run "avahi-browse -av", wait a minute or two, then upload a copy
of the "journalctl -u avahi-daemon" again?

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

Title:
  avahi-browse -av is empty, mdns not working in arduino ide

Status in avahi package in Ubuntu:
  Incomplete

Bug description:
  When I started the arduino IDE my port list is empty. This list relies
  on multicast DNS which is served by avahi.

  When running the avahi-browse -av command on ubuntu 18.04 I get a list
  of al mdns devices. On ubuntu 20.04 the're no mdns devices reported.

  The avahi-daemon is running. And when executing netstat -nlp | grep
  5353 I see avahi-daemon is listening. When also running tcpdump port
  5353 I see mdns packages arriving. But still avahi-browse -av is
  empty.

  iptables -A shows no rules and policies are accept
  ufw is disabled

  I also removed apparmor but also that didn't make any difference.

  On both ubuntu 18.04 and 20.04 the avahi version is 0.7.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-04-08 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  Package: avahi-daemon 0.7-4ubuntu7
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870410] Re: wireless does not work on boot on RPi 3s

** Changed in: systemd (Ubuntu Focal)
   Importance: Undecided => High

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

Title:
  wireless does not work on boot on RPi 3s

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  I've setup a wireless config in /etc/netplan/config.yaml and it does
  not activate on boot. I have to run 'sudo netplan apply' to get my
  wireless connected. This works fine on an RPi4 but not an RPi3B.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: User Name 5.4.0-1006.6-raspi2 5.4.24
  Uname: Linux 5.4.0-1006-raspi2 armv7l
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: armhf
  Date: Thu Apr  2 19:02:27 2020
  Lspci:
   
  Lsusb:
   Bus 001 Device 007: ID 0424:ec00 Microchip Technology, Inc. (formerly SMSC) 
SMSC9512/9514 Fast Ethernet Adapter
   Bus 001 Device 006: ID 0424:9514 Microchip Technology, Inc. (formerly SMSC) 
SMC9514 Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=dwc_otg/1p, 480M
   |__ Port 1: Dev 6, If 0, Class=Hub, Driver=hub/5p, 480M
   |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, 
Driver=smsc95xx, 480M
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:FF:6B:0F 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870930] Re: systemctl crashed with SIGSEGV

2020-04-22 Thread dinamic

same here, i use unity, systemctl crashes every time

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

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1870930] Re: systemctl crashed with SIGSEGV

** Merge proposal linked:
   
https://code.launchpad.net/~rbalint/ubuntu/+source/systemd/+git/systemd/+merge/382732

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

Title:
  systemctl crashed with SIGSEGV

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  Logged in to an updated focal, entered a few unrelated commands in
  gnome-terminal, and then the crash message showed up.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: systemd 245.2-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Apr  5 16:26:11 2020
  Disassembly: => 0x0:  Cannot access memory at address 0x0
  ExecutablePath: /usr/bin/systemctl
  InstallationDate: Installed on 2019-11-10 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Notebook P64_HJ,HK1
  ProcCmdline: systemctl --user start --wait unity-session.target
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic 
root=UUID=a8fd6652-86e7-4e1a-8259-809e0a4abd2b ro quiet splash
  SegvAnalysis:
   Segfault happened at: 0x0:   Cannot access memory at address 0x0
   PC (0x) not located in a known VMA region (needed executable region)!
  SegvReason: executing NULL VMA
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-timesyncd.service → 
/usr/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: systemctl crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 07/06/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.08
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P64_HJ,HK1
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.08:bd07/06/2017:svnNotebook:pnP64_HJ,HK1:pvrNotApplicable:rvnNotebook:rnP64_HJ,HK1:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P64_HJ,HK1
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  separator:

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.

2020-04-22 Thread dinamic

same here but on a PC

kernel: [58217.847336] systemctl[2787]: segfault at 0 ip
 sp 7ffc4b4f9df8 error 14 in
systemctl[55a481039000+1]

crash log

** Attachment added: "_bin_systemctl.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1873607/+attachment/5357849/+files/_bin_systemctl.1000.crash

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

Title:
  systemd segv coredump, reboot/poweroff ignored.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Proximate syslog:

  Apr 18 16:26:56 gate2 rssmonitor.py[2001]: settings: Running:  ip -all netns 
del
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/dbus.socket:4: 
ListenStream= references a path below legacy directory /var/run/, updating 
/var/run/dbus/system_bus_socket → /r
  un/dbus/system_bus_socket; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/sssd.service:11: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/sssd.pid → /run/sssd.pid; plea
  se update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/oddjobd.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/oddjobd.pid → /run/oddjobd.p
  id; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/fail2ban.service:12: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/fail2ban/fail2ban.pid → /r
  un/fail2ban/fail2ban.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: /lib/systemd/system/certmonger.service:6: 
PIDFile= references a path below legacy directory /var/run/, updating 
/var/run/certmonger.pid → /run/cer
  tmonger.pid; please update the unit file accordingly.
  Apr 18 16:26:56 gate2 systemd[1]: Reloading.
  Apr 18 16:26:56 gate2 kernel: [  454.966336] systemd[1]: segfault at 50 ip 
55946ed0d6f0 sp 7fff8409d210 error 4 in systemd[55946ecb4000+ae000]
  Apr 18 16:26:56 gate2 kernel: [  454.966354] Code: a8 48 8b 75 a0 c7 45 ac 00 
00 00 00 48 8b 94 c7 a0 04 00 00 48 89 45 88 48 89 f0 48 39 d6 74 17 66 2e 0f 
1f 84 00 00 00 00 00 <48
  > 8b 40 50 83 45 ac 01 48 39 c2 75 f3 48 8b 45 a0 31 db 4c 8d 7d
  Apr 18 16:26:56 gate2 rssmonitor.py[1213]: rssmain: Ran OK:   systemctl 
daemon-reload
  Apr 18 16:26:57 gate2 rssmonitor.py[1213]: rssmain: Running:  systemctl 
enable rssmonitor.service
  Apr 18 16:27:23 gate2 sssd[nss]: Enumeration requested but not enabled
  Apr 18 16:27:24 gate2 kernel: [  482.503042] printk: systemd: 43 output lines 
suppressed due to ratelimiting
  Apr 18 16:27:24 gate2 systemd[1]: Caught , dumped core as pid 2034.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.7
  ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
  Uname: Linux 5.3.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Sat Apr 18 18:09:06 2020
  InstallationDate: Installed on 2019-11-01 (169 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-46-generic 
root=UUID=82254a10-a9e1-4459-aba0-7876df48d9da ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.12.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-cosmic
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-cosmic:cvnQEMU:ct1:cvrpc-i440fx-cosmic:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-cosmic
  dmi.sys.vendor: QEMU
  mtime.conffile..etc.systemd.resolved.conf: 2020-04-18T10:41:34.662328

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection

2020-04-22 Thread You-Sheng Yang

** No longer affects: initramfs-tools (Ubuntu)

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

Title:
  [RTL810xE] No ethernet connection

Status in linux package in Ubuntu:
  Fix Released

Bug description:
  ubuntu doesn't show cable plugged-in. Wifi is also intermittent.
  Errors in log with realtek. long boot up. No problems with live-USB or
  fresh install, only after update.

  sudo lspci -vnvn > lspci-vnvn.log
  pcilib: sysfs_read_vpd: read failed: Input/output error

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-headers-5.4.0-22-generic 5.4.0-22.26
  ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29
  Uname: Linux 5.4.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  finisdiem   1332 F pulseaudio
   /dev/snd/controlC0:  finisdiem   1332 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  6 10:49:03 2020
  InstallationDate: Installed on 2020-04-01 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic 
root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-22-generic N/A
   linux-backports-modules-5.4.0-22-generic  N/A
   linux-firmware1.187
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2012
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.15
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1849
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 57.2F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: C2N51UA#ABA
  dmi.product.version: 088B1130591620100
  dmi.sys.vendor: Hewlett-Packard

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1873607] Re: systemd segv coredump, reboot/poweroff ignored.