[Touch-packages] [Bug 2020601] Re: package x11-common 1:7.7+23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Daniel van Vugt]

Thanks for the bug report.

We can't support Debian here, although the packages are very similar to
Ubuntu. I don't see any Ubuntu bugs that look like this one.

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

Title:
  package x11-common 1:7.7+23 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I ran `sudo apt-get remove xrdp` and this error happened.

  ProblemType: Package
  DistroRelease: Debian 12
  Package: x11-common 1:7.7+23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue May 23 17:27:35 2023
  Dependencies: lsb-base 9.20160110ubuntu0.2
  DistUpgraded: Fresh install
  DistroCodename: bookworm
  DistroVariant: ubuntu
  DuplicateSignature:
   package:x11-common:1:7.7+23
   Installing new version of config file /etc/init.d/x11-common ...
   invoke-rc.d: syntax error: unknown option "--skip-systemd-native"
   dpkg: error processing package x11-common (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2017-10-30 (2031 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=f9915581-9e33-4bc6-82a5-6e22ecf0db16 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  Renderer: Software
  SourcePackage: xorg
  Title: package x11-common 1:7.7+23 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jun  3 06:35:07 2022
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse MOUSE, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputVirtualPS/2 VMware VMMouse MOUSE, id 9
   inputVirtualPS/2 VMware VMMouse TOUCHSCREEN, id 10
  xserver.errors:
   AIGLX: reverting to software rendering
   No surface to present from.
   No surface to present from.
   No surface to present from.
   No surface to present from.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: vmware

To manage notifications about this bug go to:

[Touch-packages] [Bug 2018603] Re: Inconsistent cursor size with fractional scaling

[Daniel van Vugt]

desktop-icons-ng uses GTK3 so maybe that's the common factor? Basically
any older GTK app that has to fake fractional scaling by being over-
upscaled and then downscaled in the compositor.

** Also affects: gtk+3.0 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Inconsistent cursor size with fractional scaling

Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  When fractional scaling is enabled (I use 250%), the mouse cursor
  becomes very large when hovering over the desktop and in some
  applications. It returns to its normal size when moved over the panel,
  dock and most Gnome apps (evince is a notable exception here). The
  issue appeared after the update to 23.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: mutter 44.0-2ubuntu4
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  5 15:41:32 2023
  InstallationDate: Installed on 2019-10-31 (1282 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: mutter
  UpgradeStatus: Upgraded to lunar on 2023-05-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng/+bug/2018603/+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 2020601] Re: package x11-common 1:7.7+23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: xorg (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  package x11-common 1:7.7+23 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  I ran `sudo apt-get remove xrdp` and this error happened.

  ProblemType: Package
  DistroRelease: Debian 12
  Package: x11-common 1:7.7+23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue May 23 17:27:35 2023
  Dependencies: lsb-base 9.20160110ubuntu0.2
  DistUpgraded: Fresh install
  DistroCodename: bookworm
  DistroVariant: ubuntu
  DuplicateSignature:
   package:x11-common:1:7.7+23
   Installing new version of config file /etc/init.d/x11-common ...
   invoke-rc.d: syntax error: unknown option "--skip-systemd-native"
   dpkg: error processing package x11-common (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2017-10-30 (2031 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=f9915581-9e33-4bc6-82a5-6e22ecf0db16 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  Renderer: Software
  SourcePackage: xorg
  Title: package x11-common 1:7.7+23 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jun  3 06:35:07 2022
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse MOUSE, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   input   

[Touch-packages] [Bug 2020601] Re: package x11-common 1:7.7+23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package x11-common 1:7.7+23 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in xorg package in Ubuntu:
  New

Bug description:
  I ran `sudo apt-get remove xrdp` and this error happened.

  ProblemType: Package
  DistroRelease: Debian 12
  Package: x11-common 1:7.7+23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue May 23 17:27:35 2023
  Dependencies: lsb-base 9.20160110ubuntu0.2
  DistUpgraded: Fresh install
  DistroCodename: bookworm
  DistroVariant: ubuntu
  DuplicateSignature:
   package:x11-common:1:7.7+23
   Installing new version of config file /etc/init.d/x11-common ...
   invoke-rc.d: syntax error: unknown option "--skip-systemd-native"
   dpkg: error processing package x11-common (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2017-10-30 (2031 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
   Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: VMware, Inc. VMware Virtual Platform
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=f9915581-9e33-4bc6-82a5-6e22ecf0db16 ro quiet splash
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  Renderer: Software
  SourcePackage: xorg
  Title: package x11-common 1:7.7+23 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/12/2020
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jun  3 06:35:07 2022
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputVMware VMware Virtual USB Mouse MOUSE, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputVirtualPS/2 VMware VMMouse MOUSE, id 9
   inputVirtualPS/2 VMware VMMouse TOUCHSCREEN, id 10
  xserver.errors:
   AIGLX: reverting to software rendering
   No surface to present from.
   No surface to present from.
   No surface to present from.
   No surface to present from.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output
Virtual2Virtual3Virtual4Virtual5Virtual6
Virtual7Virtual8
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: vmware

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


-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 2020601] [NEW] package x11-common 1:7.7+23 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Lee Young]

Public bug reported:

I ran `sudo apt-get remove xrdp` and this error happened.

ProblemType: Package
DistroRelease: Debian 12
Package: x11-common 1:7.7+23
ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-42-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Tue May 23 17:27:35 2023
Dependencies: lsb-base 9.20160110ubuntu0.2
DistUpgraded: Fresh install
DistroCodename: bookworm
DistroVariant: ubuntu
DuplicateSignature:
 package:x11-common:1:7.7+23
 Installing new version of config file /etc/init.d/x11-common ...
 invoke-rc.d: syntax error: unknown option "--skip-systemd-native"
 dpkg: error processing package x11-common (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
ExtraDebuggingInterest: Yes
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2017-10-30 (2031 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub
 Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: VMware, Inc. VMware Virtual Platform
PackageArchitecture: all
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=f9915581-9e33-4bc6-82a5-6e22ecf0db16 ro quiet splash
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
Renderer: Software
SourcePackage: xorg
Title: package x11-common 1:7.7+23 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/12/2020
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: 6.00
dmi.board.name: 440BX Desktop Reference Platform
dmi.board.vendor: Intel Corporation
dmi.board.version: None
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 1
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd11/12/2020:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
dmi.product.name: VMware Virtual Platform
dmi.product.version: None
dmi.sys.vendor: VMware, Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Fri Jun  3 06:35:07 2022
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputVMware VMware Virtual USB Mouse MOUSE, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputVirtualPS/2 VMware VMMouse MOUSE, id 9
 inputVirtualPS/2 VMware VMMouse TOUCHSCREEN, id 10
xserver.errors:
 AIGLX: reverting to software rendering
 No surface to present from.
 No surface to present from.
 No surface to present from.
 No surface to present from.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputVirtual2 
   Virtual3Virtual4Virtual5Virtual6Virtual7 
   Virtual8
xserver.version: 2:1.19.3-1ubuntu1~16.04.4
xserver.video_driver: vmware

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


** Tags: amd64 apport-package bookworm compiz-0.9 ubuntu

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

Title:
  package x11-common 1:7.7+23 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in xorg package in Ubuntu:
  New

Bug description:
  I ran `sudo apt-get remove xrdp` and this error happened.

  ProblemType: Package
  DistroRelease: Debian 12
  Package: x11-common 1:7.7+23
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic 

[Touch-packages] [Bug 2019856] Re: Add missing ARM-cores to support Grace-based systems

[Mauricio Faria de Oliveira]

For Mantic, this indeed requires a patch, not a merge/sync, as Debian
doesn't have the commit yet either.

$ git remote get-url origin
git://git.kernel.org/pub/scm/utils/util-linux/util-linux.git

$ git describe --contains 6857cccbb4157d5da34ca98f77a0ac9d68e1e740
v2.39-rc1~126^2~4

$ git show v2.39 | grep Date:
Date:   Wed May 17 12:27:51 2023 +0200
Date:   Wed May 17 11:58:48 2023 +0200

$ rmadison -a source util-linux | grep mantic
 util-linux | 2.38.1-4ubuntu1  | mantic  | source
 util-linux | 2.38.1-5ubuntu1  | mantic-proposed | source

$ rmadison -u debian -a source util-linux
...
util-linux | 2.38.1-5 | testing| source
util-linux | 2.38.1-5 | unstable   | source
util-linux | 2.38.1-5 | unstable-debug | source

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

Title:
  Add missing ARM-cores to support Grace-based systems

Status in util-linux package in Ubuntu:
  In Progress
Status in util-linux source package in Jammy:
  In Progress
Status in util-linux source package in Kinetic:
  Won't Fix
Status in util-linux source package in Lunar:
  In Progress
Status in util-linux source package in Mantic:
  In Progress

Bug description:
  [Impact]

  When running "lscpu" on a Grace-based system + Ubuntu 22.04, it
  doesn't report a model name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Jammy's
  version.

  https://github.com/util-linux/util-
  linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-V2

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems. 

  Output doesn't change on systems with non-affected CPU models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems

[Mauricio Faria de Oliveira]

Debdiff on top of mantic-proposed (2.38.1-5ubuntu1), which should
migrate soon (all good on update-excuses [1] / pending autopkgtests).

https://people.canonical.com/~ubuntu-archive/proposed-
migration/update_excuses.html#util-linux

** Patch added: "lp2019856-mantic-util-linux.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+attachment/5675082/+files/lp2019856-mantic-util-linux.debdiff

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

Title:
  Add missing ARM-cores to support Grace-based systems

Status in util-linux package in Ubuntu:
  In Progress
Status in util-linux source package in Jammy:
  In Progress
Status in util-linux source package in Kinetic:
  Won't Fix
Status in util-linux source package in Lunar:
  In Progress
Status in util-linux source package in Mantic:
  In Progress

Bug description:
  [Impact]

  When running "lscpu" on a Grace-based system + Ubuntu 22.04, it
  doesn't report a model name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Jammy's
  version.

  https://github.com/util-linux/util-
  linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-V2

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems. 

  Output doesn't change on systems with non-affected CPU models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems

[Mauricio Faria de Oliveira]

Test packages in ppa:mfo/lp2019856, verified with GDB
(to fake CPU IDs) on Google Cloud ARM-based instances.

No differences in `lscpu` output for non-affected CPU.
Expected output for both affected CPUs (0xd15, 0xd4f).

Tested on LXD containers for Mantic, Lunar, and Jammy
(not on Kinetic as it will EOL soon, ~2 months).

Mantic:
---

$ lxc launch ubuntu-daily:mantic mantic
$ lxc shell mantic

# lsb_release -cs
No LSB modules are available.
mantic

Old:

# apt install util-linux/mantic-proposed

# dpkg -s util-linux | grep Version:
Version: 2.38.1-5ubuntu1

# lscpu | grep -e 'Vendor ID:' -e 'Model name:'
Vendor ID:   ARM
Model name:  Neoverse-N1

# lscpu > lscpu.old

Old/GDB:

# apt install gdb

# cat >lp2019856-reproducer.gdb &1 | grep -e '^\$' -e 'Model name:'
$1 = 0xaaad8570 "0xd0c"
$2 = (void *) 0xaaad8570
$3 = 0xaaad8570 "0xd15"
Model name:  -
$4 = 0xaaad8570 "0xd0c"
$5 = (void *) 0xaaad8570
$6 = 0xaaad8570 "0xd4f"
Model name:  -

New:

# add-apt-repository -y ppa:mfo/lp2019856
# sed -i '/Components:/ s,$, main/debug,' 
/etc/apt/sources.list.d/mfo-ubuntu-lp2019856-mantic.sources
# apt update
# apt install -y util-linux util-linux-dbgsym

# dpkg -s util-linux | grep Version:
Version: 2.38.1-5ubuntu2

# lscpu | grep -e 'Vendor ID:' -e 'Model name:'
Vendor ID:   ARM
Model name:  Neoverse-N1

# lscpu > lscpu.new
# diff lscpu.old lscpu.new
#

New/GDB:

# gdb -x lp2019856-reproducer.gdb lscpu 2>&1 | grep -e '^\$' -e 'Model 
name:'
$1 = 0xaaad8570 "0xd0c"
$2 = (void *) 0xaaad8570
$3 = 0xaaad8570 "0xd15"
Model name:  Cortex-R82
$4 = 0xaaad8570 "0xd0c"
$5 = (void *) 0xaaad8570
$6 = 0xaaad8570 "0xd4f"
Model name:  Neoverse-V2



Lunar
---


$ lxc launch ubuntu:lunar lunar
$ lxc shell lunar

# lsb_release -cs
No LSB modules are available.
lunar

Old:

# dpkg -s util-linux | grep Version:
Version: 2.38.1-4ubuntu1

# lscpu | grep -e 'Vendor ID:' -e 'Model name:'
Vendor ID:   ARM
Model name:  Neoverse-N1

# lscpu > lscpu.old
#

Old/GDB:

# apt install gdb
# export DEBUGINFOD_URLS="https://debuginfod.ubuntu.com;

# cat >lp2019856-reproducer.gdb <&1 | grep -e '^\$' -e 'Model name:'
$1 = 0xaaad8570 "0xd0c"
$2 = (void *) 0xaaad8570
$3 = 0xaaad8570 "0xd15"
Model name:  -
$4 = 0xaaad8570 "0xd0c"
$5 = (void *) 0xaaad8570
$6 = 0xaaad8570 "0xd4f"
Model name:  -

New:

# add-apt-repository -y ppa:mfo/lp2019856
# sed -i '/^deb .* main$/ s:$: main/debug:' 
/etc/apt/sources.list.d/mfo-ubuntu-lp2019856-lunar.list
# apt update
# apt install -y util-linux util-linux-dbgsym

# dpkg -s util-linux | grep Version:
Version: 2.38.1-4ubuntu1.1

# lscpu | grep -e 'Vendor ID:' -e 'Model name:'
Vendor ID:   ARM
Model name:  Neoverse-N1

# lscpu > lscpu.new
# diff lscpu.old lscpu.new
#

New/GDB:

# gdb -x lp2019856-reproducer.gdb lscpu 2>&1 | grep -e '^\$' -e 'Model 
name:'
$1 = 0xaaad8570 "0xd0c"
$2 = (void *) 0xaaad8570
$3 = 0xaaad8570 "0xd15"
Model name:  Cortex-R82
$4 = 0xaaad8570 "0xd0c"
$5 = (void *) 0xaaad8570
$6 = 0xaaad8570 "0xd4f"
Model name:  Neoverse-V2


Jammy
---

$ lxc launch ubuntu:jammy jammy
lxc shell jammy

# lsb_release -cs
jammy

Old:

# dpkg -s util-linux | grep Version:
Version: 2.37.2-4ubuntu3
#

# lscpu | grep -e 'Vendor ID:' -e 'Model name:'
Vendor ID:   ARM
Model name:  Neoverse-N1

# lscpu > lscpu.old

Old/GDB:

# wget 
https://launchpad.net/ubuntu/+archive/primary/+files/util-linux-dbgsym_2.37.2-4ubuntu3_arm64.ddeb
# apt install -y gdb ./util-linux-dbgsym_2.37.2-4ubuntu3_arm64.ddeb

* Jammy differences: break on arm_ids_decode() by line, and no
Model name if unknown.

# cat >lp2019856-reproducer-jammy.gdb <&1 | grep -e '^\$' -e 
'Model name:'
$1 = 0xaaacf5b0 "0xd0c"
$2 = (void *) 0xaaacf5b0
$3 = 0xaaacf5b0 "0xd15"
   

[Touch-packages] [Bug 2019856] Re: Add missing ARM-cores to support Grace-based systems

[Mauricio Faria de Oliveira]

Hey Heather, thanks for the updated debdiffs!

I've looked at them, and did minor fixes to DEP3
(moved them out of the original commit message, 
after `---`, and added Origin: fields), and just
a cosmetic adjustment to the changelog.

It turns out this patch isn't present in Mantic.
I already handled the debdiff/tests; don't worry.
I'll look for a sponsor for the devel release,
and handle the stable releases/SRUs afterward.

I marked Kinetic as won't fix, as it's not needed
and close to EOL anyway.

  $ ubuntu-distro-info --series=kinetic --days=eol
  58

I removed the verification tags you added? 
They are added automatically by the SRU machinery
when the packages land in -proposed for testing.

cheers,
Mauricio

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

Title:
  Add missing ARM-cores to support Grace-based systems

Status in util-linux package in Ubuntu:
  In Progress
Status in util-linux source package in Jammy:
  In Progress
Status in util-linux source package in Kinetic:
  Won't Fix
Status in util-linux source package in Lunar:
  In Progress
Status in util-linux source package in Mantic:
  In Progress

Bug description:
  [Impact]

  When running "lscpu" on a Grace-based system + Ubuntu 22.04, it
  doesn't report a model name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Jammy's
  version.

  https://github.com/util-linux/util-
  linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-V2

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems. 

  Output doesn't change on systems with non-affected CPU models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems

[Mauricio Faria de Oliveira]

** Description changed:

  [Impact]
- When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't 
report a model name:
+ 
+ When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't
+ report a model name:
  
  Vendor ID: ARM
  Model: 0
  
  [Fix]
- Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. 
The commit below adds the specific codes missing from Jammy's version.
+ 
+ Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
+ problem. The commit below adds the specific codes missing from Jammy's
+ version.
  
  https://github.com/util-linux/util-
  linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740
  
- [Evidence]
- When upstream code is compiled, output of lscpu is correctly displayed:
+ [Test Steps]
+ 
+ * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-V2
  
+ * Verify whether output of lscpu doesn't change on old CPUs; eg:
+ Vendor ID: ARM
+ Model name: Neoverse-N1
+ 
  [What Could Go Wrong]
- The fix does not apply directly to Jammy's version, as other commits change 
sys-utils/lscpu-arm.c. The suggestion is only to add the missing arm_part to 
the list.
+ 
+ The fix only introduces additional model identifiers to match
+ against and print a model name string, thus regression impact
+ should be contained within lscpu and printing cpus model name
+ on ARM systems. 
+ 
+ Output doesn't change on systems with non-affected CPU models.

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

Title:
  Add missing ARM-cores to support Grace-based systems

Status in util-linux package in Ubuntu:
  In Progress
Status in util-linux source package in Jammy:
  In Progress
Status in util-linux source package in Kinetic:
  Won't Fix
Status in util-linux source package in Lunar:
  In Progress
Status in util-linux source package in Mantic:
  In Progress

Bug description:
  [Impact]

  When running "lscpu" on a Grace-based system + Ubuntu 22.04, it
  doesn't report a model name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Jammy's
  version.

  https://github.com/util-linux/util-
  linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-V2

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems. 

  Output doesn't change on systems with non-affected CPU models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems

[Mauricio Faria de Oliveira]

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

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

** Changed in: util-linux (Ubuntu Kinetic)
   Status: New => Won't Fix

** Changed in: util-linux (Ubuntu Mantic)
   Status: New => In Progress

** Changed in: util-linux (Ubuntu Mantic)
 Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo)

** Tags removed: verification-needed-jammy verification-needed-lunar

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

Title:
  Add missing ARM-cores to support Grace-based systems

Status in util-linux package in Ubuntu:
  In Progress
Status in util-linux source package in Jammy:
  In Progress
Status in util-linux source package in Kinetic:
  Won't Fix
Status in util-linux source package in Lunar:
  In Progress
Status in util-linux source package in Mantic:
  In Progress

Bug description:
  [Impact]
  When running "lscpu" on a Grace-based system + Ubuntu 22.04, it doesn't 
report a model name:

  Vendor ID: ARM
  Model: 0

  [Fix]
  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the problem. 
The commit below adds the specific codes missing from Jammy's version.

  https://github.com/util-linux/util-
  linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740

  [Evidence]
  When upstream code is compiled, output of lscpu is correctly displayed:
  Vendor ID: ARM
  Model name: Neoverse-V2

  [What Could Go Wrong]
  The fix does not apply directly to Jammy's version, as other commits change 
sys-utils/lscpu-arm.c. The suggestion is only to add the missing arm_part to 
the list.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2020403] Re: Please merge 1.47.0-2 from debian/unstable

[Vladimir Petko]

1.47-2 adds patch which is already present in 1.47.0-1ubuntu1 with a
difference that ubuntu patch adds orphan_file feature.

Reject the merge.

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

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

Title:
  Please merge 1.47.0-2 from debian/unstable

Status in e2fsprogs package in Ubuntu:
  Invalid

Bug description:
  tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2020403/+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 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session

[Nick Rosbrook]

Workaround:

For me, when I reboot, the ssh.socket unit comes up again and I can
establish a session. To avoid continuously hitting the error in the
postint, run e.g. dpkg --configure -a from a non-ssh session, or script
this to happen once on reboot or something.

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

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh
  session

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2011458] Re: ssh fails to rebind when it is killed with -HUP

[Nick Rosbrook]

An issue (bug 2020474) has been reported in mantic which I believe is
caused by this patch, so I am adding block-proposed for lunar and
kinetic while I investigate.

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

Title:
  ssh fails to rebind when it is killed with -HUP

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Kinetic:
  Fix Committed
Status in openssh source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

  The sshd re-execution logic is generally broken with systemd socket 
activation, which means that (1) sshd fails when it is told to re-exec
  via SIGHUP (e.g. systemctl reload ssh), and (2) sshd fails when started in 
debug mode.

  [Test Case]

  (1) Test systemctl reload ssh:

  * On a machine with openssh-server installed, make a connection to
  localhost to activate ssh.service (the connection does not need to be
  complete, so you can just say "no" at the host key verification
  stage):

  $ ssh localhost
  [...]

  * Send SIGHUP to sshd by calling systemctl reload ssh:

  $ systemctl reload ssh

  * Check the service state:

  $ systemctl status ssh
  × ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: 
enabled)
  Drop-In: /etc/systemd/system/ssh.service.d
   └─00-socket.conf
   Active: failed (Result: exit-code) since Mon 2023-04-17 20:43:27 UTC; 4s 
ago
 Duration: 2min 44.132s
  TriggeredBy: ● ssh.socket
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 1112 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255/EXCEPTION)
  Process: 1152 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
  Process: 1153 ExecReload=/bin/kill -HUP $MAINPID (code=exited, 
status=0/SUCCESS)
 Main PID: 1112 (code=exited, status=255/EXCEPTION)
  CPU: 79ms

  Apr 17 20:40:43 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell 
server.
  Apr 17 20:41:06 lunar sshd[1113]: Connection closed by 127.0.0.1 port 54666 
[preauth]
  Apr 17 20:43:27 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure 
Shell server...
  Apr 17 20:43:27 lunar sshd[1112]: Received SIGHUP; restarting.
  Apr 17 20:43:27 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell 
server.
  Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on 0.0.0.0 failed: 
Address already in use.
  Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on :: failed: 
Address already in use.
  Apr 17 20:43:27 lunar sshd[1112]: fatal: Cannot bind any address.
  Apr 17 20:43:27 lunar systemd[1]: ssh.service: Main process exited, 
code=exited, status=255/EXCEPTION
  Apr 17 20:43:27 lunar systemd[1]: ssh.service: Failed with result 'exit-code'.

  * On an affected machine, the service will fail as shown above.

  (2) Test debug mode:

  * On a machine with openssh-server installed, edit /etc/default/ssh to
  configure debug mode for sshd:

  $ cat /etc/default/ssh 
  # Default settings for openssh-server. This file is sourced by /bin/sh from
  # /etc/init.d/ssh.

  # Options to pass to sshd
  SSHD_OPTS=-ddd

  * Attempt to make a connection to localhost:

  $ ssh localhost
  kex_exchange_identification: read: Connection reset by peer
  Connection reset by 127.0.0.1 port 22

  * On an affected machine, the attempt will fail as shown above, and
  the service will be in a failed state:

  $ systemctl status ssh
  × ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: 
enabled)
  Drop-In: /etc/systemd/system/ssh.service.d
   └─00-socket.conf
   Active: failed (Result: exit-code) since Mon 2023-04-17 20:46:34 UTC; 
2min 27s ago
 Duration: 5ms
  TriggeredBy: ● ssh.socket
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 1166 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=0/SUCCESS)
  Process: 1167 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255/EXCEPTION)
 Main PID: 1167 (code=exited, status=255/EXCEPTION)
  CPU: 40ms

  Apr 17 20:46:34 lunar sshd[1167]: Server listening on :: port 22.
  Apr 17 20:46:34 lunar sshd[1167]: debug3: fd 4 is not O_NONBLOCK
  Apr 17 20:46:34 lunar sshd[1167]: debug1: Server will not fork when running 
in debugging mode.
  Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: entering fd = 7 
config len 3456
  Apr 17 20:46:34 lunar sshd[1167]: debug3: ssh_msg_send: type 0
  Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: done
  Apr 17 20:46:34 lunar sshd[1167]: debug1: rexec start in 4 out 4 newsock 4 
pipe -1 sock 7
  Apr 17 20:46:34 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell 
server.
  Apr 17 20:46:34 lunar systemd[1]: ssh.service: Main process exited, 
code=exited, status=255/EXCEPTION
  

[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session

[Nick Rosbrook]

** Tags added: rls-mm-incoming

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh
  session

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2011458] Re: ssh fails to rebind when it is killed with -HUP

[Nick Rosbrook]

** Tags added: block-proposed-kinetic block-proposed-lunar

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

Title:
  ssh fails to rebind when it is killed with -HUP

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Kinetic:
  Fix Committed
Status in openssh source package in Lunar:
  Fix Committed

Bug description:
  [Impact]

  The sshd re-execution logic is generally broken with systemd socket 
activation, which means that (1) sshd fails when it is told to re-exec
  via SIGHUP (e.g. systemctl reload ssh), and (2) sshd fails when started in 
debug mode.

  [Test Case]

  (1) Test systemctl reload ssh:

  * On a machine with openssh-server installed, make a connection to
  localhost to activate ssh.service (the connection does not need to be
  complete, so you can just say "no" at the host key verification
  stage):

  $ ssh localhost
  [...]

  * Send SIGHUP to sshd by calling systemctl reload ssh:

  $ systemctl reload ssh

  * Check the service state:

  $ systemctl status ssh
  × ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: 
enabled)
  Drop-In: /etc/systemd/system/ssh.service.d
   └─00-socket.conf
   Active: failed (Result: exit-code) since Mon 2023-04-17 20:43:27 UTC; 4s 
ago
 Duration: 2min 44.132s
  TriggeredBy: ● ssh.socket
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 1112 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255/EXCEPTION)
  Process: 1152 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
  Process: 1153 ExecReload=/bin/kill -HUP $MAINPID (code=exited, 
status=0/SUCCESS)
 Main PID: 1112 (code=exited, status=255/EXCEPTION)
  CPU: 79ms

  Apr 17 20:40:43 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell 
server.
  Apr 17 20:41:06 lunar sshd[1113]: Connection closed by 127.0.0.1 port 54666 
[preauth]
  Apr 17 20:43:27 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure 
Shell server...
  Apr 17 20:43:27 lunar sshd[1112]: Received SIGHUP; restarting.
  Apr 17 20:43:27 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell 
server.
  Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on 0.0.0.0 failed: 
Address already in use.
  Apr 17 20:43:27 lunar sshd[1112]: error: Bind to port 22 on :: failed: 
Address already in use.
  Apr 17 20:43:27 lunar sshd[1112]: fatal: Cannot bind any address.
  Apr 17 20:43:27 lunar systemd[1]: ssh.service: Main process exited, 
code=exited, status=255/EXCEPTION
  Apr 17 20:43:27 lunar systemd[1]: ssh.service: Failed with result 'exit-code'.

  * On an affected machine, the service will fail as shown above.

  (2) Test debug mode:

  * On a machine with openssh-server installed, edit /etc/default/ssh to
  configure debug mode for sshd:

  $ cat /etc/default/ssh 
  # Default settings for openssh-server. This file is sourced by /bin/sh from
  # /etc/init.d/ssh.

  # Options to pass to sshd
  SSHD_OPTS=-ddd

  * Attempt to make a connection to localhost:

  $ ssh localhost
  kex_exchange_identification: read: Connection reset by peer
  Connection reset by 127.0.0.1 port 22

  * On an affected machine, the attempt will fail as shown above, and
  the service will be in a failed state:

  $ systemctl status ssh
  × ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: 
enabled)
  Drop-In: /etc/systemd/system/ssh.service.d
   └─00-socket.conf
   Active: failed (Result: exit-code) since Mon 2023-04-17 20:46:34 UTC; 
2min 27s ago
 Duration: 5ms
  TriggeredBy: ● ssh.socket
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 1166 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=0/SUCCESS)
  Process: 1167 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, 
status=255/EXCEPTION)
 Main PID: 1167 (code=exited, status=255/EXCEPTION)
  CPU: 40ms

  Apr 17 20:46:34 lunar sshd[1167]: Server listening on :: port 22.
  Apr 17 20:46:34 lunar sshd[1167]: debug3: fd 4 is not O_NONBLOCK
  Apr 17 20:46:34 lunar sshd[1167]: debug1: Server will not fork when running 
in debugging mode.
  Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: entering fd = 7 
config len 3456
  Apr 17 20:46:34 lunar sshd[1167]: debug3: ssh_msg_send: type 0
  Apr 17 20:46:34 lunar sshd[1167]: debug3: send_rexec_state: done
  Apr 17 20:46:34 lunar sshd[1167]: debug1: rexec start in 4 out 4 newsock 4 
pipe -1 sock 7
  Apr 17 20:46:34 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell 
server.
  Apr 17 20:46:34 lunar systemd[1]: ssh.service: Main process exited, 
code=exited, status=255/EXCEPTION
  Apr 17 20:46:34 lunar systemd[1]: ssh.service: Failed with result 'exit-code'.

  [Where problems could 

[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session

[Nick Rosbrook]

This appears to have to do with the patch addressing bug 2011458.

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh
  session

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation

[Nick Rosbrook]

You're right, I was able to reproduce this just now in the same way. I
also tried in Lunar, but Lunar does not appear to be affected.

** Summary changed:

- openssh-server-1:9.2p1-2ubuntu1 fails post-installation
+ openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session

** Changed in: openssh (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh
  session

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation

[scottfk]

root@venus2:/etc/systemd/system/ssh.service.d# /usr/sbin/sshd -d
debug1: sshd version OpenSSH_9.2, OpenSSL 3.0.8 7 Feb 2023
debug1: private host key #0: ssh-rsa 
SHA256:jBRj9thNiN3QA5SVICY9H4/b2f2tvIqyKv2krB+q1+E
debug1: private host key #1: ecdsa-sha2-nistp256 
SHA256:+AoeQEDs9PNiD54EnDi/YTJksSDND59lJqCe5BAgdz0
debug1: private host key #2: ssh-ed25519 
SHA256:fJj+sS6kyWxB/3Z36XR7DE7J1w9TYvR8GLRT0Kr+DNU
debug1: rexec_argv[0]='/usr/sbin/sshd'
debug1: rexec_argv[1]='-d'
debug1: Set /proc/self/oom_score_adj from 0 to -1000
debug1: Bind to port 22 on 0.0.0.0.
Bind to port 22 on 0.0.0.0 failed: Address already in use.
debug1: Bind to port 22 on ::.
Bind to port 22 on :: failed: Address already in use.
Cannot bind any address.

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 fails post-installation

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation

[scottfk]

root@venus2:/home/scottfk# systemctl restart ssh.socket
Job failed. See "journalctl -xe" for details.

May 23 20:36:21 venus2 systemd[2014]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
May 23 20:36:21 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
May 23 20:36:21 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
May 23 20:36:21 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit ssh.socket has entered the 'failed' state with result 'resources'.
May 23 20:36:21 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.
░░ Subject: A start job for unit ssh.socket has failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ A start job for unit ssh.socket has finished with a failure.
░░ 
░░ The job identifier is 1542 and the job result is failed.

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 fails post-installation

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

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


-- 
Mailing list: 

[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation

[scottfk]

So I tried this in an amd64 VM.  Installing this version of openssh-
server (from inside a GNOME session) worked just fine.

ssh-ing to localhost and attempting a reinstall ended up in the exact
same FAIL.

So it seems the upgrade of openssh-server 1:9.2p1-2ubuntu1 can't be done
from an ssh session (regardless of processor architecture).  I'll do
more poking around to see if I can't figure out why systemd won't/can't.

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 fails post-installation

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2020560] Re: ssh.service and ssh.socket both running.

[moose]

As I noted above, the key was restarting ssh.socket, not ssh. Even
though systemctl status ssh.socket reported (claimed) that the service
was listening on both 22 and 7022, this didn't come into effect until I
restarted ssh.socket. This last step was essential to getting this to
work. Restarting ssh.socket did not appear in any of the documentation
or Googling hits until I found this reference:
https://www.flatcar.org/docs/latest/setup/security/customizing-sshd/

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

Title:
  ssh.service and ssh.socket both running.

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 23.04. The out-of-the-box configuration allows SSH
  access on port 22. I wish to have ssh listen on both ports 22 and
  7022. The ssh_config file contains a comment that Ubuntu now uses
  socket activated connections and thus ignores the Port and
  ListenAddress entries. I looked up the ssh socket activation and found
  that I needed a /etc/systemd/system/ssh.socket.d directory that
  contains a listen.conf file. I created the directory and the
  listen.conf file that contains this.

  [Socket]
  # Uncomment the following line to turn of listening on port 22.
  #ListenStream=
  ListenStream=7022

  I then ran these two commands:
  sudo systemctl daemon-reload
  sudo systemctl restart ssh

  I then checked for port listeners:
  root# lsof -i -P -n | grep LISTEN
  systemd 1root  454u  IPv625979  0t0  TCP *:22 
(LISTEN)
  systemd-r 638 systemd-resolve   14u  IPv435332  0t0  TCP 
127.0.0.53:53 (LISTEN)
  systemd-r 638 systemd-resolve   16u  IPv435334  0t0  TCP 
127.0.0.54:53 (LISTEN)
  Xtigervnc 941   moose9u  IPv422485  0t0  TCP 
127.0.0.1:5902 (LISTEN)
  Xtigervnc 941   moose   10u  IPv622486  0t0  TCP 
[::1]:5902 (LISTEN)
  cupsd 2258639root6u  IPv6 33526334  0t0  TCP 
[::1]:631 (LISTEN)
  cupsd 2258639root7u  IPv4 33526335  0t0  TCP 
127.0.0.1:631 (LISTEN)
  sshd  3698765root3u  IPv625979  0t0  TCP *:22 
(LISTEN)

  I then discovered that both ssh.service and ssh.socket are running:
  root@/etc/netplan# systemctl status ssh.service
  ? ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: 
enabled)
  Drop-In: /etc/systemd/system/ssh.service.d
   ??00-socket.conf
   Active: active (running) since Tue 2023-05-23 11:17:29 EDT; 36min ago
  TriggeredBy: ? ssh.socket
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 3698763 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=0/SUCCESS)
 Main PID: 3698765 (sshd)
Tasks: 3 (limit: 38046)
   Memory: 3.6M
  CPU: 206ms
   CGroup: /system.slice/ssh.service
   ??3698765 "sshd: /usr/sbin/sshd -D [listener] 1 of 10-100 
startups"
   ??3777496 "sshd: root [priv]"
   ??3777497 "sshd: root [net]"

  May 23 11:51:44 alces sshd[3771657]: ...
  Hint: Some lines were ellipsized, use -l to show in full.
  root@/etc/netplan# systemctl status ssh.socket
  ? ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   ??listen.conf
   Active: active (running) since Mon 2023-05-15 09:23:44 EDT; 1 week 1 day 
ago
Until: Mon 2023-05-15 09:23:44 EDT; 1 week 1 day ago
 Triggers: ? ssh.service
   Listen: [::]:22 (Stream)
   [::]:7022 (Stream)
Tasks: 0 (limit: 38046)
   Memory: 8.0K
  CPU: 569us
   CGroup: /system.slice/ssh.socket

  May 15 09:23:44 alces systemd[1]: ...
  Hint: Some lines were ellipsized, use -l to show in full.

  
  Finally, I found that /lib/systemd/system contains both ssh.service and 
ssh.socket configurations.
  ssh.service:
  [Unit]
  Description=OpenBSD Secure Shell server
  Documentation=man:sshd(8) man:sshd_config(5)
  After=network.target auditd.service
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Service]
  EnvironmentFile=-/etc/default/ssh
  ExecStartPre=/usr/sbin/sshd -t
  ExecStart=/usr/sbin/sshd -D $SSHD_OPTS
  ExecReload=/usr/sbin/sshd -t
  ExecReload=/bin/kill -HUP $MAINPID
  KillMode=process
  Restart=on-failure
  RestartPreventExitStatus=255
  Type=notify

  [Install]
  WantedBy=multi-user.target
  Alias=sshd.service

  ssh.socket:
  [Unit]
  Description=OpenBSD Secure Shell server socket
  Before=sockets.target
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Socket]
  ListenStream=22
  Accept=no

  [Install]
  WantedBy=sockets.target

  Finally, in /etc/systemd/system there is an ssh.service.d directory
  that contains the 00-socket.conf 

[Touch-packages] [Bug 2020560] Re: ssh.service and ssh.socket both running.

[Nick Rosbrook]

According to your output from `systemctl status ssh.socket`, it is
listening on both ports. But, to be sure, I tried this in a fresh 23.04
container:

root@lunar:~# systemctl edit ssh.socket # This opens a text editor to create 
/etc/systemd/system/ssh.socket.d/override.conf 
root@lunar:~# cat /etc/systemd/system/ssh.socket.d/override.conf 
[Socket]
ListenStream=7022
root@lunar:~# systemctl daemon-reload
root@lunar:~# systemctl restart ssh.socket
root@lunar:~# systemctl status ssh.socket
● ssh.socket - OpenBSD Secure Shell server socket
 Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
Drop-In: /etc/systemd/system/ssh.socket.d
 └─override.conf
 Active: active (listening) since Tue 2023-05-23 18:03:31 UTC; 3s ago
  Until: Tue 2023-05-23 18:03:31 UTC; 3s ago
   Triggers: ● ssh.service
 Listen: [::]:22 (Stream)
 [::]:7022 (Stream)
 CGroup: /system.slice/ssh.socket

May 23 18:03:31 lunar systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
May 23 18:03:31 lunar systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.

Then, after copying my public key to the server, I was able to connect
to the instance with:

$ ssh -p 7022 root@10.136.78.53

After that, the server shows:

root@lunar:~# lsof -i :7022
COMMAND  PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
systemd1 root   28u  IPv6 5619190  0t0  TCP *:7022 (LISTEN)
sshd1054 root4u  IPv6 5619190  0t0  TCP *:7022 (LISTEN)
sshd1055 root4u  IPv6 5613043  0t0  TCP 
lunar.lxd:7022->_gateway.lxd:50488 (ESTABLISHED)

Also, configuration files in /etc/systemd/ override corresponding files
in /lib/systemd/. See
https://www.freedesktop.org/software/systemd/man/systemd.unit.html#System%20Unit%20Search%20Path.

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

Title:
  ssh.service and ssh.socket both running.

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 23.04. The out-of-the-box configuration allows SSH
  access on port 22. I wish to have ssh listen on both ports 22 and
  7022. The ssh_config file contains a comment that Ubuntu now uses
  socket activated connections and thus ignores the Port and
  ListenAddress entries. I looked up the ssh socket activation and found
  that I needed a /etc/systemd/system/ssh.socket.d directory that
  contains a listen.conf file. I created the directory and the
  listen.conf file that contains this.

  [Socket]
  # Uncomment the following line to turn of listening on port 22.
  #ListenStream=
  ListenStream=7022

  I then ran these two commands:
  sudo systemctl daemon-reload
  sudo systemctl restart ssh

  I then checked for port listeners:
  root# lsof -i -P -n | grep LISTEN
  systemd 1root  454u  IPv625979  0t0  TCP *:22 
(LISTEN)
  systemd-r 638 systemd-resolve   14u  IPv435332  0t0  TCP 
127.0.0.53:53 (LISTEN)
  systemd-r 638 systemd-resolve   16u  IPv435334  0t0  TCP 
127.0.0.54:53 (LISTEN)
  Xtigervnc 941   moose9u  IPv422485  0t0  TCP 
127.0.0.1:5902 (LISTEN)
  Xtigervnc 941   moose   10u  IPv622486  0t0  TCP 
[::1]:5902 (LISTEN)
  cupsd 2258639root6u  IPv6 33526334  0t0  TCP 
[::1]:631 (LISTEN)
  cupsd 2258639root7u  IPv4 33526335  0t0  TCP 
127.0.0.1:631 (LISTEN)
  sshd  3698765root3u  IPv625979  0t0  TCP *:22 
(LISTEN)

  I then discovered that both ssh.service and ssh.socket are running:
  root@/etc/netplan# systemctl status ssh.service
  ? ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: 
enabled)
  Drop-In: /etc/systemd/system/ssh.service.d
   ??00-socket.conf
   Active: active (running) since Tue 2023-05-23 11:17:29 EDT; 36min ago
  TriggeredBy: ? ssh.socket
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 3698763 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=0/SUCCESS)
 Main PID: 3698765 (sshd)
Tasks: 3 (limit: 38046)
   Memory: 3.6M
  CPU: 206ms
   CGroup: /system.slice/ssh.service
   ??3698765 "sshd: /usr/sbin/sshd -D [listener] 1 of 10-100 
startups"
   ??3777496 "sshd: root [priv]"
   ??3777497 "sshd: root [net]"

  May 23 11:51:44 alces sshd[3771657]: ...
  Hint: Some lines were ellipsized, use -l to show in full.
  root@/etc/netplan# systemctl status ssh.socket
  ? ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   ??listen.conf
   Active: active (running) since Mon 2023-05-15 09:23:44 EDT; 1 week 1 day 
ago

[Touch-packages] [Bug 2020560] Re: ssh.service and ssh.socket both running.

[moose]

Ok. The solution to this problem was to restart not ssh.service but ssh.socket. 
Thus:
sudo systemctl daemon-reload
sudo systemctl restart ssh.socket

I think the documentation, such as it is, should make this clear.
Googling around gets you several hits that say you should sudo systemctl
restart ssh (which is ssh.service) which is incorrect.

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

Title:
  ssh.service and ssh.socket both running.

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 23.04. The out-of-the-box configuration allows SSH
  access on port 22. I wish to have ssh listen on both ports 22 and
  7022. The ssh_config file contains a comment that Ubuntu now uses
  socket activated connections and thus ignores the Port and
  ListenAddress entries. I looked up the ssh socket activation and found
  that I needed a /etc/systemd/system/ssh.socket.d directory that
  contains a listen.conf file. I created the directory and the
  listen.conf file that contains this.

  [Socket]
  # Uncomment the following line to turn of listening on port 22.
  #ListenStream=
  ListenStream=7022

  I then ran these two commands:
  sudo systemctl daemon-reload
  sudo systemctl restart ssh

  I then checked for port listeners:
  root# lsof -i -P -n | grep LISTEN
  systemd 1root  454u  IPv625979  0t0  TCP *:22 
(LISTEN)
  systemd-r 638 systemd-resolve   14u  IPv435332  0t0  TCP 
127.0.0.53:53 (LISTEN)
  systemd-r 638 systemd-resolve   16u  IPv435334  0t0  TCP 
127.0.0.54:53 (LISTEN)
  Xtigervnc 941   moose9u  IPv422485  0t0  TCP 
127.0.0.1:5902 (LISTEN)
  Xtigervnc 941   moose   10u  IPv622486  0t0  TCP 
[::1]:5902 (LISTEN)
  cupsd 2258639root6u  IPv6 33526334  0t0  TCP 
[::1]:631 (LISTEN)
  cupsd 2258639root7u  IPv4 33526335  0t0  TCP 
127.0.0.1:631 (LISTEN)
  sshd  3698765root3u  IPv625979  0t0  TCP *:22 
(LISTEN)

  I then discovered that both ssh.service and ssh.socket are running:
  root@/etc/netplan# systemctl status ssh.service
  ? ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: 
enabled)
  Drop-In: /etc/systemd/system/ssh.service.d
   ??00-socket.conf
   Active: active (running) since Tue 2023-05-23 11:17:29 EDT; 36min ago
  TriggeredBy: ? ssh.socket
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 3698763 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=0/SUCCESS)
 Main PID: 3698765 (sshd)
Tasks: 3 (limit: 38046)
   Memory: 3.6M
  CPU: 206ms
   CGroup: /system.slice/ssh.service
   ??3698765 "sshd: /usr/sbin/sshd -D [listener] 1 of 10-100 
startups"
   ??3777496 "sshd: root [priv]"
   ??3777497 "sshd: root [net]"

  May 23 11:51:44 alces sshd[3771657]: ...
  Hint: Some lines were ellipsized, use -l to show in full.
  root@/etc/netplan# systemctl status ssh.socket
  ? ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   ??listen.conf
   Active: active (running) since Mon 2023-05-15 09:23:44 EDT; 1 week 1 day 
ago
Until: Mon 2023-05-15 09:23:44 EDT; 1 week 1 day ago
 Triggers: ? ssh.service
   Listen: [::]:22 (Stream)
   [::]:7022 (Stream)
Tasks: 0 (limit: 38046)
   Memory: 8.0K
  CPU: 569us
   CGroup: /system.slice/ssh.socket

  May 15 09:23:44 alces systemd[1]: ...
  Hint: Some lines were ellipsized, use -l to show in full.

  
  Finally, I found that /lib/systemd/system contains both ssh.service and 
ssh.socket configurations.
  ssh.service:
  [Unit]
  Description=OpenBSD Secure Shell server
  Documentation=man:sshd(8) man:sshd_config(5)
  After=network.target auditd.service
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Service]
  EnvironmentFile=-/etc/default/ssh
  ExecStartPre=/usr/sbin/sshd -t
  ExecStart=/usr/sbin/sshd -D $SSHD_OPTS
  ExecReload=/usr/sbin/sshd -t
  ExecReload=/bin/kill -HUP $MAINPID
  KillMode=process
  Restart=on-failure
  RestartPreventExitStatus=255
  Type=notify

  [Install]
  WantedBy=multi-user.target
  Alias=sshd.service

  ssh.socket:
  [Unit]
  Description=OpenBSD Secure Shell server socket
  Before=sockets.target
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Socket]
  ListenStream=22
  Accept=no

  [Install]
  WantedBy=sockets.target

  Finally, in /etc/systemd/system there is an ssh.service.d directory
  that contains the 00-socket.conf file that contains:

  [Unit]
  After=ssh.socket
  Requires=ssh.socket

  
  This is very confusing. I could disable 

[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation

[scottfk]

Before retriggering the post-installation:

root@venus2:/home/scottfk# systemctl status 904
● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
Drop-In: /etc/systemd/system/ssh.service.d
 └─00-socket.conf
 Active: active (running) since Tue 2023-05-23 15:17:36 CEST; 4h 40min ago
TriggeredBy: ● ssh.socket
   Docs: man:sshd(8)
 man:sshd_config(5)
   Main PID: 904 (sshd)
  Tasks: 1 (limit: 9378)
 Memory: 5.1M
CPU: 468ms
 CGroup: /system.slice/ssh.service
 └─904 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

May 23 15:17:35 venus2 systemd[1]: Starting ssh.service - OpenBSD Secure Shell 
server...
May 23 15:17:36 venus2 sshd[904]: Server listening on :: port 22.
May 23 15:17:36 venus2 systemd[1]: Started ssh.service - OpenBSD Secure Shell 
server.
May 23 15:17:36 venus2 sshd[905]: Accepted publickey for scottfk from 
2a02:1210:2a23:5600:9e82:2fb7:9772:3bf6 port 4092>
May 23 15:17:36 venus2 sshd[905]: pam_unix(sshd:session): session opened for 
user scottfk(uid=1000) by (uid=0)
root@venus2:/home/scottfk# systemctl status 905
● session-2.scope - Session 2 of User scottfk
 Loaded: loaded (/run/systemd/transient/session-2.scope; transient)
  Transient: yes
 Active: active (running) since Tue 2023-05-23 15:17:37 CEST; 4h 41min ago
  Tasks: 8
 Memory: 18.2M
CPU: 4.330s
 CGroup: /user.slice/user-1000.slice/session-2.scope
 ├─ 905 "sshd: scottfk [priv]"
 ├─ 997 "sshd: scottfk@pts/0"
 ├─ 998 -bash
 ├─1113 sudo bash -o vi
 ├─1114 sudo bash -o vi
 ├─1115 bash -o vi
 ├─1301 systemctl status 905
 └─1302 less

May 23 15:17:37 venus2 systemd[1]: Started session-2.scope - Session 2 of User 
scottfk.
May 23 15:17:41 venus2 sshd[905]: pam_env(sshd:session): deprecated reading of 
user environment enabled
May 23 17:41:33 venus2 sudo[1108]:  scottfk : TTY=pts/0 ; PWD=/home/scottfk ; 
USER=root ; COMMAND=/usr/bin/lsof -i :22
May 23 17:41:33 venus2 sudo[1108]: pam_unix(sudo:session): session opened for 
user root(uid=0) by scottfk(uid=1000)
May 23 17:41:33 venus2 sudo[1108]: pam_unix(sudo:session): session closed for 
user root
May 23 17:42:20 venus2 sudo[1113]:  scottfk : TTY=pts/0 ; PWD=/home/scottfk ; 
USER=root ; COMMAND=/usr/bin/bash -o vi
May 23 17:42:20 venus2 sudo[1113]: pam_unix(sudo:session): session opened for 
user root(uid=0) by scottfk(uid=1000)
root@venus2:/home/scottfk# systemctl status 997
● session-2.scope - Session 2 of User scottfk
 Loaded: loaded (/run/systemd/transient/session-2.scope; transient)
  Transient: yes
 Active: active (running) since Tue 2023-05-23 15:17:37 CEST; 4h 41min ago
  Tasks: 8
 Memory: 18.3M
CPU: 4.376s
 CGroup: /user.slice/user-1000.slice/session-2.scope
 ├─ 905 "sshd: scottfk [priv]"
 ├─ 997 "sshd: scottfk@pts/0"
 ├─ 998 -bash
 ├─1113 sudo bash -o vi
 ├─1114 sudo bash -o vi
 ├─1115 bash -o vi
 ├─1304 systemctl status 997
 └─1305 less

May 23 15:17:37 venus2 systemd[1]: Started session-2.scope - Session 2 of User 
scottfk.
May 23 15:17:41 venus2 sshd[905]: pam_env(sshd:session): deprecated reading of 
user environment enabled
May 23 17:41:33 venus2 sudo[1108]:  scottfk : TTY=pts/0 ; PWD=/home/scottfk ; 
USER=root ; COMMAND=/usr/bin/lsof -i :22
May 23 17:41:33 venus2 sudo[1108]: pam_unix(sudo:session): session opened for 
user root(uid=0) by scottfk(uid=1000)
May 23 17:41:33 venus2 sudo[1108]: pam_unix(sudo:session): session closed for 
user root
May 23 17:42:20 venus2 sudo[1113]:  scottfk : TTY=pts/0 ; PWD=/home/scottfk ; 
USER=root ; COMMAND=/usr/bin/bash -o vi
May 23 17:42:20 venus2 sudo[1113]: pam_unix(sudo:session): session opened for 
user root(uid=0) by scottfk(uid=1000)

Retriggering the post-installation:
root@venus2:/home/scottfk# dpkg --configure -a
Setting up openssh-server (1:9.2p1-2ubuntu1) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 openssh-server
root@venus2:/home/scottfk# systemctl status 904
Failed to get unit for PID 904: PID 904 does not belong to any loaded unit.
root@venus2:/home/scottfk# systemctl status 905
● session-2.scope - Session 2 of User scottfk
 Loaded: loaded (/run/systemd/transient/session-2.scope; transient)
  Transient: yes
 Active: active (running) since Tue 2023-05-23 15:17:37 CEST; 4h 43min ago
  Tasks: 8
 Memory: 33.6M
CPU: 9.657s
 CGroup: /user.slice/user-1000.slice/session-2.scope
 ├─ 905 "sshd: scottfk 

[Touch-packages] [Bug 2020560] Re: ssh.service and ssh.socket both running.

[moose]

Thank you for the prompt reply. If my configuration is correct, why is
it that I cannot connect on port 7022? I don't see a listener for it, so
I suspect my configuration in
/etc/systemd/system/ssh.socket.d/listen.conf is either not being read or
is being supplanted by the configuration in
/lib/systemd/system/ssh.socket (which only specifies ListenStream=22).

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

Title:
  ssh.service and ssh.socket both running.

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 23.04. The out-of-the-box configuration allows SSH
  access on port 22. I wish to have ssh listen on both ports 22 and
  7022. The ssh_config file contains a comment that Ubuntu now uses
  socket activated connections and thus ignores the Port and
  ListenAddress entries. I looked up the ssh socket activation and found
  that I needed a /etc/systemd/system/ssh.socket.d directory that
  contains a listen.conf file. I created the directory and the
  listen.conf file that contains this.

  [Socket]
  # Uncomment the following line to turn of listening on port 22.
  #ListenStream=
  ListenStream=7022

  I then ran these two commands:
  sudo systemctl daemon-reload
  sudo systemctl restart ssh

  I then checked for port listeners:
  root# lsof -i -P -n | grep LISTEN
  systemd 1root  454u  IPv625979  0t0  TCP *:22 
(LISTEN)
  systemd-r 638 systemd-resolve   14u  IPv435332  0t0  TCP 
127.0.0.53:53 (LISTEN)
  systemd-r 638 systemd-resolve   16u  IPv435334  0t0  TCP 
127.0.0.54:53 (LISTEN)
  Xtigervnc 941   moose9u  IPv422485  0t0  TCP 
127.0.0.1:5902 (LISTEN)
  Xtigervnc 941   moose   10u  IPv622486  0t0  TCP 
[::1]:5902 (LISTEN)
  cupsd 2258639root6u  IPv6 33526334  0t0  TCP 
[::1]:631 (LISTEN)
  cupsd 2258639root7u  IPv4 33526335  0t0  TCP 
127.0.0.1:631 (LISTEN)
  sshd  3698765root3u  IPv625979  0t0  TCP *:22 
(LISTEN)

  I then discovered that both ssh.service and ssh.socket are running:
  root@/etc/netplan# systemctl status ssh.service
  ? ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: 
enabled)
  Drop-In: /etc/systemd/system/ssh.service.d
   ??00-socket.conf
   Active: active (running) since Tue 2023-05-23 11:17:29 EDT; 36min ago
  TriggeredBy: ? ssh.socket
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 3698763 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=0/SUCCESS)
 Main PID: 3698765 (sshd)
Tasks: 3 (limit: 38046)
   Memory: 3.6M
  CPU: 206ms
   CGroup: /system.slice/ssh.service
   ??3698765 "sshd: /usr/sbin/sshd -D [listener] 1 of 10-100 
startups"
   ??3777496 "sshd: root [priv]"
   ??3777497 "sshd: root [net]"

  May 23 11:51:44 alces sshd[3771657]: ...
  Hint: Some lines were ellipsized, use -l to show in full.
  root@/etc/netplan# systemctl status ssh.socket
  ? ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   ??listen.conf
   Active: active (running) since Mon 2023-05-15 09:23:44 EDT; 1 week 1 day 
ago
Until: Mon 2023-05-15 09:23:44 EDT; 1 week 1 day ago
 Triggers: ? ssh.service
   Listen: [::]:22 (Stream)
   [::]:7022 (Stream)
Tasks: 0 (limit: 38046)
   Memory: 8.0K
  CPU: 569us
   CGroup: /system.slice/ssh.socket

  May 15 09:23:44 alces systemd[1]: ...
  Hint: Some lines were ellipsized, use -l to show in full.

  
  Finally, I found that /lib/systemd/system contains both ssh.service and 
ssh.socket configurations.
  ssh.service:
  [Unit]
  Description=OpenBSD Secure Shell server
  Documentation=man:sshd(8) man:sshd_config(5)
  After=network.target auditd.service
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Service]
  EnvironmentFile=-/etc/default/ssh
  ExecStartPre=/usr/sbin/sshd -t
  ExecStart=/usr/sbin/sshd -D $SSHD_OPTS
  ExecReload=/usr/sbin/sshd -t
  ExecReload=/bin/kill -HUP $MAINPID
  KillMode=process
  Restart=on-failure
  RestartPreventExitStatus=255
  Type=notify

  [Install]
  WantedBy=multi-user.target
  Alias=sshd.service

  ssh.socket:
  [Unit]
  Description=OpenBSD Secure Shell server socket
  Before=sockets.target
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Socket]
  ListenStream=22
  Accept=no

  [Install]
  WantedBy=sockets.target

  Finally, in /etc/systemd/system there is an ssh.service.d directory
  that contains the 00-socket.conf file that contains:

  [Unit]
  After=ssh.socket
  Requires=ssh.socket

  
  This is very confusing. I 

[Touch-packages] [Bug 2020560] Re: ssh.service and ssh.socket both running.

[Nick Rosbrook]

It is expected that you have both ssh.socket and ssh.service on your
system. The ssh.socket unit is enabled by default and is responsible for
listening on the configured port. Once it receives a connection it
activates ssh.service (which is what actually spawns sshd).

As the comment in /etc/ssh/sshd_config explains, sshd_config(5) and
contain additional documentation about how to configure a non-default
port. It may help to read about systemd socket units as well [1].

>From what I can tell, you have taken the correct steps to enable port
7022. I do not think there is a bug here, but please let me know if you
think I am missing something.

[1] https://www.freedesktop.org/software/systemd/man/systemd.socket.html

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

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

Title:
  ssh.service and ssh.socket both running.

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I am running Ubuntu 23.04. The out-of-the-box configuration allows SSH
  access on port 22. I wish to have ssh listen on both ports 22 and
  7022. The ssh_config file contains a comment that Ubuntu now uses
  socket activated connections and thus ignores the Port and
  ListenAddress entries. I looked up the ssh socket activation and found
  that I needed a /etc/systemd/system/ssh.socket.d directory that
  contains a listen.conf file. I created the directory and the
  listen.conf file that contains this.

  [Socket]
  # Uncomment the following line to turn of listening on port 22.
  #ListenStream=
  ListenStream=7022

  I then ran these two commands:
  sudo systemctl daemon-reload
  sudo systemctl restart ssh

  I then checked for port listeners:
  root# lsof -i -P -n | grep LISTEN
  systemd 1root  454u  IPv625979  0t0  TCP *:22 
(LISTEN)
  systemd-r 638 systemd-resolve   14u  IPv435332  0t0  TCP 
127.0.0.53:53 (LISTEN)
  systemd-r 638 systemd-resolve   16u  IPv435334  0t0  TCP 
127.0.0.54:53 (LISTEN)
  Xtigervnc 941   moose9u  IPv422485  0t0  TCP 
127.0.0.1:5902 (LISTEN)
  Xtigervnc 941   moose   10u  IPv622486  0t0  TCP 
[::1]:5902 (LISTEN)
  cupsd 2258639root6u  IPv6 33526334  0t0  TCP 
[::1]:631 (LISTEN)
  cupsd 2258639root7u  IPv4 33526335  0t0  TCP 
127.0.0.1:631 (LISTEN)
  sshd  3698765root3u  IPv625979  0t0  TCP *:22 
(LISTEN)

  I then discovered that both ssh.service and ssh.socket are running:
  root@/etc/netplan# systemctl status ssh.service
  ? ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: 
enabled)
  Drop-In: /etc/systemd/system/ssh.service.d
   ??00-socket.conf
   Active: active (running) since Tue 2023-05-23 11:17:29 EDT; 36min ago
  TriggeredBy: ? ssh.socket
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 3698763 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=0/SUCCESS)
 Main PID: 3698765 (sshd)
Tasks: 3 (limit: 38046)
   Memory: 3.6M
  CPU: 206ms
   CGroup: /system.slice/ssh.service
   ??3698765 "sshd: /usr/sbin/sshd -D [listener] 1 of 10-100 
startups"
   ??3777496 "sshd: root [priv]"
   ??3777497 "sshd: root [net]"

  May 23 11:51:44 alces sshd[3771657]: ...
  Hint: Some lines were ellipsized, use -l to show in full.
  root@/etc/netplan# systemctl status ssh.socket
  ? ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   ??listen.conf
   Active: active (running) since Mon 2023-05-15 09:23:44 EDT; 1 week 1 day 
ago
Until: Mon 2023-05-15 09:23:44 EDT; 1 week 1 day ago
 Triggers: ? ssh.service
   Listen: [::]:22 (Stream)
   [::]:7022 (Stream)
Tasks: 0 (limit: 38046)
   Memory: 8.0K
  CPU: 569us
   CGroup: /system.slice/ssh.socket

  May 15 09:23:44 alces systemd[1]: ...
  Hint: Some lines were ellipsized, use -l to show in full.

  
  Finally, I found that /lib/systemd/system contains both ssh.service and 
ssh.socket configurations.
  ssh.service:
  [Unit]
  Description=OpenBSD Secure Shell server
  Documentation=man:sshd(8) man:sshd_config(5)
  After=network.target auditd.service
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Service]
  EnvironmentFile=-/etc/default/ssh
  ExecStartPre=/usr/sbin/sshd -t
  ExecStart=/usr/sbin/sshd -D $SSHD_OPTS
  ExecReload=/usr/sbin/sshd -t
  ExecReload=/bin/kill -HUP $MAINPID
  KillMode=process
  Restart=on-failure
  RestartPreventExitStatus=255
  Type=notify

  [Install]
  WantedBy=multi-user.target
  Alias=sshd.service

  

[Touch-packages] [Bug 2020560] Re: ssh.service and ssh.socket both running.

[moose]

This is probably not a bug related to ssh but to the configuration
changes introduced by Ubuntu.

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

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

Title:
  ssh.service and ssh.socket both running.

Status in openssh package in Ubuntu:
  New

Bug description:
  I am running Ubuntu 23.04. The out-of-the-box configuration allows SSH
  access on port 22. I wish to have ssh listen on both ports 22 and
  7022. The ssh_config file contains a comment that Ubuntu now uses
  socket activated connections and thus ignores the Port and
  ListenAddress entries. I looked up the ssh socket activation and found
  that I needed a /etc/systemd/system/ssh.socket.d directory that
  contains a listen.conf file. I created the directory and the
  listen.conf file that contains this.

  [Socket]
  # Uncomment the following line to turn of listening on port 22.
  #ListenStream=
  ListenStream=7022

  I then ran these two commands:
  sudo systemctl daemon-reload
  sudo systemctl restart ssh

  I then checked for port listeners:
  root# lsof -i -P -n | grep LISTEN
  systemd 1root  454u  IPv625979  0t0  TCP *:22 
(LISTEN)
  systemd-r 638 systemd-resolve   14u  IPv435332  0t0  TCP 
127.0.0.53:53 (LISTEN)
  systemd-r 638 systemd-resolve   16u  IPv435334  0t0  TCP 
127.0.0.54:53 (LISTEN)
  Xtigervnc 941   moose9u  IPv422485  0t0  TCP 
127.0.0.1:5902 (LISTEN)
  Xtigervnc 941   moose   10u  IPv622486  0t0  TCP 
[::1]:5902 (LISTEN)
  cupsd 2258639root6u  IPv6 33526334  0t0  TCP 
[::1]:631 (LISTEN)
  cupsd 2258639root7u  IPv4 33526335  0t0  TCP 
127.0.0.1:631 (LISTEN)
  sshd  3698765root3u  IPv625979  0t0  TCP *:22 
(LISTEN)

  I then discovered that both ssh.service and ssh.socket are running:
  root@/etc/netplan# systemctl status ssh.service
  ? ssh.service - OpenBSD Secure Shell server
   Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: 
enabled)
  Drop-In: /etc/systemd/system/ssh.service.d
   ??00-socket.conf
   Active: active (running) since Tue 2023-05-23 11:17:29 EDT; 36min ago
  TriggeredBy: ? ssh.socket
 Docs: man:sshd(8)
   man:sshd_config(5)
  Process: 3698763 ExecStartPre=/usr/sbin/sshd -t (code=exited, 
status=0/SUCCESS)
 Main PID: 3698765 (sshd)
Tasks: 3 (limit: 38046)
   Memory: 3.6M
  CPU: 206ms
   CGroup: /system.slice/ssh.service
   ??3698765 "sshd: /usr/sbin/sshd -D [listener] 1 of 10-100 
startups"
   ??3777496 "sshd: root [priv]"
   ??3777497 "sshd: root [net]"

  May 23 11:51:44 alces sshd[3771657]: ...
  Hint: Some lines were ellipsized, use -l to show in full.
  root@/etc/netplan# systemctl status ssh.socket
  ? ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
  Drop-In: /etc/systemd/system/ssh.socket.d
   ??listen.conf
   Active: active (running) since Mon 2023-05-15 09:23:44 EDT; 1 week 1 day 
ago
Until: Mon 2023-05-15 09:23:44 EDT; 1 week 1 day ago
 Triggers: ? ssh.service
   Listen: [::]:22 (Stream)
   [::]:7022 (Stream)
Tasks: 0 (limit: 38046)
   Memory: 8.0K
  CPU: 569us
   CGroup: /system.slice/ssh.socket

  May 15 09:23:44 alces systemd[1]: ...
  Hint: Some lines were ellipsized, use -l to show in full.

  
  Finally, I found that /lib/systemd/system contains both ssh.service and 
ssh.socket configurations.
  ssh.service:
  [Unit]
  Description=OpenBSD Secure Shell server
  Documentation=man:sshd(8) man:sshd_config(5)
  After=network.target auditd.service
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Service]
  EnvironmentFile=-/etc/default/ssh
  ExecStartPre=/usr/sbin/sshd -t
  ExecStart=/usr/sbin/sshd -D $SSHD_OPTS
  ExecReload=/usr/sbin/sshd -t
  ExecReload=/bin/kill -HUP $MAINPID
  KillMode=process
  Restart=on-failure
  RestartPreventExitStatus=255
  Type=notify

  [Install]
  WantedBy=multi-user.target
  Alias=sshd.service

  ssh.socket:
  [Unit]
  Description=OpenBSD Secure Shell server socket
  Before=sockets.target
  ConditionPathExists=!/etc/ssh/sshd_not_to_be_run

  [Socket]
  ListenStream=22
  Accept=no

  [Install]
  WantedBy=sockets.target

  Finally, in /etc/systemd/system there is an ssh.service.d directory
  that contains the 00-socket.conf file that contains:

  [Unit]
  After=ssh.socket
  Requires=ssh.socket

  
  This is very confusing. I could disable ssh.service, but I am concerned that 
if I do this I will lose ssh connectivity to my headless server. What is the 
way out of this morass? It would be VERY helpful if there was a comprehensive 
guide to the 

[Touch-packages] [Bug 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation

[Nick Rosbrook]

Yeah that does look a bit odd. What do the following show?

# systemctl status 904
# systemctl status 905
# systemctl status 997

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 fails post-installation

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2020470] Re: Please merge 1.9.13p3-1 into mantic

[Danilo Egea Gondolfo]

** Attachment added: "Autopkgtest logs for amd64"
   
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2020470/+attachment/5675003/+files/autopkgtest_logs.gz

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

Title:
  Please merge 1.9.13p3-1 into mantic

Status in sudo package in Ubuntu:
  New

Bug description:
  tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2020470/+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 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation

[scottfk]

# lsof -i :22
COMMAND PIDUSER   FD   TYPE DEVICE SIZE/OFF NODE NAME
systemd   1root  140u  IPv6  22354  0t0  TCP *:ssh (LISTEN)
sshd904root3u  IPv6  22354  0t0  TCP *:ssh (LISTEN)
sshd905root3u  IPv6  22354  0t0  TCP *:ssh (LISTEN)
sshd905root4u  IPv6  18405  0t0  TCP 
venus2.home:ssh->hydra.home:40926 (ESTABLISHED)
sshd905root5u  IPv6  18405  0t0  TCP 
venus2.home:ssh->hydra.home:40926 (ESTABLISHED)
sshd997 scottfk3u  IPv6  22354  0t0  TCP *:ssh (LISTEN)
sshd997 scottfk4u  IPv6  18405  0t0  TCP 
venus2.home:ssh->hydra.home:40926 (ESTABLISHED)
sshd997 scottfk5u  IPv6  18405  0t0  TCP 
venus2.home:ssh->hydra.home:40926 (ESTABLISHED)

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 fails post-installation

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation

[Nick Rosbrook]

Er, is there something else running on port 22 then? What does lsof
-i:22 show?

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 fails post-installation

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2020460] Re: Please merge 1:2.66-4 into mantic

[Danilo Egea Gondolfo]

** Attachment added: "Autopkgtests logs for armhf"
   
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+attachment/5675001/+files/libcap2_armhf_log.gz

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

Title:
  Please merge 1:2.66-4 into mantic

Status in libcap2 package in Ubuntu:
  New

Bug description:
  tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+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 2020460] Re: Please merge 1:2.66-4 into mantic

[Danilo Egea Gondolfo]

** Attachment added: "Autopkgtests logs for amd64"
   
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+attachment/5675000/+files/libcap2_amd64_log.gz

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

Title:
  Please merge 1:2.66-4 into mantic

Status in libcap2 package in Ubuntu:
  New

Bug description:
  tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+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 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation

[scottfk]

This is just the out-of-the-box sshd config from the preinstalled Ubuntu
23.04 Server image (https://ubuntu.com/download/risc-v).  I didn't make
any changes to it.

Interestingly...  on my amd64 desktop, I only see a ssh.socket systemd
service.  On an rpi and my VisionFive2 I see both ssh.socket *and*
ssh.service.

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 fails post-installation

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 1856871] Re: i/o error if next unused loop device is queried

[Jorge Merlino]

I restored the verification-done-focal tag because I already verified
this bug on focal (see comment #24). I think the linux-bluefield kernel
patch is not appropriate for this bug.

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

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

Title:
  i/o error if next unused loop device is queried

Status in linux package in Ubuntu:
  Fix Released
Status in parted package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in udev package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released

Bug description:
  
  [Impact]

  * There's an I/O error on fsync() in a detached loop device if it has
  been previously attached. The issue is that write cache is enabled in
  the attach path in loop_configure() but it isn't disabled in the detach
  path; thus it remains enabled in the block device regardless of whether
  it is attached or not.

  * fsync() on detached loop devices can be called by partition tools and
  commands run by sosreport, so the unexpected kernel error message might
  surprise users or even distract from the actual issue being
  investigatedr. It might also trigger alerts in
  logging/monitoring/alerting stacks

  [Fix]

  * Disable write cache in the detach path

  [Test Plan]

  * Attach and detach an image to a loop device and test fsync return
  value aterwards

  # DEV=/dev/loop7

  # IMG=/tmp/image
  # truncate --size 1M $IMG

  # losetup $DEV $IMG
  # losetup -d $DEV

  Before:
  # strace -e fsync parted -s $DEV print 2>&1 | grep fsync
  fsync(3)= -1 EIO (Input/output error)
  Warning: Error fsyncing/closing /dev/loop7: Input/output error
  [  982.529929] blk_update_request: I/O error, dev loop7, sector 0 op 
0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0

  After:
  # strace -e fsync parted -s $DEV print 2>&1 | grep fsync
  fsync(3)= 0

  [Where problems could occur]

  * The detach path for block devices is modified. Worst case scenario
  would be an error when detaching loop devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856871/+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 231806] Re: apt-get: Add SMB to the valid Uri methods for software repositories

[Fuujuhi]

Just passing by to confirm that the cifs + file method works fine.

Only make sure that the samba share is mounted world readable (otherwise
apt sandbox will complain).

And use one single slash on the file: line, for instance:

deb file:/smb/someserver/deb   path/to/repo/

This would assumes that your *.deb files are available on
/smb/someserver/deb/path/to/repo/ from the local machine perspecitve.

I find this is the best method to access a repo on a file server, since
you likely don't want to mess up the apt config with how you access the
samba shares (user name, password, etc).

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

Title:
  apt-get:  Add SMB to the valid Uri methods for software repositories

Status in apt package in Ubuntu:
  Triaged

Bug description:
  1.  I want to use my ubuntu 8.04.iso mounted via an linux SMB share in
  my apt sources list.  I used
  https://help.ubuntu.com/community/Repositories/Ubuntu for info and
  instructions, so I updated my sources list to include  'deb
  smb://10.10.10.66/ hardy main restricted' (a valid and accessible smb
  share on my network).  When I reload my sources, I get the following
  error in a pop up window: " The method driver /usr/lib/apt/methods/smb
  could not be found. "

  I looked at the man file for sources.list and didn't see SMB as a
  valid URI specification? Did smb get 'dropped' for some reason as a
  valid way to access repos or is there a way to add it to the methods
  section?

   Thanks,
Dylan

  Ref:
  ls -la /usr/lib/apt/methods/
  total 392
  drwxr-xr-x 2 root root 4096 2008-05-12 17:47 .
  drwxr-xr-x 3 root root 4096 2008-05-12 17:47 ..
  -rwxr-xr-x 1 root root 15076 2008-04-22 08:21 bzip2
  -rwxr-xr-x 1 root root 19404 2008-04-22 08:21 cdrom
  -rwxr-xr-x 1 root root 11268 2008-04-22 08:21 copy
  -rwxr-xr-x 1 root root 12292 2008-04-22 08:21 file
  -rwxr-xr-x 1 root root 55836 2008-04-22 08:21 ftp
  -rwxr-xr-x 1 root root 24708 2008-04-22 08:21 gpgv
  -rwxr-xr-x 1 root root 15076 2008-04-22 08:21 gzip
  -rwxr-xr-x 1 root root 55432 2008-04-22 08:21 http
  -rwxr-xr-x 1 root root 15076 2008-04-22 08:21 lzma
  -rwxr-xr-x 1 root root 71920 2008-04-22 08:21 mirror
  -rwxr-xr-x 1 root root 15552 2008-04-22 08:21 rred
  -rwxr-xr-x 1 root root 22516 2008-04-22 08:21 rsh
  -rwxr-xr-x 1 root root 22516 2008-04-22 08:21 ssh

  cat /etc/apt/sources.list

  deb-src http://archive.ubuntu.com/ubuntu/ hardy main restricted 
  deb http://us.archive.ubuntu.com/ubuntu/ hardy main restricted
  deb-src http://us.archive.ubuntu.com/ubuntu/ hardy restricted main multiverse 
universe #Added by software-properties
  deb http://us.archive.ubuntu.com/ubuntu/ hardy-updates main restricted
  deb-src http://us.archive.ubuntu.com/ubuntu/ hardy-updates restricted main 
multiverse universe #Added by software-properties
  deb http://us.archive.ubuntu.com/ubuntu/ hardy universe
  deb http://us.archive.ubuntu.com/ubuntu/ hardy-updates universe
  deb http://us.archive.ubuntu.com/ubuntu/ hardy multiverse
  deb http://us.archive.ubuntu.com/ubuntu/ hardy-updates multiverse
  deb http://us.archive.ubuntu.com/ubuntu/ hardy-backports main restricted 
universe multiverse
  deb-src http://us.archive.ubuntu.com/ubuntu/ gutsy-backports main restricted 
universe multiverse
  deb http://archive.canonical.com/ubuntu hardy partner
  deb-src http://archive.canonical.com/ubuntu hardy partner
  deb http://security.ubuntu.com/ubuntu hardy-security main restricted
  deb-src http://security.ubuntu.com/ubuntu hardy-security restricted main 
multiverse universe #Added by software-properties
  deb http://security.ubuntu.com/ubuntu hardy-security universe
  deb http://security.ubuntu.com/ubuntu hardy-security multiverse
  deb http://us.archive.ubuntu.com/ubuntu/ hardy-proposed restricted main 
multiverse universe
  deb http://download.skype.com/linux/repos/debian/ stable non-free

  deb smb://10.10.10.66/ubuntu_804_intel_32bit/ hardy restricted main

  #the smb above is the valid SMB share from my linux server
  #it is a mounted loop iso image file and shared out in samba, I see it 
readily via network shares.


  This is the exact readout when doing a sources reload:
  The method driver /usr/lib/apt/methods/smb could not be found.The method 
driver /usr/lib/apt/methods/smb could not be found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/231806/+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 2020460] Re: Please merge 1:2.66-4 into mantic

[Danilo Egea Gondolfo]

** Merge proposal linked:
   
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/libcap2/+git/libcap2/+merge/443409

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

Title:
  Please merge 1:2.66-4 into mantic

Status in libcap2 package in Ubuntu:
  New

Bug description:
  tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+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 2020470] Re: Please merge 1.9.13p3-1 into mantic

[Danilo Egea Gondolfo]

** Merge proposal linked:
   
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/sudo/+git/sudo/+merge/443422

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

Title:
  Please merge 1.9.13p3-1 into mantic

Status in sudo package in Ubuntu:
  New

Bug description:
  tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2020470/+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 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 fails post-installation

[Nick Rosbrook]

How are you configuring sshd to run? It seems like you may have
partially-configured socket-activated sshd. The postinst script should
only try to resart ssh.socket if it was already enabled, which should
not be the case if e.g. you reverted the socket-activation change. So,
did you try and disable socket-activated sshd in the past?

The issue is not your active ssh session, because that is not the
process that is listening on port 22.

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

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 fails post-installation

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
  May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
  May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
  May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

  At this point, sshd is no longer listening for new connections.  A
  manual systemctl restart of ssh.socket fails with the same error.  I
  am ssh-ed into this box, so I *think* the failure is because my
  session is already sitting on port 22, maybe?  The only way I can be
  sure I will be able to ssh to this box again is to reboot it (so that
  ssh.socket can start cleanly).

  $ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10

  $ apt policy openssh-server
  openssh-server:
Installed: 1:9.2p1-2ubuntu1
Candidate: 1:9.2p1-2ubuntu1
Version table:
   *** 1:9.2p1-2ubuntu1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
  100 /var/lib/dpkg/status
   1:9.0p1-1ubuntu8.1 500
  500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 
Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: openssh-server 1:9.2p1-2ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
  Uname: Linux 6.2.0-19-generic riscv64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  CloudArchitecture: riscv64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230413.1
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
  Date: Tue May 23 14:58:35 2023
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
  SourcePackage: openssh
  UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2020474/+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 2019496] Re: Security implications of SUDO_ASKPASS

[Marc Deslauriers]

If an attacker can edit ~/.bashrc they can simply modify the path and
point to a malicious sudo binary that does whatever it wants with the
password. I don't think this is a SUDO_ASKPASS issue.

If you disagree with our reasoning, it would be best to file this bug
with the upstream sudo project here:

https://bugzilla.sudo.ws/index.cgi

Once you file an upstream bug, please add a comment here with a link to
it. Thanks!

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

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

Title:
  Security implications of SUDO_ASKPASS

Status in sudo package in Ubuntu:
  Incomplete

Bug description:
  All that is needed to subvert sudo is adding this line to ~/.bashrc

  alias sudo="SUDO_ASKPASS=/home/$USER/.config/git/doevil sudo -A"

  and a program that reads the password from the command line and makes
  use of it.

  Ignoring the SUDO_ASKPASS environment variable would be an option to
  stop this.

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2019496/+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 2019496] Re: Security implications of SUDO_ASKPASS

[Heinrich Schuchardt]

Anything running in the user context can edit ~/.bashrc and set aliases.
But with aliases you don't get root access.

sudo goes to great lengths to ensure that the password is directly
passed from the console and not passed through a pipe. SUDO_ASKPASS can
circumvent this security.

So this badly needs fixing.

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

Title:
  Security implications of SUDO_ASKPASS

Status in sudo package in Ubuntu:
  New

Bug description:
  All that is needed to subvert sudo is adding this line to ~/.bashrc

  alias sudo="SUDO_ASKPASS=/home/$USER/.config/git/doevil sudo -A"

  and a program that reads the password from the command line and makes
  use of it.

  Ignoring the SUDO_ASKPASS environment variable would be an option to
  stop this.

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2019496/+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 2020503] [NEW] Build libvisual-plugins on i386

[Jeremy Bícha]

Public bug reported:

The source package libvisual is built on i386 (as a dependency of
gstreamer). libvisual now builds a new binary package, lv-tool-0.4. lv-
tool-0.4 depends on libvisual-0.4-plugins.

libvisual-0.4-plugins appears to have no dependencies that are not
already available on i386

Therefore, please enable libvisual-plugins to build on i386

** Affects: libvisual (Ubuntu)
 Importance: Undecided
 Status: Triaged

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


** Tags: mantic update-excuse

** Tags added: mantic

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

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

** Tags added: update-excuse

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

Title:
  Build libvisual-plugins on i386

Status in libvisual package in Ubuntu:
  Triaged
Status in libvisual-plugins package in Ubuntu:
  New

Bug description:
  The source package libvisual is built on i386 (as a dependency of
  gstreamer). libvisual now builds a new binary package, lv-tool-0.4.
  lv-tool-0.4 depends on libvisual-0.4-plugins.

  libvisual-0.4-plugins appears to have no dependencies that are not
  already available on i386

  Therefore, please enable libvisual-plugins to build on i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvisual/+bug/2020503/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

[Benjamin Drung]

Regarding the failing autopkgtest:

* python-tz on lunar:
  - cinder/2:22.0.0-0ubuntu1.1, ironic/1:21.4.0-0ubuntu1, and 
senlin/1:15.0.0-0ubuntu1 fail on armhf due to an installation issue of mysql 
(probably bug #1980466)
  - python-caldav/0.11.0-1 on armhf: not investigated yet
* tzdata on focal:
  - postgresql-12/12.14-0ubuntu0.20.04.1 on amd64: not investigated yet
* tzdata on lunar:
  - chrony/4.3-1ubuntu4 on armhf: Flaky test case (see bug #2002910)
  - python-tz/2022.7.1-3: fixed by python-tz/2022.7.1-3ubuntu0.1

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

Title:
  tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

Status in python-tz package in Ubuntu:
  Fix Released
Status in tzdata package in Ubuntu:
  Fix Released
Status in python-tz source package in Focal:
  Invalid
Status in tzdata source package in Focal:
  Fix Committed
Status in python-tz source package in Jammy:
  Invalid
Status in tzdata source package in Jammy:
  Fix Committed
Status in python-tz source package in Kinetic:
  Invalid
Status in tzdata source package in Kinetic:
  Fix Committed
Status in python-tz source package in Lunar:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recent updates have been using `PACKRATDATA=backzone` in order to add
  all out-of-scope lower-quality pre-1970 data back that existed in
  earlier tzadata releases (see bug #2003797). However it also leads to
  time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol,
  and Pacific/Enderbury to change:

  compared to 2023c-0ubuntu0.22.04.0
  - America/Ensenada->only dst changes until 2022 are shown
  - Atlantic/Jan_Mayen->now valid data is shown
  - Europe/Tiraspol->only dst changes until 2010 are shown

  [ Test Plan ]

  Add an autopkgtest test case for post-1970 symlink consistency: Check
  that the timezones for today and in half a year (= to cover DST
  changes) do not change compared to building them without
  `PACKRATDATA=backzone`.

  The mentioned timezones that differed can also be tested manually.
  Running following commands should have the same output (the output
  mentioned here is from tzdata 2023c-0ubuntu0.22.04.0):

  ```
  $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
  Fri Apr 28 06:49:00 PDT 2023
  $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
  Fri Apr 28 15:49:00 CEST 2023
  $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
  Fri Apr 28 16:49:00 EEST 2023
  ```

  [ Where problems could occur ]

  Timezone data could be wrong. Systems with incorrect timezone set may
  observe unexpected time shift when updating the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2020474] [NEW] openssh-server-1:9.2p1-2ubuntu1 fails post-installation

[scottfk]

Public bug reported:

Installation seems to fail on restarting ssh.socket via systemctl

Setting up openssh-server (1:9.2p1-2ubuntu1) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 openssh-server
E: Sub-process /usr/bin/dpkg returned an error code (1)

$ systemctl status ssh.socket
× ssh.socket - OpenBSD Secure Shell server socket
 Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
 Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 48s 
ago
   Duration: 3h 6min 36.071s
   Triggers: ● ssh.service
 Listen: [::]:22 (Stream)
CPU: 2ms

May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - OpenBSD Secure Shell 
server socket.
May 23 15:01:41 venus2 systemd[1]: Stopping ssh.socket - OpenBSD Secure Shell 
server socket...
May 23 15:01:41 venus2 systemd[2631]: ssh.socket: Failed to create listening 
socket ([::]:22): Address already in use
May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to receive listening 
socket ([::]:22): Input/output error
May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed to listen on sockets: 
Input/output error
May 23 15:01:41 venus2 systemd[1]: ssh.socket: Failed with result 'resources'.
May 23 15:01:41 venus2 systemd[1]: Failed to listen on ssh.socket - OpenBSD 
Secure Shell server socket.

At this point, sshd is no longer listening for new connections.  A
manual systemctl restart of ssh.socket fails with the same error.  I am
ssh-ed into this box, so I *think* the failure is because my session is
already sitting on port 22, maybe?  The only way I can be sure I will be
able to ssh to this box again is to reboot it (so that ssh.socket can
start cleanly).

$ lsb_release -rd
No LSB modules are available.
Description:Ubuntu Mantic Minotaur (development branch)
Release:23.10

$ apt policy openssh-server
openssh-server:
  Installed: 1:9.2p1-2ubuntu1
  Candidate: 1:9.2p1-2ubuntu1
  Version table:
 *** 1:9.2p1-2ubuntu1 500
500 http://ch.ports.ubuntu.com/ubuntu-ports mantic-proposed/main 
riscv64 Packages
100 /var/lib/dpkg/status
 1:9.0p1-1ubuntu8.1 500
500 http://ch.ports.ubuntu.com/ubuntu-ports mantic/main riscv64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: openssh-server 1:9.2p1-2ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-19.19.1-generic 6.2.6
Uname: Linux 6.2.0-19-generic riscv64
ApportVersion: 2.26.1-0ubuntu3
Architecture: riscv64
CasperMD5CheckResult: unknown
CloudArchitecture: riscv64
CloudBuildName: server
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSerial: 20230413.1
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud-net)
Date: Tue May 23 14:58:35 2023
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 1: 
/etc/ssh/sshd_config.d/50-cloud-init.conf: Permission denied
SourcePackage: openssh
UpgradeStatus: Upgraded to mantic on 2023-05-12 (11 days ago)

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


** Tags: apport-bug cloud-image mantic package-from-proposed riscv64

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

Title:
  openssh-server-1:9.2p1-2ubuntu1 fails post-installation

Status in openssh package in Ubuntu:
  New

Bug description:
  Installation seems to fail on restarting ssh.socket via systemctl

  Setting up openssh-server (1:9.2p1-2ubuntu1) ...
  rescue-ssh.target is a disabled or a static unit not running, not starting it.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
  dpkg: error processing package openssh-server (--configure):
   installed openssh-server package post-installation script subprocess 
returned error exit status 1
  Errors were encountered while processing:
   openssh-server
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  $ systemctl status ssh.socket
  × ssh.socket - OpenBSD Secure Shell server socket
   Loaded: loaded (/lib/systemd/system/ssh.socket; enabled; preset: enabled)
   Active: failed (Result: resources) since Tue 2023-05-23 15:01:41 CEST; 
48s ago
 Duration: 3h 6min 36.071s
 Triggers: ● ssh.service
   Listen: [::]:22 (Stream)
  CPU: 2ms

  May 23 11:55:05 venus2 systemd[1]: Listening on ssh.socket - OpenBSD Secure 
Shell server socket.
  May 23 15:01:41 venus2 systemd[1]: ssh.socket: Deactivated successfully.
  May 23 15:01:41 venus2 systemd[1]: Closed ssh.socket - 

[Touch-packages] [Bug 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

[Benjamin Drung]

Verified jammy SRU: The autopkgtest runs for 2023c-0ubuntu0.22.04.2
succeeded. The manual test were successful as well:

```
$ schroot-wrapper -p tzdata -e -c jammy
(jammy)bdrung@host:~$ dpkg -s tzdata | grep Version
Version: 2023c-0ubuntu0.22.04.2
(jammy)bdrung@host:~$ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
Fri Apr 28 06:49:00 PDT 2023
(jammy)bdrung@host:~$ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
Fri Apr 28 15:49:00 CEST 2023
(jammy)bdrung@host:~$ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
Fri Apr 28 16:49:00 EEST 2023
```

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

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

Title:
  tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

Status in python-tz package in Ubuntu:
  Fix Released
Status in tzdata package in Ubuntu:
  Fix Released
Status in python-tz source package in Focal:
  Invalid
Status in tzdata source package in Focal:
  Fix Committed
Status in python-tz source package in Jammy:
  Invalid
Status in tzdata source package in Jammy:
  Fix Committed
Status in python-tz source package in Kinetic:
  Invalid
Status in tzdata source package in Kinetic:
  Fix Committed
Status in python-tz source package in Lunar:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recent updates have been using `PACKRATDATA=backzone` in order to add
  all out-of-scope lower-quality pre-1970 data back that existed in
  earlier tzadata releases (see bug #2003797). However it also leads to
  time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol,
  and Pacific/Enderbury to change:

  compared to 2023c-0ubuntu0.22.04.0
  - America/Ensenada->only dst changes until 2022 are shown
  - Atlantic/Jan_Mayen->now valid data is shown
  - Europe/Tiraspol->only dst changes until 2010 are shown

  [ Test Plan ]

  Add an autopkgtest test case for post-1970 symlink consistency: Check
  that the timezones for today and in half a year (= to cover DST
  changes) do not change compared to building them without
  `PACKRATDATA=backzone`.

  The mentioned timezones that differed can also be tested manually.
  Running following commands should have the same output (the output
  mentioned here is from tzdata 2023c-0ubuntu0.22.04.0):

  ```
  $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
  Fri Apr 28 06:49:00 PDT 2023
  $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
  Fri Apr 28 15:49:00 CEST 2023
  $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
  Fri Apr 28 16:49:00 EEST 2023
  ```

  [ Where problems could occur ]

  Timezone data could be wrong. Systems with incorrect timezone set may
  observe unexpected time shift when updating the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

[Benjamin Drung]

Verified kinetic SRU: The autopkgtest runs for 2023c-0ubuntu0.22.10.2
succeeded. The manual test were successful as well:

```
$ schroot-wrapper -p tzdata -e -c kinetic
(kinetic)bdrung@host:~$ dpkg -s tzdata | grep Version
Version: 2023c-0ubuntu0.22.10.2
(kinetic)bdrung@host:~$ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
Fri Apr 28 06:49:00 PDT 2023
(kinetic)bdrung@host:~$ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
Fri Apr 28 15:49:00 CEST 2023
(kinetic)bdrung@host:~$ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
Fri Apr 28 16:49:00 EEST 2023
```

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

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

Title:
  tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

Status in python-tz package in Ubuntu:
  Fix Released
Status in tzdata package in Ubuntu:
  Fix Released
Status in python-tz source package in Focal:
  Invalid
Status in tzdata source package in Focal:
  Fix Committed
Status in python-tz source package in Jammy:
  Invalid
Status in tzdata source package in Jammy:
  Fix Committed
Status in python-tz source package in Kinetic:
  Invalid
Status in tzdata source package in Kinetic:
  Fix Committed
Status in python-tz source package in Lunar:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recent updates have been using `PACKRATDATA=backzone` in order to add
  all out-of-scope lower-quality pre-1970 data back that existed in
  earlier tzadata releases (see bug #2003797). However it also leads to
  time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol,
  and Pacific/Enderbury to change:

  compared to 2023c-0ubuntu0.22.04.0
  - America/Ensenada->only dst changes until 2022 are shown
  - Atlantic/Jan_Mayen->now valid data is shown
  - Europe/Tiraspol->only dst changes until 2010 are shown

  [ Test Plan ]

  Add an autopkgtest test case for post-1970 symlink consistency: Check
  that the timezones for today and in half a year (= to cover DST
  changes) do not change compared to building them without
  `PACKRATDATA=backzone`.

  The mentioned timezones that differed can also be tested manually.
  Running following commands should have the same output (the output
  mentioned here is from tzdata 2023c-0ubuntu0.22.04.0):

  ```
  $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
  Fri Apr 28 06:49:00 PDT 2023
  $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
  Fri Apr 28 15:49:00 CEST 2023
  $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
  Fri Apr 28 16:49:00 EEST 2023
  ```

  [ Where problems could occur ]

  Timezone data could be wrong. Systems with incorrect timezone set may
  observe unexpected time shift when updating the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

[Benjamin Drung]

Verified focal SRU: The autopkgtest runs for 2023c-0ubuntu0.20.04.2
succeeded. The manual test were successful as well:

```
$ schroot-wrapper -p tzdata -e -c focal
(focal)bdrung@host:~$ dpkg -s tzdata | grep Version
Version: 2023c-0ubuntu0.20.04.2
(focal)bdrung@host:~$ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
Fri Apr 28 06:49:00 PDT 2023
(focal)bdrung@host:~$ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
Fri Apr 28 15:49:00 CEST 2023
(focal)bdrung@host:~$ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
Fri Apr 28 16:49:00 EEST 2023
```

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

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

Title:
  tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

Status in python-tz package in Ubuntu:
  Fix Released
Status in tzdata package in Ubuntu:
  Fix Released
Status in python-tz source package in Focal:
  Invalid
Status in tzdata source package in Focal:
  Fix Committed
Status in python-tz source package in Jammy:
  Invalid
Status in tzdata source package in Jammy:
  Fix Committed
Status in python-tz source package in Kinetic:
  Invalid
Status in tzdata source package in Kinetic:
  Fix Committed
Status in python-tz source package in Lunar:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recent updates have been using `PACKRATDATA=backzone` in order to add
  all out-of-scope lower-quality pre-1970 data back that existed in
  earlier tzadata releases (see bug #2003797). However it also leads to
  time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol,
  and Pacific/Enderbury to change:

  compared to 2023c-0ubuntu0.22.04.0
  - America/Ensenada->only dst changes until 2022 are shown
  - Atlantic/Jan_Mayen->now valid data is shown
  - Europe/Tiraspol->only dst changes until 2010 are shown

  [ Test Plan ]

  Add an autopkgtest test case for post-1970 symlink consistency: Check
  that the timezones for today and in half a year (= to cover DST
  changes) do not change compared to building them without
  `PACKRATDATA=backzone`.

  The mentioned timezones that differed can also be tested manually.
  Running following commands should have the same output (the output
  mentioned here is from tzdata 2023c-0ubuntu0.22.04.0):

  ```
  $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
  Fri Apr 28 06:49:00 PDT 2023
  $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
  Fri Apr 28 15:49:00 CEST 2023
  $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
  Fri Apr 28 16:49:00 EEST 2023
  ```

  [ Where problems could occur ]

  Timezone data could be wrong. Systems with incorrect timezone set may
  observe unexpected time shift when updating the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

[Benjamin Drung]

Verified lunar SRU: The autopkgtest runs for 2023c-2exp1ubuntu1.1
succeeded. The manual test were successful as well:

```
$ schroot-wrapper -p tzdata -e -c lunar
(lunar)bdrung@host:~$ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
Fri Apr 28 06:49:00 PDT 2023
(lunar)bdrung@host:~$ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
Fri Apr 28 15:49:00 CEST 2023
(lunar)bdrung@host:~$ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
Fri Apr 28 16:49:00 EEST 2023
(lunar)bdrung@host:~$ dpkg -s tzdata | grep Version
Version: 2023c-2exp1ubuntu1.1
```

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

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

Title:
  tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

Status in python-tz package in Ubuntu:
  Fix Released
Status in tzdata package in Ubuntu:
  Fix Released
Status in python-tz source package in Focal:
  Invalid
Status in tzdata source package in Focal:
  Fix Committed
Status in python-tz source package in Jammy:
  Invalid
Status in tzdata source package in Jammy:
  Fix Committed
Status in python-tz source package in Kinetic:
  Invalid
Status in tzdata source package in Kinetic:
  Fix Committed
Status in python-tz source package in Lunar:
  Fix Committed
Status in tzdata source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  Recent updates have been using `PACKRATDATA=backzone` in order to add
  all out-of-scope lower-quality pre-1970 data back that existed in
  earlier tzadata releases (see bug #2003797). However it also leads to
  time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol,
  and Pacific/Enderbury to change:

  compared to 2023c-0ubuntu0.22.04.0
  - America/Ensenada->only dst changes until 2022 are shown
  - Atlantic/Jan_Mayen->now valid data is shown
  - Europe/Tiraspol->only dst changes until 2010 are shown

  [ Test Plan ]

  Add an autopkgtest test case for post-1970 symlink consistency: Check
  that the timezones for today and in half a year (= to cover DST
  changes) do not change compared to building them without
  `PACKRATDATA=backzone`.

  The mentioned timezones that differed can also be tested manually.
  Running following commands should have the same output (the output
  mentioned here is from tzdata 2023c-0ubuntu0.22.04.0):

  ```
  $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
  Fri Apr 28 06:49:00 PDT 2023
  $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
  Fri Apr 28 15:49:00 CEST 2023
  $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
  Fri Apr 28 16:49:00 EEST 2023
  ```

  [ Where problems could occur ]

  Timezone data could be wrong. Systems with incorrect timezone set may
  observe unexpected time shift when updating the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2020464] Re: Please merge lvm 2.03.16-2 from Debian unstable

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Please merge lvm 2.03.16-2 from Debian unstable

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-2 from Debian unstable.
  
  Updated changelog and diff against Debian unstable to be attached below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2020464/+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 2020470] [NEW] Please merge 1.9.13p3-1 into mantic

[Danilo Egea Gondolfo]

Public bug reported:

tracking bug

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

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

Title:
  Please merge 1.9.13p3-1 into mantic

Status in sudo package in Ubuntu:
  New

Bug description:
  tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2020470/+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 1815494] Re: May remove autoremovable non-kernel packages matching pattern from APT::VersionedKernelPackages

[Luis Alvarez Pinilla]

** Changed in: update-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  May remove autoremovable non-kernel packages matching pattern from
  APT::VersionedKernelPackages

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Confirmed
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Fix Released
Status in unattended-upgrades source package in Cosmic:
  Fix Released

Bug description:
  [Impact]

  * Non-kernel related autoremovable packages may be removed by 
unattended-upgrades due to their name matching generic patterns like 
'.*-modules' which should be applied to versioned kernel packages only.
  * The fix corrects the way those patterns are handled.

  [Test Case]

  * test/test_remove_unused.py checks for correct pattern usage now.

  [Regression Potential]

  * Unattended-upgrades may stop removing autoremovable kernels, but the
  tests also contain cases covering this and u-u's kernel autoremoval
  still works.

  [Original Bug Text]

  Unattended-upgrades and Update Manager use the patterns from the
  APT::VersionedKernelPackages list directly for finding kernel packages
  to remove while APT uses patterns by attaching version and flavor to
  them.

  As a result in APT's script ".*-modules" becomes
  "^.*-modules-4\.15\.0-45-generic$":

  ...
  for package in $(apt-config dump --no-empty --format '%v%n' 
'APT::VersionedKernelPackages'); do
  for kernel in $kernels; do
  echo "   \"^${package}-${kernel}$\";"
    done
  ...

  In unattended-upgrades and update-manager ".*-modules" is used
  directly for matching and may false  identify autoremovable packages
  as kernel-related ones and remove them (of just offer the removal in
  case of update-manager):

  ...
  Removing unused kernel packages: extra-cmake-modules
  marking extra-cmake-modules for removal
  (Reading database ... 31149 files and directories currently installed.)
  Removing extra-cmake-modules (5.44.0-0ubuntu1) ...
  Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
  Packages that were successfully auto-removed: extra-cmake-modules
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1815494/+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 2020460] Re: Please merge 1:2.66-4 into mantic

[Danilo Egea Gondolfo]

PPA
https://launchpad.net/~danilogondolfo/+archive/ubuntu/libcap2/+packages

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

Title:
  Please merge 1:2.66-4 into mantic

Status in libcap2 package in Ubuntu:
  New

Bug description:
  tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+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 2020464] Re: Please merge lvm 2.03.16-2 from Debian unstable

[Dave Jones]

Test packages built in ppa:waveform/lvm2
(https://launchpad.net/~waveform/+archive/ubuntu/lvm2)

** Tags added: fr-4283

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

Title:
  Please merge lvm 2.03.16-2 from Debian unstable

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-2 from Debian unstable.
  
  Updated changelog and diff against Debian unstable to be attached below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2020464/+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 2020464] Re: Please merge lvm 2.03.16-2 from Debian unstable

[Dave Jones]

Attaching patch against Debian unstable. For ease of review, relevant
commits and tags have been pushed to the following repository:

https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2

Specifically:

* logical/2.03.16-1ubuntu1 represents our split-out delta on
  top of old/debian (2.03.16-1)
* logical/2.03.16-2ubuntu1 represents our rebased delta on
  top of new/debian (2.03.16-2)
* merge/2.03.16-2ubuntu1 adds changelog and maintainer
  changes on top of logical/2.03.16-2ubuntu1

Hence, the following command may produce output useful to the purposes
of review:

git range-diff --creation-factor=100
old/debian..logical/2.03.16-1ubuntu1
new/debian..logical/2.03.16-2ubuntu1


** Patch added: "1-2020464.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2020464/+attachment/5674963/+files/1-2020464.debdiff

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

Title:
  Please merge lvm 2.03.16-2 from Debian unstable

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-2 from Debian unstable.
  
  Updated changelog and diff against Debian unstable to be attached below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2020464/+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 1971242] Re: printing PDF appears always grey, no color

[Bug Watch Updater]

** Changed in: cups
   Status: New => Fix Released

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

Title:
  printing PDF appears always grey, no color

Status in CUPS:
  Fix Released
Status in atril package in Ubuntu:
  Confirmed
Status in cups package in Ubuntu:
  Confirmed
Status in okular package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
  document. The print appears always b/w regardless color printing was
  enabled or not. Printing from LibreOffice produces a color print. This
  behavior (bug) is reproducible on three upgraded machines. It would be
  nice to have color print back again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+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 2020110] Re: Migrate netplan settings to this package

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-settings - 23.10.1

---
ubuntu-settings (23.10.1) mantic; urgency=medium

  * ubuntu-settings: migrated (unowned, livecd-rootfs hack based) netplan
network-manager configuration to /lib/netplan from /etc/netplan
(LP: #2020110)

 -- Dave Jones   Thu, 18 May 2023 15:34:12
+0100

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Fix Released

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

Title:
  Migrate netplan settings to this package

Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  The current netplan configuration that specifies Network Manager as
  the renderer comes from a livecd-rootfs hack and results in an
  "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was
  decided at the engineering sprint to migrate this to /lib/netplan
  (with a slightly tweaked filename starting 00- for precedence) owned
  by ubuntu-settings which will ease maintenance (and image builds) in
  future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+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 2020464] [NEW] Please merge lvm 2.03.16-2 from Debian unstable

[Dave Jones]

Public bug reported:

Please merge lvm2 2.03.16-2 from Debian unstable.

Updated changelog and diff against Debian unstable to be attached below.

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

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

Title:
  Please merge lvm 2.03.16-2 from Debian unstable

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-2 from Debian unstable.
  
  Updated changelog and diff against Debian unstable to be attached below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2020464/+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 2020458] Re: Xorg crash

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.

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

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

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

Title:
  Xorg crash

Status in Ubuntu:
  Incomplete

Bug description:
  When I move a Firefox tab hover the Ubuntu top menu, the graphic
  session crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.105.17  Tue Mar 28 
18:02:59 UTC 2023
   GCC version:
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 23 11:31:17 2023
  DistUpgraded: 2023-04-21 20:36:13,884 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/7.0.6, 5.19.0-40-generic, x86_64: installed
   virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 
00 [VGA controller])
 Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:087c]
 Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
  InstallationDate: Installed on 2022-07-18 (308 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Dell Inc. XPS 15 9570
  ProcEnviron:
   LANG=fr_FR.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=4aa30583-6cc3-484d-8ece-ba7c82da34a5 ro nouveau.blacklist=1 
acpi_osi=! "acpi_osi=Windows 2015" acpi_backlight=video mem_sleep_default=deep 
quiet splash acpi_backlight=legacy vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to lunar on 2023-04-22 (31 days ago)
  dmi.bios.date: 03/13/2023
  dmi.bios.release: 1.31
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.31.0
  dmi.board.name: 0D0T05
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd03/13/2023:br1.31:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:sku087C:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9570
  dmi.product.sku: 087C
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2020458/+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 2020460] [NEW] Please merge 1:2.66-4 into mantic

[Danilo Egea Gondolfo]

Public bug reported:

tracking bug

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

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

Title:
  Please merge 1:2.66-4 into mantic

Status in libcap2 package in Ubuntu:
  New

Bug description:
  tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcap2/+bug/2020460/+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 2020458] [NEW] Xorg crash

[Pascal]

Public bug reported:

When I move a Firefox tab hover the Ubuntu top menu, the graphic session
crash.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.105.17  Tue Mar 28 
18:02:59 UTC 2023
 GCC version:
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue May 23 11:31:17 2023
DistUpgraded: 2023-04-21 20:36:13,884 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: lunar
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/7.0.6, 5.19.0-40-generic, x86_64: installed
 virtualbox/7.0.6, 6.2.0-20-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00 
[VGA controller])
   Subsystem: Dell CoffeeLake-H GT2 [UHD Graphics 630] [1028:087c]
   Subsystem: Dell GP107M [GeForce GTX 1050 Ti Mobile] [1028:087c]
InstallationDate: Installed on 2022-07-18 (308 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Dell Inc. XPS 15 9570
ProcEnviron:
 LANG=fr_FR.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=4aa30583-6cc3-484d-8ece-ba7c82da34a5 ro nouveau.blacklist=1 
acpi_osi=! "acpi_osi=Windows 2015" acpi_backlight=video mem_sleep_default=deep 
quiet splash acpi_backlight=legacy vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: Upgraded to lunar on 2023-04-22 (31 days ago)
dmi.bios.date: 03/13/2023
dmi.bios.release: 1.31
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.31.0
dmi.board.name: 0D0T05
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.31.0:bd03/13/2023:br1.31:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn0D0T05:rvrA00:cvnDellInc.:ct10:cvr:sku087C:
dmi.product.family: XPS
dmi.product.name: XPS 15 9570
dmi.product.sku: 087C
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.114-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug crash lunar 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/2020458

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  When I move a Firefox tab hover the Ubuntu top menu, the graphic
  session crash.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  525.105.17  Tue Mar 28 
18:02:59 UTC 2023
   GCC version:
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 23 11:31:17 2023
  DistUpgraded: 2023-04-21 20:36:13,884 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: 

[Touch-packages] [Bug 1990089] Update Released

[Timo Aaltonen]

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

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

Title:
  Screen freeze when performing memory stress in Wayland mode

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Released
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Running stress-ng freezes the screen under wayland on intel iris.
  Upstream has fixed it in

  5aae8a05264c354aa93017d323ce238858f68227 iris: Retry 
DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM
  646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if 
kernel can't allocate memory"

  which need to be backported for 22.2.5

  [Test case]

  Install the update, then

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  and note that it shouldn't freeze anymore.

  [Where things could go wrong]

  This moves checking ENOMEM to the right place, so it's hard to see how
  it might cause issues.

  --

  [Steps to reproduce]
  (disable systemd-oomd or executing over ssh)
  (below command allocates a lot of memory to stress kernel page fault)

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  [Expected result]
  Screen will update slowly when performing the stress-test.
  but screen needs back to work after stress.

  [Actual result]
  Screen freeze after stress test.

  [Additional information]
  kernel version: vmlinuz-5.17.0-1017-oem
  kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
  Mesa version: 22.0.5-0ubuntu0.1
  Mutter version: 42.2-0ubuntu1
  Gnome-shell version: 42.2-0ubuntu0.2

  * Issue happens in Wayland only

  * gnome-shell keeps issuing ioctl()
  ```
  (gdb) bt
  #0  __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at 
../sysdeps/unix/sysv/linux/ioctl.c:36
  #1  0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, 
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
  #2  iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, 
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
  #3  iris_wait_syncobj (bufmgr=, syncobj=, 
timeout_nsec=timeout_nsec@entry=9223372036854775807) at 
../src/gallium/drivers/iris/iris_fence.c:215
  #4  0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, 
wait=, query=0x55774159b800, ctx=) at 
../src/gallium/drivers/iris/iris_query.c:635
  #5  iris_get_query_result (ctx=, query=0x55774159b800, 
wait=, result=0x7fffc5404e50) at 
../src/gallium/drivers/iris/iris_query.c:601
  #6  0x7fcaca405e89 in tc_get_query_result (_pipe=, 
query=0x55774159b800, wait=, result=0x7fffc5404e50) at 
../src/gallium/auxiliary/util/u_threaded_context.c:881
  #7  0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, 
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at 
../src/mesa/main/queryobj.c:266
  #8  0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, 
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
  #9  get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 
"glGetQueryObjecti64v", id=, pname=34918, 
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
  at ../src/mesa/main/queryobj.c:1174
  #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, 
pname=, params=) at 
../src/mesa/main/queryobj.c:1257
  #11 0x7fcadfa39b90 in ?? () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #20 0x7fcae0743c24 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #21 0x7fcae07986f8 in ?? () from 

[Touch-packages] [Bug 2003339] Update Released

[Timo Aaltonen]

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

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Released
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 22.2.5-0ubuntu0.1~22.04.2

---
mesa (22.2.5-0ubuntu0.1~22.04.2) jammy; urgency=medium

  * patches: Fix VA-API on DCN 3.1.4. (LP: #2017142)
  * patches: Fix a freeze with iris under stress test. (LP: #1990089)
  * patches: Revert two commits causing kwin to eventually crash. (LP:
#2003339)

 -- Timo Aaltonen   Fri, 21 Apr 2023 14:51:10 +0300

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

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Released
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 1990089] Re: Screen freeze when performing memory stress in Wayland mode

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 22.2.5-0ubuntu0.1~22.04.2

---
mesa (22.2.5-0ubuntu0.1~22.04.2) jammy; urgency=medium

  * patches: Fix VA-API on DCN 3.1.4. (LP: #2017142)
  * patches: Fix a freeze with iris under stress test. (LP: #1990089)
  * patches: Revert two commits causing kwin to eventually crash. (LP:
#2003339)

 -- Timo Aaltonen   Fri, 21 Apr 2023 14:51:10 +0300

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

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

Title:
  Screen freeze when performing memory stress in Wayland mode

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Released
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Running stress-ng freezes the screen under wayland on intel iris.
  Upstream has fixed it in

  5aae8a05264c354aa93017d323ce238858f68227 iris: Retry 
DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM
  646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if 
kernel can't allocate memory"

  which need to be backported for 22.2.5

  [Test case]

  Install the update, then

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  and note that it shouldn't freeze anymore.

  [Where things could go wrong]

  This moves checking ENOMEM to the right place, so it's hard to see how
  it might cause issues.

  --

  [Steps to reproduce]
  (disable systemd-oomd or executing over ssh)
  (below command allocates a lot of memory to stress kernel page fault)

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  [Expected result]
  Screen will update slowly when performing the stress-test.
  but screen needs back to work after stress.

  [Actual result]
  Screen freeze after stress test.

  [Additional information]
  kernel version: vmlinuz-5.17.0-1017-oem
  kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
  Mesa version: 22.0.5-0ubuntu0.1
  Mutter version: 42.2-0ubuntu1
  Gnome-shell version: 42.2-0ubuntu0.2

  * Issue happens in Wayland only

  * gnome-shell keeps issuing ioctl()
  ```
  (gdb) bt
  #0  __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at 
../sysdeps/unix/sysv/linux/ioctl.c:36
  #1  0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, 
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
  #2  iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, 
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
  #3  iris_wait_syncobj (bufmgr=, syncobj=, 
timeout_nsec=timeout_nsec@entry=9223372036854775807) at 
../src/gallium/drivers/iris/iris_fence.c:215
  #4  0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, 
wait=, query=0x55774159b800, ctx=) at 
../src/gallium/drivers/iris/iris_query.c:635
  #5  iris_get_query_result (ctx=, query=0x55774159b800, 
wait=, result=0x7fffc5404e50) at 
../src/gallium/drivers/iris/iris_query.c:601
  #6  0x7fcaca405e89 in tc_get_query_result (_pipe=, 
query=0x55774159b800, wait=, result=0x7fffc5404e50) at 
../src/gallium/auxiliary/util/u_threaded_context.c:881
  #7  0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, 
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at 
../src/mesa/main/queryobj.c:266
  #8  0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, 
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
  #9  get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 
"glGetQueryObjecti64v", id=, pname=34918, 
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
  at ../src/mesa/main/queryobj.c:1174
  #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, 
pname=, params=) at 
../src/mesa/main/queryobj.c:1257
  #11 0x7fcadfa39b90 in ?? () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #20 0x7fcae0743c24 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #21 0x7fcae07986f8 in ?? () from 

[Touch-packages] [Bug 2017142] Update Released

[Timo Aaltonen]

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

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

Title:
  [jammy] VA-API doesn't work on DCN 3.1.4

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

Bug description:
  [ Impact ]
  VA-API decoding doesn't work on DCN 3.1.4.
  Mesa 22.2.5 includes all the code to support it but is missing the chip ID.

  The device ID was included in upstream mesa 22.3.1.

  [ Test Plan ]

   * Verify that VA-API works using "mpv" or a similar tool that uses VA-API
   * Verify that '# vainfo' shows the correct information.

  [ Where problems could occur ]

   * If just the new ID is backported then they would be unique to DCN 3.1.4 as 
it's now running VA-API codepaths.
   * If newer mesa point release is adopted, then it could be a regression that 
happened in changes on common code in mesa between those two point releases.

  [ Other Info ]
  * It can be cherry picked with this single commit:
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858

  * AMD has already tested cherry-picked commit on top of the Ubuntu
  mesa 22.2.5 package and verified it works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+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 2017142] Re: [jammy] VA-API doesn't work on DCN 3.1.4

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 22.2.5-0ubuntu0.1~22.04.2

---
mesa (22.2.5-0ubuntu0.1~22.04.2) jammy; urgency=medium

  * patches: Fix VA-API on DCN 3.1.4. (LP: #2017142)
  * patches: Fix a freeze with iris under stress test. (LP: #1990089)
  * patches: Revert two commits causing kwin to eventually crash. (LP:
#2003339)

 -- Timo Aaltonen   Fri, 21 Apr 2023 14:51:10 +0300

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

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

Title:
  [jammy] VA-API doesn't work on DCN 3.1.4

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

Bug description:
  [ Impact ]
  VA-API decoding doesn't work on DCN 3.1.4.
  Mesa 22.2.5 includes all the code to support it but is missing the chip ID.

  The device ID was included in upstream mesa 22.3.1.

  [ Test Plan ]

   * Verify that VA-API works using "mpv" or a similar tool that uses VA-API
   * Verify that '# vainfo' shows the correct information.

  [ Where problems could occur ]

   * If just the new ID is backported then they would be unique to DCN 3.1.4 as 
it's now running VA-API codepaths.
   * If newer mesa point release is adopted, then it could be a regression that 
happened in changes on common code in mesa between those two point releases.

  [ Other Info ]
  * It can be cherry picked with this single commit:
  
https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858

  * AMD has already tested cherry-picked commit on top of the Ubuntu
  mesa 22.2.5 package and verified it works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+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 2019940] Re: Directly manipulating NetworkManager keyfiles

[Arif Ali]

Invalid for sosreport

We collect NetworkManager and netplan data depending what is available

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

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

Title:
  Directly manipulating NetworkManager keyfiles

Status in augeas package in Ubuntu:
  New
Status in calamares package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  Invalid
Status in cruft package in Ubuntu:
  Won't Fix
Status in cruft-ng package in Ubuntu:
  New
Status in dracut package in Ubuntu:
  New
Status in forensic-artifacts package in Ubuntu:
  New
Status in guestfs-tools package in Ubuntu:
  New
Status in guix package in Ubuntu:
  New
Status in ltsp package in Ubuntu:
  Invalid
Status in netcfg package in Ubuntu:
  Won't Fix
Status in netplan.io package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  New
Status in refpolicy package in Ubuntu:
  New
Status in sosreport package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  New
Status in uhd package in Ubuntu:
  New
Status in vagrant package in Ubuntu:
  New

Bug description:
  The affected packages can manipulate NetworkManager keyfiles directly
  on disk, which might not be appropriate anymore on Ubuntu, since the
  Netplan integration was enabled in NetworkManager (starting with
  Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 2012943] Autopkgtest regression report (systemd/245.4-4ubuntu3.22)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (245.4-4ubuntu3.22) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

fwupd/1.7.9-1~20.04.1 (armhf)
gvfs/1.44.1-1ubuntu1.2 (amd64, arm64, ppc64el)
linux-bluefield/5.4.0-1063.69 (arm64)
linux-hwe-5.15/5.15.0-72.79~20.04.1 (ppc64el)
linux-intel-iotg-5.15/5.15.0-1030.35~20.04.1 (amd64)
linux-lowlatency-hwe-5.15/5.15.0-72.79~20.04.1 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  systemd-resolved crashes due to use-after-free bug

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

Bug description:
  [ Impact ]

  The continuous systemd-resolved crashes delay/hang the device startup.
  And this leads to unresponsive devices in the system. Specifically, the crash 
looks like:

  Dec 16 12:51:21 TREND-24-AF-7A systemd[1]: Started Time & Date Service.
  Dec 16 12:51:24 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main 
process exited, code=killed, status=11/SEGV
  [...]
  Dec 16 12:53:47 TREND-24-AF-7A systemd-resolved[2591]: Assertion 
'DNS_TRANSACTION_IS_LIVE(q->state)' failed at 
src/resolve/resolved-dns-query.c:520, function dns_query_complete(). Aborting.
  Dec 16 12:53:47 TREND-24-AF-7A systemd[1]: systemd-resolved.service: Main 
process exited, code=killed, status=6/ABRT

  [ Test Plan ]

  The exact steps to reproduce this issue are still not known.
  But we see this crash only in Static IP Addressing mode enabled, where 
systemd-resolved is enabled for LLMNR service.
  But we were not able to see this crash in DHCP mode.

  Steps to reproduce:
  1) Powercycle the device.
  2) Soft-reboot.

  It was also pointed out by Brian Murray that this error in the Ubuntu
  error tracker is likely the same bug:
  https://errors.ubuntu.com/problem/3cb08ae5efaa4d8c6ce992f7cebd2751ae3f168f.
  Therefore, we would expect to stop seeing this error in the tracker as
  a result of this patch.

  [ Where problems could occur ]

  The patch[1] simply disables the timer event source for a DNS query
  when the struct representing that query is free'd. I cannot see any
  realistic regression potential, because if the timer event fired on
  the DNS query after it has been free'd, then that would be this bug.
  I.e. no working code should be relying on the timer event source still
  being around after the query is free'd.

  [1]
  
https://github.com/systemd/systemd/commit/73bfd7be042cc63e7649242b377ad494bf74ea4b

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