[Touch-packages] [Bug 2062950] [NEW] RE: Flickering problems on external monitor with HDMI after installing Ubuntu 23.10

[J K]

Public bug reported:

this is a continuation of the bug reported in
https://bugs.launchpad.net/ubuntu/+bug/2062504

I reinstalled ubuntu 23, and didn't install anything else. I'm still
having the flickering when connecting an HDMI to an external monitor.
please help

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: none
CloudName: none
CloudPlatform: none
CloudSubPlatform: config
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 19 22:27:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-20 (0 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic 
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug mantic 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/2062950

Title:
  RE: Flickering problems on external monitor with HDMI after installing
  Ubuntu 23.10

Status in xorg package in Ubuntu:
  New

Bug description:
  this is a continuation of the bug reported in
  https://bugs.launchpad.net/ubuntu/+bug/2062504

  I reinstalled ubuntu 23, and didn't install anything else. I'm still
  having the flickering when connecting an HDMI to an external monitor.
  please help

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-28.29-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 22:27:21 2024
  DistUpgraded: Fresh install
  DistroCodename: mantic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
  InstallationDate: Installed on 2024-04-20 (0 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-28-generic 
root=UUID=92611de2-ed0a-4611-b724-820a5d29be02 ro quiet splash 

[Touch-packages] [Bug 2062504] [NEW] Flickering problems on external monitor with HDMI after installing Ubuntu 23.10

[J K]

Public bug reported:

I just installed ubuntu 23.10 on my thinkpad L13. It works fine on my
laptop monitor. But when I connect an HDMI cable to my other monitor,
then the screen flickers on the laptop and nothing shows on the other
monitor

I know it can't be the problem with the other monitor as I bought it
brand new last week, and the cable works fine on this same laptop when I
run in windows, and it works fine on other laptops with windows/mac

I already installed the driver with `sudo apt install nvidia-driver-535
nvidia-dkms-535` and rebooted, but that didn't help. I then installed
driver 550 and I still have the flickering

This laptop uses an intel Alder Lake-UP3 GT2

I also tried editing `etc/default/grub` by adding 'nomodeset' or
'radeon.modeset=0' within the quotation marks in the line
GRUB_CMDLINE_LINUX_DEFAULT but that didn't help either

can anyone help?

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-27.28-generic 6.5.13
Uname: Linux 6.5.0-27-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 18 23:17:21 2024
DistUpgraded: Fresh install
DistroCodename: mantic
DistroVariant: ubuntu
DkmsStatus: nvidia/550.54.14, 6.5.0-27-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Alder Lake-UP3 GT2 [Iris Xe Graphics] [8086:46a8] (rev 0c) 
(prog-if 00 [VGA controller])
   Subsystem: Lenovo Alder Lake-UP3 GT2 [Iris Xe Graphics] [17aa:50a6]
InstallationDate: Installed on 2024-04-13 (6 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-27-generic 
root=UUID=bc80dc13-87d7-4310-bd10-43d45de6d3a7 ro quiet splash radeon.modeset=0 
vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/23/2024
dmi.bios.release: 1.23
dmi.bios.vendor: LENOVO
dmi.bios.version: R1UET46W (1.23 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21B4S4QB00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76465 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.14
dmi.modalias: 
dmi:bvnLENOVO:bvrR1UET46W(1.23):bd02/23/2024:br1.23:efr1.14:svnLENOVO:pn21B4S4QB00:pvrThinkPadL13Gen3:rvnLENOVO:rn21B4S4QB00:rvrSDK0T76465WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21B4_BU_Think_FM_ThinkPadL13Gen3:
dmi.product.family: ThinkPad L13 Gen 3
dmi.product.name: 21B4S4QB00
dmi.product.sku: LENOVO_MT_21B4_BU_Think_FM_ThinkPad L13 Gen 3
dmi.product.version: ThinkPad L13 Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120+git2404140851.1179ed~oibaf~m
version.libgl1-mesa-dri: libgl1-mesa-dri 24.1~git2404150600.4a1904~oibaf~m
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug mantic third-party-packages 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/2062504

Title:
  Flickering problems on external monitor with HDMI after installing
  Ubuntu 23.10

Status in xorg package in Ubuntu:
  New

Bug description:
  I just installed ubuntu 23.10 on my thinkpad L13. It works fine on my
  laptop monitor. But when I connect an HDMI cable to my other monitor,
  then the screen flickers on the laptop and nothing shows on the other
  monitor

  I know it can't be the problem with the other monitor as I bought it
  brand new last week, and the cable works fine on this same laptop when
  I run in windows, and it works fine on other laptops with windows/mac

  I already installed the driver with `sudo apt install nvidia-
  driver-535 nvidia-dkms-535` and rebooted, but that didn't help. I then
  installed driver 550 and I still have the flickering

  This laptop uses an intel Alder Lake-UP3 GT2

  I also tried editing `etc/default/grub` by adding 'nomodeset' or
  'radeon.modeset=0' within the quotation marks in the line
  GRUB_CMDLINE_LINUX_DEFAULT but that didn't help either

  can anyone help?

  ProblemType: Bug
  

[Touch-packages] [Bug 2030784] Re: Backport Intel's AVX512 patches on openssl 3.0

[Bun K Tan]

** Patch added: "001-vaes_gcm_avx512.patch"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2030784/+attachment/5754726/+files/001-vaes_gcm_avx512.patch

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

Title:
  Backport Intel's AVX512 patches on openssl 3.0

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  https://github.com/openssl/openssl/pull/14908

  https://github.com/openssl/openssl/pull/17239

  These should provide a nice performance bonus on recent CPUs, and the
  patches are fairly self-contained.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2030784/+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 2030784] Re: Backport Intel's AVX512 patches on openssl 3.0

[Bun K Tan]

Hello @adrien-n,

I had Dan Zimmerman take a look at this issue and found a solution.
This is what he shared:

Steps to reproduce:
---
Get Source and apply patch:
git clone https://git.launchpad.net/ubuntu/+source/openssl ubuntu_openssl
cd ubuntu_openssl
git checkout applied/ubuntu/devel
git apply 001-vaes_gcm_avx512.patch (See comment #11 for attachment)
This patch is essentially what is referred to as "[PATCH 2/2] AES-GCM enabled 
with AVX512 vAES and vPCLMULQDQ."
Build OpenSSL
./config --prefix=/tmp/ubuntu_openssl_install 
--openssldir=/tmp/ubuntu_openssl_install
make -j
make test
Note AES-GCM Test Failures
 
Steps to resolution:

Apply patch:
make clean
git apply 002-vaes_gcm_avx512_fix.patch
make -j
make test
Note AES-GCM Tests Pass
 
Solution:
-
The solution to the failed test cases comes from this merged OpenSSL Pull 
Request: Avoid having another copy of key schedule in PROV_GCM_CTX by t8m · 
Pull Request #22384 · openssl/openssl (github.com)
Direct application of this PR will fail due to the fact that the OpenSSL 
doesn't support SM4_GCM in v3.0.13.  So I made the edits by hand and created 
the patch file 002-vaes_gcm_avx512_fix.patch
 

** Patch added: "002-vaes_gcm_avx512_fix.patch"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2030784/+attachment/5754725/+files/002-vaes_gcm_avx512_fix.patch

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

Title:
  Backport Intel's AVX512 patches on openssl 3.0

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  https://github.com/openssl/openssl/pull/14908

  https://github.com/openssl/openssl/pull/17239

  These should provide a nice performance bonus on recent CPUs, and the
  patches are fairly self-contained.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2030784/+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 2046459] Re: systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting in boot failure

[Nils K]

This says fix commited though it seems to be neither available in
mantic-updates nor in noble? This is annoying as we have to resort to
installing 253.5-1ubuntu4 manually from the old repository archives and
prevent updates of it

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

Title:
  systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting
  in boot failure

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  I have my system set up to rely on GPT auto generator together with
  Discoverable Partitions Specification (DPS). After upgrading my system
  the gpt generator is no longer included resulting in boot failure.

  I have been able to workaround this by setting up the mounts in fstab but 
that is unsatisfactory.
  Furthermore I work on an embedded device which uses Ubuntu as a base and 
relies on the GPT auto generator. In this case it is not possible for me to 
switch back to an old fstab file as we rely on some autodiscovery possible only 
with DPS.

  Even though it is not used by the default installation, I kindly
  request to revert a366279a84730e92ed734710560ea833709f359d. Even
  though the default does not require it does not mean that no one else
  does. Also the generator binary fairly small at a few dozen KB so not
  much is gained from omitting it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046459/+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 2046459] [NEW] systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting in boot failure

[Nils K]

Public bug reported:

I have my system set up to rely on GPT auto generator together with
Discoverable Partitions Specification (DPS). After upgrading my system
the gpt generator is no longer included resulting in boot failure.

I have been able to workaround this by setting up the mounts in fstab but that 
is unsatisfactory.
Furthermore I work on an embedded device which uses Ubuntu as a base and relies 
on the GPT auto generator. In this case it is not possible for me to switch 
back to an old fstab file as we rely on some autodiscovery possible only with 
DPS.

Even though it is not used by the default installation, I kindly request
to revert a366279a84730e92ed734710560ea833709f359d. Even though the
default does not require it does not mean that no one else does. Also
the generator binary fairly small at a few dozen KB so not much is
gained from omitting it.

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


** Tags: regression

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

Title:
  systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting
  in boot failure

Status in systemd package in Ubuntu:
  New

Bug description:
  I have my system set up to rely on GPT auto generator together with
  Discoverable Partitions Specification (DPS). After upgrading my system
  the gpt generator is no longer included resulting in boot failure.

  I have been able to workaround this by setting up the mounts in fstab but 
that is unsatisfactory.
  Furthermore I work on an embedded device which uses Ubuntu as a base and 
relies on the GPT auto generator. In this case it is not possible for me to 
switch back to an old fstab file as we rely on some autodiscovery possible only 
with DPS.

  Even though it is not used by the default installation, I kindly
  request to revert a366279a84730e92ed734710560ea833709f359d. Even
  though the default does not require it does not mean that no one else
  does. Also the generator binary fairly small at a few dozen KB so not
  much is gained from omitting it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046459/+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 2030784] Re: Backport Intel's AVX512 patches on openssl 3.0

[Bun K Tan]

Hi @schopin,

Recommended way to test the relevant code paths would be to use OpenSSL’s 
Capability Bits Environment variable.  Notes below:
 
 
Ubuntu - OpenSSL OPENSSL_ia32cap Environment Variable
OpenSSL Environment variable processor feature bit disable combos for testing. 
https://www.openssl.org/docs/manmaster/man3/OPENSSL_ia32cap.html
 
 
* AES-GCM Relevant Feature Disable
 
   Disable VAES-NI
   $ export OPENSSL_ia32cap=:~0x200
 
   Disable VPCLMULQDQ
   $ export OPENSSL_ia32cap=:~0x400
 
   Disable AES-NI
   $ export OPENSSL_ia32cap=~0x200
 
   Disable AESNI + VAESNI
   $ export OPENSSL_ia32cap=~0x200:~0x200
 
 
* RSA 2K/3K/4K Sign Relevant Feature Disable
 
   Disable AVX512F
   $ export OPENSSL_ia32cap=:~0x1
 
   Disable AVX512VL
   $ export OPENSSL_ia32cap=:~0x8000
 
   Disable AVX512DQ
   $ export OPENSSL_ia32cap=:~0x2
 
   Disable AVX512IFMA
   $ export OPENSSL_ia32cap=:~0x20
 
 
* Unset any previous caps
$ unset OPENSSL_ia32cap
 
 
Examples:
   * AES-128-GCM | AES-256-GCM
  - Baseline - Requires VAES and VPCMULQDQ features present on ICX or newer 
platform.  This should be the most performant flow.
$ taskset -c 0 openssl speed -evp aes-128-gcm

  - Individual VAES Disabled and VPCLMULQDQ Disabled should fallback to AVX 
AESNI flow and should have equivalent performance
$ OPENSSL_ia32cap=:~0x200 taskset -c 0 openssl speed -evp 
aes-128-gcm
$ OPENSSL_ia32cap=:~0x400 taskset -c 0 openssl speed -evp 
aes-128-gcm

  - AESNI and VAESNI Disabled should fallback to 'C code' performance
$ OPENSSL_ia32cap=~0x200:~0x200 taskset -c 0 
openssl speed -evp aes-128-gcm
 
   * RSA 2K/3K/4K Sign Performance
  - Baseline - Requires AVX512F, AVX512VL, AVX512DQ, and AVX512IFMA 
features on ICX or newer platform. This should be the most performant flow.
$ taskset -c 0 openssl speed rsa2048 rsa3072 rsa4096

  - Individual  AVX512F, AVX512VL, and AVX512IFMA features should yield 
equivalent performance.  This flow will use the ADOX/ADCX/MULX RSA flow.
$ OPENSSL_ia32cap=:~0x1 taskset -c 0 openssl speed rsa2048 rsa3072 
rsa4096
$ OPENSSL_ia32cap=:~0x8000 taskset -c 0 openssl speed rsa2048 
rsa3072 rsa4096
$ OPENSSL_ia32cap=:~0x2 taskset -c 0 openssl speed rsa2048 rsa3072 
rsa4096
$ OPENSSL_ia32cap=:~0x20 taskset -c 0 openssl speed rsa2048 rsa3072 
rsa4096

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

Title:
  Backport Intel's AVX512 patches on openssl 3.0

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  https://github.com/openssl/openssl/pull/14908

  https://github.com/openssl/openssl/pull/17239

  These should provide a nice performance bonus on recent CPUs, and the
  patches are fairly self-contained.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2030784/+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 2025382] Re: 22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)

[Tim K.]

Running `sudo dhclient -6 ` appears to work, the problem
seems to be with the systemd-networkd DHCPv6 client.

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

Title:
  22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.2 LTS
  kernel 5.15.0-1038-oracle
  systemd 249.11-0ubuntu3.9

  After an update a couple weeks ago, Ubuntu 22.04 can no longer get
  IPv6 via DHCPv6 systemd-networkd, at least on Oracle OCI, but there
  are also other similar reports, e.g.

  https://ubuntuforums.org/showthread.php?t=2487465=14146758

  Oracle seems to be aware of the issue but they claim it's a Ubuntu
  22.04 bug:

  https://community.oracle.com/customerconnect/discussion/687610/oci-
  ipv6-address-not-assigned-to-oci-ubuntu-instance-by-dhcp

  The workaround to assign a static IPv6 is not great when managing
  multiple cloud instances.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2025382/+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 2025382] [NEW] 22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)

[Tim K.]

Public bug reported:

Ubuntu 22.04.2 LTS
kernel 5.15.0-1038-oracle
systemd 249.11-0ubuntu3.9

After an update a couple weeks ago, Ubuntu 22.04 can no longer get IPv6
via DHCPv6 systemd-networkd, at least on Oracle OCI, but there are also
other similar reports, e.g.

https://ubuntuforums.org/showthread.php?t=2487465=14146758

Oracle seems to be aware of the issue but they claim it's a Ubuntu 22.04
bug:

https://community.oracle.com/customerconnect/discussion/687610/oci-
ipv6-address-not-assigned-to-oci-ubuntu-instance-by-dhcp

The workaround to assign a static IPv6 is not great when managing
multiple cloud instances.

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

** Description changed:

+ Ubuntu 22.04.2 LTS
+ kernel 5.15.0-1038-oracle
+ systemd 249.11-0ubuntu3.9
+ 
  After an update a couple weeks ago, Ubuntu 22.04 can no longer get IPv6
  via DHCPv6 systemd-networkd, at least on Oracle OCI, but there are also
  other similar reports, e.g.
  
  https://ubuntuforums.org/showthread.php?t=2487465=14146758
  
  Oracle seems to be aware of the issue but they claim it's a Ubuntu 22.04
  bug:
  
  https://community.oracle.com/customerconnect/discussion/687610/oci-
  ipv6-address-not-assigned-to-oci-ubuntu-instance-by-dhcp
  
  The workaround to assign a static IPv6 is not great when managing
  multiple cloud instances.

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

Title:
  22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.2 LTS
  kernel 5.15.0-1038-oracle
  systemd 249.11-0ubuntu3.9

  After an update a couple weeks ago, Ubuntu 22.04 can no longer get
  IPv6 via DHCPv6 systemd-networkd, at least on Oracle OCI, but there
  are also other similar reports, e.g.

  https://ubuntuforums.org/showthread.php?t=2487465=14146758

  Oracle seems to be aware of the issue but they claim it's a Ubuntu
  22.04 bug:

  https://community.oracle.com/customerconnect/discussion/687610/oci-
  ipv6-address-not-assigned-to-oci-ubuntu-instance-by-dhcp

  The workaround to assign a static IPv6 is not great when managing
  multiple cloud instances.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2025382/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

I just removed my WF-1000XM4 from my device list and paired them again.
Now I have "High Fidelity Playback (A2DP Sink, codec LDAC)" and it was selected 
by default.

I have no idea what changed. bluez is still 5.64 since 2022-08-28. Maybe
it's related to the blueman update from 2.3.4 to 2.3.5 on 2023-01-19 or
some pipewire update on 2023-01-12.

These are my current bluez related packages:
bluez-alsa-utils/jammy 3.0.0-2 amd64
bluez-btsco/jammy 1:0.50-0ubuntu7 amd64
bluez-cups/jammy,now 5.64-0ubuntu1 amd64 [installed]
bluez-firmware/jammy,jammy 1.2-7 all
bluez-hcidump/jammy 5.64-0ubuntu1 amd64
bluez-hcidump/jammy 5.64-0ubuntu1 i386
bluez-meshd/jammy 5.64-0ubuntu1 amd64
bluez-meshd/jammy 5.64-0ubuntu1 i386
bluez-obexd/jammy,now 5.64-0ubuntu1 amd64 [installed]
bluez-obexd/jammy 5.64-0ubuntu1 i386
bluez-tests/jammy 5.64-0ubuntu1 amd64
bluez-tests/jammy 5.64-0ubuntu1 i386
bluez-tools/jammy,now 2.0~20170911.0.7cb788c-4 amd64 [installed]
bluez/jammy,now 5.64-0ubuntu1 amd64 [installed]
bluez/jammy 5.64-0ubuntu1 i386
libasound2-plugin-bluez/jammy 3.0.0-2 amd64
libkf5bluezqt-data/jammy,jammy 5.92.0-0ubuntu1 all
libkf5bluezqt-dev/jammy 5.92.0-0ubuntu1 amd64
libkf5bluezqt-doc/jammy,jammy 5.92.0-0ubuntu1 all
libkf5bluezqt6/jammy 5.92.0-0ubuntu1 amd64
python3-bluez/jammy 0.23-4build1 amd64
qml-module-org-kde-bluezqt/jammy 5.92.0-0ubuntu1 amd64

So it seems it's somehow unrelated to bluez 5.65

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Jammy:
  In Progress
Status in bluez source package in Kinetic:
  Fix Released
Status in bluez source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality.
  Probably other headphone types would be affected too.

  https://github.com/bluez/bluez/issues/313

  [ Test Plan ]

  No verifiable test case yet. Will ask the community for testing, and
  if it fails then consider reverting the fix.

  [ Where problems could occur ]

  The fix touches Bluetooth audio logic (only). So anything relating to
  Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest
  of bluetoothd which could suffer side effects.

  [ Other Info ]

  None provided.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

IIRC I tried to install it from source back then, but had missing build
dependencies (or versions) which were not in the package repositories. I
could be wrong, though.

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Jammy:
  In Progress
Status in bluez source package in Kinetic:
  Fix Released
Status in bluez source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality.
  Probably other headphone types would be affected too.

  https://github.com/bluez/bluez/issues/313

  [ Test Plan ]

  ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN

  [ Where problems could occur ]

  The fix touches Bluetooth audio logic (only). So anything relating to
  Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest
  of bluetoothd which could suffer side effects.

  [ Other Info ]

  None provided.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

Hmm, currently when connecting it via blueman it automatically connects with 
the last used profile. 
I just saw it says "High Fidelity Playback (A2DP sink, codec SBC-XQ)". So it 
seems to have A2DP there.
But as soon as I change my Mic Input Device to my headphones it changes to 
"Headset Head Unit (HSP/HFP codec mSBC)". If try to change the profile back to 
the A2DP sink my input device is also switched back to my internal Laptop Mic.

I'm not sure anymore if the A2DP sink was always there or if came back with a 
recent OS update (Linux Mint 21.1) - I'm also not sure if bluez 5.65 can fix 
this behavior.
Is there a more or less easy way I can test this on my machine? Maybe just 
clone it from the GitHub repo, checkout 5.65, compile and install it? Or do I 
need additional steps?

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Jammy:
  In Progress
Status in bluez source package in Kinetic:
  Fix Released
Status in bluez source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality.
  Probably other headphone types would be affected too.

  https://github.com/bluez/bluez/issues/313

  [ Test Plan ]

  ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN

  [ Where problems could occur ]

  The fix touches Bluetooth audio logic (only). So anything relating to
  Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest
  of bluetoothd which could suffer side effects.

  [ Other Info ]

  None provided.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

Hey @vanvugt, is there maybe any ETA?

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

  https://github.com/bluez/bluez/issues/313

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1999993] Re: The following packages have been kept back (ubuntu-wallpapers)

[Mike K.]

my 5 cents:
```
# apt list --upgradable
Listing... Done
ubuntu-wallpapers-kinetic/kinetic-updates,kinetic-updates 
22.10.2ubuntu1-0ubuntu1 all [upgradable from: 22.10.2-0ubuntu1]
ubuntu-wallpapers/kinetic-updates,kinetic-updates 22.10.2ubuntu1-0ubuntu1 all 
[upgradable from: 22.10.2-0ubuntu1]
```

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

Title:
  The following packages have been kept back (ubuntu-wallpapers)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  
  Ubuntu version: 22.10
  Version of the packages: 
  ubuntu-wallpapers: Installed: 22.10.2-0ubuntu1. Candidate:  
22.10.2ubuntu1-0ubuntu1
  ubuntu-wallpapers-kinetic: Installed: 22.10.2-0ubuntu1. Candidate:  
22.10.2ubuntu1-0ubuntu1

  
  What is expected to happen: upgrade packages via apt-get upgrade.

  What happened instead: packages not upgrading, with a message saying
  "the following packages have been kept back: ubuntu-wallpapers ubuntu-
  wallpapers-kinetic. apt-get install ubuntu-wallpapers ubuntu-
  wallpapers-kinetic or other workarounds don't work as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/193/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

Thanks, good to know :) At least you are listening :P

Do you know about any updates on this topic?

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

  https://github.com/bluez/bluez/issues/313

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1995730] [NEW] pulseaudio does not start automatically upon startup.

[Arjun K Shibu]

Public bug reported:

Recently updated to Ubuntu 22.10 from 22.04 LTS. (kernel - 5.19.0-23)

There is no sound output unless pulseaudio is started manually. No
output devices except dummy output, until pulseaudio is started.

pulseaudio is enabled but is inactive(dead) until it is started using
systemctl.

Tested on kernels 5.19.0-23 and 5.15.0-52 but does not work. pulseaudio
require manual startup.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: pulseaudio 1:16.1+dfsg1-1ubuntu3
ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
Uname: Linux 5.19.0-23-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov  4 20:00:12 2022
InstallationDate: Installed on 2022-05-16 (171 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to kinetic on 2022-11-04 (0 days ago)
dmi.bios.date: 07/16/2022
dmi.bios.release: 1.16
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.16.0
dmi.board.name: 0FNCYP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd07/16/2022:br1.16:svnDellInc.:pnInspiron155501:pvr:rvnDellInc.:rn0FNCYP:rvrA00:cvnDellInc.:ct10:cvr:sku09E9:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 15 5501
dmi.product.sku: 09E9
dmi.sys.vendor: Dell Inc.

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


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

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

Title:
  pulseaudio does not start automatically upon startup.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Recently updated to Ubuntu 22.10 from 22.04 LTS. (kernel - 5.19.0-23)

  There is no sound output unless pulseaudio is started manually. No
  output devices except dummy output, until pulseaudio is started.

  pulseaudio is enabled but is inactive(dead) until it is started using
  systemctl.

  Tested on kernels 5.19.0-23 and 5.15.0-52 but does not work.
  pulseaudio require manual startup.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pulseaudio 1:16.1+dfsg1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', 
'/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  4 20:00:12 2022
  InstallationDate: Installed on 2022-05-16 (171 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to kinetic on 2022-11-04 (0 days ago)
  dmi.bios.date: 07/16/2022
  dmi.bios.release: 1.16
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.16.0
  dmi.board.name: 0FNCYP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.16.0:bd07/16/2022:br1.16:svnDellInc.:pnInspiron155501:pvr:rvnDellInc.:rn0FNCYP:rvrA00:cvnDellInc.:ct10:cvr:sku09E9:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 5501
  dmi.product.sku: 09E9
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1995730/+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 1991781] Re: Black areas in gtk2 apps

[Vasiliy K]

** Description changed:

- Black areas appear in all gtk2 apps. For example in text fields. After a few 
mouse clicks, they may disappear, then reappear. You can see if you open any 
app based on gtk2. For example, darksnow.
- I have Ubuntu 22.04.1 LTS.libgtk2.0-0 version: 2.24.33-2ubuntu2
+ Black areas appear in all gtk2 apps. For example in text fields. After a
+ few mouse clicks, they may disappear, then reappear. You can see if you
+ open any app based on gtk2. For example, darksnow.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgtk2.0-0 2.24.33-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  5 13:34:02 2022
  InstallationDate: Installed on 2022-09-28 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: gtk+2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Black areas in gtk2 apps

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Black areas appear in all gtk2 apps. For example in text fields. After
  a few mouse clicks, they may disappear, then reappear. You can see if
  you open any app based on gtk2. For example, darksnow.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgtk2.0-0 2.24.33-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  5 13:34:02 2022
  InstallationDate: Installed on 2022-09-28 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: gtk+2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1991781/+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 1991781] [NEW] Black areas in gtk2 apps

[Vasiliy K]

Public bug reported:

Black areas appear in all gtk2 apps. For example in text fields. After a
few mouse clicks, they may disappear, then reappear. You can see if you
open any app based on gtk2. For example, darksnow.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libgtk2.0-0 2.24.33-2ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct  5 13:34:02 2022
InstallationDate: Installed on 2022-09-28 (6 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
SourcePackage: gtk+2.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Black areas in gtk2 apps

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Black areas appear in all gtk2 apps. For example in text fields. After
  a few mouse clicks, they may disappear, then reappear. You can see if
  you open any app based on gtk2. For example, darksnow.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgtk2.0-0 2.24.33-2ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  5 13:34:02 2022
  InstallationDate: Installed on 2022-09-28 (6 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  SourcePackage: gtk+2.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1991781/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

The empty blacklist.conf seems to have caused all this.

- CLOSE -

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

Might i have emptied or removed 
/etc/modprobe.d/blacklist.conf
by mistake? It was awfully empty!?

--- pre ---
# https://askubuntu.com/a/67028/289138

$ dpkg -S /etc/modprobe.d/blacklist.conf
kmod: /etc/modprobe.d/blacklist.conf

$ sudo apt install --reinstall -o 
Dpkg::Options::="--force-confask,confnew,confmiss" kmod
...
--- /pre ---

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

Might it be the case that I somehow removed or emptied
/etc/modprobe.d/blacklist.conf ?

--- pre ---
# https://askubuntu.com/a/67028/289138
$ dpkg -S /etc/modprobe.d/blacklist.conf
dpkg -S /etc/modprobe.d/blacklist.conf
$ sudo apt install --reinstall -o 
Dpkg::Options::="--force-confask,confnew,confmiss" kmod
--- /pre ---

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

$ journalctl --disk-usage 
Archived and active journals take up 624.0M in the file system.

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

https://bugs.launchpad.net/ubuntu/+source/module-init-tools/+bug/240553

$ sudo rmmod evbug
[sudo] password for hannu: 
$

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

Another attempt:

$ cat /etc/modprobe.d/blacklist_i2c-nvidia-gpu.conf 
# https://askubuntu.com/a/1289997
blacklist i2c_nvidia_gpu

Didn't make any difference.

My judgment is that this is NOT a hardware issue, a plain software one
indicated by:

As the flow of dmesg items ends; if I start tapping ESC ant Enter keys
repeatedly I will see the X / Wayland GUI Login screen within 10
seconds.

If i do NOT do that key-tapping, then the boot stop just prior to the login 
screen; screen is black, cursor flashing in upper left corner (at least to 
begin with), it stays like that indefinitely, after some time cooling fans 
start blowing - so there appears to be some CPU-intensive thing going on.
The only way out of this is holding the power button until power drops off.
Looking into the dmesg log, there is nothing after the 10 second mark.

What appears after 10 seconds on a tap-a-long-boot doesn't seem to be
related, the list isn't long and does not seem to contain any leads into
the issue.

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  

[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

Sadly, that wasn't it... still does the same (Only at start from "cold"?
is it?)

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

Current status:
$ grep hda /etc/modprobe.d/blacklist.conf 
blacklist snd_hda_codec_realtek


Seems to stop the problems.

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


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

[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

Oh, I DO have sound in the speakers, BT high def (A2DP) audio too...

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

$ lspci | grep -i audio
00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10)
01:00.1 Audio device: NVIDIA Corporation TU116 High Definition Audio Controller 
(rev a1)

*** Is there REALLY Realtek audio hardware in here too? 
*** or just a partly initialized driver due to the missing hardware?

Looks as that driver(?) in linux-modules-extra-(uname -r)...

$ apt-file find snd-hda-intel | grep $(uname -r)
linux-modules-extra-5.13.0-52-generic: 
/lib/modules/5.13.0-52-generic/kernel/sound/pci/hda/snd-hda-intel.ko

$ apt-file find snd-hda-intel | wc -l
576

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 

[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

$ cat /sys/class/sound/hwC0D0/vendor_name
Realtek

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

Hmm...

$ cat /sys/class/sound/hwC0D0/chip_name
ALC294

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G731GU
  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: 0.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G731GU_G731GU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1988658/+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 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

--- audio in the output of lshw ---

   *-multimedia
description: Audio device
product: TU116 High Definition Audio Controller
vendor: NVIDIA Corporation
physical id: 0.1
bus info: pci@:01:00.1
version: a1
width: 32 bits
clock: 33MHz
capabilities: pm msi pciexpress bus_master cap_list
configuration: driver=snd_hda_intel latency=0
resources: irq:17 memory:a508-a5083fff
---

*-multimedia
 description: Audio device
 product: Cannon Lake PCH cAVS
 vendor: Intel Corporation
 physical id: 1f.3
 bus info: pci@:00:1f.3
 version: 10
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi bus_master cap_list
 configuration: driver=snd_hda_intel latency=32
 resources: irq:150 memory:a5418000-a541bfff 
memory:a510-a51f
---

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   17.105681] rfkill: input handler disabled
  [   28.694324] Bluetooth: RFCOMM TTY layer initialized
  [   28.694328] Bluetooth: RFCOMM socket layer initialized
  [   28.694331] Bluetooth: RFCOMM ver 1.11
  [   28.922797] rfkill: input handler enabled
  [   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   31.907300] rfkill: input handler disabled
  [   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   78.940840] usb usb3: root hub lost power or was reset
  [   78.940841] usb usb4: root hub lost power or was reset
  [  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [  929.174669] usb usb3: root hub lost power or was reset
  [  929.174671] usb usb4: root hub lost power or was reset
  -- end ---

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-52-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: skip
  Date: Sun Sep  4 08:19:01 2022
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: G731GU.312
  

[Touch-packages] [Bug 1988658] Re: boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

--- seen in dmesg ---
[5.815777] Bluetooth: hci0: Firmware revision 0.1 build 26 week 11 2020
[5.881465] NET: Registered protocol family 38
[9.328954] wlo1: authenticate with 94:18:65:08:59:ae
[9.338666] wlo1: send auth to 94:18:65:08:59:ae (try 1/3)
[9.382307] wlo1: authenticated
[9.384831] wlo1: associate with 94:18:65:08:59:ae (try 1/3)
[9.389564] wlo1: RX AssocResp from 94:18:65:08:59:ae (capab=0x431 status=0 
aid=3)
[9.392938] wlo1: associated
[9.505267] IPv6: ADDRCONF(NETDEV_CHANGE): wlo1: link becomes ready
[   64.717314] snd_hda_intel :00:1f.3: couldn't bind with audio component
[   64.772851] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC294: 
line_outs=1 (0x17/0x0/0x0/0x0/0x0) type:speaker
[   64.772856] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
[   64.772858] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
[   64.772860] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
[   64.772862] snd_hda_codec_realtek hdaudioC0D0:inputs:
[   64.772863] snd_hda_codec_realtek hdaudioC0D0:  Headset Mic=0x19
[   64.772865] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12
[   65.227287] snd_hda_codec_hdmi hdaudioC0D2: No i915 binding for Intel 
HDMI/DP codec
[   65.231312] hdaudio hdaudioC0D2: Unable to configure, disabling
[   65.232125] input: HDA Intel PCH Headset Mic as 
/devices/pci:00/:00:1f.3/sound/card0/input21
[   65.232353] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1f.3/sound/card0/input22
[  481.066720] kauditd_printk_skb: 22 callbacks suppressed
[  481.066723] audit: type=1400 audit(1663175820.795:34): apparmor="DENIED" 
operation="capable" profile="/usr/sbin/cups-browsed" pid=2107 
comm="cups-browsed" capability=23  capname="sys_nice"
[  482.476639] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit
[  482.476642] usb usb3: root hub lost power or was reset
[  482.476643] usb usb4: root hub lost power or was reset
[  482.598315] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[  482.687635] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
[  484.946351] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[  485.054903] rfkill: input handler disabled
[  491.657064] Bluetooth: RFCOMM TTY layer initialized
[  491.657070] Bluetooth: RFCOMM socket layer initialized
[  491.657073] Bluetooth: RFCOMM ver 1.11
[  491.886727] rfkill: input handler enabled
[  492.013259] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[  493.174837] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[  493.434596] rfkill: input handler disabled

--- end of dmsg ---
" autoconfig for ALC294" =>

$ sudo lshw | grep ALC294 | wc -l
0
$
---
https://www.google.com/search?q=ALC294+%2Bg731 -> notably "g731" doesn't seem 
to be present in the google-search for ALC294 

https://www.google.com/search?q=%2BALC294+%2Bg731 => no match on g731

Why is there an attempt to initialize this non-existant hardware?

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal

  3 to 5 of 10 boot occasions stops prematurely.

  dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
  I have NOT investigated further (knowledge limit).

  This very latest bootup seemed to indicate that there is something
  waiting on the keyboard, as I got all the way "up" after beating
  repeatedly - alternating - on ESC and ENTER

  --- dmesg tail on this boot ---
  4 sec pause from previous line (at 9 secs)
  [   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, 
Reinit
  [   13.444031] usb usb3: root hub lost power or was reset
  [   13.444032] usb usb4: root hub lost power or was reset
  [   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
  [   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
  [   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
  [   

[Touch-packages] [Bug 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

Thanks for clarifying, that makes sense now.

Actually I just wanted to thank you, if there would be reactions to
comments that would be great for that. But as I'm writing this comment
now I got one other question: In the sidebar I see many people being
listed under "May be notified". And I'm very sorry if all people listed
there now receive an email because of this comment,  I'm already feeling
a bit guilty writing it just because I wanted to thank Daniel. But what
does "May be notified" mean? Are there going emails out to everyone
there?

Edit: Is there maybe a "Getting Started with Launchpad", maybe even
specific to Ubuntu?

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

  https://github.com/bluez/bluez/issues/313

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

But now it looks like a fix is released, no? Sorry, I'm still new to
launchpad and not everything is obvious to me yet.

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

  https://github.com/bluez/bluez/issues/313

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

@vanvugt Thank you very much for opening this bug and everyone else for
the quick fix!

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Jammy:
  Triaged

Bug description:
  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

  https://github.com/bluez/bluez/issues/313

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1888004] Re: Bash crashed with exit code 2 after a makefile script ended up with make saying "Clang - no input files"

[Seija K.]

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1888004/+attachment/5393623/+files/Dependencies.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1888004/+attachment/5393624/+files/ProcCpuinfoMinimal.txt

** Information type changed from Public to Private

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

Title:
  Bash crashed with exit code 2 after a makefile script ended up with
  make saying "Clang - no input files"

Status in bash package in Ubuntu:
  New

Bug description:
  Immediately after I ran the build script in bash in vscode, the moment
  the "clang - no input files" error appeared, bash crashed with an exit
  code of 2.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bash 5.0-6ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Unity
  Date: Fri Jul 17 14:30:11 2020
  InstallationDate: Installed on 2020-07-06 (10 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1888004/+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 1988658] [NEW] boot stops at black screen (blinking cursor in top left corner); pulseaudio fails to intialize?

[Hannu E K N]

Public bug reported:

$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="20.04.5 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.5 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal

3 to 5 of 10 boot occasions stops prematurely.

dmesg (included here, I assume)  indicates a pulseaudio failure stopping the 
booting.
I have NOT investigated further (knowledge limit).

This very latest bootup seemed to indicate that there is something
waiting on the keyboard, as I got all the way "up" after beating
repeatedly - alternating - on ESC and ENTER

--- dmesg tail on this boot ---
4 sec pause from previous line (at 9 secs)
[   13.444028] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit
[   13.444031] usb usb3: root hub lost power or was reset
[   13.444032] usb usb4: root hub lost power or was reset
[   13.557170] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[   13.791732] ACPI Warning: \_SB.PCI0.PEG0.PEGP._DSM: Argument #4 type 
mismatch - Found [Buffer], ACPI requires [Package] (20210331/nsarguments-61)
[   17.001076] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[   17.105681] rfkill: input handler disabled
[   28.694324] Bluetooth: RFCOMM TTY layer initialized
[   28.694328] Bluetooth: RFCOMM socket layer initialized
[   28.694331] Bluetooth: RFCOMM ver 1.11
[   28.922797] rfkill: input handler enabled
[   29.043050] Lockdown: Xorg: raw io port access is restricted; see man 
kernel_lockdown.7
[   31.669031] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[   31.907300] rfkill: input handler disabled
[   41.959736] Lockdown: systemd-logind: hibernation is restricted; see man 
kernel_lockdown.7
[   78.940836] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit
[   78.940840] usb usb3: root hub lost power or was reset
[   78.940841] usb usb4: root hub lost power or was reset
[  929.174665] xhci_hcd :01:00.2: xHC error in resume, USBSTS 0x401, Reinit
[  929.174669] usb usb3: root hub lost power or was reset
[  929.174671] usb usb4: root hub lost power or was reset
-- end ---

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.13
ProcVersionSignature: Ubuntu 5.13.0-52.59~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-52-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CasperMD5CheckResult: skip
Date: Sun Sep  4 08:19:01 2022
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/19/2021
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G731GU.312
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G731GU
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: 0.6
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrG731GU.312:bd02/19/2021:br5.13:efr0.6:svnASUSTeKCOMPUTERINC.:pnROGStrixG731GU_G731GU:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG731GU:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ROG Strix
dmi.product.name: ROG Strix G731GU_G731GU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug focal

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

Title:
  boot stops at black screen (blinking cursor in top left corner);
  pulseaudio fails to intialize?

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.5 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.5 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=focal
  

[Touch-packages] [Bug 1982739] Re: BlueZ 5.65 release

[Rafael K.]

Will this also be released for jammy soon?

I'm running into this issue which should be fixed with 5.65:
https://github.com/bluez/bluez/issues/313

** Bug watch added: github.com/bluez/bluez/issues #313
   https://github.com/bluez/bluez/issues/313

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

Title:
  BlueZ 5.65 release

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.65 to kinetic:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1982739/+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 1477584] Re: package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Pavan K]

Please close the ticket. I have not seen the issue in later versions of
Ubuntu.

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

Title:
  package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in rsyslog package in Ubuntu:
  Incomplete

Bug description:
  Identified the issue after upgrade to 15.04 from 14.04

  ProblemType: Package
  DistroRelease: Ubuntu 15.04
  Package: rsyslog 7.4.4-1ubuntu14
  ProcVersionSignature: Ubuntu 3.16.0-43.58-generic 3.16.7-ckt13
  Uname: Linux 3.16.0-43-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  Date: Thu Jul 23 14:34:45 2015
  DuplicateSignature: package:rsyslog:7.4.4-1ubuntu14:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-07-12 (11 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.17.25ubuntu1
   apt  1.0.9.7ubuntu4
  SourcePackage: rsyslog
  Title: package rsyslog 7.4.4-1ubuntu14 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1477584/+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 1948752] Re: apparmor is logging too many messages

[D-nl-k]

Unfortunately that didn't made any change. My
/etc/apparmor.d/usr.bin.redshift now looks like follows.

/usr/bin/redshift {

  dbus send bus="system" 
path="/org/freedesktop/DBus"
interface="org.freedesktop.DBus"
member="{GetNameOwner,StartServiceByName,AddMatch}",

  dbus send bus="system" 
path="/org/freedesktop/GeoClue2/Manager"
interface="org.freedesktop.DBus.Properties" 
member="GetAll",

  dbus send bus="system" 
path="/org/freedesktop/GeoClue2/Manager"
interface="org.freedesktop.GeoClue2.Manager" 
member="GetClient",


  # Allow but log any other dbus activity
  audit dbus bus=system,

  owner @{HOME}/.config/redshift.conf r,
  owner /run/user/*/redshift-shared-* rw,
}

(The last three lines where already in that file)
still tons of messages like this one:

[Do Jun  9 23:15:47 2022] audit: type=1420 audit(1654809348.128:59832): 
subj_apparmor=unconfined
[Do Jun  9 23:15:47 2022] audit: type=1107 audit(1654809348.128:59833): pid=977 
uid=103 auid=4294967295 ses=4294967295 subj=? msg='apparmor="ALLOWED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/DBus" 
interface="org.freedesktop.DBus" member="StartServiceByName" mask="send" 
name="org.freedesktop.DBus" pid=158627 label="/usr/bin/redshift" 
peer_label="unconfined"
   exe="/usr/bin/dbus-daemon" sauid=103 hostname=? 
addr=? terminal=?'
[Do Jun  9 23:15:47 2022] audit: type=1420 audit(1654809348.128:59834): 
subj_apparmor=unconfined

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

Title:
  apparmor is logging too many messages

Status in Redshift:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Unfortunately, this bug does not seem to be fixed yet.
  My syslog is flooded with ALLOWED messages regarding redshift.

  My system is a Kubuntu 21.04.
  AppArmor is V. 3.0.0-0ubuntu7.1

  Attached you'll find an excerpt from /var/log/syslog for the last 5
  minutes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/redshift/+bug/1948752/+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 1948752] Re: apparmor is logging too many messages

[D-nl-k]

Which would be?

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

Title:
  apparmor is logging too many messages

Status in Redshift:
  New
Status in apparmor package in Ubuntu:
  New

Bug description:
  Unfortunately, this bug does not seem to be fixed yet.
  My syslog is flooded with ALLOWED messages regarding redshift.

  My system is a Kubuntu 21.04.
  AppArmor is V. 3.0.0-0ubuntu7.1

  Attached you'll find an excerpt from /var/log/syslog for the last 5
  minutes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/redshift/+bug/1948752/+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 1976567] [NEW] Desktop scaling was set incorrectly until I booted up the PC AFTER turning on the monitor

[Seija K.]

Public bug reported:

Whenever I boot up my PC, I turn on the monitor as well. When this
happens, the Intel Mesa graphics loads, and my screen ends up being
small with large pixelated icons. The resolution was capped at 1024x768.
Only after I reboot my PC multiple times without changing the display
settings did the resolution increase to 1680x1050, the correct
resolution.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
Uname: Linux 5.15.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun  1 21:07:53 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0589]
InstallationDate: Installed on 2022-05-22 (10 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Gateway DX4860
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.15.0-33-generic 
root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/01/2011
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P02-A1
dmi.board.name: IPISB-VR
dmi.board.vendor: Gateway
dmi.board.version: 1.01
dmi.chassis.type: 3
dmi.chassis.vendor: Gateway
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:br4.6:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:sku:
dmi.product.family: Gateway Desktop
dmi.product.name: DX4860
dmi.sys.vendor: Gateway
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy resolution 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/1976567

Title:
  Desktop scaling was set incorrectly until I booted up the PC AFTER
  turning on the monitor

Status in xorg package in Ubuntu:
  New

Bug description:
  Whenever I boot up my PC, I turn on the monitor as well. When this
  happens, the Intel Mesa graphics loads, and my screen ends up being
  small with large pixelated icons. The resolution was capped at
  1024x768. Only after I reboot my PC multiple times without changing
  the display settings did the resolution increase to 1680x1050, the
  correct resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  1 21:07:53 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0589]
  InstallationDate: Installed on 2022-05-22 (10 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Gateway DX4860
  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.15.0-33-generic 
root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 

[Touch-packages] [Bug 1967565] Re: upower takes long time to detect laptop AC charger plugged in

[Balanarayan K]

Hi,

upower 0.99.18 version contains the fix for this. Are there plans to
integrate this version to Ubuntu 20.04?

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

Title:
  upower takes long time to detect laptop AC charger plugged in

Status in Upower:
  Fix Released
Status in upower package in Ubuntu:
  Triaged

Bug description:
  upower takes a really long time (around 1-2 minutes) to detect when an AC 
charger is plugged-in.
  'upower -d' shows battery state as discharging after AC charger is plugged-in.
  'systemctl restart upower.service' would update the status immediately as 
charging. Otherwise, it takes 1-2 minutes before upower updates the status.

  Laptop Model: Acer Aspire E15 E5-573G-56JN

  Laptop battery and AC charger is not faulty as the
  charging/discharging status gets correctly detected when using Windows
  10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: upower 0.99.11-1build2
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  1 23:07:12 2022
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1967565/+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 1966849] Re: gzip exec format error under WSL1

[Joerg-k]

Just realized that my 22.04 installation was still running in WSL1... No
more error after switching to WSL2.

** Summary changed:

- gzip exec format error under WSL
+ gzip exec format error under WSL1

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

Title:
  gzip exec format error under WSL1

Status in gzip:
  New
Status in gzip package in Ubuntu:
  Confirmed

Bug description:
  gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows
  19044.1620, making WSL pretty much unusable.

  bash: /usr/bin/gzip: cannot execute binary file: Exec format error

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gzip 1.10-4ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35
  Uname: Linux 4.4.0-19041-Microsoft x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Mar 29 06:40:33 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gzip
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gzip/+bug/1966849/+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 1970105] Re: Date gives back wrong second count, 3600 seconds off

[Hannu E K N]

Corrected output:

$ echo $(( 3600 + $(date +%s -d'1970-01-01 00:02:18') ))

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

Title:
  Date gives back wrong second count, 3600 seconds off

Status in coreutils package in Ubuntu:
  New

Bug description:
  In my opinion, the required '1970-01-01 **01**:02:18' below is wrong.
  The answer should be 3600 more seconds.

  Note: **02:18 is 138 seconds.**


  
  $ man date
  ...
  %s seconds since 1970-01-01 00:00:00 UTC
  ...

  $ date +%s -d'1970-01-01 01:02:18'
  138

  $ date --version
  date (GNU coreutils) 8.30
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
.
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by David MacKenzie.

  $

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: coreutils 8.30-3ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 15:12:14 2022
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1970105/+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 1970105] [NEW] Date gives back wrong second count, 3600 seconds off

[Hannu E K N]

Public bug reported:

In my opinion, the required '1970-01-01 **01**:02:18' below is wrong.
The answer should be 3600 more seconds.

Note: **02:18 is 138 seconds.**


$ man date
...
%s seconds since 1970-01-01 00:00:00 UTC
...

$ date +%s -d'1970-01-01 01:02:18'
138

$ date --version
date (GNU coreutils) 8.30
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later .
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David MacKenzie.

$

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: coreutils 8.30-3ubuntu2
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 24 15:12:14 2022
SourcePackage: coreutils
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Date gives back wrong second count, 3600 seconds off

Status in coreutils package in Ubuntu:
  New

Bug description:
  In my opinion, the required '1970-01-01 **01**:02:18' below is wrong.
  The answer should be 3600 more seconds.

  Note: **02:18 is 138 seconds.**


  
  $ man date
  ...
  %s seconds since 1970-01-01 00:00:00 UTC
  ...

  $ date +%s -d'1970-01-01 01:02:18'
  138

  $ date --version
  date (GNU coreutils) 8.30
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
.
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by David MacKenzie.

  $

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: coreutils 8.30-3ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 24 15:12:14 2022
  SourcePackage: coreutils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1970105/+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 1967565] Re: upower takes long time to detect laptop AC charger plugged in

[Balanarayan K]

Thank you for your suggestion. I have reported the issue upstream here:  
https://gitlab.freedesktop.org/upower/upower/-/issues/179  

** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #179
   https://gitlab.freedesktop.org/upower/upower/-/issues/179

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

Title:
  upower takes long time to detect laptop AC charger plugged in

Status in upower package in Ubuntu:
  New

Bug description:
  upower takes a really long time (around 1-2 minutes) to detect when an AC 
charger is plugged-in.
  'upower -d' shows battery state as discharging after AC charger is plugged-in.
  'systemctl restart upower.service' would update the status immediately as 
charging. Otherwise, it takes 1-2 minutes before upower updates the status.

  Laptop Model: Acer Aspire E15 E5-573G-56JN

  Laptop battery and AC charger is not faulty as the
  charging/discharging status gets correctly detected when using Windows
  10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: upower 0.99.11-1build2
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  1 23:07:12 2022
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1967565/+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 1967565] [NEW] upower takes long time to detect laptop AC charger plugged in

[Balanarayan K]

Public bug reported:

upower takes a really long time (around 1-2 minutes) to detect when an AC 
charger is plugged-in.
'upower -d' shows battery state as discharging after AC charger is plugged-in.
'systemctl restart upower.service' would update the status immediately as 
charging. Otherwise, it takes 1-2 minutes before upower updates the status.

Laptop Model: Acer Aspire E15 E5-573G-56JN

Laptop battery and AC charger is not faulty as the charging/discharging
status gets correctly detected when using Windows 10.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: upower 0.99.11-1build2
ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Apr  1 23:07:12 2022
ExecutablePath: /usr/lib/upower/upowerd
InstallationDate: Installed on 2022-04-01 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
ProcEnviron:
 LANG=en_IN
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
SourcePackage: upower
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal upower

** Attachment added: "upower_incorrect_discharging.txt"
   
https://bugs.launchpad.net/bugs/1967565/+attachment/5575774/+files/upower_incorrect_discharging.txt

** Description changed:

- upower takes a really long time (around 1-2 minutes) to detect when an AC 
charger is plugged-in. 
+ upower takes a really long time (around 1-2 minutes) to detect when an AC 
charger is plugged-in.
  'upower -d' shows battery state as discharging after AC charger is plugged-in.
  'systemctl restart upower.service' would update the status immediately as 
charging. Otherwise, it takes 1-2 minutes before upower updates the status.
  
- Distro: Ubuntu 20.04.4
  Laptop Model: Acer Aspire E15 E5-573G-56JN
  
  Laptop battery and AC charger is not faulty as the charging/discharging
  status gets correctly detected when using Windows 10.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: upower 0.99.11-1build2
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  1 23:07:12 2022
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
-  LANG=en_IN
-  LANGUAGE=en_IN:en
-  PATH=(custom, no user)
+  LANG=en_IN
+  LANGUAGE=en_IN:en
+  PATH=(custom, no user)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  upower takes long time to detect laptop AC charger plugged in

Status in upower package in Ubuntu:
  New

Bug description:
  upower takes a really long time (around 1-2 minutes) to detect when an AC 
charger is plugged-in.
  'upower -d' shows battery state as discharging after AC charger is plugged-in.
  'systemctl restart upower.service' would update the status immediately as 
charging. Otherwise, it takes 1-2 minutes before upower updates the status.

  Laptop Model: Acer Aspire E15 E5-573G-56JN

  Laptop battery and AC charger is not faulty as the
  charging/discharging status gets correctly detected when using Windows
  10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: upower 0.99.11-1build2
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr  1 23:07:12 2022
  ExecutablePath: /usr/lib/upower/upowerd
  InstallationDate: Installed on 2022-04-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   LANG=en_IN
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1967565/+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 1856480] Re: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu

[Seija K.]

** Information type changed from Public to Private

** Attachment removed: "Image of printing error"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5312547/+files/Screenshot%20from%202019-12-15%2015-07-59.png

** Attachment removed: "CupsErrorLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5312548/+files/CupsErrorLog.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5312549/+files/CurrentDmesg.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5312550/+files/Dependencies.txt

** Attachment removed: "KernLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5312551/+files/KernLog.txt

** Attachment removed: "CupsErrorLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856480/+attachment/5313397/+files/CupsErrorLog.txt

** Information type changed from Private to Public

** Information type changed from Public to Private

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

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash 

[Touch-packages] [Bug 1958019] PulseList.txt

[Przemek K.]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1958019/+attachment/5554768/+files/PulseList.txt

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019] apport information

[Przemek K.]

ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  ubuntu 5091 F pulseaudio
 /dev/snd/pcmC1D0p:   ubuntu 5091 F...m pulseaudio
 /dev/snd/controlC0:  ubuntu 5091 F pulseaudio
CasperMD5CheckResult: pass
CasperVersion: 1.465
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 21.10
LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: alsa-driver (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
Tags:  impish
Uname: Linux 5.13.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/08/2021
dmi.bios.release: 1.49
dmi.bios.vendor: LENOVO
dmi.bios.version: GKCN49WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Legion 7 16ACHg6
dmi.ec.firmware.release: 1.49
dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
dmi.product.family: Legion 7 16ACHg6
dmi.product.name: 82N6
dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
dmi.product.version: Legion 7 16ACHg6
dmi.sys.vendor: LENOVO

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019] PaInfo.txt

[Przemek K.]

apport information

** Attachment added: "PaInfo.txt"
   https://bugs.launchpad.net/bugs/1958019/+attachment/5554766/+files/PaInfo.txt

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019] ProcCpuinfoMinimal.txt

[Przemek K.]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1958019/+attachment/5554767/+files/ProcCpuinfoMinimal.txt

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019] AlsaInfo.txt

[Przemek K.]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1958019/+attachment/5554764/+files/AlsaInfo.txt

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019] CurrentDmesg.txt

[Przemek K.]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1958019/+attachment/5554765/+files/CurrentDmesg.txt

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all

[Przemek K.]

Alsa-info output saved to a file

** Attachment added: "alsa-info-legion7.txt"
   
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+attachment/5554763/+files/alsa-info-legion7.txt

** Tags added: apport-collected impish

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019] Re: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all

[Przemek K.]

Alsa-info output: http://alsa-
project.org/db/?f=ae148d86e41375195a7e401ef0af5d533218f275

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019] Re: [82N6, Realtek ALC287, Speaker, Internal] No sound at all

[Przemek K.]

This might be another case of
https://bugzilla.kernel.org/show_bug.cgi?id=208555

** Also affects: sound-2.6 via
   https://bugzilla.kernel.org/show_bug.cgi?id=208555
   Importance: Unknown
   Status: Unknown

** Summary changed:

- [82N6, Realtek ALC287, Speaker, Internal] No sound at all
+ [Lenovo Legion7 82N6, Realtek ALC287, Speaker, Internal] No sound at all

** Summary changed:

- [Lenovo Legion7 82N6, Realtek ALC287, Speaker, Internal] No sound at all
+ [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at 
all

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019] Re: [82N6, Realtek ALC287, Speaker, Internal] No sound at all

[Przemek K.]

I have the same issue.
I have a Legion 7 16ACHg6 which I'm testing under Ubuntu 20.04.3 LTS and 21.10 
LiveUSB, and in both of them there is no sound out of the built-in speakers. 
Headphones are working fine though.
05:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 
10h-1fh) HD Audio Controller
hwinfo shows that there is a "Realtek ALC701" chip in this laptop.
Full hwinfo output attached.

** Attachment added: "legion7-ubuntu.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1958019/+attachment/5554762/+files/legion7-ubuntu.txt

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

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Unknown
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1950393] Re: GDM session crashes on suspend on Ubuntu 21.10

[Vladislav K. Valtchev]

Hi Daniel,
In my understanding, the crash is not reproducible after my workaround 
(switching to the nvidia driver), because the nvidia-resume.service is not 
masked (my theory).

Therefore, I switched back to the Nouveau driver, and I reproduced the
problem and collected the system logs as you asked. Now prevboot.txt
contains the logs from a clean boot, through the session crash and ends
with a (user requested) reboot.

Just for the record, these are the steps to reproduce the bug:

 1. Install Ubuntu 21.10 on a laptop(?) with an nvidia GPU
 2. Open "Software & Updates" -> "Additional Drivers"
 3. Select the latest driver (470)
 4. Reboot
 5. Login normally on GDM
 6. Open "Software & Updates" -> "Additional Drivers"
 7. Select "Nouveau display driver" and apply the changes
 8. Reboot
 9. Login normally on GDM
10. Try to suspend the system
11. You should observe a session crash here


** Attachment added: "System journal for the previous boot, as requested in 
update #8"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950393/+attachment/5540130/+files/prevboot.txt

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

Title:
  GDM session crashes on suspend on Ubuntu 21.10

Status in gdm3 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Since I started using kernel 5.13.0-20 (and 5.13.0-21) on Ubuntu
  21.10, my GDM session crashes when I try to put my laptop to standby.

  I've attached a relevant slice of the system journal that starts from
  the moment I pressed the power button, configured to trigger suspend,
  in my case.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 00:47:13 2021
  DistUpgraded: 2021-10-16 23:05:19,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:380a]
 Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
  InstallationDate: Installed on 2020-03-17 (602 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 80RU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=0e855d19-79da-402d-9586-b7bfe9a9622a ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to impish on 2021-10-16 (24 days ago)
  dmi.bios.date: 08/09/2017
  dmi.bios.release: 1.61
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 700-15ISK
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN61WW:bd08/09/2017:br1.61:efr1.22:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:skuLENOVO_MT_80RU_BU_idea_FM_Lenovoideapad700-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80RU
  dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO
  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
  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/+source/gdm3/+bug/1950393/+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 1941752]

[K-d-hudson]

Created attachment 143424
New crash information added by DrKonqi

gwenview (20.12.3) using Qt 5.15.2

- What I was doing when the application crashed:

This is a little bizarre. I encountered this while rapidly scrolling
through thumbnails in a directory. One particular image reliably crashes
QwenView, but it isn't the image itself because QwenView opens the image
just fine if I copy it to another directory. If I copy just a few of the
images to another directory, QwenView also works just fine. The
directory contents are available online to replicate this issue. I
downloaded and replicated again just to be sure.

The directory contents are available online inside this archive:
https://downloads.open-
tx.org/2.3/release/sdcard/opentx-t16/sdcard-480x272-2.3V0025.zip. The
directory is IMAGES. The image QwenView crashes on is IMAGES/P51.jpg.

To replicate, extract the archive, and start clicking through the
images. I double clicked on in Dolphin to start.

The crash can be reproduced every time.

-- Backtrace (Reduced):
#4  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49
#5  0x7f191f393864 in __GI_abort () at abort.c:79
[...]
#12 0x7f191f00a92d in Exiv2::Xmpdatum::write(std::ostream&, Exiv2::ExifData 
const*) const () from /lib/x86_64-linux-gnu/libexiv2.so.27
#13 0x7f1921515250 in 
Gwenview::ImageMetaInfoModel::setExiv2Image(Exiv2::Image const*) () from 
/lib/x86_64-linux-gnu/libgwenviewlib.so.5
#14 0x7f19214dfa70 in 
Gwenview::Document::setExiv2Image(std::unique_ptr >) () from 
/lib/x86_64-linux-gnu/libgwenviewlib.so.5

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

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Unknown
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1950393] Re: GDM session crashes on suspend on Ubuntu 21.10

[Vladislav K. Valtchev]

Interesting update


Given the "Unit nvidia-resume.service is masked" complain by systemd-
logind in my previous comment, I thought it could be related with the
switching on and off the proprietary nvidia driver: after turning it on,
I turned it off (switching to Nouveau) because of this other bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947614


So, I opened the "Software & Updates" tool and in "Additional Drivers" I turned 
nvidia-driver-470 on again and... voila', the session-crash-on-suspend bug 
disappeared.

It looks like to me that the tool messed up some systemd units like
nvidia-resume.service and it didn't return them to the previous state
after I switched back to Nouveau.

Note: the only thing I used to turn on and off the nvidia driver is that
"Software & Updates" tool, no custom configurations/hacks at all.

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

Title:
  GDM session crashes on suspend on Ubuntu 21.10

Status in gdm3 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Since I started using kernel 5.13.0-20 (and 5.13.0-21) on Ubuntu
  21.10, my GDM session crashes when I try to put my laptop to standby.

  I've attached a relevant slice of the system journal that starts from
  the moment I pressed the power button, configured to trigger suspend,
  in my case.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 00:47:13 2021
  DistUpgraded: 2021-10-16 23:05:19,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:380a]
 Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
  InstallationDate: Installed on 2020-03-17 (602 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 80RU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=0e855d19-79da-402d-9586-b7bfe9a9622a ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to impish on 2021-10-16 (24 days ago)
  dmi.bios.date: 08/09/2017
  dmi.bios.release: 1.61
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 700-15ISK
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN61WW:bd08/09/2017:br1.61:efr1.22:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:skuLENOVO_MT_80RU_BU_idea_FM_Lenovoideapad700-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80RU
  dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO
  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
  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/+source/gdm3/+bug/1950393/+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 1950393] Re: GDM session crashes on suspend on Ubuntu 21.10

[Vladislav K. Valtchev]

If I grep for `systemd`, after the first meaningful message:

Nov 10 00:20:06 lenovo systemd-logind[11553]: Power key pressed.

The first error is:

Nov 10 00:20:11 lenovo systemd-logind[11553]: Error during inhibitor-
delayed operation (already returned success to client): Unit nvidia-
resume.service is masked.

And later:

Nov 10 00:20:13 lenovo /usr/libexec/gdm-x-session[12386]: (EE) systemd-
logind disappeared (stopped/restarted?)


** Also 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/1950393

Title:
  GDM session crashes on suspend on Ubuntu 21.10

Status in gdm3 package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  Since I started using kernel 5.13.0-20 (and 5.13.0-21) on Ubuntu
  21.10, my GDM session crashes when I try to put my laptop to standby.

  I've attached a relevant slice of the system journal that starts from
  the moment I pressed the power button, configured to trigger suspend,
  in my case.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: xorg 1:7.7+22ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 10 00:47:13 2021
  DistUpgraded: 2021-10-16 23:05:19,206 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: impish
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:380a]
 Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
  InstallationDate: Installed on 2020-03-17 (602 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 80RU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-21-generic 
root=UUID=0e855d19-79da-402d-9586-b7bfe9a9622a ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to impish on 2021-10-16 (24 days ago)
  dmi.bios.date: 08/09/2017
  dmi.bios.release: 1.61
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN61WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 700-15ISK
  dmi.ec.firmware.release: 1.22
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN61WW:bd08/09/2017:br1.61:efr1.22:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:skuLENOVO_MT_80RU_BU_idea_FM_Lenovoideapad700-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80RU
  dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO
  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
  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/+source/gdm3/+bug/1950393/+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 1948752] [NEW] apparmor is logging too many messages

[D-nl-k]

Public bug reported:

Unfortunately, this bug does not seem to be fixed yet.
My syslog is flooded with ALLOWED messages regarding redshift.

My system is a Kubuntu 21.04.
AppArmor is V. 3.0.0-0ubuntu7.1

Attached you'll find an excerpt from /var/log/syslog for the last 5
minutes.

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

** Attachment added: "5 Minutes excerpt of /var/lkog/syslog"
   https://bugs.launchpad.net/bugs/1948752/+attachment/5536110/+files/syslog

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

Title:
  apparmor is logging too many messages

Status in apparmor package in Ubuntu:
  New

Bug description:
  Unfortunately, this bug does not seem to be fixed yet.
  My syslog is flooded with ALLOWED messages regarding redshift.

  My system is a Kubuntu 21.04.
  AppArmor is V. 3.0.0-0ubuntu7.1

  Attached you'll find an excerpt from /var/log/syslog for the last 5
  minutes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1948752/+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 1948438] [NEW] Printer kan niet worden gestart. Controleer de configuratie van uw printer

[Fred K.]

Public bug reported:

My Canon MP499 printer is recognized, but if i try to use it in
LibreOffice Writer, a message appears (see above). Using translate, it
shows this message:

Printer cannot be started. Check your printer's configuration


fred@fred-Latitude-E6430:~$ lpstat 
fred@fred-Latitude-E6430:~$ lpstat -t
scheduler is running
no system default destination
device for DCP-L3550CDW: 
dnssd://Brother%20DCP-L3550CDW%20series._ipp._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4dc9c43
device for MP495-series: usb://Canon/MP495%20series?serial=24F65A=1
DCP-L3550CDW accepting requests since vr 23 jul 2021 12:55:49 CEST
MP495-series accepting requests since vr 22 okt 2021 10:58:01 CEST
printer DCP-L3550CDW is idle.  enabled since vr 23 jul 2021 12:55:49 CEST
printer MP495-series is idle.  enabled since vr 22 okt 2021 10:58:01 CEST
fred@fred-Latitude-E6430:~$ sudo service cups status 
[sudo] wachtwoord voor fred: 
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: >
 Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 977 (cupsd)
  Tasks: 3 (limit: 9421)
 Memory: 24.9M
 CGroup: /system.slice/cups.service
 ├─ 977 /usr/sbin/cupsd -l
 ├─2129 /usr/lib/cups/notifier/dbus dbus://
 └─4449 /usr/lib/cups/notifier/dbus dbus://

okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler.
okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea>
lines 1-16/16 (END)...skipping...
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: >
 Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 977 (cupsd)
  Tasks: 3 (limit: 9421)
 Memory: 24.9M
 CGroup: /system.slice/cups.service
 ├─ 977 /usr/sbin/cupsd -l
 ├─2129 /usr/lib/cups/notifier/dbus dbus://
 └─4449 /usr/lib/cups/notifier/dbus dbus://

okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler.
okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea>
~
~
~
~
~
~
~
~
lines 1-16/16 (END)...skipping...
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: >
 Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 977 (cupsd)
  Tasks: 3 (limit: 9421)
 Memory: 24.9M
 CGroup: /system.slice/cups.service
 ├─ 977 /usr/sbin/cupsd -l
 ├─2129 /usr/lib/cups/notifier/dbus dbus://
 └─4449 /usr/lib/cups/notifier/dbus dbus://

okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler.
okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea>
~
~
~
~
~
~
~
~
~
lines 1-16/16 (END)...skipping...
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: >
 Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 977 (cupsd)
  Tasks: 3 (limit: 9421)
 Memory: 24.9M
 CGroup: /system.slice/cups.service
 ├─ 977 /usr/sbin/cupsd -l
 ├─2129 /usr/lib/cups/notifier/dbus dbus://
 └─4449 /usr/lib/cups/notifier/dbus dbus://

okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler.
okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea>
~
~
~
~
~
~
~
~
~
~
~
lines 1-16/16 (END)...skipping...
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: >
 Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 977 (cupsd)
  Tasks: 3 (limit: 9421)
 Memory: 24.9M
 CGroup: /system.slice/cups.service
 ├─ 977 /usr/sbin/cupsd -l
 ├─2129 /usr/lib/cups/notifier/dbus dbus://
 └─4449 /usr/lib/cups/notifier/dbus dbus://

okt 22 10:56:11 fred-Latitude-E6430 systemd[1]: Started CUPS Scheduler.
okt 22 10:57:39 fred-Latitude-E6430 /hpfax[2022]: [2022]: error: Failed to crea>
~
~
~
~
~
~
~
~
~
~
~
~
lines 1-16/16 (END)...skipping...
● cups.service - CUPS Scheduler
 Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: >
 Active: active (running) since Fri 2021-10-22 10:56:11 CEST; 8min ago
TriggeredBy: ● cups.path
 ● cups.socket
   Docs: man:cupsd(8)
   Main PID: 977 (cupsd)
  Tasks: 3 (limit: 9421)
 Memory: 24.9M
 CGroup: /system.slice/cups.service
 ├─ 977 

[Touch-packages] [Bug 1856480] Re: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu

[Seija K.]

** Information type changed from Private to Public

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

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

To manage notifications about 

[Touch-packages] [Bug 1870975] Re: [Dell Inspiron 5570] No audio devices appear except "Dummy Output" after I close my laptop lid while audio is playing and then open it back up.

[Seija K.]

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361003/+files/WifiSyslog.txt

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360989/+files/CRDA.txt

** Information type changed from Public to Private

** Attachment removed: "Image of Audio Settings Menu"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5347299/+files/Screenshot%20from%202020-04-05%2014-51-31.png

** Attachment removed: "journalctl.log"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5349980/+files/journalctl.log

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

** Changed in: linux (Ubuntu)
   Status: Invalid => Confirmed

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5347300/+files/Dependencies.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5347301/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360990/+files/CurrentDmesg.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360999/+files/ProcModules.txt

** Attachment removed: "PulseList.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361000/+files/PulseList.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360992/+files/IwConfig.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361002/+files/UdevDb.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360991/+files/Dependencies.txt

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360988/+files/AlsaInfo.txt

** Attachment removed: "RfKill.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5361001/+files/RfKill.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360998/+files/ProcInterrupts.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360993/+files/Lspci.txt

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Attachment removed: "Lspci-vt.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360994/+files/Lspci-vt.txt

** Attachment removed: "Lsusb-v.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360996/+files/Lsusb-v.txt

** Attachment removed: "Lsusb-t.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360995/+files/Lsusb-t.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870975/+attachment/5360997/+files/ProcCpuinfoMinimal.txt

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

Title:
  [Dell Inspiron 5570] No audio devices appear except "Dummy Output"
  after I close my laptop lid while audio is playing and then open it
  back up.

Status in alsa-driver package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  When I closed my laptop lid while sound was playing in Audacity and
  then opened the lid back up, the device woke up from sleep. However,
  my headphones were plugged in at the time, and Ubuntu acted as if the
  audio resumed.

  However, I was not hearing audio. So I went to the Audio section of
  Settings and found there was only one sound device: Dummy Device,
  instead of seeing the speakers built into the laptop and the
  headphones.

  Description: Ubuntu 18.04.4 LTS
  Release: 18.04

  I am forced to reboot my machine as a workaround.

  gnome-control-center:
Installed: 1:3.28.2-0ubuntu0.18.04.6
Candidate: 1:3.28.2-0ubuntu0.18.04.6
Version table:
   *** 1:3.28.2-0ubuntu0.18.04.6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.28.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: 

[Touch-packages] [Bug 1856718] Re: CUPS server has an internal error whenever I attempt to add my HP OfficeJet8600 printer to configured devices via networking

[Seija K.]

** Attachment removed: "ping.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313410/+files/ping.txt

** Attachment removed: "Screenshot of configuring screen and terminal"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313383/+files/Screenshot%20from%202019-12-17%2009-43-12.png

** Attachment removed: "CupsErrorLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313384/+files/CupsErrorLog.txt

** Information type changed from Public to Private

** Attachment removed: "dnssd.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313412/+files/dnssd.txt

** Attachment removed: "nmap.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313411/+files/nmap.txt

** Attachment removed: "route.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313416/+files/route.txt

** Attachment removed: "access_log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313417/+files/access_log.txt

** Attachment removed: "Locale.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313388/+files/Locale.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313394/+files/ProcModules.txt

** Attachment removed: "KernLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313387/+files/KernLog.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313385/+files/CurrentDmesg.txt

** Attachment removed: "PrintingPackages.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313390/+files/PrintingPackages.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313393/+files/ProcInterrupts.txt

** Attachment removed: "ifconfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313414/+files/ifconfig.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313386/+files/Dependencies.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313392/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313389/+files/Lspci.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313391/+files/ProcCpuinfo.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313395/+files/UdevDb.txt

** Attachment removed: "modified.conffile..etc.apport.crashdb.conf.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313396/+files/modified.conffile..etc.apport.crashdb.conf.txt

** Attachment removed: "lpinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313413/+files/lpinfo.txt

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

Title:
  CUPS server has an internal error whenever I attempt to add my HP
  OfficeJet8600 printer to configured devices via networking

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to add my HP OfficeJet8600 printer and configure it
  for printing on my Ubuntu PC, CUPS has an internal error and it is
  unable to configure the device or install drivers.

  This happened when I ran "system-config-printer" and selected the
  printer from the list of network printers and clicked "Forward"

  Instead of configuring the printer and installing drivers, CUPS had an
  error.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 09:37:45 2019
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor 

[Touch-packages] [Bug 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep

[Seija K.]

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310885/+files/Dependencies.txt

** Attachment removed: "NetDevice.enp4s0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310888/+files/NetDevice.enp4s0.txt

** Attachment removed: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310889/+files/NetDevice.lo.txt

** Attachment removed: "NetDevice.wlp3s0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310890/+files/NetDevice.wlp3s0.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310893/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "AlsaInfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350595/+files/AlsaInfo.txt

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350597/+files/CurrentDmesg.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350598/+files/Dependencies.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350600/+files/IwConfig.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350601/+files/Lspci.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350612/+files/UdevDb.txt

** Attachment removed: "RfKill.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350611/+files/RfKill.txt

** Attachment removed: "PulseList.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350610/+files/PulseList.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350609/+files/ProcModules.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350608/+files/ProcInterrupts.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350607/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "NetDevice.wlp2s0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350604/+files/NetDevice.wlp2s0.txt

** Attachment removed: "NetDevice.lo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350603/+files/NetDevice.lo.txt

** Attachment removed: "NetDevice.enp1s0.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350602/+files/NetDevice.enp1s0.txt

** Description changed:

- Whenever I wake the computer up from sleep, the computer no longer
- connects to the Internet without my having to go into Settings and turn
- Wi-Fi off and then back on again.
- 
- Please address this issue.
- 
- Thank you!
- 
- network-manager:
-   Installed: 1.10.6-2ubuntu1.2
-   Candidate: 1.10.6-2ubuntu1.2
-   Version table:
-  *** 1.10.6-2ubuntu1.2 500
- 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  1.10.6-2ubuntu1.1 500
- 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
-  1.10.6-2ubuntu1 500
- 500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
- 
- Description:  Ubuntu 18.04.3 LTS
- Release:  18.04
- 
- ProblemType: Bug
- DistroRelease: Ubuntu 18.04
- Package: network-manager 1.10.6-2ubuntu1.2
- ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
- Uname: Linux 5.0.0-37-generic x86_64
- ApportVersion: 2.20.9-0ubuntu7.9
- Architecture: amd64
- CurrentDesktop: ubuntu:GNOME
- Date: Sun Dec  8 19:51:31 2019
- IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  auto lo
-  iface lo inet loopback
- IpRoute:
-  default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
-  169.254.0.0/16 dev wlp3s0 scope link metric 1000 
-  192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600
- NetworkManager.state:
-  [main]
-  NetworkingEnabled=true
-  WirelessEnabled=true
-  WWANEnabled=true
- ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
- RfKill:
-  0: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
- SourcePackage: network-manager
- UpgradeStatus: No upgrade log present (probably fresh install)
- nmcli-con:
-  NAMEUUID  TYPE  

[Touch-packages] [Bug 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep

[Seija K.]

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350596/+files/CRDA.txt

** Attachment removed: "CRDA.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310884/+files/CRDA.txt

** Attachment removed: "PciNetwork.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350606/+files/PciNetwork.txt

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

Title:
  Ubuntu keeps having resolution issues and disconnects from the network
  after I wake it up from sleep

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

Bug description:
  Whenever I wake the computer up from sleep, the computer no longer
  connects to the Internet without my having to go into Settings and
  turn Wi-Fi off and then back on again.

  Please address this issue.

  Thank you!

  network-manager:
Installed: 1.10.6-2ubuntu1.2
Candidate: 1.10.6-2ubuntu1.2
Version table:
   *** 1.10.6-2ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.10.6-2ubuntu1.1 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1.10.6-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 19:51:31 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   64704ba2-aba5-44de-ad4a-7d0de569815b  wifi  
1575852612  Sun 08 Dec 2019 07:50:12 PM EST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  28634e82-4c1c-3a61-b152-3bd92aaa6992  ethernet  
1575852610  Sun 08 Dec 2019 07:50:10 PM EST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   64704ba2-aba5-44de-ad4a-7d0de569815b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp4s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  seija  1560 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2020-04-04 (5 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  IpRoute:
   

[Touch-packages] [Bug 1870607] Re: After installing Ubuntu 20.04 alongside 19.10, initramfs no longer is able to extract from either OSes when I boot them.

[Seija K.]

** Attachment removed: "my initrd.img"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1870607/+attachment/5345796/+files/initrd.img

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1870607/+attachment/5345795/+files/ProcCpuinfoMinimal.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1870607/+attachment/5345794/+files/Dependencies.txt

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

Title:
  After installing Ubuntu 20.04 alongside 19.10, initramfs no longer is
  able to extract from either OSes when I boot them.

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After installing Ubuntu 20.04, initramfs no longer can extract from
  either 20.04 OR 19.10. However, the initramfs should work AT LEAST on
  20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: initramfs-tools-core 0.133ubuntu10
  ProcVersionSignature: Ubuntu 5.3.0-45.37-generic 5.3.18
  Uname: Linux 5.3.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.8
  Architecture: amd64
  Date: Fri Apr  3 15:33:36 2020
  InstallationDate: Installed on 2020-04-03 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: initramfs-tools
  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/1870607/+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 1855628] Re: Ubuntu keeps having resolution issues and disconnects from the network after I wake it up from sleep

[Seija K.]

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310894/+files/WifiSyslog.txt

** Attachment removed: "IpAddr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310886/+files/IpAddr.txt

** Attachment removed: "PciNetwork.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310892/+files/PciNetwork.txt

** Attachment removed: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310891/+files/NetworkManager.conf.txt

** Attachment removed: "IwConfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5310887/+files/IwConfig.txt

** Attachment removed: "NetworkManager.conf.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350605/+files/NetworkManager.conf.txt

** Attachment removed: "IpAddr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350599/+files/IpAddr.txt

** Attachment removed: "WifiSyslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1855628/+attachment/5350613/+files/WifiSyslog.txt

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

Title:
  Ubuntu keeps having resolution issues and disconnects from the network
  after I wake it up from sleep

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

Bug description:
  Whenever I wake the computer up from sleep, the computer no longer
  connects to the Internet without my having to go into Settings and
  turn Wi-Fi off and then back on again.

  Please address this issue.

  Thank you!

  network-manager:
Installed: 1.10.6-2ubuntu1.2
Candidate: 1.10.6-2ubuntu1.2
Version table:
   *** 1.10.6-2ubuntu1.2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.10.6-2ubuntu1.1 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
   1.10.6-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  8 19:51:31 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IpRoute:
   default via 192.168.1.1 dev wlp3s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000 
   192.168.1.0/24 dev wlp3s0 proto kernel scope link src 192.168.1.33 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   NETGEAR18   64704ba2-aba5-44de-ad4a-7d0de569815b  wifi  
1575852612  Sun 08 Dec 2019 07:50:12 PM EST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp3s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  28634e82-4c1c-3a61-b152-3bd92aaa6992  ethernet  
1575852610  Sun 08 Dec 2019 07:50:10 PM EST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
NETGEAR18   64704ba2-aba5-44de-ad4a-7d0de569815b  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp4s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged

[Touch-packages] [Bug 1916714] [NEW] cross build fails

[Vijai Kumar K]

Public bug reported:

Cross building of base-files package fails.

Version: 11ubuntu5.3

Steps to reproduce:
---
armhf:
DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -aarmhf -Pcross,nocheck

arm64:
DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -aarm64 -Pcross,nocheck

Log:

make[1]: Leaving directory '/media/data/base-files-11ubuntu5.3'
   dh_missing
   dh_strip
aarch64-linux-gnu-objcopy: Unable to recognise the format of the input file 
`debian/base-files/usr/bin/locale-check'
dh_strip: error: aarch64-linux-gnu-objcopy --only-keep-debug 
--compress-debug-sections debian/base-files/usr/bin/locale-check 
debian/.debhelper/base-files/dbgsym-root/usr/lib/debug/.build-id/71/aa3df0a7e05817cb7e212513aeae7db21d8593.debug
 returned exit code 1
dh_strip: error: Aborting due to earlier error
make: *** [debian/rules:15: binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned exit 
status 2

Expected output:

Should compile successfully


Thanks,
Vijai Kumar K

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  cross build  fails

Status in base-files package in Ubuntu:
  New

Bug description:
  Cross building of base-files package fails.

  Version: 11ubuntu5.3

  Steps to reproduce:
  ---
  armhf:
  DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -aarmhf -Pcross,nocheck

  arm64:
  DEB_BUILD_OPTIONS=nocheck dpkg-buildpackage -aarm64 -Pcross,nocheck

  Log:
  
  make[1]: Leaving directory '/media/data/base-files-11ubuntu5.3'
 dh_missing
 dh_strip
  aarch64-linux-gnu-objcopy: Unable to recognise the format of the input file 
`debian/base-files/usr/bin/locale-check'
  dh_strip: error: aarch64-linux-gnu-objcopy --only-keep-debug 
--compress-debug-sections debian/base-files/usr/bin/locale-check 
debian/.debhelper/base-files/dbgsym-root/usr/lib/debug/.build-id/71/aa3df0a7e05817cb7e212513aeae7db21d8593.debug
 returned exit code 1
  dh_strip: error: Aborting due to earlier error
  make: *** [debian/rules:15: binary] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  Expected output:
  
  Should compile successfully

  
  Thanks,
  Vijai Kumar K

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1916714/+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 1726124] Re: DNS domain search paths not updated when VPN started

[Vadym K]

Still an issue in 20.04 LTS

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager-openvpn package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage 

[Touch-packages] [Bug 1876219] Re: iris driver for old cpu

[K van Murfi]

Same problem here (Ubuntu 20.04, i915 driver, Skylake Intel(R) Core(TM) 
i7-6500U CPU @ 2.50GHz
) :
- glxgears and vlc both give a black window
- /usr/bin/kcmshell5 kcm_networkmanagementreturns a segfault.

'export MESA_LOADER_DRIVER_OVERRIDE=i965' seems to solve all this. Many
thanks to Chenxi Wu  for this trick.

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

Title:
  iris driver for old cpu

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I am not completely sure where I should file the bug. I am using
  Lubuntu 20.04 with lxqt, and since the upgrade to 20.04 iris is the
  default graphics driver, which results in crashes in multiple apps
  including guvcview and calibre. Setting
  MESA_LOADER_DRIVER_OVERRIDE=i965 fixed the problem. I am not sure but
  is it true that iris does not support older generations of Intel CPUs?
  If it is the case would it be possible to revert to i965 in those
  circumstances? Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1876219/+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 1316634] Re: Does not automatically reconnect to hidden WiFi network

[K]

On the Debian bug site it shows that adding wifi.hidden yes via "nmcli
connection modify  wifi.hidden yes" does seem to produce a solution
but it only works one time. When I did this and restarted network
manager service I had hidden wifi connect once successfully but it
wouldn't do it again when I cycled the wifi interface down/up.

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

Title:
  Does not automatically reconnect to hidden WiFi network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Running Lubuntu 14.04 32-bit on a Lenovo 3000 C200 laptop with an
  integrated Broadcom network adapter, I installed
  firmware-b43-installer and then successfully connected to my hidden
  (SSID not broadcast) WiFi net.

  But I see that it will not automatically reconnect.  I don't have to
  re-enter the password, but I do have to click the nm-applet indicator,
  choose 'Connect to Hidden Wi-Fi Network' and then choose my already-
  defined connection, which indeed has been saved but not used to
  automatically reconnect.

  If I edit the connection, I see that on the General tab it is already
  set to 'Automatically connect to this network when it is available.'

  The only way I can get automatic reconnection is to enable SSID
  Broadcast.

  And a similar effect: If I am connected to the network while SSID
  Broadcast is in effect and then disable SSID Broadcast, network-
  manager immediately loses the connection.

  Someone suggested that network-manager would find the hidden network
  if I just waited, but after waiting 15 minutes it had still not
  connected.

  Dual-booting this same laptop with Windows Vista, I see that Windows
  knows how to automatically reconnect to the hidden net.

  I see that https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/295796 describes similar behavior, but that was reported
  back in 2008 and I'm imagining that there should be a separate report
  for the new release.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDesktop: LXDE
  Date: Tue May  6 10:24:32 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-25 (10 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.118  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 1ac7ba941-660f-40c5-9b1f-4d24accc6225   
802-3-ethernet1399385892   Tue 06 May 2014 10:18:12 AM EDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   PRP   d25473c0-98d8-4d93-ab37-3dd070bbd34b   
802-11-wireless   1399386192   Tue 06 May 2014 10:23:12 AM EDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1316634/+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 1316634] Re: Does not automatically reconnect to hidden WiFi network

[K]

I'm confirming this bug 6 years later is real and unfixed still! The
solution worked for me. Can this be patched ASAP?

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

Title:
  Does not automatically reconnect to hidden WiFi network

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Running Lubuntu 14.04 32-bit on a Lenovo 3000 C200 laptop with an
  integrated Broadcom network adapter, I installed
  firmware-b43-installer and then successfully connected to my hidden
  (SSID not broadcast) WiFi net.

  But I see that it will not automatically reconnect.  I don't have to
  re-enter the password, but I do have to click the nm-applet indicator,
  choose 'Connect to Hidden Wi-Fi Network' and then choose my already-
  defined connection, which indeed has been saved but not used to
  automatically reconnect.

  If I edit the connection, I see that on the General tab it is already
  set to 'Automatically connect to this network when it is available.'

  The only way I can get automatic reconnection is to enable SSID
  Broadcast.

  And a similar effect: If I am connected to the network while SSID
  Broadcast is in effect and then disable SSID Broadcast, network-
  manager immediately loses the connection.

  Someone suggested that network-manager would find the hidden network
  if I just waited, but after waiting 15 minutes it had still not
  connected.

  Dual-booting this same laptop with Windows Vista, I see that Windows
  knows how to automatically reconnect to the hidden net.

  I see that https://bugs.launchpad.net/ubuntu/+source/network-
  manager/+bug/295796 describes similar behavior, but that was reported
  back in 2008 and I'm imagining that there should be a separate report
  for the new release.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: network-manager 0.9.8.8-0ubuntu7
  ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
  Uname: Linux 3.13.0-24-generic i686
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: i386
  CRDA: Error: [Errno 2] No such file or directory: 'iw'
  CurrentDesktop: LXDE
  Date: Tue May  6 10:24:32 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-04-25 (10 days ago)
  InstallationMedia: Lubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140416.2)
  IpRoute:
   default via 192.168.1.1 dev wlan0  proto static 
   192.168.1.0/24 dev wlan0  proto kernel  scope link  src 192.168.1.118  
metric 9
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 1ac7ba941-660f-40c5-9b1f-4d24accc6225   
802-3-ethernet1399385892   Tue 06 May 2014 10:18:12 AM EDTyes   
no /org/freedesktop/NetworkManager/Settings/1
   PRP   d25473c0-98d8-4d93-ab37-3dd070bbd34b   
802-11-wireless   1399386192   Tue 06 May 2014 10:23:12 AM EDTyes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1316634/+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 1882524] [NEW] [CF-53DA502FW, Realtek ALC269VB, Speaker, Internal] Playback problem

[dani k]

Public bug reported:

i have no audio from speakers in my laptop but i have audio output on hdmi. i 
have another harddrive with windows 7 on it and the speakers work correctly on 
that. they used to work on this distro
Description:Ubuntu 20.04 LTS
Release:20.04

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
Uname: Linux 5.4.0-33-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  dani   1677 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun  8 12:59:05 2020
InstallationDate: Installed on 2020-03-24 (75 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_Type: Only some of outputs are working
Title: [CF-53DA502FW, Realtek ALC269VB, Speaker, Internal] Playback problem
UpgradeStatus: Upgraded to focal on 2020-05-16 (22 days ago)
dmi.bios.date: 05/25/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.00L15
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: CF53-1
dmi.board.vendor: Panasonic Corporation
dmi.board.version: 1
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: Panasonic Corporation
dmi.chassis.version: 001
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.00L15:bd05/25/2012:svnPanasonicCorporation:pnCF-53DA502FW:pvr001:rvnPanasonicCorporation:rnCF53-1:rvr1:cvnPanasonicCorporation:ct10:cvr001:
dmi.product.family: CF53-1
dmi.product.name: CF-53DA502FW
dmi.product.sku: CF-53DA502FW
dmi.product.version: 001
dmi.sys.vendor: Panasonic Corporation

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


** Tags: amd64 apport-bug focal

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

Title:
  [CF-53DA502FW, Realtek ALC269VB, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  i have no audio from speakers in my laptop but i have audio output on hdmi. i 
have another harddrive with windows 7 on it and the speakers work correctly on 
that. they used to work on this distro
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dani   1677 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  8 12:59:05 2020
  InstallationDate: Installed on 2020-03-24 (75 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [CF-53DA502FW, Realtek ALC269VB, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to focal on 2020-05-16 (22 days ago)
  dmi.bios.date: 05/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.00L15
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CF53-1
  dmi.board.vendor: Panasonic Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Panasonic Corporation
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.00L15:bd05/25/2012:svnPanasonicCorporation:pnCF-53DA502FW:pvr001:rvnPanasonicCorporation:rnCF53-1:rvr1:cvnPanasonicCorporation:ct10:cvr001:
  dmi.product.family: CF53-1
  dmi.product.name: CF-53DA502FW
  dmi.product.sku: CF-53DA502FW
  dmi.product.version: 001
  dmi.sys.vendor: Panasonic Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1882524/+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 1878226] [NEW] package libasound2-plugins 1.2.2-1ubuntu1 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/10-samplerate.conf', which is different from othe

[K. Mehta]

Public bug reported:

tried to reinstall ubuntu-desktop for some mutter problems; some keys
cannot be typed/copied; but it has worsened

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libasound2-plugins 1.2.2-1ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
AptOrdering:
 libasound2-plugins:i386: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri May  8 22:14:51 2020
DpkgTerminalLog:
 Preparing to unpack .../libasound2-plugins_1.2.2-1ubuntu1_i386.deb ...
 Unpacking libasound2-plugins:i386 (1.2.2-1ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libasound2-plugins_1.2.2-1ubuntu1_i386.deb (--unpack):
  trying to overwrite shared '/etc/alsa/conf.d/10-samplerate.conf', which is 
different from other instances of package libasound2-plugins:i386
ErrorMessage: trying to overwrite shared '/etc/alsa/conf.d/10-samplerate.conf', 
which is different from other instances of package libasound2-plugins:i386
InstallationDate: Installed on 2020-03-13 (60 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
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.2
SourcePackage: alsa-plugins
Title: package libasound2-plugins 1.2.2-1ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/etc/alsa/conf.d/10-samplerate.conf', which is 
different from other instances of package libasound2-plugins:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal third-party-packages

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

Title:
  package libasound2-plugins 1.2.2-1ubuntu1 failed to install/upgrade:
  trying to overwrite shared '/etc/alsa/conf.d/10-samplerate.conf',
  which is different from other instances of package
  libasound2-plugins:i386

Status in alsa-plugins package in Ubuntu:
  New

Bug description:
  tried to reinstall ubuntu-desktop for some mutter problems; some keys
  cannot be typed/copied; but it has worsened

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libasound2-plugins 1.2.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  AptOrdering:
   libasound2-plugins:i386: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May  8 22:14:51 2020
  DpkgTerminalLog:
   Preparing to unpack .../libasound2-plugins_1.2.2-1ubuntu1_i386.deb ...
   Unpacking libasound2-plugins:i386 (1.2.2-1ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libasound2-plugins_1.2.2-1ubuntu1_i386.deb (--unpack):
trying to overwrite shared '/etc/alsa/conf.d/10-samplerate.conf', which is 
different from other instances of package libasound2-plugins:i386
  ErrorMessage: trying to overwrite shared 
'/etc/alsa/conf.d/10-samplerate.conf', which is different from other instances 
of package libasound2-plugins:i386
  InstallationDate: Installed on 2020-03-13 (60 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  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.2
  SourcePackage: alsa-plugins
  Title: package libasound2-plugins 1.2.2-1ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/etc/alsa/conf.d/10-samplerate.conf', which is 
different from other instances of package libasound2-plugins:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1878226/+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 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

[Gökhan K .]

Sorry for all, "Fix Released" information for status isn't true, it's my
mistake.

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874851/+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 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

[Gökhan K .]

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

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874851/+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 1874851] Re: Unable to remove file or folder from desktop using key or dropdown menu interface

[Gökhan K .]

** Changed in: gnome-shell (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Unable to remove file or folder from desktop using  key or
  dropdown menu interface

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 20.04 LTS installed
  2. Open terminal and create new file and new folder

   mkdir ~/Desktop/folder
   touch ~/Desktop/file

  3. Close terminal
  4. Locate *folder* and *file* on the desktop, then
  4.1. Press 
  4.2. Do right mouse click on each and try to find Delete/Remove menu item

  
  Expected results:
  * user is able to remove object from Desktop by mouse or keyboard

  Actual results:
  * user is unable to remove object from Desktop by mouse or keyboard

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-desktop 1.450
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 19:07:36 2020
  InstallationDate: Installed on 2020-04-24 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Jo K]

By the way : user.lastnamelastnamelastn...@domain.fr does not trigger
the bug.

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

Title:
  cannot log in with long username

Status in pam package in Ubuntu:
  Incomplete

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

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

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

  I reproduce it on ubuntu 18.04 and 20.04 daylibuild.

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

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

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

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

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

[Jo K]

Just retried with fresh download of this file : 
http://cdimage.ubuntu.com/daily-live/current/focal-desktop-amd64.iso

I confirm that entering on tty3
username.lastnamelastnamelastn...@domain.fr
(not just "user.")
does trigger the bug.

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

Title:
  cannot log in with long username

Status in pam package in Ubuntu:
  Incomplete

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

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

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

  I reproduce it on ubuntu 18.04 and 20.04 daylibuild.

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

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

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

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

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

[Jo K]

Nothing but i misexplained, bug isn't related to the fact that account exists 
or not.
Please try to enter in a tty that exact login :

'username.lastnamelastnamelastn...@domain.fr'

It reset without asking for password, and the error line is added to
auth.log

Then try :

'username.lastn...@domain.fr'

It asks for password, even that account doesn't exists, and the error
line isn't added

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

Title:
  cannot log in with long username

Status in pam package in Ubuntu:
  Incomplete

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

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

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

  I reproduce it on ubuntu 18.04 and 20.04 daylibuild.

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

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

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

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

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

[Jo K]

All Ubuntu systems are affected.
That's not related to a personal configuration, booting live latest ubuntu let 
me reproduce this.

Its more clear on tty, as you see username field resets, but it's the
same from ligthdm

So should i open a bug for agetty package instead ?

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

Title:
  cannot log in with long username

Status in pam package in Ubuntu:
  Incomplete

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

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

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

  I reproduce it on ubuntu 18.04 and 20.04 daylibuild.

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

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

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

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

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

[Jo K]

Public bug reported:

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

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

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

I reproduce it on ubuntu 18.04 and 20.04 daylibuild.

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

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

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

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

Title:
  cannot log in with long username

Status in pam package in Ubuntu:
  New

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

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

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

  I reproduce it on ubuntu 18.04 and 20.04 daylibuild.

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

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

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

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

[Touch-packages] [Bug 1861440] Re: [upstream regression] wget does not honor dot-prefixed domains in no_proxy env variable

[Shawn K. O'Shea]

** Bug watch added: Red Hat Bugzilla #1763702
   https://bugzilla.redhat.com/show_bug.cgi?id=1763702

** Also affects: wget (CentOS) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1763702
   Importance: Unknown
   Status: Unknown

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

Title:
  [upstream regression] wget does not honor dot-prefixed domains in
  no_proxy env variable

Status in wget package in Ubuntu:
  New
Status in wget package in CentOS:
  Unknown

Bug description:
  Traditionally (AFAIK for at least the last decade), tools that support
  the no_proxy environment variable support specifying an entire
  subdomain by prefixing it with a "dot". For example, to exclude any
  website under example.com from using the proxy, you would set no_proxy
  to .example.com (export no_proxy=.example.com).

  A regression in wget 1.19 changed this behavior to expect non-prefixed
  domains (example.com vs .example.com). This regression was ultimately
  fixed and released with the 1.20 release of wget. bionic includes the
  regressed behavior version of wget.

  The regression was apparently introduced in wget 1.19.3. This bug
  should not effect other Ubuntu releases (xenial contains 1.17.1 and
  both disco and eoan contain 1.20.x versions that have the upstream
  fix).

  For more details, see references below and my additional comments on
  the RHEL8 bug filed for this issue (RH bug 1763702 linked below).

  What happens:
  no_proxy=.example.com in bionic sends requests to the proxy server for URLs 
like http://www.example.com/ despite requesting proxy exception via no_proxy.

  What should happen:
  Request should bypass the proxy and go directly to the web server. (works in 
xenial, disco and eoan as expected).

  System/software information:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy wget
  wget:
Installed: 1.19.4-1ubuntu2.2
Candidate: 1.19.4-1ubuntu2.2
Version table:
   *** 1.19.4-1ubuntu2.2 500
  500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-updates/main 
amd64 Packages
  500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-security/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1.19.4-1ubuntu2 500
  500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic/main amd64 
Packages

  References:
  * Upstream wget bug report: 
GNU Wget - Bugs: bug #53622 wget no_proxy leading dot on (sub)domains not 
working contradicting man page
https://savannah.gnu.org/bugs/?53622

  * Upstream commit reference that introduces the regression

http://git.savannah.gnu.org/cgit/wget.git/commit/?id=fd85ac9cc623847e9d94d9f9241ab34e2c146cbf

  * Upstream commit reference that introduces the fix

http://git.savannah.gnu.org/cgit/wget.git/commit/?id=fd85ac9cc623847e9d94d9f9241ab34e2c146cbf

  * Expected behavior of no_proxy as documented in the GNU Emacs manual:
  https://www.gnu.org/software/emacs/manual/html_node/url/Proxies.html

  * Red Hat Bugzilla entry for this issue (Reported against RHEL8.1)
Bug 1763702 - wget is ignoring no_proxy environment variable 
https://bugzilla.redhat.com/show_bug.cgi?id=1763702

  * Red Hat Bugzilla entry tracking the (now released) errata package for 
RHEL8.1
Bug 1772821 - wget is ignoring no_proxy environment variable [rhel-8.1.0.z] 
https://bugzilla.redhat.com/show_bug.cgi?id=1772821

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1861440/+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 1861440] Re: wget does not honor dot-prefixed domains in no_proxy env variable

[Shawn K. O'Shea]

Just another data point. I searched Debian packages and there is not an
associated release impacted by this issue.

Debian oldstable (stretch) ships wget 1.18 (pre-regression release). See 
https://packages.debian.org/stretch/wget 
Debian stable (buster) ships wget 1.20 (regression fixed release). See 
https://packages.debian.org/buster/wget

** Summary changed:

- wget does not honor dot-prefixed domains in no_proxy env variable
+ [upstream regression] wget does not honor dot-prefixed domains in no_proxy 
env variable

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

Title:
  [upstream regression] wget does not honor dot-prefixed domains in
  no_proxy env variable

Status in wget package in Ubuntu:
  New

Bug description:
  Traditionally (AFAIK for at least the last decade), tools that support
  the no_proxy environment variable support specifying an entire
  subdomain by prefixing it with a "dot". For example, to exclude any
  website under example.com from using the proxy, you would set no_proxy
  to .example.com (export no_proxy=.example.com).

  A regression in wget 1.19 changed this behavior to expect non-prefixed
  domains (example.com vs .example.com). This regression was ultimately
  fixed and released with the 1.20 release of wget. bionic includes the
  regressed behavior version of wget.

  The regression was apparently introduced in wget 1.19.3. This bug
  should not effect other Ubuntu releases (xenial contains 1.17.1 and
  both disco and eoan contain 1.20.x versions that have the upstream
  fix).

  For more details, see references below and my additional comments on
  the RHEL8 bug filed for this issue (RH bug 1763702 linked below).

  What happens:
  no_proxy=.example.com in bionic sends requests to the proxy server for URLs 
like http://www.example.com/ despite requesting proxy exception via no_proxy.

  What should happen:
  Request should bypass the proxy and go directly to the web server. (works in 
xenial, disco and eoan as expected).

  System/software information:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy wget
  wget:
Installed: 1.19.4-1ubuntu2.2
Candidate: 1.19.4-1ubuntu2.2
Version table:
   *** 1.19.4-1ubuntu2.2 500
  500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-updates/main 
amd64 Packages
  500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-security/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1.19.4-1ubuntu2 500
  500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic/main amd64 
Packages

  References:
  * Upstream wget bug report: 
GNU Wget - Bugs: bug #53622 wget no_proxy leading dot on (sub)domains not 
working contradicting man page
https://savannah.gnu.org/bugs/?53622

  * Upstream commit reference that introduces the regression

http://git.savannah.gnu.org/cgit/wget.git/commit/?id=fd85ac9cc623847e9d94d9f9241ab34e2c146cbf

  * Upstream commit reference that introduces the fix

http://git.savannah.gnu.org/cgit/wget.git/commit/?id=fd85ac9cc623847e9d94d9f9241ab34e2c146cbf

  * Expected behavior of no_proxy as documented in the GNU Emacs manual:
  https://www.gnu.org/software/emacs/manual/html_node/url/Proxies.html

  * Red Hat Bugzilla entry for this issue (Reported against RHEL8.1)
Bug 1763702 - wget is ignoring no_proxy environment variable 
https://bugzilla.redhat.com/show_bug.cgi?id=1763702

  * Red Hat Bugzilla entry tracking the (now released) errata package for 
RHEL8.1
Bug 1772821 - wget is ignoring no_proxy environment variable [rhel-8.1.0.z] 
https://bugzilla.redhat.com/show_bug.cgi?id=1772821

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1861440/+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 1861440] [NEW] wget does not honor dot-prefixed domains in no_proxy env variable

[Shawn K. O'Shea]

Public bug reported:

Traditionally (AFAIK for at least the last decade), tools that support
the no_proxy environment variable support specifying an entire subdomain
by prefixing it with a "dot". For example, to exclude any website under
example.com from using the proxy, you would set no_proxy to .example.com
(export no_proxy=.example.com).

A regression in wget 1.19 changed this behavior to expect non-prefixed
domains (example.com vs .example.com). This regression was ultimately
fixed and released with the 1.20 release of wget. bionic includes the
regressed behavior version of wget.

The regression was apparently introduced in wget 1.19.3. This bug should
not effect other Ubuntu releases (xenial contains 1.17.1 and both disco
and eoan contain 1.20.x versions that have the upstream fix).

For more details, see references below and my additional comments on the
RHEL8 bug filed for this issue (RH bug 1763702 linked below).

What happens:
no_proxy=.example.com in bionic sends requests to the proxy server for URLs 
like http://www.example.com/ despite requesting proxy exception via no_proxy.

What should happen:
Request should bypass the proxy and go directly to the web server. (works in 
xenial, disco and eoan as expected).

System/software information:
$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
$ apt-cache policy wget
wget:
  Installed: 1.19.4-1ubuntu2.2
  Candidate: 1.19.4-1ubuntu2.2
  Version table:
 *** 1.19.4-1ubuntu2.2 500
500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-updates/main 
amd64 Packages
500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-security/main 
amd64 Packages
100 /var/lib/dpkg/status
 1.19.4-1ubuntu2 500
500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic/main amd64 
Packages

References:
* Upstream wget bug report: 
  GNU Wget - Bugs: bug #53622 wget no_proxy leading dot on (sub)domains not 
working contradicting man page
  https://savannah.gnu.org/bugs/?53622

* Upstream commit reference that introduces the regression
  
http://git.savannah.gnu.org/cgit/wget.git/commit/?id=fd85ac9cc623847e9d94d9f9241ab34e2c146cbf

* Upstream commit reference that introduces the fix
  
http://git.savannah.gnu.org/cgit/wget.git/commit/?id=fd85ac9cc623847e9d94d9f9241ab34e2c146cbf

* Expected behavior of no_proxy as documented in the GNU Emacs manual:
https://www.gnu.org/software/emacs/manual/html_node/url/Proxies.html

* Red Hat Bugzilla entry for this issue (Reported against RHEL8.1)
  Bug 1763702 - wget is ignoring no_proxy environment variable 
  https://bugzilla.redhat.com/show_bug.cgi?id=1763702

* Red Hat Bugzilla entry tracking the (now released) errata package for RHEL8.1
  Bug 1772821 - wget is ignoring no_proxy environment variable [rhel-8.1.0.z] 
  https://bugzilla.redhat.com/show_bug.cgi?id=1772821

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

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

Title:
  wget does not honor dot-prefixed domains in no_proxy env variable

Status in wget package in Ubuntu:
  New

Bug description:
  Traditionally (AFAIK for at least the last decade), tools that support
  the no_proxy environment variable support specifying an entire
  subdomain by prefixing it with a "dot". For example, to exclude any
  website under example.com from using the proxy, you would set no_proxy
  to .example.com (export no_proxy=.example.com).

  A regression in wget 1.19 changed this behavior to expect non-prefixed
  domains (example.com vs .example.com). This regression was ultimately
  fixed and released with the 1.20 release of wget. bionic includes the
  regressed behavior version of wget.

  The regression was apparently introduced in wget 1.19.3. This bug
  should not effect other Ubuntu releases (xenial contains 1.17.1 and
  both disco and eoan contain 1.20.x versions that have the upstream
  fix).

  For more details, see references below and my additional comments on
  the RHEL8 bug filed for this issue (RH bug 1763702 linked below).

  What happens:
  no_proxy=.example.com in bionic sends requests to the proxy server for URLs 
like http://www.example.com/ despite requesting proxy exception via no_proxy.

  What should happen:
  Request should bypass the proxy and go directly to the web server. (works in 
xenial, disco and eoan as expected).

  System/software information:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy wget
  wget:
Installed: 1.19.4-1ubuntu2.2
Candidate: 1.19.4-1ubuntu2.2
Version table:
   *** 1.19.4-1ubuntu2.2 500
  500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-updates/main 
amd64 Packages
  500 http://div6mirrors.llan.ll.mit.edu:80/ubuntu bionic-security/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1.19.4-1ubuntu2 

[Touch-packages] [Bug 1860622] Re: Dependency error installing pulseaudio-esound-compat

[Jeff K]

Do you know when 1:11.1-1ubuntu7.5 will be re-released?
My update Ubuntu installation has the last version installed on Nov 22, 2019.
Also, my apt package manager doesn't seem to know about "withdrawals" so the 
rest of my pulseaudio files remain from 1:11.1-1ubuntu7.5

BTW, I was able to install pulseaudio-esound-compate 11.1-1ubuntu7.5
manually from the site you linked above so your diagnosis seems right.

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

Title:
  Dependency error installing pulseaudio-esound-compat

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  Running: apt-get install pulseaudio-esound-compat
  I get the following error:
  The following packages have unmet dependencies:
   pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 
1:11.1-1ubuntu7.5 is to be installed
  Depends: pulseaudio (= 1:11.1-1ubuntu7.4)

  Seems like pulseaudio-esound-compat has not been updated for the
  latest package versions of libpulse0 and pulseaudio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622/+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 1860622] [NEW] Dependency error installing pulseaudio-esound-compat

[Jeff K]

Public bug reported:

Running: apt-get install pulseaudio-esound-compat
I get the following error:
The following packages have unmet dependencies:
 pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 
1:11.1-1ubuntu7.5 is to be installed
Depends: pulseaudio (= 1:11.1-1ubuntu7.4)

Seems like pulseaudio-esound-compat has not been updated for the latest
package versions of libpulse0 and pulseaudio.

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

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

Title:
  Dependency error installing pulseaudio-esound-compat

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Running: apt-get install pulseaudio-esound-compat
  I get the following error:
  The following packages have unmet dependencies:
   pulseaudio-esound-compat : Depends: libpulse0 (= 1:11.1-1ubuntu7.4) but 
1:11.1-1ubuntu7.5 is to be installed
  Depends: pulseaudio (= 1:11.1-1ubuntu7.4)

  Seems like pulseaudio-esound-compat has not been updated for the
  latest package versions of libpulse0 and pulseaudio.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1860622/+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 1597840] Re: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: trying to overwrite '/usr/include/jerror.h', which is also in package libjpeg9-dev:amd64 1:9b-1u

[Brian K. White]

** Tags added: disco eoan

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

Title:
  package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade:
  trying to overwrite '/usr/include/jerror.h', which is also in package
  libjpeg9-dev:amd64 1:9b-1ubuntu1

Status in One Hundred Papercuts:
  Confirmed
Status in libjpeg-turbo package in Ubuntu:
  Confirmed
Status in libjpeg9 package in Ubuntu:
  Confirmed

Bug description:
  Just got back from restart.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-turbo8-dev 1.4.2-0ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jun 29 12:14:30 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
   libjpeg-turbo8 1.4.2-0ubuntu3
   multiarch-support 2.23-0ubuntu3
  DpkgTerminalLog:
   Preparing to unpack .../libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb ...
   Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack):
trying to overwrite '/usr/include/jerror.h', which is also in package 
libjpeg9-dev:amd64 1:9b-1ubuntu1
  DuplicateSignature:
   package:libjpeg-turbo8-dev:1.4.2-0ubuntu3
   Unpacking libjpeg-turbo8-dev:amd64 (1.4.2-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-turbo8-dev_1.4.2-0ubuntu3_amd64.deb (--unpack):
trying to overwrite '/usr/include/jerror.h', which is also in package 
libjpeg9-dev:amd64 1:9b-1ubuntu1
  ErrorMessage: trying to overwrite '/usr/include/jerror.h', which is also in 
package libjpeg9-dev:amd64 1:9b-1ubuntu1
  InstallationDate: Installed on 2016-06-13 (17 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8-dev 1.4.2-0ubuntu3 failed to install/upgrade: 
trying to overwrite '/usr/include/jerror.h', which is also in package 
libjpeg9-dev:amd64 1:9b-1ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1597840/+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 1688018] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6

[Vadym K]

18.04.3 LTS !, still reproduced, which makes me sad.

As a workaround: `sudo apt-get install resolvconf-admin`

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6

Status in network-manager package in Ubuntu:
  Triaged
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Won't Fix

Bug description:
  This was initially opened as #1671606 then later duped to #1639776.
  Discussion in #1639776 indicate that we need new bug for this so I am
  opening one ... Please don't mark this as duplicate to #1639776 or
  other similar bug report. We already lost several months and we are
  again at beginning ...

  TL;DR; -> network-manager-1.2.2-0ubuntu0.16.04.4 use DNS defined by
  VPN (correct). network-manager-1.2.6-0ubuntu0.16.04.1 use DNS from
  DHCP instead of one defined by VPN (wrong).

  DNS resolver should query only DNS servers defined by VPN while
  connection is active.

  =

  Test steps / result:

  - upgraded network-manager to 1.2.6-0ubuntu0.16.04.1 
(dnsmasq-base-2.75-1ubuntu0.16.04.2)
  - restated my laptop to ensure clean start
  - connected to VPN using openconnect / network-manager-openconnect-gnome

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by LAN connection (this is wrong / connection not working at
  all)

  - "killall dnsmasq"
  - dnsmasq get automatically restarted by system

  Observed results -> most of the the queries are forwarded to DNS
  servers defined by VPN, but lot of queries get forwarded to DNS
  servers defined by LAN connection (this is still wrong / DNS leaks,
  attacker can hijack connection even if VPN is enabled)

  - I downgraded back network-manager to 1.2.2-0ubuntu0.16.04.4 (dnsmasq-base 
stay same)
  - restated my laptop to ensure clean test
  - connected to same VPN using openconnect

  Observed results -> DNS queries are forwarded only to DNS servers
  defined by VPN connection. There are no leaks to LAN DNS server (this
  is correct behavior).

  =

  Paul Smith requested additional details in #1639776. Here are:

  * If you're using IPv4 vs. IPv6
  -> IPv4 only. I have IPv6 set to ignore on all network definition (lan / wifi 
/vpn)

  * If you have checked or unchecked the "Use this connection only for 
resources on its network"
  -> unchecked on all nw definition

  * If you have this checked, try unchecking it and see if that makes a 
difference
  -> no change if I toggle this option. Behavior is same.

  * When you say "DNS lookups" please be clear about whether the hostnames 
being looked up are public (e.g., www.google.com or whatever), on your local 
LAN, or in the network accessed via the VPN. Does it make a difference which 
one you choose?
  -> No difference.

  * Are you using fully-qualified hostnames, or relying on the DNS domain 
search path? Does it make a difference if you do it differently?
  -> I normaly use FQDN due to nature of HTTPs cert validation. I don't see 
difference when I try same using hostname + domain search.

  =

  I am using openconnect (cisco) and openvpn. Test result are by using
  openconnect but I saw same behaviour also while using openvpn.

  =

  Thanks

  Lukas

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1688018/+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 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

[Vladislav K. Valtchev]

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

Thanks Miroslav for opening this bug, two weeks after me opening bug #1846557. 
Unfortunately, it took proving that gdb couldn't debug properly _any_ 32-bit 
program, not just kernels running on QEMU, in order to get some attention. 
Honestly, I didn't even thought the bug could be _that_ bad and I didn't test 
that simple scenario. I just assumed it worked.

But, certainly, just a simple question from any maintainer about this
use-case could have helped solving this bug much earlier and saving time
to all the people it affected. I mean, it's not disappointing that it
took one month to get a fix. If the bug affected only my scenario that
would had been fine. It's disappointing that even if there was a single
_small_ 100% guilty patch, in one month, bug #1846557 did not get a
_single_ technical comment/question. We could have discovered this
broader-scope bug much earlier. It's not about fixing any bug "right
now" (bugs have priority). It's about at least talking with the reporter
and don't underestimate the scope of the bug, even if it appears to be
narrow. It might not be.

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
  on breakpoint when running a 32-bit application (on 64-bit Ubuntu).

  [Test Case]
  This can be reproduced with a simple “hello world” program:

  $ cat hello.c
  #include 
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  [Regression Risk]
  Test case ran on arm64 and regression tested using the above test case on 
amd64, i386 and s390x.

  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+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 1846557] Re: Unable to debug any kernel on i386 qemu machine

[Vladislav K. Valtchev]

A fix was released after bug #1848200, reporting the same problem, was
opened.

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

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

Title:
  Unable to debug any kernel on i386 qemu machine

Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  Hi,
  On my x86_64 machine [running Ubuntu 18.04.3 LTS] with gdb version 'Ubuntu 
8.1-0ubuntu3' I could happily debug any kernel running on a i386 qemu VM 
(qemu-system-i386) by just doing the following:

  > target remote localhost:1234
  > b term.c:694

  and then, when the breakpoint was hit I used to observe output like:

  > Breakpoint 1, term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)
  > at /home/vlad/dev/tilck/kernel/char/tty/term.c:694

  And then I was able to do `s`, `si` or `c`, exactly like with regular
  user applications.

  With the newest update of gdb, version 'Ubuntu 8.1-0ubuntu3.1', instead, 
something is broken.
  By doing the same things I observe:

  > (gdb) b term.c:693
  > warning: Breakpoint address adjusted from 0xc01158fe to 0xc01158fe.

  Which seems (and actually is) a bad sign, for what comes later. [why
  do you need to change the address? why do you want to extend it to
  64-bit for a 32-bit machine?? mmm..]

  GDB detects the breakpoint, but in a weird way:

  Program received signal SIGTRAP, Trace/breakpoint trap.
  term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)

  At this point, I'm able to read the memory and the variables BUT, I
  cannot continue the execution, NOR doing any kind of step. The
  commands apparently don't get delivered to the remote side (QEMU), or
  they get delivered in a wrong way somehow. Example output:

  (gdb) b 709
  warning: Breakpoint address adjusted from 0xc0115a45 to 0xc0115a45.
  Breakpoint 2 at 0xc0115a45: file /home/vlad/dev/tilck/kernel/char/tty/term.c, 
line 709.
  (gdb) c
  Continuing.

  Program received signal SIGTRAP, Trace/breakpoint trap.
  term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)
  at /home/vlad/dev/tilck/kernel/char/tty/term.c:693
  693t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols);
  (gdb) c
  Continuing.

  Program received signal SIGTRAP, Trace/breakpoint trap.
  term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)
  at /home/vlad/dev/tilck/kernel/char/tty/term.c:693
  693t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols);
  (gdb) c
  Continuing.

  As you see, the whole QEMU VM is stuck until I quit GDB.

  Note: I downgraded exclusively GDB back to version 'Ubuntu
  8.1-0ubuntu3' in order to check if the problem would be fixed and it
  is. I'm sure the problem has been introduced in this specific version
  'Ubuntu 8.1-0ubuntu3.1' and it's *not* related with QEMU *nor* with
  the kernel that is being debugged. It's totally independent from that.

  Final remark: note that I'm running gdb on x86_64 machine, while I'm
  debugging a kernel running on a i386 (virtual) machine. I believe that
  the cross-arch scenario almost certainly has something to do with the
  bug, as it happened in the past on both sides (qemu and gdb).

  Thanks a lot,
  Vlad

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1846557/+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 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

[Vladislav K. Valtchev]

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

** This bug has been marked a duplicate of bug 1846557
   Unable to debug any kernel on i386 qemu machine

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Fix Released
Status in gdb source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
  on breakpoint when running a 32-bit application (on 64-bit Ubuntu).

  [Test Case]
  This can be reproduced with a simple “hello world” program:

  $ cat hello.c
  #include 
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  [Regression Risk]
  Test case ran on arm64 and regression tested using the above test case on 
amd64, i386 and s390x.

  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+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 1846557] Re: Unable to debug any kernel on i386 qemu machine

[Vladislav K. Valtchev]

Hi guys,
any update on this?

Just to be sure, I tried to the Linux kernel 4.19.16 in the same
scenario and I got the same result. I built the kernel with buildroot
and I launched QEMU with:

qemu-system-i386 -kernel bzImage -S -s -append 'nokaslr'

I know it needs an initrd and a hdd img in order to boot a full system, but for 
me it was enough
to break on start_kernel and then trying to do `stepi`. Exactly like with the 
other project, with the gdb version `Ubuntu 8.1-0ubuntu3` it worked perfectly, 
while with gdb `Ubuntu 8.1-0ubuntu3.1` I got the same problem:


(gdb) b start_kernel
warning: Breakpoint address adjusted from 0xc17257cd to 0xc17257cd.
Breakpoint 1 at 0xc17257cd
(gdb) c
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
0xc17257cd in start_kernel ()
(gdb) si
0xc17257cd in start_kernel ()
(gdb) si
0xc17257cd in start_kernel ()
(gdb) si
0xc17257cd in start_kernel ()
(gdb) si


Therefore, as expected, the bug affects _definitively_ any kind of 32-bit code 
when remote debugging is used and the client is 64-bit. I also checked if the 
latest non-Ubuntu gdb is affected by this issue and it's not.

In conclusion, I believe that the following patch introduced the
regression:

http://launchpadlibrarian.net/431301516/gdb_8.1-0ubuntu3_8.1-0ubuntu3.1.diff.gz

And that the bug needs to get some attention. After all, people _cannot_
debug a 32-bit linux kernel running on a VM anymore, if they're using
Ubuntu.

@Manoj could you please comment?

Thanks

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

Title:
  Unable to debug any kernel on i386 qemu machine

Status in gdb package in Ubuntu:
  New

Bug description:
  Hi,
  On my x86_64 machine [running Ubuntu 18.04.3 LTS] with gdb version 'Ubuntu 
8.1-0ubuntu3' I could happily debug any kernel running on a i386 qemu VM 
(qemu-system-i386) by just doing the following:

  > target remote localhost:1234
  > b term.c:694

  and then, when the breakpoint was hit I used to observe output like:

  > Breakpoint 1, term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)
  > at /home/vlad/dev/tilck/kernel/char/tty/term.c:694

  And then I was able to do `s`, `si` or `c`, exactly like with regular
  user applications.

  With the newest update of gdb, version 'Ubuntu 8.1-0ubuntu3.1', instead, 
something is broken.
  By doing the same things I observe:

  > (gdb) b term.c:693
  > warning: Breakpoint address adjusted from 0xc01158fe to 0xc01158fe.

  Which seems (and actually is) a bad sign, for what comes later. [why
  do you need to change the address? why do you want to extend it to
  64-bit for a 32-bit machine?? mmm..]

  GDB detects the breakpoint, but in a weird way:

  Program received signal SIGTRAP, Trace/breakpoint trap.
  term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)

  At this point, I'm able to read the memory and the variables BUT, I
  cannot continue the execution, NOR doing any kind of step. The
  commands apparently don't get delivered to the remote side (QEMU), or
  they get delivered in a wrong way somehow. Example output:

  (gdb) b 709
  warning: Breakpoint address adjusted from 0xc0115a45 to 0xc0115a45.
  Breakpoint 2 at 0xc0115a45: file /home/vlad/dev/tilck/kernel/char/tty/term.c, 
line 709.
  (gdb) c
  Continuing.

  Program received signal SIGTRAP, Trace/breakpoint trap.
  term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)
  at /home/vlad/dev/tilck/kernel/char/tty/term.c:693
  693t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols);
  (gdb) c
  Continuing.

  Program received signal SIGTRAP, Trace/breakpoint trap.
  term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)
  at /home/vlad/dev/tilck/kernel/char/tty/term.c:693
  693t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols);
  (gdb) c
  Continuing.

  As you see, the whole QEMU VM is stuck until I quit GDB.

  Note: I downgraded exclusively GDB back to version 'Ubuntu
  8.1-0ubuntu3' in order to check if the problem would be fixed and it
  is. I'm sure the problem has been introduced in this specific version
  'Ubuntu 8.1-0ubuntu3.1' and it's *not* related with QEMU *nor* with
  the kernel that is being debugged. It's totally independent from that.

  Final remark: note that I'm running gdb on x86_64 machine, while I'm
  debugging a kernel running on a i386 (virtual) machine. I believe that
  the cross-arch scenario almost certainly has something to do with the
  bug, as it happened in the past on both sides (qemu and gdb).

  Thanks a lot,
  Vlad

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1846557/+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 1846557] [NEW] Unable to debug any kernel on i386 qemu machine

[Vladislav K. Valtchev]

Public bug reported:

Hi,
On my x86_64 machine [running Ubuntu 18.04.3 LTS] with gdb version 'Ubuntu 
8.1-0ubuntu3' I could happily debug any kernel running on a i386 qemu VM 
(qemu-system-i386) by just doing the following:

> target remote localhost:1234
> b term.c:694

and then, when the breakpoint was hit I used to observe output like:

> Breakpoint 1, term_action_use_alt_buffer (t=0xc017514c , 
> use_alt_buffer=true)
> at /home/vlad/dev/tilck/kernel/char/tty/term.c:694

And then I was able to do `s`, `si` or `c`, exactly like with regular
user applications.

With the newest update of gdb, version 'Ubuntu 8.1-0ubuntu3.1', instead, 
something is broken.
By doing the same things I observe:

> (gdb) b term.c:693
> warning: Breakpoint address adjusted from 0xc01158fe to 0xc01158fe.

Which seems (and actually is) a bad sign, for what comes later. [why do
you need to change the address? why do you want to extend it to 64-bit
for a 32-bit machine?? mmm..]

GDB detects the breakpoint, but in a weird way:

Program received signal SIGTRAP, Trace/breakpoint trap.
term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true)

At this point, I'm able to read the memory and the variables BUT, I
cannot continue the execution, NOR doing any kind of step. The commands
apparently don't get delivered to the remote side (QEMU), or they get
delivered in a wrong way somehow. Example output:

(gdb) b 709
warning: Breakpoint address adjusted from 0xc0115a45 to 0xc0115a45.
Breakpoint 2 at 0xc0115a45: file /home/vlad/dev/tilck/kernel/char/tty/term.c, 
line 709.
(gdb) c
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true)
at /home/vlad/dev/tilck/kernel/char/tty/term.c:693
693  t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols);
(gdb) c
Continuing.

Program received signal SIGTRAP, Trace/breakpoint trap.
term_action_use_alt_buffer (t=0xc017514c , use_alt_buffer=true)
at /home/vlad/dev/tilck/kernel/char/tty/term.c:693
693  t->alt_buf = kmalloc(sizeof(u16) * t->rows * t->cols);
(gdb) c
Continuing.

As you see, the whole QEMU VM is stuck until I quit GDB.

Note: I downgraded exclusively GDB back to version 'Ubuntu 8.1-0ubuntu3'
in order to check if the problem would be fixed and it is. I'm sure the
problem has been introduced in this specific version 'Ubuntu
8.1-0ubuntu3.1' and it's *not* related with QEMU *nor* with the kernel
that is being debugged. It's totally independent from that.

Final remark: note that I'm running gdb on x86_64 machine, while I'm
debugging a kernel running on a i386 (virtual) machine. I believe that
the cross-arch scenario almost certainly has something to do with the
bug, as it happened in the past on both sides (qemu and gdb).

Thanks a lot,
Vlad

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


** Tags: bionic regression-update

** Description changed:

  Hi,
  On my x86_64 machine [running Ubuntu 18.04.3 LTS] with gdb version 'Ubuntu 
8.1-0ubuntu3' I could happily debug any kernel running on a i386 qemu VM 
(qemu-system-i386) by just doing the following:
  
  > target remote localhost:1234
  > b term.c:694
  
  and then, when the breakpoint was hit I used to observe output like:
  
  > Breakpoint 1, term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)
  > at /home/vlad/dev/tilck/kernel/char/tty/term.c:694
  
  And then I was able to do `s`, `si` or `c`, exactly like with regular
  user applications.
  
  With the newest update of gdb, version 'Ubuntu 8.1-0ubuntu3.1', instead, 
something is broken.
  By doing the same things I observe:
  
  > (gdb) b term.c:693
  > warning: Breakpoint address adjusted from 0xc01158fe to 0xc01158fe.
  
- Which seems (and actually is a bad sign), for what comes later. [why do
+ Which seems (and actually is) a bad sign, for what comes later. [why do
  you need to change the address? why do you want to extend it to 64-bit
  for a 32-bit machine?? mmm..]
  
  GDB detects the breakpoint, but in a weird way:
  
  Program received signal SIGTRAP, Trace/breakpoint trap.
  term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)
  
  At this point, I'm able to read the memory and the variables BUT, I
  cannot continue the execution, NOR doing any kind of step. The commands
  apparently don't get delivered to the remote side (QEMU), or they get
  delivered in a wrong way somehow. Example output:
  
  (gdb) b 709
  warning: Breakpoint address adjusted from 0xc0115a45 to 0xc0115a45.
  Breakpoint 2 at 0xc0115a45: file /home/vlad/dev/tilck/kernel/char/tty/term.c, 
line 709.
  (gdb) c
  Continuing.
  
  Program received signal SIGTRAP, Trace/breakpoint trap.
  term_action_use_alt_buffer (t=0xc017514c , 
use_alt_buffer=true)
- at /home/vlad/dev/tilck/kernel/char/tty/term.c:693
+ at /home/vlad/dev/tilck/kernel/char/tty/term.c:693
  693t->alt_buf = kmalloc(sizeof(u16) * 

[Touch-packages] [Bug 1836328] Re: unattended-upgrades should not be enabled by default

[Vlad K.]

s/closed to/close to/ .

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

Title:
  unattended-upgrades should not be enabled by default

Status in unattended-upgrades package in Ubuntu:
  Won't Fix
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  The unattended-upgrades package and the whole concept of upgrading
  software automatically behind user's back is HARMFUL and the
  service/timer should NOT be enabled by default.

  It harms experience even for novice users with applications like
  Firefox preventing opening links until you restart it (which is
  terribad if you're in the middle of some work and don't want to do
  that at THAT particular moment!), and some other applications crashing
  in some cases, especially applications that run sub-processes
  interactively or on timers/cronjobs -- where updates to their libs or
  other dependencies create error states due to version/API/ABI
  mismatches.

  Please do not enable the service/timer by default and leave it to
  advanced users to enable assuming they understand the consequences.

  The same problem plagues snaps but that's a different bug report I
  suppose.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1836328/+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