[Touch-packages] [Bug 2085382] [NEW] lightdm is endlessly starting and dying in a several seconds cycle

[Darko Veberic]

Public bug reported:

since the upgrade from 24.04 to 24.10 the lightdm login does not work
anymore and is starting and then immediately dying in a very fast cycle.
the only way to stop the endless cycle is to quickly try to switch to
the linux vt and press ctrl-alt-del for reboot and then use
systemrescuecd to run "dpkg-reconfigure lightdm" in a chroot to switch
to gdm3 login. i was checking various logs but could not find anything
obvious except for the segfault in the seat0-greeter.log (attached).

ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: lightdm 1.30.0-0ubuntu14
ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
Uname: Linux 6.11.0-9-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: XFCE
Date: Tue Oct 22 22:03:06 2024
InstallationDate: Installed on 2023-09-29 (389 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
SourcePackage: lightdm
UpgradeStatus: Upgraded to oracular on 2024-10-20 (2 days ago)

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


** Tags: amd64 apport-bug oracular third-party-packages

** Attachment added: "tar of the /var/log/lightdm/ contents"
   
https://bugs.launchpad.net/bugs/2085382/+attachment/5830894/+files/lightdm.tar.bz2

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

Title:
  lightdm is endlessly starting and dying in a several seconds cycle

Status in lightdm package in Ubuntu:
  New

Bug description:
  since the upgrade from 24.04 to 24.10 the lightdm login does not work
  anymore and is starting and then immediately dying in a very fast
  cycle. the only way to stop the endless cycle is to quickly try to
  switch to the linux vt and press ctrl-alt-del for reboot and then use
  systemrescuecd to run "dpkg-reconfigure lightdm" in a chroot to switch
  to gdm3 login. i was checking various logs but could not find anything
  obvious except for the segfault in the seat0-greeter.log (attached).

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: lightdm 1.30.0-0ubuntu14
  ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
  Uname: Linux 6.11.0-9-generic x86_64
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Tue Oct 22 22:03:06 2024
  InstallationDate: Installed on 2023-09-29 (389 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oracular on 2024-10-20 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/2085382/+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 2018539] Re: File selector extremely slow

[Tim Blackmore]

I'm also having this issue with the gtk file selector after upgrading
from 22.04 to 24.04.

Nautilus was also very slow to open folders with many files, switched to
Nemo because it was too frustrating. Can't seem to do anything about the
file selector though.

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

Title:
  File selector extremely slow

Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed

Bug description:
  When you try to upload/download a file in an application (e.g.
  Firefox, Signal, etc) the file selector that opens is extremely slow
  to appear, search and change directory.

  Often times, if I try to search for a file in it, I have to wait 10 or
  more second before the letters I typed appear, and most of the time
  the last letter I pressed when typing, will appear before the rest of
  what I wrote, meaning I have to wait for my query to be deleted before
  I re-type it again.

  This has only just started since upgrading to Ubuntu 23.04.  I noticed
  that Nautilus has been faster in general since the update, but in the
  file selector specifically, it's become unusable.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: nautilus 1:44.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May  4 20:39:48 2023
  InstallationDate: Installed on 2022-10-22 (194 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to lunar on 2023-04-21 (13 days ago)
  usr_lib_nautilus:
   file-roller   43.0-1
   nautilus-extension-gnome-terminal 3.48.0-1ubuntu1
   python3-nautilus  4.0-1build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/2018539/+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 2085261] Re: Merge openssh from Debian unstable for plucky

[Nick Rosbrook]

I will plan on doing this.

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => Nick Rosbrook (enr0n)

** Tags added: foundations-todo

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

Title:
  Merge openssh from Debian unstable for plucky

Status in openssh package in Ubuntu:
  New

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1:9.9p1-2
  Ubuntu:   1:9.7p1-7ubuntu4

  
  foundations team has maintained this package's merge in the past.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Jammy Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  openssh (1:9.9p1-2) unstable; urgency=medium

* Don't prefer host-bound public key signatures if there was no initial
  host key, as is the case when using GSS-API key exchange (closes:
  #1041521).
* Use runuser rather than sudo in autopkgtests where possible, avoiding a
  dependency.

   -- Colin Watson   Mon, 21 Oct 2024 18:24:07
  +0100

  openssh (1:9.9p1-1) unstable; urgency=medium

* Alias the old Debian-specific SetupTimeOut client option to
  ConnectTimeout rather than to ServerAliveInterval.
* New upstream release (https://www.openssh.com/releasenotes.html#9.9p1):
  - ssh(1): remove support for pre-authentication compression.
  - ssh(1), sshd(8): processing of the arguments to the 'Match'
configuration directive now follows more shell-like rules for quoted
strings, including allowing nested quotes and /-escaped characters.
  - ssh(1), sshd(8): add support for a new hybrid post-quantum key
exchange based on the FIPS 203 Module-Lattice Key Enapsulation
mechanism (ML-KEM) combined with X25519 ECDH as described by

https://datatracker.ietf.org/doc/html/draft-kampanakis-curdle-ssh-pq-ke-03
This algorithm 'mlkem768x25519-sha256' is available by default.
  - ssh(1): the ssh_config 'Include' directive can now expand environment
as well as the same set of %-tokens 'Match Exec' supports.
  - sshd(8): add a sshd_config 'RefuseConnection' option that, if set will
terminate the connection at the first authentication request.
  - sshd(8): add a 'refuseconnection' penalty class to sshd_config
PerSourcePenalties that is applied when a connection is dropped by the
new RefuseConnection keyword.
  - sshd(8): add a 'Match invalid-user' predicate to sshd_config Match
options that matches when the target username is not valid on the
server.
  - ssh(1), sshd(8): update the Streamlined NTRUPrime code to a
substantially faster implementation.
  - ssh(1), sshd(8): the hybrid Streamlined NTRUPrime/X25519 key exchange
algorithm now has an IANA-assigned name in addition to the
'@openssh.com' vendor extension name. This algorithm is now also
available under this name 'sntrup761x25519-sha512'
  - ssh(1), sshd(8), ssh-agent(1): prevent private keys from being
included in core dump files for most of their lifespans. This is in
addition to pre-existing controls in ssh-agent(1) and sshd(8) that
prevented coredumps.
  - All: convert key handling to use the libcrypto EVP_PKEY API, with the
exception of DSA.
  - sshd(8): add a random amount of jitter (up to 4 seconds) to the grace
login time to make its expiry unpredictable.
  - sshd(8): fix regression introduced in openssh-9.8 that swapped the
order of source and destination addresses in some sshd log messages.
  - sshd(8): do not apply authorized_keys options when signature
verification fails. Prevents more restrictive key options being
incorrectly applied to subsequent keys in authorized_keys.
  - ssh-keygen(1): include pathname in some of ssh-keygen's passphrase
prompts. Helps the user know what's going on when ssh-keygen is
invoked via other tools.
  - ssh(1), ssh-add(1): make parsing user@host consistently look for the
last '@' in the string rather than the first. This makes it possible
to more consistently use usernames that contain '@' characters.
  - ssh(1), sshd(8): be more strict in parsing key type names. Only allow
short names (e.g 'rsa') in user-interface code and require full SSH
protocol names (e.g. 'ssh-rsa') everywhere else.
  - regress: many performance and correctness improvements to the
re-keying regression test.
  - ssh-keygen(1): clarify that ed25519 is the default key type generated
and clarify that rsa-sha2-512 is the default signature scheme when RSA
  

[Touch-packages] [Bug 2085377] Re: transmission-gtk fails to start in separate network namespace

[Georgia Garcia]

Hi Janne, thanks for reporting. Adding attach_disconnected to the profile flags 
is the correct course of action at this point. 
I submitted a MR upstream with the information you provided: 
https://gitlab.com/apparmor/apparmor/-/merge_requests/1395

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

Title:
  transmission-gtk fails to start in separate network namespace

Status in apparmor package in Ubuntu:
  New

Bug description:
  The symptom is that I am no longer unable to start transmission-gtk in
  a separate network namespace. This worked in the past. I have been
  impacted by this bug since upgrading from Ubuntu 22.04 to 24.04.

  Some context: Why would someone run a torrent client in a network
  namespace? It is very convenient for example if one wants to run
  torrent traffic through a VPN tunnel while keeping rest of the system
  connected normally (without VPN).

  Relevant package versions:
  - transmission-gtk: 4.0.5-1build5
  - apparmor: 4.0.1really4.0.1-0ubuntu0.24.04.3

  How to reproduce:

  1. Create a network namespace for running transmission-gtk (for the
  purposes of this demonstration it does not matter that the new
  namespace we create does not have any internet connectivity):

  $ sudo ip netns add foo
  $ sudo -E ip netns exec foo sudo -E -u $USER bash

  2. Now try starting transmission-gtk in that namespace and observe
  failure:

  $ transmission-gtk &
  [1] 2013757
  (transmission-gtk:2013757): Gtk-WARNING **: 21:13:37.265: Failed to open 
display
  [1]+  Exit 1  transmission-gtk

  3. Check why it fails with strace (observe it gets "permission denied"
  when trying to connect to wayland socket):

  $ strace transmission-gtk 
  execve("/usr/bin/transmission-gtk", ["transmission-gtk"], 0x7fff327128d0 /* 
67 vars */) = 0
  [..]
  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC, 0) = 5
  connect(5, {sa_family=AF_UNIX, sun_path="/run/user/1000/wayland-0"}, 27) = -1 
EACCES (Permission denied)
  [..]
  exit_group(1)   = ?
  +++ exited with 1 +++

  4. Also observe messages such as the following appear in
  /var/log/syslog:

  2024-10-22T19:32:27.557750+03:00 XXX kernel: audit: type=1400
  audit(1729614747.556:11615): apparmor="ALLOWED" operation="connect"
  class="file" info="Failed name lookup - disconnected path" error=-13
  profile="transmission-gtk" name="run/user/1000/wayland-0" pid=1978576
  comm="transmission-gt" requested_mask="wr" denied_mask="wr" fsuid=1000
  ouid=1000

  5. Implement workaround (add "attach_disconnected" to apparmor profile
  flags):

  $ sudo sed -i 's/transmission-gtk flags=(complain)/transmission-gtk 
flags=(complain,attach_disconnected)/' /etc/apparmor.d/transmission
  $ sudo apparmor_parser -r /etc/apparmor.d/transmission

  6. Observe now it starts successfully in the same network namespace:

  $ transmission-gtk &
  $

  
  I do not know what is the correct way to fix this properly. I am not familiar 
enough with apparmor. According to apparmor.d(5) manual page that 
"attach_disconnected" flag should not be used except for debugging and policy 
development.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor 4.0.1really4.0.1-0ubuntu0.24.04.3
  ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Oct 22 21:06:02 2024
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-6.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash i8042.noaux vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apparmor
  UpgradeStatus: Upgraded to noble on 2024-08-30 (53 days ago)
  modified.conffile..etc.apparmor.d.transmission: [modified]
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.apparmor.d.transmission: 2024-10-22T20:45:07.247425
  mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2085377/+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 2085377] Re: transmission-gtk fails to start in separate network namespace

[Janne Snabb]

** Description changed:

- The symptom is that I am no longer unable to start transmission-gtk in a
+ The symptom is that I am no longer able to start transmission-gtk in a
  separate network namespace. This worked in the past. I have been
  impacted by this bug since upgrading from Ubuntu 22.04 to 24.04.
  
  Some context: Why would someone run a torrent client in a network
  namespace? It is very convenient for example if one wants to run torrent
  traffic through a VPN tunnel while keeping rest of the system connected
  normally (without VPN).
  
  Relevant package versions:
  - transmission-gtk: 4.0.5-1build5
  - apparmor: 4.0.1really4.0.1-0ubuntu0.24.04.3
  
  How to reproduce:
  
  1. Create a network namespace for running transmission-gtk (for the
  purposes of this demonstration it does not matter that the new namespace
  we create does not have any internet connectivity):
  
  $ sudo ip netns add foo
  $ sudo -E ip netns exec foo sudo -E -u $USER bash
  
  2. Now try starting transmission-gtk in that namespace and observe
  failure:
  
  $ transmission-gtk &
  [1] 2013757
  (transmission-gtk:2013757): Gtk-WARNING **: 21:13:37.265: Failed to open 
display
  [1]+  Exit 1  transmission-gtk
  
  3. Check why it fails with strace (observe it gets "permission denied"
  when trying to connect to wayland socket):
  
- $ strace transmission-gtk 
+ $ strace transmission-gtk
  execve("/usr/bin/transmission-gtk", ["transmission-gtk"], 0x7fff327128d0 /* 
67 vars */) = 0
  [..]
  socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC, 0) = 5
  connect(5, {sa_family=AF_UNIX, sun_path="/run/user/1000/wayland-0"}, 27) = -1 
EACCES (Permission denied)
  [..]
  exit_group(1)   = ?
  +++ exited with 1 +++
  
  4. Also observe messages such as the following appear in
  /var/log/syslog:
  
  2024-10-22T19:32:27.557750+03:00 XXX kernel: audit: type=1400
  audit(1729614747.556:11615): apparmor="ALLOWED" operation="connect"
  class="file" info="Failed name lookup - disconnected path" error=-13
  profile="transmission-gtk" name="run/user/1000/wayland-0" pid=1978576
  comm="transmission-gt" requested_mask="wr" denied_mask="wr" fsuid=1000
  ouid=1000
  
  5. Implement workaround (add "attach_disconnected" to apparmor profile
  flags):
  
  $ sudo sed -i 's/transmission-gtk flags=(complain)/transmission-gtk 
flags=(complain,attach_disconnected)/' /etc/apparmor.d/transmission
  $ sudo apparmor_parser -r /etc/apparmor.d/transmission
  
  6. Observe now it starts successfully in the same network namespace:
  
  $ transmission-gtk &
  $
  
- 
- I do not know what is the correct way to fix this properly. I am not familiar 
enough with apparmor. According to apparmor.d(5) manual page that 
"attach_disconnected" flag should not be used except for debugging and policy 
development.
+ I do not know what is the correct way to fix this properly. I am not
+ familiar enough with apparmor. According to apparmor.d(5) manual page
+ that "attach_disconnected" flag should not be used except for debugging
+ and policy development.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor 4.0.1really4.0.1-0ubuntu0.24.04.3
  ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Oct 22 21:06:02 2024
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-6.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash i8042.noaux vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apparmor
  UpgradeStatus: Upgraded to noble on 2024-08-30 (53 days ago)
  modified.conffile..etc.apparmor.d.transmission: [modified]
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.apparmor.d.transmission: 2024-10-22T20:45:07.247425
  mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07

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

Title:
  transmission-gtk fails to start in separate network namespace

Status in apparmor package in Ubuntu:
  New

Bug description:
  The symptom is that I am no longer able to start transmission-gtk in a
  separate network namespace. This worked in the past. I have been
  impacted by this bug since upgrading from Ubuntu 22.04 to 24.04.

  Some context: Why would someone run a torrent client in a network
  namespace? It is very convenient for example if one wants to run
  torrent traffic through a VPN tunnel while keeping rest of the system
  connected normally (without VPN).

  Relevant package versions:
  - transmission-gtk: 4.0.5-1build5
  - apparmor: 4.0.1really4.0.1-0ubuntu0.24.04.3

  How to reproduce:

  1. Create a network namespace for running transmission-gtk (for the
  purposes of this demonstration it does not matter that t

[Touch-packages] [Bug 2085388] [NEW] MSI Bravo 15, AMD, Radeon - loud fan, HDMI not working

[Launchpad Bug Tracker]

*** This bug is a security vulnerability ***

You have been subscribed to a public security bug:

I am experiencing two significant issues on my MSI Bravo 15 laptop (AMD
Ryzen™ 5 4600H with Radeon™ Graphics × 12) running Ubuntu 24.04.1 LTS:

Fan Noise: The system is consistently making loud fan noises, even
during low workloads. This happens immediately after boot and persists,
affecting the overall user experience.

HDMI Not Working: Despite various attempts (including driver updates,
reconfiguring display settings, and using different HDMI cables), the
HDMI output is completely non-functional. The system does not recognize
external displays at all.

These issues significantly impact usability, and I would greatly
appreciate any assistance or insights on how to resolve them.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/seq:purplebyteone   3166 F pipewire
 /dev/snd/controlC0:  purplebyteone   3169 F wireplumber
 /dev/snd/controlC1:  purplebyteone   3169 F wireplumber
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 22 23:15:37 2024
InstallationDate: Installed on 2024-07-24 (90 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
MachineType: Micro-Star International Co., Ltd. Bravo 15 A4DDR
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
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/29/2020
dmi.bios.release: 1.16
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16WKAMS.110
dmi.board.asset.tag: Default string
dmi.board.name: MS-16WK
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16WKAMS.110:bd10/29/2020:br1.16:svnMicro-StarInternationalCo.,Ltd.:pnBravo15A4DDR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16WK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16WK.1:
dmi.product.family: Br
dmi.product.name: Bravo 15 A4DDR
dmi.product.sku: 16WK.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug noble wayland-session
-- 
MSI Bravo 15, AMD, Radeon - loud fan, HDMI not working
https://bugs.launchpad.net/bugs/2085388
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 2085388] Re: MSI Bravo 15, AMD, Radeon - loud fan, HDMI not working

[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/2085388

Title:
  MSI Bravo 15, AMD, Radeon - loud fan, HDMI not working

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I am experiencing two significant issues on my MSI Bravo 15 laptop
  (AMD Ryzen™ 5 4600H with Radeon™ Graphics × 12) running Ubuntu 24.04.1
  LTS:

  Fan Noise: The system is consistently making loud fan noises, even
  during low workloads. This happens immediately after boot and
  persists, affecting the overall user experience.

  HDMI Not Working: Despite various attempts (including driver updates,
  reconfiguring display settings, and using different HDMI cables), the
  HDMI output is completely non-functional. The system does not
  recognize external displays at all.

  These issues significantly impact usability, and I would greatly
  appreciate any assistance or insights on how to resolve them.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
  Uname: Linux 6.8.0-45-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/seq:purplebyteone   3166 F pipewire
   /dev/snd/controlC0:  purplebyteone   3169 F wireplumber
   /dev/snd/controlC1:  purplebyteone   3169 F wireplumber
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 22 23:15:37 2024
  InstallationDate: Installed on 2024-07-24 (90 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  MachineType: Micro-Star International Co., Ltd. Bravo 15 A4DDR
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  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/29/2020
  dmi.bios.release: 1.16
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16WKAMS.110
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16WK
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16WKAMS.110:bd10/29/2020:br1.16:svnMicro-StarInternationalCo.,Ltd.:pnBravo15A4DDR:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16WK:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku16WK.1:
  dmi.product.family: Br
  dmi.product.name: Bravo 15 A4DDR
  dmi.product.sku: 16WK.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2085388/+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 2085219] Re: Merge bridge-utils from Debian unstable for plucky

[Bryce Harrington]

** Summary changed:

- Merge bridge-utils from Debian unstable for jammy
+ Merge bridge-utils from Debian unstable for plucky

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

Title:
  Merge bridge-utils from Debian unstable for plucky

Status in bridge-utils package in Ubuntu:
  Incomplete

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1.7.1-2
  Ubuntu:   1.7.1-2ubuntu1


  There is nothing yet to merge for bridge-utils currently, but this
  ticket is filed prospectfully for tracking purposes in case a merge
  does become available later this cycle.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Jammy Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  bridge-utils (1.7.1-2) unstable; urgency=low

[ Debian Janitor ]
* Trim trailing whitespace.
* Update standards version to 4.6.2, no changes needed.

[ Chris Hofstaedtler ]
* Install files into /usr instead of /. (Closes: #1059394)

   -- Santiago García Mantiñán   Fri, 01 Mar 2024
  23:09:33 +0100

  bridge-utils (1.7.1-1) unstable; urgency=low

* New upstream version.
  Only some fixes for compilation warnings and the man page.
* Update standards version to 4.6.1, no changes needed.
* Set debhelper-compat version in Build-Depends.
* Trim trailing whitespace.

   -- Santiago García Mantiñán   Wed, 25 Jan 2023
  22:11:52 +0100

  bridge-utils (1.7-2) unstable; urgency=medium

* Add BRIDGE_DISABLE_LINKLOCAL_IPV6_ALSO_PHYS to /etc/default/bridge-utils
  to stop disabling IPv6 on physical interfaces of vlan ports if set to no.
  Closes: #989162.
* Update interfaces man page, IPv6 works with STP on after DAD was fixed.
  Closes: #980507.
* Treat vlan ports the same as ifupdown, avoid octal vlans. Closes: #995627.
* Update NEWS file to fix us blaming the kernel for the MAC address
  selection that is really overridden by systemd.

   -- Santiago García Mantiñán   Mon, 03 Oct 2022
  23:11:46 +0200

  bridge-utils (1.7-1) unstable; urgency=medium

* New upstream version.
  Only messages related changes and compilation fixes.
* Remove preserve_gcc_flags patch (in upstream now).
* Bump standards, no change needed.
* Clarify portprio and fix example.
* Update upstream url.
* Fix NEWS versioning of last entry :-?

   -- Santiago Garcia Mantinan   Wed, 24 Feb 2021
  12:34:03 +0100

  bridge-utils (1.6-6) unstable; urgency=medium

* Fix IPv6 address getting assigned on hotplug devices.
  Closes: #980752.
* Fix waiting so that DAD works again. Closes: #982943.
* Move mac setting before brctl addif to ensure mac setting.
  Closes: #980856.
* Update documentation and add examples. Closes: #765098.
* Update manpages. Closes: #981253.
* Add a note on MTU settings. Closes: #292088.
* Hook also on down to recreate the bridge so that multiple
  stanzas work Ok on ifdown. Closes: #319832.

   -- Santiago Garcia Mantinan   Tue, 16 Feb 2021
  13:29:04 +0100

  bridge-utils (1.6-5) unstable; urgency=low

* Overload bridge_hw to allow do specify an interface as well as the
  MAC address. Closes: #966244.
* Change man page for bridge-utils-interfaces and news fileto document
  this overloading.

   -- Santiago Garcia Mantinan   Fri, 22 Jan 2021
  11:08:47 +0100

  bridge-utils (1.6-4) unstable; urgency=low

* Add en* to the device regex so that all catches them. Closes: #966319.
* Document MAC address changes on news. Closes: #980505.

   -- Santiago Garcia Mantinan   Thu, 21 Jan 2021
  10:51:31 +0100

  bridge-utils (1.6-3) unstable; urgency=medium

* Support VLAN aware setups where we need vlan filtering.
  Thanks Benedikt Spranger for the patch. Closes: #950879.
* Clarify on manual page that stp will get IPv6 lost. Closes: #736336.
* Add a 1 second sleep if hw address needs to be changed. Closes: #945466.

   -- Santiago Garcia Mantinan   Thu, 30 Apr 2020
  10:06:38 +0200

  bridge-utils (1.6-2) unstable; urgency=medium

* Bump Standards-Version.
* Preserve gcc flags set when building the lib.

   -- Santiago Garcia Mantinan   Mon, 28 Jan 2019
  00:25:14 +0100

  bridge-utils (1.6-1) unstable; urgency=low

* New upstream version.
* Change default back to not hotplug. Closes: #892277.
* Allow mtu to be set on the bridge by propagating it to the bridged
  interfaces. Closes: #661711.
* Remove kernel headers from the package.


  ### Old Ubuntu Delta ###

  bridge-utils (1.7.1-2ubuntu1) oracular; urgency=medium

* Merge with Debian unstable (LP: #2064391). Remaining changes

[Touch-packages] [Bug 2085255] Re: Merge net-tools from Debian unstable for plucky

[Bryce Harrington]

** Summary changed:

- Merge net-tools from Debian unstable for jammy
+ Merge net-tools from Debian unstable for plucky

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

Title:
  Merge net-tools from Debian unstable for plucky

Status in net-tools package in Ubuntu:
  Incomplete

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   2.10-1.1
  Ubuntu:   2.10-1.1ubuntu1


  There is nothing yet to merge for net-tools currently, but this ticket
  is filed prospectfully for tracking purposes in case a merge does
  become available later this cycle.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Jammy Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  net-tools (2.10-1.1) unstable; urgency=medium

* Non-maintainer upload.
* Release to unstable. (Closes: #1059409)

   -- Chris Hofstaedtler   Mon, 22 Apr 2024 01:55:29
  +0200

  net-tools (2.10-1) experimental; urgency=medium

* Move to /usr-merge (DEP17).

   -- Utkarsh Gupta   Thu, 23 Nov 2023 14:41:07
  +

  net-tools (2.10-0.1) unstable; urgency=medium

* Non-maintainer upload.
* Update Martina's name and email address.
* Drop DECnet support (Closes: #1024730)
* Revert 'Fix d/watch to point to upstream git repository'
* New upstream version 2.10 (Closes: #1000281)

   -- Bastian Germann   Fri, 25 Nov 2022 15:15:20 +0100

  net-tools (1.60+git20181103.0eebece-1) unstable; urgency=medium

* New upstream version 1.60+git20181103.0eebece
  - Fix nstrcmp() to prevent ifconfig from showing
duplicate interfaces. (Closes: #812886)
* Fix d/watch to point to upstream git repository
* Add patch to fix decoding of MII vendor ids. (Closes: #549397)
  - Thanks, Ben Hutchings, for the patch.
* Add patch to fix Japanese translation which uses a wrong
  Kanji character. (Closes: #621752)
  - Thanks, Takeshi Hamasaki, for the patch.
* Add patch to fix wrong indentation of 'collisions' in  the
  Japanese translation. (Closes: #653117)
  - Thanks, NODA, Kai, for the patch.
* Fix Uploaders' field.
  - Add myself as an uploader.
  - Fix Tina's details.

   -- Utkarsh Gupta   Fri, 02 Oct 2020 15:01:04
  +0530

  net-tools (1.60+git20180626.aebd88e-1) unstable; urgency=medium

* New upstream snapshot
* Refresh patches.
* Fix typos in German manpages. Thanks to Prof. Dr. Steffen Wendzel and
  Dr. Tobias Quathamer for the patch. Closes: #900962.

   -- Martina Ferrari   Mon, 24 Sep 2018 19:08:57 +

  net-tools (1.60+git20161116.90da8a0-4) unstable; urgency=medium

* Update maintainer email address. Closes: #899617.
* Update Standards-Version with no changes.

   -- Martina Ferrari   Mon, 24 Sep 2018 17:16:31 +

  net-tools (1.60+git20161116.90da8a0-3) unstable; urgency=medium

* debian/control: Update Vcs-* and Standards-Version.
* debian/control: remove references to ancient package ja-trans.
* debian/gbp.conf: Update repo layout.

   -- Martina Ferrari   Tue, 31 Jul 2018 19:09:00 +

  net-tools (1.60+git20161116.90da8a0-2) unstable; urgency=medium

* Fix typo in French manpage. Thanks to  Michel Grigaut for the patch.
* Add manpage for iptunnel, thanks to Sergio Durigan Junior.
  Closes: #88910
* Rename patches so CME does not choke on them.
* Automated cme fixes; packaging improvements.
* Remove unused and ancient patch.

   -- Martina Ferrari   Sun, 11 Feb 2018 17:29:24 +

  net-tools (1.60+git20161116.90da8a0-1) unstable; urgency=medium

* New upstream snapshot.
* Re-synced translations.patch.
* Acknowledge NMUs. Thanks a lot to Andrey Rahmatullin for the
  fixes and uploads. Closes: 846509.
* Fix FTCBFS, thanks to Helmut Grohne for the patch. Closes: #811561.
  + Really assign CC for cross compilation.
  + Use triplet prefixed pkg-config.
* Add debian/NEWS warning about changing output in net-tools commands.
  Closing bugs that reported problems in 3rd-party scripts arising from 
these
  changes.  Closes: #845153, #843892, #820212.
* Update Standards-Version, with no changes.

   -- Martina Ferrari   Mon, 26 Dec 2016 05:58:42 +

  net-tools (1.60+git20150829.73cef8a-2.2) unstable; urgency=medium

* Non-maintainer upload.
* Apply an additional fix for the previous FTBFS for some architectures.

   -- Andrey Rahmatullin   Thu, 01 Dec 2016 22:49:27
  +0500


  ### Old Ubuntu Delta ###

  net-tools (2.10-1.1ubuntu1) oracular; urgency=medium

* Merge with Debian unstable (LP: #2064431). Remaining changes:
  - Ubuntu_unit_conversion.patch (LP #240073):
   

[Touch-packages] [Bug 2078047] Re: Collect logs for linux-firmware

[Juerg Haefliger]

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

** This bug has been marked a duplicate of bug 1872059
   missing hardware/runtime info when reporing linux-firmware bugs via apport

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

Title:
  Collect logs for linux-firmware

Status in apport package in Ubuntu:
  New

Bug description:
  When a bug is filed against linux-firmware (or any other firmware
  package), kernel logs should be collected and attached to the bug
  report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2078047/+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 2085255] Re: Merge net-tools from Debian unstable for jammy

[Lena Voytek]

** Changed in: net-tools (Ubuntu)
 Assignee: (unassigned) => Lena Voytek (lvoytek)

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

Title:
  Merge net-tools from Debian unstable for jammy

Status in net-tools package in Ubuntu:
  Incomplete

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   2.10-1.1
  Ubuntu:   2.10-1.1ubuntu1


  There is nothing yet to merge for net-tools currently, but this ticket
  is filed prospectfully for tracking purposes in case a merge does
  become available later this cycle.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Jammy Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  net-tools (2.10-1.1) unstable; urgency=medium

* Non-maintainer upload.
* Release to unstable. (Closes: #1059409)

   -- Chris Hofstaedtler   Mon, 22 Apr 2024 01:55:29
  +0200

  net-tools (2.10-1) experimental; urgency=medium

* Move to /usr-merge (DEP17).

   -- Utkarsh Gupta   Thu, 23 Nov 2023 14:41:07
  +

  net-tools (2.10-0.1) unstable; urgency=medium

* Non-maintainer upload.
* Update Martina's name and email address.
* Drop DECnet support (Closes: #1024730)
* Revert 'Fix d/watch to point to upstream git repository'
* New upstream version 2.10 (Closes: #1000281)

   -- Bastian Germann   Fri, 25 Nov 2022 15:15:20 +0100

  net-tools (1.60+git20181103.0eebece-1) unstable; urgency=medium

* New upstream version 1.60+git20181103.0eebece
  - Fix nstrcmp() to prevent ifconfig from showing
duplicate interfaces. (Closes: #812886)
* Fix d/watch to point to upstream git repository
* Add patch to fix decoding of MII vendor ids. (Closes: #549397)
  - Thanks, Ben Hutchings, for the patch.
* Add patch to fix Japanese translation which uses a wrong
  Kanji character. (Closes: #621752)
  - Thanks, Takeshi Hamasaki, for the patch.
* Add patch to fix wrong indentation of 'collisions' in  the
  Japanese translation. (Closes: #653117)
  - Thanks, NODA, Kai, for the patch.
* Fix Uploaders' field.
  - Add myself as an uploader.
  - Fix Tina's details.

   -- Utkarsh Gupta   Fri, 02 Oct 2020 15:01:04
  +0530

  net-tools (1.60+git20180626.aebd88e-1) unstable; urgency=medium

* New upstream snapshot
* Refresh patches.
* Fix typos in German manpages. Thanks to Prof. Dr. Steffen Wendzel and
  Dr. Tobias Quathamer for the patch. Closes: #900962.

   -- Martina Ferrari   Mon, 24 Sep 2018 19:08:57 +

  net-tools (1.60+git20161116.90da8a0-4) unstable; urgency=medium

* Update maintainer email address. Closes: #899617.
* Update Standards-Version with no changes.

   -- Martina Ferrari   Mon, 24 Sep 2018 17:16:31 +

  net-tools (1.60+git20161116.90da8a0-3) unstable; urgency=medium

* debian/control: Update Vcs-* and Standards-Version.
* debian/control: remove references to ancient package ja-trans.
* debian/gbp.conf: Update repo layout.

   -- Martina Ferrari   Tue, 31 Jul 2018 19:09:00 +

  net-tools (1.60+git20161116.90da8a0-2) unstable; urgency=medium

* Fix typo in French manpage. Thanks to  Michel Grigaut for the patch.
* Add manpage for iptunnel, thanks to Sergio Durigan Junior.
  Closes: #88910
* Rename patches so CME does not choke on them.
* Automated cme fixes; packaging improvements.
* Remove unused and ancient patch.

   -- Martina Ferrari   Sun, 11 Feb 2018 17:29:24 +

  net-tools (1.60+git20161116.90da8a0-1) unstable; urgency=medium

* New upstream snapshot.
* Re-synced translations.patch.
* Acknowledge NMUs. Thanks a lot to Andrey Rahmatullin for the
  fixes and uploads. Closes: 846509.
* Fix FTCBFS, thanks to Helmut Grohne for the patch. Closes: #811561.
  + Really assign CC for cross compilation.
  + Use triplet prefixed pkg-config.
* Add debian/NEWS warning about changing output in net-tools commands.
  Closing bugs that reported problems in 3rd-party scripts arising from 
these
  changes.  Closes: #845153, #843892, #820212.
* Update Standards-Version, with no changes.

   -- Martina Ferrari   Mon, 26 Dec 2016 05:58:42 +

  net-tools (1.60+git20150829.73cef8a-2.2) unstable; urgency=medium

* Non-maintainer upload.
* Apply an additional fix for the previous FTBFS for some architectures.

   -- Andrey Rahmatullin   Thu, 01 Dec 2016 22:49:27
  +0500


  ### Old Ubuntu Delta ###

  net-tools (2.10-1.1ubuntu1) oracular; urgency=medium

* Merge with Debian unstable (LP: #2064431). Remaining changes:
  - Ubuntu_unit_conversion.patch (LP #240073):
+ Ubuntu Policy: output using

[Touch-packages] [Bug 2084923] Re: Upload for Plucky has wrong strings

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 13.5ubuntu2

---
base-files (13.5ubuntu2) plucky; urgency=medium

  * Mark release as development. LP: #2084923.

 -- Matthias Klose   Sat, 19 Oct 2024 11:52:42 +0200

** Changed in: base-files (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Upload for Plucky has wrong strings

Status in base-files package in Ubuntu:
  Fix Released

Bug description:
  Just blocking the migration:

  https://launchpad.net/ubuntu/+source/base-files/13.5ubuntu1
  os-release, issue, etc should say something like "Ubuntu Plucky Puffin 
(development branch)", not directly the version number.
  Looking at the diff for the Oracular release gives a hint: 
http://launchpadlibrarian.net/753020717/base-files_13.3ubuntu5_13.3ubuntu6.diff.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2084923/+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 2084775] Re: BlueZ release 5.78

[Launchpad Bug Tracker]

This bug was fixed in the package bluez - 5.78-0ubuntu2

---
bluez (5.78-0ubuntu2) plucky; urgency=medium

  * Revert "Updated to new cups backend path". While testing the build on
Oracular required that change at the time, the archive seems to want
the old syntax when building for Plucky.

 -- Daniel van Vugt   Mon, 21 Oct 2024
17:02:23 +0800

** Changed in: bluez (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  BlueZ release 5.78

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.78 to Ubuntu 25.04 (when it opens)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2084775/+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 2085377] [NEW] transmission-gtk fails to start in separate network namespace

[Janne Snabb]

Public bug reported:

The symptom is that I am no longer unable to start transmission-gtk in a
separate network namespace. This worked in the past. I have been
impacted by this bug since upgrading from Ubuntu 22.04 to 24.04.

Some context: Why would someone run a torrent client in a network
namespace? It is very convenient for example if one wants to run torrent
traffic through a VPN tunnel while keeping rest of the system connected
normally (without VPN).

Relevant package versions:
- transmission-gtk: 4.0.5-1build5
- apparmor: 4.0.1really4.0.1-0ubuntu0.24.04.3

How to reproduce:

1. Create a network namespace for running transmission-gtk (for the
purposes of this demonstration it does not matter that the new namespace
we create does not have any internet connectivity):

$ sudo ip netns add foo
$ sudo -E ip netns exec foo sudo -E -u $USER bash

2. Now try starting transmission-gtk in that namespace and observe
failure:

$ transmission-gtk &
[1] 2013757
(transmission-gtk:2013757): Gtk-WARNING **: 21:13:37.265: Failed to open display
[1]+  Exit 1  transmission-gtk

3. Check why it fails with strace (observe it gets "permission denied"
when trying to connect to wayland socket):

$ strace transmission-gtk 
execve("/usr/bin/transmission-gtk", ["transmission-gtk"], 0x7fff327128d0 /* 67 
vars */) = 0
[..]
socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC, 0) = 5
connect(5, {sa_family=AF_UNIX, sun_path="/run/user/1000/wayland-0"}, 27) = -1 
EACCES (Permission denied)
[..]
exit_group(1)   = ?
+++ exited with 1 +++

4. Also observe messages such as the following appear in
/var/log/syslog:

2024-10-22T19:32:27.557750+03:00 XXX kernel: audit: type=1400
audit(1729614747.556:11615): apparmor="ALLOWED" operation="connect"
class="file" info="Failed name lookup - disconnected path" error=-13
profile="transmission-gtk" name="run/user/1000/wayland-0" pid=1978576
comm="transmission-gt" requested_mask="wr" denied_mask="wr" fsuid=1000
ouid=1000

5. Implement workaround (add "attach_disconnected" to apparmor profile
flags):

$ sudo sed -i 's/transmission-gtk flags=(complain)/transmission-gtk 
flags=(complain,attach_disconnected)/' /etc/apparmor.d/transmission
$ sudo apparmor_parser -r /etc/apparmor.d/transmission

6. Observe now it starts successfully in the same network namespace:

$ transmission-gtk &
$


I do not know what is the correct way to fix this properly. I am not familiar 
enough with apparmor. According to apparmor.d(5) manual page that 
"attach_disconnected" flag should not be used except for debugging and policy 
development.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: apparmor 4.0.1really4.0.1-0ubuntu0.24.04.3
ProcVersionSignature: Ubuntu 6.8.0-45.45-generic 6.8.12
Uname: Linux 6.8.0-45-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Tue Oct 22 21:06:02 2024
ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-6.8.0-45-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash i8042.noaux vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: apparmor
UpgradeStatus: Upgraded to noble on 2024-08-30 (53 days ago)
modified.conffile..etc.apparmor.d.transmission: [modified]
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.apparmor.d.transmission: 2024-10-22T20:45:07.247425
mtime.conffile..etc.init.d.apport: 2024-07-22T17:59:07

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


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

** Attachment removed: "KernLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2085377/+attachment/5830889/+files/KernLog.txt

** Attachment removed: "Syslog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2085377/+attachment/5830893/+files/Syslog.txt

** Attachment removed: "PstreeP.txt"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2085377/+attachment/5830892/+files/PstreeP.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2085377/+attachment/5830891/+files/ProcEnviron.txt

** Attachment removed: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2085377/+attachment/5830890/+files/ProcCpuinfoMinimal.txt

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

Title:
  transmission-gtk fails to start in separate network namespace

Status in apparmor package in Ubuntu:
  New

Bug description:
  The symptom is that I am no longer unable to start transmission-gtk in
  a separate network namespace. This worked in the past. I have been
  impacted by this bug since upgrading from Ubuntu 22.04 to 24.04.

  Some context: Why would someone run a torrent client in a network
  namespace? It is very convenient for example if one wants to run
  torr

[Touch-packages] [Bug 2085261] Re: Merge openssh from Debian unstable for plucky

[Bryce Harrington]

** Summary changed:

- Merge openssh from Debian unstable for jammy
+ Merge openssh from Debian unstable for plucky

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

Title:
  Merge openssh from Debian unstable for plucky

Status in openssh package in Ubuntu:
  New

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1:9.9p1-2
  Ubuntu:   1:9.7p1-7ubuntu4

  
  foundations team has maintained this package's merge in the past.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Jammy Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  openssh (1:9.9p1-2) unstable; urgency=medium

* Don't prefer host-bound public key signatures if there was no initial
  host key, as is the case when using GSS-API key exchange (closes:
  #1041521).
* Use runuser rather than sudo in autopkgtests where possible, avoiding a
  dependency.

   -- Colin Watson   Mon, 21 Oct 2024 18:24:07
  +0100

  openssh (1:9.9p1-1) unstable; urgency=medium

* Alias the old Debian-specific SetupTimeOut client option to
  ConnectTimeout rather than to ServerAliveInterval.
* New upstream release (https://www.openssh.com/releasenotes.html#9.9p1):
  - ssh(1): remove support for pre-authentication compression.
  - ssh(1), sshd(8): processing of the arguments to the 'Match'
configuration directive now follows more shell-like rules for quoted
strings, including allowing nested quotes and /-escaped characters.
  - ssh(1), sshd(8): add support for a new hybrid post-quantum key
exchange based on the FIPS 203 Module-Lattice Key Enapsulation
mechanism (ML-KEM) combined with X25519 ECDH as described by

https://datatracker.ietf.org/doc/html/draft-kampanakis-curdle-ssh-pq-ke-03
This algorithm 'mlkem768x25519-sha256' is available by default.
  - ssh(1): the ssh_config 'Include' directive can now expand environment
as well as the same set of %-tokens 'Match Exec' supports.
  - sshd(8): add a sshd_config 'RefuseConnection' option that, if set will
terminate the connection at the first authentication request.
  - sshd(8): add a 'refuseconnection' penalty class to sshd_config
PerSourcePenalties that is applied when a connection is dropped by the
new RefuseConnection keyword.
  - sshd(8): add a 'Match invalid-user' predicate to sshd_config Match
options that matches when the target username is not valid on the
server.
  - ssh(1), sshd(8): update the Streamlined NTRUPrime code to a
substantially faster implementation.
  - ssh(1), sshd(8): the hybrid Streamlined NTRUPrime/X25519 key exchange
algorithm now has an IANA-assigned name in addition to the
'@openssh.com' vendor extension name. This algorithm is now also
available under this name 'sntrup761x25519-sha512'
  - ssh(1), sshd(8), ssh-agent(1): prevent private keys from being
included in core dump files for most of their lifespans. This is in
addition to pre-existing controls in ssh-agent(1) and sshd(8) that
prevented coredumps.
  - All: convert key handling to use the libcrypto EVP_PKEY API, with the
exception of DSA.
  - sshd(8): add a random amount of jitter (up to 4 seconds) to the grace
login time to make its expiry unpredictable.
  - sshd(8): fix regression introduced in openssh-9.8 that swapped the
order of source and destination addresses in some sshd log messages.
  - sshd(8): do not apply authorized_keys options when signature
verification fails. Prevents more restrictive key options being
incorrectly applied to subsequent keys in authorized_keys.
  - ssh-keygen(1): include pathname in some of ssh-keygen's passphrase
prompts. Helps the user know what's going on when ssh-keygen is
invoked via other tools.
  - ssh(1), ssh-add(1): make parsing user@host consistently look for the
last '@' in the string rather than the first. This makes it possible
to more consistently use usernames that contain '@' characters.
  - ssh(1), sshd(8): be more strict in parsing key type names. Only allow
short names (e.g 'rsa') in user-interface code and require full SSH
protocol names (e.g. 'ssh-rsa') everywhere else.
  - regress: many performance and correctness improvements to the
re-keying regression test.
  - ssh-keygen(1): clarify that ed25519 is the default key type generated
and clarify that rsa-sha2-512 is the default signature scheme when RSA
is in use.
  - sshd(8): 

[Touch-packages] [Bug 2085236] Re: Merge init-system-helpers from Debian unstable for plucky

[Bryce Harrington]

** Summary changed:

- Merge init-system-helpers from Debian unstable for jammy
+ Merge init-system-helpers from Debian unstable for plucky

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

Title:
  Merge init-system-helpers from Debian unstable for plucky

Status in init-system-helpers package in Ubuntu:
  New

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1.67
  Ubuntu:   1.66ubuntu1

  
  foundations team has maintained this package's merge in the past.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Jammy Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  init-system-helpers (1.67) unstable; urgency=medium

[ Mark Hindley ]
* Don't manually set status symlinks for native openrc-run scripts. For
  native openrc-run scripts, fiddling with the links before the script
  is run actually prevents it from running as openrc-run detects the
  status has been changed and considers the script as already started.
  (Closes: #1081994)

[ Luca Boccassi ]
* d/control: bump Standards-Version to 4.7.0, no changes

   -- Luca Boccassi   Tue, 17 Sep 2024 17:07:33 +0200

  init-system-helpers (1.66) unstable; urgency=medium

[ Samuel Thibault ]
* Add hurd-amd64 case.

[ Gioele Barabucci ]
* d/init.lintian-overrides: Silence warning about 'Important' field
  `Important: yes` instructs APT to warn the user before removing this
  package.

[ Johannes Schauer Marin Rodrigues ]
* script/update-rc.d: DPKG_ROOT support for sysvinit

[ Ansgar ]
* Add 'Protected: yes' to package 'init' The 'Protected' field does the
  same as 'Important' already did in apt, but is also understood by dpkg
  (since dpkg 1.20.1).

[ Luca Boccassi ]
* Bump Standards-Version to 4.6.2, no changes
* Override Lintian warning for Protected: yes
* deb-systemd-invoke: support reload/reexec. This is useful for the
  --user case, to provide a shortcut that loops over all active user
  sessions over D-Bus.
* deb-systemd-invoke: support --no-dbus for reload/reexec. Provide
  common implementation for SIGHUP/SIGRTMIN+25 to reload/reexec the
  system or user instances.

   -- Luca Boccassi   Sun, 26 Nov 2023 20:42:28 +

  init-system-helpers (1.65.2) unstable; urgency=low

* Undo yet another hostile and baseless NMU.

   -- Luca Boccassi   Sun, 18 Sep 2022 02:53:19 +0100

  init-system-helpers (1.65.1) unstable; urgency=low

* Undo hostile NMU.

   -- Luca Boccassi   Sun, 18 Sep 2022 01:53:32 +0100

  init-system-helpers (1.65) unstable; urgency=low

* Upload to unstable.

   -- Luca Boccassi   Sat, 17 Sep 2022 21:11:07 +0100

  init-system-helpers (1.65~exp2) experimental; urgency=medium

* fakechroot tests: skip on architectures where it is not available

   -- Luca Boccassi   Thu, 15 Sep 2022 21:14:08 +0100

  init-system-helpers (1.65~exp1) experimental; urgency=medium

[ Luca Boccassi ]
* Drop outdated conflict with file-rc
* Add myself to Uploaders
* d/rules: use execute_after instead of override
* Add a dependency on usrmerge | usr-is-merged to complete the
  transition. As per ctte decision and discussion at:
  https://lists.debian.org/debian-ctte/2022/07/msg00019.html
  https://lists.debian.org/debian-ctte/2022/07/msg00061.html
  https://lists.debian.org/debian-ctte/2022/08/msg6.html

[ Victor Westerhuis ]
* Make deb-systemd-helper work on template units with DefaultInstance.
  DefaultInstance only influences the meaning of WantedBy/RequiredBy.
  Alias and Also are not impacted. This patch does not enable changing
  template instantiations, so `deb-systemd-helper enable
  getty@tty2.service` will still fail.
* Fix tests depending on ordering of lines in state file. The previous
  commit changes the order in which lines are written to the state file.
  Because correctness does not depend on the order in which the state
  file is written, ignore the order in the test.

   -- Luca Boccassi   Sat, 10 Sep 2022 13:27:16 +0100

  init-system-helpers (1.64) unstable; urgency=medium

* Team upload.
* d-s-h: break infinite recursion on symlinks. (Closes: #1014119)
* Bump Standards-Version to 4.6.1, no changes
* Update date ranges in d/copyright


  
  ### Old Ubuntu Delta ###

  init-system-helpers (1.66ubuntu1) noble; urgency=medium

* Merge from Debian unstable.  Remaining changes:
  - Drop dependency on usrmerge.

   -- Steve Langasek   Tue, 05 Dec 2023
  23:50:15 -0800

To manage notifications about this bug go to:
h

[Touch-packages] [Bug 2085257] Re: Merge nspr from Debian unstable for plucky

[Bryce Harrington]

** Summary changed:

- Merge nspr from Debian unstable for jammy
+ Merge nspr from Debian unstable for plucky

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

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

Title:
  Merge nspr from Debian unstable for plucky

Status in nspr package in Ubuntu:
  Incomplete

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   2:4.35-1.1
  Ubuntu:   2:4.35-1.1ubuntu1


  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Jammy Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  nspr (2:4.35-1.1) unstable; urgency=medium

* Non-maintainer upload
* Avoid libreswan build failures on mipsel (Closes: #854472)

   -- Daniel Kahn Gillmor   Wed, 22 Feb 2023
  15:00:34 -0500

  nspr (2:4.35-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Sun, 18 Sep 2022 06:29:06 +0900

  nspr (2:4.34.1-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Wed, 24 Aug 2022 06:54:43 +0900

  nspr (2:4.34-1) unstable; urgency=medium

* New upstream release.

* debian/libnspr4.symbols: Add PR_GetPrefLoopbackAddrInfo to symbols
  file.

   -- Mike Hommey   Wed, 01 Jun 2022 06:21:09 +0900

  nspr (2:4.33-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Wed, 06 Apr 2022 09:13:06 +0900

  nspr (2:4.32-3) unstable; urgency=medium

* nspr/configure.in: Fix AC_CONFIG_AUX_DIR.

   -- Mike Hommey   Sun, 21 Nov 2021 09:06:33 +0900

  nspr (2:4.32-2) unstable; urgency=medium

* debian/libnspr4-dev.links.in, debian/control: Remove xulrunner-nspr.pc,
  which breaks libxmlsec1-dev (<= 1.2.33-1).
* debian/copyright: Use secure copyright file specification URI.
* debian/compat, debian/control:
  - Bump debhelper from deprecated 9 to 13.
  - Set debhelper-compat version in Build-Depends.
* debian/rules: Drop transition for old debug package migration.
* debian/*lintian-overrides*:
  - Remove unused copyright-refers-to-versionless-license-file.
  - s/shlib-without-versioned-soname/shared-library-lacks-version/
  - 
s/dev-pkg-without-shlib-symlink/lacks-unversioned-link-to-shared-library/
* debian/watch: Upgrade watch file to version 4.
* debian/rules:
  - Build with `make -s` when DEB_BUILD_OPTIONS contains terse.
  - Enable all hardnening options.
* debian/control:
  - Add Rules-Requires-Root: no.
  - Upgrade Standards-Version to 4.6.0.
  - Remove conflict with libnspr3-0d. The last Debian version with
libnspr3-0d was jessie, and it had a newer version anyways.
  - Remove now unnecessary autotools-dev build dependency.
* debian/libnspr4.symbols: Add Build-Depends-Package in symbols file.
* debian/control, debian/rules: Always set Multi-Arch: same.
* debian/upstream/metadata: Add upstream bug tracking metadata.
* debian/libnspr4.triggers: Remove ldconfig trigger, dh_makeshlibs adds
  it automatically.
* debian/not-installed: Don't install compile-et.pl and prerr.properties.

   -- Mike Hommey   Sun, 21 Nov 2021 07:09:06 +0900

  nspr (2:4.32-1) unstable; urgency=medium

* New upstream release. Closes: #991234.

   -- Mike Hommey   Mon, 19 Jul 2021 06:13:28 +0900

  nspr (2:4.29-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Wed, 21 Oct 2020 07:58:38 +0900

  nspr (2:4.28-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Thu, 03 Sep 2020 10:45:34 +0900

  nspr (2:4.27-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Wed, 29 Jul 2020 16:47:26 +0900

  nspr (2:4.25-1) unstable; urgency=medium

* New upstream release.
* debian/rules: Adapt to changes to runtests.sh.


  
  ### Old Ubuntu Delta ###

  nspr (2:4.35-1.1ubuntu1) oracular; urgency=medium

* Drop explicit -Wl,--as-needed linker flag. It's the default.
* Drop explicit CFLAGS that are checked by configure.
* Also use non-hardening flags from dpkg-buildflags to pick up flags
  like -fno-omit-frame-pointer.

   -- Benjamin Drung   Mon, 22 Jul 2024 11:39:40
  +0200

  nspr (2:4.35-1.1build1) noble; urgency=high

* No change rebuild for 64-bit time_t and frame pointers.

   -- Julian Andres Klode   Mon, 08 Apr 2024
  18:14:31 +0200

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

[Touch-packages] [Bug 2085235] Re: Merge heimdal from Debian unstable for plucky

[Bryce Harrington]

** Summary changed:

- Merge heimdal from Debian unstable for jammy
+ Merge heimdal from Debian unstable for plucky

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

Title:
  Merge heimdal from Debian unstable for plucky

Status in heimdal package in Ubuntu:
  New

Bug description:
  Upstream: tbd
  Debian:   7.8.git20221117.28daf24+dfsg-8
  Ubuntu:   7.8.git20221117.28daf24+dfsg-8ubuntu1


  Debian does new releases regularly, so it's likely there will be newer
  versions available before FF that we can pick up if this merge is done
  later in the cycle.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Jammy Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  heimdal (7.8.git20221117.28daf24+dfsg-8) unstable; urgency=medium

[ Andreas Hasenack ]
* Fix FTBFS with autoconf 2.72. Closes: #1078494.

   -- Brian May   Mon, 12 Aug 2024 10:55:53 +1000

  heimdal (7.8.git20221117.28daf24+dfsg-7) unstable; urgency=medium

* Add include and includedir patch that was accidentally omitted.
* Rename pkg-config to pkgconf in dependancy.

[ Andreas Hasenack ]
* Add support for include and includedir directives to krb5.conf.

   -- Brian May   Thu, 08 Aug 2024 10:42:42 +1000

  heimdal (7.8.git20221117.28daf24+dfsg-6) unstable; urgency=medium

* Fix FTBFS due to not linking with crypt correctly. Applied patch from
  https://github.com/heimdal/heimdal/pull/1085. Closes: #1075064.

[ Andreas Hasenack ]
* Add a kinit DEP8 test which relies on the includedir support.

   -- Brian May   Thu, 25 Jul 2024 16:19:48 +1000

  heimdal (7.8.git20221117.28daf24+dfsg-5) unstable; urgency=medium

* Apply NMU patches. Closes: #1065373.

   -- Brian May   Sat, 09 Mar 2024 11:01:27 +1100

  heimdal (7.8.git20221117.28daf24+dfsg-4.2) unstable; urgency=medium

[ Matthias Klose ]
* Filter-out -Werror=implicit-function-declaration, unconditionally set
  by abi=time64.

   -- Steve Langasek   Fri, 08 Mar 2024 08:21:09
  +

  heimdal (7.8.git20221117.28daf24+dfsg-4.1) unstable; urgency=medium

* Non-maintainer upload.
* Rename libraries for 64-bit time_t transition.  Closes: #1064097

   -- Lukas Märdian   Wed, 28 Feb 2024 08:36:52 +

  heimdal (7.8.git20221117.28daf24+dfsg-4) unstable; urgency=medium

* Always build the rk_strlcat and rk_strlcpy symbols even if included in
  glibc. Closes: #1055316.

   -- Brian May   Wed, 03 Jan 2024 11:43:58 +1100

  heimdal (7.8.git20221117.28daf24+dfsg-3) unstable; urgency=medium

* Fix random 'Ticket expired' and 'Clock skew too great' errors by setting
  kdc_offset correctly. Closes: #1039992.

   -- Brian May   Tue, 04 Jul 2023 10:09:56 +1000

  heimdal (7.8.git20221117.28daf24+dfsg-2) unstable; urgency=medium

* Fix incorrect license of Debian files.
* Fix deprecated dependancies.
* gsskrb5: fix accidental logic inversions (CVE-2022-45142)
  (Closes: #1030849) - change applied from NMU version
  7.8.git20221117.28daf24+dfsg-1.1
* Add ro.po file. Closes: #1031897.

   -- Brian May   Sat, 25 Feb 2023 09:32:57 +1100

  heimdal (7.8.git20221117.28daf24+dfsg-1) unstable; urgency=medium

* New upstream release.

   -- Brian May   Sat, 10 Dec 2022 16:29:20 +1100

  heimdal (7.8.git20221115.a6cf945+dfsg-3) unstable; urgency=medium

* Source-only upload to enable migration to testingi (2nd attempt).

   -- Brian May   Sun, 04 Dec 2022 09:56:06 +1100

  heimdal (7.8.git20221115.a6cf945+dfsg-2) unstable; urgency=medium

* Source-only upload to enable migration to testing.

   -- Brian May   Sun, 04 Dec 2022 09:09:44 +1100

  heimdal (7.8.git20221115.a6cf945+dfsg-1) unstable; urgency=medium

* New upstream version.
* Numerous security fixes (Closes: #1024187).
* asn1: Invalid free in ASN.1 codec (CVE-2022-44640)
* krb5: PAC parse integer overflows (CVE-2022-42898)
* gsskrb5: Use constant-time memcmp() for arcfour unwrap (CVE-2022-3437)
* gsskrb5: Use constant-time memcmp() in unwrap_des3() (CVE-2022-3437)
* gsskrb5: Don't pass NULL pointers to memcpy() in DES unwrap


  ### Old Ubuntu Delta ###

  heimdal (7.8.git20221117.28daf24+dfsg-8ubuntu1) oracular;
  urgency=medium

* Merge from Debian unstable. Remaining changes:
  - d/rules: Disable lto, to regain dep on roken, otherwise
dependencies on amd64 are different than i386 resulting in
different files on amd64 and i386.

   -- Gianfranco Costamagna   Mon, 12 Aug 2024
  14:50:58 +0200

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


-- 
Mailin

[Touch-packages] [Bug 2085260] Re: Merge openldap from Debian unstable for plucky

[Bryce Harrington]

** Summary changed:

- Merge openldap from Debian unstable for jammy
+ Merge openldap from Debian unstable for plucky

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

Title:
  Merge openldap from Debian unstable for plucky

Status in openldap package in Ubuntu:
  New

Bug description:
  Upstream: tbd
  Debian:   2.5.18+dfsg-32.6.8+dfsg-1~exp4
  Ubuntu:   2.6.8+dfsg-1~exp4ubuntu1


  Debian new has 2.6.8+dfsg-1~exp4, which may be available for merge
  soon.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Jammy Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  openldap (2.5.18+dfsg-3) unstable; urgency=medium

* Fix FTBFS on 32-bit architectures. (ITS#10253) (Closes: #1078822)

   -- Ryan Tandy   Wed, 21 Aug 2024 20:38:08 -0700

  openldap (2.5.18+dfsg-2) unstable; urgency=medium

* Apply upstream patch to fix back-perl linking with libperl.
  (ITS#10221, LP: #2072976)
* Add a superficial autopkgtest to ensure back_perl can be loaded.

   -- Ryan Tandy   Sun, 14 Jul 2024 14:37:43 -0700

  openldap (2.5.18+dfsg-1) unstable; urgency=medium

[ Ryan Tandy ]
* New upstream release.
* Drop patch smbk5pwd-implicit-declaration, applied upstream.

[ Sergio Durigan Junior ]
* d/control: B-D on pkgconf instead of pkg-config.

[ Helmut Grohne ]
* Move systemd drop-in to /usr (DEP17). (Closes: #1073059)

   -- Ryan Tandy   Wed, 12 Jun 2024 19:23:12 -0700

  openldap (2.5.17+dfsg-1) unstable; urgency=medium

* New upstream release.
  - fixed slapo-dynlist so it can't be global (ITS#10091) (Closes: #1040382)
* debian/copyright: Exclude doc/guide/admin/guide.html from the upstream
  source, because the tool required to build it from source is not packaged
  in Debian. Fixes a Lintian error (source-is-missing).
* Update Swedish debconf translation. (Closes: #1056955)
  Thanks to Martin Bagge and Anders Jonsson.
* debian/salsa-ci.yml: Enable Salsa CI pipeline.

   -- Ryan Tandy   Fri, 26 Apr 2024 16:09:29 -0700

  openldap (2.5.16+dfsg-2) unstable; urgency=medium

* debian/patches/64-bit-time-t-compat: handle sizeof(time_t) >
  sizeof(long) in format strings.

   -- Steve Langasek   Tue, 12 Mar 2024 06:26:07
  +

  openldap (2.5.16+dfsg-1) unstable; urgency=medium

[ Ryan Tandy ]
* New upstream release.
  - fixed possible null pointer dereferences if strdup fails
(ITS#9904) (Closes: #1036995, CVE-2023-2953)
  - fixed unaligned accesses in LMDB on sparc64
(ITS#9916) (Closes: #1020319)
* Update Turkish debconf translation. (Closes: #1029758)
  Thanks to Atila KOÇ.
* Add Romanian debconf translation. (Closes: #1033177)
  Thanks to Remus-Gabriel Chelu.
* Create an autopkgtest covering basic TLS functionality.
  Thanks to John Scott.
* Drop transitional package slapd-smbk5pwd. (Closes: #1032742)
* Drop dbgsym migration for slapd-dbg.
* Build and install the ppm module in slapd-contrib. (Closes: #1039740)
* Fix implicit declaration of kadm5_s_init_with_password_ctx.
  (Closes: #1065633)

[ Sergio Durigan Junior ]
* d/control: Bump Standards-Version to 4.6.2; no changes needed.
* d/control: Bump debhelper-compat to 13.
* d/control: Drop lsb-base from slapd's Depends.
* Enable SASL/GSSAPI tests.
  Thanks to Andreas Hasenack 

   -- Ryan Tandy   Fri, 08 Mar 2024 21:46:26 -0800

  openldap (2.5.13+dfsg-5) unstable; urgency=medium

* Fix sha2-contrib autopkgtest failure. Call slappasswd using its full path.
  (Closes: #1030814)
* Disable flaky test test069-delta-multiprovider-starttls.

   -- Ryan Tandy   Tue, 07 Feb 2023 17:56:12 -0800

  openldap (2.5.13+dfsg-4) unstable; urgency=medium

[ Andreas Hasenack ]
* d/rules: Fix passwd/sha2 build (Closes: #1030716, LP: #2000817)
* d/t/sha2-contrib: add test for sha2 module

   -- Ryan Tandy   Mon, 06 Feb 2023 19:21:05 -0800

  openldap (2.5.13+dfsg-3) unstable; urgency=medium

[ Ryan Tandy ]
* Disable flaky test test063-delta-multiprovider. Mitigates #1010608.

[ Gioele Barabucci ]
* slapd.scripts-common: Avoid double-UTF8-encoding org name (Closes: 
#1016185)


  ### Old Ubuntu Delta ###

  openldap (2.6.8+dfsg-1~exp4ubuntu1) oracular; urgency=medium

* Merge with Debian unstable (LP: #2078261). Remaining changes:
  - Enable AppArmor support:
+ d/apparmor-profile: add AppArmor profile
+ d/rules: use dh_apparmor
+ d/control: Build-Depends on dh-apparmor
+ d/slapd.README.Debian: add note about AppArmor
  - Enable ufw support:
+ d/control: s

[Touch-packages] [Bug 2028282] Re: SSH pubkey authetication fails when GSSAPI enabled

[Bug Watch Updater]

** Changed in: openssh (Debian)
   Status: Fix Committed => Fix Released

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

Title:
  SSH pubkey authetication fails when GSSAPI enabled

Status in openssh package in Ubuntu:
  Triaged
Status in openssh package in Debian:
  Fix Released

Bug description:
  Since the upgrade from Ubuntu 20.04 to 22.04 the SSH login via a SSH
  pubkey to our servers fails, while password and kerberos are still
  working.

  $ssh user@server
  sign_and_send_pubkey: internal error: initial hostkey not recorded 

  This seem related to the bugreport at openssh:
  https://bugzilla.mindrot.org/show_bug.cgi?id=3406

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssh-server 1:8.9p1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
  Uname: Linux 5.15.0-76-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Thu Jul 20 17:25:01 2023
  InstallationDate: Installed on 2020-08-24 (1060 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: openssh
  UpgradeStatus: Upgraded to jammy on 2023-07-20 (0 days ago)

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

[Timo Aaltonen]

** Description changed:

  [Impact]
  The graphics HWE stack from oracular needs to be backported for 24.04.2
  
  libdrm
  - build-dep of mesa
  
  spirv-llvm-translator
  - build-dep of llvm
  
  llvm-toolchain-19
  - new source in noble
  - build-dep of mesa
  - required for new AMD platforms
  - needs two uploads:
    * 1st stage bootstrap build
    * 2nd stage after spirv-llvm-translator has built against 1st stage
  
  mesa
  - new major release (24.2.x)
  - new HW support, Lunar Lake, Battlemage..
  
+ meson
+ - needed by mesa
+ - tests disabled because four irrelevant ones fail for some reason, doesn't
+   affect the mesa backport
+ 
  [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 driver 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/ADL/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 noble, we'd already know 
if there are serious issues.

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

Title:
  Backport packages for 24.04.2 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-19 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in spirv-llvm-translator-19 package in Ubuntu:
  Invalid
Status in libdrm source package in Noble:
  New
Status in llvm-toolchain-19 source package in Noble:
  Confirmed
Status in mesa source package in Noble:
  Confirmed
Status in spirv-llvm-translator-19 source package in Noble:
  New

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

  libdrm
  - build-dep of mesa

  spirv-llvm-translator
  - build-dep of llvm

  llvm-toolchain-19
  - new source in noble
  - build-dep of mesa
  - required for new AMD platforms
  - needs two uploads:
    * 1st stage bootstrap build
    * 2nd stage after spirv-llvm-translator has built against 1st stage

  mesa
  - new major release (24.2.x)
  - new HW support, Lunar Lake, Battlemage..

  meson
  - needed by mesa
  - tests disabled because four irrelevant ones fail for some reason, doesn't
affect the mesa backport

  [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 driver 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/ADL/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 noble, we'd already know 
if there are serious issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/2083020/+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 2085244] Re: Merge libseccomp from Debian unstable for plucky

[Bryce Harrington]

** Summary changed:

- Merge libseccomp from Debian unstable for jammy
+ Merge libseccomp from Debian unstable for plucky

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

Title:
  Merge libseccomp from Debian unstable for plucky

Status in libseccomp package in Ubuntu:
  Incomplete

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   2.5.5-1
  Ubuntu:   2.5.5-1ubuntu4

  
  foundations team has maintained this package's merge in the past.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Jammy Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### Old Ubuntu Delta ###

  libseccomp (2.5.5-1ubuntu4) oracular-proposed; urgency=medium

* LP: #2076340: No-change rebuild to pick up changed build flags on
  ppc64el and s390x.

   -- Matthias Klose   Thu, 08 Aug 2024 14:55:38 +0200

  libseccomp (2.5.5-1ubuntu3) noble; urgency=medium

* No-change rebuild for CVE-2024-3094

   -- Steve Langasek   Sun, 31 Mar 2024
  07:58:07 +

  libseccomp (2.5.5-1ubuntu2) noble; urgency=medium

* No-change rebuild to build with python3.12 only.

   -- Matthias Klose   Sat, 16 Mar 2024 23:14:35 +0100

  libseccomp (2.5.5-1ubuntu1) noble; urgency=medium

* Merge from Debian unstable; remaining changes:
  - Add autopkgtests
* Added changes:
  - d/t/test-filter: generate syscalls list from src/syscalls.csv rather 
than
shipping a static list to ensure all get tested via autopkgtests
* Dropped changes:
  - d/t/data/all-5.16-rc1.filter: remove static syscall list

   -- Alex Murray   Fri, 02 Feb 2024 13:30:43
  +1030

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/2085244/+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 2064408] Re: Merge init-system-helpers from Debian unstable for oracular

[Bryce Harrington]

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

** This bug has been marked a duplicate of bug 2085236
   Merge init-system-helpers from Debian unstable for plucky

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

Title:
  Merge init-system-helpers from Debian unstable for oracular

Status in init-system-helpers package in Ubuntu:
  Incomplete

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1.66
  Ubuntu:   1.66ubuntu1

  
  foundations team has maintained this package's merge in the past.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Oracular Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  init-system-helpers (1.66) unstable; urgency=medium

[ Samuel Thibault ]
* Add hurd-amd64 case.

[ Gioele Barabucci ]
* d/init.lintian-overrides: Silence warning about 'Important' field
  `Important: yes` instructs APT to warn the user before removing this
  package.

[ Johannes Schauer Marin Rodrigues ]
* script/update-rc.d: DPKG_ROOT support for sysvinit

[ Ansgar ]
* Add 'Protected: yes' to package 'init' The 'Protected' field does the
  same as 'Important' already did in apt, but is also understood by dpkg
  (since dpkg 1.20.1).

[ Luca Boccassi ]
* Bump Standards-Version to 4.6.2, no changes
* Override Lintian warning for Protected: yes
* deb-systemd-invoke: support reload/reexec. This is useful for the
  --user case, to provide a shortcut that loops over all active user
  sessions over D-Bus.
* deb-systemd-invoke: support --no-dbus for reload/reexec. Provide
  common implementation for SIGHUP/SIGRTMIN+25 to reload/reexec the
  system or user instances.

   -- Luca Boccassi   Sun, 26 Nov 2023 20:42:28 +

  init-system-helpers (1.65.2) unstable; urgency=low

* Undo yet another hostile and baseless NMU.

   -- Luca Boccassi   Sun, 18 Sep 2022 02:53:19 +0100

  init-system-helpers (1.65.1) unstable; urgency=low

* Undo hostile NMU.

   -- Luca Boccassi   Sun, 18 Sep 2022 01:53:32 +0100

  init-system-helpers (1.65) unstable; urgency=low

* Upload to unstable.

   -- Luca Boccassi   Sat, 17 Sep 2022 21:11:07 +0100

  init-system-helpers (1.65~exp2) experimental; urgency=medium

* fakechroot tests: skip on architectures where it is not available

   -- Luca Boccassi   Thu, 15 Sep 2022 21:14:08 +0100

  init-system-helpers (1.65~exp1) experimental; urgency=medium

[ Luca Boccassi ]
* Drop outdated conflict with file-rc
* Add myself to Uploaders
* d/rules: use execute_after instead of override
* Add a dependency on usrmerge | usr-is-merged to complete the
  transition. As per ctte decision and discussion at:
  https://lists.debian.org/debian-ctte/2022/07/msg00019.html
  https://lists.debian.org/debian-ctte/2022/07/msg00061.html
  https://lists.debian.org/debian-ctte/2022/08/msg6.html

[ Victor Westerhuis ]
* Make deb-systemd-helper work on template units with DefaultInstance.
  DefaultInstance only influences the meaning of WantedBy/RequiredBy.
  Alias and Also are not impacted. This patch does not enable changing
  template instantiations, so `deb-systemd-helper enable
  getty@tty2.service` will still fail.
* Fix tests depending on ordering of lines in state file. The previous
  commit changes the order in which lines are written to the state file.
  Because correctness does not depend on the order in which the state
  file is written, ignore the order in the test.

   -- Luca Boccassi   Sat, 10 Sep 2022 13:27:16 +0100

  init-system-helpers (1.64) unstable; urgency=medium

* Team upload.
* d-s-h: break infinite recursion on symlinks. (Closes: #1014119)
* Bump Standards-Version to 4.6.1, no changes
* Update date ranges in d/copyright

   -- Luca Boccassi   Mon, 04 Jul 2022 11:19:08 +0100

  init-system-helpers (1.63) unstable; urgency=medium

[ Debian Janitor ]
* Remove constraints unnecessary since buster
  * init-system-helpers: Drop versioned constraint on perl-base in Depends.
  * init: Drop versioned constraint on init-system-helpers in Depends.

[ Johannes Schauer Marin Rodrigues ]
* t/helpers.pm: use installed version of deb-systemd-helper if
  TEST_INSTALLED is set
* add DPKG_ROOT support (Closes: #983421)


  
  ### Old Ubuntu Delta ###

  init-system-helpers (1.66ubuntu1) noble; urgency=medium

* Merge from Debian unstable.  Remaining changes:
  - Drop dependency on usrmerge.

   -- Steve Langasek   Tue, 05 Dec 2023
  2

[Touch-packages] [Bug 2064420] Re: Merge libseccomp from Debian unstable for oracular

[Bryce Harrington]

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

** This bug has been marked a duplicate of bug 2085244
   Merge libseccomp from Debian unstable for plucky

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

Title:
  Merge libseccomp from Debian unstable for oracular

Status in libseccomp package in Ubuntu:
  Incomplete

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   2.5.5-1
  Ubuntu:   2.5.5-1ubuntu3

  
  NOT SERVER TEAM has maintained this package's merge in the past.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Oracular Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### Old Ubuntu Delta ###

  libseccomp (2.5.5-1ubuntu3) noble; urgency=medium

* No-change rebuild for CVE-2024-3094

   -- Steve Langasek   Sun, 31 Mar 2024
  07:58:07 +

  libseccomp (2.5.5-1ubuntu2) noble; urgency=medium

* No-change rebuild to build with python3.12 only.

   -- Matthias Klose   Sat, 16 Mar 2024 23:14:35 +0100

  libseccomp (2.5.5-1ubuntu1) noble; urgency=medium

* Merge from Debian unstable; remaining changes:
  - Add autopkgtests
* Added changes:
  - d/t/test-filter: generate syscalls list from src/syscalls.csv rather 
than
shipping a static list to ensure all get tested via autopkgtests
* Dropped changes:
  - d/t/data/all-5.16-rc1.filter: remove static syscall list

   -- Alex Murray   Fri, 02 Feb 2024 13:30:43
  +1030

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/2064420/+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 2085340] Re: Plenty of amdgpu backtraces post resume

[Julian Andres Klode]

Attaching the Journal, the initial crash can be seen at 12:31:54, lots
going on there, but nothing root-causing this.

** Attachment added: "Journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085340/+attachment/5830742/+files/Journal.txt

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

Title:
  Plenty of amdgpu backtraces post resume

Status in linux package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  This is a very weird case: The GNOME session crashed 3 times today,
  the last time, it went to gdm, but then gdm did not recognize it was
  docked and suspended. I think the kernel needed two attempts to
  resume, it got suspended again after the first one; and it produced a
  whole bunch of back traces in dmesg.

  
  [ 3300.659129] WARNING: CPU: 1 PID: 65823 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315 
dal_gpio_service_open+0x1b6/0x270 [amdgpu]
  [ 3410.146130] WARNING: CPU: 4 PID: 73742 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:221 
dmub_psr_enable+0x102/0x110 [amdgpu]

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: linux-image-6.11.0-9-generic 6.11.0-9.9
  ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
  Uname: Linux 6.11.0-9-generic x86_64
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Tue Oct 22 12:45:20 2024
  InstallationDate: Installed on 2022-11-26 (696 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: LENOVO 21CF004PGE
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-9-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 
zswap.zpool=zsmalloc vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.11.0-9-generic N/A
   linux-backports-modules-6.11.0-9-generic  N/A
   linux-firmware20240913.gita34e7a5f-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2024
  dmi.bios.release: 1.53
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET77W (1.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085340/+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 2080216] Re: sshd cannot bind to IPv4 interfaces

[Vasya Pupkin]

Any estimate when the fixed version will be available in Ubuntu 24.04
without -proposal repos?

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

Title:
  sshd cannot bind to IPv4 interfaces

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Noble:
  In Progress

Bug description:
  [Impact]

  The default listening sockets for sshd are different depending on
  whether socket activation is used or not, even when
  /etc/ssh/sshd_config is the default. E.g.:

  # Socket-activated

  root@n2:~# systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/usr/lib/systemd/system/ssh.socket; enabled; preset: 
enabled)
   Active: active (listening) since Tue 2024-10-01 20:36:15 UTC; 12min ago
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
   CGroup: /system.slice/ssh.socket

  Oct 01 20:36:15 n2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell 
server socket.
  root@n2:~# lsof -i :22
  COMMAND PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
  systemd   1 root   47u  IPv6 2781411  0t0  TCP *:ssh (LISTEN)

  # Non-socket-activated

  root@n2:~# systemctl disable --now ssh.socket
  Removed "/etc/systemd/system/ssh.service.requires/ssh.socket".
  Removed "/etc/systemd/system/sockets.target.wants/ssh.socket".
  root@n2:~# ln -s /dev/null 
/etc/systemd/system-generators/sshd-socket-generator
  root@n2:~# systemctl enable --now ssh.service
  Synchronizing state of ssh.service with SysV service script with 
/usr/lib/systemd/systemd-sysv-install.
  Executing: /usr/lib/systemd/systemd-sysv-install enable ssh
  Created symlink /etc/systemd/system/sshd.service → 
/usr/lib/systemd/system/ssh.service.
  Created symlink /etc/systemd/system/multi-user.target.wants/ssh.service → 
/usr/lib/systemd/system/ssh.service.
  root@n2:~# lsof -i :22
  COMMAND PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
  sshd798 root3u  IPv4 2793622  0t0  TCP *:ssh (LISTEN)
  sshd798 root4u  IPv6 2793624  0t0  TCP *:ssh (LISTEN)

  By default, we have net.ipv6.bindv6only=0 sysctl, and
  BindIPv6Only=both on ssh.socket, which means usually users can connect
  over IPv4 regardless. However, the fact remains that the resulting
  listening sockets are different in these two cases, and socket-
  activated ssh does not accurately reflect the settings in
  /etc/ssh/sshd_config.

  [Test Plan]

  1. Check that on a noble system, without custom sshd_config, sshd is
  listening on both IPv4 and IPv6 on port 22:

  $ lsof -i :22

  2. Check that setting AddressFamily to e.g. inet results in only an
  IPv4 socket:

  $ echo "AddressFamily inet" >> /etc/ssh/sshd_config.d/custom.conf
  $ systemctl daemon-reload
  $ systemctl restart ssh.socket
  $ lsof -i :22

  There should only be one listener now.

  3. Check the same thing with inet6, and a custom port for good
  measure:

  $ echo "AddressFamily inet6" >> /etc/ssh/sshd_config.d/custom.conf
  $ echo "Port 1234" >> /etc/ssh/sshd_config.d/custom.conf
  $ systemctl daemon-reload
  $ systemctl restart ssh.socket
  $ lsof -i :1234

  4. The new tests in debian/tests/sshd-socket-generator should all pass
  in autopkgtest.

  [Where problems could occur]

  The fix requires new default settings in the [Socket] section of
  ssh.socket, and handling for new defaults in sshd-socket-generator. It
  would be more likely to see problems with the generator as opposed to
  the changes in ssh.socket. However, new subtests were added to
  debian/tests/sshd-socket-generator to help avoid this.

  [Original Description]

  After upgrading from 22.04 to 24.04 I noticed that my sshd only
  listening on IPv6 interface (::), while previously it was listening
  both IPv4 (0.0.0.0) and IPv6 (::). I tried to explicitly specify
  ListenAddress 0.0.0.0 (assuming it would bind to IPv4 only) but after
  restart sshd was still listening on IPv6 only.

  This problem affects other packages as well, for example, openvpn.

  Rebuilding applications from sources seems to fix the issue.

  Setting net.ipv6.bindv6only=0 also helps, but that's not a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openssh-server 1:9.6p1-3ubuntu13.5
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Sep 10 16:45:54 2024
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=screen.xterm-256color
  SourcePackage: openssh
  UpgradeStatus: Upgraded to noble on 2024-09-10 (0 days ago)

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


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

[Touch-packages] [Bug 2085340] [NEW] Plenty of amdgpu backtraces post resume

[Julian Andres Klode]

Public bug reported:

This is a very weird case: The GNOME session crashed 3 times today, the
last time, it went to gdm, but then gdm did not recognize it was docked
and suspended. I think the kernel needed two attempts to resume, it got
suspended again after the first one; and it produced a whole bunch of
back traces in dmesg.


[ 3300.659129] WARNING: CPU: 1 PID: 65823 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315 
dal_gpio_service_open+0x1b6/0x270 [amdgpu]
[ 3410.146130] WARNING: CPU: 4 PID: 73742 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:221 
dmub_psr_enable+0x102/0x110 [amdgpu]

ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: linux-image-6.11.0-9-generic 6.11.0-9.9
ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
Uname: Linux 6.11.0-9-generic x86_64
ApportVersion: 2.30.0-0ubuntu4
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME
Date: Tue Oct 22 12:45:20 2024
InstallationDate: Installed on 2022-11-26 (696 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
MachineType: LENOVO 21CF004PGE
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-9-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 
zswap.zpool=zsmalloc vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-6.11.0-9-generic N/A
 linux-backports-modules-6.11.0-9-generic  N/A
 linux-firmware20240913.gita34e7a5f-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/29/2024
dmi.bios.release: 1.53
dmi.bios.vendor: LENOVO
dmi.bios.version: R23ET77W (1.53 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21CF004PGE
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T76538 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.32
dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
dmi.product.family: ThinkPad T14 Gen 3
dmi.product.name: 21CF004PGE
dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
dmi.product.version: ThinkPad T14 Gen 3
dmi.sys.vendor: LENOVO

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

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


** Tags: amd64 apport-bug oracular third-party-packages wayland-session

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

** Description changed:

  This is a very weird case: The GNOME session crashed 3 times today, the
  last time, it went to gdm, but then gdm did not recognize it was docked
  and suspended. I think the kernel needed two attempts to resume, it got
  suspended again after the first one; and it produced a whole bunch of
  back traces in dmesg.
+ 
+ 
+ [ 3300.659129] WARNING: CPU: 1 PID: 65823 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315 
dal_gpio_service_open+0x1b6/0x270 [amdgpu]
+ [ 3410.146130] WARNING: CPU: 4 PID: 73742 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:221 
dmub_psr_enable+0x102/0x110 [amdgpu]
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: linux-image-6.11.0-9-generic 6.11.0-9.9
  ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
  Uname: Linux 6.11.0-9-generic x86_64
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Tue Oct 22 12:45:20 2024
  InstallationDate: Installed on 2022-11-26 (696 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: LENOVO 21CF004PGE
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-9-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 
zswap.zpool=zsmalloc vt.handoff=7
  RelatedPackageVersions:
-  linux-restricted-modules-6.11.0-9-generic N/A
-  linux-backports-modules-6.11.0-9-generic  N/A
-  linux-firmware20240913.gita34e7a5f-0ubuntu2
+  linux-restricted-modules-6.11.0-9-generic N/A
+  linux-backports-modules-6.11.0-9-generic  N/A
+  linux-firmware20240913.gita34e7a5f-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2024
  dmi.bios.release: 1.53
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET77W (1.

[Touch-packages] [Bug 2085395] [NEW] Clam TK won't update

[David Oxland]

Public bug reported:

ClamTK will not update

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
Uname: Linux 6.8.0-47-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 22 18:34:16 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation Iris Plus Graphics 650 [8086:5927] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Intel Corporation Iris Plus Graphics 650 [8086:2068]
InstallationDate: Installed on 2024-10-14 (9 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 046d:08d7 Logitech, Inc. QuickCam Communicate STX
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Intel Corporation NUC7i7BNH
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic 
root=UUID=0c9d3a4a-dc89-4e34-b66b-b47faef57367 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2017
dmi.bios.release: 5.6
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BNKBL357.86A.0052.2017.0918.1346
dmi.board.name: NUC7i7BNB
dmi.board.vendor: Intel Corporation
dmi.board.version: J31145-307
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2
dmi.ec.firmware.release: 8.9
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0052.2017.0918.1346:bd09/18/2017:br5.6:efr8.9:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2:sku:
dmi.product.family: Intel NUC
dmi.product.name: NUC7i7BNH
dmi.product.version: J31153-308
dmi.sys.vendor: Intel Corporation
mtime.conffile..etc.init.d.apport: 2024-07-22T07:59:07
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
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 noble performance third-party-packages ubuntu 
wayland-session

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

Title:
  Clam TK won't update

Status in xorg package in Ubuntu:
  New

Bug description:
  ClamTK will not update

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
  Uname: Linux 6.8.0-47-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 22 18:34:16 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Iris Plus Graphics 650 [8086:5927] (rev 06) (prog-if 00 
[VGA controller])
 Subsystem: Intel Corporation Iris Plus Graphics 650 [8086:2068]
  InstallationDate: Installed on 2024-10-14 (9 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 046d:08d7 Logitech, Inc. QuickCam Communicate STX
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bluetooth wireless interface
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: Intel Corporation NUC7i7BNH
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-47-generic 
root=UUID=0c9d3a4a-dc89-4e34-b66b-b47faef57367 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/18/2017
  dmi.bios.release: 5.6
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0052.2017.0918.1346
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-307
  dmi.chassis.type: 3
  dmi.chassis.

[Touch-packages] [Bug 2071815] Re: Investigate ASLR re-randomization being disabled for children

[Chris Halse Rogers]

Hello Marc, or anyone else affected,

Accepted openssh into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:9.6p1-3ubuntu13.6 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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: openssh (Ubuntu Noble)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  Investigate ASLR re-randomization being disabled for children

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  The systemd-socket-activation.patch patch has an Ubuntu delta to fix
  bug 2011458, but this results in ASLR not being re-randomized for
  children because the patch delta does "rexec_flag = 0;".

  This was discovered as part of the CVE-2024-6387 discovery by Qualys,
  and is mentioned in the disclosure itself:

  Side note: we discovered that Ubuntu 24.04 does not re-randomize the
  ASLR of its sshd children (it is randomized only once, at boot time); we
  tracked this down to the patch below, which turns off sshd's rexec_flag.
  This is generally a bad idea, but in the particular case of this signal
  handler race condition, it prevents sshd from being exploitable: the
  syslog() inside the SIGALRM handler does not call any of the malloc
  functions, because it is never the very first call to syslog().

  This is also mentioned in the release notes of OpenSSH 9.8:

  Exploitation on non-glibc systems is conceivable but has not been
  examined. Systems that lack ASLR or users of downstream Linux
  distributions that have modified OpenSSH to disable per-connection
  ASLR re-randomisation (yes - this is a thing, no - we don't
  understand why) may potentially have an easier path to exploitation.

  We should investigate why that was needed, and if an alternative way
  of fixing the original bug can be done.

  [Test Plan]

  We just want to test that when a connection is accepted by sshd, the
  child process re-execs. There is a log message at the debug level from
  sshd when this happens.

  1. Enable debug-level logging in sshd:

  $ echo "LogLevel DEBUG" >> /etc/ssh/sshd_config.d/log-level.conf

  2. Watch the logs:

  $ journalctl -t sshd -b -f

  3. From another host, connect to the test machine:

  $ ssh @

  4. On the test machine, among other messages, there should be a
  message noting the start of the re-exec, e.g.:

  sshd[2212]: debug1: rexec start in 6 out 6 newsock 6 pipe 8 sock 9

  [Where problems could occur]

  Through the iterations of d/p/systemd-socket-activation.patch, there
  have been issues related to the re-exec behavior, and how the listen
  fds passed by systemd are handled. See [1][2] for examples. This patch
  hopes to finally resolve these issues.

  However, as was the case with previous bugs in this area, problems
  would most likely be related to incorrectly closing, or not closing,
  socket fds in sshd.

  [1] https://bugs.launchpad.net/bugs/2020474
  [2] https://bugs.launchpad.net/bugs/2011458

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2071815/+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 2069041] Re: Changing Port in sshd_config requires calling systemctl daemon-reload

[Chris Halse Rogers]

Hello teutat3s, or anyone else affected,

Accepted openssh into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:9.6p1-3ubuntu13.6 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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: openssh (Ubuntu Noble)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  Changing Port in sshd_config requires calling systemctl daemon-reload

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  There is currently no comment in the default /etc/ssh/sshd_config
  explaining that a systemctl daemon-reload is needed for changes to
  Port etc. to take effect when systemd socket activation is used (the
  default on Ubuntu).

  Users may change e.g. Port in  /etc/ssh/sshd_config and expect
  systemctl restart ssh.service to reflect the change, but this will not
  work.

  [Test Plan]

  1. The proposed fix here is to improve the documentation by adding a
  comment above the default Port setting in /etc/ssh/sshd_config. Hence,
  the test is to simply install openssh-server from noble-proposed, and
  verify that the comment is there.

  2. Because the patch changes the default sshd_config, and
  debian/openssh-server.ucf-md5sum needs to be updated when this
  happens, an upgrade from noble to oracular should be done after
  installing openssh-server from noble-proposed. If a debconf prompt is
  shown, then a mistake was made in recording the checksums. Otherwise,
  they are correct.

  [Where problems could occur]

  There is low technical risk, but we should be sure that the
  documentation is clear and improves the experience of users. It could
  be harmful if the documentation accidentally makes things worse, or is
  just confusing.

  Also, a packaging quirk of openssh-server is that checksums of the
  patched sshd_config (along with certain settings tweaked) need to be
  recorded in debian/openssh-server.ucf-md5sum to avoid unnecessary
  debconf prompts on upgrades. I have updated those checksums, but if
  they are incorrent, then in future upgrades users might see an
  unnecessary debconf prompt about /etc/ssh/sshd_config.

  [Original Description]

  Changing the Port directive in sshd_config and restarting ssh.service
  is without effect, sshd keeps listening to port 22.

  Also mentioned in https://discourse.ubuntu.com/t/sshd-now-uses-socket-
  based-activation-ubuntu-22-10-and-later/30189/32

  Steps to reproduce:
  1. Install Ubuntu 24.04 LTS
  2. Change Port directive in /etc/ssh/sshd_config to Port 2233
  3. Restart ssh.service
  4. Observe sshd still listening to port 22

  Expected behaviour: sshd changes port to 2233

  Actual behaviour: sshd keeps listening to port 22

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2069041/+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 2076023] Re: Failed to apply 'Match' directive in sshd_config with sshd-socket-generator

[Chris Halse Rogers]

Hello Enorize, or anyone else affected,

Accepted openssh into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:9.6p1-3ubuntu13.6 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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: openssh (Ubuntu Noble)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  Failed to apply 'Match' directive in sshd_config with sshd-socket-
  generator

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Noble:
  Fix Committed
Status in openssh source package in Oracular:
  Fix Released

Bug description:
  [Impact]

  When users have a Match section in their sshd config, their
  configuration cannot be parsed by the sshd-socket-generator (because
  there is no connection, hence no connection spec to be matched), and
  the generator fails. This means no custom config is applied at all.

  [Test Plan]

  1. On a noble system with sshd installed, create a drop-in config with
  a Match directive, and run the generator locally:

  $ cat > /etc/ssh/sshd_config.d/custom.conf << EOF
  Port 1234
  Match LocalPort 22
  PasswordAuthentication no
  EOF
  $ /lib/systemd/system-generators/sshd-socket-generator .
  'Match LocalPort' in configuration but 'lport' not in connection test 
specification.

  On an affected system, the above error will be shown. On a patched
  system, the generator will succeed, and ./ssh.socket.d/addresses.conf
  will reflect the Port 1234 option.

  2. A new subtest was added to debian/tests/sshd-socket-generator,
  test_match_port. It does the same as the above, and should pass in
  autopkgtest.

  [Where problems could occur]

  This patch simply removes the code from sshd-socket-generator that
  tries to parse the match config. If problems did occur, it would be
  related to the generator again. Specifically, it would likely be
  related to missing/unparsed options.

  [Original Description]

  When using the Match statement in sshd_config or sshd_config.d/*.conf
  with socket activation(not classic method), sshd does not start as
  expected.

  Environment:

  Ubuntu: Ubuntu 24.04 LTS
  OpenSSH Server: 1:9.6p1-3ubuntu13.4

  Steps to Reproduce:

  /etc/ssh/sshd_config
  ```
  Include /etc/ssh/sshd_config.d/*.conf
  Port 22
  Port 2
  KbdInteractiveAuthentication no
  UsePAM yes
  X11Forwarding yes
  PrintMotd no
  AcceptEnv LANG LC_*
  Subsystem sftp/usr/lib/openssh/sftp-server
  Match LocalPort 2
  PasswordAuthentication no
  PubkeyAuthentication yes
  ```

  command:

  sudo systemctl daemon-reload && sudo systemctl restart ssh.socket

  Expected Behavior:

  sshd should listen on both ports 22 and 2.
  When connecting via port 2, password login should not be allowed and only 
public key authentication should be permitted.

  Actual Behavior:

  sshd only listens on port 22 and not on port 2. The configuration
  is not correctly applied.

  After daemon-reload, the output from journalctl is as follows:

  $ sudo journalctl -t (sd-exec-
  Aug 04 12:47:36 ults (sd-exec-[479259]: 
/usr/lib/systemd/system-generators/sshd-socket-generator failed with exit 
status 255.

  Additional Information:

  1.Using sshd -T -C to test the configuration produces the following result:
  $ sudo sshd -T -C lport=22 | grep passwordauthentication
  passwordauthentication yes

  $ sudo sshd -T -C lport=2 | grep passwordauthentication
  passwordauthentication no

  2.The output when manually running 
/usr/lib/systemd/system-generators/sshd-socket-generator is:
  $ sudo /usr/lib/systemd/system-generators/sshd-socket-generator ./
  'Match LocalPort' in configuration but 'lport' not in connection test 
specification.

  3.I have test some

[Touch-packages] [Bug 2080216] Re: sshd cannot bind to IPv4 interfaces

[Chris Halse Rogers]

Hello Vasya, or anyone else affected,

Accepted openssh into noble-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:9.6p1-3ubuntu13.6 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-
noble to verification-done-noble. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-noble. 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: openssh (Ubuntu Noble)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-noble

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

Title:
  sshd cannot bind to IPv4 interfaces

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Noble:
  Fix Committed

Bug description:
  [Impact]

  The default listening sockets for sshd are different depending on
  whether socket activation is used or not, even when
  /etc/ssh/sshd_config is the default. E.g.:

  # Socket-activated

  root@n2:~# systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/usr/lib/systemd/system/ssh.socket; enabled; preset: 
enabled)
   Active: active (listening) since Tue 2024-10-01 20:36:15 UTC; 12min ago
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
   CGroup: /system.slice/ssh.socket

  Oct 01 20:36:15 n2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell 
server socket.
  root@n2:~# lsof -i :22
  COMMAND PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
  systemd   1 root   47u  IPv6 2781411  0t0  TCP *:ssh (LISTEN)

  # Non-socket-activated

  root@n2:~# systemctl disable --now ssh.socket
  Removed "/etc/systemd/system/ssh.service.requires/ssh.socket".
  Removed "/etc/systemd/system/sockets.target.wants/ssh.socket".
  root@n2:~# ln -s /dev/null 
/etc/systemd/system-generators/sshd-socket-generator
  root@n2:~# systemctl enable --now ssh.service
  Synchronizing state of ssh.service with SysV service script with 
/usr/lib/systemd/systemd-sysv-install.
  Executing: /usr/lib/systemd/systemd-sysv-install enable ssh
  Created symlink /etc/systemd/system/sshd.service → 
/usr/lib/systemd/system/ssh.service.
  Created symlink /etc/systemd/system/multi-user.target.wants/ssh.service → 
/usr/lib/systemd/system/ssh.service.
  root@n2:~# lsof -i :22
  COMMAND PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
  sshd798 root3u  IPv4 2793622  0t0  TCP *:ssh (LISTEN)
  sshd798 root4u  IPv6 2793624  0t0  TCP *:ssh (LISTEN)

  By default, we have net.ipv6.bindv6only=0 sysctl, and
  BindIPv6Only=both on ssh.socket, which means usually users can connect
  over IPv4 regardless. However, the fact remains that the resulting
  listening sockets are different in these two cases, and socket-
  activated ssh does not accurately reflect the settings in
  /etc/ssh/sshd_config.

  [Test Plan]

  1. Check that on a noble system, without custom sshd_config, sshd is
  listening on both IPv4 and IPv6 on port 22:

  $ lsof -i :22

  2. Check that setting AddressFamily to e.g. inet results in only an
  IPv4 socket:

  $ echo "AddressFamily inet" >> /etc/ssh/sshd_config.d/custom.conf
  $ systemctl daemon-reload
  $ systemctl restart ssh.socket
  $ lsof -i :22

  There should only be one listener now.

  3. Check the same thing with inet6, and a custom port for good
  measure:

  $ echo "AddressFamily inet6" >> /etc/ssh/sshd_config.d/custom.conf
  $ echo "Port 1234" >> /etc/ssh/sshd_config.d/custom.conf
  $ systemctl daemon-reload
  $ systemctl restart ssh.socket
  $ lsof -i :1234

  4. The new tests in debian/tests/sshd-socket-generator should all pass
  in autopkgtest.

  [Where problems could occur]

  The fix requires new default settings in the [Socket] section of
  ssh.socket, and handling for new defaults in sshd-socket-generator. It
  would be more likely to see problems with the generator as opposed to
  the changes in ssh.socket. However, new subtests were added to
  debian/tests/sshd-socket-generator to

[Touch-packages] [Bug 2085404] [NEW] No display after booting

[何思亮]

Public bug reported:

[Impact]

No display is shown after booting the machine.

[Reproduce]

1. connect a monitor to the machine and boot it.
2. ssh into the machine and check the display using the following commands:
$ export DISPLAY=":0.0"
$ xrandr

[Fail rate]

5/5 (100% failure rate)

[Expected result]

Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384
DP-1 disconnected primary (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
DP-3 disconnected (normal left inverted right x axis y axis)
HDMI-3 disconnected (normal left inverted right x axis y axis)

[Actual result]

Authorization required, but no authorization protocol specified

Can't open display :0.0

[Additional information]

https://certification.canonical.com/hardware/201912-27623/
https://certification.canonical.com/hardware/202005-27944/

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.8.12
Uname: Linux 6.8.0-48-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
BootLog:
 
CasperMD5CheckResult: pass
CloudArchitecture: x86_64
CloudID: maas
CloudName: maas
CloudPlatform: maas
CloudSubPlatform: seed-dir (http://10.102.160.2:5248/MAAS/metadata/)
Date: Wed Oct 23 14:10:39 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
DkmsStatus: fwts-efi-runtime-dkms/24.09.00: added
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc8] (prog-if 00 
[VGA controller])
   Subsystem: Dell CometLake-S GT2 [UHD Graphics 630] [1028:09aa]
InstallationDate: Installed on 2024-05-31 (145 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. KB212-B Quiet Key Keyboard
 Bus 001 Device 003: ID 0781:5530 SanDisk Corp. Cruzer
 Bus 001 Device 004: ID 0cf3:e007 Qualcomm Atheros Communications 
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: Dell Inc. Precision 3440
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-48-generic 
root=UUID=696f0fb9-b9c8-410a-abed-8efe16d0560a ro
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/31/2020
dmi.bios.release: 1.0
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.0
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.0:bd03/31/2020:br1.0:svnDellInc.:pnPrecision3440:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct3:cvr:sku09AA:
dmi.product.family: Precision
dmi.product.name: Precision 3440
dmi.product.sku: 09AA
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.9-0ubuntu0.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
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 corruption noble ubuntu

** Attachment added: "201912_27623_journal_log.txt"
   
https://bugs.launchpad.net/bugs/2085404/+attachment/5831009/+files/201912_27623_journal_log.txt

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

Title:
  No display after booting

Status in xorg package in Ubuntu:
  New

Bug description:
  [Impact]

  No display is shown after booting the machine.

  [Reproduce]

  1. connect a monitor to the machine and boot it.
  2. ssh into the machine and check the display using the following commands:
  $ export DISPLAY=":0.0"
  $ xrandr

  [Fail rate]

  5/5 (100% failure rate)

  [Expected result]

  Screen 0: minimum 320 x 200, current 1024 x 768, maximum 16384 x 16384
  DP-1 disconnected primary (normal left inverted right x axis y axis)
  HDMI-1 disconnected (normal left inverted right x axis y axis)
  DP-2 disconnected (normal left inverted right x axis y axis)
  HDMI-2 disconnected (normal left inverted right x axis y axis)
  DP-3 disconnected (normal left inverted right x axis y axis)
  HDMI-3 disconnected (normal left inverted right x axis y axis)

  [Actual result]

  Authorization required, but no authorization protocol specified

  Can't open display :0.0

  [Additional information]

  https://certification.canon

[Touch-packages] [Bug 2085397] Re: package libasound2-plugins 1.2.7.1-1ubuntu5 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is dif

[Apport retracing service]

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

** Tags removed: need-duplicate-check

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

Title:
  package libasound2-plugins 1.2.7.1-1ubuntu5 failed to install/upgrade:
  trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-
  default.conf.example', which is different from other instances of
  package libasound2-plugins:i386

Status in alsa-plugins package in Ubuntu:
  New

Bug description:
  Errors were encountered while processing:
   /tmp/apt-dpkg-install-2C2KfX/152-libasound2-plugins_1.2.7.1-1ubuntu5_i386.deb

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: libasound2-plugins 1.2.7.1-1ubuntu5
  ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
  Uname: Linux 6.8.0-47-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Oct 23 10:07:22 2024
  DuplicateSignature:
   package:libasound2-plugins:1.2.7.1-1ubuntu5
   Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu5) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-2C2KfX/152-libasound2-plugins_1.2.7.1-1ubuntu5_i386.deb 
(--unpack):
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  ErrorMessage: trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  InstallationDate: Installed on 2024-10-21 (2 days ago)
  InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
  Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.6ubuntu6.1
   apt  2.7.14build2
  SourcePackage: alsa-plugins
  Title: package libasound2-plugins 1.2.7.1-1ubuntu5 failed to install/upgrade: 
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/2085397/+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 2085397] [NEW] package libasound2-plugins 1.2.7.1-1ubuntu5 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is d

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Errors were encountered while processing:
 /tmp/apt-dpkg-install-2C2KfX/152-libasound2-plugins_1.2.7.1-1ubuntu5_i386.deb

ProblemType: Package
DistroRelease: Ubuntu 24.04
Package: libasound2-plugins 1.2.7.1-1ubuntu5
ProcVersionSignature: Ubuntu 6.8.0-47.47-generic 6.8.12
Uname: Linux 6.8.0-47-generic x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Oct 23 10:07:22 2024
DuplicateSignature:
 package:libasound2-plugins:1.2.7.1-1ubuntu5
 Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu5) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-2C2KfX/152-libasound2-plugins_1.2.7.1-1ubuntu5_i386.deb 
(--unpack):
  trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
ErrorMessage: trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
InstallationDate: Installed on 2024-10-21 (2 days ago)
InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 
(20240827.1)
Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 
3.12.3-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.6ubuntu6.1
 apt  2.7.14build2
SourcePackage: alsa-plugins
Title: package libasound2-plugins 1.2.7.1-1ubuntu5 failed to install/upgrade: 
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package need-duplicate-check noble package-conflict
-- 
package libasound2-plugins 1.2.7.1-1ubuntu5 failed to install/upgrade: trying 
to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', 
which is different from other instances of package libasound2-plugins:i386
https://bugs.launchpad.net/bugs/2085397
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-plugins 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 2069516] Re: Totem won't play video files, OpenGL initialization error

[Julien Olivier]

Totem works perfectly if launched from a terminal though...

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

Title:
  Totem won't play video files, OpenGL initialization error

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  I confirm this bug also occurs with totem and the vanilla Gnome in a
  Debian Sid install.

  When launching totem to play any format movie, it throws error "Could
  not initialise OpenGL support".

  It's confirmed OpenGL is working (glxgears)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libgstreamer1.0-0 1.24.2-1
  ProcVersionSignature: Ubuntu 6.8.0-35.35-generic 6.8.4
  Uname: Linux 6.8.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.28.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 15 15:35:05 2024
  InstallationDate: Installed on 2024-06-15 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Release amd64 (20240424)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2069516/+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 2085340] Re: Plenty of amdgpu backtraces post resume

[Launchpad Bug Tracker]

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

** Changed in: linux (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/2085340

Title:
  Plenty of amdgpu backtraces post resume

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

Bug description:
  This is a very weird case: The GNOME session crashed 3 times today,
  the last time, it went to gdm, but then gdm did not recognize it was
  docked and suspended. I think the kernel needed two attempts to
  resume, it got suspended again after the first one; and it produced a
  whole bunch of back traces in dmesg.

  
  [ 3300.659129] WARNING: CPU: 1 PID: 65823 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315 
dal_gpio_service_open+0x1b6/0x270 [amdgpu]
  [ 3410.146130] WARNING: CPU: 4 PID: 73742 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:221 
dmub_psr_enable+0x102/0x110 [amdgpu]

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: linux-image-6.11.0-9-generic 6.11.0-9.9
  ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
  Uname: Linux 6.11.0-9-generic x86_64
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Tue Oct 22 12:45:20 2024
  InstallationDate: Installed on 2022-11-26 (696 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: LENOVO 21CF004PGE
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-9-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 
zswap.zpool=zsmalloc vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.11.0-9-generic N/A
   linux-backports-modules-6.11.0-9-generic  N/A
   linux-firmware20240913.gita34e7a5f-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2024
  dmi.bios.release: 1.53
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET77W (1.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085340/+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 2085340] Re: Plenty of amdgpu backtraces post resume

[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/2085340

Title:
  Plenty of amdgpu backtraces post resume

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

Bug description:
  This is a very weird case: The GNOME session crashed 3 times today,
  the last time, it went to gdm, but then gdm did not recognize it was
  docked and suspended. I think the kernel needed two attempts to
  resume, it got suspended again after the first one; and it produced a
  whole bunch of back traces in dmesg.

  
  [ 3300.659129] WARNING: CPU: 1 PID: 65823 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315 
dal_gpio_service_open+0x1b6/0x270 [amdgpu]
  [ 3410.146130] WARNING: CPU: 4 PID: 73742 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:221 
dmub_psr_enable+0x102/0x110 [amdgpu]

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: linux-image-6.11.0-9-generic 6.11.0-9.9
  ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
  Uname: Linux 6.11.0-9-generic x86_64
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Tue Oct 22 12:45:20 2024
  InstallationDate: Installed on 2022-11-26 (696 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: LENOVO 21CF004PGE
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-9-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 
zswap.zpool=zsmalloc vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.11.0-9-generic N/A
   linux-backports-modules-6.11.0-9-generic  N/A
   linux-firmware20240913.gita34e7a5f-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2024
  dmi.bios.release: 1.53
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET77W (1.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085340/+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 2064508] Re: re-enable Ubuntu FAN in the Noble kernel

[Timo Aaltonen]

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

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

Title:
  re-enable Ubuntu FAN in the Noble kernel

Status in iproute2 package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in iproute2 source package in Noble:
  Invalid
Status in linux source package in Noble:
  Fix Released
Status in iproute2 source package in Oracular:
  Fix Released
Status in linux source package in Oracular:
  Fix Released

Bug description:
  [Impact]

  In LP: #2063298, we have opted to deprecate Ubuntu FAN support because
  of the maintenance overhead and the possibility of regressions /
  conflicts with the new networking eBPF APIs in kernels >= 6.8.

  However, we cannot disable this feature in HWE/backport kernels, so it
  seems safer to adjust the Ubuntu FAN kernel patch set to ensure proper
  co-existence with the updated vxlan policy requirements in newer 6.8
  kernels.

  The re-introduction of Ubuntu FAN should be considered as a temporary
  measure, aimed at facilitating a smooth transition during its
  deprecation without disrupting existing users (specifically Juju), and
  enabling the backporting of 6.8 kernels to older releases.

  The main plan is still to deprecate Ubuntu FAN at some point in the
  future.

  [Test case]

  Rely on the specific Ubuntu FAN regression test to validate the proper
  kernel support of this feature:

  https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-
  tests/tree/ubuntu_fan_smoke_test?h=autotest3

  [Fix]

  Re-apply the Ubuntu FAN patch set to the latest Noble kernel 6.8 and
  integrate the IFLA_VXLAN_FAN_MAP attribute type in vxlan_policy to
  satisfy the strict length validation check.

  [Regression potential]

  We may experience regressions with eBPF vxlan capabilities and
  potentially specific use cases of the Ubuntu FAN technology (Juju
  installations).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2064508/+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 2085340] Re: Plenty of amdgpu backtraces post resume

[AaronMa]

A similar upstream bug:
https://gitlab.freedesktop.org/drm/amd/-/issues/3587

Could you try to add amdgpu.dcdebugmask=0x10 to kernel options?

** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #3587
   https://gitlab.freedesktop.org/drm/amd/-/issues/3587

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

Title:
  Plenty of amdgpu backtraces post resume

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

Bug description:
  This is a very weird case: The GNOME session crashed 3 times today,
  the last time, it went to gdm, but then gdm did not recognize it was
  docked and suspended. I think the kernel needed two attempts to
  resume, it got suspended again after the first one; and it produced a
  whole bunch of back traces in dmesg.

  
  [ 3300.659129] WARNING: CPU: 1 PID: 65823 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315 
dal_gpio_service_open+0x1b6/0x270 [amdgpu]
  [ 3410.146130] WARNING: CPU: 4 PID: 73742 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:221 
dmub_psr_enable+0x102/0x110 [amdgpu]

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: linux-image-6.11.0-9-generic 6.11.0-9.9
  ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
  Uname: Linux 6.11.0-9-generic x86_64
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Tue Oct 22 12:45:20 2024
  InstallationDate: Installed on 2022-11-26 (696 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: LENOVO 21CF004PGE
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-9-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 
zswap.zpool=zsmalloc vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.11.0-9-generic N/A
   linux-backports-modules-6.11.0-9-generic  N/A
   linux-firmware20240913.gita34e7a5f-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2024
  dmi.bios.release: 1.53
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET77W (1.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085340/+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 2085157] Re: mkinitramfs fails with copy_file binary '/libgcc_s.so.[1-9]' not found

[Frank Heimes]

** Description changed:

- I recently did an 24.10 install (on s390x, but I think this doesn't
- matter) and was surprised that the system hangs during the post-install
- reboot.
+ I recently did an 24.10 install and was surprised that the system hangs
+ during the post-install reboot.
  
  Investigation showed that this happens if the installer applies updates,
  which is done by default, if there is proper network connectivity and
  archive access.
  
  In case of an install where I disabled the network, hence an offline
  install was done, the installation incl. post-install reboot was
  successful.
  
  So I took such a successfully installed system (where no updates were 
applied) and noticed that currently the available updates are:
  $ apt list --upgradable
  iproute2/oracular-updates 6.10.0-2ubuntu1 s390x [upgradable from: 6.10.0-2]
  linux-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8]
  linux-headers-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 
6.11.0-8.8]
  linux-image-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 
6.11.0-8.8]
  linux-libc-dev/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8]
  linux-tools-common/oracular-updates 6.11.0-9.9 all [upgradable from: 
6.11.0-8.8]
  
  So seemed to be kernel related, hence tried to update the kernel manually:
  $ sudo apt install linux-image-generic/oracular-updates
  Selected version '6.11.0-9.9' (Ubuntu:24.10/oracular-updates [s390x]) for 
'linux-image-generic'
  Upgrading:
-   linux-generic  linux-image-generic  linux-tools-common
-   linux-headers-generic  linux-libc-dev
+   linux-generic  linux-image-generic  linux-tools-common
+   linux-headers-generic  linux-libc-dev
  
  Installing dependencies:
-   linux-headers-6.11.0-9  linux-modules-extra-6.11.0-9-generic
-   linux-headers-6.11.0-9-generic  linux-tools-6.11.0-9
-   linux-image-6.11.0-9-genericlinux-tools-6.11.0-9-generic
-   linux-modules-6.11.0-9-generic
+   linux-headers-6.11.0-9  linux-modules-extra-6.11.0-9-generic
+   linux-headers-6.11.0-9-generic  linux-tools-6.11.0-9
+   linux-image-6.11.0-9-genericlinux-tools-6.11.0-9-generic
+   linux-modules-6.11.0-9-generic
  
  Suggested packages:
-   fdutils  linux-tools
+   fdutils  linux-tools
  
  Summary:
-   Upgrading: 5, Installing: 7, Removing: 0, Not Upgrading: 1
-   Download size: 65.3 MB
-   Space needed: 165 MB / 21.2 GB available
-   └─ in /boot:  43.1 MB / 1,876 MB available
+   Upgrading: 5, Installing: 7, Removing: 0, Not Upgrading: 1
+   Download size: 65.3 MB
+   Space needed: 165 MB / 21.2 GB available
+   └─ in /boot:  43.1 MB / 1,876 MB available
  
  Continue? [Y/n] Y
  ...
  Setting up linux-generic (6.11.0-9.9) ...
- Progress: [ 96%] [███▋  ] 
- Progress: [ 96%] [███▋  ] 
- Progress: [ 96%] [███▋  ] 
+ Progress: [ 96%] [███▋  ]
+ Progress: [ 96%] [███▋  ]
+ Progress: [ 96%] [███▋  ]
  update-initramfs: Generating /boot/initrd.img-6.11.0-9-generic
- mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found█▋  ] 
+ mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found█▋  ]
  mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found
  Using config file '/etc/zipl.conf'
  Run /lib/s390-tools/zipl_helper.device-mapper 252:1
  Building bootmap in '/boot'
  Adding IPL section 'ubuntu' (default)
  Run /lib/s390-tools/zipl_helper.device-mapper 252:1
  Run /lib/s390-tools/zipl_helper.device-mapper 252:1
  Preparing boot device for LD-IPL: dm-0.
  Done.
  /etc/kernel/postinst.d/kdump-tools:
  kdump-tools: Generating /var/lib/kdump/initrd.img-6.11.0-9-generic
  mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
  mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found
  /etc/kernel/postinst.d/zz-zipl:
  Using config file '/etc/zipl.conf'
  Run /lib/s390-tools/zipl_helper.device-mapper 252:1
  Building bootmap in '/boot'
  Adding IPL section 'ubuntu' (default)
  Run /lib/s390-tools/zipl_helper.device-mapper 252:1
  Run /lib/s390-tools/zipl_helper.device-mapper 252:1
  Preparing boot device for LD-IPL: dm-0.
  Done.
- Scanning processes... 
  
- Scanning processor microcode...   
  
- Scanning linux images...  
  
+ Scanning processes...
+ Scanning processor microcode...
+ Scanning linux images...
  
  Pending kernel upgrade!
  Running kernel version:
-   6.11.0-8-generic
+   6.11.0-8-generic
  Diagnostics:
-   The currently running kernel version is not the expected kernel version
+   The currently running ker

[Touch-packages] [Bug 2074212] Re: [SRU] Enable frame-pointer on Noble in libdmapsharing

[Paride Legovini]

Thanks!

Uploading libdmapsharing_3.9.13-2ubuntu1~22.04.1.dsc
Uploading libdmapsharing_3.9.13-2ubuntu1~22.04.1.debian.tar.xz
Uploading libdmapsharing_3.9.13-2ubuntu1~22.04.1_source.buildinfo
Uploading libdmapsharing_3.9.13-2ubuntu1~22.04.1_source.changes


** Changed in: libdmapsharing (Ubuntu Noble)
   Status: New => In Progress

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

Title:
  [SRU] Enable frame-pointer on Noble in libdmapsharing

Status in libdmapsharing package in Ubuntu:
  Fix Released
Status in libdmapsharing source package in Noble:
  In Progress

Bug description:
  [ Impact ]

  In order to help developers with profiling, Ubuntu enabled frame-
  pointers for packages in the main archive.

  https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame-
  pointers-by-default

  The `Affects` packages were missed due to the packaging issues. These
  have been fixed on Oracular and can now be ported to Noble.

  [Proposed fix]

  Previously, tests run via dh_auto_test were failing and the error
  ignored. See https://launchpadlibrarian.net/722365230/buildlog_ubuntu-
  noble-amd64.libdmapsharing_3.9.13-2build1_BUILDING.txt.gz for the log
  of the build of the package currently in noble.

  Running the test suite was calling `make check`, rebuilding the
  binaries with specific CFLAGS and replacing the ones previously built
  with proper CLFAGS. These binaries were then packaged into the deb.

  Not running the tests was found to be the best solution until upstream
  maintainers fix the way test binaries are built.

  [ Test Plan ]

  Look at the DW_AT_producer in the associated debug ELF file for flags.
  -fno-omit-frame-pointer should be present after the fix.

  The following scripts can be used as a reference
  https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208
  https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c

  -fno-omit-frame-pointer is also present in build logs and now binaries
  are not rebuilt without this flag anymore to run tests.

  Smoke test I ran:

  Download https://www2.cs.uic.edu/~i101/SoundFiles/StarWars3.wav (or
  any wav file)

  sudo apt install rhythmbox
  sudo dpkg -i libdmapsharing-4.0-3t64_3.9.13-2ubuntu1_amd64.deb

  
  I was unable to find a daap server in the archive (I even tried to configure 
rhythmbox/xmms2/vlc to do it, without any luck) so I had to use owntone in a 
container. A simpler solution may exist though.

  mkdir -p scratch/owntone/{etc,media,cache}
  cp StarWars3.wav scratch/owntone/media/
  docker run -d \
    --name=OwnTone \
    --network=host \
    -e UID=$(id -u) \
    -e GID=$(id -g) \
    -v $HOME/scratch/owntone/etc:/etc/owntone \
    -v $HOME/scratch/owntone/media:/srv/media \
    -v $HOME/scratch/owntone/cache:/var/cache/owntone \
    --restart unless-stopped \
    docker.io/owntone/owntone:latest

  At this point owntone is sharing the wav file over DAAP.
  Launch rhythmbox.
  An entry in the `Shared` section of the left menu should be visible. 
StarWars3.wav should be playable.

  
  [ Where problems could occur ]

  No source changes are made. The packaging fixes have enabled other
  security hardening flags. This could have unintended effects.

  [ Other Info ]

  Changes in dpkg have been made to make sure frame-pointers are not
  enabled on s390x and ppc64el.

  Bug reference with similar SRU
  - https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdmapsharing/+bug/2074212/+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 2085157] Re: mkinitramfs fails with copy_file binary '/libgcc_s.so.[1-9]' not found

[Frank Heimes]

The 'hook-functions' where the code is included is actually part of 
initramfs-tools-core:
dpkg -S /usr/share/initramfs-tools/hook-functions
initramfs-tools-core: /usr/share/initramfs-tools/hook-functions

** Also affects: initramfs-tools
   Importance: Undecided
   Status: New

** No longer affects: initramfs-tools

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

Title:
  mkinitramfs fails with copy_file binary '/libgcc_s.so.[1-9]' not found

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I recently did an 24.10 install and was surprised that the system
  hangs during the post-install reboot.

  Investigation showed that this happens if the installer applies
  updates, which is done by default, if there is proper network
  connectivity and archive access.

  In case of an install where I disabled the network, hence an offline
  install was done, the installation incl. post-install reboot was
  successful.

  So I took such a successfully installed system (where no updates were 
applied) and noticed that currently the available updates are:
  $ apt list --upgradable
  iproute2/oracular-updates 6.10.0-2ubuntu1 s390x [upgradable from: 6.10.0-2]
  linux-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8]
  linux-headers-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 
6.11.0-8.8]
  linux-image-generic/oracular-updates 6.11.0-9.9 s390x [upgradable from: 
6.11.0-8.8]
  linux-libc-dev/oracular-updates 6.11.0-9.9 s390x [upgradable from: 6.11.0-8.8]
  linux-tools-common/oracular-updates 6.11.0-9.9 all [upgradable from: 
6.11.0-8.8]

  So seemed to be kernel related, hence tried to update the kernel manually:
  $ sudo apt install linux-image-generic/oracular-updates
  Selected version '6.11.0-9.9' (Ubuntu:24.10/oracular-updates [s390x]) for 
'linux-image-generic'
  Upgrading:
    linux-generic  linux-image-generic  linux-tools-common
    linux-headers-generic  linux-libc-dev

  Installing dependencies:
    linux-headers-6.11.0-9  linux-modules-extra-6.11.0-9-generic
    linux-headers-6.11.0-9-generic  linux-tools-6.11.0-9
    linux-image-6.11.0-9-genericlinux-tools-6.11.0-9-generic
    linux-modules-6.11.0-9-generic

  Suggested packages:
    fdutils  linux-tools

  Summary:
    Upgrading: 5, Installing: 7, Removing: 0, Not Upgrading: 1
    Download size: 65.3 MB
    Space needed: 165 MB / 21.2 GB available
    └─ in /boot:  43.1 MB / 1,876 MB available

  Continue? [Y/n] Y
  ...
  Setting up linux-generic (6.11.0-9.9) ...
  Progress: [ 96%] [███▋  ]
  Progress: [ 96%] [███▋  ]
  Progress: [ 96%] [███▋  ]
  update-initramfs: Generating /boot/initrd.img-6.11.0-9-generic
  mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found█▋  ]
  mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found
  Using config file '/etc/zipl.conf'
  Run /lib/s390-tools/zipl_helper.device-mapper 252:1
  Building bootmap in '/boot'
  Adding IPL section 'ubuntu' (default)
  Run /lib/s390-tools/zipl_helper.device-mapper 252:1
  Run /lib/s390-tools/zipl_helper.device-mapper 252:1
  Preparing boot device for LD-IPL: dm-0.
  Done.
  /etc/kernel/postinst.d/kdump-tools:
  kdump-tools: Generating /var/lib/kdump/initrd.img-6.11.0-9-generic
  mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found
  mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found
  /etc/kernel/postinst.d/zz-zipl:
  Using config file '/etc/zipl.conf'
  Run /lib/s390-tools/zipl_helper.device-mapper 252:1
  Building bootmap in '/boot'
  Adding IPL section 'ubuntu' (default)
  Run /lib/s390-tools/zipl_helper.device-mapper 252:1
  Run /lib/s390-tools/zipl_helper.device-mapper 252:1
  Preparing boot device for LD-IPL: dm-0.
  Done.
  Scanning processes...
  Scanning processor microcode...
  Scanning linux images...

  Pending kernel upgrade!
  Running kernel version:
    6.11.0-8-generic
  Diagnostics:
    The currently running kernel version is not the expected kernel version
  6.11.0-9-generic.

  Restarting the system to load the new kernel will not be handled 
automatically,
  so you should consider rebooting.

  Failed to check for processor microcode upgrades.

  No services need to be restarted.

  No containers need to be restarted.

  No user sessions are running outdated binaries.

  No VM guests are running outdated hypervisor (qemu) binaries on this
  host.

  I noticed these two lines, that have been spit out by update-initramfs:
  update-initramfs: Generating /boot/initrd.img-6.11.0-9-generic
  mkinitramfs: copy_file: binary '/usr/lib/udev/dmsetup_env' not found█▋  ]
  mkinitramfs: copy_file: binary '/libgcc_s.so.[1-9]' not found

  Hence I tried to ran 

[Touch-packages] [Bug 2085340] Re: Plenty of amdgpu backtraces post resume

[Mario Limonciello]

> Attaching the Journal, the initial crash can be seen at 12:31:54, lots
going on there, but nothing root-causing this.

[ 3300.659129] WARNING: CPU: 1 PID: 65823 at
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315
dal_gpio_service_open+0x1b6/0x270 [amdgpu]

This is the assertion you're hitting:
https://github.com/torvalds/linux/blob/v6.12-rc4/drivers/gpu/drm/amd/display/dc/gpio/gpio_service.c#L315

Can you reproduce this at will?  Is it tied to being docked?  If so it
might be related to HPD events coming in at the wrong time from the
dock.  We saw something similar that has been fixed in 6.11.y.

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/gpu/drm/amd?h=linux-6.11.y&id=c2356296f546326f9f06c109e201d42201e1e783

If you can still reproduce this (at will) with 6.11.y and 6.12-rc4
please raise it upstream.


At this point I'm not convinced that PSR is the perpetrator, but rather feels 
like a victim.

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

Title:
  Plenty of amdgpu backtraces post resume

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

Bug description:
  This is a very weird case: The GNOME session crashed 3 times today,
  the last time, it went to gdm, but then gdm did not recognize it was
  docked and suspended. I think the kernel needed two attempts to
  resume, it got suspended again after the first one; and it produced a
  whole bunch of back traces in dmesg.

  
  [ 3300.659129] WARNING: CPU: 1 PID: 65823 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/gpio/gpio_service.c:315 
dal_gpio_service_open+0x1b6/0x270 [amdgpu]
  [ 3410.146130] WARNING: CPU: 4 PID: 73742 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dce/dmub_psr.c:221 
dmub_psr_enable+0x102/0x110 [amdgpu]

  ProblemType: Bug
  DistroRelease: Ubuntu 24.10
  Package: linux-image-6.11.0-9-generic 6.11.0-9.9
  ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
  Uname: Linux 6.11.0-9-generic x86_64
  ApportVersion: 2.30.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Tue Oct 22 12:45:20 2024
  InstallationDate: Installed on 2022-11-26 (696 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  MachineType: LENOVO 21CF004PGE
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.11.0-9-generic 
root=/dev/mapper/ubuntu-root ro rootflags=subvol=@next quiet splash 
crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M 
zswap.enabled=1 zswap.compressor=zstd zswap.max_pool_percent=20 
zswap.zpool=zsmalloc vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-6.11.0-9-generic N/A
   linux-backports-modules-6.11.0-9-generic  N/A
   linux-firmware20240913.gita34e7a5f-0ubuntu2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2024
  dmi.bios.release: 1.53
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R23ET77W (1.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21CF004PGE
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76538 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrR23ET77W(1.53):bd05/29/2024:br1.53:efr1.32:svnLENOVO:pn21CF004PGE:pvrThinkPadT14Gen3:rvnLENOVO:rn21CF004PGE:rvrSDK0T76538WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21CF_BU_Think_FM_ThinkPadT14Gen3:
  dmi.product.family: ThinkPad T14 Gen 3
  dmi.product.name: 21CF004PGE
  dmi.product.sku: LENOVO_MT_21CF_BU_Think_FM_ThinkPad T14 Gen 3
  dmi.product.version: ThinkPad T14 Gen 3
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2085340/+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 2018128] Re: Apport does not collect all logs when the package is HWE kernel (or any derivative)

[Juerg Haefliger]

** Summary changed:

- Apport does not collect all logs when the package is HWE kernel
+ Apport does not collect all logs when the package is HWE kernel (or any 
derivative)

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

** Also affects: linux-meta (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: linux-meta (Ubuntu)

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

Title:
  Apport does not collect all logs when the package is HWE kernel (or
  any derivative)

Status in apport package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 LTS with kernel 5.19.0-41-generic

  When filing bugs against the package 'linux' apport collects all the logs 
needed
  to the kernel

  But in case the user is not on stock kernel anymore and has the HWE kernel
  apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt

  and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my
  case)

  would it be possible to make apport collect all the logs needed in all
  kernel cases?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.4
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 05:25:30 2023
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+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 2085360] [NEW] DAC Aune X1 not recognize

[Valentine]

Public bug reported:

Hi, I would like to listen my Flac songs on external USB DAC AUne X1 
24bit/192Khz. It doesn't recognize on pipewire.
Many thanks

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.8.0-47.47.1-lowlatency 6.8.12
Uname: Linux 6.8.0-47-lowlatency x86_64
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Tue Oct 22 15:33:22 2024
InstallationDate: Installed on 2024-05-29 (146 days ago)
InstallationMedia: Ubuntu-Studio 24.04 LTS "Noble Numbat" - Release amd64 
(20240424.1)
MachineType: Dell Inc. Precision T1700
PackageArchitecture: all
ProcEnviron:
 LANG=fr_FR.UTF-8
 LANGUAGE=
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
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: 06/26/2017
dmi.bios.release: 4.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A23
dmi.board.name: 0JVY7H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd06/26/2017:br4.6:svnDellInc.:pnPrecisionT1700:pvr01:rvnDellInc.:rn0JVY7H:rvrA00:cvnDellInc.:ct6:cvr:skuPrecisionT1700:
dmi.product.name: Precision T1700
dmi.product.sku: Precision T1700
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-bug noble

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

Title:
  DAC Aune X1 not recognize

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi, I would like to listen my Flac songs on external USB DAC AUne X1 
24bit/192Khz. It doesn't recognize on pipewire.
  Many thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-47.47.1-lowlatency 6.8.12
  Uname: Linux 6.8.0-47-lowlatency x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Oct 22 15:33:22 2024
  InstallationDate: Installed on 2024-05-29 (146 days ago)
  InstallationMedia: Ubuntu-Studio 24.04 LTS "Noble Numbat" - Release amd64 
(20240424.1)
  MachineType: Dell Inc. Precision T1700
  PackageArchitecture: all
  ProcEnviron:
   LANG=fr_FR.UTF-8
   LANGUAGE=
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  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: 06/26/2017
  dmi.bios.release: 4.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A23
  dmi.board.name: 0JVY7H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA23:bd06/26/2017:br4.6:svnDellInc.:pnPrecisionT1700:pvr01:rvnDellInc.:rn0JVY7H:rvrA00:cvnDellInc.:ct6:cvr:skuPrecisionT1700:
  dmi.product.name: Precision T1700
  dmi.product.sku: Precision T1700
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2085360/+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 2074212] Re: [SRU] Enable frame-pointer on Noble in libdmapsharing

[Paul Mars]

Fixed the version again per Paride's comment.

** Patch added: "debdiff-libdmapsharing-noble.diff"
   
https://bugs.launchpad.net/ubuntu/+source/libdmapsharing/+bug/2074212/+attachment/5830759/+files/debdiff-libdmapsharing-noble.diff

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

Title:
  [SRU] Enable frame-pointer on Noble in libdmapsharing

Status in libdmapsharing package in Ubuntu:
  Fix Released
Status in libdmapsharing source package in Noble:
  New

Bug description:
  [ Impact ]

  In order to help developers with profiling, Ubuntu enabled frame-
  pointers for packages in the main archive.

  https://ubuntu.com/blog/ubuntu-performance-engineering-with-frame-
  pointers-by-default

  The `Affects` packages were missed due to the packaging issues. These
  have been fixed on Oracular and can now be ported to Noble.

  [Proposed fix]

  Previously, tests run via dh_auto_test were failing and the error
  ignored. See https://launchpadlibrarian.net/722365230/buildlog_ubuntu-
  noble-amd64.libdmapsharing_3.9.13-2build1_BUILDING.txt.gz for the log
  of the build of the package currently in noble.

  Running the test suite was calling `make check`, rebuilding the
  binaries with specific CFLAGS and replacing the ones previously built
  with proper CLFAGS. These binaries were then packaged into the deb.

  Not running the tests was found to be the best solution until upstream
  maintainers fix the way test binaries are built.

  [ Test Plan ]

  Look at the DW_AT_producer in the associated debug ELF file for flags.
  -fno-omit-frame-pointer should be present after the fix.

  The following scripts can be used as a reference
  https://gist.github.com/julian-klode/85e3f85c410a1b856a93dce77208
  https://gist.github.com/julian-klode/95818246eaef0ac6a54588f7f368e25c

  -fno-omit-frame-pointer is also present in build logs and now binaries
  are not rebuilt without this flag anymore to run tests.

  Smoke test I ran:

  Download https://www2.cs.uic.edu/~i101/SoundFiles/StarWars3.wav (or
  any wav file)

  sudo apt install rhythmbox
  sudo dpkg -i libdmapsharing-4.0-3t64_3.9.13-2ubuntu1_amd64.deb

  
  I was unable to find a daap server in the archive (I even tried to configure 
rhythmbox/xmms2/vlc to do it, without any luck) so I had to use owntone in a 
container. A simpler solution may exist though.

  mkdir -p scratch/owntone/{etc,media,cache}
  cp StarWars3.wav scratch/owntone/media/
  docker run -d \
    --name=OwnTone \
    --network=host \
    -e UID=$(id -u) \
    -e GID=$(id -g) \
    -v $HOME/scratch/owntone/etc:/etc/owntone \
    -v $HOME/scratch/owntone/media:/srv/media \
    -v $HOME/scratch/owntone/cache:/var/cache/owntone \
    --restart unless-stopped \
    docker.io/owntone/owntone:latest

  At this point owntone is sharing the wav file over DAAP.
  Launch rhythmbox.
  An entry in the `Shared` section of the left menu should be visible. 
StarWars3.wav should be playable.

  
  [ Where problems could occur ]

  No source changes are made. The packaging fixes have enabled other
  security hardening flags. This could have unintended effects.

  [ Other Info ]

  Changes in dpkg have been made to make sure frame-pointers are not
  enabled on s390x and ppc64el.

  Bug reference with similar SRU
  - https://bugs.launchpad.net/ubuntu/+source/ipvsadm/+bug/2071949

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdmapsharing/+bug/2074212/+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 2080216] Re: sshd cannot bind to IPv4 interfaces

[Nick Rosbrook]

This is waiting on review from the SRU team. Many of the SRU team
members are also busy with opening the archive for 25.04 and other
things this week, but I will ping them.

Once it is accepted into noble-proposed, it will be at least a week
until it moves to noble-updates.

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

Title:
  sshd cannot bind to IPv4 interfaces

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Noble:
  In Progress

Bug description:
  [Impact]

  The default listening sockets for sshd are different depending on
  whether socket activation is used or not, even when
  /etc/ssh/sshd_config is the default. E.g.:

  # Socket-activated

  root@n2:~# systemctl status ssh.socket
  ● ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/usr/lib/systemd/system/ssh.socket; enabled; preset: 
enabled)
   Active: active (listening) since Tue 2024-10-01 20:36:15 UTC; 12min ago
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
   CGroup: /system.slice/ssh.socket

  Oct 01 20:36:15 n2 systemd[1]: Listening on ssh.socket - OpenBSD Secure Shell 
server socket.
  root@n2:~# lsof -i :22
  COMMAND PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
  systemd   1 root   47u  IPv6 2781411  0t0  TCP *:ssh (LISTEN)

  # Non-socket-activated

  root@n2:~# systemctl disable --now ssh.socket
  Removed "/etc/systemd/system/ssh.service.requires/ssh.socket".
  Removed "/etc/systemd/system/sockets.target.wants/ssh.socket".
  root@n2:~# ln -s /dev/null 
/etc/systemd/system-generators/sshd-socket-generator
  root@n2:~# systemctl enable --now ssh.service
  Synchronizing state of ssh.service with SysV service script with 
/usr/lib/systemd/systemd-sysv-install.
  Executing: /usr/lib/systemd/systemd-sysv-install enable ssh
  Created symlink /etc/systemd/system/sshd.service → 
/usr/lib/systemd/system/ssh.service.
  Created symlink /etc/systemd/system/multi-user.target.wants/ssh.service → 
/usr/lib/systemd/system/ssh.service.
  root@n2:~# lsof -i :22
  COMMAND PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
  sshd798 root3u  IPv4 2793622  0t0  TCP *:ssh (LISTEN)
  sshd798 root4u  IPv6 2793624  0t0  TCP *:ssh (LISTEN)

  By default, we have net.ipv6.bindv6only=0 sysctl, and
  BindIPv6Only=both on ssh.socket, which means usually users can connect
  over IPv4 regardless. However, the fact remains that the resulting
  listening sockets are different in these two cases, and socket-
  activated ssh does not accurately reflect the settings in
  /etc/ssh/sshd_config.

  [Test Plan]

  1. Check that on a noble system, without custom sshd_config, sshd is
  listening on both IPv4 and IPv6 on port 22:

  $ lsof -i :22

  2. Check that setting AddressFamily to e.g. inet results in only an
  IPv4 socket:

  $ echo "AddressFamily inet" >> /etc/ssh/sshd_config.d/custom.conf
  $ systemctl daemon-reload
  $ systemctl restart ssh.socket
  $ lsof -i :22

  There should only be one listener now.

  3. Check the same thing with inet6, and a custom port for good
  measure:

  $ echo "AddressFamily inet6" >> /etc/ssh/sshd_config.d/custom.conf
  $ echo "Port 1234" >> /etc/ssh/sshd_config.d/custom.conf
  $ systemctl daemon-reload
  $ systemctl restart ssh.socket
  $ lsof -i :1234

  4. The new tests in debian/tests/sshd-socket-generator should all pass
  in autopkgtest.

  [Where problems could occur]

  The fix requires new default settings in the [Socket] section of
  ssh.socket, and handling for new defaults in sshd-socket-generator. It
  would be more likely to see problems with the generator as opposed to
  the changes in ssh.socket. However, new subtests were added to
  debian/tests/sshd-socket-generator to help avoid this.

  [Original Description]

  After upgrading from 22.04 to 24.04 I noticed that my sshd only
  listening on IPv6 interface (::), while previously it was listening
  both IPv4 (0.0.0.0) and IPv6 (::). I tried to explicitly specify
  ListenAddress 0.0.0.0 (assuming it would bind to IPv4 only) but after
  restart sshd was still listening on IPv6 only.

  This problem affects other packages as well, for example, openvpn.

  Rebuilding applications from sources seems to fix the issue.

  Setting net.ipv6.bindv6only=0 also helps, but that's not a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openssh-server 1:9.6p1-3ubuntu13.5
  ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
  Uname: Linux 6.8.0-41-generic x86_64
  ApportVersion: 2.28.1-0ubuntu3.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Sep 10 16:45:54 2024
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=screen.xterm-256color
  SourcePackage: openssh
  UpgradeStatus: Upgraded to noble on 2024-09-10 (0 days ago)

To manage notifications about this bug go to:
htt

[Touch-packages] [Bug 2085257] Re: Merge nspr from Debian unstable for jammy

[Lena Voytek]

** Changed in: nspr (Ubuntu)
 Assignee: (unassigned) => Lena Voytek (lvoytek)

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

Title:
  Merge nspr from Debian unstable for jammy

Status in nspr package in Ubuntu:
  New

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   2:4.35-1.1
  Ubuntu:   2:4.35-1.1ubuntu1


  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Jammy Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  nspr (2:4.35-1.1) unstable; urgency=medium

* Non-maintainer upload
* Avoid libreswan build failures on mipsel (Closes: #854472)

   -- Daniel Kahn Gillmor   Wed, 22 Feb 2023
  15:00:34 -0500

  nspr (2:4.35-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Sun, 18 Sep 2022 06:29:06 +0900

  nspr (2:4.34.1-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Wed, 24 Aug 2022 06:54:43 +0900

  nspr (2:4.34-1) unstable; urgency=medium

* New upstream release.

* debian/libnspr4.symbols: Add PR_GetPrefLoopbackAddrInfo to symbols
  file.

   -- Mike Hommey   Wed, 01 Jun 2022 06:21:09 +0900

  nspr (2:4.33-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Wed, 06 Apr 2022 09:13:06 +0900

  nspr (2:4.32-3) unstable; urgency=medium

* nspr/configure.in: Fix AC_CONFIG_AUX_DIR.

   -- Mike Hommey   Sun, 21 Nov 2021 09:06:33 +0900

  nspr (2:4.32-2) unstable; urgency=medium

* debian/libnspr4-dev.links.in, debian/control: Remove xulrunner-nspr.pc,
  which breaks libxmlsec1-dev (<= 1.2.33-1).
* debian/copyright: Use secure copyright file specification URI.
* debian/compat, debian/control:
  - Bump debhelper from deprecated 9 to 13.
  - Set debhelper-compat version in Build-Depends.
* debian/rules: Drop transition for old debug package migration.
* debian/*lintian-overrides*:
  - Remove unused copyright-refers-to-versionless-license-file.
  - s/shlib-without-versioned-soname/shared-library-lacks-version/
  - 
s/dev-pkg-without-shlib-symlink/lacks-unversioned-link-to-shared-library/
* debian/watch: Upgrade watch file to version 4.
* debian/rules:
  - Build with `make -s` when DEB_BUILD_OPTIONS contains terse.
  - Enable all hardnening options.
* debian/control:
  - Add Rules-Requires-Root: no.
  - Upgrade Standards-Version to 4.6.0.
  - Remove conflict with libnspr3-0d. The last Debian version with
libnspr3-0d was jessie, and it had a newer version anyways.
  - Remove now unnecessary autotools-dev build dependency.
* debian/libnspr4.symbols: Add Build-Depends-Package in symbols file.
* debian/control, debian/rules: Always set Multi-Arch: same.
* debian/upstream/metadata: Add upstream bug tracking metadata.
* debian/libnspr4.triggers: Remove ldconfig trigger, dh_makeshlibs adds
  it automatically.
* debian/not-installed: Don't install compile-et.pl and prerr.properties.

   -- Mike Hommey   Sun, 21 Nov 2021 07:09:06 +0900

  nspr (2:4.32-1) unstable; urgency=medium

* New upstream release. Closes: #991234.

   -- Mike Hommey   Mon, 19 Jul 2021 06:13:28 +0900

  nspr (2:4.29-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Wed, 21 Oct 2020 07:58:38 +0900

  nspr (2:4.28-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Thu, 03 Sep 2020 10:45:34 +0900

  nspr (2:4.27-1) unstable; urgency=medium

* New upstream release.

   -- Mike Hommey   Wed, 29 Jul 2020 16:47:26 +0900

  nspr (2:4.25-1) unstable; urgency=medium

* New upstream release.
* debian/rules: Adapt to changes to runtests.sh.


  
  ### Old Ubuntu Delta ###

  nspr (2:4.35-1.1ubuntu1) oracular; urgency=medium

* Drop explicit -Wl,--as-needed linker flag. It's the default.
* Drop explicit CFLAGS that are checked by configure.
* Also use non-hardening flags from dpkg-buildflags to pick up flags
  like -fno-omit-frame-pointer.

   -- Benjamin Drung   Mon, 22 Jul 2024 11:39:40
  +0200

  nspr (2:4.35-1.1build1) noble; urgency=high

* No change rebuild for 64-bit time_t and frame pointers.

   -- Julian Andres Klode   Mon, 08 Apr 2024
  18:14:31 +0200

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