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

[Doug Smythies]

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

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

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

Status in curtin:
  Invalid
Status in subiquity:
  New
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

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

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

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

  At first glance this seems related to:

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

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

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 1843083] Re: tracker-store crashed with SIGSEGV

[Launchpad Bug Tracker]

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

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

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

Title:
  tracker-store crashed with SIGSEGV

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I din't know about

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.2.99.0-1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Sep  6 20:15:58 2019
  ExecutablePath: /usr/lib/tracker/tracker-store
  InstallationDate: Installed on 2016-02-29 (1284 days ago)
  InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcCmdline: /usr/lib/tracker/tracker-store
  ProcEnviron:
   LANG=ca_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   LANGUAGE=ca
  SegvAnalysis:
   Segfault happened at: 0x55affda50c33:cmpq   $0x0,0x8(%rdi)
   PC (0x55affda50c33) ok
   source "$0x0" ok
   destination "0x8(%rdi)" (0x0008) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   ()
   ()
   tracker_data_commit_transaction () at 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   ()
  Title: tracker-store crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-07-30 (37 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1843083] Re: tracker-store crashed with SIGSEGV

[Apport retracing service]

** Tags added: focal

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

Title:
  tracker-store crashed with SIGSEGV

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  I din't know about

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.2.99.0-1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Sep  6 20:15:58 2019
  ExecutablePath: /usr/lib/tracker/tracker-store
  InstallationDate: Installed on 2016-02-29 (1284 days ago)
  InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcCmdline: /usr/lib/tracker/tracker-store
  ProcEnviron:
   LANG=ca_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   LANGUAGE=ca
  SegvAnalysis:
   Segfault happened at: 0x55affda50c33:cmpq   $0x0,0x8(%rdi)
   PC (0x55affda50c33) ok
   source "$0x0" ok
   destination "0x8(%rdi)" (0x0008) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   ()
   ()
   tracker_data_commit_transaction () at 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   ()
  Title: tracker-store crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-07-30 (37 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Touch-packages] [Bug 1865833] Re: tracker-store crashed with SIGSEGV in tracker_data_commit_transaction()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1865833/+attachment/5332929/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1865833/+attachment/5332931/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1865833/+attachment/5332934/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1865833/+attachment/5332935/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1865833/+attachment/5332936/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1865833/+attachment/5332937/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1865833/+attachment/5332938/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1843083
   tracker-store crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  tracker-store crashed with SIGSEGV in
  tracker_data_commit_transaction()

Status in tracker package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: tracker 2.3.1-3build1
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CrashCounter: 1
  Date: Tue Mar  3 08:41:10 2020
  ExecutablePath: /usr/lib/tracker/tracker-store
  ExecutableTimestamp: 1581584165
  ProcCmdline: /usr/lib/tracker/tracker-store
  ProcCwd: /home/kabinet-izo
  ProcEnviron:
   LANG=ru_RU.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   LANGUAGE=ru
  SegvAnalysis:
   Segfault happened at: 0x559ed513a243:cmpq   $0x0,0x8(%rdi)
   PC (0x559ed513a243) ok
   source "$0x0" ok
   destination "0x8(%rdi)" (0x0008) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   ?? ()
   ?? ()
   tracker_data_commit_transaction () from 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   ?? () from /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   ?? ()
  Title: tracker-store crashed with SIGSEGV in tracker_data_commit_transaction()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

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

[Doug Smythies]

I have a 20.04 VM that I had not run for awhile (Feb 12th). It has kmod
version 26-3ubuntu1, and installed mainline kernel
5.6.0-050600rc4-lowlatency fine.

The other two physical 20.04 test servers have kmod version 27-1ubuntu1,
and both spew the error 5600 times during kernel installation the first
time. If I reinstall the same kernel there are no errors spewed. If I
purge the kernel and re-install it, then the error is spewed 5600 times
again.

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

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

Status in curtin:
  Invalid
Status in subiquity:
  New
Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

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

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

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

  At first glance this seems related to:

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

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

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

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

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

[Touch-packages] [Bug 416725] Re: Pulseaudio bluetooth module does not recognize a2dp profile

[stuart naylor]

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

The thing is its debatable if bluez.class = "0x240404" as I don't think
it is as its HSP/HFP and your device is multiprofile and the default is
HSP/HFP.

```
21,18 | 10 | 2Major Service Class
CoD Bit 21: Audio (Speaker, Microphone, Headset service, …)
CoD Bit 18: Rendering (Printing, Speaker, …)
Major Device Class
CoD Bits 10: Audio/Video (headset,speaker,stereo, video display, vcr…)
Minor Device Class
CoD Bits 2: Wearable Headset Device
```

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

Title:
  Pulseaudio bluetooth module does not recognize a2dp profile

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: pulseaudio-module-bluetooth

  Hi,
  I'm trying to use the auto detection of the bluetooth devices, but the module 
does not recognizes my device as a2dp stereo device.

  Release: Karmic Koala Alpha4
  Package Version: 1:0.9.16~test5-0ubuntu1

  
  I: module-udev-detect.c: /dev/snd/controlC0 is accessible: yes

   
  I: card.c: Created 1 "bluez_card.00_11_67_80_00_14"   

   
  I: sink.c: Created sink 1 "bluez_sink.00_11_67_80_00_14" with sample spec 
s16le 1ch 8000Hz and channel map mono   
   
  I: sink.c: bluetooth.protocol = "sco" 

   
  I: sink.c: device.intended_roles = "phone"

   
  I: sink.c: device.description = "BCK-08"  

   
  I: sink.c: device.string = "00:11:67:80:00:14"

   
  I: sink.c: device.api = "bluez"   

   
  I: sink.c: device.class = "sound" 

   
  I: sink.c: device.bus = "bluetooth"
  I: sink.c: device.form_factor = "headset"
  I: sink.c: bluez.path = "/org/bluez/4955/hci0/dev_00_11_67_80_00_14"
  I: sink.c: bluez.class = "0x240404"
  I: sink.c: bluez.name = "BCK-08"
  I: sink.c: device.icon_name = "audio-headset-bluetooth"
  I: source.c: Created source 2 "bluez_sink.00_11_67_80_00_14.monitor" with 
sample spec s16le 1ch 8000Hz and channel map mono
  I: source.c: device.description = "Monitor of BCK-08"
  I: source.c: device.class = "monitor"
  I: source.c: device.string = "00:11:67:80:00:14"
  I: source.c: device.api = "bluez"
  I: source.c: device.bus = "bluetooth"
  I: source.c: device.form_factor = "headset"
  I: source.c: bluez.path = "/org/bluez/4955/hci0/dev_00_11_67_80_00_14"
  I: source.c: bluez.class = "0x240404"
  I: source.c: bluez.name = "BCK-08"
  I: source.c: device.icon_name = "audio-headset-bluetooth"
  I: source.c: Created source 3 "bluez_source.00_11_67_80_00_14" with sample 
spec s16le 1ch 8000Hz and channel map mono
  I: source.c: bluetooth.protocol = "hsp"
  I: source.c: device.intended_roles = "phone"
  I: source.c: device.description = "BCK-08"
  I: source.c: device.string = "00:11:67:80:00:14"
  I: source.c: device.api = "bluez"
  I: source.c: device.class = "sound"
  I: source.c: device.bus = "bluetooth"
  I: source.c: device.form_factor = "headset"
  I: source.c: bluez.path = "/org/bluez/4955/hci0/dev_00_11_67_80_00_14"
  I: source.c: bluez.class = "0x240404"
  I: source.c: bluez.name = "BCK-08"
  I: source.c: device.icon_name = "audio-headset-bluetooth"

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

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

[Touch-packages] [Bug 1769936] Re: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga 720

[Asif Youssuff]

This is still an issue for me in 20.04 -- how can we get some traction
on this issue?

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

Title:
  [80X7, Realtek ALC236, Mic, Internal] Sound is distorted Lenovo Yoga
  720

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Happy to do further testing, fresh install of Bionic. Discovered this
  when trying to do a video conference using the built in mic and was
  able to verify the issue by installing gnome-sound-recorder.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   asif   2213 F...m pulseaudio
   /dev/snd/controlC0:  asif   2213 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  8 11:58:37 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-04-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Mic, Internal
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [80X7, Realtek ALC236, Mic, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4MCN31WW(V2.03)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 720-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4MCN31WW(V2.03):bd03/08/2018:svnLENOVO:pn80X7:pvrLenovoYOGA720-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct31:cvrLenovoYOGA720-15IKB:
  dmi.product.family: YOGA 720-15IKB
  dmi.product.name: 80X7
  dmi.product.version: Lenovo YOGA 720-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

[Christian Ehrhardt ]

I've redone the patches following the usual patch guidelines and opened an MP 
with these at:
=> 
https://code.launchpad.net/~paelzer/ubuntu/+source/openssh/+git/openssh/+merge/380138

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

Title:
  SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Triaged

Bug description:
  [Impact]

   * The version check in ssh was broken no more following RFC 4253 and
     thereby denying some clients that it shouldn't

   * Upstream fixed that and this is backporting the changes to bionic.

  [Test Case]

   # Prep
   * configure the ssh server to generally work
   # Testcase
   $ wget 
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py
   $ apt install python3-paramiko
   $ python3 test_bug_1863930.py localhost (or whatever your host is)

   Will report "Server is not patched." or "Server is patched.

   * for an extra regression check it might be worth to do some "normal" ssh 
 connections as well

  [Regression Potential]

   * The change is very small and reviewable as well as being upstream and 
 in all Ubuntu releases >=Cosmic for a while now so it seems safe.
 If anything the kind of regression to expect is that some former 
 (wrong) connection denials will then succeed. I can only think of
 that being an issue in test suites but not in the real world.

  [Other Info]

   * n/a

  --

  SSHD closes the connection and logs the error message below when a
  client presents a protoversion of "1.99":

  Protocol major versions differ for X.X.X.X port X:
  SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX

  RFC 4253 only states that clients should treat a server's protoversion
  of "1.99" as equivalent to "2.0"; however, some backward-compatible
  clients send a protoversion of "1.99" and expect the server to treat
  it as "2.0".

  This regression was introduced in openssh-portable 7.6p1 from commit
  97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06.
  I've attached a patch with both of those fixes.

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

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

[Touch-packages] [Bug 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~paelzer/ubuntu/+source/openssh/+git/openssh/+merge/380138

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

Title:
  SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Triaged

Bug description:
  [Impact]

   * The version check in ssh was broken no more following RFC 4253 and
     thereby denying some clients that it shouldn't

   * Upstream fixed that and this is backporting the changes to bionic.

  [Test Case]

   # Prep
   * configure the ssh server to generally work
   # Testcase
   $ wget 
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py
   $ apt install python3-paramiko
   $ python3 test_bug_1863930.py localhost (or whatever your host is)

   Will report "Server is not patched." or "Server is patched.

   * for an extra regression check it might be worth to do some "normal" ssh 
 connections as well

  [Regression Potential]

   * The change is very small and reviewable as well as being upstream and 
 in all Ubuntu releases >=Cosmic for a while now so it seems safe.
 If anything the kind of regression to expect is that some former 
 (wrong) connection denials will then succeed. I can only think of
 that being an issue in test suites but not in the real world.

  [Other Info]

   * n/a

  --

  SSHD closes the connection and logs the error message below when a
  client presents a protoversion of "1.99":

  Protocol major versions differ for X.X.X.X port X:
  SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX

  RFC 4253 only states that clients should treat a server's protoversion
  of "1.99" as equivalent to "2.0"; however, some backward-compatible
  clients send a protoversion of "1.99" and expect the server to treat
  it as "2.0".

  This regression was introduced in openssh-portable 7.6p1 from commit
  97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06.
  I've attached a patch with both of those fixes.

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

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

[Touch-packages] [Bug 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

[Christian Ehrhardt ]

Thanks Kyle,
I agree the testcase is great and works in my tests.
This is exactly what I needed to craft the SRU template as needed.

But OTOH about severity of this, as it will mean everyone having ssh installed 
(which is almost every installation out there) will have to download and 
install a new package. I was wondering if there is a (can be more complex and 
doesn't have to have step-by-step instructions) real use-case that is making 
this bug more severe by breaking it. If there isn't I'm tempted to say it is a 
correct bug and fix, but doesn't qualify to do the SRU on its own.
We might then still prep it completely but hold it in -proposed to only release 
it together with some other more severe update that will force a new download 
anyway.

Looking forward to your answer and adding the SRU template for now ...

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

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

** Description changed:

- SSHD closes the connection and logs the error message below when a
- client presents a protoversion of "1.99":
+ [Impact]
  
- Protocol major versions differ for X.X.X.X port X:
+  * The version check in ssh was broken no more following RFC 4253 and
+thereby denying some clients that it shouldn't
+ 
+  * Upstream fixed that and this is backporting the changes to bionic.
+ 
+ [Test Case]
+ 
+  # Prep
+  * configure the ssh server to generally work
+  # Testcase
+  $ wget 
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py
+  $ apt install python3-paramiko
+  $ python3 test_bug_1863930.py localhost (or whatever your host is)
+ 
+  Will report "Server is not patched." or "Server is patched.
+ 
+ [Regression Potential]
+ 
+ TODO
+ 
+ [Other Info]
+  
+  * n/a
+ 
+ --
+ 
+ 
+ SSHD closes the connection and logs the error message below when a client 
presents a protoversion of "1.99":
+ 
+ Protocol major versions differ for X.X.X.X port X:
  SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX
  
  RFC 4253 only states that clients should treat a server's protoversion
  of "1.99" as equivalent to "2.0"; however, some backward-compatible
  clients send a protoversion of "1.99" and expect the server to treat it
  as "2.0".
  
  This regression was introduced in openssh-portable 7.6p1 from commit
  97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06.
  I've attached a patch with both of those fixes.

** Description changed:

  [Impact]
  
-  * The version check in ssh was broken no more following RFC 4253 and
-thereby denying some clients that it shouldn't
+  * The version check in ssh was broken no more following RFC 4253 and
+    thereby denying some clients that it shouldn't
  
-  * Upstream fixed that and this is backporting the changes to bionic.
+  * Upstream fixed that and this is backporting the changes to bionic.
  
  [Test Case]
  
-  # Prep
-  * configure the ssh server to generally work
-  # Testcase
-  $ wget 
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py
-  $ apt install python3-paramiko
-  $ python3 test_bug_1863930.py localhost (or whatever your host is)
+  # Prep
+  * configure the ssh server to generally work
+  # Testcase
+  $ wget 
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py
+  $ apt install python3-paramiko
+  $ python3 test_bug_1863930.py localhost (or whatever your host is)
  
-  Will report "Server is not patched." or "Server is patched.
+  Will report "Server is not patched." or "Server is patched.
+ 
+  * for an extra regression check it might be worth to do some "normal" ssh 
+connections as well
  
  [Regression Potential]
  
- TODO
+  * The change is very small and reviewable as well as being upstream and 
+in all Ubuntu releases >=Cosmic for a while now so it seems safe.
+If anything the kind of regression to expect is that some former 
+(wrong) connection denials will then succeed. I can only think of
+that being an issue in test suites but not in the real world.
  
  [Other Info]
-  
-  * n/a
+ 
+  * n/a
  
  --
  
- 
- SSHD closes the connection and logs the error message below when a client 
presents a protoversion of "1.99":
+ SSHD closes the connection and logs the error message below when a
+ client presents a protoversion of "1.99":
  
  Protocol major versions differ for X.X.X.X port X:
  SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX
  
  RFC 4253 only states that clients should treat a server's protoversion
  of "1.99" as equivalent to "2.0"; however, some backward-compatible
  clients send a protoversion of "1.99" and expect the server to treat it
  as "2.0".
  
  This regression was introduced in openssh-portable 7.6p1 from commit
  97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06.
  I've attached a patch with both 

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

[Kai-Heng Feng]

Reproducible with kmod version 27-1ubuntu1. Previous version 26-1ubuntu1
doesn't have this issue.

** This bug is no longer a duplicate of bug 1863261
   modinfo prints an error message if modules.builtin.bin is missing

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

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

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

Status in curtin:
  Invalid
Status in subiquity:
  New
Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

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

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

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

  At first glance this seems related to:

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

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

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  --- 
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  focal uec-images
  Uname: Linux 5.4.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU

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

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

Re: [Touch-packages] [Bug 1865450] [NEW] PermissionError for AppArmor Profiles i.e., SSH

[Seth Arnold]

On Mon, Mar 02, 2020 at 09:15:56AM -, Shaheena Kazi wrote:
> Public bug reported:
> 
> I have created an AppArmor profile for SSH.

ssh server or ssh client?

What profile transitions did you put into your profile?

> The profile is created successfully but each time I run aa-logprof it gives 
> PermissionError: [Errno 13] 
> PermissionError: [Errno 13] Permission denied: 
> '/etc/apparmor.d/usr.sbin.tcpdumpwvx1h0xl~' -> 
> '/etc/apparmor.d/usr.sbin.tcpdump'

Do you get an apparmor DENIED entry in your log for this?

Thanks

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

Title:
  PermissionError for AppArmor Profiles i.e., SSH

Status in apparmor package in Ubuntu:
  New

Bug description:
  I have created an AppArmor profile for SSH.
  The profile is created successfully but each time I run aa-logprof it gives 
PermissionError: [Errno 13] 

  
  An example of the error: 
  Traceback (most recent call last):
File "/usr/sbin/aa-enforce", line 35, in module>
  tool.cmd_enforce()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 150, in 
cmd_enforce
  apparmor.set_enforce(profile, program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 293, in 
set_enforce
  change_profile_flags(filename, program, 'complain', False)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 704, in 
change_profile_flags
  set_profile_flags(filename, program, newflags)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 753, in 
set_profile_flags
  os.rename(temp_file.name, prof_filename)
  PermissionError: [Errno 13] Permission denied: 
'/etc/apparmor.d/usr.sbin.tcpdumpwvx1h0xl~' -> 
'/etc/apparmor.d/usr.sbin.tcpdump'
  
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

  
+++
  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 1824, in 
do_logprof_pass
  save_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 1921, in 
save_profiles
  write_profile_ui_feedback(profile_name)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3404, in 
write_profile_ui_feedback
  write_profile(profile)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3413, in 
write_profile
  newprof = tempfile.NamedTemporaryFile('w', suffix='~', delete=False, 
dir=profile_dir)
File "/usr/lib/python3.5/tempfile.py", line 688, in NamedTemporaryFile
  (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags, output_type)
File "/usr/lib/python3.5/tempfile.py", line 399, in _mkstemp_inner
  fd = _os.open(file, flags, 0o600)
  PermissionError: [Errno 13] Permission denied: '/etc/apparmor.d/tmpujtge2jq~'

  
  An unexpected error occurred!

  For details, see /tmp/apparmor-bug report-5qnjyx3t.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.
  
+++

  
+++
  root@protegrity-framework314:/var/www# aa-complain /etc/apparmor.d/*
  Profile for /etc/apparmor.d/abstractions not found, skipping
  Profile for /etc/apparmor.d/apache2.d not found, skipping
  Setting /etc/apparmor.d/bin.ping to complain mode.
  Profile for /etc/apparmor.d/cache not found, skipping
  Profile for /etc/apparmor.d/disable not found, skipping
  Setting /etc/apparmor.d/etc.opt.Cluster.cluster_config.status.xml to complain 
mode.
  Setting /etc/apparmor.d/etc.opt.Cluster.cluster_config.xml to complain mode.
  Traceback (most recent call last):
File "/usr/sbin/aa-complain", line 35, in 
  tool.cmd_complain()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 165, in 
cmd_complain
  apparmor.set_complain(profile, program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 286, in 
set_complain
  change_profile_flags(filename, program, 'complain', True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 704, in 
change_profile_flags
  set_profile_flags(filename, program, newflags)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 720, in 
set_profile_flags
  temp_file = tempfile.NamedTemporaryFile('w', prefix=prof_filename, 
suffix='~', delete=False, dir=profile_dir)
File "/usr/lib/python3.5/tempfile.py", line 688, in NamedTemporaryFile
  (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags, output_type)
File "/usr/lib/python3.5/tempfile.py", line 399, in _mkstemp_inner
  fd = _os.open(file, flags, 0o600)
  PermissionError: 

[Touch-packages] [Bug 1865645] [NEW] its crash sometimes and its hang

[Morteza.zamani]

Public bug reported:

its crash sometimes and its hang

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
Uname: Linux 5.0.0-38-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar  3 04:50:48 2020
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:827e]
InstallationDate: Installed on 2019-06-24 (252 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 
G3/G4/SE9 G2
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 002: ID 064e:3401 Suyin Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Spectre x360 Convertible 13-ac0XX
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic 
root=UUID=eee03b6e-c69f-4398-9f52-40b9ef9cdb67 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F.20
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 827E
dmi.board.vendor: HP
dmi.board.version: 94.54
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.20:bd12/01/2016:svnHP:pnHPSpectrex360Convertible13-ac0XX:pvr:rvnHP:rn827E:rvr94.54:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 13-ac0XX
dmi.product.sku: Y4P52AV
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
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 disco 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/1865645

Title:
  its crash sometimes and its hang

Status in xorg package in Ubuntu:
  New

Bug description:
  its crash sometimes and its hang

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  3 04:50:48 2020
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:827e]
  InstallationDate: Installed on 2019-06-24 (252 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 002: ID 0951:1666 Kingston Technology DataTraveler 100 
G3/G4/SE9 G2
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 064e:3401 Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Spectre x360 Convertible 13-ac0XX
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-38-generic 
root=UUID=eee03b6e-c69f-4398-9f52-40b9ef9cdb67 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.20
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 827E
  dmi.board.vendor: HP
  dmi.board.version: 94.54
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.20:bd12/01/2016:svnHP:pnHPSpectrex360Convertible13-ac0XX:pvr:rvnHP:rn827E:rvr94.54:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  

[Touch-packages] [Bug 1865387] Re: Linux Biolinum O italic lowercase m not displayed by poppler

[Ian Turner]

Libertinus has committed a fix as well. https://github.com/alif-
type/libertinus/commit/a0a7467b4655d5b263a44de45ebf11536cc5e7a3

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

Title:
  Linux Biolinum O italic lowercase m not displayed by poppler

Status in FreeType:
  Unknown
Status in Linux Libertine:
  New
Status in fonts-linuxlibertine package in Ubuntu:
  New
Status in freetype package in Ubuntu:
  New

Bug description:
  STEPS TO REPRODUCE: Create a PDF document with the character U+006D LATIN 
SMALL LETTER M
   in Linux Biolinum O, for example with libreoffice.

  Expected behavior: The 'm' is displayed

  Actual behavior: The 'm' is not displayed (but does take up space)

  This issue is discussed in this thread in the poppler forum, which
  leads me to think it is a problem with the font:
  https://lists.nongnu.org/archive/html/freetype-
  devel/2018-12/msg00063.html

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: fonts-linuxlibertine 5.3.0-4
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Mar  1 17:13:17 2020
  Dependencies:
   
  PackageArchitecture: all
  SourcePackage: fonts-linuxlibertine
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1865387] Re: Linux Biolinum O italic lowercase m not displayed by poppler

[Ian Turner]

According to the bug report for Libertinus , FreeType has
accepted this as a bug and released a fix. I updated the bug links
accordingly.

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

** Bug watch added: Non-GNU Savannah Bug Tracker #55414
   http://savannah.nongnu.org/bugs/?55414

** Also affects: freetype via
   http://savannah.nongnu.org/bugs/?55414
   Importance: Unknown
   Status: Unknown

** Bug watch added: github.com/alif-type/libertinus/issues #300
   https://github.com/alif-type/libertinus/issues/300

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

Title:
  Linux Biolinum O italic lowercase m not displayed by poppler

Status in FreeType:
  Unknown
Status in Linux Libertine:
  New
Status in fonts-linuxlibertine package in Ubuntu:
  New
Status in freetype package in Ubuntu:
  New

Bug description:
  STEPS TO REPRODUCE: Create a PDF document with the character U+006D LATIN 
SMALL LETTER M
   in Linux Biolinum O, for example with libreoffice.

  Expected behavior: The 'm' is displayed

  Actual behavior: The 'm' is not displayed (but does take up space)

  This issue is discussed in this thread in the poppler forum, which
  leads me to think it is a problem with the font:
  https://lists.nongnu.org/archive/html/freetype-
  devel/2018-12/msg00063.html

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: fonts-linuxlibertine 5.3.0-4
  ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21
  Uname: Linux 5.0.0-38-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Mar  1 17:13:17 2020
  Dependencies:
   
  PackageArchitecture: all
  SourcePackage: fonts-linuxlibertine
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Hui Wang]

@sil2100,

The alsa-lib in proposed has some minor problems, need the new uploaded
alsa-lib in the queue to fix it. The new uploaded alsa-lib in the queue
is an incremental fix for proposed.

Could we release them together? or it is also fine to release the
proposed alsa-lib first, then release the new one in the queue in the
next cycle.

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

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

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions

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

[Touch-packages] [Bug 1863189] Re: package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

[GivFnz]

Sim, era um problema temporário nos mirrors. Agora eles voltaram ao
normal. Obrigado pela ajuda!

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

Title:
  package libuuid1:amd64 2.34-0.1ubuntu2.2 failed to install/upgrade: O
  pacote está num mau estado de inconsistência; deve  reinstala-lo antes
  de tentar configura-lo.

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  I can't update my packages by using sudo apt-get update, because it fails to 
download some repositories. 
  (Atingido:1 http://security.ubuntu.com/ubuntu eoan-security InRelease
  Atingido:2 http://br.archive.ubuntu.com/ubuntu eoan InRelease
  Obter:3 http://br.archive.ubuntu.com/ubuntu eoan-updates InRelease [97,5 kB]
  Obter:4 http://br.archive.ubuntu.com/ubuntu eoan-backports InRelease [88,8 kB]
  Obter:5 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 
[210 kB]
  Obter:6 http://br.archive.ubuntu.com/ubuntu eoan-updates/main i386 Packages 
[167 kB]
  Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata [73,0 kB]
  Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata [73,0 kB]
  Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata [73,0 kB]
  Ign:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata
  Ign:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 
Icons
  Ign:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 
Icons
  Ign:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 
Metadata
  Ign:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 
Icons
  Ign:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 
Icons
  Ign:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 
DEP-11 Metadata
  Obter:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata [73,0 kB]
  Err:7 http://br.archive.ubuntu.com/ubuntu eoan-updates/main amd64 DEP-11 
Metadata
File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 
2801:82:80ff:8000::5 80]
Hashes of expected file:
 - Filesize:73000 [weak]
 - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3
 - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak]
 - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak]
Release file created at: Thu, 13 Feb 2020 22:49:41 +
  Obter:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 
Icons [9.954 B]
  Err:11 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 48x48 
Icons

  Obter:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 
Icons [15,1 kB]
  Err:12 http://br.archive.ubuntu.com/ubuntu eoan-updates/main DEP-11 64x64 
Icons

  Obter:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 
DEP-11 Metadata [26,2 kB]
  Err:13 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 DEP-11 
Metadata

  Obter:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 
48x48 Icons [18,5 kB]
  Err:14 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 48x48 
Icons

  Obter:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 
64x64 Icons [22,9 kB]
  Err:15 http://br.archive.ubuntu.com/ubuntu eoan-updates/universe DEP-11 64x64 
Icons

  Obter:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 
DEP-11 Metadata [8.064 B]
  Err:16 http://br.archive.ubuntu.com/ubuntu eoan-backports/universe amd64 
DEP-11 Metadata
File has unexpected size (8068 != 8064). Mirror sync in progress? [IP: 
200.236.31.4 80]
Hashes of expected file:
 - Filesize:8064 [weak]
 - SHA256:ec8750e513d95f057f05b2c0269f7c043db0ef78f9d1facca70260870c14440e
 - SHA1:b3548883a3b75fdf0d92dca2221bb63381fcecd1 [weak]
 - MD5Sum:835c424e73a6a3f4235535befe47ea27 [weak]
Release file created at: Thu, 13 Feb 2020 22:50:01 +
  Baixados 186 kB em 4s (44,0 kB/s)   
  Lendo listas de pacotes... Pronto
  E: Falhou ao buscar 
http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/Components-amd64.yml.xz
  File has unexpected size (72992 != 73000). Mirror sync in progress? [IP: 
2801:82:80ff:8000::5 80]
 Hashes of expected file:
  - Filesize:73000 [weak]
  - SHA256:942ddf79e7fcfba3b36f88623eeb90e3d1a31f7677254d2a490034b33e036ac3
  - SHA1:e5cc597a6edd5ebbfe10c8f8f239840d2c302326 [weak]
  - MD5Sum:d1b819be88c2cddb2737c7e81eeaa8d9 [weak]
 Release file created at: Thu, 13 Feb 2020 22:49:41 +
  E: Falhou ao buscar 
http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-48x48.tar.gz
  
  E: Falhou ao buscar 
http://br.archive.ubuntu.com/ubuntu/dists/eoan-updates/main/dep11/icons-64x64.tar.gz
  
  E: Falhou 

[Touch-packages] [Bug 1865437] Re: satpy: autopkgtest unable to run on s390x

[Steve Langasek]

hint added, closing the bug.

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

** Changed in: python3-defaults (Ubuntu)
   Status: New => Invalid

** Changed in: python-xarray (Ubuntu)
   Status: New => Invalid

** Changed in: python-pyproj (Ubuntu)
   Status: New => Invalid

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

Title:
  satpy: autopkgtest unable to run on s390x

Status in python-pyproj package in Ubuntu:
  Invalid
Status in python-xarray package in Ubuntu:
  Invalid
Status in python3-defaults package in Ubuntu:
  Invalid
Status in satpy package in Ubuntu:
  Invalid

Bug description:
  satpy now has a test-dependency on python3-zarr which is not
  installable on s390x due to python3-numcodecs not being available
  there

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

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

[Touch-packages] [Bug 1863930] Re: SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

[Kyle Birkeland]

The easiest way I found to reproduce was to monkey patch the python
paramiko library.  I've attached a short script which can be used to
test a host.  It requires either python-paramiko or python3-paramiko to
run.

** Attachment added: "test_bug_1863930.py"
   
https://bugs.launchpad.net/ubuntu/bionic/+source/openssh/+bug/1863930/+attachment/5332797/+files/test_bug_1863930.py

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

Title:
  SSH 1.99 clients fail to connect to openssh-server 1:7.6p1-4ubuntu0.3

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  New

Bug description:
  SSHD closes the connection and logs the error message below when a
  client presents a protoversion of "1.99":

  Protocol major versions differ for X.X.X.X port X:
  SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 vs. SSH-1.99-XXX

  RFC 4253 only states that clients should treat a server's protoversion
  of "1.99" as equivalent to "2.0"; however, some backward-compatible
  clients send a protoversion of "1.99" and expect the server to treat
  it as "2.0".

  This regression was introduced in openssh-portable 7.6p1 from commit
  97f4d3083; fixes were implemented in commits 9e9c4a7e5 and c9c1bba06.
  I've attached a patch with both of those fixes.

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

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

[Touch-packages] [Bug 1833116] Re: chtmax98090 not working out of the box

[greensysadmin]

On the latest 18.04.4 ISO, it's a little different. After following the
Github instructions, the chtmax98098 device appears, and there appears
to be output in Pulsemixer when you play sound, but nothing comes out of
the speakers.

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

Title:
  chtmax98090 not working out of the box

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  chtmax98090 intel HD audio device doesn't work out of the box after
  installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
  audio devices.

  Audio options shows device and it works if I do this:

   git clone https://github.com/plbossart/UCM.git
   cd UCM
   cp -r chtmax98090/ /usr/share/alsa/ucm/
   alsactl store

  It would be great if there were a solution to make it works out of the
  box. The device (Chromebook Acer CB3-111 has it's end of life for
  chromeOS in July-August, so I suppose more people with this device
  will change OS perhaps to Ubuntu).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaime  1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 17 20:32:35 2019
  InstallationDate: Installed on 2019-06-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Touch-packages] [Bug 1865571] [NEW] Sound card not detected on HP Spectre x360 13-aw0xxx

[Séverin Lemaignan]

Public bug reported:

On a fresh Ubuntu 19.10 install with the Linux kernel updated to 5.3.0
(via proposed-packages), no sound card detected (CPU: Intel i7-1065G).

Relevant dmesg output:

```
[4.544994] sof-audio-pci :00:1f.3: Direct firmware load for 
intel/sof/sof-icl.ri failed with error -2
[4.544997] sof-audio-pci :00:1f.3: error: request firmware 
intel/sof/sof-icl.ri failed err: -2
[4.544999] sof-audio-pci :00:1f.3: error: failed to load DSP firmware -2
[4.545000] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: -2
```

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
Uname: Linux 5.3.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: GNOME
Date: Mon Mar  2 20:47:33 2020
InstallationDate: Installed on 2020-02-28 (3 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/25/2019
dmi.bios.vendor: AMI
dmi.bios.version: F.11
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 86FA
dmi.board.vendor: HP
dmi.board.version: 87.44
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd12/25/2019:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.44:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
dmi.product.sku: 8NF08EA#ABU
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug eoan wayland-session

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

Title:
  Sound card not detected on HP Spectre x360 13-aw0xxx

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  On a fresh Ubuntu 19.10 install with the Linux kernel updated to 5.3.0
  (via proposed-packages), no sound card detected (CPU: Intel i7-1065G).

  Relevant dmesg output:

  ```
  [4.544994] sof-audio-pci :00:1f.3: Direct firmware load for 
intel/sof/sof-icl.ri failed with error -2
  [4.544997] sof-audio-pci :00:1f.3: error: request firmware 
intel/sof/sof-icl.ri failed err: -2
  [4.544999] sof-audio-pci :00:1f.3: error: failed to load DSP firmware 
-2
  [4.545000] sof-audio-pci :00:1f.3: error: sof_probe_work failed err: 
-2
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-42.34-generic 5.3.18
  Uname: Linux 5.3.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Mon Mar  2 20:47:33 2020
  InstallationDate: Installed on 2020-02-28 (3 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2019
  dmi.bios.vendor: AMI
  dmi.bios.version: F.11
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 86FA
  dmi.board.vendor: HP
  dmi.board.version: 87.44
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAMI:bvrF.11:bd12/25/2019:svnHP:pnHPSpectrex360Convertible13-aw0xxx:pvr:rvnHP:rn86FA:rvr87.44:cvnHP:ct31:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Spectre
  dmi.product.name: HP Spectre x360 Convertible 13-aw0xxx
  dmi.product.sku: 8NF08EA#ABU
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1833116] Re: chtmax98090 not working out of the box

[greensysadmin]

Thanks for the link, but I'm a little confused. That seems to be a patch
for 4.19? I've still got no audio on the C200 on today's daily ISO of
Ubuntu Mate 20.04 out of the box. Kernel version is 5.4.0-14-generic.

Following the instructions to use the settings from the OP to use the
Github repo makes the device (chtmax98090) appear in the volume control,
but the device is muted and cannot be unmuted.

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

Title:
  chtmax98090 not working out of the box

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  chtmax98090 intel HD audio device doesn't work out of the box after
  installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
  audio devices.

  Audio options shows device and it works if I do this:

   git clone https://github.com/plbossart/UCM.git
   cd UCM
   cp -r chtmax98090/ /usr/share/alsa/ucm/
   alsactl store

  It would be great if there were a solution to make it works out of the
  box. The device (Chromebook Acer CB3-111 has it's end of life for
  chromeOS in July-August, so I suppose more people with this device
  will change OS perhaps to Ubuntu).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaime  1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 17 20:32:35 2019
  InstallationDate: Installed on 2019-06-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Touch-packages] [Bug 1865517] Re: cannot log in with long username

[Steve Langasek]

What do you get on the affected system when you run 'getent passwd
username.lastnamelastnamelastn...@domain.fr'?

Is this reproducible with services other than a local console login?

The error message in your log is from agetty, not from pam.

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

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

Title:
  cannot log in with long username

Status in pam package in Ubuntu:
  Incomplete

Bug description:
  We use ldap authentication with mail addresses as usernames.
  So usernames are not posix and some are > 32 chars but are working.

  Some of them fire a bug :
  When trying to log, it doesn't asks for password, it just wait some seconds 
then reset to ask username.

  I can't clearly identify which regex fire the bug or not but this one does
  "username.lastnamelastnamelastn...@domain.fr"

  I reproduce it on ubuntu 18.04 and 20.04 daylibuild.

  In auth.log, that line pops up when bug is started

  "Mar  2 16:23:14 premier agetty[97945]: checkname failed: Operation
  not permitted"

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

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

[Touch-packages] [Bug 1861408] Re: firefox apparmor messages

[John Johansen]

I can not speak to specifics but there are a lot of potential reason's a
packager (not firefox specific) might not be updating the profile.

- They don't use the profile / or maybe apparmor. (package
maintainership evolves and not everyone who might even be aware of it
without digging in)

- The auto package tests don't report a failure. This could be the tests
aren't set up to use apparmor or just that they don't have a specific
test for a change. Packagers are often very busy and won't dig into an
update unless there are problems being reported.

- The packager can be using a different kernel version which results in
apparmor or the kernel/apparmor having different features being used.
Yes they should be testing on a given release but there are HWE kernels
and upstream kernel builds that users may be using that are different
from what the packager tests on.

- Testing didn't show up an issue, but a different config or usage
pattern that a user has will show up an issue.

- The packager is not familiar with apparmor and can't or at least
doesn't feel compfortable updating the profile.

- The upstream packager tries to maintain a single profile version for
all releases of a package. Eg. FF 71 is released on multiple distro
versions (xenial, bionic, ...) each of those distros have different
kernels and the application will use different features and apparmor
presents different features.

- AppArmor does not provide adequate means to distribute/use a single
profile version across multiple releases when the features required are
significantly different.

I am not arguing that the profile should not be updated, just providing
some reasons for why it might not be. Ideally it should be tested, and
updated if necessary with every release especially when the profile is
part of the package.

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

Title:
  firefox apparmor messages

Status in apparmor package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New

Bug description:
  firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
  19.3.

  i see there is newer ubuntu version in
  
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
  , 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
  apparmor.

  i have not found a page for firefox bugs in linux mint sites, so i
  belive i should report here. but i have also asked about that in linux
  mint's irc and then github.

  i have enabled apparmor for firefox and see these types of messages in
  syslog:

  Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
  [system] Activating via systemd: service
  name='org.freedesktop.hostname1' unit='dbus-
  org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
  pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")

  Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5525.077960] audit: type=1400 audit(1580226276.440:27):
  apparmor="DENIED" operation="capable"
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
  comm="firefox" capability=21  capname="sys_admin"

  Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
  5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
  uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
  operation="dbus_method_call"  bus="system"
  path="/org/freedesktop/RealtimeKit1"
  interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
  name="org.freedesktop.RealtimeKit1" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
  member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/Private/RemoteVolumeMonitor"
  interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
  mask="send" name=":1.35" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
  member="ListMounts2" mask="send" name=":1.10" pid=15948
  label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
  peer_label="unconfined"

  Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
  apparmor="DENIED" operation="dbus_method_call"  bus="session"
  path="/org/gtk/vfs/mounttracker" 

[Touch-packages] [Bug 1865351] Re: Update to poppler 0.86.0 in Focal

[Amr Ibrahim]

Poppler 0.86.1 has nice fixes in the glib backend, which is used by Evince, as 
it is has this MR
https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/377
which fixes this 3 year old bug
https://gitlab.freedesktop.org/poppler/poppler/issues/129
https://gitlab.gnome.org/GNOME/evince/issues/1280

And it fixes a leak in the glib backend (which is considered under-
maintained by upstream).

https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/NEWS
Release 0.86.1:
core:
* Fix regression in Browse Link handling
* Internal code improvements


** Bug watch added: gitlab.freedesktop.org/poppler/poppler/issues #129
   https://gitlab.freedesktop.org/poppler/poppler/issues/129

** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1280
   https://gitlab.gnome.org/GNOME/evince/issues/1280

** Summary changed:

- Update to poppler 0.86.0 in Focal
+ Update to poppler 0.86.1 in Focal

** Description changed:

- Please update to poppler 0.86.0 in Focal
+ Please update to poppler 0.86.1 in Focal
+ 
+ https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/NEWS
+ 
+ Release 0.86.1:
+ core:
+ * Fix regression in Browse Link handling
+ * Internal code improvements
  
  Release 0.86.0:
  core:
  * Fix link content exfiltration attack
  * Splash: Implement gouraudTriangleShadedFill for some non parametrized 
shadings
  * Fix case unsensitive search for Old Hungarian, Warang Citi, Medefaidrin and 
Adlam
  * Internal code improvements
  
  glib:
  * Automatic handle of page's cropbox on annots. Issue #129
  * Fix memory leak if poppler_document_new_from_file fails
  * Minor speed optimization on poppler_page_get_annot_mapping
  
  utils:
  * pdfdetach: add 'savefile' option
  * pdftoppm/pdftocairo: Fix more odd/even mismatch
  
  qt5:
  * Fix loading from iodevice

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

Title:
  Update to poppler 0.86.1 in Focal

Status in poppler package in Ubuntu:
  Incomplete

Bug description:
  Please update to poppler 0.86.1 in Focal

  https://gitlab.freedesktop.org/poppler/poppler/-/blob/master/NEWS

  Release 0.86.1:
  core:
  * Fix regression in Browse Link handling
  * Internal code improvements

  Release 0.86.0:
  core:
  * Fix link content exfiltration attack
  * Splash: Implement gouraudTriangleShadedFill for some non parametrized 
shadings
  * Fix case unsensitive search for Old Hungarian, Warang Citi, Medefaidrin and 
Adlam
  * Internal code improvements

  glib:
  * Automatic handle of page's cropbox on annots. Issue #129
  * Fix memory leak if poppler_document_new_from_file fails
  * Minor speed optimization on poppler_page_get_annot_mapping

  utils:
  * pdfdetach: add 'savefile' option
  * pdftoppm/pdftocairo: Fix more odd/even mismatch

  qt5:
  * Fix loading from iodevice

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

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

[Touch-packages] [Bug 1865450] Re: PermissionError for AppArmor Profiles i.e., SSH

[John Johansen]

AppArmor does not currently cache denials except an extremely limited
dedup for capabilities. Currently apparmor is relying on the audit
subsystems rate limiting for it logging which you have rightly noted is
insufficient.

AppArmor will continue to report a denial for the error until the
profile is reloaded. genprof/logprof should do this when you save but I
am pretty sure that is not happening in this case, given the other
errors you are seeing.

You can manually reload the profile by doing

  sudo apparmor_parser -r /path/to/profile_name

A better apparmor specific dedup cache is in development but it won't
land upstream until the 5.7 or 5.8 kernels.

As for the permission error, I am not sure what is going on but it
appears that part of the problem is that the tools are not configured
correctly. They are looking /etc/apparmor.d and not finding what they
are looking for


  > Profile for /etc/apparmor.d/abstractions not found, skipping
  > Profile for /etc/apparmor.d/apache2.d not found, skipping
  > Setting /etc/apparmor.d/bin.ping to complain mode.
  > Profile for /etc/apparmor.d/cache not found, skipping
  > Profile for /etc/apparmor.d/disable not found, skipping

I know debian has the cache configured to /var/cache/apparmor so looking
in /etc/apparmor.d for the cache is not right.

The failure to create the tmp file as root is interesting. How is your
/etc/ mounted?

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

Title:
  PermissionError for AppArmor Profiles i.e., SSH

Status in apparmor package in Ubuntu:
  New

Bug description:
  I have created an AppArmor profile for SSH.
  The profile is created successfully but each time I run aa-logprof it gives 
PermissionError: [Errno 13] 

  
  An example of the error: 
  Traceback (most recent call last):
File "/usr/sbin/aa-enforce", line 35, in module>
  tool.cmd_enforce()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 150, in 
cmd_enforce
  apparmor.set_enforce(profile, program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 293, in 
set_enforce
  change_profile_flags(filename, program, 'complain', False)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 704, in 
change_profile_flags
  set_profile_flags(filename, program, newflags)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 753, in 
set_profile_flags
  os.rename(temp_file.name, prof_filename)
  PermissionError: [Errno 13] Permission denied: 
'/etc/apparmor.d/usr.sbin.tcpdumpwvx1h0xl~' -> 
'/etc/apparmor.d/usr.sbin.tcpdump'
  
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

  
+++
  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 1824, in 
do_logprof_pass
  save_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 1921, in 
save_profiles
  write_profile_ui_feedback(profile_name)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3404, in 
write_profile_ui_feedback
  write_profile(profile)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3413, in 
write_profile
  newprof = tempfile.NamedTemporaryFile('w', suffix='~', delete=False, 
dir=profile_dir)
File "/usr/lib/python3.5/tempfile.py", line 688, in NamedTemporaryFile
  (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags, output_type)
File "/usr/lib/python3.5/tempfile.py", line 399, in _mkstemp_inner
  fd = _os.open(file, flags, 0o600)
  PermissionError: [Errno 13] Permission denied: '/etc/apparmor.d/tmpujtge2jq~'

  
  An unexpected error occurred!

  For details, see /tmp/apparmor-bug report-5qnjyx3t.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.
  
+++

  
+++
  root@protegrity-framework314:/var/www# aa-complain /etc/apparmor.d/*
  Profile for /etc/apparmor.d/abstractions not found, skipping
  Profile for /etc/apparmor.d/apache2.d not found, skipping
  Setting /etc/apparmor.d/bin.ping to complain mode.
  Profile for /etc/apparmor.d/cache not found, skipping
  Profile for /etc/apparmor.d/disable not found, skipping
  Setting /etc/apparmor.d/etc.opt.Cluster.cluster_config.status.xml to complain 
mode.
  Setting /etc/apparmor.d/etc.opt.Cluster.cluster_config.xml to complain mode.
  Traceback (most recent call last):
File "/usr/sbin/aa-complain", line 35, in 
  tool.cmd_complain()
File 

[Touch-packages] [Bug 1863532] Re: Invoking "python" brings inappropriate response from command-not-found when python3 installed

[Bill (franksmcb)]

Using 20.04 current build still see:

$ python

Command 'python' not found, but can be installed with:

If I run sudo apt install python

Package python is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  python2-minimal:i386 python2:i386 python2-minimal python2 2to3

E: Package 'python' has no installation candidate

This has an effect on an upgrade to 20.04 of uninstalling any package
that depends on "python" for example slack-desktop.

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

Title:
  Invoking "python" brings inappropriate response from command-not-found
  when python3 installed

Status in command-not-found package in Ubuntu:
  Triaged
Status in python3-defaults package in Ubuntu:
  Triaged
Status in command-not-found source package in Focal:
  Triaged
Status in python3-defaults source package in Focal:
  Triaged

Bug description:
  Ubuntu Mate 20.04 development release, upgraded from 19.10. I don't
  have python 2.7 installed, but have python 3 installed as per default.

  Please see ascii-cast at
  https://asciinema.org/a/SZR20NHz2FN6N6O1hj2Mqmnv8 .

  Running `python` brings up text from command-not-found which suggests
  installing `python3` as a solution to the missing command. `python3`
  is already installed, is a later version than the one indicated by
  command-not-found and does not supply a binary or symlink named
  `python`.

  $ apt policy python
  python:
Installed: (none)
Candidate: (none)
Version table:
   2.7.17-1 -1
  100 /var/lib/dpkg/status
  $ apt policy python3
  python3:
Installed: 3.8.0-3
Candidate: 3.8.0-3
Version table:
   *** 3.8.0-3 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  $ apt policy command-not-found
  command-not-found:
Installed: 19.10.0
Candidate: 19.10.0
Version table:
   *** 19.10.0 500
  500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://gb.archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status

  I don't know whether this is a bug in python3 or command-not-found
  (the latter of which doesn't seem to have been updated for 20.04 yet).
  i don't know if it is intentional that `python3` will not provide a
  binary or symlink named `python`. if that is the case, the output of
  `command-not-found` should be updated to reflect that.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: python3 3.8.0-3
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Mon Feb 17 01:35:16 2020
  InstallationDate: Installed on 2019-10-11 (128 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.2)
  SourcePackage: python3-defaults
  UpgradeStatus: Upgraded to focal on 2020-02-07 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1863532/+subscriptions

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

[Touch-packages] [Bug 1864436] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file

[corrado venturini]

I have a similar problem (more than 4.000 repeated error messages) 
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.6.0-050600rc4-generic/modules.builtin.bin'
installing kernel 5.6.0-050600rc4-generic downloaded from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6-rc4/

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file

Status in kmod package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04
  linux Ubuntu 5.4.0-14.17-generic 5.4.18
  linux-modules-5.4.0-15-generic 5.4.0-15.18

  Upgrading from 5.4.0-14.17 to 5.4.0-15.18 leads to a large number of repeated 
error messages:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-15-generic/modules.builtin.bin'

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

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

[Touch-packages] [Bug 1865435] Re: package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade: installed uuid-runtime package post-installation script subprocess returned error exit status 1

[Mauricio Faria de Oliveira]

Hi Nagendra,

Please provide the output of this command:

$ systemctl status -- -.mount

Did you happen to run 'sudo systemctl mask' on the -.mount unit ?

The problem in package install/update is caused because that unit is masked, 
but it's not on my Eoan system.
So currently wondering if that has been done manually, or by another package 
being upgraded (I looked at some packages from util-linux, but didn't find it.)

Thanks,
Mauricio

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

Title:
  package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade:
  installed uuid-runtime package post-installation script subprocess
  returned error exit status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade:
  installed uuid-runtime package post-installation script subprocess
  returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: uuid-runtime 2.34-0.1ubuntu2.2
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.4
  Architecture: amd64
  Date: Mon Mar  2 12:31:53 2020
  ErrorMessage: installed uuid-runtime package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-03-02 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Python3Details: /usr/bin/python3.7, Python 3.7.5, python3-minimal, 3.7.5-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.4
  SourcePackage: util-linux
  Title: package uuid-runtime 2.34-0.1ubuntu2.2 failed to install/upgrade: 
installed uuid-runtime package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1864436] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file

[actionmystique]

Same issue when upgrading to linux-modules-5.4.0-17-generic 5.4.0.17.20.

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file

Status in kmod package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 20.04
  linux Ubuntu 5.4.0-14.17-generic 5.4.18
  linux-modules-5.4.0-15-generic 5.4.0-15.18

  Upgrading from 5.4.0-14.17 to 5.4.0-15.18 leads to a large number of repeated 
error messages:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open 
builtin file '/lib/modules/5.4.0-15-generic/modules.builtin.bin'

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

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

[Touch-packages] [Bug 1865558] [NEW] gdm-session-worker segmentation fault when checking online crl from smartcard authentication

[Nicholas Clark]

Public bug reported:

Error occurs after pin for the PIV card is entered into the GNOME login GUI.
Error in /var/log/messages:
gdm-session-wor[23783]: segfault at 0 ip 7f3e851589ab sp 7ffd2e747300 
error 6 in libcrypto.so.1.1[7f3e84f6a000+29b000]

Remove "crl_online" from cert_policy in /etc/pam_pkcs11/pam_pkcs11.conf
and there is no segmentation fault.

openssl 1.1.1-1ubuntu2.1~18.04.5
opensc 0.17.0-3
libpam-pkcs11 0.6.9-2build2

Using opensc pkcs11_module.
Smartcard has a CRL URL set with FQDN and the prefix of the URL is http://.
This did not exist in Ubuntu 16. This started in 18.04 (first release) and has 
existed in all minor versions of 18.

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


** Tags: crl gdm-session-worker libcrypto segfault smartcard

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

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

Title:
  gdm-session-worker segmentation fault when checking online crl from
  smartcard authentication

Status in openssl package in Ubuntu:
  New

Bug description:
  Error occurs after pin for the PIV card is entered into the GNOME login GUI.
  Error in /var/log/messages:
  gdm-session-wor[23783]: segfault at 0 ip 7f3e851589ab sp 7ffd2e747300 
error 6 in libcrypto.so.1.1[7f3e84f6a000+29b000]

  Remove "crl_online" from cert_policy in
  /etc/pam_pkcs11/pam_pkcs11.conf and there is no segmentation fault.

  openssl 1.1.1-1ubuntu2.1~18.04.5
  opensc 0.17.0-3
  libpam-pkcs11 0.6.9-2build2

  Using opensc pkcs11_module.
  Smartcard has a CRL URL set with FQDN and the prefix of the URL is http://.
  This did not exist in Ubuntu 16. This started in 18.04 (first release) and 
has existed in all minor versions of 18.

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

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

[Touch-packages] [Bug 1865555] [NEW] libxml2

[kuzey caglar]

Public bug reported:

when i want to install a package for example reportbug this happens:

Building dependency tree   
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libxml2-dev : Breaks: libxml2-dev:i386 (!= 2.9.10+dfsg-1ubuntu3) but 
2.9.4+dfsg1-8ubuntu3 is to be installed
 libxml2-dev:i386 : Depends: libxml2:i386 (= 2.9.4+dfsg1-8ubuntu3) but 
2.9.10+dfsg-1ubuntu3 is to be installed
Breaks: libxml2-dev (!= 2.9.4+dfsg1-8ubuntu3) but 
2.9.10+dfsg-1ubuntu3 is to be installed
 reportbug : Depends: python3-reportbug (= 7.6.0ubuntu1) but it is not going to 
be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
And with apt --fix-broken install:

Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libxml2-dev:i386
The following packages will be upgraded:
  libxml2-dev:i386
1 upgraded, 0 newly installed, 0 to remove and 217 not upgraded.
1 not fully installed or removed.
Need to get 0 B/799 kB of archives.
After this operation, 30,7 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 540117 files and directories currently installed.)
Preparing to unpack .../libxml2-dev_2.9.10+dfsg-1ubuntu3_i386.deb ...
Unpacking libxml2-dev:i386 (2.9.10+dfsg-1ubuntu3) over (2.9.4+dfsg1-8ubuntu3) ..
.
dpkg: error processing archive /var/cache/apt/archives/libxml2-dev_2.9.10+dfsg-1
ubuntu3_i386.deb (--unpack):
 trying to overwrite shared '/usr/bin/xml2-config', which is different from othe
r instances of package libxml2-dev:i386
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/libxml2-dev_2.9.10+dfsg-1ubuntu3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: libxml2 2.9.10+dfsg-1ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar  2 20:46:30 2020
InstallationDate: Installed on 2020-01-23 (39 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: libxml2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libxml2 (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 libxml2 in Ubuntu.
https://bugs.launchpad.net/bugs/186

Title:
  libxml2

Status in libxml2 package in Ubuntu:
  New

Bug description:
  when i want to install a package for example reportbug this happens:

  Building dependency tree   
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   libxml2-dev : Breaks: libxml2-dev:i386 (!= 2.9.10+dfsg-1ubuntu3) but 
2.9.4+dfsg1-8ubuntu3 is to be installed
   libxml2-dev:i386 : Depends: libxml2:i386 (= 2.9.4+dfsg1-8ubuntu3) but 
2.9.10+dfsg-1ubuntu3 is to be installed
  Breaks: libxml2-dev (!= 2.9.4+dfsg1-8ubuntu3) but 
2.9.10+dfsg-1ubuntu3 is to be installed
   reportbug : Depends: python3-reportbug (= 7.6.0ubuntu1) but it is not going 
to be installed
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
  And with apt --fix-broken install:

  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Correcting dependencies... Done
  The following additional packages will be installed:
libxml2-dev:i386
  The following packages will be upgraded:
libxml2-dev:i386
  1 upgraded, 0 newly installed, 0 to remove and 217 not upgraded.
  1 not fully installed or removed.
  Need to get 0 B/799 kB of archives.
  After this operation, 30,7 kB disk space will be freed.
  Do you want to continue? [Y/n] Y
  (Reading database ... 540117 files and directories currently installed.)
  Preparing to unpack .../libxml2-dev_2.9.10+dfsg-1ubuntu3_i386.deb ...
  Unpacking libxml2-dev:i386 (2.9.10+dfsg-1ubuntu3) over (2.9.4+dfsg1-8ubuntu3) 
..
  .
  dpkg: error processing archive 
/var/cache/apt/archives/libxml2-dev_2.9.10+dfsg-1
  ubuntu3_i386.deb (--unpack):
   trying to overwrite shared '/usr/bin/xml2-config', which is different from 
othe
  r instances of package libxml2-dev:i386
  dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
  Errors were encountered while processing:
   /var/cache/apt/archives/libxml2-dev_2.9.10+dfsg-1ubuntu3_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  

[Touch-packages] [Bug 1865519] Re: apparmor depends on python3

[John Johansen]

aa-status needs a major update. It doesn't support several things

  - profile stacks
  - newer profile modes
  - additional profile info available in kernel (revision etc)
  - it doesn't deal with namespaces
  - can't identify when userspace and kernel policy are out of sync
  - doesn't take advantage of newer apis when available
  - doesn't work with unprivileged policy

The actual mechanics of aa-status are pretty straight forward. It
wouldn't be too hard to rewrite in C and since its part of the required
base it should be.

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

Title:
  apparmor depends on python3

Status in snapd:
  New
Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  The TL;DR;
  - AppArmor depends on python3 to support aa-status.
  - snapd depends on apparmor.
  - buildd images have no python
  - building snaps requires snapd
  - snapd does not require aa-status
  - building snaps unnecessarily installs python3 onto the system

  Proposal:
  - Split runtime requirements from apparmor into apparmor-minimal
  - have apparmor depend on apparmor-minimal
  - change snapd's dependency on apparmor to apparmor-minimal

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

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

[Touch-packages] [Bug 1865558] [NEW] gdm-session-worker segmentation fault when checking online crl from smartcard authentication

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Error occurs after pin for the PIV card is entered into the GNOME login GUI.
Error in /var/log/messages:
gdm-session-wor[23783]: segfault at 0 ip 7f3e851589ab sp 7ffd2e747300 
error 6 in libcrypto.so.1.1[7f3e84f6a000+29b000]

Remove "crl_online" from cert_policy in /etc/pam_pkcs11/pam_pkcs11.conf
and there is no segmentation fault.

openssl 1.1.1-1ubuntu2.1~18.04.5
opensc 0.17.0-3
libpam-pkcs11 0.6.9-2build2

Using opensc pkcs11_module.
Smartcard has a CRL URL set with FQDN and the prefix of the URL is http://.
This did not exist in Ubuntu 16. This started in 18.04 (first release) and has 
existed in all minor versions of 18.

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


** Tags: crl gdm-session-worker libcrypto segfault smartcard
-- 
gdm-session-worker segmentation fault when checking online crl from smartcard 
authentication
https://bugs.launchpad.net/bugs/1865558
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to openssl in Ubuntu.

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

[Touch-packages] [Bug 1865531] Re: ip6tables alternate is not setup correctly

[Jamie Strandboge]

This appears to be a test environment issue. I was unable to reproduce
on my laptop, in Debian sid, in an eoan to focal upgrade and a bionic to
focal upgrade. iptables.postinst looks fine too. I'll reopen if I have
something more concrete.

** Changed in: iptables (Ubuntu)
   Status: In Progress => Invalid

** Changed in: iptables (Ubuntu)
 Assignee: Jamie Strandboge (jdstrand) => (unassigned)

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

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

Title:
  ip6tables alternate is not setup correctly

Status in iptables package in Ubuntu:
  Invalid

Bug description:
  ip6tables is not properly setup for the nft backend.

  $ sudo update-alternatives --query ip6tables
  Name: ip6tables
  Link: /usr/sbin/ip6tables
  Slaves:
   ip6tables-restore /usr/sbin/ip6tables-restore
   ip6tables-save /usr/sbin/ip6tables-save
  Status: auto
  Best: /usr/sbin/ip6tables-legacy
  Value: /usr/sbin/ip6tables-legacy

  Alternative: /usr/sbin/ip6tables-legacy
  Priority: 20
  Slaves:
   ip6tables-restore /usr/sbin/ip6tables-legacy-restore
   ip6tables-save /usr/sbin/ip6tables-legacy-save

  Alternative: /usr/sbin/ip6tables-nft
  Priority: 10
  Slaves:
   ip6tables-restore /usr/sbin/ip6tables-nft-restore
   ip6tables-save /usr/sbin/ip6tables-nft-save

  
  But, looking at the files in /usr/sbin, /usr/sbin/ip6tables is not a symlink 
into /etc/alternatives/ip6tables:

  $ ls -l /usr/sbin/ip6tables
  -rwxr-xr-x 1 root root 99296 Feb 28 08:16 /usr/sbin/ip6tables

  but the symlink in /etc/alternatives is setup ok:

  $ ls -l /etc/alternatives/ip6tables
  lrwxrwxrwx 1 root root 26 Mar  2 10:12 /etc/alternatives/ip6tables -> 
/usr/sbin/ip6tables-legacy

  This breaks, for example, ufw when the system is setup for nft.

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

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

[Touch-packages] [Bug 1865519] Re: apparmor depends on python3

[Jamie Strandboge]

We've discussed this in the past and it was determined that 'aa-status'
is to be part of every apparmor minimal install (which is why it is in
apparmor and all the other python tools are in apparmor-utils) so
splitting out of apparmor-minimal doesn't really work with this
thinking.

Perhaps moving aa-status to a new 'apparmor-status' package, have it
Depends on python3, then have the 'apparmor' package Recommends
'apparmor-status' could be a way to go. snapd should still Depends on
apparmor, which would pull in apparmor-status (and it should-- we want
aa-status on UC devices, etc).

Alternatively, aa-status could be rewritten in C/C++ (like other parts
of apparmor). This is probably the best solution for your problem.

Can you elaborate on the problem this is trying to solve (building snaps
unnecessarily installs python3 onto the system-- why specifically is
this an issue?)

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

Title:
  apparmor depends on python3

Status in snapd:
  New
Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  The TL;DR;
  - AppArmor depends on python3 to support aa-status.
  - snapd depends on apparmor.
  - buildd images have no python
  - building snaps requires snapd
  - snapd does not require aa-status
  - building snaps unnecessarily installs python3 onto the system

  Proposal:
  - Split runtime requirements from apparmor into apparmor-minimal
  - have apparmor depend on apparmor-minimal
  - change snapd's dependency on apparmor to apparmor-minimal

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

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

[Touch-packages] [Bug 1865536] [NEW] OBS consumes all memory, fixed in upstream Mesa

[Václav Haisman]

Public bug reported:

There is an issue where due to a Mesa bug OBS consumes all memory
eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426.
Unfortunately, this issue is in all recent Ubuntu versions.

** Affects: mesa
 Importance: Unknown
 Status: Unknown

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


** Tags: eoan

** Package changed: mesa (Ubuntu) => mesa

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #1426
   https://gitlab.freedesktop.org/mesa/mesa/issues/1426

** Changed in: mesa
   Importance: Undecided => Unknown

** Changed in: mesa
   Status: New => Unknown

** Changed in: mesa
 Remote watch: None => gitlab.freedesktop.org/mesa/mesa/issues #1426

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

** Description changed:

  There is an issue where due to a Mesa bug OBS consumes all memory
  eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426.
- Unfortunately, this issue is in all released Ubuntu versions.
+ Unfortunately, this issue is in all recent Ubuntu versions.

** Tags added: eoan

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

Title:
  OBS consumes all memory, fixed in upstream Mesa

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  New

Bug description:
  There is an issue where due to a Mesa bug OBS consumes all memory
  eventually. See https://gitlab.freedesktop.org/mesa/mesa/issues/1426.
  Unfortunately, this issue is in all recent Ubuntu versions.

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

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

[Touch-packages] [Bug 1833116] Re: chtmax98090 not working out of the box

[Jaime Pérez]

https://bugzilla.kernel.org/show_bug.cgi?id=201787

** Bug watch added: Linux Kernel Bug Tracker #201787
   https://bugzilla.kernel.org/show_bug.cgi?id=201787

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

Title:
  chtmax98090 not working out of the box

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  chtmax98090 intel HD audio device doesn't work out of the box after
  installing ubuntu (from 14.04 to 18.04). It shows "Dummy Output" on
  audio devices.

  Audio options shows device and it works if I do this:

   git clone https://github.com/plbossart/UCM.git
   cd UCM
   cp -r chtmax98090/ /usr/share/alsa/ucm/
   alsactl store

  It would be great if there were a solution to make it works out of the
  box. The device (Chromebook Acer CB3-111 has it's end of life for
  chromeOS in July-August, so I suppose more people with this device
  will change OS perhaps to Ubuntu).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaime  1293 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 17 20:32:35 2019
  InstallationDate: Installed on 2019-06-17 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/18/2014
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd08/18/2014:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

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

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

[Touch-packages] [Bug 1865531] [NEW] ip6tables alternate is not setup correctly

[Jamie Strandboge]

Public bug reported:

ip6tables is not properly setup for the nft backend.

$ sudo update-alternatives --query ip6tables
Name: ip6tables
Link: /usr/sbin/ip6tables
Slaves:
 ip6tables-restore /usr/sbin/ip6tables-restore
 ip6tables-save /usr/sbin/ip6tables-save
Status: auto
Best: /usr/sbin/ip6tables-legacy
Value: /usr/sbin/ip6tables-legacy

Alternative: /usr/sbin/ip6tables-legacy
Priority: 20
Slaves:
 ip6tables-restore /usr/sbin/ip6tables-legacy-restore
 ip6tables-save /usr/sbin/ip6tables-legacy-save

Alternative: /usr/sbin/ip6tables-nft
Priority: 10
Slaves:
 ip6tables-restore /usr/sbin/ip6tables-nft-restore
 ip6tables-save /usr/sbin/ip6tables-nft-save


But, looking at the files in /usr/sbin, /usr/sbin/ip6tables is not a symlink 
into /etc/alternatives/ip6tables:

$ ls -l /usr/sbin/ip6tables
-rwxr-xr-x 1 root root 99296 Feb 28 08:16 /usr/sbin/ip6tables

but the symlink in /etc/alternatives is setup ok:

$ ls -l /etc/alternatives/ip6tables
lrwxrwxrwx 1 root root 26 Mar  2 10:12 /etc/alternatives/ip6tables -> 
/usr/sbin/ip6tables-legacy

This breaks, for example, ufw when the system is setup for nft.

** Affects: iptables (Ubuntu)
 Importance: Medium
 Assignee: Jamie Strandboge (jdstrand)
 Status: In Progress

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

** Changed in: iptables (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: iptables (Ubuntu)
   Status: Triaged => In Progress

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

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

Title:
  ip6tables alternate is not setup correctly

Status in iptables package in Ubuntu:
  In Progress

Bug description:
  ip6tables is not properly setup for the nft backend.

  $ sudo update-alternatives --query ip6tables
  Name: ip6tables
  Link: /usr/sbin/ip6tables
  Slaves:
   ip6tables-restore /usr/sbin/ip6tables-restore
   ip6tables-save /usr/sbin/ip6tables-save
  Status: auto
  Best: /usr/sbin/ip6tables-legacy
  Value: /usr/sbin/ip6tables-legacy

  Alternative: /usr/sbin/ip6tables-legacy
  Priority: 20
  Slaves:
   ip6tables-restore /usr/sbin/ip6tables-legacy-restore
   ip6tables-save /usr/sbin/ip6tables-legacy-save

  Alternative: /usr/sbin/ip6tables-nft
  Priority: 10
  Slaves:
   ip6tables-restore /usr/sbin/ip6tables-nft-restore
   ip6tables-save /usr/sbin/ip6tables-nft-save

  
  But, looking at the files in /usr/sbin, /usr/sbin/ip6tables is not a symlink 
into /etc/alternatives/ip6tables:

  $ ls -l /usr/sbin/ip6tables
  -rwxr-xr-x 1 root root 99296 Feb 28 08:16 /usr/sbin/ip6tables

  but the symlink in /etc/alternatives is setup ok:

  $ ls -l /etc/alternatives/ip6tables
  lrwxrwxrwx 1 root root 26 Mar  2 10:12 /etc/alternatives/ip6tables -> 
/usr/sbin/ip6tables-legacy

  This breaks, for example, ufw when the system is setup for nft.

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

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

[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal

[Mauricio Faria de Oliveira]

Hi Lukasz, thanks! Sure thing, I'll add it.

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

Title:
  Crash and failure installing focal

Status in subiquity:
  New
Status in curtin package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in curtin source package in Eoan:
  Invalid
Status in util-linux source package in Eoan:
  Fix Committed
Status in curtin source package in Focal:
  Fix Released
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  New

Bug description:
  [Impact]

   * lsblk no longer prints a partition's parent
     kernel device name (the wholedisk).
     (i.e., 'lsblk -no PKNAME /dev/partition')

   * Another impact is the 'removable media' check
     always return zero for partitions.
     (i.e., 'lsblk -no RM /dev/partition')

   * The regression was introduced on v2.34, only
     Eoan (v2.34) and later are affected.
     Disco (v2.33) and earlier are not affected.

   * The regression is fixed in v2.35, in commit
     e3bb9bfb76c1 ("lsblk: force to print PKNAME
     for partition"); fixes RM for partition too.

  [Test Case]

   * $ lsblk -no PKNAME /dev/vda1 # partition

   * Expected output: vda # wholedisk

   * Current output: (nothing)

   * $ lsblk -no RM /dev/sdb1 # partition in removable disk

   * Expected output: 1 # removable media

   * Current output: 0 # not removable media

  [Regression Potential]

   * Columns that depend on a partition device's
     parent device (i.e., seen as 'wholedisk')
     could in theory show incorrect values if
     another bug is present in v2.34 for that.

   * Other usages of 'parent' pointer in the
     function have been examined and reported
     (e.g. issue w/ removable media column),
     and others found to not have issues
     (e.g. --merge option, to group multiple
     parents of a device, as in RAID.)

  [Other Info]

   * The impacts to the curtin source package
     have been addressed in other way, it no
     longer requires util-linux, comment #14.

   * util-linux github issue:
     https://github.com/karelzak/util-linux/issues/813

  [Original Bug Description]

  During an install of the daily live image for 20.04 Ubuntu Server, the
  installer first crashed and restarted itself, then failed to install
  the system.

  Attached are the logs left on the install USB key.

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

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

[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal

[Mauricio Faria de Oliveira]

$ lsb_release -cs
eoan

Test device: partition (sdb1) in removable / USB flash disk (sdb)

$ ls -1d /sys/block/sdb/sdb1
/sys/block/sdb/sdb1

$ cat /sys/block/sdb/removable 
1

eoan-proposed:  
---

- PKNAME shows partition's parent/wholedisk.
- RM shows 1 for removable disk's partition.

$ dpkg -s util-linux | grep ^Version:
Version: 2.34-0.1ubuntu2.3

$ lsblk -no PKNAME /dev/sdb1
sdb

$ lsblk -no RM /dev/sdb1
 1

eoan-updates:
---

- PKNAME shows nothing.
- RM shows 0 despite it's actually a removable disk's partition.

$ dpkg -s util-linux | grep ^Version:
Version: 2.34-0.1ubuntu2.2

$ lsblk -no PKNAME /dev/sdb1

$

$ lsblk -no RM /dev/sdb1
 0


** Description changed:

  [Impact]
  
-  * lsblk no longer prints a partition's parent 
-kernel device name (the wholedisk).
-(i.e., 'lsblk -no PKNAME /dev/partition')
+  * lsblk no longer prints a partition's parent
+    kernel device name (the wholedisk).
+    (i.e., 'lsblk -no PKNAME /dev/partition')
  
-  * Another impact is the 'removable media' check
-always return zero for partitions.
-(i.e., 'lsblk -no RM /dev/partition')
+  * Another impact is the 'removable media' check
+    always return zero for partitions.
+    (i.e., 'lsblk -no RM /dev/partition')
  
-  * The regression was introduced on v2.34, only
-Eoan (v2.34) and later are affected.
-Disco (v2.33) and earlier are not affected.
+  * The regression was introduced on v2.34, only
+    Eoan (v2.34) and later are affected.
+    Disco (v2.33) and earlier are not affected.
  
-  * The regression is fixed in v2.35, in commit
-e3bb9bfb76c1 ("lsblk: force to print PKNAME
-for partition"); fixes RM for partition too.
+  * The regression is fixed in v2.35, in commit
+    e3bb9bfb76c1 ("lsblk: force to print PKNAME
+    for partition"); fixes RM for partition too.
  
  [Test Case]
  
-  * lsblk -no PKNAME /dev/vda1 # partition
+  * $ lsblk -no PKNAME /dev/vda1 # partition
  
-  * Expected output: vda # wholedisk
+  * Expected output: vda # wholedisk
  
-  * Current output: (nothing)
+  * Current output: (nothing)
+ 
+  * $ lsblk -no RM /dev/sdb1 # partition in removable disk
+ 
+  * Expected output: 1 # removable media
+ 
+  * Current output: 0 # not removable media
  
  [Regression Potential]
  
-  * Columns that depend on a partition device's
-parent device (i.e., seen as 'wholedisk')
-could in theory show incorrect values if
-another bug is present in v2.34 for that.
+  * Columns that depend on a partition device's
+    parent device (i.e., seen as 'wholedisk')
+    could in theory show incorrect values if
+    another bug is present in v2.34 for that.
  
-  * Other usages of 'parent' pointer in the
-function have been examined and reported
-(e.g. issue w/ removable media column),
-and others found to not have issues
-(e.g. --merge option, to group multiple
-parents of a device, as in RAID.)
-
+  * Other usages of 'parent' pointer in the
+    function have been examined and reported
+    (e.g. issue w/ removable media column),
+    and others found to not have issues
+    (e.g. --merge option, to group multiple
+    parents of a device, as in RAID.)
+ 
  [Other Info]
  
-  * The impacts to the curtin source package
-have been addressed in other way, it no
-longer requires util-linux, comment #14.
+  * The impacts to the curtin source package
+    have been addressed in other way, it no
+    longer requires util-linux, comment #14.
  
-  * util-linux github issue:
-https://github.com/karelzak/util-linux/issues/813
+  * util-linux github issue:
+    https://github.com/karelzak/util-linux/issues/813
  
  [Original Bug Description]
  
  During an install of the daily live image for 20.04 Ubuntu Server, the
  installer first crashed and restarted itself, then failed to install the
  system.
  
  Attached are the logs left on the install USB key.

** Tags added: verification-done-eoan

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

Title:
  Crash and failure installing focal

Status in subiquity:
  New
Status in curtin package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in curtin source package in Eoan:
  Invalid
Status in util-linux source package in Eoan:
  Fix Committed
Status in curtin source package in Focal:
  Fix Released
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  New

Bug description:
  [Impact]

   * lsblk no longer prints a partition's parent
     kernel device name (the wholedisk).
     (i.e., 'lsblk -no PKNAME /dev/partition')

   * Another impact is the 'removable media' check
     always return zero for partitions.
     (i.e., 'lsblk -no RM /dev/partition')

   * The regression was introduced on v2.34, only
     Eoan (v2.34) and later are affected.
     Disco (v2.33) and earlier are 

[Touch-packages] [Bug 1865516] Re: Allow packages not related to installation, to be available for install to use apps that help triage also.

[Kangarooo Jānis]

Why i cant add Boot-Repair?

** Description changed:

  Allow packages not related to installation, to be available for install
  to use apps that help triage also.
  
  Gif maker Peek
  Boot fixer boot-repair
  etc.. (can post here more good triaging apps)
- 
  
  Example solution from Peek github https://github.com/phw/peek#ubuntu
  
  [[Ubuntu
  
  You can install the latest versions of Peek from the Ubuntu PPA.
  
  sudo add-apt-repository ppa:peek-developers/stable
  sudo apt update
  sudo apt install peek
  
- If you want to use the latest development version there is also a PPA
- with daily builds available. Use the repository ppa:peek-
- developers/daily in the above commands.]]
  
+ sudo add-apt-repository ppa:yannubuntu/boot-repair
+ sudo apt-get update
+ sudo apt-get install -y boot-repair && boot-repair
+ 
+ 
+ If you want to use the latest development version there is also a PPA with 
daily builds available. Use the repository ppa:peek-developers/daily in the 
above commands.]]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar  2 17:08:39 2020
  InstallationDate: Installed on 2020-03-01 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

** Attachment added: "Screenshot_20200302_175836.png"
   
https://bugs.launchpad.net/ubuntu/+source/peek/+bug/1865516/+attachment/5332748/+files/Screenshot_20200302_175836.png

** Summary changed:

- Allow packages not related to installation, to be available for install to 
use apps that help triage also.
+ Allow packages not related to installation, to be available for install with 
daily or with asking if really want to add app from another version repository 
to use apps that help triage also daily builds.

** Summary changed:

- Allow packages not related to installation, to be available for install with 
daily or with asking if really want to add app from another version repository 
to use apps that help triage also daily builds.
+ Allow packages not related to installation, to be available for install with 
daily or with asking if really want to add app from another version repository 
to triage also daily builds.

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

Title:
  Allow packages not related to installation, to be available for
  install with daily or with asking if really want to add app from
  another version repository to triage also daily builds.

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

Bug description:
  Allow packages not related to installation, to be available for
  install to use apps that help triage also.

  Gif maker Peek
  Boot fixer boot-repair
  etc.. (can post here more good triaging apps)

  Example solution from Peek github https://github.com/phw/peek#ubuntu

  [[Ubuntu

  You can install the latest versions of Peek from the Ubuntu PPA.

  sudo add-apt-repository ppa:peek-developers/stable
  sudo apt update
  sudo apt install peek

  
  sudo add-apt-repository ppa:yannubuntu/boot-repair
  sudo apt-get update
  sudo apt-get install -y boot-repair && boot-repair

  
  If you want to use the latest development version there is also a PPA with 
daily builds available. Use the repository ppa:peek-developers/daily in the 
above commands.]]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar  2 17:08:39 2020
  InstallationDate: Installed on 2020-03-01 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1865516] Re: Allow packages not related to installation, to be available for install to use apps that help triage also.

[Kangarooo Jānis]

** Description changed:

  Allow packages not related to installation, to be available for install
  to use apps that help triage also.
  
  Gif maker Peek
  Boot fixer boot-repair
  etc.. (can post here more good triaging apps)
+ 
+ 
+ Example solution from Peek github https://github.com/phw/peek#ubuntu
+ 
+ [[Ubuntu
+ 
+ You can install the latest versions of Peek from the Ubuntu PPA.
+ 
+ sudo add-apt-repository ppa:peek-developers/stable
+ sudo apt update
+ sudo apt install peek
+ 
+ If you want to use the latest development version there is also a PPA
+ with daily builds available. Use the repository ppa:peek-
+ developers/daily in the above commands.]]
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar  2 17:08:39 2020
  InstallationDate: Installed on 2020-03-01 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Allow packages not related to installation, to be available for
  install with daily or with asking if really want to add app from
  another version repository to use apps that help triage also daily
  builds.

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

Bug description:
  Allow packages not related to installation, to be available for
  install to use apps that help triage also.

  Gif maker Peek
  Boot fixer boot-repair
  etc.. (can post here more good triaging apps)

  Example solution from Peek github https://github.com/phw/peek#ubuntu

  [[Ubuntu

  You can install the latest versions of Peek from the Ubuntu PPA.

  sudo add-apt-repository ppa:peek-developers/stable
  sudo apt update
  sudo apt install peek

  
  sudo add-apt-repository ppa:yannubuntu/boot-repair
  sudo apt-get update
  sudo apt-get install -y boot-repair && boot-repair

  
  If you want to use the latest development version there is also a PPA with 
daily builds available. Use the repository ppa:peek-developers/daily in the 
above commands.]]

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar  2 17:08:39 2020
  InstallationDate: Installed on 2020-03-01 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1865519] Re: apparmor depends on python3

[Dimitri John Ledkov]

Package splits are pain, simply downgrade the python3 Depends to
Recommends or Suggests, as appropriate.


Do buildd images install recommends?

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

Title:
  apparmor depends on python3

Status in snapd:
  New
Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  The TL;DR;
  - AppArmor depends on python3 to support aa-status.
  - snapd depends on apparmor.
  - buildd images have no python
  - building snaps requires snapd
  - snapd does not require aa-status
  - building snaps unnecessarily installs python3 onto the system

  Proposal:
  - Split runtime requirements from apparmor into apparmor-minimal
  - have apparmor depend on apparmor-minimal
  - change snapd's dependency on apparmor to apparmor-minimal

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

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

[Touch-packages] [Bug 1865519] [NEW] apparmor depends on python3

[Sergio Schvezov]

Public bug reported:

The TL;DR;
- AppArmor depends on python3 to support aa-status.
- snapd depends on apparmor.
- buildd images have no python
- building snaps requires snapd
- snapd does not require aa-status
- building snaps unnecessarily installs python3 onto the system

Proposal:
- Split runtime requirements from apparmor into apparmor-minimal
- have apparmor depend on apparmor-minimal
- change snapd's dependency on apparmor to apparmor-minimal

** Affects: snapd
 Importance: Undecided
 Status: New

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

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

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

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

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

Title:
  apparmor depends on python3

Status in snapd:
  New
Status in apparmor package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  The TL;DR;
  - AppArmor depends on python3 to support aa-status.
  - snapd depends on apparmor.
  - buildd images have no python
  - building snaps requires snapd
  - snapd does not require aa-status
  - building snaps unnecessarily installs python3 onto the system

  Proposal:
  - Split runtime requirements from apparmor into apparmor-minimal
  - have apparmor depend on apparmor-minimal
  - change snapd's dependency on apparmor to apparmor-minimal

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

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

[Touch-packages] [Bug 1865517] [NEW] cannot log in with long username

[Jo K]

Public bug reported:

We use ldap authentication with mail addresses as usernames.
So usernames are not posix and some are > 32 chars but are working.

Some of them fire a bug :
When trying to log, it doesn't asks for password, it just wait some seconds 
then reset to ask username.

I can't clearly identify which regex fire the bug or not but this one does
"username.lastnamelastnamelastn...@domain.fr"

I reproduce it on ubuntu 18.04 and 20.04 daylibuild.

In auth.log, that line pops up when bug is started

"Mar  2 16:23:14 premier agetty[97945]: checkname failed: Operation not
permitted"

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

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

Title:
  cannot log in with long username

Status in pam package in Ubuntu:
  New

Bug description:
  We use ldap authentication with mail addresses as usernames.
  So usernames are not posix and some are > 32 chars but are working.

  Some of them fire a bug :
  When trying to log, it doesn't asks for password, it just wait some seconds 
then reset to ask username.

  I can't clearly identify which regex fire the bug or not but this one does
  "username.lastnamelastnamelastn...@domain.fr"

  I reproduce it on ubuntu 18.04 and 20.04 daylibuild.

  In auth.log, that line pops up when bug is started

  "Mar  2 16:23:14 premier agetty[97945]: checkname failed: Operation
  not permitted"

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

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

[Touch-packages] [Bug 1865516] [NEW] Allow packages not related to installation, to be available for install to use apps that help triage also.

[Kangarooo Jānis]

Public bug reported:

Allow packages not related to installation, to be available for install
to use apps that help triage also.

Gif maker Peek
Boot fixer boot-repair
etc.. (can post here more good triaging apps)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-desktop (not installed)
ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
Uname: Linux 5.4.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
CurrentDesktop: KDE
Date: Mon Mar  2 17:08:39 2020
InstallationDate: Installed on 2020-03-01 (0 days ago)
InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (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 ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1865516

Title:
  Allow packages not related to installation, to be available for
  install to use apps that help triage also.

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Allow packages not related to installation, to be available for
  install to use apps that help triage also.

  Gif maker Peek
  Boot fixer boot-repair
  etc.. (can post here more good triaging apps)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar  2 17:08:39 2020
  InstallationDate: Installed on 2020-03-01 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1865516] Re: Allow packages not related to installation, to be available for install to use apps that help triage also.

[Kangarooo Jānis]

https://bugs.launchpad.net/boot-repair/+bug/1865377


** Attachment added: "Screenshot_20200301_195142.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1865516/+attachment/5332745/+files/Screenshot_20200301_195142.png

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

Title:
  Allow packages not related to installation, to be available for
  install to use apps that help triage also.

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Allow packages not related to installation, to be available for
  install to use apps that help triage also.

  Gif maker Peek
  Boot fixer boot-repair
  etc.. (can post here more good triaging apps)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar  2 17:08:39 2020
  InstallationDate: Installed on 2020-03-01 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1865504] Re: hwclock reports incorrect status in audit message

[Joy Latten]

** Description changed:

+ [IMPACT]
+ hwclock reports incrorect status in audit message
+ 
+ hwclock calls audit_log_user_message(3) to create an audit entry.
  audit_log_user_message(3) result 1 is "success" and 0 is
  "failed", hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse
- status. Thus reports status incorrectly in audit message. This has been fixed 
upstream in 
https://github.com/karelzak/util-linux/commit/189edf1fe501ea39b35911337eab1740888fae7a
+ status. Thus reports it's status incorrectly in audit message. 
+ 
+ It is a requirement for Common Criteria Certification that hwclock
+ reports correct status in audit message.
+ 
+ This has been fixed upstream in https://github.com/karelzak/util-
+ linux/commit/189edf1fe501ea39b35911337eab1740888fae7a
+ 
+ [TEST]
+ 
+ Steps to test:
+ 1. Install auditd
+ 2. Run following testcase,
+ 
+ # hwclock
+ 2020-03-02 15:03:03.280351+
+ # hwclock --set --date "1/1/2000 00:00:00"
+ # echo $?
+ 0
+ # hwclock
+ 2000-01-01 00:00:05.413924+
+ # hwclock --utc --systohc
+ # echo $?
+ 0
+ # hwclock
+ 2020-03-02 15:07:00.264331+
+ 
+ Following audit messages from /var/log/audit/audit.log,
+ 
+ type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0 auid=1000 
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips 
addr=? terminal=pts/0 res=failed'
+ type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0 auid=1000 
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips 
addr=? terminal=pts/0 res=failed'
+ 
+ Note that last entry in each audit record produced when hardware clock
+ was modified has, "res=failed". Although, testcase shows no failure
+ occurred.
+ 
+ [Regression Potential]
+ There should not be any regression to fix the status given to auditd.

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

Title:
  hwclock reports incorrect status in audit message

Status in util-linux package in Ubuntu:
  New

Bug description:
  [IMPACT]
  hwclock reports incrorect status in audit message

  hwclock calls audit_log_user_message(3) to create an audit entry.
  audit_log_user_message(3) result 1 is "success" and 0 is
  "failed", hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse
  status. Thus reports it's status incorrectly in audit message. 

  It is a requirement for Common Criteria Certification that hwclock
  reports correct status in audit message.

  This has been fixed upstream in https://github.com/karelzak/util-
  linux/commit/189edf1fe501ea39b35911337eab1740888fae7a

  [TEST]

  Steps to test:
  1. Install auditd
  2. Run following testcase,

  # hwclock
  2020-03-02 15:03:03.280351+
  # hwclock --set --date "1/1/2000 00:00:00"
  # echo $?
  0
  # hwclock
  2000-01-01 00:00:05.413924+
  # hwclock --utc --systohc
  # echo $?
  0
  # hwclock
  2020-03-02 15:07:00.264331+

  Following audit messages from /var/log/audit/audit.log,

  type=USYS_CONFIG msg=audit(1583161562.884:105): pid=2084 uid=0 auid=1000 
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips 
addr=? terminal=pts/0 res=failed'
  type=USYS_CONFIG msg=audit(1583161614.497:106): pid=2103 uid=0 auid=1000 
ses=1 msg='op=change-system-time exe="/sbin/hwclock" hostname=bionic-fips 
addr=? terminal=pts/0 res=failed'

  Note that last entry in each audit record produced when hardware clock
  was modified has, "res=failed". Although, testcase shows no failure
  occurred.

  [Regression Potential]
  There should not be any regression to fix the status given to auditd.

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

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

[Touch-packages] [Bug 1865516] Re: Allow packages not related to installation, to be available for install to use apps that help triage also.

[Kangarooo Jānis]

** Attachment added: "Screenshot_20200302_164639.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1865516/+attachment/5332746/+files/Screenshot_20200302_164639.png

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

Title:
  Allow packages not related to installation, to be available for
  install to use apps that help triage also.

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Allow packages not related to installation, to be available for
  install to use apps that help triage also.

  Gif maker Peek
  Boot fixer boot-repair
  etc.. (can post here more good triaging apps)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar  2 17:08:39 2020
  InstallationDate: Installed on 2020-03-01 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1865516] Re: Allow packages not related to installation, to be available for install to use apps that help triage also.

[Kangarooo Jānis]

https://bugs.launchpad.net/ubuntu/+source/peek/+bug/1865514

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

Title:
  Allow packages not related to installation, to be available for
  install to use apps that help triage also.

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Allow packages not related to installation, to be available for
  install to use apps that help triage also.

  Gif maker Peek
  Boot fixer boot-repair
  etc.. (can post here more good triaging apps)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Mar  2 17:08:39 2020
  InstallationDate: Installed on 2020-03-01 (0 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Daniel van Vugt]

I don't have any headset exhibiting such issues myself, but it sounds
like pulseaudio is not detecting all available profiles reliably, maybe
due to a race condition.

Since there are three newer versions of PulseAudio in Ubuntu releases
after 18.04, the first thing we should check is to see if this has
already been fixed. When you can please boot 20.04 (prerelease) from
USB:

  http://cdimage.ubuntu.com/daily-live/current/

and tell us if the bug still exists there.


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

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

Title:
  pulseaudio doesn't detect (new) USB headset

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

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

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

[Touch-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Daniel van Vugt]

** Tags added: bionic

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

Title:
  pulseaudio doesn't detect (new) USB headset

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

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

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

[Touch-packages] [Bug 1865504] [NEW] hwclock reports incorrect status in audit message

[Joy Latten]

Public bug reported:

audit_log_user_message(3) result 1 is "success" and 0 is
"failed", hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse
status. Thus reports status incorrectly in audit message. This has been fixed 
upstream in 
https://github.com/karelzak/util-linux/commit/189edf1fe501ea39b35911337eab1740888fae7a

** Affects: util-linux (Ubuntu)
 Importance: High
 Assignee: Joy Latten (j-latten)
 Status: New

** Changed in: util-linux (Ubuntu)
   Importance: Undecided => Medium

** Changed in: util-linux (Ubuntu)
   Importance: Medium => High

** Changed in: util-linux (Ubuntu)
 Assignee: (unassigned) => Joy Latten (j-latten)

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

Title:
  hwclock reports incorrect status in audit message

Status in util-linux package in Ubuntu:
  New

Bug description:
  audit_log_user_message(3) result 1 is "success" and 0 is
  "failed", hwclock use standard EXIT_{SUCCESS,FAILURE} macros with reverse
  status. Thus reports status incorrectly in audit message. This has been fixed 
upstream in 
https://github.com/karelzak/util-linux/commit/189edf1fe501ea39b35911337eab1740888fae7a

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

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

[Touch-packages] [Bug 1865437] Re: satpy: autopkgtest unable to run on s390x

[Graham Inggs]

force-reset-test satpy/0.19.1-1/s390x

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

Title:
  satpy: autopkgtest unable to run on s390x

Status in python-pyproj package in Ubuntu:
  New
Status in python-xarray package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in satpy package in Ubuntu:
  New

Bug description:
  satpy now has a test-dependency on python3-zarr which is not
  installable on s390x due to python3-numcodecs not being available
  there

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

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

[Touch-packages] [Bug 1865499] Re: pulseaudio doesn't detect (new) USB headset

[Timo Denissen]

** Summary changed:

- pulseaudio doesn't new usb headset
+ pulseaudio doesn't detect (new) USB headset

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

Title:
  pulseaudio doesn't detect (new) USB headset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

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

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

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

[Łukasz Zemczak]

Hello! Is this actually verified already? Asking since there is another
alsa-lib upload in the queue, blocked on this one getting released.

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

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

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1859754/+subscriptions

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

[Touch-packages] [Bug 1865499] [NEW] pulseaudio doesn't detect (new) USB headset

[Timo Denissen]

Public bug reported:

When booting the system (Lenovo Thinkpad L480/L490), all connected USB
headsets are recognized and can be used, and configured via pavucontrol.

When hot-plugging the USB headset, either the speaker is recognized, or
the microphone, rarely both. But when both are recognized, the
microphone is always a "multichannel" device. When both the speaker and
the "multichannel" microphone are recognized, only one can be used -
either speaker or microphone. When selecting the speaker, the microphone
is switched back to any other device available, them same goes for the
microphone and the speaker - any other speaker is selected.

A workaround is to plug in the USB headset and run "pkill -U $USER
pulseaudio". Everything works fine until the next hot-plug (eg. a second
headset).

Running "lsb_release -a" gives   
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.4 LTS
Release:18.04
Codename:   bionic

Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
our users are affected by this bug, all running the same Ubuntu and
package versions. I activated the proposed repository to check if any
updates available fix the problem, but to no avail. I also switched
kernels (from 4.15 to 5.5 mainline from
https://wiki.ubuntu.com/Kernel/MainlineBuilds).

I read bug #1325282
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282) and
it sounds somewhat very familiar, but instead of "env={}" in /usr/share
/ubuntu-drivers-common/detect/sl-modem.py there's "env=env". Removing
"env=env" doesn't resolve the problem.

Do you require additional information?

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

** Attachment added: "pulseaudio.info"
   
https://bugs.launchpad.net/bugs/1865499/+attachment/5332737/+files/pulseaudio.info

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

Title:
  pulseaudio doesn't detect (new) USB headset

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When booting the system (Lenovo Thinkpad L480/L490), all connected USB
  headsets are recognized and can be used, and configured via
  pavucontrol.

  When hot-plugging the USB headset, either the speaker is recognized,
  or the microphone, rarely both. But when both are recognized, the
  microphone is always a "multichannel" device. When both the speaker
  and the "multichannel" microphone are recognized, only one can be used
  - either speaker or microphone. When selecting the speaker, the
  microphone is switched back to any other device available, them same
  goes for the microphone and the speaker - any other speaker is
  selected.

  A workaround is to plug in the USB headset and run "pkill -U $USER
  pulseaudio". Everything works fine until the next hot-plug (eg. a
  second headset).

  Running "lsb_release -a" gives   
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.4 LTS
  Release:  18.04
  Codename: bionic

  Attached is the output from "ubuntu-bug pulseaudio". Currently 10 % of
  our users are affected by this bug, all running the same Ubuntu and
  package versions. I activated the proposed repository to check if any
  updates available fix the problem, but to no avail. I also switched
  kernels (from 4.15 to 5.5 mainline from
  https://wiki.ubuntu.com/Kernel/MainlineBuilds).

  I read bug #1325282
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1325282)
  and it sounds somewhat very familiar, but instead of "env={}" in
  /usr/share/ubuntu-drivers-common/detect/sl-modem.py there's "env=env".
  Removing "env=env" doesn't resolve the problem.

  Do you require additional information?

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

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

[Touch-packages] [Bug 1864057] Re: Xorg Server terminated with error (1) on Intel/18.04 Laptop

[Michel-Ekimia]

** Description changed:

  On a 18.04 ( kernel 5.3 ) Intel laptop :
  
  - At cold start Xorg keeps crashing several times
  - After Several restart , Xorg finally suceed to start
  - it seems user encounter that since kernel 5.3
  
- 
- Notes : 
- Possible Root cause : 
+ Notes :
+ Possible Root cause :
  
  [ 9.014] (EE) modeset(0): drmSetMaster failed: Permission denied
  [ 9.014] (EE)
  Fatal server error:
  [ 9.014] (EE) AddScreen/ScreenInit failed for driver 0
  [ 9.014] (EE)
  
- 
  It seems related to systemd :
  
  https://github.com/systemd/systemd/issues/13943
+ 
+ 
+ Conclusion : 
+ 
+ - Fix is realeased in 20.04
+ - Fix will never be released ( AFAIK ) in 18.04 
  
  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1325]
  InstallationDate: Installed on 2019-03-04 (353 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 06cb:00a8 Synaptics, Inc.
   Bus 001 Device 004: ID 8087:0025 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook N150ZU
  Package: xorg-server (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AG.utf8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=5b433ea6-7902-4568-9ee0-36a15ff2f274 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Tags:  bionic ubuntu
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
  
  _MarkForUpload: True
  dmi.bios.date: 10/19/2018
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.01
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150ZU
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.01:bd10/19/2018:svnNotebook:pnN150ZU:pvrNotApplicable:rvnNotebook:rnN150ZU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: N150ZU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

Title:
  Xorg Server terminated with error (1) on Intel/18.04 Laptop

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  On a 18.04 ( kernel 5.3 ) Intel laptop :

  - At cold start Xorg keeps crashing several times
  - After Several restart , Xorg finally suceed to start
  - it seems user encounter that since kernel 5.3

  Notes :
  Possible Root cause :

  [ 9.014] (EE) modeset(0): drmSetMaster failed: Permission denied
  [ 9.014] (EE)
  Fatal server error:
  [ 9.014] (EE) AddScreen/ScreenInit failed for driver 0
  [ 9.014] (EE)

  It seems related to systemd :

  https://github.com/systemd/systemd/issues/13943

  
  Conclusion : 

  - Fix is realeased in 20.04
  - Fix will never be released ( AFAIK ) in 18.04 

  
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroRelease: Ubuntu 18.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3ea0] (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:1325]
  InstallationDate: Installed on 2019-03-04 (353 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd
   Bus 001 Device 

[Touch-packages] [Bug 1862846] Please test proposed package

[Łukasz Zemczak]

Hello Alberto, or anyone else affected,

Accepted util-linux into eoan-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.34-0.1ubuntu2.3 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  Crash and failure installing focal

Status in subiquity:
  New
Status in curtin package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in curtin source package in Eoan:
  Invalid
Status in util-linux source package in Eoan:
  Fix Committed
Status in curtin source package in Focal:
  Fix Released
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  New

Bug description:
  [Impact]

   * lsblk no longer prints a partition's parent 
 kernel device name (the wholedisk).
 (i.e., 'lsblk -no PKNAME /dev/partition')

   * Another impact is the 'removable media' check
 always return zero for partitions.
 (i.e., 'lsblk -no RM /dev/partition')

   * The regression was introduced on v2.34, only
 Eoan (v2.34) and later are affected.
 Disco (v2.33) and earlier are not affected.

   * The regression is fixed in v2.35, in commit
 e3bb9bfb76c1 ("lsblk: force to print PKNAME
 for partition"); fixes RM for partition too.

  [Test Case]

   * lsblk -no PKNAME /dev/vda1 # partition

   * Expected output: vda # wholedisk

   * Current output: (nothing)

  [Regression Potential]

   * Columns that depend on a partition device's
 parent device (i.e., seen as 'wholedisk')
 could in theory show incorrect values if
 another bug is present in v2.34 for that.

   * Other usages of 'parent' pointer in the
 function have been examined and reported
 (e.g. issue w/ removable media column),
 and others found to not have issues
 (e.g. --merge option, to group multiple
 parents of a device, as in RAID.)
 
  [Other Info]

   * The impacts to the curtin source package
 have been addressed in other way, it no
 longer requires util-linux, comment #14.

   * util-linux github issue:
 https://github.com/karelzak/util-linux/issues/813

  [Original Bug Description]

  During an install of the daily live image for 20.04 Ubuntu Server, the
  installer first crashed and restarted itself, then failed to install
  the system.

  Attached are the logs left on the install USB key.

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

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

[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal

[Łukasz Zemczak]

Hey! The package looks good so I'll accept it. In the impact you have
mentioned that currently lsblk -no RM also doesn't work correctly, so
maybe we should add it to the test case?

** Changed in: util-linux (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  Crash and failure installing focal

Status in subiquity:
  New
Status in curtin package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Fix Released
Status in curtin source package in Eoan:
  Invalid
Status in util-linux source package in Eoan:
  Fix Committed
Status in curtin source package in Focal:
  Fix Released
Status in util-linux source package in Focal:
  Fix Released
Status in util-linux package in Debian:
  New

Bug description:
  [Impact]

   * lsblk no longer prints a partition's parent 
 kernel device name (the wholedisk).
 (i.e., 'lsblk -no PKNAME /dev/partition')

   * Another impact is the 'removable media' check
 always return zero for partitions.
 (i.e., 'lsblk -no RM /dev/partition')

   * The regression was introduced on v2.34, only
 Eoan (v2.34) and later are affected.
 Disco (v2.33) and earlier are not affected.

   * The regression is fixed in v2.35, in commit
 e3bb9bfb76c1 ("lsblk: force to print PKNAME
 for partition"); fixes RM for partition too.

  [Test Case]

   * lsblk -no PKNAME /dev/vda1 # partition

   * Expected output: vda # wholedisk

   * Current output: (nothing)

  [Regression Potential]

   * Columns that depend on a partition device's
 parent device (i.e., seen as 'wholedisk')
 could in theory show incorrect values if
 another bug is present in v2.34 for that.

   * Other usages of 'parent' pointer in the
 function have been examined and reported
 (e.g. issue w/ removable media column),
 and others found to not have issues
 (e.g. --merge option, to group multiple
 parents of a device, as in RAID.)
 
  [Other Info]

   * The impacts to the curtin source package
 have been addressed in other way, it no
 longer requires util-linux, comment #14.

   * util-linux github issue:
 https://github.com/karelzak/util-linux/issues/813

  [Original Bug Description]

  During an install of the daily live image for 20.04 Ubuntu Server, the
  installer first crashed and restarted itself, then failed to install
  the system.

  Attached are the logs left on the install USB key.

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

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

[Touch-packages] [Bug 1865351] Re: Update to poppler 0.86.0 in Focal

[Sebastien Bacher]

Thank you for your bug report, why do you think we should update to this
version? Focal is feature frozen now and new poppler versions come with
soname changes which makes they require full transitions to their
rdepends so it's not trivial update

** Changed in: poppler (Ubuntu)
   Importance: Undecided => Wishlist

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

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

Title:
  Update to poppler 0.86.0 in Focal

Status in poppler package in Ubuntu:
  Incomplete

Bug description:
  Please update to poppler 0.86.0 in Focal

  Release 0.86.0:
  core:
  * Fix link content exfiltration attack
  * Splash: Implement gouraudTriangleShadedFill for some non parametrized 
shadings
  * Fix case unsensitive search for Old Hungarian, Warang Citi, Medefaidrin and 
Adlam
  * Internal code improvements

  glib:
  * Automatic handle of page's cropbox on annots. Issue #129
  * Fix memory leak if poppler_document_new_from_file fails
  * Minor speed optimization on poppler_page_get_annot_mapping

  utils:
  * pdfdetach: add 'savefile' option
  * pdftoppm/pdftocairo: Fix more odd/even mismatch

  qt5:
  * Fix loading from iodevice

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

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

[Touch-packages] [Bug 1742941] Re: zlib: improve crc32 performance on P8

[Frank Heimes]

The crc32 performance optimization for P8 were added to zlib version 
1.2.11.dfsg-2ubuntu1 (thx to doko) and landed already in proposed:
"zlib | 1:1.2.11.dfsg-2ubuntu1  | focal-proposed  | source"
Hence changing the status of this ticket to Fix Committed.

** Changed in: zlib (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: ubuntu-power-systems
   Status: In Progress => Fix Committed

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

Title:
  zlib: improve  crc32 performance on P8

Status in The Ubuntu-power-systems project:
  Fix Committed
Status in zlib package in Ubuntu:
  Fix Committed

Bug description:
  Calculate the checksum of data that is 16 byte aligned and a multiple
  of  16 bytes.

  The first step is to reduce it to 1024 bits. We do this in 8 parallel
   chunks in order to mask the latency of the vpmsum instructions. If we
   have more than 32 kB of data to checksum we repeat this step multiple
   times, passing in the previous 1024 bits.

   The next step is to reduce the 1024 bits to 64 bits. This step adds
   32 bits of 0s to the end - this matches what a CRC does. We just
   calculate constants that land the data in this 32 bits.

   We then use fixed point Barrett reduction to compute a mod n over GF(2)
   for n = CRC using POWER8 instructions. We use x = 32.

   http://en.wikipedia.org/wiki/Barrett_reduction

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

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

[Touch-packages] [Bug 1822501] Re: chpasswd mishandles --root option

[Colin Hogben]

I decided to "scratch my own itch" and submitted a PR upstream.

https://github.com/shadow-maint/shadow/issues/219


** Bug watch added: github.com/shadow-maint/shadow/issues #219
   https://github.com/shadow-maint/shadow/issues/219

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

Title:
  chpasswd mishandles --root option

Status in shadow package in Ubuntu:
  New

Bug description:
  I did

echo root:secret | chpasswd --root=/mnt/img

  I expected the password to be changed on the mounted filesystem at /mnt/img
  Instead, it changed the password on the host filesystem.

  Although the chpasswd(1) manual page does not list --root=CHROOT_DIR
  as valid syntax, it is common for programs to accept both --arg param
  and --arg=param as valid syntax (as per gnu getopt_long).  At the very
  least, chpasswd should fail with an error report if unacceptable
  option syntax is used, rather than ignoring it.

  passwd 1:4.5-1ubuntu1 on Ubuntu 18.04.2 LTS

  (though bug tracker seems to think this does not exist in Ubuntu)

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

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

[Touch-packages] [Bug 1863873] Re: Systemd fails to configure bridged network in LXC container

[Thomas Wien]

Thanks a lot for your explanations and workaround examples.

I expanded our ansible update playbooks to check if
/etc/netplan/10-lxc.yaml is installed, then to remove that file, runs
"netplan apply" and then remove the package "netplan.io". It seems to
work in our environment, without loosing the network configuration while
updating and also after reboot.

Here is the ansible section we tested. Maybe it is helpful to anyone
else. This script comes with no warranty and should be tested in your
environment thoroughly.

- name: Is Netplan configuring LXC?
  stat:
path: /etc/netplan/10-lxc.yaml
  register: netplan
- name: Remove networkd/netplan configuration
  file:
path: /etc/netplan/10-lxc.yaml
state: absent
  when: "netplan.stat.exists == true and ansible_virtualization_type == 'lxc'"
- name: Reload networkd/netplan
  command: netplan apply
  when: "netplan.stat.exists == true and ansible_virtualization_type == 'lxc'"
- name: Remove netplan.io
  apt:
name: netplan.io
state: absent
  when: "netplan.stat.exists == true and ansible_virtualization_type == 'lxc'"

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

Title:
  Systemd fails to configure bridged network in LXC container

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  In all our LXC containers running Bionic Beaver, Eoan Ermine or Focal
  Fossa, installing the latest systemd package results in losing network
  configuration.

  It is still possible to configure the network "by hand" with
  /usr/sbin/ip, but of course, the configuration is lost at reboot.

  An example is provided, followed by a complete procedure to reproduce
  the issue.

  Affected container distributions
  

  Xenial Xerus systemd 229-4ubuntu21.27: OK, not affected
  Bionic Beaver systemd 237-3ubuntu10.38: OK, not affected
  Bionic Beaver systemd 237-3ubuntu10.39: BUGGY
  Disco Dingo systemd 240-6ubuntu5.8: OK, not affected
  Eoan Ermine systemd 242-7ubuntu3.6: OK, not affected
  Eoan Ermine systemd 242-7ubuntu3.7: BUGGY
  Focal Fossa systemd 244.2-1ubuntu1: BUGGY

  Affected hosts
  ==

  Debian Buster with default 4.19.0-6-amd64, custom 5.3.9, 5.4.8 or 5.4.13 
kernel
  Ubuntu 16.04 lxc 2.0.8-0ubuntu1~16.04.2 
(https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1863873/comments/7)

  Example
  ===

  Example host bridge configuration
  -

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: eth0:  mtu 1500 qdisc mq master br0 state 
UP group default qlen 1000
  link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff
  3: eth1:  mtu 1500 qdisc mq master br1 
state DOWN group default qlen 1000
  link/ether 00:25:90:2b:f1:61 brd ff:ff:ff:ff:ff:ff
  4: br0:  mtu 1500 qdisc noqueue state UP 
group default qlen 1000
  link/ether 00:25:90:2b:f1:60 brd ff:ff:ff:ff:ff:ff
  inet 192.168.252.24/24 brd 192.168.252.255 scope global br0
     valid_lft forever preferred_lft forever
  inet 192.168.193.203/24 brd 192.168.193.255 scope global br0:1
     valid_lft forever preferred_lft forever
  inet6 fe80::225:90ff:fe2b:f160/64 scope link
     valid_lft forever preferred_lft forever

  Example container network configuration
  ---

  lxc.net.0.type = veth
  lxc.net.0.veth.pair = vps525389
  lxc.net.0.flags = up
  lxc.net.0.link = br0
  lxc.net.0.hwaddr = 02:00:00:52:53:89
  lxc.net.0.name = eth0
  lxc.net.0.ipv4.gateway = 192.168.252.1
  lxc.net.0.ipv4.address = 192.168.252.177/32

  Example steps to reproduce, inside the container
  

  root@vps525389:~# lsb_release -rd
  Description:Ubuntu 18.04.4 LTS
  Release:18.04
  root@vps525389:~# apt-cache policy systemd
  systemd:
    Installed: 237-3ubuntu10.38
    Candidate: 237-3ubuntu10.39
    Version table:
   237-3ubuntu10.39 500
  500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 237-3ubuntu10.38 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  root@vps525389:~# ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  1958: eth0@if1959:  mtu 1500 qdisc noqueue 
state UP 

[Touch-packages] [Bug 1855893] Re: Properly let PCM leave suspended state when hardware doesn't support PCM resume

[Kai-Heng Feng]

** Changed in: pulseaudio (Ubuntu Bionic)
 Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)

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

Title:
  Properly let PCM leave suspended state when hardware doesn't support
  PCM resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume.

  [Fix]
  According to alia-lib's document, to make PCM properly leave suspended state, 
we only use snd_pcm_resume() if hardware support PCM resume.
  For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB 
dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to 
make device leave suspended state. This patch defaults to use snd_pcm_drop() to 
achieve the goal.

  [Test]
  1. See if microphone on snd-usb-audio works in gnome-control-center/cheese.
  2. Suspend/resume.
  3. See if microphone still works in those apps.
  I can the issue is fixed after each suspend/resume cycle.

  [Regression Potential]
  Low. This fix makes PCM suspend/resume more reliable. No functional change 
intended. I also don't find any regression during some smoke test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1855893/+subscriptions

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

[Touch-packages] [Bug 1865373] Re: Authentication Prompt cut off

[Daniel van Vugt]

Can you please run this command to send us more information about your
gnome-shell?

  apport-collect 1865373

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

** Changed in: gnome-shell (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/1865373

Title:
  Authentication Prompt cut off

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Every time the "Authentication Required" prompt pops up, the right side is 
cut off short. 
  My resolution is currently set to 1600x900 on a 1920x1080 13." screen.  The 
same thing happened at native resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  Uname: Linux 5.4.0-14-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  1 14:40:57 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:081b]
  InstallationDate: Installed on 2020-02-29 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200229)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 0bda:58ca Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 004: ID 0a5c:5832 Broadcom Corp. 5880
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 7390
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_evtvik@/vmlinuz-5.4.0-14-generic 
root=ZFS=rpool/ROOT/ubuntu_evtvik ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.13.1
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.13.1:bd11/08/2019:svnDellInc.:pnLatitude7390:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7390
  dmi.product.sku: 081B
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1767654] Re: [Intel Braswell] Cursor gets stuck on left side of the screen

[Kai-Heng Feng]

I can't reproduce this with Focal daily image. Can you guys please
confirm?

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

Title:
  [Intel Braswell] Cursor gets stuck on left side of the screen

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  When moving the cursor to the left side of the screen, it stops close
  to the edge. The cursor still moves over in the area but invisible
  until I move it out of the area. When it doesn't do this, glitching
  occurs on the screen where the cursor is until I log out. And on
  screen cast it shows the cursor going to the side of the screen and
  moving.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 28 09:49:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx 
Integrated Graphics Controller [8086:22b1] (rev 21) (prog-if 00 [VGA 
controller])
 Subsystem: Intel Corporation Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:2060]
  InstallationDate: Installed on 2018-04-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-20-generic 
root=UUID=c6f92850-287a-4747-ac0d-3af593994183 ro quiet splash vt.handoff=1 
initrd=boot\initrd.img-4.15.0-20-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2017
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PYBSWCEL.86A.0062.2017.0308.1328
  dmi.board.name: NUC5CPYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H61145-408
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0062.2017.0308.1328:bd03/08/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-408:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1770429] Re: Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3

[Kiran Dhakal]

#7 worked for me, Thanks EDEMPCO (edemco)
But my internal speakers are now detected as HDMI / DisplayPort - Built-in Audio

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

Title:
  Ubuntu 18.04 No audio from speakers. Headphones working. Surface Pro 3

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I updated my Surface Pro 3 From Ubuntu 17.10 to Ubuntu 18.04 (did a clean 
install) and the only  audio working was from the headphone jack.
  I tried all these:
  [troubleshooting 
guide](https://help.ubuntu.com/community/SoundTroubleshootingProcedure)
  [this 
answer](https://askubuntu.com/questions/117842/no-sound-from-speakers-but-headphones-work)
  [another 
answer](https://askubuntu.com/questions/829520/ubuntu-16-04-no-sound-from-speakers-only-headphones-working)

  I went back and tested the live CD and even the live cd has no audio
  through the speakers. so this must be related to 18.04. I never had
  sound issues before and under windows audio still works correctly.

  here is my alsa iformation http://www.alsa-
  project.org/db/?f=8bf135db52610a603014779ef24041a491c8a32d

  and here is how I fixed it:

  renaming /etc/modprobe.d/alsa-base.conf to /etc/modprobe.d/alsa-
  base.bk , then rebooting the computer fixed the my speaker sound
  issue.

  I then restored line by line in to /etc/modprobe.d/alsa-base.conf, rebooting 
between restored lines, until all lines were back and ... it still worked!
  so I restored the original /etc/modprobe.d/alsa-base.conf and rebooted the 
computer and everything was still working
  so I am not sure what the problem was but is now fixed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.16.7-041607-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  carlosr2267 F pulseaudio
   /dev/snd/controlC0:  carlosr2267 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 10 10:15:29 2018
  InstallationDate: Installed on 2018-04-27 (13 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3.11.2350
  dmi.board.asset.tag: 0
  dmi.board.name: Surface Pro 3
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: 0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: 1
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3.11.2350:bd01/23/2018:svnMicrosoftCorporation:pnSurfacePro3:pvr1:rvnMicrosoftCorporation:rnSurfacePro3:rvr1:cvnMicrosoftCorporation:ct9:cvr1:
  dmi.product.family: Surface
  dmi.product.name: Surface Pro 3
  dmi.product.version: 1
  dmi.sys.vendor: Microsoft Corporation
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2018-05-09T14:04:13.313882

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

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

[Touch-packages] [Bug 1865257] Re: Pulseaudio needs kernal conf IMU=size (64)

[Daniel van Vugt]

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

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

Title:
  Pulseaudio needs kernal conf IMU=size (64)

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Since Pulseaudio 11.0
  https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/11.0/
  "Improved bluetooth MTU configuration
  The packet size (a.k.a. MTU, "maximum transmission unit") that PulseAudio 
uses with the bluetooth HSP profile was previously always configured to be 48 
bytes. That worked with most hardware, but some adapters require a different 
packet size. Now PulseAudio asks the kernel what packet size should be used, 
which fixes the problem.

  However, a new problem appeared: some adapters that used to work with
  48 byte packet size don't any more work with the size that the kernel
  tells PulseAudio to use. If you find that HSP audio stopped working
  when upgrading to PulseAudio 11.0, you can revert to the old behaviour
  by passing option "autodetect_mtu=no" to module-bluetooth-discover in
  /etc/pulse/default.pa. If that fixes the problem, then please report
  the problem to the BlueZ and/or PulseAudio developers, so that the
  kernel can be fixed.

  Update: We decided to disable the MTU autodetection in 11.1 by
  default, because the feature caused too much problems and it looked
  like the kernel would not really get fixed even when people reported
  issues."

  Presume its a config option in the kernel that differs on each model.
  Pi3/4 should be 64 as they are very much like the 48 byte packages in
  reverse as don't work with the default of 48.

  Its listed as Pulse audio but presume it should be a config setting of
  the kernel for each Pi model.

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

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

[Touch-packages] [Bug 1865254] Re: After fresh installation 19.10 on Dell vostro 15 3568 it is showing screen blinking when I try to unlock and locking with Super+L

[Daniel van Vugt]

It sounds like you are seeing the wrong virtual terminal. Please try
Ctrl+Alt+F1 or Ctrl+Alt+F2. And please also attach a photo or video of
the issue.

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

Title:
  After fresh installation 19.10 on Dell vostro 15 3568 it is showing
  screen blinking when I try to unlock and locking with Super+L

Status in gdm3 package in Ubuntu:
  New

Bug description:
  I am new to report such issues so I just don't know what to share
  here. though below is the kernel and syslog of the system.

  I having this issue with this model only as many of this model to
  test.

  Kernel: 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
  x86_64 x86_64 x86_64 GNU/Linux

  Syslog:-

  Feb 29 12:01:16 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for 
context 0x5603df1c4330 ==
  Feb 29 12:01:16 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0   5603e0fd7930 i 
  resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15)
  Feb 29 12:01:16 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1   7ffceebe4f80 b 
  self-hosted:975 (7fdf75834160 @ 392)
  Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button 
(0x5603e0eaccd0), has been already deallocated — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
  Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for 
context 0x5603df1c4330 ==
  Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0   5603e0fd7930 i 
  resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15)
  Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1   7ffceebe4f80 b 
  self-hosted:975 (7fdf75834160 @ 392)
  Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button 
(0x5603e0eaccd0), has been already deallocated — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
  Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for 
context 0x5603df1c4330 ==
  Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0   7ffceebe4540 b 
  resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15)
  Feb 29 12:01:17 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1   7ffceebe4f80 b 
  self-hosted:975 (7fdf75834160 @ 392)
  Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button 
(0x5603e0eaccd0), has been already deallocated — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
  Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for 
context 0x5603df1c4330 ==
  Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0   7ffceebe4ed0 b 
  resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15)
  Feb 29 12:01:18 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1   7ffceebe4f80 b 
  self-hosted:975 (7fdf75834160 @ 392)
  Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: Object St.Button 
(0x5603e0eaccd0), has been already deallocated — impossible to get any property 
from it. This might be caused by the object having been destroyed from C code 
using something such as destroy(), dispose(), or remove() vfuncs.
  Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: == Stack trace for 
context 0x5603df1c4330 ==
  Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: #0   7ffceebe4ed0 b 
  resource:///org/gnome/shell/ui/workspace.js:709 (7fdf75972e50 @ 15)
  Feb 29 12:01:19 Bigstep-Vostro-15-3568 gnome-shell[1779]: #1   7ffceebe4f80 b 
  self-hosted:975 (7fdf75834160 @ 392)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb 29 11:49:13 2020
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793]
  InstallationDate: Installed on 2020-02-28 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: Dell Inc. Vostro 15-3568
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=e4c9da5a-c5ed-4509-ac83-acf0ed89a193 ro quiet splash vt.handoff=7

[Touch-packages] [Bug 1864982] Re: Ubuntu desktop computer doesn't seem to lock correctly

[Brian Murray]

** Information type changed from Public to Public Security

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

Title:
  Ubuntu desktop computer doesn't seem to lock correctly

Status in lightdm package in Ubuntu:
  New

Bug description:
  Ubuntu desktop computer doesn't seem to lock correctly if I click "Lock 
Screen" it does lock if I use shortcut. If I use the "lock screen" button then 
anyone can unlock it by merely pressing "ctrl+alt+f7".
  The problem is not that I cannot lock my screen, the problem is I was under 
the impression that my computer was being locked when it was not.
  now that I know that the "Lock Screen" button doesn't work correctly I know 
of other ways to lock my computer still the lock screen button should work and 
it looks like it locked my screen,but if I press "ctrl+alt+f7" then it 
magically unlocks

  So it is a security incident.

  Thanks in Advance.

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

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

[Touch-packages] [Bug 1864997] Re: System is running in low graphics mode

[Daniel van Vugt]

Yes the attached info suggests the graphics mode is correct:

  1366x768 (0x4c) 76.660MHz +HSync -VSync *current +preferred

and also that the GPU is fully supported.

Can you please provide more information like a photo showing what the problem 
is?
 

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (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/1864997

Title:
  System is running in low graphics mode

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am receiving this error while booting

  System is running in low graphics mode.

  I am using Intel core gen 2 graphic card on my lenevo L430 Thinkpad,
  runnin gon 64 bit Linux Xenial 16.04 (LTS).

  Kindly help.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-174.204-generic 4.4.211
  Uname: Linux 4.4.0-174-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Feb 27 17:42:25 2020
  DistUpgraded: 2018-02-07 11:07:14,401 DEBUG /openCache(), new cache size 86347
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:21f7]
  InstallationDate: Installed on 2017-01-23 (1129 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 2466CV8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-174-generic 
root=UUID=88cc2d85-ce2f-4456-b022-dedcdd8398b9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2018-02-07 (750 days ago)
  dmi.bios.date: 06/20/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G3ET36WW(1.10)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2466CV8
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG3ET36WW(1.10):bd06/20/2012:svnLENOVO:pn2466CV8:pvrThinkPadL430:rvnLENOVO:rn2466CV8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2466CV8
  dmi.product.version: ThinkPad L430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Feb 27 17:37:28 2020
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id9020 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Touch-packages] [Bug 1865130] Re: [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to reset the VCPU!!!

[Daniel van Vugt]

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

Title:
  [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, trying to
  reset the VCPU!!!

Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  when trying > DRI_PRIME=1 glxgears , the result in dmesg is as
  following

  [  +0.91] radeon :01:00.0: WB enabled
  [  +0.02] radeon :01:00.0: fence driver on ring 0 use gpu addr 
0x8c00 and cpu addr 0x8ac2d26f
  [  +0.01] radeon :01:00.0: fence driver on ring 1 use gpu addr 
0x8c04 and cpu addr 0xa848de20
  [  +0.01] radeon :01:00.0: fence driver on ring 2 use gpu addr 
0x8c08 and cpu addr 0x1e4494a9
  [  +0.01] radeon :01:00.0: fence driver on ring 3 use gpu addr 
0x8c0c and cpu addr 0x98a9748e
  [  +0.01] radeon :01:00.0: fence driver on ring 4 use gpu addr 
0x8c10 and cpu addr 0xb6ff734d
  [  +0.000212] radeon :01:00.0: fence driver on ring 5 use gpu addr 
0x00075a18 and cpu addr 0x6b4da526
  [  +0.100566] radeon :01:00.0: failed VCE resume (-110).
  [  +0.179115] [drm] ring test on 0 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 1 succeeded in 1 usecs
  [  +0.04] [drm] ring test on 2 succeeded in 1 usecs
  [  +0.06] [drm] ring test on 3 succeeded in 3 usecs
  [  +0.04] [drm] ring test on 4 succeeded in 3 usecs
  [  +1.171892] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015643] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015509] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015572] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015514] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015405] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015442] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015416] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015388] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +1.015379] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
trying to reset the VCPU!!!
  [  +0.019924] [drm:uvd_v1_0_start [radeon]] *ERROR* UVD not responding, 
giving up!!!
  [  +0.40] radeon :01:00.0: failed initializing UVD (-1).
  [  +0.60] [drm] ib test on ring 0 succeeded in 0 usecs
  [  +0.51] [drm] ib test on ring 1 succeeded in 0 usecs
  [  +0.32] [drm] ib test on ring 2 succeeded in 0 usecs
  [  +0.52] [drm] ib test on ring 3 succeeded in 0 usecs
  [  +0.29] [drm] ib test on ring 4 succeeded in 0 usecs

  Also it affects the boot time.

  the used OpenGL renderer is:
  "OpenGL renderer string: AMD OLAND (DRM 2.50.0, 5.3.0-40-generic, LLVM 9.0.0)"

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Feb 28 11:50:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 5.3.0-28-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 5.3.0-40-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed
   virtualbox, 5.2.34, 5.3.0-40-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3801]
     Subsystem: Lenovo Mars [Radeon HD 8670A/8670M/8750M] [17aa:3801]
  InstallationDate: Installed on 2019-09-17 (163 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 20238
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=385a4174-5cfe-49c9-b4c3-9e64a251d432 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 79CN46WW(V3.05)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: INVALID
  dmi.board.vendor: LENOVO
  dmi.board.version: Not 

[Touch-packages] [Bug 1863724] Re: Add missing pci-id's for Comet Lake (CML)

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 19.2.8-0ubuntu0~18.04.3

---
mesa (19.2.8-0ubuntu0~18.04.3) bionic; urgency=medium

  * i965-sync-pciids.diff: Add back three pci-id's for CML that were
lost during a rebase. (LP: #1863724)

 -- Timo Aaltonen   Wed, 19 Feb 2020 07:09:44 +0200

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

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

Title:
  Add missing pci-id's for Comet Lake (CML)

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Bionic:
  Fix Released
Status in mesa source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  After rebasing mesa to 19.2.x debian/patches/i965-sync-pciids.diff was
  updated but some parts of it got accidentally dropped, losing a couple
  of pci-id's for CML. They need to be restored.

  [Test case]

  Install the updates on an affected machine, check with glxinfo -B that
  the proper driver is loaded.

  [Regression potential]

  none, this just adds pci-id's

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

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

[Touch-packages] [Bug 1864980] Re: using hebrew in a german basic setup

[Daniel van Vugt]

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

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  using hebrew in a german basic setup

Status in gnome-control-center package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hi!

  I was trying to use different languages/keyboards like german, english and 
hebrew in a german setup, meaning I put the basić language of my ubuntu into 
german and then wanted to use hebrew aswell, which was not possible and I also 
didn't find a workaround. When I put the basic language of ubuntu into hebrew 
it works (of course), and I realized that in english as basic language it also 
works to change between different languages/keyboards. Would be nice to have 
this option in a german environment aswell. You know, these two countries, they 
have enough issues already ;) 
  Best regards 
  Benedikt

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  Uname: Linux 5.3.0-28-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 27 10:26:24 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Haswell-ULT Integrated Graphics 
Controller [1179:f910]
  InstallationDate: Installed on 2020-02-25 (1 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: TOSHIBA SATELLITE C50-B
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/27/2014
  dmi.bios.vendor: TOSHIBA
  dmi.bios.version: 1.40
  dmi.board.asset.tag: *
  dmi.board.name: ZSWAA
  dmi.board.vendor: TOSHIBA
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: *
  dmi.chassis.type: 10
  dmi.chassis.vendor: TOSHIBA
  dmi.chassis.version: *
  dmi.modalias: 
dmi:bvnTOSHIBA:bvr1.40:bd11/27/2014:svnTOSHIBA:pnSATELLITEC50-B:pvrPSCLUE-01W010GR:rvnTOSHIBA:rnZSWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*:
  dmi.product.family: *
  dmi.product.name: SATELLITE C50-B
  dmi.product.sku: PSCLUE
  dmi.product.version: PSCLUE-01W010GR
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1865450] Re: PermissionError for AppArmor Profiles i.e., SSH

[Shaheena Kazi]

Also, I am creating/ running as root.

** Tags added: apparmor

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

Title:
  PermissionError for AppArmor Profiles i.e., SSH

Status in apparmor package in Ubuntu:
  New

Bug description:
  I have created an AppArmor profile for SSH.
  The profile is created successfully but each time I run aa-logprof it gives 
PermissionError: [Errno 13] 

  
  An example of the error: 
  Traceback (most recent call last):
File "/usr/sbin/aa-enforce", line 35, in module>
  tool.cmd_enforce()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 150, in 
cmd_enforce
  apparmor.set_enforce(profile, program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 293, in 
set_enforce
  change_profile_flags(filename, program, 'complain', False)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 704, in 
change_profile_flags
  set_profile_flags(filename, program, newflags)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 753, in 
set_profile_flags
  os.rename(temp_file.name, prof_filename)
  PermissionError: [Errno 13] Permission denied: 
'/etc/apparmor.d/usr.sbin.tcpdumpwvx1h0xl~' -> 
'/etc/apparmor.d/usr.sbin.tcpdump'
  
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.

  
+++
  Traceback (most recent call last):
File "/usr/sbin/aa-logprof", line 50, in 
  apparmor.do_logprof_pass(logmark)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 1824, in 
do_logprof_pass
  save_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 1921, in 
save_profiles
  write_profile_ui_feedback(profile_name)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3404, in 
write_profile_ui_feedback
  write_profile(profile)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3413, in 
write_profile
  newprof = tempfile.NamedTemporaryFile('w', suffix='~', delete=False, 
dir=profile_dir)
File "/usr/lib/python3.5/tempfile.py", line 688, in NamedTemporaryFile
  (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags, output_type)
File "/usr/lib/python3.5/tempfile.py", line 399, in _mkstemp_inner
  fd = _os.open(file, flags, 0o600)
  PermissionError: [Errno 13] Permission denied: '/etc/apparmor.d/tmpujtge2jq~'

  
  An unexpected error occurred!

  For details, see /tmp/apparmor-bug report-5qnjyx3t.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.
  
+++

  
+++
  root@protegrity-framework314:/var/www# aa-complain /etc/apparmor.d/*
  Profile for /etc/apparmor.d/abstractions not found, skipping
  Profile for /etc/apparmor.d/apache2.d not found, skipping
  Setting /etc/apparmor.d/bin.ping to complain mode.
  Profile for /etc/apparmor.d/cache not found, skipping
  Profile for /etc/apparmor.d/disable not found, skipping
  Setting /etc/apparmor.d/etc.opt.Cluster.cluster_config.status.xml to complain 
mode.
  Setting /etc/apparmor.d/etc.opt.Cluster.cluster_config.xml to complain mode.
  Traceback (most recent call last):
File "/usr/sbin/aa-complain", line 35, in 
  tool.cmd_complain()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 165, in 
cmd_complain
  apparmor.set_complain(profile, program)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 286, in 
set_complain
  change_profile_flags(filename, program, 'complain', True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 704, in 
change_profile_flags
  set_profile_flags(filename, program, newflags)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 720, in 
set_profile_flags
  temp_file = tempfile.NamedTemporaryFile('w', prefix=prof_filename, 
suffix='~', delete=False, dir=profile_dir)
File "/usr/lib/python3.5/tempfile.py", line 688, in NamedTemporaryFile
  (fd, name) = _mkstemp_inner(dir, prefix, suffix, flags, output_type)
File "/usr/lib/python3.5/tempfile.py", line 399, in _mkstemp_inner
  fd = _os.open(file, flags, 0o600)
  PermissionError: [Errno 13] Permission denied: 
'/etc/apparmor.d/etc.opt.Cluster.cluster_config.xml7m7t4rvb~'

  
  An unexpected error occurred!

  For details, see /tmp/apparmor-bugreport-oe_mo879.txt
  Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
  and attach this file.
  
++

  Secondly, once I accept this denial, AppArmor repeatedly gives similar
  denials for 

[Touch-packages] [Bug 1865450] [NEW] PermissionError for AppArmor Profiles i.e., SSH

[Shaheena Kazi]

Public bug reported:

I have created an AppArmor profile for SSH.
The profile is created successfully but each time I run aa-logprof it gives 
PermissionError: [Errno 13] 


An example of the error: 
Traceback (most recent call last):
  File "/usr/sbin/aa-enforce", line 35, in module>
tool.cmd_enforce()
  File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 150, in 
cmd_enforce
apparmor.set_enforce(profile, program)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 293, in set_enforce
change_profile_flags(filename, program, 'complain', False)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 704, in 
change_profile_flags
set_profile_flags(filename, program, newflags)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 753, in 
set_profile_flags
os.rename(temp_file.name, prof_filename)
PermissionError: [Errno 13] Permission denied: 
'/etc/apparmor.d/usr.sbin.tcpdumpwvx1h0xl~' -> 
'/etc/apparmor.d/usr.sbin.tcpdump'

Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
and attach this file.

+++
Traceback (most recent call last):
  File "/usr/sbin/aa-logprof", line 50, in 
apparmor.do_logprof_pass(logmark)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 1824, in 
do_logprof_pass
save_profiles()
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 1921, in 
save_profiles
write_profile_ui_feedback(profile_name)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3404, in 
write_profile_ui_feedback
write_profile(profile)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3413, in 
write_profile
newprof = tempfile.NamedTemporaryFile('w', suffix='~', delete=False, 
dir=profile_dir)
  File "/usr/lib/python3.5/tempfile.py", line 688, in NamedTemporaryFile
(fd, name) = _mkstemp_inner(dir, prefix, suffix, flags, output_type)
  File "/usr/lib/python3.5/tempfile.py", line 399, in _mkstemp_inner
fd = _os.open(file, flags, 0o600)
PermissionError: [Errno 13] Permission denied: '/etc/apparmor.d/tmpujtge2jq~'


An unexpected error occurred!

For details, see /tmp/apparmor-bug report-5qnjyx3t.txt
Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
and attach this file.
+++

+++
root@protegrity-framework314:/var/www# aa-complain /etc/apparmor.d/*
Profile for /etc/apparmor.d/abstractions not found, skipping
Profile for /etc/apparmor.d/apache2.d not found, skipping
Setting /etc/apparmor.d/bin.ping to complain mode.
Profile for /etc/apparmor.d/cache not found, skipping
Profile for /etc/apparmor.d/disable not found, skipping
Setting /etc/apparmor.d/etc.opt.Cluster.cluster_config.status.xml to complain 
mode.
Setting /etc/apparmor.d/etc.opt.Cluster.cluster_config.xml to complain mode.
Traceback (most recent call last):
  File "/usr/sbin/aa-complain", line 35, in 
tool.cmd_complain()
  File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 165, in 
cmd_complain
apparmor.set_complain(profile, program)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 286, in 
set_complain
change_profile_flags(filename, program, 'complain', True)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 704, in 
change_profile_flags
set_profile_flags(filename, program, newflags)
  File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 720, in 
set_profile_flags
temp_file = tempfile.NamedTemporaryFile('w', prefix=prof_filename, 
suffix='~', delete=False, dir=profile_dir)
  File "/usr/lib/python3.5/tempfile.py", line 688, in NamedTemporaryFile
(fd, name) = _mkstemp_inner(dir, prefix, suffix, flags, output_type)
  File "/usr/lib/python3.5/tempfile.py", line 399, in _mkstemp_inner
fd = _os.open(file, flags, 0o600)
PermissionError: [Errno 13] Permission denied: 
'/etc/apparmor.d/etc.opt.Cluster.cluster_config.xml7m7t4rvb~'


An unexpected error occurred!

For details, see /tmp/apparmor-bugreport-oe_mo879.txt
Please consider reporting a bug at https://bugs.launchpad.net/apparmor/
and attach this file.
++

Secondly, once I accept this denial, AppArmor repeatedly gives similar
denials for almost every profile.

I am using a security product and running it on Debian 9.
root@protegrity:/var/www# cat /etc/debian_version
9.9

I expect that these denials should not occur repeatedly.

Please do check.

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

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

Title:
  PermissionError for 

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

[Daniel van Vugt]

When the freeze happens can you still move the mouse cursor? If so then
it would be gnome-shell and not Xorg.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (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/1865410

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  My Nvidia GPU is set to on-demand mode, so it uses the integrated
  intel iGPU for most of the every day tasks.

  This hang seems to happen when watching media (1080p @ 11605 kbps in
  H.264 in MKV container with EAC3 5.1 sound) and then switching to a
  resource intensive tab, which loads up lot's of media (ex: Reddit)

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18
  Uname: Linux 5.3.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.59  Thu Jan 30 01:00:41 
UTC 2020
   GCC version:  gcc version 9.2.1 20200224 (Ubuntu 9.2.1-30ubuntu1)
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  1 22:48:00 2020
  DistUpgraded: 2020-02-27 20:01:03,129 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 440.59, 5.3.0-40-generic, x86_64: installed
   nvidia, 440.59, 5.4.0-14-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 630 (Mobile) [17aa:229f]
   NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev 
a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f]
  InstallationDate: Installed on 2020-01-22 (39 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20QVCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic 
root=UUID=126cdadc-728b-44e1-9491-cb5cba23fd10 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to focal on 2020-02-28 (3 days ago)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2OET41W (1.28 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QVCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2OET41W(1.28):bd11/25/2019:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QVCTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme 2nd
  dmi.product.name: 20QVCTO1WW
  dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
  dmi.product.version: ThinkPad X1 Extreme 2nd
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1854237] Re: autopkgtests fail after security fixes

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.11-0ubuntu8.5

---
apport (2.20.11-0ubuntu8.5) eoan; urgency=medium

  * data/whoopsie-upload-all: append to the crash report using fdopen and open
from os to cope with protected_regular being set to 1. (LP: #1848064)

  [ Michael Hudson-Doyle ]
  * Fix autopkgtest failures since recent security update: (LP: #1854237)
- Fix regression in creating report for crashing setuid process by getting
  kernel to tell us the executable path rather than reading
  /proc/[pid]/exe.
- Fix deletion of partially written core files.
- Fix test_get_logind_session to use new API.
- Restore add_proc_info raising ValueError for a dead process.
- Delete test_lock_symlink, no longer applicable now that the lock is
  created in a directory only root can write to.

 -- Brian Murray   Mon, 24 Feb 2020 09:38:55 -0800

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

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

Title:
  autopkgtests fail after security fixes

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  New
Status in apport source package in Bionic:
  New
Status in apport source package in Disco:
  New
Status in apport source package in Eoan:
  Fix Released

Bug description:
  The following autopkgtests fail after the recent security fixes:

  log:FAIL: test_get_logind_session (__main__.T)
  log:FAIL: test_core_dump_packaged (__main__.T)
  log:FAIL: test_core_dump_unpackaged (__main__.T)
  log:FAIL: test_crash_setuid_drop (__main__.T)
  log:FAIL: test_crash_setuid_keep (__main__.T)
  log:FAIL: test_crash_setuid_nonwritable_cwd (__main__.T)
  log:FAIL: test_lock_symlink (__main__.T)

  test_get_logind_session is a test failing to keep up with an API
  change. test_core_dump_* is failures to remove partly written core
  files. Both of these are easy fixes, I'll have a MP for them soon.

  test_crash_setuid_* are caused by the dropping of privileges when
  accessing the crashing process's /proc. They seem to be testing
  behaviour now explicitly forbidden by the fix to be honest!

  test_lock_symlink fails because the lock file is now always in
  /var/lock/apport/ and not in $APPORT_REPORT_DIR. I guess we could
  update the test, but is it really worth it after the fix?

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

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

[Touch-packages] [Bug 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.11-0ubuntu8.5

---
apport (2.20.11-0ubuntu8.5) eoan; urgency=medium

  * data/whoopsie-upload-all: append to the crash report using fdopen and open
from os to cope with protected_regular being set to 1. (LP: #1848064)

  [ Michael Hudson-Doyle ]
  * Fix autopkgtest failures since recent security update: (LP: #1854237)
- Fix regression in creating report for crashing setuid process by getting
  kernel to tell us the executable path rather than reading
  /proc/[pid]/exe.
- Fix deletion of partially written core files.
- Fix test_get_logind_session to use new API.
- Restore add_proc_info raising ValueError for a dead process.
- Delete test_lock_symlink, no longer applicable now that the lock is
  created in a directory only root can write to.

 -- Brian Murray   Mon, 24 Feb 2020 09:38:55 -0800

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

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:PermissionError:/usr/share/apport/whoopsie-upload-
  all@168:collect_info:process_report

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  whoopsie-upload-all is not collecting data for existing crash reports which 
are not owned by root if /proc/sys/fs/protected_regular is set to 1. 
Subsequently, the crash reports are incomplete and not getting uploaded to the 
Error Tracker therefore Ubuntu developers may be missing out on important crash 
reports.

  [Test Case]
  1) Confirm /proc/sys/fs/protected_regular is set to 1.
  2) Run an application as your user and cause it to crash. (kill -11 $APP)
  3) Confirm there is a crash report in /var/crash
  4) Run 'sudo /usr/share/apport/whoopsie-upload-all'
  5) Observe the Traceback in this bug report is produced by 
whoopsie-upload-all.

  With the version of apport from -proposed the Traceback will not occur
  and a .uploaded file will be created for the corresponding .crash
  file.

  [Regression Potential]
  Not all systems may have /proc/sys/fs/protected_regular set to 1, so we 
should also test the case where /proc/sys/fs/protected_regular is set to 0. 
This can be done by manually changing the value and running through the test 
case above and confirming that a .uploaded file is created for the .crash file.

  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu8, the problem page at 
https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae 
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/apport/+bug/1848064/+subscriptions

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

[Touch-packages] [Bug 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report

[Łukasz Zemczak]

Ok, the verification looks good. As per request I will be releasing this
slightly earlier - I think 5+ days is enough of a wait anyway.

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:PermissionError:/usr/share/apport/whoopsie-upload-
  all@168:collect_info:process_report

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  whoopsie-upload-all is not collecting data for existing crash reports which 
are not owned by root if /proc/sys/fs/protected_regular is set to 1. 
Subsequently, the crash reports are incomplete and not getting uploaded to the 
Error Tracker therefore Ubuntu developers may be missing out on important crash 
reports.

  [Test Case]
  1) Confirm /proc/sys/fs/protected_regular is set to 1.
  2) Run an application as your user and cause it to crash. (kill -11 $APP)
  3) Confirm there is a crash report in /var/crash
  4) Run 'sudo /usr/share/apport/whoopsie-upload-all'
  5) Observe the Traceback in this bug report is produced by 
whoopsie-upload-all.

  With the version of apport from -proposed the Traceback will not occur
  and a .uploaded file will be created for the corresponding .crash
  file.

  [Regression Potential]
  Not all systems may have /proc/sys/fs/protected_regular set to 1, so we 
should also test the case where /proc/sys/fs/protected_regular is set to 0. 
This can be done by manually changing the value and running through the test 
case above and confirming that a .uploaded file is created for the .crash file.

  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu8, the problem page at 
https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae 
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/apport/+bug/1848064/+subscriptions

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

[Touch-packages] [Bug 1848064] Update Released

[Łukasz Zemczak]

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

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:PermissionError:/usr/share/apport/whoopsie-upload-
  all@168:collect_info:process_report

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  whoopsie-upload-all is not collecting data for existing crash reports which 
are not owned by root if /proc/sys/fs/protected_regular is set to 1. 
Subsequently, the crash reports are incomplete and not getting uploaded to the 
Error Tracker therefore Ubuntu developers may be missing out on important crash 
reports.

  [Test Case]
  1) Confirm /proc/sys/fs/protected_regular is set to 1.
  2) Run an application as your user and cause it to crash. (kill -11 $APP)
  3) Confirm there is a crash report in /var/crash
  4) Run 'sudo /usr/share/apport/whoopsie-upload-all'
  5) Observe the Traceback in this bug report is produced by 
whoopsie-upload-all.

  With the version of apport from -proposed the Traceback will not occur
  and a .uploaded file will be created for the corresponding .crash
  file.

  [Regression Potential]
  Not all systems may have /proc/sys/fs/protected_regular set to 1, so we 
should also test the case where /proc/sys/fs/protected_regular is set to 0. 
This can be done by manually changing the value and running through the test 
case above and confirming that a .uploaded file is created for the .crash file.

  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu8, the problem page at 
https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae 
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/apport/+bug/1848064/+subscriptions

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

[Touch-packages] [Bug 1776622] Re: snapd updates on focal never finish installing. Can't install any other updates.

[Daniel van Vugt]

Further to comment #38, here's a workaround that works for me on 20.04:

sudo killall apt
sudo rm /var/lib/dpkg/lock
sudo dpkg -r snapd gnome-software-plugin-snap
sudo apt update
sudo apt full-upgrade

** Changed in: snapd
   Status: Expired => Confirmed

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

Title:
  snapd updates on focal never finish installing. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1776622] Re: snapd updates on cosmic never finish installing. Can't install any other updates.

[Daniel van Vugt]

Confirmed on 20.04 today.

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

** Summary changed:

- snapd updates on cosmic never finish installing. Can't install any other 
updates.
+ snapd updates on focal never finish installing. Can't install any other 
updates.

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

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

** Tags added: champagne focal

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

Title:
  snapd updates on focal never finish installing. Can't install any
  other updates.

Status in snapd:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  snapd (2.33+18.10ubuntu3) cosmic never finishes installing. Can't
  install any other updates.

  The first time I gave up waiting and killed it. Then...

  $ sudo apt full-upgrade
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  $ sudo dpkg --configure -a
  Setting up snapd (2.33+18.10ubuntu3) ...
  snapd.snap-repair.service is a disabled or a static unit, not starting it.

  << never ends >>

  All the while the snap and snapd process use about 0.3% CPU (which is
  more than usual).

  WORKAROUND:

  sudo killall apt dpkg
  sudo dpkg -r snapd gnome-software-plugin-snap
  sudo apt update
  sudo apt full-upgrade

  ---

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: snapd 2.33+18.10ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  Date: Wed Jun 13 16:49:20 2018
  InstallationDate: Installed on 2018-05-26 (17 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report

[Brian Murray]

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

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:PermissionError:/usr/share/apport/whoopsie-upload-
  all@168:collect_info:process_report

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  whoopsie-upload-all is not collecting data for existing crash reports which 
are not owned by root if /proc/sys/fs/protected_regular is set to 1. 
Subsequently, the crash reports are incomplete and not getting uploaded to the 
Error Tracker therefore Ubuntu developers may be missing out on important crash 
reports.

  [Test Case]
  1) Confirm /proc/sys/fs/protected_regular is set to 1.
  2) Run an application as your user and cause it to crash. (kill -11 $APP)
  3) Confirm there is a crash report in /var/crash
  4) Run 'sudo /usr/share/apport/whoopsie-upload-all'
  5) Observe the Traceback in this bug report is produced by 
whoopsie-upload-all.

  With the version of apport from -proposed the Traceback will not occur
  and a .uploaded file will be created for the corresponding .crash
  file.

  [Regression Potential]
  Not all systems may have /proc/sys/fs/protected_regular set to 1, so we 
should also test the case where /proc/sys/fs/protected_regular is set to 0. 
This can be done by manually changing the value and running through the test 
case above and confirming that a .uploaded file is created for the .crash file.

  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu8, the problem page at 
https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae 
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/apport/+bug/1848064/+subscriptions

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

[Touch-packages] [Bug 1854237] Update Released

[Łukasz Zemczak]

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

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

Title:
  autopkgtests fail after security fixes

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  New
Status in apport source package in Bionic:
  New
Status in apport source package in Disco:
  New
Status in apport source package in Eoan:
  Fix Committed

Bug description:
  The following autopkgtests fail after the recent security fixes:

  log:FAIL: test_get_logind_session (__main__.T)
  log:FAIL: test_core_dump_packaged (__main__.T)
  log:FAIL: test_core_dump_unpackaged (__main__.T)
  log:FAIL: test_crash_setuid_drop (__main__.T)
  log:FAIL: test_crash_setuid_keep (__main__.T)
  log:FAIL: test_crash_setuid_nonwritable_cwd (__main__.T)
  log:FAIL: test_lock_symlink (__main__.T)

  test_get_logind_session is a test failing to keep up with an API
  change. test_core_dump_* is failures to remove partly written core
  files. Both of these are easy fixes, I'll have a MP for them soon.

  test_crash_setuid_* are caused by the dropping of privileges when
  accessing the crashing process's /proc. They seem to be testing
  behaviour now explicitly forbidden by the fix to be honest!

  test_lock_symlink fails because the lock file is now always in
  /var/lock/apport/ and not in $APPORT_REPORT_DIR. I guess we could
  update the test, but is it really worth it after the fix?

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

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

[Touch-packages] [Bug 1863724] Re: Add missing pci-id's for Comet Lake (CML)

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 19.2.8-0ubuntu0~19.10.3

---
mesa (19.2.8-0ubuntu0~19.10.3) eoan; urgency=medium

  * i965-sync-pciids.diff: Add back three pci-id's for CML that were
lost during a rebase. (LP: #1863724)

 -- Timo Aaltonen   Wed, 19 Feb 2020 07:09:44 +0200

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

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

Title:
  Add missing pci-id's for Comet Lake (CML)

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Bionic:
  Fix Committed
Status in mesa source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  After rebasing mesa to 19.2.x debian/patches/i965-sync-pciids.diff was
  updated but some parts of it got accidentally dropped, losing a couple
  of pci-id's for CML. They need to be restored.

  [Test case]

  Install the updates on an affected machine, check with glxinfo -B that
  the proper driver is loaded.

  [Regression potential]

  none, this just adds pci-id's

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

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

[Touch-packages] [Bug 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report

[Brian Murray]

bdmurray@clean-eoan-amd64:~$ apt-cache policy apport
apport:
  Installed: 2.20.11-0ubuntu8.5
  Candidate: 2.20.11-0ubuntu8.5
  Version table:
 *** 2.20.11-0ubuntu8.5 500
500 http://archive.ubuntu.com/ubuntu eoan-proposed/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu eoan-proposed/main i386 Packages
100 /var/lib/dpkg/status
bdmurray@clean-eoan-amd64:~$ sudo cat /proc/sys/fs/protected_regular
0
bdmurray@clean-eoan-amd64:~$ sudo /usr/share/apport/whoopsie-upload-all 
/var/crash/_usr_share_dput_execute-dput.1000.crash already marked for upload, 
skipping
Collecting info for /var/crash/_usr_bin_screen.1000.crash...
Marking /var/crash/_usr_bin_screen.1000.crash for whoopsie upload
All reports processed

With the version of apport in -proposed we can see that crash reporting
still works with /proc/sys/fs/protected_regular set to 0.

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:PermissionError:/usr/share/apport/whoopsie-upload-
  all@168:collect_info:process_report

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  whoopsie-upload-all is not collecting data for existing crash reports which 
are not owned by root if /proc/sys/fs/protected_regular is set to 1. 
Subsequently, the crash reports are incomplete and not getting uploaded to the 
Error Tracker therefore Ubuntu developers may be missing out on important crash 
reports.

  [Test Case]
  1) Confirm /proc/sys/fs/protected_regular is set to 1.
  2) Run an application as your user and cause it to crash. (kill -11 $APP)
  3) Confirm there is a crash report in /var/crash
  4) Run 'sudo /usr/share/apport/whoopsie-upload-all'
  5) Observe the Traceback in this bug report is produced by 
whoopsie-upload-all.

  With the version of apport from -proposed the Traceback will not occur
  and a .uploaded file will be created for the corresponding .crash
  file.

  [Regression Potential]
  Not all systems may have /proc/sys/fs/protected_regular set to 1, so we 
should also test the case where /proc/sys/fs/protected_regular is set to 0. 
This can be done by manually changing the value and running through the test 
case above and confirming that a .uploaded file is created for the .crash file.

  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu8, the problem page at 
https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae 
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/apport/+bug/1848064/+subscriptions

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

[Touch-packages] [Bug 1848064] Re: /usr/share/apport/whoopsie-upload-all:PermissionError:/usr/share/apport/whoopsie-upload-all@168:collect_info:process_report

[Brian Murray]

We can also see that crash reporting works with
/proc/sys/fs/protected_regular set to 1.

bdmurray@clean-eoan-amd64:~$ sudo cat /proc/sys/fs/protected_regular
1
bdmurray@clean-eoan-amd64:~$ sudo /usr/share/apport/whoopsie-upload-all 
Collecting info for /var/crash/_usr_share_dput_execute-dput.1000.crash...
Marking /var/crash/_usr_share_dput_execute-dput.1000.crash for whoopsie upload
All reports processed
bdmurray@clean-eoan-amd64:~$ apt-cache policy apport
apport:
  Installed: 2.20.11-0ubuntu8.5
  Candidate: 2.20.11-0ubuntu8.5
  Version table:
 *** 2.20.11-0ubuntu8.5 500
500 http://archive.ubuntu.com/ubuntu eoan-proposed/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu eoan-proposed/main i386 Packages

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:PermissionError:/usr/share/apport/whoopsie-upload-
  all@168:collect_info:process_report

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Eoan:
  Fix Committed

Bug description:
  [Impact]
  whoopsie-upload-all is not collecting data for existing crash reports which 
are not owned by root if /proc/sys/fs/protected_regular is set to 1. 
Subsequently, the crash reports are incomplete and not getting uploaded to the 
Error Tracker therefore Ubuntu developers may be missing out on important crash 
reports.

  [Test Case]
  1) Confirm /proc/sys/fs/protected_regular is set to 1.
  2) Run an application as your user and cause it to crash. (kill -11 $APP)
  3) Confirm there is a crash report in /var/crash
  4) Run 'sudo /usr/share/apport/whoopsie-upload-all'
  5) Observe the Traceback in this bug report is produced by 
whoopsie-upload-all.

  With the version of apport from -proposed the Traceback will not occur
  and a .uploaded file will be created for the corresponding .crash
  file.

  [Regression Potential]
  Not all systems may have /proc/sys/fs/protected_regular set to 1, so we 
should also test the case where /proc/sys/fs/protected_regular is set to 0. 
This can be done by manually changing the value and running through the test 
case above and confirming that a .uploaded file is created for the .crash file.

  Original Description
  
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu8, the problem page at 
https://errors.ubuntu.com/problem/d9f09f3b3e7aa8ab77434ef30f33416a856971ae 
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/apport/+bug/1848064/+subscriptions

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

[Touch-packages] [Bug 1863724] Update Released

[Łukasz Zemczak]

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

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

Title:
  Add missing pci-id's for Comet Lake (CML)

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Bionic:
  Fix Committed
Status in mesa source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  After rebasing mesa to 19.2.x debian/patches/i965-sync-pciids.diff was
  updated but some parts of it got accidentally dropped, losing a couple
  of pci-id's for CML. They need to be restored.

  [Test case]

  Install the updates on an affected machine, check with glxinfo -B that
  the proper driver is loaded.

  [Regression potential]

  none, this just adds pci-id's

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

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

[Touch-packages] [Bug 1854237] Re: autopkgtests fail after security fixes

[Brian Murray]

The amd64 autopkgtests are now passing so I'm setting this to
verification-done.

http://autopkgtest.ubuntu.com/packages/a/apport/eoan/amd64

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

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

Title:
  autopkgtests fail after security fixes

Status in Apport:
  New
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  New
Status in apport source package in Bionic:
  New
Status in apport source package in Disco:
  New
Status in apport source package in Eoan:
  Fix Committed

Bug description:
  The following autopkgtests fail after the recent security fixes:

  log:FAIL: test_get_logind_session (__main__.T)
  log:FAIL: test_core_dump_packaged (__main__.T)
  log:FAIL: test_core_dump_unpackaged (__main__.T)
  log:FAIL: test_crash_setuid_drop (__main__.T)
  log:FAIL: test_crash_setuid_keep (__main__.T)
  log:FAIL: test_crash_setuid_nonwritable_cwd (__main__.T)
  log:FAIL: test_lock_symlink (__main__.T)

  test_get_logind_session is a test failing to keep up with an API
  change. test_core_dump_* is failures to remove partly written core
  files. Both of these are easy fixes, I'll have a MP for them soon.

  test_crash_setuid_* are caused by the dropping of privileges when
  accessing the crashing process's /proc. They seem to be testing
  behaviour now explicitly forbidden by the fix to be honest!

  test_lock_symlink fails because the lock file is now always in
  /var/lock/apport/ and not in $APPORT_REPORT_DIR. I guess we could
  update the test, but is it really worth it after the fix?

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

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