[Touch-packages] [Bug 1928080] Re: Noto Sans Hebrew is not set as the fallback font of Noto Sans

[Omer I.S.]

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

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

Title:
  Noto Sans Hebrew is not set as the fallback font of Noto Sans

Status in fontconfig package in Ubuntu:
  New

Bug description:
  [This is a minor issue]

  Hello, Noto Sans Hebrew is not set as the fallback font of Noto Sans in 
Kubuntu, and the current fallback font of Noto Sans is Liberation Sans, and not 
Noto Sans Hebrew.
  May you fix it, please?

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


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

[Touch-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915

[ChrisC]

I just tagged the bug as affecting : initramfs-tools

As I found this bug when doing: 
$ sudo update-initramfs -u
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

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

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

Title:
  Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it
  loads i915

Status in initramfs-tools package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Dear all,

  I can see that the linux-firmware is missing firmware files, in Ubuntu
  20.04.1 LTS, for initramfs, when it loads i915.

  Package: linux-firmware 1.187.15
  It contains the following files, for the module i915:
  i915/tgl_dmc_ver2_04.bin  2019-09-13  installed
  i915/tgl_dmc_ver2_06.bin  2020-03-04  installed
  i915/tgl_dmc_ver2_08.bin  2020-08-13  installed
  i915/tgl_guc_35.2.0.bin   2019-11-06  installed
  i915/tgl_huc_7.0.12.bin   2020-03-04  installed
  i915/tgl_huc_7.0.3.bin2019-11-06  installed

  Package: linux-firmware
  MUST at least contain the following files, for the module i915:
  i915/tgl_huc_7.5.0.bin2020-08-13  i915: Add HuC 
firwmare v7.5.0 for TGL
  as the module asks for it, during 'update-initramfs', to avoid:
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  But it COULD also contain : 
  i915/tgl_dmc_ver2_12.bin  2021-07-28  i915: Add v2.12 DMC for TGL
  i915/tgl_guc_49.0.1.bin   2020-11-24  i915: Add GuC firmware 
v49.0.1 for all platforms
  i915/tgl_guc_62.0.0.bin   2021-06-29  firmware/i915/guc: Add 
GuC v62.0.0 for all platforms
  i915/tgl_huc_7.9.3.bin2021-06-29  firmware/i915/guc: Add 
HuC v7.9.3 for TGL & DG1

  Source: 
  $ modprobe --show-depends --ignore-install i915
  ...
  insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko 

  $ modinfo -F firmware 
/lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko
  ...
  i915/tgl_dmc_ver2_08.bin
  i915/tgl_guc_35.2.0.bin
  i915/tgl_huc_7.5.0.bin

  Actual result:
  $ sudo update-initramfs -u
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  
  Expected result:
  No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915

  
  Info : INTEL Repository of firmware:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.15
  ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46
  Uname: Linux 5.10.0-1038-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  1699 F pulseaudio
   /dev/snd/pcmC0D0p:   chris  1699 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Aug 15 14:46:47 2021
  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-bulbasaur+X54
  InstallationDate: Installed on 2021-08-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem 
root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1038-oem N/A
   linux-backports-modules-5.10.0-1038-oem  N/A
   linux-firmware   1.187.15
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2021
  dmi.bios.release: 3.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.0.4
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.0.4:bd07/16/2021:br3.0:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 1939973] Re: make 4.3-4.1 triggers build failures

[Matthias Klose]

copied the binary packages to
https://launchpad.net/~doko/+archive/ubuntu/toolchain

and removed them from impish-proposed

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

Title:
  make 4.3-4.1 triggers build failures

Status in make-dfsg package in Ubuntu:
  Confirmed

Bug description:
  trying to rebuild cross-toolchain-base from
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile/+packages

  triggers a build failure:

  [...]
  START stamp-dir/init-binutils
  tar -x -f  /usr/src/binutils/binutils-2.37.tar.xz
  set -e; cd binutils-2.37 ; cp -a /usr/src/binutils/debian/ . ; if [ -n 
"$(grep -v '^\#' /<>/debian/patches/binutils/series)" ]; then 
QUILT_PATCHES=/<>/debian/patches/binutils quilt --quiltrc 
/dev/null  push -a; fi; rm -rf .pc
  cd binutils-2.37 ; env -i CROSS_ARCHS="amd64 i386 s390x ppc64el arm64 armhf 
armel  powerpc" debian/rules stamps/control
  make: dpkg-architecture: No such file or directory
  make: lsb_release: No such file or directory
  make: lsb_release: No such file or directory
  make: pwd: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  debian/rules:163: *** unexpected source package name: .  Stop.
  make: *** [debian/rules:215: stamp-dir/init-binutils] Error 2
  dpkg-buildpackage.pl: error: debian/rules build subprocess returned exit 
status 2

  
  working around by omitting the -i option to env, or by setting PATH 
explicitly. Reverting to the version in the release pocket lets the c-t-b- 
build succeed.

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


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

[Touch-packages] [Bug 1901316] Re: [Z370 AORUS Gaming 7, Realtek ALC1220, Green Line Out, Rear] Playback problem. Center and subwoofer work, everything else has no sound.

[Terry]

Hello

I've upgrade to Ubuntu 21.04, the the issue still exists.
Kernel version: Linux 5.11.0-25-generic #27-Ubuntu SMP Fri Jul 9 23:06:29 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  [Z370 AORUS Gaming 7, Realtek ALC1220, Green Line Out, Rear] Playback
  problem.  Center and subwoofer work, everything else has no sound.

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  When using the Ubuntu sound settings and doing a test, only the center
  and subwoofer channels produce sound.  When playing any media that
  relies on left/right channels, I don't hear anything.

  Used alsamixer to unmute / increase volume to all desired channels with no 
change
  Used PulseAudio volume control to load multiple different audio profiles with 
the same results.

  Ubuntu Release: 
  Description:  Ubuntu 20.10
  Release:  20.10

  alsa-base:
Installed: 1.0.25+dfsg-0ubuntu5
Candidate: 1.0.25+dfsg-0ubuntu5
Version table:
   *** 1.0.25+dfsg-0ubuntu5 500
  500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  100 /var/lib/dpkg/status

  pulseaudio:
Installed: 1:13.99.2-1ubuntu1
Candidate: 1:13.99.2-1ubuntu1
Version table:
   *** 1:13.99.2-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  I also experienced the issue in the latest default kernel for Ubuntu,
  so I downloaded one of the later stable ones:

  Linux terry-pc 5.9.1-050901-generic #202010170731 SMP Sat Oct 17
  07:42:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

  When doing a speaker test, I get the following results:

  speaker-test -c6

  speaker-test 1.2.3

  Playback device is default
  Stream parameters are 48000Hz, S16_LE, 6 channels
  Using 16 octaves of pink noise
  Rate set to 48000Hz (requested 48000Hz)
  Buffer size range from 32 to 349525
  Period size range from 10 to 116509
  Using max buffer size 349524
  Periods = 4
  was set period_size = 87381
  was set buffer_size = 349524
   0 - Front Left -- NO SOUND
   4 - Center -- WORKS CORRECTLY
   1 - Front Right -- NO SOUND
   3 - Rear Right -- NO SOUND
   2 - Rear Left -- NO SOUND
   5 - LFE -- WORKS CORRECTLY

  I plugged headphones into the front jack, and the system detected and
  switched the sound output device to the headphones.  However, I still
  did not hear any sound when doing a test.

  Lastly, this sound device works as expected under Windows 10, so I
  don't believe that it is a hardware issue.

  Thank you for your time.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 5.9.1-050901-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 24 09:12:25 2020
  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_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Only some of outputs are working
  Title: [Z370 AORUS Gaming 7, Realtek ALC1220, Green Line Out, Rear] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/28/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F15a
  dmi.board.asset.tag: Default string
  dmi.board.name: Z370 AORUS Gaming 7
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF15a:bd11/28/2019:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnZ370AORUSGaming7:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ370AORUSGaming7:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z370 AORUS Gaming 7
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.modprobe.d.alsa-base.conf: [deleted]

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


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

[Touch-packages] [Bug 1939989] Re: Module i915 is not updated, in Ubuntu 20.04 LTS

[ChrisC]

I just tagged the bug as affecting : initramfs-tools

As I found this bug when doing: 
$ sudo update-initramfs -u
W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

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

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

Title:
  Module i915 is not updated, in Ubuntu 20.04 LTS

Status in initramfs-tools package in Ubuntu:
  New
Status in linux-oem-5.10 package in Ubuntu:
  New

Bug description:
  Dear all,

  Module i915.ko is asking for the firmware file:
  i915/tgl_huc_7.5.0.bin
  Date: 2020-08-13
  Description: i915: Add HuC firwmare v7.5.0 for TGL

  But the module i915 should also ask for :
  i915/tgl_huc_7.9.3.bin
  Date: 2021-06-29
  Description: firmware/i915/guc: Add HuC v7.9.3 for TGL & DG1

  i915/tgl_dmc_ver2_12.bin
  Date: 2021-07-28
  Description: i915: Add v2.12 DMC for TGL

  i915/tgl_guc_62.0.0.bin
  Date: 2021-06-29
  Description: firmware/i915/guc: Add GuC v62.0.0 for all platforms

  or at least (this 8 month old firmware):
  i915/tgl_guc_49.0.1.bin
  Date: 2020-11-24
  Description: i915: Add GuC firmware v49.0.1 for all platforms

  This requirement will fix some bugs and improve stability on our hardware 
using Ubuntu 20.04.1 LTS.
  FYI: I cannot appreciate myself, if this is a security vulnerability or not.

  Cheers

  
  Command lines, of the actual result:
  $ modprobe --show-depends --ignore-install i915
  ...
  insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko 

  $ modinfo -F firmware 
/lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko
  ...
  i915/tgl_dmc_ver2_08.bin
  i915/tgl_guc_35.2.0.bin
  i915/tgl_huc_7.5.0.bin


  Package: linux-modules-5.10.0-1038-oem:
    Installed: 5.10.0-1038.40
    Candidate: 5.10.0-1038.40

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-modules-5.10.0-1038-oem 5.10.0-1038.40
  ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46
  Uname: Linux 5.10.0-1038-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Aug 15 15:09:44 2021
  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-bulbasaur+X54
  InstallationDate: Installed on 2021-08-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  SourcePackage: linux-oem-5.10
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915

[ChrisC]

Updating lib/firmware with the ones over
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/tree/i915 makes all the warning go away.

As per Bug 1847786: 
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847786

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

Title:
  Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it
  loads i915

Status in initramfs-tools package in Ubuntu:
  New
Status in linux-firmware package in Ubuntu:
  New

Bug description:
  Dear all,

  I can see that the linux-firmware is missing firmware files, in Ubuntu
  20.04.1 LTS, for initramfs, when it loads i915.

  Package: linux-firmware 1.187.15
  It contains the following files, for the module i915:
  i915/tgl_dmc_ver2_04.bin  2019-09-13  installed
  i915/tgl_dmc_ver2_06.bin  2020-03-04  installed
  i915/tgl_dmc_ver2_08.bin  2020-08-13  installed
  i915/tgl_guc_35.2.0.bin   2019-11-06  installed
  i915/tgl_huc_7.0.12.bin   2020-03-04  installed
  i915/tgl_huc_7.0.3.bin2019-11-06  installed

  Package: linux-firmware
  MUST at least contain the following files, for the module i915:
  i915/tgl_huc_7.5.0.bin2020-08-13  i915: Add HuC 
firwmare v7.5.0 for TGL
  as the module asks for it, during 'update-initramfs', to avoid:
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  But it COULD also contain : 
  i915/tgl_dmc_ver2_12.bin  2021-07-28  i915: Add v2.12 DMC for TGL
  i915/tgl_guc_49.0.1.bin   2020-11-24  i915: Add GuC firmware 
v49.0.1 for all platforms
  i915/tgl_guc_62.0.0.bin   2021-06-29  firmware/i915/guc: Add 
GuC v62.0.0 for all platforms
  i915/tgl_huc_7.9.3.bin2021-06-29  firmware/i915/guc: Add 
HuC v7.9.3 for TGL & DG1

  Source: 
  $ modprobe --show-depends --ignore-install i915
  ...
  insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko 

  $ modinfo -F firmware 
/lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko
  ...
  i915/tgl_dmc_ver2_08.bin
  i915/tgl_guc_35.2.0.bin
  i915/tgl_huc_7.5.0.bin

  Actual result:
  $ sudo update-initramfs -u
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  
  Expected result:
  No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915

  
  Info : INTEL Repository of firmware:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.15
  ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46
  Uname: Linux 5.10.0-1038-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  1699 F pulseaudio
   /dev/snd/pcmC0D0p:   chris  1699 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Aug 15 14:46:47 2021
  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-bulbasaur+X54
  InstallationDate: Installed on 2021-08-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem 
root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1038-oem N/A
   linux-backports-modules-5.10.0-1038-oem  N/A
   linux-firmware   1.187.15
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2021
  dmi.bios.release: 3.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.0.4
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.0.4:bd07/16/2021:br3.0:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

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


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

[Touch-packages] [Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

[Theodore Ts'o]

It doesn't matter whether you store your personal data on the partition
where the OS is located, or elsewhere.   Either way, you may need to
know how to run e2fsck on the file system if you want to try to
maximally recover data.   If you don't know what you are doing, sure, go
ahead and run fsck -y.   But there is the chance you may lose data that
you might have been able to recover if you had more skills.

Note that in the case that you referenced, the kernel had already
detected some kind of file system inconsistency.   That is the source of
the "/dev/sda1 contains a file system with errors, checked force".
This should not happen, unless there is some kind of hardware bug, or
kernel bug which has led to the file system getting corrupted.   This
could be caused by flaky/low-quality/failing memory, or flaky/low-
quality/failing HDD or SSD.   An expert would have to look at the kernel
logs for hints to see what might have gone wrong.

If the user has regularly been doing backups, then sure, maybe you don't
care they can just run "fsck -y".But I don't want to give that
advice, only to hear that some graduate student had ten years worth of
thesis research, and it wasn't backed up, and they were using the lowest
possible cost HDD or SSD that was not reliably storing their data.
Sometimes, the best thing to do for low-comptency users, is for them to
ask for help, maybe at a local Linux User's Group, so that an expert can
try help them out.There is no magic incantation, no kind of "Hocus
Pocus" magic set of instructions that will always do the right thing.
And to give "low competency users" instructions which might not be the
best thing is ultimately, IMHO, going to doing them a grave disservice.

P.S.  One could argue that a graduate student who has ten years of
research on cheap sh*t storage and who hasn't been doing their backups
doesn't deserve to graduate with a Ph.D.   But that's not a very
charitable attitude

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

Title:
  UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Hello
  This problem did not occur on my computer.

  https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png

  It occurs in users who are not competent.
  This week, the French forum collapsed over this incident.

  I think changing the advice phrase might improve understanding of the
  action to be taken.

  Can these lines
  "   ( i.e.. without -a or -p options) 
  fsck existed with status code 4
  The root file system on /dev/ requires a manual fsck"
  become
  "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root 
file system."

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-terminal 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 15:16:28 2021
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2020-08-02 (370 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago)

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


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

[Touch-packages] [Bug 1870829] Re: AptX and AptX HD unavailable as Bluetooth audio quality options

[Nobuto Murata]

>From a duplicate of this bug, as tldr:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1939933
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597
> > > Does that mean that enabling it, would only add some dependencies but
> > > not actually do anything?
> >
> > Yes, a (soft) dependency should probably be added against
> > gstreamer1.0-plugins-bad, but as I said, the needed version (>= 1.19) is
> > not yet in debian
> 
> https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/commit/b916522382aaa33f216636a292e97cd769ac4093
> > 1.19.1

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

Title:
  AptX and AptX HD unavailable as Bluetooth audio quality options

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Unknown

Bug description:
  Current situation:

  When one connects a Bluetooth audio device, at best one can choose
  between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback
  (A2DP Sink)". That is sad when the audio device supports AptX or AptX
  HD.

  
  Expected situation:

  One can select AptX or AptX HD as the Bluetooth audio output profile.

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


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

[Touch-packages] [Bug 1940008] [NEW] systemd lsb-base integration script leaking shell variable changes which can break consumers

[Ryan]

Public bug reported:

I am using systemd version 248.3-1ubuntu3 from the impish repository.

It was compiled and built in the following manner:
# add impish deb-src repository to apt sources
apt build-dep systemd/impish
apt source -b systemd/impish

Once built, it was installed over the top of systemd 245.4-4ubuntu3.

I am running ubuntu 20.04.2.

The source tarball of systemd includes a file
(./debian/systemd/lib/lsb/init-functions.d/40-systemd) which is intended
to be installed into the drop-in script directory provided by the lsb-
base package (/lib/lsb/init-functions.d).

The problem that I am having is that this file (which is sourced by any
script which sources /lib/lsb/init-functions) is setting variables, and
in doing so, accidentally overwriting variables which are configured by
the calling script.

https://gist.github.com/TheWug/e120145f08e994d89e235e077a82ea75#file-40-systemd-L19

I noticed this when investigating why ipmiutil_wdt.service (provided by
package ipmiutil) was failing to start. The problem is that the
ipmiutil_wdt script, which makes use of init-functions, was statically
setting some variables for later use, including one called $prog. $prog
is then inadvertently overwritten by 40-systemd when ipmiutil_wdt
sources /lib/lsb/init-functions.

I think this is systemd's bug because systemd's lsb-base drop-in is not
being a "good neighbor" to the scripts with which it shares a
controlling shell. Even if ipmiutil were to rewrite its ipmiutil-wdt
script, any other such script provided by another package which tries to
use a variable called $prog (or $executable, or $argument, or $service,
or $state, or any of a handful of others) will find its feet being
stepped on by systemd's drop-in.

I propose that the drop-in be modified to encapsulate all of this
behavior where variables are assigned to within a function or subshell
or something, so they can't accidentally contaminate the outside world.

Other related package versions:
lsb-base: 11.1.0ubuntu2
ipmiutil: 3.1.5-1

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

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

Title:
  systemd lsb-base integration script leaking shell variable changes
  which can break consumers

Status in systemd package in Ubuntu:
  New

Bug description:
  I am using systemd version 248.3-1ubuntu3 from the impish repository.

  It was compiled and built in the following manner:
  # add impish deb-src repository to apt sources
  apt build-dep systemd/impish
  apt source -b systemd/impish

  Once built, it was installed over the top of systemd 245.4-4ubuntu3.

  I am running ubuntu 20.04.2.

  The source tarball of systemd includes a file
  (./debian/systemd/lib/lsb/init-functions.d/40-systemd) which is
  intended to be installed into the drop-in script directory provided by
  the lsb-base package (/lib/lsb/init-functions.d).

  The problem that I am having is that this file (which is sourced by
  any script which sources /lib/lsb/init-functions) is setting
  variables, and in doing so, accidentally overwriting variables which
  are configured by the calling script.

  
https://gist.github.com/TheWug/e120145f08e994d89e235e077a82ea75#file-40-systemd-L19

  I noticed this when investigating why ipmiutil_wdt.service (provided
  by package ipmiutil) was failing to start. The problem is that the
  ipmiutil_wdt script, which makes use of init-functions, was statically
  setting some variables for later use, including one called $prog.
  $prog is then inadvertently overwritten by 40-systemd when
  ipmiutil_wdt sources /lib/lsb/init-functions.

  I think this is systemd's bug because systemd's lsb-base drop-in is
  not being a "good neighbor" to the scripts with which it shares a
  controlling shell. Even if ipmiutil were to rewrite its ipmiutil-wdt
  script, any other such script provided by another package which tries
  to use a variable called $prog (or $executable, or $argument, or
  $service, or $state, or any of a handful of others) will find its feet
  being stepped on by systemd's drop-in.

  I propose that the drop-in be modified to encapsulate all of this
  behavior where variables are assigned to within a function or subshell
  or something, so they can't accidentally contaminate the outside
  world.

  Other related package versions:
  lsb-base: 11.1.0ubuntu2
  ipmiutil: 3.1.5-1

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


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

[Touch-packages] [Bug 1940014] [NEW] Several potential bugs of null pointer dereference in libx11-1.6.4

[yuxuan He]

Public bug reported:

Ubuntu version: 18.04
libx11-xcb-dev version:1.6.4
Hello,I found some potential bugs in package libx11,and the .docx file in the 
attachment I uploaded shows the occurrence process of the bug in a graphical 
way.Would you help me check whether the bugs mentioned below are true? I'm not 
100% sure that the bugs I submitted is correct. I hope you don't mind seeing 
the wrong bug I submitted.Thank you very much for your patience.

In file libx11-1.6.4/src/Xrm.c,defination of function XrmGetStringDatebase,line 
1559.
there is a statement call function NewDataBase(),load its return value to 
db,and this function may return a null pointer.in line 1560,there is a 
statement derefer db without check it.the process of this potential bug is 
shown in figure 1. There are several bugs caused by same reason such as in file 
Xrm.c,defination of function XrmPutStringResource,line 1532.In file Xrm.c 
,defination of function XrmCombineFileDatabase,line 1702.In file 
Xrm.c,defiantion of function XrmGetFileDatabase,line 1678.In file 
Xrm.c,defination of function XrmPutLineResource,line 1547.In file 
Xrms.c,defination of function XrmGetStringDatabase,line 1559.

In file libx11-1.6.4/src/Xrm.c,defination of function append_value_list,line 
489.
there is a statement call function Xmalloc to allocate memory,load its return 
value to value_list,but Xmalloc may fail to allocate memory,so value_list may 
be a null pointer.in line 490,there is a statement derefer value_list without 
check it.the process of this potential bug is shown in figure 2. 


In file libx11-1.6.4/modules/im/ximcp/imLcIm.c,defination of function 
_XimWriteCachedDefaultTree,line 464.
there is a statement call function Xmalloc to allocate memory,load its return 
value to m,but Xmalloc may fail to allocate memory,so m may be a null 
pointer.statements after derefer m without check it.the process of this 
potential bug is shown in figure 3. 

In file libx11-1.6.4/src/PolyReg.c,defination of function InsertEdgeInET,line 
98.
there is a statement call function Xmalloc to allocate memory,load its return 
value to tmpSLLBlock,but Xmalloc may fail to allocate memory,so tmpSLLBlock may 
be a null pointer.in line 100,there is a statement derefer tmpSLLBlock without 
check it.the process of this potential bug is shown in figure 5.btw,there are 
several null pointer dereference caused by same reason,one of which is marked 
by green text in graph 4.

In file libx11-1.6.4/modules/im/ximcp/imCallbk.c,defination of function 
_XimStrConversionCallback,line 338.
there is a statement call function Xmalloc to allocate memory,load its return 
value to buf,but Xmalloc may fail to allocate memory,so buf may be a null 
pointer.in line 340,buf act as the first parameter of funcion 
_XimSetHeader(this function is in file 
libx11-1.6.2/modules/im/ximcp/imDefIm.c,line 78),in this function there are 
several statement derefer buf without check.the process of this potential bug 
is shown in figure 5.btw,some of lines after line 340 also will derefer buf 
without check. 

In file libx11-1.6.4/modules/im/ximcp/imCallbk.c,defination of function 
_read_text_from_packet,line 528.
there is a statement call function Xmalloc to allocate memory,load its return 
value to text->feedback,but Xmalloc may fail to allocate memory,so 
text->feedback may be a null pointer.In line 531,there is a statement derefer 
text->feedback without check it.the process of this potential bug is shown in 
figure 6.

In file libx11-1.6.4/src/xcms/cmsColNm.c,defination of function 
_XcmsParseColorString,line 212.
there is a statement call function Xmalloc to allocate memory,load its return 
value to string_lowered ,but Xmalloc may fail to allocate memory,so 
string_lowered may be a null pointer.In line 219,there is a statement derefer 
string_lowered without check it.the process of this potential bug is shown in 
figure 7. 

In file libx11-1.6.4/src/xcms/cmsColNm.c,defination of function 
_XcmsLookupColorName,line 421.
there is a statement call function Xmalloc to allocate memory,load its return 
value to name_lowered ,but Xmalloc may fail to allocate memory,so name_lowered 
may be a null pointer.In line 432,there is a statement derefer name_lowered 
without check it.the process of this potential bug is shown in figure 8.


In file libx11-1.6.4/src/xcms/IdOfPr.c,defination of function 
XcmsFormatOfPrefix,line 70.
there is a statement call function Xmalloc to allocate memory,load its return 
value to string_lowered ,but Xmalloc may fail to allocate memory,so 
string_lowered  may be a null pointer.In line 82,there is a statement derefer 
string_lowered without check it.the process of this potential bug is shown in 
figure 9.

In file libx11-1.6.4/src/InitExt.c,defination of function XESetWireToError,line 
332.
there is a statement call function Xmalloc to allocate memory,load its return 
value to dpy->error_vec ,but Xmalloc may fail to allocate memory,so 
dpy->error_vec may be a null pointer.In line 

[Touch-packages] [Bug 1940018] [NEW] Several potential bugs of memory leak in libx11-1.6.4

[yuxuan He]

Public bug reported:

Ubuntu version: 18.04
libx11 version:1.6.4
Hello,I found some potential bugs in package libx11-xcb-dev,and the microsoft 
word file in the attachment I uploaded shows the occurrence process of the bug 
in a graphical way.Would you help me check whether the bugs mentioned below are 
true? I'm not 100% sure that the bugs I submitted is correct. I hope you don't 
mind seeing the wrong bug I submitted.Thank you very much for your patience.

In file libx11-1.6.4/modules/im/ximcp/imLcPrs.c,defination of 
parsestringfile,line 734.
The statement "tbp=malloc(size);"allocate memory to tbp and in line 738,if 
select false branch at this statement,tbp will not be freed correctly.the 
process of this potential bug is shown in figure 1.

In file libx11-1.6.4/src/xlibi18n/lcDB.c,defination of f_numeric,line 882.
The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 883,if 
select false branch at this statement,function f_numeric will go on to 
execute.In line 910 or line 915,if select false branch at this statement,wordp 
will not be freed correctly.the process of this potential bug is shown in 
figure 2.

In file libx11-1.6.4/src/xlibi18n/lcDB.c,defination of f_default,line 933.
The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 934,if 
select false branch at this statement,function f_default will go on to 
execute.and if select true branch in line 938,flow goto err,In line 989,if 
select false branch here,wordp will not be freed correctly.the process of this 
potential bug is shown in figure 3.

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

** Attachment added: "libx11_memory_leak.docx"
   
https://bugs.launchpad.net/bugs/1940018/+attachment/5518042/+files/libx11_memory_leak.docx

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

Title:
  Several potential bugs of memory leak in libx11-1.6.4

Status in libx11 package in Ubuntu:
  New

Bug description:
  Ubuntu version: 18.04
  libx11 version:1.6.4
  Hello,I found some potential bugs in package libx11-xcb-dev,and the microsoft 
word file in the attachment I uploaded shows the occurrence process of the bug 
in a graphical way.Would you help me check whether the bugs mentioned below are 
true? I'm not 100% sure that the bugs I submitted is correct. I hope you don't 
mind seeing the wrong bug I submitted.Thank you very much for your patience.

  In file libx11-1.6.4/modules/im/ximcp/imLcPrs.c,defination of 
parsestringfile,line 734.
  The statement "tbp=malloc(size);"allocate memory to tbp and in line 738,if 
select false branch at this statement,tbp will not be freed correctly.the 
process of this potential bug is shown in figure 1.

  In file libx11-1.6.4/src/xlibi18n/lcDB.c,defination of f_numeric,line 882.
  The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 
883,if select false branch at this statement,function f_numeric will go on to 
execute.In line 910 or line 915,if select false branch at this statement,wordp 
will not be freed correctly.the process of this potential bug is shown in 
figure 2.

  In file libx11-1.6.4/src/xlibi18n/lcDB.c,defination of f_default,line 933.
  The statement "wordp=malloc(len+1);"allocate memory to wordp and in line 
934,if select false branch at this statement,function f_default will go on to 
execute.and if select true branch in line 938,flow goto err,In line 989,if 
select false branch here,wordp will not be freed correctly.the process of this 
potential bug is shown in figure 3.

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


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

[Touch-packages] [Bug 1939966] Re: Random system stops

[Daniel van Vugt]

Thanks for the bug report. Next time the problem happens, please:

1. Wait 10 seconds.

2. Reboot.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.

5. Also check for crashes using these instructions:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

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

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

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

Title:
  Random system stops

Status in Ubuntu:
  Incomplete

Bug description:
  Every once in a while (it's been three times this week), the entire
  system will just stop. There's still electricity running. The keyboard
  is lit up, and the monitor is black (electricity-running black, and
  not shutdown-black). There's no picture and no sound. Just immediately
  before it does, I know it's about to happen because whatever audio is
  playing at the time will begin repeating, and then the computer goes
  down. I don't actually know if it's an Xorg problem. It just sounded
  like the closest possibility, based on the way the computer actually
  behaves.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-25.27~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .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  470.57.02  Tue Jul 13 
16:14:05 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat Aug 14 19:34:11 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 470.57.02, 5.11.0-25-generic, x86_64: installed
   nvidia, 470.57.02, 5.8.0-63-generic, x86_64: installed
   virtualbox, 6.1.22, 5.11.0-25-generic, x86_64: installed
   virtualbox, 6.1.22, 5.8.0-63-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU106 [GeForce RTX 2060] [10de:1f15] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1e21]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev f0) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Renoir [1043:1e21]
  InstallationDate: Installed on 2021-03-20 (147 days ago)
  InstallationMedia: Xubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 
(20210204)
  MachineType: ASUSTeK COMPUTER INC. TUF Gaming FA506IV_TUF506IV
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-25-generic 
root=UUID=0fc8340c-98de-4434-9806-ec613e241e8c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/02/2020
  dmi.bios.release: 5.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FA506IV.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FA506IV
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 3.9
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFA506IV.309:bd07/02/2020:br5.16:efr3.9:svnASUSTeKCOMPUTERINC.:pnTUFGamingFA506IV_TUF506IV:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnFA506IV:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF Gaming FA506IV
  dmi.product.name: TUF Gaming FA506IV_TUF506IV
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To 

[Touch-packages] [Bug 1939941] Re: Drop down menu issues

[Daniel van Vugt]

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

** Also affects: firefox (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/1939941

Title:
  Drop down menu issues

Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  I found that about a month or so ago that I was having problems with
  dropdown menus in Thunderbird where they would not respond when I
  clicked on them. I managed to get around this by using the arrow keys
  but I would also have issues with the thunderbird icon in the icon
  tray not responding if I suspended the computer with Thunderbird still
  open. Now I find that the drop down application menu in Firefox also
  doesn't work and when I click on it the menu flashes up very quickly
  but then disappears. Also sometimes drop down menus that I have opened
  continue to persist in the display even after I have shut down the
  program, so I don't think it is a problem just in Mozilla products. I
  have reported the bug to Mozilla however just in case.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Aug 14 13:19:47 2021
  DistUpgraded: 2021-05-17 16:32:46,967 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05bd]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / 
Radeon 520 Mobile] [1028:05bd]
  InstallationDate: Installed on 2021-03-06 (160 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Dell Inc. Latitude E6440
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_i3o8fa@/vmlinuz-5.11.0-25-generic 
root=ZFS=rpool/ROOT/ubuntu_i3o8fa ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to hirsute on 2021-05-17 (88 days ago)
  dmi.bios.date: 06/13/2019
  dmi.bios.release: 65.24
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A24
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA24:bd06/13/2019:br65.24:svnDellInc.:pnLatitudeE6440:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6440
  dmi.product.sku: 05BD
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


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

[Touch-packages] [Bug 1870829] Re: AptX and AptX HD unavailable as Bluetooth audio quality options

[Daniel van Vugt]

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

** Bug watch added: Debian Bug tracker #991597
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597

** Also affects: pulseaudio (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=991597
   Importance: Unknown
   Status: Unknown

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

Title:
  AptX and AptX HD unavailable as Bluetooth audio quality options

Status in pulseaudio package in Ubuntu:
  Confirmed
Status in pulseaudio package in Debian:
  Unknown

Bug description:
  Current situation:

  When one connects a Bluetooth audio device, at best one can choose
  between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback
  (A2DP Sink)". That is sad when the audio device supports AptX or AptX
  HD.

  
  Expected situation:

  One can select AptX or AptX HD as the Bluetooth audio output profile.

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


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

[Touch-packages] [Bug 1931722] Re: software-properties-gtk generates python errors

[Launchpad Bug Tracker]

[Expired for software-properties (Ubuntu) because there has been no
activity for 60 days.]

** Changed in: software-properties (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  software-properties-gtk generates python errors

Status in software-properties package in Ubuntu:
  Expired

Bug description:
  Launching software-properties-gtk gives all these Python errors after
  having upgraded to 21.04:

  Gtk-Message: 17:32:53.643: Failed to load module "appmenu-gtk-module"
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 196, in __init__
  bus = dbus.SystemBus()
File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 195, in __new__
  return Bus.__new__(cls, Bus.TYPE_SYSTEM, mainloop=mainloop,
File "/usr/lib/python3/dist-packages/dbus/_dbus.py", line 102, in __new__
  bus = BusConnection.__new__(subclass, bus_type, mainloop=mainloop)
File "/usr/lib/python3/dist-packages/dbus/bus.py", line 124, in __new__
  bus = cls._new_for_bus(address_or_type, mainloop=mainloop)
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.LimitsExceeded: The 
maximum number of active connections for UID 1000 has been reached

  Version: 0.99.10

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: software-properties-common 0.99.10
  ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Fri Jun 11 17:36:34 2021
  InstallationDate: Installed on 2020-09-06 (277 days ago)
  InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to hirsute on 2021-06-08 (2 days ago)

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


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

[Touch-packages] [Bug 1940008] Re: systemd lsb-base integration script leaking shell variable changes which can break consumers

[Ryan]

I'm not a bash script architect, but I bodged together this workaround
and the ipmiutil_wdt service starts correctly with it applied to my
system:

https://gist.github.com/TheWug/1a7f509e040f10c05039acc06fe29d9e

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

Title:
  systemd lsb-base integration script leaking shell variable changes
  which can break consumers

Status in systemd package in Ubuntu:
  New

Bug description:
  I am using systemd version 248.3-1ubuntu3 from the impish repository.

  It was compiled and built in the following manner:
  # add impish deb-src repository to apt sources
  apt build-dep systemd/impish
  apt source -b systemd/impish

  Once built, it was installed over the top of systemd 245.4-4ubuntu3.

  I am running ubuntu 20.04.2.

  The source tarball of systemd includes a file
  (./debian/systemd/lib/lsb/init-functions.d/40-systemd) which is
  intended to be installed into the drop-in script directory provided by
  the lsb-base package (/lib/lsb/init-functions.d).

  The problem that I am having is that this file (which is sourced by
  any script which sources /lib/lsb/init-functions) is setting
  variables, and in doing so, accidentally overwriting variables which
  are configured by the calling script.

  
https://gist.github.com/TheWug/e120145f08e994d89e235e077a82ea75#file-40-systemd-L19

  I noticed this when investigating why ipmiutil_wdt.service (provided
  by package ipmiutil) was failing to start. The problem is that the
  ipmiutil_wdt script, which makes use of init-functions, was statically
  setting some variables for later use, including one called $prog.
  $prog is then inadvertently overwritten by 40-systemd when
  ipmiutil_wdt sources /lib/lsb/init-functions.

  I think this is systemd's bug because systemd's lsb-base drop-in is
  not being a "good neighbor" to the scripts with which it shares a
  controlling shell. Even if ipmiutil were to rewrite its ipmiutil-wdt
  script, any other such script provided by another package which tries
  to use a variable called $prog (or $executable, or $argument, or
  $service, or $state, or any of a handful of others) will find its feet
  being stepped on by systemd's drop-in.

  I propose that the drop-in be modified to encapsulate all of this
  behavior where variables are assigned to within a function or subshell
  or something, so they can't accidentally contaminate the outside
  world.

  Other related package versions:
  lsb-base: 11.1.0ubuntu2
  ipmiutil: 3.1.5-1

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


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

[Touch-packages] [Bug 1940008] Re: systemd lsb-base integration script leaking shell variable changes which can break consumers

[Ryan]

It also looks like, farther down, systemctl_redirect() leaks $service.
Not sure if it's intentional or not, given that it works to protect its
other variables, so maybe it could use some attention too.

https://gist.github.com/TheWug/e120145f08e994d89e235e077a82ea75#file-40-systemd-L70

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

Title:
  systemd lsb-base integration script leaking shell variable changes
  which can break consumers

Status in systemd package in Ubuntu:
  New

Bug description:
  I am using systemd version 248.3-1ubuntu3 from the impish repository.

  It was compiled and built in the following manner:
  # add impish deb-src repository to apt sources
  apt build-dep systemd/impish
  apt source -b systemd/impish

  Once built, it was installed over the top of systemd 245.4-4ubuntu3.

  I am running ubuntu 20.04.2.

  The source tarball of systemd includes a file
  (./debian/systemd/lib/lsb/init-functions.d/40-systemd) which is
  intended to be installed into the drop-in script directory provided by
  the lsb-base package (/lib/lsb/init-functions.d).

  The problem that I am having is that this file (which is sourced by
  any script which sources /lib/lsb/init-functions) is setting
  variables, and in doing so, accidentally overwriting variables which
  are configured by the calling script.

  
https://gist.github.com/TheWug/e120145f08e994d89e235e077a82ea75#file-40-systemd-L19

  I noticed this when investigating why ipmiutil_wdt.service (provided
  by package ipmiutil) was failing to start. The problem is that the
  ipmiutil_wdt script, which makes use of init-functions, was statically
  setting some variables for later use, including one called $prog.
  $prog is then inadvertently overwritten by 40-systemd when
  ipmiutil_wdt sources /lib/lsb/init-functions.

  I think this is systemd's bug because systemd's lsb-base drop-in is
  not being a "good neighbor" to the scripts with which it shares a
  controlling shell. Even if ipmiutil were to rewrite its ipmiutil-wdt
  script, any other such script provided by another package which tries
  to use a variable called $prog (or $executable, or $argument, or
  $service, or $state, or any of a handful of others) will find its feet
  being stepped on by systemd's drop-in.

  I propose that the drop-in be modified to encapsulate all of this
  behavior where variables are assigned to within a function or subshell
  or something, so they can't accidentally contaminate the outside
  world.

  Other related package versions:
  lsb-base: 11.1.0ubuntu2
  ipmiutil: 3.1.5-1

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


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

[Touch-packages] [Bug 1939933] Re: pulseaudio is not built with AptX support

[Daniel van Vugt]

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

Oh, sorry I never tested any of the new codecs. Bug 1870829 has been
reopened.

** This bug has been marked a duplicate of bug 1870829
   AptX and AptX HD unavailable as Bluetooth audio quality options

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

Title:
  pulseaudio is not built with AptX support

Status in pulseaudio package in Ubuntu:
  New
Status in pulseaudio package in Debian:
  Unknown

Bug description:
  The changelog mentions AptX, but it's not actually enabled in the
  build if I'm not mistaken. Aptx support seems to require gstreamer in
  the build dependency at least.

  [changelog]
  pulseaudio (1:15.0+dfsg1-1ubuntu1) impish; urgency=medium

* New upstream version resynchronized on Debian
 - Support for bluetooth LDAC and AptX codecs and HFP profiles for
   improved audio quality

  [upstream release notes]
  
https://www.freedesktop.org/wiki/Software/PulseAudio/Notes/15.0/#supportforldacandaptxbluetoothcodecsplussbcxqsbcwithhigher-qualityparameters

  
  [meson.build]

  bluez5_gst_dep = dependency('gstreamer-1.0', version : '>= 1.14', required : 
get_option('bluez5-gstreamer'))
  bluez5_gstapp_dep = dependency('gstreamer-app-1.0', required : 
get_option('bluez5-gstreamer'))
  have_bluez5_gstreamer = false
  if bluez5_gst_dep.found() and bluez5_gstapp_dep.found()
have_bluez5_gstreamer = true
cdata.set('HAVE_GSTLDAC', 1)
cdata.set('HAVE_GSTAPTX', 1)
  endif

  
  [build log]
  
https://launchpadlibrarian.net/551304449/buildlog_ubuntu-impish-amd64.pulseaudio_1%3A15.0+dfsg1-1ubuntu1_BUILDING.txt.gz

  ...
  Dependency gstreamer-1.0 skipped: feature gstreamer disabled
  Dependency gstreamer-app-1.0 skipped: feature gstreamer disabled
  Dependency gstreamer-rtp-1.0 skipped: feature gstreamer disabled
  Run-time dependency gstreamer-1.0 found: NO (tried pkgconfig and cmake)
  Run-time dependency gstreamer-app-1.0 found: NO (tried pkgconfig and cmake)
  ...

  Enable D-Bus:  true
Enable BlueZ 5:  true
  Enable native headsets:true
  Enable  ofono headsets:true
  Enable GStreamer based codecs: false

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


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

[Touch-packages] [Bug 1883798] Re: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different f

[Sagar]

Thank you so much ...you make my day.
Thanks Diki for the solution

Solution By " Diki Taufik Gurohman (taufikdiki11) wrote on 2020-12-15 "

rm -rf /usr/share/doc/libjpeg-turbo8/changelog.Debian.gz

then

apt --fix-broken install

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

Title:
  package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libjpeg-
  turbo8/changelog.Debian.gz', which is different from other instances
  of package libjpeg-turbo8:amd64

Status in libjpeg-turbo package in Ubuntu:
  Confirmed

Bug description:
  not install file !!! packettracer

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libjpeg-turbo8 2.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   libjpeg-turbo8:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jun 17 03:37:01 2020
  DpkgTerminalLog:
   Preparing to unpack .../libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb ...
   Unpacking libjpeg-turbo8:amd64 (2.0.3-0ubuntu1.20.04.1) over 
(2.0.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
  InstallationDate: Installed on 2020-06-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', 
which is different from other instances of package libjpeg-turbo8:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1939973] [NEW] make 4.3-4.1 triggers build failures

[Matthias Klose]

Public bug reported:

trying to rebuild cross-toolchain-base from
https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile/+packages

triggers a build failure:

[...]
START stamp-dir/init-binutils
tar -x -f  /usr/src/binutils/binutils-2.37.tar.xz
set -e; cd binutils-2.37 ; cp -a /usr/src/binutils/debian/ . ; if [ -n "$(grep 
-v '^\#' /<>/debian/patches/binutils/series)" ]; then 
QUILT_PATCHES=/<>/debian/patches/binutils quilt --quiltrc 
/dev/null  push -a; fi; rm -rf .pc
cd binutils-2.37 ; env -i CROSS_ARCHS="amd64 i386 s390x ppc64el arm64 armhf 
armel  powerpc" debian/rules stamps/control
make: dpkg-architecture: No such file or directory
make: lsb_release: No such file or directory
make: lsb_release: No such file or directory
make: pwd: No such file or directory
make: dpkg-parsechangelog: No such file or directory
make: dpkg-parsechangelog: No such file or directory
make: dpkg-parsechangelog: No such file or directory
make: dpkg-parsechangelog: No such file or directory
debian/rules:163: *** unexpected source package name: .  Stop.
make: *** [debian/rules:215: stamp-dir/init-binutils] Error 2
dpkg-buildpackage.pl: error: debian/rules build subprocess returned exit status 
2


working around by omitting the -i option to env, or by setting PATH explicitly. 
Reverting to the version in the release pocket lets the c-t-b- build succeed.

** Affects: make-dfsg (Ubuntu)
 Importance: High
 Status: Confirmed


** Tags: block-proposed rls-ii-incoming

** Changed in: make-dfsg (Ubuntu)
   Status: New => Confirmed

** Changed in: make-dfsg (Ubuntu)
   Importance: Undecided => High

** Tags added: block-proposed rls-ii-incoming

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

Title:
  make 4.3-4.1 triggers build failures

Status in make-dfsg package in Ubuntu:
  Confirmed

Bug description:
  trying to rebuild cross-toolchain-base from
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile/+packages

  triggers a build failure:

  [...]
  START stamp-dir/init-binutils
  tar -x -f  /usr/src/binutils/binutils-2.37.tar.xz
  set -e; cd binutils-2.37 ; cp -a /usr/src/binutils/debian/ . ; if [ -n 
"$(grep -v '^\#' /<>/debian/patches/binutils/series)" ]; then 
QUILT_PATCHES=/<>/debian/patches/binutils quilt --quiltrc 
/dev/null  push -a; fi; rm -rf .pc
  cd binutils-2.37 ; env -i CROSS_ARCHS="amd64 i386 s390x ppc64el arm64 armhf 
armel  powerpc" debian/rules stamps/control
  make: dpkg-architecture: No such file or directory
  make: lsb_release: No such file or directory
  make: lsb_release: No such file or directory
  make: pwd: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  debian/rules:163: *** unexpected source package name: .  Stop.
  make: *** [debian/rules:215: stamp-dir/init-binutils] Error 2
  dpkg-buildpackage.pl: error: debian/rules build subprocess returned exit 
status 2

  
  working around by omitting the -i option to env, or by setting PATH 
explicitly. Reverting to the version in the release pocket lets the c-t-b- 
build succeed.

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


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

[Touch-packages] [Bug 1939238] Re: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

[geole0]

Hello
"It asks me to do an fsk manually if I read between the lines, and I don't 
understand what that means or what to do." => 
https://forum.ubuntu-fr.org/viewtopic.php?pid=22480277#p22480277

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

Title:
  UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  Hello
  This problem did not occur on my computer.

  https://nsa40.casimages.com/img/2021/08/07/210807015400327092.png

  It occurs in users who are not competent.
  This week, the French forum collapsed over this incident.

  I think changing the advice phrase might improve understanding of the
  action to be taken.

  Can these lines
  "   ( i.e.. without -a or -p options) 
  fsck existed with status code 4
  The root file system on /dev/ requires a manual fsck"
  become
  "execute this command 'fsck -y /dev/xx' to do a manual fsck on the root 
file system."

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-terminal 3.38.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug  8 15:16:28 2021
  ExecutablePath: /usr/libexec/gnome-terminal-server
  InstallationDate: Installed on 2020-08-02 (370 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to hirsute on 2021-07-11 (27 days ago)

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


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