[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

[Christian Ehrhardt ]

Hi Etanay,

I realize I maybe wrote too much :-/
So I start with a TL;DR:
AFAICS you are right in all you say, but I think there can not be "one right 
answer" anyway. Hence I'm trying to leave all parties their freedom of defining 
what is important to them and try to learn from them what impact irqbalance has 
to that.


> Yes I was not arguing strictly against irqbalance, just trying
> to ascertain some discussion parameters as well as parameters for data
> collection.

Yeah, I see that and didn't intend to rebut your statements either.
Just push them a bit into potential context and POV of others.


> I have not yet seen a coherent philosophy on what it means to "optimize
> performance" with default settings that serve the greatest capacity of
> server or desktop scenarios.

That is true, but the reason for that is that you can only optimize for
something like a workload or particular HW.

The defaults are usually trying to be not too crappy for any possible
thing that might happen on e.g. Ubuntu which is quite a scope.

> In my humble opinion, data collection is useless without this
> framework of understanding what it is we are trying to achieve
> and why in terms of system performance. To me this is the deeper
> unresolved issue, perhaps.

I can see your point and would not even argue against. But this is
(this is opinion and a bit of experience, not scientific proven
truth) only the problem if we'd try to solve the singular global
and always valid "is irqbalance good or bad" question.

Thinking about it I think I'm even of the same opinion than you,
but instead of standardizing excatly what we are trying to achieve
(which to me feels like selecting a workload or HW as optimization
target) I was trying to reach out to as many groups as possible
so we can see what HW/workloads are important to them and how
irqbalance might help or interfere with that.

A bit like the old case where some clouds brought it up that it is
conflicting in virtio-net on their substrate and to be disabled
by default there (see Debian and also some Ubuntu cloud images).

I have personally no hope in reaching a general "this is good / bad"
without considering it per workload or HW environment.

Hence my hope is that if we manage to get this variety of preferences
of different parties and only then the impact of irqbalance to that
we can make compartmentalized decisions.
For example as some suggested, making it no more the default in
Desktop, but keeping it in other cases.

And this is just me trying to be helpful and drive this from being
a dormant case to something useful, I do not pretend to have the
masterplan or the solution yet :-)


> I fear that systems are currently optimized by default for throughput. For
> users, responsiveness (which can include but is not limited to throughput)
> and latency may be more important psychologically

Can I just say yes here, you go into lengths explaining (thanks) but I
already agreed here :-)

Yet - as true as that is - it is true for a set of workloads and hardware,
but not for all that Ubuntu can be (as I outlined above neither decision
could be true for all)

> And power saving is important in global terms, as even small gains
> multiplied over hundreds or thousands of deployments can have a
> significant impact

True as well, yet - again - most servers are often split by some virt
solution to pay off by their price running at high utilization.
There to reach density often people are ok to forfeit some latency
for overall throughput and thereby density which saves power by
having x% less systems active at all.


P.S. I'm now waiting for further input by all of you that found the thread so 
far as well as hopefully
some of all the teams, hardware manufacturers and clouds that I have connected 
to please think about this question.

P.P.S. I'm drifting away of seeing a big deja-vu into my decade of
Linux on mainframe performance - and density and performance and
interfering workloads that invalidated all you knew when looking
at just one ... and you know what the answer always was and still is:
"it depends" as any performance engineer will love to tell you :-)

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in Ubuntu on IBM z Systems:
  New
Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  

[Touch-packages] [Bug 2036467] Re: Resizing cloud-images occasionally fails due to superblock checksum mismatch in resize2fs

[Krister Johansen]

Hi Matthew,
Thanks for the update.  I went ahead and tested your updated packages on a 
Focal, Jammy, and Noble image in EC2 this evening.  With the latest packages 
installed, I was unable to reproduce the problem on any of the three installs.  
I'm uncertain which builds were inconsistent about triggering the problem for 
you, but it might be worth noting that the version of the package after Focal 
got an additional partial fix for the superblock checksum mismatch.  In those 
cases, it'll re-try the read of the block up to 3 times before returning a 
failure.  In my previous testing, this would increase the amount of time before 
one hits the problem, but not eliminate it entirely.

Thanks again for you help with getting these patches in.  It's much
appreciated!

-K

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

Title:
  Resizing cloud-images occasionally fails due to superblock checksum
  mismatch in resize2fs

Status in cloud-images:
  New
Status in e2fsprogs package in Ubuntu:
  In Progress
Status in e2fsprogs source package in Trusty:
  Won't Fix
Status in e2fsprogs source package in Xenial:
  Won't Fix
Status in e2fsprogs source package in Bionic:
  Won't Fix
Status in e2fsprogs source package in Focal:
  In Progress
Status in e2fsprogs source package in Jammy:
  In Progress
Status in e2fsprogs source package in Lunar:
  In Progress
Status in e2fsprogs source package in Mantic:
  In Progress

Bug description:
  [Impact]

  This is a long running bug plaguing cloud-images, where on a rare
  occasion resize2fs would fail and the image would not resize to fit
  the entire disk.

  Online resizes would fail due to a superblock checksum mismatch, where
  the superblock in memory differs from what is currently on disk due to
  changes made to the image.

  $ resize2fs /dev/nvme1n1p1
  resize2fs 1.47.0 (5-Feb-2023)
  resize2fs: Superblock checksum does not match superblock while trying to open 
/dev/nvme1n1p1
  Couldn't find valid filesystem superblock.

  Changing the read of the superblock to Direct I/O solves the issue.

  [Testcase]

  Start an c5.large instance on AWS, and attach a 60gb gp3 volume for
  use as a scratch disk.

  Run the following script, courtesy of Krister Johansen and his team:

     #!/usr/bin/bash
     set -euxo pipefail

     while true
     do
     parted /dev/nvme1n1 mklabel gpt mkpart primary 2048s 2099200s
     sleep .5
     mkfs.ext4 /dev/nvme1n1p1
     mount -t ext4 /dev/nvme1n1p1 /mnt
     stress-ng --temp-path /mnt -D 4 &
     STRESS_PID=$!
     sleep 1
     growpart /dev/nvme1n1 1
     resize2fs /dev/nvme1n1p1
     kill $STRESS_PID
     wait $STRESS_PID
     umount /mnt
     wipefs -a /dev/nvme1n1p1
     wipefs -a /dev/nvme1n1
     done

  Test packages are available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp2036467-test

  If you install the test packages, the race no longer occurs.

  [Where problems could occur]

  We are changing how resize2fs reads the superblock from underlying
  disks.

  If a regression were to occur, resize2fs could fail to resize offline
  or online volumes. As all cloud-images are online resized during their
  initial boot, this could have a large impact to public and private
  clouds should a regression occur.

  [Other info]

  Upstream mailing list discussion:
  https://lore.kernel.org/linux-ext4/20230605225221.ga5...@templeofstupid.com/
  https://lore.kernel.org/linux-ext4/20230609042239.ga1436...@mit.edu/

  This was fixed in the below commit upstream:

  commit 43a498e938887956f393b5e45ea6ac79cc5f4b84
  Author: Theodore Ts'o 
  Date: Thu, 15 Jun 2023 00:17:01 -0400
  Subject: resize2fs: use Direct I/O when reading the superblock for
   online resizes
  Link: 
https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=43a498e938887956f393b5e45ea6ac79cc5f4b84

  The commit has not been tagged to any release. All supported Ubuntu
  releases require this fix, and need to be published in standard non-
  ESM archives to be picked up in cloud images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/2036467/+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 2049051] Re: Laptop screen

[Daniel van Vugt]

The version of Mesa installed: 24.0.0.20231114.1-2088~22.04 is not
supported or provided by Ubuntu. We cannot fix any bugs it causes.

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

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

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

Title:
  Laptop screen

Status in Ubuntu:
  Invalid

Bug description:
  Laptop screen don't work after update drivers

  Ubuntu 22.04.3 LTS

  
  lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris 
Xe Graphics] (rev 01)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 17:32:30 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake-LP GT2 [Iris Xe Graphics] 
[103c:8716]
  InstallationDate: Installed on 2022-01-17 (723 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HP HP Elite Dragonfly G2 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=e2543c89-cd10-40b1-a8c0-ece1f910ccb5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2021
  dmi.bios.release: 4.1
  dmi.bios.vendor: HP
  dmi.bios.version: T90 Ver. 01.04.01
  dmi.board.name: 8716
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 37.1D.05
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 55.29
  dmi.modalias: 
dmi:bvnHP:bvrT90Ver.01.04.01:bd06/01/2021:br4.1:efr55.29:svnHP:pnHPEliteDragonflyG2NotebookPC:pvr:rvnHP:rn8716:rvrKBCVersion37.1D.05:cvnHP:ct31:cvr:sku3C6G9ES#ACB:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP Elite Dragonfly G2 Notebook PC
  dmi.product.sku: 3C6G9ES#ACB
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.0.20231114.1-2088~22.04
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2049051/+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 1922414] Re: Xorg scripts fail with "has_option: command not found"

[Daniel van Vugt]

See also bug 2049016.

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

Title:
  Xorg scripts fail with "has_option: command not found"

Status in Light Display Manager:
  Invalid
Status in gdm3 package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1922414/+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 1922414] Re: Xorg scripts fail with "has_option: command not found"

[Daniel van Vugt]

** Summary changed:

- ssh-agent fails to start (has_option: command not found)
+ Xorg scripts fail with "has_option: command not found"

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

Title:
  Xorg scripts fail with "has_option: command not found"

Status in Light Display Manager:
  Invalid
Status in gdm3 package in Ubuntu:
  Fix Released
Status in lightdm package in Ubuntu:
  Invalid
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1922414/+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 2043915] Re: Booting into live session results in try/install page white screen

[Nobuto Murata]

Just to give a data point, mesa/23.3.3-1ubuntu1 fixes many issues with
snaps and LibGL on my laptop, namely:

- white blank screen when opening firmware-updater snap
- no OpenGL hardware acceleration but software rendering only in chromium snap, 
and missing background effect in Google Meet because of that
- Zoom snap wouldn't start with "Failed to create OpenGL context"

And by installing the ubuntu-desktop-installer snap by hand after
updating to mesa/23.3.3-1ubuntu1, I don't see the white blank window any
longer. I'm pretty sure the issue will go away when mesa/23.3.3-1ubuntu1
gets promoted to noble from noble-proposed and a new image gets built.

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

Title:
  Booting into live session results in try/install page white screen

Status in ubuntu-desktop-installer:
  New
Status in mesa package in Ubuntu:
  Fix Committed

Bug description:
  Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into
  live session results in try/install page white screen.Selecting
  install from the dash results in same white screen.

  see the attached screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.487
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 19 07:02:48 2023
  LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2043915] Re: Booting into live session results in try/install page white screen

[Daniel van Vugt]

From what I read of overnight discussions, it is believed that Mesa
23.3.3 has a fix. Looks like some kind of GLX protocol breakage happened
in 23.3.0?

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

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

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

Title:
  Booting into live session results in try/install page white screen

Status in ubuntu-desktop-installer:
  New
Status in mesa package in Ubuntu:
  Fix Committed

Bug description:
  Testing Ubuntu Noble desktop daily ISO dated 19-11-2023 - Booting into
  live session results in try/install page white screen.Selecting
  install from the dash results in same white screen.

  see the attached screen shot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.487
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 19 07:02:48 2023
  LiveMediaBuild: Ubuntu 24.04 "Noble Numbat" - Daily amd64 (20231119)
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-desktop-installer/+bug/2043915/+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 2049117] Re: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep

[Jānis Kangarooo]

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

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

Title:
  [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No
  sound at all From google Chrome youtube after putting computer to
  sleep

Status in alsa-driver package in Ubuntu:
  Invalid
Status in plasma-workspace package in Ubuntu:
  New

Bug description:
  [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound 
at all From google Chrome youtube after putting computer to sleep
  From testing sound came but not from google chrome
  ---=== Update ===---
  False alarm. Sound i was able to put back on, turn out i dont remember i 
turned off sound on Chrome in task menu of Kubuntu. Icon shows sound playing 
and when clicking sound speaker icon in taskbar of chrome then it shows very 
thin line that sound is turned mute off.
  === Suggestion ===
  Since i dont remember i turned it off or dont see big difference or red icon 
that sound is off then i dont know its off.
  NEED different icon (size, more contrast, red color, round red X sign) so i 
can see warning that sound is off. image attached how hard it is to see any 
difference from speaker icon when turned off

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kng2239 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jan 12 01:20:49 2024
  InstallationDate: Installed on 2024-01-05 (6 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kng2239 F pulseaudio
   /dev/snd/pcmC0D0p:   kng2239 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2023
  dmi.bios.release: 15.0
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.15.00
  dmi.board.name: 87E0
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.24.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.36
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.15.00:bd10/06/2023:br15.0:efr51.36:svnHP:pnHPProBook440G8NotebookPC:pvrSBKPF:rvnHP:rn87E0:rvrKBCVersion33.24.00:cvnHP:ct10:cvr:sku27J72EA#B1R:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 440 G8 Notebook PC
  dmi.product.sku: 27J72EA#B1R
  dmi.product.version: SBKPF
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2049117/+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 2049119] Re: my audio wont work at all no mater what i do

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  my audio wont work at all no mater what i do

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  i had updated some stuff such as chrome and fire fox and after that my
  volume keys stopped working then my volume would turn up and down on
  its own then i couldn't even adjust the volume from settings and it
  would be on full blast and now its just wont work anymore

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gage   1069 F wireplumber
   /dev/snd/controlC0:  gage   1069 F wireplumber
   /dev/snd/seq:gage   1062 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Jan 11 18:36:25 2024
  InstallationDate: Installed on 2023-12-19 (23 days ago)
  InstallationMedia: Ubuntu-Unity 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/04/2023
  dmi.bios.release: 15.72
  dmi.bios.vendor: AMI
  dmi.bios.version: F.72
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 87B7
  dmi.board.vendor: HP
  dmi.board.version: 28.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 28.23
  dmi.modalias: 
dmi:bvnAMI:bvrF.72:bd10/04/2023:br15.72:efr28.23:svnHP:pnHPLaptop14-fq0xxx:pvr:rvnHP:rn87B7:rvr28.23:cvnHP:ct10:cvrChassisVersion:sku26Z02UA#ABA:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 14-fq0xxx
  dmi.product.sku: 26Z02UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2049119/+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 2049119] [NEW] my audio wont work at all no mater what i do

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

i had updated some stuff such as chrome and fire fox and after that my
volume keys stopped working then my volume would turn up and down on its
own then i couldn't even adjust the volume from settings and it would be
on full blast and now its just wont work anymore

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  gage   1069 F wireplumber
 /dev/snd/controlC0:  gage   1069 F wireplumber
 /dev/snd/seq:gage   1062 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: Unity:Unity7:ubuntu
Date: Thu Jan 11 18:36:25 2024
InstallationDate: Installed on 2023-12-19 (23 days ago)
InstallationMedia: Ubuntu-Unity 23.10 "Mantic Minotaur" - Release amd64 
(20231010)
PackageArchitecture: all
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/04/2023
dmi.bios.release: 15.72
dmi.bios.vendor: AMI
dmi.bios.version: F.72
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 87B7
dmi.board.vendor: HP
dmi.board.version: 28.23
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 28.23
dmi.modalias: 
dmi:bvnAMI:bvrF.72:bd10/04/2023:br15.72:efr28.23:svnHP:pnHPLaptop14-fq0xxx:pvr:rvnHP:rn87B7:rvr28.23:cvnHP:ct10:cvrChassisVersion:sku26Z02UA#ABA:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 14-fq0xxx
dmi.product.sku: 26Z02UA#ABA
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug mantic
-- 
my audio wont work at all no mater what i do
https://bugs.launchpad.net/bugs/2049119
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver 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 2049117] Re: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep

[Jānis Kangarooo]

Here is sound on, and it looks the same so small

** Attachment added: "Screenshot_20240112_014238.png"
   
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/2049117/+attachment/5738602/+files/Screenshot_20240112_014238.png

** Description changed:

  [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound 
at all From google Chrome youtube after putting computer to sleep
  From testing sound came but not from google chrome
  ---=== Update ===---
- False alarm. Sound i was able to put back on, turn out i dont remember i 
turned off sound on Chrome in task menu of Kubuntu. Icon shows sound playing 
and when clicking sound speaker icon in taskbar of chrome then it shows very 
thin line that sound is turned mute off. 
+ False alarm. Sound i was able to put back on, turn out i dont remember i 
turned off sound on Chrome in task menu of Kubuntu. Icon shows sound playing 
and when clicking sound speaker icon in taskbar of chrome then it shows very 
thin line that sound is turned mute off.
  === Suggestion ===
+ Since i dont remember i turned it off or dont see big difference or red icon 
that sound is off then i dont know its off.
  Make different icon so i can see warning that sound is off. image attached 
how hard it is to see any difference from speaker icon when turned off
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kng2239 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jan 12 01:20:49 2024
  InstallationDate: Installed on 2024-01-05 (6 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kng2239 F pulseaudio
   /dev/snd/pcmC0D0p:   kng2239 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2023
  dmi.bios.release: 15.0
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.15.00
  dmi.board.name: 87E0
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.24.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.36
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.15.00:bd10/06/2023:br15.0:efr51.36:svnHP:pnHPProBook440G8NotebookPC:pvrSBKPF:rvnHP:rn87E0:rvrKBCVersion33.24.00:cvnHP:ct10:cvr:sku27J72EA#B1R:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 440 G8 Notebook PC
  dmi.product.sku: 27J72EA#B1R
  dmi.product.version: SBKPF
  dmi.sys.vendor: HP

** Description changed:

  [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound 
at all From google Chrome youtube after putting computer to sleep
  From testing sound came but not from google chrome
  ---=== Update ===---
  False alarm. Sound i was able to put back on, turn out i dont remember i 
turned off sound on Chrome in task menu of Kubuntu. Icon shows sound playing 
and when clicking sound speaker icon in taskbar of chrome then it shows very 
thin line that sound is turned mute off.
  === Suggestion ===
  Since i dont remember i turned it off or dont see big difference or red icon 
that sound is off then i dont know its off.
- Make different icon so i can see warning that sound is off. image attached 
how hard it is to see any difference from speaker icon when turned off
+ NEED different icon (size, more contrast, red color, round red X sign) so i 
can see warning that sound is off. image attached how hard it is to see any 
difference from speaker icon when turned off
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kng2239 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jan 12 01:20:49 2024
  InstallationDate: Installed on 2024-01-05 (6 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA 

[Touch-packages] [Bug 2049117] Re: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep

[Jānis Kangarooo]

Here sound accidentally turned off since theres no notification that i
turned sound off

** Attachment added: "Screenshot_20240112_013915.png"
   
https://bugs.launchpad.net/ubuntu/+source/plasma-workspace/+bug/2049117/+attachment/5738601/+files/Screenshot_20240112_013915.png

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

Title:
  [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No
  sound at all From google Chrome youtube after putting computer to
  sleep

Status in alsa-driver package in Ubuntu:
  New
Status in plasma-workspace package in Ubuntu:
  New

Bug description:
  [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound 
at all From google Chrome youtube after putting computer to sleep
  From testing sound came but not from google chrome
  ---=== Update ===---
  False alarm. Sound i was able to put back on, turn out i dont remember i 
turned off sound on Chrome in task menu of Kubuntu. Icon shows sound playing 
and when clicking sound speaker icon in taskbar of chrome then it shows very 
thin line that sound is turned mute off.
  === Suggestion ===
  Since i dont remember i turned it off or dont see big difference or red icon 
that sound is off then i dont know its off.
  NEED different icon (size, more contrast, red color, round red X sign) so i 
can see warning that sound is off. image attached how hard it is to see any 
difference from speaker icon when turned off

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kng2239 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jan 12 01:20:49 2024
  InstallationDate: Installed on 2024-01-05 (6 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kng2239 F pulseaudio
   /dev/snd/pcmC0D0p:   kng2239 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2023
  dmi.bios.release: 15.0
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.15.00
  dmi.board.name: 87E0
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.24.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.36
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.15.00:bd10/06/2023:br15.0:efr51.36:svnHP:pnHPProBook440G8NotebookPC:pvrSBKPF:rvnHP:rn87E0:rvrKBCVersion33.24.00:cvnHP:ct10:cvr:sku27J72EA#B1R:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 440 G8 Notebook PC
  dmi.product.sku: 27J72EA#B1R
  dmi.product.version: SBKPF
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2049117/+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 2049117] Re: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep

[Jānis Kangarooo]

** Description changed:

  [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound 
at all From google Chrome youtube after putting computer to sleep
  From testing sound came but not from google chrome
+ ---=== Update ===---
+ False alarm. Sound i was able to put back on, turn out i dont remember i 
turned off sound on Chrome in task menu of Kubuntu. Icon shows sound playing 
and when clicking sound speaker icon in taskbar of chrome then it shows very 
thin line that sound is turned mute off. 
+ === Suggestion ===
+ Make different icon so i can see warning that sound is off. image attached 
how hard it is to see any difference from speaker icon when turned off
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  kng2239 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  kng2239 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jan 12 01:20:49 2024
  InstallationDate: Installed on 2024-01-05 (6 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  kng2239 F pulseaudio
-  /dev/snd/pcmC0D0p:   kng2239 F...m pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  kng2239 F pulseaudio
+  /dev/snd/pcmC0D0p:   kng2239 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2023
  dmi.bios.release: 15.0
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.15.00
  dmi.board.name: 87E0
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.24.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.36
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.15.00:bd10/06/2023:br15.0:efr51.36:svnHP:pnHPProBook440G8NotebookPC:pvrSBKPF:rvnHP:rn87E0:rvrKBCVersion33.24.00:cvnHP:ct10:cvr:sku27J72EA#B1R:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 440 G8 Notebook PC
  dmi.product.sku: 27J72EA#B1R
  dmi.product.version: SBKPF
  dmi.sys.vendor: HP

** Also affects: plasma-workspace (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No
  sound at all From google Chrome youtube after putting computer to
  sleep

Status in alsa-driver package in Ubuntu:
  New
Status in plasma-workspace package in Ubuntu:
  New

Bug description:
  [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound 
at all From google Chrome youtube after putting computer to sleep
  From testing sound came but not from google chrome
  ---=== Update ===---
  False alarm. Sound i was able to put back on, turn out i dont remember i 
turned off sound on Chrome in task menu of Kubuntu. Icon shows sound playing 
and when clicking sound speaker icon in taskbar of chrome then it shows very 
thin line that sound is turned mute off. 
  === Suggestion ===
  Make different icon so i can see warning that sound is off. image attached 
how hard it is to see any difference from speaker icon when turned off

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kng2239 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jan 12 01:20:49 2024
  InstallationDate: Installed on 2024-01-05 (6 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   

[Touch-packages] [Bug 2049117] [NEW] [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at all From google Chrome youtube after putting computer to sleep

[Jānis Kangarooo]

Public bug reported:

[HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound at 
all From google Chrome youtube after putting computer to sleep
>From testing sound came but not from google chrome

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kng2239 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Jan 12 01:20:49 2024
InstallationDate: Installed on 2024-01-05 (6 days ago)
InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp successful
Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  kng2239 F pulseaudio
 /dev/snd/pcmC0D0p:   kng2239 F...m pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No 
sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/06/2023
dmi.bios.release: 15.0
dmi.bios.vendor: HP
dmi.bios.version: T70 Ver. 01.15.00
dmi.board.name: 87E0
dmi.board.vendor: HP
dmi.board.version: KBC Version 33.24.00
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 51.36
dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.15.00:bd10/06/2023:br15.0:efr51.36:svnHP:pnHPProBook440G8NotebookPC:pvrSBKPF:rvnHP:rn87E0:rvrKBCVersion33.24.00:cvnHP:ct10:cvr:sku27J72EA#B1R:
dmi.product.family: 103C_5336AN HP ProBook
dmi.product.name: HP ProBook 440 G8 Notebook PC
dmi.product.sku: 27J72EA#B1R
dmi.product.version: SBKPF
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug jammy

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

Title:
  [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No
  sound at all From google Chrome youtube after putting computer to
  sleep

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No sound 
at all From google Chrome youtube after putting computer to sleep
  From testing sound came but not from google chrome

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kng2239 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Fri Jan 12 01:20:49 2024
  InstallationDate: Installed on 2024-01-05 (6 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kng2239 F pulseaudio
   /dev/snd/pcmC0D0p:   kng2239 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [HP ProBook 440 G8 Notebook PC, Realtek ALC236, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/06/2023
  dmi.bios.release: 15.0
  dmi.bios.vendor: HP
  dmi.bios.version: T70 Ver. 01.15.00
  dmi.board.name: 87E0
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 33.24.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 51.36
  dmi.modalias: 
dmi:bvnHP:bvrT70Ver.01.15.00:bd10/06/2023:br15.0:efr51.36:svnHP:pnHPProBook440G8NotebookPC:pvrSBKPF:rvnHP:rn87E0:rvrKBCVersion33.24.00:cvnHP:ct10:cvr:sku27J72EA#B1R:
  dmi.product.family: 103C_5336AN HP ProBook
  dmi.product.name: HP ProBook 440 G8 Notebook PC
  dmi.product.sku: 27J72EA#B1R
  dmi.product.version: SBKPF
  dmi.sys.vendor: HP

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


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

[Touch-packages] [Bug 2048092] Re: [low-priority SRU] Fix CVE-2022-0563 in source

[Andreas Hasenack]

> However, some users are known to build their own binaries from this Ubuntu 
> source and therefore could be 
> impacted.

Do you know of users rebuilding specifically util-linux and enabling
those tools? What was it about this specific CVE and specifically util-
linux that caught your attention and made you want to propose this SRU?

I see the patches only affect the binaries we don't ship, but have you
also made sure that no other tools or files from the package include the
affected code in their build?

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

Title:
  [low-priority SRU] Fix CVE-2022-0563 in source

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Jammy:
  In Progress
Status in util-linux source package in Lunar:
  Fix Released
Status in util-linux source package in Mantic:
  Fix Released
Status in util-linux source package in Noble:
  Fix Released

Bug description:
  [Impact]
  We did not fix this CVE in Ubuntu because we do not build the impacted 
binaries (we use --disable-chfn-chsh). However, some users are known to build 
their own binaries from this Ubuntu source and therefore could be impacted.

  [Test Plan]
  Since there is no impact to Ubuntu binaries, there is no functional change to 
verify. Regression testing using the existing build-time tests and autopkgtests 
should suffice.

  We should also verify that util-linux source builds fine w/ chfn and
  chsh enabled after applying this patch - otherwise it is really
  helping no one.

  [Where problems could occur]
  The upstream patch is clearly restricted to the chfn chsh binaries, which are 
not compiled by Ubuntu, so I don't see a risk there. I do see a risk that this 
is used as a precedent to fix other no-impact-to-Ubuntu security issues in 
other source - say, just to silence 3rd party security scanners. I do not 
intend to set such a precedent here, and suggest we consider them only on a 
case-by-case basis.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2048092/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

[Lucas Kanashiro]

Hi Aleksandr,

Let me try to clarify this for you. The two options presented by you are
not what we want. We want to grab the package from Debian unstable (with
the latest changes) and merge what we have in Ubuntu, which means having
a complete changelog (including the previous Ubuntu changes). You can
find some info about the merge process here:

https://wiki.ubuntu.com/UbuntuDevelopment/Merging

There is some outdated content there (like using bzr), if you want to do
this using git properly you can try to use the workflow described here:

https://wiki.ubuntu.com/UbuntuDevelopment/Merging/GitWorkflow

This is also some good content maintained by the Canonical Server team
which explains well the package merge process in our team's perspective:

https://github.com/canonical/ubuntu-maintainers-
handbook/blob/main/PackageMerging.md

I hope that's useful.

Now, I took a quick look at the proposed changes and I believe you
should double check the necessity of those binary packages name changes.
We are providing some transitional packages since Jammy, maybe now it is
time to get rid off them. In Debian, those transitional packages do not
exist, a good a idea (since we are merging our changes with Debian
again) might be to follow the package names from Debian. If it makes
sense, this will make the package way simpler. As a data point, the
Ubuntu package provides 12 binary packages and the Debian one provides 6
binary packages.

In the debian/tests/control file you need to add a comma (',') between
the two restriction names. A comment here is that if you merge the
changes from Debian we will get 2 more DEP-8 tests (autopkgtest) in the
package.

Nitpick: you committed the debian/files file which is not necessary.

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

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2047982] Re: Highlighting of patches offers insufficient contrast

[Simon Quigley]

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

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

Title:
  Highlighting of patches offers insufficient contrast

Status in vim package in Ubuntu:
  Fix Committed

Bug description:
  With vim 2:9.0.2189-1ubuntu1 the coloring of patches has been changed.

  The result is that in konsole patches have become illegible. See
  appendix.

  Deleted lines have foreground cyan #18b2b2 and background light blue
  #7f7fff. Kind of blue on blue.

  Please, provide sane color defaults. The previous release used bright
  white on black for deleted lines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2047982/+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 2047656] Re: [SRU] Players terminate after stopping and restarting

[Andreas Hasenack]

Hello Michael, or anyone else affected,

Accepted fluidsynth into mantic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/fluidsynth/2.3.3-2.1ubuntu0.23.10.1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: fluidsynth (Ubuntu Mantic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-mantic

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

Title:
  [SRU] Players terminate after stopping and restarting

Status in fluidsynth package in Ubuntu:
  Fix Released
Status in fluidsynth source package in Mantic:
  Fix Committed
Status in fluidsynth source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop
  of playback of a midi song, causing issues for a multitude of players
  including EasyABC. This will cause said player to be unable to
  playback again and perhaps even crash. See
  https://github.com/FluidSynth/fluidsynth/issues/1272, fix in
  
https://github.com/FluidSynth/fluidsynth/commit/377ab9db2f87bc407eeb940e0361edc77da77055.
  This is the included patch with the upload of
  2.3.3-2.1ubuntu-0.23.10.1

  [ Test Case ]

  * To reproduce the bug:

  # download sample midi file from wikiepdia:

  wget
  https://upload.wikimedia.org/wikipedia/commons/5/55/MIDI_sample.mid

  # play it with fluidsynth

  fluidsynth MIDI_sample.mid

  # at this point, you will actually be at a prompt. Wait for the song
  to play for a few seconds, then issue a stop command at that prompt:

  player_stop

  # And this is where the bug happens. Issue a continuation:

  player_cont

  And this is where things break:

  > player_cont
  > fluidsynth: error: The maximum playback duration has been reached. 
Terminating player!

  * With the fixed package, the audio resumes playback.

  [ What could go wrong ]

  This is actually a fix for a regression that was found in version
  2.3.3 of fluidsynth and fixed for 2.3.4, which can be found in noble.
  I think the only thing that can go wrong here is that this patch is
  not the actual fix and we need to find more solutions within.

  I have tested this in my PPA and it *seems* to fix it, but it would be
  nice if the original reporter could verify once this lands in
  proposed.

  [ Other information ]

  Included below is the original report, in which case the reporter
  deduces that the problem is the binary being spat-out is the 2.3.2
  version from the 2.3.3 sources. This is not the case, as it appears to
  be confusion due to the -2.1 Debian revision number. I assure, this is
  definitely the 2.3.3, and the bug, per the github link in the Impact
  section, is pertinent to this version.

  ---

  The latest package of fluidsynth should include the sources from
  version 2.3.3 but the binary includes only version 2.3.2

  This version has a bug (see
  https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to
  problems in EasyABC.

  Please include the latest version 2.3.3 from upstream in the ubuntu
  package.

  --

  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  $ apt-cache policy libfluidsynth3
  libfluidsynth3:
    Installiert:   2.3.3-2.1
    Installationskandidat: 2.3.3-2.1
    Versionstabelle:
   *** 2.3.3-2.1 500
  500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/+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 2047656] Re: [SRU] Players terminate after stopping and restarting

[Erich Eickmeyer]

Andreas, I fully support this. I can update the description with that as
it's a much simpler reproduction than a python script. :)

** Description changed:

  [ Impact ]
  
  Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop of
  playback of a midi song, causing issues for a multitude of players
  including EasyABC. This will cause said player to be unable to playback
  again and perhaps even crash. See
  https://github.com/FluidSynth/fluidsynth/issues/1272, fix in
  
https://github.com/FluidSynth/fluidsynth/commit/377ab9db2f87bc407eeb940e0361edc77da77055.
  This is the included patch with the upload of 2.3.3-2.1ubuntu-0.23.10.1
  
  [ Test Case ]
  
- * See test in Comment 4 below
- (https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/comments/4)
+ * To reproduce the bug:
+ 
+ # download sample midi file from wikiepdia:
+ 
+ wget https://upload.wikimedia.org/wikipedia/commons/5/55/MIDI_sample.mid
+ 
+ # play it with fluidsynth
+ 
+ fluidsynth MIDI_sample.mid
+ 
+ # at this point, you will actually be at a prompt. Wait for the song to
+ play for a few seconds, then issue a stop command at that prompt:
+ 
+ player_stop
+ 
+ # And this is where the bug happens. Issue a continuation:
+ 
+ player_cont
+ 
+ And this is where things break:
+ 
+ > player_cont
+ > fluidsynth: error: The maximum playback duration has been reached. 
Terminating player!
+ 
+ * With the fixed package, the audio resumes playback.
  
  [ What could go wrong ]
  
  This is actually a fix for a regression that was found in version 2.3.3
  of fluidsynth and fixed for 2.3.4, which can be found in noble. I think
  the only thing that can go wrong here is that this patch is not the
  actual fix and we need to find more solutions within.
  
  I have tested this in my PPA and it *seems* to fix it, but it would be
  nice if the original reporter could verify once this lands in proposed.
  
  [ Other information ]
  
  Included below is the original report, in which case the reporter
  deduces that the problem is the binary being spat-out is the 2.3.2
  version from the 2.3.3 sources. This is not the case, as it appears to
  be confusion due to the -2.1 Debian revision number. I assure, this is
  definitely the 2.3.3, and the bug, per the github link in the Impact
  section, is pertinent to this version.
  
  ---
  
  The latest package of fluidsynth should include the sources from version
  2.3.3 but the binary includes only version 2.3.2
  
  This version has a bug (see
  https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to
  problems in EasyABC.
  
  Please include the latest version 2.3.3 from upstream in the ubuntu
  package.
  
  --
  
  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic
  
  $ apt-cache policy libfluidsynth3
  libfluidsynth3:
    Installiert:   2.3.3-2.1
    Installationskandidat: 2.3.3-2.1
    Versionstabelle:
   *** 2.3.3-2.1 500
  500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages
  100 /var/lib/dpkg/status

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

Title:
  [SRU] Players terminate after stopping and restarting

Status in fluidsynth package in Ubuntu:
  Fix Released
Status in fluidsynth source package in Mantic:
  In Progress
Status in fluidsynth source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop
  of playback of a midi song, causing issues for a multitude of players
  including EasyABC. This will cause said player to be unable to
  playback again and perhaps even crash. See
  https://github.com/FluidSynth/fluidsynth/issues/1272, fix in
  
https://github.com/FluidSynth/fluidsynth/commit/377ab9db2f87bc407eeb940e0361edc77da77055.
  This is the included patch with the upload of
  2.3.3-2.1ubuntu-0.23.10.1

  [ Test Case ]

  * To reproduce the bug:

  # download sample midi file from wikiepdia:

  wget
  https://upload.wikimedia.org/wikipedia/commons/5/55/MIDI_sample.mid

  # play it with fluidsynth

  fluidsynth MIDI_sample.mid

  # at this point, you will actually be at a prompt. Wait for the song
  to play for a few seconds, then issue a stop command at that prompt:

  player_stop

  # And this is where the bug happens. Issue a continuation:

  player_cont

  And this is where things break:

  > player_cont
  > fluidsynth: error: The maximum playback duration has been reached. 
Terminating player!

  * With the fixed package, the audio resumes playback.

  [ What could go wrong ]

  This is actually a fix for a regression that was found in version
  2.3.3 of fluidsynth and fixed for 2.3.4, which can be found in noble.
  I think the only thing that can go wrong here is that this patch is
  not the actual fix and we need to find more solutions within.

  I have tested this in 

[Touch-packages] [Bug 2047656] Re: [SRU] Players terminate after stopping and restarting

[Andreas Hasenack]

Here is a better test case in my opinion. If you (reporter, or uploader,
or Eric) agree, could you please update the test plan in the
description?

To reproduce the bug:

# download sample midi file from wikiepdia:

wget https://upload.wikimedia.org/wikipedia/commons/5/55/MIDI_sample.mid

# play it with fluidsynth

fluidsynth MIDI_sample.mid

# at this point, you will actually be at a prompt. Wait for the song to
play for a few seconds, then issue a stop command at that prompt:

player_stop


# And this is where the bug happens. Issue a continuation:

player_cont

And this is where things break:

> player_cont
> fluidsynth: error: The maximum playback duration has been reached. 
> Terminating player!

With the fixed package, the audio resumes playback.

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

Title:
  [SRU] Players terminate after stopping and restarting

Status in fluidsynth package in Ubuntu:
  Fix Released
Status in fluidsynth source package in Mantic:
  In Progress
Status in fluidsynth source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop
  of playback of a midi song, causing issues for a multitude of players
  including EasyABC. This will cause said player to be unable to
  playback again and perhaps even crash. See
  https://github.com/FluidSynth/fluidsynth/issues/1272, fix in
  
https://github.com/FluidSynth/fluidsynth/commit/377ab9db2f87bc407eeb940e0361edc77da77055.
  This is the included patch with the upload of
  2.3.3-2.1ubuntu-0.23.10.1

  [ Test Case ]

  * See test in Comment 4 below
  (https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/comments/4)

  [ What could go wrong ]

  This is actually a fix for a regression that was found in version
  2.3.3 of fluidsynth and fixed for 2.3.4, which can be found in noble.
  I think the only thing that can go wrong here is that this patch is
  not the actual fix and we need to find more solutions within.

  I have tested this in my PPA and it *seems* to fix it, but it would be
  nice if the original reporter could verify once this lands in
  proposed.

  [ Other information ]

  Included below is the original report, in which case the reporter
  deduces that the problem is the binary being spat-out is the 2.3.2
  version from the 2.3.3 sources. This is not the case, as it appears to
  be confusion due to the -2.1 Debian revision number. I assure, this is
  definitely the 2.3.3, and the bug, per the github link in the Impact
  section, is pertinent to this version.

  ---

  The latest package of fluidsynth should include the sources from
  version 2.3.3 but the binary includes only version 2.3.2

  This version has a bug (see
  https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to
  problems in EasyABC.

  Please include the latest version 2.3.3 from upstream in the ubuntu
  package.

  --

  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  $ apt-cache policy libfluidsynth3
  libfluidsynth3:
    Installiert:   2.3.3-2.1
    Installationskandidat: 2.3.3-2.1
    Versionstabelle:
   *** 2.3.3-2.1 500
  500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages
  100 /var/lib/dpkg/status

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

[bugproxy]

--- Comment From holger.deng...@ibm.com 2024-01-11 13:09 EDT---
(In reply to comment #9)
> Holger: I can't pretend speaking for the SRU team, but I'd be willing to bet
> that having "the fix is trivial" as a test plan would result in the SRU
> being trivially rejected :-).

@schopin: The API description of localtime_r() (man localtime_r)
describes, that the function can return a NULL pointer on error. The API
documentation of strftime() (man strftime) describes, that the last
parameter of the function should not be a NULL pointer. If a program put
the return value of localtime_r() as the last parameter in a strftime()
call, than we have a classical programming error. It is just a missing
NULL pointer check. That was the thing, that I meant with "trivial".
There are a lot of patches in many projects, which introduces NULL
pointer checks. For the most of them I guess, there was never a test
case or test plan.

So yes, if you find a way to cause a reproducible failure of
localtime_r(), you can write a testcase. But I'm not sure, if it is
worth to spend all that effort in a fix, which just fixes a missing NULL
pointer check...

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

Title:
  pam_lastlog doesn't handle localtime_r related errors properly

Status in Ubuntu on IBM z Systems:
  New
Status in pam package in Ubuntu:
  New
Status in pam package in Fedora:
  Fix Released

Bug description:
  The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to 
noble) are affected by
  https://bugzilla.redhat.com/show_bug.cgi?id=2012871

  Customers report a command going through PAM crashing for a given user.
  A potential follow on issue can be that no ssh remote connections to an 
affected server are possible anymore, esp. painful with headless systems (was 
reported on a different distro).

  This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
  with tm = localtime_r(...) that can be NULL and needs to be handled.

  There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
  314-  ll_time = last_login.ll_time;
  315:  if ((tm = localtime_r (_time, _buf)) != NULL) {
  316-  strftime (the_time, sizeof (the_time),
  317-  /* TRANSLATORS: "strftime options for date of last 
login" */
  --
  574-
  575-  lf_time = utuser.ut_tv.tv_sec;
  576:  tm = localtime_r (_time, _buf);
  577-  strftime (the_time, sizeof (the_time),
  578-  /* TRANSLATORS: "strftime options for date of last login" */

  Case 1 (line 315) is properly handled, but not case 2 (line 576).

  The second case got fixed by:
  
https://github.com/linux-pam/linux-pam/commit/40c271164dbcebfc5304d0537a42fb42e6b6803c

  This fix should be included in Ubuntu (and Debian).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2045250/+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 2049014] Re: software-properties-common is missing dependecy python3-six in Noble

[Hans Joachim Desserud]

** Tags added: noble packaging

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

Title:
  software-properties-common is missing dependecy python3-six  in Noble

Status in software-properties package in Ubuntu:
  New

Bug description:
  Ubuntu version: "24.04 (Noble Numbat)"
  software-properties-common version: 0.99.40

  This command fails to run when package python3-six is not installed:

  ```
  $ add-apt-repository -y --ppa ppa:ubuntu-wsl-dev/ppa
  Traceback (most recent call last):
    File "/usr/bin/add-apt-repository", line 14, in 
  from softwareproperties.shortcuts import shortcut_handler
    File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
23, in 
  from softwareproperties.ppa import PPAShortcutHandler
    File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 25, 
in 
  from launchpadlib.launchpad import Launchpad
    File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 48, 
in 
  from launchpadlib.credentials import (
    File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 59, 
in 
  from six.moves.urllib.parse import parse_qs
  ModuleNotFoundError: No module named 'six'
  ```

  I reproduced this bug in docker. The following dockerfile exercises it:
  ```
  FROM ubuntu:devel
  ENV DEBIAN_FRONTEND=noninteractive
  RUN apt-get update
  RUN apt-get install -y software-properties-common
  RUN add-apt-repository -y --ppa ppa:ubuntu-wsl-dev/ppa
  ```

  Modifying the docker file by adding `RUN apt-get install -y
  python3-six` before the last line works as a workaround.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2049014/+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 1813076] Re: goa crashes when trying to authenticate against google & DUO

[Jeremy Bícha]

This is fixed for Ubuntu 24.04 LTS which will use the browser to log in
to Google or Microsoft for Settings > Online Accounts.

Previously, it used a popup powered by WebkitGTK. Webkit is the engine
in Apple's Safari browsers so this user agent identifies itself as
similar to Safari.

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

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

Title:
  goa crashes when trying to authenticate against google & DUO

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  My google eMAIL account is managed by my organisation.  They recently
  required everyone to validate their sign-ons (sign-ins) via a central
  authentication server (CAS) using the 2FA from DUO.  When attempting
  to connect using goa, I am now re-directed to my organisation's CAS
  and when the DUO login page refreshes, it states that login could not
  proceed because I am using a SAFARI browser that is more than one year
  out of date.  Of course, I'm not using SAFARI, but rather goa.  Is
  there a way to deed the proper header (a more recent version of SAFARI
  in goa) to be able to complete 2FA with DUO?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-online-accounts 3.28.0-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.18.0-14.15~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Jan 23 15:20:45 2019
  InstallationDate: Installed on 2019-01-15 (8 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1813076/+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 1827764] Re: GOA cannot add a Gmail account of a minor (young child who needs consent)

[Jeremy Bícha]

I believe this is fixed for Ubuntu 24.04 LTS which will use the browser
to log in instead of a popup window powered by WebkitGTK.

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

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  GOA cannot add a Gmail account of a minor (young child who needs
  consent)

Status in gnome-online-accounts package in Ubuntu:
  Fix Committed

Bug description:
  Hello
  I am user of ubuntu 18.04 with gnome version 3.28.2 and it seems that I have 
found a bug when a GMAIL account is added.
  I have a problem setting up my child's GMAIL account (minor). The normal 
thing in any web browser is that when entering the GMAIL website, enter the 
data of them and then have to enter mine to consent to their access. In the 
GNOME directly blocks access when entering from ONLINE ACCOUNTS. Is there a 
solution for you to access? 
  Thanks and best regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-release-upgrader-core 1:18.04.31
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  5 07:43:54 2019
  InstallationDate: Installed on 2019-04-07 (27 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1827764/+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 1826311] Re: Cannot Login to Google with Advanced Protection Enabled

[Jeremy Bícha]

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

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

Title:
  Cannot Login to Google with Advanced Protection Enabled

Status in gnome-online-accounts:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  Fix Committed

Bug description:
  Description:  Ubuntu 19.04
  Release:  19.04

  
  gnome-online-accounts:
Installed: 3.32.0-1ubuntu1
Candidate: 3.32.0-1ubuntu1
Version table:
   *** 3.32.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  1) Open Online accounts and select google (From settings or during OS setup)
  2) enter username and password.

  What I expect: I get the prompt to plug-in my 2 factor hardware key
  What actually happens: I get a prompt saying, "You can only use your Security 
keys with Google Chrome"

  
  Not sure if this is actually fixable, I know desktop firefox has hidden 
settings to allow u2f, but not sure if that extends to the embedded browsers 
(if gnome-online-accounts even uses an embedded firefox for its browser)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 00:16:27 2019
  InstallationDate: Installed on 2019-04-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1826311/+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 2045250] Re: pam_lastlog doesn't handle localtime_r related errors properly

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Importance: Undecided => High

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

Title:
  pam_lastlog doesn't handle localtime_r related errors properly

Status in Ubuntu on IBM z Systems:
  New
Status in pam package in Ubuntu:
  New
Status in pam package in Fedora:
  Fix Released

Bug description:
  The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to 
noble) are affected by
  https://bugzilla.redhat.com/show_bug.cgi?id=2012871

  Customers report a command going through PAM crashing for a given user.
  A potential follow on issue can be that no ssh remote connections to an 
affected server are possible anymore, esp. painful with headless systems (was 
reported on a different distro).

  This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
  with tm = localtime_r(...) that can be NULL and needs to be handled.

  There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
  314-  ll_time = last_login.ll_time;
  315:  if ((tm = localtime_r (_time, _buf)) != NULL) {
  316-  strftime (the_time, sizeof (the_time),
  317-  /* TRANSLATORS: "strftime options for date of last 
login" */
  --
  574-
  575-  lf_time = utuser.ut_tv.tv_sec;
  576:  tm = localtime_r (_time, _buf);
  577-  strftime (the_time, sizeof (the_time),
  578-  /* TRANSLATORS: "strftime options for date of last login" */

  Case 1 (line 315) is properly handled, but not case 2 (line 576).

  The second case got fixed by:
  
https://github.com/linux-pam/linux-pam/commit/40c271164dbcebfc5304d0537a42fb42e6b6803c

  This fix should be included in Ubuntu (and Debian).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2045250/+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

Re: [Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

[ethanay]

Hi Christian,

Thank you. Yes I was not arguing strictly against irqbalance, just trying
to ascertain some discussion parameters as well as parameters for data
collection.

I have not yet seen a coherent philosophy on what it means to "optimize
performance" with default settings that serve the greatest capacity of
server or desktop scenarios. In my humble opinion, data collection is
useless without this framework of understanding what it is we are trying to
achieve and why in terms of system performance. To me this is the deeper
unresolved issue, perhaps.

I fear that systems are currently optimized by default for throughput. For
users, responsiveness (which can include but is not limited to throughput)
and latency may be more important psychologically (there is an analogy to
this in AV production: we can actually get by with fairly poor video
quality--which consumes the most bandwidth and processor power--if audio
quality remains adequate; ie, audio quality has a disproportionately high
impact on psychology compared to video, especially per unit of data or
processing power allocated). And power saving is important in global terms,
as even small gains multiplied over hundreds or thousands of deployments
can have a significant impact, even if the client or operator doesn't
notice much.

ethan

On Wed, Jan 10, 2024 at 4:35 AM Christian Ehrhardt  <
1833...@bugs.launchpad.net> wrote:

> Hi Ethanay
> > All I can find is a recommendation not to use it on CPUs with 2 or fewer
> > cores as the overhead is said to be too high
>
> This isn't a real problem anyway, the service will stop immediately if only
> running on one core - even if running on multiple cores with the same
> cache (as the intended benefit is due to cache hotness by having all I/O
> hitting the same cache).
>
> > I can imagine it might still add undesirable or even critical latency in
> > applications that are highly latency sensitive
>
> I understand your line of thought, but it might even improve latency.
> If there is no bottleneck on the cores assigned to handle an IRQ then
> the improved cache hit rate will make even latency better.
> And if there is a strong bottleneck, then some drivers without IRQbalance
> would end up locked on one cpu - so again these might gain lower latency.
> But I have no data on this either (just like no one seems to have on almost
> any of this).
>
> Just like others I'd personally more expect the drawback to be on a
> potential
> lack of power saving.
>
> > This website gave me some clarity on the theory and purpose:
> > https://www.baeldung.com/linux/irqbalance-modern-hardware
>
> Hah, didn't find this one yet - thank you!
> But to me it only underlines the "it can help as much or even more often"
> expectation.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1833322
>
> Title:
>   Consider removing irqbalance from default install on desktop images
>
> Status in irqbalance package in Ubuntu:
>   Confirmed
> Status in ubuntu-meta package in Ubuntu:
>   Confirmed
>
> Bug description:
>   as per https://github.com/pop-os/default-settings/issues/60
>
>   Distribution (run cat /etc/os-release):
>
>   $ cat /etc/os-release
>   NAME="Pop!_OS"
>   VERSION="19.04"
>   ID=ubuntu
>   ID_LIKE=debian
>   PRETTY_NAME="Pop!_OS 19.04"
>   VERSION_ID="19.04"
>   HOME_URL="https://system76.com/pop;
>   SUPPORT_URL="http://support.system76.com;
>   BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
>   PRIVACY_POLICY_URL="https://system76.com/privacy;
>   VERSION_CODENAME=disco
>   UBUNTU_CODENAME=disco
>
>   Related Application and/or Package Version (run apt policy $PACKAGE
>   NAME):
>
>   $ apt policy irqbalance
>   irqbalance:
>   Installed: 1.5.0-3ubuntu1
>   Candidate: 1.5.0-3ubuntu1
>   Version table:
>   *** 1.5.0-3ubuntu1 500
>   500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
>   100 /var/lib/dpkg/status
>
>   $ apt rdepends irqbalance
>   irqbalance
>   Reverse Depends:
>   Recommends: ubuntu-standard
>   gce-compute-image-packages
>
>   Issue/Bug Description:
>
>   as per konkor/cpufreq#48 and
>   http://konkor.github.io/cpufreq/faq/#irqbalance-detected
>
>   irqbalance is technically not needed on desktop systems (supposedly it
>   is mainly for servers), and may actually reduce performance and power
>   savings. It appears to provide benefits only to server environments
>   that have relatively-constant loading. If it is truly a server-
>   oriented package, then it shouldn't be installed by default on a
>   desktop/laptop system and shouldn't be included in desktop OS images.
>
>   Steps to reproduce (if you know):
>
>   This is potentially an issue with all default installs.
>
>   Expected behavior:
>
>   n/a
>
>   Other Notes:
>
>   I can safely remove it via "sudo apt purge irqbalance" without any
>   apparent adverse side-effects. If someone is running a situation where
>   they need it, then they always have the 

[Touch-packages] [Bug 1838372] Re: 'ubuntu-bug -w' doesn't work under wayland

[Julian Andres Klode]

Needs some investigation whether this is possible, Wayland has a
security focused design where I'd expect it not to be.

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

Title:
  'ubuntu-bug -w' doesn't work under wayland

Status in apport package in Ubuntu:
  Triaged

Bug description:
  
  'ubuntu-bug -w' doesn't work for most applications such nautilus, gedit, 
settings, etc. under wayland.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1838372/+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 2045250] Re: pam_lastlog doesn't handle localtime_r related errors properly

[Simon Chopin]

sarnold, good point!

Holger: I can't pretend speaking for the SRU team, but I'd be willing to
bet that having "the fix is trivial" as a test plan would result in the
SRU being trivially rejected :-).

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

Title:
  pam_lastlog doesn't handle localtime_r related errors properly

Status in Ubuntu on IBM z Systems:
  New
Status in pam package in Ubuntu:
  New
Status in pam package in Fedora:
  Fix Released

Bug description:
  The pam version(s) in Debian (checked buster) and Ubuntu (checked focal to 
noble) are affected by
  https://bugzilla.redhat.com/show_bug.cgi?id=2012871

  Customers report a command going through PAM crashing for a given user.
  A potential follow on issue can be that no ssh remote connections to an 
affected server are possible anymore, esp. painful with headless systems (was 
reported on a different distro).

  This is caused by an issue in modules/pam_lastlog/pam_lastlog.c:
  with tm = localtime_r(...) that can be NULL and needs to be handled.

  There are two such cases in modules/pam_lastlog/pam_lastlog.c (here noble):
  314-  ll_time = last_login.ll_time;
  315:  if ((tm = localtime_r (_time, _buf)) != NULL) {
  316-  strftime (the_time, sizeof (the_time),
  317-  /* TRANSLATORS: "strftime options for date of last 
login" */
  --
  574-
  575-  lf_time = utuser.ut_tv.tv_sec;
  576:  tm = localtime_r (_time, _buf);
  577-  strftime (the_time, sizeof (the_time),
  578-  /* TRANSLATORS: "strftime options for date of last login" */

  Case 1 (line 315) is properly handled, but not case 2 (line 576).

  The second case got fixed by:
  
https://github.com/linux-pam/linux-pam/commit/40c271164dbcebfc5304d0537a42fb42e6b6803c

  This fix should be included in Ubuntu (and Debian).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2045250/+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 2047780] Re: BlueZ release 5.71

[Simon Quigley]

It looks like I was overly strict with the MIR compliance, which sort of
balances out this bug as a whole. :)

After it migrates, Gianfranco or myself will try reverting ubuntu2 to
see if we can push those two packages forward.

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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

[Touch-packages] [Bug 2046459] Re: systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting in boot failure

[Nick Rosbrook]

** Tags removed: foundations-todo
** Tags added: systemd-sru-next

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

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

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Mantic:
  Triaged

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

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

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

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


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

[Touch-packages] [Bug 1969365] Re: focal: backport kexec fallback patch

[Nick Rosbrook]

Thanks for the verification, Dan!

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

Title:
  focal: backport kexec fallback patch

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  It would be great if focal's systemd could have
  
https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3
  backported to it.

  [Impact]

  We have observed that kexec'ing to another kernel will fail as the
  drive containing the `kexec` binary has been unmounted by the time
  systemd attempts to do so, indicated in the console:

   Starting Reboot via kexec...
  [  163.960938] shutdown[1]: (sd-kexec) failed with exit status 1.
  [  163.963463] reboot: Restarting system

  [Test Plan]

  1) Launch a 20.04 instance
  2) `apt-get install kexec-tools`
  3) In `/boot`, filling in whatever  needed in your environment:

  kexec -l vmlinuz --initrd initrd.img --append ''

  4) `reboot`

  (I have reproduced this in a single-disk VM, so I assume it reproduces
  ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot`
  could be used to emulate the unmounting.)

  [Where problems could occur]

  Users could inadvertently be relying on the current behaviour: if they
  have configured their systems to kexec, they currently will be
  rebooting normally, and this patch would cause them to start actually
  kexec'ing.

  [Other info]

  We're currently maintaining a systemd tree with only this patch added
  to focal's tree: this patch has received a bunch of testing from us in
  focal.

  This patch landed in v246, so it's already present in supported
  releases later than focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969365/+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 2049051] [NEW] Laptop screen

[Marat]

Public bug reported:

Laptop screen don't work after update drivers

Ubuntu 22.04.3 LTS


lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris Xe 
Graphics] (rev 01)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 11 17:32:30 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company TigerLake-LP GT2 [Iris Xe Graphics] 
[103c:8716]
InstallationDate: Installed on 2022-01-17 (723 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: HP HP Elite Dragonfly G2 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=e2543c89-cd10-40b1-a8c0-ece1f910ccb5 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/01/2021
dmi.bios.release: 4.1
dmi.bios.vendor: HP
dmi.bios.version: T90 Ver. 01.04.01
dmi.board.name: 8716
dmi.board.vendor: HP
dmi.board.version: KBC Version 37.1D.05
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 55.29
dmi.modalias: 
dmi:bvnHP:bvrT90Ver.01.04.01:bd06/01/2021:br4.1:efr55.29:svnHP:pnHPEliteDragonflyG2NotebookPC:pvr:rvnHP:rn8716:rvrKBCVersion37.1D.05:cvnHP:ct31:cvr:sku3C6G9ES#ACB:
dmi.product.family: 103C_5336AN HP EliteBook x360
dmi.product.name: HP Elite Dragonfly G2 Notebook PC
dmi.product.sku: 3C6G9ES#ACB
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.0.20231114.1-2088~22.04
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.5
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy third-party-packages ubuntu

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

Title:
  Laptop screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Laptop screen don't work after update drivers

  Ubuntu 22.04.3 LTS

  
  lspci | grep VGA
  00:02.0 VGA compatible controller: Intel Corporation TigerLake-LP GT2 [Iris 
Xe Graphics] (rev 01)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 11 17:32:30 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company TigerLake-LP GT2 [Iris Xe Graphics] 
[103c:8716]
  InstallationDate: Installed on 2022-01-17 (723 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: HP HP Elite Dragonfly G2 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=e2543c89-cd10-40b1-a8c0-ece1f910ccb5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/01/2021
  dmi.bios.release: 4.1
  dmi.bios.vendor: HP
  dmi.bios.version: T90 Ver. 01.04.01
  dmi.board.name: 8716
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 37.1D.05
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 55.29
  dmi.modalias: 
dmi:bvnHP:bvrT90Ver.01.04.01:bd06/01/2021:br4.1:efr55.29:svnHP:pnHPEliteDragonflyG2NotebookPC:pvr:rvnHP:rn8716:rvrKBCVersion37.1D.05:cvnHP:ct31:cvr:sku3C6G9ES#ACB:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP Elite Dragonfly G2 Notebook PC
  dmi.product.sku: 3C6G9ES#ACB
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 

[Touch-packages] [Bug 2046459] Re: systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting in boot failure

[Nick Rosbrook]

The "Fix Committed" status means that I have uploaded the change (to
noble-proposed), but it is not available in the release yet. "Fix
Released" means the change is actually available in the specified
release.

I have not staged the change for Mantic, but I have added a bug task for
it.

** Also affects: systemd (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

** Changed in: systemd (Ubuntu Mantic)
   Importance: Undecided => Medium

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

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

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Mantic:
  Triaged

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

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

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

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


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

[Touch-packages] [Bug 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"

[Adrien Nader]

Thanks for the review and upload.

I have a similar take on the patches in this series and I believe it
would be very difficult and riskier to try to skip some of the patches
in this series which has seen real-world use as a whole, starting with
openssl >= 3.0.4 (which we started shipping in lunar).

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

Title:
  openssl: backport to jammy "clear method store / query cache
  confusion"

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Jammy:
  In Progress
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [ATTENTION]
  This SRU contains THREE changes which are listed in the section below.

  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  This ( #2033422 ) is the "central" bug with the global information and 
debdiff.

  This SRU addresses three issues with Jammy's openssl version:
  - http://pad.lv/1994165: ignored SMIME signature errors
  - http://pad.lv/2023545: imbca engine dumps core
  - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections 
(this one)

  The SRU information has been added to the three bug reports and I am
  attaching the debdiff here only for all three.

  All the patches have been included in subsequent openssl 3.0.x
  releases which in turn have been included in subsequent Ubuntu
  releases. There has been no report of issues when updating to these
  Ubuntu releases.

  I have rebuilt the openssl versions and used abi-compliance-checker to
  compare the ABIs of the libraries in jammy and the one for the SRU.
  Both matched completely (FYI, mantic's matched completely too).

  I have also pushed the code to git (without any attempt to make it
  git-ubuntu friendly).

  
https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy-
  sru

  I asked Brian Murray about phasing speed and he concurs a slow roll-out is 
probably better for openssl. There is a small uncertainty because a security 
update could come before the phasing is over, effectively fast-forwarding the 
SRU. Still, unless there is already a current pre-advisory, this is probably 
better than a 10% phasing which is over after only a couple days anyway.
  NB: at the moment openssl doesn't phase slowly so this needs to be 
implemented.

  [Impact]
  Severely degraded performance for concurrent operations compared to openssl 
1.1. The performance is so degraded that some workloads fail due to timeouts or 
insufficient resources (noone magically has 5 times more machines). As a 
consequence, a number of people use openssl 1.1 instead and do not get security 
updates.

  [Test plan]
  Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py
 .

  To test, follow these steps:
  - run "time python3 main.py" # using the aforementioned main.py script
  - apt install -t jammy-proposed libssl3
  - run "time python3 main.py"
  - compare the runtimes for the two main.py runs

  You can run this on x86_64, Raspberry Pi 4 or any machine, and get a
  very large speed-up in all cases. The improvements are not
  architecture-dependant.

  Using this changeset, I get the following numbers for ten runs on my
  laptop:

  3.0.2:
  real  2m5.567s
  user  4m3.948s
  sys   2m0.233s

  this SRU:
  real  0m23.966s
  user  2m35.687s
  sys   0m1.920s

  As can be easily seen, the speed-up is massive: system time is divided
  by 60 and overall wall clock time is roughly five times lower.

  In http://pad.lv/2009544 , Rafael also shared his performance numbers
  and they are relatable to these. He used slightly different versions
  (upstreams rather than patched with cherry-picks) but at least one of
  the version used does not include other performance change. He also
  used different hardware and this performance issue seems to depend on
  the number of CPUs available but also obtained a performance several
  times better. Results on a given machine vary also very little across
  runs (less than 2% variation on runs of size 10). They are also very
  similar on a Raspberry Pi 4 (8GB).

  The benchmark uses https://www.google.com/humans.txt which takes
  around 130ms to download on my machine but I modified the script to
  download something only 20ms away. Results are so close to the ones
  using humans.txt that they are within the error margin. This is
  consistent with the high-concurrency in the benchmark which both
  saturates CPU, and "hides" latencies that are relatively low.

  Finally, there are positive reports on github. Unfortunately they are
  not always completely targeted at these patches only and therefore I
  will not link directly to them but they have also been 

[Touch-packages] [Bug 2046574] Re: Printer grey scale/bw option is not available

[Sebastien Bacher]

@Till, do you have any idea how to debug this issue? How is the GTK
print dialog getting the color modes available?

** Changed in: gtk+3.0 (Ubuntu)
   Status: Incomplete => New

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

Title:
  Printer grey scale/bw option is not available

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I was using 22.04 LTS until last week(8 Dec 2023). I upgraded to 23.10
  and noticed a difference with the printing options.

  In 22.04 (as far as I remember),
  There was Monochrome, Grey scale and Color. I used to print using grey scale 
and it used to print in grey scale.

  After upgrade to 23.10,
  There is no grey scale option. Instead there is Color, Auto Monochrome, 
Monochrome and process Monochrome. I tried all the monochrome options and all 
of them printed with color. Even when I checked preview it was showing color 
with these options selected. I think the monochrome options are not selected at 
all.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2046574/+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 2047780] Re: BlueZ release 5.71

[Jeremy Bícha]

ell had an approved MIR but the only thing it was used for was iwd which
is not currently in main. After the MIR is approved, something in main
needs to depend on it (or add it to a main seed) and then the Archive
Admins can promote it to main.

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2037604] Re: Backport packages for 22.04.4 HWE stack

[Treviño]

I can test this too if needed, I've a AMD® Ryzen 7 pro 7840u with radeon
780m graphics (phoenix).

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

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2046477] Re: Enable unprivileged user namespace restrictions by default

[John Johansen]

We will get this updated with requested information soon. We are
currently working on a revision that provides more flexibility and will
support some cases that break today.

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

Title:
  Enable unprivileged user namespace restrictions by default

Status in apparmor package in Ubuntu:
  Triaged

Bug description:
  As per https://discourse.ubuntu.com/t/spec-unprivileged-user-
  namespace-restrictions-via-apparmor-in-ubuntu-23-10/37626,
  unprivileged user namespace restrictions for Ubuntu 23.10 are to be
  enabled by default via a sysctl.d conf file in apparmor, and for that
  to happen, the restrictions need to be enabled for 24.04

  When the unprivileged user namespace restrictions are enabled, various
  applications within and outside the Ubuntu archive fail to function,
  as they use unprivileged user namespaces as part of their normal
  operation.

  A search of the Ubuntu archive for the 23.10 release was performed
  looking for all applications that make legitimate use of the
  CLONE_NEWUSER argument, the details of which can be seen in
  
https://docs.google.com/spreadsheets/d/1MOPVoTW0BROF1TxYqoWeJ3c6w2xKElI4w-VjdCG0m9s/edit#gid=2102562502

  For each package identified in that list, an investigation was made to
  determine if the application actually used this as an unprivileged
  user, and if so which of the binaries within the package were
  affected.

  The full investigation can be seen in
  https://warthogs.atlassian.net/browse/SEC-1898 (which is unfortunately
  private) but is summarised to the following list of Ubuntu source
  packages, as well as some out-of-archive applications that are known
  to use unprivileged user namespaces.

  For each of these binaries, an apparmor profile is required so that
  the binary can be granted use of unprivileged user namespaces - an
  example profile for the ch-run binary within the charliecloud package
  is shown:

  $ cat /etc/apparmor.d/ch-run
  abi ,

  include 

  profile ch-run /usr/bin/ch-run flags=(unconfined) {
userns,

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

  However, in a few select cases, it has been decided not to ship an apparmor 
profile, since this would effectively allow this mitigation to be bypassed. In 
particular, the unshare and setns binaries within the util-linux package are 
installed on every Ubuntu system, and allow an unprivileged user the ability to 
launch an arbitrary application within a new user namespace. Any malicious 
application then that wished to exploit an unprivileged user namespace to 
conduct an attack on the kernel would simply need to spawn itself via `unshare 
-U` or similar to be granted this permission. Therefore, due to the ubiquitous 
nature of the unshare (and setns) binaries, profiles are not planned to be 
provided for these by default. 
  Similarly, the bwrap binary within bubblewrap is also installed by default on 
Ubuntu Desktop 24.04 and can also be used to launch arbitrary binaries within a 
new user namespace and so no profile is planned to be provided for this either.

  In Bug 2035315 new apparmor profiles were added to the apparmor
  package for various applications which require unprivileged user
  namespaces, using a new unconfined profile mode. They were also added
  in the AppArmor upstream project.

  As well as enabling the sysctl via the sysctl.d conf file, it is
  proposed to add logic into the apparmor.service systemd unit to check
  that the kernel supports the unconfined profile mode and that it is
  enabled - and if not then to force disable the userns restrictions
  sysctl via the following logic:

  userns_restricted=$(sysctl -n kernel.apparmor_restrict_unprivileged_userns)
  unconfined_userns=$([ -f 
/sys/kernel/security/apparmor/features/policy/unconfined_restrictions/userns ] 
&& cat 
/sys/kernel/security/apparmor/features/policy/unconfined_restrictions/userns || 
echo 0)
  if [ -n "$userns_restricted" ] && [ "$userns_restricted" -eq 1 ]; then
if [ "$unconfined_userns" -eq 0 ]; then
  # userns restrictions rely on unconfined userns to be supported
  echo "disabling unprivileged userns restrictions since unconfined userns 
is not supported / enabled"
  sysctl -w kernel.apparmor_restrict_unprivileged_userns=0
fi
  fi

  This allows a local admin to disable the sysctl via the regular
  sysctl.d conf approach, but to also make sure we don't inadvertently
  enable it when it is not supported by the kernel.

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


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

[Touch-packages] [Bug 2049019] [NEW] RFE: also show processes witing for IO (status "D") as running (highlight y)

[Mikko Rantalainen]

Public bug reported:

Currently when I run top and use key "y" to enable highlighting for
running task, only tasks with status "R" are highlighted. However, as
many modern processes are IO limited instead of CPU limited, it would
make sense to highlight both CPU limited and IO limited processes
because both are logically running as far as the user is interested.

I'm hereby requesting that the "running tasks" highlight should
highlight all processes with status "R" or "D" instead of only "R" like
it currently does.

I don't understand the "I" state to know if it would make sense to
include that, too, as a "running task".

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: procps 2:3.3.17-6ubuntu2.1
ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-lowlatency 6.2.16
Uname: Linux 6.2.0-1014-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Thu Jan 11 13:05:28 2024
InstallationDate: Installed on 2022-03-25 (657 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: procps
UpgradeStatus: Upgraded to jammy on 2023-05-25 (230 days ago)

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


** Tags: amd64 apport-bug jammy

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

Title:
  RFE: also show processes witing for IO (status "D") as running
  (highlight y)

Status in procps package in Ubuntu:
  New

Bug description:
  Currently when I run top and use key "y" to enable highlighting for
  running task, only tasks with status "R" are highlighted. However, as
  many modern processes are IO limited instead of CPU limited, it would
  make sense to highlight both CPU limited and IO limited processes
  because both are logically running as far as the user is interested.

  I'm hereby requesting that the "running tasks" highlight should
  highlight all processes with status "R" or "D" instead of only "R"
  like it currently does.

  I don't understand the "I" state to know if it would make sense to
  include that, too, as a "running task".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: procps 2:3.3.17-6ubuntu2.1
  ProcVersionSignature: Ubuntu 6.2.0-1014.14~22.04.1-lowlatency 6.2.16
  Uname: Linux 6.2.0-1014-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Thu Jan 11 13:05:28 2024
  InstallationDate: Installed on 2022-03-25 (657 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: procps
  UpgradeStatus: Upgraded to jammy on 2023-05-25 (230 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/2049019/+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 2045621] Re: Improve power consumption on Framework systems

[Ciaby]

Testing on Jammy:
1. Enabled jammy-proposed
2. Installed systemd-hwe-hwdb (version 249.11.5)
3. File /usr/lib/udev/hwdb.d/90-ubuntu-autosuspend.hwdb is created
4. Check power status (HDMI card):
$ cat /sys/devices/pci:00/:00:08.3/:c3:00.3/usb5/5-1/manufacturer
Framework
$ cat /sys/devices/pci:00/:00:08.3/:c3:00.3/usb5/5-1/power/control
auto

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

Title:
  Improve power consumption on Framework systems

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd-hwe package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Won't Fix
Status in systemd-hwe source package in Jammy:
  Fix Committed
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd-hwe source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix
Status in systemd-hwe source package in Mantic:
  Fix Committed
Status in systemd source package in Noble:
  Fix Committed
Status in systemd-hwe source package in Noble:
  Invalid

Bug description:
  [ Impact ]

   * Framework systems that have DP or HDMI cards connected will have
  increased power consumption even when nothing is connected to DP or
  HDMI ports since the cards don't default to autosuspend.

   * Backporting upstream patch that adds rules in
  hwdb.d/60-autosuspend.hwdb for Framework's HDMI and DP extensions.

  [ Test Plan ]

   * DUT: Framework with DP and HDMI:

  $ lsusb | grep Framework
  Bus 007 Device 002: ID 32ac:0003 Framework DisplayPort Expansion Card
  Bus 001 Device 002: ID 32ac:0002 Framework HDMI Expansion Card

   1. Autosuspend is not enabled before patch. Set to "on" in
  power/control

  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/manufacturer
  Framework
  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-1/power/control
  on

  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/manufacturer
  Framework
  $ cat /sys/devices/pci:00/:00:08.1/:c1:00.3/usb1/1-2/power/control
  on

   2. Install patch
   3. Autosuspend is enabled for both extensions. Set to "auto" in power/control

  $ cat power/control
  auto

  [ Where problems could occur ]

   * During testing verified that both DP+HDMI display show good output after 
hot-plug, system suspend, and reboot. There might be some differences when 
hibernate and hotplug.
   
  [ Other Info ]

   *
  
https://github.com/systemd/systemd/commit/9023630cb7025650aa4d01ee794b0bb68bfdf2c1

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2045621/+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 2039868] Re: amdgpu reset during usage of firefox

[Launchpad Bug Tracker]

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

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

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

Title:
  amdgpu reset during usage of firefox

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Running nightly on 23.10 (since monday), I have been experiencing a
  few amdgpu resets in the past hours

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-9-generic 6.5.0-9.9
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 19 18:26:43 2023
  HibernationDevice: RESUME=/dev/mapper/vg--ubuntu-lv--ubuntu--swap
  InstallationDate: Installed on 2022-07-04 (472 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/vg--ubuntu-lv--ubuntu--root ro rootflags=subvol=@ quiet splash 
resume=/dev/mapper/vg--ubuntu-lv--ubuntu--swap vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-9-generic N/A
   linux-backports-modules-6.5.0-9-generic  N/A
   linux-firmware   20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (3 days ago)
  dmi.bios.date: 05/15/2023
  dmi.bios.release: 1.24
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1MET54W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21A0CTO1WW
  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.24
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1MET54W(1.24):bd05/15/2023:br1.24:efr1.24:svnLENOVO:pn21A0CTO1WW:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a:
  dmi.product.family: ThinkPad P14s Gen 2a
  dmi.product.name: 21A0CTO1WW
  dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a
  dmi.product.version: ThinkPad P14s Gen 2a
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/2039868/+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 2049014] [NEW] software-properties-common is missing dependecy python3-six in Noble

[Edu Gómez Escandell]

Public bug reported:

Ubuntu version: "24.04 (Noble Numbat)"
software-properties-common version: 0.99.40

This command fails to run when package python3-six is not installed:

```
$ add-apt-repository -y --ppa ppa:ubuntu-wsl-dev/ppa
Traceback (most recent call last):
  File "/usr/bin/add-apt-repository", line 14, in 
from softwareproperties.shortcuts import shortcut_handler
  File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
23, in 
from softwareproperties.ppa import PPAShortcutHandler
  File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 25, in 

from launchpadlib.launchpad import Launchpad
  File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 48, in 

from launchpadlib.credentials import (
  File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 59, 
in 
from six.moves.urllib.parse import parse_qs
ModuleNotFoundError: No module named 'six'
```

I reproduced this bug in docker. The following dockerfile exercises it:
```
FROM ubuntu:devel
ENV DEBIAN_FRONTEND=noninteractive
RUN apt-get update
RUN apt-get install -y software-properties-common
RUN add-apt-repository -y --ppa ppa:ubuntu-wsl-dev/ppa
```

Modifying the docker file by adding `RUN apt-get install -y python3-six`
before the last line works as a workaround.

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Ubuntu version: "24.04 (Noble Numbat)"
  software-properties-common version: 0.99.40
- 
  
  This command fails to run when package python3-six is not installed:
  
  ```
  $ add-apt-repository -y --ppa ppa:ubuntu-wsl-dev/ppa
  Traceback (most recent call last):
-   File "/usr/bin/add-apt-repository", line 14, in 
- from softwareproperties.shortcuts import shortcut_handler
-   File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
23, in 
- from softwareproperties.ppa import PPAShortcutHandler
-   File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 25, 
in 
- from launchpadlib.launchpad import Launchpad
-   File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 48, 
in 
- from launchpadlib.credentials import (
-   File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 59, 
in 
- from six.moves.urllib.parse import parse_qs
+   File "/usr/bin/add-apt-repository", line 14, in 
+ from softwareproperties.shortcuts import shortcut_handler
+   File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
23, in 
+ from softwareproperties.ppa import PPAShortcutHandler
+   File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 25, 
in 
+ from launchpadlib.launchpad import Launchpad
+   File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 48, 
in 
+ from launchpadlib.credentials import (
+   File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 59, 
in 
+ from six.moves.urllib.parse import parse_qs
  ModuleNotFoundError: No module named 'six'
  ```
  
  I reproduced this bug in docker. The following dockerfile exercises it:
  ```
  FROM ubuntu:devel
  ENV DEBIAN_FRONTEND=noninteractive
  RUN apt-get update
  RUN apt-get install -y software-properties-common
  RUN add-apt-repository -y --ppa ppa:ubuntu-wsl-dev/ppa
  ```
  
  Modifying the docker file by adding `RUN apt-get install -y python3-six`
- works as a workaround.
+ before the last line works as a workaround.

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

Title:
  software-properties-common is missing dependecy python3-six  in Noble

Status in software-properties package in Ubuntu:
  New

Bug description:
  Ubuntu version: "24.04 (Noble Numbat)"
  software-properties-common version: 0.99.40

  This command fails to run when package python3-six is not installed:

  ```
  $ add-apt-repository -y --ppa ppa:ubuntu-wsl-dev/ppa
  Traceback (most recent call last):
    File "/usr/bin/add-apt-repository", line 14, in 
  from softwareproperties.shortcuts import shortcut_handler
    File "/usr/lib/python3/dist-packages/softwareproperties/shortcuts.py", line 
23, in 
  from softwareproperties.ppa import PPAShortcutHandler
    File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 25, 
in 
  from launchpadlib.launchpad import Launchpad
    File "/usr/lib/python3/dist-packages/launchpadlib/launchpad.py", line 48, 
in 
  from launchpadlib.credentials import (
    File "/usr/lib/python3/dist-packages/launchpadlib/credentials.py", line 59, 
in 
  from six.moves.urllib.parse import parse_qs
  ModuleNotFoundError: No module named 'six'
  ```

  I reproduced this bug in docker. The following dockerfile exercises it:
  ```
  FROM ubuntu:devel
  ENV DEBIAN_FRONTEND=noninteractive
  RUN apt-get update
  

[Touch-packages] [Bug 2048388] Re: Test suite often fails with "systemd units changed without reload" on s390x

[Olivier Gayot]

Added wpa as affected so this bug can show in the proposed migrations
report.

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

** Tags added: update-excuse

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

Title:
  Test suite often fails with "systemd units changed without reload" on
  s390x

Status in netplan:
  Invalid
Status in netplan.io package in Ubuntu:
  Triaged
Status in wpa package in Ubuntu:
  New

Bug description:
  The "ethernets" autopkgtest for netplan.io 0.107-5ubuntu2 on s390x
  often fails with

  AssertionError: systemd units changed without reload

  Looking at the history of autopkgtest runs, it looks like that the
  error does not always occur during execution of a specific test. I've
  seen occurrences of this error during the following test-cases:

  test_dhcp6 (__main__.TestNetworkd.test_dhcp6) ... FAIL
  test_link_local_ipv4 (__main__.TestNetworkd.test_link_local_ipv4) ... FAIL
  test_eth_mtu (__main__.TestNetworkd.test_eth_mtu) ... FAIL

  Example [1]:

  781s FAIL: test_dhcp6 (__main__.TestNetworkd.test_dhcp6)
  781s --
  781s Traceback (most recent call last):
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/ethernets.py", line 
189, in test_dhcp6
  781s self.generate_and_settle([self.state_dhcp6(self.dev_e_client)])
  781s   File 
"/tmp/autopkgtest.G0qQU0/build.Snp/src/tests/integration/base.py", line 342, in 
generate_and_settle
  781s self.fail('systemd units changed without reload')
  781s AssertionError: systemd units changed without reload

  [1] https://autopkgtest.ubuntu.com/results/autopkgtest-
  noble/noble/s390x/n/netplan.io/20240105_144627_cb35e@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2048388/+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 2047780] Re: BlueZ release 5.71

[Gianfranco Costamagna]

next time we should make sure the changelog lists all the delta from Debian :)
But with the same tarball it will be easier to find it out

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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