[Touch-packages] [Bug 1913368] [NEW] Xorg freeze

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I have a Dell laptop with a Magic Trackpad 2. A couple of days ago my system 
crashed overnight and hung on reboot. Once I unplugged the trackpad, it came 
right up. If I attach the trackpad to the running system it does not recognize 
it.
I've been using this hardware configuration for months and haven't made any 
changes to my libinput configuration for at least a couple of months.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 26 23:23:45 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Dell HD Graphics 630 [1028:07a9]
InstallationDate: Installed on 2020-09-13 (135 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Dell Inc. Precision 3520
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic 
root=UUID=ff5fae3d-e88f-436d-8a84-d0a544463eb9 ro quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/07/2020
dmi.bios.release: 1.17
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.17.1
dmi.board.name: 0C7J6P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd01/07/2020:br1.17:svnDellInc.:pnPrecision3520:pvr:rvnDellInc.:rn0C7J6P:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 3520
dmi.product.sku: 07A9
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
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/1913368
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 1913356] Re: Windows flicker when resizing after update to 20.10

[Daniel van Vugt]

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

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

** Tags added: focal

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

Title:
  Windows flicker when resizing

Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Yesterday I updated to Ubuntu 20.10 (from 20.04 LTS) and immediately
  noticed an issue with windows flickering when I resize them.

  Here is a video demonstrating the issue: https://youtu.be/nNOoJWdDEes

  This did not happen in 20.04.

  Windows this has been noticed on include:

  - Software & Updates (as shown in video)
  - Tilix
  - KeePassXC

  Here is some information about my system:

  - OS: Ubuntu 20.10 x86_64 
  - Host: XPS 13 9370 
  - Kernel: 5.8.0-40-generic 
  - Shell: bash 5.0.17 
  - Resolution: 1920x1080 
  - DE: GNOME 3.38.2 
  - WM: Mutter 
  - WM Theme: Adwaita 
  - Theme: Yaru-dark [GTK2/3] 
  - Icons: Yaru [GTK2/3] 
  - CPU: Intel i7-8550U (8) @ 4.000GHz 
  - GPU: Intel UHD Graphics 620 
  - Memory: 6139MiB / 15725MiB 

  Please let me know if there's any further details or diagnostics that
  would be useful.

  Thank you.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu15
  ProcVersionSignature: Ubuntu 5.8.0-40.45-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  CurrentDmesg: Error: command ['pkexec', 'dmesg'] failed with exit code 126: 
Error executing command as another user: Request dismissed
  Date: Wed Jan 27 00:23:33 2021
  DistUpgraded: 2021-01-25 15:06:27,142 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:07e6]
  InstallationDate: Installed on 2018-02-01 (1090 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0489:e0a2 Foxconn / Hon Hai 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 7: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 7: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Dell Inc. XPS 13 9370
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic 
root=UUID=04d2ce0b-b5d2-4184-93fc-428c29d5e2fd ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to groovy on 2021-01-25 (1 days ago)
  dmi.bios.date: 05/25/2018
  dmi.bios.release: 1.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd05/25/2018:br1.4:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sun Dec 16 15:22:33 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5252 
   vendor SHP
  xserver.version: 2:1.18.4-0ubuntu0.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1913356/

[Touch-packages] [Bug 1913368] Re: Xorg freeze

[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/1913368

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a Dell laptop with a Magic Trackpad 2. A couple of days ago my system 
crashed overnight and hung on reboot. Once I unplugged the trackpad, it came 
right up. If I attach the trackpad to the running system it does not recognize 
it.
  I've been using this hardware configuration for months and haven't made any 
changes to my libinput configuration for at least a couple of months.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 26 23:23:45 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:07a9]
  InstallationDate: Installed on 2020-09-13 (135 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Precision 3520
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic 
root=UUID=ff5fae3d-e88f-436d-8a84-d0a544463eb9 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2020
  dmi.bios.release: 1.17
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.1
  dmi.board.name: 0C7J6P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd01/07/2020:br1.17:svnDellInc.:pnPrecision3520:pvr:rvnDellInc.:rn0C7J6P:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3520
  dmi.product.sku: 07A9
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  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/1913368/+subscriptions

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

[Touch-packages] [Bug 1913366] Re: Login screen freezes when xserver-xorg-video-openchrome is in use

[Daniel van Vugt]

Please try editing /etc/gdm3/custom.conf and change:

  #WaylandEnable=false

to

  WaylandEnable=false

Then reboot.

** Summary changed:

- Persiste problema con ubuntu 18.04 no reconoce monitor ni resolución óptima
+ Login screen freezes when xserver-xorg-video-openchrome is in use

** Package changed: xorg (Ubuntu) => xserver-xorg-video-openchrome
(Ubuntu)

** Changed in: xserver-xorg-video-openchrome (Ubuntu)
   Status: New => Incomplete

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

Title:
  Login screen freezes when xserver-xorg-video-openchrome is in use

Status in xserver-xorg-video-openchrome package in Ubuntu:
  Incomplete

Bug description:
  Tuve que reinstalar ubuntu 18.04 ya que no pude ingresar más al
  sistema operativo, ya que se quedaba congelado en el inicio, no me
  permitía ingresar la contraseña. Al hacerlo seguía presentando el
  mismo problema de baja resolución, volví a tratar de solucionarlo con
  sudo apt install xserver-xorg-video-openchrome y nuevamente se congeló
  el sistema. Me vi forzado a realizar una segunda reinstalación de
  Ubuntu y no he vuelto a intentar porque obviamente se corre el riesgo
  de que se quede colgada otra vez. Así que estoy tratando de trabajar
  con la baja resolución 640x480 especificada en el informe. La instale
  un escritorio cinamon y me informa al inicio que està trabajando sin
  aceleración de software lo cual puede afectar el rendimiento del
  equipo. Esta es la situación. Gracias por el interés demostrado en mi
  caso. Saludos.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78
  Uname: Linux 5.4.0-64-generic i686
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: i386
  CompositorRunning: None
  Date: Tue Jan 26 23:47:50 2021
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   VIA Technologies, Inc. CN896/VN896/P4M900 [Chrome 9 HC] [1106:3371] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Biostar Microtech Int'l Corp CN896/VN896/P4M900 [Chrome 9 HC] 
[1565:1207]
  InstallationDate: Installed on 2021-01-26 (0 days ago)
  InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release i386 
(20190805)
  MachineType: BIOSTAR Group P4M900-M7 FE
  ProcEnviron:
   LANGUAGE=es_VE:es
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=es_VE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=c6c9ee95-4dbf-4f30-b579-32cfe165d16e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/25/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: P4M900-M7 FE
  dmi.board.vendor: BIOSTAR Group
  dmi.board.version: Ver:1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: BIOSTAR Group
  dmi.chassis.version: P4M900-M7 FE
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd06/25/2008:svnBIOSTARGroup:pnP4M900-M7FE:pvrVer1.0:rvnBIOSTARGroup:rnP4M900-M7FE:rvrVer1.0:cvnBIOSTARGroup:ct3:cvrP4M900-M7FE:
  dmi.product.name: P4M900-M7 FE
  dmi.product.version: Ver:1.0
  dmi.sys.vendor: BIOSTAR Group
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1913366/+subscriptions

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

[Touch-packages] [Bug 1913368] Re: Xorg freeze

[Daniel van Vugt]

Thanks for the bug report.

Your kernel errors:

[32883.824222] pcieport :00:1c.0: AER: Corrected error received: 
:00:1c.0
[32883.824246] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, (Transmitter ID)
[32883.824254] pcieport :00:1c.0: AER:   device [8086:a111] error 
status/mask=1000/2000
[32883.824259] pcieport :00:1c.0: AER:[12] Timeout   
[32975.541566] pcieport :00:1c.0: AER: Corrected error received: 
:00:1c.0
[32975.541583] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, (Transmitter ID)
[32975.541592] pcieport :00:1c.0: AER:   device [8086:a111] error 
status/mask=1000/2000
[32975.541598] pcieport :00:1c.0: AER:[12] Timeout   
[32994.793110] pcieport :00:1c.0: AER: Corrected error received: 
:00:1c.0
[32994.793125] pcieport :00:1c.0: AER: PCIe Bus Error: severity=Corrected, 
type=Data Link Layer, (Transmitter ID)
[32994.793133] pcieport :00:1c.0: AER:   device [8086:a111] error 
status/mask=1000/2000
[32994.793139] pcieport :00:1c.0: AER:[12] Timeout   

remind me of bug 1912898.

Please try an older kernel series like: https://kernel.ubuntu.com
/~kernel-ppa/mainline/v5.4.92/

** Summary changed:

- Xorg freeze
+ System freeze

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

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

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

Title:
  System freeze

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell laptop with a Magic Trackpad 2. A couple of days ago my system 
crashed overnight and hung on reboot. Once I unplugged the trackpad, it came 
right up. If I attach the trackpad to the running system it does not recognize 
it.
  I've been using this hardware configuration for months and haven't made any 
changes to my libinput configuration for at least a couple of months.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-40.45~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 26 23:23:45 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 630 [1028:07a9]
  InstallationDate: Installed on 2020-09-13 (135 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Precision 3520
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-40-generic 
root=UUID=ff5fae3d-e88f-436d-8a84-d0a544463eb9 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2020
  dmi.bios.release: 1.17
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.17.1
  dmi.board.name: 0C7J6P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.17.1:bd01/07/2020:br1.17:svnDellInc.:pnPrecision3520:pvr:rvnDellInc.:rn0C7J6P:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 3520
  dmi.product.sku: 07A9
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  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/linux/+bug/1913368/+subscriptions

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

[Touch-packages] [Bug 1913400] [NEW] While I updating ModemManager to 1.14.2, there is no mobile broadband dop down menu in system state bar.

[Freedom]

Public bug reported:

While I updating ModemManager to 1.14.2, there is no mobile broadband dop down 
menu in system state bar.
I just can see mobile broadband in network in system settings menu

my step:
git clone -b 1.24.2 https://gitlab.freedesktop.org/mobile-broadband/libmbim
NOCONFIGURE=1 ./autogen.sh
./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu
make
sudo make install

git clone -b 1.26.4 https://gitlab.freedesktop.org/mobile-broadband/libqmi
NOCONFIGURE=1 ./autogen.sh
./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --enable-mbim-qmux 
--enable-collection=basic
make
sudo make install

git clone -b 1.14.2 https://gitlab.freedesktop.org/mobile-broadband/ModemManager
NOCONFIGURE=1 ./autogen.sh
./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --enable-gtk-doc 
--with-polkit=strict --with-suspend-resume=systemd 
--with-systemdsystemunitdir=/lib/systemd/systemmake
make
sudo make install


OS: ubuntu20.04
Module: SDX55
ModemManager:1.14.2
iusse: 1.No mobile broadband in system status bar drop-down menu.
   2.Every time I connect to the mobile broadband network in system 
settings menu, I need to add new connection.

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

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

Title:
  While I updating ModemManager to 1.14.2, there is no mobile broadband
  dop down menu  in system state bar.

Status in modemmanager package in Ubuntu:
  New

Bug description:
  While I updating ModemManager to 1.14.2, there is no mobile broadband dop 
down menu in system state bar.
  I just can see mobile broadband in network in system settings menu

  my step:
  git clone -b 1.24.2 https://gitlab.freedesktop.org/mobile-broadband/libmbim
  NOCONFIGURE=1 ./autogen.sh
  ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu
  make
  sudo make install

  git clone -b 1.26.4 https://gitlab.freedesktop.org/mobile-broadband/libqmi
  NOCONFIGURE=1 ./autogen.sh
  ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu 
--enable-mbim-qmux --enable-collection=basic
  make
  sudo make install

  git clone -b 1.14.2 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager
  NOCONFIGURE=1 ./autogen.sh
  ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --enable-gtk-doc 
--with-polkit=strict --with-suspend-resume=systemd 
--with-systemdsystemunitdir=/lib/systemd/systemmake
  make
  sudo make install

  
  OS: ubuntu20.04
  Module: SDX55
  ModemManager:1.14.2
  iusse: 1.No mobile broadband in system status bar drop-down menu.
 2.Every time I connect to the mobile broadband network in system 
settings menu, I need to add new connection.

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

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

[Touch-packages] [Bug 1913400] Re: While I updating ModemManager to 1.14.2, there is no mobile broadband dop down menu in system state bar.

[Freedom]

No mobile broadband in system status bar drop-down menu.

** Attachment added: "1.JPG"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1913400/+attachment/5457328/+files/1.JPG

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

Title:
  While I updating ModemManager to 1.14.2, there is no mobile broadband
  dop down menu  in system state bar.

Status in modemmanager package in Ubuntu:
  New

Bug description:
  While I updating ModemManager to 1.14.2, there is no mobile broadband dop 
down menu in system state bar.
  I just can see mobile broadband in network in system settings menu

  my step:
  git clone -b 1.24.2 https://gitlab.freedesktop.org/mobile-broadband/libmbim
  NOCONFIGURE=1 ./autogen.sh
  ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu
  make
  sudo make install

  git clone -b 1.26.4 https://gitlab.freedesktop.org/mobile-broadband/libqmi
  NOCONFIGURE=1 ./autogen.sh
  ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu 
--enable-mbim-qmux --enable-collection=basic
  make
  sudo make install

  git clone -b 1.14.2 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager
  NOCONFIGURE=1 ./autogen.sh
  ./configure --prefix=/usr --libdir=/usr/lib/x86_64-linux-gnu --enable-gtk-doc 
--with-polkit=strict --with-suspend-resume=systemd 
--with-systemdsystemunitdir=/lib/systemd/systemmake
  make
  sudo make install

  
  OS: ubuntu20.04
  Module: SDX55
  ModemManager:1.14.2
  iusse: 1.No mobile broadband in system status bar drop-down menu.
 2.Every time I connect to the mobile broadband network in system 
settings menu, I need to add new connection.

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

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

[Touch-packages] [Bug 1891798] Re: Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug

[Colin Watson]

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

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

Title:
  Backport fix from sudo 1.8.22 to fix "stair-stepped output" bug

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

Bug description:
  sudo 1.8.20 introduced a bug in commit
  44dc15d02dc0b34bf03bc971ba08d3a761c3a031
  that is fixed by sudo 1.8.22 in commit
  3b88cdfcd8d1a39eabbb5b7d0c8fe8f035d7a264

  When the "use_pty" option is enabled, "stair-stepped output" occurs if
  sudo is piped to another command.

  Example output attached in a text file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: sudo 1.8.21p2-3ubuntu1.2
  Uname: Linux 5.4.50+ x86_64
  ApportVersion: 2.20.9-0ubuntu7.16
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 16 12:29:23 2020
  InstallationDate: Installed on 2014-05-10 (2290 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: sudo
  UpgradeStatus: Upgraded to bionic on 2018-11-24 (630 days ago)
  modified.conffile..etc.pam.d.sudo: [inaccessible: [Errno 13] Permission 
denied: '/etc/pam.d/sudo']
  modified.conffile..etc.sudoers: [inaccessible: [Errno 13] Permission denied: 
'/etc/sudoers']
  modified.conffile..etc.sudoers.d.README: [inaccessible: [Errno 13] Permission 
denied: '/etc/sudoers.d/README']

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

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

[Touch-packages] [Bug 1906741] Re: Firefox sometimes causes garbled audio

[chris m]

For me many videos have garbled audio, today it's https://octopus.com/,
some others, e.g. a cloud guru, tedx weren't working before, but are
now.  Perhaps it's not related to the video format.

Ubuntu 20.04 and FF 84.0.2

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

Title:
  Firefox sometimes causes garbled audio

Status in firefox package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Opening certain applications/websites at the same time as Firefox
  causes the audio to become garbled.

  The audio sounds distorted with an echo.

  Certain actions are guaranteed to cause this, but it can also
  happening when only running instances of Firefox.

  I've been able to consistently cause this by launching Zoom from a link 
within Firefox. 
  This does not occur when using Chrome. 

  The only way to fix the issue is to shut down all audio-related
  programs.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: firefox 83.0+build2-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-56.62-generic 5.4.73
  Uname: Linux 5.4.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  rdevans   55475 F pulseaudio
   /dev/snd/controlC0:  rdevans   55475 F pulseaudio
   /dev/snd/controlC3:  rdevans   55475 F pulseaudio
   /dev/snd/controlC1:  rdevans   55475 F pulseaudio
  BuildID: 20201112153044
  CasperMD5CheckResult: skip
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  3 16:55:36 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2017-10-20 (1140 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 10.0.0.1 dev enp7s0 proto dhcp metric 100 
   10.0.0.0/24 dev enp7s0 proto kernel scope link src 10.0.0.7 metric 100 
   169.254.0.0/16 dev enp7s0 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:354
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=83.0/20201112153044 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to focal on 2020-11-12 (21 days ago)
  dmi.bios.date: 02/18/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: H67M
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd02/18/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH67M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

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

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

[Touch-packages] [Bug 1913187] Re: iproute2 segfaults when filtering sockets

[Robie Basak]

Hello Rafael, or anyone else affected,

Accepted iproute2 into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/iproute2/4.15.0-2ubuntu1.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: iproute2 (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

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

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

Title:
  iproute2 segfaults when filtering sockets

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * The ss tool crashes when a query returns no results (seg fault)

  [Test Case]

   * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 
127.0.0.1
  Segmentation fault

   * PPA with the fix:
  https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187

  [Where problems could occur]

   * The ss tool is impacted and it has its code changed for the fix.

   * The fix is a clean cherry-pick and straightforward (moving
  declaration after a NULL check).

  [Other Info]

  When in Ubuntu Bionic, if one calls:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

  it works. Just like when in Groovy:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

  but.. if there is nothing to show, in Bionic we get a segfault:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

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

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

[Touch-packages] [Bug 1913423] [NEW] getgrouplist is not thread safe with libnss_systemd

[Daniel Sung]

Public bug reported:

This upstream issue (https://github.com/systemd/systemd/issues/17007) is
affecting the latest version of systemd in Ubuntu Focal. It has been
fixed upstream with https://github.com/systemd/systemd/pull/17033. Can
we have this patched for Focal please as it causes Mesos to randomly
segfault on start.

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

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

Title:
  getgrouplist is not thread safe with libnss_systemd

Status in systemd package in Ubuntu:
  New

Bug description:
  This upstream issue (https://github.com/systemd/systemd/issues/17007)
  is affecting the latest version of systemd in Ubuntu Focal. It has
  been fixed upstream with
  https://github.com/systemd/systemd/pull/17033. Can we have this
  patched for Focal please as it causes Mesos to randomly segfault on
  start.

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

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

[Touch-packages] [Bug 1907850] Re: Cache not generated for all translations

[Julian Andres Klode]

** Also affects: apt (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

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

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

** Description changed:

  [Impact]
  In bug 1161743 we discovered that if a system is configured with multiple 
locales, only the locales of the user who generated the apt-cache will be 
available for translated descriptions.
  
  [Test case]
+ An automated test case has been included as a snippet in  
test/integration/test-bug-49-search-in-all-translations which runs during 
autopkgtest. That's sufficient for validation.
+ 
+ Manual test:
  
  # apt install locales-all # get the locale
  # export LANG=sv_SE.UTF-8
  # locale
  LANG=sv_SE.UTF-8
  LANGUAGE=
  LC_CTYPE="sv_SE.UTF-8"
  LC_NUMERIC="sv_SE.UTF-8"
  LC_TIME="sv_SE.UTF-8"
  LC_COLLATE="sv_SE.UTF-8"
  LC_MONETARY="sv_SE.UTF-8"
  LC_MESSAGES="sv_SE.UTF-8"
  LC_PAPER="sv_SE.UTF-8"
  LC_NAME="sv_SE.UTF-8"
  LC_ADDRESS="sv_SE.UTF-8"
  LC_TELEPHONE="sv_SE.UTF-8"
  LC_MEASUREMENT="sv_SE.UTF-8"
  LC_IDENTIFICATION="sv_SE.UTF-8"
  LC_ALL=
  # apt update
  # apt-cache show tasksel | grep Desc
  Description-sv: tool for selecting tasks for installation on Debian systems
  Description-md5: cbbb747708986d11ea77c80b9b038fec
  # apt-cache showpkg tasksel
  Package: tasksel
  Versions:
  3.34ubuntu16 
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
   Description Language:
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
    MD5: cbbb747708986d11ea77c80b9b038fec
   Description Language: sv
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv
    MD5: cbbb747708986d11ea77c80b9b038fec
   Description Language: en
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
    MD5: cbbb747708986d11ea77c80b9b038fec
  [...]
  
  So far so good, but now assume the root user actually has C configured
  as locale, and e.g. runs apt-cache show (or apt-daily.service does an
  update):
  
  root@g:~# rm /var/cache/apt/*.bin
  root@g:~# LANG=C apt-cache  show tasksel
  [...]
  Description-en: tool for selecting tasks for installation on Debian systems
   This package provides 'tasksel', a simple interface for users who
   want to configure their system to perform a specific task.
  
  root@g:~# apt-cache  showpkg tasksel
  Package: tasksel
  Versions:
  3.34ubuntu16 
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
   Description Language:
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
    MD5: cbbb747708986d11ea77c80b9b038fec
   Description Language: en
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
    MD5: cbbb747708986d11ea77c80b9b038fec
  
  This should show the sv locale as well given that it's still around
  (also we are still running with LANG=sv_SE.UTF-8), but it only generated
  the cache with the english language description in here.
  
  [Where problems could occur]
- Unknown so far, we've not investigated the cause or solution yet.
- 
- [Other Info]
- N/A
+ People might end up seeing a wrong translation if other code paths are wrong, 
but then they'd already see them if they explicitly configured multiple 
languages and then switched the preferred one.

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

Title:
  Cache not generated for all translations

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Xenial:
  New
Status in apt source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in apt source package in Groovy:
  New
Status in apt source package in Hirsute:
  Confirmed

Bug description:
  [Impact]
  In bug 1161743 we discovered that if a system is configured with multiple 
locales, only the locales of the user who generated the apt-cache will be 
available for translated descriptions.

  [Test case]
  An automated test case has been included as a snippet in  
test/integration/test-bug-49-search-in-all-translations which runs during 
autopkgtest. That's sufficient for validation.

  Manual test:

  # apt install locales-all # get the locale
  # export LANG=sv_SE.UTF-8
  # locale
  LANG=sv_SE.UTF-8
  LANGUAGE=
  LC_CTYPE="sv_SE.UTF-8"
  LC_NUMERIC="sv_SE.UTF-8"
  LC_TIME="sv_SE.UTF-8"
  LC_COLLATE="sv_SE.UTF-8"
  LC_MONETARY="sv_SE.UTF-8"
  LC_MESSAGES="sv_SE.UTF-8"
  LC_PAPER="sv_SE.UTF-8"
  LC_NAME="sv_SE.UTF-8

[Touch-packages] [Bug 1913423] Re: getgrouplist is not thread safe with libnss_systemd

[Dimitri John Ledkov]

** Tags added: rls-ff-incoming

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

Title:
  getgrouplist is not thread safe with libnss_systemd

Status in systemd package in Ubuntu:
  New

Bug description:
  This upstream issue (https://github.com/systemd/systemd/issues/17007)
  is affecting the latest version of systemd in Ubuntu Focal. It has
  been fixed upstream with
  https://github.com/systemd/systemd/pull/17033. Can we have this
  patched for Focal please as it causes Mesos to randomly segfault on
  start.

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

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

[Touch-packages] [Bug 1452751] Re: Connecting network jump is confusing

[Matthew Paul Thomas]

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: Matthew Paul Thomas (mpt) => (unassigned)

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

Title:
  Connecting network jump is confusing

Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Ubuntu 15.04 r23

  1. Do any of the following:
  - open System Settings > "Wi-Fi"
  - open the network indicator
  - flash the phone and go to the "Connect to Wi-Fi" step

  2. Tap a closed network that is not on top and that you haven't used
  before

  Behaviour I get:
  Network jumps to top. After a while a prompt pops up to request your 
password. This can take up to 5 second on slow networks.
  This is very confusing. When the network jumped to the top, I wasn't sure if 
I tapped it, so I tapped it again. This had the following result: *popup asking 
for password appears* *popup goes away almost immediately* *popup comes back 
after a few seconds*

  Proposed solution:
  Immediately after tapping a network, even before putting it on top of the 
list, give it an indication of "trying to connect" either by a different color, 
a loading icon, ... (let the design guys figure this out)

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

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

[Touch-packages] [Bug 1913187] Autopkgtest regression report (iproute2/4.15.0-2ubuntu1.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted iproute2 (4.15.0-2ubuntu1.3) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

postgresql-common/190ubuntu0.1 (amd64, i386)
ubuntu-fan/0.12.10 (amd64, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#iproute2

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  iproute2 segfaults when filtering sockets

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * The ss tool crashes when a query returns no results (seg fault)

  [Test Case]

   * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 
127.0.0.1
  Segmentation fault

   * PPA with the fix:
  https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187

  [Where problems could occur]

   * The ss tool is impacted and it has its code changed for the fix.

   * The fix is a clean cherry-pick and straightforward (moving
  declaration after a NULL check).

  [Other Info]

  When in Ubuntu Bionic, if one calls:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

  it works. Just like when in Groovy:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

  but.. if there is nothing to show, in Bionic we get a segfault:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

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

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

[Touch-packages] [Bug 1913423] Re: getgrouplist is not thread safe with libnss_systemd

[Balint Reczey]

Fixed in v247 and v246.5 in Hirsute and Groovy.

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

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

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

Title:
  getgrouplist is not thread safe with libnss_systemd

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

Bug description:
  This upstream issue (https://github.com/systemd/systemd/issues/17007)
  is affecting the latest version of systemd in Ubuntu Focal. It has
  been fixed upstream with
  https://github.com/systemd/systemd/pull/17033. Can we have this
  patched for Focal please as it causes Mesos to randomly segfault on
  start.

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

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

[Touch-packages] [Bug 1913453] [NEW] Xorg freeze

[james]

Public bug reported:

System
Description:Ubuntu 20.04.1 LTS
Release:20.04

Description:
Plugging in USB hub with peripherals while system is running causes gradual lag 
of a visual response, until freezing. usually takes < 1 min.  Only work around 
is to sleep system between plugging in hub.

I thought I fixed it by change DM but the issue has persisted.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
Uname: Linux 5.4.0-64-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 27 14:27:12 2021
DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed
 acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed
 acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
InstallationDate: Installed on 2018-12-25 (763 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: LENOVO 2324AS7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago)
dmi.bios.date: 04/11/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ETB2WW (2.72 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2324AS7
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: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230
dmi.product.name: 2324AS7
dmi.product.sku: LENOVO_MT_2324
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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
xserver.bootTime: Tue Nov 24 16:32:27 2020
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.20.8-2ubuntu2.4
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug focal freeze third-party-packages ubuntu 
wayland-session

** Description changed:

  System
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04
  
  Description:
  Plugging in USB hub with peripherals while system is running causes gradual 
lag of a visual response, until freezing. usually takes < 1 min.  Only work 
around is to sleep system between plugging in hub.
  
- I thought I fixed it by change DE but the issue has persisted.
+ I thought I fixed it by change DM but the issue has persisted.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  Uname: Linux 5.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 27 14:27:12 2021
  DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
-  acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed
-  acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed
-  acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed
+  acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed
+  acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed
+  acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed
  ExtraDebuggingInterest:

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

[William Wilson]

I wrote a note to make sure I always look for old versions that no
longer exist in later releases, and here is a corrected patch.

** Patch added: "lp1829401_groovy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1829401/+attachment/5457420/+files/lp1829401_groovy.debdiff

-- 
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 1913179] Re: krb5 fails dep8 in Hirsute

[Robie Basak]

krb5 has now migrated with the fix to openldap.

** Changed in: krb5 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  krb5 fails dep8 in Hirsute

Status in krb5 package in Ubuntu:
  Fix Released

Bug description:
  I'm creating this bug to lead people looking at update_excuses to the
  MP that fixes this issue, since unfortunately there's no easier way of
  doing that.

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

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

[Touch-packages] [Bug 1907433] Re: [SRU] New stable release 2.64.6

[Iain Lane]

> retry the test

That has been done. Now the only red is netplan.io.

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

Title:
  [SRU] New stable release 2.64.6

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Focal:
  Fix Committed

Bug description:
  [ Description ]

  Take this new upstrem stable release.

  It was easiest for me to merge the latest release in this series from
  Debian, and then import the subsequent point releases on top of that.

  Visually in the diff there is one change resulting from this:
  splitting a two-patch upstream cherry pick into two individual patch
  files. This is cleaner anyway IMO, but is also no change if you look
  at the resulting patched source.

  Overview of changes in GLib 2.64.6
  ==

  * This is expected to be the last release in the 2.64 series; the new stable
    series is 2.66, and maintenance efforts will shift to that

  * Bugs fixed:
   - #2194 gtk3/glib crash on gimp
   - #2209 gthreadedresolver: faulty logic in parse_res_txt
   - !1633 Backport !1632 Fix large writes in gfileutils to glib-2-64
   - !1634 Backport !1631 “Fix splice behavior on cancellation” to glib-2-64
   - !1656 Backport !1187 “Define G_MSVC_SYMBOL_PREFIX correctly for ARM32” to 
glib-2-64
   - !1659 Backport !1652 “trash portal: Handle portal failures” to glib-2-64
   - !1666 Backport !1665 “Fix g_module_symbol() under Windows sometimes not 
succeeding” to glib-2-64
   - !1672 Backport !1671 “gdatetime: Avoid integer overflow creating dates too 
far in the past” to glib-2-64

  * Translation updates:
   - Croatian
   - Portuguese

  Overview of changes in GLib 2.64.5
  ==

  * Fix deadlock in `g_subprocess_communicate_async()` (work by
  Alexander Larsson) (#2182)

  * Fix cross-compilation on iOS (work by Nirbheek Chauhan) (#1868)

  * Bugs fixed:
   - !1519 Backport !1468 “glib-compile-resources: Fix exporting on Visual 
Studio” to glib-2-64
   - !1520 Backport !1517 “GWin32RegistryKey: Move assertions” to glib-2-64
   - !1565 Backport !1563 “gdesktopappinfo: Fix unnecessarily copied and leaked 
URI list” to glib-2-64
   - !1608 Backport !1607 “meson: Don't use gnulib for printf on iOS” to 
glib-2-64
   - !1618 Backport !1617 “Ensure g_subprocess_communicate_async() never 
blocks” to glib-2-64
   - !1621 Backport !1620 “gvariant: Ensure GVS.depth is initialised” to 
glib-2-64

  Overview of changes in GLib 2.64.4
  ==

  * Bugs fixed:
   - #2140 calling malloc in fork child is undefined-behaviour
   - !1507 Backport !1504 “win32 gpoll: Fix wait for at least one thread to 
return” to glib-2-64
   - !1523 Backport !1522 “meson: Fix gnulib printf checks” to glib-2-64
   - !1547 Backport !1544 “Resolve "calling malloc in fork child is 
undefined-behaviour"” to glib-2-64

  * Translation updates:
   - Kazakh
   - Slovenian

  [ QA ]

  Upstream release, so QA already performed by maintainers

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  This upload will trigger many autopkgtests that we expect to not be
  regressed by this upload.

  [ What could go wrong ]

  This update contains fixes in multiple places so multiple apps could
  be affected. The consequences of a broken GLib can range from some
  functions returning bad results sometimes, which have minimal runtime
  implications, up to the system simply crashing all the time.

  Pretty much all parts of GNOME use GLib, so test anything in the
  desktop that you can. If you reboot the machine and can get to the
  desktop, that's already tested GLib extensively. But also run
  applications like GNOME terminal, Files and Epiphany.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1907433/+subscriptions

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

[Touch-packages] [Bug 1912535] Re: [SRU] python-cffi and libffi in Groovy need a no-change rebuild

[Erich Eickmeyer]

Upon further investigation, it appears as though libffi was built on an
older version of cffi, which would probably explain this a little
further. Adding libffi to the bug.


** Summary changed:

- [SRU] python-cffi in Groovy needs a no-change rebuild
+ [SRU] python-cffi and libffi in Groovy need a no-change rebuild

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

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

** Description changed:

  [Impact]
  
-  * Users of studio-controls have been reporting bugs against studio-
+  * Users of studio-controls have been reporting bugs against studio-
  controls upstream on Github. For reference, see
  https://github.com/ovenwerks/studio-controls/issues/43
  
-  * Per the bug report, the following error is being thrown: SystemError:
+  * Per the bug report, the following error is being thrown: SystemError:
  ffi_prep_closure(): bad user_data (it seems that the version of the
  libffi library seen at runtime is different from the 'ffi.h' file seen
  at compile-time)
  
-  * Based on this error, and based on the build time of python-cffi, it
- appears as though python-cffi was built on an older version of cffi.
- This explains the error.
+  * Based on this error, and based on the build time of python-cffi and
+ libffi in relation to cffi, it appears as though python-cffi and libffi
+ were built on an older version of cffi. This explains the error.
  
  [Test Case]
  
-  * A certain number of users have reported that simply running studio-
+  * A certain number of users have reported that simply running studio-
  controls causes this error.
  
  [Where problems could occur]
  
-  * Since this is a no-change rebuild being requested, the possibility of
+  * Since this is a no-change rebuild being requested, the possibility of
  breakage is slim to none. We are introducing no new changes here, but
  rather, resolving a regression that happened as a result of a newer
  version of cffi being introduced without a rebuild of dependencies.
  
-  * If any problems happen, it would be a result of applications using
+  * If any problems happen, it would be a result of applications using
  python-cffi and expecting this bug with built-in workarounds. I can't
  imagine such a case exists, so this is just a stretch.

** Changed in: libffi (Ubuntu Groovy)
   Importance: Undecided => High

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

Title:
  [SRU] python-cffi and libffi in Groovy need a no-change rebuild

Status in libffi package in Ubuntu:
  Fix Released
Status in python-cffi package in Ubuntu:
  Fix Released
Status in libffi source package in Groovy:
  New
Status in python-cffi source package in Groovy:
  New
Status in libffi source package in Hirsute:
  Fix Released
Status in python-cffi source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Users of studio-controls have been reporting bugs against studio-
  controls upstream on Github. For reference, see
  https://github.com/ovenwerks/studio-controls/issues/43

   * Per the bug report, the following error is being thrown:
  SystemError: ffi_prep_closure(): bad user_data (it seems that the
  version of the libffi library seen at runtime is different from the
  'ffi.h' file seen at compile-time)

   * Based on this error, and based on the build time of python-cffi and
  libffi in relation to cffi, it appears as though python-cffi and
  libffi were built on an older version of cffi. This explains the
  error.

  [Test Case]

   * A certain number of users have reported that simply running studio-
  controls causes this error.

  [Where problems could occur]

   * Since this is a no-change rebuild being requested, the possibility
  of breakage is slim to none. We are introducing no new changes here,
  but rather, resolving a regression that happened as a result of a
  newer version of cffi being introduced without a rebuild of
  dependencies.

   * If any problems happen, it would be a result of applications using
  python-cffi and expecting this bug with built-in workarounds. I can't
  imagine such a case exists, so this is just a stretch.

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

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

[Touch-packages] [Bug 1912535] Re: [SRU] python-cffi and libffi in Groovy need a no-change rebuild

[Stefano Rivera]

First: How do we reproduce the error? That'd be the best way to dig
deeper.

Second: libffi doesn't build against cffi.

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

Title:
  [SRU] python-cffi and libffi in Groovy need a no-change rebuild

Status in libffi package in Ubuntu:
  Fix Released
Status in python-cffi package in Ubuntu:
  Fix Released
Status in libffi source package in Groovy:
  New
Status in python-cffi source package in Groovy:
  New
Status in libffi source package in Hirsute:
  Fix Released
Status in python-cffi source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

   * Users of studio-controls have been reporting bugs against studio-
  controls upstream on Github. For reference, see
  https://github.com/ovenwerks/studio-controls/issues/43

   * Per the bug report, the following error is being thrown:
  SystemError: ffi_prep_closure(): bad user_data (it seems that the
  version of the libffi library seen at runtime is different from the
  'ffi.h' file seen at compile-time)

   * Based on this error, and based on the build time of python-cffi and
  libffi in relation to cffi, it appears as though python-cffi and
  libffi were built on an older version of cffi. This explains the
  error.

  [Test Case]

   * A certain number of users have reported that simply running studio-
  controls causes this error.

  [Where problems could occur]

   * Since this is a no-change rebuild being requested, the possibility
  of breakage is slim to none. We are introducing no new changes here,
  but rather, resolving a regression that happened as a result of a
  newer version of cffi being introduced without a rebuild of
  dependencies.

   * If any problems happen, it would be a result of applications using
  python-cffi and expecting this bug with built-in workarounds. I can't
  imagine such a case exists, so this is just a stretch.

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

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

[Touch-packages] [Bug 84580] Re: avahi-autoipd causes failure if multiple networking stanzas exist

[fname]

This fix does not working and the bug still exists. There is a race condition 
between the `ip route show` check and the `/bin/ip route add` command, and 
systemd will launch multiple `ifup` concurrently.
Maybe the failure of `/etc/network/if-up.d/avahi-autoipd` should be ignored to 
avoid causing problem to ifup/ifdown.
FYI, one can recover from this problem by executing `ip addr flush dev xxx`

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

Title:
  avahi-autoipd causes failure if multiple networking stanzas exist

Status in avahi package in Ubuntu:
  Fix Released
Status in avahi package in Debian:
  New

Bug description:
  When I switch from one networking profile to another (by stopping
  networking, copying new /etc/network/interfaces and other files, and
  restarting networking), I notice that /etc/network/if-up.d/avahi-
  autoipd complains about something and exits with status 1, causing the
  ifup command to stop prematurely before configuring wireless settings.
  I don't remember the exact error message, but if it is considered
  important, I can trigger it again.

  I've attached the /etc/network/interfaces file which causes the problem.
  I suspect the problem may be due to having multiple network interfaces and 
bridging them (using Shorewall).  Adding an "exit 0" to the beginning of 
/etc/network/if-up.d/avahi-autoipd allows the configuration to succeed, but I 
would really prefer that the problem be fixed properly.

  One way of addressing this would be to put an "exit 0" line at the
  very end of the file, so that any errors that occur in the "route add"
  command do not cause the entire configuration process to terminate.

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

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

[Touch-packages] [Bug 1899218] Re: Incorrect warning from apparmor_parser on force complained profiles

[Andreas Hasenack]

Just saw this in bionic, I guess it's not important enough for an SRU?

# apparmor_parser -r -T -W --Complain /etc/apparmor.d/pam_roles 
/etc/apparmor.d/usr.sbin.sshd
Warning failed to create cache: pam_roles
Warning failed to create cache: usr.sbin.sshd

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

Title:
  Incorrect warning from apparmor_parser on force complained profiles

Status in apparmor package in Ubuntu:
  Fix Released

Bug description:
  apparmor_parser on a force complained profile produces an incorrect
  warning message:

  $ sudo apparmor_parser -rW /etc/apparmor.d/usr.sbin.sssd
  Warning: found usr.sbin.sssd in /etc/apparmor.d/force-complain, forcing 
complain mode
  Warning from /etc/apparmor.d/usr.sbin.sssd (/etc/apparmor.d/usr.sbin.sssd 
line 54): Warning failed to create cache: usr.sbin.sssd

  Even though not generating the cache at all is expected, the warning
  should describe caching is disabled for force complained profiles
  instead of failure to create it.

  $ lsb_release -rd
  Description:  Ubuntu Groovy Gorilla (development branch)
  Release:  20.10

  $ apt-cache policy apparmor
  apparmor:
    Installed: 3.0.0~beta1-0ubuntu6
    Candidate: 3.0.0~beta1-0ubuntu6
    Version table:
   *** 3.0.0~beta1-0ubuntu6 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Touch-packages] [Bug 1913481] [NEW] Update tzdata to version 2021a

[Brian Murray]

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

Public bug reported:

New upstream version affecting the following timestamp:
$region/$timezone = Africa/Juba
Verification is done with 'zdump'. The first timezone that gets changed in the 
updated package is dumped with 'zdump -v $region/$timezone_that_changed' (this 
needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v 
Africa/Juba'.] This is compared to the same output after the updated package 
got installed. If those are different the verification is considered done.
[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021
For releases with ICU timezone data verification is done using the following 
with dates before and after the change:[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba')); 
print(str(tz.utcoffset(datetime(2021, 2, 1'
Additionally, an upstream update of tzdata removed the 'old' SystemV timezones, 
so we should ensure that they are kept in Ubuntu 20.04 LTS and earlier 
releases. Subsequently, these should be checked for using the following:
[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut 
-d' ' -f2-)
Nothing should be returned by the above command.

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

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

Title:
  Update tzdata to version 2021a

Status in tzdata package in Ubuntu:
  New

Bug description:
  New upstream version affecting the following timestamp:
  $region/$timezone = Africa/Juba
  Verification is done with 'zdump'. The first timezone that gets changed in 
the updated package is dumped with 'zdump -v $region/$timezone_that_changed' 
(this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v 
Africa/Juba'.] This is compared to the same output after the updated package 
got installed. If those are different the verification is considered done.
  [Test Case for all releases]
  1) zdump -v Africa/Juba | grep 2021
  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:[Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba')); 
print(str(tz.utcoffset(datetime(2021, 2, 1'
  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)
  Nothing should be returned by the above command.

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

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

[Touch-packages] [Bug 1913482] [NEW] Update tzdata to version 2021a

[Brian Murray]

Public bug reported:

New upstream version affecting the following timestamp:

$region/$timezone = Africa/Juba

Verification is done with 'zdump'. The first timezone that gets changed
in the updated package is dumped with 'zdump -v
$region/$timezone_that_changed' (this needs to be greped for in
/usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
compared to the same output after the updated package got installed. If
those are different the verification is considered done.

[Test Case for all releases]
1) zdump -v Africa/Juba | grep 2021

For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
[Test Case for releases >= 20.04 LTS]
1) sudo apt-get install python3-icu
2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba')); 
print(str(tz.utcoffset(datetime(2021, 2, 1'

Additionally, an upstream update of tzdata removed the 'old' SystemV
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
and earlier releases. Subsequently, these should be checked for using
the following:

[Test Case for releases <= 20.04 LTS]
diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | cut 
-d' ' -f2-)

Nothing should be returned by the above command.

** Affects: tzdata (Ubuntu)
 Importance: Undecided
 Assignee: Brian Murray (brian-murray)
 Status: In Progress

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

** Changed in: tzdata (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  Update tzdata to version 2021a

Status in tzdata package in Ubuntu:
  In Progress

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Africa/Juba

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Africa/Juba | grep 2021

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba')); 
print(str(tz.utcoffset(datetime(2021, 2, 1'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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

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

[Touch-packages] [Bug 1913481] Re: Update tzdata to version 2021a

[Brian Murray]

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

** This bug has been marked a duplicate of bug 1913482
   Update tzdata to version 2021a

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

Title:
  Update tzdata to version 2021a

Status in tzdata package in Ubuntu:
  New

Bug description:
  New upstream version affecting the following timestamp:
  $region/$timezone = Africa/Juba
  Verification is done with 'zdump'. The first timezone that gets changed in 
the updated package is dumped with 'zdump -v $region/$timezone_that_changed' 
(this needs to be greped for in /usr/share/zoneinfo/). [For example: 'zdump -v 
Africa/Juba'.] This is compared to the same output after the updated package 
got installed. If those are different the verification is considered done.
  [Test Case for all releases]
  1) zdump -v Africa/Juba | grep 2021
  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:[Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba')); 
print(str(tz.utcoffset(datetime(2021, 2, 1'
  Additionally, an upstream update of tzdata removed the 'old' SystemV 
timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS and 
earlier releases. Subsequently, these should be checked for using the following:
  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)
  Nothing should be returned by the above command.

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

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

[Touch-packages] [Bug 1913482] Re: Update tzdata to version 2021a

[Brian Murray]

** Description changed:

  New upstream version affecting the following timestamp:
+ 
+ - South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.
  
  $region/$timezone = Africa/Juba
  
  Verification is done with 'zdump'. The first timezone that gets changed
  in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
  compared to the same output after the updated package got installed. If
  those are different the verification is considered done.
  
  [Test Case for all releases]
  1) zdump -v Africa/Juba | grep 2021
  
  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba')); 
print(str(tz.utcoffset(datetime(2021, 2, 1'
  
  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:
  
  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)
  
  Nothing should be returned by the above command.

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

Title:
  Update tzdata to version 2021a

Status in tzdata package in Ubuntu:
  In Progress

Bug description:
  New upstream version affecting the following timestamp:

  - South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.

  $region/$timezone = Africa/Juba

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Africa/Juba | grep 2021

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba')); 
print(str(tz.utcoffset(datetime(2021, 2, 1'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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

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

[Touch-packages] [Bug 1913482] Re: Update tzdata to version 2021a

[Brian Murray]

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

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

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

** Also affects: tzdata (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

Title:
  Update tzdata to version 2021a

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Groovy:
  New

Bug description:
  New upstream version affecting the following timestamp:

  - South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.

  $region/$timezone = Africa/Juba

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Africa/Juba | grep 2021

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba')); 
print(str(tz.utcoffset(datetime(2021, 2, 1'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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

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

[Touch-packages] [Bug 1913482] Re: Update tzdata to version 2021a

[Brian Murray]

Trusty debdiff.

** Patch added: "trusty-2021a.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+attachment/5457507/+files/trusty-2021a.debdiff

** Changed in: tzdata (Ubuntu Xenial)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: tzdata (Ubuntu Bionic)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: tzdata (Ubuntu Focal)
 Assignee: (unassigned) => Brian Murray (brian-murray)

** Changed in: tzdata (Ubuntu Groovy)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  Update tzdata to version 2021a

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Groovy:
  New

Bug description:
  New upstream version affecting the following timestamp:

  - South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.

  $region/$timezone = Africa/Juba

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Africa/Juba | grep 2021

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba')); 
print(str(tz.utcoffset(datetime(2021, 2, 1'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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

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

[Touch-packages] [Bug 1913482] Re: Update tzdata to version 2021a

[Brian Murray]

Precise debdiff.

** Patch added: "2021a-precise.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1913482/+attachment/5457509/+files/2021a-precise.debdiff

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

Title:
  Update tzdata to version 2021a

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Groovy:
  New

Bug description:
  New upstream version affecting the following timestamp:

  - South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.

  $region/$timezone = Africa/Juba

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Africa/Juba | grep 2021

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba')); 
print(str(tz.utcoffset(datetime(2021, 2, 1'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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

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

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

[William Wilson]

** Description changed:

  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)
+   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)
+   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
+ 
+ 
+ [Impact] 
+ 
+  * If selected mirrors are not reachable or have
+expired GPG keys, software-properties-gtk
+would crash
+ 
+ [Test Case]
+ 
+  * Edit the file /usr/share/python-apt/templates/Ubuntu.mirrors
+ 
+  * Find your locale in this file and add a non-existent URL
+to the list
+ 
+  * Run software-properties-gtk and choose your newly added
+URL from the "Download From" dropdown menu
+ 
+  * Press "Close" in the bottom right, and when
+prompted press "Reload"
+ 
+  * You should be presented with an error window rather than
+the program crashing
+ 
+ [Where problems could occur]
+ 
+  * The new error window binds to the parent window. If the
+parent window has gotten into a bad state this could
+cause problems

-- 
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)

Re: [Touch-packages] [Bug 1830955] Re: Systemd removes OpenVPN IP addresses

[Leroy Tennison]

Dan,
Unfortunately i can no longer reproduce this behavior.  Guess the bug needs to 
be closed, sorry for the hassle.


-Original Message-
From: Dan Streetman <1830...@bugs.launchpad.net>
To: leroy.tenni...@verizon.net
Sent: Fri, Dec 11, 2020 8:49 am
Subject: [Bug 1830955] Re: Systemd removes OpenVPN IP addresses

please boot with kernel boot parameter 'systemd.log_level=debug' and
reproduce this, then provide the journal logs (before rebooting) with:

$ journalctl -k -b > /tmp/lp1830955.log


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

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1830955

Title:
  Systemd removes OpenVPN IP addresses

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  This is probably related to,  but not a duplicate of, bug 1815101.
  Running

  root@third:/home/leroy# lsb_release -rd
  Description:    Ubuntu 18.04.2 LTS
  Release:        18.04

  Systemd version:

  root@third:/home/leroy# apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10.21
    Candidate: 237-3ubuntu10.21
    Version table:
  *** 237-3ubuntu10.21 500
          500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
          100 /var/lib/dpkg/status
      237-3ubuntu10.19 500
          500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
      237-3ubuntu10 500
          500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  I expected the OpenVPN IP addresses to remain, instead they were
  removed, the physical NIC address remained, process:

  Start OpenVPN with systemctl start openvpn@ (in this
  situation, two instances).  Result:

  root@third:/etc/openvpn# ip addr sh tun0
  7: tun0:  mtu 1500 qdisc fq_codel 
state UNKNOWN group default qlen 100
      link/none 
      inet 10.57.3.1 peer 10.57.3.2/32 scope global tun0
        valid_lft forever preferred_lft forever
      inet6 fe80::f0ea:151b:cb91:5d1b/64 scope link stable-privacy 
        valid_lft forever preferred_lft forever
  root@third:/etc/openvpn# ip addr sh tun1
  8: tun1:  mtu 1500 qdisc fq_codel 
state UNKNOWN group default qlen 100
      link/none 
      inet 10.222.108.234 peer 10.222.108.233/32 scope global tun1
        valid_lft forever preferred_lft forever
      inet6 fe80::3103:7936:cf19:6237/64 scope link stable-privacy 
        valid_lft forever preferred_lft forever

  Test a configuration (which, incidentally, isn't valid for this
  system) with 'netplan try ..' and allow it to revert (which should
  have restored the previous configuration), see below:

  root@third:/etc/openvpn# cd ~leroy/Downloads
  root@third:/home/leroy/Downloads# ll *.yaml
  -rw-rw-r-- 1 leroy leroy 555 May 29 10:46 startup.yaml
  root@third:/home/leroy/Downloads# netplan --debug try --config-file 
~leroy/Downloads/startup.yaml --timeout 15
  DEBUG:eno1 not found in {}
  DEBUG:Merged config:
  network:
    bonds: {}
    bridges: {}
    ethernets:
      eno1:
        addresses:
        - 10.15.0.37/24
        dhcp4: false
        gateway4: 10.15.0.1
        nameservers:
          addresses:
          - 10.15.0.8
          - 10.3.77.11
          - 10.45.77.11
          - 8.8.8.8
    vlans: {}
    wifis: {}

  DEBUG:New interfaces: {'eno1'}
  ** (generate:8216): DEBUG: 11:19:39.770: Processing input file 
/etc/netplan/01-network-manager-all.yaml..
  ** (generate:8216): DEBUG: 11:19:39.771: starting new processing pass
  ** (generate:8216): DEBUG: 11:19:39.771: Processing input file 
/etc/netplan/startup.1559146779.768221.yaml..
  ** (generate:8216): DEBUG: 11:19:39.771: starting new processing pass
  ** (generate:8216): DEBUG: 11:19:39.771: eno1: setting default backend to 2
  ** (generate:8216): DEBUG: 11:19:39.771: Generating output files..
  ** (generate:8216): DEBUG: 11:19:39.771: networkd: definition eno1 is not for 
us (backend 2)
  DEBUG:no netplan generated networkd configuration exists
  DEBUG:netplan generated NM configuration exists, restarting NM
  DEBUG:eno1 not found in {}
  DEBUG:Merged config:
  network:
    bonds: {}
    bridges: {}
    ethernets:
      eno1:
        addresses:
        - 10.15.0.37/24
        dhcp4: false
        gateway4: 10.15.0.1
        nameservers:
          addresses:
          - 10.15.0.8
          - 10.3.77.11
          - 10.45.77.11
          - 8.8.8.8
    vlans: {}
    wifis: {}

  DEBUG:Skipping non-physical interface: lo
  DEBUG:Skipping non-physical interface: enp2s0
  DEBUG:Skipping non-physical interface: virbr0
  DEBUG:Skipping non-physical interface: virbr0-nic
  DEBUG:Skipping non-physical interface: tun0
  DEBUG:Skipping non-physical interface: tun1
  DEBUG:{}
  DEBUG:netplan triggering .link rules for lo
  DEBUG:netplan triggering .link rules for enp2s0
  DEBUG:netplan triggering .link rules for virbr0
  DEBUG:netplan triggering .link rules for virbr0-nic
  DEBUG:netplan triggering .link rules for tun0
  DEBUG:netplan triggering .l

[Touch-packages] [Bug 1913485] [NEW] PulseEffects + YTMD

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

when opening both apps its always a big complication with a lot a
latency and distortion

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78
Uname: Linux 5.4.0-64-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.21
Architecture: amd64
CompositorRunning: None
Date: Wed Jan 27 13:56:37 2021
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0682]
InstallationDate: Installed on 2018-01-28 (1095 days ago)
InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
MachineType: Acer TravelMate P653-M
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=068acae8-2f26-4217-b2a3-e5afc4dd438d ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2012
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: V2.03.
dmi.board.asset.tag: No Asset Tag
dmi.board.name: TravelMate P653-M
dmi.board.vendor: Acer
dmi.board.version: V2.03.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Acer
dmi.chassis.version: V2.03.
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.03.:bd10/16/2012:svnAcer:pnTravelMateP653-M:pvrV2.03.:rvnAcer:rnTravelMateP653-M:rvrV2.03.:cvnAcer:ct9:cvrV2.03.:
dmi.product.family: TravelMate P653-M
dmi.product.name: TravelMate P653-M
dmi.product.sku: TravelMate P653-M_0682_2.03
dmi.product.version: V2.03.
dmi.sys.vendor: Acer
version.compiz: compiz N/A
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 N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic third-party-packages ubuntu
-- 
PulseEffects + YTMD
https://bugs.launchpad.net/bugs/1913485
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 1913485] Re: PulseEffects + YTMD

[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/1913485

Title:
  PulseEffects + YTMD

Status in xorg package in Ubuntu:
  New

Bug description:
  when opening both apps its always a big complication with a lot a
  latency and distortion

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78
  Uname: Linux 5.4.0-64-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Jan 27 13:56:37 2021
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0682]
  InstallationDate: Installed on 2018-01-28 (1095 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: Acer TravelMate P653-M
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=068acae8-2f26-4217-b2a3-e5afc4dd438d ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.03.
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TravelMate P653-M
  dmi.board.vendor: Acer
  dmi.board.version: V2.03.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.03.
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.03.:bd10/16/2012:svnAcer:pnTravelMateP653-M:pvrV2.03.:rvnAcer:rnTravelMateP653-M:rvrV2.03.:cvnAcer:ct9:cvrV2.03.:
  dmi.product.family: TravelMate P653-M
  dmi.product.name: TravelMate P653-M
  dmi.product.sku: TravelMate P653-M_0682_2.03
  dmi.product.version: V2.03.
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1913482] Re: Update tzdata to version 2021a

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Update tzdata to version 2021a

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Xenial:
  New
Status in tzdata source package in Bionic:
  New
Status in tzdata source package in Focal:
  New
Status in tzdata source package in Groovy:
  New

Bug description:
  New upstream version affecting the following timestamp:

  - South Sudan changes from +03 to +02 on 2021-02-01 at 00:00.

  $region/$timezone = Africa/Juba

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Africa/Juba'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Africa/Juba | grep 2021

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.creat eTimeZone('Africa/Juba')); 
print(str(tz.utcoffset(datetime(2021, 2, 1'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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

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

[Touch-packages] [Bug 1913499] [NEW] Bluetooth input doesn't work w/ Bose QC35 ii

[Daniel Newman]

Public bug reported:

When connecting the Bose QC35 ii, the bluetooth audio works just fine
initially, but the microphone does not. When I go to the sound settings
and change the mic input to use the QC35 ii bluetooth input, the audio
changes from stereo to mono and sounds terrible and cannot understand
anything. Also the mic picks up some input, but the result output sounds
about the same, completely un-understandable, a stuttering digitized
version of the input.

> lsb_release -rd
Description:Ubuntu 20.10
Release:20.10

Linux dan-xps-9700 5.10.5-051005-generic #202101061537 SMP Wed Jan 6
15:43:53 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

3. I expected the microphone input and headset output to both work 
simultaneously via bluetooth.
4. Only the headset output worked well, when enabling microphone both sounded 
terrible (unusable).

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: bluez 5.55-0ubuntu1.1
Uname: Linux 5.10.5-051005-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 27 17:53:00 2021
InstallationDate: Installed on 2021-01-06 (21 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
InterestingModules: rfcomm bnep bluetooth
MachineType: Dell Inc. XPS 17 9700
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.5-051005-generic 
root=UUID=d87c0f2c-adf4-493f-95dc-e2df02f584b3 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/03/2020
dmi.bios.release: 1.4
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 03CPGC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd09/03/2020:br1.4:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn03CPGC:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 17 9700
dmi.product.sku: 098F
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: UART
BD Address: 28:C2:1F:87:52:EC  ACL MTU: 1024:8  SCO MTU: 240:4
UP RUNNING PSCAN 
RX bytes:1599 acl:0 sco:0 events:91 errors:0
TX bytes:198368 acl:0 sco:0 commands:849 errors:0
mtime.conffile..etc.bluetooth.main.conf: 2021-01-27T17:24:11.108718

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


** Tags: amd64 apport-bug groovy

** Summary changed:

- Bluetooth input doesn't work w/ Bose QC36 ii
+ Bluetooth input doesn't work w/ Bose QC35 ii

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

Title:
  Bluetooth input doesn't work w/ Bose QC35 ii

Status in bluez package in Ubuntu:
  New

Bug description:
  When connecting the Bose QC35 ii, the bluetooth audio works just fine
  initially, but the microphone does not. When I go to the sound
  settings and change the mic input to use the QC35 ii bluetooth input,
  the audio changes from stereo to mono and sounds terrible and cannot
  understand anything. Also the mic picks up some input, but the result
  output sounds about the same, completely un-understandable, a
  stuttering digitized version of the input.

  > lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  Linux dan-xps-9700 5.10.5-051005-generic #202101061537 SMP Wed Jan 6
  15:43:53 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  3. I expected the microphone input and headset output to both work 
simultaneously via bluetooth.
  4. Only the headset output worked well, when enabling microphone both sounded 
terrible (unusable).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1.1
  Uname: Linux 5.10.5-051005-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 27 17:53:00 2021
  InstallationDate: Installed on 2021-01-06 (21 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep bluetooth
  MachineType: Dell Inc. XPS 17 9700
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.5-051005-generic 
root=UUID=d87c0f2c-adf4-493f-95dc-e2df02f584b3 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 03CPGC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd09/03/2020:br1.4:svnDellInc.:pnXPS

[Touch-packages] [Bug 1913500] [NEW] package linux-firmware 1.187.8 failed to install/upgrade: installed linux-firmware package post-installation script subprocess returned error exit status 1

[Ian Murphy]

Public bug reported:

This happened a little while back and it other than not being able to
boot into the new kernel, it hasn't been a problem (at least for the old
5.4.0-58) It exits on the plymouth hook

Ubuntu 20.04.1 LTS
initramfs-tools 0.136ubuntu6.3

I expected the update-initramfs to rebuild the installed kernel and
finish the update but instead it failed during the plymouth hook.

Other package updates that failed because of this:
 linux-firmware
 linux-image-generic-hwe-20.04
 linux-generic-hwe-20.04
 linux-image-5.8.0-38-generic
 linux-image-5.8.0-40-generic
 linux-image-5.4.0-59-generic
 linux-image-5.8.0-36-generic

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-firmware 1.187.8
ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
Uname: Linux 5.4.0-58-generic x86_64
NonfreeKernelModules: lkp_Ubuntu_5_4_0_58_64_generic_74 zfs zunicode zavl icp 
zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.14
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  egon   9806 F pulseaudio
 /dev/snd/controlC1:  egon   9806 F pulseaudio
 /dev/snd/pcmC1D0p:   egon   9806 F...m pulseaudio
CasperMD5CheckResult: skip
Date: Wed Jan 27 20:08:29 2021
Dependencies:
 
ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-10-08 (111 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
MachineType: Hewlett-Packard HP EliteBook Folio 9480m
PackageArchitecture: all
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-58-generic 
root=UUID=0741ccf4-941c-43b4-9413-fa78aee3b5f1 ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions: grub-pc 2.04-1ubuntu26.8
SourcePackage: initramfs-tools
Title: package linux-firmware 1.187.8 failed to install/upgrade: installed 
linux-firmware package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2018
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: M85 Ver. 01.46
dmi.board.name: 22DA
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 92.17
dmi.chassis.asset.tag: 5CG52944SB
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrM85Ver.01.46:bd08/08/2018:svnHewlett-Packard:pnHPEliteBookFolio9480m:pvrA3009DD10303:rvnHewlett-Packard:rn22DA:rvrKBCVersion92.17:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
dmi.product.name: HP EliteBook Folio 9480m
dmi.product.sku: K2Y11US#ABA
dmi.product.version: A3009DD10303
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package focal

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

Title:
  package linux-firmware 1.187.8 failed to install/upgrade: installed
  linux-firmware package post-installation script subprocess returned
  error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  This happened a little while back and it other than not being able to
  boot into the new kernel, it hasn't been a problem (at least for the
  old  5.4.0-58) It exits on the plymouth hook

  Ubuntu 20.04.1 LTS
  initramfs-tools 0.136ubuntu6.3

  I expected the update-initramfs to rebuild the installed kernel and
  finish the update but instead it failed during the plymouth hook.

  Other package updates that failed because of this:
   linux-firmware
   linux-image-generic-hwe-20.04
   linux-generic-hwe-20.04
   linux-image-5.8.0-38-generic
   linux-image-5.8.0-40-generic
   linux-image-5.4.0-59-generic
   linux-image-5.8.0-36-generic

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.8
  ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73
  Uname: Linux 5.4.0-58-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_58_64_generic_74 zfs zunicode zavl icp 
zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  egon   9806 F pulseaudio
   /dev/snd/controlC1:  egon   9806 F pulseaudio
   /dev/snd/pcmC1D0p:   egon   9806 F...m pulseaudio
  CasperMD5CheckResult: skip
  Date: Wed Jan 27 20:08:29 2021
  Dependencies:
   
  ErrorMessage: installed linux-firmware package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on

[Touch-packages] [Bug 1868330] Re: Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work

[Fedor]

Hello, did you fix this issue?

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

Title:
  Lenovo ThinkPad-X1-Carbon-7th Gen microphone doesnt work

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On Focal Fossa the microphone is recognised but doesn't work.

  Chromium shows the microphone as present but off, and if it is
  renabled it goes off again after a couple of seconds.

  Chromium logs this error:

  [ 2149.047888] sof-audio-pci :00:1f.3: error: no reply expected, received 
0x0
  [ 2149.177469] sof-audio-pci :00:1f.3: firmware boot complete
  [ 2160.561825] sof-audio-pci :00:1f.3: error: no reply expected, received 
0x0
  [ 2160.656755] sof-audio-pci :00:1f.3: firmware boot complete
  [ 2414.391790] sof-audio-pci :00:1f.3: error: no reply expected, received 
0x0
  [ 2414.487256] sof-audio-pci :00:1f.3: firmware boot complete

  Mar 20 23:09:24 user-ThinkPad-X1-Carbon-7th
  chromium_chromium.desktop[9531]:
  [9531:9531:0320/230924.861503:ERROR:pulse_util.cc(300)] pa_operation
  is nullptr.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu20
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   1687 F pulseaudio
   /dev/snd/pcmC0D0p:   user   1687 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 20 23:03:01 2020
  InstallationDate: Installed on 2020-03-11 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Black Mic, Right
  Symptom_Type: None of the above
  Title: [20R1000RUS, Realtek ALC285, Black Mic, Right] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET19W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20R1000RUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20R1000RUS
  dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-03-12T15:40:19.308712

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

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

[Touch-packages] [Bug 1913411] Re: While I updating ModemManager to 1.14.2, there isno mobile broadband in system status bar drop-down menu.

[Daniel van Vugt]

Thanks for the bug report. it appears version 1.14.2 is not supported on
Ubuntu 20.04. If you need that version then you might need to upgrade to
Ubuntu 20.10.

** Tags added: focal

** Changed in: gnome-shell (Ubuntu)
   Status: New => Invalid

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

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

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

Title:
  While I updating ModemManager to 1.14.2, there isno mobile broadband
  in system status bar drop-down menu.

Status in gnome-shell package in Ubuntu:
  Invalid
Status in modemmanager package in Ubuntu:
  Invalid

Bug description:
  While I updating ModemManager to 1.14.2, there isno mobile broadband in 
system status bar drop-down menu.
  I just can see mobile broadband in network in system settings menu.

  OS: ubuntu20.04
  Module: SDX55
  ModemManager:1.14.2
  iusse: 1.No mobile broadband in system status bar drop-down menu.
 2.Every time I connect to the mobile broadband network in system 
settings menu, I need to add new connection.

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

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

[Touch-packages] [Bug 1913499] Re: Bluetooth input doesn't work w/ Bose QC35 ii

[Daniel van Vugt]

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

Low quality audio when the mic is enabled is unfortunately a feature of
the old Bluetooth standard, which is the only Bluetooth standard
PulseAudio currently supports.

We currently have bug 1838151 open about this.

** This bug has been marked a duplicate of bug 1838151
   Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing wide 
band speech support (Bluetooth A2DP codecs).

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

Title:
  Bluetooth input doesn't work w/ Bose QC35 ii

Status in bluez package in Ubuntu:
  New

Bug description:
  When connecting the Bose QC35 ii, the bluetooth audio works just fine
  initially, but the microphone does not. When I go to the sound
  settings and change the mic input to use the QC35 ii bluetooth input,
  the audio changes from stereo to mono and sounds terrible and cannot
  understand anything. Also the mic picks up some input, but the result
  output sounds about the same, completely un-understandable, a
  stuttering digitized version of the input.

  > lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10

  Linux dan-xps-9700 5.10.5-051005-generic #202101061537 SMP Wed Jan 6
  15:43:53 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  3. I expected the microphone input and headset output to both work 
simultaneously via bluetooth.
  4. Only the headset output worked well, when enabling microphone both sounded 
terrible (unusable).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: bluez 5.55-0ubuntu1.1
  Uname: Linux 5.10.5-051005-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 27 17:53:00 2021
  InstallationDate: Installed on 2021-01-06 (21 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  InterestingModules: rfcomm bnep bluetooth
  MachineType: Dell Inc. XPS 17 9700
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.5-051005-generic 
root=UUID=d87c0f2c-adf4-493f-95dc-e2df02f584b3 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/03/2020
  dmi.bios.release: 1.4
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 03CPGC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd09/03/2020:br1.4:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn03CPGC:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 17 9700
  dmi.product.sku: 098F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: UART
BD Address: 28:C2:1F:87:52:EC  ACL MTU: 1024:8  SCO MTU: 240:4
UP RUNNING PSCAN 
RX bytes:1599 acl:0 sco:0 events:91 errors:0
TX bytes:198368 acl:0 sco:0 commands:849 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2021-01-27T17:24:11.108718

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

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

[Touch-packages] [Bug 1913485] Re: PulseEffects + YTMD

[Daniel van Vugt]

Please explain in more detail what kind of problem you are experiencing.

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

** Package changed: xorg (Ubuntu) => pulseeffects (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/1913485

Title:
  PulseEffects + YTMD

Status in pulseeffects package in Ubuntu:
  Incomplete

Bug description:
  when opening both apps its always a big complication with a lot a
  latency and distortion

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-64.72~18.04.1-generic 5.4.78
  Uname: Linux 5.4.0-64-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.21
  Architecture: amd64
  CompositorRunning: None
  Date: Wed Jan 27 13:56:37 2021
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 3rd Gen Core processor Graphics 
Controller [1025:0682]
  InstallationDate: Installed on 2018-01-28 (1095 days ago)
  InstallationMedia: Ubuntu 18.04.5 LTS "Bionic Beaver" - Release amd64 
(20200806.1)
  MachineType: Acer TravelMate P653-M
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=068acae8-2f26-4217-b2a3-e5afc4dd438d ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: V2.03.
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: TravelMate P653-M
  dmi.board.vendor: Acer
  dmi.board.version: V2.03.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V2.03.
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrV2.03.:bd10/16/2012:svnAcer:pnTravelMateP653-M:pvrV2.03.:rvnAcer:rnTravelMateP653-M:rvrV2.03.:cvnAcer:ct9:cvrV2.03.:
  dmi.product.family: TravelMate P653-M
  dmi.product.name: TravelMate P653-M
  dmi.product.sku: TravelMate P653-M_0682_2.03
  dmi.product.version: V2.03.
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  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 N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1913453] Re: Xorg freeze

[Daniel van Vugt]

Next time the problem starts please open a Terminal window and run:

  journalctl -b0 > curboot.txt

Or if you had to reboot then instead run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

Also, while the problem is happening, does 'top' show any process using
high CPU?



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

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

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

Title:
  Xorg freeze

Status in Ubuntu:
  Incomplete

Bug description:
  System
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  Description:
  Plugging in USB hub with peripherals while system is running causes gradual 
lag of a visual response, until freezing. usually takes < 1 min.  Only work 
around is to sleep system between plugging in hub.

  I thought I fixed it by change DM but the issue has persisted.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-64.72-generic 5.4.78
  Uname: Linux 5.4.0-64-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan 27 14:27:12 2021
  DistUpgraded: 2020-04-28 14:42:33,856 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.4.0-62-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-64-generic, x86_64: installed
   acpi-call, 1.1.0, 5.4.0-65-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa]
  InstallationDate: Installed on 2018-12-25 (763 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO 2324AS7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-64-generic 
root=UUID=957184f1-8feb-4ca9-ac97-3fb70937b4ac ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-04-28 (274 days ago)
  dmi.bios.date: 04/11/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ETB2WW (2.72 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2324AS7
  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: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ETB2WW(2.72):bd04/11/2018:svnLENOVO:pn2324AS7:pvrThinkPadX230:rvnLENOVO:rn2324AS7:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2324AS7
  dmi.product.sku: LENOVO_MT_2324
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~ppa1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  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
  xserver.bootTime: Tue Nov 24 16:32:27 2020
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.20.8-2ubuntu2.4
  xserver.video_driver: modeset

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

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