[Touch-packages] [Bug 1958147] Re: Nvidia acceleration has gone

2022-01-17 Thread Daniel van Vugt
Thanks for the bug report.

Indeed it looks like there is no Nvidia kernel driver loaded. To fix
that please open the 'Additional Drivers' app and it will help you to
install the appropriate Nvidia driver.


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

Title:
  Nvidia acceleration has gone

Status in Ubuntu:
  Incomplete

Bug description:
  since the last update my nvidia acceleration no longer works

  This is the card
  02:00.0 3D controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 17 15:20:30 2022
  DistUpgraded: 2021-10-27 20:53:18,542 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  DkmsStatus:
   alsa-firewire, 4.4, 4.13.0-39-generic, x86_64: installed
   evdi, 1.2.58: added
  ExtraDebuggingInterest: Yes
  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:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2016-08-29 (1967 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to impish on 2021-10-27 (81 days ago)
  dmi.bios.date: 02/13/2018
  dmi.bios.release: 65.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.asset.tag: AMIAS
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A11
  dmi.chassis.asset.tag: AMIAS
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd02/13/2018:br65.11:svnDellInc.:pnDellPrecisionM3800:pvrA11:rvnDellInc.:rnDellPrecisionM3800:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:skuDellPrecisionM3800:
  dmi.product.name: Dell Precision M3800
  dmi.product.sku: Dell Precision M3800
  dmi.product.version: A11
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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-2build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1958147/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed

2022-01-17 Thread Daniel van Vugt
I don't think it's quite doubling. Usually "chipmunks sound" bugs are a
mismatch between 44.1kHz and 48.0kHz somewhere in the system.

The refresh rate of the monitor should be completely irrelevant to any
audio.

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

Title:
  Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double
  playback speed

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a desktop computer with a 60Hz 4K display connected through Display 
Port. The display is a ThinkVision X1 with built in audio. With the Display 
Port cable I am then able to output sound from the monitor and this works 
without any issues.
  I have now added a 4K Samsung television through HDMI to the same GPU, which 
also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only 
do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear 
however, that when it is set to 60Hz in Wayland, the animation on the 
television is much more smooth. 

  The problem is that whenever I set the television to 60Hz, the playback of 
any sound is both high pitched and faster than normal. If I play a video in 
YouTube, the video appears to playback about twice as fast as normal and and 
very high pitched sound (everyone sounds like chipmunks). This is the case on 
the entire system (also when playing the video or any other sounds on the X1 
display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz 
again does everything play and sound normal again. 
  It is only the playback of media that is doubled in speed. Everything else 
(animations, mouse, etc.) is still behaving as normal.

  If I change audio output to the ThinkVision X1 (or something else) at
  60Hz while also being connected to the television at 60Hz, the audio
  stays high pitched and sped up.

  If I unplug the main display, ThinkVision X1, then the playback of
  media on the television becomes normal.

  I have tried with different +100 USD HDMI cables, that are all rated
  as HDMI 2.0 and the behavior stays the same.

  My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the
  behavior was the same.

  I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI).

  As mentioned I cannot test it in Xorg, but that is only because it
  does not allow me to set the refresh rate to 60Hz.

  I am uncertain whether this is related to MESA, Pulseaudio or maybe
  Mutter/Wayland?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1951624] Re: OpenSSL 3.0 transition might lead to unsupported protocols

2022-01-17 Thread Sebastien Bacher
Upstream fixed it in https://w1.fi/cgit/hostap/commit/?id=ff2eccbd which
is included in the new 2.10 version uploaded to Ubuntu

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

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

Title:
  OpenSSL 3.0 transition might lead to unsupported protocols

Status in wpa package in Ubuntu:
  Fix Released

Bug description:
  OpenSSL 3.0, which is planned to land in the archive Very Soon™, has
  moved quite a few algorithms to its "legacy" provider, which isn't
  loaded by default. Some of those algorithms are used in various
  protocols implemented by wpa_supplicant, so it's likely that the
  package will be broken in this regard.

  Sadly, this isn't caught by either the build-time tests nor the
  autopkgtests.

  A first good step would be to patch wpa_supplicant to load the
  "legacy" provider (and the default one too, cf
  https://www.openssl.org/docs/manmaster/man7/crypto.html , look for
  "legacy").

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1951624/+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 1939455] Re: Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc video output

2022-01-17 Thread Timo Aaltonen
thanks for testing

focal-proposed (and impish) has 21.2.6, so once it lands in updates,
it's also fixed for focal

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

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

Title:
  Upgrading from 20.0.4-2ubuntu1 to 21.0.3-0ubuntu0.2~20.04.1 breaks vlc
  video output

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Hello!

  As reported here
  https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1939447 upgrading
  mesa-vdpau-drivers package from 20.0.4-2ubuntu1 to
  21.0.3-0ubuntu0.2~20.04.1 breaks vlc video hardware acceleration.

  Thanks!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mesa-vdpau-drivers 21.0.3-0ubuntu0.2~20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-80.90-generic 5.4.124
  Uname: Linux 5.4.0-80-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Wed Aug 11 02:21:08 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Mullins [Radeon R4/R5 Graphics] 
[1002:9851] (rev 40) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mullins [Radeon R4/R5 Graphics] 
[103c:81e5]
  MachineType: HP HP 245 G5 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-80-generic 
root=UUID=e8820090-c9e5-4245-bcb4-92818bd91e34 ro quiet splash vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/21/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.08
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81E5
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 73.14
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.08:bd04/21/2016:svnHP:pnHP245G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81E5:rvrKBCVersion73.14:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=245
  dmi.product.name: HP 245 G5 Notebook PC
  dmi.product.sku: Y9Q66PC#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-12T15:11:08.785042
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.2~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1939455/+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 1956831] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-01-17 Thread Brian Murray
It looks like the last time we updated /boot partition sizing used by
the install was with the Artful (17.10) release of Ubuntu, so your
install was well before this and likely has small /boot partition. Given
that we can't do anything about the already installed system I'm going
to close this as Invalid. Thanks for getting back to us!

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  Happened during do-release-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
  Uname: Linux 4.15.0-166-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 18:54:36 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-10-04 (2288 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2022-01-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956831/+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 1912911] Re: When printing with my Brother hl-2170w printer I keep getting an invalid page range error on a blank page, after the desired pages are printed

2022-01-17 Thread tedo
Upstream bugfix released in https://github.com/OpenPrinting/cups-
filters/releases/tag/1.28.11

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

Title:
  When printing with my Brother hl-2170w printer I keep getting an
  invalid page range error on a blank page, after the desired pages are
  printed

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  When I run uname -a, this is basically what I get:
  "5.8.0-38-generic #43~20.04.1-Ubuntu SMP Tue Jan 12 16:39:47 UTC 2021 x86_64 
x86_64 x86_64 GNU/Linux"

  apt-cache policy cups gives me the following:

  cups:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu1.1
Version table:
   *** 2.3.1-9ubuntu1.1 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  
===

  4 and 5 are being answered together...

  Before the upgrade, I was able to print one or more pages, and not see the 
extra error page.
  This is the desired behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.8.0-38.43~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 23 13:15:24 2021
  InstallationDate: Installed on 2020-12-21 (33 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Lpstat: device for SCRIBE: 
dnssd://Brother%20HL-2170W%20series._pdl-datastream._tcp.local/
  MachineType: Dell Inc. Inspiron 7773
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/SCRIBE.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/SCRIBE.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-38-generic 
root=UUID=9899e123-f378-4328-a399-78cd6361f58e ro quiet splash 
resume=UUID=46e80ad1-16de-4fdf-b1f7-96f4f58b1c57
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/14/2017
  dmi.bios.release: 1.2
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.1
  dmi.board.name: 0R58C3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.1:bd09/14/2017:br1.2:svnDellInc.:pnInspiron7773:pvr:rvnDellInc.:rn0R58C3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 7773
  dmi.product.sku: 0809
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1912911/+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 1927192] Re: gdb ftbfs on armhf, testsuite timeouts

2022-01-17 Thread Brian Murray
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal

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

Title:
  gdb ftbfs on armhf, testsuite timeouts

Status in gdb:
  Incomplete
Status in gdb package in Ubuntu:
  Fix Released
Status in glibc package in Ubuntu:
  Fix Released
Status in gdb source package in Focal:
  Fix Committed
Status in glibc source package in Focal:
  Fix Committed
Status in gdb source package in Groovy:
  Won't Fix
Status in glibc source package in Groovy:
  Won't Fix
Status in gdb source package in Hirsute:
  Won't Fix
Status in glibc source package in Hirsute:
  Won't Fix
Status in gdb source package in Impish:
  Fix Released
Status in glibc source package in Impish:
  Fix Released

Bug description:
  [Impact]

  * Gdb can't set some breakpoints in ld.so on armhf when libc6-dbg is
  not installed.

  [Test Plan]

  * Check that ld.so is not stripped on armhf:
  $  /lib/*/ld-2.31.so
  libc6/lib/arm-linux-gnueabihf/ld-2.31.so: ELF 32-bit LSB shared object, ARM, 
EABI5 version 1 (SYSV), dynamically linked, 
BuildID[sha1]=e20a43bff0c4d2aa7f508c93eadad973ea0c0af9, with debug_info, not 
stripped

  * Check that ld.so is stripped on amd64:

  $ file /lib/x86_64-linux-gnu/ld-2.31.so
  /lib/x86_64-linux-gnu/ld-2.31.so: ELF 64-bit LSB shared object, x86-64, 
version 1 (SYSV), dynamically linked, 
BuildID[sha1]=ea85fcb25ee4c4c9e7b180924ab4a44257a9547a, stripped

  [Where problems could occur]

  * The fix is not stripping ld.so on armhf. Not stripping it comes with
  a notable increase in file size and it may be performance critical
  109K stripped vs 1.3M unstripped. Accidentally ld.so could be left
  unstripped on other architectures, but the test plan covers checking
  that, at least on amd64. Other than those not stripping ld.so should
  not cause any issue.

  [Original Bug Text]

  see https://launchpad.net/ubuntu/+source/gdb/10.2-0ubuntu3

  $ zcat buildlog_ubuntu-impish-armhf.gdb_10.2-0ubuntu3_BUILDING.txt.gz | fgrep 
'(timeout)'|wc -l
  10451

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1927192/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed

2022-01-17 Thread Troels Petersen
However, audio going through USB on the X1 ThinkVision (called "Analog Output - 
X1") is now playing correctly in Wayland with both monitors at 60Hz. 
When selecting the television output "HDMI / DisplayPort - Vega 20 HDMI Audio 
[Radeon VII]" on Wayland with 60Hz on both monitors, the playback doubles and 
sound is high pitched. (This one is connected through HDMI)

When selecting the X1 monitor output "HDMI / DisplayPort 2 - Vega 20
HDMI Audio [Radeon VII]" on Wayland with 60Hz on both monitors, the
playback doubles and sound is also high pitched. (This one is connected
through DisplayPort)

So it appears that on Wayland with both monitors on 60Hz, the audio
going through either HDMI or DisplayPort doubles in speed and becomes
high pitched.

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

Title:
  Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double
  playback speed

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a desktop computer with a 60Hz 4K display connected through Display 
Port. The display is a ThinkVision X1 with built in audio. With the Display 
Port cable I am then able to output sound from the monitor and this works 
without any issues.
  I have now added a 4K Samsung television through HDMI to the same GPU, which 
also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only 
do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear 
however, that when it is set to 60Hz in Wayland, the animation on the 
television is much more smooth. 

  The problem is that whenever I set the television to 60Hz, the playback of 
any sound is both high pitched and faster than normal. If I play a video in 
YouTube, the video appears to playback about twice as fast as normal and and 
very high pitched sound (everyone sounds like chipmunks). This is the case on 
the entire system (also when playing the video or any other sounds on the X1 
display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz 
again does everything play and sound normal again. 
  It is only the playback of media that is doubled in speed. Everything else 
(animations, mouse, etc.) is still behaving as normal.

  If I change audio output to the ThinkVision X1 (or something else) at
  60Hz while also being connected to the television at 60Hz, the audio
  stays high pitched and sped up.

  If I unplug the main display, ThinkVision X1, then the playback of
  media on the television becomes normal.

  I have tried with different +100 USD HDMI cables, that are all rated
  as HDMI 2.0 and the behavior stays the same.

  My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the
  behavior was the same.

  I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI).

  As mentioned I cannot test it in Xorg, but that is only because it
  does not allow me to set the refresh rate to 60Hz.

  I am uncertain whether this is related to MESA, Pulseaudio or maybe
  Mutter/Wayland?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed

2022-01-17 Thread Troels Petersen
This does not fix the issue. Playback is still double and high pitched in 
Wayland with both monitors at 60Hz.
In Xorg I can still only select 30Hz as the maximum on the television.

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

Title:
  Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double
  playback speed

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have a desktop computer with a 60Hz 4K display connected through Display 
Port. The display is a ThinkVision X1 with built in audio. With the Display 
Port cable I am then able to output sound from the monitor and this works 
without any issues.
  I have now added a 4K Samsung television through HDMI to the same GPU, which 
also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only 
do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear 
however, that when it is set to 60Hz in Wayland, the animation on the 
television is much more smooth. 

  The problem is that whenever I set the television to 60Hz, the playback of 
any sound is both high pitched and faster than normal. If I play a video in 
YouTube, the video appears to playback about twice as fast as normal and and 
very high pitched sound (everyone sounds like chipmunks). This is the case on 
the entire system (also when playing the video or any other sounds on the X1 
display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz 
again does everything play and sound normal again. 
  It is only the playback of media that is doubled in speed. Everything else 
(animations, mouse, etc.) is still behaving as normal.

  If I change audio output to the ThinkVision X1 (or something else) at
  60Hz while also being connected to the television at 60Hz, the audio
  stays high pitched and sped up.

  If I unplug the main display, ThinkVision X1, then the playback of
  media on the television becomes normal.

  I have tried with different +100 USD HDMI cables, that are all rated
  as HDMI 2.0 and the behavior stays the same.

  My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the
  behavior was the same.

  I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI).

  As mentioned I cannot test it in Xorg, but that is only because it
  does not allow me to set the refresh rate to 60Hz.

  I am uncertain whether this is related to MESA, Pulseaudio or maybe
  Mutter/Wayland?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 174032] Re: lvresize fails attempting to call fsadm with --resizefs parameter

2022-01-17 Thread halil sen
It looks like this issue is fixed on Ubuntu 20.04 but a similar issue persists 
if `lvresize --resizefs` is called within a init-premount script (even though 
lvresize and fsadm copied via coy_exec).
 
```
/sbin/fsadm: execvp failed: No such file or directory
Filesystem check failed.

exit code 5.

```

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

Title:
  lvresize fails attempting to call fsadm with --resizefs parameter

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: lvm2

  
  System information:

  uname -a
  Linux tardbook 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 
GNU/Linux

  (Ubuntu Gutsy with all updates.)

  Package version:

  dpkg -l | grep lvm
  ii  lvm2   2.02.26-1ubuntu4   
   The Linux Logical Volume Manager

  To reproduce the error:

  lvresize --verbose --resizefs --size +1036 /dev/usb_vg/testvol1
  Finding volume group usb_vg
  Executing: fsadm check /dev/usb_vg/testvol1 (null)
fsadm: execlp failed: No such file or directory
fsadm failed: 2

  Workaround:

  Remove the --resizefs parameter and as a second step use resize2fs or
  ext2prepare and ext2fsresize to modify the file system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/174032/+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 1955347] Re: rsync works bad with encfs now

2022-01-17 Thread Lucas Kanashiro
Hi Claude,

Are you able to roll rsycn back to version 3.1.3-8 to see if this gets
fixed? In 2021-11-16, we got an update to fix LP #1896251. FWIW, this is
the upstream patch that was applied:

https://github.com/WayneD/rsync/commit/af6118d98b3482cbcfc223bf2a0777bc19eccb02

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

Title:
  rsync works bad with encfs now

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I think rsync works bad with encfs now.

  When root uses it, rsync cannot read a directory encrypted with encfs
  by a user. More precisely, it cannot read the mounted directory, the
  virtual one where the user can read the datas.

  Until now there was only a warning like this
  "rsync: readlink_stat("/home/claude/Documents_chiffres") failed:
  Permission denied (13)"
  and the software went on working (only ignoring the content of the mounted 
directory and of course without saving this content)

  But recently there is this more:
  "IO error encountered -- skipping file deletion"
  and because of this "skipping file deletion", the software can't work 
normally. The destination gets bigger more and more because the deleted files 
in the source are not deleted in the destination.

  Thanks for reading me.
  rsync 3.1.3-8ubuntu0.1
  Description:Ubuntu 20.04.3 LTS
  Release:20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1955347/+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 495981] Re: NM disconnects Wi-Fi every 2 minutes but iwconfig+dhclient and wicd don't -- ath9k

2022-01-17 Thread corrado venturini
Same problem on Ubuntu 22.04 
corrado@corrado-n3-jj-0103:~$ apt policy network-manager
network-manager:
  Installed: 1.32.12-0ubuntu2
  Candidate: 1.32.12-0ubuntu2
  Version table:
 *** 1.32.12-0ubuntu2 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-n3-jj-0103:~$

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

Title:
  NM disconnects Wi-Fi every 2 minutes but iwconfig+dhclient and wicd
  don't -- ath9k

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: network-manager

  I have Dell studio XPS 13 running:
  Description:  Ubuntu 9.10
  Release:  9.10

  with wifi card (lspci):
  06:00.0 Network controller: Atheros Communications Inc. AR928X Wireless 
Network Adapter (PCI-Express) (rev 01)

  that works (tries to) with ath9k module.

  It connects to my access point and works ok however, It disconnects every 2-3 
min saying (in dmesg):
  [  311.600306] wlan0: RX AssocResp from 00:1d:68:0c:97:63 (capab=0x411 
status=0 aid=2)
  and then automatically reconnects... I have tried different drivers and other 
things

  Interestingly when I right-clicked on network manger applet, select ¨disable 
networking¨ and then set up everything myself on console using iwconfig and 
dhclient. IT WORKS!!!
  no disconnections
  wpa_supplicant is still running in a background but not doing anything (my 
wifi has WEP encryption).

  I´ve seen some similar reports in Internet but they seem to think that
  it is a driver problem when to me it looks like a NetworkManager
  issue...

  Hope it helps

  drphd

  ProblemType: Bug
  Architecture: amd64
  CRDA: Error: [Errno 2] No such file or directory
  Date: Sat Dec 12 19:42:18 2009
  DistroRelease: Ubuntu 9.10
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  IpRoute:
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.65
   172.16.77.0/24 dev vmnet1  proto kernel  scope link  src 172.16.77.1
   172.16.158.0/24 dev vmnet8  proto kernel  scope link  src 172.16.158.1
   default via 192.168.1.254 dev wlan0
  NonfreeKernelModules: nvidia
  Package: network-manager 0.8~a~git.20091013t193206.679d548-0ubuntu1
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.31-16.53-generic
  SourcePackage: network-manager
  Uname: Linux 2.6.31-16-generic x86_64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/495981/+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 1958060] Re: bash returns wrong variable value/call more proccesses?

2022-01-17 Thread Dark Archangel
Brian Murray (brian-murray)
It's tested other man on ubuntu 20.04 x64 and apple mac pro with m1 pro CPU.
GNU bash, version 5.1.16(1)-release (aarch64-apple-darwin21.1.0)
GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)
I will test it from lubuntu 20.04 x64 livecd and will add new results.

...
Tested on Lubuntu 20.04, results are the same.
https://sun9-21.userapi.com/impg/epKIlh1A6x-RtHgZ5EUERBK59vFYIAJcg_c3YQ/7iW2z_L1Ajc.jpg?size=1063x500=95=cae5f41c4a9a41ffc7d0ad65bde94db8=album

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

Title:
  bash returns wrong variable value/call more proccesses?

Status in bash package in Ubuntu:
  Incomplete

Bug description:
  Simple function gives different results when interpretator set in first 
string of script
  CHECKPROC()
  {
  i=$(ps aux | grep -c $0)
  ps aux | grep -c $0
  echo variable is $i
  sleep 10
  }
  CHECKPROC

  Expected
  In any conditions it will return same values, then will increments when other 
copies of script  will be found in proccesses list.

  Happened.
  We set interpretator with #!/bin/bash or #!/bin/sh in first string of script 
and runs multiple copies of script from one terminal with & after scriptname. 
It's returns "1" and "variable is 1" always.
  Without interpretator setup, when string #!/bin/bash or #!/bin/sh deleted.
  Run multiple copies scriptname.sh&
  On every iteration it returns right first value and "variable is $value+1"

  $scriptname.sh&
  2
  variable is 3
  $scriptname.sh&
  3
  variable is 4
  ...and so on.

  Without counting in first case it returns only string with grep, in
  second case -- one more string with different PID and script name when
  called from i=$(...) or i=`...`

  
  Ubuntu 14.04 x32, bash 4.3.11(1)-release
  Same results from other man on
  GNU bash, version 5.1.16(1)-release (aarch64-apple-darwin21.1.0)
  GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)

  
  lsb_release -rd
  Description:  Ubuntu 14.04.6 LTS
  Release:  14.04

  apt-cache policy bash
  bash:
Установлен: 4.3-7ubuntu1.7
Кандидат:   4.3-7ubuntu1.7
Таблица версий:
   4.3-7ubuntu1.8+esm1 0
 -32768 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main i386 
Packages
   *** 4.3-7ubuntu1.7 0
  500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
  100 /var/lib/dpkg/status
   4.3-6ubuntu1 0
  500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1958060/+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 1958060] Re: bash returns wrong variable value/call more proccesses?

2022-01-17 Thread Dark Archangel
Brian Murray (brian-murray)
It's tested other man on ubuntu 20.04 x64 and apple mac pro with m1 pro CPU.
GNU bash, version 5.1.16(1)-release (aarch64-apple-darwin21.1.0)
GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)
I will test it from lubuntu 20.04 x64 livecd and will add new results.

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

Title:
  bash returns wrong variable value/call more proccesses?

Status in bash package in Ubuntu:
  Incomplete

Bug description:
  Simple function gives different results when interpretator set in first 
string of script
  CHECKPROC()
  {
  i=$(ps aux | grep -c $0)
  ps aux | grep -c $0
  echo variable is $i
  sleep 10
  }
  CHECKPROC

  Expected
  In any conditions it will return same values, then will increments when other 
copies of script  will be found in proccesses list.

  Happened.
  We set interpretator with #!/bin/bash or #!/bin/sh in first string of script 
and runs multiple copies of script from one terminal with & after scriptname. 
It's returns "1" and "variable is 1" always.
  Without interpretator setup, when string #!/bin/bash or #!/bin/sh deleted.
  Run multiple copies scriptname.sh&
  On every iteration it returns right first value and "variable is $value+1"

  $scriptname.sh&
  2
  variable is 3
  $scriptname.sh&
  3
  variable is 4
  ...and so on.

  Without counting in first case it returns only string with grep, in
  second case -- one more string with different PID and script name when
  called from i=$(...) or i=`...`

  
  Ubuntu 14.04 x32, bash 4.3.11(1)-release
  Same results from other man on
  GNU bash, version 5.1.16(1)-release (aarch64-apple-darwin21.1.0)
  GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)

  
  lsb_release -rd
  Description:  Ubuntu 14.04.6 LTS
  Release:  14.04

  apt-cache policy bash
  bash:
Установлен: 4.3-7ubuntu1.7
Кандидат:   4.3-7ubuntu1.7
Таблица версий:
   4.3-7ubuntu1.8+esm1 0
 -32768 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main i386 
Packages
   *** 4.3-7ubuntu1.7 0
  500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
  100 /var/lib/dpkg/status
   4.3-6ubuntu1 0
  500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1958060/+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 1958148] [NEW] mkinitramfs is too slow

2022-01-17 Thread Heinrich Schuchardt
Public bug reported:

On the Nezha board creating an initrd takes more than 1 hour. The
compression level -19 for zstd is unwisely chosen.

Here are durations and compression results for an SiFive Unmatched board
with four cores using zstd:

-T0 -1 => 13.92s, 136298155 bytes
-T0 -2 => 15.73s, 131717830 bytes
-T0 -3 => 26.11s, 127434653 bytes
-T0 -4 => 29.31s, 126924540 bytes
-T0 -5 => 36.44s, 125296557 bytes
-T0 -6 => 39.36s, 124781669 bytes
-T0 -7 => 46.56s, 116200665 bytes
-T0 -8 => 51.95s, 113172941 bytes
-T0 -9 => 55.89s, 112835937 bytes
-T0 -10 => 61.32s, 108326876 bytes
-T0 -11 => 64.32s, 108115060 bytes
-T0 -12 => 76.37s, 108016478 bytes
-T0 -13 => 148.99s, 109121308 bytes
-T0 -14 => 156.58s, 108908574 bytes
-T0 -15 => 228.64s, 109213554 bytes
-T0 -16 => 380.26s, 107260643 bytes
-T0 -17 => 453.36s, 103679714 bytes
-T0 -18 => 714.79s, 100402249 bytes
-T0 -19 => 1046.58s, 100188713 bytes

Compression level between -2 to -10 offer a good compromise between CPU
time and compression results.

Ideally there would be a parameter that we could pass to mkinitfs. But
for as fast solution we should simply replace -19 by -9 in mkinitramfs.

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

Title:
  mkinitramfs is too slow

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  On the Nezha board creating an initrd takes more than 1 hour. The
  compression level -19 for zstd is unwisely chosen.

  Here are durations and compression results for an SiFive Unmatched
  board with four cores using zstd:

  -T0 -1 => 13.92s, 136298155 bytes
  -T0 -2 => 15.73s, 131717830 bytes
  -T0 -3 => 26.11s, 127434653 bytes
  -T0 -4 => 29.31s, 126924540 bytes
  -T0 -5 => 36.44s, 125296557 bytes
  -T0 -6 => 39.36s, 124781669 bytes
  -T0 -7 => 46.56s, 116200665 bytes
  -T0 -8 => 51.95s, 113172941 bytes
  -T0 -9 => 55.89s, 112835937 bytes
  -T0 -10 => 61.32s, 108326876 bytes
  -T0 -11 => 64.32s, 108115060 bytes
  -T0 -12 => 76.37s, 108016478 bytes
  -T0 -13 => 148.99s, 109121308 bytes
  -T0 -14 => 156.58s, 108908574 bytes
  -T0 -15 => 228.64s, 109213554 bytes
  -T0 -16 => 380.26s, 107260643 bytes
  -T0 -17 => 453.36s, 103679714 bytes
  -T0 -18 => 714.79s, 100402249 bytes
  -T0 -19 => 1046.58s, 100188713 bytes

  Compression level between -2 to -10 offer a good compromise between
  CPU time and compression results.

  Ideally there would be a parameter that we could pass to mkinitfs. But
  for as fast solution we should simply replace -19 by -9 in
  mkinitramfs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958148/+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 1958147] [NEW] Nvidia acceleration has gone

2022-01-17 Thread amias
Public bug reported:

since the last update my nvidia acceleration no longer works

This is the card
02:00.0 3D controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1)

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: xorg 1:7.7+22ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
Uname: Linux 5.13.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 17 15:20:30 2022
DistUpgraded: 2021-10-27 20:53:18,542 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: impish
DistroVariant: ubuntu
DkmsStatus:
 alsa-firewire, 4.4, 4.13.0-39-generic, x86_64: installed
 evdi, 1.2.58: added
ExtraDebuggingInterest: Yes
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:060d]
   Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
InstallationDate: Installed on 2016-08-29 (1967 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: Dell Inc. Dell Precision M3800
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet
SourcePackage: xorg
UpgradeStatus: Upgraded to impish on 2021-10-27 (81 days ago)
dmi.bios.date: 02/13/2018
dmi.bios.release: 65.11
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.asset.tag: AMIAS
dmi.board.name: Dell Precision M3800
dmi.board.vendor: Dell Inc.
dmi.board.version: A11
dmi.chassis.asset.tag: AMIAS
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd02/13/2018:br65.11:svnDellInc.:pnDellPrecisionM3800:pvrA11:rvnDellInc.:rnDellPrecisionM3800:rvrA11:cvnDellInc.:ct8:cvrNotSpecified:skuDellPrecisionM3800:
dmi.product.name: Dell Precision M3800
dmi.product.sku: Dell Precision M3800
dmi.product.version: A11
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.2-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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-2build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1

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


** Tags: amd64 apport-bug impish possible-manual-nvidia-install ubuntu 
wayland-session

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

Title:
  Nvidia acceleration has gone

Status in xorg package in Ubuntu:
  New

Bug description:
  since the last update my nvidia acceleration no longer works

  This is the card
  02:00.0 3D controller: NVIDIA Corporation GK107GLM [Quadro K1100M] (rev a1)

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog:
   
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 17 15:20:30 2022
  DistUpgraded: 2021-10-27 20:53:18,542 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  DkmsStatus:
   alsa-firewire, 4.4, 4.13.0-39-generic, x86_64: installed
   evdi, 1.2.58: added
  ExtraDebuggingInterest: Yes
  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:060d]
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:060d]
  InstallationDate: Installed on 2016-08-29 (1967 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Dell Precision M3800
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-25-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to impish on 2021-10-27 (81 days ago)
  dmi.bios.date: 02/13/2018
  dmi.bios.release: 65.11
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.asset.tag: AMIAS
  dmi.board.name: Dell Precision M3800
  dmi.board.vendor: Dell Inc.
  

[Touch-packages] [Bug 1958060] Re: bash returns wrong variable value/call more proccesses?

2022-01-17 Thread Brian Murray
Trusty is no longer a supported release of Ubuntu. Have you tested this
with a supported release of Ubuntu? If so what version of bash were you
using?

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

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

Title:
  bash returns wrong variable value/call more proccesses?

Status in bash package in Ubuntu:
  Incomplete

Bug description:
  Simple function gives different results when interpretator set in first 
string of script
  CHECKPROC()
  {
  i=$(ps aux | grep -c $0)
  ps aux | grep -c $0
  echo variable is $i
  sleep 10
  }
  CHECKPROC

  Expected
  In any conditions it will return same values, then will increments when other 
copies of script  will be found in proccesses list.

  Happened.
  We set interpretator with #!/bin/bash or #!/bin/sh in first string of script 
and runs multiple copies of script from one terminal with & after scriptname. 
It's returns "1" and "variable is 1" always.
  Without interpretator setup, when string #!/bin/bash or #!/bin/sh deleted.
  Run multiple copies scriptname.sh&
  On every iteration it returns right first value and "variable is $value+1"

  $scriptname.sh&
  2
  variable is 3
  $scriptname.sh&
  3
  variable is 4
  ...and so on.

  Without counting in first case it returns only string with grep, in
  second case -- one more string with different PID and script name when
  called from i=$(...) or i=`...`

  
  Ubuntu 14.04 x32, bash 4.3.11(1)-release
  Same results from other man on
  GNU bash, version 5.1.16(1)-release (aarch64-apple-darwin21.1.0)
  GNU bash, version 4.4.20(1)-release (x86_64-pc-linux-gnu)

  
  lsb_release -rd
  Description:  Ubuntu 14.04.6 LTS
  Release:  14.04

  apt-cache policy bash
  bash:
Установлен: 4.3-7ubuntu1.7
Кандидат:   4.3-7ubuntu1.7
Таблица версий:
   4.3-7ubuntu1.8+esm1 0
 -32768 https://esm.ubuntu.com/ubuntu/ trusty-infra-security/main i386 
Packages
   *** 4.3-7ubuntu1.7 0
  500 http://ru.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main i386 
Packages
  100 /var/lib/dpkg/status
   4.3-6ubuntu1 0
  500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1958060/+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 1958131] [NEW] Sync cpio 2.13+dfsg-7 (main) from Debian sid (main)

2022-01-17 Thread Heinrich Schuchardt
Public bug reported:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

 affects ubuntu/cpio
 status new
 importance wishlist
 subscribe ubuntu-sponsors
 done

Please sync cpio 2.13+dfsg-7 (main) from Debian sid (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * SECURITY UPDATE: arbitrary code execution via crafted pattern file
- debian/patches/CVE-2021-38185.patch: rewrite dynamic string support
  in src/copyin.c, src/copyout.c, src/copypass.c, src/dstring.c,
  src/dstring.h, src/util.c.
- debian/patches/CVE-2021-38185.2.patch: don't call ds_resize in a loop
  in src/dstring.c.
- debian/patches/CVE-2021-38185.3.patch: fix dynamic string
  reallocations in src/dstring.c.
- CVE-2021-38185
  * Back out CVE-2021-381185 patches for now as they appear to be causing a
regression when building the kernel
- debian/patches/CVE-2021-38185.patch: disabled
- debian/patches/CVE-2021-38185.2.patch: disabled
  * SECURITY UPDATE: arbitrary code execution via crafted pattern file
- debian/patches/CVE-2021-38185.2.patch: don't call ds_resize in a loop
  in src/dstring.c.
- CVE-2021-38185
  * SECURITY UPDATE: arbitrary code execution via crafted pattern file
- debian/patches/CVE-2021-38185.patch: rewrite dynamic string support
  in src/copyin.c, src/copyout.c, src/copypass.c, src/dstring.c,
  src/dstring.h, src/util.c.
- CVE-2021-38185

The code changes by the patch series in Ubuntu and Debian are the same.
The patches are just name differently:

d/992045-CVE-2021-38185-rewrite-dynamic-string-support 
u/patches/CVE-2021-38185.patch
d/992098-regression-of-orig-fix-for-CVE-2021-38185 u/CVE-2021-38185.2.patch
d/992192-Fix-dynamic-string-reallocations.patch u/patches/CVE-2021-38185.3.patch
-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEEK7wKXt3/btL6/yA+hO4vgnE3U0sFAmHlU6oACgkQhO4vgnE3
U0s83g//e0P9zbgAB77m0zHcBpyiAYrIDfaWHGGXOARuRd7T5GXrrYFEo1ldGSqy
eq9MrcQmFjEjy+0O7AGzmMVoQL0zyjze4OKIEb/8Hv2z9asyscJkI8zkTH7oO+Sg
GWER6yP66MCOvTCseGMdlrCWng93GAyJbJSOhVFh1t0Pssl3QJ3txPdNU5j6jKwS
b7NKnAMLvxBUHpftayFMHUtbZ/RpTzJavnQlperzN9W9OBbVccwSWwBJ3rjPoj1D
LOaXxeuWBDcHi9k7bB/HtDIitkQDvFSqCB0otn14F3I5BUCiM3xqT7kiGZAeP6TP
jny3IElHXDdepZOjqZ+UTJ0oTldKxRErz3XXWl32gVB0dOUgF7GgSoPSKckCp5hG
P7f7stsc3Cout+jo88AUEDmsV9GX5kLLGFfC8kGlXnIS9S7lH+yd1xfNd6WmZkyd
79pZAXZXAO/wrcD+g2U4OaD5a+LPYDxul6aA2l8hykN9OcN5Q+/F/r5DT2Oa4GeV
vCvpbXrs+WGOPfU50qwofB0lhBScsHZ9Yuga6l3VWBrFnbgT0G1ceYqc5X/ym4is
fTEBCthtTq7mDVzuSCGe21Ar4TwQtSPhwCu5RRLphmkIREFbFhBLDzSS8wQyyz2V
OJuv38UGAmhOMajhmt504BBb/ssMf5ItdRX1+imF0MTQrX4YSbg=
=2bpu
-END PGP SIGNATURE-

** Affects: cpio (Ubuntu)
 Importance: Wishlist
 Status: New

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

Title:
  Sync cpio 2.13+dfsg-7 (main) from Debian sid (main)

Status in cpio package in Ubuntu:
  New

Bug description:
  -BEGIN PGP SIGNED MESSAGE-
  Hash: SHA256

   affects ubuntu/cpio
   status new
   importance wishlist
   subscribe ubuntu-sponsors
   done

  Please sync cpio 2.13+dfsg-7 (main) from Debian sid (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* SECURITY UPDATE: arbitrary code execution via crafted pattern file
  - debian/patches/CVE-2021-38185.patch: rewrite dynamic string support
in src/copyin.c, src/copyout.c, src/copypass.c, src/dstring.c,
src/dstring.h, src/util.c.
  - debian/patches/CVE-2021-38185.2.patch: don't call ds_resize in a loop
in src/dstring.c.
  - debian/patches/CVE-2021-38185.3.patch: fix dynamic string
reallocations in src/dstring.c.
  - CVE-2021-38185
* Back out CVE-2021-381185 patches for now as they appear to be causing a
  regression when building the kernel
  - debian/patches/CVE-2021-38185.patch: disabled
  - debian/patches/CVE-2021-38185.2.patch: disabled
* SECURITY UPDATE: arbitrary code execution via crafted pattern file
  - debian/patches/CVE-2021-38185.2.patch: don't call ds_resize in a loop
in src/dstring.c.
  - CVE-2021-38185
* SECURITY UPDATE: arbitrary code execution via crafted pattern file
  - debian/patches/CVE-2021-38185.patch: rewrite dynamic string support
in src/copyin.c, src/copyout.c, src/copypass.c, src/dstring.c,
src/dstring.h, src/util.c.
  - CVE-2021-38185

  The code changes by the patch series in Ubuntu and Debian are the same.
  The patches are just name differently:

  d/992045-CVE-2021-38185-rewrite-dynamic-string-support 
u/patches/CVE-2021-38185.patch
  d/992098-regression-of-orig-fix-for-CVE-2021-38185 u/CVE-2021-38185.2.patch
  d/992192-Fix-dynamic-string-reallocations.patch 
u/patches/CVE-2021-38185.3.patch
  -BEGIN PGP SIGNATURE-

  iQIzBAEBCAAdFiEEK7wKXt3/btL6/yA+hO4vgnE3U0sFAmHlU6oACgkQhO4vgnE3
  U0s83g//e0P9zbgAB77m0zHcBpyiAYrIDfaWHGGXOARuRd7T5GXrrYFEo1ldGSqy
  

[Touch-packages] [Bug 1956831] Re: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-01-17 Thread Anders
Thank you Brian for getting back.

The problem was indeed that /boot was full -  after cleaning it up
manually the upgrade went through. Since I know that /boot is a problem
with updates, I did clean it before doing the upgrade, but apparently
not enough.

The installation was done long ago (7 years according to the status
dump) and I think it was from a bootable USB stick with online download
of packages. I've never made a reinstall for these years - just upgraded
multiple times.

To me, this problem is solved and it the ticket can be closed. When I
looked it up I found multiple similar bug reports, but for older
versions. So I did send in the auto-report to inform that it occurs in
this version too and hope it could help with clues on what causes the
crash to the upgrade.

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

Title:
  package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  Happened during do-release-upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 4.15.0-166.174-generic 4.15.18
  Uname: Linux 4.15.0-166-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jan  8 18:54:36 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-10-04 (2288 days ago)
  InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 
(20150805)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2022-01-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1956831/+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 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.

2022-01-17 Thread Lars Melin
There are 2 usable configurations in 12d1:15c1, cfg#2 which is cdc_ether
and cfg#3 which is cdc_mbim , usb_modeswitch will select the linux
preferred mbim configuration if mbim drivers are present in the kernel.
This is by design and not a bug.

A user who prefers cdc_ether can disable the the automagic mbim switch
by changing the line DisableMBIMGlobal=0 to DisableMBIMGlobal=1 in
/etc/usb_modeswitch.conf, there is really no need to revert to an older
usb_modeswitch version in order to disable the mbim auto selection.

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

Title:
  The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work
  after install Ubuntu Hirsute.

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  u@u-ThinkPad-L460:~$ uname -a
  Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 
20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  u@u-ThinkPad-L460:~$ cat /etc/issue
  Ubuntu 21.04 \n \l

  CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module

  [Steps]
  1. Make a Live CD for Ubuntu Hirsute
  2. Plug in the Live CD
  3. Boot ThinkPad L460
  4. Install Ubuntu Hirsute and completed all configurations
  5. Make sure the installation done
  6. Boot the system and log in
  7. Enable the proposed channel
  8. Do the update and upgrade
  9. Reboot the system and check mmcli is upgraded to 1.16.6
  7. Verify the WWAN working or not.

  [Actual result]
  The WWAN can not be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.16
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Wed Aug 18 01:32:17 2021
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 
   10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.30.0-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940377/+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 1956147] Re: bluetooth: Google Nest not working

2022-01-17 Thread Paul Menzel
The system was updated from Ubuntu 20.04 to 21.10, but it’s still not
working out of the box without the script `a2dp.py`.

I am not able to work more on the issue, as I do not have the
environment, but maybe Canonical and Google should work more closely
together on the QA side.

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

Title:
  bluetooth: Google Nest not working

Status in gnome-bluetooth package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Connect a Google Nest to a ASUS laptop running Ubuntu 20.04, the
  devices pair, and *Office Speaker* shows up as an output device in the
  *Sound* settings, but no sound is heard (also doing the speaker test).

  In Debian sid/unstable with GNOME Shell 41.2 and *gnome-bluetooth*
  3.34.5-4, there is one more row in the audio settings allowing to set
  up some codecs. After changing that around, it finally works.

  Ubuntu probably needs something similar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/1956147/+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 1958127] [NEW] jammy:armhf assertion fail ../../bfd/elf32-arm.c:14759

2022-01-17 Thread Paolo Pisati
Public bug reported:

While running glibc autopkgtsts, ld assertion fail like this:

arm-linux-gnueabihf-gcc-10   -shared -static-libgcc  
-Wl,-dynamic-linker=/lib/ld-linux-armhf.so.3 -Wl,-z,defs 
-B/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/csu/  
-Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both  
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/math 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/dlfcn 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nss 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nis 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/rt 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/resolv 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/mathvec 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/support 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nptl 
-Wl,-rpath-link=/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/math:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/dlfcn:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nss:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nis:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/rt:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/resolv:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/mathvec:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/support:/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nptl
 -o 
/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf/sotruss-lib.so  
/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/csu/abi-note.o 
-Wl,--as-needed 
/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf/sotruss-lib.os  
-Wl,--no-as-needed -Wl,--start-group 
/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/libc.so 
/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/libc_nonshared.a 
-Wl,--as-needed 
/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf/ld.so 
-Wl,--no-as-needed -Wl,--end-group
mv -f 
/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf/ld-linux-armhf.so.3.new
 
/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf/ld-linux-armhf.so.3
/usr/bin/ld: BFD (GNU Binutils for Ubuntu) 2.37 assertion fail 
../../bfd/elf32-arm.c:14759
collect2: error: ld returned 1 exit status

Full log here: https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-
canonical-kernel-team-
bootstrap/jammy/armhf/g/glibc/20220114_114517_661dd@/log.gz

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

** Affects: binutils (Ubuntu Jammy)
 Importance: Undecided
 Status: New

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

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

Title:
  jammy:armhf assertion fail ../../bfd/elf32-arm.c:14759

Status in binutils package in Ubuntu:
  New
Status in binutils source package in Jammy:
  New

Bug description:
  While running glibc autopkgtsts, ld assertion fail like this:

  arm-linux-gnueabihf-gcc-10   -shared -static-libgcc  
-Wl,-dynamic-linker=/lib/ld-linux-armhf.so.3 -Wl,-z,defs 
-B/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/csu/  
-Wl,-z,combreloc -Wl,-z,relro -Wl,--hash-style=both  
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/math 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/elf 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/dlfcn 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nss 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nis 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/rt 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/resolv 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/mathvec 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/support 
-L/tmp/autopkgtest.yv4Uj8/build.WNF/src/build-tree/armhf-libc/nptl 

[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

2022-01-17 Thread jeremyszu
** Changed in: oem-priority
   Status: Confirmed => Triaged

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Focal:
  New
Status in systemd source package in Impish:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+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 1940377] Re: The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work after install Ubuntu Hirsute.

2022-01-17 Thread Rex Tsai
** Tags added: oem-priority

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

Title:
  The WWAN - Huawei Technologies Co., Ltd. [12d1:15c1] does not work
  after install Ubuntu Hirsute.

Status in OEM Priority Project:
  New
Status in linux package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Confirmed
Status in usb-modeswitch package in Ubuntu:
  Confirmed

Bug description:
  u@u-ThinkPad-L460:~$ uname -a
  Linux u-ThinkPad-L460 Kernel 5.11.0-16-generic #17-Ubuntu SMP Wed Apr 14 
20:12:43 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

  u@u-ThinkPad-L460:~$ cat /etc/issue
  Ubuntu 21.04 \n \l

  CPU : Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  WWAN : 12d1:15c1 Huawei Technologies Co., Ltd. ME906s LTE M.2 Module

  [Steps]
  1. Make a Live CD for Ubuntu Hirsute
  2. Plug in the Live CD
  3. Boot ThinkPad L460
  4. Install Ubuntu Hirsute and completed all configurations
  5. Make sure the installation done
  6. Boot the system and log in
  7. Enable the proposed channel
  8. Do the update and upgrade
  9. Reboot the system and check mmcli is upgraded to 1.16.6
  7. Verify the WWAN working or not.

  [Actual result]
  The WWAN can not be detected.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.16
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  Date: Wed Aug 18 01:32:17 2021
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 21.04
  InstallationDate: Installed on 2021-08-18 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  IpRoute:
   default via 10.1.1.1 dev wlp3s0 proto dhcp metric 600 
   10.1.1.0/24 dev wlp3s0 proto kernel scope link src 10.1.1.106 metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.30.0-1ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Tags:  hirsute
  Uname: Linux 5.11.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1940377/+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