[Touch-packages] [Bug 1980937] [NEW] [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise

2022-07-07 Thread fwjmath
Public bug reported:

New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake-LP
audio controller. When playing any audio, the internal speaker plays no
sound except periodic loud crackling noise. The 3.5mm jack does not work
either, producing the same craclking noise alongside some eletrical
noise. HDMI audio skimmishly tested, but also gave no sound. Curiously,
USB headphone (along with microphone) works perfectly, also the internal
microphone.

As attempts to fix the problem, I have tried the following separately, with no 
avail:
- Installing some Ubuntu OEM version of the 5.17 kernel
- Updating to the v2.2 firmware from Sound Open Firmware Project (thesofproject 
on github), reverted afterwards

I found exactly the same problem reported in the Fedora community:
https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086

As the pre-installed Windows has been destroyed, no further test on
Windows has been done.

Since USB headphone and internal microphone work, I think that there is
no problem on the Intel Tiger Lake-LP controller and its driver. The bug
probably lies elsewhere, like in the handling of ALC245 on this new
laptop model.

Thank you very much for your time and effort in advance.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  fwjmath2810 F pulseaudio
  fwjmath   72467 F alsamixer
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Thu Jul  7 10:59:22 2022
InstallationDate: Installed on 2022-06-29 (7 days ago)
InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  fwjmath2810 F pulseaudio
  fwjmath   72467 F alsamixer
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/05/2022
dmi.bios.release: 9.1
dmi.bios.vendor: HP
dmi.bios.version: T37 Ver. 01.09.01
dmi.board.name: 8AB8
dmi.board.vendor: HP
dmi.board.version: KBC Version 58.03.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 88.3
dmi.modalias: 
dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP EliteBook 840 G8 Notebook PC
dmi.product.sku: 6A3P3AV
dmi.sys.vendor: HP
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239

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


** Tags: amd64 apport-bug jammy

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

Title:
  [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal]
  No sound except loud crackling (popping) noise

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake-
  LP audio controller. When playing any audio, the internal speaker
  plays no sound except periodic loud crackling noise. The 3.5mm jack
  does not work either, producing the same craclking noise alongside
  some eletrical noise. HDMI audio skimmishly tested, but also gave no
  sound. Curiously, USB headphone (along with microphone) works
  perfectly, also the internal microphone.

  As attempts to fix the problem, I have tried the following separately, with 
no avail:
  - Installing some Ubuntu OEM version of the 5.17 kernel
  - Updating to the v2.2 firmware from Sound Open Firmware Project 
(thesofproject on github), reverted afterwards

  I found exactly the same problem reported in the Fedora community:
  
https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086

  As the pre-installed Windows has been destroyed, no further test on
  Windows has been done.

  Since USB headphone and internal microphone work, I think that there
  is no problem on the Intel Tiger Lake-LP controller and its driver.
  The bug probably lies elsewhere, like in the handling of ALC245 on
  this new laptop model.

  Thank you very much for your time and effort in advance.

  ProblemType: Bug
  

[Touch-packages] [Bug 1980804] Re: New bugfix release 22.0.5

2022-07-07 Thread Łukasz Zemczak
Hello Timo, or anyone else affected,

Accepted mesa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/22.0.5-0ubuntu0.1
in a few hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-jammy

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

Title:
  New bugfix release 22.0.5

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 22.0.x-series, we should put it
  in jammy so latest bugfixes would get there, and in focal for 20.04.5
  image.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1980804/+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 1961427] Comment bridged from LTC Bugzilla

2022-07-07 Thread bugproxy
--- Comment From mario.h...@de.ibm.com 2022-07-07 07:55 EDT---
(In reply to comment #13)
> We just realized that we had DFLTCC support in 20.04, so we need to put this
> fix there as well.

So this still gets fixed in Focal (20.04).

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

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  In Progress
Status in bedtools package in Ubuntu:
  New
Status in htslib package in Ubuntu:
  Invalid
Status in zlib package in Ubuntu:
  In Progress
Status in bedtools source package in Focal:
  Invalid
Status in htslib source package in Focal:
  New
Status in zlib source package in Focal:
  New
Status in bedtools source package in Impish:
  Won't Fix
Status in htslib source package in Impish:
  Won't Fix
Status in zlib source package in Impish:
  Won't Fix
Status in bedtools source package in Jammy:
  New
Status in htslib source package in Jammy:
  Invalid
Status in zlib source package in Jammy:
  New

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  * On top of this actual zlib fix, there is another patch needed:
   'Remove compressBound assertions. (PR #1258)' for htslib.

  * But there is a standalone 'htslib' package version, as well as a
htslib version included in (some) 'bedtools' packages.
Both need to be patched (see '[Other]' for more details).

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected by the zlib issue.

  * The 'htslib' version '1.13+ds' (as it is part of I, J and K),
already includes the patch,
hence only htslib '1.10.2' in focal needs to be patched.

  * The bedtools version '2.30.0+dfsg' (as it is part of I, J and K),
requires the patch,
but version '2.27.1+dfsg' bedtools in focal does not incl. an
embedded htslib, hence does not need to be (actually can't be)
patched.

  * Patched version of the affected htslib and bedtools packages
are build and also available at this PPA:
https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427  

  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC 

[Touch-packages] [Bug 1980545] Re: Update evolution-data-server to 3.44.3

2022-07-07 Thread Nathan Teodosio
** Changed in: evolution-data-server (Ubuntu Jammy)
   Status: Triaged => In Progress

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

Title:
  Update evolution-data-server to 3.44.3

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series.

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.3/NEWS

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1980545/+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 1980545] Re: Update evolution-data-server to 3.44.3

2022-07-07 Thread Nathan Teodosio
Merge request for ubuntu/jammy proposed at Salsa:

  https://salsa.debian.org/gnome-team/evolution-data-
server/-/merge_requests/6

Please note that, for Gmail, I could not get the Google Authentication
Request to work and thus could not access my mail. After allowing
Evolution access, it gets stuck in "Requesting access token, please
wait...". However, that is both for 3.44.2-0ubuntu1 and 3.44.3-0ubuntu1,
so this is not a problem introduced by the latter, and other accounts
such as Microsoft's work fine.

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

Title:
  Update evolution-data-server to 3.44.3

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series.

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.3/NEWS

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1980545/+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 1980689] Re: package linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-07-07 Thread Apport retracing service
** Package changed: ubuntu => initramfs-tools (Ubuntu)

** Tags removed: need-duplicate-check

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

Title:
  package linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Sending bug report.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-51-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jul  4 12:13:43 2022
  DpkgHistoryLog:
   Start-Date: 2022-07-04  12:13:07
   Commandline: /usr/bin/unattended-upgrade
   Install: linux-image-5.13.0-52-generic:amd64 (5.13.0-52.59~20.04.1, 
automatic), linux-modules-extra-5.13.0-52-generic:amd64 (5.13.0-52.59~20.04.1, 
automatic), linux-modules-5.13.0-52-generic:amd64 (5.13.0-52.59~20.04.1, 
automatic), linux-headers-5.13.0-52-generic:amd64 (5.13.0-52.59~20.04.1, 
automatic), linux-hwe-5.13-headers-5.13.0-52:amd64 (5.13.0-52.59~20.04.1, 
automatic)
   Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.13.0.51.58~20.04.31, 
5.13.0.52.59~20.04.31), linux-image-generic-hwe-20.04:amd64 
(5.13.0.51.58~20.04.31, 5.13.0.52.59~20.04.31), linux-generic-hwe-20.04:amd64 
(5.13.0.51.58~20.04.31, 5.13.0.52.59~20.04.31)
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  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/1980689/+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 1980689] [NEW] package linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-07-07 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Sending bug report.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1
ProcVersionSignature: Ubuntu 5.13.0-51.58~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-51-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Jul  4 12:13:43 2022
DpkgHistoryLog:
 Start-Date: 2022-07-04  12:13:07
 Commandline: /usr/bin/unattended-upgrade
 Install: linux-image-5.13.0-52-generic:amd64 (5.13.0-52.59~20.04.1, 
automatic), linux-modules-extra-5.13.0-52-generic:amd64 (5.13.0-52.59~20.04.1, 
automatic), linux-modules-5.13.0-52-generic:amd64 (5.13.0-52.59~20.04.1, 
automatic), linux-headers-5.13.0-52-generic:amd64 (5.13.0-52.59~20.04.1, 
automatic), linux-hwe-5.13-headers-5.13.0-52:amd64 (5.13.0-52.59~20.04.1, 
automatic)
 Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.13.0.51.58~20.04.31, 
5.13.0.52.59~20.04.31), linux-image-generic-hwe-20.04:amd64 
(5.13.0.51.58~20.04.31, 5.13.0.52.59~20.04.31), linux-generic-hwe-20.04:amd64 
(5.13.0.51.58~20.04.31, 5.13.0.52.59~20.04.31)
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3.2
 apt  2.0.9
SourcePackage: initramfs-tools
Title: package linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check
-- 
package linux-image-5.13.0-52-generic 5.13.0-52.59~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
https://bugs.launchpad.net/bugs/1980689
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools in Ubuntu.

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


[Touch-packages] [Bug 1970799] Re: wifi connection on hotspot with wpa enterprise on 22.04

2022-07-07 Thread VAN LAETHEM
OK, I'm now on site ... and it works

here is the journal log


thanks for the efforts of the team


** Attachment added: "journal log"
   
https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+attachment/5601872/+files/journal.log

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

Title:
  wifi connection on hotspot with wpa enterprise on 22.04

Status in Ubuntu MATE:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  Incomplete

Bug description:
  With 20.04 I used a wifi connection with a hotspot Telenet with following 
parametres:
  security : WPA2 entreprise
  authentification : tunneled TLS
  no AC certificat drequired
  inner authentication : MSCHAPV2(non EAP)
  user name: my id
  password : my pswd

  with 22.04 it doesn’t work anymore nor with the internal broadcom wifi
  nor with dongles (nor my Dlink 140 nor TP-link WN7200)

  This problem is only present with hotspot requesting an identification
  (user+pswd) awith hotspots without identification everything is OK

  in appendice some infos
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  michelvlt   1725 F pulseaudio
   /dev/snd/pcmC0D0p:   michelvlt   1725 F...m pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 22.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source /etc/network/interfaces.d/*
  InstallationDate: Installed on 2022-04-21 (7 days ago)
  InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  IpRoute:
   default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600 
   10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown 
   169.254.0.0/16 dev pan1 scope link metric 1000 linkdown 
   192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 
600
  MachineType: Apple Inc. MacBookPro8,1
  NonfreeKernelModules: wl
  Package: wpa
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  Tags:  jammy
  Uname: Linux 5.15.0-25-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: 06/13/2019
  dmi.bios.release: 0.1
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: 87.0.0.0.0
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245B3640C91C81
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245B3640C91C81
  dmi.modalias: 
dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro8,1
  dmi.product.sku: System SKU#
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1970799/+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 1980664] Re: package linux-image-5.14.0-1044-oem 5.14.0-1044.49 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2022-07-07 Thread Eduardo Barretto
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package linux-image-5.14.0-1044-oem 5.14.0-1044.49 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  it fails to update

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.14.0-1044-oem 5.14.0-1044.49
  ProcVersionSignature: Ubuntu 5.14.0-1042.47-oem 5.14.21
  Uname: Linux 5.14.0-1042-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Jul  4 10:15:49 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-02-11 (142 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.8
  SourcePackage: initramfs-tools
  Title: package linux-image-5.14.0-1044-oem 5.14.0-1044.49 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  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/1980664/+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 1915910] Re: evince does not print (apparmor, pxgsettings)

2022-07-07 Thread Etienne URBAH
With evince 42.3-0ubuntu2 and apparmor 3.0.4-2ubuntu2.1 on cinnamon
5.2.7-4 from Ubuntu 22.04 (Jammy Jellyfish) :

-  The 'at-spi/bus' issue is fixed.

-  The print issue is NOT fixed yet, but Karsten's workaround inside
apparmor still works.

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

Title:
  evince does not print (apparmor, pxgsettings)

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

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

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

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

  The error is reproduceable

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


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


[Touch-packages] [Bug 1980991] [NEW] /usr/sbin/on_ac_power incorrectly reporting ac power status

2022-07-07 Thread Kevin Tate
Public bug reported:

Good afternoon, folks.

I believe I discovered a bug in the /usr/sbin/on_ac_power script. I have
a Dell OptiPlex 5090 host that has an entry in /sys/class/power_supply
for "ucsi-source-psy-USBC000:001". I believe this is the USB-C power
delivery port on the front of the chassis. The issue I'm encountering is
that /usr/sbin/on_ac_power is exiting with code 1 which states: (1
(false) if not on AC power) when that isn't the case.

This looks to be because of the ucsi-source-psy-USBC000:001 entry
reporting the "online" status as 0, presumably because nothing is
currently connected to that USB-C port.

This causes /usr/sbin/on_ac_power to incorrectly report that the machine
isn't connected to AC power and causes other utilities like unattended-
upgrades to quit when using the default configuration since it believes
the machine isn't connected to AC power.

There is a workaround with unattended-upgrades where you can specify it
to run regardless of if AC power is connected, but as more and more
chassis implement power-delivery USB-C ports I foresee this becoming
more of an issue.

I'm not sure if it's anything to look into, but I figured I would share
my findings. Please let me know if you have any questions or if I can
provide any additional information, troubleshooting, or testing.

Thanks!
-Kevin

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

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

Title:
  /usr/sbin/on_ac_power incorrectly reporting ac power status

Status in powermgmt-base package in Ubuntu:
  New

Bug description:
  Good afternoon, folks.

  I believe I discovered a bug in the /usr/sbin/on_ac_power script. I
  have a Dell OptiPlex 5090 host that has an entry in
  /sys/class/power_supply for "ucsi-source-psy-USBC000:001". I believe
  this is the USB-C power delivery port on the front of the chassis. The
  issue I'm encountering is that /usr/sbin/on_ac_power is exiting with
  code 1 which states: (1 (false) if not on AC power) when that isn't
  the case.

  This looks to be because of the ucsi-source-psy-USBC000:001 entry
  reporting the "online" status as 0, presumably because nothing is
  currently connected to that USB-C port.

  This causes /usr/sbin/on_ac_power to incorrectly report that the
  machine isn't connected to AC power and causes other utilities like
  unattended-upgrades to quit when using the default configuration since
  it believes the machine isn't connected to AC power.

  There is a workaround with unattended-upgrades where you can specify
  it to run regardless of if AC power is connected, but as more and more
  chassis implement power-delivery USB-C ports I foresee this becoming
  more of an issue.

  I'm not sure if it's anything to look into, but I figured I would
  share my findings. Please let me know if you have any questions or if
  I can provide any additional information, troubleshooting, or testing.

  Thanks!
  -Kevin

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/powermgmt-base/+bug/1980991/+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 1979579] Re: jammy jellifish libsystemd-dev has wrong dependency version to libsystemd0 (and fails to install)

2022-07-07 Thread vargaconsulting.ca
*** This bug is a duplicate of bug 1979244 ***
https://bugs.launchpad.net/bugs/1979244

I don't quite understand; but something is not hmm functional...

The following packages have unmet dependencies:
 libsystemd-dev : Depends: libsystemd0 (= 249.11-0ubuntu3) but 
249.11-0ubuntu3.3 is to be installed

Thu 07 Jul 2022 03:18:36 PM EDT
steven@ivargalinux:~/src/synergy-core$ apt-cache policy libsystemd-dev
libsystemd-dev:
  Installed: (none)
  Candidate: 249.11-0ubuntu3
  Version table:
 249.11-0ubuntu3.4 1 (phased 70%)
500 http://ca.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
 249.11-0ubuntu3 500
500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

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

Title:
  jammy jellifish libsystemd-dev has wrong dependency version to
  libsystemd0 (and fails to install)

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  libsystemd-dev wants libsystemd0 = 249.11-0ubuntu3 but 249.11-0ubuntu3.1 is 
installed.
  libsystemd-dev should depend on libsystemd0 249.11-0ubuntu3.1 to allow its 
installation.

  installation currently fails:

  $ LANG=C sudo apt install libsystemd-dev
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libsystemd-dev : Depends: libsystemd0 (= 249.11-0ubuntu3) but 
249.11-0ubuntu3.1 is to be installed
  E: Unable to correct problems, you have held broken packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1979579/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

2022-07-07 Thread Nathan Teodosio
I tested libnotify4 from the proposed pocket (0.7.9-3ubuntu5.22.04.1) on
Jammy and confirm that icons are shown on launching

  notify-send-test-snap
  notify-send-test-snap.image-path
  notify-send-test-snap.image-uri

I also confirm that the six notify-send-test-snap.desktop-entry*
commands produce either

   - A `notify-send-test-snap_`-prefixed desktop ID
   - A .desktop file path (readable from both inside and outside the snap)
   - A .desktop file uri (readable from both inside and outside the snap)

as in the attachment.

** Attachment added: "out2"
   
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+attachment/5601903/+files/out2

** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  Fix Released
Status in libnotify source package in Bionic:
  Fix Committed
Status in libnotify source package in Focal:
  Fix Committed
Status in libnotify source package in Jammy:
  Fix Committed

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems.

  

  [ Impact ]

  Icons sonuds and desktop files referenced by a snapped app using
  notifications aren't exposed to the desktop in absolute paths

  [ Test case ]

  Build the test snap (or install it from the attached files to this bug):
    git clone https://github.com/3v1n0/notify-send-test-snap
    snapcraft prime
    snap try prime

  To use the pre-built snap 
(https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7)
    snap install --dangerous notify-send-test-snap_*.snap

  Check that icons are shown when launching:
    notify-send-test-snap
    notify-send-test-snap.image-path
notify-send-test-snap.image-uri

  Ensure that desktop entry is correctly sent, monitoring the dbus
  session:

   In a terminal:
     dbus-monitor --session --monitor 
"interface='org.freedesktop.Notifications'"

   In the other:
     notify-send-test-snap.desktop-entry
     notify-send-test-snap.desktop-entry-explicit-id
     notify-send-test-snap.desktop-entry-explicit-file-name
     notify-send-test-snap.desktop-entry-explicit-path
     notify-send-test-snap.desktop-entry-explicit-uri
     notify-send-test-snap.desktop-entry-explicit-snapped-uri

  The
   `desktop-entry` value sent to dbus should be either:
     - A `notify-send-test-snap_`-prefixed desktop ID
     - A .desktop file path (readable from both inside and outside the snap)
     - A .desktop file uri (readable from both inside and outside the snap)

  [ Regression potential ]

  Normal applications that are run with a SNAP environment variable set,
  might use wrong paths for files or desktop file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1981042] [NEW] /etc/localtime symlink not correctly handled when using /etc/writable

2022-07-07 Thread Robert Ancell
Public bug reported:

When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a symlink
to /etc/writable/localtime (which in itself if a symlink). Systemd
doesn't handle this correctly when doing firstboot or using inotify to
watch for changed to localtime.

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

Title:
  /etc/localtime symlink not correctly handled when using /etc/writable

Status in systemd package in Ubuntu:
  New

Bug description:
  When using /etc/writable (e.g. Ubuntu Core) /etc/localtime is a
  symlink to /etc/writable/localtime (which in itself if a symlink).
  Systemd doesn't handle this correctly when doing firstboot or using
  inotify to watch for changed to localtime.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981042/+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 1971538] Re: My machine as Wi-Fi Hotspot broken after upgrade to 22.04

2022-07-07 Thread Umar B
I seem to be having similar issues. I could connect my android phone for
a bit then it just kinda stopped. My Ipad has never been able to join
the network. sometimes with an error saying the channel is too busy
(fixed that by starting with nmcli and selecting another channel).
Otherwise, the Ipad gives the error "unable to join network" (A nice
helpful message, thanks apple)

All devices can connect to other networks (android hotstpot and wifi
router)

I've attached my log file if it'll be any help

This might be the wrong place to post, but it was the most recent
relevant bug report.

** Attachment added: "My Journalctl log file"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+attachment/5601989/+files/log

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 22.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  Upon updating to 22.04, none of my machines can use the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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