[Touch-packages] [Bug 1915491] Re: Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260 [8086:24f3]) installed but can't be found in Settings

2021-02-25 Thread You-Sheng Yang
** Tags added: hwe-networking-wifi

** Summary changed:

- Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260 
[8086:24f3]) installed but can't be found in Settings
+ Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260 [8086:24f3] 
subsystem [8086:0050]) installed but can't be found in Settings

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

Title:
  Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260
  [8086:24f3] subsystem [8086:0050]) installed but can't be found in
  Settings

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  # Summary:
  > ## Wifi Adpter Not found

  ## Steps to Reproduce:
  - I don't know

  
  ## Expected Results:
  Wifi should always be available

  ## Problem Description:
  Sometimes when startup my pc there is no wifi icon on the top right corner 
menu. When checking the wifi settings on the settings window it shows that the 
wifi adapter not found. But after restarting the pc, everything back to normal 
again. This is happening too frequently now.

  * * *

  
  Screenshot: 
https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 12 11:13:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Latitude E7470 [1028:06dc]
  InstallationDate: Installed on 2021-01-06 (36 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2018
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.3
  dmi.board.name: 047I7V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.product.sku: 06DC
  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 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 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/1915491/+subscriptions

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


[Touch-packages] [Bug 1743029] Re: glib-pacrunner assert failure: *** Error in `/usr/lib/glib-networking/glib-pacrunner': double free or corruption (!prev): 0x00007f01e80177d0 ***

2021-02-25 Thread Sudheer
I am facing this issue consistently each day. Please see the attachment
for more details. I reported the bug many times through the send report
option.

** Attachment added: "Screen Shot of the Internal Problem Report"
   
https://bugs.launchpad.net/ubuntu/+source/glib-networking/+bug/1743029/+attachment/5467427/+files/Screenshot%20from%202021-02-26%2011-57-04.png

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

Title:
  glib-pacrunner assert failure: *** Error in `/usr/lib/glib-networking
  /glib-pacrunner': double free or corruption (!prev):
  0x7f01e80177d0 ***

Status in glib-networking package in Ubuntu:
  Confirmed

Bug description:
  please solve this bug

  
  errors.u.c: 
https://errors.ubuntu.com/problem/852d2ea7be7d213614748a158517c62679fd6883

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: glib-networking-services 2.54.1-2
  ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
  Uname: Linux 4.13.0-21-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/lib/glib-networking/glib-pacrunner': 
double free or corruption (!prev): 0x7f01e80177d0 ***
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 13 00:54:46 2018
  ExecutablePath: /usr/lib/glib-networking/glib-pacrunner
  InstallationDate: Installed on 2017-12-29 (13 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcCmdline: /usr/lib/glib-networking/glib-pacrunner
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: glib-networking
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f01fb3974e8 
"*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (action=, str=0x7f01fb397820 "double free or 
corruption (!prev)", ptr=, ar_ptr=) at 
malloc.c:5425
   _int_free (av=0x7f01e820, p=, have_lock=0) at 
malloc.c:4174
   __GI___libc_free (mem=) at malloc.c:3144
   ?? () from /usr/lib/x86_64-linux-gnu/libproxy.so.1
  Title: glib-pacrunner assert failure: *** Error in 
`/usr/lib/glib-networking/glib-pacrunner': double free or corruption (!prev): 
0x7f01e80177d0 ***
  UpgradeStatus: Upgraded to bionic on 2018-01-03 (8 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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


[Touch-packages] [Bug 1915491] Re: Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260 [8086:24f3]) installed but can't be found in Settings

2021-02-25 Thread Daniel van Vugt
FYI other bugs with the same wifi chip: bug 1838836, bug 1880426

** No longer affects: gnome-control-center (Ubuntu)

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

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

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

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

Title:
  Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260
  [8086:24f3]) installed but can't be found in Settings

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  # Summary:
  > ## Wifi Adpter Not found

  ## Steps to Reproduce:
  - I don't know

  
  ## Expected Results:
  Wifi should always be available

  ## Problem Description:
  Sometimes when startup my pc there is no wifi icon on the top right corner 
menu. When checking the wifi settings on the settings window it shows that the 
wifi adapter not found. But after restarting the pc, everything back to normal 
again. This is happening too frequently now.

  * * *

  
  Screenshot: 
https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 12 11:13:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Latitude E7470 [1028:06dc]
  InstallationDate: Installed on 2021-01-06 (36 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2018
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.3
  dmi.board.name: 047I7V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.product.sku: 06DC
  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 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 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/1915491/+subscriptions

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


[Touch-packages] [Bug 1915491] Re: Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260 [8086:24f3]) installed but can't be found in Settings

2021-02-25 Thread Daniel van Vugt
Thanks. The iwconfig output seems to show the wifi adapter is missing at
the kernel level. When it was working your kernel log shows the adapter
was called 'wlp1s0'... Next time the problem happens, please run this
while it is happening:

  dmesg > dmesg.txt

and attach the resulting text file here.


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

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

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

Title:
  Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260
  [8086:24f3]) installed but can't be found in Settings

Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  # Summary:
  > ## Wifi Adpter Not found

  ## Steps to Reproduce:
  - I don't know

  
  ## Expected Results:
  Wifi should always be available

  ## Problem Description:
  Sometimes when startup my pc there is no wifi icon on the top right corner 
menu. When checking the wifi settings on the settings window it shows that the 
wifi adapter not found. But after restarting the pc, everything back to normal 
again. This is happening too frequently now.

  * * *

  
  Screenshot: 
https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 12 11:13:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Latitude E7470 [1028:06dc]
  InstallationDate: Installed on 2021-01-06 (36 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2018
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.3
  dmi.board.name: 047I7V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.product.sku: 06DC
  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 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 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/1915491/+subscriptions

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


[Touch-packages] [Bug 1915491] Re: Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260 [8086:24f3]) installed but can't be found in Settings

2021-02-25 Thread Daniel van Vugt
** Summary changed:

- Wifi adapter installed but can't be found in Settings
+ Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260 
[8086:24f3]) installed but can't be found in Settings

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => New

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

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

Title:
  Dell Latitude E7470 wifi adapter (Intel Corporation Wireless 8260
  [8086:24f3]) installed but can't be found in Settings

Status in gnome-control-center package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  # Summary:
  > ## Wifi Adpter Not found

  ## Steps to Reproduce:
  - I don't know

  
  ## Expected Results:
  Wifi should always be available

  ## Problem Description:
  Sometimes when startup my pc there is no wifi icon on the top right corner 
menu. When checking the wifi settings on the settings window it shows that the 
wifi adapter not found. But after restarting the pc, everything back to normal 
again. This is happening too frequently now.

  * * *

  
  Screenshot: 
https://drive.google.com/file/d/1i1gyhacC9I7zDHs4vGgxra9_7uvCDOR7/view?usp=sharing

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 12 11:13:48 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Latitude E7470 [1028:06dc]
  InstallationDate: Installed on 2021-01-06 (36 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic 
root=UUID=26d49ac7-77fe-4d5d-abbd-c857cbefc6f2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/20/2018
  dmi.bios.release: 1.20
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.20.3
  dmi.board.name: 047I7V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.20.3:bd08/20/2018:br1.20:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn047I7V:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.product.sku: 06DC
  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 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 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/gnome-control-center/+bug/1915491/+subscriptions

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


[Touch-packages] [Bug 1781917] Re: Misleading error message when adding PPA source

2021-02-25 Thread AlekseyK
So how to solve? Need to install this:
https://answers.launchpad.net/ubuntu/+source/git-cola/+question/695751

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

Title:
  Misleading error message when adding PPA source

Status in software-properties package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 LTS

  Please add the exception message to stdout, preferably in all cases
  where an exception is caught.

  When trying to add a ppa source, following error message was displayed

  ~$ sudo add-apt-repository ppa:ubuntu-toolchain-r/test
  Cannot add PPA: 'ppa:~ubuntu-toolchain-r/ubuntu/test'.
  ERROR: '~ubuntu-toolchain-r' user or team does not exist.

  After reading code and adding print statements in ppa.py, came to following 
exception:
   'Error reading 
https://launchpad.net/api/1.0/~ubuntu-toolchain-r/+archive/ubuntu/test: [SSL: 
CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:645)'

  Exception was thrown by 'get_ppa_info_from_lp(user, ppa)' called in
  'get_ppa_info(shortcut)'

  This has nothing to do with user or team, but was due to wrong
  time/date setting on my machine.

  Googling found that there are more users with the same problem having
  a different root-cause (e.g. proxy server settings)

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

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


[Touch-packages] [Bug 1916948] Re: AMD. Extreme slowness in xorg after upgrading to the 5.8.0-44-generic kernel (Ubuntu 20.04.2)

2021-02-25 Thread Daniel van Vugt
Please try a 5.10 kernel as well as a 5.4 kernel so we can get a better
idea of which versions are affected:

https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D

** Tags added: amdgpu radeon

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

** Summary changed:

- AMD. Extreme slowness in xorg after upgrading to the 5.8.0-44-generic kernel 
(Ubuntu 20.04.2)
+ [amdgpu] [radeon] Extreme slowness in xorg after upgrading to the 
5.8.0-44-generic kernel (Ubuntu 20.04.2)

** 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/1916948

Title:
  [amdgpu] [radeon] Extreme slowness in xorg after upgrading to the
  5.8.0-44-generic kernel (Ubuntu 20.04.2)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  UBUNTU 20.04.2 updated until 02/25/2021

  5.8.0-44-generic kernel

  xorg version: 1:7.7+19ubuntu14

  I expected to have a minimally acceptable performance, just as it was
  before the update.

  The problem only happens in sessions with XORG, either through the
  GNOME or UBUNTU session. The screen is extremely slow, with a slight
  increase in the temperature of components like CPU, nothing too
  serious. The animations are very slow and everything takes a long time
  to open or load, absurdly.

  The problem does not happen in the Wayland session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 25 16:41:02 2021
  DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1043:0513]
  InstallationDate: Installed on 2020-07-24 (216 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-10-23 (125 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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/1916948/+subscriptions

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


[Touch-packages] [Bug 1916950] Re: Screen fails to wake up after sleep

2021-02-25 Thread Daniel van Vugt
** Tags added: amdgpu

** Summary changed:

- Screen fails to wake up after sleep
+ [amdgpu] Screen fails to wake up after sleep

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

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #1427
   https://gitlab.freedesktop.org/drm/amd/-/issues/1427

** Also affects: linux via
   https://gitlab.freedesktop.org/drm/amd/-/issues/1427
   Importance: Unknown
   Status: Unknown

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

Title:
  [amdgpu] Screen fails to wake up after sleep

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  New

Bug description:
  It looks an awful lot like this issue :
  https://gitlab.freedesktop.org/drm/amd/-/issues/1427.

  I'm hitting these:
  [11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* 
dce112_get_pix_clk_dividers: Invalid parameters!!
  [11596.269781] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* 
Restoring old state failed with -22

  Switching to tty2 wakes it up and allows me to switch back and recover
  my xorg session.

  Should this be filed against the kernel, xorg, or amd drivers? I'm not
  sure..

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Feb 25 21:07:28 2021
  DistUpgraded: 2020-04-22 17:41:41,681 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 6.1.16, 5.4.0-64-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed
   virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed
   zfs, 0.8.3, 5.4.0-65-generic, x86_64: installed
   zfs, 0.8.3, 5.4.0-66-generic, x86_64: installed (WARNING! Diff between built 
and installed module!) (WARNING! Diff between built and installed module!) 
(WARNING! Diff between built and installed module!) (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] 
[1458:3701]
  InstallationDate: Installed on 2019-08-15 (560 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-66-generic 
root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash 
amd_iommu=on iommu=pt video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 
rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset 
usbhid.quirks=0x1b1c:0x1b44:0x2408 usbcore.quirks=1b1c:1b44:gn 
crashkernel=384M vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-04-22 (309 days ago)
  dmi.bios.date: 02/17/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F33c
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS PRO
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33c:bd02/17/2021:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X570 MB
  dmi.product.name: X570 AORUS PRO
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962
  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 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: 

[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_find_wind

2021-02-25 Thread Daniel van Vugt
Thanks, those stack traces are exactly what we needed. I can't find any
other reports of those crashes, but that's likely just because nobody
else had debugged it with GDK_SYNCHRONIZE yet...

Next please report the bug to the developers at
https://gitlab.gnome.org/GNOME/gtk/-/issues and remember to attach the
full stack traces from comments #25 and #28.

** Summary changed:

- GDK/GTK app crash when performing drag operation (in gdk_window_cache_new <- 
gdk_window_cache_get <- drag_context_find_window_cache <- 
gdk_x11_drag_context_find_window)
+ GDK/GTK app crash in XFCE when performing drag operation (in 
gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache 
<- gdk_x11_drag_context_find_window)

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => New

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

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Triaged

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

** No longer affects: thunar (Ubuntu)

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

Title:
  GDK/GTK app crash in XFCE when performing drag operation (in
  gdk_window_cache_new <- gdk_window_cache_get <-
  drag_context_find_window_cache <- gdk_x11_drag_context_find_window)

Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  

[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_find_wind

2021-02-25 Thread Daniel van Vugt
** Summary changed:

- GDK/GTK app crash when performing drag operation
+ GDK/GTK app crash when performing drag operation (in gdk_window_cache_new <- 
gdk_window_cache_get <- drag_context_find_window_cache <- 
gdk_x11_drag_context_find_window)

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

Title:
  GDK/GTK app crash in XFCE when performing drag operation (in
  gdk_window_cache_new <- gdk_window_cache_get <-
  drag_context_find_window_cache <- gdk_x11_drag_context_find_window)

Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => 

[Touch-packages] [Bug 1835541] Re: ibus only provides non-standard UK keyboard layouts

2021-02-25 Thread Bug Watch Updater
** Changed in: ibus (Debian)
   Status: Confirmed => Fix Released

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

Title:
  ibus only provides non-standard UK keyboard layouts

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

Bug description:
  When I attempt to add my standard UK keyboard to the layouts ibus
  knows about, I cannot do so.

  (See the attached image for the list of available layouts.)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: ibus 1.5.19-4ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu3
  Architecture: amd64
  CurrentDesktop: i3
  Date: Fri Jul  5 10:07:41 2019
  InstallationDate: Installed on 2019-05-07 (58 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: Upgraded to eoan on 2019-05-08 (57 days ago)

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

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


[Touch-packages] [Bug 1905768] Re: ld: DWARF error: could not find variable specification at offset

2021-02-25 Thread Bug Watch Updater
** Changed in: binutils (Debian)
   Status: New => Fix Released

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

Title:
  ld: DWARF error: could not find variable specification at offset

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils package in Debian:
  Fix Released

Bug description:
  Fixed upstream. Please update (I still get the error in
  2.35.1-1ubuntu1 on groovy).

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

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


[Touch-packages] [Bug 1916701] Re: [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, eventually comes up without Wayland support (only Xorg sessions offered)

2021-02-25 Thread Treviño
** Changed in: glib2.0 (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: glib2.0 (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed,
  eventually comes up without Wayland support (only Xorg sessions
  offered)

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  When I installed the glib2.0 2.67.4-1 packages I consistently
  encountered a black screen on boot. The login screen was
  missing/delayed but eventually comes up without Wayland support (only
  Xorg sessions offered).

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

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


[Touch-packages] [Bug 1916956] Re: mutter fails to run using wayland with glib2.0 2.67.4-1

2021-02-25 Thread Treviño
*** This bug is a duplicate of bug 1916701 ***
https://bugs.launchpad.net/bugs/1916701

** This bug has been marked a duplicate of bug 1916701
   [glib2.0 2.67.4-1] Black screen on boot, login screen missing/delayed, 
eventually comes up without Wayland support (only Xorg sessions offered)

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

Title:
  mutter fails to run using wayland with glib2.0 2.67.4-1

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  When hirsute-proposed is enabled (works fine in hirsute), mutter fails
  building as per xvfb not able to run:

  XIO:  fatal IO error 88 (Socket operation on non-socket) on X server ":99"
    after 209 requests (209 known processed) with 2 events remaining.
  (EE) could not connect to wayland server

  Full log at https://launchpadlibrarian.net/525081731/buildlog_ubuntu-
  hirsute-s390x.mutter_3.38.3-3ubuntu1inputthread1~wip2_BUILDING.txt.gz

  See more at
  https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu1

  This just happens by running in a session:
mutter --wayland --nested

  That fails instead of opening a nested compositor

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

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


[Touch-packages] [Bug 1869796] Re: vague error during upgrade

2021-02-25 Thread Bug Watch Updater
** Changed in: debhelper (Debian)
   Status: Incomplete => 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/1869796

Title:
  vague error during upgrade

Status in debhelper package in Ubuntu:
  New
Status in libvirt package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in debhelper package in Debian:
  New

Bug description:
  Seen from today's apt upgrade on focal:

  Setting up libvirt-daemon-driver-qemu (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-rbd (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-driver-storage-zfs (6.0.0-0ubuntu6) ...
  Setting up libvirt-daemon-system (6.0.0-0ubuntu6) ...
  Job failed. See "journalctl -xe" for details.
  virtlockd.service is a disabled or a static unit, not starting it.
  virtlogd.service is a disabled or a static unit, not starting it.
  Setting up libvirt-daemon dnsmasq configuration.

  
  Sadly 'journactl -xe' was useless. (It only showed a thousand unrelated 
lines.) A raw journalctl took forever to run long enough to let me see it 
generated two million lines of output, and started about two years ago, that 
I'm not keen on trying to run that through less or similar. Advice accepted.

  systemctl status looks good enough though:

  $ systemctl status 'libvirt*'
  ● libvirtd.socket - Libvirt local socket
   Loaded: loaded (/lib/systemd/system/libvirtd.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local
  socket.

  ● libvirtd.service - Virtualization daemon
   Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
  TriggeredBy: ● libvirtd-admin.socket
   ● libvirtd.socket
   ● libvirtd-ro.socket
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 3646435 (libvirtd)
Tasks: 19 (limit: 32768)
   Memory: 26.9M
   CGroup: /system.slice/libvirtd.service
   ├─   3054 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   ├─   3055 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
   └─3646435 /usr/sbin/libvirtd

  Mar 30 20:44:55 millbarge systemd[1]: Starting Virtualization daemon...
  Mar 30 20:44:55 millbarge systemd[1]: Started Virtualization daemon.
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read /etc/hosts - 7 addresses
  Mar 30 20:44:55 millbarge dnsmasq[3054]: read 
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
  Mar 30 20:44:55 millbarge dnsmasq-dhcp[3054]: read 
/var/lib/libvirt/dnsmasq/default.hostsfile

  ● libvirtd-admin.socket - Libvirt admin socket
   Loaded: loaded (/lib/systemd/system/libvirtd-admin.socket; enabled; 
vendor preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-admin-sock (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-admin.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt admin
  socket.

  ● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/lib/systemd/system/libvirt-guests.service; enabled; 
vendor preset: enabled)
   Active: active (exited) since Wed 2020-03-25 00:41:47 UTC; 5 days ago
 Docs: man:libvirtd(8)
   https://libvirt.org
 Main PID: 2808 (code=exited, status=0/SUCCESS)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirt-guests.service

  Mar 25 00:41:47 millbarge systemd[1]: Starting Suspend/Resume Running libvirt 
Guests...
  Mar 25 00:41:47 millbarge systemd[1]: Finished Suspend/Resume Running libvirt 
Guests.

  ● libvirtd-ro.socket - Libvirt local read-only socket
   Loaded: loaded (/lib/systemd/system/libvirtd-ro.socket; enabled; vendor 
preset: enabled)
   Active: active (running) since Mon 2020-03-30 20:44:55 UTC; 6min ago
 Triggers: ● libvirtd.service
   Listen: /run/libvirt/libvirt-sock-ro (Stream)
Tasks: 0 (limit: 18814)
   Memory: 0B
   CGroup: /system.slice/libvirtd-ro.socket

  Mar 30 20:44:55 millbarge systemd[1]: Listening on Libvirt local read-
  only socket.

  
  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libvirt-daemon 6.0.0-0ubuntu6
 

[Touch-packages] [Bug 1883297] Re: dh-python's autopkg tests fail with python3.8 as the only supported python3 version

2021-02-25 Thread Bug Watch Updater
** Changed in: dh-python (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  dh-python's autopkg tests fail with python3.8 as the only supported
  python3 version

Status in dh-python package in Ubuntu:
  Fix Released
Status in dh-python package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/956190:

  Package: dh-python
  Version: 4.20200315
  Severity: serious
  Tags: sid bullseye

  dh-python's autopkg tests fail with python3.8 as the only supported
  python3 version.

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

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


[Touch-packages] [Bug 1916956] Re: mutter fails to run using wayland with glib2.0 2.67.4-1

2021-02-25 Thread Treviño
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2332
   https://gitlab.gnome.org/GNOME/glib/-/issues/2332

** Also affects: xorg-server via
   https://gitlab.gnome.org/GNOME/glib/-/issues/2332
   Importance: Unknown
   Status: Unknown

** Changed in: glib2.0 (Ubuntu)
   Status: New => Triaged

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Critical

** Project changed: xorg-server => glib

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

Title:
  mutter fails to run using wayland with glib2.0 2.67.4-1

Status in GLib:
  Unknown
Status in glib2.0 package in Ubuntu:
  Triaged
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  When hirsute-proposed is enabled (works fine in hirsute), mutter fails
  building as per xvfb not able to run:

  XIO:  fatal IO error 88 (Socket operation on non-socket) on X server ":99"
    after 209 requests (209 known processed) with 2 events remaining.
  (EE) could not connect to wayland server

  Full log at https://launchpadlibrarian.net/525081731/buildlog_ubuntu-
  hirsute-s390x.mutter_3.38.3-3ubuntu1inputthread1~wip2_BUILDING.txt.gz

  See more at
  https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu1

  This just happens by running in a session:
mutter --wayland --nested

  That fails instead of opening a nested compositor

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

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


[Touch-packages] [Bug 1916956] Re: xvfb fails when building mutter in hirsute-proposed

2021-02-25 Thread Treviño
** Changed in: xorg-server (Ubuntu)
   Status: New => Invalid

** Summary changed:

- xvfb fails when building mutter in hirsute-proposed
+ mutter fails to run using wayland with glib2.0 2.67.4-1

** Description changed:

  When hirsute-proposed is enabled (works fine in hirsute), mutter fails
  building as per xvfb not able to run:
  
  XIO:  fatal IO error 88 (Socket operation on non-socket) on X server ":99"
-   after 209 requests (209 known processed) with 2 events remaining.
+   after 209 requests (209 known processed) with 2 events remaining.
  (EE) could not connect to wayland server
  
  Full log at https://launchpadlibrarian.net/525081731/buildlog_ubuntu-
  hirsute-s390x.mutter_3.38.3-3ubuntu1inputthread1~wip2_BUILDING.txt.gz
+ 
+ See more at https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu1
+ 
+ This just happens by running in a session:
+   mutter --wayland --nested
+ 
+ That fails instead of opening a nested compositor

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

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

Title:
  mutter fails to run using wayland with glib2.0 2.67.4-1

Status in glib2.0 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  When hirsute-proposed is enabled (works fine in hirsute), mutter fails
  building as per xvfb not able to run:

  XIO:  fatal IO error 88 (Socket operation on non-socket) on X server ":99"
    after 209 requests (209 known processed) with 2 events remaining.
  (EE) could not connect to wayland server

  Full log at https://launchpadlibrarian.net/525081731/buildlog_ubuntu-
  hirsute-s390x.mutter_3.38.3-3ubuntu1inputthread1~wip2_BUILDING.txt.gz

  See more at
  https://launchpad.net/ubuntu/+source/mutter/3.38.3-3ubuntu1

  This just happens by running in a session:
mutter --wayland --nested

  That fails instead of opening a nested compositor

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

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


[Touch-packages] [Bug 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

2021-02-25 Thread Bug Watch Updater
** Changed in: pam (Debian)
   Status: New => Fix Released

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  Confirmed
Status in pam source package in Groovy:
  Confirmed
Status in pam package in Debian:
  Fix Released

Bug description:
  Hello, after upgrading to focal I found the following in my journalctl
  output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  
  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

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

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


[Touch-packages] [Bug 1895839] Re: CVE-2020-24977

2021-02-25 Thread Mattia Rizzolo
** Also affects: libxml2 (Ubuntu Hirsute)
   Importance: High
   Status: Confirmed

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

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

Title:
  CVE-2020-24977

Status in libxml2 package in Ubuntu:
  Fix Released
Status in libxml2 source package in Hirsute:
  Fix Released
Status in libxml2 package in Debian:
  Fix Released

Bug description:
  GNOME project libxml2 v2.9.10 and earlier have a global buffer over-
  read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c.

  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977

  Upstream patch: 
  
https://gitlab.gnome.org/GNOME/libxml2/-/commit/50f06b3efb638efb0abd95dc62dca05ae67882c2

  Bug report: https://gitlab.gnome.org/GNOME/libxml2/-/issues/178

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

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


[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

2021-02-25 Thread Bug Watch Updater
** Changed in: avahi (Debian)
   Status: New => Fix Released

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Fix Released
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Fix Released
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  Fix Released
Status in bind9 source package in Cosmic:
  Confirmed
Status in avahi package in Debian:
  Fix Released

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: openconnect
  UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago)

To manage notifications about this bug 

[Touch-packages] [Bug 1826639] Re: wpasupplicant: unknown keys in no-mac-addr-change.conf

2021-02-25 Thread Bug Watch Updater
** Changed in: wpa (Debian)
   Status: New => Fix Released

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

Title:
  wpasupplicant: unknown keys in no-mac-addr-change.conf

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Focal:
  Fix Released
Status in wpa package in Debian:
  Fix Released

Bug description:
  * Impact
  wpa ships an invalid network-manager configuration that triggers warnings

  * Test case
  $ journalctl | grep no-mac-addr-change
  should not have errors listed

  * Regression potential
  the change removes configurations which are not needed (since they set the 
value to the same one as the default) and in the wrong section, it shouldn't 
have any visible impact

  

  Hi,

  NetworkManager warns that no-mac-addr-change.conf contains unknown
  configuration directives:

  # journalctl | grep no-mac-addr-change
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] Read 
config: /etc/NetworkManager/NetworkManager.conf (lib: 10-dns-resolved.conf, 
20-connectivity-ubuntu.conf, no-mac-addr-change.conf) (etc: 
10-globally-managed-devices.conf, default-wifi-powersave-on.conf)
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'wifi.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'
  Apr 25 09:24:50 vougeot NetworkManager[573]:   [1556177090.0596] 
config: unknown key 'ethernet.cloned-mac-address' in section 
[device-mac-addr-change-wifi] of file 
'/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: wpasupplicant 2:2.6-21ubuntu3
  Uname: Linux 5.0.9-050009-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Apr 27 13:15:27 2019
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1897620] Re: ABI breakage: paths changed for sysusers.d/sysctl.d/binfmt/modules-load.d

2021-02-25 Thread Bug Watch Updater
** Changed in: systemd (Debian)
   Status: New => Fix Released

** Changed in: systemd (Debian)
   Importance: Undecided => Unknown

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

Title:
  ABI breakage: paths changed for sysusers.d/sysctl.d/binfmt/modules-
  load.d

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd package in Debian:
  Fix Released

Bug description:
  Imported from Debian bug http://bugs.debian.org/971282:

  Package: systemd
  Version: 246.6-1
  Severity: important

  Upstream changed the paths in systemd.pc from prefix to rootprefix in
  v246 for sysusers_dir, sysctl_dir, binfmt_dir and modules-load_dir:
  
https://github.com/systemd/systemd/commit/4a56315a990b802860170ecd1bbd3eb68e14a38b

  This breaks packages which use pkg-config to determine those paths and
  where .install files reference /usr/. An example is mandos.

  I think we should revert this change. I don't see a compelling reason to
  move those files from /usr to /lib given that we require /usr to be
  pre-mounted by initramfs, if it's separate.
  Moving files from /usr to /lib files kinda backwards nowadays.

  I intend to apply a patch like the attached one in Debian.
  That said, I hope I can convince Lennart to revert this change upstream
  as well.

  Thoughts, Comments?

  Michael

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

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


[Touch-packages] [Bug 1895839] Re: CVE-2020-24977

2021-02-25 Thread Bug Watch Updater
** Changed in: libxml2 (Debian)
   Status: Unknown => Fix Released

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

Title:
  CVE-2020-24977

Status in libxml2 package in Ubuntu:
  Confirmed
Status in libxml2 package in Debian:
  Fix Released

Bug description:
  GNOME project libxml2 v2.9.10 and earlier have a global buffer over-
  read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c.

  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977

  Upstream patch: 
  
https://gitlab.gnome.org/GNOME/libxml2/-/commit/50f06b3efb638efb0abd95dc62dca05ae67882c2

  Bug report: https://gitlab.gnome.org/GNOME/libxml2/-/issues/178

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

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


[Touch-packages] [Bug 1913951] Re: ca-certificates: Symantec CA blacklisted for non-TLS uses

2021-02-25 Thread Bug Watch Updater
** Changed in: ca-certificates (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  ca-certificates:  Symantec CA blacklisted for non-TLS uses

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Groovy:
  Fix Released
Status in ca-certificates source package in Hirsute:
  Fix Released
Status in ca-certificates package in Debian:
  Fix Released

Bug description:
  ~$ lsb_release -rd
  Description:  Ubuntu 20.10
  Release:  20.10
  ~$ apt list --installed | grep ca-certificates

  WARNING: apt does not have a stable CLI interface. Use with caution in
  scripts.

  ca-certificates/groovy-updates,groovy-security,now
  20201027ubuntu0.20.10.1 all [installed,automatic]

  
  Repro steps:

  1.  Open Terminal.
  2.  Execute:

wget https://dot.net/v1/dotnet-install.sh
chmod +x ./dotnet-install.sh
./dotnet-install.sh -c 5.0
export DOTNET_ROOT=$HOME/.dotnet
export PATH=$PATH:$HOME/.dotnet
dotnet new console
dotnet add package System.Collections.Immutable

  Expected result:
Package restore will succeed.

  Actual result:
Package restore fails with:

error: NU3028: Package 'System.Collections.Immutable 5.0.0' from
  source 'https://api.nuget.org/v3/index.json': The author primary
  signature's timestamp found a chain building issue: UntrustedRoot:
  self signed certificate in certificate chain

  
  There has been a planned process to distrust Symantec certificates in the 
certificate store over the past two years.  The Debian ca-certificates package 
removed this CA for both TLS (expected) and other uses (like timestamping) 
(unexpected).  Trust was added back in a subsequent update.  See 
https://release.debian.org/proposed-updates/stable.html#ca-certificates_20200601~deb10u2
 for details.

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

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


[Touch-packages] [Bug 1902898] Re: power-button action inconsistent between user session and greeter

2021-02-25 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-settings - 21.04.1

---
ubuntu-settings (21.04.1) hirsute; urgency=medium

  * debian/ubuntu-settings.gsettings-override:
- use the same power options between session and greeter. (LP: #1902898)

 -- Didier Roche   Thu, 25 Feb 2021 13:07:54 +0100

** Changed in: ubuntu-settings (Ubuntu Hirsute)
   Status: Confirmed => Fix Released

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

Title:
  power-button action inconsistent between user session and greeter

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Focal:
  Incomplete
Status in ubuntu-settings source package in Groovy:
  Incomplete
Status in ubuntu-settings source package in Hirsute:
  Fix Released

Bug description:
  When a user is logged in to the Ubuntu desktop, a power button event
  will cause the user to be prompted to choose if they'd like to proceed
  with a shutdown. However, if the system is sitting at a greeter
  screen, a power button event will instead attempt a suspend w/o
  prompting. This is due to a different set of defaults for the greeter
  and the user:

  For a logged-in desktop user, they
  see:

  $ gsettings get org.gnome.settings-daemon.plugins.power
  power-button-action 'interactive'

  But the gdm user sees:
  $ sudo machinectl shell gdm@ /bin/bash
  Connected to the local host. Press ^] three times within 1s to exit session.
  gdm:~$ gsettings get org.gnome.settings-daemon.plugins.power 
power-button-action
  'suspend'

  Changing the gdm user's setting to "interactive" using gsettings
  causes the greeter to begin prompting, consistent with the logged in
  user experience.

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

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


[Touch-packages] [Bug 1916948] Re: AMD. Extreme slowness in xorg after upgrading to the 5.8.0-44-generic kernel (Ubuntu 20.04.2)

2021-02-25 Thread sepukkuhero
** Attachment removed: "a"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1916948/+attachment/5467211/+files/a

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

Title:
  AMD. Extreme slowness in xorg after upgrading to the 5.8.0-44-generic
  kernel (Ubuntu 20.04.2)

Status in xorg package in Ubuntu:
  New

Bug description:
  UBUNTU 20.04.2 updated until 02/25/2021

  5.8.0-44-generic kernel

  xorg version: 1:7.7+19ubuntu14

  I expected to have a minimally acceptable performance, just as it was
  before the update.

  The problem only happens in sessions with XORG, either through the
  GNOME or UBUNTU session. The screen is extremely slow, with a slight
  increase in the temperature of components like CPU, nothing too
  serious. The animations are very slow and everything takes a long time
  to open or load, absurdly.

  The problem does not happen in the Wayland session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 25 16:41:02 2021
  DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000]
   Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / 
RX 540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1043:0513]
  InstallationDate: Installed on 2020-07-24 (216 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-10-23 (125 days ago)
  dmi.bios.date: 11/25/2014
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-USB3 6.0
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: SEx
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-USB3 6.0
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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/1916948/+subscriptions

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


[Touch-packages] [Bug 1509717] Re: Wily LVM-RAID1 – md: personality for level 1 is not loaded

2021-02-25 Thread Bug Watch Updater
** Changed in: lvm2 (Debian)
   Status: Incomplete => Fix Released

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

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in lvm2 source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Invalid
Status in lvm2 source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Invalid
Status in lvm2 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Invalid
Status in lvm2 source package in Eoan:
  Fix Released
Status in lvm2 package in Debian:
  Fix Released

Bug description:
  [Impact]
  system does not boot after converting lvm volume to raid1 w/o having mdadm 
installed.

  [Test case]

  1. Install server to LVM
  2. Add second disk to it
  3. Run pvcreate /dev/vdb
  4. Run vgextend ubuntu-vg /dev/vdb
  5. Run lvconvert -m1 --type raid1 ubuntu-vg/ubuntu-lv

  Reboot and check that it still boots.

  6. Remove mdadm
  7. Upgrade to lvm2 from proposed

  Reboot and check that it still boots.

  8. Downgrade lvm2 to release

  Reboot and check that it fails to boot

  [Regression potential]
  Not really anything, we just add the raid1 module to initramfs, so it might 
be loaded during boot, and raid1 logical volumes might appear earlier.

  [Original bug report]
  After upgrading to Wily, raid1 LVs don't activate during the initrd phase. 
Since the root LV is also RAID1-mirrored, the system doesn't boot.

  I get the following message each time LVM tries to activate a raid1 LV:
  md: personality for level 1 is not loaded!

  Everything was fine with Vivid. I had to downgrade to Vivid kernel
  (3.19.0-30) to get my system to a usable state. I pretty much hope it
  to be a temporary workaround and I'll get the new 4.2.0 kernel work
  with Wily in days.

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

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


[Touch-packages] [Bug 1073323] Re: Add simple test cases

2021-02-25 Thread Bug Watch Updater
** Changed in: gzip (Debian)
   Status: New => Fix Released

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

Title:
  Add simple test cases

Status in gzip package in Ubuntu:
  Fix Released
Status in gzip package in Debian:
  Fix Released

Bug description:
  The branch adds a simple test case to check if gzip/gunzip works.

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

-- 
Mailing list: https://launchpad.net/~touch-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

2021-02-25 Thread Andreas Hasenack
postgresql-common amd64 and i386: passed after a retry
ubuntu-fan: see previous comment, known flaky test, and analysis of the test 
output shows that the test actually passed. I retried both amd64 and s390x, but 
I ask the SRU team to consider those runs green if they failed again (update: 
amd64 just passed, s390x still pending results).

-- 
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 1916950] [NEW] Screen fails to wake up after sleep

2021-02-25 Thread Anders Aagaard
Public bug reported:

It looks an awful lot like this issue :
https://gitlab.freedesktop.org/drm/amd/-/issues/1427.

I'm hitting these:
[11596.268677] [drm:dce112_get_pix_clk_dividers [amdgpu]] *ERROR* 
dce112_get_pix_clk_dividers: Invalid parameters!!
[11596.269781] [drm:dm_restore_drm_connector_state [amdgpu]] *ERROR* Restoring 
old state failed with -22

Switching to tty2 wakes it up and allows me to switch back and recover
my xorg session.

Should this be filed against the kernel, xorg, or amd drivers? I'm not
sure..

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86
Uname: Linux 5.4.0-66-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Feb 25 21:07:28 2021
DistUpgraded: 2020-04-22 17:41:41,681 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 6.1.16, 5.4.0-64-generic, x86_64: installed
 virtualbox, 6.1.16, 5.4.0-65-generic, x86_64: installed
 virtualbox, 6.1.16, 5.4.0-66-generic, x86_64: installed
 zfs, 0.8.3, 5.4.0-65-generic, x86_64: installed
 zfs, 0.8.3, 5.4.0-66-generic, x86_64: installed (WARNING! Diff between built 
and installed module!) (WARNING! Diff between built and installed module!) 
(WARNING! Diff between built and installed module!) (WARNING! Diff between 
built and installed module!) (WARNING! Diff between built and installed 
module!) (WARNING! Diff between built and installed module!) (WARNING! Diff 
between built and installed module!) (WARNING! Diff between built and installed 
module!)
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 
540/540X/550/550X / RX 540X/550/550X] [1002:0b04]
 NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP104 [GeForce GTX 1070] [1458:3701]
InstallationDate: Installed on 2019-08-15 (560 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Gigabyte Technology Co., Ltd. X570 AORUS PRO
ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_fnpezh@/vmlinuz-5.4.0-66-generic 
root=ZFS=rpool/ROOT/ubuntu_fnpezh ro usbcore.autosuspend=-1 quiet splash 
amd_iommu=on iommu=pt video=efifb:off,vesafb=off,simplefb=off nouveau.modeset=0 
rd.driver.blacklist=nouveau,nvidia,nvidia_uvm,nvidia_drm,nvidia_modeset 
usbhid.quirks=0x1b1c:0x1b44:0x2408 usbcore.quirks=1b1c:1b44:gn 
crashkernel=384M vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-04-22 (309 days ago)
dmi.bios.date: 02/17/2021
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F33c
dmi.board.asset.tag: Default string
dmi.board.name: X570 AORUS PRO
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF33c:bd02/17/2021:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSPRO:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSPRO:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570 AORUS PRO
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2020-03-23T10:46:45.197962
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 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 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 kubuntu 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/1916950

Title:
  Screen fails to wake up after sleep

Status in xorg package in Ubuntu:
  New

Bug description:
  It looks an awful lot like this issue :
  https://gitlab.freedesktop.org/drm/amd/-/issues/1427.

  I'm hitting these:
  [11596.268677] 

[Touch-packages] [Bug 1916948] [NEW] AMD. Extreme slowness in xorg after upgrading to the 5.8.0-44-generic kernel (Ubuntu 20.04.2)

2021-02-25 Thread sepukkuhero
Public bug reported:

UBUNTU 20.04.2 updated until 02/25/2021

5.8.0-44-generic kernel

xorg version: 1:7.7+19ubuntu14

I expected to have a minimally acceptable performance, just as it was
before the update.

The problem only happens in sessions with XORG, either through the GNOME
or UBUNTU session. The screen is extremely slow, with a slight increase
in the temperature of components like CPU, nothing too serious. The
animations are very slow and everything takes a long time to open or
load, absurdly.

The problem does not happen in the Wayland session.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 25 16:41:02 2021
DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000]
 Advanced Micro Devices, Inc. [AMD/ATI] Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1002:699f] (rev c7) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Lexa PRO [Radeon 540/540X/550/550X / RX 
540X/550/550X] [1043:0513]
InstallationDate: Installed on 2020-07-24 (216 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-44-generic 
root=UUID=b12510e7-1702-4d36-80bc-11251ef87185 ro quiet splash radeon.audio=1 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-10-23 (125 days ago)
dmi.bios.date: 11/25/2014
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F2
dmi.board.name: GA-78LMT-USB3 6.0
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: SEx
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: GA-78LMT-USB3 6.0
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
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 performance ubuntu wayland-session

** Attachment added: "a"
   https://bugs.launchpad.net/bugs/1916948/+attachment/5467211/+files/a

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

Title:
  AMD. Extreme slowness in xorg after upgrading to the 5.8.0-44-generic
  kernel (Ubuntu 20.04.2)

Status in xorg package in Ubuntu:
  New

Bug description:
  UBUNTU 20.04.2 updated until 02/25/2021

  5.8.0-44-generic kernel

  xorg version: 1:7.7+19ubuntu14

  I expected to have a minimally acceptable performance, just as it was
  before the update.

  The problem only happens in sessions with XORG, either through the
  GNOME or UBUNTU session. The screen is extremely slow, with a slight
  increase in the temperature of components like CPU, nothing too
  serious. The animations are very slow and everything takes a long time
  to open or load, absurdly.

  The problem does not happen in the Wayland session.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 25 16:41:02 2021
  DistUpgraded: 2020-10-23 13:38:17,737 DEBUG /openCache(), new cache size 66390
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro 

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

2021-02-25 Thread Andreas Hasenack
ubuntu-fan dep8 failures are due to
https://bugs.launchpad.net/ubuntu/+source/ubuntu-fan/+bug/1830180. It
was fixed in focal+, but in bionic it remains flaky. Explanation is in
https://bugs.launchpad.net/ubuntu/+source/ubuntu-
fan/+bug/1830180/comments/1

I'll retry it once or twice, but we can see from the test output that the test 
worked, and the stderr text is just noise that happened because systemd-resolve 
was called too soon:
Starting fanatic-test
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
slave: detected primary route through eth0
sd_bus_open_system: No such file or directory <-- too soon
slave: waiting for systemd resolver...
slave: DNS: systemd(250.40.8.1) <--- now it worked, and the test continues
...

-- 
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 1916893] Re: Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode parts cause serious regressions

2021-02-25 Thread Leonidas S. Barbosa
Regression update reverting the CVE-2021-3177 patch was made:
https://ubuntu.com/security/notices/USN-4754-2

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3177

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

Title:
  Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode
  parts cause serious regressions

Status in python2.7 package in Ubuntu:
  New

Bug description:
  [Scenario]
  A security update was made for python2.7 in xenial and bionic that can cause 
a serious regression since it is modifying unicode code for python2.7.

  [Issue]
  It can cause a serious break in the way python prints, rprs, unicode 
information, causing serious damage for any application that is running 
python2.7 in that scenario.

  [More info]
  https://ubuntu.com/security/CVE-2021-3177

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916893/+subscriptions

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


[Touch-packages] [Bug 1885646] Re: RM ring FTBFS

2021-02-25 Thread Bug Watch Updater
** Changed in: ring (Debian)
   Status: New => Fix Released

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

Title:
  RM ring FTBFS

Status in nettle package in Ubuntu:
  Incomplete
Status in ring package in Ubuntu:
  Fix Released
Status in ring package in Debian:
  Fix Released

Bug description:
  Please remove
  ring 20190215.1.f152c98~ds1-1build4 groovy-proposed
  ring 20190215.1.f152c98~ds1-1build2 groovy-release

  FTBFS, RC-buggy, removed from testing

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

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


[Touch-packages] [Bug 1905735] Re: ubuntu-image autopkgtests failing since python-debian 0.1.38

2021-02-25 Thread Bug Watch Updater
** Changed in: python-debian (Debian)
   Status: Unknown => Fix Released

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

Title:
  ubuntu-image autopkgtests failing since python-debian 0.1.38

Status in python-debian package in Ubuntu:
  Fix Committed
Status in ubuntu-image package in Ubuntu:
  Fix Released
Status in python-debian package in Debian:
  Fix Released

Bug description:
  In the tests it seems that since some - yet to be found - change ~20th
  Nov the tests of ubuntu-image fail.

  Tests all list those three sub-tests as failing:
   unittests.sh FAIL non-zero exit status 1
   qa   FAIL non-zero exit status 1
   coverage.sh  FAIL non-zero exit status 1

  Fails all seem to be related to some python/pytest/py* change that
  might have slipped in without gating on this test.

  Ubuntu-image itself also isn't new - still the same as in groovy
   ubuntu-image | 1.10+20.10ubuntu2 | groovy | source, all
   ubuntu-image | 1.10+20.10ubuntu2 | hirsute| source, all

  == log start 
===
  Obtaining file:///tmp/autopkgtest.ZuL7Da/build.chY/src
  ERROR: Command errored out with exit status 1:
   command: 
/tmp/autopkgtest.ZuL7Da/build.chY/src/.tox/py38-nocov/bin/python -c 'import 
sys, setuptools, tokenize; sys.argv[0] = 
'"'"'/tmp/autopkgtest.ZuL7Da/build.chY/src/setup.py'"'"'; 
__file__='"'"'/tmp/autopkgtest.ZuL7Da/build.chY/src/setup.py'"'"';f=getattr(tokenize,
 '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', 
'"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info 
--egg-base /tmp/pip-pip-egg-info-yaplrymq
   cwd: /tmp/autopkgtest.ZuL7Da/build.chY/src/
  Complete output (5 lines):
  Traceback (most recent call last):
    File "", line 1, in 
    File "/tmp/autopkgtest.ZuL7Da/build.chY/src/setup.py", line 49, in 

  __version__ = str(Changelog(infp).get_version())
  AttributeError: 'Changelog' object has no attribute 'get_version'
  
  ERROR: Command errored out with exit status 1: python setup.py egg_info Check 
the logs for full command output.
  === log end 


  The issue reproducible in local KVM-autopkgtest against hirsute-proposed and 
hirsute-release for me (I mistyped before).
  Example:
   sudo ~/work/autopkgtest/autopkgtest/runner/autopkgtest --no-built-binaries 
--apt-upgrade --apt-pocket=proposed --shell-fail 
ubuntu-image_1.10+20.10ubuntu2.dsc --testname=qa -- qemu --qemu-options='-cpu 
host' --ram-size=1536 --cpus 2 ~/work/autopkgtest-hirsute-amd64.img

  
  In terms of similar bug signatures I found
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973227
  Fixed by:
  
https://gitlab.kitware.com/debian/dh-cmake/-/commit/3337c8e0e9ebd109490d3c40f0bd5c1e367bedc8

  Looking for the same issue in ubuntu-image has shown an entry in setup.py
    setup.py:49:__version__ = str(Changelog(infp).get_version())

  And now that we know all that we see
  https://launchpad.net/ubuntu/+source/python-debian/+publishinghistory

  New version in since
  2020-11-20 02:23:27 CET

  That is a perfect match to our bug.


  $ diff -Naur python-debian-0.1.3[78]/lib/debian/changelog.py
  ...
  -def get_version(self):
  -# type: () -> Version
  +def _get_version(self):
  +# type: () -> Optional[Version]
   """Return a Version object for the last version"""
  -return self._blocks[0].version
  +return self._blocks[0].version   # type: ignore
  ...

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

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


[Touch-packages] [Bug 1889301] Re: package sudo 1.8.31-1ubuntu1 failed to install/upgrade: o subprocesso instalado, do pacote sudo, o script pre-removal retornou erro do status de saída 1

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

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

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

Title:
  package sudo 1.8.31-1ubuntu1 failed to install/upgrade: o subprocesso
  instalado, do pacote sudo, o script pre-removal retornou erro do
  status de saída 1

Status in sudo package in Ubuntu:
  Confirmed

Bug description:
  I don't know, it just came up at the initialization proccess.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: sudo 1.8.31-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  AptOrdering:
   ubuntu-minimal:amd64: Remove
   sudo:amd64: Remove
   surfshark-vpn:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jul 27 03:06:04 2020
  ErrorMessage: o subprocesso instalado, do pacote sudo, o script pre-removal 
retornou erro do status de saída 1
  InstallationDate: Installed on 2020-05-24 (65 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: sudo
  Title: package sudo 1.8.31-1ubuntu1 failed to install/upgrade: o subprocesso 
instalado, do pacote sudo, o script pre-removal retornou erro do status de 
saída 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: análise OK
   /etc/sudoers.d/README: análise OK

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

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


[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation

2021-02-25 Thread XXX
** Attachment added: "--gtk-debug=all output from thunar"
   
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1911036/+attachment/5467187/+files/thunar-debug3.out

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fdbb45dd000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdbb43e9000)
  libgmodule-2.0.so.0 => 

[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation

2021-02-25 Thread XXX
Here's the gdb & gtk-debug=all output from thunar.

** Attachment added: "thunar gdb output"
   
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1911036/+attachment/5467186/+files/thunar-gdb.out

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fdbb45dd000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdbb43e9000)
 

[Touch-packages] [Bug 1916893] Re: Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode parts cause serious regressions

2021-02-25 Thread Steve Beattie
** Information type changed from Private Security to Public Security

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

Title:
  Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode
  parts cause serious regressions

Status in python2.7 package in Ubuntu:
  New

Bug description:
  [Scenario]
  A security update was made for python2.7 in xenial and bionic that can cause 
a serious regression since it is modifying unicode code for python2.7.

  [Issue]
  It can cause a serious break in the way python prints, rprs, unicode 
information, causing serious damage for any application that is running 
python2.7 in that scenario.

  [More info]
  https://ubuntu.com/security/CVE-2021-3177

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916893/+subscriptions

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


[Touch-packages] [Bug 1916915] Re: Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale)

2021-02-25 Thread Colin Watson
This update was broken and intentionally reverted.  There should be a
USN update coming soon, and it will be superseded by a newer version,
but it was better to quickly withdraw the update to avoid causing
serious breakage.

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

Title:
  Incorrect package version available on bionic pool
  (2.7.17-1~18.04ubuntu1.3 not availbale)

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Apt tries to get the python2.7 package and some of its dependencies
  with version (2.7.17-1~18.04ubuntu1.3). However it returns an error
  with:

  Failed to fetch
  
http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.88.152 80]

  The problem is present on BIONIC distro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916915/+subscriptions

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


[Touch-packages] [Bug 1916931] [NEW] omshell returns inconsistent results or segfaults

2021-02-25 Thread Bill MacAllister
Public bug reported:

I have just built a Ubuntu 20.04 server and installed isc-dhcp-server
4.4.1 on it and I am seeing inconsistent returns from omshell. 
Initially omshell returns data as expected, but when I exit and re-enter 
omshell connections fail.

Here is the initial, working, session:

# omshell
> server localhost
> port 7911
> key omapi_key 
> connect
obj: 
> new failover-state
obj: failover-state
> set name = "dhcp-failover"
obj: failover-state
name = "dhcp-failover"
> open
obj: failover-state
name = "dhcp-failover"
partner-address = c0:9d:e9:76:e9:55:00:00
partner-port = 00:00:02:07
local-address = 10:9d:e9:76:e9:55:00:00
local-port = 00:00:02:07
max-outstanding-updates = 00:00:00:0a
mclt = 00:00:01:2c
load-balance-max-secs = 00:00:00:03
load-balance-hba =
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
partner-state = 00:00:00:02
local-state = 00:00:00:02
partner-stos = 60:36:d0:68
local-stos = 60:36:8b:3b
hierarchy = 00:00:00:01
last-packet-sent = 00:00:00:00
last-timestamp-received = 00:00:00:00
skew = 00:00:00:00
max-response-delay = 00:00:00:3c
cur-unacked-updates = 00:00:00:00

Here is what I see when the connect fails.  Well, just hangs really.

# omshell
> server localhost
> port 7911
> key omapi_key 
> connect

And then I hit ctrl-c to break out and tried again:

# omshell
> server localhost
> port 7911
> key omapi_key 
> connect
Segmentation fault (core dumped)

Note, the peer to this server is still running Ubuntu 18.04 with
isc-dhcp-server 4.3.5.  Running the exact same commands on the peer
works reliably.  (They are using the same python script to drive
omshell.)  The DHCP server on the new system appears to be working 
just fine as reported by omshell on the peer and systemctl.

I was curious if the problem could be with the mis-matched versions
of isc-dhcp-server so I shutdown isc-dhcp-server on the 18.04 system
and get the same results.

I also tried using a python script with the pypureomapi module to
try and determine if the problem was in omshell or the server.  I 
got very similar results when I attempted to get information about
the failover state of the server.  Interestingly interrogating
the server about host information seems to work just fine.

This is a critical bug since I don't see how to fail over a DHCP
that is running the isc-dhcp-server on 20.04 without being able
to issue omapi commands.

I am attaching apport output to this bug report.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "omapi-failures.apport"
   
https://bugs.launchpad.net/bugs/1916931/+attachment/5467107/+files/omapi-failures.apport

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

Title:
  omshell returns inconsistent results or segfaults

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  I have just built a Ubuntu 20.04 server and installed isc-dhcp-server
  4.4.1 on it and I am seeing inconsistent returns from omshell. 
  Initially omshell returns data as expected, but when I exit and re-enter 
  omshell connections fail.

  Here is the initial, working, session:

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect
  obj: 
  > new failover-state
  obj: failover-state
  > set name = "dhcp-failover"
  obj: failover-state
  name = "dhcp-failover"
  > open
  obj: failover-state
  name = "dhcp-failover"
  partner-address = c0:9d:e9:76:e9:55:00:00
  partner-port = 00:00:02:07
  local-address = 10:9d:e9:76:e9:55:00:00
  local-port = 00:00:02:07
  max-outstanding-updates = 00:00:00:0a
  mclt = 00:00:01:2c
  load-balance-max-secs = 00:00:00:03
  load-balance-hba =
  
ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
  partner-state = 00:00:00:02
  local-state = 00:00:00:02
  partner-stos = 60:36:d0:68
  local-stos = 60:36:8b:3b
  hierarchy = 00:00:00:01
  last-packet-sent = 00:00:00:00
  last-timestamp-received = 00:00:00:00
  skew = 00:00:00:00
  max-response-delay = 00:00:00:3c
  cur-unacked-updates = 00:00:00:00

  Here is what I see when the connect fails.  Well, just hangs really.

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect

  And then I hit ctrl-c to break out and tried again:

  # omshell
  > server localhost
  > port 7911
  > key omapi_key 
  > connect
  Segmentation fault (core dumped)

  Note, the peer to this server is still running Ubuntu 18.04 with
  isc-dhcp-server 4.3.5.  Running the exact same commands on the peer
  works reliably.  (They are using the same python script to drive
  omshell.)  The DHCP server on the new system appears to be working 
  just fine as reported by omshell on the peer and systemctl.

  I was curious if the problem could be with the mis-matched versions
  of isc-dhcp-server so I shutdown isc-dhcp-server on the 

[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation

2021-02-25 Thread XXX
** Attachment added: "--gtk-debug=all output from gucharmap"
   
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1911036/+attachment/5467105/+files/gucharmap-debug.out

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fdbb45dd000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdbb43e9000)
  

[Touch-packages] [Bug 1870585] Re: Not cleaning /var/tmp by default

2021-02-25 Thread Bug Watch Updater
** Changed in: systemd (Debian)
   Status: Unknown => 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/1870585

Title:
  Not cleaning /var/tmp by default

Status in systemd package in Ubuntu:
  New
Status in systemd package in Debian:
  New

Bug description:
  1) 20.04
  2) 245.2-1ubuntu2
  3) I expect /var/tmp to be cleaned up in some way.
  4) It's commented out per 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773313

  In sosreport was comparing the difference between /tmp (Ubuntu/Debian)
  and /var/tmp (RH) and determined that as long as /var/tmp gets cleaned
  on a regular basis we would prefer /var/tmp.

  The  bug that appears to have prompted the disabling was fixed a long
  time ago, can we have this 30d delete re-enabled by default?

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

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


[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation

2021-02-25 Thread XXX
I'm planning on rebooting soon which will hopefully fix whatever is
preventing thunar from displaying.  I'll that output as well, if I can.

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fdbb45dd000)
  libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fdbb43e9000)
  libgmodule-2.0.so.0 => 

[Touch-packages] [Bug 1907676] Re: segmentation fault when opening fd

2021-02-25 Thread Bug Watch Updater
** Changed in: python-apt (Debian)
   Status: Unknown => Fix Released

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

Title:
  segmentation fault when opening fd

Status in python-apt package in Ubuntu:
  Fix Released
Status in python-apt source package in Xenial:
  Fix Released
Status in python-apt source package in Bionic:
  Fix Released
Status in python-apt source package in Focal:
  Fix Released
Status in python-apt source package in Groovy:
  Fix Released
Status in python-apt package in Debian:
  Fix Released

Bug description:
  [Impact]

  USN-4668-1 introduced a regression in python-apt when using certain
  APIs with a file handle.

  [Test case]

  # Landscape scenario:
  1) On the Landscape server, create a package profile that installs a single 
package, 'hello' is enough.
  2) On the Landscape server, apply the package profile to a client
  3) On the Landscape client, verify that there is no segfault message on 
'/var/log/kern.log'
  4) On the Landscape server, verify that the activity to apply the package 
profile ends with success.

  Step 3) would show a segfault and step 4), the activity would stay 'In
  Progress' forever.

  # dak scenario:
  dak crashes with a segmentation fault in python3-apt when processing
  uploads or processing the NEW queue on ftp-master; and also on my
  playground server (used to generate the backtrace).

  [Where problems could occurs]

  [Other info]

  See Debian bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=977000

  Fix:
  
https://salsa.debian.org/apt-team/python-apt/-/commit/3d9af5f196ad6a6c6973ac699a15888d21a9bb52

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

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


[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash when performing drag operation

2021-02-25 Thread XXX
ah, gotcha.  My gdb skills are a bit rusty.

For some reason, thunar wouldn't come up so I used gucharmap.  I'm
attaching the output as well from using --gdk-debug=all.


** Attachment added: "gdb backtrace output"
   
https://bugs.launchpad.net/ubuntu/+source/thunar/+bug/1911036/+attachment/5467104/+files/gucharmap-gdb.out

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

Title:
  GDK/GTK app crash when performing drag operation

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in thunar package in Ubuntu:
  Incomplete

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => 

[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers

2021-02-25 Thread Brian Murray
** Also affects: glibc (Ubuntu Hirsute)
   Importance: Critical
   Status: Triaged

** Also affects: libseccomp (Ubuntu Hirsute)
   Importance: Critical
   Status: Fix Committed

** Tags removed: rls-hh-incoming

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

Title:
  test -x fails inside shell scripts in containers

Status in glibc package in Ubuntu:
  Triaged
Status in libseccomp package in Ubuntu:
  Fix Committed
Status in glibc source package in Hirsute:
  Triaged
Status in libseccomp source package in Hirsute:
  Fix Committed

Bug description:
  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail

  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #

  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--==
  ii  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement

  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

  The build fails with:

  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation

  The simple Dockerfile to reproduce the error - "docker build -t foo ."

  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 

  USER root

  RUN apt-get update \
   && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
    && curl https://syncthing.net/release-key.txt | apt-key add -

  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.

  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.

  Flo

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

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


[Touch-packages] [Bug 571481] Re: when slapd upgrade fails, later upgrade attempts overwrite saved backups of pre-upgrade configuration files

2021-02-25 Thread Ryan Tandy
Fixed in 2.4.51+dfsg-1 i.e. groovy

** Changed in: openldap (Ubuntu)
 Assignee: Ryan Tandy (rtandy) => (unassigned)

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

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

Title:
  when slapd upgrade fails, later upgrade attempts overwrite saved
  backups of pre-upgrade configuration files

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap package in Debian:
  Fix Released

Bug description:
  When called in "upgrade" mode, the slapd.postinst script starts out by
  making a backup of the $SLAPD_CONF directory into /var/backups/slapd
  -/ .

  However, if the upgrade fails (e.g. because of bug #571057), then
  later attempts to run the upgrade script will still be called with the
  same old-package-version, and the script will blindly re-run the
  backup of $SLAPD_CONF onto the same destination directory, overwriting
  the original pre-upgrade-attempt versions of those files with the
  copies that include edits made by the earlier runs of the upgrade
  script.

  I see there is some logic in the compute_backup_path function to check
  if the backup target already exists, and to abort the upgrade run if
  it does.  Doing the same sort of check-and-abort in backup_config_once
  would be better than the current scenario, though it might be even
  nicer if the program could pick a new backup directory (e.g.
  /var/backups/slapd-_try or something)
  automatically, rather than aborting and forcing the user to clean up
  manually

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

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


[Touch-packages] [Bug 1916485] Re: test -x fails inside shell scripts in containers

2021-02-25 Thread Matthieu Clemenceau
** Tags added: fr-1159

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

Title:
  test -x fails inside shell scripts in containers

Status in glibc package in Ubuntu:
  Triaged
Status in libseccomp package in Ubuntu:
  Fix Committed

Bug description:
  glibc regression causes test -x to fail inside scripts inside
  docker/podman, dash and bash are broken, mksh and zsh are fine:

  root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
  root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
  Fail
  root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
  root@0df2ce5d7a46:/#

  root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
  root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail
  root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
  Fail

  The -f flag works, as does /usr/bin/test:
  # bash -c "test -f /usr/bin/gpg  || echo Fail"
  # bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
  #

  [Original bug report]
  root@84b750e443f8:/# lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04
  root@84b750e443f8:/# dpkg -l gnupg apt
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name   Version Architecture Description
  
+++-==-===--==
  ii  apt2.1.20  amd64commandline package manager
  ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free 
PGP replacement

  Hi,
  for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

  The build fails with:

  0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
  them is required for this operation

  The simple Dockerfile to reproduce the error - "docker build -t foo ."

  FROM amd64/ubuntu:hirsute
  MAINTAINER Florian Lohoff 

  USER root

  RUN apt-get update \
   && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
    && curl https://syncthing.net/release-key.txt | apt-key add -

  Breaking it down it this seems to be an issue that there is new
  functionality in apt/apt-key e.g. security hardening that docker
  prohibits in its containers. Running this manually works only in an
  --privileged container.

  So adding keys in unpriviledged container or possibly kubernetes will
  not work anymore.

  Flo

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

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


[Touch-packages] [Bug 1903966] Re: Loading keymaps via udev is not reliable, please use upstream rule

2021-02-25 Thread Bug Watch Updater
** Changed in: v4l-utils (Debian)
   Status: Unknown => New

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

Title:
  Loading keymaps via udev is not reliable, please use upstream rule

Status in v4l-utils package in Ubuntu:
  Fix Released
Status in v4l-utils package in Debian:
  New

Bug description:
  Dear Maintainer,

  the udev rule installed from debian/ir-keytable.udev is not guaranteed to be 
run at the
  appropriate moment during bootup which can cause the remote not to be
  configured according to the settings in /etc/rc_maps.cfg. This seems to occur 
more often with newer kernel versions.

  Please use the upstream version
  (https://git.linuxtv.org/v4l-utils.git/tree/utils/keytable/70-infrared.rules) 
instead.
  This commit message explains the need for this change:
  
https://git.linuxtv.org/v4l-utils.git/commit/utils/keytable/70-infrared.rules?id=e440918467868a5f3e7f73f54ef2cbd85d68f3f1

  Description:Ubuntu 20.04.1 LTS
  Release:20.04

  ir-keytable version: 1.18.0-2build1 and later

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

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


[Touch-packages] [Bug 1871794] Re: [Bluetooth] No audio output/input in HSP/HFP mode

2021-02-25 Thread Stefan W
Same problem:

- Kernel: 5.8.0-41-generic
- OS: Ubuntu 20.04.02 LTS
- Headset: Sennheiser MB Pro 2

I can switch to HSP but even audio output won't work at all.

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1916915] Re: Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale)

2021-02-25 Thread Ruslan Skriabin
Same for Ubuntu 16.04.7:

Err:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 python2.7 
amd64 2.7.12-1ubuntu0~16.04.14
  404  Not Found [IP: 91.189.88.142 80]
Err:2 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libpython2.7-stdlib amd64 2.7.12-1ubuntu0~16.04.14
  404  Not Found [IP: 91.189.88.142 80]
Err:3 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
python2.7-minimal amd64 2.7.12-1ubuntu0~16.04.14
  404  Not Found [IP: 91.189.88.142 80]
Err:4 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
libpython2.7-minimal amd64 2.7.12-1ubuntu0~16.04.14
  404  Not Found [IP: 91.189.88.142 80]
Err:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 libpython2.7 
amd64 2.7.12-1ubuntu0~16.04.14
  404  Not Found [IP: 91.189.88.142 80]

# apt-cache policy python2.7
python2.7:
  Installed: 2.7.12-1ubuntu0~16.04.13
  Candidate: 2.7.12-1ubuntu0~16.04.14
  Version table:
 2.7.12-1ubuntu0~16.04.14 500
500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 *** 2.7.12-1ubuntu0~16.04.13 100
100 /var/lib/dpkg/status
 2.7.11-7ubuntu1 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

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

Title:
  Incorrect package version available on bionic pool
  (2.7.17-1~18.04ubuntu1.3 not availbale)

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Apt tries to get the python2.7 package and some of its dependencies
  with version (2.7.17-1~18.04ubuntu1.3). However it returns an error
  with:

  Failed to fetch
  
http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.88.152 80]

  The problem is present on BIONIC distro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916915/+subscriptions

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


[Touch-packages] [Bug 1914740] Comment bridged from LTC Bugzilla

2021-02-25 Thread bugproxy
--- Comment From wint...@de.ibm.com 2021-02-25 10:28 EDT---
(In reply to comment #25)
> For netplan yaml of:
>
> network:
> version: 2
> ethernets:
> enc8f00:
> dhcp4: yes
>
> It would be interesting to see if L3 dhcp starts to work if one does:
>
> $ sudo mkdir -p /etc/systemd/network/10-netplan-enc8f00.network.d
> $ cat < /etc/systemd/network/10-netplan-enc8f00.network.d/30-request-broadcast.conf
> [DHCPv4]
> RequestBroadcast=yes
> EOF
>
> $ sudo networkctl reconfigure enc8f00
>
> (or chzdev -d 0.0.8f00; chzdev -e 0.0.8f00 or reboot, whatever is easier to
> make networkd force renew).

Thank you xnox. I confirm that this works with chzdev -d/-e and with reboot.
@Asha, this is a better solution for you.

--- Comment From wint...@de.ibm.com 2021-02-25 10:36 EDT---
(In reply to comment #26)
> My preference would be to fix networkd, if that fails netplan, and isc-dhcp
> only if there is syntax to online the device in the right l2/l3 state via
> kernel cmdline and that one needs to complete install over it.
>
> For example, does automatic chzdev device enablement provides
> autoconfiguration for hipersockets in l3? in that case it would be neat for
> ip=dhcp to just do the right thing.
>
Yes, 'chzdev -e' defaults to Layer3 unless you explicitely specify 'chzdev -e 
layer2=1'. Note that chzdev creates a udev rule to make this setting persistent.

> Would turning on RequestBroadcast=yes for ID_NET_DRIVER=qeth_l3 interfaces
> be good enough in networkd?
Yes, that sounds good.

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

Title:
  IPs are not assigned for Hipersockets in DHCP mode

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ---Problem Description---
  IPs are not getting assigned for Hipersockets in DHCP mode
   
  Contact Information = Asha Shekharappa(ashsh...@in.ibm.com)  
Sankar(sankar...@in.ibm.com) 
   
  ---uname output---
  52-Ubuntu SMP Thu Sep 10 10:59:04 UTC 2020 s390x s390x s390x GNU/Linux
   
  Machine Type = s390x 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Ubuntu 20.04
  Netplan with systemd-networkd as renderer

  Creating ethernet connection on Hipersockets device in DHCP mode fails
  to assign IPs

  1. Configure a Hipersockets device
 chzdev -e 0.0.8f00

  2. Create a .yaml file with the below details

  network:
  version: 2
  ethernets:
  enc8f00:
  dhcp4: yes

  3. netplan apply

  
  4. The IP is not assigned as seen below

  root@M96SANKAR:/etc/netplan# ip a s

  enc8f00:  mtu 32768 qdisc mq state UP 
group default qlen 1000
  link/ether fe:da:af:44:08:02 brd ff:ff:ff:ff:ff:ff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1914740/+subscriptions

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


[Touch-packages] [Bug 1916915] Re: Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale)

2021-02-25 Thread Matias N. Goldberg
This bug should be marked as CRITICAL and be fixed ASAP. It's preventing
automatic security upgrades.


Hopefully this was a mistake by a packager, but investigation should be made in 
order to check this isn't a Supply Chain Attack


More info on apt output:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-headers-5.4.0-66-generic linux-hwe-5.4-headers-5.4.0-66 
linux-image-5.4.0-66-generic linux-modules-5.4.0-66-generic 
linux-modules-extra-5.4.0-66-generic
The following packages have been kept back:
  mesa-va-drivers mesa-va-drivers:i386 mesa-vulkan-drivers:i386
The following packages will be upgraded:
  dirmngr dnsmasq-base gnupg gnupg-agent gnupg-l10n gnupg-utils gpg gpg-agent 
gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv idle-python2.7 idle-python3.6 
libpython2.7 libpython2.7-dev
  libpython2.7-minimal libpython2.7-stdlib libpython3.6 libpython3.6-dev 
libpython3.6-minimal libpython3.6-stdlib linux-generic-hwe-18.04 
linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04
  linux-libc-dev python-httplib2 python2.7 python2.7-dev python2.7-minimal 
python3-httplib2 python3.6 python3.6-dev python3.6-minimal retroarch xterm
37 upgraded, 5 newly installed, 0 to remove and 3 not upgraded.
Need to get 33,4 MB/166 MB of archives.
After this operation, 349 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Ign:1 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
python2.7-dev amd64 2.7.17-1~18.04ubuntu1.3
Ign:2 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
libpython2.7-dev amd64 2.7.17-1~18.04ubuntu1.3
Ign:3 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
libpython2.7 amd64 2.7.17-1~18.04ubuntu1.3
Ign:4 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python2.7 
amd64 2.7.17-1~18.04ubuntu1.3
Ign:5 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
libpython2.7-stdlib amd64 2.7.17-1~18.04ubuntu1.3
Ign:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
python2.7-minimal amd64 2.7.17-1~18.04ubuntu1.3
Ign:7 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
libpython2.7-minimal amd64 2.7.17-1~18.04ubuntu1.3
Err:1 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
python2.7-dev amd64 2.7.17-1~18.04ubuntu1.3
  404  Not Found [IP: 91.189.91.39 80]
Err:2 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
libpython2.7-dev amd64 2.7.17-1~18.04ubuntu1.3
  404  Not Found [IP: 91.189.91.39 80]
Err:3 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
libpython2.7 amd64 2.7.17-1~18.04ubuntu1.3
  404  Not Found [IP: 91.189.91.39 80]
Err:4 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 python2.7 
amd64 2.7.17-1~18.04ubuntu1.3
  404  Not Found [IP: 91.189.91.39 80]
Err:5 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
libpython2.7-stdlib amd64 2.7.17-1~18.04ubuntu1.3
  404  Not Found [IP: 91.189.91.39 80]
Err:6 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
python2.7-minimal amd64 2.7.17-1~18.04ubuntu1.3
  404  Not Found [IP: 91.189.91.39 80]
Err:7 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
libpython2.7-minimal amd64 2.7.17-1~18.04ubuntu1.3
  404  Not Found [IP: 91.189.91.39 80]
E: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-dev_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.91.39 80]
E: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/libpython2.7-dev_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.91.39 80]
E: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/libpython2.7_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.91.39 80]
E: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.91.39 80]
E: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/libpython2.7-stdlib_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.91.39 80]
E: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.91.39 80]
E: Failed to fetch 
http://us.archive.ubuntu.com/ubuntu/pool/main/p/python2.7/libpython2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.91.39 80]
E: Unable to fetch some archives, maybe run apt-get update or try with 
--fix-missing?

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

Title:
  Incorrect package version available on bionic pool
  (2.7.17-1~18.04ubuntu1.3 not availbale)

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Apt tries 

[Touch-packages] [Bug 1916915] Re: Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale)

2021-02-25 Thread Ivan
** Summary changed:

- Incorrect pacakge version available on bionic pool (2.7.17-1~18.04ubuntu1.3 
not availbale)
+ Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 
not availbale)

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

Title:
  Incorrect package version available on bionic pool
  (2.7.17-1~18.04ubuntu1.3 not availbale)

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Apt tries to get the python2.7 package and some of its dependencies
  with version (2.7.17-1~18.04ubuntu1.3). However it returns an error
  with:

  Failed to fetch
  
http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.88.152 80]

  The problem is present on BIONIC distro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916915/+subscriptions

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


[Touch-packages] [Bug 1916915] Re: Incorrect pacakge version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale)

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

** Changed in: python2.7 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Incorrect package version available on bionic pool
  (2.7.17-1~18.04ubuntu1.3 not availbale)

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Apt tries to get the python2.7 package and some of its dependencies
  with version (2.7.17-1~18.04ubuntu1.3). However it returns an error
  with:

  Failed to fetch
  
http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.88.152 80]

  The problem is present on BIONIC distro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916915/+subscriptions

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


[Touch-packages] [Bug 1916915] [NEW] Incorrect package version available on bionic pool (2.7.17-1~18.04ubuntu1.3 not availbale)

2021-02-25 Thread Ivan
Public bug reported:

Apt tries to get the python2.7 package and some of its dependencies with
version (2.7.17-1~18.04ubuntu1.3). However it returns an error with:

Failed to fetch
http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb
404  Not Found [IP: 91.189.88.152 80]

The problem is present on BIONIC distro

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Summary changed:

- Incorrect pacakge version available on bionic pull (2.7.17-1~18.04ubuntu1.3 
not availbale)
+ Incorrect pacakge version available on bionic pool (2.7.17-1~18.04ubuntu1.3 
not availbale)

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

Title:
  Incorrect package version available on bionic pool
  (2.7.17-1~18.04ubuntu1.3 not availbale)

Status in python2.7 package in Ubuntu:
  Confirmed

Bug description:
  Apt tries to get the python2.7 package and some of its dependencies
  with version (2.7.17-1~18.04ubuntu1.3). However it returns an error
  with:

  Failed to fetch
  
http://security.ubuntu.com/ubuntu/pool/main/p/python2.7/python2.7-minimal_2.7.17-1~18.04ubuntu1.3_amd64.deb
  404  Not Found [IP: 91.189.88.152 80]

  The problem is present on BIONIC distro

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916915/+subscriptions

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


[Touch-packages] [Bug 1894172] Re: isc-dhcp-server using wrong env variable for INTERFACES

2021-02-25 Thread Utkarsh Gupta
** Changed in: isc-dhcp (Ubuntu)
   Status: Triaged => Fix Released

** Also affects: isc-dhcp (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: isc-dhcp (Ubuntu Groovy)
   Status: New => Fix Released

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

Title:
  isc-dhcp-server using wrong env variable for INTERFACES

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Bionic:
  Triaged
Status in isc-dhcp source package in Focal:
  Confirmed
Status in isc-dhcp source package in Groovy:
  Fix Released

Bug description:
  When checking isc-dhcp-server unit file I saw isc-dhcp-server is being
  started by:

  ConditionPathExists=/etc/default/isc-dhcp-server
  ConditionPathExists=|/etc/ltsp/dhcpd.conf
  ConditionPathExists=|/etc/dhcp/dhcpd.conf

  [Service]
  EnvironmentFile=/etc/default/isc-dhcp-server
  RuntimeDirectory=dhcp-server
  # The leases files need to be root:dhcpd even when dropping privileges
  ExecStart=/bin/sh -ec '\
  CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
  if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; 
fi; \
  [ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \
  chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \
  chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \
  exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES'

  But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and
  $INTERFACESv6.

  This has only been working because cmdline sets -4 and subnet
  declaration in dhcpd.conf file makes dhcp-server to bind to the
  correct interfaces, as it looks like.

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

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


[Touch-packages] [Bug 1887732] Re: py3compile: NameError: name 'quiet' is not defined

2021-02-25 Thread Bug Watch Updater
** Changed in: python3.8 (Debian)
   Status: New => Fix Released

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

Title:
  py3compile: NameError: name 'quiet' is not defined

Status in eric package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  Confirmed
Status in python3.8 package in Ubuntu:
  Confirmed
Status in python3.8 package in Debian:
  Fix Released

Bug description:
  I was upgrading from 18.04 LTS to 20.04 LTS and this popped up. Not
  sure what else to say.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jul 15 17:38:05 2020
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2019-06-26 (385 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: python3-defaults
  Title: package python3 3.8.2-0ubuntu2 failed to install/upgrade: installed 
python3 package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to focal on 2020-07-16 (0 days ago)

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

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


[Touch-packages] [Bug 1916903] [NEW] [X542UQ, Realtek ALC294, Mic, Internal] No sound at all

2021-02-25 Thread Suryansh Sharma
Public bug reported:

please fix this.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
Uname: Linux 5.4.0-65-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  suryansh   1898 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 25 19:54:28 2021
InstallationDate: Installed on 2019-11-28 (454 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  suryansh   1898 F pulseaudio
Symptom_Jack: Mic, Internal
Symptom_Type: No sound at all
Title: [X542UQ, Realtek ALC294, Mic, Internal] No sound at all
UpgradeStatus: Upgraded to focal on 2020-05-13 (288 days ago)
dmi.bios.date: 05/18/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X542UQ.202
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X542UQ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX542UQ.202:bd05/18/2017:svnASUSTeKCOMPUTERINC.:pnX542UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X542UQ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug focal

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

Title:
  [X542UQ, Realtek ALC294, Mic, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  please fix this.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78
  Uname: Linux 5.4.0-65-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  suryansh   1898 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 25 19:54:28 2021
  InstallationDate: Installed on 2019-11-28 (454 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  suryansh   1898 F pulseaudio
  Symptom_Jack: Mic, Internal
  Symptom_Type: No sound at all
  Title: [X542UQ, Realtek ALC294, Mic, Internal] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-05-13 (288 days ago)
  dmi.bios.date: 05/18/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X542UQ.202
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X542UQ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX542UQ.202:bd05/18/2017:svnASUSTeKCOMPUTERINC.:pnX542UQ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX542UQ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X542UQ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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


[Touch-packages] [Bug 1903814] Re: [binutils] Prevent GOT access rewrite for certain symbols

2021-02-25 Thread Frank Heimes
Ok thx Ilyia, with that I'm going to update the tags accordingly ...

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

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

Title:
  [binutils] Prevent GOT access rewrite for certain symbols

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Committed
Status in binutils package in Debian:
  New

Bug description:
  [Impact]

   * In s390 kernel context, this bug manifests itself as random errors
  and infinite loops.

  [Test Case]

   * Needs to be confirmed by IBM
   * Build-time tests-suite (applied upstream) backported to Bionic in
     + ld/testsuite/ld-s390/gotreloc-1.s
     + ld/testsuite/ld-s390/gotreloc-1.ver
     + ld/testsuite/ld-s390/gotreloc_31-1.dd
     + ld/testuite/ld-s390/gotreloc_64-1.dd
   * If you build the kernel with CONFIG_DEBUG_INFO_BTF, there is a 50% chance 
that you will see "Failed verification: in-kernel BTF is malformed" during boot

  [Where problems could occur]

   * Binutils is a base toolchain package
     - A problem could potentially affect the whole system
     - With compiler/linker errors
     - Or random errors in the produced binaries
   * This patch touches only architecture specific code in bfd/elf64-s390.c
     - It would only affect the s390x architecture in this case

  [Other Info]

   * While testing the fix in Bileto, we found one pending autopkgtest 
regression with linux/amd64 4.15.0-135.139 which is resolved in 4.15.0-136.140 
(currently in -proposed).
   * The failed test in snapcraft is not a regression, as it never passed 
before.

  == Original Description ==
  Please backport the following bugfix into Ubuntu LTS: 
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e6213e09ed0e

  Some relevant historic links:
  Debian bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961736
  glibc bugreport: https://sourceware.org/bugzilla/show_bug.cgi?id=18960

  In s390 kernel context, this bug manifests itself as random errors and
  infinite loops, so it's fairly severe.

  These are the current versions of binutils:
  Package binutils

  xenial (16.04LTS) (devel): GNU assembler, linker and binary utilities
  2.26.1-1ubuntu1~16.04.8 [security]: amd64 i386
  2.26-8ubuntu2 [ports]: arm64 armhf powerpc ppc64el s390x
  xenial-updates (devel): GNU assembler, linker and binary utilities
  2.26.1-1ubuntu1~16.04.8: amd64 arm64 armhf i386 powerpc ppc64el s390x
  bionic (18.04LTS) (devel): GNU assembler, linker and binary utilities
  2.30-21ubuntu1~18.04.4 [security]: amd64 i386
  2.30-15ubuntu1 [ports]: arm64 armhf ppc64el s390x
  bionic-updates (devel): GNU assembler, linker and binary utilities
  2.30-21ubuntu1~18.04.4: amd64 arm64 armhf i386 ppc64el s390x
  focal (20.04LTS) (devel): GNU assembler, linker and binary utilities
  2.34-6ubuntu1: amd64 arm64 armhf i386 ppc64el s390x
  groovy (devel): GNU assembler, linker and binary utilities
  2.35.1-1ubuntu1: amd64 arm64 armhf i386 ppc64el s390x

  The patch applies fine to 2.26 and 2.30 (except for tests, but we
  don't need them). We don't need it on 2.32+.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903814/+subscriptions

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


[Touch-packages] [Bug 1915547] Re: sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to 1.1ubuntu1.18.04.7~16.04.7 ) Xenial

2021-02-25 Thread Balint Reczey
Fixed in 2.8.

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Fix Released

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

Title:
   sru unattended-upgrades (  1.1ubuntu1.18.04.7~16.04.6  update to
  1.1ubuntu1.18.04.7~16.04.7 ) Xenial

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

Bug description:
  == Begin SRU Template ==
  [Impact]
  When upgrading from trusty to xenial, we are prompted about config changes on 
50unattended-upgrades with the following diff:

  --- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08 
19:21:39
  +++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644 
2020-02-17 18:03:38
  @@ -1,11 +1,13 @@
   // Automatically upgrade packages from these (origin:archive) pairs
   Unattended-Upgrade::Allowed-Origins {
  + "${distro_id}:${distro_codename}";
   "${distro_id}:${distro_codename}-security";
   // Extended Security Maintenance; doesn't necessarily exist for
   // every release and this system may not have it installed, but if
   // available, the policy for updates is such that unattended-upgrades
   // should also install from here by default.
  - "${distro_id}ESM:${distro_codename}";
  + "${distro_id}ESMApps:${distro_codename}-apps-security";
  + "${distro_id}ESM:${distro_codename}-infra-security";
   // "${distro_id}:${distro_codename}-updates";
   // "${distro_id}:${distro_codename}-proposed";
   // "${distro_id}:${distro_codename}-backports";

  The reason we are presented with this diff is that the xenial package
  does not contain a md5sum history file that informs ucf about all the
  supported configs for 50unattended-upgrades. To fix that upgrade
  problem, we are prosing the following changes on the xenial package of
  unattended-upgrades:

  - Add 50unattended-upgrades.md5sum file into the xenial package
  - Add md5sum of the current xenial 50unattende-upgrades file into the 
md5sum history file
  - Modify ucf command in postinst to be aware of the md5sum history file

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  We have performed a manual test with a modified version of the xenial package:
  https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa

  Using that package, we were able to verify that the config change
  prompt no longer happens from trusty to xenial.

  
  [Regression Potential]
  Since we are modifying are features on unattended-upgrades, just adding a new 
file to package, we don't believe there is any regression potential

  [Discussion]

  == End SRU Template ==

  == Changelog ==

* data: add md5sum history file on the data folder
  - This file contains md5sum of several supported 50unattended-upgrades
config files
* data: add xenial md5sum of 50unattented-upgrades into md5sum file
* debian/postint: make ucf command reference the md5sum history file

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

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


[Touch-packages] [Bug 1916893] [NEW] Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode parts cause serious regressions

2021-02-25 Thread Leonidas S. Barbosa
*** This bug is a security vulnerability ***

Private security bug reported:

[Scenario]
A security update was made for python2.7 in xenial and trusty-esm that can 
cause a serious regression since it is modifying unicode code for python2.7. 

[Issue]
It can cause a serious break in the way python prints, rprs, unicode 
information, causing serious damage for any application that is running 
python2.7 in that scenario.

[More info]
https://ubuntu.com/security/CVE-2021-3177

** Affects: python2.7 (Ubuntu)
 Importance: Undecided
 Status: New

** Information type changed from Public to Private Security

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

Title:
  Regression - upate python2.7 for cover CVE-2021-3177 modifying unicode
  parts cause serious regressions

Status in python2.7 package in Ubuntu:
  New

Bug description:
  [Scenario]
  A security update was made for python2.7 in xenial and trusty-esm that can 
cause a serious regression since it is modifying unicode code for python2.7. 

  [Issue]
  It can cause a serious break in the way python prints, rprs, unicode 
information, causing serious damage for any application that is running 
python2.7 in that scenario.

  [More info]
  https://ubuntu.com/security/CVE-2021-3177

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1916893/+subscriptions

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


[Touch-packages] [Bug 1915547] Re: sru unattended-upgrades ( 1.1ubuntu1.18.04.7~16.04.6 update to 1.1ubuntu1.18.04.7~16.04.7 ) Xenial

2021-02-25 Thread Lucas Albuquerque Medeiros de Moura
I will further increase this SRU bug with information that is lacking on
from the original bug proposal:

[Impact]
During an upgrade from trusty to xenial, users will be prompted to make a 
decision regarding the diff on unattended-upgrades. This is not a good user 
experience, specially because the user can make an uninformed decision of 
keeping the old config file, which will make unattended-upgrades to not work as 
we expect.

[Test case]

To reproduce the isse, you can:

1. Launch a trusty vm
2. Perform a do-release-upgrade and observe that you will be prompted with the 
50unattende-upgrades change

To verify that the error is fixed:

1. Launch a trusty vm 
2. Import this ppa into the system:
   https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa
3. Configure do-release-upgrade to allow using third parties during upgrade
4. Run a do-release-upgrade
5. Verify the prompt is no longer there and that we end up with the expected 
50unattended-upgrades
   config file

[Where problems could occur]

The changes is this package should only be surface during an upgrade
operation. Because we are now delivering a new file to the system and
configuring postinst to use it. Because of that, we believe this is the
only scenario that could be affect in case of a regression is discovered
in the package.


---

Finally, if there is any additional information that I need to add to
this SRU, just let me know and I will provide it

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

Title:
   sru unattended-upgrades (  1.1ubuntu1.18.04.7~16.04.6  update to
  1.1ubuntu1.18.04.7~16.04.7 ) Xenial

Status in unattended-upgrades package in Ubuntu:
  New
Status in unattended-upgrades source package in Xenial:
  Triaged

Bug description:
  == Begin SRU Template ==
  [Impact]
  When upgrading from trusty to xenial, we are prompted about config changes on 
50unattended-upgrades with the following diff:

  --- /etc/apt/apt.conf.d/50unattended-upgrades root.root 0644 2017-05-08 
19:21:39
  +++ /etc/apt/apt.conf.d/50unattended-upgrades.ucftmp root.root 0644 
2020-02-17 18:03:38
  @@ -1,11 +1,13 @@
   // Automatically upgrade packages from these (origin:archive) pairs
   Unattended-Upgrade::Allowed-Origins {
  + "${distro_id}:${distro_codename}";
   "${distro_id}:${distro_codename}-security";
   // Extended Security Maintenance; doesn't necessarily exist for
   // every release and this system may not have it installed, but if
   // available, the policy for updates is such that unattended-upgrades
   // should also install from here by default.
  - "${distro_id}ESM:${distro_codename}";
  + "${distro_id}ESMApps:${distro_codename}-apps-security";
  + "${distro_id}ESM:${distro_codename}-infra-security";
   // "${distro_id}:${distro_codename}-updates";
   // "${distro_id}:${distro_codename}-proposed";
   // "${distro_id}:${distro_codename}-backports";

  The reason we are presented with this diff is that the xenial package
  does not contain a md5sum history file that informs ucf about all the
  supported configs for 50unattended-upgrades. To fix that upgrade
  problem, we are prosing the following changes on the xenial package of
  unattended-upgrades:

  - Add 50unattended-upgrades.md5sum file into the xenial package
  - Add md5sum of the current xenial 50unattende-upgrades file into the 
md5sum history file
  - Modify ucf command in postinst to be aware of the md5sum history file

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  We have performed a manual test with a modified version of the xenial package:
  https://launchpad.net/~lamoura/+archive/ubuntu/unattended-upgrades-ppa

  Using that package, we were able to verify that the config change
  prompt no longer happens from trusty to xenial.

  
  [Regression Potential]
  Since we are modifying are features on unattended-upgrades, just adding a new 
file to package, we don't believe there is any regression potential

  [Discussion]

  == End SRU Template ==

  == Changelog ==

* data: add md5sum history file on the data folder
  - This file contains md5sum of several supported 50unattended-upgrades
config files
* data: add xenial md5sum of 50unattented-upgrades into md5sum file
* debian/postint: make ucf command reference the md5sum history file

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

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


[Touch-packages] [Bug 1916729] Re: libnss3 package in Ubuntu 20.10 ships files under `/usr/lib/${DEB_HOST_MULTIARCH}` literally without expansion

2021-02-25 Thread Paride Legovini
Thanks for this bug report. This is fixed already in Hirsute (the
current development release) in version 2:3.55-1ubuntu4, but as you
noted the bug still affects Groovy.

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

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

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

** Changed in: nss (Ubuntu Groovy)
   Status: New => Triaged

** Tags added: server-next

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

Title:
  libnss3 package in Ubuntu 20.10 ships files under
  `/usr/lib/${DEB_HOST_MULTIARCH}` literally without expansion

Status in nss package in Ubuntu:
  Fix Released
Status in nss source package in Groovy:
  Triaged

Bug description:
  ```
  brlin@groovy:~$ dpkg-query --listfiles libnss3
  /.
  /usr
  /usr/lib
  /usr/lib/${DEB_HOST_MULTIARCH}

  ...stripped...

  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreebl3.so
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.chk
  /usr/lib/${DEB_HOST_MULTIARCH}/libfreeblpriv3.so
  ```

  The path appears to be a result of a failed parameter expansion.

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

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


[Touch-packages] [Bug 1903814] Comment bridged from LTC Bugzilla

2021-02-25 Thread bugproxy
--- Comment From i...@de.ibm.com 2021-02-25 07:36 EDT---
binutils-s390x-linux-gnu s390x 2.30-21ubuntu1~18.04.5 works fine.

Tested as follows:

#include 
char a __attribute((aligned(1)));
char b __attribute((aligned(1)));
int main() { printf("%p %p\n", , ); }

prints the following:

0x2aa00c02014 0x2aa00c02014

on the latest bionic (the pointers are the same - bad).

After the upgrade to bionic-proposed it prints:

0x2aa2ed82015 0x2aa2ed82014

(the pointers are different - good).

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

Title:
  [binutils] Prevent GOT access rewrite for certain symbols

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Committed
Status in binutils package in Debian:
  New

Bug description:
  [Impact]

   * In s390 kernel context, this bug manifests itself as random errors
  and infinite loops.

  [Test Case]

   * Needs to be confirmed by IBM
   * Build-time tests-suite (applied upstream) backported to Bionic in
     + ld/testsuite/ld-s390/gotreloc-1.s
     + ld/testsuite/ld-s390/gotreloc-1.ver
     + ld/testsuite/ld-s390/gotreloc_31-1.dd
     + ld/testuite/ld-s390/gotreloc_64-1.dd
   * If you build the kernel with CONFIG_DEBUG_INFO_BTF, there is a 50% chance 
that you will see "Failed verification: in-kernel BTF is malformed" during boot

  [Where problems could occur]

   * Binutils is a base toolchain package
     - A problem could potentially affect the whole system
     - With compiler/linker errors
     - Or random errors in the produced binaries
   * This patch touches only architecture specific code in bfd/elf64-s390.c
     - It would only affect the s390x architecture in this case

  [Other Info]

   * While testing the fix in Bileto, we found one pending autopkgtest 
regression with linux/amd64 4.15.0-135.139 which is resolved in 4.15.0-136.140 
(currently in -proposed).
   * The failed test in snapcraft is not a regression, as it never passed 
before.

  == Original Description ==
  Please backport the following bugfix into Ubuntu LTS: 
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e6213e09ed0e

  Some relevant historic links:
  Debian bugreport: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961736
  glibc bugreport: https://sourceware.org/bugzilla/show_bug.cgi?id=18960

  In s390 kernel context, this bug manifests itself as random errors and
  infinite loops, so it's fairly severe.

  These are the current versions of binutils:
  Package binutils

  xenial (16.04LTS) (devel): GNU assembler, linker and binary utilities
  2.26.1-1ubuntu1~16.04.8 [security]: amd64 i386
  2.26-8ubuntu2 [ports]: arm64 armhf powerpc ppc64el s390x
  xenial-updates (devel): GNU assembler, linker and binary utilities
  2.26.1-1ubuntu1~16.04.8: amd64 arm64 armhf i386 powerpc ppc64el s390x
  bionic (18.04LTS) (devel): GNU assembler, linker and binary utilities
  2.30-21ubuntu1~18.04.4 [security]: amd64 i386
  2.30-15ubuntu1 [ports]: arm64 armhf ppc64el s390x
  bionic-updates (devel): GNU assembler, linker and binary utilities
  2.30-21ubuntu1~18.04.4: amd64 arm64 armhf i386 ppc64el s390x
  focal (20.04LTS) (devel): GNU assembler, linker and binary utilities
  2.34-6ubuntu1: amd64 arm64 armhf i386 ppc64el s390x
  groovy (devel): GNU assembler, linker and binary utilities
  2.35.1-1ubuntu1: amd64 arm64 armhf i386 ppc64el s390x

  The patch applies fine to 2.26 and 2.30 (except for tests, but we
  don't need them). We don't need it on 2.32+.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1903814/+subscriptions

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


[Touch-packages] [Bug 1904192] Re: ebtables can not rename just created chain

2021-02-25 Thread Bug Watch Updater
** Changed in: iptables (Debian)
   Status: Unknown => Fix Released

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

Title:
  ebtables can not rename just created chain

Status in iptables:
  Unknown
Status in iptables package in Ubuntu:
  Fix Released
Status in iptables source package in Groovy:
  Fix Released
Status in iptables source package in Hirsute:
  Fix Released
Status in iptables package in Debian:
  Fix Released
Status in iptables package in Fedora:
  Fix Committed

Bug description:
  [SRU]

   * Changes that went into 1.8.5 ave broken the errno handling.
 In particular loading extensions. Due to that it has become
 impossible to rename rules.

   * Upstream has created a fix and this backports that change to
 Ubuntu
 => 
http://git.netfilter.org/iptables/commit/?id=55b7c71dce7144f4dc0297c17abf0f04879ee247

  [Test Case]

   * # ebtables -t nat -N foo
 # ebtables -t nat -E foo bar
 ebtables v1.8.5 (nf_tables): Chain 'foo' doesn't exists

   * with the fix the above command sequence works

  [Where problems could occur]

   * The change moved code from nft_chain_user_rename to do_commandeb and 
 therefore in theory any ebtables/xtables subcommand could be affected.
 Yet what it does is just resetting the error code in a better place, so 
 while it "could" affect every subcommand it should (tm) not do so.
 

  [Other Info]
   
   * n/a

  
  ---

  Hi,
  I have an issue with ebtables that affects libvirt.
  While initially found in hirsute I had to realize this is broken in
  Groovy and even Bionic (might be a different reason back then) as well right 
now.
  But working in Focal (witch matches my memory of it being good before [1]).

  I was isolating the commands that libvirt runs (identical between Focal
  and Hirsute) to find a simplified trigger. Gladly I found one that leaves
  libvirt and other components out of the equation.
  The following works on focal, but fails on the other releases.

  Note: I checked which tool is in use and in both cases it is 
xtables-nft-multi.
  /usr/sbin/ebtables -> /etc/alternatives/ebtables*
  /etc/alternatives/ebtables -> /usr/sbin/ebtables-nft*
  /usr/sbin/ebtables-nft -> xtables-nft-multi*
  So I converted the libvirt issued commands into xtables-nft-multi just to be
  sure in case a system to compare has other alternatives set.

  Focal (Good):
  /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -N testrule3
  /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -E testrule3 
testrule3-renamed
  

  Groovy/Hirsute (Fail):
  /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -N testrule3
  /usr/sbin/xtables-nft-multi ebtables --concurrent -t nat -E testrule3 
testrule3-renamed
  ebtables v1.8.5 (nf_tables): Chain 'testrule3' doesn't exists
  Try `ebtables -h' or 'ebtables --help' for more information.

  What might be the root cause for this?

  -- Old test instructions --

  As I said I was tracking a fail in libvirt so the test instructions initially
  were around that:

  # the following us done as 2nd level guest (to not mess with the host,
  # but works on bare metal jst as much)
  uvt-kvm create --host-passthrough --memory 2048 --cpu 4 --disk 16 
--password=ubuntu hirsute-kvm release=hirsute arch=amd64 label=daily
  # On guest then

  sudo apt update
  sudo apt install uvtool uvtool-libvirt
  uvt-simplestreams-libvirt --verbose sync --source 
http://cloud-images.ubuntu.com/daily arch=amd64 label=daily release=hirsute
  uvt-kvm create --disk 5 --machine-type ubuntu --password=ubuntu 
hirsute-2nd-lvm release=hirsute arch=amd64 label=daily
  uvt-kvm wait hirsute-2nd-lvm
  virsh shutdown hirsute-2nd-lvm
  virsh edit hirsute-2nd-lvm
  # add this to the network
    
  
    
  virsh start hirsute-2nd-lvm
    error: Failed to start domain hirsute-2nd-nwfilter
    error: internal error: applyDHCPOnlyRules failed - spoofing not protected!

  FYI: Get helpful log details with these in /etc/libvirt/libvirtd.conf
  log_filters="1:util.firewall"
  log_outputs="1:syslog:libvirtd"

  -- --

  [1]: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1758037

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

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


[Touch-packages] [Bug 1888543] Re: hwclock: fails to set time on glibc 2.31

2021-02-25 Thread Bug Watch Updater
** Changed in: busybox (Debian)
   Status: Confirmed => Fix Released

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

Title:
  hwclock: fails to set time on glibc 2.31

Status in busybox package in Ubuntu:
  Fix Released
Status in busybox source package in Focal:
  Fix Released
Status in busybox source package in Groovy:
  Fix Released
Status in busybox package in Debian:
  Fix Released

Bug description:
  [Impact]
   * With glibc 2.31, hwclock from busybox is unable to set the system time
 due to the changes in settimeofday behavior.

  [Test Case]
  * Run:
sudo busybox hwclock -s

  * It should succeed in the fixed version

  [Where problems could occur]
  * The fix calls the originally called glibc function twice, instead of 
passing both non-NULL parameters at once. If this compiles there should be no 
other issue.

  [Original Bug Text]
  With glibc 2.31, hwclock from busybox is unable to set the system time
  due to the changes in settimeofday behavior.

  The problem has been reported upstream in [1] which also contains a
  patch.

  hwclock from busybox is important as it's used on the Raspberry Pi to set the 
system
  time when an RTC is present.

  This bug applies to focal and groovy.

  [1] https://bugs.busybox.net/show_bug.cgi?id=12756

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

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


[Touch-packages] [Bug 1900905] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: »installiertes initramfs-tools-Skript des Paketes post-installation«-Unterprozess gab den Fehlerwer

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

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

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  »installiertes initramfs-tools-Skript des Paketes post-
  installation«-Unterprozess gab den Fehlerwert 1 zurück

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  do-release-upgrade from 18.04 LTS to 20.04 LTS results in this error

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 4.15.0-122.124-generic 4.15.18
  Uname: Linux 4.15.0-122-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.10
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Oct 21 23:15:14 2020
  ErrorMessage: »installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  InstallationDate: Installed on 2015-02-06 (2084 days ago)
  InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.3)
  PackageArchitecture: all
  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:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
»installiertes initramfs-tools-Skript des Paketes 
post-installation«-Unterprozess gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to focal on 2020-10-21 (0 days ago)

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

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


[Touch-packages] [Bug 1916877] [NEW] Bluetooth sound card not detected

2021-02-25 Thread zaf
Public bug reported:

"Dummy output" is on audio volume setting and there is no sound

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: KDE
Date: Thu Feb 25 06:06:58 2021
InstallationDate: Installed on 2021-02-24 (0 days ago)
InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: Bluetooth sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2007
dmi.bios.release: 5.2
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R0052N7
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.ec.firmware.release: 5.2
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0052N7:bd07/11/2007:br5.2:efr5.2:svnSonyCorporation:pnVGN-TZ150N:pvrJ002NHLG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: N/A
dmi.product.name: VGN-TZ150N
dmi.product.sku: N/A
dmi.product.version: J002NHLG
dmi.sys.vendor: Sony Corporation

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


** Tags: amd64 apport-bug focal

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

Title:
  Bluetooth sound card not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  "Dummy output" is on audio volume setting and there is no sound

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Thu Feb 25 06:06:58 2021
  InstallationDate: Installed on 2021-02-24 (0 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/11/2007
  dmi.bios.release: 5.2
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: R0052N7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 5.2
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrR0052N7:bd07/11/2007:br5.2:efr5.2:svnSonyCorporation:pnVGN-TZ150N:pvrJ002NHLG:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: N/A
  dmi.product.name: VGN-TZ150N
  dmi.product.sku: N/A
  dmi.product.version: J002NHLG
  dmi.sys.vendor: Sony Corporation

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

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


[Touch-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]

2021-02-25 Thread Daniel van Vugt
** Summary changed:

- gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in 
cso_destroy_context() [r300_dri.so]
+ gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in 
cso_destroy_context() [r300_dri.so]

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

Title:
  gnome-shell/gnome-session-check-accelerated-gl-helper crashed with
  SIGSEGV in cso_destroy_context() [r300_dri.so]

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Triaged
Status in mesa package in Fedora:
  Unknown

Bug description:
  Graphical user interface is not coming up upon start. Only SSH is
  possible.

  lsb_release -rd:

  Description:  Ubuntu 20.10
  Release:  20.10

  dmesg:

  [   11.985343] gnome-session-c[1013]: segfault at 0 ip  sp 
7fff7679ca48 error 14 in 
gnome-session-check-accelerated-gl-helper[56020e238000+2000]
  [   11.985352] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   14.216117] gnome-shell[1094]: segfault at 0 ip  sp 
7ffeddff9f88 error 14
  [   14.216122] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   15.316292] gnome-shell[1109]: segfault at 0 ip  sp 
7ffc70716198 error 14
  [   15.316297] Code: Unable to access opcode bytes at RIP 0xffd6.

  apt-cache policy:

  gnome-session:
Installed: (none)
Candidate: 3.38.0-1ubuntu1
Version table:
   3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  gnome-session-bin:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-session-common:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  100 /var/lib/dpkg/status

  /var/crash: see attachment

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

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


[Touch-packages] [Bug 1916855] Re: /usr/lib/tracker/tracker-extract:31:g_assertion_message:g_assertion_message_expr:gst_audio_decoder_push_buffers:gst_audio_decoder_chain_forward:gst_audio_decoder_cha

2021-02-25 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1715222 ***
https://bugs.launchpad.net/bugs/1715222

** This bug has been marked a duplicate of bug 1715222
   tracker-extract crashed with SIGABRT in g_assertion_message() in 
gst_audio_decoder_push_buffers: "assertion failed: (offset + len <= av)"

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

Title:
  /usr/lib/tracker/tracker-
  
extract:31:g_assertion_message:g_assertion_message_expr:gst_audio_decoder_push_buffers:gst_audio_decoder_chain_forward:gst_audio_decoder_chain

Status in tracker package in Ubuntu:
  New

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

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

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


[Touch-packages] [Bug 1916851] Re: module-echo-cancel fails on first run

2021-02-25 Thread Shahar Or
I noticed that if I comment out the loading of the `module-card-restore`
in `/etc/pulse/default.pa`  then this problem does not occur. The echo
cancelled devices are present on the first run. Of course, I do like
having my cards restored!

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

Title:
  module-echo-cancel fails on first run

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have the following in `.config/pulse/default.pa`:

  ```
  .include /etc/pulse/default.pa
  load-module module-echo-cancel aec_method=webrtc 
aec_args="analog_gain_control=0 digital_gain_control=1"
  ```

  After a reboot, there is no echo cancelled device.

  And then I run `systemctl --user restart pulseaudio` and the echo
  cancelled devices appear.

  That's a bit of a hassle.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shahar39906 F pulseaudio
   /dev/snd/controlC1:  shahar39906 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 25 16:05:48 2021
  InstallationDate: Installed on 2010-10-12 (3788 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (122 days ago)
  dmi.bios.date: 10/24/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.1a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.1a:bd10/24/2018:br5.11:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: Default string
  dmi.product.name: X10SRA
  dmi.product.sku: Default string
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.system.pa: 2021-02-20T16:50:24.134862

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

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


[Touch-packages] [Bug 1916855] [NEW] /usr/lib/tracker/tracker-extract:31:g_assertion_message:g_assertion_message_expr:gst_audio_decoder_push_buffers:gst_audio_decoder_chain_forward:gst_audio_decoder_c

2021-02-25 Thread errors.ubuntu.com bug bridge
*** This bug is a duplicate of bug 1715222 ***
https://bugs.launchpad.net/bugs/1715222

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
tracker.  This problem was most recently seen with package version 2.3.0-1, the 
problem page at 
https://errors.ubuntu.com/problem/c5b1687c531c1b8f98a3471d579e1eec93f14b6d 
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/.

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


** Tags: artful bionic cosmic disco eoan yakkety zesty

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

Title:
  /usr/lib/tracker/tracker-
  
extract:31:g_assertion_message:g_assertion_message_expr:gst_audio_decoder_push_buffers:gst_audio_decoder_chain_forward:gst_audio_decoder_chain

Status in tracker package in Ubuntu:
  New

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

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

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


[Touch-packages] [Bug 1916851] [NEW] module-echo-cancel fails on first run

2021-02-25 Thread Shahar Or
Public bug reported:

I have the following in `.config/pulse/default.pa`:

```
.include /etc/pulse/default.pa
load-module module-echo-cancel aec_method=webrtc 
aec_args="analog_gain_control=0 digital_gain_control=1"
```

After a reboot, there is no echo cancelled device.

And then I run `systemctl --user restart pulseaudio` and the echo
cancelled devices appear.

That's a bit of a hassle.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: pulseaudio 1:13.99.2-1ubuntu2.3
ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  shahar39906 F pulseaudio
 /dev/snd/controlC1:  shahar39906 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 25 16:05:48 2021
InstallationDate: Installed on 2010-10-12 (3788 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to groovy on 2020-10-25 (122 days ago)
dmi.bios.date: 10/24/2018
dmi.bios.release: 5.11
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.1a
dmi.board.asset.tag: Default string
dmi.board.name: X10SRA
dmi.board.vendor: Supermicro
dmi.board.version: 1.01
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 17
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.1a:bd10/24/2018:br5.11:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
dmi.product.family: Default string
dmi.product.name: X10SRA
dmi.product.sku: Default string
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
modified.conffile..etc.pulse.system.pa: [modified]
mtime.conffile..etc.pulse.system.pa: 2021-02-20T16:50:24.134862

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


** Tags: amd64 apport-bug groovy

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

Title:
  module-echo-cancel fails on first run

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have the following in `.config/pulse/default.pa`:

  ```
  .include /etc/pulse/default.pa
  load-module module-echo-cancel aec_method=webrtc 
aec_args="analog_gain_control=0 digital_gain_control=1"
  ```

  After a reboot, there is no echo cancelled device.

  And then I run `systemctl --user restart pulseaudio` and the echo
  cancelled devices appear.

  That's a bit of a hassle.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu2.3
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shahar39906 F pulseaudio
   /dev/snd/controlC1:  shahar39906 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 25 16:05:48 2021
  InstallationDate: Installed on 2010-10-12 (3788 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (122 days ago)
  dmi.bios.date: 10/24/2018
  dmi.bios.release: 5.11
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.1a
  dmi.board.asset.tag: Default string
  dmi.board.name: X10SRA
  dmi.board.vendor: Supermicro
  dmi.board.version: 1.01
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 17
  dmi.chassis.vendor: Supermicro
  dmi.chassis.version: 0123456789
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.1a:bd10/24/2018:br5.11:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789:
  dmi.product.family: Default string
  dmi.product.name: X10SRA
  dmi.product.sku: Default string
  dmi.product.version: 0123456789
  dmi.sys.vendor: Supermicro
  modified.conffile..etc.pulse.system.pa: [modified]
  mtime.conffile..etc.pulse.system.pa: 2021-02-20T16:50:24.134862

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

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


[Touch-packages] [Bug 571481] Re: when slapd upgrade fails, later upgrade attempts overwrite saved backups of pre-upgrade configuration files

2021-02-25 Thread Bug Watch Updater
** Changed in: openldap (Debian)
   Status: Confirmed => Fix Released

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

Title:
  when slapd upgrade fails, later upgrade attempts overwrite saved
  backups of pre-upgrade configuration files

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap package in Debian:
  Fix Released

Bug description:
  When called in "upgrade" mode, the slapd.postinst script starts out by
  making a backup of the $SLAPD_CONF directory into /var/backups/slapd
  -/ .

  However, if the upgrade fails (e.g. because of bug #571057), then
  later attempts to run the upgrade script will still be called with the
  same old-package-version, and the script will blindly re-run the
  backup of $SLAPD_CONF onto the same destination directory, overwriting
  the original pre-upgrade-attempt versions of those files with the
  copies that include edits made by the earlier runs of the upgrade
  script.

  I see there is some logic in the compute_backup_path function to check
  if the backup target already exists, and to abort the upgrade run if
  it does.  Doing the same sort of check-and-abort in backup_config_once
  would be better than the current scenario, though it might be even
  nicer if the program could pick a new backup directory (e.g.
  /var/backups/slapd-_try or something)
  automatically, rather than aborting and forcing the user to clean up
  manually

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

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


[Touch-packages] [Bug 1869716] Re: Removing libpango1.0-0 broke Minecraft Launcher

2021-02-25 Thread Bug Watch Updater
** Changed in: pango1.0 (Debian)
   Status: New => Fix Released

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

Title:
  Removing  libpango1.0-0  broke Minecraft Launcher

Status in pango1.0 package in Ubuntu:
  Fix Released
Status in pango1.0 package in Debian:
  Fix Released

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

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

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

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

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

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

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

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


[Touch-packages] [Bug 1891548] Re: autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd

2021-02-25 Thread Bug Watch Updater
** Changed in: autofs (Debian)
   Status: Unknown => Fix Released

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

Title:
  autofs-ldap's /etc/ldap/schema/autofs.schema crashes slapd

Status in autofs package in Ubuntu:
  New
Status in openldap package in Ubuntu:
  New
Status in autofs package in Debian:
  Fix Released

Bug description:
  Ubuntu Release:
  # lsb_release -rd
  Description:  Ubuntu 20.04.1 LTS
  Release:  20.04

  Version of packages in use:
  # dpkg -l autofs autofs-ldap slapd | grep '^ii'
  ii  autofs 5.1.6-2ubuntu0.1   amd64kernel-based 
automounter for Linux
  ii  autofs-ldap5.1.6-2ubuntu0.1   amd64LDAP map support for 
autofs
  ii  slapd  2.4.49+dfsg-2ubuntu1.3 amd64OpenLDAP server (slapd)

  Expected:
  No errors from slaptest

  Actual Output:
  5f359370 /etc/ldap/schema/autofs.schema: line 14 attributetype: AttributeType 
inappropriate matching rule: "caseExactMatch"

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

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


[Touch-packages] [Bug 1894907] Re: FTBFS with sphinx 3.2

2021-02-25 Thread Bug Watch Updater
** Changed in: cyrus-sasl2 (Debian)
   Status: New => Fix Released

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

Title:
  FTBFS with sphinx 3.2

Status in Cyrus-sasl2:
  New
Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  cyrus-sasl2 ships with a sphinx extension to build its documentation,
  and this extension was based on a very old sphinx version. It no
  longer builds with sphinx 3.2.1 from groovy, failing in several
  places:

  a) "NoUri"
  Extension error:
  Could not import extension sphinxlocal.builders.manpage (exception: cannot 
import name 'NoUri' from 'sphinx.environment' 
(/usr/lib/python3/dist-packages/sphinx/environment/__init__.py))
  make[2]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2
  make[2]: Leaving directory 
'/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal'
  make[1]: *** [Makefile:686: all-recursive] Error 1
  make[1]: Leaving directory 
'/home/ubuntu/deb/cyrus-sasl2-2.1.27+dfsg/build-heimdal'
  make: *** [Makefile:556: all] Error 2

  Debian has a bug report already at https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=955095

  b) MACRO_DEF
  Extension error:
  Could not import extension sphinxlocal.builders.manpage (exception: cannot 
import name 'MACRO_DEF' from 'sphinx.writers.manpage' 
(/usr/lib/python3/dist-packages/sphinx/writers/manpage.py))
  make[4]: *** [Makefile:1166: man/.sphinx-build.stamp] Error 2
  make[4]: Leaving directory 
'/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal'
  make[3]: *** [Makefile:686: all-recursive] Error 1
  make[3]: Leaving directory 
'/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal'
  make[2]: *** [Makefile:556: all] Error 2
  make[2]: Leaving directory 
'/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2/build-heimdal'
  dh_auto_build: error: cd build-heimdal && make -j4 
sasldir=/usr/lib/x86_64-linux-gnu/sasl2 returned exit code 2
  make[1]: *** [debian/rules:164: override_dh_auto_build] Error 25
  make[1]: Leaving directory '/home/ubuntu/git/packages/cyrus-sasl2/cyrus-sasl2'
  make: *** [debian/rules:122: build] Error 2
  dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1894907/+subscriptions

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


[Touch-packages] [Bug 1914884] Re: udev tries to assign identical name to multiple network cards

2021-02-25 Thread sm8ps
In case anybody else should stumble over this issue, my solution was to create 
a .link file /etc/systemd/network/10-fix-names.link with content
[Match]
OriginalName=*
[Link]
NamePolicy=path
AlternativeNamesPolicy=path
as described in 
https://www.freedesktop.org/software/systemd/man/systemd.link.html. For reasons 
unknown to me the AlternativeNamesPolicy is necessary; otherwise the name is 
kept at ens2 (only) for the active link (the other two NICs are inactive).

sudo SYSTEMD_LOG_LEVEL=debug udevadm test-builtin net_setup_link
/sys/class/net/ens2 yields the expected result enp5s0 and the machine
can be rebooted.

Closing this issue.

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

Title:
  udev tries to assign identical name to multiple network cards

Status in systemd package in Ubuntu:
  New

Bug description:
  Upon upgrading from U18.04 to U20.04.2, the network interface names became 
unpredictable. They could be *any* of eth0, eth1, eth2 and ens2. Further 
inspection shows error messages like
  "systemd-udevd: eth1: Failed to rename network interface 3 from 'eth1' to 
'ens2': File exists"

  The installation is plain vanilla; in fact, the system had not been
  used at all yet. Neither of the files '/lib/udev/rules.d/75
  -persistent-net-generator.rules', '/etc/udev/rules.d/70-persistent-
  net.rules' or '/lib/udev/rules.d/71-biosdevname.rules' exist.

  On U18.04, 'ls /sys/class/net' yielded "enp5s0 enp14s0 enp9s0 lo".
  After the upgrade, it currently shows "ens2  eth0  eth1  lo".
  For each of these entries, 'udevadm test-builtin net_id $nic 2>/dev/null' 
gives the following:

  /sys/class/net/ens2
  ID_NET_NAMING_SCHEME=v245
  ID_NET_NAME_MAC=enx002481d13e60
  ID_OUI_FROM_DATABASE=Hewlett Packard
  ID_NET_NAME_PATH=enp14s0
  ID_NET_NAME_SLOT=ens2

  /sys/class/net/eth0
  ID_NET_NAMING_SCHEME=v245
  ID_NET_NAME_MAC=enx001018b197dc
  ID_OUI_FROM_DATABASE=Broadcom
  ID_NET_NAME_PATH=enp5s0
  ID_NET_NAME_SLOT=ens2

  /sys/class/net/eth1
  ID_NET_NAMING_SCHEME=v245
  ID_NET_NAME_MAC=enx00101897069a
  ID_OUI_FROM_DATABASE=Broadcom
  ID_NET_NAME_PATH=enp9s0
  ID_NET_NAME_SLOT=ens2

  This seems to be a case where the naming scheme v245 should be replaced by 
v247, according to 
  
https://www.freedesktop.org/software/systemd/man/systemd.net-naming-scheme.html
  The situation does not change with passing "net.naming-scheme=latest" to the 
kernel.
  The installed version of udev is 245.4-4ubuntu3.4.

  Since this faulty behavior happened completely out of the blue on a
  practically pristine LTS installation, I hope to have some kind of
  solution similar to a backport. Thanks for comments!

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

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