date:20200331

Cool.

Also keep in mind there are multiple different standards for 4-ring
plugs. And no guarantee your headset and computer use the same standard
:/

https://www.cablechick.com.au/blog/understanding-trrs-and-audio-jacks/

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Bionic:
  Triaged
Status in pulseaudio source package in Focal:
  Triaged

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1861230] Re: _sasl_plugin_load failed

[Expired for cyrus-sasl2 (Ubuntu) because there has been no activity for
60 days.]

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  _sasl_plugin_load failed

Status in cyrus-sasl2 package in Ubuntu:
  Expired

Bug description:
  We are seeing the following in the journal after upgrading to these
  sets of packages:

  libsasl2-2/bionic-updates,bionic-security 2.1.27~101-g0780600+dfsg-3ubuntu2.1 
amd64
  libsasl2-modules/bionic-updates,bionic-security 
2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64
  libsasl2-modules-db/bionic-updates,bionic-security 
2.1.27~101-g0780600+dfsg-3ubuntu2.1 amd64 
  libsasl2-modules-gssapi-mit/bionic-updates,bionic-security 
2.1.27~101-g0780600+dfsg-3ubuntu2.1 

  Here are the errors:

  Jan 28 15:58:43 my-hostname sssd[20949]: Starting up
  Jan 28 15:58:43 my-hostname sssd[be[20950]: Starting up
  Jan 28 15:58:43 my-hostname sssd_be[20950]: ldapdb
  Jan 28 15:58:43 my-hostname sssd_be[20950]: _sasl_plugin_load failed on 
sasl_canonuser_init
  Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found
  Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found
  Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found
  Jan 28 15:58:43 my-hostname sssd[be[20950]: No worthy mechs found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1861230/+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 1860985] Re: packagekitd using 100% CPU

[Expired for packagekit (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  packagekitd using 100% CPU

Status in packagekit package in Ubuntu:
  Expired

Bug description:
  That's all I can report at this stage. Any attempt to kill it or
  disable the service fails and up goes its CPU usage, fans blowing the
  works!

  packagekit status give 
  Jan 27 13:59:02 owen-Precision-M4600 https[820460]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 http[820454]: Libgcrypt warning: missing 
initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 store[820894]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 https[820443]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 https[820455]: Libgcrypt warning: 
missing initialization - please fix the application
  Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying 
to obtain org.freedesktop.packagekit.system-sources-refresh auth 
(only_trusted:0)
  Jan 27 13:59:02 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained 
auth for org.freedesktop.packagekit.system-sources-refresh
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: refresh-cache 
transaction /29159_bdcaeddd from uid 1000 finished with cancelled-priority 
after 2137ms
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 is trying 
to obtain org.freedesktop.packagekit.system-sources-refresh auth 
(only_trusted:0)
  Jan 27 13:59:03 owen-Precision-M4600 PackageKit[437888]: uid 1000 obtained 
auth for org.freedesktop.packagekit.system-sources-refresh

  I am uid: 1000. It would be helpful if it gave some indication as to
  "the application". I can't find anywhere to admin this. It looks like
  my trust level is too low "only_trusted:0"

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: packagekit 1.1.13-2
  Uname: Linux 5.5.0-050500rc7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Jan 27 13:54:13 2020
  InstallationDate: Installed on 2017-12-06 (782 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to focal on 2019-11-13 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1860985/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-03-31 Thread hugh chao

I think 3 stripes = 4 rings, and we are talking the same thing, I will
make it more clear

** Description changed:

  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.
  
  [Test Case]
- 1. Insert 3-ring headset into front audio port (headset icon)
+ 1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output
  
  [Expected result]
  Can detect external headset
  
  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.
  
  [Regression Potential]
  Low.
  
  [Failure rate]
  100%
  
  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2
  
  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Bionic:
  Triaged
Status in pulseaudio source package in Focal:
  Triaged

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 4 rings(3 stripes) headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing

You can download older and newer kernels from https://kernel.ubuntu.com
/~kernel-ppa/mainline/?C=M;O=D

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

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

Status in bluez package in Ubuntu:
  New

Bug description:
  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2

  Summary
  ===

  BT earphones/speaker cannot be connected either using GNOME control
  center, either using bluetoothctl. I've tried with previous versions
  of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same
  issue, so I believe this is a problem with bluez.

  However, the same procedure works fine on Ubuntu 19.10 (kernel
  5.3.0-18, bluez 5.50), so I think it's a regression in bluez.

  Steps to reproduce
  ==

  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
    -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
    -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)

  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.

  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:

  $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
    0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed

  Additional information
  ==

  $ lspci -vv -s 01:00.0
  01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
   Subsystem: Intel Corporation Dual Band Wireless-AC 7265
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
St

[Touch-packages] [Bug 1869996] [NEW] Hibernation can NOT work due to incorrect RESUME=

2020-03-31 Thread Dexuan Cui

Public bug reported:

In Ubuntu 18.04 I have the below 4 lines, but in Ubuntu 20.04 (dev
build) these lines are missing:

--- /usr/share/initramfs-tools/init2020-04-01 01:15:20.533208700 +
+++ /usr/share/initramfs-tools/init 2020-04-01 00:59:43.931655200 +
@@ -163,6 +163,10 @@
;;
resume=*)
RESUME="${x#resume=}"
+   case $RESUME in
+   UUID=*)
+RESUME="/dev/disk/by-uuid/${RESUME#UUID=}"
+   esac
;;
resume_offset=*)
resume_offset="${x#resume_offset=}"

As a result, hibernation can not work: the saved state in the swap
partition is lost and no resume happens.

The issue is: when I use the "resume=UUID=533b2cd9-31ac-449b-82ff-
014f09ab0a9c" kernel parameter for hibernation, due to the missing
lines, the variable 'resume' in a later place in "/usr/share/initramfs-
tools/init" is set to "UUID=533b2cd9-31ac-449b-82ff-014f09ab0a9c" rather
than "/dev/disk/by-uuid/533b2cd9-31ac-449b-82ff-014f09ab0a9c". Next, in
/usr/share/initramfs-tools/scripts/local-premount/resume:

DEV=$(readlink "$resume")
DEV=/sys/class/block/${DEV##*/}/dev
if [ -r "$DEV" ]; then
read -r MAJMIN < "$DEV"
fi
if [ -z "$MAJMIN" ]; then
exit 1
fi

Here the 'readlink' will fail, so $DEV is not pointing to a valid device, and 
then $MAJMIN is empty and
we "exit 1", so no resume can happen!


Not sure why the 4 lines are removed in Ubuntu 20.04...


PS, this is my version info:

root@localhost:~# dpkg-query -s initramfs-tools-core
Package: initramfs-tools-core
Status: install ok installed
Priority: optional
Section: utils
Installed-Size: 271
Maintainer: Ubuntu Developers 
Architecture: all
Multi-Arch: foreign
Source: initramfs-tools
Version: 0.136ubuntu1
Replaces: initramfs-tools (<< 0.121~)
Depends: busybox-initramfs (>= 1:1.30.1-4ubuntu5~), initramfs-tools-bin (= 
0.136ubuntu1), klibc-utils (>= 2.0.4-8~), cpio (>= 2.12), lz4, kmod, udev, 
coreutils (>= 8.24), logsave | e2fsprogs (<< 1.45.3-1~)
Suggests: bash-completion
Breaks: busybox-initramfs (<< 1:1.30.1-4ubuntu5~), initramfs-tools (<< 0.121~)
Conffiles:
 /etc/initramfs-tools/initramfs.conf 4ec999d424d01b9ca685e65ba0f22a13
Description: generic modular initramfs generator (core tools)
 This package contains the mkinitramfs program that can be used to
 create a bootable initramfs for a Linux kernel.  The initramfs should
 be loaded along with the kernel and is then responsible for mounting
 the root filesystem and starting the main init system.
Original-Maintainer: Debian kernel team 

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Hibernation can NOT work due to incorrect RESUME=

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  In Ubuntu 18.04 I have the below 4 lines, but in Ubuntu 20.04 (dev
  build) these lines are missing:

  --- /usr/share/initramfs-tools/init2020-04-01 01:15:20.533208700 +
  +++ /usr/share/initramfs-tools/init 2020-04-01 00:59:43.931655200 +
  @@ -163,6 +163,10 @@
  ;;
  resume=*)
  RESUME="${x#resume=}"
  +   case $RESUME in
  +   UUID=*)
  +RESUME="/dev/disk/by-uuid/${RESUME#UUID=}"
  +   esac
  ;;
  resume_offset=*)
  resume_offset="${x#resume_offset=}"

  As a result, hibernation can not work: the saved state in the swap
  partition is lost and no resume happens.

  The issue is: when I use the "resume=UUID=533b2cd9-31ac-449b-82ff-
  014f09ab0a9c" kernel parameter for hibernation, due to the missing
  lines, the variable 'resume' in a later place in "/usr/share
  /initramfs-tools/init" is set to "UUID=533b2cd9-31ac-449b-82ff-
  014f09ab0a9c" rather than "/dev/disk/by-uuid/533b2cd9-31ac-449b-82ff-
  014f09ab0a9c". Next, in /usr/share/initramfs-tools/scripts/local-
  premount/resume:

  DEV=$(readlink "$resume")
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
  read -r MAJMIN < "$DEV"
  fi
  if [ -z "$MAJMIN" ]; then
  exit 1
  fi

  Here the 'readlink' will fail, so $DEV is not pointing to a valid device, and 
then $MAJMIN is empty and
  we "exit 1", so no resume can happen!

  
  Not sure why the 4 lines are removed in Ubuntu 20.04...

  
  PS, this is my version info:

  root@localhost:~# dpkg-query -s initramfs-tools-core
  Package: initramfs-tools-core
  Status: install ok installed
  Priority: optional
  Section: utils
  Installed-Size: 271
  Maintainer: Ubuntu Developers 
  Architecture: all
  Multi-Arch: foreign
  Source: initramfs-tools
  Version: 0.136ubuntu1
  Replaces: initramfs-tools (<< 0.121~)
  Depends: busybox-initramfs (>= 1:1.30.1-4ubuntu5~

[Touch-packages] [Bug 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

> 1. Insert 3-ring headset into front audio port (headset icon)

Is that right? Unless it's a strange-shaped 3-ring plug I think you will
find it needs to have 4 rings to be a working (stereo) 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/1869819

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Bionic:
  Triaged
Status in pulseaudio source package in Focal:
  Triaged

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 3-ring headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1869945] Re: design flaw: application menu.

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

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


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

** This bug has been marked a duplicate of bug 968213
   Too many icons in Gnome Shell Activities Overview require ellipses

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

Title:
  design flaw: application menu.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Bad design. The inscriptions do not fit into their places in the application 
menu. 
  Look at the attachment.

  Плохой дизайн. Надписи не вписываются в свои места в меню приложений.
  Смотрите вложение.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 31 12:06:39 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2020-03-30 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. VMware Virtual USB Mouse
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=1ed2509c-6bde-4abc-80f6-2cf45bec3d55 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
  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/gnome-shell/+bug/1869945/+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 1869155] Re: When installing with subiquity, the generated network config uses the macaddress keyword on s390x (where MAC addresses are not necessarily stable across reboots)

2020-03-31 Thread Michael Hudson-Doyle

Pretty sure it's initramfs-tools that is putting the mac addresses in
the netplan. That probably needs to grow a little platform-dependent
behaviour around this.

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  When installing with subiquity, the generated network config uses the
  macaddress keyword on s390x (where MAC addresses are not necessarily
  stable across reboots)

Status in cloud-init:
  Incomplete
Status in subiquity:
  New
Status in Ubuntu on IBM z Systems:
  New
Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  While performing a subiquity focal installation on an s390x LPAR (where the 
LPAR is connected to a VLAN trunk) I saw a section like this:
 match:
  macaddress: 02:28:0b:00:00:53
  So the macaddress keyword is used, but on several s390x machine generation 
MAC addresses are
  not necessarily stable and uniquie across reboots.
  (z14 GA2 and newer system have in between a modified firmware that ensures 
that MAC addresses are stable and uniquire across reboots, but for z14 GA 1 and 
older systems, incl. the z13 that I used this is not the case - and a backport 
of the firmware modification is very unlikely)

  The configuration that I found is this:

  $ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by the datasource. Changes
  # to it will not persist across an instance reboot. To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  ethernets:
  enc600:
  addresses:
  - 10.245.236.26/24
  gateway4: 10.245.236.1
  match:
  macaddress: 02:28:0b:00:00:53
  nameservers:
  addresses:
  - 10.245.236.1
  set-name: enc600
  version: 2

  (This is a spin-off of ticket LP 1868246.)

  It's understood that the initial idea for the MAC addresses was to have a 
unique identifier, but
  I think with the right tooling (ip, ifconfig, ethtool or even the 
network-manager UI) you can even change MAC addresses today on other platforms.

  Nowadays interface names are based on their underlying physical
  device/address (here in this case '600' or to be precise '0600' -
  leading '0' are removed), which makes the interface and it's name
  already quite unique - since it is not possible to have two devices
  (in one system) with the exact same address.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1869155/+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 1856376] Re: "Dummy Output" -- built-in audio not detected

@dogmatic69,

Please refer to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869799

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

Title:
  "Dummy Output" -- built-in audio not detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I no longer seem to be getting audio on my laptop, and only "Dummy
  Output" shows up in the sound settings dialog. This sounds similar to
  LP #1781294 (including the same PCI device), though that seems to have
  been marked expired.

  alex@tapada:~$ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Lenovo Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 64, IRQ 159
Memory at 2ffb028000 (64-bit, non-prefetchable) [size=16K]
Memory at 2ffb00 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  alex@tapada:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 13 23:38:35 2019
  InstallationDate: Installed on 2019-08-31 (104 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T22:15:32.867642

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856376/+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 1869814] Re: ubuntu-docs build failure - possible solution

Thanks Shaun! It's indeed that bug. Why am I not surprised when seeing
that you filed it? :)

I grabbed a Fedora patch and submitted a Debian merge request:

https://salsa.debian.org/xml-sgml-team/libxml2/-/merge_requests/3

It looks pretty spot on, don't you think? At least, with that patch
applied I can build ubuntu-docs 19.10.2 successfully again. A syntax
error in one of the Chinese translations is reported as warnings as
expected.

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

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

** Changed in: libxml2 (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  Invalid
Status in libxml2 package in Ubuntu:
  In Progress
Status in ubuntu-docs package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869981] [NEW] Printer notification every day at midnight

2020-03-31 Thread Alan Pope 🍺🐧🐱 🦄

Public bug reported:

Every day, all my 20.04 machines get a notification that the printer in
my house has been detected.

The printer works fine and is already added. So not sure why I need to
be told repeatedly that I have a printer on the network?

(see screenshot)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups 2.3.1-9ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CupsErrorLog:
 
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr  1 00:00:31 2020
InstallationDate: Installed on 2020-03-01 (30 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
MachineType: LENOVO 20BV001BUK
Papersize: a4
PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/14/2019
dmi.bios.vendor: LENOVO
dmi.bios.version: JBET73WW (1.37 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20BV001BUK
dmi.board.vendor: LENOVO
dmi.board.version: 0B98417 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T450
dmi.product.name: 20BV001BUK
dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
dmi.product.version: ThinkPad T450
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug focal

** Attachment added: "Screenshot from 2020-04-01 00-01-14.png"
   
https://bugs.launchpad.net/bugs/1869981/+attachment/5343944/+files/Screenshot%20from%202020-04-01%2000-01-14.png

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

Title:
  Printer notification every day at midnight

Status in cups package in Ubuntu:
  New

Bug description:
  Every day, all my 20.04 machines get a notification that the printer
  in my house has been detected.

  The printer works fine and is already added. So not sure why I need to
  be told repeatedly that I have a printer on the network?

  (see screenshot)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  1 00:00:31 2020
  InstallationDate: Installed on 2020-03-01 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  Lpstat: device for HP_LaserJet_100_colorMFP_M175nw_6DCDD4_: 
implicitclass://HP_LaserJet_100_colorMFP_M175nw_6DCDD4_/
  MachineType: LENOVO 20BV001BUK
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/HP_LaserJet_100_colorMFP_M175nw_6DCDD4_.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_pyyy5h@/vmlinuz-5.4.0-21-generic 
root=ZFS=rpool/ROOT/ubuntu_pyyy5h ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET73WW (1.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BV001BUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98417 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET73WW(1.37):bd08/14/2019:svnLENOVO:pn20BV001BUK:pvrThinkPadT450:rvnLENOVO:rn20BV001BUK:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450
  dmi.product.name: 20BV001BUK
  dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450
  dmi.product.version: ThinkPad T450
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1869979] [NEW] liborc-0.4.so doesn't exist after install

2020-03-31 Thread Raj Bhattacharjea

Public bug reported:

If you apt install liborc-0.4-0, there is no liborc-0.4.so file in
/usr/lib/x86_64-linux-gnu/

There IS a liborc-0.4.so.0 file that is a link to iborc-0.4.so.0.28.0, but 
there is no link with name liborc-0.4.so pointing to that same file. I don't 
know if this is a bug or expected behavior, but it does trigger issues with 
other packages, such as out-of-tree modules for GNURadio:
https://github.com/bastibl/gr-foo/issues/24#issuecomment-606925453

Those can be fixed with a simple symlink. If this is a problem with the
build system of the other project (i.e., it should have picked up the
so.0 file), my apologies and please close the issue. Thanks.

System details:
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Version:
liborc-0.4-0
  Installed: 1:0.4.28-1
Summary:
I expect there to be a .so file by the name of the library somewhere on the 
system after installing. There is not one, but instead, the name I expect with 
a .so.0 extension exists, but there is no symlink with the expected name.

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

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

Title:
  liborc-0.4.so doesn't exist after install

Status in orc package in Ubuntu:
  New

Bug description:
  If you apt install liborc-0.4-0, there is no liborc-0.4.so file in
  /usr/lib/x86_64-linux-gnu/

  There IS a liborc-0.4.so.0 file that is a link to iborc-0.4.so.0.28.0, but 
there is no link with name liborc-0.4.so pointing to that same file. I don't 
know if this is a bug or expected behavior, but it does trigger issues with 
other packages, such as out-of-tree modules for GNURadio:
  https://github.com/bastibl/gr-foo/issues/24#issuecomment-606925453

  Those can be fixed with a simple symlink. If this is a problem with
  the build system of the other project (i.e., it should have picked up
  the so.0 file), my apologies and please close the issue. Thanks.

  System details:
  Description: Ubuntu 18.04.4 LTS
  Release: 18.04
  Version:
  liborc-0.4-0
Installed: 1:0.4.28-1
  Summary:
  I expect there to be a .so file by the name of the library somewhere on the 
system after installing. There is not one, but instead, the name I expect with 
a .so.0 extension exists, but there is no symlink with the expected name.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/orc/+bug/1869979/+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 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing

2020-03-31 Thread Pierre Equoy

Please find attached my dmesg. I don't see anything related to
bluetoothd.

The same issue happens with two other BT devices (2 earphones from the
same brand, TaoTronics), so I'm pretty confident it's not a BT device
issue. Plus, as I mention, it works well with the same hardware (laptop
and BT devices) on 19.10 (kernel 5.3 + bluez 5.50).

How can I install kernel 5.3 on focal?

** Attachment added: "dmesg.log"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1869857/+attachment/5343943/+files/dmesg.log

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

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

Status in bluez package in Ubuntu:
  New

Bug description:
  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2

  Summary
  ===

  BT earphones/speaker cannot be connected either using GNOME control
  center, either using bluetoothctl. I've tried with previous versions
  of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same
  issue, so I believe this is a problem with bluez.

  However, the same procedure works fine on Ubuntu 19.10 (kernel
  5.3.0-18, bluez 5.50), so I think it's a regression in bluez.

  Steps to reproduce
  ==

  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
    -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
    -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)

  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.

  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:

  $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
    0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Fail

[Touch-packages] [Bug 1866435] Re: Please remove gypsy from Ubuntu

2020-03-31 Thread Steve Langasek

Removing packages from focal:
gypsy 0.8-0ubuntu8 in focal
gypsy-daemon 0.8-0ubuntu8 in focal amd64
gypsy-daemon 0.8-0ubuntu8 in focal arm64
gypsy-daemon 0.8-0ubuntu8 in focal armhf
gypsy-daemon 0.8-0ubuntu8 in focal ppc64el
gypsy-daemon 0.8-0ubuntu8 in focal s390x
libgypsy-dev 0.8-0ubuntu8 in focal amd64
libgypsy-dev 0.8-0ubuntu8 in focal arm64
libgypsy-dev 0.8-0ubuntu8 in focal armhf
libgypsy-dev 0.8-0ubuntu8 in focal ppc64el
libgypsy-dev 0.8-0ubuntu8 in focal s390x
libgypsy-doc 0.8-0ubuntu8 in focal amd64
libgypsy-doc 0.8-0ubuntu8 in focal arm64
libgypsy-doc 0.8-0ubuntu8 in focal armhf
libgypsy-doc 0.8-0ubuntu8 in focal ppc64el
libgypsy-doc 0.8-0ubuntu8 in focal s390x
libgypsy0 0.8-0ubuntu8 in focal amd64
libgypsy0 0.8-0ubuntu8 in focal arm64
libgypsy0 0.8-0ubuntu8 in focal armhf
libgypsy0 0.8-0ubuntu8 in focal ppc64el
libgypsy0 0.8-0ubuntu8 in focal s390x
Comment: Ubuntu-specific, FTBFS, no reverse-dependencies; LP: #1866435
1 package successfully removed.


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

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

Title:
  Please remove gypsy from Ubuntu

Status in gypsy package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu-only, no reverse dependencies. FTBFS on rebuild. No new
  upstream releases since 2012.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gypsy/+bug/1866435/+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 1222527] Re: Rename 'Software & Updates' label

2020-03-31 Thread Merlijn Sebrechts

Just wanted to add that the issue mpt talk about is now fixed: in the
Gnome search view, system settings are now displayed very different from
applications.

Thus, the ideal solution is to add Software & Updates to Gnome Control
Center.

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

Title:
  Rename 'Software & Updates' label

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 13.10
  Language: English US

  UX Problem:
  When searching in the Dash for the system software updater - a pretty common 
task - always two entries are presented to the user with nearly the same name. 
There is the update-manager labeled ' Software Updater' and there is 
software-properties labeled 'Software & Updates', result: 'Software Updater' 
and 'Software & Updates'.
  Both names start with a capital S and a capital U → they should be easier to 
distinguish.

  Suggested solution:
  Relabel the less common GenericName of the .desktop file to something else. 
As the software-properties are less important IMHO for the daily use of an 
average user, I purpose to relabel it to 'Software Settings'. Not my favorite 
name, but visual much better to distinguish then the current name and it would 
share the naming pattern of having 'Settings' at the end of a program that 
allows the user to configure something.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: software-properties-gtk 0.92.25
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sun Sep  8 20:50:21 2013
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2013-08-27 (11 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130827)
  InterpreterPath: /usr/bin/python3.3
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1222527/+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 1824088] Re: unattended upgrade ran one day after schedule

2020-03-31 Thread Carl Winbäck

How about this idea?

What if we add this line to the beginning of
usr/lib/apt/apt.systemd.daily:

export TZ="UTC0"

(I got this idea from the GNU Coreutils manual. See
https://www.gnu.org/software/coreutils/manual/html_node/Relative-items-
in-date-strings.html)

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

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+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 1869961] Re: systemd-networkd ignores RA preference and creates multipath routes anyway

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

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

Title:
  systemd-networkd ignores RA preference and creates multipath routes
  anyway

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  When IPv6 ND RAs are sent from two different routers, one with Medium
  and one with High preferences, systemd-networkd will ignore the fact
  they have different preferences and create two multipath routes with
  the same weight.

  I ran a tcpdump of the RAs and confirmed that both have different
  preferences sent.

  i.e.

  nms-mon1:~$ ip -6 route
  2a0d:1a40:7551:6010::/64 dev ens18 proto ra metric 100 pref medium
  fe80::/64 dev ens18 proto kernel metric 256 pref medium
  default proto ra metric 100 
nexthop via fe80::c030:9cff:fe10:3492 dev ens18 weight 1 
nexthop via fe80::215:5dff:fe83:c81c dev ens18 weight 1

  Ubuntu version: Ubuntu 18.04.4 LTS
  systemd version: 237-3ubuntu10.39

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869961/+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 1824088] Re: unattended upgrade ran one day after schedule

2020-03-31 Thread Carl Winbäck

If we look at lines 131 and 132 in /usr/lib/apt/apt.systemd.daily, we
will se the following:

interval="${interval%d}"
interval=$((interval*60*60*24))

I’m not 100% certain but I think that this time logic is what cause the
bug to occur, in accordance with what Magnus has pointed out in his
comments.

(It’s possible that lines 122-130 are also relevant.)

Any ideas on how to modify the code in order to avoid this bug?

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

Title:
  unattended upgrade ran one day after schedule

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I have noticed a strange behaviour in unattended upgrades. The host in
  question is scheduled to run upgrades on Mondays every second week.
  However, this week it ran upgrades on Tuesday instead (2019-04-09).

  This is the first time I’ve noticed this behaviour. I checked the logs
  in /var/log/apt/history.log* and I saw that worked as intended up
  until this week. Upgrades ran as expected on 2019-03-11 and
  2019-03-25, which where both Mondays.

  The schedule was set with the line 'APT::Periodic::Unattended-Upgrade
  "14";' in the file /etc/apt/apt.conf.d/20auto-upgrades.

  Could it be daylight savings time that has caused skewing of the
  schedule?

  The server is located in Sweden and on 2019-03-31 we switched from CET
  to CEST. If the time diff is calculated with hours instead of calendar
  days passed, perhaps the missing hour on 2019-03-31 caused the
  scheduler to believe that on Monday 2019-03-08, two weeks (336 hours)
  had not yet passed.

  
  ADDITIONAL INFO

  Description:Ubuntu 16.04.6 LTS
  Release:16.04

  apt:
Installed: 1.2.29ubuntu0.1
Candidate: 1.2.31
Version table:
   1.2.31 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
   *** 1.2.29ubuntu0.1 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.2.10ubuntu1 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  unattended-upgrades:
Installed: 0.90ubuntu0.10
Candidate: 0.90ubuntu0.10
Version table:
   *** 0.90ubuntu0.10 500
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main i386 
Packages
  100 /var/lib/dpkg/status
   0.90 500
  500 http://se.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://se.archive.ubuntu.com/ubuntu xenial/main i386 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.29ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Apr 10 09:06:49 2019
  InstallationDate: Installed on 2017-12-28 (467 days ago)
  InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1824088/+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 1869961] [NEW] systemd-networkd ignores RA preference and creates multipath routes anyway

2020-03-31 Thread Joseph Marsden

Public bug reported:

When IPv6 ND RAs are sent from two different routers, one with Medium
and one with High preferences, systemd-networkd will ignore the fact
they have different preferences and create two multipath routes with the
same weight.

I ran a tcpdump of the RAs and confirmed that both have different
preferences sent.

i.e.

nms-mon1:~$ ip -6 route
2a0d:1a40:7551:6010::/64 dev ens18 proto ra metric 100 pref medium
fe80::/64 dev ens18 proto kernel metric 256 pref medium
default proto ra metric 100 
nexthop via fe80::c030:9cff:fe10:3492 dev ens18 weight 1 
nexthop via fe80::215:5dff:fe83:c81c dev ens18 weight 1

Ubuntu version: Ubuntu 18.04.4 LTS
systemd version: 237-3ubuntu10.39

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1869961

Title:
  systemd-networkd ignores RA preference and creates multipath routes
  anyway

Status in systemd package in Ubuntu:
  New

Bug description:
  When IPv6 ND RAs are sent from two different routers, one with Medium
  and one with High preferences, systemd-networkd will ignore the fact
  they have different preferences and create two multipath routes with
  the same weight.

  I ran a tcpdump of the RAs and confirmed that both have different
  preferences sent.

  i.e.

  nms-mon1:~$ ip -6 route
  2a0d:1a40:7551:6010::/64 dev ens18 proto ra metric 100 pref medium
  fe80::/64 dev ens18 proto kernel metric 256 pref medium
  default proto ra metric 100 
nexthop via fe80::c030:9cff:fe10:3492 dev ens18 weight 1 
nexthop via fe80::215:5dff:fe83:c81c dev ens18 weight 1

  Ubuntu version: Ubuntu 18.04.4 LTS
  systemd version: 237-3ubuntu10.39

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1869961/+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 1868210] Re: [SRU] Load ucm on Lenovo notebooks based on bios version

2020-03-31 Thread Brian Murray

Hello Anthony, or anyone else affected,

Accepted alsa-lib into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.1.9-0ubuntu1.3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
eoan to verification-done-eoan. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-eoan. In either case, without details of your testing we will not
be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: alsa-lib (Ubuntu Eoan)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-eoan

** Changed in: alsa-lib (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supports ucm2, and with ucm2 all machines could share
  one ucm, so latest alsa-lib does not have this problem. This problem
  is only specific to the alsa-lib in Bionic and Eoan.

  [Impact]
  On some Lenovo notebooks, UCM files are not loaded and mic can't be used.

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.

  Lenovo X1C7 should load the N2H/*.conf and verify the audio
  functionalities. The Dell machine should still load the ucm by
  cardname, and it should work as good as before.

  [Regression Potential]
  low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1868210/+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 1868210] Please test proposed package

2020-03-31 Thread Brian Murray

Hello Anthony, or anyone else affected,

Accepted alsa-lib into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.1.3-5ubuntu0.5 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [SRU] Load ucm on Lenovo notebooks based on bios version

Status in HWE Next:
  New
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed
Status in alsa-lib source package in Focal:
  Invalid

Bug description:
  This SRU is not backported from upstream of alsa-lib and this SRU is
  not going to be submitted to upstream. That is because the latest
  alsa-lib already supports ucm2, and with ucm2 all machines could share
  one ucm, so latest alsa-lib does not have this problem. This problem
  is only specific to the alsa-lib in Bionic and Eoan.

  [Impact]
  On some Lenovo notebooks, UCM files are not loaded and mic can't be used.

  [Fix]
  UCM was loaded based on cardlongname, but that can't cover all configs of the 
same model. Lenovo suggested to load  ucm by the first 3 letters of 
/sys/devices/virtual/dmi/id/bios_version, so that all configs could use just 
one ucm.

  [Test Case]
  After applying this patch, install the testing alsa-lib on Lenovo X1C7 and 
Dell vostro 5390, which are all machines with the DMIC connected to PCH. After 
system bootup, check the /usr/share/alsa/ucm/ for the presence of 
LENOVO-BIOSID-xxx directories.

  Lenovo X1C7 should load the N2H/*.conf and verify the audio
  functionalities. The Dell machine should still load the ucm by
  cardname, and it should work as good as before.

  [Regression Potential]
  low, just add some new UCMs and let Lenovo machine find the UCM by 
bios_version if it fails by cardlongname. I've already tested the change on 
Lenovo and Dell machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1868210/+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 1856376] Re: "Dummy Output" -- built-in audio not detected

2020-03-31 Thread dogmatic69

Sound has been working for me on 19.10 but stopped working a few weeks
back after an update.

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

Title:
  "Dummy Output" -- built-in audio not detected

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I no longer seem to be getting audio on my laptop, and only "Dummy
  Output" shows up in the sound settings dialog. This sounds similar to
  LP #1781294 (including the same PCI device), though that seems to have
  been marked expired.

  alex@tapada:~$ lspci -v | grep -A7 -i "audio"
  00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 
(prog-if 80)
Subsystem: Lenovo Sunrise Point-LP HD Audio
Flags: bus master, fast devsel, latency 64, IRQ 159
Memory at 2ffb028000 (64-bit, non-prefetchable) [size=16K]
Memory at 2ffb00 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  alex@tapada:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  Codename: bionic

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec 13 23:38:35 2019
  InstallationDate: Installed on 2019-08-31 (104 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET68W (1.43 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET68W(1.43):bd10/16/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-12-13T22:15:32.867642

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856376/+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 1868085] Re: Bug related to the new kernel version 5.3.0-42-generic

2020-03-31 Thread Paolo Mainardi

I confirm the ACPI problems using the sof drivers starting from
5.3.0-40, is there something i can use to debug back from sleep issue ?

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

Title:
  Bug related to the new kernel version 5.3.0-42-generic

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  Hi all,

  After an update of Ubuntu kernel (version 5.3.0-42-generic) I can't
  have sound any more. No soundcards are detected any I have a "dummy
  output" in the sound pannel in settings. Furthermore I can't resume
  from sleep anymore.

  Output of ALSA Information script:

   
  !!
  !!ALSA Information Script v 0.4.64
  !!

  !!Script ran on: Wed Mar 18 14:46:19 UTC 2020

  
  !!Linux Distribution
  !!--

  Ubuntu 18.04.4 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu
  18.04.4 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.4 LTS" HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies
  /privacy-policy" UBUNTU_CODENAME=bionic

  
  !!DMI Information
  !!---

  Manufacturer:  HP
  Product Name:  HP ZBook 15u G6
  Product Version:   
  Firmware Version:  R70 Ver. 01.03.04
  Board Vendor:  HP
  Board Name:8549

  
  !!ACPI Device Status Information
  !!---

  /sys/bus/acpi/devices/ACPI000C:00/status   15
  /sys/bus/acpi/devices/HPIC000C:00/status   15
  /sys/bus/acpi/devices/HPQ6001:00/status15
  /sys/bus/acpi/devices/IFX0785:00/status15
  /sys/bus/acpi/devices/INT3400:00/status15
  /sys/bus/acpi/devices/INT3403:00/status15
  /sys/bus/acpi/devices/INT3403:01/status15
  /sys/bus/acpi/devices/INT340E:00/status15
  /sys/bus/acpi/devices/INT34BB:00/status15
  /sys/bus/acpi/devices/INT3F0D:00/status15
  /sys/bus/acpi/devices/LNXPOWER:00/status   15
  /sys/bus/acpi/devices/LNXPOWER:02/status   1
  /sys/bus/acpi/devices/LNXPOWER:03/status   1
  /sys/bus/acpi/devices/LNXPOWER:05/status   1
  /sys/bus/acpi/devices/LNXPOWER:06/status   1
  /sys/bus/acpi/devices/LNXPOWER:07/status   1
  /sys/bus/acpi/devices/LNXPOWER:08/status   1
  /sys/bus/acpi/devices/PNP0103:00/status15
  /sys/bus/acpi/devices/PNP0B00:00/status15
  /sys/bus/acpi/devices/PNP0C02:00/status3
  /sys/bus/acpi/devices/PNP0C02:01/status3
  /sys/bus/acpi/devices/PNP0C02:05/status3
  /sys/bus/acpi/devices/PNP0C09:00/status15
  /sys/bus/acpi/devices/PNP0C0A:00/status31
  /sys/bus/acpi/devices/PNP0C0C:00/status11
  /sys/bus/acpi/devices/PRP1:00/status   11
  /sys/bus/acpi/devices/SYNA3092:00/status   15
  /sys/bus/acpi/devices/USBC000:00/status15
  /sys/bus/acpi/devices/device:04/status 15
  /sys/bus/acpi/devices/device:27/status 15
  /sys/bus/acpi/devices/device:28/status 15
  /sys/bus/acpi/devices/device:4c/status 15

  
  !!Kernel Information
  !!--

  Kernel release:5.3.0-42-generic
  Operating System:  GNU/Linux
  Architecture:  x86_64
  Processor: x86_64
  SMP Enabled:   Yes

  
  !!ALSA Version
  !!

  Driver version: k5.3.0-42-generic
  Library version:1.1.3
  Utilities version:  1.1.3

  
  !!Loaded ALSA modules
  !!---


  !!Sound Servers on this system
  !!

  Pulseaudio:
Installed - Yes (/usr/bin/pulseaudio)
Running - Yes

  
  !!Soundcards recognised by ALSA
  !!-

  --- no soundcards ---

  
  !!PCI Soundcards installed in the system
  !!--

  00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device 
[8086:9dc8] (rev 11)
Subsystem: Hewlett-Packard Company Device [103c:8549]

  
  !!Modprobe options (Sound related)
  !!

  snd_pcsp: index=-2
  snd_usb_audio: index=-2
  snd_atiixp_modem: index=-2
  snd_intel8x0m: index=-2
  snd_via82xx_modem: index=-2
  snd_atiixp_modem: index=-2
  snd_intel8x0m: index=-2
  snd_via82xx_modem: index=-2
  snd_usb_audio: index=-2
  snd_usb_caiaq: index=-2
  snd_usb_ua101: index=-2
  snd_usb_us122l: index=-2
  snd_usb_usx2y: index=-2
  snd_cmipci: mpu_port=0x330 fm_port=0x388
  snd_pcsp: index=-2
  snd_usb_audio: index=-2

  
  !!Loaded sound module options
  !!---

  
  !!ALSA Device nodes
  !!-

  crw-rw  1 root audio 116,  1 Mar 18 14:45 /dev/snd/seq
  crw-rw  1 root audio 116, 33 Mar 18 14:44 /dev/snd/timer

  
  !!Aplay/Arecord output
  !!

  APLAY

[Touch-packages] [Bug 1727908] Re: Software & Updates application does not permit changes on the "Other Software" tab

I see this issue in focal. Nothing happens if I try to enable or disable
a source in the "Other Software" tab by clicking a checkbox. I get the
same error message as mentioned in comment #2 if I start software-
properties-gtk in terminal.

Adding or removing sources works, but not enabling/disabling them.

** Tags added: focal

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

Title:
  Software & Updates application does not permit changes on the "Other
  Software" tab

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Bionic:
  Confirmed
Status in software-properties source package in Bionic:
  Confirmed

Bug description:
  
  On the "Other Software" tab, I am unable to select "Canonical Partners".
  Similarly, the other checkboxes on the "Other Software" can not be clicked.
  Clicking on a checkbox has no effect, and a dialog requesting the admin 
password is not presented.

  However, activating or deactivating checkboxes on other tabs causes an
  authorization dialog to be presented to the user.

  I experience this bug in an an Xorg session.

  sources.list and sources.list.d have the following permissions:
  -rw-r--r--   1 root root  2897 Oct 26 22:35 sources.list
  drwxr-xr-x   2 root root  4096 Oct 26 21:29 sources.list.d

  All files in sources.list.d have the following permissions as this example:
  -rw-r--r-- 1 root root  189 Oct 25 21:50 google-chrome.list

  $ lsb_release -rd
  Description:  Ubuntu 17.10
  Release:  17.10

  $ apt-cache policy software-properties-gtk
  software-properties-gtk:
Installed: 0.96.24.17
Candidate: 0.96.24.17
Version table:
   *** 0.96.24.17 500
  500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu artful/main i386 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: software-properties-gtk 0.96.24.17
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: wl nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Oct 26 22:45:09 2017
  InstallationDate: Installed on 2017-10-26 (1 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.10.25 amd64 "Custom Artful Aardvark"
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1727908/+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 1869945] [NEW] design flaw: application menu.

2020-03-31 Thread Georg

Public bug reported:

Bad design. The inscriptions do not fit into their places in the application 
menu. 
Look at the attachment.

Плохой дизайн. Надписи не вписываются в свои места в меню приложений.
Смотрите вложение.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
Uname: Linux 5.3.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 31 12:06:39 2020
DistUpgraded: Fresh install
DistroCodename: eoan
DistroVariant: ubuntu
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2020-03-30 (1 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. VMware Virtual USB Mouse
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=1ed2509c-6bde-4abc-80f6-2cf45bec3d55 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/13/2018
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~19.10.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug eoan fonts ubuntu

** Attachment added: "Снимок экрана от 2020-03-31 12-00-57.png"
   
https://bugs.launchpad.net/bugs/1869945/+attachment/5343903/+files/%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA%20%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0%20%D0%BE%D1%82%202020-03-31%2012-00-57.png

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

Title:
  design flaw: application menu.

Status in xorg package in Ubuntu:
  New

Bug description:
  Bad design. The inscriptions do not fit into their places in the application 
menu. 
  Look at the attachment.

  Плохой дизайн. Надписи не вписываются в свои места в меню приложений.
  Смотрите вложение.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 31 12:06:39 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2020-03-30 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 004: ID 0e0f:0008 VMware, Inc. VMware Virtual USB Mouse
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-45-generic 
root=UUID=1ed2509c-6bde-4abc-80f6-2cf45bec3d55 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.vers

[Touch-packages] [Bug 1869814] Re: ubuntu-docs build failure - possible solution

2020-03-31 Thread Shaun McCance

So in general, syntax errors in translations just cause a warning, and
the original text is used. itstool only errors on syntax if you pass
--strict, and yelp.m4 doesn't even give you a way to pass --strict.

There's a chance this is itstool's fault. You do still have to do memory
management with libxml2's Python bindings, so stuff like double frees in
application code is possible. But since this crash happens during error
reporting for a language with many-byte UTF-8 chars, and since it
weirdly only happens with Python 3, I suspect it's this libxml2 bug:

https://bugzilla.gnome.org/show_bug.cgi?id=789714


** Bug watch added: bugzilla.gnome.org/ #789714
   https://bugzilla.gnome.org/show_bug.cgi?id=789714

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  Invalid
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869940] [NEW] No networks available/visible after suspend

2020-03-31 Thread Marcus Grenängen

Public bug reported:

WiFI network disconnected and no networks visible after resume from
suspend. Had to reboot the machine to get networking (WiFI) back up and
running.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.22.10-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
ApportVersion: 2.20.11-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 31 21:18:43 2020
InstallationDate: Installed on 2020-03-31 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330)
IpRoute:
 default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp59s0 scope link metric 1000 
 192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 600
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE  TIMESTAMP   TIMESTAMP-REAL 
   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE   STATE  ACTIVE-PATH 
SLAVE  FILENAME 
  
 DORIAN  2c3f821d-0865-4747-974a-2f861ee0dc38  wifi  1585682245  tis 31 mar 
2020 21:17:25  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp59s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/DORIAN.nmconnection
nmcli-dev:
 DEVICE   TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH   
 wlp59s0  wifi  connected full  limited   
/org/freedesktop/NetworkManager/Devices/2  DORIAN  
2c3f821d-0865-4747-974a-2f861ee0dc38  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 p2p-dev-wlp59s0  wifi-p2p  disconnected  none  none  
/org/freedesktop/NetworkManager/Devices/3  --  --   
 -- 
 lo   loopback  unmanaged unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
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/1869940

Title:
  No networks available/visible after suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  WiFI network disconnected and no networks visible after resume from
  suspend. Had to reboot the machine to get networking (WiFI) back up
  and running.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 31 21:18:43 2020
  InstallationDate: Installed on 2020-03-31 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330)
  IpRoute:
   default via 192.168.1.1 dev wlp59s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp59s0 scope link metric 1000 
   192.168.1.0/24 dev wlp59s0 proto kernel scope link src 192.168.1.30 metric 
600
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  TIMESTAMP   
TIMESTAMP-REALAUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE   STATE  
ACTIVE-PATH SLAVE  FILENAME 
  
   DORIAN  2c3f821d-0865-4747-974a-2f861ee0dc38  wifi  1585682245  tis 31 mar 
2020 21:17:25  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp59s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/etc/NetworkManager/system-connections/DORIAN.nmconnection
  nmcli-dev:
   DEVICE   TYPE  STATE IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH   
   wlp59s0  wifi  connected full  limited   
/org/freedesktop/Netw

[Touch-packages] [Bug 1862232] Re: Long hostname causes networking setup to fail

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

Title:
  Long hostname causes networking setup to fail

Status in systemd:
  Fix Released
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

Bug description:
  [impact]

  networkd fails to bring up networking on systems with long hostname

  [test case]

  setting the hostname:

  $ sudo hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf

  then reboot and check the networking.

  [regression potential]

  as this adjusts logging and certain error handling while performing
  dhcp, any regression would likely cause dhcp failure.

  [scope]

  this is fixed by upstream commit
  a8494759b4f14af5337391727ba295ab708b92f9 (along with some associated
  commits around it), which is included starting in v240, so this is
  included already in Eoan and later.

  This is needed in Bionic and Xenial.

  [other info]

  the problem around this is that Linux sets HOST_NAME_MAX to 64, but
  RFC 1035 limits DNS labels to 63 characters, so any host with a max-
  length single-label hostname (i.e. a 64 character hostname with no
  dots) will be "valid" from Linux's perspective, but will violate RFC
  1035 and thus systemd will consider it invalid and won't pass it to
  the dhcp server.

  Also note that a 64-character hostname that is *not* single-label
  (i.e. a hostname with at least 1 dot) will not cause this problem.

  The systemd patches continue to reject sending the invalid hostname to
  the dhcp server, but do not prevent networkd from finishing setting up
  networking.

  [original description]

  1) ubuntu version
  # lsb_release -rd
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

  2) package version
  # apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10.31
    Candidate: 237-3ubuntu10.31
    Version table:
   *** 237-3ubuntu10.31 500
  500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
Packag
  es
  100 /var/lib/dpkg/status
   237-3ubuntu10.29 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages

  3) I expect the network to come online correctly regardless of how
  long the hostname is. This is what happens with both 14.0 and 19.0 (I
  tested the same behavior with both of them).

  4) the external network interface fails to be configured and is stuck
  in a (pending) state as reported by networkctl status -a

  setting the hostname:

  # hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf

  after rebooting the machine, it no longer has network access.

  # journalctl
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: 
Starting Wait for Network to be Configured...
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: Link state is up-to-date
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: found matching network 
'/run/systemd/network/10-netplan-eth0.network'
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: sd-netlink: callback failed: Invalid argument
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: lo: Link state is up-to-date

  # networkctl status -a:
  ● 1: lo
     Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
     State: carrier (unmanaged)
   Address: 127.0.0.1
    ::1

  ● 2: eth0
     Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
     State: off (pending)
  Path: pci-:00:03.0
    Driver: virtio_net
    Vendor: Red Hat, Inc.
     Model: Virtio network device
    HW Address: ae:4d:91:1c:e8:86
   DNS: 67.207.67.3
    67.207.67.2

  and to bring up the network correctly, set the hostname to something
  shorter

  # hostnamectl set-hostname asdf
  # systemctl restart systemd-networkd
  # networkctl status -a
  ● 1: lo
     Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
     State: carrier (unmanaged)
   Address: 127.0.0.1
    ::1

  ● 2: eth0
     Link File: /run/systemd/network/10-netplan-eth0.link

[Touch-packages] [Bug 1862232] Re: Long hostname causes networking setup to fail

** Description changed:

  [impact]
  
  networkd fails to bring up networking on systems with long hostname
  
  [test case]
  
  setting the hostname:
  
  $ sudo hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf
  
  then reboot and check the networking.
  
  [regression potential]
  
  as this adjusts logging and certain error handling while performing
  dhcp, any regression would likely cause dhcp failure.
  
  [scope]
  
  this is fixed by upstream commit
  a8494759b4f14af5337391727ba295ab708b92f9 (along with some associated
  commits around it), which is included starting in v240, so this is
  included already in Eoan and later.
  
  This is needed in Bionic and Xenial.
+ 
+ [other info]
+ 
+ NOTE: the problem around this is that Linux sets HOST_NAME_MAX to 64,
+ but RFC 1035 limits DNS labels to 63 characters, so any host with a max-
+ length single-label hostname (i.e. a 64 character hostname with no dots)
+ will be "valid" from Linux's perspective, but will violate RFC 1035 and
+ thus systemd will consider it invalid and won't pass it to the dhcp
+ server.
+ 
+ Also note that a 64-character hostname that is *not* single-label (i.e.
+ a hostname with at least 1 dot) will not cause this problem.
+ 
+ The systemd patches continue to reject sending the invalid hostname to
+ the dhcp server, but do not prevent networkd from finishing setting up
+ networking.
  
  [original description]
  
  1) ubuntu version
  # lsb_release -rd
  Description:Ubuntu 18.04.3 LTS
  Release:18.04
  
  2) package version
  # apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10.31
    Candidate: 237-3ubuntu10.31
    Version table:
   *** 237-3ubuntu10.31 500
  500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
Packag
  es
  100 /var/lib/dpkg/status
   237-3ubuntu10.29 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages
  
  3) I expect the network to come online correctly regardless of how long
  the hostname is. This is what happens with both 14.0 and 19.0 (I tested
  the same behavior with both of them).
  
  4) the external network interface fails to be configured and is stuck in
  a (pending) state as reported by networkctl status -a
  
  setting the hostname:
  
  # hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf
  
  after rebooting the machine, it no longer has network access.
  
  # journalctl
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: 
Starting Wait for Network to be Configured...
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: Link state is up-to-date
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: found matching network 
'/run/systemd/network/10-netplan-eth0.network'
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: sd-netlink: callback failed: Invalid argument
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: lo: Link state is up-to-date
  
  # networkctl status -a:
  ● 1: lo
     Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
     State: carrier (unmanaged)
   Address: 127.0.0.1
    ::1
  
  ● 2: eth0
     Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
     State: off (pending)
  Path: pci-:00:03.0
    Driver: virtio_net
    Vendor: Red Hat, Inc.
     Model: Virtio network device
    HW Address: ae:4d:91:1c:e8:86
   DNS: 67.207.67.3
    67.207.67.2
  
  and to bring up the network correctly, set the hostname to something
  shorter
  
  # hostnamectl set-hostname asdf
  # systemctl restart systemd-networkd
  # networkctl status -a
  ● 1: lo
     Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
     State: carrier (unmanaged)
   Address: 127.0.0.1
    ::1
  
  ● 2: eth0
     Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
     State: routable (configured)
  Path: pci-:00:03.0
    Driver: virtio_net
    Vendor: Red Hat, Inc.
     Model: Virtio network device
    HW Address: ae:4d:91:1c:e8:86
   Address: 10.17.0.5
    157.245.210.250
    fe80::ac4d:91ff:fe1c:e886
   Gate

[Touch-packages] [Bug 1869661] Re: lxc 3.23 (?) breaks nested lxd with snaps

2020-03-31 Thread Stéphane Graber

This is now fixed in all channels and our own validation now checks for
this too.

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

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

Title:
  lxc 3.23 (?) breaks nested lxd with snaps

Status in lxc package in Ubuntu:
  Fix Released

Bug description:
  It looks like the latest release of lxd broke our snapd lxd test. The
  failure looks like it's lxd itself that can no longer run a nested
  lxd.

  The full log is available on e.g. 
https://api.travis-ci.org/v3/job/668138958/log.txt, search for 
  """
  Starting my-inner-ubuntu
  + MATCH from-the-INSIDE-inside
  + lxd.lxc exec my-nesting-ubuntu -- lxd.lxc exec my-inner-ubuntu -- echo 
from-the-INSIDE-inside
  Error: EOF
  grep error: pattern not found, got:
  """

  The relevant part of the test is:
  https://github.com/snapcore/snapd/blob/master/tests/main/lxd/task.yaml#L153

  I.e. this test creates an lxd container and sets up lxd inside this
  container.

  Happy to help with debugging (if needed), it really easy to reproduce
  with the above spread script.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1869661/+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 1862232] Re: Long hostname causes networking setup to fail

** Description changed:

  [impact]
  
  networkd fails to bring up networking on systems with long hostname
  
  [test case]
  
  setting the hostname:
  
  $ sudo hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf
  
  then reboot and check the networking.
  
  [regression potential]
  
- TBD
+ as this adjusts logging and certain error handling while performing
+ dhcp, any regression would likely cause dhcp failure.
  
  [scope]
  
- This is reproducable only on Bionic.
+ this is fixed by upstream commit
+ a8494759b4f14af5337391727ba295ab708b92f9 (along with some associated
+ commits around it), which is included starting in v240, so this is
+ included already in Eoan and later.
  
- [other info]
+ This is needed in Bionic and Xenial.
  
- original description:
- ---
- 
+ [original description]
  
  1) ubuntu version
  # lsb_release -rd
  Description:Ubuntu 18.04.3 LTS
  Release:18.04
  
  2) package version
  # apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10.31
    Candidate: 237-3ubuntu10.31
    Version table:
   *** 237-3ubuntu10.31 500
  500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
Packag
  es
  100 /var/lib/dpkg/status
   237-3ubuntu10.29 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages
  
  3) I expect the network to come online correctly regardless of how long
  the hostname is. This is what happens with both 14.0 and 19.0 (I tested
  the same behavior with both of them).
  
  4) the external network interface fails to be configured and is stuck in
  a (pending) state as reported by networkctl status -a
  
  setting the hostname:
  
  # hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf
  
  after rebooting the machine, it no longer has network access.
  
  # journalctl
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: 
Starting Wait for Network to be Configured...
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: Link state is up-to-date
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: found matching network 
'/run/systemd/network/10-netplan-eth0.network'
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: sd-netlink: callback failed: Invalid argument
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: lo: Link state is up-to-date
  
  # networkctl status -a:
  ● 1: lo
     Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
     State: carrier (unmanaged)
   Address: 127.0.0.1
    ::1
  
  ● 2: eth0
     Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
     State: off (pending)
  Path: pci-:00:03.0
    Driver: virtio_net
    Vendor: Red Hat, Inc.
     Model: Virtio network device
    HW Address: ae:4d:91:1c:e8:86
   DNS: 67.207.67.3
    67.207.67.2
  
  and to bring up the network correctly, set the hostname to something
  shorter
  
  # hostnamectl set-hostname asdf
  # systemctl restart systemd-networkd
  # networkctl status -a
  ● 1: lo
     Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
     State: carrier (unmanaged)
   Address: 127.0.0.1
    ::1
  
  ● 2: eth0
     Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
     State: routable (configured)
  Path: pci-:00:03.0
    Driver: virtio_net
    Vendor: Red Hat, Inc.
     Model: Virtio network device
    HW Address: ae:4d:91:1c:e8:86
   Address: 10.17.0.5
    157.245.210.250
    fe80::ac4d:91ff:fe1c:e886
   Gateway: 157.245.208.1 (ICANN, IANA Department)
   DNS: 67.207.67.3
    67.207.67.2

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

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

** Changed in: systemd (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: systemd (Ubuntu Bionic)
   Status: Confirmed => In P

[Touch-packages] [Bug 1864992] Update Released

2020-03-31 Thread Brian Murray

The verification of the Stable Release Update for kmod has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  Fix Committed
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  Fix Released
Status in kmod source package in Focal:
  Fix Released

Bug description:
  [Impact]

  * There is no impact to the end user but spurious error messages (tons
  of them) causing the perception that something really bad happened:

  Example of one of those tons of messages:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  [Test Case]

  * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin

  * sudo depmod -a -F /boot/System.map-$(uname -r)

  This will cause the spurious error messages because depmod -a -F won't
  have the "modules.builtin.bin" file created. This is a simulation of
  what the linux-modules postinst package does and an example of why the
  messages happen.

  [Regression Potential]

  * We are reverting a debian patch so we will be closer to upstream
  code base.

  * the change is about 2 different priority changes on verbosity, so
  biggest problem would be extra (or fewer) stdout/stderr messages (for
  scripts relying on them, for example).

  * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed
  to work fine.

  [Other Info]

  * Original Description:

  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   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
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/ca

[Touch-packages] [Bug 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

This bug was fixed in the package kmod - 26-1ubuntu1.1

---
kmod (26-1ubuntu1.1) eoan; urgency=medium

  * d/p/verbose_missing_bin: drop this patch to avoid spurious missing
file messages when running depmod -a for the first time in recent
kernels (>= 5.3.x) (LP: #1864992)
  * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not
actually contain a library. (Closes: #939779)

 -- Rafael David Tinoco   Wed, 11 Mar 2020
19:32:52 +

** Changed in: kmod (Ubuntu Eoan)
   Status: Fix Committed => Fix Released

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  Fix Committed
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  Fix Released
Status in kmod source package in Focal:
  Fix Released

Bug description:
  [Impact]

  * There is no impact to the end user but spurious error messages (tons
  of them) causing the perception that something really bad happened:

  Example of one of those tons of messages:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  [Test Case]

  * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin

  * sudo depmod -a -F /boot/System.map-$(uname -r)

  This will cause the spurious error messages because depmod -a -F won't
  have the "modules.builtin.bin" file created. This is a simulation of
  what the linux-modules postinst package does and an example of why the
  messages happen.

  [Regression Potential]

  * We are reverting a debian patch so we will be closer to upstream
  code base.

  * the change is about 2 different priority changes on verbosity, so
  biggest problem would be extra (or fewer) stdout/stderr messages (for
  scripts relying on them, for example).

  * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed
  to work fine.

  [Other Info]

  * Original Description:

  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   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
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no

[Touch-packages] [Bug 1864644] Re: I get logged out immediately after login to an X session (QXL Xorg driver on kernel 5.4)

2020-03-31 Thread Chris Ward

Yes, this is fixed in today's build of Focal Fossa. The bug can be
closed.

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

Title:
  I get logged out immediately after login to an X session (QXL Xorg
  driver on kernel 5.4)

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-qxl package in Ubuntu:
  Invalid
Status in systemd source package in Focal:
  Fix Released
Status in xserver-xorg-video-qxl source package in Focal:
  Invalid

Bug description:
  I just installed ubuntu 20.04 in a virtual machine and did 'apt-get
  update;apt-get upgrade' to get current (using Ctl-Alt-F2 to get a
  non-X session). After that, I tried logging in to a gnome session, and
  got logged out during login processing. This happened a few times;
  then I installed xfce4, rebooted, and got the same behaviour (logout
  during login processing) while trying to log in to an xfce session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  Date: Tue Feb 25 12:06:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2020-02-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   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
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=14c5cf63-466a-44d5-add6-bd5fc486c067 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  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-eoan
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-eoan
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  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+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/systemd/+bug/1864644/+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 1869924] [NEW] High power consumption by Intel iGPU on Skylake+

2020-03-31 Thread Sultan Alsawaf

Public bug reported:

There is an outstanding regression in i915 that breaks the RC6 power
state for Intel iGPUs on Skylake and newer. This bug was fixed upstream
in Linux 5.5. I submitted a backport of the fix for 5.4 upstream [1].

My cover letter [2] describes the issue:
The first bug, fixed by "drm/i915/gt: Schedule request retirement when timeline 
idles" upstream, is very high power consumption by i915 hardware due to an old 
commit that broke the RC6 power state for the iGPU on Skylake+. On my laptop, a 
Dell Precision 5540 with an i9-9880H, the idle power consumption of my laptop 
with this commit goes down from 10 W to 2 W, saving a massive 8 W of power. On 
other Skylake+ laptops I tested, this commit reduced idle power consumption by 
at least a few watts. The difference in power consumption can be observed by 
running `powertop` while disconnected from the charger, or by using the 
intel-undervolt tool [1] and running `intel-undervolt measure` which doesn't 
require being disconnected from the charger. The psys measurement from 
intel-undervolt is the one of interest.

Backporting this commit was not trivial due to i915's high rate of
churn, but the backport didn't require changing any code from the
original commit; it only required moving code around and not altering
some #includes.

[1] 
https://lore.kernel.org/stable/20200330033057.2629052-3-sul...@kerneltoast.com/
[2] 
https://lore.kernel.org/stable/20200330033057.2629052-1-sul...@kerneltoast.com/

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

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

** Also affects: linux
   Importance: Undecided
   Status: New

** No longer affects: lightdm (Ubuntu)

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

** No longer affects: linux

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

** Description changed:

  There is an outstanding regression in i915 that breaks the RC6 power
  state for Intel iGPUs on Skylake and newer. This bug was fixed upstream
  in Linux 5.5. I submitted a backport of the fix for 5.4 upstream [1].
  
  My cover letter [2] describes the issue:
- The first bug, fixed by
- "drm/i915/gt: Schedule request retirement when timeline idles" upstream, is 
very
- high power consumption by i915 hardware due to an old commit that broke the 
RC6
- power state for the iGPU on Skylake+. On my laptop, a Dell Precision 5540 with
- an i9-9880H, the idle power consumption of my laptop with this commit goes 
down
- from 10 W to 2 W, saving a massive 8 W of power. On other Skylake+ laptops I
- tested, this commit reduced idle power consumption by at least a few watts. 
The
- difference in power consumption can be observed by running `powertop` while
- disconnected from the charger, or by using the intel-undervolt tool [1] and
- running `intel-undervolt measure` which doesn't require being disconnected 
from
- the charger. The psys measurement from intel-undervolt is the one of interest.
+ The first bug, fixed by "drm/i915/gt: Schedule request retirement when 
timeline idles" upstream, is very high power consumption by i915 hardware due 
to an old commit that broke the RC6 power state for the iGPU on Skylake+. On my 
laptop, a Dell Precision 5540 with an i9-9880H, the idle power consumption of 
my laptop with this commit goes down from 10 W to 2 W, saving a massive 8 W of 
power. On other Skylake+ laptops I tested, this commit reduced idle power 
consumption by at least a few watts. The difference in power consumption can be 
observed by running `powertop` while disconnected from the charger, or by using 
the intel-undervolt tool [1] and running `intel-undervolt measure` which 
doesn't require being disconnected from the charger. The psys measurement from 
intel-undervolt is the one of interest.
  
- Backporting this commit was not trivial due to i915's high rate of churn, but
- the backport didn't require changing any code from the original commit; it 
only
- required moving code around and not altering some #includes.
- 
+ Backporting this commit was not trivial due to i915's high rate of
+ churn, but the backport didn't require changing any code from the
+ original commit; it only required moving code around and not altering
+ some #includes.
  
  [1] 
https://lore.kernel.org/stable/20200330033057.2629052-3-sul...@kerneltoast.com/
  [2] 
https://lore.kernel.org/stable/20200330033057.2629052-1-sul...@kerneltoast.com/

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

Title:
  High power consumption by Intel iGPU on Skylake+

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Focal:
  Incomplete

Bug description:
  There is an outstanding regression in i915 that breaks the RC6 power
  state for Intel iGPUs

[Touch-packages] [Bug 1869923] [NEW] lightdm crashes on login to system 20.04

2020-03-31 Thread Bill (franksmcb)

Public bug reported:

Ubuntu MATE 20.04 updated 03312020

Hesitation on login to system
Login successful
System reports error and crash file located in /var/crash

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu3.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-0ubuntu21
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Mar 31 11:13:52 2020
InstallationDate: Installed on 2019-12-13 (109 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20191213)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal third-party-packages

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

Title:
  lightdm crashes on login to system 20.04

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu MATE 20.04 updated 03312020

  Hesitation on login to system
  Login successful
  System reports error and crash file located in /var/crash

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu3.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-0ubuntu21
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 31 11:13:52 2020
  InstallationDate: Installed on 2019-12-13 (109 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20191213)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1869923/+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 1869117] Re: python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)

2020-03-31 Thread Arpit sharma

Is python-pip removed for focal?

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

Title:
  python-pip install fails in Ubuntu 20.04 unmet dependencies (Focal)

Status in python-pip package in Ubuntu:
  Confirmed
Status in python2.7 package in Ubuntu:
  Invalid

Bug description:
  apt-get install python-pip fails in Ubuntu 20.04:

  The following packages have unmet dependencies:
   python-pip : Depends: python-pip-whl (= 18.1-5ubuntu1) but 20.0.2-2 is to be 
installed
Recommends: python-all-dev (>= 2.6) but it is not going to be 
installed
Recommends: python-wheel but it is not going to be installed
  E: Unable to correct problems, you have held broken packages.

  The python-pip package needs to be updated to accept newer versions of
  python-pip-whl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pip/+bug/1869117/+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 1869920] [NEW] no sound

2020-03-31 Thread Hoffmann

Public bug reported:

cat /proc/asound/cards

cat /proc/asound/cards 
 0 [HDMI   ]: HDA-Intel - HDA ATI HDMI
  HDA ATI HDMI at 0xffb64000 irq 43
 1 [Generic]: HDA-Intel - HD-Audio Generic
  HD-Audio Generic at 0xffb6 irq 16

aplay /usr/share/sounds/alsa/Front_Center.wav


ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave
aplay: main:788: Fehler beim Öffnen des Gerätes: Datei oder Verzeichnis nicht 
gefunden

lsb_release -rd

Description:Ubuntu 18.04.4 LTS
Release:18.04

apt-cache policy pkgname

N: Paket pkgname kann nicht gefunden werden.


http://alsa-project.org/db/?f=faeda5de343b2d29e504e3ba0e8fdc20818d5f02

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
Uname: Linux 4.15.0-91-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.12
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  klaus 14375 F alsamixer
CurrentDesktop: GNOME-Flashback:GNOME
Date: Tue Mar 31 18:41:50 2020
InstallationDate: Installed on 2018-07-05 (635 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
PackageArchitecture: all
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to bionic on 2018-09-01 (577 days ago)
dmi.bios.date: 10/27/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.00
dmi.board.name: QC5000-ITX/PH
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd10/27/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQC5000-ITX/PH:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

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


** Tags: amd64 apport-bug bionic

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

Title:
  no sound

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  cat /proc/asound/cards

  cat /proc/asound/cards 
   0 [HDMI   ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xffb64000 irq 43
   1 [Generic]: HDA-Intel - HD-Audio Generic
HD-Audio Generic at 0xffb6 irq 16

  aplay /usr/share/sounds/alsa/Front_Center.wav

  
  ALSA lib pcm_dmix.c:1052:(snd_pcm_dmix_open) unable to open slave
  aplay: main:788: Fehler beim Öffnen des Gerätes: Datei oder Verzeichnis nicht 
gefunden

  lsb_release -rd

  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04

  apt-cache policy pkgname

  N: Paket pkgname kann nicht gefunden werden.


  http://alsa-project.org/db/?f=faeda5de343b2d29e504e3ba0e8fdc20818d5f02

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18
  Uname: Linux 4.15.0-91-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  klaus 14375 F alsamixer
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Tue Mar 31 18:41:50 2020
  InstallationDate: Installed on 2018-07-05 (635 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to bionic on 2018-09-01 (577 days ago)
  dmi.bios.date: 10/27/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.00
  dmi.board.name: QC5000-ITX/PH
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.00:bd10/27/2014:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQC5000-ITX/PH:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

-- 
Mailing list:

[Touch-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2020-03-31 Thread Lukas Dzunko

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

It is impressive how quick there was response and still this and related
bug (#1688018) is abandoned for more than 3 years ...

> On March 23, 2020 3:08:07 AM PDT, Kiruahxh <1671...@bugs.launchpad.net> wrote:
> >*** This bug is a duplicate of bug 1688018 ***
> > https://bugs.launchpad.net/bugs/1688018
> >
> >It affects me too on Ubuntu 19.04 using OpenConnect VPN
> 
> Ubuntu 19.04 has reached end of life and is no longer supported. Please 
> upgrade.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  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.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1596381] Re: [X555UA, Realtek ALC256, Mic, Internal] No sound at all

2020-03-31 Thread Xopek Endurance

Lenovo Ideapad 300 15Ibr - With Linux microphone work with strong noise
and very hard to hear me. But with Windows 7 microphone worked perfect.
I tried all of the solutions from this topic - nothing helps

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

Title:
  [X555UA, Realtek ALC256, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal mic doesn't work for Asus X555UA, Codec: Realtek ALC256

  speakers work, it's just the mic not working.

  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x5003
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_AMP_GAIN_MUTE 0x6003
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x5200
  sudo hda-verb /dev/snd/hwC0D0 0x23 SET_AMP_GAIN_MUTE 0x6200
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x503f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_AMP_GAIN_MUTE 0x603f
  sudo hda-verb /dev/snd/hwC0D0 0x08 SET_POWER_STATE 0
  sudo hda-verb /dev/snd/hwC0D0 0x1a SET_POWER_STATE 0

  8 lines make mic working until reboot.

  thx a lot for

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Sun Jun 26 23:56:46 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_AlsaRecordingTestStderr: a r e c o r d :   p c m _ r e a d : 2 0 3 2 
:   r e a d   e r r o r :   I n p u t / o u t p u t   e r r o r
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0c:   ubuntu 1983 F...m pulseaudio
   /dev/snd/controlC0:  ubuntu 1983 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X555UA, Realtek ALC256, Mic, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555UA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555UA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555UA.206:bd01/23/2016:svnASUSTeKCOMPUTERINC.:pnX555UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X555UA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1596381/+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 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

Please wait for -46 or install -43, the mute led problem will be fixed
in the -46 since I just checked the patch is in the -46 kernel. And if
the ucm doesn't cover your machine, please install
1.1.9-0ubuntu1.2testucm from
https://launchpad.net/~hui.wang/+archive/ubuntu/audio-master before the
1.3 is ready.

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

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

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Released
Status in alsa-lib source package in Eoan:
  Fix Released

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

2020-03-31 Thread ramon

I have a X1C7, Ubuntu 19.10 (Kernel 5.3.0-45), and only get a "dummy
output" in the gnome settings. If I boot with boot parameter
snd_hda_intel.dmic_detect=0 I get a working soundcard (hda intel pch,
only stereo) but no mic support. Also the mute LED does not work (but
did a few kernel updates before as did the 4.0 support). Any hints? Wait
for 46-kernel? Maybe my specific model is not in the ucm files?

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

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

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Released
Status in alsa-lib source package in Eoan:
  Fix Released

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length

** Also affects: wpa (Ubuntu Focal)
   Importance: Medium
   Status: Triaged

** Tags removed: champagne

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

Title:
  Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length

Status in wpa package in Ubuntu:
  Triaged
Status in wpa source package in Focal:
  Triaged

Bug description:
  Some wifi adapters kept asking for a password when MAC address
  randomization was enabled.

  I reported this to Realtek, and they gave me a patch for
  wpa_supplicant, which fixes the issue.

  I asked Realtek to report this upstream to wpasupplicant, and they
  did, the commit is:
  http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563

  It would be very nice to cherrypick that for Focal.

  I uploaded it as a merge request below, and I tested that it fixes the issue 
with adapters based on the following chipsets:
  ath9k, rtl8812au, rtl88x2bu and rtl8821cu

  To reproduce this:

  Ubuntu's network-manager defaults to "MAC randomization disabled", I think as 
a workaround to this specific issue. This is defined in two places:
  - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf
  - Some specific drivers in 
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf.

  With these, the problem happens in around 10% of the cases.
  To be able to reproduce it in 100% of the cases, it's best to remove these 
Ubuntu workarounds. So:
  - Set "wifi.scan-rand-mac-address=yes" in 
/etc/NetworkManager/NetworkManager.conf
  - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf.
  - systemctl stop network-manager
  - killall wpa_supplicant
  - systemctl start network-manager

  Then insert a USB wifi adapter that results in a big name with 15
  characters like wlx74ee2ae2436a and try to connect to a wifi network.
  It will keep asking for a password.

  Then apply the patch, run the 3 commands above to restart network-
  manager, and verify that it can now connect properly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+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 1868409] Re: gnome-{calculator, logs, characters} snaps not removed after the equivalent APT packages are installed on 20.04, and gnome-software APT package not replaced by snap-

2020-03-31 Thread Marcus Tomlinson

Hi Naël, yes that's correct. If you wish not to use update-manager,
correcting this will need to be done manually as you've described.

** Also affects: update-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: update-manager (Ubuntu)
   Status: New => Triaged

** Changed in: update-manager (Ubuntu)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

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

** No longer affects: gnome-logs (Ubuntu)

** No longer affects: gnome-characters (Ubuntu)

** No longer affects: gnome-calculator (Ubuntu)

** Changed in: update-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: update-manager (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  gnome-{calculator,logs,characters} snaps not removed after the
  equivalent APT packages are installed on 20.04, and gnome-software APT
  package not replaced by snap-store

Status in update-manager package in Ubuntu:
  In Progress

Bug description:
  I'm trialing the development release of Ubuntu 20.04, installed in
  December and kept up-to-date by regularly running apt full-upgrade.

  I understand from [1] that 20.04 will ship
  gnome-{calculator,logs,characters} as APT packages rather than snap
  apps, and gnome-software as a snap app (called snap-store) rather than
  an APT package.

  Following an apt full-upgrade in late February, I now have:

  * both the snap and the APT versions of gnome-{calculator,logs,characters}
  * still only the APT version of gnome-software, no snap-store

  Is this normal? A user in the #ubuntu+1 IRC channel reports that a
  fresh install of the development release:

  * only features the APT versions of gnome-{calculator,logs,characters}
  * features the snap-store (but also the APT version of gnome-software)

  Are users of older installs of the development release supposed to
  manually uninstall the snap versions of
  gnome-{calculator,logs,characters} and manually install the snap-
  store?

  [1] https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-
  remove-for-snap-snap-store/14542

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1868409/+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 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

2020-03-31 Thread Antonello

Il mar 31 mar 2020, 12:30 Sebastien Bacher  ha
scritto:

> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please answer these questions:
> * Is this reproducible? Sorry i don't know
> * If so, what specific steps should we take to recreate this bug?
>
> This will help us to find and resolve the problem.
>
> ** Changed in: ibus (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1869484
>
> Title:
>   ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()
>
> Status in ibus package in Ubuntu:
>   Incomplete
>
> Bug description:
>   i don't know what's happened
>
>   ProblemType: Crash
>   DistroRelease: Ubuntu 20.04
>   Package: ibus 1.5.22-2ubuntu1
>   ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
>   Uname: Linux 5.4.0-18-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu21
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Mar 27 23:00:56 2020
>   ExecutablePath: /usr/libexec/ibus-ui-gtk3
>   InstallationDate: Installed on 2018-08-07 (598 days ago)
>   InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64
> (20180426)
>   ProcCmdline: /usr/libexec/ibus-ui-gtk3
>   ProcEnviron:
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=it_IT.UTF-8
>SHELL=/bin/bash
>   Signal: 6
>   SourcePackage: ibus
>   StacktraceTop:
>?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
>g_assertion_message_expr () from
> /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
>?? ()
>?? ()
>?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
>   Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
>   UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   separator:
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869484/+subscriptions
>

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869484/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

This bug was fixed in the package pango1.0 - 1.44.7-2ubuntu2

---
pango1.0 (1.44.7-2ubuntu2) focal; urgency=medium

  * debian/control.in:
- version the provide, that seems needed for some of those closed
  source softwares (lp: #1869716)

 -- Sebastien Bacher   Mon, 30 Mar 2020 20:58:10
+0200

** Changed in: pango1.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Released

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

** Changed in: pulseaudio (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: pulseaudio (Ubuntu Focal)
   Status: New => Triaged

** Changed in: pulseaudio (Ubuntu Bionic)
 Assignee: (unassigned) => hugh chao (hugh712)

** Changed in: pulseaudio (Ubuntu Focal)
 Assignee: (unassigned) => hugh chao (hugh712)

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Bionic:
  Triaged
Status in pulseaudio source package in Focal:
  Triaged

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 3-ring headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 1869814] Re: ubuntu-docs build failure - possible solution

Thanks Sebastien!

Or https://gitlab.gnome.org/GNOME/libxml2/issues/64 (which is not yet
closed).

@Boyuan: Well, it does scream loudly in the sense that the build fails.

I wouldn't blame the build system in this case. It has worked in a
sensible and robust way for many years. The segfault issue only happens
with python3-libxml2, not with python-libxml2. And I have the impression
(not yet confirmed) that the segfault only happens for XML syntax errors
in Chinese translations; for similar errors in non-Chinese translations
it only prints a warning and moves on (which is the desired behavior).

** Bug watch added: gitlab.gnome.org/GNOME/libxml2/issues #64
   https://gitlab.gnome.org/GNOME/libxml2/issues/64

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  Invalid
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

2020-03-31 Thread Rob Frohne

As another work around (for those of us doing online lectures to avoid spread
of Covid-19) you can use this gnome extension.
https://extensions.gnome.org/extension/906/sound-output-device-chooser/

--
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:
[Dell Inspiron 7370] shows up in the sound output options but the
sound keeps being emitted from the internal laptop speaker

Status in PulseAudio:
New
Status in pulseaudio package in Ubuntu:
In Progress
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/pulseaudio/+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 1862232] Re: Long hostname causes networking setup to fail

2020-03-31 Thread Bug Watch Updater

** Changed in: systemd
   Status: Unknown => 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/1862232

Title:
  Long hostname causes networking setup to fail

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  [impact]

  networkd fails to bring up networking on systems with long hostname

  [test case]

  setting the hostname:

  $ sudo hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf

  then reboot and check the networking.

  [regression potential]

  TBD

  [scope]

  This is reproducable only on Bionic.

  [other info]

  original description:
  ---

  
  1) ubuntu version
  # lsb_release -rd
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

  2) package version
  # apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10.31
    Candidate: 237-3ubuntu10.31
    Version table:
   *** 237-3ubuntu10.31 500
  500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
Packag
  es
  100 /var/lib/dpkg/status
   237-3ubuntu10.29 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages

  3) I expect the network to come online correctly regardless of how
  long the hostname is. This is what happens with both 14.0 and 19.0 (I
  tested the same behavior with both of them).

  4) the external network interface fails to be configured and is stuck
  in a (pending) state as reported by networkctl status -a

  setting the hostname:

  # hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf

  after rebooting the machine, it no longer has network access.

  # journalctl
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: 
Starting Wait for Network to be Configured...
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: Link state is up-to-date
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: found matching network 
'/run/systemd/network/10-netplan-eth0.network'
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: sd-netlink: callback failed: Invalid argument
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: lo: Link state is up-to-date

  # networkctl status -a:
  ● 1: lo
     Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
     State: carrier (unmanaged)
   Address: 127.0.0.1
    ::1

  ● 2: eth0
     Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
     State: off (pending)
  Path: pci-:00:03.0
    Driver: virtio_net
    Vendor: Red Hat, Inc.
     Model: Virtio network device
    HW Address: ae:4d:91:1c:e8:86
   DNS: 67.207.67.3
    67.207.67.2

  and to bring up the network correctly, set the hostname to something
  shorter

  # hostnamectl set-hostname asdf
  # systemctl restart systemd-networkd
  # networkctl status -a
  ● 1: lo
     Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
     State: carrier (unmanaged)
   Address: 127.0.0.1
    ::1

  ● 2: eth0
     Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
     State: routable (configured)
  Path: pci-:00:03.0
    Driver: virtio_net
    Vendor: Red Hat, Inc.
     Model: Virtio network device
    HW Address: ae:4d:91:1c:e8:86
   Address: 10.17.0.5
    157.245.210.250
    fe80::ac4d:91ff:fe1c:e886
   Gateway: 157.245.208.1 (ICANN, IANA Department)
   DNS: 67.207.67.3
    67.207.67.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1862232/+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: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

** Also affects: pulseaudio (Ubuntu Focal)
   Importance: High
   Status: Confirmed

** Changed in: pulseaudio (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: pulseaudio (Ubuntu Focal)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Tags removed: rls-ff-incoming

-- 
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:
  [Dell Inspiron 7370] shows up in the sound output options but the
  sound keeps being emitted from the internal laptop speaker

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  In Progress
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/pulseaudio/+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 1869723] Re: latest updates to libpango-1.0-0 seem to break dependencies from DropBox and BitDefender

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

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

** Changed in: pango1.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  latest updates to libpango-1.0-0 seem to break dependencies from
  DropBox and BitDefender

Status in pango1.0 package in Ubuntu:
  Confirmed

Bug description:
  I'm using 20.04 beta. I think the latest updates to Pango have broken
  dependencies for DropBox-2020 and BitDefender, of less importance.

  Has libpango1.0-0 become libpango-1.0-0? I think DropBox depends on
  libpango-1.0-0, or maybe another package that's been superceded. doing
  a sudo apt upgrade gives:

  The following additional packages will be installed:
libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev libpangocairo-1.0-0 
libpangocairo-1.0-0:i386 libpangoft2-1.0-0 libpangoft2-1.0-0:i386 
libpangoxft-1.0-0 pango1.0-tools
  The following packages will be REMOVED
bitdefender-scanner-gui dropbox libpango1.0-0
  The following packages will be upgraded:
gir1.2-pango-1.0 libpango-1.0-0 libpango-1.0-0:i386 libpango1.0-dev 
libpangocairo-1.0-0 libpangocairo-1.0-0:i386 libpangoft2-1.0-0 
libpangoft2-1.0-0:i386 libpangoxft-1.0-0 pango1.0-tools

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869723/+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 1869814] Re: ubuntu-docs build failure - possible solution

2020-03-31 Thread Boyuan Yang

@Gunnar It seems that the root cause has been found, thanks! It's well
known that translation could be fragile when the build system is not
well defined; all I can think of is to make the build system robust
enough and yell out loudly enough whenever an error (e.g., segfault)
happens.

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  Invalid
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks

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

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

Title:
  zfs-initramfs fails with multiple rpool on separate disks

Status in grub2 package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  == Test Case ==
  1. On a multi disks setup, install Ubuntu with ZFS on disk 1
  2. Reboot and make sure everything works as expected
  3. Do a second installation and install Ubuntu with ZFS on disk 2
  4. Reboot

  * Expected Result *
  GRUB should display all the machines available and let the user select which 
installation to boot

  * Actual result *
  - Only one machine is listed
  - initramfs crashes because there are several pool with the same name but 
different IDs and import the pools by name
  - Same problem in the systemd generator which will try to import all the 
rpools.

  == Original Description ==

  I had an Ubuntu old installation that used a ZFS root, using the
  layout described in the ZFS on Linux docs. Consequently, the pool name
  for my Ubuntu installation was "rpool". I'm currently encountering an
  issue with that pool that only allows me to mount it read-only. So,
  I'd like to replicate the datasets from there to a new device.

  On the new device, I've set up a ZFS system using the Ubuntu 20.04
  daily installer (March 9, 2020). This setup creates a new pool named
  "rpool". So, with both devices inserted, I have two distinct pools
  each named "rpool", one of which will kernel panic if I try to mount
  it read-write.

  ZFS is fine with having multiple pools with the same name. In these
  cases, you use `zfs import` with the pool's GUID and give it a
  distinct pool name on import. However, the grub config for booting
  from ZFS doesn't appear to handle multiple pools with the same rpool
  name very well. Rather than using the pool's GUID, it uses the name,
  and as such, it's unable to boot properly when another pool with the
  name "rpool" is attached to the system.

  I think it'd be better if the config were written in such a way that
  `update-grub` generated boot config bound to whatever pool it found at
  the time of its invocation, and not start searching through all pools
  dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system
  with a ZFS root that boots just fine. But, the moment I attach the old
  pool, also named "rpool", I'm no longer able to boot up my system even
  though I haven't removed the good pool and I haven't re-run `update-
  grub`. Instead of booting, I'm thrown into the grub command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+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 1862232] Re: Long hostname causes networking setup to fail

** Bug watch added: github.com/systemd/systemd/issues #9759
   https://github.com/systemd/systemd/issues/9759

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/9759
   Importance: Unknown
   Status: Unknown

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

Title:
  Long hostname causes networking setup to fail

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  [impact]

  networkd fails to bring up networking on systems with long hostname

  [test case]

  setting the hostname:

  $ sudo hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf

  then reboot and check the networking.

  [regression potential]

  TBD

  [scope]

  This is reproducable only on Bionic.

  [other info]

  original description:
  ---

  
  1) ubuntu version
  # lsb_release -rd
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

  2) package version
  # apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10.31
    Candidate: 237-3ubuntu10.31
    Version table:
   *** 237-3ubuntu10.31 500
  500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
Packag
  es
  100 /var/lib/dpkg/status
   237-3ubuntu10.29 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   237-3ubuntu10 500
  500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages

  3) I expect the network to come online correctly regardless of how
  long the hostname is. This is what happens with both 14.0 and 19.0 (I
  tested the same behavior with both of them).

  4) the external network interface fails to be configured and is stuck
  in a (pending) state as reported by networkctl status -a

  setting the hostname:

  # hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf

  after rebooting the machine, it no longer has network access.

  # journalctl
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: 
Starting Wait for Network to be Configured...
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: Link state is up-to-date
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: found matching network 
'/run/systemd/network/10-netplan-eth0.network'
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: sd-netlink: callback failed: Invalid argument
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: lo: Link state is up-to-date

  # networkctl status -a:
  ● 1: lo
     Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
     State: carrier (unmanaged)
   Address: 127.0.0.1
    ::1

  ● 2: eth0
     Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
     State: off (pending)
  Path: pci-:00:03.0
    Driver: virtio_net
    Vendor: Red Hat, Inc.
     Model: Virtio network device
    HW Address: ae:4d:91:1c:e8:86
   DNS: 67.207.67.3
    67.207.67.2

  and to bring up the network correctly, set the hostname to something
  shorter

  # hostnamectl set-hostname asdf
  # systemctl restart systemd-networkd
  # networkctl status -a
  ● 1: lo
     Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
     State: carrier (unmanaged)
   Address: 127.0.0.1
    ::1

  ● 2: eth0
     Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
     State: routable (configured)
  Path: pci-:00:03.0
    Driver: virtio_net
    Vendor: Red Hat, Inc.
     Model: Virtio network device
    HW Address: ae:4d:91:1c:e8:86
   Address: 10.17.0.5
    157.245.210.250
    fe80::ac4d:91ff:fe1c:e886
   Gateway: 157.245.208.1 (ICANN, IANA Department)
   DNS: 67.207.67.3
    67.207.67.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1862232/+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 1869814] Re: ubuntu-docs build failure - possible solution

It's segfault in libxml code, their binding doesn't seem to handle
invalid files well, somewaht similar to
https://gitlab.gnome.org/GNOME/libxml2/-/issues/12

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

** Bug watch added: gitlab.gnome.org/GNOME/libxml2/-/issues #12
   https://gitlab.gnome.org/GNOME/libxml2/-/issues/12

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  Invalid
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1869814] Re: ubuntu-docs build failure - possible solution

Uploaded a new version of ubuntu-docs, which builds on focal despite the
issue discussed in this bug report.

** Changed in: ubuntu-docs (Ubuntu)
   Status: New => Fix Committed

** Changed in: ubuntu-docs (Ubuntu)
 Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Tags added: focal regression-release

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

Title:
  ubuntu-docs build failure - possible solution

Status in itstool package in Ubuntu:
  New
Status in libxml2 package in Ubuntu:
  New
Status in ubuntu-docs package in Ubuntu:
  Fix Committed

Bug description:
  ubuntu-docs failed to build during the second Focal Fossa test
  rebuild:

  https://launchpad.net/ubuntu/+archive/test-
  rebuild-20200327-focal/+build/18982738

  It was itstool which failed to generate the localized zh_CN pages. If
  dropping zh_CN from ubuntu-help/Makefile.am, ubuntu-docs builds. But
  excluding the Chinese pages is apparently not an acceptable solution.

  The itstool package in focal {build-,}depends on python3. I built
  itstool in a PPA with python2 instead, and in that PPA ubuntu-docs
  built fine without modifications:

  https://launchpad.net/~gunnarhj/+archive/ubuntu/ubuntu-docs/+packages

  So the root cause seems to lie neither in ubuntu-docs nor itstool. I
  would suspect that python3-libxml2 is buggy, but since itstool was
  built against python2 in eoan, it's hard to tell if it's a regression.

  Would building itstool against python2 be an acceptable workaround in
  focal?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/itstool/+bug/1869814/+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 1867774] Re: PCI/internal sound card not detected

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


some fixing patches are in the 5.3.0-43, but somehow they are not in the
5.3.0-45. I just checked the 5.3.0-46, those patches are in the -46
kernel.

So please use -43 kernel or wait for -46 kernel.


** This bug has been marked a duplicate of bug 1869799
   no sound driver since 5.3.0.42 kernel

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Two days ago the audio of my laptop was still working fine. Between
  then and now I did a kernel and gnome-shell update (those are the ones
  I remember). Now my sound settings do not show any devices beyond the
  dummy ones.

  I have Ubuntu 19.10 on my Thinkpad X1 Yoga and I've tried these
  https://itsfoss.com/fix-sound-ubuntu-1304-quick-tip/ and
  https://help.ubuntu.com/community/SoundTroubleshooting things

  Here are some maybe relevant packages

  apt-cache policy alsa-base pulseaudio
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu5
    Candidate: 1.0.25+dfsg-0ubuntu5
    Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status
  pulseaudio:
    Installed: 1:13.0-1ubuntu1.1
    Candidate: 1:13.0-1ubuntu1.1
    Version table:
   *** 1:13.0-1ubuntu1.1 500
  500 http://de.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  
  Here my lspci, which as you can see includes a audio device

  00:00.0 Host bridge: Intel Corporation Device 3e34 (rev 0c)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 
(Whiskey Lake) (rev 02)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
  00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 
/ 6th/7th Gen Core Processor Gaussian Mixture Model
  00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP 
Thermal Controller (rev 11)
  00:13.0 Serial controller: Intel Corporation Cannon Point-LP Integrated 
Sensor Hub (rev 11)
  00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI 
Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi 
[Wireless-AC] (rev 11)
  00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP 
Serial IO I2C Controller #0 (rev 11)
  00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP 
Serial IO I2C Controller #1 (rev 11)
  00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI 
Controller #1 (rev 11)
  00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port 
#1 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 11)
  00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 11)
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI 
Controller (rev 11)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-V 
(rev 11)
  02:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced 
Modem (rev 01)
  03:00.0 Non-Volatile memory controller: Sandisk Corp Device 5006
  05:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  06:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  06:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  06:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  06:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  07:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C 
step) [Alpine Ridge 4C 2016] (rev 02)
  2d:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB 
Controller (C step) [Alpine Ridge 4C 2016] (rev 02)

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_6

[Touch-packages] [Bug 1867774] Re: PCI/internal sound card not detected

2020-03-31 Thread Jesko

I'm now on -45 and the issue still exists

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Two days ago the audio of my laptop was still working fine. Between
  then and now I did a kernel and gnome-shell update (those are the ones
  I remember). Now my sound settings do not show any devices beyond the
  dummy ones.

  I have Ubuntu 19.10 on my Thinkpad X1 Yoga and I've tried these
  https://itsfoss.com/fix-sound-ubuntu-1304-quick-tip/ and
  https://help.ubuntu.com/community/SoundTroubleshooting things

  Here are some maybe relevant packages

  apt-cache policy alsa-base pulseaudio
  alsa-base:
    Installed: 1.0.25+dfsg-0ubuntu5
    Candidate: 1.0.25+dfsg-0ubuntu5
    Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu eoan/main i386 Packages
  100 /var/lib/dpkg/status
  pulseaudio:
    Installed: 1:13.0-1ubuntu1.1
    Candidate: 1:13.0-1ubuntu1.1
    Version table:
   *** 1:13.0-1ubuntu1.1 500
  500 http://de.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  
  Here my lspci, which as you can see includes a audio device

  00:00.0 Host bridge: Intel Corporation Device 3e34 (rev 0c)
  00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 620 
(Whiskey Lake) (rev 02)
  00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c)
  00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 
/ 6th/7th Gen Core Processor Gaussian Mixture Model
  00:12.0 Signal processing controller: Intel Corporation Cannon Point-LP 
Thermal Controller (rev 11)
  00:13.0 Serial controller: Intel Corporation Cannon Point-LP Integrated 
Sensor Hub (rev 11)
  00:14.0 USB controller: Intel Corporation Cannon Point-LP USB 3.1 xHCI 
Controller (rev 11)
  00:14.2 RAM memory: Intel Corporation Cannon Point-LP Shared SRAM (rev 11)
  00:14.3 Network controller: Intel Corporation Cannon Point-LP CNVi 
[Wireless-AC] (rev 11)
  00:15.0 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP 
Serial IO I2C Controller #0 (rev 11)
  00:15.1 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP 
Serial IO I2C Controller #1 (rev 11)
  00:16.0 Communication controller: Intel Corporation Cannon Point-LP MEI 
Controller #1 (rev 11)
  00:1c.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port 
#1 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1d.4 PCI bridge: Intel Corporation Cannon Point-LP PCI Express Root Port 
#13 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Cannon Point-LP LPC Controller (rev 11)
  00:1f.3 Audio device: Intel Corporation Cannon Point-LP High Definition Audio 
Controller (rev 11)
  00:1f.4 SMBus: Intel Corporation Cannon Point-LP SMBus Controller (rev 11)
  00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Point-LP SPI 
Controller (rev 11)
  00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (6) I219-V 
(rev 11)
  02:00.0 Wireless controller [0d40]: Intel Corporation XMM7360 LTE Advanced 
Modem (rev 01)
  03:00.0 Non-Volatile memory controller: Sandisk Corp Device 5006
  05:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  06:00.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  06:01.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  06:02.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  06:04.0 PCI bridge: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) 
[Alpine Ridge 4C 2016] (rev 02)
  07:00.0 System peripheral: Intel Corporation JHL6540 Thunderbolt 3 NHI (C 
step) [Alpine Ridge 4C 2016] (rev 02)
  2d:00.0 USB controller: Intel Corporation JHL6540 Thunderbolt 3 USB 
Controller (C step) [Alpine Ridge 4C 2016] (rev 02)

  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 17 14:21:31 2020
  InstallationDate: Installed on 2020-01-15 (61 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Rele

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

some fixing patches are in the 5.3.0-43, but somehow they are not in the
5.3.0-45.  I just checked the 5.3.0-46, those patches are in the -46
kernel.

So please use -43 kernel or wait for -46 kernel.

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

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

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Released
Status in alsa-lib source package in Eoan:
  Fix Released

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

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

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

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

-- 
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:
  Incomplete
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: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1864644] Re: I get logged out immediately after login to an X session (QXL Xorg driver on kernel 5.4)

Fixed by landing 245 to Focal.

** Changed in: systemd (Ubuntu Focal)
 Assignee: (unassigned) => Balint Reczey (rbalint)

** Changed in: systemd (Ubuntu Focal)
   Status: Triaged => 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/1864644

Title:
  I get logged out immediately after login to an X session (QXL Xorg
  driver on kernel 5.4)

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-qxl package in Ubuntu:
  Invalid
Status in systemd source package in Focal:
  Fix Released
Status in xserver-xorg-video-qxl source package in Focal:
  Invalid

Bug description:
  I just installed ubuntu 20.04 in a virtual machine and did 'apt-get
  update;apt-get upgrade' to get current (using Ctl-Alt-F2 to get a
  non-X session). After that, I tried logging in to a gnome session, and
  got logged out during login processing. This happened a few times;
  then I installed xfce4, rebooted, and got the same behaviour (logout
  during login processing) while trying to log in to an xfce session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  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
  Date: Tue Feb 25 12:06:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) (prog-if 00 
[VGA controller])
 Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100]
  InstallationDate: Installed on 2020-02-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   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
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=linux
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-14-generic 
root=UUID=14c5cf63-466a-44d5-add6-bd5fc486c067 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  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-eoan
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-eoan:cvnQEMU:ct1:cvrpc-i440fx-eoan:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-eoan
  dmi.sys.vendor: QEMU
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu1
  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+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/systemd/+bug/1864644/+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 1869484] Re: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please answer these questions:
* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

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

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

Title:
  ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message.cold()

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  i don't know what's happened

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: ibus 1.5.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 27 23:00:56 2020
  ExecutablePath: /usr/libexec/ibus-ui-gtk3
  InstallationDate: Installed on 2018-08-07 (598 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcCmdline: /usr/libexec/ibus-ui-gtk3
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: ibus
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? ()
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
  Title: ibus-ui-gtk3 crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: Upgraded to focal on 2020-03-08 (19 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1869484/+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 1869501] Re: Bluetooth status in the Unity menu bar does not always match status in system settings

** Package changed: bluez (Ubuntu) => indicator-bluetooth (Ubuntu)

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

Title:
  Bluetooth status in the Unity menu bar does not always match status in
  system settings

Status in indicator-bluetooth package in Ubuntu:
  New
Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  When no Bluetooth device is connected and I turn off Bluetooth with
  the switch in the menu of the notification icon, the Bluetooth status
  in System Settings app is still "on" however Bluetooth seems to be
  off.

  Also, when Bluetooth is turned on, the status of a paired device may
  show "connection on" in the notification icon menu when it is actually
  not connected, as System Settings do show correctly. In this case I
  have to switch off and on again if I want to activate the connection.

  Also, I can not switch the connection to a paired device on or off
  with the System Settings app. The switches are grey and I can not
  click them, however they do always show the correct status.

  Using: Ubuntu 19.10 with Unity desktop on Asus x571 laptop

  Info:

  unity: 7.5.0+19.10.20190924-0ubuntu1
  unity-control-center: 15.04.0+19.10.20190921-0ubuntu1

  service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset: enabled)
 Active: active (running) since Sat 2020-03-28 11:26:18 CET; 5h 42min ago
   Docs: man:bluetoothd(8)
   Main PID: 1035 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4915)
 Memory: 3.5M
 CGroup: /system.slice/bluetooth.service
 └─1035 /usr/lib/bluetooth/bluetoothd

  Mär 28 14:17:39 Abook bluetoothd[1035]: 
/org/bluez/hci0/dev_00_22_37_55_9E_7D/fd0: fd(22) ready
  Mär 28 16:46:32 Abook bluetoothd[1035]: Failed to set mode: Blocked through 
rfkill (0x12)
  Mär 28 16:49:02 Abook bluetoothd[1035]: 
/org/bluez/hci0/dev_00_22_37_55_9E_7D/fd1: fd(22) ready
  Mär 28 16:49:22 Abook bluetoothd[1035]: Failed to set mode: Blocked through 
rfkill (0x12)
  Mär 28 16:50:05 Abook bluetoothd[1035]: Control: Refusing unexpected connect
  Mär 28 16:50:08 Abook bluetoothd[1035]: 
/org/bluez/hci0/dev_00_22_37_55_9E_7D/fd2: fd(22) ready
  Mär 28 16:53:38 Abook bluetoothd[1035]: Failed to set mode: Blocked through 
rfkill (0x12)
  Mär 28 16:58:41 Abook bluetoothd[1035]: Failed to set mode: Blocked through 
rfkill (0x12)
  Mär 28 16:59:23 Abook bluetoothd[1035]: Control: Refusing unexpected connect
  Mär 28 16:59:25 Abook bluetoothd[1035]: 
/org/bluez/hci0/dev_00_22_37_55_9E_7D/fd3: fd(22) ready

  Bluetooth device:
  T:  Bus=01 Lev=01 Prnt=01 Port=13 Cnt=02 Dev#=  6 Spd=12  MxCh= 0
  D:  Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
  P:  Vendor=8087 ProdID=0029 Rev=00.01
  C:  #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
  I:  If#=0x0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
  I:  If#=0x1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: unity-control-center 15.04.0+19.10.20190921-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Mar 28 16:53:08 2020
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-01-20 (68 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1869501/+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 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

Marking as invalid for systemd since there is not much pointing at
systemd here.

** Changed in: systemd (Ubuntu)
   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/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: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks

2020-03-31 Thread Didier Roche

Hey Balint. I just added the task post ZFS upload (the upload was
yesterday and I added the task this morning) so indeed, there is some
work needed, part of it being in systemd.

Basically, systemd isn’t capable of mounting datasets when pool names are 
duplicated on a machine
zfs-mount-generator generates .mount units with the pool name. systemd needs to 
either, for all poo«ls mactching the desired name
- prefers pool id matching zpool.cache
- check every pools for their dataset and import the first matching one (same 
dataset path)
- or the .mount unit should be able to import by ID and zfs-mount-generator 
upstream should generate a pool id somewhere in the unit file.

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

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

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

Title:
  zfs-initramfs fails with multiple rpool on separate disks

Status in grub2 package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  == Test Case ==
  1. On a multi disks setup, install Ubuntu with ZFS on disk 1
  2. Reboot and make sure everything works as expected
  3. Do a second installation and install Ubuntu with ZFS on disk 2
  4. Reboot

  * Expected Result *
  GRUB should display all the machines available and let the user select which 
installation to boot

  * Actual result *
  - Only one machine is listed
  - initramfs crashes because there are several pool with the same name but 
different IDs and import the pools by name
  - Same problem in the systemd generator which will try to import all the 
rpools.

  == Original Description ==

  I had an Ubuntu old installation that used a ZFS root, using the
  layout described in the ZFS on Linux docs. Consequently, the pool name
  for my Ubuntu installation was "rpool". I'm currently encountering an
  issue with that pool that only allows me to mount it read-only. So,
  I'd like to replicate the datasets from there to a new device.

  On the new device, I've set up a ZFS system using the Ubuntu 20.04
  daily installer (March 9, 2020). This setup creates a new pool named
  "rpool". So, with both devices inserted, I have two distinct pools
  each named "rpool", one of which will kernel panic if I try to mount
  it read-write.

  ZFS is fine with having multiple pools with the same name. In these
  cases, you use `zfs import` with the pool's GUID and give it a
  distinct pool name on import. However, the grub config for booting
  from ZFS doesn't appear to handle multiple pools with the same rpool
  name very well. Rather than using the pool's GUID, it uses the name,
  and as such, it's unable to boot properly when another pool with the
  name "rpool" is attached to the system.

  I think it'd be better if the config were written in such a way that
  `update-grub` generated boot config bound to whatever pool it found at
  the time of its invocation, and not start searching through all pools
  dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system
  with a ZFS root that boots just fine. But, the moment I attach the old
  pool, also named "rpool", I'm no longer able to boot up my system even
  though I haven't removed the good pool and I haven't re-run `update-
  grub`. Instead of booting, I'm thrown into the grub command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+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 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks

Is there anything left to do in systemd?

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

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

Title:
  zfs-initramfs fails with multiple rpool on separate disks

Status in grub2 package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Incomplete
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  == Test Case ==
  1. On a multi disks setup, install Ubuntu with ZFS on disk 1
  2. Reboot and make sure everything works as expected
  3. Do a second installation and install Ubuntu with ZFS on disk 2
  4. Reboot

  * Expected Result *
  GRUB should display all the machines available and let the user select which 
installation to boot

  * Actual result *
  - Only one machine is listed
  - initramfs crashes because there are several pool with the same name but 
different IDs and import the pools by name
  - Same problem in the systemd generator which will try to import all the 
rpools.

  == Original Description ==

  I had an Ubuntu old installation that used a ZFS root, using the
  layout described in the ZFS on Linux docs. Consequently, the pool name
  for my Ubuntu installation was "rpool". I'm currently encountering an
  issue with that pool that only allows me to mount it read-only. So,
  I'd like to replicate the datasets from there to a new device.

  On the new device, I've set up a ZFS system using the Ubuntu 20.04
  daily installer (March 9, 2020). This setup creates a new pool named
  "rpool". So, with both devices inserted, I have two distinct pools
  each named "rpool", one of which will kernel panic if I try to mount
  it read-write.

  ZFS is fine with having multiple pools with the same name. In these
  cases, you use `zfs import` with the pool's GUID and give it a
  distinct pool name on import. However, the grub config for booting
  from ZFS doesn't appear to handle multiple pools with the same rpool
  name very well. Rather than using the pool's GUID, it uses the name,
  and as such, it's unable to boot properly when another pool with the
  name "rpool" is attached to the system.

  I think it'd be better if the config were written in such a way that
  `update-grub` generated boot config bound to whatever pool it found at
  the time of its invocation, and not start searching through all pools
  dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system
  with a ZFS root that boots just fine. But, the moment I attach the old
  pool, also named "rpool", I'm no longer able to boot up my system even
  though I haven't removed the good pool and I haven't re-run `update-
  grub`. Instead of booting, I'm thrown into the grub command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+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 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing

Please also try kernel 5.3 or older on focal.

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

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

Status in bluez package in Ubuntu:
  New

Bug description:
  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2

  Summary
  ===

  BT earphones/speaker cannot be connected either using GNOME control
  center, either using bluetoothctl. I've tried with previous versions
  of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same
  issue, so I believe this is a problem with bluez.

  However, the same procedure works fine on Ubuntu 19.10 (kernel
  5.3.0-18, bluez 5.50), so I think it's a regression in bluez.

  Steps to reproduce
  ==

  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
    -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
    -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)

  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.

  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:

  $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
    0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed

  Additional information
  ==

  $ lspci -vv -s 01:00.0
  01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
   Subsystem: Intel Corporation Dual Band Wireless-AC 7265
   Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
   Status: Cap+ 66MHz- UD

[Touch-packages] [Bug 1869857] Re: [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately after pairing

Just testing my own machine again I quickly encountered a crash in
bluetoothd. Do you see anything like that on your machine (run dmesg)?

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

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

Status in bluez package in Ubuntu:
  New

Bug description:
  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2

  Summary
  ===

  BT earphones/speaker cannot be connected either using GNOME control
  center, either using bluetoothctl. I've tried with previous versions
  of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same
  issue, so I believe this is a problem with bluez.

  However, the same procedure works fine on Ubuntu 19.10 (kernel
  5.3.0-18, bluez 5.50), so I think it's a regression in bluez.

  Steps to reproduce
  ==

  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
    -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
    -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)

  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.

  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:

  $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
    0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed

  Additional information
  ==

  $ lspci -vv -s 01:00.0
  01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
   Subsystem: Intel Corporation Dual Band Wireless-AC 7265
   Control: I/O- Mem+ BusMaster+ SpecCy

[Touch-packages] [Bug 1869629] Re: please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns

2020-03-31 Thread Christian Ehrhardt 

** Tags added: rls-ff-incoming

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

Title:
  please add /etc/mdns.allow to /etc/apparmor.d/abstractions/mdns

Status in apparmor package in Ubuntu:
  New
Status in chrony package in Ubuntu:
  Invalid

Bug description:
  In focal users of mdns get denials in apparmor confined applications.
  An exampel can be found in the original bug below.

  It seems it is a common pattern, see
  https://github.com/lathiat/nss-mdns#etcmdnsallow

  Therefore I'm asking to add
 /etc/mdns.allow r,
  to the file
 /etc/apparmor.d/abstractions/mdns"
  by default.

  --- original bug ---

  Many repetitions of

  audit: type=1400 audit(1585517168.705:63): apparmor="DENIED"
  operation="open" profile="/usr/sbin/chronyd" name="/etc/mdns.allow"
  pid=1983815 comm="chronyd" requested_mask="r" denied_mask="r"
  fsuid=123 ouid=0

  in log.  I use libnss-mdns for .local name resolution, so
  /etc/nsswitch.conf contains

  hosts:  files mdns [NOTFOUND=return] myhostname dns

  and /etc/mnds.allow contains the domains to resolve with mDNS (in may
  case, "local." and "local"; see /usr/share/doc/libnss-
  mdns/README.html.)

  Presumably cronyd calls a gethostbyX() somewhere, thus eventually
  trickling down through the name service switch and opening
  /etc/mdns.allow, which the AppArmor profile in the chrony package does
  not allow.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: chrony 3.5-6ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  Date: Sun Mar 29 15:02:39 2020
  InstallationDate: Installed on 2020-03-26 (3 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200326)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: chrony
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1869629/+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 1869857] Re: [Intel 7265][Regression] Cannot connect BT earphones or speakers

Oh, it's a UE BOOM.

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

** Summary changed:

- [Intel 7265][Regression] Cannot connect BT earphones or speakers
+ [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects immediately 
after pairing

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

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

Status in bluez package in Ubuntu:
  New

Bug description:
  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2

  Summary
  ===

  BT earphones/speaker cannot be connected either using GNOME control
  center, either using bluetoothctl. I've tried with previous versions
  of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same
  issue, so I believe this is a problem with bluez.

  However, the same procedure works fine on Ubuntu 19.10 (kernel
  5.3.0-18, bluez 5.50), so I think it's a regression in bluez.

  Steps to reproduce
  ==

  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
    -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
    -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)

  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.

  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:

  $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
    0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed

  Additional information
  ==

  $ lspci -vv -s 01:00.0
  01:00.0 Network controller: Intel Corpo

[Touch-packages] [Bug 1869765] Re: Problems dealing with Java Script promise in HTML

2020-03-31 Thread Dmitry Shachnev

Will you mind if I close this bug then?

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

Title:
  Problems dealing with Java Script promise in HTML

Status in qtwebkit-opensource-src package in Ubuntu:
  New

Bug description:
  We're using the GlobalProtect UI Client in Ubuntu. This uses
  libqt5webkit5 to provide allow login with an external SAML single sign
  on provider. This works with several identity providers (okta,
  jumpcloud). However, it does not work with Azure.

  Issue ID 9415 - https://docs.paloaltonetworks.com/globalprotect/5-1
  /globalprotect-app-release-notes/gp-app-release-information/known-
  issues-related-to-gp-app

  The problem seems to be that the Azure AD HTML response has a java
  promise in it and this seems to be problematic in versions of
  libqt5webkit5 >= 5.212.0.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1869765/+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 1869857] Re: [Intel 7265][Regression] Cannot connect BT earphones or speakers

I can't see anyone else reporting such issues right now. What model of
speaker/headphones is it?

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

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

Title:
  [Intel 7265][Regression] Ultimate Ears BOOM speaker disconnects
  immediately after pairing

Status in bluez package in Ubuntu:
  New

Bug description:
  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2

  Summary
  ===

  BT earphones/speaker cannot be connected either using GNOME control
  center, either using bluetoothctl. I've tried with previous versions
  of the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same
  issue, so I believe this is a problem with bluez.

  However, the same procedure works fine on Ubuntu 19.10 (kernel
  5.3.0-18, bluez 5.50), so I think it's a regression in bluez.

  Steps to reproduce
  ==

  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
    -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
    -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)

  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.

  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:

  $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
    0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed

  Additional information
  ==

  $ lspci -vv -s 01:00.0
  01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
   Subsystem: Intel Corporation Dual Band Wireless-AC 7265
   Control: I/O-

[Touch-packages] [Bug 1867007] Re: zfs-initramfs fails with multiple rpool on separate disks

This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu10

---
zfs-linux (0.8.3-1ubuntu10) focal; urgency=medium

  [ Jean-Baptiste Lallement ]
  [ Didier Roche ]
  * Make debian/patches/4000-zsys-support.patch more robust in case of
corruption and faster:
- Don’t call out zsys if the system hasn’t changed compared to its cache.
  This drastically speed up boot by some seconds.
- Drop into emergency mode with some error message in dmesg with the
  failing command output in case some errors happen during revert.
  Prevents thus booting which would have screwed over root partition by
  creating a /boot non empty directory (like /boot/grub) in mounting over.
  Let now user still boot without reverting to be able to fix the issue.
- Base what we import on cache file so that in the future (once grub is
  fixed) booting with multiple rpool and bpool. (LP: #1867007)
  * debian/patches/4500-fix-generator-invalid-cache.patch:
- Removed, not needed anymore with previous patch enhancement.

 -- Didier Roche   Mon, 30 Mar 2020 17:05:32 +0200

** Changed in: zfs-linux (Ubuntu)
   Status: Triaged => 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/1867007

Title:
  zfs-initramfs fails with multiple rpool on separate disks

Status in grub2 package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in zfs-linux package in Ubuntu:
  Fix Released

Bug description:
  == Test Case ==
  1. On a multi disks setup, install Ubuntu with ZFS on disk 1
  2. Reboot and make sure everything works as expected
  3. Do a second installation and install Ubuntu with ZFS on disk 2
  4. Reboot

  * Expected Result *
  GRUB should display all the machines available and let the user select which 
installation to boot

  * Actual result *
  - Only one machine is listed
  - initramfs crashes because there are several pool with the same name but 
different IDs and import the pools by name
  - Same problem in the systemd generator which will try to import all the 
rpools.

  == Original Description ==

  I had an Ubuntu old installation that used a ZFS root, using the
  layout described in the ZFS on Linux docs. Consequently, the pool name
  for my Ubuntu installation was "rpool". I'm currently encountering an
  issue with that pool that only allows me to mount it read-only. So,
  I'd like to replicate the datasets from there to a new device.

  On the new device, I've set up a ZFS system using the Ubuntu 20.04
  daily installer (March 9, 2020). This setup creates a new pool named
  "rpool". So, with both devices inserted, I have two distinct pools
  each named "rpool", one of which will kernel panic if I try to mount
  it read-write.

  ZFS is fine with having multiple pools with the same name. In these
  cases, you use `zfs import` with the pool's GUID and give it a
  distinct pool name on import. However, the grub config for booting
  from ZFS doesn't appear to handle multiple pools with the same rpool
  name very well. Rather than using the pool's GUID, it uses the name,
  and as such, it's unable to boot properly when another pool with the
  name "rpool" is attached to the system.

  I think it'd be better if the config were written in such a way that
  `update-grub` generated boot config bound to whatever pool it found at
  the time of its invocation, and not start searching through all pools
  dynamically upon boot. Just to be clear, I have an Ubuntu 20.04 system
  with a ZFS root that boots just fine. But, the moment I attach the old
  pool, also named "rpool", I'm no longer able to boot up my system even
  though I haven't removed the good pool and I haven't re-run `update-
  grub`. Instead of booting, I'm thrown into the grub command line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867007/+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 1869857] Re: [Intel 7265][Regression] Cannot connect BT earphones or speakers

2020-03-31 Thread Pierre Equoy

** Attachment added: "5.3.0-18-btmon-speaker.log"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1869857/+attachment/5343689/+files/5.3.0-18-btmon-speaker.log

** Description changed:

  Laptop: Dell Inspiron 7370
  CID: 201704-25503
  Ubuntu version: 20.04 daily
  Linux kernel: 5.4.0-18-generic
  Bluez: 5.53-0ubuntu2
  
  Summary
  ===
  
  BT earphones/speaker cannot be connected either using GNOME control
- center, either using bluetoothctl.
+ center, either using bluetoothctl. I've tried with previous versions of
+ the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue,
+ so I believe this is a problem with bluez.
  
  However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18,
- bluez 5.50)
+ bluez 5.50), so I think it's a regression in bluez.
  
  Steps to reproduce
  ==
  
  1. Open GNOME control center, go to Bluetooth, make sure it's turned on
  2. Put the BT device in pairing mode (usually, long press on the Power button)
-   -> in g-c-c, the device appears as "Not Set Up" (OK)
+   -> in g-c-c, the device appears as "Not Set Up" (OK)
  3. Click on the device to pair it
-   -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)
+   -> the device is briefly marked as "Connected", then immediately switches 
to "Disconnected" (Not OK)
  
  The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
  when I follow steps 1-3 above.
  
  I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
  5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)
  
  Back to Ubuntu 20.04, if I try to pair and connect the device using
  bluetoothctl, it fails:
  
- $ sudo bluetoothctl 
+ $ sudo bluetoothctl
  Agent registered
  [CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
  [bluetooth]# power on
  Changing power on succeeded
  [bluetooth]# pairable on
  Changing pairable on succeeded
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
  [NEW] Device 88:C6:26:1A:9E:AF UE BOOM
  [CHG] Device 61:E5:46:38:58:8B RSSI: -86
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
  [CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
-   0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
+   0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
  [CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
  [CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
  [CHG] Device 56:AE:9C:58:00:BA RSSI: -87
  [CHG] Device 56:AE:9C:58:00:BA TxPower: 12
  [CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
  [CHG] Device 75:79:4D:66:E9:FF RSSI: -81
  [CHG] Device 75:79:4D:66:E9:FF TxPower: 12
  [CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
  [bluetooth]# scan off
  Discovery stopped
  [CHG] Controller C8:21:58:B7:2E:82 Discovering: no
  [CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
  [CHG] Device 75:79:4D:66:E9:FF TxPower is nil
  [CHG] Device 75:79:4D:66:E9:FF RSSI is nil
  [CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
  [CHG] Device 56:AE:9C:58:00:BA TxPower is nil
  [CHG] Device 56:AE:9C:58:00:BA RSSI is nil
  [CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
  [CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
  [CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
  [CHG] Device 61:E5:46:38:58:8B RSSI is nil
  [CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
  [CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
  [bluetooth]# pair 88:C6:26:1A:9E:AF
  Attempting to pair with 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Connected: yes
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
  [CHG] Device 88:C6:26:1A:9E:AF Paired: yes
  Pairing successful
  [CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
  [CHG] Device 88:C6:26:1A:9E:AF Connected: no
  [bluetooth]# trust 88:C6:26:1A:9E:AF
  [CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
  Changing 88:C6:26:1A:9E:AF trust succeeded
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  [bluetooth]# connect 88:C6:26:1A:9E:AF
  Attempting to connect to 88:C6:26:1A:9E:AF
  Failed to connect: org.bluez.Error.Failed
  
- 
- 
  Additional information
  ==
  
  $ lspci -vv -s 01:00.0
  01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
-   Subsystem: Intel Corporation Dual Band

[Touch-packages] [Bug 1869857] [NEW] [Intel 7265][Regression] Cannot connect BT earphones or speakers

2020-03-31 Thread Pierre Equoy

Public bug reported:

Laptop: Dell Inspiron 7370
CID: 201704-25503
Ubuntu version: 20.04 daily
Linux kernel: 5.4.0-18-generic
Bluez: 5.53-0ubuntu2

Summary
===

BT earphones/speaker cannot be connected either using GNOME control
center, either using bluetoothctl. I've tried with previous versions of
the kernel as well (5.4.0-14, 5.4.0-9) and it exhibits the same issue,
so I believe this is a problem with bluez.

However, the same procedure works fine on Ubuntu 19.10 (kernel 5.3.0-18,
bluez 5.50), so I think it's a regression in bluez.

Steps to reproduce
==

1. Open GNOME control center, go to Bluetooth, make sure it's turned on
2. Put the BT device in pairing mode (usually, long press on the Power button)
  -> in g-c-c, the device appears as "Not Set Up" (OK)
3. Click on the device to pair it
  -> the device is briefly marked as "Connected", then immediately switches to 
"Disconnected" (Not OK)

The attached btmon logs (5.4.0-18-btmon-speaker.log) show what happens
when I follow steps 1-3 above.

I tried the same procedure on a 19.10 live usb (kernel 5.3.0-18, bluez
5.50) and it works fine (see attached logs 5.3.0-18-btmon-speaker.log)

Back to Ubuntu 20.04, if I try to pair and connect the device using
bluetoothctl, it fails:

$ sudo bluetoothctl
Agent registered
[CHG] Controller C8:21:58:B7:2E:82 Pairable: yes
[bluetooth]# power on
Changing power on succeeded
[bluetooth]# pairable on
Changing pairable on succeeded
[bluetooth]# scan on
Discovery started
[CHG] Controller C8:21:58:B7:2E:82 Discovering: yes
[NEW] Device 88:C6:26:1A:9E:AF UE BOOM
[CHG] Device 61:E5:46:38:58:8B RSSI: -86
[CHG] Device 61:E5:46:38:58:8B ManufacturerData Key: 0x004c
[CHG] Device 61:E5:46:38:58:8B ManufacturerData Value:
  0c 0e 08 c5 ea 55 99 d4 da 92 56 98 49 f3 8b 13  .UV.I...
[CHG] Device 38:F9:D3:3D:A2:CC RSSI: -87
[CHG] Device 7D:2A:91:B5:44:07 RSSI: -90
[CHG] Device 7D:2A:91:B5:44:07 TxPower: 12
[CHG] Device 56:AE:9C:58:00:BA RSSI: -87
[CHG] Device 56:AE:9C:58:00:BA TxPower: 12
[CHG] Device 28:11:A5:B6:FE:DD RSSI: -86
[CHG] Device 75:79:4D:66:E9:FF RSSI: -81
[CHG] Device 75:79:4D:66:E9:FF TxPower: 12
[CHG] Device 31:DD:66:D7:C9:3D RSSI: -87
[bluetooth]# scan off
Discovery stopped
[CHG] Controller C8:21:58:B7:2E:82 Discovering: no
[CHG] Device 31:DD:66:D7:C9:3D RSSI is nil
[CHG] Device 75:79:4D:66:E9:FF TxPower is nil
[CHG] Device 75:79:4D:66:E9:FF RSSI is nil
[CHG] Device 28:11:A5:B6:FE:DD RSSI is nil
[CHG] Device 56:AE:9C:58:00:BA TxPower is nil
[CHG] Device 56:AE:9C:58:00:BA RSSI is nil
[CHG] Device 7D:2A:91:B5:44:07 TxPower is nil
[CHG] Device 7D:2A:91:B5:44:07 RSSI is nil
[CHG] Device 38:F9:D3:3D:A2:CC RSSI is nil
[CHG] Device 61:E5:46:38:58:8B RSSI is nil
[CHG] Device 88:C6:26:1A:9E:AF TxPower is nil
[CHG] Device 88:C6:26:1A:9E:AF RSSI is nil
[bluetooth]# pair 88:C6:26:1A:9E:AF
Attempting to pair with 88:C6:26:1A:9E:AF
[CHG] Device 88:C6:26:1A:9E:AF Connected: yes
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: -deca-fade-deca-deafdecacaff
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1101--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110a--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110b--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110c--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 110e--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 111e--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF UUIDs: 1200--1000-8000-00805f9b34fb
[CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: yes
[CHG] Device 88:C6:26:1A:9E:AF Paired: yes
Pairing successful
[CHG] Device 88:C6:26:1A:9E:AF ServicesResolved: no
[CHG] Device 88:C6:26:1A:9E:AF Connected: no
[bluetooth]# trust 88:C6:26:1A:9E:AF
[CHG] Device 88:C6:26:1A:9E:AF Trusted: yes
Changing 88:C6:26:1A:9E:AF trust succeeded
[bluetooth]# connect 88:C6:26:1A:9E:AF
Attempting to connect to 88:C6:26:1A:9E:AF
Failed to connect: org.bluez.Error.Failed
[bluetooth]# connect 88:C6:26:1A:9E:AF
Attempting to connect to 88:C6:26:1A:9E:AF
Failed to connect: org.bluez.Error.Failed

Additional information
==

$ lspci -vv -s 01:00.0
01:00.0 Network controller: Intel Corporation Wireless 7265 (rev 59)
 Subsystem: Intel Corporation Dual Band Wireless-AC 7265
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- 
SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
 Kernel driver in use: iwlwifi
 Kernel modules: iwlwifi

$ dmesg | grep -i bluetooth
[   15.748300] Bluetooth: Core ver 2.22
[   15.748312] Bluetooth: HCI device and connection manager initialized
[   15.748315] Bluetooth: HCI socket layer initialized
[   15.748317] Bluetooth: L2CAP socket layer initialized
[   15.748320] Bluetooth: SCO socket layer initialized
[   15.925524] Bluetooth: hci0: read Intel version: 370810011003110e00
[   15.926254] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-h

[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

2020-03-31 Thread Alkis Georgopoulos

Anydesk too. Thanks for the fix! :)

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

** Changed in: network-manager (Ubuntu Xenial)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)

** Changed in: network-manager (Ubuntu)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)

** Changed in: network-manager (Ubuntu Yakkety)
 Assignee: Mathieu Trudel-Lapierre (cyphermox) => (unassigned)

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Won't Fix

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1839290] Re: systemd doesn't restart a service after crashes

2020-03-31 Thread Vladimir Kononov

Thank you, Dan, that is great news.

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

Title:
  systemd doesn't restart a service after crashes

Status in systemd:
  Fix Released
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 Disco:
  Fix Released

Bug description:
  [impact]

  when a service configured to restart crashes, under certain
  configurations, that service is not correctly restarted.

  [test case]

  see comment 8

  [regression potential]

  this changes the job mode of manager-triggered restarts to 'replace'
  any existing queued job(s), instead of failing if there are queued
  job(s).  thus any regressions would occur when a service fails, that
  is configured to restart on failure.

  [scope]

  This is needed only for Xenial and Bionic.

  this is fixed with commit 03ff2dc71ecb09272d728d458498b44f7f132f51
  which is included already in Eoan.

  [other info]

  original description:
  ---

  Affected versions of OS and systemd:
  $ cat /etc/issue
  Ubuntu 16.04.6 LTS \n \l
  $ systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Affected packages:
  systemd 229-4ubuntu21.22 and previous versions.

  Expected behaviour you didn't see:
  Scheduling restart of failed service.
  A process crashed by sigabrt and didn't restart.

  Description:
  The bug was reported to a systemd upstream repository: 
https://github.com/systemd/systemd/issues/11456
  The bug was fixed and accepted to the master branch: 
https://github.com/systemd/systemd/pull/11467/files

  Action:
  Include this patch to Ubuntu 16.04 and other version of Ubuntu which are 
supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1839290/+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 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager (Ubuntu)
   Status: New => Triaged

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

Title:
  [focal] nm-online -s --timeout=10 timeout every time

Status in MAAS:
  Incomplete
Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Also created bug on upstream :
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398

  
  This issue will cause "NetworkManager-wait-online.service: Failed with result 
'exit-code'."
  And cloud-init.service is counting on this service for network status.

  So this issue will finally cause MaaS deploying failed.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu1 [modified: 
lib/systemd/system/NetworkManager-wait-online.service]
  ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8
  Uname: Linux 5.4.0-1002-oem x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  Date: Wed Mar 25 12:43:13 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09
  IfupdownConfig: source /etc/network/interfaces.d/*.cfg
  InstallationDate: Installed on 2020-03-25 (0 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200316-08:40
  IpRoute:
   default via 192.168.101.1 dev eno1 proto static metric 100
   10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200
   169.254.0.0/16 dev eno1 scope link metric 1000
   192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 
100
  NetDevice.bonding_masters:
   Error: command ['udevadm', 'info', '--query=all', '--path', 
'/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device 
"/sys/class/net/bonding_masters": No such device

   X: INTERFACE_MAC=Error: command ['cat', 
'/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: 
/sys/class/net/bonding_masters/address: Not a directory
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL  AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE  FILENAME
   netplan-eno1  10838d80-caeb-349e-ba73-08ed16d4d666  ethernet  158577  
廿廿年三月廿五日 (週三) 十二時39分37秒  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes eno1activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  -- 
/run/NetworkManager/system-connections/netplan-eno1.nmconnection
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW   
WIFI  WWAN-HW  WWAN
   running  1.22.10  connected  starting  full  enabled disabled  
disabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1868915/+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 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

2020-03-31 Thread Owen

It's not just Minecraft, it's DropBox-2020 and BitDefender as well. I'm
sure there are others as well.

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Committed

Bug description:
  I just updated my machine, and when I did libpango1.0-0 was removed.
  This removed minecraft-launcher - the (very) popular launcher for
  Minecraft Java edition.

  I have reported this upstream, in case they can update their package
  https://bugs.mojang.com/browse/MCL-13512

  I am filing this bug so we can track it internally. I personally think
  this shouldn't have been done this late in the cycle, but there may
  well have been good reasons for it.

  As a result of the change though, it's now not possible to install
  Minecraft on Ubuntu 20.04.

  $ sudo apt install ./Minecraft\(1\).deb 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Note, selecting 'minecraft-launcher' instead of './Minecraft(1).deb'
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies.
   minecraft-launcher : Depends: libpango1.0-0 (>= 1.14.0) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1869716/+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 1863733] Re: Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later

https://launchpad.net/ubuntu/+source/bubblewrap/0.4.0-1ubuntu3

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

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

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

Title:
  Bubblewrap upstream-as-root test fails on libcap2 1:2.31-1 and later

Status in bubblewrap package in Ubuntu:
  Fix Released
Status in libcap2 package in Ubuntu:
  Invalid
Status in bubblewrap package in Debian:
  Fix Released

Bug description:
  The bubblewrap upstream-as-root test started failing after libcap2
  1:2.31-1 got synced from Debian. The same failure can be seen with
  1:2.32-1. I have reproduced the issue locally on focal - when using
  the focal-proposed version, the aforementioned test fails, where with
  the release version (1:2.27-1) it passes.

  It seems to fail here already:
  bwrap --bind / / --tmpfs /tmp --as-pid-1 --cap-drop CAP_KILL --cap-drop 
CAP_FOWNER --unshare-pid capsh --print
  assert_not_file_has_content caps.test '^Current: =.*cap_kill'

  It looks like the requested caps did not get dropped, as the logs show
  that both cap_kill and cap_fowner are still there. This is only for
  the upstream-as-root test, i.e. executing tests/test-run.sh as root.

  This might be an issue with bubblewrap, but seeing that it all works
  fine with the release version, it all feels weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bubblewrap/+bug/1863733/+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 1859754] Re: [SRU] add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

2020-03-31 Thread Martin Seener

I just see kernel 5.3.0-45-101 as a new kernel and in the changelog only
see "Bump ABI". Where can i see all changes and will it fix more of this
issue here or make it worse again?

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

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

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Invalid
Status in alsa-lib source package in Bionic:
  Fix Released
Status in alsa-lib source package in Eoan:
  Fix Released

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1859754/+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 1869819] Re: [SRU] System can't detect external headset in the codec of Conexant

2020-03-31 Thread Anthony Wong

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

** Also affects: pulseaudio (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

Title:
  [SRU] System can't detect external headset in the codec of Conexant

Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  New
Status in pulseaudio source package in Bionic:
  New
Status in pulseaudio source package in Focal:
  New

Bug description:
  [Impact]
  In some hp's devices, there are two audio jacks(one headset and one 
headphone) in the audio interface which is using the codec of Conexant, and 
apparently it's not working, the system can't detect the headset in current 
codec.

  [Test Case]
  1. Insert 3-ring headset into front audio port (headset icon)
  2. Check System Setting->Sound->Output

  [Expected result]
  Can detect external headset

  [Actual result]
  Only shows internal speaker.
  External headset microphone was detected.
  Another front audio port (earphone icon) works fine.

  [Regression Potential]
  Low.

  [Failure rate]
  100%

  [Additional information]
  system-product-name: HP EliteDesk 800 G5 SFF
  CPU: Intel(R) Core(TM) i7-9700 CPU @ 3.00GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:3e98] (rev 02)
  OS-version: 18.04
  kernel-version: 4.15.0-1065-oem
  pulseaudio-version: 1:11.1-1ubuntu7.2

  Upstream issue:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/272

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1869819/+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 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-03-31 Thread Pranav bhattarai

I am currently having this issue.
The issue = Login Loop.

Distro: Ubuntu 19.10

As a temporary solution, I am using Lightdm instead of default GDM3.
Is there anything that I can help, do let me know.

-- 
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:
  Confirmed
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: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[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-03-31 Thread Pranav bhattarai

Note: I don't even have any NVIDIA stuff.

-- 
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:
  Confirmed
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: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+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 1866923] Re: Wifi connection says it's connected but this is not true after the computer goes into a sleep status

Thank you for your bug report. according to the WifiSyslog.txt log and
the networkmanager one the wifi is connected. What isn't working
exactly?


** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Wifi connection says it's connected but this is not true after the
  computer goes into a sleep status

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  The wifi is connected and working correctly when powered on, however
  when I close the laptop lid, which I think puts it to sleep, and then
  reopen it, it says it's connected according to the icon but this is
  not true.

  A workaround is turning on Airplane mode and then switching it back on
  again. It then reconnects and is then fine again. Unless I close the
  lid and then the process repeats again.

  I guess this is to do with the wifi driver but I don't know what
  package it is so I just picked network-manager, sorry - I'm trying :)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager 1.20.4-2ubuntu2.2
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 10 19:29:03 2020
  InstallationDate: Installed on 2020-03-09 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.68.1 dev wlp1s0 proto dhcp metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.68.0/24 dev wlp1s0 proto kernel scope link src 192.168.68.18 metric 
600
  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.20.4   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/1866923/+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: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker

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

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

--
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:
[Dell Inspiron 7370] shows up in the sound output options but the
sound keeps being emitted from the internal laptop speaker

Status in PulseAudio:
New
Status in pulseaudio package in Ubuntu:
Confirmed

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:

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+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 1824088] Re: unattended upgrade ran one day after schedule