[Touch-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-08-25 Thread Christian Ehrhardt 
https://launchpad.net/ubuntu/+source/systemd/246.2-1ubuntu1 is still in
proposed and I was looking forward to a bunch of custom triggers this
morning.

But I found everything migrated this morning despite those new tests not being 
done.
https://autopkgtest.ubuntu.com/packages/s/systemd/groovy/amd64

Since the bug had no update about it I checked and found:
http://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/4957

Thanks rbalint - this certainly unblocks things for now.
Anything coming later should test against the new systemd version and then 
hopefully work.
Due to that I think we can set the formerly affected extra tasks to invalid 
(since they were only here for tracking of the update-excuses tag).

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

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

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

** Changed in: glib2.0 (Ubuntu)
   Status: Confirmed => Invalid

** Also affects: build-essential (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: build-essential (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: build-essential (Ubuntu)
   Status: New => Invalid

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

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

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

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in build-essential source package in Focal:
  Confirmed
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  New

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 

[Touch-packages] [Bug 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-08-25 Thread Christian Ehrhardt 
What is left is the similar situation in Focal (as mentioned before).
I have updated the tasks to reflect that properly and get update-excuse tagging 
there.

In Focal it is currently blocking qemu and build-essential SRUs and I
wanted to ask if the plan is to do the same upload+test-reset there or
anything else.

@ddstreet - rbalint said you are prepping the systemd SRUs, could you
let us know what is the plan there?

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in build-essential package in Ubuntu:
  Invalid
Status in glib2.0 package in Ubuntu:
  Invalid
Status in iputils package in Ubuntu:
  Invalid
Status in kbd package in Ubuntu:
  Invalid
Status in ntpsec package in Ubuntu:
  Invalid
Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in build-essential source package in Focal:
  Confirmed
Status in qemu source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  New

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 
F.B...FFF.FF..F..F.FFF.F
  logind (F  2% S  0% B  2% => P 95%/) 
..B...F.
  upstream   (F 22% S  0% B  2% => P 75%/) 
...F.FB.F.F.F..FFF.F
  root-unittests (F 12% S  0% B  2% => P 85%/) 
..B.F...F.FF...F

  (I'm sure LP will make this unreadable, but is is nice in monospace)

  Whatever the root cause is - the success rate of these has reduced so
  much that the (even formerly questionable) practice of retry-until-
  success won't work anymore.

  
  I have run the two tests in a local VM and systemd-fsckd works there while 
tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services".

  We had the discussion in the past, but I think I need to again bring
  up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until
  they are on reasonable success rates.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1892979] Re: Sizing issue on Startup

2020-08-25 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1892521 ***
https://bugs.launchpad.net/bugs/1892521

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


** This bug has been marked a duplicate of bug 1892521
   UI bug - system fonts enlarge after every reboot

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

Title:
  Sizing issue on Startup

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hello, I recently put together a new PC and installed a fresh Ubuntu
  20.04. Immediately I noticed that, on startup, there was a flashing
  cursor and the decryption password screen was unusually large, but the
  login screen and desktop GUI was fine, so I thought nothing of it.
  With a recent update, the decryption password screen and the login
  screen are now both sized improperly and the text on the GUI is
  abnormally sized. I have included an image of the GUI with the bug
  apparent. If I toggle the 'large text' in universal access on then
  off, the problem resolves, but this is a hassle and happens every
  startup. I did have issues with the display driver for the GPU on
  installation and this may be a contributor but I am not sure and I am
  also not sure where to begin in troubleshooting this problem. Any help
  would be greatly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 26 14:15:32 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-42-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU117 [GeForce GTX 
1650] [1462:8d92]
  InstallationDate: Installed on 2020-07-28 (28 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID c0f4:05c0 SZH usb keyboard
   Bus 001 Device 003: ID :0538   USB OPTICAL MOUSE
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B365M D3H
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: B365M D3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnB365MD3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B365M D3H
  dmi.product.sku: Default string
  dmi.product.version: 

[Touch-packages] [Bug 1892979] Re: Sizing issue on Startup

2020-08-25 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1892521 ***
https://bugs.launchpad.net/bugs/1892521

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

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

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

Title:
  Sizing issue on Startup

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hello, I recently put together a new PC and installed a fresh Ubuntu
  20.04. Immediately I noticed that, on startup, there was a flashing
  cursor and the decryption password screen was unusually large, but the
  login screen and desktop GUI was fine, so I thought nothing of it.
  With a recent update, the decryption password screen and the login
  screen are now both sized improperly and the text on the GUI is
  abnormally sized. I have included an image of the GUI with the bug
  apparent. If I toggle the 'large text' in universal access on then
  off, the problem resolves, but this is a hassle and happens every
  startup. I did have issues with the display driver for the GPU on
  installation and this may be a contributor but I am not sure and I am
  also not sure where to begin in troubleshooting this problem. Any help
  would be greatly appreciated.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: wl nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 26 14:15:32 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
   nvidia, 440.100, 5.4.0-42-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU117 [GeForce GTX 
1650] [1462:8d92]
  InstallationDate: Installed on 2020-07-28 (28 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID c0f4:05c0 SZH usb keyboard
   Bus 001 Device 003: ID :0538   USB OPTICAL MOUSE
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. B365M D3H
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F2
  dmi.board.asset.tag: Default string
  dmi.board.name: B365M D3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnB365MD3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B365M D3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  

[Touch-packages] [Bug 1892979] [NEW] Sizing issue on Startup

2020-08-25 Thread Adrian Barbuio
Public bug reported:

Hello, I recently put together a new PC and installed a fresh Ubuntu
20.04. Immediately I noticed that, on startup, there was a flashing
cursor and the decryption password screen was unusually large, but the
login screen and desktop GUI was fine, so I thought nothing of it. With
a recent update, the decryption password screen and the login screen are
now both sized improperly and the text on the GUI is abnormally sized. I
have included an image of the GUI with the bug apparent. If I toggle the
'large text' in universal access on then off, the problem resolves, but
this is a hassle and happens every startup. I did have issues with the
display driver for the GPU on installation and this may be a contributor
but I am not sure and I am also not sure where to begin in
troubleshooting this problem. Any help would be greatly appreciated.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: wl nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.100  Fri May 29 08:45:51 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 26 14:15:32 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 5.4.0-26-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 5.4.0-42-generic, x86_64: installed
 nvidia, 440.100, 5.4.0-42-generic, x86_64: installed (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!)
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] TU117 [GeForce GTX 1650] 
[1462:8d92]
InstallationDate: Installed on 2020-07-28 (28 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID c0f4:05c0 SZH usb keyboard
 Bus 001 Device 003: ID :0538   USB OPTICAL MOUSE
 Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle 
(HCI mode)
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Gigabyte Technology Co., Ltd. B365M D3H
ProcEnviron:
 LANGUAGE=en_AU:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/13/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F2
dmi.board.asset.tag: Default string
dmi.board.name: B365M D3H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF2:bd08/13/2019:svnGigabyteTechnologyCo.,Ltd.:pnB365MD3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB365MD3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: B365M D3H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal fonts ubuntu

** Attachment added: "Screenshot of GUI with enlarged text"
   
https://bugs.launchpad.net/bugs/1892979/+attachment/5404595/+files/Screenshot%20from%202020-08-25%2020-36-38.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 1892898] Re: screen goes down automatic

2020-08-25 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1892615 ***
https://bugs.launchpad.net/bugs/1892615

** This bug has been marked a duplicate of bug 1892615
   screen goes down sometimes

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

Title:
  screen goes down automatic

Status in xorg package in Ubuntu:
  New

Bug description:
  screen goes down automatic updating will not solve it

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-114.115-generic 4.15.18
  Uname: Linux 4.15.0-114-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Aug 25 23:03:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-114-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1]
  InstallationDate: Installed on 2015-10-17 (1774 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-114-generic 
root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.0B
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C1
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.11
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May 28 11:49:11 2020
  xserver.configfile: default
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1892898/+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 1892847] Re: Xorg freeze

2020-08-25 Thread Daniel van Vugt
It sounds like something is crashing. If you find any files in
/var/crash then please follow these instructions:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

Otherwise, next time you have to restart using the power button, please
run this command as soon as it restarts:

  journalctl -b-1 > prevboot.txt

and then attach the resulting text file here.


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

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

** Summary changed:

- Xorg freeze
+ Screen freeze

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

Title:
  Screen freeze

Status in Ubuntu:
  Incomplete

Bug description:
  I plug a network adapter to my pc, it's TP-Link, i connect to a wifi, then i 
start sharing connection using hostspot (using my pc network card), after maybe 
1h, the screen freeze and everything stop, i had to restart it using the power 
button.
  After that i did the same thing, everything was ok, than i tried to write 
ifconfig, nothing happen, the settings freeze, and when i unplug the adabter 
the screen freeze and i had to restart it using the power button.
  and even when i just use my network card, it freeze sometime, i don't know 
why.
  yesterday it wrote (failed to evaluate _DSM), i searched about it and i 
didn't understand.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 25 10:39:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: fwts-efi-runtime-dkms, 20.03.00, 5.4.0-42-generic, x86_64: 
installed (WARNING! Diff between built and installed module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation 3rd Gen Core processor Graphics Controller 
[1179:fa33]
 Subsystem: Toshiba Corporation GeForce 710M [1179:fa33]
  InstallationDate: Installed on 2020-08-02 (22 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA SATELLITE C55-A-1UV
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=93843777-b112-4ce6-81dc-fb6cddf7e1f3 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PT10F
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.30:bd11/22/2013:svnTOSHIBA:pnSATELLITEC55-A-1UV:pvrPSCGCE-02M00KG4:rvnIntel:rnPT10F:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C55-A-1UV
  dmi.product.sku: PSCGCE
  dmi.product.version: PSCGCE-02M00KG4
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1892847/+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 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second

2020-08-25 Thread Daniel van Vugt
** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

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

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

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second

Status in gnome-shell package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+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 1875101] Re: Hidden WiFi does not automatically connect on startup

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Hidden WiFi does not automatically connect on startup

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Lenovo ThinkPad T430

  Ubuntu 20.04 LTS

  When starting Ubuntu 20.04 LTS from cold boot or reboot, hidden WiFi networks 
do not automatically connect despite having this option selected. 
  This is new to 20.04 and did not exist in 18.04.

  Waking from suspend does not have this issue.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 20.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-09-25 (579 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.12 metric 600
  Package: network-manager-applet (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Tags:  focal
  Uname: Linux 5.4.0-26-generic x86_64
  UpgradeStatus: Upgraded to focal on 2020-04-19 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  nmcli-dev:
   DEVICE   TYPE  STATEIP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH   
   wlp3s0   wifi  connectedfull  limited   
/org/freedesktop/NetworkManager/Devices/3  Pandanet
9254f39c-f7a5-4542-adda-599069bfd65d  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   enp0s25  ethernet  unavailable  none  none  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo   loopback  unmanagedunknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1875101/+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 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf

2020-08-25 Thread Dimitri John Ledkov
I'm not quite sure what is the point of wireguard package / wireguard-
tools on Ubuntu.

Our kernel ships wireguard modules by default anyway, and one can
configure wireguard via networkd and soon via netplan. Which is our
default tooling to interact with the wireguard kernel module.

wg / wg-quick seem like specific to wireguard tooling, which should not
be integrated or used by default on Ubuntu. Since all of the regular and
standard networking tooling now supports wireguard out of the box.

** Changed in: wireguard (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/1892798

Title:
  systemd package missing resolvconf(8) compatibility symlink, and a
  Provides: resolvconf

Status in systemd package in Ubuntu:
  Won't Fix
Status in wireguard package in Ubuntu:
  Incomplete

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf

2020-08-25 Thread Dimitri John Ledkov
Also see prior discussions on similar topic at
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1713803

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

Title:
  systemd package missing resolvconf(8) compatibility symlink, and a
  Provides: resolvconf

Status in systemd package in Ubuntu:
  Won't Fix
Status in wireguard package in Ubuntu:
  Incomplete

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf

2020-08-25 Thread Dimitri John Ledkov
Arch used to use openresolv, openresolv compat was added to systemd-
resolved, and yes hence they were able to switch to systemd-resolved
providing openresolv symlink / compat / integration. Either by default,
or as an option.

That is not possible for Debian/Ubuntu because of more than three dozen
of packaging & hooks, calling resolvconf with .$suffix notation.

Please see previous bugs about this, trying to identify, enumerate and
fix all of those usecases.

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

Title:
  systemd package missing resolvconf(8) compatibility symlink, and a
  Provides: resolvconf

Status in systemd package in Ubuntu:
  Won't Fix
Status in wireguard package in Ubuntu:
  Confirmed

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf

2020-08-25 Thread Dimitri John Ledkov
Ubuntu/Debian has never used openresolv, and yes systemd-resolved had a
contribution to have openresolv compatible input interface.

I am not asking for wireguard to implement any legacy/compat interfaces,
but use directly systemd-resolved standard interface which has abi
guarantees.

There is a lot more things and options one can provide to systemd-
resolved via native API that is impossible to specify via openresolv or
compat-openresolv.

I do not wish to ship any openresolv/resolvconf/compat symlinks at all
going forward.

Integration with resolvconf _without_ using .$suffix of where the DNS
information is originating is incorrect integration on Debian/Ubuntu,
because of how resolvconf is shipped and configured on Debian/Ubuntu and
used by other packages.

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

Title:
  systemd package missing resolvconf(8) compatibility symlink, and a
  Provides: resolvconf

Status in systemd package in Ubuntu:
  Won't Fix
Status in wireguard package in Ubuntu:
  Confirmed

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second

2020-08-25 Thread Felipe Pires de Oliveira
I`m facing the same issues on both Ubuntu 20.04.1 and Pop Os 20.04.

Intel® Core™ i3-9100T CPU @ 3.10GHz × 4 
Mesa Intel® UHD Graphics 630 (CFL GT2)
Gnome version 3.36.2

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

Title:
  Resizing any window will randomly result in graphics corruption for a
  fraction of a second

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  When resizing any window in any direction the window can appear glitchy as 
presented in the screenshot.
  This glitchy appearance is restored immediately.
  The issue seems to be seen less often when the CPU is utilized more heavily, 
as when I recorded the screen with OBS to grab the screenshot.
  The screenshots shows gnome-system-monitor, but I could trigger it with 
Firefox, gnome-terminal and others.

  No such issues were experienced with previously installed Ubuntu Mate
  or Windows 10.

  Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™
  i5-7200U CPU @ 2.50GHz × 4

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-4ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 14 20:45:47 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-04-14 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+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 1888575] Re: Split motd-news config into a new package

2020-08-25 Thread Andreas Hasenack
Xenial verification

Versions we are handling:
base-files 9.4ubuntu4.12 -> 9.4ubuntu4.13
ubuntu-server 1.361.4-> 1.361.5
motd-news-config n/a -> 9.4ubuntu4.13

Note that in xenial, at the moment, ubuntu-server is not pre-installed
in the images.

This verification is quite long, given the amount of tests involved.

TL;DR All tests from (a) to (j) passed as required.

xenial verification succeeded.


a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
apt install base-files
- upgrades ubuntu-server
- installs motd-news-config
- /e/d/motd-news remains, motd-news remains enabled

starting point:
ubuntu@xenial-motd-news-split:~$ dpkg -l base-files ubuntu-server 
motd-news-config | grep ^ii
dpkg-query: no packages found matching motd-news-config
ii  base-files 9.4ubuntu4.12 amd64Debian base system miscellaneous 
files
ii  ubuntu-server  1.361.4   amd64The Ubuntu Server system

unmodified config:
ubuntu@xenial-motd-news-split:~$ dpkg -s base-files | grep 
/etc/default/motd-news; echo -n ' '; md5sum /etc/default/motd-news | awk 
'{print $2,$1}'
 /etc/default/motd-news c08a329a603b640095da5ffe4e73491c
 /etc/default/motd-news c08a329a603b640095da5ffe4e73491c

motd-news enabled:
ubuntu@xenial-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.
ubuntu@xenial-motd-news-split:~$ echo $?
0

apt install base-files result:
The following NEW packages will be installed:
  motd-news-config
The following packages will be upgraded:
  base-files ubuntu-server
2 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.

new state:
ubuntu@xenial-motd-news-split:~$ dpkg -l base-files ubuntu-server 
motd-news-config | grep ^ii
ii  base-files   9.4ubuntu4.13 amd64Debian base system 
miscellaneous files
ii  motd-news-config 9.4ubuntu4.13 all  Configuration for motd-news 
shipped in base-files
ii  ubuntu-server1.361.5   amd64The Ubuntu Server system

motd-news remains enabled:
ubuntu@xenial-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news 
--force;echo $?

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.
0


b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
apt install base-files
- upgrades ubuntu-server
- installs motd-news-config
- /e/d/motd-news remains with the original modification

Starting point:
ubuntu@xenial-motd-news-split:~$ dpkg -l base-files ubuntu-server 
motd-news-config | grep ^ii
dpkg-query: no packages found matching motd-news-config
ii  base-files 9.4ubuntu4.12 amd64Debian base system miscellaneous 
files
ii  ubuntu-server  1.361.4   amd64The Ubuntu Server system

Modified config file, to disable motd-news:
ubuntu@xenial-motd-news-split:~$ sudo sed -i 's,^ENABLED=.*,ENABLED=0,' 
/etc/default/motd-news 
ubuntu@xenial-motd-news-split:~$ dpkg -s base-files | grep 
/etc/default/motd-news; echo -n ' '; md5sum /etc/default/motd-news | awk 
'{print $2,$1}'
 /etc/default/motd-news c08a329a603b640095da5ffe4e73491c
 /etc/default/motd-news e2d38a5c7454c64a967d6a2fe033558f
ubuntu@xenial-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news 
--force;echo $?
0

base-files install result:
The following NEW packages will be installed:
  motd-news-config
The following packages will be upgraded:
  base-files ubuntu-server
2 upgraded, 1 newly installed, 0 to remove and 9 not upgraded.

new state:
ii  base-files   9.4ubuntu4.13 amd64Debian base system 
miscellaneous files
ii  motd-news-config 9.4ubuntu4.13 all  Configuration for motd-news 
shipped in base-files
ii  ubuntu-server1.361.5   amd64The Ubuntu Server system

motd-news remains disabled:
ubuntu@xenial-motd-news-split:~$ ll /etc/default/motd-news*
-rw-r--r-- 1 root root 682 Aug 25 21:15 /etc/default/motd-news
ubuntu@xenial-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news 
--force;echo $?
0

config file moved to the motd-news-config package and the modification was 
preserved:
ubuntu@xenial-motd-news-split:~$ dpkg -s motd-news-config | grep 
/etc/default/motd-news; echo -n ' '; md5sum /etc/default/motd-news | awk 
'{print $2,$1}'
 /etc/default/motd-news c08a329a603b640095da5ffe4e73491c
 /etc/default/motd-news e2d38a5c7454c64a967d6a2fe033558f


c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news
apt install base-files
- upgrades base-files
- removes /e/d/motd-news
- motd-news is disabled

initial state:
ubuntu@xenial-motd-news-split:~$ dpkg -l base-files ubuntu-server 
motd-news-config | grep ^ii
dpkg-query: no packages found matching ubuntu-server
dpkg-query: no packages found matching motd-news-config
ii  base-files 9.4ubuntu4.12 amd64 

[Touch-packages] [Bug 1892798] Re: systemd package missing resolvconf(8) compatibility symlink, and a Provides: resolvconf

2020-08-25 Thread Jason A. Donenfeld
By the way, Arch manages the possibility of openresolv colliding with
systemd's resolvconf by providing a package called "systemd-resolvconf":
https://www.archlinux.org/packages/core/x86_64/systemd-resolvconf/
https://github.com/archlinux/svntogit-
packages/blob/packages/systemd/trunk/PKGBUILD#L239-L251

This seems like a perfectly reasonable way to accomplish this. Simply
package the symlink in a separate package, and then the "Recommends:"
for wireguard just includes systemd-resolvconf in the list alongside
openresolv and resolvconf.

That seems like an exceedingly reasonable way of going about things. Why
not just do the same thing here?

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

Title:
  systemd package missing resolvconf(8) compatibility symlink, and a
  Provides: resolvconf

Status in systemd package in Ubuntu:
  Won't Fix
Status in wireguard package in Ubuntu:
  Confirmed

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-08-25 Thread Rafael Motta
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

experiencing this as well
Lenovo ideapad 330
jbl live400bt
mic over bluetooth not working :(
but fully works over cable plugged in

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1385013] Re: proper fix for apparmor mediation of lower (encrypted) filesystem

2020-08-25 Thread Steve Beattie
** Changed in: apparmor (Ubuntu)
   Status: Fix Released => Confirmed

** Changed in: ecryptfs-utils (Ubuntu)
   Status: Fix Released => Confirmed

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

Title:
  proper fix for apparmor mediation of lower (encrypted) filesystem

Status in apparmor package in Ubuntu:
  Confirmed
Status in ecryptfs-utils package in Ubuntu:
  Confirmed

Bug description:
  This is the proper fix for LP: #359338 which is needed for user data
  encryption.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1385013/+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 1888575] Re: Split motd-news config into a new package

2020-08-25 Thread Andreas Hasenack
For the focal verification, I added a secondary test (j2) like I did for
bionic, and that is a release upgrade from an updated focal non-server
system to groovy, using the base-files package from focal-proposed, thus
simulating the release upgrade once this SRU is complete.

Result is correct as well. Details below.

j2) do-release-upgrade from focal to groovy with the focal-proposed base-files 
package installed, no ubuntu-server installed, and thus motd-news-config 
disabled:
Starting point: 
ubuntu@focal-motd-news-split:~$ dpkg -l base-files ubuntu-server 
motd-news-config | grep ^ii
dpkg-query: no packages found matching motd-news-config 
ii  base-files 11ubuntu5.2  amd64Debian base system miscellaneous 
files
ubuntu@focal-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force
ubuntu@focal-motd-news-split:~$ echo $? 
0   
ubuntu@focal-motd-news-split:~$ apt-cache policy base-files 
base-files: 
  Installed: 11ubuntu5.2
  Candidate: 11ubuntu5.2
  Version table:
 *** 11ubuntu5.2 500
500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
(...)   

Just before running do-release-upgrade, I removed focal-proposed from 
sources.list, to avoid upgrading other packages, not related to this test.

Final state:
ubuntu@focal-motd-news-split:~$ dpkg -l base-files ubuntu-server 
motd-news-config | grep ^ii
dpkg-query: no packages found matching motd-news-config 
ii  base-files 11ubuntu12   amd64Debian base system miscellaneous 
files
ubuntu@focal-motd-news-split:~$ apt-cache policy base-files 
base-files: 
  Installed: 11ubuntu12 
  Candidate: 11ubuntu12 
  Version table:
 *** 11ubuntu12 500 
500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages  

motd-new disabled as expected:  
ubuntu@focal-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force
ubuntu@focal-motd-news-split:~$ echo $? 
0

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed
Status in ubuntu-meta source package in Focal:
  Fix Committed
Status in base-files source package in Groovy:
  Fix Released
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set 

[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package

2020-08-25 Thread Andreas Hasenack
Bionic verification

This verification is quite long, given the amount of tests involved.

TL;DR All tests from (a) to (j) passed as required.

bionic verification succeeded.

Latest updates from bionic:
base-files:
 *** 10.1ubuntu2.9 500
500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
and
ubuntu-server:
 *** 1.417.4 500
500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages


a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
apt install base-files
- upgrades ubuntu-server
- installs motd-news-config
- /e/d/motd-news remains, motd-news remains enabled

Starting point:
ubuntu@bionic-motd-news-split:~$ dpkg -l base-files ubuntu-server 
motd-news-config | grep ^ii
dpkg-query: no packages found matching motd-news-config
ii  base-files 10.1ubuntu2.9 amd64Debian base system miscellaneous 
files
ii  ubuntu-server  1.417.4   amd64The Ubuntu Server system

Unmodified config:
$ dpkg -s base-files | grep /etc/default/motd-news; echo -n ' '; md5sum 
/etc/default/motd-news | awk '{print $2,$1}'
 /etc/default/motd-news c08a329a603b640095da5ffe4e73491c
 /etc/default/motd-news c08a329a603b640095da5ffe4e73491c

Installing base-files pulls in motd-news-config and upgrades base-files and 
ubuntu-server:
ubuntu@bionic-motd-news-split:~$ sudo apt install base-files
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  motd-news-config ubuntu-server
Recommended packages:
  grub-legacy-ec2
The following NEW packages will be installed:
  motd-news-config
The following packages will be upgraded:
  base-files ubuntu-server
2 upgraded, 1 newly installed, 0 to remove and 14 not upgraded

motd-news remains enabled:
ubuntu@bionic-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.

config is now part of motd-news-config package:
ubuntu@bionic-motd-news-split:~$ dpkg -s motd-news-config | grep 
/etc/default/motd-news; echo -n ' '; md5sum /etc/default/motd-news | awk 
'{print $2,$1}'
 /etc/default/motd-news c08a329a603b640095da5ffe4e73491c
 /etc/default/motd-news c08a329a603b640095da5ffe4e73491c


b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
apt install base-files
- upgrades ubuntu-server
- installs motd-news-config
- /e/d/motd-news remains with the original modification

Starting point:
ubuntu@bionic-motd-news-split:~$ dpkg -l base-files ubuntu-server 
motd-news-config | grep ^ii
dpkg-query: no packages found matching motd-news-config
ii  base-files 10.1ubuntu2.9 amd64Debian base system miscellaneous 
files
ii  ubuntu-server  1.417.4   amd64The Ubuntu Server system

Modified config:
ubuntu@bionic-motd-news-split:~$ sudo sed -i "s,^ENABLED=.*,ENABLED=0," 
/etc/default/motd-news
ubuntu@bionic-motd-news-split:~$ dpkg -s base-files | grep 
/etc/default/motd-news; echo -n ' '; md5sum /etc/default/motd-news | awk 
'{print $2,$1}'
 /etc/default/motd-news c08a329a603b640095da5ffe4e73491c
 /etc/default/motd-news e2d38a5c7454c64a967d6a2fe033558f

motd-news disabled with that modification:
ubuntu@bionic-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force
ubuntu@bionic-motd-news-split:~$ echo $?
0

Running apt install base-files also pulls in motd-news-config and upgrades 
ubuntu-server:
ubuntu@bionic-motd-news-split:~$ sudo apt install base-files
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
  motd-news-config ubuntu-server
Recommended packages:
  grub-legacy-ec2
The following NEW packages will be installed:
  motd-news-config
The following packages will be upgraded:
  base-files ubuntu-server
2 upgraded, 1 newly installed, 0 to remove and 14 not upgraded.

Config file now belongs to motd-news-config, and is still flagged as modified:
ubuntu@bionic-motd-news-split:~$ dpkg -s motd-news-config | grep 
/etc/default/motd-news; echo -n ' '; md5sum /etc/default/motd-news | awk 
'{print $2,$1}'
 /etc/default/motd-news c08a329a603b640095da5ffe4e73491c
 /etc/default/motd-news e2d38a5c7454c64a967d6a2fe033558f

And motd-news remains disabled because of the modification:
ubuntu@bionic-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force
ubuntu@bionic-motd-news-split:~$ echo $?
0

And no other config file is in /e/d:
ubuntu@bionic-motd-news-split:~$ ls -la /etc/default/motd-news*
-rw-r--r-- 1 root root 682 Aug 25 19:26 /etc/default/motd-news


c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news
apt install base-files
- upgrades base-files
- removes /e/d/motd-news
- motd-news is disabled

Starting point:
ubuntu@bionic-motd-news-split:~$ dpkg -l base-files 

[Touch-packages] [Bug 1385013] Re: proper fix for apparmor mediation of lower (encrypted) filesystem

2020-08-25 Thread NYEIN LIN THU
** Changed in: apparmor (Ubuntu)
 Assignee: (unassigned) => NYEIN LIN THU (mgnyein)

** Changed in: ecryptfs-utils (Ubuntu)
   Status: Confirmed => Fix Released

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

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

Title:
  proper fix for apparmor mediation of lower (encrypted) filesystem

Status in apparmor package in Ubuntu:
  Fix Released
Status in ecryptfs-utils package in Ubuntu:
  Fix Released

Bug description:
  This is the proper fix for LP: #359338 which is needed for user data
  encryption.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1385013/+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 1886886] Re: Plymouth 0.9.5 release

2020-08-25 Thread Launchpad Bug Tracker
This bug was fixed in the package plymouth - 0.9.5-0ubuntu2

---
plymouth (0.9.5-0ubuntu2) groovy; urgency=medium

  * Clear twostep footer, at the end of fsck, and clear lingering Ctrl+C
message LP: #1880250

plymouth (0.9.5-0ubuntu1) groovy; urgency=medium

  * New upstream version (lp: #1886886)
  * debian/control:
- remove the intltool Build-Depends, the new version uses gettext
  * debian/patches/git-drm-improve.patch,
debian/patches/gitlab-center-messages.patchs:
- removed, the changes are in the new version
  * debian/libplymouth5.symbols:
- refreshed for the new version
  * debian/patches/gitlab_correct_keynames.patch:
- use the correct title and subtitle key names

 -- Dimitri John Ledkov   Wed, 12 Aug 2020 22:03:42
+0100

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

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

Title:
  Plymouth 0.9.5 release

Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Plymouth 0.9.5 release:

  https://www.freedesktop.org/software/plymouth/releases/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1886886/+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 1880250] Re: Ctrl-C message displayed without any actual disk check

2020-08-25 Thread Launchpad Bug Tracker
This bug was fixed in the package plymouth - 0.9.5-0ubuntu2

---
plymouth (0.9.5-0ubuntu2) groovy; urgency=medium

  * Clear twostep footer, at the end of fsck, and clear lingering Ctrl+C
message LP: #1880250

plymouth (0.9.5-0ubuntu1) groovy; urgency=medium

  * New upstream version (lp: #1886886)
  * debian/control:
- remove the intltool Build-Depends, the new version uses gettext
  * debian/patches/git-drm-improve.patch,
debian/patches/gitlab-center-messages.patchs:
- removed, the changes are in the new version
  * debian/libplymouth5.symbols:
- refreshed for the new version
  * debian/patches/gitlab_correct_keynames.patch:
- use the correct title and subtitle key names

 -- Dimitri John Ledkov   Wed, 12 Aug 2020 22:03:42
+0100

** Changed in: plymouth (Ubuntu Groovy)
   Status: Fix Committed => Fix Released

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

Title:
  Ctrl-C message displayed without any actual disk check

Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in plymouth source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in plymouth source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Confirmed

Bug description:
  It seems the transition to bgrt lost something with Ubuntu's disk
  check details. The only thing I see on my screen during a long disk
  check is the "press Ctrl-C to stop all in progress disk checks" with
  no progress.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1880250/+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 1891316] Re: duplicate "progname" under gcc-10

2020-08-25 Thread Launchpad Bug Tracker
This bug was fixed in the package kbd - 2.0.4-4ubuntu4

---
kbd (2.0.4-4ubuntu4) groovy; urgency=medium

  * Add d/p/fix-duplicate-progname.patch to fix duplicate progname linker
error under gcc-10 (LP: #1891316)

 -- Dave Jones   Wed, 12 Aug 2020 12:01:20
+0100

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

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

Title:
  duplicate "progname" under gcc-10

Status in kbd package in Ubuntu:
  Fix Released

Bug description:
  Under gcc-10's linker an error occurs wherein "progname" appears to be
  included from multiple locations (as it's defined in version.h rather
  than merely declared).

  A trivial patch is available from the following branch:

  https://code.launchpad.net/~waveform/ubuntu/+source/kbd/+git/kbd/+ref
  /fix-duplicate-progname

  With test builds in the following PPA:

  https://launchpad.net/~waveform/+archive/ubuntu/kbd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/1891316/+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 1892798] Re: eliminating resolvconf/openresolv dependencies

2020-08-25 Thread Jason A. Donenfeld
> wireguard package => please feed DNS data direct to systemd-resolved
using either dbus or the cli.

Absolutely not. We're not going to add vendor-specific hacks for broken
distros that are unable to include the standard interface for this kind
of thing, resolvconf(8). This is a pretty clear case of downstream being
broken.

> Unfortunately systemd's resolved's resolvctl is not compatible with
Debian's/Ubuntu's historical resolvconf.

First of all, we're not talking about systemd's resolvectl. We're
talking about systemd's resolvconf compatibility symlink which provides
the same interface as openresolv or the debian resolvconf monster.

With that clarified, if you still think there's a problem due to
Debian's resolvconf using an interface prefix list, I think you're
incorrect there too. Firstly, openresolv doesn't act that way, and
things work fine. Secondly, systems that have moved to systemd-resolved
(that is, Ubuntu itself) have in the process _broken_ resolvconf anyway.
Replacing broken resolvconf with one that is less broken -- even if it
doesn't do priority interface prefixes -- is still a marked improvement.
And thirdly, every script I've seen that uses resolvconf actually
continues to work fine with systemd's compatibility symlink of
resolvconf; if any you see don't, why not fix them?

So, in other words, I don't think you've presented a very compelling
argument at all. I can't see any correct technical reasoning in what you
wrote. It seems like adding the resolvconf compatibility symlink is a
marked improvement over the current broken status quo.

** Summary changed:

- eliminating resolvconf/openresolv dependencies
+ systemd package missing resolvconf(8) compatibility symlink, and a Provides: 
resolvconf

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

Title:
  systemd package missing resolvconf(8) compatibility symlink, and a
  Provides: resolvconf

Status in systemd package in Ubuntu:
  Won't Fix
Status in wireguard package in Ubuntu:
  Confirmed

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1888575] Re: Split motd-news config into a new package

2020-08-25 Thread Andreas Hasenack
Focal verification

This verification is quite long, given the amount of tests involved.

TL;DR All tests from (a) to (j) passed as required.

focal verification succeeded.

Details below.


a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
apt install base-files
- upgrades ubuntu-server
- installs motd-news-config
- /e/d/motd-news remains, motd-news remains enabled

Starting with:
ii  base-files 11ubuntu5.1  amd64Debian base system miscellaneous 
files
ii  ubuntu-server  1.450.1  amd64The Ubuntu Server system

With proposed enabled, an apt install base-files pulls in motd-news-config and 
upgrades ubuntu-server:
$ sudo apt install base-files
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  motd-news-config ubuntu-server
The following NEW packages will be installed:
  motd-news-config
The following packages will be upgraded:
  base-files ubuntu-server
(...)

And motd-news remains enabled:
ubuntu@focal-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.

ubuntu@focal-motd-news-split:~$ apt-cache policy base-files ubuntu-server 
motd-news-config
base-files:
  Installed: 11ubuntu5.2
  Candidate: 11ubuntu5.2
  Version table:
 *** 11ubuntu5.2 500
500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
(...)
ubuntu-server:
  Installed: 1.450.2
  Candidate: 1.450.2
  Version table:
 *** 1.450.2 500
500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
(...)
motd-news-config:
  Installed: 11ubuntu5.2
  Candidate: 11ubuntu5.2
  Version table:
 *** 11ubuntu5.2 500
500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages


b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
apt install base-files
- upgrades ubuntu-server
- installs motd-news-config
- /e/d/motd-news remains with the original modification

First, change /e/d/motd-news to disable the service:
ubuntu@focal-motd-news-split:~$ sudo sed -i 's,^ENABLED=.*,ENABLED=0,' 
/etc/default/motd-news 
ubuntu@focal-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force
ubuntu@focal-motd-news-split:~$ 

Confirm installed packages:
ubuntu@focal-motd-news-split:~$ dpkg -l base-files ubuntu-server 
motd-news-config | grep ^i
dpkg-query: no packages found matching motd-news-config
ii  base-files 11ubuntu5.1  amd64Debian base system miscellaneous 
files
ii  ubuntu-server  1.450.1  amd64The Ubuntu Server system

Install base-files, which upgrades ubuntu-server, base-files, and installs the 
new motd-news-config package:
ubuntu@focal-motd-news-split:~$ sudo apt install base-files
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following additional packages will be installed:
  motd-news-config ubuntu-server
The following NEW packages will be installed:
  motd-news-config
The following packages will be upgraded:
  base-files ubuntu-server
2 upgraded, 1 newly installed, 0 to remove and 15 not upgraded.

And confirm motd-news remains disabled (which was the modification done):
ubuntu@focal-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force
ubuntu@focal-motd-news-split:~$ 

c) base-files installed, ubuntu-server not installed, unmodified /e/d/motd-news
apt install base-files
- upgrades base-files
- removes /e/d/motd-news
- motd-news is disabled

Starting from:
- unmodified config:
ubuntu@focal-motd-news-split:~$ dpkg -s base-files | grep 
/etc/default/motd-news ; md5sum /etc/default/motd-news 
 /etc/default/motd-news c08a329a603b640095da5ffe4e73491c
c08a329a603b640095da5ffe4e73491c  /etc/default/motd-news

- ubuntu-server removed:
ubuntu@focal-motd-news-split:~$ dpkg -l base-files ubuntu-server 
motd-news-config | grep ^i
dpkg-query: no packages found matching ubuntu-server
dpkg-query: no packages found matching motd-news-config
ii  base-files 11ubuntu5.1  amd64Debian base system miscellaneous 
files

apt install base-files upgrades just base-files, and /e/d/motd-news is removed, 
resulting in a disabled motd-news:
$ sudo apt install base-files
...
The following packages will be upgraded:
  base-files
1 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
...
ubuntu@focal-motd-news-split:~$ ls -la /etc/default/motd-news
ls: cannot access '/etc/default/motd-news': No such file or directory
ubuntu@focal-motd-news-split:~$ sudo /etc/update-motd.d/50-motd-news --force
ubuntu@focal-motd-news-split:~$ 


d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
apt install base-files
- upgrades base-files
- /e/d/motd-news gets renamed to backup
- motd-news is disabled


[Touch-packages] [Bug 1888575] Re: Split motd-news config into a new package

2020-08-25 Thread Andreas Hasenack
This is fixed in groovy already.

** Changed in: ubuntu-meta (Ubuntu Groovy)
   Status: In Progress => Fix Released

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in ubuntu-meta source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed
Status in ubuntu-meta source package in Focal:
  Fix Committed
Status in base-files source package in Groovy:
  Fix Released
Status in ubuntu-meta source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  The motd-news script is largely useless for desktop users, as they rarely 
login via a text console. It makes more sense for server users.

  We can use package dependencies to have the motd-news script enabled on 
servers, but disabled on desktops, and still handle upgrades. This is the plan:
  - move /etc/default/motd-news from base-files into a new binary package 
(motd-news-config, produced by src:base-files)
  - have ubuntu-server depend on motd-news-config
  - have base-files break current ubuntu-server, so that if base-files if 
upgraded and ubuntu-server is installed, ubuntu-server will also be upgraded to 
the new version which has the depends on motd-news-config

  Care must be taken to preserve a changed /etc/default/motd-news when
  the upgrade installs the new motd-news-config package. For example, on
  a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
  to the new base-files and ubuntu-server, and gets the new motd-config-
  news package, ENABLED=0 must remain set.

  [Test Case]
  a) base-files installed, ubuntu-server installed, unmodified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains, motd-news remains enabled

  b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
  apt install base-files
  - upgrades ubuntu-server
  - installs motd-news-config
  - /e/d/motd-news remains with the original modification

  c) base-files installed, ubuntu-server not installed, unmodified 
/e/d/motd-news
  apt install base-files
  - upgrades base-files
  - removes /e/d/motd-news
  - motd-news is disabled

  d) base-files installed, ubuntu-server not installed, modified /e/d/motd-news
  apt install base-files
  - upgrades base-files
  - /e/d/motd-news gets renamed to backup
  - motd-news is disabled

  e) removing motd-news-config will also remove ubuntu-server (since
  it's a depends, and not a recommends)

  f) upgrading just ubuntu-server should pull motd-news-config in, and
  force-upgrade base-files

  g) Removing motd-news-server leaves /e/d/motd-news around; purging
  motd-news-server removes the /e/d/motd-news config file

  h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
  - apt install base-files
  - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
  - /e/d/motd-news is installed with ENABLED=0

  i) base-files installed, ubuntu-server NOT installed, removed e/d/motd-news
  - apt install base-files
  - base-files is upgraded
  - no /e/d/motd-news is installed, motd-news remains disabled

  j) Perform a release upgrade from the previous ubuntu release to the
  one being tested while having ubuntu-server NOT installed (or use a
  desktop install). At the end, motd-news should be disabled. Verify
  with:

  $ sudo /etc/update-motd.d/50-motd-news --force
  $ (no output)

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-config package when it is installed, otherwise this SRU would 
jsut re-enabled motd-news. This is handled in d/motd-news-config.postinst's 
configure case.

  b) /e/d/motd-news config file was *removed* while it belonged to base-files. 
In such a case, a normal upgrade of the package (base-files in this example) 
would not reinstate the file. Much less this upgrade here, which has an 
explicit rm_conffile maintscript-helper for it. But the motd-news-config 
package that could be installed in the transaction would place the default 
config file back, and the default is ENABLED=1. Thus, a system that had 
motd-news disabled via removing the config file would now have it re-enabled 
after the upgrade.
  This was trickier to 

[Touch-packages] [Bug 1888572] Re: motd-news: use wget instead of curl

2020-08-25 Thread Andreas Hasenack
Xenial verification

Test (a)

Current base-files and curl installed (no ubuntu-server out-of-the-box on 
xenial lxd images):
ii  base-files 9.4ubuntu4.12  amd64Debian base system 
miscellaneous files
ii  curl   7.47.0-1ubuntu2.16 amd64command line tool for 
transferring data with URL syntax

motd-news runs:
ubuntu@xenial-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.

Remove curl, and it exits immediatelly:
ubuntu@xenial-motd-news-wget:~$ dpkg -l curl | grep curl
un  curl (no description available)

ubuntu@xenial-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force
ubuntu@xenial-motd-news-wget:~$ echo $?
0

With base-files and motd-news-config from xenial-proposed:
base-files:
  Installed: 9.4ubuntu4.13
  Candidate: 9.4ubuntu4.13
  Version table:
 *** 9.4ubuntu4.13 500
500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
(...)
motd-news-config:
  Installed: 9.4ubuntu4.13
  Candidate: 9.4ubuntu4.13
  Version table:
 *** 9.4ubuntu4.13 500
500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages

Still with curl removed:
ubuntu@xenial-motd-news-wget:~$ dpkg -l curl | grep curl
un  curl (no description available)

motd-news works again:
ubuntu@xenial-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.
ubuntu@xenial-motd-news-wget:~$ echo $?
0


Test (b)
Verify motd-news per cloud remains working.

b1) aws
ubuntu@xenial-motd-news-wget:~$ cloud-id
aws
ubuntu@xenial-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.
ubuntu@xenial-motd-news-wget:~$ sudo sh -x /etc/update-motd.d/50-motd-news 
--force 2>&1 | grep -wE 'wget .*cloud_id/[a-z]+'
+ wget --timeout 60 -U wget/1.17.1-1ubuntu1.5 Ubuntu/16.04.7/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/aws -O- --content-on-error https://motd.ubuntu.com

b2) gce
ubuntu@xenial-motd-news-wget:~$ cloud-id
gce
ubuntu@xenial-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.
ubuntu@xenial-motd-news-wget:~$ sudo sh -x /etc/update-motd.d/50-motd-news 
--force 2>&1 | grep -wE 'wget .*cloud_id/[a-z]+'
+ wget --timeout 60 -U wget/1.17.1-1ubuntu1.5 Ubuntu/16.04.7/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/gce -O- --content-on-error https://motd.ubuntu.com

b3) azure
ubuntu@xenial-motd-news-wget:~$ cloud-id
azure
ubuntu@xenial-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.
ubuntu@xenial-motd-news-wget:~$ sudo sh -x /etc/update-motd.d/50-motd-news 
--force 2>&1 | grep -wE 'wget .*cloud_id/[a-z]+'
+ wget --timeout 60 -U wget/1.17.1-1ubuntu1.5 Ubuntu/16.04.7/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/azure -O- --content-on-error https://motd.ubuntu.com


Xenial verification succeeded.


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

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

Title:
  motd-news: use wget instead of curl

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed

Bug description:
  [Impact] 
  The motd-news script is using curl, but since that is an optional package, 
there is no guarantee that it will be installed. The script correctly checks 
for its presence before trying to use it, though, so it won't fail. As we don't 
want to add such a dependency to the base-files package, we should switch to 
wget, which is standard.

  [Test Case]
  wget has a different behavior than curl in some areas, one of which is 
crucial for the motd-per-cloud feature. While curl will only complain about a 
404 from the server if given a specific parameter 

[Touch-packages] [Bug 1829401] Re: gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted question as no klass support

2020-08-25 Thread Norbert
Still happens on Groovy.
Opened `software-properties-gtk`, enabled Source Code and groovy-proposed, then 
it asked to reload cache. So I was moved to this bug report (really to bug 
1832057) .

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

Title:
  gi.repository.GLib.GError: pk-client-error-quark: could not do
  untrusted question as no klass support

Status in packagekit package in Ubuntu:
  Triaged
Status in packagekit source package in Eoan:
  Won't Fix
Status in packagekit source package in Focal:
  Confirmed

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

  [Back trace]
  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 86, in on_pktask_finish
  results = self._pktask.generic_finish(result)
  gi.repository.GLib.GError: pk-client-error-quark: could not do untrusted 
question as no klass support (8)

  During handling of the above exception, another exception occurred:

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/DialogCacheOutdated.py", 
line 89, in on_pktask_finish
  Gtk.ButtonsType.CANCEL, _("Error while refreshing cache"))
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 575, in 
__init__
  self._init(*args, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/Gtk.py", line 521, in 
__init__
  _window_init(self, *args, **kwargs)
File "/usr/lib/python3/dist-packages/gi/overrides/__init__.py", line 319, 
in new_init
  return super_init_func(self, **new_kwargs)
  TypeError: could not convert value for property `transient_for' from 
DialogCacheOutdated to GtkWindow

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+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 1888572] Re: motd-news: use wget instead of curl

2020-08-25 Thread Andreas Hasenack
Bionic verification

Test (a)

Current base-files, ubuntu-server and curl installed:
ii  base-files 10.1ubuntu2.9  amd64Debian base system 
miscellaneous files
ii  curl   7.58.0-2ubuntu3.10 amd64command line tool for 
transferring data with URL syntax
ii  ubuntu-server  1.417.4amd64The Ubuntu Server system

motd-news runs:
$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.

Without curl, it exits immediately:
ubuntu@bionic-motd-news-wget:~$ dpkg -l curl | grep curl
un  curl (no description available)
ubuntu@bionic-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force
ubuntu@bionic-motd-news-wget:~$ echo $?
0
ubuntu@bionic-motd-news-wget:~$ 

Installing base-files and motd-news-config from bionic-proposed:
ubuntu@bionic-motd-news-wget:~$ apt-cache policy base-files motd-news-config
base-files:
  Installed: 10.1ubuntu2.10
  Candidate: 10.1ubuntu2.10
  Version table:
 *** 10.1ubuntu2.10 500
500 http://br.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
(...)
motd-news-config:
  Installed: 10.1ubuntu2.10
  Candidate: 10.1ubuntu2.10
  Version table:
 *** 10.1ubuntu2.10 500
500 http://br.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages

Still no curl:
$ dpkg -l curl | grep curl
un  curl (no description available)

motd-news works again:
ubuntu@bionic-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.
ubuntu@bionic-motd-news-wget:~$ echo $?
0


Test (b)
Verify motd-news per cloud remains working.

b1) aws
ubuntu@bionic-motd-news-wget:~$ cloud-id
aws
ubuntu@bionic-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.
ubuntu@bionic-motd-news-wget:~$ sudo sh -x /etc/update-motd.d/50-motd-news 
--force 2>&1 | grep -wE 'wget .*cloud_id/[a-z]+'
+ wget --timeout 60 -U wget/1.19.4-1ubuntu2.2 Ubuntu/18.04.5/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/aws -O- --content-on-error https://motd.ubuntu.com

b2) gce
ubuntu@bionic-motd-news-wget:~$ cloud-id
gce
ubuntu@bionic-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.
ubuntu@bionic-motd-news-wget:~$ sudo sh -x /etc/update-motd.d/50-motd-news 
--force 2>&1 | grep -wE 'wget .*cloud_id/[a-z]+'
+ wget --timeout 60 -U wget/1.19.4-1ubuntu2.2 Ubuntu/18.04.5/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/gce -O- --content-on-error https://motd.ubuntu.com

b3) azure
ubuntu@bionic-motd-news-wget:~$ cloud-id
azure
ubuntu@bionic-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.
ubuntu@bionic-motd-news-wget:~$ sudo sh -x /etc/update-motd.d/50-motd-news 
--force 2>&1 | grep -wE 'wget .*cloud_id/[a-z]+'
+ wget --timeout 60 -U wget/1.19.4-1ubuntu2.2 Ubuntu/18.04.5/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/azure -O- --content-on-error https://motd.ubuntu.com


Bionic verification succeeded.


** Tags removed: verification-needed-bionic verification-needed-focal
** Tags added: verification-done-bionic verification-done-focal

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

Title:
  motd-news: use wget instead of curl

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed

Bug description:
  [Impact] 
  The motd-news script is using curl, but since that is an optional package, 
there is no guarantee that it will be installed. The script correctly checks 
for its presence before trying to use it, though, so it won't fail. As we don't 
want to add such a dependency to the base-files package, we should switch to 
wget, which is standard.

  [Test Case]
  wget has a different behavior than curl in some areas, one of which is 

[Touch-packages] [Bug 1888572] Re: motd-news: use wget instead of curl

2020-08-25 Thread Andreas Hasenack
Focal verification

Test (a)

Current base-files, ubuntu-server and curl installed:
ii  base-files 11ubuntu5.1   amd64Debian base system 
miscellaneous files
ii  curl   7.68.0-1ubuntu2.2 amd64command line tool for 
transferring data with URL syntax
ii  ubuntu-server  1.450.1   amd64The Ubuntu Server system

motd-news runs:
$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.

Without curl:
$ dpkg -l curl | grep curl
un  curl (no description available)

motd-news exits immediately:
ubuntu@focal-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force
ubuntu@focal-motd-news-wget:~$ echo $?
0

With base-files and motd-news-config from focal-proposed:
ubuntu@focal-motd-news-wget:~$ apt-cache policy base-files motd-news-config
base-files:
  Installed: 11ubuntu5.2
  Candidate: 11ubuntu5.2
  Version table:
 *** 11ubuntu5.2 500
500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
(...)
motd-news-config:
  Installed: 11ubuntu5.2
  Candidate: 11ubuntu5.2
  Version table:
 *** 11ubuntu5.2 500
500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages

Still no curl:
$ dpkg -l curl | grep curl
un  curl (no description available)

motd-news works again:
$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.


Test (b)
Verify motd-news per cloud remains working.

b1) aws
ubuntu@focal-motd-news-wget:~$ cloud-id
aws
$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.

cloud_id/aws was sent:
$ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1 | grep -wE 'wget 
.*cloud_id/[a-z]+'
+ wget --timeout 60 -U wget/1.20.3-1ubuntu1 Ubuntu/20.04.1/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/aws -O- --content-on-error https://motd.ubuntu.com


b2) gce
ubuntu@focal-motd-news-wget:~$ cloud-id
gce
ubuntu@focal-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.
ubuntu@focal-motd-news-wget:~$ sudo sh -x /etc/update-motd.d/50-motd-news 
--force 2>&1 | grep -wE 'wget .*cloud_id/[a-z]+'
+ wget --timeout 60 -U wget/1.20.3-1ubuntu1 Ubuntu/20.04.1/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/gce -O- --content-on-error https://motd.ubuntu.com

b3) azure
ubuntu@focal-motd-news-wget:~$ cloud-id
azure
ubuntu@focal-motd-news-wget:~$ sudo /etc/update-motd.d/50-motd-news --force

 * Are you ready for Kubernetes 1.19? It's nearly here! Try RC3 with
   sudo snap install microk8s --channel=1.19/candidate --classic

   https://microk8s.io/ has docs and details.
ubuntu@focal-motd-news-wget:~$ sudo sh -x /etc/update-motd.d/50-motd-news 
--force 2>&1 | grep -wE 'wget .*cloud_id/[a-z]+'
+ wget --timeout 60 -U wget/1.20.3-1ubuntu1 Ubuntu/20.04.1/LTS 
GNU/Linux/5.4.0-42-generic/x86_64 Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz 
cloud_id/azure -O- --content-on-error https://motd.ubuntu.com


Focal verification succeeded.

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

Title:
  motd-news: use wget instead of curl

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed

Bug description:
  [Impact] 
  The motd-news script is using curl, but since that is an optional package, 
there is no guarantee that it will be installed. The script correctly checks 
for its presence before trying to use it, though, so it won't fail. As we don't 
want to add such a dependency to the base-files package, we should switch to 
wget, which is standard.

  [Test Case]
  wget has a different behavior than curl in some areas, one of which is 
crucial for the motd-per-cloud feature. While curl will only complain about a 
404 from the server if given a specific parameter (-f), wget does that by 
default, and needs special handling.

  a) With curl, base-files and ubuntu-server installed, first verify motd-news 
works:
  $ sudo /etc/update-motd.d/50-motd-news --force

   * Are you ready for Kubernetes 1.19? It's 

Re: [Touch-packages] [Bug 1877078] Re: Please ship empty /etc/fstab in LXD images

2020-08-25 Thread Steve Langasek
On Tue, Aug 25, 2020 at 02:20:50PM -, Balint Reczey wrote:
> @vorlon What is your plan regarding this fix? The revert may have helped
> MAAS, but broke all LXD instances. IMO if MAAS relied on having a broken
> fstab then MAAS should be fixed and not LXD images should be broken, so
> I'd prefer having this fix in again. Maybe with /etc/fstab as an empty
> file which is not particularly beautiful, but not invalid at least.

MAAS images were broken because cloud-init could not handle the new
behavior.  This is not the MAAS team's responsibility to fix, the Server
Team has been working on it with Dimitri; and having our MAAS images broken
was an unacceptable regression that was blocking kernel testing.

See the other linked bug, LP: #1890803, for details.  If the
cloud-initramfs-tools change has landed, then the livecd-rootfs revert can
be reverted again.

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

Title:
  Please ship empty /etc/fstab in LXD images

Status in livecd-rootfs package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Systemd boots degraded because of the invalid content of /etc/fstab:

  $ lxc shell gg-test 
  root@gg-test:~# systemctl is-system-running 
  degraded
  root@gg-test:~# systemctl list-units --failed 
UNIT   LOAD   ACTIVE SUBDESCRIPTION 

  ● systemd-remount-fs.service loaded failed failed Remount Root and Kernel 
File Systems

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  1 loaded units listed.
  root@gg-test:~# cat /etc/fstab 
  LABEL=cloudimg-rootfs /ext4   defaults0 0
  root@gg-test:~# echo "" > /etc/fstab 
  root@gg-test:~# reboot

  Session terminated, killing shell... ...killed.
  rbalint@yogi:~$ lxc shell gg-test 
  root@gg-test:~# systemctl is-system-running 
  running
  root@gg-test:~# systemctl list-units --failed 
UNIT LOAD ACTIVE SUB DESCRIPTION
  0 loaded units listed.

  
  Not shipping is also fixing the issue, but some programs (such as systemd 
autopkgtes) reads fstab and a missing fstab should be special-cased, thus that 
would cause more breakages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/1877078/+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 1892898] [NEW] screen goes down automatic

2020-08-25 Thread praveen
Public bug reported:

screen goes down automatic updating will not solve it

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-114.115-generic 4.15.18
Uname: Linux 4.15.0-114-generic x86_64
NonfreeKernelModules: wl
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
CompositorRunning: None
Date: Tue Aug 25 23:03:11 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-114-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1]
InstallationDate: Installed on 2015-10-17 (1774 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: Hewlett-Packard HP Notebook
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-114-generic 
root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.0B
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 80C1
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 96.11
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP
dmi.product.name: HP Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu May 28 11:49:11 2020
xserver.configfile: default
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4.4

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  screen goes down automatic

Status in xorg package in Ubuntu:
  New

Bug description:
  screen goes down automatic updating will not solve it

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-114.115-generic 4.15.18
  Uname: Linux 4.15.0-114-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  CompositorRunning: None
  Date: Tue Aug 25 23:03:11 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.15.0-114-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80c1]
  InstallationDate: Installed on 2015-10-17 (1774 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Hewlett-Packard HP Notebook
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-114-generic 
root=UUID=733f49c2-0b52-4a07-9eea-15cbf15593cf ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.0B
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80C1
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 96.11
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.0B:bd06/04/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn80C1:rvr96.11:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  

[Touch-packages] [Bug 1886572] Re: Remove uptime from the motd-news user agent

2020-08-25 Thread Andreas Hasenack
Xenial verification 

Current version:
ubuntu@xenial-motd-news-no-uptime:~$ apt-cache policy base-files
base-files: 
  Installed: 9.4ubuntu4.12  
  Candidate: 9.4ubuntu4.12  
  Version table:
 *** 9.4ubuntu4.12 500  
500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
100 /var/lib/dpkg/status

Uptime is there:
ubuntu@xenial-motd-news-no-uptime:~$ grep uptime /etc/update-motd.d/50-motd-news
# Some messages may only be pertinent before or after some amount of uptime 
read up idle < /proc/uptime 
uptime="uptime/$up/$idle"   
USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"  

After updating: 
ubuntu@xenial-motd-news-no-uptime:~$ apt-cache policy base-files
base-files: 
  Installed: 9.4ubuntu4.13  
  Candidate: 9.4ubuntu4.13  
  Version table:
 *** 9.4ubuntu4.13 500  
500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 
Packages
100 /var/lib/dpkg/status

Uptime is gone: 
ubuntu@xenial-motd-news-no-uptime:~$ grep uptime /etc/update-motd.d/50-motd-news
ubuntu@xenial-motd-news-no-uptime:~$


Xenial verification succeeded.

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

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed

Bug description:
  [Impact] 
  The uptime value in the user-agent string sent to the motd-news server is 
unused and not necessary. It should be removed.

  [Test Case]
  Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is 
no longer used.

  Previous version:
  $ grep uptime /etc/update-motd.d/50-motd-news 
  # Some messages may only be pertinent before or after some amount of uptime
  read up idle < /proc/uptime
  uptime="uptime/$up/$idle"
  USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"

  Updated version:
  $ grep uptime /etc/update-motd.d/50-motd-news
   (no output)

  
  [Regression Potential] 
  The server side, if it were checking this value, could be surprised by this 
change.

  [Other Info]
  N/A

  [Original Description]
  I don't why that was included but it shouldn't be. Please remove it.

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

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


[Touch-packages] [Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

2020-08-25 Thread Philippe
Same issue on Ubuntu Mate 20.04 with Radeon RX 5600 XT with stock driver and 
also with driver version 20.30 (from AMD).
Affected : 
- single DP>VGA monitor
- single HDMI>HDMI TV
- dual screens DP>VGA monitor with HDMI>HDMI TV

Another workaround : no issue if set to marco with GPU compositor compton:
`marco-compton`
If upgraded from 18.04 to 20.04 compton is still installed.

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

Status in Linux:
  Unknown
Status in libxcb package in Ubuntu:
  Confirmed
Status in xfwm4 package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Confirmed

Bug description:
  Update based on further research.

  This only happens when the secondary external display is operating at
  a different pixel width to the internal. In this case eDP is 1920x1080
  whereas the external HDMI-A-0 is natively 1680x1050.

  It is caused by xfwm4's recent switch from using glx to xpresent for
  AMD GPUs.

  The underlying bug is in the AMD driver.

  I was able to reproduce on an external 1920x1200 display only when it
  was set to a non-native 1680x1050 resolution.

  ---
  Two identical Lenovo E495 laptops with 20.04 installed. The problem occurred 
initially on the laptop that is having package upgrades applied regularly.

  With dual monitors and the external monitor placed left or right the
  display has a blocked staircase effect shown in the attached
  photograph, and seems related to

  https://gitlab.freedesktop.org/xorg/driver/xf86-video-
  amdgpu/-/issues/10

  More detailed investigation suggests it only happens when the X
  coordinate of the two monitors is different. The symptom looks like an
  off-by-one error because it appears as if the display is divided into,
  say, 10 rows and 15 columns but the first row has 16 'columns' worth
  of blocks on it and so wraps to the beginning of the 2nd row, and so
  on.

  On the laptop without package upgrades being applied this didn't
  happen. So I upgraded it (314 packages) and restarted and it too sees
  the same problem.

  I suspected libxcomposite1 and downgraded it to 1:0.4.5-0ubuntu1 but
  that didn't solve it.

  I now suspect libxcb but so far haven't been able to prove it.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroRelease: Ubuntu 20.04
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c1) (prog-if 
00 [VGA controller])
     Subsystem: Lenovo ThinkPad E595 [17aa:5124]
  InstallationDate: Installed on 2020-04-08 (11 days ago)
  InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200408)
  MachineType: LENOVO 20NECTO1WW
  Package: xserver-xorg-video-amdgpu 19.1.0-1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic 
root=/dev/mapper/ELLOE000-rootfs ro acpi_osi=! "acpi_osi=Windows 2016" quiet 
splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Tags:  focal ubuntu ubuntu
  Uname: Linux 5.4.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sudo users
  _MarkForUpload: True
  dmi.bios.date: 12/23/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R11ET32W (1.12 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NECTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET32W(1.12):bd12/23/2019:svnLENOVO:pn20NECTO1WW:pvrThinkPadE495:rvnLENOVO:rn20NECTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad E495
  dmi.product.name: 20NECTO1WW
  dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
  dmi.product.version: ThinkPad E495
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

-- 
Mailing list: 

[Touch-packages] [Bug 1886572] Re: Remove uptime from the motd-news user agent

2020-08-25 Thread Andreas Hasenack
Focal verification  

Current focal version:  
  Version table:
 *** 11ubuntu5.1 500
500 http://br.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages

Verifying uptime is present:
# grep uptime /etc/update-motd.d/50-motd-news   
# Some messages may only be pertinent before or after some amount of uptime 
read up idle < /proc/uptime 
uptime="uptime/$up/$idle"   
USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"  

In the updated version, uptime is gone: 
base-files: 
  Installed: 11ubuntu5.2
  Candidate: 11ubuntu5.2
  Version table:
 *** 11ubuntu5.2 500
500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages

# grep uptime /etc/update-motd.d/50-motd-news   
#   

Focal verification succeeded. 

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

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed

Bug description:
  [Impact] 
  The uptime value in the user-agent string sent to the motd-news server is 
unused and not necessary. It should be removed.

  [Test Case]
  Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is 
no longer used.

  Previous version:
  $ grep uptime /etc/update-motd.d/50-motd-news 
  # Some messages may only be pertinent before or after some amount of uptime
  read up idle < /proc/uptime
  uptime="uptime/$up/$idle"
  USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"

  Updated version:
  $ grep uptime /etc/update-motd.d/50-motd-news
   (no output)

  
  [Regression Potential] 
  The server side, if it were checking this value, could be surprised by this 
change.

  [Other Info]
  N/A

  [Original Description]
  I don't why that was included but it shouldn't be. Please remove it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+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 1886572] Re: Remove uptime from the motd-news user agent

2020-08-25 Thread Andreas Hasenack
Bionic verification 

Current version:
$ apt-cache policy base-files   
base-files: 
  Installed: 10.1ubuntu2.9  
  Candidate: 10.1ubuntu2.9  
  Version table:
 *** 10.1ubuntu2.9 500  
500 http://br.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status

Uptime is there:
ubuntu@bionic-motd-news-no-uptime:~$ grep uptime /etc/update-motd.d/50-motd-news
# Some messages may only be pertinent before or after some amount of uptime 
read up idle < /proc/uptime 
uptime="uptime/$up/$idle"   
USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"  

After updating, it's gone:  
ubuntu@bionic-motd-news-no-uptime:~$ apt-cache policy base-files
base-files: 
  Installed: 10.1ubuntu2.10 
  Candidate: 10.1ubuntu2.10 
  Version table:
 *** 10.1ubuntu2.10 500 
500 http://br.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 10.1ubuntu2.9 500  

ubuntu@bionic-motd-news-no-uptime:~$ grep uptime /etc/update-motd.d/50-motd-news
ubuntu@bionic-motd-news-no-uptime:~$

Bionic verification succeeded.

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

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed

Bug description:
  [Impact] 
  The uptime value in the user-agent string sent to the motd-news server is 
unused and not necessary. It should be removed.

  [Test Case]
  Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is 
no longer used.

  Previous version:
  $ grep uptime /etc/update-motd.d/50-motd-news 
  # Some messages may only be pertinent before or after some amount of uptime
  read up idle < /proc/uptime
  uptime="uptime/$up/$idle"
  USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"

  Updated version:
  $ grep uptime /etc/update-motd.d/50-motd-news
   (no output)

  
  [Regression Potential] 
  The server side, if it were checking this value, could be surprised by this 
change.

  [Other Info]
  N/A

  [Original Description]
  I don't why that was included but it shouldn't be. Please remove it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+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 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2020-08-25 Thread Iain
HSP/HFP does not work on Ubuntu 20.04 with Sony WI-1000X.  A2DP does
work (output) but as soon as I switch to HSP/HFP then I loose bluetooth
audio (input and output).  Ran Ubuntu 18.04 from a live USB and HSP/HFP
did work so something has changed between 18.04 and 20.04.

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

Title:
  [Bluetooth] No audio output/input in HSP/HFP mode

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm testing with Sony bluetooth headset SBH20, works fine in A2DP
  profile, but I can't get audio input and output work in HSP/HFP
  profile.

  [Reproduce steps]
  1. Scan and pair BT headset in Bluetooth setting
  2. Switch to HSP/HFP profile in Sound setting
  3. Test sound output/input

  [Machine information]
  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
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr  9 16:26:52 2020
  InstallationDate: Installed on 2020-04-09 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: SBH20
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1359 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SBH20, recording] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.13
  dmi.board.name: 0188D1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 31
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn0188D1:rvrA00:cvnDellInc.:ct31:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390 2-in-1
  dmi.product.sku: 08B0
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1871794/+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 1892130] Re: systemd 245.4-4ubuntu3.2 ADT test failure with linux-aws 5.4.0-1022.22

2020-08-25 Thread Kleber Sacilotto de Souza
** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Description changed:

  Testing failed on:
- amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20200817_235646_79e19@/log.gz
+ amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20200817_235646_79e19@/log.gz
+ 
+ The testcase systemd-fsckd is falling with several kernels in Focal:
+ 
+ ==
+ FAIL: test_fsck_with_failure (__main__.FsckdTest)
+ Ensure that a failing fsck doesn't prevent fsckd to stop
+ --
+ Traceback (most recent call last):
+   File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", 
line 100, in test_fsck_wi
+ th_failure
+ self.assertFalse(self.is_failed_unit('process-killer'))
+ AssertionError: True is not false
+ 
+ 
+ ==
+ FAIL: test_systemd_fsck_with_failure (__main__.FsckdTest)
+ Ensure that a failing systemd-fsck doesn't prevent fsckd to stop
+ --
+ Traceback (most recent call last):
+   File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", 
line 114, in test_systemd_fsck_with_failure
+ self.assertProcessKilled()
+   File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", 
line 204, in assertProcessKilled
+ self.assertFalse(self.is_failed_unit('process-killer'))
+ AssertionError: True is not false

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

Title:
  systemd 245.4-4ubuntu3.2 ADT test failure with linux-aws 5.4.0-1022.22

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

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal/focal/amd64/s/systemd/20200817_235646_79e19@/log.gz

  The testcase systemd-fsckd is falling with several kernels in Focal:

  ==
  FAIL: test_fsck_with_failure (__main__.FsckdTest)
  Ensure that a failing fsck doesn't prevent fsckd to stop
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", 
line 100, in test_fsck_wi
  th_failure
  self.assertFalse(self.is_failed_unit('process-killer'))
  AssertionError: True is not false

  
  ==
  FAIL: test_systemd_fsck_with_failure (__main__.FsckdTest)
  Ensure that a failing systemd-fsck doesn't prevent fsckd to stop
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", 
line 114, in test_systemd_fsck_with_failure
  self.assertProcessKilled()
File "/tmp/autopkgtest.wrZrJf/build.LgN/src/debian/tests/systemd-fsckd", 
line 204, in assertProcessKilled
  self.assertFalse(self.is_failed_unit('process-killer'))
  AssertionError: True is not false

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892130/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

2020-08-25 Thread Launchpad Bug Tracker
This bug was fixed in the package bcache-tools - 1.0.8-2ubuntu0.18.04.1

---
bcache-tools (1.0.8-2ubuntu0.18.04.1) bionic; urgency=medium

  [ Ryan Harper ]
  * Add helper script to read bcache devs superblock (LP: #1861941)

 -- Rafael David Tinoco   Wed, 05 Aug 2020
17:44:05 -0300

** Changed in: bcache-tools (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in bcache-tools source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  In Progress

Bug description:
  SRU TEAM: The last 2 commits show a summary for the merges/changes
  I added some specific (to Bionic) notes in the template.
  Thanks!

  [Impact]

   * bcache-tools udev created symlinks might disappear when other udev
  events are processed for the same devices.

   * after mkfs.XXX in /dev/bcacheY you might face a condition where
  /dev/bcache/by-{uuid,label}/zzz symlinks are gone.

   * /dev/bcache/by-{uuid,label}/ symlinks are important so bcache
  devices can be addressed by their UUIDs and not the ordering they were
  assembled (MAAS depends on this feature, for example).

   * it was also discussed in this bug that systemd-udev should *not*
  populate /dev/disk/by-uuid/ with symlinks of disks that were bcache
  backing devices. this was turned into a discussion whether blkid
  should report those or not, and this discussion "died" after sometime.
  This last item is what the systemd update is all about: to disallow
  /dev/disk/by-XXX/ creation for bcache backing devices (a simple
  change that will reduce end users confusion).

  [Test Case]

   * The reproducer script is here:

     https://paste.ubuntu.com/p/37KGy2Smnp/

   * Bionic can't reproduce the issue with the 18.04 kernel, nor with
  the HWE kernel. Nevertheless, it is preferable that Bionic also do the
  same thing: to read bcache superblock and feed environment for
  /dev/bcache/by-{uuid,label} symlinks creation.

  [Regression Potential]

   * We are not depending on bcache device udev events any more when
  creating the /dev/bcache/by-{uuid,label}/ symlinks. Instead, we are
  depending on a wrapper script that heads bcache device superblock. If
  there is a bug in this wrapper the symlinks wouldn't work.

   * Previously we were thinking in asking the kernel team to remove the
  bcache udev event delta script they've done for previous case (LP:
  #1729145). It creates the udev events that were being read and filling
  the symlinks. We decided not to remove those (just from Groovy and on)
  so we don't need to worry on Breaks/Conflicts in between the kernel
  package and bcache-tools (and udev)).

   * Long story short: kernel will continue to emit bcache udev events
  as it did previously but now those events won't be used by anything -
  after installing this SRU - because udev wrapper script is doing this
  job (and doing it properly)

  [Other Info]

  - Original Description:

  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
    Installed: 5.4.0.12.15
    Candidate: 5.4.0.12.15
    Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic
  linux-image-5.4.0-12-generic:
    Installed: 5.4.0-12.15
    Candidate: 5.4.0-12.15
    Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   

[Touch-packages] [Bug 1831467] Re: test-umockdev tests flaky on armhf (and sometimes other archs)

2020-08-25 Thread Launchpad Bug Tracker
This bug was fixed in the package umockdev - 0.11.1-1ubuntu0.1

---
umockdev (0.11.1-1ubuntu0.1) bionic; urgency=medium

  * d/p/lp1831467/0001-src-umockdev.vala-fix-ScriptRunner.op_write.patch,

d/p/lp1831467/0002-tests-read-expected-number-of-bytes-maybe-over-multi.patch,

d/p/lp1831467/0003-tests-test-umockdev-record.vala-add-slow_testbed_fac.patch,

d/p/lp1831467/0004-tests-test-umockdev.c-add-slow_testbed_factor-variab.patch,

d/p/lp1831467/0005-tests-test-umockdev-run.vala-add-slow_testbed_factor.patch,
d/p/lp1831467/0006-remove_SocketServer_ctrl-r_assert.patch,
d/rules, d/t/upstream:
- Fix various timing-related tests
  Fix ScriptRunner fuzz checking function
  (LP: #1831467)

 -- Dan Streetman   Thu, 06 Aug 2020 20:43:44
-0400

** Changed in: umockdev (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  test-umockdev tests flaky on armhf (and sometimes other archs)

Status in umockdev package in Ubuntu:
  Fix Released
Status in umockdev source package in Xenial:
  In Progress
Status in umockdev source package in Bionic:
  Fix Released
Status in umockdev source package in Focal:
  Fix Released
Status in umockdev source package in Groovy:
  Fix Released

Bug description:
  [impact]

  these tests fail intermittently, due to various timing issues, as well
  as an actual code bug in how data fuzz is calculated.

  it looks like the failures are mostly on armhf, but do happen less
  often on other archs.

  [test case]

  check the previous autopkgtest logs, e.g.
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz

  [regression potential]

  any regression would likely result in incorrectly failing/passing 
autopkgtests, or in a incorrect pass or incorrect fail of the ScriptRunner
  to verify the data's level of fuzz.

  [scope]

  as the tests are flaky on armhf all the way back to trusty, this is
  needed for all releases.

  [other info]

  Fixed upstream in PR https://github.com/martinpitt/umockdev/pull/103

  Most of the changes are test case fixes, but there is one fix to
  source code to fix the ScriptRunning function that validates the level
  of fuzz in data, so this is not *only* a testcase fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1831467/+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 1831467] Update Released

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

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

Title:
  test-umockdev tests flaky on armhf (and sometimes other archs)

Status in umockdev package in Ubuntu:
  Fix Released
Status in umockdev source package in Xenial:
  In Progress
Status in umockdev source package in Bionic:
  Fix Released
Status in umockdev source package in Focal:
  Fix Released
Status in umockdev source package in Groovy:
  Fix Released

Bug description:
  [impact]

  these tests fail intermittently, due to various timing issues, as well
  as an actual code bug in how data fuzz is calculated.

  it looks like the failures are mostly on armhf, but do happen less
  often on other archs.

  [test case]

  check the previous autopkgtest logs, e.g.
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz

  [regression potential]

  any regression would likely result in incorrectly failing/passing 
autopkgtests, or in a incorrect pass or incorrect fail of the ScriptRunner
  to verify the data's level of fuzz.

  [scope]

  as the tests are flaky on armhf all the way back to trusty, this is
  needed for all releases.

  [other info]

  Fixed upstream in PR https://github.com/martinpitt/umockdev/pull/103

  Most of the changes are test case fixes, but there is one fix to
  source code to fix the ScriptRunning function that validates the level
  of fuzz in data, so this is not *only* a testcase fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1831467/+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 1831467] Re: test-umockdev tests flaky on armhf (and sometimes other archs)

2020-08-25 Thread Launchpad Bug Tracker
This bug was fixed in the package umockdev - 0.14.1-1ubuntu0.1

---
umockdev (0.14.1-1ubuntu0.1) focal; urgency=medium

  * d/p/lp1831467/0001-src-umockdev.vala-fix-ScriptRunner.op_write.patch,

d/p/lp1831467/0002-tests-read-expected-number-of-bytes-maybe-over-multi.patch,

d/p/lp1831467/0003-tests-test-umockdev-record.vala-add-slow_testbed_fac.patch,

d/p/lp1831467/0004-tests-test-umockdev.c-add-slow_testbed_factor-variab.patch,

d/p/lp1831467/0005-tests-test-umockdev-run.vala-add-slow_testbed_factor.patch,
d/p/lp1831467/0006-remove_SocketServer_ctrl-r_assert.patch,
d/rules, d/t/upstream:
- Fix various timing-related tests
  Fix ScriptRunner fuzz checking function
  (LP: #1831467)

 -- Dan Streetman   Thu, 06 Aug 2020 20:39:01
-0400

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

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

Title:
  test-umockdev tests flaky on armhf (and sometimes other archs)

Status in umockdev package in Ubuntu:
  Fix Released
Status in umockdev source package in Xenial:
  In Progress
Status in umockdev source package in Bionic:
  Fix Released
Status in umockdev source package in Focal:
  Fix Released
Status in umockdev source package in Groovy:
  Fix Released

Bug description:
  [impact]

  these tests fail intermittently, due to various timing issues, as well
  as an actual code bug in how data fuzz is calculated.

  it looks like the failures are mostly on armhf, but do happen less
  often on other archs.

  [test case]

  check the previous autopkgtest logs, e.g.
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic/cosmic/armhf/u/umockdev/20190601_015323_8f795@/log.gz

  [regression potential]

  any regression would likely result in incorrectly failing/passing 
autopkgtests, or in a incorrect pass or incorrect fail of the ScriptRunner
  to verify the data's level of fuzz.

  [scope]

  as the tests are flaky on armhf all the way back to trusty, this is
  needed for all releases.

  [other info]

  Fixed upstream in PR https://github.com/martinpitt/umockdev/pull/103

  Most of the changes are test case fixes, but there is one fix to
  source code to fix the ScriptRunning function that validates the level
  of fuzz in data, so this is not *only* a testcase fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/umockdev/+bug/1831467/+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 1659719] Re: ssh can't call a binary from a snap without the full path

2020-08-25 Thread Brian Murray
If kopanocore is known to be flaky on armhf please add a hint for it to
https://code.launchpad.net/~ubuntu-sru/britney/hints-ubuntu-focal/.

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

Title:
  ssh can't call a binary from a snap without the full path

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  New
Status in openssh source package in Xenial:
  New
Status in pam source package in Xenial:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in openssh source package in Bionic:
  New
Status in pam source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Focal:
  New
Status in openssh source package in Focal:
  New
Status in pam source package in Focal:
  Fix Committed
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  Fix Released
Status in openssh package in Debian:
  New

Bug description:
  [impact]
  ssh can't call a binary from a snap, it will only work using the full path.

  [test case]
  Create a container. Install the go snap (and make sure golang-go is not 
installed). Run "ssh  go version" and check the binary is found.

  [regression potential]
  It's a pam change an they are always a bit scary but the code follows the 
existing pattern for updating PATH in /etc/environment and has been tested in 
groovy.

  [original description]

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659719/+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 257135] Re: notify-send(1) can't replace an existing notification

2020-08-25 Thread sezanzeb
Yes, please deploy the patch if it works

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

Title:
  notify-send(1) can't replace an existing notification

Status in libnotify package in Ubuntu:
  Confirmed
Status in libnotify package in Debian:
  New

Bug description:
  Binary package hint: libnotify-bin

  Ubuntu 8.04, libnotify-bin 0.4.4-3build1.

  notify-send(1) is very useful but it doesn't tell me the notification
  ID that's been created, nor does it let me specify that to replace an
  earlier notification.  See http://www.galago-
  project.org/specs/notification/0.9/x408.html#command-notify, in
  particular the replaces_id parameter and the return value.

  I'd like to be able to use it something like

  id=$(notify-send --show-id foo)
  sleep 60
  notify-send --replace $id bar

  This would be great for long-running shell scripts that are monitoring
  something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/257135/+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 1659719] Re: ssh can't call a binary from a snap without the full path

2020-08-25 Thread Launchpad Bug Tracker
This bug was fixed in the package pam - 1.1.8-3.6ubuntu2.18.04.2

---
pam (1.1.8-3.6ubuntu2.18.04.2) bionic; urgency=medium

  * debian/libpam-modules.postinst: Add /snap/bin to $PATH in
/etc/environment. (LP: #1659719)

 -- Michael Hudson-Doyle   Wed, 22 Jul 2020
11:40:59 +1200

** Changed in: pam (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  ssh can't call a binary from a snap without the full path

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  New
Status in openssh source package in Xenial:
  New
Status in pam source package in Xenial:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in openssh source package in Bionic:
  New
Status in pam source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Focal:
  New
Status in openssh source package in Focal:
  New
Status in pam source package in Focal:
  Fix Committed
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  Fix Released
Status in openssh package in Debian:
  New

Bug description:
  [impact]
  ssh can't call a binary from a snap, it will only work using the full path.

  [test case]
  Create a container. Install the go snap (and make sure golang-go is not 
installed). Run "ssh  go version" and check the binary is found.

  [regression potential]
  It's a pam change an they are always a bit scary but the code follows the 
existing pattern for updating PATH in /etc/environment and has been tested in 
groovy.

  [original description]

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659719/+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 1659719] Update Released

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

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

Title:
  ssh can't call a binary from a snap without the full path

Status in Snappy:
  Fix Committed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in openssh package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  New
Status in openssh source package in Xenial:
  New
Status in pam source package in Xenial:
  New
Status in livecd-rootfs source package in Bionic:
  New
Status in openssh source package in Bionic:
  New
Status in pam source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Focal:
  New
Status in openssh source package in Focal:
  New
Status in pam source package in Focal:
  Fix Committed
Status in livecd-rootfs source package in Groovy:
  Fix Released
Status in openssh source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  Fix Released
Status in openssh package in Debian:
  New

Bug description:
  [impact]
  ssh can't call a binary from a snap, it will only work using the full path.

  [test case]
  Create a container. Install the go snap (and make sure golang-go is not 
installed). Run "ssh  go version" and check the binary is found.

  [regression potential]
  It's a pam change an they are always a bit scary but the code follows the 
existing pattern for updating PATH in /etc/environment and has been tested in 
groovy.

  [original description]

  Let's say I have the hello snap installed in 192.168.122.24. Then:

  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 hello
  elopio@192.168.122.24's password:
  bash: hello: command not found
  elopio@ubuntu-xenial:~/mosh$ ssh 192.168.122.24 /snap/bin/hello
  elopio@192.168.122.24's password:
  Hello, world!

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1659719/+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 1891208] Re: Removable storage device not detected as block device

2020-08-25 Thread Dan Streetman
*** This bug is a duplicate of bug 1856608 ***
https://bugs.launchpad.net/bugs/1856608

this appears to be dup of bug 1856608

** This bug has been marked a duplicate of bug 1856608
   [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?

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

Title:
  Removable storage device not detected as block device

Status in systemd package in Ubuntu:
  New

Bug description:
  my usb 3.1 devices not mount on my ubuntu 20.04.1 and sometime mound very 
late please fix it
  Linux shadow 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.2
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.snapd.rules 70-snap.canonical-livepatch.rules
  Date: Tue Aug 11 19:59:16 2020
  GvfsMonitorError:
   This tool has been deprecated, use 'gio mount' instead.
   See 'gio help mount' for more info.
  GvfsMonitorLog: Monitoring events. Press Ctrl+C to quit.
  HotplugNewDevices: /dev/sdd1 /dev/sdd
  HotplugNewMounts:
   
  InstallationDate: Installed on 2020-08-11 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Inspiron 7520
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=e82ab6f9-f116-4231-80de-2f81fde3e5d6 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  Symptom: storage
  Title: Removable storage device not detected as block device
  UdisksMonitorLog:
   Monitoring the udisks daemon. Press Ctrl+C to exit.
   19:59:31.995: The udisks-daemon is running (name-owner :1.10).
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/17/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0PXH02
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/17/2018:svnDellInc.:pnInspiron7520:pvrA14:rvnDellInc.:rn0PXH02:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Inspiron 7520
  dmi.product.sku: Inspiron 7520
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1891208/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-08-25 Thread Christian Ehrhardt 
[16:34]  seb128, cpaelzer ahasenack sorry, i was out and apparently 
forgot setting that in my email. the last systemd upload should fix everything 
except for the livecd-rootfs revert that made fstab in lxd images invalide
[16:45]  rbalint: " the last systemd upload" means groovy I guess, 
what about focal?
[16:47]  cpaelzer, sru-s are usually prepared by ddstreet, but i guess 
you mean the flakiness
[16:49]  cpaelzer, as i look at the last runs the latest focal systemd 
upload got flakier without a change in systemd so it may be an infra issue or 
needs more investigation
[16:50]  rbalint: do you want a new bug about it for you and ddstreet 
then?
[16:50]  to focus the discussion in one place I mean
[16:50]  cpaelzer, LP: #1892358 is not open against focal so i think 
just adding focal would be enough

Task added

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

** Also affects: glib2.0 (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

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

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

** No longer affects: qemu (Ubuntu Focal)

** No longer affects: kbd (Ubuntu Focal)

** No longer affects: ntpsec (Ubuntu Focal)

** No longer affects: glib2.0 (Ubuntu Focal)

** No longer affects: iputils (Ubuntu Focal)

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in iputils package in Ubuntu:
  Confirmed
Status in kbd package in Ubuntu:
  Confirmed
Status in ntpsec package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Focal:
  New

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 
F.B...FFF.FF..F..F.FFF.F
  logind (F  2% S  0% B  

[Touch-packages] [Bug 1892798] Re: eliminating resolvconf/openresolv dependencies

2020-08-25 Thread Dimitri John Ledkov
wireguard package => please feed DNS data direct to systemd-resolved
using either dbus or the cli.

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

Title:
  eliminating resolvconf/openresolv dependencies

Status in systemd package in Ubuntu:
  Won't Fix
Status in wireguard package in Ubuntu:
  Confirmed

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1892798] Re: eliminating resolvconf/openresolv dependencies

2020-08-25 Thread Dimitri John Ledkov
In ubuntu everything should feed DNS information direct into resolved whenever 
possible.
We are working on improving it, for example in groovy isc-dhcp-client & 
ifupdown started to do that too.

Unfortunately systemd's resolved's resolvctl is not compatible with
Debian's/Ubuntu's historical resolvconf.

Specifically Debian/Ubuntu has a lot of $interface.$suffix where $suffix
is arbitrary, such syntax is widely used and not supported by systemd.

So for the time being it is not possible to switch /sbin/resolvconf to
be the one provided by systemd.

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Won't Fix

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

Title:
  eliminating resolvconf/openresolv dependencies

Status in systemd package in Ubuntu:
  Won't Fix
Status in wireguard package in Ubuntu:
  Confirmed

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1892455] Re: [MIR] libselinux1

2020-08-25 Thread Christian Ehrhardt 
** Changed in: libselinux (Ubuntu)
   Status: New => Incomplete

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

Title:
  [MIR] libselinux1

Status in libselinux package in Ubuntu:
  Incomplete

Bug description:
  Many applications have Flatpak integration using libflatpak. The
  Ubuntu desktop team would like libflatpak in main so we can easily
  build such applications (LP: #1812456). libselinux is a dependency of
  this, so it would also need to be in main. We don't need SELinux
  functionality, and do not expect any other SELinux packages to be
  installed by default.

  Availability
  
  In Universe, builds for all architectures and in sync with Debian.

  Rationale
  =
  Required for libostree-1-1 being in main (LP: #1892454)

  Security
  
  This will need a Security review.

  Quality Assurance
  =
  Should be subscribed to by Ubuntu Desktop Bugs.

  Contains a single .so and doesn't have any debconf prompts. Package is
  maintained in Debian. No major bugs in Debian or Ubuntu.

  UI Standards
  
  N/A

  Dependencies
  
  All in main.

  Standards Compliance
  
  Package uses standards version 4.5.0.

  Maintenance
  ===
  Actively developed upstream https://github.com/SELinuxProject/selinux.
  Packages actively maintained in Debian.

  Security Checks
  ===
  41 CVEs found in http://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=selinux, but 
they seem to relate to actual SELinux functionality, not issues in libselinux.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libselinux/+bug/1892455/+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 1892358] Re: autopkgtest success rate dropped inhibiting proposed migration

2020-08-25 Thread Balint Reczey
@paelzer The fstab bug is LP: #1877078, I'm waiting for @vorlon's
comment's about what his plan is after his revert.

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

Title:
  autopkgtest success rate dropped inhibiting proposed migration

Status in glib2.0 package in Ubuntu:
  Confirmed
Status in iputils package in Ubuntu:
  Confirmed
Status in kbd package in Ubuntu:
  Confirmed
Status in ntpsec package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  we had such cases in the past like bug 1817721 for bionic and maybe bug 
1892130 is about the same as well. There were more but I didn't want to search 
for all of them - what I checked is that there are no open ones clearly 
pointing out the recent further drop in already flaky subtests.

  In particular the tests "tests-in-lxd" and "systemd-fsckd" were known
  to be flaky before, but got even worse.

  Here stats of the last 40 runs, it might be a coincidences that this
  is after 246-2ubuntu1 landed. Could as well be any other change

  groovy
amd64
  tests-in-lxd   (F 42% S  0% B 10% => P 45%/) 
BFFFBFF.B.F.F...FBF
  build-login(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  unit-config(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  networkd-testpy(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-and-services  (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  boot-smoke (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  logind (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  storage(F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  upstream   (F 35% S  0% B 10% => P 52%/) 
..FFB.FFF.FFBFF.B.F.F..FFBF
  udev   (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
  systemd-fsckd  (F 37% S  0% B 10% => P 50%/) 
BFFFB.FF...FB.F..B.
  root-unittests (F  0% S  0% B 10% => P 87%/) 
B...B...BB.
ppc64el
  tests-in-lxd   (F 25% S  0% B  0% => P 75%/) 
FFFFF.F.
  systemd-fsckd  (F 35% S  0% B  0% => P 65%/) 
FFF...FFFFF.F..F
  root-unittests (F  2% S  0% B  0% => P 97%/) 
..F.
s390x
  tests-in-lxd   (F 52% S  0% B  0% => P 47%/) 
FFF.FFF.FF....F.
  timedated  (F  2% S  0% B  0% => P 97%/) 
...F
  upstream   (F 17% S  0% B  0% => P 82%/) 
.F..F.F.FFF...F.
  systemd-fsckd  (F 32% S  0% B  0% => P 67%/) 
FFF..FF..F.FF..F
  root-unittests (F 10% S  0% B  0% => P 90%/) 
FFF...F.
arm64
  tests-in-lxd   (F 40% S  0% B  2% => P 57%/) 
F.B...FFF.FF..F..F.FFF.F
  logind (F  2% S  0% B  2% => P 95%/) 
..B...F.
  upstream   (F 22% S  0% B  2% => P 75%/) 
...F.FB.F.F.F..FFF.F
  root-unittests (F 12% S  0% B  2% => P 85%/) 
..B.F...F.FF...F

  (I'm sure LP will make this unreadable, but is is nice in monospace)

  Whatever the root cause is - the success rate of these has reduced so
  much that the (even formerly questionable) practice of retry-until-
  success won't work anymore.

  
  I have run the two tests in a local VM and systemd-fsckd works there while 
tests-in-lxd seems to trip over the old flaky fellow being "boot-and-services".

  We had the discussion in the past, but I think I need to again bring
  up the suggestion to skip "tests-in-lxd" and "systemd-fsckd" until
  they are on reasonable success rates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1892358/+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 1877078] Re: Please ship empty /etc/fstab in LXD images

2020-08-25 Thread Balint Reczey
@vorlon What is your plan regarding this fix? The revert may have helped
MAAS, but broke all LXD instances. IMO if MAAS relied on having a broken
fstab then MAAS should be fixed and not LXD images should be broken, so
I'd prefer having this fix in again. Maybe with /etc/fstab as an empty
file which is not particularly beautiful, but not invalid at least.

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

Title:
  Please ship empty /etc/fstab in LXD images

Status in livecd-rootfs package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Systemd boots degraded because of the invalid content of /etc/fstab:

  $ lxc shell gg-test 
  root@gg-test:~# systemctl is-system-running 
  degraded
  root@gg-test:~# systemctl list-units --failed 
UNIT   LOAD   ACTIVE SUBDESCRIPTION 

  ● systemd-remount-fs.service loaded failed failed Remount Root and Kernel 
File Systems

  LOAD   = Reflects whether the unit definition was properly loaded.
  ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
  SUB= The low-level unit activation state, values depend on unit type.

  1 loaded units listed.
  root@gg-test:~# cat /etc/fstab 
  LABEL=cloudimg-rootfs /ext4   defaults0 0
  root@gg-test:~# echo "" > /etc/fstab 
  root@gg-test:~# reboot

  Session terminated, killing shell... ...killed.
  rbalint@yogi:~$ lxc shell gg-test 
  root@gg-test:~# systemctl is-system-running 
  running
  root@gg-test:~# systemctl list-units --failed 
UNIT LOAD ACTIVE SUB DESCRIPTION
  0 loaded units listed.

  
  Not shipping is also fixing the issue, but some programs (such as systemd 
autopkgtes) reads fstab and a missing fstab should be special-cased, thus that 
would cause more breakages.

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

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


Re: [Touch-packages] [Bug 1798369] Re: Reinstall Ubuntu (with preserving existing data) shows error message due to "Could not get lock /target/var/cache/apt/archives/lock"

2020-08-25 Thread Ronaldo Garry Müller
OK.
Thanks!
RGMüller

Em seg., 24 de ago. de 2020 às 17:40, Brian Murray <
1798...@bugs.launchpad.net> escreveu:

> ** Tags added: restore-new-distro
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1884686).
> https://bugs.launchpad.net/bugs/1798369
>
> Title:
>   Reinstall Ubuntu (with preserving existing data) shows error message
>   due to "Could not get lock /target/var/cache/apt/archives/lock"
>
> Status in APT:
>   New
> Status in ubiquity:
>   New
> Status in apt package in Ubuntu:
>   Invalid
> Status in ubiquity package in Ubuntu:
>   Confirmed
> Status in apt source package in Eoan:
>   Invalid
> Status in ubiquity source package in Eoan:
>   Won't Fix
>
> Bug description:
>   When trying to reinstall an existing Ubuntu cosmic installation using
>   latest 18.10 desktop images, the install shows an error dialog around
>   the end of the installation with an "Error restoring installed
>   applications". Looking at the syslog such a traceback can be seen:
>
>   apt_pkg.Error: E:Could not get lock
>   /target/var/cache/apt/archives/lock - open (11: Resource temporarily
>   unavailable), E:Unable to lock directory
>   /target/var/cache/apt/archives/
>
>   After reproducing this on a live session, after chrooting into /target
>   indeed any apt-get install operations result in the same lock-file
>   error. The whole syslog of the reinstall attached to the bug.
>
>   Test case:
>* Download latest cosmic image
>* Install cosmic on the whole disk (can be on a VM)
>* (optional) Boot into the system and leave a file in the home
> directory (to leave a trace, just in case)
>* Reboot and install cosmic using the first option in ubiquity:
> Reinstall Ubuntu
>* Finish configuration
>
>   The install itself doesn't fail, but around the end of the
>   installation process the error dialog appears. System is still
>   bootable but left with old packages.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/apt/+bug/1798369/+subscriptions
>

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

Title:
  Reinstall Ubuntu (with preserving existing data) shows error message
  due to "Could not get lock /target/var/cache/apt/archives/lock"

Status in APT:
  New
Status in ubiquity:
  New
Status in apt package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Confirmed
Status in apt source package in Eoan:
  Invalid
Status in ubiquity source package in Eoan:
  Won't Fix

Bug description:
  When trying to reinstall an existing Ubuntu cosmic installation using
  latest 18.10 desktop images, the install shows an error dialog around
  the end of the installation with an "Error restoring installed
  applications". Looking at the syslog such a traceback can be seen:

  apt_pkg.Error: E:Could not get lock
  /target/var/cache/apt/archives/lock - open (11: Resource temporarily
  unavailable), E:Unable to lock directory
  /target/var/cache/apt/archives/

  After reproducing this on a live session, after chrooting into /target
  indeed any apt-get install operations result in the same lock-file
  error. The whole syslog of the reinstall attached to the bug.

  Test case:
   * Download latest cosmic image
   * Install cosmic on the whole disk (can be on a VM)
   * (optional) Boot into the system and leave a file in the home directory (to 
leave a trace, just in case)
   * Reboot and install cosmic using the first option in ubiquity: Reinstall 
Ubuntu
   * Finish configuration

  The install itself doesn't fail, but around the end of the
  installation process the error dialog appears. System is still
  bootable but left with old packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apt/+bug/1798369/+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 1869759] Re: [amdgpu] Opengl or vulkan or mesa bug that causes textures to glitch when mipmapping or trilinear/bilinear filtering is enabled

2020-08-25 Thread AS
** Changed in: mesa (Ubuntu)
   Status: New => Fix Released

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

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
   Status: New => Fix Released

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

Title:
  [amdgpu] Opengl or vulkan or mesa bug that causes textures to glitch
  when mipmapping or trilinear/bilinear filtering is enabled

Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Fix Released

Bug description:
  Textures are glitched (almost like they are cut up and repeated) when
  mipmapping or trilinear/bilinear filtering is enabled. Workaround is
  to disable both.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 30 12:03:39 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c4) (prog-if 
00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Picasso [1025:134f]
  InstallationDate: Installed on 2019-11-04 (147 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Acer Aspire A515-43
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic 
root=UUID=a44eb2b0-d036-44b7-9c90-d0a427ecd008 ro quiet splash 
resume=/dev/nvme0n1p5 resume_offset=15261696 vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2019
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.06
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Grumpy_PK
  dmi.board.vendor: PK
  dmi.board.version: V1.06
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.06
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.06:bd09/26/2019:svnAcer:pnAspireA515-43:pvrV1.06:rvnPK:rnGrumpy_PK:rvrV1.06:cvnAcer:ct10:cvrV1.06:
  dmi.product.family: Aspire 5
  dmi.product.name: Aspire A515-43
  dmi.product.sku: 
  dmi.product.version: V1.06
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

2020-08-25 Thread Ubuntu Foundations Team Bug Bot
The attachment "network-manager_1.22.10-1ubuntu2.2.debdiff" seems to be
a debdiff.  The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff.  If
the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

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

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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 1892847] Re: Xorg freeze

2020-08-25 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I plug a network adapter to my pc, it's TP-Link, i connect to a wifi, then i 
start sharing connection using hostspot (using my pc network card), after maybe 
1h, the screen freeze and everything stop, i had to restart it using the power 
button.
  After that i did the same thing, everything was ok, than i tried to write 
ifconfig, nothing happen, the settings freeze, and when i unplug the adabter 
the screen freeze and i had to restart it using the power button.
  and even when i just use my network card, it freeze sometime, i don't know 
why.
  yesterday it wrote (failed to evaluate _DSM), i searched about it and i 
didn't understand.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug 25 10:39:45 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: fwts-efi-runtime-dkms, 20.03.00, 5.4.0-42-generic, x86_64: 
installed (WARNING! Diff between built and installed module!)
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Within the last few days
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Toshiba Corporation 3rd Gen Core processor Graphics Controller 
[1179:fa33]
 Subsystem: Toshiba Corporation GeForce 710M [1179:fa33]
  InstallationDate: Installed on 2020-08-02 (22 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: TOSHIBA SATELLITE C55-A-1UV
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=93843777-b112-4ce6-81dc-fb6cddf7e1f3 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/22/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: PT10F
  dmi.board.vendor: Intel
  dmi.board.version: Type2 - Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: OEM Chassis Manufacturer
  dmi.chassis.version: OEM Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.30:bd11/22/2013:svnTOSHIBA:pnSATELLITEC55-A-1UV:pvrPSCGCE-02M00KG4:rvnIntel:rnPT10F:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
  dmi.product.family: Type1Family
  dmi.product.name: SATELLITE C55-A-1UV
  dmi.product.sku: PSCGCE
  dmi.product.version: PSCGCE-02M00KG4
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1892847/+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 1892847] [NEW] Xorg freeze

2020-08-25 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I plug a network adapter to my pc, it's TP-Link, i connect to a wifi, then i 
start sharing connection using hostspot (using my pc network card), after maybe 
1h, the screen freeze and everything stop, i had to restart it using the power 
button.
After that i did the same thing, everything was ok, than i tried to write 
ifconfig, nothing happen, the settings freeze, and when i unplug the adabter 
the screen freeze and i had to restart it using the power button.
and even when i just use my network card, it freeze sometime, i don't know why.
yesterday it wrote (failed to evaluate _DSM), i searched about it and i didn't 
understand.

Thank you.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 25 10:39:45 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: fwts-efi-runtime-dkms, 20.03.00, 5.4.0-42-generic, x86_64: 
installed (WARNING! Diff between built and installed module!)
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last few days
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Toshiba Corporation 3rd Gen Core processor Graphics Controller 
[1179:fa33]
   Subsystem: Toshiba Corporation GeForce 710M [1179:fa33]
InstallationDate: Installed on 2020-08-02 (22 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: TOSHIBA SATELLITE C55-A-1UV
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=93843777-b112-4ce6-81dc-fb6cddf7e1f3 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/22/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: 1.30
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: PT10F
dmi.board.vendor: Intel
dmi.board.version: Type2 - Board Version
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: OEM Chassis Manufacturer
dmi.chassis.version: OEM Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvr1.30:bd11/22/2013:svnTOSHIBA:pnSATELLITEC55-A-1UV:pvrPSCGCE-02M00KG4:rvnIntel:rnPT10F:rvrType2-BoardVersion:cvnOEMChassisManufacturer:ct10:cvrOEMChassisVersion:
dmi.product.family: Type1Family
dmi.product.name: SATELLITE C55-A-1UV
dmi.product.sku: PSCGCE
dmi.product.version: PSCGCE-02M00KG4
dmi.sys.vendor: TOSHIBA
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal freeze ubuntu
-- 
Xorg freeze
https://bugs.launchpad.net/bugs/1892847
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

-- 
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 1891196] Re: FTBFS because of porefs=noline, wrap is unrecognized

2020-08-25 Thread Lukas Märdian
sensible-utils 0.0.13 migrated from -proposed

** Changed in: sensible-utils (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  FTBFS because of porefs=noline,wrap is unrecognized

Status in sensible-utils package in Ubuntu:
  Fix Released
Status in sensible-utils package in Debian:
  Fix Released

Bug description:
  THe porefs value needs to be changed from 'noline,wrap' to 'noline'.

  This will be solved with 'sensible-utils 0.0.13', currently in Debian
  experimental.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sensible-utils/+bug/1891196/+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 1620459] Re: package bash-completion 1:2.1-4ubuntu0.2 failed to install/upgrade: trying to overwrite '/usr/share/bash-completion/completions/apt', which is also in package apt 1.

2020-08-25 Thread Julian Andres Klode
Trusty is EOL. The system in question seems to be in an unsupported
state. The apt version is old, and the upgrade seems to have been
attempted with apt instead of do-release-upgrade (as do-release-upgrade
would tell you to upgrade first).

apt in trusty does not contain the bash completion, and apt in xenial
has appropriate Replaces on the bash-completion that is causing the
conflict here.

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

** Changed in: bash-completion (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  package bash-completion 1:2.1-4ubuntu0.2 failed to install/upgrade:
  trying to overwrite '/usr/share/bash-completion/completions/apt',
  which is also in package apt 1.0.1ubuntu2.14

Status in apt package in Ubuntu:
  Invalid
Status in bash-completion package in Ubuntu:
  Incomplete

Bug description:
  I updated my system from 14.XX LTS to 16.04 LTS and now my updates
  will not finish

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bash-completion 1:2.1-4ubuntu0.2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Mon Sep  5 23:17:46 2016
  DuplicateSignature:
   package:bash-completion:1:2.1-4ubuntu0.2
   Unpacking bash-completion (1:2.1-4.2ubuntu1.1) over (1:2.1-4ubuntu0.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/bash-completion_1%3a2.1-4.2ubuntu1.1_all.deb (--unpack):
trying to overwrite '/usr/share/bash-completion/completions/apt', which is 
also in package apt 1.0.1ubuntu2.14
  ErrorMessage: trying to overwrite 
'/usr/share/bash-completion/completions/apt', which is also in package apt 
1.0.1ubuntu2.14
  InstallationDate: Installed on 2015-04-23 (501 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.14
  SourcePackage: bash-completion
  Title: package bash-completion 1:2.1-4ubuntu0.2 failed to install/upgrade: 
trying to overwrite '/usr/share/bash-completion/completions/apt', which is also 
in package apt 1.0.1ubuntu2.14
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1620459/+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 1892814] Re: pulseaudio very unstable

2020-08-25 Thread Daniel van Vugt
Please make a separate bug for each issue using the 'ubuntu-bug'
command. Please also reword this bug into a single issue and use the
'apport-collect' command to attach more information about the system.


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

** Tags added: focal

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

Title:
  pulseaudio very unstable

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Pulseaudio has been super unstable since ubuntu 20.04. 
  bluetooth has multiple connectivity issues which sometimes can only be 
resolved by unpairing and then pairing again.
  Microphones randomly stop working until changing the active microphone 
multiple times. Today my mic stopped working 3 times.
  Sometimes cannot switch bluetooth headset profiles. Or it says that it 
switched it but when you click on a different tab and go back, it reverts to 
the old setting. 

  I see some warnings/errors in the logs that could be related:
  gsd-media-keys[2948]: Unable to get default sink
  gsd-media-keys[2948]: Unable to get default source

  kernel: Bluetooth: hci0: SCO packet for unknown connection handle 65

  pulseaudio[2489]: q overrun, queuing locally

  please see the attached log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+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 1892814] Re: pulseaudio very unstable

2020-08-25 Thread Sebastien Bacher
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 1892814

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.

Reassigning also to pulseaudio since that's the problematic component,
it would be worth also reporting upstream on
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues

** Package changed: gnome-settings-daemon (Ubuntu) => pulseaudio
(Ubuntu)

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

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

Title:
  pulseaudio very unstable

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio has been super unstable since ubuntu 20.04. 
  bluetooth has multiple connectivity issues which sometimes can only be 
resolved by unpairing and then pairing again.
  Microphones randomly stop working until changing the active microphone 
multiple times. Today my mic stopped working 3 times.
  Sometimes cannot switch bluetooth headset profiles. Or it says that it 
switched it but when you click on a different tab and go back, it reverts to 
the old setting. 

  I see some warnings/errors in the logs that could be related:
  gsd-media-keys[2948]: Unable to get default sink
  gsd-media-keys[2948]: Unable to get default source

  kernel: Bluetooth: hci0: SCO packet for unknown connection handle 65

  pulseaudio[2489]: q overrun, queuing locally

  please see the attached log.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1892814/+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 1892814] [NEW] pulseaudio very unstable

2020-08-25 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Pulseaudio has been super unstable since ubuntu 20.04. 
bluetooth has multiple connectivity issues which sometimes can only be resolved 
by unpairing and then pairing again.
Microphones randomly stop working until changing the active microphone multiple 
times. Today my mic stopped working 3 times.
Sometimes cannot switch bluetooth headset profiles. Or it says that it switched 
it but when you click on a different tab and go back, it reverts to the old 
setting. 

I see some warnings/errors in the logs that could be related:
gsd-media-keys[2948]: Unable to get default sink
gsd-media-keys[2948]: Unable to get default source

kernel: Bluetooth: hci0: SCO packet for unknown connection handle 65

pulseaudio[2489]: q overrun, queuing locally

please see the attached log.

** Affects: pulseaudio (Ubuntu)
 Importance: Low
 Status: Confirmed

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

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


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

2020-08-25 Thread Daniel van Vugt
There is no update available right now. And yes you can just delete that
folder because it gets recreated automatically.

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

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

Status in PulseAudio:
  Fix Released
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:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1844879] Re: Behaviour change in systemd 243 breaks libvirt autopkgtest

2020-08-25 Thread Christian Ehrhardt 
This no more affects libvirt, marking it as such to not show up in
excuses.

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

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

Title:
  Behaviour change in systemd 243 breaks libvirt autopkgtest

Status in systemd:
  New
Status in libvirt package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  With systemd 243 libvirt autopkgtest starts failing:

  http://autopkgtest.ubuntu.com/packages/libv/libvirt/eoan/amd64

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-eoan/eoan/amd64/libv/libvirt/20190921_104518_69667@/log.gz
  ...
  + virt-xml-validate debian/tests/smoke-lxc.xml
  debian/tests/smoke-lxc.xml validates
  + virsh define debian/tests/smoke-lxc.xml
  Domain sl defined from debian/tests/smoke-lxc.xml

  + rm -f /var/log/libvirt/lxc/sl.log
  + virsh start sl
  Domain sl started

  + grep -qs starting up /var/log/libvirt/lxc/sl.log
  + check_domain
  + grep/bin/ls

  
  Domain sl has been undefined

   -qs sl[[:space:]]\+running
  + virsh list
  + virsh lxc-enter-namespace --noseclabel sl /bin/ls /bin/ls
  + systemctl restart libvirtd
  + check_domain
  + grep -qs sl[[:space:]]\+running
  + virsh list
  + cleanup
  + [ -z  ]
  + virsh destroy sl
  error: Failed to destroy domain sl
  error: Requested operation is not valid: domain is not running
  + true
  + virsh undefine sl
  + CLEANED_UP=1
  autopkgtest [10:41:05]: test smoke-lxc: ---]
  autopkgtest [10:41:07]: test smoke-lxc:  - - - - - - - - - - results - - - - 
- - - - - -
  smoke-lxcFAIL non-zero exit status 1
  ...

  The behaviour change is still present in systemd master
  (v243-112-g984b96aa7a)

  I can revert the change in systemd, but it also fixes an issue reported at 
upstream.
  I will take another look later, but wanted to document my findings.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1844879/+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 1892798] Re: eliminating resolvconf/openresolv dependencies

2020-08-25 Thread Jason A. Donenfeld
Thanks for bringing this to my attention. I believe your assessment is
correct. Do you know which Ubuntu first started using resolved? How far
back do we need to make changes?

There are two facets of this:

1) The Ubuntu systemd package should install the resolvconf
compatibility symlink. I have no idea why this isn't already the case,
and that seems like a bug that should be remedied ASAP. resolvconf(8) is
the standard interface for programs to interact with DNS, which is why
systemd provides it. Not providing it is super confusing.

2) The Recommends in the wireguard package should be adjusted.

I believe apw@ can handle (2). Somebody on the systemd team should
handle (1).

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

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

** Changed in: systemd (Ubuntu)
   Status: New => 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/1892798

Title:
  eliminating resolvconf/openresolv dependencies

Status in systemd package in Ubuntu:
  Confirmed
Status in wireguard package in Ubuntu:
  Confirmed

Bug description:
  By default Ubuntu now uses systemd to manage the nameservers in
  resolv.conf, so resolvconf and openresolv seem to be redundant.
  However, it appears that systemd's resolvectl is compatable with
  resolvconf style commands if symlinked as resolvconf.

  I'm not really sure how deb packaging works, but if it possible to
  check for the resolvconf command, and if not found just symlink
  /usr/bin/resolvectl to /usr/sbin/resolvconf then wg-quick will work
  without additional packages.

  See
  
https://manpages.ubuntu.com/manpages/focal/man1/resolvectl.1#compatibility%20with%20resolvconf(8)
  for more info.

  Apologies if there is a better place to direct this info.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1892798/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2020-08-25 Thread zwn
Same problem with Edifier TWS200:

Device 5C:C6:E9:C4:29:2F (public)
Name: EDIFIER TWS200 R
Alias: EDIFIER TWS200 R
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Serial Port   (1101--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Vendor specific   (eb03-d102-11e1-9b23-00025b00a5a5)


Only Handsfree available, no Headset.

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

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

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


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

2020-08-25 Thread Sujit Kumar
Hi Daniel! are you sure I can just delete that folder? Will Ubuntu
automatically download a later version?

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

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

Status in PulseAudio:
  Fix Released
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:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

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

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

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

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

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

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

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

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

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


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

2020-08-25 Thread Sujit Kumar
Can I not just update thee package using terminal?

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

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

Status in PulseAudio:
  Fix Released
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:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

2020-08-25 Thread Leon Liao
The patch was merged into debian network-manager repository
in 
https://salsa.debian.org/utopia-team/network-manager/-/commit/e7b44ef4c80907346ec7492a09c45277459924fc.

For Groovy, when network-manager version >= 1.26.2, this patch will be included.
For Focal, the network-manager (1.22.10) needs to carry on this patch.

Append the debdiff for focal.

** Patch added: "network-manager_1.22.10-1ubuntu2.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1891632/+attachment/5404329/+files/network-manager_1.22.10-1ubuntu2.2.debdiff

-- 
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 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

2020-08-25 Thread Shengyao Xue
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done-focal

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

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  ucm-substitute-OpenName.patch
  ucm-substitute-CardNumber.patch
  ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  ucm-substitute-device-modifier-names-too.patch
  ucm-substitute-device-strings-in-the-device-lists.patch
  ucm-substitute-component-sequence-string.patch
  ucm-substitute-verb-name-and-file-field.patch
  ucm-substitute-Comment-in-Transition-and-Device.patch
  ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch
  ucm-substitute-arguments-in-sequences-only-for-synta.patch
  ucm-shuffle-code-in-compound_merge.patch
  ucm-implement-CardIdByName-substitution.patch
  ucm-allow-to-ignore-errors-for-the-value-substitutio.patch
  

[Touch-packages] [Bug 1889217] Re: Make digital mic on the AMD Renoir machines work under gnome desktop

2020-08-25 Thread Shengyao Xue
-proposed package tested OK

installed a latest Ubuntu 20.04 image on a Lenovo ThinkPad T14s(AMD
Renoir) and installed the packages libasound2(1.2.2-2.1ubuntu2) and
pulseaudio(1.13.99.1-1ubuntu3.6) from focal-proposed.

the audio functions works fine.

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

Title:
  Make digital mic on the AMD Renoir machines work under gnome desktop

Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Committed
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Committed
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  On the LENOVO AMD Renoir machines, there is a digital mic directly
  connected to the APU instead of the codec, so there are two separate
  sound cards in the system, one is for analogue codec driven by hda
  driver, the other is for the dmic driven by ASoC acp driver.

  The current audio stack (pulseaudio + alsa-ucm-conf + alsa-lib) doesn't
  support this design yet, it could support all audio devices on the codec
  well, but it doesn't support that dmic well. In the gnome-control-center,
  the dmic becomes two input devices: analog input and multichannel input,
  and users can only record sound from analog input, the multichannel input
  can't function at all. Besides this issue, there is another issue, after
  users plug an external mic, the external mic can't replace the dmic
  automatically, this gives users a bad experience since this behaviour is
  different from the other audio designs.

  [Fix for pulseaudio]
  backport 3 patches:
  2 of them from upstream
  device-port: queue CARD CHANGE event before update default sink
  alsa: adjust ucm sink/source priority according to ports priority
  1 of them from a merge request:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/305

  [Fix for alsa-ucm-conf]
  backport 14 patches:
  11 of them from upstream:
  ucm-fix-wrong-If-in-sequence-in-HiFi-dual.conf.patch
  ucm2-add-initial-ucm.conf-for-the-latest-alsa-lib.patch
  sof-hda-dsp-don-t-fail-if-Auto-Mute-control-is-not-p.patch
  ucm.conf-add-support-for-the-kernel-module-name-tree.patch
  sof-hda-dsp-make-Headphone-Playback-Switch-condition.patch
  sof-soundwire-initial-UCM2-version.patch
  sof-soundwire-cleanups-recommended-by-the-ucm-valida.patch
  sof-soundwire-rewrite-for-syntax-3.patch
  HDA-Intel-add-support-for-AMD-acp-microphone-devices.patch
  Fix-invalid-Regex-Type-in-various-Condition-blocks.patch
  hda-hdmi-add-HDMI4-HDMI5-HDMI6-devices.patch
  3 of them from a merge request:
  https://github.com/alsa-project/alsa-ucm-conf/pull/41

  [Fix for alsa-lib]
  backport 47 patches from upstream:
  Enabled-extended-namehints-in-alsa.conf.patch
  conf-add-snd_config_is_array-function.patch
  topology-use-snd_config_is_array-function.patch
  ucm-merge-the-array-items-from-the-condition-blocks.patch
  ucm-parse-SectionOnce-section-in-the-master-UCM-conf.patch
  ucm-execute-SectionDefaults-lately-when-the-first-ve.patch
  ucm-handle-set-_once-command.patch
  ucm-handle-set-_defaults-command.patch
  ucm-initialize-mgr-once_list.patch
  ucm-fix-SectionOnce-comment.patch
  ucm-fix-compilation-error-in-set_defaults_user.patch
  ucm-rename-SectionOnce-to-BootSequence.patch
  ucm-rename-_once-command-to-_boot-command.patch
  ucm-configuration-implement-in-place-Include.patch
  ucm-configuration-substitute-ConfDir-and-ConfTopDir.patch
  ucm-config-substitute-File-string-to-allow-variables.patch
  ucm-configuration-allow-to-define-the-configuration-.patch
  ucm-configuration-add-DefineRegex.patch
  ucm-substitute-arguments-in-sequences.patch
  ucm-allow-syntax-version-3.patch
  ucm-config-change-the-in-place-include-evaluation-or.patch
  ucm-allow-to-specify-the-toplevel-directory-using-as.patch
  ucm-substitute-also-value-strings.patch
  ucm-handle-strict-prefix-correctly-for-the-UCM-card-.patch
  ucm-String-condition-implement-Empty.patch
  ucm-Define-DefineRegex-is-supported-in-Syntax-3.patch
  ucm-substitute-OpenName.patch
  ucm-substitute-CardNumber.patch
  ucm-implement-the-toplevel-ucm-configuration-file-pa.patch
  ucm-substitute-device-modifier-names-too.patch
  ucm-substitute-device-strings-in-the-device-lists.patch
  ucm-substitute-component-sequence-string.patch
  ucm-substitute-verb-name-and-file-field.patch
  ucm-substitute-Comment-in-Transition-and-Device.patch
  ucm-substitute-RenameDevice-and-DeleteDevice-lists.patch
  ucm-substitute-arguments-in-sequences-only-for-synta.patch
  

[Touch-packages] [Bug 1891632] Re: The network manager does not check the NM_SETTING_WIRELESS_WAKE_ON_WLAN_IGNORE bit

2020-08-25 Thread Leon Liao
** Also affects: oem-priority/focal
   Importance: Undecided
   Status: New

** No longer affects: oem-priority/focal

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/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 1866194] Re: External audio device shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker, or none at all.

2020-08-25 Thread Daniel van Vugt
But you don't need to wait for the update. You can fix it yourself by
removing:

  ~/.config/pulse

and restarting. If that doesn't work then please open a NEW bug and
mention it's different to this one.

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

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

Status in PulseAudio:
  Fix Released
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:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

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

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

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

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

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

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

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

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

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


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

2020-08-25 Thread Daniel van Vugt
No timeframe, but the fix is concretely queued up in the update *after*
the next update.

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

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

Status in PulseAudio:
  Fix Released
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:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

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

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

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

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

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

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

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

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

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


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

2020-08-25 Thread Sujit Kumar
I have the same issue. When will it be fixed?

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

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

Status in PulseAudio:
  Fix Released
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:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

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

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

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

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

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

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

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

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

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


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

2020-08-25 Thread Sujit Kumar
Like, when will the next milestone be 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/1866194

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

Status in PulseAudio:
  Fix Released
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:
  Ubuntu version: focal dev
  Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020
  Pulseaudio: 1:13.99.1-1ubuntu1
  Device CID: 201704-25503

  Steps to reproduce:

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

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1887977] Re: [boAt Rockerz 510] Bluetooth headset is not reconnecting automatically if disconnected in between

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

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

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

Title:
  [boAt Rockerz 510] Bluetooth headset is not reconnecting automatically
  if disconnected in between

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Some times Bluetooth headset is not reconnecting automatically if
  disconnected in between. I need to remove the bluetooth headset and
  again pair it, then it is connecting.

  1. Ubuntu Version - 20.04
  2. Software version - bluez Installed: 5.53-0ubuntu3
  3. Expected result : Every time when I restart the laptop or resume it the 
headset should connect automatically
  4. Issues Faced : Some times when I restart the laptop or resume the laptop, 
then eventhough headset is switched on bluetooth connection is not established. 
Instead if I remove the the headset from bluetooth list and again newly pair it 
with laptop then headset it connected. Verified the bluetooth head set by 
connecting it to mobile phone and other os like windows/mac os and it seems 
there is no issue with headset.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul 17 19:58:10 2020
  InstallationDate: Installed on 2020-05-04 (73 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0408:a060 Quanta Computer, Inc. HD Webcam
   Bus 001 Device 003: ID 8087:0aaa Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Nitro AN515-52
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic 
root=UUID=a609dea6-45d9-4ed8-8a46-ba56dae5a117 ro quiet splash
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/13/2018
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.19
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Freed_CFS
  dmi.board.vendor: CFL
  dmi.board.version: V1.19
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.19
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.19:bd07/13/2018:svnAcer:pnNitroAN515-52:pvrV1.19:rvnCFL:rnFreed_CFS:rvrV1.19:cvnAcer:ct10:cvrV1.19:
  dmi.product.family: Acer Nitro 5
  dmi.product.name: Nitro AN515-52
  dmi.product.sku: 
  dmi.product.version: V1.19
  dmi.sys.vendor: Acer
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 18:56:80:A6:CA:8D  ACL MTU: 1021:4  SCO MTU: 96:6
    UP RUNNING PSCAN
    RX bytes:16973 acl:0 sco:0 events:2752 errors:0
    TX bytes:678011 acl:0 sco:0 commands:2750 errors:0

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