[Touch-packages] [Bug 2028023] Re: [jammy] DNS issue triggered by command "udevadm trigger --subsystem-nomatch=input"

[Rex Tsai]

I would add a command to collect the status of rsolvectl, to understand
what went wrong when the dns is not working.

% resolvectl status

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

Title:
  [jammy] DNS issue triggered by command "udevadm trigger --subsystem-
  nomatch=input"

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  [Summary]
  In jammy server image, when we use NetworkManager as netplan renderer, we may 
have DNS issue after executing command "udevadm trigger 
--subsystem-nomatch=input" as super user, the udevadm command may also be 
executed when we use "apt install XX" or "snap install XX".

  [Steps to reproduce]
  1. Login to a jammy server(jammy desktop environment works fine) image 
environment with Vagrant
  2. execute command "apt install network-manager"
  3. modify netplan config to use NetworkManager as renderer
  """
  # Let NetworkManager manage all devices on this system
  network:
    version: 2
    renderer: NetworkManager
  """
  4. reboot
  5. execute command "ping google.com" first to make sure DNS works fine
  6. execute command "udevadm trigger --subsystem-nomatch=input" as super user
  7. execute command "ping google.com" to check if DNS still works fine
  8. if DNS works fine, then repeat step 6-7, the fail rate is around 20-30%

  [Other info]
  I have tested the above mentioned steps for the following scenarios, which 
work fine without DNS issue
  1. Using focal server environment with Vagrant, there is no DNS issue
  2. Using jammy server environment with Vagrant which has DNS issue, then add 
the kinetic/kinetic-updates source list, install systemd(version: 
251.4-1ubuntu7.3) from kinetic, and there is no DNS issue

  If using focal server environment with Vagrant, then add the
  jammy/jammy-updates source list, install systemd(version:
  249.11-0ubuntu3.9) from jammy, then I will have DNS issue as well by
  following the steps mentioned in [Steps to reproduce]

  [Other info - Vagrantfile]
  The following content is for the Vagrantfile that I used to test
  """
  Vagrant.configure("2") do |config|
if Vagrant.has_plugin?("vagrant-timezone")
  config.timezone.value = :host
end
config.vm.define "test" do |test|
  test.vm.box = "ubuntu/jammy64"
  test.vm.provider "virtualbox" do |vb|
vb.name = "test2"
vb.memory = "4096"
vb.cpus = 4
config.disksize.size = "50GB"
  end
end
  end
  """

  [Fail rate]
  20-30%

  [Test script]
  The following is the script that I used to test. Ideally it should run forever
  """
  #!/bin/bash

  set -ex

  counter=1

  while true; do
   echo "$(date): test round ${counter}"
   counter=$((counter + 1))
   sudo udevadm trigger --subsystem-nomatch=input
   ping google.com -c 2
   sleep 0.5
  done
  """

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2028023/+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 2006517] Re: Bluetooth works on desktop but not on ubuntu core

[Rex Tsai]

- Dell Precision 5570[1] has the CNVi wireless module on an Alder Lake-S 
platform. The wireless module needs the correct firmware[2] for bluetooth to 
work. Based on Dilyn's comment #18[3], it's unclear if the firmware has been 
loaded on Core. Please check dmesg and see if it loads the 
intel/ibt-0040-0041.* firmwares.

- Plase include the following information in the following tests, which will 
help the team identify the root cause quicker
$ sudo grep '' /sys/class/dmi/id/product_* /sys/class/dmi/id/*_serial
$ sudo cat /etc/cpuinfo
$ snap info bluez && snap connections bluez # version of bluez (even
it's not been updated for a while, but we may not remember what it is
after a while)
$ snap info pc-kernel
$ sudo lspci -nn -vvv -k
$ sudo lsusb -vvv

[1] Dell Precision 5570 (RTX A2000 ) certified on Ubuntu 20.04 LTS -
https://ubuntu.com/certified/202112-29758/20.04%20LTS
[2] [Bug #1933938 “Missing CNVi firmware for Intel
AX211/AX201/9560/9...” : Bugs : linux-firmware package : Ubuntu -
https://bugs.launchpad.net/bugs/1933938
[3] https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/comments/18

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

Title:
  Bluetooth works on desktop but not on ubuntu core

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  We have built a snap that uses some bluetooth functionality.

  The snap runs well when using Ubuntu desktop 22.04 (all updates applied end 
of Jan 2022).
  We have tried using this same snap on Ubuntu Core 22 running on X86_64.

  On some hardware platforms (thinkpad E15 and x86 Mac) everything works as 
expected.
  We can install the snap on Jammy 22.04 or Core 22 on these platforms and get 
expected functionality regardless of OS.

  
  On our targeted platform (a Dell 5570) things are not working.  When running 
22.04 Jammy, everything works.  When running Core 22, some advanced bluetooth 
functionality is not available.
  Since the Core 22 image installs and runs on other X86_64 hardware we suspect 
a device driver issue.

  Attached are several files taken from the Dell 5570
  1) dmesg from Core 22.
  2) dmesg from Jammy 22.04
  3) output of lspci from Jammy 22.04
  4) Output of lsusb from Jammy 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+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 2006517] Re: Bluetooth works on desktop but not on ubuntu core

[Rex Tsai]

The title of the bug seems incorrect, the Bluetooth AdvertisementMonitor
does not work with bluetoohd from bluez 22/stable: 5.64-2 2022-05-03
with Ubuntu Core22 on Dell Precision 5570.

I would assume the rest of bluetooth functions and profile are still working, eg
% bluetoothctl show

If order to isolate the root cause is between kernel hci driver or bluetoothd. 
Could you please run the following commands on core to see if the hci driver 
works as expected? 
% sudo btmgmt version
% sudo btmgmt revision
% sudo btmgmt monitor.features
% sudo btmon --mgmt

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

Title:
  Bluetooth works on desktop but not on ubuntu core

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  We have built a snap that uses some bluetooth functionality.

  The snap runs well when using Ubuntu desktop 22.04 (all updates applied end 
of Jan 2022).
  We have tried using this same snap on Ubuntu Core 22 running on X86_64.

  On some hardware platforms (thinkpad E15 and x86 Mac) everything works as 
expected.
  We can install the snap on Jammy 22.04 or Core 22 on these platforms and get 
expected functionality regardless of OS.

  
  On our targeted platform (a Dell 5570) things are not working.  When running 
22.04 Jammy, everything works.  When running Core 22, some advanced bluetooth 
functionality is not available.
  Since the Core 22 image installs and runs on other X86_64 hardware we suspect 
a device driver issue.

  Attached are several files taken from the Dell 5570
  1) dmesg from Core 22.
  2) dmesg from Jammy 22.04
  3) output of lspci from Jammy 22.04
  4) Output of lsusb from Jammy 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+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 1994936] Re: initramfs need to mount efivarfs because kernel 6.0 deprecated 'efivars' sysfs interface

[Rex Tsai]

Canonical will need to carry this patch as a Ubuntu sauce for Jammy, in
order to support Intel VMD in 22.04 (jammy) with linux-oem 6.0+ kernel.

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

Title:
  initramfs need to mount efivarfs because kernel 6.0 deprecated
  'efivars' sysfs interface

Status in OEM Priority Project:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  New

Bug description:
  [ Impact ]

  kernel 6.0 deprecated efivars sysfs interface [1]. For Intel VROC
  RAID, mdadm needs initramfs to mount efivarfs instead.

  [1] The commit:
  commit 0f5b2c69a4cbe4166ca24b76d5ada98ed2867741
  Author: Ard Biesheuvel 
  Date: Mon Jun 20 13:34:03 2022 +0200

  efi: vars: Remove deprecated 'efivars' sysfs interface

  [ Test Plan ]

  1. Install initramfs-tools
  2. update-initramfs -u
  3. unmkinitramfs initrd.img-`uname -r` /tmp/extract-initramfs
  4. Check if boot script 00_mount_efivarfs exists in directory 
/tmp/extract-initramfs/main/scripts/init-top/
  5. Check /tmp/extract-initramfs/main/scripts/init-top/ORDER if the boot 
script 00_mount_efivarfs will be execute before udev.

  [ Where problems could occur ]

  Not sure if there any other tools/utilities also need to mount efivarfs as 
early as mdadm but the probability of file conflict should be very low.
  Also, there are no impact mounting efivarfs multiple times.
  mount: /sys/firmware/efi/efivars: efivarfs already mounted on 
/sys/firmware/efi/efivars.

  [ Scope ]

  Jammy, Kinetic

  [ Other Info ]

  The private bug link
  https://bugs.launchpad.net/somerville/+bug/1990231

  debian MR:
  https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/66

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994936/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Rex Tsai]

Hi, There are a few OEM platforms that also requires these memory
patches in grub2 on jammy, could we also port 2.06-2ubuntu16 back to
jammy?

** Tags added: originate-from-1998995

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Fix Committed
Status in grub2-unsigned package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Workaround]

  Some workarounds have been suggested in
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125

  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory region starvation in <1G
  addresses:

  Type   StartEnd  # Pages  Attributes
  Available  -00086FFF 0087 000F
  BS_Data00087000-00087FFF 0001 000F
  Available  00088000-0009EFFF 0017 000F
  Reserved   0009F000-0009 0001 000F
  Available  0010-00FF 0F00 000F
  LoaderCode 0100-01021FFF 0022 000F
  Available  01022000-238A7FFF 00022886 000F
  BS_Data238A8000-23927FFF 0080 000F
  Available  23928000-28860FFF 4F39 000F
  BS_Data28861000-2AB09FFF 22A9 000F
  LoaderCode 2AB0A000-2ACF8FFF 01EF 000F
  BS_Data2ACF9000-2B2FAFFF 0602 000F
  Available  2B2FB000-2B611FFF 0317 000F
  BS_Data2B612000-2B630FFF 001F 000F
  Available  2B631000-2B632FFF 0002 000F
  BS_Data2B633000-2B63CFFF 000A 000F
  Available  2B63D000-2B649FFF 000D 000F
  BS_Data2B64A000-2B64EFFF 0005 000F
  Available  2B64F000-2B666FFF 0018 000F
  BS_Data2B667000-2D8D5FFF 226F 000F
  LoaderCode 2D8D6000-2D8E9FFF 0014 000F
  BS_Data2D8EA000-2D925FFF 003C 000F
  LoaderCode 2D926000-2D932FFF 000D 000F
  BS_Data2D933000-2D969FFF 0037 000F
  BS_Code2D96A000-2D973FFF 000A 000F
  BS_Data2D974000-2E377FFF 0A04 000F
  Available  2E378000-2E37AFFF 0003 000F
  ...
  Reserved   3C08B000-4192 58A5 000F
  ACPI_NVS   4193-41B2 0200 000F
  ACPI_Recl  41B3-41BFEFFF 00CF 000F
  BS_Data41BFF000-41BF 0001 000F
  Available  0001-0002AB7F 001AB800 000F
  Reserved   000A-000F 0060 
  Reserved   

[Touch-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

[Rex Tsai]

@seb

Sorry, I did not see the modemmanager (1.20.0-1ubuntu1) in jammy-proposed, 
would you please confirm the process? 
 
% rmadison modemmanager
 modemmanager | 1.0.0-2ubuntu1| trusty   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el
 modemmanager | 1.0.0-2ubuntu1.1  | trusty-updates   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el
 modemmanager | 1.4.12-1ubuntu1   | xenial   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el, s390x
 modemmanager | 1.6.4-1ubuntu0.16.04.1| xenial-updates   | source, amd64, 
arm64, armhf, i386, powerpc, ppc64el, s390x
 modemmanager | 1.6.8-2ubuntu1| bionic   | source, amd64, 
arm64, armhf, i386, ppc64el, s390x
 modemmanager | 1.10.0-1~ubuntu18.04.2| bionic-updates   | source, amd64, 
arm64, armhf, i386, ppc64el, s390x
 modemmanager | 1.12.8-1  | focal| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.18.6-1~ubuntu20.04.1| focal-updates| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.18.6-1  | jammy| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.19~git20220905-0ubuntu2 | kinetic  | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.20.0-1~ubuntu22.10.1| kinetic-proposed | source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.20.0-1ubuntu1   | lunar| source, amd64, 
arm64, armhf, i386, ppc64el, riscv64, s390x


** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => Yao Wei (medicalwei)

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

Title:
  Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in modemmanager package in Ubuntu:
  Fix Released

Bug description:
  * Impact

  Fibocom FM350 modems aren't working with the current version of
  modemmanager in 22.04.

  * Test case

  - install modemmanager, libmbim, and libqmi from -proposed
  - reboot and try WWAN function to see if any regression there.
  - perform dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  The verification should be done on FM350 to ensure it's correctly
  handled but also on other hardware to verify that there are no
  regressions

  * Regression potential

  The SRU does an update to new modemmanager serie so we should do a
  complete round of testing on different hardware and confirm there are
  no regression.

  ---

  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
  Subsystem: Hewlett-Packard Company Device [103c:8914]

  https://lore.kernel.org/linux-
  wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/

  Modemmanager requires >= 1.19.1, the detail info is in
  lp:1962525

  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:

  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-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel 

[Touch-packages] [Bug 1994027] Re: Can't move window by drag and drop by using touch screen

[Rex Tsai]

** Changed in: oem-priority
   Importance: High => Critical

** Changed in: oem-priority
   Status: Triaged => Won't Fix

** Changed in: oem-priority
   Status: Won't Fix => Fix Committed

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

Title:
  Can't move window by drag and drop by using touch screen

Status in OEM Priority Project:
  Fix Committed
Status in XServer:
  Unknown
Status in xorg package in Ubuntu:
  New

Bug description:
  [Impact]
  Users using touch screen could not move windows with 'Drag-n-drop'.
  This SRU fixes the issue.

  [Test Plan]
  1. Install the 22.04
  2. Boot and login
  3. Open a folder or terminal
  4. Drag-n-drop the title bar of nautilus or terminal windows with finger touch
  5. Drag-n-drop the title bar of nautilus or terminal windows with the Wacom 
Pen

  Expected: Both finger touch and wacom pen work normally.

  Actual: Wacom Pen works normally, finger touch can not move the
  windows.

  [Where problems could occur]
  It's a regression of upstream packages, 
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/866

  It reverts f682e0563f736ed2c2c612ed575e05b6e3db945e.

  [Version]
  xserver-xorg-core 2:21.1.3-2ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1994027/+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 1994027] Re: Can't move window by drag and drop by using touch screen

[Rex Tsai]

** Changed in: oem-priority
   Importance: Undecided => High

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

Title:
  Can't move window by drag and drop by using touch screen

Status in Mutter:
  New
Status in OEM Priority Project:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  [Summary]
  For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed.

  [Steps to reproduce]
  1. Install the 22.04
  2. Boot and login
  3. Open a folder
  4. Drag-n-drop the folder with finger touch
  5. Drag-n-drop the folder with the Wacom Pen

  [Expected result]
  Both finger touch and wacom pen work normally.

  [Actual result]
  Wacom Pen works normally, finger touch can not move the folder.

  [Failure rate]
  100%

  [Checkbox job `com.canonical.certification::touchscreen/drag-n-drop`
  output]

  [Other Information]
  xorg  1:7.7+23ubuntu2
  mutter-common 42.2-0ubuntu1
  gnome-shell 42.4-0ubuntu0.22.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1994027/+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 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome

[Rex Tsai]

** Changed in: oem-priority
   Importance: Undecided => High

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

Title:
  When using Wayland, the onscreen keyboard does not open in text inputs
  for non-GTK applications such as Firefox or Chrome

Status in OEM Priority Project:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed

Bug description:
  When using wayland - onscreen keyboard not open in text inputs in many
  applications such as firefox or chrome.

  Ubuntu 18.04
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2015-06-09 (1455 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=cs_CZ.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-50-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1831039/+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 1965901] Re: SRU the new 1.18 serie to focal for hwe

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  SRU the new 1.18 serie to focal for hwe

Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  We want to update to the newer serie for better hardware support
  (support for Quectel EM120R-GL and EM160R-GL)

  [Test Plan]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Where problems could occur]

  The new version no longer automatically performs the FCC unlock
  procedure by default, see details on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/

  It means some modem will stop working out of the box.
  Users can manually install the unlock utility as described in the "FCC unlock 
procedures in ModemManager >= 1.18.4" section in the page above.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1965901/+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 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work
  after install Ubuntu Hirsute.

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  u@u-ThinkPad-L460:~$ uname -a
  Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 
20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  u@u-ThinkPad-L460:~$ cat /etc/issue
  Ubuntu 21.04 \n \l

  CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module

  [Steps]
  1. Make a Live CD for Ubuntu Hirsute
  2. Plug in the Live CD
  3. Boot ThinkPad L460
  4. Install Ubuntu Hirsute and completed all configurations
  5. Make sure the installation done
  6. Boot the system and log in
  7. Enable the proposed channel
  8. Do the update and upgrade
  9. Reboot the system and check mmcli is upgraded to 1.16.6
  7. Verify the WWAN working or not.

  [Actual result]
  The WWAN can not be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.16
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Wed Aug 18 01:32:17 2021
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 
   10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.30.0-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940377/+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 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Low

** Changed in: oem-priority
   Importance: Low => Wishlist

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

Title:
  The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work
  after install Ubuntu Hirsute.

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  u@u-ThinkPad-L460:~$ uname -a
  Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 
20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  u@u-ThinkPad-L460:~$ cat /etc/issue
  Ubuntu 21.04 \n \l

  CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module

  [Steps]
  1. Make a Live CD for Ubuntu Hirsute
  2. Plug in the Live CD
  3. Boot ThinkPad L460
  4. Install Ubuntu Hirsute and completed all configurations
  5. Make sure the installation done
  6. Boot the system and log in
  7. Enable the proposed channel
  8. Do the update and upgrade
  9. Reboot the system and check mmcli is upgraded to 1.16.6
  7. Verify the WWAN working or not.

  [Actual result]
  The WWAN can not be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.16
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Wed Aug 18 01:32:17 2021
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 
   10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.30.0-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940377/+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 1944409] Re: Systemd uses CPU after wakeup due to power_supply BAT0 (battery) continued polling

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Systemd uses CPU after wakeup due to power_supply BAT0 (battery)
  continued polling

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  My setup:
   - Dell Latitude 7520
   - Dell WD15 USB C docking station
   - Ubuntu 20.04.3
   - systemd 245.4-4ubuntu3.13
   - uname -a:
  Linux CLIFMI085 5.13.0-1012-oem #16-Ubuntu SMP Tue Sep 7 09:23:08 UTC 2021 
x86_64 x86_64 x86_64 GNU/Linux

  I leave my laptop docked and, after waking it up from sleep, the fans
  start blowing. After a quick inspection with top/htop, I always see
  /usr/lib/systemd/systemd-udev consuming 50+% of my CPU.

  After a quick search, I discover that I can use `udevadm monitor` to
  check what device is making all this fuss, and this is the output:

  UDEV  [92591.827159] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92591.873819] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92591.920022] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92591.967005] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92592.018200] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92592.068351] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92592.115100] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92592.166201] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92592.213318] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92592.261046] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92592.308824] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92592.356577] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92592.403766] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92592.451164] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)

  As you can see, the battery status is being polled every 0.05s. To fix
  this, I just need to restart the service with:

  sudo systemctl restart systemd-udevd systemd-udevd-kernel.socket
  systemd-udevd-control.socket

  Afterwards, this is the output of `udevadm monitor`:

  KERNEL[92739.612371] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92739.646888] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  KERNEL[92741.076823] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92741.099370] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  KERNEL[92742.539438] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)
  UDEV  [92742.573812] change   
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0 (power_supply)

  As you can see, the battery is now being polled every ~1.5s, which is
  fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1944409/+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 1930910] Re: Fix micmute hotkeys on HP ProBooks

[Rex Tsai]

OEM team need the patch in focal to meet the project schedule by 2021-07-09.

The upstream is not released yet.
% git tag --contains=a7161e0288d1
v249-rc1
v249-rc2

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

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+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 1926547] Re: Add Dell Privacy Mic Mute Key mapping

[Rex Tsai]

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1926547/+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 1925779] Re: [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] [Lenovo T14s-AMD] No sound at all when the audio output from HDMI port.

[Rex Tsai]

** Tags added: hwe-audio

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

Title:
  [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] [Lenovo T14s-AMD] No
  sound at all when the audio output from HDMI port.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound at all when the audio output from HDMI port.

  [Steps to reproduce]
  1. Install the daily build image on Lenovo T14s-AMD 
  2. Login the system
  3. Connect the HDMI port with a Monitor
  4. Select the 'Output Device' is HDMI
  5. Try to play sound from the monitor

  [Actual result]
  No sound at all when the audio output from HDMI port.
  The internal speaker works normally.

  [Test image]
  http://cdimage.ubuntu.com/ubuntu/daily-live/current/hirsute-desktop-amd64.iso

  [Test Device]
  https://certification.canonical.com/hardware/202006-27964

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  u  1424 F pulseaudio
   /dev/snd/controlC1:  u  1424 F pulseaudio
   /dev/snd/controlC0:  u  1424 F pulseaudio
   /dev/snd/pcmC0D0c:   u  1424 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 23 06:18:01 2021
  InstallationDate: Installed on 2021-04-23 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   LANG=en_US.UTF-8
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  u  1424 F pulseaudio
   /dev/snd/controlC1:  u  1424 F pulseaudio
   /dev/snd/controlC0:  u  1424 F pulseaudio
   /dev/snd/pcmC0D0c:   u  1424 F...m pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [20UHZ5DXUS, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/15/2020
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1CET55T(1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UHZ5DXUS
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1CET55T(1.24):bd09/15/2020:br1.24:efr1.24:svnLENOVO:pn20UHZ5DXUS:pvrThinkPadT14sGen1:rvnLENOVO:rn20UHZ5DXUS:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T14s Gen 1
  dmi.product.name: 20UHZ5DXUS
  dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1
  dmi.product.version: ThinkPad T14s Gen 1
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1925779/+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 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device

[Rex Tsai]

The upstream alia-lib has not yet accepted the patch[1].

Shengyao, Hui, please clarify all "Cmedia Audio" chip does not support
"Digital Output(S/PDIF)" as iec958 device.


[1] conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device by 
jason77-wang · Pull Request #122 · alsa-project/alsa-lib - 
https://github.com/alsa-project/alsa-lib/pull/122/commits/879d57d979b59be8632ba788d5f567f2b6ec0c19

Regards
-Rex

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

Title:
  [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-
  Audio.pcm.iec958_device

Status in OEM Priority Project:
  In Progress
Status in alsa-lib package in Ubuntu:
  In Progress
Status in alsa-lib source package in Focal:
  In Progress
Status in alsa-lib source package in Groovy:
  In Progress
Status in alsa-lib source package in Hirsute:
  In Progress

Bug description:
  [Impact]
  On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Where problems will occur]
  This fix limits to the Cmedia Audio only, other devices are unaffected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1921452/+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 1918855] Re: Xorg xserver got signal 6 to abort

[Rex Tsai]

** Changed in: oem-priority
   Importance: Undecided => High

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

Title:
  Xorg xserver got signal 6 to abort

Status in OEM Priority Project:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  I run checkbox job
  com.canonical.certification::memory/memory_stress_ng on focal, and the
  xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+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 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic

[Rex Tsai]

** Tags added: originate-from-1910630 sutton

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

Title:
  [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be
  selected automatically if there is no internal mic

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released
Status in pulseaudio source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the Dell AIO machines, there is no internal mic, after plugging a
  headset, users expect the headset-mic or headphone-mic could be selected
  automatically. But with the current rule, the headset-mic/headphone-mic will 
not be selected automatically and even users manually select them, they will 
not show up in the gnome sound setting, and users could not record sound by 
headset-mic/headphone-mic.

  [Fix]
  backport a patch from pulseaudio mergerequest, the patch is going to be
  merged to pulseaudio 14.1. This patch could be backported to hirsute without 
any change, but need to be changed if backport it to groovy and focal.

  [Test]
  With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a 
headset to the problematic Dell AIO machine will not automatically select 
headset-mic/headphone-mic, and they also do not show up in Gnome sound 
settings, leading to failure to record any sound.

  With the new proposed package, on those Dell AIO, plug a headset, open
  the gnome sound setting, the headset-mic is selected automatically,
  use the headset-mic to record the sound, the sound could be recorded
  and the sound quality is good.

  [Where problems could occur]
  This patch could change the policy of audio device switching, it will not
  affect all audio devices, but only the devices which has AVAIL_UNKNOWN 
available status, that means it has possibility to introduce the regression on 
headphone-mic ,headset-mic, internal mic and internal speaker's switching since 
they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, 
the input device will not switch to internal mic automatically or after unplug 
the headphone, the output device will not switch to internal speaker 
automatically. But this possibility is very low, we have tested the patch on 
many Dell and Lenovo machines, all worked well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1908167/+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 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack

[Rex Tsai]

** Tags added: oem-priority originate-from-1912136 sutton

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

Title:
  Lenovo P1G3 - unable to select system speakers when headset plugged
  into audio jack

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I suspect this is a pulseaudio or alsa bug.

  Our test team reported this:
  1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS .
  2. Boot system.
  3. Play audio or video file.
  4. Open Settings > Sound.
  5. Hot attach headset.
  6. Notice that headset is selected as output device in sound settings and 
sound can be heard from headset => EXPECTED
  7. While playback, select Internal Speaker as output device => KEYPOINT
  9. Notice:SUT havo no sound from Internal Speakers => PROBLEM

  I was able to confirm this - it seems with the headphones connected
  that I can't select the system speakers. If I don't have headphones
  connected I can switch between dock audio and system speakers
  correctly - so it's just related to the audio jack

  Thanks
  Mark

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1896098/+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 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack

[Rex Tsai]

** Tags added: hwe-audio

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

Title:
  Lenovo P1G3 - unable to select system speakers when headset plugged
  into audio jack

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  I suspect this is a pulseaudio or alsa bug.

  Our test team reported this:
  1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS .
  2. Boot system.
  3. Play audio or video file.
  4. Open Settings > Sound.
  5. Hot attach headset.
  6. Notice that headset is selected as output device in sound settings and 
sound can be heard from headset => EXPECTED
  7. While playback, select Internal Speaker as output device => KEYPOINT
  9. Notice:SUT havo no sound from Internal Speakers => PROBLEM

  I was able to confirm this - it seems with the headphones connected
  that I can't select the system speakers. If I don't have headphones
  connected I can switch between dock audio and system speakers
  correctly - so it's just related to the audio jack

  Thanks
  Mark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1896098/+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 1901000] Re: dmesg need permission after kernel 5.8

[Rex Tsai]

** Changed in: oem-priority
   Importance: Critical => Medium

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

Title:
  dmesg need permission after kernel 5.8

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Groovy:
  Confirmed

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1901000/+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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

[Rex Tsai]

Added upstream issue link in the description for referenc - platform:
add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status check (!597) ·
Merge Requests · NetworkManager / NetworkManager · GitLab -
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639


** Description changed:

  [Impact]
  
   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).
  
   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.
  
   The killer 500s Wi-Fi does not want the network-manger to manager the
  wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set. (The
  driver will manager itself.) When the network-manager managers the wake-
  on-LAN, all of the Wi-Fi functions will be lost after the OS resumed
  from suspend.
  
  [Test Case]
  
   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend
  
   After resume from suspend, the Wi-Fi function still is normal.
  
   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633
  
  [Regression Potential]
  
   * This patch modifies the wake on lan parameters, please test that the
  corresponding feature still works fine with the different configuration
  values.
  
-  1. Magic packet test:
-   Set Wake on Wireless to off
-   Send magic packet to the system
-   Ensure it does not wake up
+  1. Magic packet test:
+   Set Wake on Wireless to off
+   Send magic packet to the system
+   Ensure it does not wake up
  
-   Set Wake on Wirless to on
-   Send magic packet to the system
-   Ensure it does wake up
+   Set Wake on Wirless to on
+   Send magic packet to the system
+   Ensure it does wake up
  
-  2. Wi-Fi function test after resumed from suspend:
-   After resume from suspend, the Wi-Fi should work normally.
-   Scan APs.
-   Connect to an AP.
+  2. Wi-Fi function test after resumed from suspend:
+   After resume from suspend, the Wi-Fi should work normally.
+   Scan APs.
+   Connect to an AP.
  
  [Other Info]
  
-  * None
+  * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status
+ check (!597) · Merge Requests · NetworkManager / NetworkManager · GitLab
+ -
+ 
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/597#note_588639

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in OEM Priority Project focal series:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  In Progress

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

   The killer 500s Wi-Fi does not want the network-manger to manager the
  wake-on-LAN so the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set.
  (The driver will manager itself.) When the network-manager managers
  the wake-on-LAN, all of the Wi-Fi functions will be lost after the OS
  resumed from suspend.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi function still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * This patch modifies the wake on lan parameters, please test that
  the corresponding feature still works fine with the different
  configuration values.

   1. Magic packet test:
    Set Wake on Wireless to off
    Send magic packet to the system
    Ensure it does not wake up

    Set Wake on Wirless to on
    Send magic packet to the system
    Ensure it does wake up

   2. Wi-Fi function test after resumed from suspend:
    After resume from suspend, the Wi-Fi should work normally.
    Scan APs.
    Connect to an AP.

  [Other Info]

   * platform: add the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE status
  check (!597) · Merge Requests · NetworkManager / 

[Touch-packages] [Bug 1901000] Re: dmesg need permission after kernel 5.8

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  dmesg need permission after kernel 5.8

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  New

Bug description:
  apport used to collect dmesg well before kernel 5.8.
  But not it just show permission issue while collect dmesg so that apport not 
able to upload dmesg information for launchpad bugs after kernel 5.8.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu50
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  Uname: Linux 5.8.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports: 640:1001:125:66238:2020-10-15 18:43:14.784183502 
+0800:2020-10-15 18:43:15.784183502 
+0800:/var/crash/_usr_lib_ubuntu-release-upgrader_check-new-release-gtk.1001.crash
  Date: Thu Oct 22 18:54:46 2020
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 2157 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDmesg:
   Error: command ['pkexec', 'dmesg'] failed with exit code 127: 
polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  DistroRelease: Ubuntu 20.10
  InstallationDate: Installed on 2020-10-15 (7 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20201013.1)
  MachineType: Dell Inc. Precision 5550
  Package: linux-image-5.8.0-25-generic 5.8.0-25.26
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic 
root=UUID=8ca13cda-8130-47e0-a506-138e96e7d2ce ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
  RelatedPackageVersions:
   linux-restricted-modules-5.8.0-25-generic N/A
   linux-backports-modules-5.8.0-25-generic  N/A
   linux-firmware1.190
  Tags:  groovy
  Uname: Linux 5.8.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: sudo
  WifiSyslog:
   
  _MarkForUpload: True
  acpidump:
   Error: command ['pkexec', '/usr/share/apport/dump_acpi_tables.py'] failed 
with exit code 127: polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   Error executing command as another user: Not authorized
   
   This incident has been reported.
  dmi.bios.date: 06/01/2020
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0203K4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 7654321
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd06/01/2020:br1.2:svnDellInc.:pnPrecision5550:pvr:rvnDellInc.:rn0203K4:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5550
  dmi.product.sku: 097E
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1901000/+subscriptions

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

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

[Rex Tsai]

** Tags added: oem-priority originate-from-1896145 sutton

** Changed in: oem-priority
   Importance: Undecided => Low

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

Title:
  initramfs unpacking failed

Status in OEM Priority Project:
  New
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

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

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

  ---

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1835660/+subscriptions

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

[Touch-packages] [Bug 1892288] Re: Comet Lake PCH-H RAID not support on Ubuntu20.04

[Rex Tsai]

** Package changed: ubuntu-meta (Ubuntu) => linux (Ubuntu)

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

Title:
  Comet Lake PCH-H RAID not support on Ubuntu20.04

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  As Ubuntu 20.04 AHCI driver doesn’t include comet lake PCH-H RAID support
  { PCI_VDEVICE(INTEL, 0x06d6), board_ahci }, /* Comet Lake PCH-H RAID */

  If Thinkstation P340 configured as RAID mode, It can not find any RAID volume 
disk.
  please update such support. Thanks.

  Regards,
  Jiqi.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1892288/+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 1773897] Re: [regression] Logitech M337 mice are automatically disconnected after connected

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  [regression] Logitech M337 mice are automatically disconnected after
  connected

Status in Bluez Utilities:
  Confirmed
Status in OEM Priority Project:
  Incomplete
Status in bluez package in Ubuntu:
  Invalid

Bug description:
  The BT 3.0 mouse is disconnected automatically after connected with the 
notebook.
  The fail rate is around 9/10.

  1. The bug only occurs on the machine with intel 8265 module.
   I got three Dell XPS 13 (one is with Killer 1435, two are with intel 8265).
   This bug can not be reproduced on the machine with Killer 1435. 

  2. This bug can be reproduced since bluez 5.46.
   Using bluez 5.45, this bug can not be reproduced.

  
  Notebook: Dell XPS 13
  Wi-Fi/BT module: intel 8265, 8087:0a2b
  bluez: 5.48
  BT mouse: logitech M337
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-05-29 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 27c6:5385  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9370
  Package: bluez 5.48-0ubuntu3 [origin: unknown]
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=d6251f09-cbb5-4635-8f42-31e6c32f1c03 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.3.13
  dmi.board.name: 0173S1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.3.13:bd11/03/2017:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0173S1:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D4:25:8B:4F:7E:D6  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN 
RX bytes:61781 acl:382 sco:0 events:536 errors:0
TX bytes:7985 acl:69 sco:0 commands:168 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1773897/+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 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1871329/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  missing hardware/runtime info when reporing linux-firmware bugs via
  apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Invalid
Status in linux-firmware source package in Eoan:
  Invalid
Status in apport source package in Focal:
  Fix Released
Status in linux-firmware source package in Focal:
  Invalid

Bug description:
  Updated Description to match SRU requirements for bionic

  [Impact]
  linux-firmware doesn't install any package hooks for apport, so it will only 
carry some default items leaving hardware list, kernel messages unattached. 
Suggest symlink /usr/share/apport/package-hooks/source_linux-firmware.py to 
source_linux.py as other linux image debs do in bug 1847967.

  [Test Case]
  1) On an Ubuntu 18.04 LTS system run 'apport-cli linux-firmware'.
  2) Choose 'View report'
  3) Observe that 'ProcFB' is not collected

  With the version of apport from -proposed 'ProcFB' will be in the
  report.

  
  [Regression Potential]
  Very limited, as we are just adding a symlink from linux-firmware to the 
linux source package hook. this change has been available in Focal and Groovy 
without problem


  Original Description
  
  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 10 19:15:15 2020
  Dependencies:

  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  PackageArchitecture: allSourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Dependencies:

  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux-firmware
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic 
root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet 
splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 156.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1864813] Re: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once.

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  As there is not built-in speaker, and not any output, the dummy output
  in g-c-c will disappear after plug headset once.

Status in OEM Priority Project:
  New
Status in gnome-control-center package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  The dummy output in gnome-contol-center (g-c-c) will exists if

  - no built-in speaker
  - no headphone/earphone plugged
  - using display (like VGA, DVI) without audio out is plugged.

  However, in bionic, it will disappear as the headset is plugged and selected.
  After it disappears, a reboot won't make it appear again.

  bionic:
gnome-control-center: 1:3.28.2-0ubuntu0.18.04.6
pulseaudio: 1:11.1-1ubuntu7.4

  In Focal, dummy output won't disappear.

  focal:
    pulseaudio 1:13.0-3ubuntu2
    gnome-control-center 1:3.35.91-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1864813/+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 1690980] Re: unattended-upgrades does not block shutdown of system, as it is designed to

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  unattended-upgrades does not block shutdown of system, as it is
  designed to

Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project xenial series:
  Triaged
Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in apt source package in Zesty:
  Won't Fix
Status in unattended-upgrades source package in Zesty:
  Won't Fix

Bug description:
  Title: No pop-up window to warn users that system should not reboot or
  shutdown while installing security updates

  Summary:
  No pop-up window to warn users that system should not reboot or shutdown 
while installing security updates

  Steps:
  1. trigger unattended-upgrades
  2. reboot or shutdown system while installing packages

  Expected results: There is a pop-up window to warn users that system
  should not reboot or shutdown

  Actual results: There is no pop-up window to warn users

  Additional information:
  $ apt-cache policy unattended-upgrades
  unattended-upgrades:
    Installed: 0.90
    Candidate: 0.90ubuntu0.5
  $ lsb_release -rd
  Description:Ubuntu 16.04 LTS

  * APT SRU *
  [Impact]
  Stopping apt-daily-upgrade.service terminates dpkg and friends by sending the 
signals to all processes in the cgroup, and will send KILL quickly after.

  [Test case]
  Start apt-daily-upgrade.service and stop it while unattended-upgrades is 
running.

  The upgrade should run to completion or a safe exit point as long as
  it takes less than about 900s (which is the timeout for sending kill).

  [Regression potential]
  Leftover processes might remain in the apt-daily-upgrade cgroup if the 
postinst scripts or some apt hooks do something funny.

  Shutdown might take longer due to the 900 second timeout.

  * unattended-upgrades SRU

  [Impact]

   * Undattended-upgrades does not stop quickly gracefully when shutdown/reboot 
is initiated by the user.
   * The fix is performing the updates in minimal package sets and allow 
gracefully stopping between those steps when unattended-upgrades.service sends 
a TERM signal to running u-u. The signal is sent on receiving 
PrepareForShutdown() from logind 
(https://www.freedesktop.org/wiki/Software/systemd/inhibit/) to stop 
unattended-upgrades a bit earlier than the shutdown process starts (LP: 
#1803137).

  [Test Case]

  * Configure the system to have several 20+ packages upgradable by
  unattended-upgrades. One easy way of setting this up is starting with
  a system where packages from -security are installed but packages from
  -updates are not and enabling -updates in u-u:

# echo 'Unattended-Upgrade::Allowed-Origins::
  "${distro_id}:${distro_codename}-updates";' > /etc/apt/apt.conf.d
  /51unattended-upgrades-updates-too

  * Pre-download upgrades
# unattended-upgraded --download-only

  * Trigger unattended-upgrades run:
# service apt-daily-upgrade start

  * Shutdown the system from a graphical user session or by executing
# dbus-send --system --print-reply --dest=org.freedesktop.login1 
/org/freedesktop/login1 "org.freedesktop.login1.Manager.Reboot" boolean:false

   * Observe the system unattended-upgrades being gracefully stopped,
  checking /var/log/unattended-upgrades/unattended-upgrades.log. There
  should be packages left to be upgraded.

  [Regression Potential]

  On Xenial (with Unity) starting shutdown from the graphical session
  does not log the user out nor show any progress on the shutdown until
  the inhibition timer expires which is confusing. Users should be
  logged out on PrepareForShutdown() (LP: #1803581).

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1690980/+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 1647283] Re: WiFi being detected as ethernet when race condition on renaming for persistent name

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  WiFi being detected as ethernet when race condition on renaming for
  persistent name

Status in HWE Next:
  Fix Released
Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Confirmed
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  New

Bug description:
  [Impact]

   * It is a very bad user experience that the WiFi device is recognized
  as an Ethernet device making Ubuntu users unable to connect to WiFi
  network.

  [Test Case]

   * Find some laptop that can reduplicate this issue.
   * Keep rebooting the system until you see this issue.
   * Usually this issue can be reduplicated within 10 reboot cycles on the 
right laptop.

  [Regression Potential]

   * No trivial regression.

  [Other Info]
   
   * network-manager_1.2.6-0ubuntu0.16.04.2.debdiff (comment #8) is for xenial

  [Original Bug Description]

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

  Version: NetworkManager 1.4.2

  This bug happens after power-on with probability about 1/50.
  That means we need to reboot about 50 times to get into the buggy situation.
  "nmcli d" shows the device type is ethernet:

  DEVICE   TYPE  STATECONNECTION
  wlp1s0   ethernet  unavailable  --
  lo   loopback  unmanaged--

  The bug starts from a race condition. But it is not the root cause.
  I've also attach 2 logs. One is in good situation. Another is in bad 
situation.
  This log is generated by applying a "log patch" to network-manager 1.4.2 so 
we can see more stuff.

  In the bad situation. The bug starts with race condition. But the race 
condition is not the root cause. The race condition is:
   * During the renaming from "wlan0" to "wlp1s0". "wlan0" disappeared.
   * Inside the NM, it is still using "wlan0" in "_linktype_get_type()".
   * Since /sys/class/net/wlan0/uevent is disappeared. so the type matching 
failed in _linktype_get_type().
   * Also wifi_utils_is_wifi() failed to because /sys/class/net/wlan0 
disappeared.
   * And finally, devtype and kind are both NULL, so it returns 
NM_LINK_TYPE_ETHERNET for wlan0.

  Later, wlan0 is renamed to wlp1s0, and it seems to me that the Object inherit 
the type so it is still type ethernet.
  But from the log, I saw _linktype_get_type() is called several times later 
and return the correct type (wifi). But just, "nmcli d" still shows type 
ethernet.

  I'm wondering if we are missing to update the type in the Object
  created after renaming and re-detecting the type.

  fix need landing LP: #1645698

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1647283/+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 1889378] Re: dbus method 'Sleep' not work

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  dbus method 'Sleep' not work

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  refer to https://salsa.debian.org/utopia-team/network-
  
manager/-/blob/debian/master/introspection/org.freedesktop.NetworkManager.xml#L157

  
  
    
  

  But the network not be deactivated after the Sleep method be called.

  steps:
   1.$ gdbus call --system --dest org.freedesktop.NetworkManager --object-path 
/org/freedesktop/NetworkManager --method org.freedesktop.NetworkManager.Sleep 
true

   2.$ journal ctl ; # see the dbus method be called correctly.
  NetworkManager[843]:   [1596010870.8622] manager: sleep: sleep 
requested (sleeping: no  enabled: yes)
  NetworkManager[843]:   [1596010870.8626] device (p2p-dev-wlp0s20f3): 
state change: disconnected -> unmanaged (reason 'sleeping', sys-iface-state: 
'managed')
  NetworkManager[843]:   [1596010870.8632] manager: NetworkManager state 
is now ASLEEP
  NetworkManager[843]:   [1596010870.8635] audit: op="sleep-control" 
arg="on" pid=2825 uid=0 result="success"

  3. $ ping 8.8.8.8 ; # still work unexpectedly

  Note: this issue can be reproduced on the latest version of network-
  manager source : https://git.launchpad.net/network-
  manager/commit/?id=6e17a2e7ad9453c0afe34dab0e6768ad8ee447c2

  upstream bug:
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/503

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1889378/+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 1888352] Re: use builtin dump_acpi_tables.py in hookutils

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  use builtin dump_acpi_tables.py in hookutils

Status in Apport:
  New
Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  New
Status in apport source package in Groovy:
  New

Bug description:
  1. add apcidump to hookutils.py:attach_hardware and use the builtin 
dump_acpi_tables.py.
  2. remove explicit acpidump from oem-getlogs to use the builtin one.
  3. refine usage string in oem-getlogs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1888352/+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 1883670] Re: Disable IEC958 on HP Thunderbolt Dock

[Rex Tsai]

** Changed in: oem-priority
   Status: Confirmed => Fix Released

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

Title:
  Disable IEC958 on HP Thunderbolt Dock

Status in HWE Next:
  New
Status in OEM Priority Project:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On HP Thunderbolt Dock, unusable SPDIF can be selected as output from 
PulseAudio.

  [Fix]
  Disable IEC958 (SPDIF) through ALSA UCM.

  [Test]
  With the UCM applied, `pactl` and audio panel in gnome-control-center no 
longer have SPDIF option.

  [Regression Potential]
  Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883670/+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 1840416] Re: 2.4g wifi connection failed randomly during wpa re-key

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  2.4g wifi connection failed randomly during wpa re-key

Status in OEM Priority Project:
  Confirmed
Status in network-manager package in Ubuntu:
  New

Bug description:
  I'm not sure this issue caused by WIFI AP or WIFI module.
  From log, it looks the tested machine can not get new key from WIFI AP 
randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.1
  ProcVersionSignature: Ubuntu 4.15.0-1030.35-oem 4.15.18
  Uname: Linux 4.15.0-1030-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Aug 16 14:51:12 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+italia-whl+X37
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2019-08-14 (2 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  IpRoute:
   default via 10.101.46.1 dev wlp2s0 proto dhcp metric 600 
   10.101.46.0/24 dev wlp2s0 proto kernel scope link src 10.101.46.198 metric 
600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  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 
   Canonical-2.4GHz-g  f0a4469e-23e9-4899-a498-49a50b3a8e21  wifi  1565938016  
廿十九年八月十六日 (週五) 十四時46分56秒  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/5  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
Canonical-2.4GHz-g  f0a4469e-23e9-4899-a498-49a50b3a8e21  
/org/freedesktop/NetworkManager/ActiveConnection/5 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1840416/+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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

[Rex Tsai]

** Changed in: oem-priority
   Status: Confirmed => Fix Committed

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released
Status in pulseaudio source package in Disco:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  The network manager does not check the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  [Impact]

   In some cases, the wow is not configured and the
  NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE is set (for to disable
  management of wake-on-LAN in NetworkManager).

   The network manager only checks the NM_SETTING_WIRELESS_WAKE_ON_WLAN_NONE 
bit.
   But, the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE does not be check.
   So, the management of wake-on-LAN still is done by NetworkManager.

  [Test Case]

   On a machine with killer 500s Wi-Fi and install the Qualcomm's driver.
   Step 1. Enter suspend (s2idle)
   Setp 2. Resume from suspend

   After resume from suspend, the Wi-Fi functiall still is normal.

   You can download the kernel and linux-firmware that backport the Qucalcomm's 
dirver fro focal from below link:
   https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1879633

  [Regression Potential]

   * No potential regressions.

  [Other Info]
   
   * None

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

[Rex Tsai]

** Tags added: oem-priority

-- 
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:
  Invalid
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 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

[Rex Tsai]

Hi, Lukas and SRU taem

This one is blocking another SRU[1] for a certification platform.

If we would like land the #1887610 soon to meet the project schedule,
what would be the best approach to do this?

- Can we reduce the review time for this SRU, since it's verified?
- Or should we merge two SRU into one?

[1] https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1887610

** Changed in: oem-priority
 Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh)

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

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * On the Dell machines with multi function audio jack, the
     headphone/headset can't output sound automatically, which is different
     from ubuntu 18.04. The headphone/headset should be able to  output
     sound automatically after plugging in the audio jack.

  [Test Case]

   * On Tiger Lake platform
     Reproduce step:
     1. plug headphone/headset
     2. open g-c-c sound to check

     Expect result: The output device should switch to headphone or headset,
    since headphone's priority is higher in ucm2 config.
     Actual result: The output device is still internal speaker.

  [Regression Potential]

   * The change insert the ucm device by its priority, the potential
 regression is low, since if the change is not working properly, the 
 side effect is that the order of ucm devices are wrong, and it won't 
 switch to the correct output device as expect, but user can still
 config it manually.

  [Other]

   * This bug originates from an OEM private bug #1875597, then ubuntu users
     reported 2 public bugs #1871329 and #1881659. The 2nd issue of #1871329
     and the 1st issue of #1881659 have the same root cause as #1875597

   * The root cause is the ucm2 conf defines 2 input devices: the Mic2 and
     Headset MIC, and the pulseaudio parse the input device Headset MIC
     first then Mic2, finally the audio jack is set to Mic2 mode, this make
     the audio jack can't output sound anymore. To fix it, let the audio
     jack set to Headset MIC mode by default (Headset MIC has higher
     priority than Mic2 in the ucm2 conf), to do so, let pulseaudio send the
     device event to module-switch-on-port-available by the order of
     priority in the umc2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+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 1887610] Re: [SRU]There is no available audio entry in sound settings after execute suspend in 'Performance mode'

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => Shengyao Xue (xueshengyao)

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

Title:
  [SRU]There is no available audio entry in sound settings after execute
  suspend in 'Performance mode'

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Confirmed
Status in pulseaudio source package in Eoan:
  Won't Fix
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  On some I+N machines (inlcuding lenovo and dell machines), after
  setting the graphic mode to perofermance mode, and open the gnome
  sound seting, run suspend/resume test, the audio devices will
  disappear from UI, instead a dummy audio shows on the UI, and from
  then on, the audio can't work anymore.

  [Fix]
  The root cause is after resuming, the pulseaudio try to recover the
  PCM device, but at that moment, the devices nodes at /dev/snd/ are
  not accessible yet sometimes, it will make snd_pcm_open fail and
  the pulseaudio will calll unload_module to unload alsa audio card.
  I cherrpicked a fix from upstream, the fix adds retry and pa_msleep(),
  this will retry the snd_pcm_open() a couple of times if it fails.

  [Test Case]
  Install the pulseaudio wit this fix, set the graphic mode to
  performance mode, open the sound setting, then run suspend/resume 90
  times, after test check the audio devices on the UI, the speaker,
  digital mic are still on the UI, and they could work well.

  [Regression Risk]
  Low, this SRU just add retry and pa_msleep(), if the snd_pcm_open()
  doesn't fail, this patch will not introduce any change, if snd_pcm_open()
  fails, it just retry a couple of times, so it will not introduce the
  regression in theory.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1887610/+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 1883846] Re: hwdb: Mask rfkill event from intel-hid on HP platforms

[Rex Tsai]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
 Assignee: (unassigned) => hugh chao (hugh712)

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

Title:
  hwdb: Mask rfkill event from intel-hid on HP platforms

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  Press wireless hotkey on HP's latest generation laptops generate two rfkill 
events, prevent airplane mode from turning off.

  One event is from intel-hid and the other one is from hp-wireless.

  [Fix]
  Commit "hwdb: Mask rfkill event from intel-hid on HP platforms", to only use 
rfkill from hp-wireless.

  [Test]
  With the one-liner fix, press wireless hotkey only generate one rfkill event, 
hence airplane mode works as expected.

  [Regression Potential]
  Low, use hp-wireless over intel-hid is anticipated.

  any regression would likely result in missed rfkill events.

  [scope]

  this is fixed upstream by commit
  d8a9dd0dc17df77229d079afe29c05ae4a9e2ae9 which is not included in any
  version yet, so this is needed for f and g.

  @kaihengfeng is this needed on b and/or x as well?

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1883846/+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 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)

[Rex Tsai]

** Tags added: beaver-osp1-melisa

** Tags added: oem-priority

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

Title:
  Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8
  GT2)

Status in OEM Priority Project:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The system freezes frequently then logs out.
  If happens at apparently random times, and using no particular app.

  Extract of syslog is attached.

  Requested info is below:

  1) release
  Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30)

  2) package version
  gnome-session:
Installeret: (ingen)
Kandidat:3.28.1-0ubuntu3
Versionstabel:
   3.28.1-0ubuntu3 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
   3.28.1-0ubuntu2 500
  500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  3) Gnome shouldn't crash

  4) Gnome crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1878670/+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 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

[Rex Tsai]

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  This bug originates from an OEM private bug #1875597, then ubuntu
  users reported 2 public bugs #1871329 and #1881659. The 2nd issue of
  #1871329 and the 1st issue of #1881659 have the same root cause as
  #1875597

  [Impact]
  On the Dell machines with multi function audio jack, after installing the 
ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the 
headphone/headset can't output sound automatically after users plug in a 
headphone/headset. This is different from ubuntu 18.04, on the 18.04, the 
headphone/headset could output sound automatically after plugging in the audio 
jack.

  [Fix]
  The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset 
MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, 
finally the audio jack is set to Mic2 mode, this make the audio jack can't 
output sound anymore. To fix it, let the audio jack set to Headset MIC mode by 
default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, 
let pulseaudio send the device event to module-switch-on-port-available by the 
order of priority in the umc2.

  [Test Case]
  applying the fix patch to pulseaudio, plug a headset/headphone to the multi 
function audio jack, play sound from headset/headphone, the sound could be 
heard from headset/headphone.

  [Regression Risk]
  Low, just do a small change to store the ucm devices by their priority. and 
upstream just merged this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Support kernel 5.4 Intel sound driver on bionic

Status in OEM Priority Project:
  Fix Committed
Status in pulseaudio package in Ubuntu:
  Invalid
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * Some Intel platform bionic user audio function will be broken after
  upgrade to kernel 5.4

   * pulseaudio can't find working profile, since card name is changed
  in kernel 5.4

  [Test Case]

   * install kernel 5.4 and check audio function
     1. enable Pre-released updates in Developer Options
    Software & Updates > Developer Options > Pre-released updates 
(bionic-proposed)
     2. $ sudo apt update
     3. $ sudo apt install linux-generic-hwe-18.04-edge
     4. $ sudo reboot

   * install updated linux-firmware and pulseaudio
     $ sudo add-apt-repository ppa:kchsieh/training
     $ sudo apt-get update
     $ sudo apt install linux-firmware
     $ sudo apt install pulseaudio
     $ sudo reboot

   * test items
     1. check internal speaker/mic to playback and record audio
     2. plug headset and check headset functions
     3. plug HDMI from external monitor/TV, and check audio functions
     4. 1, 2, 3 works fine after resume from suspend

  [Regression Potential]

   * The updated pulseaudio breaks audio function on old kernel

  [Scope]

   * Need for bionic only

  [Bug Discussion]

   * https://bugs.launchpad.net/timbuktu/+bug/1880632
   * MP: 
https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610

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

[Rex Tsai]

** Changed in: oem-priority
   Status: Confirmed => Fix Committed

** Changed in: oem-priority
   Status: Fix Committed => Fix Released

-- 
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:
  Fix Released
Status in OEM Priority Project bionic series:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released

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

  Ubuntu-Focal-Source:
  
https://code.launchpad.net/~hugh712/ubuntu/+source/pulseaudio/+git/pulseaudio/+ref/focal-1869819

  PPA: https://launchpad.net/~hugh712/+archive/ubuntu/sru-1869819

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 1881094] Re: Support kernel 5.4 Intel sound driver on bionic

[Rex Tsai]

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  Support kernel 5.4 Intel sound driver on bionic

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Invalid
Status in pulseaudio source package in Bionic:
  New

Bug description:
  [Impact]

   * Some Intel platform bionic user audio function will be broken after
  upgrade to kernel 5.4

   * pulseaudio can't find working profile, since card name is changed
  in kernel 5.4

  [Test Case]

   * install kernel 5.4 and check audio function
 1. enable Pre-released updates in Developer Options
Software & Updates > Developer Options > Pre-released updates 
(bionic-proposed)
     2. $ sudo apt update
     3. $ sudo apt install linux-generic-hwe-18.04-wip
     4. $ sudo reboot

   * install updated linux-firmware and pulseaudio
     $ sudo add-apt-repository ppa:kchsieh/training
     $ sudo apt-get update
     $ sudo apt install linux-firmware
     $ sudo apt install pulseaudio
     $ sudo reboot

   * test items
     1. check internal speaker/mic to playback and record audio
     2. plug headset and check headset functions
     3. plug HDMI from external monitor/TV, and check audio functions
     4. 1, 2, 3 works fine after resume from suspend

  [Regression Potential]

   * The updated pulseaudio breaks audio function on old kernel

  [Scope]

   * Need for bionic only

  [Bug Discussion]

   * https://bugs.launchpad.net/timbuktu/+bug/1880632
   * MP: 
https://code.launchpad.net/~kchsieh/pulseaudio/+git/bionic-1880632/+merge/384610

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1881094/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport

[Rex Tsai]

** Changed in: oem-priority
   Importance: High => Medium

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

Title:
  missing hardware/runtime info when reporing linux-firmware bugs via
  apport

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-firmware source package in Bionic:
  Invalid
Status in linux-firmware source package in Eoan:
  Invalid
Status in apport source package in Focal:
  In Progress
Status in linux-firmware source package in Focal:
  Invalid

Bug description:
  linux-firmware doesn't install any package hooks for apport, so it
  will only carry some default items leaving hardware list, kernel
  messages unattached. Suggest symlink /usr/share/apport/package-hooks
  /source_linux-firmware.py to source_linux.py as other linux image debs
  do in bug 1847967.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 10 19:15:15 2020
  Dependencies:
   
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Dependencies:
   
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2019-09-28 (194 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  MachineType: Apple Inc. MacBookPro11,1
  NonfreeKernelModules: wl
  Package: linux-firmware
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic 
root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet 
splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-21-generic N/A
   linux-backports-modules-5.4.0-21-generic  N/A
   linux-firmware1.187
  Tags:  focal
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev 
sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 06/13/2019
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 156.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-189A3D4F975D5FFC
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro11,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-189A3D4F975D5FFC
  dmi.modalias: 
dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
  dmi.product.family: Mac
  dmi.product.name: MacBookPro11,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1510570] Re: Bluetooth LE pairing fail

[Rex Tsai]

** Changed in: oem-priority
   Status: Confirmed => Won't Fix

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

Title:
  Bluetooth LE pairing fail

Status in OEM Priority Project:
  Won't Fix
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Xenial:
  Won't Fix

Bug description:
  [Impact]

  When the Bluetooth adapter is not powered on it is not possible to use
  it in normal way. We used to have a hack to force powering on by using
  an udev rule but this doe snot work anymore. Luckily the BlueZ has
  introduced "AutoEnable" option that makes the stack power on adapters by
  itself.

  Backporting this to xenial will improve life of the desktop users and
  will not require them to hack the solution on their own. The fix itself
  uses the well known solution to this problem that is floating around
  there for a while.

  The upload fixes the bug by enabling the 'AutoEnable' option in the
  bluetoothd config file.

  [Original Report]

  . 15.10 we now have bluez 5 so we can pair BLE devices like the
  Microsoft Arc Touch Bluetooth Mouse.

  But this pairing doesn't work very well. Mouse is seen but pairing fail.
  More information: https://bugzilla.kernel.org/show_bug.cgi?id=104011#c5

  This is due to udev rule that use "hcitool" to power on device.
  Hopefully, bluez 5.35 has a new parameter "AutoEnable" who can be used
  instead of udev rules.

  here is a commit with this parameter:
  http://bazaar.launchpad.net/~guilhem-fr/bluez/autoenable/revision/138

  [Test Case]

  On xenial install from ppa:
  https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

  Now reboot the machine. The BT adapter shall be
  powered on.

  [Regression Potential]

  If things go wrong the adapter will not be powered on after the system
  boots up. Therefore while testing please focus on the adapter state,
  i.e. powered on or off.

  [Other Info]

  This fix is included in the development release, see:
  http://bazaar.launchpad.net/~bluetooth/bluez/ubuntu-zesty/revision/22

  [What to upload]

  For xenial as in:

  ) https://launchpad.net/~bluetooth/+archive/ubuntu/bluez
  ) 
https://launchpadlibrarian.net/347480725/bluez_5.37-0ubuntu5_5.37-0ubuntu5.2~build1.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1510570/+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 1781428] Re: please enable snap mediation support

[Rex Tsai]

Hi,

This SRU is blocking another pulseaudio SRU #1869819 [1] to support a
Conexant codec on HP EliteDesk 800 G5 SFF with Canonical/Ubuntu Desktop
certification.

1:11.1-1ubuntu7.5 for this bug is still in bionic-proposed, will we
finish the SRU for bionic by end of this month?

[1] Bug #1869819 “[SRU] System can't detect external headset in the ...”
: Bugs : OEM Priority Project - https://bugs.launchpad.net/bugs/1869819

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

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  IMPORTANT: if updating pulseaudio while the session is running, either
  need to reboot for the test or kill pulseaudio so it can restart with
  the new snap policy

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  $ exit # out of snap run --shell

  For strict snaps with pulseaudio:
  $ sudo snap install test-snapd-pulseaudio --edge
  $ sudo snap connect test-snapd-pulseaudio:pulseaudio

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connected which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes

  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes

  For strict snaps with audio-playback/audio-record:
  $ 

[Touch-packages] [Bug 1871329] Re: No "Select Audio Device" panel when plugging headphones, and no sound output to headphones

[Rex Tsai]

This is a known issue[1][2]. This will remain as a known limitation at
the moment - headphone would be recognized as headset, and no prompt to
users to overwrite it, and Intel is still working towards a long term
fix to it.

[1] https://github.com/thesofproject/linux/issues/956
[2] http://pad.lv/1829101

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

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
   Importance: Undecided => Medium

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

Title:
  No "Select Audio Device" panel when plugging headphones, and no sound
  output to headphones

Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:

  
  Summary
  ===

  Internal speakers work as expected, but when plugging headphones
  through the 3.5mm jack, the "Select Audio Device" panel doesn't show
  up (it normally shows up to allow user to select what kind of device
  has been plugged in, be it headphones, microphone or headset). In the
  Sound Settings, the Output Device automatically switches to
  "Headphones - sof-hda-dsp", but no sound can be heard even though the
  vumeter in the Sound Settings moves!

  Steps to reproduce
  ==

  1. Install focal beta
  2. Make sure the sound works as expected using the internal speakers and an 
audio file or Youtube
  3. Plug headphones in jack 3.5mm interface

  Expected Results
  

  - In Sound Settings, the headphones are automatically selected as output 
device
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound
  - Sound can be heard through the headphones

  
  Actual results
  ==

  - In Sound Settings, the headphones are automatically selected as output 
device (OK)
  - In Sound Settings, the vumeter under the Output Device moves according to 
the sound (OK)
  - No sound can be heard (Not OK)

  Attached are output of `pactl info` and `pactl list` before and after
  plugging headphones, while playing a tune on Bandcamp in Firefox.

  
  Additional Info
  ===

  Ubuntu: 20.04 beta image
  Certified device: 
  system-manufacturer: Dell Inc.
  system-product-name: Vostro 5590
  bios-version: 1.1.0
  CPU: Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz (8x)
  GPU: 00:02.0 VGA compatible controller [0300]: Intel Corporation Device 
[8086:9b41] (rev 02)
  01:00.0 3D controller [0302]: NVIDIA Corporation Device [10de:1d13] (rev a1)
  kernel-version: 5.4.0-21-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu24
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pieq   1768 F pulseaudio
   /dev/snd/pcmC0D0p:   pieq   1768 F...m pulseaudio
   /dev/snd/pcmC0D6c:   pieq   1768 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  7 16:33:27 2020
  InstallationDate: Installed on 2020-04-07 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd07/18/2019:svnDellInc.:pnVostro5590:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 5590
  dmi.product.sku: 095A
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1871329/+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 1855402] Re: [TGL] mesa support

[Rex Tsai]

** Tags added: tigerlake

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

Title:
  [TGL] mesa support

Status in intel:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  Description:

  this feature tracks the updates of mesa 3d for TGL support.

  We will update the commitid list as necessary

  Target Release: 20.04
  Target version: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1855402/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones

[Rex Tsai]

** Changed in: oem-priority
   Importance: Undecided => High

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

Title:
  oem kernel packages treated differently from generic kernel ones

Status in OEM Priority Project:
  New
Status in apport package in Ubuntu:
  New

Bug description:
  When `apport-bug linux` was executed on systems with linux-oem, linux-
  oem-osp1 kernels, many details are not included as generic linux
  kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1846692] Re: PCI/internal sound card not detected

[Rex Tsai]

** Changed in: alsa-driver (Ubuntu)
 Assignee: (unassigned) => Rex Tsai (chihchun)

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

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  As discussed with Rex Tsai

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  4 09:43:52 2019
  InstallationDate: Installed on 2019-09-23 (10 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/11/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET37W (1.20 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDCTO1WW
  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:bvrN2HET37W(1.20):bd09/11/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDCTO1WW
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846692/+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 1843381] Re: Dell system takes a long time to connect network with external dock

[Rex Tsai]

** Tags removed: id-5d84ab32951ae364f0c9f3b7
** Tags added: id-5d84ab32951ae364f0c9f3b7oem-priority

** Tags removed: id-5d84ab32951ae364f0c9f3b7oem-priority
** Tags added: id-5d84ab32951ae364f0c9f3b7 oem-priority

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

Title:
  Dell system takes a long time to connect network with external dock

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  This is a bug reopen from
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700
  The original one caused systemd regressed.
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651

  This issue needs an alternative solution.
  

  Dell has a feature called MAC addrss passthrough[1] that would force usb 
ethernet adapters to be assigned with a predefined MAC address stored in BIOS 
or so. This feature has been landed to mainline kernel in driver r8152[2]. So 
whenever a r8152 managed device is plugged into Dell devices with MAC addrss 
passthrough enabled, this driver will set NIC MAC to a predefined one.

  And some Dell devices have already one built-in r8152 NIC port. On
  these devices, when a second r8152 NIC is plugged in, a Debian
  originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev
  built-in command `net_id` to give a persistent name, and that will be
  based on MAC address. However, since the system has already
  initialized the built-in r8152 NIC with that name, renaming the second
  interface with this name will always fail.

  While Debian still carries a patch called "Revert-udev-network-device-
  renaming-immediately-give.patch"[4] that tries to keep support of
  already deprecated "75-persistent-net-generator.rules" based interface
  renaming mechanism, this patch also propagated into Ubuntu[5]. This
  patch will retry renaming with a 90 seconds timeout when the error
  code is -EEXIST, so the uevent processing will always be blocked in
  the last ifrename step in the victim system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules 
lib/udev/rules.d/50-udev-default.rules 
lib/udev/rules.d/73-special-net-names.rules 
lib/udev/rules.d/73-usb-net-by-mac.rules]
  ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18
  Uname: Linux 4.15.0-1043-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules
  Date: Wed Jul 24 15:30:59 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90
  InstallationDate: Installed on 2019-07-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 7424 Rugged Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed 
root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet 
splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0Y7FK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7424 Rugged Extreme
  dmi.sys.vendor: Dell Inc.

  [1]: 
https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c
  [3]: 
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules
  [4]: 
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch
  [5]: 
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1843381/+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 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

[Rex Tsai]

Is there anything we can do to speed up the process? What would be the
next step to land the reverted version for the regression?

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

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [Impact]

   * Many server users upgraded from previous Ubuntu LTS series, such as
  14.04 and 16.04, will be affected by this regression.

   * Because there is /etc/udev/rules/70-persistent-network.rules or
  /etc/udev/rules.d/70-persistent-net.rules generated by
  /lib/udev/write_net_rules left.

   * The previous SRU commit of LP: #1837700 doesn't cover this
  persistent network rule.

  [Test Case]

   * It needs to have two Ethernet devices and provides
  /etc/udev/rules.d/70-persistent-net.rules as below.

  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  [Regression Potential]

   * When users upgrade to next LTS 20.04, they may also encounter this
  issue because Debian has dropped the same patch.

   * We need to figure another way to avoid this regression for next LTS
  20.04.

   * Adding back the origial patch from Debian will casue another issue.
  (LP: #1837700)

  [Other Info]

  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+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 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

[Rex Tsai]

** Changed in: oem-priority
   Status: In Progress => Confirmed

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

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with 
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+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 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

[Rex Tsai]

** Changed in: oem-priority
   Status: New => In Progress

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

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with 
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+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 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

[Rex Tsai]

The user will have a 70-persistent-net.rules generated by
/lib/udev/write_net_rules, when they upgraded from 14.04/12.04 to newer
version. The server user may have the iptables rules or netowrk ip
setting based on the persistent interface name. This is critical.

The regression is introduced in 237-3ubuntu10.26.

If we don't have a quick solution to support both 70-persistent-
net.rules and same mac address.

We should quickly revert the changes back to the original version.

[1] 237-3ubuntu10.26 : systemd package : Ubuntu - 
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.26
[2] Bug #1837700 “Dell system takes a long time to connect network w...” : Bugs 
: systemd package : Ubuntu - https://bugs.launchpad.net/bugs/1837700

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

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with 
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+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 1842651] Re: Regression: after Uprade from udev_237-3ubuntu10.25 to udev_237-3ubuntu10.26 network interfaces don't get renamed by 70-persistent-network.rules

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  Regression: after Uprade from udev_237-3ubuntu10.25 to
  udev_237-3ubuntu10.26 network interfaces don't get renamed by 70
  -persistent-network.rules

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Since the latest update from udev_237-3ubuntu10.25 and
  systemd_237-3ubuntu10.25 to udev_237-3ubuntu10.26 and
  systemd_237-3ubuntu10.26 the renaming of network interfaces by
  /etc/udev/rules/70-persistent-network.rules does not work.

  /etc/udev/rules/70-persistent-network.rules:
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:55", 
NAME="eth0"
  SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:30:18:cb:5b:56", 
NAME="eth1"

  /var/log/syslog:
  systemd-udevd[423]: Error changing net interface name 'eth1' to 'eth0': File 
exists

  When I downgrade the packages to the version with 237-3ubuntu10.25 the 
following messages are in /var/log/syslog:
  Sep  4 13:10:09 brutus kernel: [4.518507] igb :04:00.0 rename2: 
renamed from eth0
  Sep  4 13:10:09 brutus kernel: [4.565081] igb :07:00.0 eth0: renamed 
from eth1

  The latest version does not rename the interfaces temporary if there
  is a conflict!

  Manually installing the old packages with 
  dpkg -i libacl1_2.2.52-3_amd64.deb libsystemd0_237-3ubuntu10.25_amd64.deb 
libudev1_237-3ubuntu10.25_amd64.deb systemd_237-3ubuntu10.25_amd64.deb 
systemd-sysv_237-3ubuntu10.25_amd64.deb udev_237-3ubuntu10.25_amd64.deb
  did fix the problem temporary.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1842651/+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 1837700] Re: Dell system takes a long time to connect network with external dock

[Rex Tsai]

** Changed in: systemd (Ubuntu Bionic)
 Assignee: You-Sheng Yang (vicamo) => Shih-Yuan Lee (fourdollars)

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

Title:
  Dell system takes a long time to connect network with external dock

Status in HWE Next:
  New
Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Disco:
  New

Bug description:
  update for SRU process:

  [Impact]
  1. On system featured mac passthrough, e.g., Dell/Lenovo laptop, or system 
occasionally install two USB ethernet with same MAC address, the system will 
suffer 90 seconds for network interface renaming mechanism before the last USB 
ethernet interface to activate.

  [Test Case]
  1. Install ubuntu on Dell laptop.
  2. Connect the Dell laptop with two Realtek 8153 USB ethernet dongle. Users 
can observe the last one will take 90 seconds for renaming to rename0.
  3. Users can also find that the two USB ethernet have the same MAC address.

  [Regression Potential] 
  To resolve the issue, drop a debian patch from systemd package. The debian 
patch is to revert an upstream commit to support 
75-persistent-net-generator.rules udev rule. Since the udev rule is deprecated, 
the regression potential should be relatively low.

  ---

  
  Dell has a feature called MAC addrss passthrough[1] that would force usb 
ethernet adapters to be assigned with a predefined MAC address stored in BIOS 
or so. This feature has been landed to mainline kernel in driver r8152[2]. So 
whenever a r8152 managed device is plugged into Dell devices with MAC addrss 
passthrough enabled, this driver will set NIC MAC to a predefined one.

  And some Dell devices have already one built-in r8152 NIC port. On
  these devices, when a second r8152 NIC is plugged in, a Debian
  originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev
  built-in command `net_id` to give a persistent name, and that will be
  based on MAC address. However, since the system has already
  initialized the built-in r8152 NIC with that name, renaming the second
  interface with this name will always fail.

  While Debian still carries a patch called "Revert-udev-network-device-
  renaming-immediately-give.patch"[4] that tries to keep support of
  already deprecated "75-persistent-net-generator.rules" based interface
  renaming mechanism, this patch also propagated into Ubuntu[5]. This
  patch will retry renaming with a 90 seconds timeout when the error
  code is -EEXIST, so the uevent processing will always be blocked in
  the last ifrename step in the victim system.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules 
lib/udev/rules.d/50-udev-default.rules 
lib/udev/rules.d/73-special-net-names.rules 
lib/udev/rules.d/73-usb-net-by-mac.rules]
  ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18
  Uname: Linux 4.15.0-1043-oem x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules
  Date: Wed Jul 24 15:30:59 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90
  InstallationDate: Installed on 2019-07-03 (20 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  MachineType: Dell Inc. Latitude 7424 Rugged Extreme
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed 
root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet 
splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0Y7FK3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: X03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7424 Rugged Extreme
  dmi.sys.vendor: Dell Inc.

  [1]: 
https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en
  [2]: 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c
  [3]: 
https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules
  [4]: 

[Touch-packages] [Bug 1724370] Re: NVME model does not show up

[Rex Tsai]

Thank you for taking the time to report this bug and helping to make Ubuntu 
better. Please execute the following command only once, as it will 
automatically gather debugging information, in a terminal:
apport-collect BUGNUMBER

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

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

** Changed in: gnome-disk-utility (Ubuntu)
   Status: Confirmed => 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/1724370

Title:
  NVME model does not show up

Status in gnome-disk-utility package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete
Status in udisks2 package in Ubuntu:
  Incomplete

Bug description:
  The Model field for NVME drives is blank. I believe this issue comes
  from udisks2, and then from udev.

  udisks2 has a function for getting the model which returns blank,
  udisks_drive_get_model

  udev has a parameter that should be returned for a disk if it has a
  model, ID_MODEL

  The Linux kernel exposes the true model in a sys file,
  /sys/block/nvme0n1/device/model

  This data should be displayed in GNOME Disks when available, but is
  not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1724370/+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 1837173] Re: shall allow local save even it's neither ubuntu nor native.

[Rex Tsai]

I think the Device enablement team can add a new apport "symptoms"
script to collect the debug messages of the OEM image, but not targeting
a meta package which is not exist on Ubuntu archive.

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

Title:
  shall allow local save even it's neither ubuntu nor native.

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Incomplete

Bug description:
  For command, apport-cli -p PKG -f --save=local-save.log, if the PKG is
  a local test one, it won't save the log.

  Let's skip package check if --save option is used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1837173/+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 1837174] Re: auto compress if save filename ends with .gz

[Rex Tsai]

Hi, Brian

In device enablement projects, the apport log file will be generated on
a fresh-installed machine or by a QA engineer works in a ODM factory
without direct internet access.

These users or use case are not able to submit the log file to a private
launchpad bug. They will share the log file in a usb pendrive or submit
the log using a helper scripts provided by device enablement team.

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

Title:
  auto compress if save filename ends with .gz

Status in OEM Priority Project:
  Confirmed
Status in apport package in Ubuntu:
  Incomplete

Bug description:
  email plain text file will be likely cause problem. gzip the save file
  could help lots of back and forth.

  Proposed to gzip the file if filename ends with ".gz".

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1837174/+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 1740894] Re: KEY_RFKILL is not passed to userspace

[Rex Tsai]

** Changed in: oem-priority/bionic
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

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

Title:
  KEY_RFKILL is not passed to userspace

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  New
Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xorgproto source package in Bionic:
  Fix Released
Status in libxkbcommon source package in Cosmic:
  Fix Released
Status in xkeyboard-config source package in Cosmic:
  Fix Released
Status in xorgproto source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace

[Rex Tsai]

** Tags added: oem-priority

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

Title:
  KEY_RFKILL is not passed to userspace

Status in OEM Priority Project:
  New
Status in OEM Priority Project bionic series:
  New
Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released
Status in xorgproto package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Released
Status in xkeyboard-config source package in Bionic:
  Fix Committed
Status in xorgproto source package in Bionic:
  Fix Released
Status in libxkbcommon source package in Cosmic:
  Fix Released
Status in xkeyboard-config source package in Cosmic:
  Fix Released
Status in xorgproto source package in Cosmic:
  Fix Released

Bug description:
  * Impact
  the airplane mode key doesn't work in GNOME

  * Test case
  Use a laptop with a key to activate airplane mode, it should toggle the 
corresponding mode on/off when used

  * Regression potential
  The change adds a new key definition but doesn't touch any existing one, 
nothing specific to test out of the new key working

  -

  There are a couple things going on, that could be fixed by a Debian or
  Ubuntu maintainer:

  - libxkbdcommon needs to be updated from 0.7.1 to 0.7.2. This
  introduces the RFKill key: https://lists.freedesktop.org/archives
  /wayland-devel/2017-August/034721.html

  - x11-proto needs a new release. This commit added RFKill, but it is
  not in a release:
  
https://cgit.freedesktop.org/xorg/proto/xproto/commit/?id=98a32d328e7195e12c38baa877917335bceffbaf

  - Likely other X11 packages need to be rebuilt.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1740894/+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 1825940] Re: [graphics] Enable ICL

[Rex Tsai]

** Tags added: icelake

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

Title:
  [graphics] Enable ICL

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  New
Status in mesa source package in Bionic:
  New

Bug description:
  [Impact]
  Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based 
on 18.04.3 graphics stack with linux-oem-osp1 kernel.

  
  [Test case]
  The usual desktop usage, graphics tests etc.

  
  [Regression potential]
  Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and 
it can't regress any currently running system.

  Mesa backports are limited to ICL, so they shouldn't regress earlier
  generations either.

  --

  Original description:

  ICL graphics is not enabled in 19.04.
  if you want to use 19.04 on ICL platform, you need do like this

  Add kernel option
  i915.alpha_support=1

  Target Release:19.10
  Target Kernel: 5.2
  Target Mesa: 19.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1825940/+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 1799364] Re: The wlan/bt hotkey doesn't work for all Dell Latitude and Precision computers

[Rex Tsai]

** Changed in: oem-priority
   Status: New => Fix Released

** Changed in: oem-priority/bionic
   Status: New => 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/1799364

Title:
  The wlan/bt hotkey doesn't work for all Dell Latitude and Precision
  computers

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project bionic series:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  Fix Released

Bug description:
  [Impact]

   * All Dell Latitude and Precision computer users can not use the
  wlan/bt hotkey.

  [Test Case]

   * Use any Dell Latitude and Precision computer to check the wlan/bt
  hotkey.

   * If you don't have the computer above, you can use the following
  command to check, and the expected output is "KEYBOARD_KEY_88=!wlan"
  instead of "KEYBOARD_KEY_88=!".

   `systemd-hwdb query
  
evdev:atkbd:dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  | grep KEYBOARD_KEY_88`

  [Regression Potential]

   * No regression

  [Other Info]

   * None

  Just install the official Ubuntu 18.10 on any Dell Latitude or
  Precision computer and press wlan/bt hotkey on the keyboard.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: systemd 239-7ubuntu10
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 23 15:37:41 2018
  InstallationDate: Installed on 2018-10-23 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp.
   Bus 001 Device 002: ID 0bda:5520 Realtek Semiconductor Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 3300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=be88d6f2-7d21-4a3c-b384-0c5356fb9220 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/05/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 0.0.24
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr0.0.24:bd10/05/2018:svnDellInc.:pnLatitude3300:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 3300
  dmi.product.sku: 08BB
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1799364/+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 1505475] Re: call mock emergency number like CMCC or China Unicom still display the not an emergency number message and can not get through

[Rex Tsai]

not sure why we need this fake emergency number, the requirement has
been implemented in http://pad.lv/593602

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

Title:
  call mock emergency number like CMCC or China Unicom still display the
  not an emergency number message and can not get through

Status in telephony-service package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New

Bug description:
  system-image-cli -i
  current build number: 136
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en
  last update: 2015-10-13 02:24:46
  version version: 136
  version ubuntu: 20151009
  version device: 20150818-0b38025
  version custom: 20150925-900-8-47

  reproduce steps:
  Step 1: SETUP
  Passed  Fail  Block  No Run
  1) Enable developer Mode on the device 
  2) Connect to PC 
  3) adb shell 
  4)mc-tool update ofono/ofono/account0 string:fakeEmergencyNumber=$NUMBER 
(where $NUMBER is another device you own) 
  5) mc-tool reconnect ofono/ofono/account0 
  6) Reboot 
  /!\ Device MUST HAVE A SIM CARD IN IT
  step2:Unlock sim if it is locked
  step3:Swipe to unlock the device
  step4:Tap on Emergency Call
  step5:Type in the $NUMBER you input in the mc-tool and hit the call button

  expect result:
  the mock emergency number which we set CMCC or China Unicom number can get 
through
  actual result:
  call the mock emergency number which we set CMCC or China Unicom unmber still 
display the not an emergency number and can not get through

  note:
  CMCC: 15801382817China Unicom:18612725801

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1505475/+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 1579303] Re: Please include ubuntu-keyboard-chinese-chewing as default

[Rex Tsai]

Change merged. 
* Merge into ubuntu-touch.yakkety : add-chinese-chewing : Code : Ubuntu Seeds - 
https://code.launchpad.net/~michael-sheldon/ubuntu-seeds/add-chinese-chewing/+merge/293631

** Package changed: ubuntu-touch-meta (Ubuntu) => ubuntu-meta (Ubuntu)

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please include ubuntu-keyboard-chinese-chewing as default

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  The feature has been landed[1], but not shipped as default. ubuntu-
  keyboard-chinese-chewing (Ubuntu on-screen keyboard data files -
  Chinese Chewing) provide input method for Traditional Chinese users,
  mainly for Taiwan.

  The package depends on other two packages - libchewing3 and
  libchewing3-data.

  [1] https://requests.ci-train.ubuntu.com/#/ticket/1224

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1579303/+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 1579303] [NEW] Please include ubuntu-keyboard-chinese-chewing as default

[Rex Tsai]

Public bug reported:

The feature has been landed[1], but not shipped as default. ubuntu-
keyboard-chinese-chewing (Ubuntu on-screen keyboard data files - Chinese
Chewing) provide input method for Traditional Chinese users, mainly for
Taiwan.

The package depends on other two packages - libchewing3 and
libchewing3-data.

[1] https://requests.ci-train.ubuntu.com/#/ticket/1224

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

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

Title:
  Please include ubuntu-keyboard-chinese-chewing as default

Status in ubuntu-touch-meta package in Ubuntu:
  New

Bug description:
  The feature has been landed[1], but not shipped as default. ubuntu-
  keyboard-chinese-chewing (Ubuntu on-screen keyboard data files -
  Chinese Chewing) provide input method for Traditional Chinese users,
  mainly for Taiwan.

  The package depends on other two packages - libchewing3 and
  libchewing3-data.

  [1] https://requests.ci-train.ubuntu.com/#/ticket/1224

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-touch-meta/+bug/1579303/+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 1566896] Re: Camera app and messaging app on mako no mic in video mode

[Rex Tsai]

FYI

* Fix audio recording for mako/flo - 
https://requests.ci-train.ubuntu.com/#/ticket/1228
* Landing PPA 061 : “CI Train PPA Service Team” team - 
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-061
* 
https://launchpadlibrarian.net/252130876/pulseaudio_1%3A6.0-0ubuntu9.24~test3_1%3A6.0-0ubuntu9.24.diff.gz

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

Title:
  Camera app and messaging app on mako no mic in video mode

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Flash OTA-10-RC image from rc channel to mako
  2. Open the camera app
  3. Accept access to camera
  4. Switch to video
  5. Tap record
  6. Accept Mic access
  7. Record something while talking into the mic for 10 seconds
  8. Playback the video

  EXPECTED:
  Audio to come from the speaker

  ACTUAL:
  I see the video footage but no audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1566896/+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 1566896] Re: Camera app and messaging app on mako no mic in video mode

[Rex Tsai]

In 1:6.0-0ubuntu9.12, the default audio source is hardcoded to AUDIO_SOURCE_MIC.
   546  /* Setting audio source to MIC by default */
   547  pa_snprintf(audio_source, sizeof(audio_source), "%s=%u", 
AUDIO_PARAMETER_STREAM_INPUT_SOURCE, AUDIO_SOURCE_MIC);
   548  u->stream->common.set_parameters(>stream->common, audio_source);
   549  pa_log_debug("Setting audio source to AUDIO_SOURCE_MIC by default");

In the newer 1:6.0-0ubuntu9.23 which introduced the regression on mako,
it use conversion_table_default_audio_source table to translate
AUDIO_DEVICE_IN_BUILTIN_MIC.

src/modules/droid/droid-util.c
207:for (unsigned int i = 0; i < 
sizeof(conversion_table_default_audio_source) / (sizeof(uint32_t) * 2); i++) {

But AUDIO_DEVICE_IN_BUILTIN_MIC is missing in droid-util-44.h.[1] Thanks
Simon Fels to find out the fix.

[1] https://paste.ubuntu.com/15669064/

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

Title:
  Camera app and messaging app on mako no mic in video mode

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Flash OTA-10-RC image from rc channel to mako
  2. Open the camera app
  3. Accept access to camera
  4. Switch to video
  5. Tap record
  6. Accept Mic access
  7. Record something while talking into the mic for 10 seconds
  8. Playback the video

  EXPECTED:
  Audio to come from the speaker

  ACTUAL:
  I see the video footage but no audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1566896/+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 1566896] Re: Camera app and messaging app on mako no mic in video mode

[Rex Tsai]

The issue can be verified on OTA-10-rc[1],

1) The recording functions are broken on both built-in mic and wired
headset. (switching audio routing seems fine.)

I found a few error message from logcat, while testing with parec. 
I/audio_hw_primary( 5603): select_devices: enter - uc_id 4
I/audio_hw_primary( 5603): select_devices: VOICE_CALL is active
E/audio_hw_primary( 5603): start_input_stream: cannot open device 
'/dev/snd/pcmC0D0c': Invalid argument
E/audio_hw_primary( 5603): disable_snd_device: Invalid sound device 0
D/audio_hw_primary( 5603): start_input_stream: exit: status(-5)

2) The other minor issue is pulseaudio module-trust-store.

The pulseaudio trust-store rejected to access, but the client seems
ignore that and requesting input stream. (which caused the error in
finding 1)

I: [pulseaudio] client.c: Created 8 "Native client (UNIX socket client)"
D: [pulseaudio] protocol-dbus.c: Interface org.PulseAudio.Core1.Client added 
for object /org/pulseaudio/core1/client8
D: [pulseaudio] protocol-native.c: Protocol version: remote 30, local 30
I: [pulseaudio] protocol-native.c: Got credentials: uid=32011 gid=32011 
success=1
D: [pulseaudio] protocol-native.c: SHM possible: yes
D: [pulseaudio] protocol-native.c: Negotiated SHM: no
D: [pulseaudio] protocol-native.c: Disabling srbchannel, reason: Must be 
enabled by module parameter
D: [pulseaudio] module-augment-properties.c: Looking for .desktop file for 
camera-app
I: [pulseaudio] module-trust-store.c: Client application name is: 
'qtubuntu-camera'
I: [pulseaudio] module-trust-store.c: Client apparmor profile is: 
'com.ubuntu.camera_camera_3.0.0.644'
D: [pulseaudio] module-trust-store.c: Checking permission to record for client 
8 (unknown) 
D: [pulseaudio] module-trust-store.c: Checking queue, size: 1, thread object: no
D: [pulseaudio] module-trust-store.c: Starting thread to ask about client 8 
(com.ubuntu.camera_camera_3.0.0.644)
I: [trust-store] module-trust-store.c: User needs to authorize the application..
D: Asking Ubuntu touch trust store for permission (app: 
com.ubuntu.camera_camera_3.0.0.644)
I: Request denied.
D: [pulseaudio] module-trust-store.c: Checking queue, size: 1, thread object: 
yes
D: [pulseaudio] module-trust-store.c: Letting client 8 
(com.ubuntu.camera_camera_3.0.0.644) know the result (rejected)
I: [pulseaudio] client.c: Freed 8 "qtubuntu-camera"
I: [pulseaudio] protocol-native.c: Connection died.

[1] OTA-10-rc
current build number: 25
device name: mako
channel: ubuntu-touch/rc/ubuntu
last update: 2016-04-07 13:16:14
version version: 25
version ubuntu: 20160401.1
version tag: OTA-10-rc
version device: 20160401.1
version custom: 20160401.1

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

Title:
  Camera app and messaging app on mako no mic in video mode

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  STEPS:
  1. Flash OTA-10-RC image from rc channel to mako
  2. Open the camera app
  3. Accept access to camera
  4. Switch to video
  5. Tap record
  6. Accept Mic access
  7. Record something while talking into the mic for 10 seconds
  8. Playback the video

  EXPECTED:
  Audio to come from the speaker

  ACTUAL:
  I see the video footage but no audio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1566896/+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 1427359] Re: ubuntu-device-flash fails to flash image once it reboots into recovery mode

[Rex Tsai]

The problem is the u-d-f (ubuntu-device-flash) could get access to "adb
shell" to deploy new images after it send "adb reboot recovery" to the
device.

It's because the production recovery image does not enable adb shell for
security reason. You have to pass a engineering version recovery to
reflash with ubuntu-device-flash.

You could find the engineering recovery image at

http://people.canonical.com/~jhm/barajas/recovery-krillin.img
http://people.canonical.com/~alextu/tangxi/recovery/recovery.img


** Changed in: android-tools (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  ubuntu-device-flash fails to flash image once it reboots into recovery
  mode

Status in android-tools package in Ubuntu:
  Invalid

Bug description:
  Running Ubuntu Trusty 14.04 and the latest packages from the android-
  tools PPA: https://launchpad.net/~phablet-team/+archive/ubuntu/tools

  1. Try to flash a krillin device via: ubuntu-device-flash touch 
--channel=ubuntu-touch/ubuntu-rtm/14.09
  2. Observe that at the time of this bug, RTM image 19 is downloaded and 
pushed to the phone successfully.
  3. u-d-f reboots the phone into recovery mode and you see the Ubuntu logo 
spinning.
  4. u-d-f complains that it failed to enter recovery after about 60 seconds.

  See the log output for more details. [1]

  
  [1] http://pastebin.ubuntu.com/10505648/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1427359/+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 1421623] Re: Welcome wizard claims GPS is less accurate than wifi based location

[Rex Tsai]

I believe "only wifi + cellular" is needed for user. Since that many
apps are not designed for "preserve battery" but for best performance,
which these apps will try to access to most accurate location
information anytime, which consumed battery from gps sensors.

That option is needed to allow a user put the phone into power-saving
mode.

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

Title:
  Welcome wizard claims GPS is less accurate than wifi based location

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  First boot welcome wizard in location sections claims GPS is less accurate 
than network based location service from HERE.
  While this can be theoretically true in some insane corner case, in normal 
life GPS is far more accurate.

  To help form correct text here are main differences.

  GPS - more accurate, but slow to acquire fix, does not work indoors,
  drains battery more, no need for internet connection, does not send
  any data out.

  Network based location - almost instant to get coarse location, works
  indoors, accuracy depends on network coverage in the area, more power
  efficient, requires internet connection. To get location data about
  visible GSM network and wifi networks needs to be send to 3rd party
  server.

  tested on krillin vivid-proposed r107

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+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 1421623] Re: Welcome wizard claims GPS is less accurate than wifi based location

[Rex Tsai]

+1 on Ondrej's comment.

The wizard UI imply that GPS is less accurate, which  is simply
misleading if the user has no knowledge on GPS fix. Even the user know
about GPS fix, there is no other UI indicate the phone has locked the
GPS.

To make sure setting more friendly, my suggestion is
O High accuracy (Using GPS, anonymized Wi-Fi and cellular network info)
O Power saving (Using anonymized Wi-Fi and cellular network info)
O Device only (Using only GPS, without sharing network info for privacy)
O Disable Location Service

Does it make sense to user, and explain a bit more why a user need to
make a choice ?

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

Title:
  Welcome wizard claims GPS is less accurate than wifi based location

Status in Canonical System Image:
  New
Status in Ubuntu UX:
  Invalid
Status in ubuntu-system-settings package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  First boot welcome wizard in location sections claims GPS is less accurate 
than network based location service from HERE.
  While this can be theoretically true in some insane corner case, in normal 
life GPS is far more accurate.

  To help form correct text here are main differences.

  GPS - more accurate, but slow to acquire fix, does not work indoors,
  drains battery more, no need for internet connection, does not send
  any data out.

  Network based location - almost instant to get coarse location, works
  indoors, accuracy depends on network coverage in the area, more power
  efficient, requires internet connection. To get location data about
  visible GSM network and wifi networks needs to be send to 3rd party
  server.

  tested on krillin vivid-proposed r107

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+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 1460895] Re: Alarm API is not working on vivid

[Rex Tsai]

In order to access to alarm api, the app need `calendar` policy group.

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

Title:
  Alarm API is not working on vivid

Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.Alarm/

  Test code: bzr branch lp:~liu-xiao-guo/debiantrial/alarm

  The test image:

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 208
  device name: mako
  channel: ubuntu-touch/devel-proposed/ubuntu
  last update: 2015-05-25 08:16:16
  version version: 208
  version ubuntu: 20150524
  version device: 20150210
  version custom: 20150524

  syslog on the phone:

  Jun  2 11:29:40 ubuntu-phablet dbus[1668]: apparmor=DENIED 
operation=dbus_method_call  bus=session 
path=/org/gnome/evolution/dataserver/SourceManager 
interface=org.freedesktop.DBus.ObjectManager member=GetManagedObjects 
mask=send name=:1.39 pid=6205 label=alarm.liu-xiao-guo_alarm_0.1 
peer_pid=2538 peer_label=unconfined
  Jun  2 11:48:26 ubuntu-phablet dbus[1668]: apparmor=DENIED 
operation=dbus_method_call  bus=session 
path=/org/gnome/evolution/dataserver/SourceManager 
interface=org.freedesktop.DBus.ObjectManager member=GetManagedObjects 
mask=send name=:1.39 pid=6928 label=alarm.liu-xiao-guo_alarm_0.1 
peer_pid=2538 peer_label=unconfined

  Is there any missing security policy for the API?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1460895/+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 1108064] Re: HUD messes up application's Alt key bindings

[Rex Tsai]

** Changed in: fcitx (Ubuntu)
   Status: Confirmed = Invalid

** Changed in: ibus (Ubuntu)
   Status: Confirmed = Invalid

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

Title:
  HUD messes up application's Alt key bindings

Status in Unity:
  New
Status in blender package in Ubuntu:
  Confirmed
Status in emacs23 package in Ubuntu:
  Confirmed
Status in fcitx package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Confirmed
Status in hud package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Invalid
Status in unity package in Ubuntu:
  New

Bug description:
  If Alt-key is assigned to HUD, Alt key doesn't work correctly in some
  applications.

  For example, Blender doesn't accept Alt key press at all.  See a bug
  report in Blender bug tracker for detail:

  http://projects.blender.org/tracker/?func=detailatid=498aid=33831group_id=9

  When pressing Alt key, Blender receives unnecessary FocusOut and
  FocusIn events, so Blender immediately forgets the Alt key is pressed
  down.  Blender developer was very angry with Unity's such strange
  behavior.

  In Emacs, after select a region, Alt key press sometimes cancels the
  selection unexpectedly, so I can do nothing in the region.

  
  Unity 6.12.0-0ubuntu0.2
  Ubuntu 12.10 amd64

To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1108064/+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 1462982] Re: Missing Chinese word rendering in title of qml Page render, when using GRID_UNIT_PX=23

[Rex Tsai]

** Attachment added: 50gu-23px-text.png
   
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411509/+files/50gu-23px-text.png

** Description changed:

  If switch GRID_UNIT_PX to 23 in arael, there will be one Chinese word in
  title missing randomly.
  
  The default was 40gu, and it works fine. But if switching to 50gu/23px,
  one of the 4 words in system-settings will be missed to render.
+ 
+ 
+ working -
+ 
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411501/+files/40gu-28px.png
+ broken -
+ 
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411503/+files/50gu-23px.png
+ 
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411504/+files/50gu-23px-2.png
+ 
+ another example in text scope
+ working
+ 
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411502/+files/40gu-28px-text.png
+ broken
+ 
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411509/+files/50gu-23px-text.png
  
  $ system-image-cli -i
  current build number: 4
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.zh
  last update: 2015-06-08 18:15:34
  version version: 4
  version ubuntu: 20150608
  version device: 20150522-a851049
  version custom: 20150602-730-6-1
  
  $ dpkg-query -W libqt5qml5 ubuntu-system-settings
  libqt5qml5:armhf  5.4.1-1ubuntu7
  ubuntu-system-settings0.3+15.04.20150514-0ubuntu1

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

Title:
  Missing Chinese word rendering in title of qml Page render, when using
  GRID_UNIT_PX=23

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  If switch GRID_UNIT_PX to 23 in arael, there will be one Chinese word
  in title missing randomly.

  The default was 40gu, and it works fine. But if switching to
  50gu/23px, one of the 4 words in system-settings will be missed to
  render.

  
  working -
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411501/+files/40gu-28px.png
  broken -
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411503/+files/50gu-23px.png
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411504/+files/50gu-23px-2.png

  another example in text scope
  working
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411502/+files/40gu-28px-text.png
  broken
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411509/+files/50gu-23px-text.png

  $ system-image-cli -i
  current build number: 4
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.zh
  last update: 2015-06-08 18:15:34
  version version: 4
  version ubuntu: 20150608
  version device: 20150522-a851049
  version custom: 20150602-730-6-1

  $ dpkg-query -W libqt5qml5 ubuntu-system-settings
  libqt5qml5:armhf  5.4.1-1ubuntu7
  ubuntu-system-settings0.3+15.04.20150514-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+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 1462982] Re: Missing Chinese word rendering in title of qml Page render, when using GRID_UNIT_PX=23

[Rex Tsai]

** Attachment added: 50gu-23px-2.png
   
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411504/+files/50gu-23px-2.png

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

Title:
  Missing Chinese word rendering in title of qml Page render, when using
  GRID_UNIT_PX=23

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  If switch GRID_UNIT_PX to 23 in arael, there will be one Chinese word
  in title missing randomly.

  The default was 40gu, and it works fine. But if switching to
  50gu/23px, one of the 4 words in system-settings will be missed to
  render.

  
  working -
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411501/+files/40gu-28px.png
  broken -
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411503/+files/50gu-23px.png
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411504/+files/50gu-23px-2.png

  another example in text scope
  working
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411502/+files/40gu-28px-text.png
  broken
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411509/+files/50gu-23px-text.png

  $ system-image-cli -i
  current build number: 4
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.zh
  last update: 2015-06-08 18:15:34
  version version: 4
  version ubuntu: 20150608
  version device: 20150522-a851049
  version custom: 20150602-730-6-1

  $ dpkg-query -W libqt5qml5 ubuntu-system-settings
  libqt5qml5:armhf  5.4.1-1ubuntu7
  ubuntu-system-settings0.3+15.04.20150514-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+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 1462982] Re: Missing Chinese word rendering in title of qml Page render, when using GRID_UNIT_PX=23

[Rex Tsai]

** Attachment added: 50gu-23px.png
   
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411503/+files/50gu-23px.png

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

Title:
  Missing Chinese word rendering in title of qml Page render, when using
  GRID_UNIT_PX=23

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  If switch GRID_UNIT_PX to 23 in arael, there will be one Chinese word
  in title missing randomly.

  The default was 40gu, and it works fine. But if switching to
  50gu/23px, one of the 4 words in system-settings will be missed to
  render.

  
  working -
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411501/+files/40gu-28px.png
  broken -
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411503/+files/50gu-23px.png
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411504/+files/50gu-23px-2.png

  another example in text scope
  working
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411502/+files/40gu-28px-text.png
  broken
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411509/+files/50gu-23px-text.png

  $ system-image-cli -i
  current build number: 4
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.zh
  last update: 2015-06-08 18:15:34
  version version: 4
  version ubuntu: 20150608
  version device: 20150522-a851049
  version custom: 20150602-730-6-1

  $ dpkg-query -W libqt5qml5 ubuntu-system-settings
  libqt5qml5:armhf  5.4.1-1ubuntu7
  ubuntu-system-settings0.3+15.04.20150514-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+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 1462982] Re: Missing Chinese word rendering in title of qml Page render, when using GRID_UNIT_PX=23

[Rex Tsai]

** Attachment added: 40gu-28px-text.png
   
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411502/+files/40gu-28px-text.png

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

Title:
  Missing Chinese word rendering in title of qml Page render, when using
  GRID_UNIT_PX=23

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  If switch GRID_UNIT_PX to 23 in arael, there will be one Chinese word
  in title missing randomly.

  The default was 40gu, and it works fine. But if switching to
  50gu/23px, one of the 4 words in system-settings will be missed to
  render.

  
  working -
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411501/+files/40gu-28px.png
  broken -
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411503/+files/50gu-23px.png
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411504/+files/50gu-23px-2.png

  another example in text scope
  working
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411502/+files/40gu-28px-text.png
  broken
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411509/+files/50gu-23px-text.png

  $ system-image-cli -i
  current build number: 4
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.zh
  last update: 2015-06-08 18:15:34
  version version: 4
  version ubuntu: 20150608
  version device: 20150522-a851049
  version custom: 20150602-730-6-1

  $ dpkg-query -W libqt5qml5 ubuntu-system-settings
  libqt5qml5:armhf  5.4.1-1ubuntu7
  ubuntu-system-settings0.3+15.04.20150514-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+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 1462982] [NEW] Missing Chinese word rendering in title of qml Page render, when using GRID_UNIT_PX=23

[Rex Tsai]

Public bug reported:

If switch GRID_UNIT_PX to 23 in arael, there will be one Chinese word in
title missing randomly.

The default was 40gu, and it works fine. But if switching to 50gu/23px,
one of the 4 words in system-settings will be missed to render.


working -
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411501/+files/40gu-28px.png
broken -
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411503/+files/50gu-23px.png
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411504/+files/50gu-23px-2.png

another example in text scope
working
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411502/+files/40gu-28px-text.png
broken
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411509/+files/50gu-23px-text.png

$ system-image-cli -i
current build number: 4
device name: arale
channel: ubuntu-touch/rc-proposed/meizu.zh
last update: 2015-06-08 18:15:34
version version: 4
version ubuntu: 20150608
version device: 20150522-a851049
version custom: 20150602-730-6-1

$ dpkg-query -W libqt5qml5 ubuntu-system-settings
libqt5qml5:armhf5.4.1-1ubuntu7
ubuntu-system-settings  0.3+15.04.20150514-0ubuntu1

** Affects: qtdeclarative-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Missing Chinese word rendering in title of qml Page render, when using
  GRID_UNIT_PX=23

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  If switch GRID_UNIT_PX to 23 in arael, there will be one Chinese word
  in title missing randomly.

  The default was 40gu, and it works fine. But if switching to
  50gu/23px, one of the 4 words in system-settings will be missed to
  render.

  
  working -
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411501/+files/40gu-28px.png
  broken -
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411503/+files/50gu-23px.png
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411504/+files/50gu-23px-2.png

  another example in text scope
  working
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411502/+files/40gu-28px-text.png
  broken
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411509/+files/50gu-23px-text.png

  $ system-image-cli -i
  current build number: 4
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.zh
  last update: 2015-06-08 18:15:34
  version version: 4
  version ubuntu: 20150608
  version device: 20150522-a851049
  version custom: 20150602-730-6-1

  $ dpkg-query -W libqt5qml5 ubuntu-system-settings
  libqt5qml5:armhf  5.4.1-1ubuntu7
  ubuntu-system-settings0.3+15.04.20150514-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+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 1462982] Re: Missing Chinese word rendering in title of qml Page render, when using GRID_UNIT_PX=23

[Rex Tsai]

** Attachment added: 40gu-28px.png
   
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411501/+files/40gu-28px.png

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

Title:
  Missing Chinese word rendering in title of qml Page render, when using
  GRID_UNIT_PX=23

Status in qtdeclarative-opensource-src package in Ubuntu:
  New

Bug description:
  If switch GRID_UNIT_PX to 23 in arael, there will be one Chinese word
  in title missing randomly.

  The default was 40gu, and it works fine. But if switching to
  50gu/23px, one of the 4 words in system-settings will be missed to
  render.

  
  working -
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411501/+files/40gu-28px.png
  broken -
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411503/+files/50gu-23px.png
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411504/+files/50gu-23px-2.png

  another example in text scope
  working
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411502/+files/40gu-28px-text.png
  broken
  
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+attachment/4411509/+files/50gu-23px-text.png

  $ system-image-cli -i
  current build number: 4
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.zh
  last update: 2015-06-08 18:15:34
  version version: 4
  version ubuntu: 20150608
  version device: 20150522-a851049
  version custom: 20150602-730-6-1

  $ dpkg-query -W libqt5qml5 ubuntu-system-settings
  libqt5qml5:armhf  5.4.1-1ubuntu7
  ubuntu-system-settings0.3+15.04.20150514-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1462982/+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 1451325] Re: Missing PDF reader support libs on Ubuntu phone system image

[Rex Tsai]

The developer should be able to include the library in their app, the
system image should only include library supported by the defined
software framework but not includes everything the developer needs. The
system image will be soon growing too large to distribute and manage.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New = Invalid

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

Title:
  Missing PDF reader support libs on Ubuntu phone system image

Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Currently, a developer is developing a PDF reader application on
  Ubuntu touch platform. However, the supported libraries like:

  libpoppler-dev - PDF rendering library -- development files

  is missing on our platform. A developer has to do a lot of things to
  make it happen on our platform. I would suggest adding the support
  into our Ubuntu phone platform since PDF reader is such an essential
  application.

  Thanks  best regards,
  XiaoGuo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1451325/+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 1268097] Re: [System settings] Can't set user-supplied ring tone

[Rex Tsai]

It only need the ubuntu-system-settings to look into user's folder.

I wonder would it be suitable to just  looks into ${XDG_MUSIC_DIR} or we
like to have ${XDG_MUSIC_DIR}/ringtone or ${XDG_MUSIC_DIR}/notification

XDG_MUSIC_DIR=/home/phablet/Music

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

Title:
  [System settings] Can't set user-supplied ring tone

Status in Ubuntu UX bugs:
  Triaged
Status in content-hub package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  AFAICS I can't set a custom ring tone without using a writable image.
  (http://askubuntu.com/questions/372759/ringtones-in-ubuntu-touch)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1268097/+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 742929] Re: libsqlite3-dev requesting wrong dependence

[Rex Tsai]

Thank you for reporting this bug to Ubuntu. maverick reached EOL on April 10, 
2012.
See this document for currently supported Ubuntu releases: 
https://wiki.ubuntu.com/Releases

I've tried recreating this bug with RELEASE and was unable to, given the
information you've provided. Please upgrade to the latest version and
re-test. If the bug is still reproducible, increase the verbosity of the
steps to recreate it so we can try again.

Do feel free to report any other bugs you may find.

** Changed in: sqlite3 (Ubuntu)
   Status: New = Incomplete

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

Title:
  libsqlite3-dev requesting wrong dependence

Status in sqlite3 package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: libsqlite3-dev

  When try to install libsqlite3-dev, it is requesting libsqlite3-0 
(3.7.2-1ubuntu0.1), but only (3.7.2-1) is available.
  To reproduce, open terminal and type:
  sudo apt-get install -d libsqlite3-dev
  The system will report:
  libsqlite3-dev : Depende: libsqlite3-0 (= 3.7.2-1) mas 3.7.2-1ubuntu0.1 está 
para ser instalado

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: libsqlite3-dev (not installed)
  ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
  Uname: Linux 2.6.35-28-generic i686
  Architecture: i386
  Date: Sat Mar 26 00:36:47 2011
  InstallationMedia: Ubuntu-Netbook 10.10 Maverick Meerkat - Release i386 
(20101007)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, user)
   LANG=pt_BR.utf8
   SHELL=/bin/bash
  SourcePackage: sqlite3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/742929/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.

[Rex Tsai]

Hi, Michal

The PES mainstream team identified that it has a higher probability
happend, if the user runing the emulator on a virtualzation disabled
machine.

The user does not even get the panel / welcome screen / greeter, the
whole screen of the emulator is blank. It comes back *sometimes* if
restart unity8 by

  $ kill -9 $(pidof unity8) $(pidof unity8-dash)

Here is my theory - When disabled virtualzation in emulator, the system
will be running very slow, and it's possible incrase odds for a race
condition of the unity8/unity8-dash.

Reference -
The developer need to have VT-X/AMD-V hardware for the emulator, and it need to 
be enabled from BIOS to have better
emulator performance.

The developer can check with the following command -
  # check if the hardware support virtualzation
  $ grep -e svm -e vmx /proc/cpuinfo
  # check if it's enabled from BIOS
  $ sudo apt-get install cpu-checker  kvm-ok

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

Title:
  unity8 display blank in emulator, host utopic, rtm-14.09 instance.

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  As run emulator, device screen is blank.

  Step to reproduce:

  1. install utopic.
  2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa
  3. sudo apt-get install ubuntu-sdk
  4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and 
chroot:click-ubuntu-sdk-14.10-i386
  5. create device instance i386 / rtm-14.09 and launch it.

  Expected result:
  See ubuntu phone UI there.

  Current result:
  Emulator screen is black.

  Extra Note:
  1. On the pc, in the first run of the instance, I can see phone interface on 
first boot after I kill -9 unity8 unity8-dash.
  But this work around failed as I stop the instance and run again. I even 
create the same instance with the other name
     and try this work around, still can't see anything on the screen.
  2. I can run test_glesv2 and see the result on the screen of the display 
correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1335007] Re: Can't use pinyin for Chinese in browser URL bar due to Qt.ImhUrlCharactersOnly

[Rex Tsai]

I agree to in order to support Internationalized domain name and search
function, the url bar need to accept  non-Latin characters.

Should this bug be fixed from the browser by removing
ImhUrlCharactersOnly hint?

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

Title:
  Can't use pinyin for Chinese in browser URL bar due to
  Qt.ImhUrlCharactersOnly

Status in Ubuntu Keyboard:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  With Chinese pinyin input method enabled, open the browser, tap the
  URL bar/ search bar, type n and i. You should see 你 as a word
  prediction. In fact no words show up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1335007/+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 1335002] Re: Chinese input method does not work after enable Chinese keyboard in Ubuntu Phone

[Rex Tsai]

The original bug has been fixed IIRC. I can not reprodudce it with
vivid-proposed (16,23).

XiaoGuo's suggestion is nice to have, it required improving the
suggestion algorithm in libpinyin4/ubuntu-keyboard-chinese-pinyin.

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

Title:
  Chinese input method does not work after enable Chinese keyboard in
  Ubuntu Phone

Status in Ubuntu Keyboard:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  Reproduce steps:

  1, enable Chinese keyboard in system settings
  2, launch an app can input text like notes
  3, long press global icon and switch Chinese

  Expecting:
  user can input Chinese like press 'n' and 'i' then 你 should show up on 
candidate bar

  Actual:
  no candidate bar, so still input English

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1335002/+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 1335007] Re: Can't use pinyin for Chinese in browser URL bar due to Qt.ImhUrlCharactersOnly

[Rex Tsai]

Is this a expected behavior ? Any input component with
ImhUrlCharactersOnly hint should not allowed to input Chinese.

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

Title:
  Can't use pinyin for Chinese in browser URL bar due to
  Qt.ImhUrlCharactersOnly

Status in Ubuntu Keyboard:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  With Chinese pinyin input method enabled, open the browser, tap the
  URL bar/ search bar, type n and i. You should see 你 as a word
  prediction. In fact no words show up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1335007/+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 1335002] Re: Chinese input method does not work after enable Chinese keyboard in Ubuntu Phone

[Rex Tsai]

After the user enter 'ni' as 你 at first time, 你 will be popup as first
suggestion when the user press 'n', which make sense to me.

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

Title:
  Chinese input method does not work after enable Chinese keyboard in
  Ubuntu Phone

Status in Ubuntu Keyboard:
  Confirmed
Status in “ubuntu-keyboard” package in Ubuntu:
  New
Status in “ubuntu-keyboard” package in Ubuntu RTM:
  New

Bug description:
  Reproduce steps:

  1, enable Chinese keyboard in system settings
  2, launch an app can input text like notes
  3, long press global icon and switch Chinese

  Expecting:
  user can input Chinese like press 'n' and 'i' then 你 should show up on 
candidate bar

  Actual:
  no candidate bar, so still input English

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1335002/+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 1390919] Re: Scope template cannot be running for devel emulator

[Rex Tsai]

Tested on emulator of ubuntu-touch/ubuntu-rtm/14.09 channel, it works
fine.

ubuntu=20141114,device=20141106.1,version=7
$ system-image-cli -i
current build number: 7
device name: generic_x86
channel: ubuntu-touch/ubuntu-rtm/14.09
last update: 2014-11-14 18:49:53
version version: 7
version ubuntu: 20141114
version device: 20141106.1

The build issue most likely happend in of development kit, please check
which development kit installed for the emulator. I tested and verified
it works with click-ubuntu-sdk-14.10-i386.

** Attachment added: 2014-11-17 19:12:15 的螢幕擷圖.png
   
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1390919/+attachment/4262265/+files/2014-11-17%2019%3A12%3A15%20%E7%9A%84%E8%9E%A2%E5%B9%95%E6%93%B7%E5%9C%96.png

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

Title:
  Scope  template cannot be running for devel emulator

Status in “click” package in Ubuntu:
  Confirmed

Bug description:
  Some libs are missing in the chroot, and the scope cannot be running
  for emulator (devel i386). Attached please find the captured screen.

  -- package 'process-cpp' not found
  -- package 'net-cpp=1.1.0' not found
  -- package 'net-cpp=1.1.0' not found

  

  -- The CXX compiler identification is GNU 4.9.1
  -- Check for working CXX compiler: /usr/bin/i686-linux-gnu-g++
  -- Check for working CXX compiler: /usr/bin/i686-linux-gnu-g++ -- works
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Found PkgConfig: /usr/bin/pkg-config (found version 0.28)
  -- Boost version: 1.55.0
  -- checking for modules 'libunity-scopes=0.6.0;net-cpp=1.1.0'
  --   package 'net-cpp=1.1.0' not found
  CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:283 (message):
A required package was not found
  Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:337 
(_pkg_check_modules_internal)
CMakeLists.txt:34 (pkg_check_modules)
  -- Found Gettext: /usr/bin/msgmerge (found version 0.19.2)
  -- Found XGettext: /usr/bin/xgettext (found version 0.19.2)
  CMake Error at cmake/FindGMock.cmake:6 (add_subdirectory):
add_subdirectory given source /usr/src/gmock which is not an existing
directory.
  Call Stack (most recent call first):
tests/CMakeLists.txt:3 (include)
  -- checking for module 'process-cpp'
  --   package 'process-cpp' not found
  -- Configuring incomplete, errors occurred!
  See also 
/home/liuxg/release/build-scopetest1-UbuntuSDK_for_i386_GCC_ubuntu_sdk_14_10_utopic-Default/CMakeFiles/CMakeOutput.log.
  CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:283 (message):
A required package was not found
  Call Stack (most recent call first):
/usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:337 
(_pkg_check_modules_internal)
tests/CMakeLists.txt:6 (pkg_check_modules)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1390919/+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 1362172] Re: [webapp-container] 2d context drawed to only first one canvas in one page

[Rex Tsai]

You should use Touch events not mouse events.

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

Title:
  [webapp-container] 2d context drawed to only first one canvas in one
  page

Status in “webbrowser-app” package in Ubuntu:
  Invalid

Bug description:
  If there is more then one canvas on same page[1],
  the 2d context can only draw to first canvas element.

  [1] https://github.com/chihchun/ubuntuwebapp-
  twocanvas/blob/master/www/index.html#L11

  Tested on
  current build number: 7
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-08-26 11:30:09
  version version: 7
  version ubuntu: 20140826
  version device: 20140811.1

  Package version
  qml-module-qtwebkit:armhf 5.3.0+dfsg-1ubuntu2
  qtdeclarative5-ubuntu-web-plugin:armhf0.23+14.10.20140819.1-0ubuntu1
  unity-webapps-qml 0.1+14.10.20140813-0ubuntu1
  webapp-container  0.23+14.10.20140819.1-0ubuntu1
  webbrowser-app0.23+14.10.20140819.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1362172/+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 1362172] Re: [webapp-container] 2d context drawed to only first one canvas in one page

[Rex Tsai]

The runtime did not response to every clicks if the user click quickly,
verified with my testing app[1] on  utopic-proposed build 234.

This should be filed in another new bug.

current build number: 234
device name: mako
channel: ubuntu-touch/utopic-proposed
last update: 2014-09-09 12:54:29
version version: 234
version ubuntu: 20140909
version device: 20140903.1
version custom: mako-0.3a

[1] https://github.com/chihchun/ubuntuphone-
sandbox/tree/master/html5/mouseon

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

Title:
  [webapp-container] 2d context drawed to only first one canvas in one
  page

Status in “webbrowser-app” package in Ubuntu:
  New

Bug description:
  If there is more then one canvas on same page[1],
  the 2d context can only draw to first canvas element.

  [1] https://github.com/chihchun/ubuntuwebapp-
  twocanvas/blob/master/www/index.html#L11

  Tested on
  current build number: 7
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-08-26 11:30:09
  version version: 7
  version ubuntu: 20140826
  version device: 20140811.1

  Package version
  qml-module-qtwebkit:armhf 5.3.0+dfsg-1ubuntu2
  qtdeclarative5-ubuntu-web-plugin:armhf0.23+14.10.20140819.1-0ubuntu1
  unity-webapps-qml 0.1+14.10.20140813-0ubuntu1
  webapp-container  0.23+14.10.20140819.1-0ubuntu1
  webbrowser-app0.23+14.10.20140819.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1362172/+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 1362172] Re: [webapp-container] 2d context drawed to only first one canvas in one page

[Rex Tsai]

If you use touch event[1][2], it works[3] as expected.

[1] Touch Events http://www.w3.org/TR/touch-events/
[2] Safari Web Content Guide: Handling Events 
https://developer.apple.com/library/safari/documentation/AppleApplications/Reference/SafariWebContent/HandlingEvents/HandlingEvents.html
[3] https://github.com/chihchun/ubuntuphone-sandbox/tree/master/html5/touchevent

** Changed in: webbrowser-app (Ubuntu)
   Status: New = Invalid

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

Title:
  [webapp-container] 2d context drawed to only first one canvas in one
  page

Status in “webbrowser-app” package in Ubuntu:
  Invalid

Bug description:
  If there is more then one canvas on same page[1],
  the 2d context can only draw to first canvas element.

  [1] https://github.com/chihchun/ubuntuwebapp-
  twocanvas/blob/master/www/index.html#L11

  Tested on
  current build number: 7
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-08-26 11:30:09
  version version: 7
  version ubuntu: 20140826
  version device: 20140811.1

  Package version
  qml-module-qtwebkit:armhf 5.3.0+dfsg-1ubuntu2
  qtdeclarative5-ubuntu-web-plugin:armhf0.23+14.10.20140819.1-0ubuntu1
  unity-webapps-qml 0.1+14.10.20140813-0ubuntu1
  webapp-container  0.23+14.10.20140819.1-0ubuntu1
  webbrowser-app0.23+14.10.20140819.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1362172/+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 1362172] Re: [webapp-container] 2d context drawed to only first one canvas in one page

[Rex Tsai]

** Attachment added: selct canvas 2 from web inspector.
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1362172/+attachment/4188296/+files/20140827210533.png

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

Title:
  [webapp-container] 2d context drawed to only first one canvas in one
  page

Status in “webbrowser-app” package in Ubuntu:
  New

Bug description:
  If there is more then one canvas on same page[1],
  the 2d context can only draw to first canvas element.

  [1] https://github.com/chihchun/ubuntuwebapp-
  twocanvas/blob/master/www/index.html#L11

  Tested on
  current build number: 7
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-08-26 11:30:09
  version version: 7
  version ubuntu: 20140826
  version device: 20140811.1

  Package version
  qml-module-qtwebkit:armhf 5.3.0+dfsg-1ubuntu2
  qtdeclarative5-ubuntu-web-plugin:armhf0.23+14.10.20140819.1-0ubuntu1
  unity-webapps-qml 0.1+14.10.20140813-0ubuntu1
  webapp-container  0.23+14.10.20140819.1-0ubuntu1
  webbrowser-app0.23+14.10.20140819.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1362172/+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 1362172] Re: [webapp-container] 2d context drawed to only first one canvas in one page

[Rex Tsai]

** Attachment added: com.ubuntu.developer.chihchun.canvas_0.1_all.click
   
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1362172/+attachment/4188291/+files/com.ubuntu.developer.chihchun.canvas_0.1_all.click

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

Title:
  [webapp-container] 2d context drawed to only first one canvas in one
  page

Status in “webbrowser-app” package in Ubuntu:
  New

Bug description:
  If there is more then one canvas on same page[1],
  the 2d context can only draw to first canvas element.

  [1] https://github.com/chihchun/ubuntuwebapp-
  twocanvas/blob/master/www/index.html#L11

  Tested on
  current build number: 7
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-08-26 11:30:09
  version version: 7
  version ubuntu: 20140826
  version device: 20140811.1

  Package version
  qml-module-qtwebkit:armhf 5.3.0+dfsg-1ubuntu2
  qtdeclarative5-ubuntu-web-plugin:armhf0.23+14.10.20140819.1-0ubuntu1
  unity-webapps-qml 0.1+14.10.20140813-0ubuntu1
  webapp-container  0.23+14.10.20140819.1-0ubuntu1
  webbrowser-app0.23+14.10.20140819.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1362172/+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 1362172] [NEW] [webapp-container] 2d context drawed to only first one canvas in one page

[Rex Tsai]

Public bug reported:

If there is more then one canvas on same page[1],
the 2d context can only draw to first canvas element.

[1] https://github.com/chihchun/ubuntuwebapp-
twocanvas/blob/master/www/index.html#L11

Tested on
current build number: 7
device name: mako
channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
last update: 2014-08-26 11:30:09
version version: 7
version ubuntu: 20140826
version device: 20140811.1

Package version
qml-module-qtwebkit:armhf   5.3.0+dfsg-1ubuntu2
qtdeclarative5-ubuntu-web-plugin:armhf  0.23+14.10.20140819.1-0ubuntu1
unity-webapps-qml   0.1+14.10.20140813-0ubuntu1
webapp-container0.23+14.10.20140819.1-0ubuntu1
webbrowser-app  0.23+14.10.20140819.1-0ubuntu1

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: 20140827200436.png
   
https://bugs.launchpad.net/bugs/1362172/+attachment/4188290/+files/20140827200436.png

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

Title:
  [webapp-container] 2d context drawed to only first one canvas in one
  page

Status in “webbrowser-app” package in Ubuntu:
  New

Bug description:
  If there is more then one canvas on same page[1],
  the 2d context can only draw to first canvas element.

  [1] https://github.com/chihchun/ubuntuwebapp-
  twocanvas/blob/master/www/index.html#L11

  Tested on
  current build number: 7
  device name: mako
  channel: ubuntu-touch/ubuntu-rtm/14.09-proposed
  last update: 2014-08-26 11:30:09
  version version: 7
  version ubuntu: 20140826
  version device: 20140811.1

  Package version
  qml-module-qtwebkit:armhf 5.3.0+dfsg-1ubuntu2
  qtdeclarative5-ubuntu-web-plugin:armhf0.23+14.10.20140819.1-0ubuntu1
  unity-webapps-qml 0.1+14.10.20140813-0ubuntu1
  webapp-container  0.23+14.10.20140819.1-0ubuntu1
  webbrowser-app0.23+14.10.20140819.1-0ubuntu1

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