date:20220323

This bug was fixed in the package tzdata - 2022a-0ubuntu0.21.10

---
tzdata (2022a-0ubuntu0.21.10) impish; urgency=medium

  * New upstream release (LP: #1965791):
- Palestine will spring forward on 2022-03-27 (not 2022-03-26).

 -- Brian Murray   Mon, 21 Mar 2022 12:50:13 -0700

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

Title:
  Update tzdata to version 2022a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Impish:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza | grep 'Mar.*2022'

  With the version of the package from -proposed this will show Mar 26
  not Mar 25.

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); 
print(str(tz.utcoffset(datetime(2022, 3, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1965791] Update Released

2022-03-23 Thread Chris Halse Rogers

The verification of the Stable Release Update for tzdata has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Update tzdata to version 2022a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Impish:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza | grep 'Mar.*2022'

  With the version of the package from -proposed this will show Mar 26
  not Mar 25.

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); 
print(str(tz.utcoffset(datetime(2022, 3, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1965791] Re: Update tzdata to version 2022a

This bug was fixed in the package tzdata - 2022a-0ubuntu0.20.04

---
tzdata (2022a-0ubuntu0.20.04) focal; urgency=medium

  * New upstream release (LP: #1965791):
- Palestine will spring forward on 2022-03-27 (not 2022-03-26).

 -- Brian Murray   Mon, 21 Mar 2022 13:26:35 -0700

** Changed in: tzdata (Ubuntu Focal)
   Status: Fix Committed => Fix Released

** Changed in: tzdata (Ubuntu Impish)
   Status: Fix Committed => Fix Released

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

Title:
  Update tzdata to version 2022a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Impish:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza | grep 'Mar.*2022'

  With the version of the package from -proposed this will show Mar 26
  not Mar 25.

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); 
print(str(tz.utcoffset(datetime(2022, 3, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1965791] Re: Update tzdata to version 2022a

This bug was fixed in the package tzdata - 2022a-0ubuntu0.18.04

---
tzdata (2022a-0ubuntu0.18.04) bionic; urgency=medium

  * New upstream release (LP: #1965791):
- Palestine will spring forward on 2022-03-27 (not 2022-03-26).

 -- Brian Murray   Mon, 21 Mar 2022 13:52:27 -0700

** Changed in: tzdata (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Update tzdata to version 2022a

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Bionic:
  Fix Released
Status in tzdata source package in Focal:
  Fix Released
Status in tzdata source package in Impish:
  Fix Released
Status in tzdata source package in Jammy:
  Fix Released

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza | grep 'Mar.*2022'

  With the version of the package from -proposed this will show Mar 26
  not Mar 25.

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); 
print(str(tz.utcoffset(datetime(2022, 3, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1966127] Re: ubuntu-desktop-minimal pulls gnome-session which is in universe

2022-03-23 Thread Jeremy Bicha

I think this is because ubuntu-desktop-minimal depends on gdm3.
gdm3 Recommends gnome-session | x-session-manager

While ubuntu-session provides x-session-manager, apt is trying the first
choice.

It looks like no official Ubuntu flavor besides the default desktop
version uses gdm3, so it should be safe for us to just add ubuntu-
session first in that recommends list.

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

Title:
  ubuntu-desktop-minimal pulls gnome-session which is in universe

Status in gdm3 package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ubuntu-desktop-minimal is in main but installing it pulls gnome-
  session from universe. Here is how to reproduce it:

  1) Create a Jammy VM:
  $ lxc launch images:ubuntu/jammy jammy-vm --vm
  2) Enter the Jammy VM:
  $ lxc shell jammy-vm
  3) Install ubuntu-desktop-minimal
  root@jammy-vm:~# apt-get update
  ...
  root@jammy-vm:~# apt-get install -V ubuntu-desktop-minimal
  ...
  Get:726 http://archive.ubuntu.com/ubuntu jammy/main amd64 libxfont2 amd64 
1:2.0.5-1 [94.7 kB]   
  Get:727 http://archive.ubuntu.com/ubuntu jammy/main amd64 xwayland amd64 
2:22.1.0-1 [932 kB]
  Get:728 http://archive.ubuntu.com/ubuntu jammy/universe amd64 gnome-session 
all 42.0-1ubuntu1 [15.2 kB]
  Get:729 http://archive.ubuntu.com/ubuntu jammy/main amd64 
yaru-theme-gnome-shell all 22.04.2 [66.4 kB]
  Get:730 http://archive.ubuntu.com/ubuntu jammy/main amd64 ubuntu-session all 
42.0-1ubuntu1 [5,418 B]
  ...
  4) Check the policy of packages:
  root@jammy-vm:~# apt-cache policy ubuntu-desktop-minimal gnome-session
  ubuntu-desktop-minimal:
Installed: 1.478
Candidate: 1.478
Version table:
   *** 1.478 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-session:
Installed: 42.0-1ubuntu1
Candidate: 42.0-1ubuntu1
Version table:
   *** 42.0-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Both should be from main.


  Additional information:

  root@jammy-vm:~# lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966127/+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 1966127] Re: ubuntu-desktop-minimal pulls gnome-session which is in universe

2022-03-23 Thread Jeremy Bicha

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

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

Title:
  ubuntu-desktop-minimal pulls gnome-session which is in universe

Status in gdm3 package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ubuntu-desktop-minimal is in main but installing it pulls gnome-
  session from universe. Here is how to reproduce it:

  1) Create a Jammy VM:
  $ lxc launch images:ubuntu/jammy jammy-vm --vm
  2) Enter the Jammy VM:
  $ lxc shell jammy-vm
  3) Install ubuntu-desktop-minimal
  root@jammy-vm:~# apt-get update
  ...
  root@jammy-vm:~# apt-get install -V ubuntu-desktop-minimal
  ...
  Get:726 http://archive.ubuntu.com/ubuntu jammy/main amd64 libxfont2 amd64 
1:2.0.5-1 [94.7 kB]   
  Get:727 http://archive.ubuntu.com/ubuntu jammy/main amd64 xwayland amd64 
2:22.1.0-1 [932 kB]
  Get:728 http://archive.ubuntu.com/ubuntu jammy/universe amd64 gnome-session 
all 42.0-1ubuntu1 [15.2 kB]
  Get:729 http://archive.ubuntu.com/ubuntu jammy/main amd64 
yaru-theme-gnome-shell all 22.04.2 [66.4 kB]
  Get:730 http://archive.ubuntu.com/ubuntu jammy/main amd64 ubuntu-session all 
42.0-1ubuntu1 [5,418 B]
  ...
  4) Check the policy of packages:
  root@jammy-vm:~# apt-cache policy ubuntu-desktop-minimal gnome-session
  ubuntu-desktop-minimal:
Installed: 1.478
Candidate: 1.478
Version table:
   *** 1.478 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-session:
Installed: 42.0-1ubuntu1
Candidate: 42.0-1ubuntu1
Version table:
   *** 42.0-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Both should be from main.


  Additional information:

  root@jammy-vm:~# lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1966127/+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 1966133] [NEW] /sbin/iptables symbolic links removed when upgrading from 18.04 to 20.04

2022-03-23 Thread Steve Buehrle

Public bug reported:

When upgraded from Ubuntu 18.04 to Ubuntu 20.04 the symbolic links in
/sbin are removed.

Before upgrade

# ls -al /sbin/ip*tables*
lrwxrwxrwx 1 root root 13 Nov 12  2017 /sbin/ip6tables -> xtables-multi
lrwxrwxrwx 1 root root 13 Nov 12  2017 /sbin/ip6tables-restore -> xtables-multi
lrwxrwxrwx 1 root root 13 Nov 12  2017 /sbin/ip6tables-save -> xtables-multi
lrwxrwxrwx 1 root root 13 Nov 12  2017 /sbin/iptables -> xtables-multi
lrwxrwxrwx 1 root root 13 Nov 12  2017 /sbin/iptables-restore -> xtables-multi
lrwxrwxrwx 1 root root 13 Nov 12  2017 /sbin/iptables-save -> xtables-multi


# dpkg -S /sbin/ip*tables*
iptables: /sbin/ip6tables
iptables: /sbin/ip6tables-restore
iptables: /sbin/ip6tables-save
iptables: /sbin/iptables
iptables: /sbin/iptables-restore
iptables: /sbin/iptables-save


After upgrade

# ls -al /sbin/ip*tables*
ls: cannot access '/sbin/ip*tables*': No such file or directory

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

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

Title:
  /sbin/ip*tables* symbolic links removed when upgrading from 18.04 to
  20.04

Status in iptables package in Ubuntu:
  New

Bug description:
  When upgraded from Ubuntu 18.04 to Ubuntu 20.04 the symbolic links in
  /sbin are removed.

  Before upgrade

  # ls -al /sbin/ip*tables*
  lrwxrwxrwx 1 root root 13 Nov 12  2017 /sbin/ip6tables -> xtables-multi
  lrwxrwxrwx 1 root root 13 Nov 12  2017 /sbin/ip6tables-restore -> 
xtables-multi
  lrwxrwxrwx 1 root root 13 Nov 12  2017 /sbin/ip6tables-save -> xtables-multi
  lrwxrwxrwx 1 root root 13 Nov 12  2017 /sbin/iptables -> xtables-multi
  lrwxrwxrwx 1 root root 13 Nov 12  2017 /sbin/iptables-restore -> xtables-multi
  lrwxrwxrwx 1 root root 13 Nov 12  2017 /sbin/iptables-save -> xtables-multi

  
  # dpkg -S /sbin/ip*tables*
  iptables: /sbin/ip6tables
  iptables: /sbin/ip6tables-restore
  iptables: /sbin/ip6tables-save
  iptables: /sbin/iptables
  iptables: /sbin/iptables-restore
  iptables: /sbin/iptables-save

  
  After upgrade

  # ls -al /sbin/ip*tables*
  ls: cannot access '/sbin/ip*tables*': No such file or directory

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1966133/+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 1966132] [NEW] [USB-Audio - SteelSeries Arctis 5, playback] Crackling sound about every second when audio starts

2022-03-23 Thread Nick Glyzhko

Public bug reported:

Sound is fine on any other device.
The Steelseries headphones doesn't affected by this issue on Windows 11.
Both Steelseries Game/Chat outputs are affected by this issue.
Doesn't matter if I play the sound is on the browser or download.
The crackling sound appears about every second. Ear where I hear it is always 
random. It can be quieter or louder randomly but when you increase volume, the 
crackling is also became louder.

Description: Ubuntu 20.04.4 LTS
Release: 20.04
Advanced Linux Sound Architecture Driver Version k5.13.0-37-generic.

I expect clear sound but hear repeating crackles.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 24 00:00:47 2022
InstallationDate: Installed on 2022-03-05 (18 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S5 successful
Symptom_Card: GM204 High Definition Audio Controller - HDA NVidia
Symptom_PulseAudioLog: мар 23 19:27:36 nick-pc dbus-daemon[1048]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.38' (uid=125 pid=1358 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [USB-Audio - SteelSeries Arctis 5, playback] Underruns, dropouts or 
crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2020
dmi.bios.release: 10.3
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1003
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX Z490-F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1003:bd11/30/2020:br10.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ490-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: Default string
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: ASUS
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-03-23T18:40:09.773036

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

Title:
  [USB-Audio - SteelSeries Arctis 5, playback] Crackling sound about
  every second when audio starts

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound is fine on any other device.
  The Steelseries headphones doesn't affected by this issue on Windows 11.
  Both Steelseries Game/Chat outputs are affected by this issue.
  Doesn't matter if I play the sound is on the browser or download.
  The crackling sound appears about every second. Ear where I hear it is always 
random. It can be quieter or louder randomly but when you increase volume, the 
crackling is also became louder.

  Description: Ubuntu 20.04.4 LTS
  Release: 20.04
  Advanced Linux Sound Architecture Driver Version k5.13.0-37-generic.

  I expect clear sound but hear repeating crackles.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 24 00:00:47 2022
  InstallationDate: Installed on 2022-03-05 (18 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:S5 successful
  Symptom_Card: GM204 High Definition Audio Controller - HDA NVidia
  Symptom_PulseAudioLog: мар 23 19:27:36 nick-pc dbus-daemon[1048]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.38' (uid=125 pid=1358 
comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined")
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound

[Touch-packages] [Bug 1966127] [NEW] ubuntu-desktop-minimal pulls gnome-session which is in universe

2022-03-23 Thread Simon Déziel

Public bug reported:

ubuntu-desktop-minimal is in main but installing it pulls gnome-session
from universe. Here is how to reproduce it:

1) Create a Jammy VM:
$ lxc launch images:ubuntu/jammy jammy-vm --vm
2) Enter the Jammy VM:
$ lxc shell jammy-vm
3) Install ubuntu-desktop-minimal
root@jammy-vm:~# apt-get update
...
root@jammy-vm:~# apt-get install -V ubuntu-desktop-minimal
...
Get:726 http://archive.ubuntu.com/ubuntu jammy/main amd64 libxfont2 amd64 
1:2.0.5-1 [94.7 kB]   
Get:727 http://archive.ubuntu.com/ubuntu jammy/main amd64 xwayland amd64 
2:22.1.0-1 [932 kB]
Get:728 http://archive.ubuntu.com/ubuntu jammy/universe amd64 gnome-session all 
42.0-1ubuntu1 [15.2 kB]
Get:729 http://archive.ubuntu.com/ubuntu jammy/main amd64 
yaru-theme-gnome-shell all 22.04.2 [66.4 kB]
Get:730 http://archive.ubuntu.com/ubuntu jammy/main amd64 ubuntu-session all 
42.0-1ubuntu1 [5,418 B]
...
4) Check the policy of packages:
root@jammy-vm:~# apt-cache policy ubuntu-desktop-minimal gnome-session
ubuntu-desktop-minimal:
  Installed: 1.478
  Candidate: 1.478
  Version table:
 *** 1.478 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
gnome-session:
  Installed: 42.0-1ubuntu1
  Candidate: 42.0-1ubuntu1
  Version table:
 *** 42.0-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
100 /var/lib/dpkg/status


Both should be from main.


Additional information:

root@jammy-vm:~# lsb_release -rd
Description:Ubuntu Jammy Jellyfish (development branch)
Release:22.04

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  ubuntu-desktop-minimal pulls gnome-session which is in universe

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ubuntu-desktop-minimal is in main but installing it pulls gnome-
  session from universe. Here is how to reproduce it:

  1) Create a Jammy VM:
  $ lxc launch images:ubuntu/jammy jammy-vm --vm
  2) Enter the Jammy VM:
  $ lxc shell jammy-vm
  3) Install ubuntu-desktop-minimal
  root@jammy-vm:~# apt-get update
  ...
  root@jammy-vm:~# apt-get install -V ubuntu-desktop-minimal
  ...
  Get:726 http://archive.ubuntu.com/ubuntu jammy/main amd64 libxfont2 amd64 
1:2.0.5-1 [94.7 kB]   
  Get:727 http://archive.ubuntu.com/ubuntu jammy/main amd64 xwayland amd64 
2:22.1.0-1 [932 kB]
  Get:728 http://archive.ubuntu.com/ubuntu jammy/universe amd64 gnome-session 
all 42.0-1ubuntu1 [15.2 kB]
  Get:729 http://archive.ubuntu.com/ubuntu jammy/main amd64 
yaru-theme-gnome-shell all 22.04.2 [66.4 kB]
  Get:730 http://archive.ubuntu.com/ubuntu jammy/main amd64 ubuntu-session all 
42.0-1ubuntu1 [5,418 B]
  ...
  4) Check the policy of packages:
  root@jammy-vm:~# apt-cache policy ubuntu-desktop-minimal gnome-session
  ubuntu-desktop-minimal:
Installed: 1.478
Candidate: 1.478
Version table:
   *** 1.478 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-session:
Installed: 42.0-1ubuntu1
Candidate: 42.0-1ubuntu1
Version table:
   *** 42.0-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Both should be from main.


  Additional information:

  root@jammy-vm:~# lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1966127/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest

Marc, I lean your way in terms of my feel for the likelihood that
someone is relying on incorrect behaviour in bionic/openssl-1.1.1.

I can say that while the lp1940141* patches rely on the pr9780 ones, the
reverse is absolutely not the case and thus the lp1940141 ones could be
dropped as a whole to achieve the functional portion of the backport
without it being optional.

But I leave that decision to those with more experience.

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

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  The issue leads to various client failures with TLS 1.3 as described
  in, e.g.

  https://github.com/golang/go/issues/35722
  https://github.com/golang/go/issues/34040

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file 
test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
  CertificateRequest, Length=1570
    request_context (len=0):
    extensions, length = 1567
  extension_type=status_request(5), length=1521
     - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   
0..
    000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   
0.+.0..
    001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   
0...0..
    002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   
0..1.0...UG
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest

Good point, Dan. A caveat to my work here on this patch: I did some C
programming and played with the Perl test harness in the early 90s which
gave me enough abililty to develop this patch set but I would benefit
from any deeper knowledge someone else may have, especially anyone with
openssl knowledge.

In terms of due dilligance, I've searched through the source files for
references to 'TSProxy' which is the parent directory for a number of
the test hardness perl modules changes in the commit and nothing I find
indicates it is referenced by the actual openssl C code but only is part
of the build/test process.

For extra due diligence I built with only the tests change backported
and two tests fail. Tests failing is expected because the actual
functional backport is missing. When I add the functional backport then
all tests succeed, as expected. When I then make the test optional, the
same two tests fail, as expected. See the test-results.txt attachment
for more.

I fix the tests by enabling the fix for 'Test 6' only in
openssl-1.1.1/test/recipes/70-test_tls13messages.t by wrapping the test
with perl code to set and delete the FIX_LP_1940141 environment
variable. As an aside, I now see that other such env var setting does
not use single-quoted strings but rather just bare strings; this is
allowed in perl and my patch does not followed the style in the rest of
the test file.

My understanding is that there are several flags for subtests, thus
accounting for the two passing or failing.

But more to your point about the risk of backporting the tests, my assessment
is that the perl modules are only in testing and while there are a non-trivial
number of tests added along with the one that tests what is being backported,
the fact that they all pass suggests that they are relevant here.

That is, it looks to me these additional tests are not-inappropriate, are
actually appropriate, and in fact the reason they were added later was this
fix forced the issue on the lack of capability in the test coverage.

** Attachment added: "test-results.txt"

https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+attachment/5572296/+files/test-results.txt

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

Title:
OpenSSL servers can send a non-empty status_request in a
CertificateRequest

Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Bionic:
New

Bug description:
[Impact]

openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
CertificateRequest message to the client with a non-empty
status_request extension.

This issue was fixed in openssl-1.1.1d and is included in Focal
onward.

Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
Upstream patch review at https://github.com/openssl/openssl/pull/9780

The issue leads to various client failures with TLS 1.3 as described
in, e.g.

https://github.com/golang/go/issues/35722
https://github.com/golang/go/issues/34040

[Test Plan]

The issue can be reproduced by building with `enable-ssl-trace`
and then running `s_server` like this:

```
openssl s_server -key key.pem -cert cert.pem -status_file
test/recipes/ocsp-response.der -Verify 5
```

And running `s_client` like this:

```
openssl s_client -status -trace -cert cert.pem -key key.pem
```

The output shows a `status_request` extension in the
`CertificateRequest` as follows:

Received Record
Header:
Version = TLS 1.2 (0x303)
Content Type = ApplicationData (23)
Length = 1591
Inner Content Type = Handshake (22)
CertificateRequest, Length=1570
request_context (len=0):
extensions, length = 1567
extension_type=status_request(5), length=1521
- 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2
0..
000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01
0.+.0..
001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86
0...0..
002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47
0..1.0...UG
...more lines omitted...

If the `status_request` extension is present in a
`CertificateRequest` then it must be empty according to RFC8446,
Sec. 4.4.2.1.

[Where problems could occur]

The patch disables the `status_request` extension inside a
`CertificateRequest`. Applications expecting the incorrect,
non-empty reply for the `status_request` extension will break
with this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest

uploaded to bionic queue, thanks!

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

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  The issue leads to various client failures with TLS 1.3 as described
  in, e.g.

  https://github.com/golang/go/issues/35722
  https://github.com/golang/go/issues/34040

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file 
test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
  CertificateRequest, Length=1570
    request_context (len=0):
    extensions, length = 1567
  extension_type=status_request(5), length=1521
     - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   
0..
    000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   
0.+.0..
    001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   
0...0..
    002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   
0..1.0...UG
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest

If you'd rather remove the opt-in part, that's fine with me; I can
sponsor the debdiff then with the opt-in parts left out, if that works
for you Bruce and Nicolas.

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

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  The issue leads to various client failures with TLS 1.3 as described
  in, e.g.

  https://github.com/golang/go/issues/35722
  https://github.com/golang/go/issues/34040

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file 
test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
  CertificateRequest, Length=1570
    request_context (len=0):
    extensions, length = 1567
  extension_type=status_request(5), length=1521
     - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   
0..
    000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   
0.+.0..
    001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   
0...0..
    002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   
0..1.0...UG
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1966115] Re: wrong icon used with the new branding

2022-03-23 Thread Jeremy Bicha

I think this logo comes from
https://salsa.debian.org/gnome-team/gnome-online-accounts/-/blob/ubuntu/master/debian/patches/0001-ubuntu-sso-provider.patch

with these file names
icons/scalable/goa-account-ubuntusso.svg
icons/symbolic/goa-account-ubuntusso-symbolic.svg

** Package changed: gnome-initial-setup (Ubuntu) => gnome-online-
accounts (Ubuntu)

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Triaged

** Changed in: gnome-online-accounts (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  wrong icon used with the new branding

Status in gnome-online-accounts package in Ubuntu:
  Triaged

Bug description:
  Since the updated ubuntu branding has landed, the icon isn't just the
  logo.  See attached screenshot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1966115/+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 1966115] [NEW] wrong icon used with the new branding

You have been subscribed to a public bug:

Since the updated ubuntu branding has landed, the icon isn't just the
logo.  See attached screenshot

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: iso-testing rls-jj-incoming
-- 
wrong icon used with the new branding
https://bugs.launchpad.net/bugs/1966115
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gnome-online-accounts 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 1965219] Re: gnome lock screen does not permit reentering password

2022-03-23 Thread Jeff Burdges

I'd another crash with a purple screen and no mouse movement, but this
time only a 10 minute lid close caused the crash.  Awful lot of gdm and
gnome-shell errors this time, but not clear the source.

** Attachment added: "purple_no_mouse-23_march.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965219/+attachment/5572272/+files/purple_no_mouse-23_march.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/1965219

Title:
  gnome lock screen does not permit reentering password

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Initially, only the mouse works in the gnome lock screen, without any
  way to get a password prompt.  It's likely only happening when
  returning from suspend with lid open.

  It's possible to ssh into the machine or to press Fn+Ctrl+Alt+F?? and
  login without gnome.  After this, Fn+Ctrl+Alt+F1 brings up a purple
  ubuntu login screen, but then after login you simply return to the
  lock screen with no working keyboard.  I never found any method to
  force unlock from ssh or another vt though, so this always still
  required a reboot, or killing all of gnome.

  I've randomly tried some solutions from
  https://askubuntu.com/questions/1242110/after-upgrading-to-
  ubuntu-20-04-lockscreen-not-working  including reinstalling many gnome
  components.  After this, the behavior initially disappeared by
  returning from suspend merely took a long time, like 30 seconds or 1
  minute.  It's possible the delay stems from memory size, but a
  previous identical lenovo x1 had no such problems.

  I've now a worse problem just a few hours later where unsuspend went
  directly to a purple ubuntu login screen, but neither the mouse nor
  keyboard worked.  I've not yet been able to test ssh on this problem.

  It's possibly all connected to recent firmware upgrades, so I'm happy
  to try downgrading the firmware, but I've not found any instructions
  on doing so, or even identifying the firmware upgrade log.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
  Uname: Linux 5.14.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 03:44:49 2022
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-focal-amd64-20210412-218+sutton-newell-focal-amd64+X00
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Within the last week or two
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22d5]
  InstallationDate: Installed on 2021-04-15 (335 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20210412-22:07
  MachineType: LENOVO 20XWCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.14.0-1027-oem 
root=UUID=6a411137-06bb-4de1-be93-c2fcd4f44a5a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XWCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XWCTO1WW:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XWCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XW_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XWCTO1WW
  dmi.product.sku: LENOVO_MT_20XW_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel:

[Touch-packages] [Bug 1965811] Re: software-properties-qt does not load driver information

2022-03-23 Thread Erich Eickmeyer 

** Changed in: software-properties (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  software-properties-qt does not load driver information

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Released

Bug description:
  Driver information is not being loaded by software-properties-qt. This
  appears to be a python issue, perhaps a python 3.10 compatibility
  issue.

  Traceback (most recent call last):
File 
"/usr/lib/python3/dist-packages/softwareproperties/qt/SoftwarePropertiesQt.py", 
line 1024, in detect_drivers
  self.devices = detect.system_device_drivers(self.apt_cache)
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 752, in 
system_device_drivers
  for pkg, pkginfo in system_driver_packages(apt_cache, sys_path,
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 448, in 
system_driver_packages
  for p in packages_for_modalias(apt_cache, alias):
File "/usr/lib/python3/dist-packages/UbuntuDrivers/detect.py", line 200, in 
packages_for_modalias
  apt_cache_hash = hash(package.get_fullname() for package in 
apt_cache.packages)
  AttributeError: 'Cache' object has no attribute 'packages'
  Exception ignored in: 

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-qt 0.99.19
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Mon Mar 21 11:34:54 2022
  InstallationDate: Installed on 2021-03-20 (365 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (134 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1965811/+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 1964880] Re: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'

This bug was fixed in the package software-properties - 0.99.20

---
software-properties (0.99.20) jammy; urgency=medium

  [ Alberto Milone ]
  * Update to be compatible with the new ubuntu-drivers-common version
(lp: #1964880)

 -- Sebastien Bacher   Tue, 22 Mar 2022 10:38:01
+0100

** Changed in: software-properties (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  software-properties-gtk crashed with AttributeError in
  packages_for_modalias(): 'Cache' object has no attribute 'packages'

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Released

Bug description:
  Opened up "Software & Updates" and clicked the "Additional Drivers
  Tab", for the tab to crash.

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: software-properties-gtk 0.99.19
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 15 19:02:39 2022
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2022-01-02 (72 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220101)
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/software-properties-gtk
  Python3Details: /usr/bin/python3.10, Python 3.10.2+, python3-minimal, 
3.10.1-0ubuntu2
  PythonArgs: ['/usr/bin/software-properties-gtk']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: software-properties-gtk crashed with AttributeError in 
packages_for_modalias(): 'Cache' object has no attribute 'packages'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1964880/+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 1965791] Re: Update tzdata to version 2022a

2022-03-23 Thread Leonidas S. Barbosa

Thanks Brian, trusty/xenial esm sponsored/building :)

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

Title:
  Update tzdata to version 2022a

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

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza | grep 'Mar.*2022'

  With the version of the package from -proposed this will show Mar 26
  not Mar 25.

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); 
print(str(tz.utcoffset(datetime(2022, 3, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest

2022-03-23 Thread Marc Deslauriers

ACK on the two PR9780* patches, but I must say I'm a bit uncomfortable
making a bug fix optional (which is what is done in the lp1940141*
patches).

While it does change what is returned to the client, that part shouldn't
be there in the first place. While it's nice to be overly cautious, we
don't typically make bug fixes optional unless there is an unwanted
behaviour change, and I don't think that is applicable here. This was
fixed in all later releases without causing regressions that I know of,
and having it by default will fix more users than having it be optional.

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

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  The issue leads to various client failures with TLS 1.3 as described
  in, e.g.

  https://github.com/golang/go/issues/35722
  https://github.com/golang/go/issues/34040

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file 
test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
  CertificateRequest, Length=1570
    request_context (len=0):
    extensions, length = 1567
  extension_type=status_request(5), length=1521
     - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   
0..
    000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   
0.+.0..
    001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   
0...0..
    002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   
0..1.0...UG
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1962453] Re: Apply default TTL to records obtained from getaddrinfo()

2022-03-23 Thread Shyam Prasad

Just a quick update. 
We've hit some issues during the tests, and we're trying to debug and 
understand if it's an actual bug, or a setup issue.

I will keep this page updated on the results.

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

Title:
  Apply default TTL to records obtained from getaddrinfo()

Status in keyutils package in Ubuntu:
  Fix Released
Status in keyutils source package in Bionic:
  Fix Committed
Status in keyutils source package in Focal:
  Incomplete
Status in keyutils source package in Impish:
  Incomplete

Bug description:
  [Impact]
  

  There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for
  DNS resolution. The keyutils package contains the userspace utility to
  update the kernel keyring with the DNS mapping to IP address. Prior to
  1.6.2, this utility may erroneously set unlimited lifetime for this
  keyring in the kernel.

  [Test plan]
  ===

  1. Create a file share on an SMB server (can be a samba server) with
  two IP addresses. Make sure that FQDN of the server resolves to one of
  these addresses.

  2. mount the created share on the cifs client using the FQDN for the
  server. Make sure that the mount point is accessible.

  3. Using the ss command on the client, to kill the sockets that
  connect to the server: sudo ss -K dport :445

  4. Now update the DNS entry to make sure that the server FQDN now
  resolves to the second IP address of the server. Make sure that
  nslookup on the client now resolves to the new IP address.

  5. Repeat step 3 to kill the sockets that connect to server to force
  re-connection again.

  Without the fix, after step 5, with the "ss -t" command, you'll see
  that the client has reconnected to the old IP address, even when DNS
  lookups return the new IP.

  With the fix (after a reboot of the client machine to make sure that
  kernel keys are refreshed), you'll see that the client reconnects to
  the new IP address.

  The bug is due to unlimited lifetime set by key.dns_resolver (which is
  part of keyutils package). As a result, even if IP address for the DNS
  entries change, the kernel filesystems would continue to use old IP
  address, due to the cached keys. This issue causes clients to
  misbehave when Azure Files service endpoints move to a different
  cluster.

  [Where problems could occur]
  

  Address records obtained from getaddrinfo() don't come with any TTL
  information, even if they're obtained from the DNS, so if someone is
  relying on this particularly, might face some problem/regression but I
  don't think they would face that as it would still be highly
  configurable.

  [Other information]
  ===

  This request is essentially from one of our cloud partners and they're
  highly affected by this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest

@ubuntu-security since this is openssl, could you give the debdiff a
review? I can sponsor it as a normal SRU if you have no objections (and
the changes look ok to you), as it doesn't really seem like it would
specifically need to go to the -security pocket.

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

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  The issue leads to various client failures with TLS 1.3 as described
  in, e.g.

  https://github.com/golang/go/issues/35722
  https://github.com/golang/go/issues/34040

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file 
test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
  CertificateRequest, Length=1570
    request_context (len=0):
    extensions, length = 1567
  extension_type=status_request(5), length=1521
     - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   
0..
    000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   
0.+.0..
    001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   
0...0..
    002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   
0..1.0...UG
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest

> It's not needed for actual functionality of the backport but that
assumes that any future backports or fixes don't break this backport

yes i get that, my comment is about whether or not the patch changes any
code *outside* of the self-tests, e.g. the TLSProxy perl code changes.
If that's *only* used for self-tests then including in the backport
shouldn't cause any regression.

Remember that people reviewing/sponsoring patches may not have deep
experience with the code so it's good to more clearly explain things
that aren't necessarily obvious, such as the 2nd patch only affecting
test code (if that is indeed the case), since at first glance that isn't
what it looks like.

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

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  The issue leads to various client failures with TLS 1.3 as described
  in, e.g.

  https://github.com/golang/go/issues/35722
  https://github.com/golang/go/issues/34040

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file 
test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
  CertificateRequest, Length=1570
    request_context (len=0):
    extensions, length = 1567
  extension_type=status_request(5), length=1521
     - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   
0..
    000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   
0.+.0..
    001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   
0...0..
    002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   
0..1.0...UG
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1966091] Re: Random noises with 5.13.0-37-generic but not with 5.13.0-35-generic

2022-03-23 Thread Tejesember

I can confirm this bug. I run Kubuntu 21.10, and after updating the
kernel to 5.13.0-37 (and no other packages changed), whenever audio is
active, there is a pop in like every half a second.

I have 3 audio devices. The one integrated into the motherboard seems
not to be affected. The Logitech G432 headset (which has a USB dongle),
and the Behringer U-Phoria UMC22 (which is also a USB sound device) are
producing the problem. Booting the 5.13.0-35 kernel solves the problem.

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

Title:
  Random noises with 5.13.0-37-generic but not with 5.13.0-35-generic

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After a recent update to linux-image-5.13.0-37-generic, I started
  experiencing random noises about every five seconds.  After rebooting
  into linux-image-5.13.0-35-generic, the noises were gone.

  Some details that I've noticed:

  1.  When launching pulseaudio manually, not as a daemon, the problem
  disappears.

  2.  If I set the log-level in /etc/pulse/daemon.conf to debug and
  reload it, the log has a lot of:

  Mar 23 17:22:44 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:43 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:39 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:38 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!

  Which roughly correspond with the noises.

  3.  The usual "rm -f -r ~/.config/pulse && pulseaudio -k && sudo alsa
  force-reload" doesn't seem to help.  Only a kernel downgrade does.

  4.  This happens both in Firefox (where I first noticed it) as well as
  in Totem and in system sounds.

  5.  I tried to report the bug using "ubuntu-bug audio", but it showed
  me six inputs of which three looked the same, and for each of them it
  told me that it pulseaudio wasn't configured to use it.  I'm ready to
  collect logs and other info within the next days.


  Additional Info

$ lsb_release -a
  LSB Version:  
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  Codename: focal

$ apt-cache policy linux-image-generic-hwe-20.04
  linux-image-generic-hwe-20.04:
Installed: 5.13.0.37.42~20.04.22
Candidate: 5.13.0.37.42~20.04.22
Version table:
   *** 5.13.0.37.42~20.04.22 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
  100 /var/lib/dpkg/status
   5.4.0.26.32 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

$ apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.13
Candidate: 1:13.99.1-1ubuntu3.13
Version table:
   *** 1:13.99.1-1ubuntu3.13 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.8 500
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
   1:13.99.1-1ubuntu3 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966091/+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 1965791] Re: Update tzdata to version 2022a

2022-03-23 Thread Brian Murray

Here's a debdiff for Trusty's ESM.

** Patch added: "2022a-trusty.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+attachment/5572233/+files/2022a-trusty.debdiff

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

Title:
  Update tzdata to version 2022a

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

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza | grep 'Mar.*2022'

  With the version of the package from -proposed this will show Mar 26
  not Mar 25.

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); 
print(str(tz.utcoffset(datetime(2022, 3, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1966091] Re: Random noises with 5.13.0-37-generic but not with 5.13.0-35-generic

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Random noises with 5.13.0-37-generic but not with 5.13.0-35-generic

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After a recent update to linux-image-5.13.0-37-generic, I started
  experiencing random noises about every five seconds.  After rebooting
  into linux-image-5.13.0-35-generic, the noises were gone.

  Some details that I've noticed:

  1.  When launching pulseaudio manually, not as a daemon, the problem
  disappears.

  2.  If I set the log-level in /etc/pulse/daemon.conf to debug and
  reload it, the log has a lot of:

  Mar 23 17:22:44 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:43 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:39 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:38 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!

  Which roughly correspond with the noises.

  3.  The usual "rm -f -r ~/.config/pulse && pulseaudio -k && sudo alsa
  force-reload" doesn't seem to help.  Only a kernel downgrade does.

  4.  This happens both in Firefox (where I first noticed it) as well as
  in Totem and in system sounds.

  5.  I tried to report the bug using "ubuntu-bug audio", but it showed
  me six inputs of which three looked the same, and for each of them it
  told me that it pulseaudio wasn't configured to use it.  I'm ready to
  collect logs and other info within the next days.


  Additional Info

$ lsb_release -a
  LSB Version:  
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  Codename: focal

$ apt-cache policy linux-image-generic-hwe-20.04
  linux-image-generic-hwe-20.04:
Installed: 5.13.0.37.42~20.04.22
Candidate: 5.13.0.37.42~20.04.22
Version table:
   *** 5.13.0.37.42~20.04.22 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
  100 /var/lib/dpkg/status
   5.4.0.26.32 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

$ apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.13
Candidate: 1:13.99.1-1ubuntu3.13
Version table:
   *** 1:13.99.1-1ubuntu3.13 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.8 500
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
   1:13.99.1-1ubuntu3 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966091/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2022-03-23 Thread Lukas Jerabek

still very unpleasant problem :/// I cant use headphones microphone on
zoom calls, or any other calls. I thought buying bluetooth headphones
would make my life easier... well maybe if I was using windows.

Device 78:5E:A2:6B:02:38 (public)
Name: JBL TUNE230NC TWS
Alias: JBL TUNE230NC TWS
Class: 0x00240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Serial Port   (1101--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (110d--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: Vendor specific   (----)
UUID: Vendor specific   (81c2e72a-0591-443e-a1ff-05f988593351)
UUID: Vendor specific   (8a482a08-5507-42ac-b673-a88df48b3fc7)
UUID: Vendor specific   (931c7e8a-540f-4686-b798-e8df0a2ad9f7)
UUID: Vendor specific   (df21fe2c-2515-4fdb-8886-f12c4d67927c)
UUID: Vendor specific   (f8d1fbe4-7966-4334-8024-ff96c9330e15)
Modalias: bluetooth:v02B0pd001F



index: 2
name: 
driver: 
owner module: 29
properties:
device.description = "JBL TUNE230NC TWS"
device.string = "78:5E:A2:6B:02:38"
device.api = "bluez"
device.class = "sound"
device.bus = "bluetooth"
device.form_factor = "headset"
bluez.path = "/org/bluez/hci0/dev_78_5E_A2_6B_02_38"
bluez.class = "0x240404"
bluez.alias = "JBL TUNE230NC TWS"
device.icon_name = "audio-headset-bluetooth"
device.intended_roles = "phone"
profiles:
a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
off: Off (priority 0, available: yes)
active profile: 
sinks:
bluez_sink.78_5E_A2_6B_02_38.a2dp_sink/#6: JBL TUNE230NC TWS
sources:
bluez_sink.78_5E_A2_6B_02_38.a2dp_sink.monitor/#7: Monitor of 
JBL TUNE230NC TWS
ports:
headset-output: Headset (priority 0, latency offset 0 usec, 
available: unknown)
properties:

headset-input: Headset (priority 0, latency offset 0 usec, 
available: no)
properties:

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1845797]

2022-03-23 Thread freedman.joshua

Ahh, because I said 5.16.13 didn't work; sorry ;p

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1845797/+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 1703821] Re: Dovecot and Apparmor complains at operation file_inherit

2022-03-23 Thread Bryce Harrington

** Tags added: bitesize

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

Title:
  Dovecot and Apparmor complains at operation file_inherit

Status in AppArmor:
  Fix Released
Status in apparmor package in Ubuntu:
  Expired
Status in dovecot package in Ubuntu:
  Fix Released
Status in apparmor source package in Bionic:
  New
Status in dovecot source package in Bionic:
  Triaged

Bug description:
  My server is running Ubuntu 17.04 and Dovecot 2.2.27 (c0f36b0).
  Apparmor is still complaining about problems with file_inherit. I have
  put the profiles in complain-only mode, so I can continue, but still,
  it's a problem.

  Jul 12 13:31:19 myserver kernel: [ 3905.672577] audit: type=1400
  audit(1499859079.016:363): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/lib/dovecot/anvil" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/sbin/dovecot"

  Jul 12 13:31:19 myserver kernel: [ 3905.672578] audit: type=1400
  audit(1499859079.016:364): apparmor="ALLOWED" operation="file_inherit"
  profile="/usr/sbin/dovecot" pid=3766 comm="anvil" family="unix"
  sock_type="stream" protocol=0 requested_mask="send receive"
  denied_mask="send receive" addr=none peer_addr=none
  peer="/usr/lib/dovecot/anvil"

  My configuration of Dovecot has changed slightly:

  /etc/dovecot/dovecot-sql.conf.ext
 driver = mysql
 connect = host=localhost dbname=mail user=mail password=mailpassword
 default_pass_scheme = MD5-CRYPT
 password_query = ...
 user_query = ...

  /etc/dovecot/conf.d/10-auth.conf
 disable_plaintext_auth = yes
 auth_mechanisms = plain login
 #!include auth-system.conf.ext
 !include auth-sql.conf.ext

  /etc/dovecot/conf.d/10-mail.conf
 mail_location = maildir:/var/vmail/%d/%n
 mail_uid = vmail
 mail_gid = mail
 first_valid_uid = 150
 last_valid_uid = 150

  /etc/dovecot/conf.d/10-ssl.conf
 ssl = required
 ssl_cert = 

  /usr/sbin/dovecot flags=(complain,attach_disconnected) {
#include 
#include 
#include 
#include 
#include 
#include 
#include 

capability chown,
capability dac_override,
capability fsetid,
capability kill,
capability net_bind_service,
capability setuid,
capability sys_chroot,
capability sys_resource,

/etc/dovecot/** r,
/etc/mtab r,
/etc/lsb-release r,
/etc/SuSE-release r,
@{PROC}/@{pid}/mounts r,
/usr/bin/doveconf rix,
/usr/lib/dovecot/anvil Px,
/usr/lib/dovecot/auth Px,
/usr/lib/dovecot/config Px,
/usr/lib/dovecot/dict Px,
/usr/lib/dovecot/dovecot-auth Pxmr,
/usr/lib/dovecot/imap Pxmr,
/usr/lib/dovecot/imap-login Pxmr,
/usr/lib/dovecot/lmtp Px,
/usr/lib/dovecot/log Px,
/usr/lib/dovecot/managesieve Px,
/usr/lib/dovecot/managesieve-login Pxmr,
/usr/lib/dovecot/pop3 Px,
/usr/lib/dovecot/pop3-login Pxmr,
/usr/lib/dovecot/ssl-build-param rix,
/usr/lib/dovecot/ssl-params Px,
/usr/sbin/dovecot mrix,
/usr/share/dovecot/protocols.d/   r,
/usr/share/dovecot/protocols.d/** r,
/var/lib/dovecot/ w,
/var/lib/dovecot/* rwkl,
/var/spool/postfix/private/auth w,
/var/spool/postfix/private/dovecot-lmtp w,
/{,var/}run/dovecot/ rw,
/{,var/}run/dovecot/** rw,
link /{,var/}run/dovecot/** -> /var/lib/dovecot/**,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

  Profile usr.lib.dovecot.anvil:

  #include 

  /usr/lib/dovecot/anvil flags=(complain) {
#include 
#include 

capability setuid,
capability sys_chroot,

/usr/lib/dovecot/anvil mr,

# Site-specific additions and overrides. See local/README for details.
#include 
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1703821/+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 1845797]

2022-03-23 Thread freedman.joshua

(In reply to C Sights from comment #30)
> (In reply to Josh from comment #29)
> 
> If you could git bisect the kernel and find out which commit breaks between
> 5.16.11 and 5.16.13 you might get some attention and keep the gains.

Ok, so 5.16.11 is good, 5.16.12 is bad.  I looked at the git bisect
tool, but I don't know enough to say what commits are relevant and or
bad/good.

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

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

2022-03-23 Thread freedman.joshua

5.16.11 works, is there a reason you said to bisect between 5.16.11 and
5.16.13 and not 5.16.12?

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

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

2022-03-23 Thread csights

(In reply to Josh from comment #29)

If you could git bisect the kernel and find out which commit breaks
between 5.16.11 and 5.16.13 you might get some attention and keep the
gains.

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

Title:
  Microphone not detected Lenovo Yoga S940

Status in Linux:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo
  Yoga S940

  Attached the screen of gnome sound control panel.

  Inxi output:

  System:Host:  Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: 
Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) 
  Machine:   Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga 
S940-14IWL serial:  
 Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial:  UEFI: LENOVO v: AKCN34WW date: 06/12/2019 
  CPU:   Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT 
MCP L2 cache: 8192 KiB 
 Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 
2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 
 8: 2229 
  Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: 
snd_hda_intel 
 Sound Server: ALSA v: k5.3.0-13-generic
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  daniele2239 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-09-12 (17 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 81Q7
  Package: pulseaudio 1:13.0-1ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-13-generic N/A
   linux-backports-modules-5.3.0-13-generic  N/A
   linux-firmware1.182
  Tags:  eoan
  Uname: Linux 5.3.0-13-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago)
  UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: AKCN34WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Yoga S940-14IWL
  dmi.modalias: 
dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL:
  dmi.product.family: Yoga S940-14IWL
  dmi.product.name: 81Q7
  dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL
  dmi.product.version: Lenovo Yoga S940-14IWL
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1845797/+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 1965791] Re: Update tzdata to version 2022a

2022-03-23 Thread Brian Murray

Here's a debdiff for Xenial's ESM.

** Patch added: "2022a-16.04.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+attachment/5572213/+files/2022a-16.04.debdiff

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

Title:
  Update tzdata to version 2022a

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

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza | grep 'Mar.*2022'

  With the version of the package from -proposed this will show Mar 26
  not Mar 25.

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); 
print(str(tz.utcoffset(datetime(2022, 3, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1965791/+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 1966060] Re: [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, dropouts or crackling sound

2022-03-23 Thread Hans Joachim Desserud

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

** This bug has been marked a duplicate of bug 1966059
   [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, dropouts or 
crackling sound

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

Title:
  [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns,
  dropouts or crackling sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I can rollback to old kernel and audio works fine there.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pekka  2097 F pulseaudio
   /dev/snd/controlC2:  pekka  2097 F pulseaudio
   /dev/snd/controlC0:  pekka  2097 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:59:30 2022
  InstallationDate: Installed on 2022-01-05 (76 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Sound successful
  Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
  Symptom_PulseAudioLog:
   maalis 23 12:56:55 ubuntu dbus-daemon[1217]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.38' (uid=126 pid=1429 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   maalis 23 12:57:06 ubuntu systemd[1408]: pulseaudio.service: Deactivated 
successfully.
   maalis 23 12:57:17 ubuntu systemd[1408]: pulseaudio.socket: Deactivated 
successfully.
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3103
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3103:bd06/17/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1966060/+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 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/417577

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Invalid
Status in gnome-shell source package in Focal:
  Invalid
Status in systemd source package in Focal:
  New
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Invalid
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Won't Fix
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Invalid
Status in gnome-shell source package in Impish:
  Invalid
Status in systemd source package in Impish:
  New
Status in accountsservice source package in Jammy:
  Invalid
Status in dbus source package in Jammy:
  Invalid
Status in gnome-shell source package in Jammy:
  Invalid
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * There's currently a deadlock between PID 1 and dbus-daemon: in some
  cases dbus-daemon will do NSS lookups (which are blocking) at the same
  time PID 1 synchronously blocks on some call to dbus-daemon (e.g. 
`GetConnectionUnixUser` DBus call). Let's break
  that by setting SYSTEMD_NSS_DYNAMIC_BYPASS=1 env var for dbus-daemon,
  which will disable synchronously blocking varlink calls from nss-systemd
  to PID 1.

   * This can lead to delayed boot times

   * It can also lead to dbus-daemon being killed/re-started, taking
  down other services with it, like GDM, killing user sessions on the
  way (e.g. on installing updates)

  [Test Plan]

   * This bug is really hard to reproduce, as can be seen from the
  multi-year long discussion at
  https://github.com/systemd/systemd/issues/15316

   * Canonical's CPC team has the ability to reproduce  this issue (with
  a relatively high probability) in their Azure test environment, due to
  the specific setup they are using

   * So our test plan is to ask CPC (@gjolly) for confirmation if the
  issue is fixed.

  [Where problems could occur]

   * This fix touches the communication between systemd and dbus daemon,
  especially the NSS lookup, so if something is broken the (user-)name
  resolution could be broken.

   * As a workaround dbus-daemon could be replaced by dbus-broker, which
  never showed this issue or the behaviour could be changed back by
  using the `SYSTEMD_NSS_DYNAMIC_BYPASS` env variable, like this:

  #/etc/systemd/system/dbus.service.d/override.conf
  [Service]
  Environment=SYSTEMD_NSS_DYNAMIC_BYPASS=0

  [Other Info]
   
   * Fixed upstream (v251) in https://github.com/systemd/systemd/pull/22552

  
  === Original Description ===


  
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel

[Touch-packages] [Bug 1958284] Re: shutdown hangs at "Waiting for process: ..." for 90s, ignoring DefaultTimeoutStopSec

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/417577

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

Title:
  shutdown hangs at "Waiting for process: ..." for 90s, ignoring
  DefaultTimeoutStopSec

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  Confirmed

Bug description:
  [Impact]

  The systemd shutdown sequence does not honor systemd-system.conf
  settings when waiting for remaining processes. This means that, for
  example, if a systemd service specifies KillMode=process and a process
  remaining from that service does not properly handle SIGTERM, then the
  remaining process will not be killed until after the compiled-in
  default value of DefaultTimeoutStopSec (90s), even if the user has
  changed the setting of DefaultTimeoutStopSec. In such cases, this
  impacts users by significantly increasing the time required for
  shutdown/reboot.

  [Test Plan]

  * Create a new script, /usr/local/bin/loop-ignore-sigterm:
```
#!/bin/bash
loop_forever() {
while true; do sleep 1; done
}

(
trap 'echo Ignoring SIGTERM...' SIGTERM
loop_forever
)

loop_forever
```

This script will spawn a subshell which will loop forever and ignore 
SIGTERM. This will force systemd to wait for the subprocess at 
reboot/shutdown, and eventually send SIGKILL after TimeoutStopSec 
(DefaultTimeoutStopSec in this case).

  * Make the script executable: 
$ chmod +x /usr/local/bin/loop-ignore-sigterm

  * Create a systemd service for this script. Add the following to 
/etc/systemd/system/loop-ignore-sigterm.service:
```
[Service]
KillMode=process
ExecStart=/usr/local/bin/loop-ignore-sigterm
```

  * Start the service:
$ systemctl start loop-ignore-sigterm.service

  * Edit /etc/systemd/system.conf, and uncomment the 
   'DefaultTimeoutStopSec=90s' line. Modify 90s to something much shorter, 
e.g. 20s.

  * Re-exec the daemon so this new default takes effect:
$ systemctl daemon-reexec

  * Reboot, and monitor the logs. Observe that systemd-shutdown will wait 
for the loop-ignore-sigterm process for 90s, instead of the 20s 
configured earlier.

  [Where problems could occur]

  The patch moves the reset_arguments() call to the end of main, which
  means reset_arguments() is no longer called before daemon re-execution
  (if that branch is taken). If anything in that code path relied on
  reset_arguments() being called before re-executing, those assumptions
  could be broken. Any such problems would potentially be seen during
  daemon re-execution, e.g. when calling systemctl daemon-reexec.

  [ Original Description ]

  With systemd v245 as shipped with 20.04, the shutdown sequence does
  not use the value of `DefaultTimeoutStopSec` to wait for remaining
  processes, it instead uses the compiled in default of 90s.

  This is most visible with services that use `KillMode=process`
  (docker, k8s, k3s, etc...), especially if the remaining processes do
  not handle `SIGTERM` or choose to ignore it.

  For example:
  ```
  [ OK ] Finished Reboot.
  [ OK ] Reached target Reboot.
  [ 243.652848 ] systemd-shutdown[1]: Waiting for process: containerd-shim, 
containerd-shim, containerd-shim, fluent-bit

  --- hangs here for 90s even if DefaultTimeoutStopSec is set to a lower
  value ---

  ```

  The bug has been fixed upstream here:
  https://github.com/systemd/systemd/commit/7d9eea2bd3d4f83668c7a78754d201b22

  Marc was kind enough to package the patch for 20.04 so I could test it
  
(https://launchpad.net/~mdeslaur/+archive/ubuntu/testing/+sourcepub/13210617/+listing-
  archive-extra) and with that package, I can confirm that it indeed
  fixes the issue.

  Here's a few github issues I stumbled upon while trying to debug this,
  along with a short writeup of the workaround I ended up using:

  - https://github.com/moby/moby/issues/41831
  - https://github.com/k3s-io/k3s/issues/2400
  - https://github.com/systemd/systemd/issues/16991
  - https://raby.sh/debugging-90s-hangs-during-shutdown-on-ubuntu-2004.html

  Of course, it would be much better if all the processes would properly
  handle `SIGTERM`, but having a way to enforce a maximum wait time at
  shutdown is a decent workaround.

  Given that the patch is relatively simple, would it be possible to add
  it the package for 20.04?

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1958284/+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 1966092] [NEW] apt update doesn't update Packages list

2022-03-23 Thread Rossen

Public bug reported:

I'm investigating an issue where new packages in the repository are not picked
up by hosts after running `apt-get update`. The repository is hosted on
foreman/katello via pulp and pulp_deb. I know there have been comparability
issues, but I'm not sure what is going wrong here.

There is no InRlease file (unsigned repo), but the Release file is
getting updated. However, the Packages files are not being updated
locally. See attached show how the files differ

The workaround for the moment is to delete the lists files for the
affected repository, and rerun `apt-get update`

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

** Attachment added: "aptupdate_packages_mismatch.txt"

https://bugs.launchpad.net/bugs/1966092/+attachment/5572201/+files/aptupdate_packages_mismatch.txt

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

Title:
apt update doesn't update Packages list

Status in apt package in Ubuntu:
New

Bug description:

I'm investigating an issue where new packages in the repository are not
picked up by hosts after running `apt-get update`. The repository is hosted on
foreman/katello via pulp and pulp_deb. I know there have been comparability
issues, but I'm not sure what is going wrong here.

There is no InRlease file (unsigned repo), but the Release file is
getting updated. However, the Packages files are not being updated
locally. See attached show how the files differ

The workaround for the moment is to delete the lists files for the
affected repository, and rerun `apt-get update`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1966092/+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 1966091] [NEW] Random noises with 5.13.0-37-generic but not with 5.13.0-35-generic

2022-03-23 Thread Ainar Garipov

Public bug reported:

After a recent update to linux-image-5.13.0-37-generic, I started
experiencing random noises about every five seconds.  After rebooting
into linux-image-5.13.0-35-generic, the noises were gone.

Some details that I've noticed:

1.  When launching pulseaudio manually, not as a daemon, the problem
disappears.

2.  If I set the log-level in /etc/pulse/daemon.conf to debug and reload
it, the log has a lot of:

Mar 23 17:22:44 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
Mar 23 17:22:43 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
Mar 23 17:22:39 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
Mar 23 17:22:38 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!

Which roughly correspond with the noises.

3.  The usual "rm -f -r ~/.config/pulse && pulseaudio -k && sudo alsa
force-reload" doesn't seem to help.  Only a kernel downgrade does.

4.  This happens both in Firefox (where I first noticed it) as well as
in Totem and in system sounds.

5.  I tried to report the bug using "ubuntu-bug audio", but it showed me
six inputs of which three looked the same, and for each of them it told
me that it pulseaudio wasn't configured to use it.  I'm ready to collect
logs and other info within the next days.


Additional Info

  $ lsb_release -a
LSB Version:
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
Distributor ID: Ubuntu
Description:Ubuntu 20.04.4 LTS
Release:20.04
Codename:   focal

  $ apt-cache policy linux-image-generic-hwe-20.04
linux-image-generic-hwe-20.04:
  Installed: 5.13.0.37.42~20.04.22
  Candidate: 5.13.0.37.42~20.04.22
  Version table:
 *** 5.13.0.37.42~20.04.22 500
500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
100 /var/lib/dpkg/status
 5.4.0.26.32 500
500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

  $ apt-cache policy pulseaudio
pulseaudio:
  Installed: 1:13.99.1-1ubuntu3.13
  Candidate: 1:13.99.1-1ubuntu3.13
  Version table:
 *** 1:13.99.1-1ubuntu3.13 500
500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:13.99.1-1ubuntu3.8 500
500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
 1:13.99.1-1ubuntu3 500
500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

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

Title:
  Random noises with 5.13.0-37-generic but not with 5.13.0-35-generic

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After a recent update to linux-image-5.13.0-37-generic, I started
  experiencing random noises about every five seconds.  After rebooting
  into linux-image-5.13.0-35-generic, the noises were gone.

  Some details that I've noticed:

  1.  When launching pulseaudio manually, not as a daemon, the problem
  disappears.

  2.  If I set the log-level in /etc/pulse/daemon.conf to debug and
  reload it, the log has a lot of:

  Mar 23 17:22:44 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:43 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:39 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!
  Mar 23 17:22:38 ainar-ThinkPad-X13-Gen-1 pulseaudio[76435]: Wakeup from ALSA!

  Which roughly correspond with the noises.

  3.  The usual "rm -f -r ~/.config/pulse && pulseaudio -k && sudo alsa
  force-reload" doesn't seem to help.  Only a kernel downgrade does.

  4.  This happens both in Firefox (where I first noticed it) as well as
  in Totem and in system sounds.

  5.  I tried to report the bug using "ubuntu-bug audio", but it showed
  me six inputs of which three looked the same, and for each of them it
  told me that it pulseaudio wasn't configured to use it.  I'm ready to
  collect logs and other info within the next days.


  Additional Info

$ lsb_release -a
  LSB Version:  
core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04
  Codename: focal

$ apt-cache policy linux-image-generic-hwe-20.04
  linux-image-generic-hwe-20.04:
Installed: 5.13.0.37.42~20.04.22
Candidate: 5.13.0.37.42~20.04.22
Version table:
   *** 5.13.0.37.42~20.04.22 500
  500 http://mirror.yandex.ru/ubuntu focal-updates/main amd64 Packages
  500 http://mirror.yandex.ru/ubuntu focal-security/main amd64 Packages
  100 /var/lib/dpkg/status
   5.4.0.26.32 500
  500 http://mirror.yandex.ru/ubuntu focal/main amd64 Packages

$ apt-cache policy pulseaudio

[Touch-packages] [Bug 1480923] Re: lvm thin corruption after lvresize

2022-03-23 Thread mai ling

filed https://bugzilla.redhat.com/show_bug.cgi?id=2067215, let's see how
it evolves

** Bug watch added: Red Hat Bugzilla #2067215
   https://bugzilla.redhat.com/show_bug.cgi?id=2067215

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

Title:
  lvm thin corruption after lvresize

Status in lvm2 package in Ubuntu:
  New

Bug description:
  lvm2 version 2.02.98-6ubuntu2

  After doing a lvresize of a LVM Thin Pool, I had a corruption all sub
  LVM Thin Volumes and lost all of them. Then tried to dump/repair the
  tmeta and end up with empty thin volumes (no more filesystem signature on 
them).

  To sum up
  The thin_pool was 2T and I tried to increased it to 3T...

  As fare as I know, none of the partitions were full but I increased the main
  thin pool as it was close to the sum of all sub thin volumes.

  I assume that using LVM Thin is still not stable on 14.04 LTS right?

  I guess that lvm2 2.02.98 does not properly handle the metadata resize
  of a thin pool right? (maybe add a warning somewhere in doc?)

  Maybe related to
  http://comments.gmane.org/gmane.linux.kernel.device-mapper.devel/19190
  https://www.redhat.com/archives/lvm-devel/2013-June/msg00371.html

  I managed to recover some files from the raw thin_pool (tdata/tpool) with 
scalapel
  but that is it.

  Do you known any other tools to recovery lvm thin volumes or
  partition/data on it?

  Errors

    attempt to access beyond end of device
    dm-6: rw=0, want=7753528, limit=262144
    attempt to access beyond end of device
    dm-6: rw=0, want=7753528, limit=262144
    attempt to access beyond end of device
    dm-6: rw=0, want=7753528, limit=262144
    attempt to access beyond end of device
    dm-6: rw=0, want=7753528, limit=262144

    /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 2199023190016: 
Input/output error
    /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 2199023247360: 
Input/output error
    /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 0: Input/output 
error
    /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 4096: 
Input/output error
    /dev/mainvg/thin_archive: read failed after 0 of 4096 at 805306302464: 
Input/output error
    /dev/mainvg/thin_archive: read failed after 0 of 4096 at 805306359808: 
Input/output error
    /dev/mainvg/thin_archive: read failed after 0 of 4096 at 0: Input/output 
error
    /dev/mainvg/thin_archive: read failed after 0 of 4096 at 4096: Input/output 
error

  lvs
    LV VG Attr  LSize   Pool  Origin Data%  Move Log 
Copy%  Convert
    thin_archive   mainvg Vwi-aotz- 500.00g thin_pool 94.65
    thin_rsnapshot mainvg Vwi-aotz-   1.50t thin_pool 94.01
    thin_pool  mainvg twi-a-tz-   3.00t   71.65

  lvresize -L 2T /dev/mapper/mainvg-thin_rsnapshot
    /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 1649267376128: 
Input/output error
    /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 1649267433472: 
Input/output error
    /dev/mainvg/thin_archive: read failed after 0 of 4096 at 536870846464: 
Input/output error
    /dev/mainvg/thin_archive: read failed after 0 of 4096 at 536870903808: 
Input/output error
    Extending logical volume thin_rsnapshot to 2.00 TiB
    Logical volume thin_rsnapshot successfully resized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1480923/+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 1902464] Re: The rear panel of Lenovo P620 doesn't support more than one audio device at the same time

2022-03-23 Thread David Ober

Following instruction in forwarded email after appling the alsa-ucm-
conf=1.2.2-1ubuntu0.12sutton1 package the rear microphone jack works
correctly

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Confirmed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  After backporting following patches from PA and alsa-ucm-conf and then
  it works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1902464/+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 1480923] Re: lvm thin corruption after lvresize

2022-03-23 Thread mai ling

I have just got bitten by this. I have deployed dozens of boxes with the
same cloned disk image, so I expect more will hit me sooner or later.
Does anyone if there is a Redhat bugzilla issue for it?

RHEL clone (OL8.4), kernel 5.4.17-2102.202.5.el8uek.x86_64

[root@localhost ~]# journalctl --since '2022-02-09 10:47:54' --until 
'2022-02-09 10:47:56' --no-pager
-- Logs begin at Fri 2021-04-09 13:02:56 EEST, end at Wed 2022-03-23 16:02:07 
EET. --
Feb 09 10:47:54 localhost.localdomain systemd[1]: Starting Cleanup of Temporary 
Directories...
Feb 09 10:47:54 localhost.localdomain kernel: device-mapper: btree spine: 
node_check failed: blocknr 10012793332687714485 != wanted 94
Feb 09 10:47:54 localhost.localdomain kernel: device-mapper: block manager: 
btree_node validator check failed for block 94
Feb 09 10:47:54 localhost.localdomain kernel: device-mapper: thin: 
process_cell: dm_thin_find_block() failed: error = -15
Feb 09 10:47:54 localhost.localdomain kernel: device-mapper: btree spine: 
node_check failed: blocknr 10012793332687714485 != wanted 94
Feb 09 10:47:54 localhost.localdomain kernel: device-mapper: block manager: 
btree_node validator check failed for block 94
Feb 09 10:47:54 localhost.localdomain kernel: device-mapper: thin: 
process_cell: dm_thin_find_block() failed: error = -15
Feb 09 10:47:54 localhost.localdomain kernel: device-mapper: btree spine: 
node_check failed: blocknr 10012793332687714485 != wanted 94
Feb 09 10:47:54 localhost.localdomain kernel: device-mapper: block manager: 
btree_node validator check failed for block 94
Feb 09 10:47:54 localhost.localdomain kernel: device-mapper: thin: 
process_cell: dm_thin_find_block() failed: error = -15
Feb 09 10:47:54 localhost.localdomain kernel: EXT4-fs error (device dm-10): 
__ext4_get_inode_loc:4713: inode #652801: block 2621472: comm systemd-tmpfile: 
unable to read itable block
Feb 09 10:47:54 localhost.localdomain kernel: device-mapper: btree spine: 
node_check failed: blocknr 10012793332687714485 != wanted 94
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: block manager: 
btree_node validator check failed for block 94
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: thin: 
process_cell: dm_thin_find_block() failed: error = -15
Feb 09 10:47:55 localhost.localdomain kernel: Buffer I/O error on dev dm-10, 
logical block 0, lost sync page write
Feb 09 10:47:55 localhost.localdomain kernel: EXT4-fs (dm-10): I/O error while 
writing superblock
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: btree spine: 
node_check failed: blocknr 10012793332687714485 != wanted 94
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: block manager: 
btree_node validator check failed for block 94
Feb 09 10:47:55 localhost.localdomain kernel: EXT4-fs warning (device dm-10): 
htree_dirblock_to_tree:997: inode #130564: lblock 0: comm systemd-tmpfile: 
error -5 reading directory block
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: btree spine: 
node_check failed: blocknr 10012793332687714485 != wanted 94
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: block manager: 
btree_node validator check failed for block 94
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: btree spine: 
node_check failed: blocknr 10012793332687714485 != wanted 94
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: block manager: 
btree_node validator check failed for block 94
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: btree spine: 
node_check failed: blocknr 10012793332687714485 != wanted 94
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: block manager: 
btree_node validator check failed for block 94
Feb 09 10:47:55 localhost.localdomain kernel: EXT4-fs error (device dm-10): 
__ext4_get_inode_loc:4713: inode #261121: block 1048608: comm systemd-tmpfile: 
unable to read itable block
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: btree spine: 
node_check failed: blocknr 10012793332687714485 != wanted 94
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: block manager: 
btree_node validator check failed for block 94
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: thin: 
process_cell: dm_thin_find_block() failed: error = -15
Feb 09 10:47:55 localhost.localdomain kernel: Buffer I/O error on dev dm-10, 
logical block 0, lost sync page write
Feb 09 10:47:55 localhost.localdomain kernel: EXT4-fs (dm-10): I/O error while 
writing superblock
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: btree spine: 
node_check failed: blocknr 10012793332687714485 != wanted 94
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper: block manager: 
btree_node validator check failed for block 94
Feb 09 10:47:55 localhost.localdomain kernel: EXT4-fs error (device dm-10): 
__ext4_get_inode_loc:4713: inode #522241: block 2097184: comm systemd-tmpfile: 
unable to read itable block
Feb 09 10:47:55 localhost.localdomain kernel: device-mapper:

[Touch-packages] [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest

"variable, we" -> "variable) we"
"and future" -> "any future"

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

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  The issue leads to various client failures with TLS 1.3 as described
  in, e.g.

  https://github.com/golang/go/issues/35722
  https://github.com/golang/go/issues/34040

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file 
test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
  CertificateRequest, Length=1570
    request_context (len=0):
    extensions, length = 1567
  extension_type=status_request(5), length=1521
     - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   
0..
    000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   
0.+.0..
    001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   
0...0..
    002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   
0..1.0...UG
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest

It's not needed for actual functionality of the backport but that
assumes that any future backports or fixes don't break this backport. By
adding the tests (and wrapping the one test that fails when the
backport-enabling environment variable is not set with the enabling of
that environmetn variable, we ensure that and future changes don't break
this change.

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

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  The issue leads to various client failures with TLS 1.3 as described
  in, e.g.

  https://github.com/golang/go/issues/35722
  https://github.com/golang/go/issues/34040

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file 
test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
  CertificateRequest, Length=1570
    request_context (len=0):
    extensions, length = 1567
  extension_type=status_request(5), length=1521
     - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   
0..
    000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   
0.+.0..
    001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   
0...0..
    002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   
0..1.0...UG
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1960268] Re: SSL handshake failed - VPN SSL broken in 22.04

2022-03-23 Thread Simon Chopin

I'm sorry, I still don't understand. Is Global Protect VPN a piece of
software that runs on your Ubuntu install? Do you use Remmina on top of
that, or is it a potential replacement? Which application is the one
emitting the handshake error?

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

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

Title:
  SSL handshake failed - VPN SSL broken in 22.04

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  I'm trying to connect with global protect VPN but fails at login with:

  SSL handshake failed
  Failed to load URL https://...
  QtNetwork Error 6

  Another VPN client does work but the rdp connection to a remote server fails 
with:

  transport_connect_tls:freerdp_set_last_error_ex ERRCONNECT_TLS_CONNECT_FAILED
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 21.10
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session impish
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to impish on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-03-19 (325 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  Package: openssl 3.0.1-0ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Tags:  wayland-session jammy
  Uname: Linux 5.15.0-18-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-02-04 (3 days ago)
  UserGroups: adm cdrom dialout dip docker input lpadmin lxd plugdev sambashare 
sudo uinput
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1960268/+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 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest

The 2nd upstream patch appears to add new functionality, for actually
parsing a certificate request; is that actually needed (outside of the
self-tests)? If not, it shouldn't be included in the backport.

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

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  The issue leads to various client failures with TLS 1.3 as described
  in, e.g.

  https://github.com/golang/go/issues/35722
  https://github.com/golang/go/issues/34040

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file 
test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
  CertificateRequest, Length=1570
    request_context (len=0):
    extensions, length = 1567
  extension_type=status_request(5), length=1521
     - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   
0..
    000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   
0.+.0..
    001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   
0...0..
    002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   
0..1.0...UG
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1940141/+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 1960307] Re: No gstreamer dependency causes high-fidelity codecs to be missing for Bluetooth devices

2022-03-23 Thread Ernst Sjöstrand

Up to date Jammy system as of today.
They bluetooth service list a number of aptx and ldac sink and source endpoints 
now.
However I seem to be limited to the SBC codec still.

What exactly is the "pactl [...] list-codec" command you mentioned?

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

Title:
  No gstreamer dependency causes high-fidelity codecs to be missing for
  Bluetooth devices

Status in PulseAudio:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Confirmed
Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After the announcements of PulseAudio 15 and Gstreamer 1.20, which
  both advertised LDAC and AptX (HD) support, I expected that jammy
  (22.04) would support those codecs.

  Though in reality it seems that something is missing, gstreamer
  reports that those codecs are supported but "pactl [...] list-codec"
  only lists sbc (and variants).

  Checking here https://packages.ubuntu.com/jammy/pulseaudio-module-
  bluetooth it seems that PulseAudio is not built with gstreamer
  support, is that the current blocker?

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1960307/+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 1961898] Re: chromium-browser is refusing to start

2022-03-23 Thread Christoph Singer

Same here, Chromium does not start anymore.
System: Kubuntu 21.10 with latest updates as of today

chris@kubuntu:~$ LANG=C SNAPD_DEBUG=1 snap run chromium
2022/03/23 12:09:12.183829 tool_linux.go:204: DEBUG: restarting into 
"/snap/core/current/usr/bin/snap"
2022/03/23 12:09:12.201553 cmd_run.go:1026: DEBUG: executing snap-confine from 
/snap/core/12821/usr/lib/snapd/snap-confine
2022/03/23 12:09:12.201954 cmd_run.go:433: DEBUG: SELinux not enabled
2022/03/23 12:09:12.202219 tracking.go:46: DEBUG: creating transient scope 
snap.chromium.chromium
2022/03/23 12:09:12.202980 tracking.go:186: DEBUG: using session bus
2022/03/23 12:09:12.204386 tracking.go:319: DEBUG: create transient scope job: 
/org/freedesktop/systemd1/job/561
2022/03/23 12:09:12.205375 tracking.go:419: DEBUG: job result is "failed"
error: transient scope could not be started, job 
/org/freedesktop/systemd1/job/561 finished with result failed

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

Title:
  chromium-browser is refusing to start

Status in snapd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu jammy box.

  I woke my box this morning & resumed it (from suspend; LXQt session) &
  everything was normal (many apps including chromium-browser visible on
  displays).  I can't say when I last logged in (many days no doubt!),
  but I shutdown session to use box for QA-test & comment on bug report.

  After normal reboot & logging in though I tried opening `chromium`
  many times but nothing happened (from dock in GNOME). As most of what
  I do is in `firefox` I ignored it...  It's been like that several
  hours with occasional tries & no exploration as to issue.

  On opening a terminal to try and open `chromium-browser` I get the
  following

  --
  guiverc@d960-ubu2:~$   chromium-browser 
  internal error, please report: running "chromium" failed: transient scope 
could not be started, job /org/freedesktop/systemd1/job/771 finished with 
result failed
  --

  In `journalctl` I notice

  --
  Feb 23 17:53:01 d960-ubu2 sudo[74762]:  guiverc : TTY=pts/0 ; 
PWD=/home/guiverc ; USER=root ; COMMAND=/usr/bin/journalctl
  Feb 23 17:53:01 d960-ubu2 sudo[74762]: pam_unix(sudo:session): session opened 
for user root(uid=0) by (uid=1000)
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Couldn't 
move process 74970 to requested cgrou>
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Failed to 
add PIDs to scope's control group: P>
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Failed with 
result 'resources'.
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: Failed to start 
snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope.
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Couldn't 
move process 74994 to requested c>
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Failed 
to add PIDs to scope's control grou>
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Failed 
with result 'resources'.
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: Failed to start 
snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope.
  Feb 23 17:53:07 d960-ubu2 polkitd(authority=local)[48397]: Registered 
Authentication Agent for unix-process:74411:1109253 (system bus name :1.183 
[pkttyage>
  Feb 23 17:53:11 d960-ubu2 polkit-agent-helper-1[75023]: pam_ecryptfs: 
pam_sm_authenticate: /home/guiverc is already mounted
  Feb 23 17:53:11 d960-ubu2 polkitd(authority=local)[48397]: Operator of 
unix-session:10 successfully authenticated as unix-user:guiverc to gain 
ONE-SHOT aut>
  Feb 23 17:53:11 d960-ubu2 pkexec[75020]: pam_unix(polkit-1:session): session 
opened for user root(uid=0) by (uid=1000)
  Feb 23 17:53:11 d960-ubu2 pkexec[75020]: guiverc: Executing command 
[USER=root] [TTY=/dev/pts/1] [CWD=/home/guiverc] [COMMAND=/usr/bin/dmesg]
  --
   
  I see a snap-confine error in `dmesg` but I don't think its related (nothing 
else is even close)

  [ 9697.594155] audit: type=1400 audit(1645597770.987:130):
  apparmor="DENIED" operation="capable"
  profile="/snap/core/12725/usr/lib/snapd/snap-confine" pid=73276
  comm="snap-confine" capability=4  capname="fsetid"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME

[Touch-packages] [Bug 1961898] Re: chromium-browser is refusing to start

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  chromium-browser is refusing to start

Status in snapd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu jammy box.

  I woke my box this morning & resumed it (from suspend; LXQt session) &
  everything was normal (many apps including chromium-browser visible on
  displays).  I can't say when I last logged in (many days no doubt!),
  but I shutdown session to use box for QA-test & comment on bug report.

  After normal reboot & logging in though I tried opening `chromium`
  many times but nothing happened (from dock in GNOME). As most of what
  I do is in `firefox` I ignored it...  It's been like that several
  hours with occasional tries & no exploration as to issue.

  On opening a terminal to try and open `chromium-browser` I get the
  following

  --
  guiverc@d960-ubu2:~$   chromium-browser 
  internal error, please report: running "chromium" failed: transient scope 
could not be started, job /org/freedesktop/systemd1/job/771 finished with 
result failed
  --

  In `journalctl` I notice

  --
  Feb 23 17:53:01 d960-ubu2 sudo[74762]:  guiverc : TTY=pts/0 ; 
PWD=/home/guiverc ; USER=root ; COMMAND=/usr/bin/journalctl
  Feb 23 17:53:01 d960-ubu2 sudo[74762]: pam_unix(sudo:session): session opened 
for user root(uid=0) by (uid=1000)
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Couldn't 
move process 74970 to requested cgrou>
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Failed to 
add PIDs to scope's control group: P>
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope: Failed with 
result 'resources'.
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: Failed to start 
snap.chromium.chromium.92bf8241-9710-47ef-bb6e-3642bf7db51e.scope.
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Couldn't 
move process 74994 to requested c>
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Failed 
to add PIDs to scope's control grou>
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: 
snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope: Failed 
with result 'resources'.
  Feb 23 17:53:07 d960-ubu2 systemd[12489]: Failed to start 
snap.chromium.chromedriver.0a6c0ea3-d0bb-4bbf-909b-ed15a870599c.scope.
  Feb 23 17:53:07 d960-ubu2 polkitd(authority=local)[48397]: Registered 
Authentication Agent for unix-process:74411:1109253 (system bus name :1.183 
[pkttyage>
  Feb 23 17:53:11 d960-ubu2 polkit-agent-helper-1[75023]: pam_ecryptfs: 
pam_sm_authenticate: /home/guiverc is already mounted
  Feb 23 17:53:11 d960-ubu2 polkitd(authority=local)[48397]: Operator of 
unix-session:10 successfully authenticated as unix-user:guiverc to gain 
ONE-SHOT aut>
  Feb 23 17:53:11 d960-ubu2 pkexec[75020]: pam_unix(polkit-1:session): session 
opened for user root(uid=0) by (uid=1000)
  Feb 23 17:53:11 d960-ubu2 pkexec[75020]: guiverc: Executing command 
[USER=root] [TTY=/dev/pts/1] [CWD=/home/guiverc] [COMMAND=/usr/bin/dmesg]
  --
   
  I see a snap-confine error in `dmesg` but I don't think its related (nothing 
else is even close)

  [ 9697.594155] audit: type=1400 audit(1645597770.987:130):
  apparmor="DENIED" operation="capable"
  profile="/snap/core/12725/usr/lib/snapd/snap-confine" pid=73276
  comm="snap-confine" capability=4  capname="fsetid"

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: chromium-browser 1:85.0.4183.83-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DVI-I-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAs7hAkAQEBAQAaAQOANB14KrclpFdRoCYQUFS/74CzAKlAlQCBwIGAqcBxT4EAAjqAGHE4LUBYLEUACSUhAAAeZiFQsFEAGzBAcDYACSUhAAAe/QA3TB5SEQAKICAgICAg/ABLQUxFRDI0TU9OQ0EKAJo=
   modes: 1920x1080 1600x1200 1680x1050 1600x900 1280x1024 1280x1024 1440x900 
1360x768 1280x800 1152x864 1280x720 1024x768 1024x768 1024x768 832x624 800x600 
800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
  DRM.card0-DVI-I-2:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAEchMBz9ogAhYUAQOAMx14KsKFpFZNnCUSUFSzDABxT4EAgYCVALMA0cABAQEBAjqAGHE4LUBYLEUA/h8RAAAe/QA4Sx5TEQAKICAgICAg/ABBY2VyIEcyMzVICiAg/wBMSkswVzAxNjQzMjAKAIg=
   modes: 1920x1080 1680x1050 1280x1024

[Touch-packages] [Bug 1965932] Re: package linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-5.13.0-37-generic 5.13.0-37.42~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:
  Confirmed

Bug description:
  Error experienced under a Software Updater run.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Mar 22 12:49:47 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-12-28 (83 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
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package linux-image-5.13.0-37-generic 5.13.0-37.42~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/1965932/+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 1966059] [NEW] [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, dropouts or crackling sound

2022-03-23 Thread rebd

Public bug reported:

I can rollback to old kernel and audio works fine there.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
Uname: Linux 5.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  pekka  2097 F pulseaudio
 /dev/snd/controlC2:  pekka  2097 F pulseaudio
 /dev/snd/controlC0:  pekka  2097 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:59:30 2022
InstallationDate: Installed on 2022-01-05 (76 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Sound successful
Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
Symptom_PulseAudioLog:
 maalis 23 12:56:55 ubuntu dbus-daemon[1217]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.38' 
(uid=126 pid=1429 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
 maalis 23 12:57:06 ubuntu systemd[1408]: pulseaudio.service: Deactivated 
successfully.
 maalis 23 12:57:17 ubuntu systemd[1408]: pulseaudio.socket: Deactivated 
successfully.
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, 
dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/17/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3103
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX B450-F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3103:bd06/17/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug impish

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

Title:
  [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns,
  dropouts or crackling sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I can rollback to old kernel and audio works fine there.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pekka  2097 F pulseaudio
   /dev/snd/controlC2:  pekka  2097 F pulseaudio
   /dev/snd/controlC0:  pekka  2097 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:59:30 2022
  InstallationDate: Installed on 2022-01-05 (76 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Sound successful
  Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
  Symptom_PulseAudioLog:
   maalis 23 12:56:55 ubuntu dbus-daemon[1217]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.38' (uid=126 pid=1429 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   maalis 23 12:57:06 ubuntu systemd[1408]: pulseaudio.service: Deactivated 
successfully.
   maalis 23 12:57:17 ubuntu systemd[1408]: pulseaudio.socket: Deactivated 
successfully.
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3103
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.

[Touch-packages] [Bug 1966060] [NEW] [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, dropouts or crackling sound

2022-03-23 Thread rebd

Public bug reported:

I can rollback to old kernel and audio works fine there.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
Uname: Linux 5.13.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  pekka  2097 F pulseaudio
 /dev/snd/controlC2:  pekka  2097 F pulseaudio
 /dev/snd/controlC0:  pekka  2097 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 23 12:59:30 2022
InstallationDate: Installed on 2022-01-05 (76 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Sound successful
Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
Symptom_PulseAudioLog:
 maalis 23 12:56:55 ubuntu dbus-daemon[1217]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.38' 
(uid=126 pid=1429 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" 
label="unconfined")
 maalis 23 12:57:06 ubuntu systemd[1408]: pulseaudio.service: Deactivated 
successfully.
 maalis 23 12:57:17 ubuntu systemd[1408]: pulseaudio.socket: Deactivated 
successfully.
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, 
dropouts or crackling sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/17/2020
dmi.bios.release: 5.13
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3103
dmi.board.asset.tag: Default string
dmi.board.name: ROG STRIX B450-F GAMING
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3103:bd06/17/2020:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB450-FGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug impish

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

Title:
  [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns,
  dropouts or crackling sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I can rollback to old kernel and audio works fine there.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2.2
  ProcVersionSignature: Ubuntu 5.13.0-37.42-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  pekka  2097 F pulseaudio
   /dev/snd/controlC2:  pekka  2097 F pulseaudio
   /dev/snd/controlC0:  pekka  2097 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:59:30 2022
  InstallationDate: Installed on 2022-01-05 (76 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Sound successful
  Symptom_Card: Starship/Matisse HD Audio Controller - HD-Audio Generic
  Symptom_PulseAudioLog:
   maalis 23 12:56:55 ubuntu dbus-daemon[1217]: [system] Activating via 
systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by 
':1.38' (uid=126 pid=1429 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
   maalis 23 12:57:06 ubuntu systemd[1408]: pulseaudio.service: Deactivated 
successfully.
   maalis 23 12:57:17 ubuntu systemd[1408]: pulseaudio.socket: Deactivated 
successfully.
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [USB-Audio - HyperX Virtual Surround Sound, playback] Underruns, 
dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3103
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX B450-F GAMING
  dmi.board.vendor: ASUSTeK COMPUTER INC.

[Touch-packages] [Bug 1965960] Re: apt installs snap packages

2022-03-23 Thread ts

point taken, apologies for addressing the wrong audience, who indeed
volunteer their time to help.

I do not quite agree with the metaphor, as my old parcel deliverer has taken an 
old working delivery back and pushed me a new delivery that doesn't work in my 
environment - without prior notice or leaving me any choice. 
But I see indeed that the decision has been taken and the fundamental problem 
lies somewhere else.

Thanks again.

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

Title:
  apt installs snap packages

Status in apt package in Ubuntu:
  Invalid

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  $ apt-cache policy apt
  apt:
Installed: 2.4.1
Candidate: 2.4.1
Version table:
   *** 2.4.1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) I expected to dist-upgrade my system, running apt-get dist-upgrade

  4) apt tried to install firefox from snap. I naturally aborted the upgrade, 
if I want a snap package I install it with snap, I use apt to install 
debian/apt packages.
  Aborting the install essentially broke my system. Trying to repair it, and 
installing firefox using apt again, hence getting force-fed the snap of 
firefox, broke my install, too, as the snap cannot access my firefox 
configuration files (for good reasons).
  It took me half a day to repair the system and switch to a PPA to keep the 
system (and Ubuntu with its intended processes - apt for deb, snap for snap, 
probably flatpaks and whatever for other stuff  - for that matter) running.

  In summary: We know you love snap. We use snap for certain purposes, and apt 
for others. Please don't force your love for snap on us, snaps constantly break 
long-running systems and require careful introduction.
   
  The proper solution could have been to stop supporting firefox from apt, so 
we have to consciously deal with the situation - without getting our systems 
broken.

  Thanks ❤️

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Mar 22 16:26:47 2022
  InstallationDate: Installed on 2022-03-07 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1965960/+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 1965960] Re: apt installs snap packages

2022-03-23 Thread David Kalnischkies

fwiw it is "invalid" here as apt has nothing to do with it, as it did
what it is supposed to do, upgrade a package: It has no business in the
contents, similar to a parcel deliverer. It is probably more productive
you figure out what exactly is not working in foo.deb vs. foo.snap and
report this to foo (or snap) so it can be worked on and perhaps fixed.
Currently, you are angrily complaining to your old parcel deliverer that
they brought you a letter informing you that the next letter will come
with a different parcel deliverer.

(Disclaimer: Not an Ubuntu dev, not even a user, but one of the devs of
apt itself reading "downstream" bug reports)

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

Title:
  apt installs snap packages

Status in apt package in Ubuntu:
  Invalid

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  $ apt-cache policy apt
  apt:
Installed: 2.4.1
Candidate: 2.4.1
Version table:
   *** 2.4.1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) I expected to dist-upgrade my system, running apt-get dist-upgrade

  4) apt tried to install firefox from snap. I naturally aborted the upgrade, 
if I want a snap package I install it with snap, I use apt to install 
debian/apt packages.
  Aborting the install essentially broke my system. Trying to repair it, and 
installing firefox using apt again, hence getting force-fed the snap of 
firefox, broke my install, too, as the snap cannot access my firefox 
configuration files (for good reasons).
  It took me half a day to repair the system and switch to a PPA to keep the 
system (and Ubuntu with its intended processes - apt for deb, snap for snap, 
probably flatpaks and whatever for other stuff  - for that matter) running.

  In summary: We know you love snap. We use snap for certain purposes, and apt 
for others. Please don't force your love for snap on us, snaps constantly break 
long-running systems and require careful introduction.
   
  The proper solution could have been to stop supporting firefox from apt, so 
we have to consciously deal with the situation - without getting our systems 
broken.

  Thanks ❤️

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Mar 22 16:26:47 2022
  InstallationDate: Installed on 2022-03-07 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1965960/+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 1965960] Re: apt installs snap packages

2022-03-23 Thread ts

Thanks for your attention to this bug report. I don't quite see how it's
invalid - the upgrading behavior implemented here is breaking systems
without prior notice (and without offering any choice).

The least that could have been done is warn during one update cycle and
switch over sometimes later, but the dialog has exactly one option,
which is "OK". I guess this dialog was intended as a reference to
"Qualityland" (for those who read German), but it's all but sensible or
respectful treatment of the users. I understand that the aim of Ubuntu
is to appify everything and kill off the Unix culture of easy
integration, and since I choose to use Ubuntu I will have to agree with
this policy and rebuild my systems accordingly. But please let's avoid
Ubuntu becoming like a Goliath corporation that effs up its "customers"
and doesn't give a damn.

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

Title:
  apt installs snap packages

Status in apt package in Ubuntu:
  Invalid

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  $ apt-cache policy apt
  apt:
Installed: 2.4.1
Candidate: 2.4.1
Version table:
   *** 2.4.1 500
  500 http://de.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) I expected to dist-upgrade my system, running apt-get dist-upgrade

  4) apt tried to install firefox from snap. I naturally aborted the upgrade, 
if I want a snap package I install it with snap, I use apt to install 
debian/apt packages.
  Aborting the install essentially broke my system. Trying to repair it, and 
installing firefox using apt again, hence getting force-fed the snap of 
firefox, broke my install, too, as the snap cannot access my firefox 
configuration files (for good reasons).
  It took me half a day to repair the system and switch to a PPA to keep the 
system (and Ubuntu with its intended processes - apt for deb, snap for snap, 
probably flatpaks and whatever for other stuff  - for that matter) running.

  In summary: We know you love snap. We use snap for certain purposes, and apt 
for others. Please don't force your love for snap on us, snaps constantly break 
long-running systems and require careful introduction.
   
  The proper solution could have been to stop supporting firefox from apt, so 
we have to consciously deal with the situation - without getting our systems 
broken.

  Thanks ❤️

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.1
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Mar 22 16:26:47 2022
  InstallationDate: Installed on 2022-03-07 (15 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1965960/+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 1965661] Re: software-properties-gtk crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'