[Touch-packages] [Bug 2022825] [NEW] motd-news.timer trigger motd-news.service even if disable

[Nadav Levi Yahel]

Public bug reported:

Hello, guys, how are you?
I notice motd-news.timer activate motd-news.service even when motd-new.service 
disable.

I follow this doc's from UBUNTU:
https://ubuntu.com/legal/motd

/etc/default/motd-news has an ENABLED=1 setting that to 0 for disable.

It's not working too…

When you reboot the server and put
sudo systemctl status motd-news.service

Service look dead. (disable)
but he got trigger by motd-news.timer after 10 - 20 minutes (screenshot):
https://ibb.co/yXTpzGq

if you look on the screenshot, you will see:
TriggeredBy: ● motd-news.timer

I can disable the motd-news.timer service, but i don't know if it will affect 
other services of UBUNTU.
Anyway It's still a bug, even if i disable the timer service, it's not should 
be this way.

Happened on 2 Different machines of UBUNTU 22.04 (Google Cloud Platform)

Be happy for your recommendation before i disable the motd-new.timer
with systemctl.

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

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

Title:
  motd-news.timer trigger motd-news.service even if disable

Status in base-files package in Ubuntu:
  New

Bug description:
  Hello, guys, how are you?
  I notice motd-news.timer activate motd-news.service even when 
motd-new.service disable.

  I follow this doc's from UBUNTU:
  https://ubuntu.com/legal/motd

  /etc/default/motd-news has an ENABLED=1 setting that to 0 for disable.

  It's not working too…

  When you reboot the server and put
  sudo systemctl status motd-news.service

  Service look dead. (disable)
  but he got trigger by motd-news.timer after 10 - 20 minutes (screenshot):
  https://ibb.co/yXTpzGq

  if you look on the screenshot, you will see:
  TriggeredBy: ● motd-news.timer

  I can disable the motd-news.timer service, but i don't know if it will affect 
other services of UBUNTU.
  Anyway It's still a bug, even if i disable the timer service, it's not should 
be this way.

  Happened on 2 Different machines of UBUNTU 22.04 (Google Cloud
  Platform)

  Be happy for your recommendation before i disable the motd-new.timer
  with systemctl.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2022825/+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 2022824] [NEW] random blue/pink frames in the desktop

[alex valin]

Public bug reported:

I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop.
every 1-2 minutes, there will be a random blue/pink frame(i'm not sure
of the color because it only appears for a short time). I don't get this
problem in fullscreen games running with dxvk and the random frames
didn't show when I recorded my desktop with obs studio. I also got this
problem in gnome(on wayland). When I have a dxvk game running, I don't
get this issue.

what I tried:
-rebooting
-updating
-disabling blur in kde settings
-lowering my refresh rate from 144hz to 120hz

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-43-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: KDE
Date: Sat Jun  3 00:45:32 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT / 
6800M] [1002:73df] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT / 6800M] 
[1043:05d7]
InstallationDate: Installed on 2023-06-01 (1 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-43-generic 
root=UUID=ca576fb0-08b4-45d8-aadd-83e9df696ff2 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/10/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.80
dmi.board.name: B450M Pro4-F
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.80:bd05/10/2021:br5.17:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MPro4-F:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug corruption jammy kubuntu 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/2022824

Title:
  random blue/pink frames in the desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  I am running a fresh install of ubuntu 22.04 with kde-plasma-desktop.
  every 1-2 minutes, there will be a random blue/pink frame(i'm not sure
  of the color because it only appears for a short time). I don't get
  this problem in fullscreen games running with dxvk and the random
  frames didn't show when I recorded my desktop with obs studio. I also
  got this problem in gnome(on wayland). When I have a dxvk game
  running, I don't get this issue.

  what I tried:
  -rebooting
  -updating
  -disabling blur in kde settings
  -lowering my refresh rate from 144hz to 120hz

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Jun  3 00:45:32 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Navi 22 [Radeon RX 6700/6700 XT / 
6800M] [1002:73df] (rev c1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Navi 22 [Radeon RX 6700/6700 XT / 6800M] 
[1043:05d7]
  InstallationDate: Installed on 2023-06-01 (1 days ago)
  InstallationMedia: Ubuntu 

[Touch-packages] [Bug 2015355] Autopkgtest regression report (util-linux/2.34-0.1ubuntu9.4)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted util-linux (2.34-0.1ubuntu9.4) for 
focal have finished running.
The following regressions have been reported in tests triggered by the package:

nfs-utils/1:1.3.4-2.5ubuntu3.4 (amd64)
systemd/245.4-4ubuntu3.21 (armhf)
ubiquity/20.04.15.19 (amd64, arm64, armhf, ppc64el)


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#util-linux

[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 util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/2015355

Title:
  Please backport patches for false atari partition detection to Ubuntu
  20.04

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The partition detection logic in libblkid1 can falsely report the
  presence of an atari partition. One place where this has a practical
  impact is in kubernetes where mount-utils will refuse to format the
  device (https://github.com/kubernetes/mount-
  utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441).

  [Test Plan]

  * Create a new qcow2 disk image:

  $ qemu-img create -f qcow2 test.img 20G

  * Boot a focal ISO with QEMU/KVM as if installing to test.img:

  $ qemu-system-x86_64 -enable-kvm -m 4096 -name test -drive
  file=test.img,format=qcow2 -net nic,model=virtio -net
  user,hostfwd=tcp::1022-:22 -vga virtio -cdrom ubuntu-20.04.6-desktop-
  amd64.iso

  * Using the live environment, format the empty disk. These particular
  commands were given as a reproducer on the upstream bug report
  (https://github.com/util-linux/util-linux/issues/1116).

  $ parted -s /dev/sda -- mklabel msdos
  $ parted -s /dev/sda -- mkpart primary 0% 10% mkpart primary 10% 30%

  * Run wipefs on /dev/sda to list partitions. On an affected machine,
  an atari partition will be listed. On a fixed machine, the incorrect
  atari listing will be gone.

  $ wipefs /dev/sda
  DEVICE OFFSET TYPE  UUID LABEL
  sda0x1fe  dos
  sda0x1d2  atari

  [Where problems could occur]

  These patches specifically address the atari prober logic in libblkid.
  Therefore, if we saw regressions it would be related to detecting
  atari partitions with libblkid. This would potentially impact tools
  such as wipefs and blkid, or any other tool that uses libblkid1 for
  this purpose.

  [Original Description]

  There are three patches in util-linux upstream that were released in
  util-linux 2.37 and prevent false detection of the atari partition
  table with blkid and wipefs. We see this mostly on LUKS devices
  initialised via luksFormat reporting there is an atari partition table
  on the device when it is empty. This causes issues in various places,
  but one key example for us is in kubernetes where mount-utils will
  refuse to format the device (https://github.com/kubernetes/mount-
  utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441)

  RedHat backported these fixes to RHEL 8 under
  https://bugzilla.redhat.com/show_bug.cgi?id=2060030 and it would be
  helpful if Ubuntu also backported them to Ubuntu 20.04 which is still
  running util-linux 2.34

  The request is to backport patches based on the
  https://github.com/util-linux/util-linux/issues/1159 upstream report.

  Upstream commits to cherry-pick the changes to 
libblkid/src/partitions/atari.c from:
  2cc76d50d7a14bef8e7b07fab11b26c9e49d36a2
  282ceadc3a72fc07dd0388b8880fd751490bb87f
  c70b4f2a5b99876d230b8f4f413c3bb3ee6647f1

  # lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.6 LTS
  Release:20.04
  Codename:   focal
  # blkid -V
  blkid from util-linux 2.34  (libblkid 2.34.0, 14-Jun-2019)
  # blkid -p -s TYPE -s PTTYPE -o export 
/dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted
  DEVNAME=dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted
  PTTYPE=atari
  # lsblk
  ...
  sdccrypto_LUKS
 a79d2982-74f2-44c7-bb29-460768ebfe64
  `-3600a09803830474a735d4c63744c4a56crypto_LUKS
 a79d2982-74f2-44c7-bb29-460768ebfe64
    `-pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2015355/+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 1883880] Re: fix non-8-bit x86 displacements breaking AVX512 builds on Bionic

[Bug Watch Updater]

** Changed in: binutils (Debian)
   Status: Confirmed => Fix Released

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

Title:
  fix non-8-bit x86 displacements breaking AVX512 builds on Bionic

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  Fix Released
Status in binutils package in Debian:
  Fix Released

Bug description:
  [Impact]

   * the assembler scales non 8 bit cases which was identified
 to break e.g. some AVX512 code. It is nasty as it isn't a compile/link/ 
 time error. Instead the instructions might silently be corrupted until 
 running. Things might even work on some but fail on other systems if 
 e.g. the AVX code paths only run on newer chips.

* The fix is upstream for a while and not re-changed again. Furthermore 
  it is in several Ubuntu releases without bugs due to that, which should 
  make the backport rather safe.

  [Test Case]

   * Simple example to trigger the bug:

  echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d
  avx.o | grep vmovaps

  The expected output is that the objdump output matches the vmovaps
  instruction input. When using binutils with the bug, the initial 0x40
  will be incorrect.

  Working:
  $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | 
grep vmovaps
 0: 62 f1 7c 48 28 04 05 vmovaps 0x40(,%rax,1),%zmm0
  Failing:
  $ echo "vmovaps 0x40(,%rax,1),%zmm0" | as --64 -o avx.o && objdump -d avx.o | 
grep vmovaps
 0: 62 f1 7c 48 28 04 05 vmovaps 0x1(,%rax,1),%zmm0

  [Regression Potential]

   * Well, this is a double edged sword. On one hand this is fortunately a 
 small change and only affects something formerly clearly broken. So it 
 should be good and only change cases formerly being bad.
 But OTOH binutils areused in so many cases that I feel unable to say
 "nothing will happen". The change goes to the gnu assembler, so that is 
 the place to look out for regressions.

  [Other Info]
   
   * needs a sponsor experienced with binutils to check potential pitfalls


  
  ---

  
  Hi,
  DPDK has run into some issues in the past
   https://bugs.dpdk.org/show_bug.cgi?id=97
   https://bugs.dpdk.org/show_bug.cgi?id=249

  Eventually the issues got resolved in binutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=23465

  After binutils is fixed people rebuilding DPDK themselve can use
   http://patches.dpdk.org/patch/71679/
  to gain more performance while on Bionics bintuils level.

  Note: Bionic is on DPDK 17.11.x which will not get further stable release 
afaik. But quite often people build their own DPDK. In fact this came up as a 
request from Openvswitch upstream/Intel to allow such builds on Bionic.
  I'd ping those people about the bug and ask them to participate in the 
verification if this becomes an SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1883880/+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 2020604] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.3) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mutter/42.5-0ubuntu1 (amd64)


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/jammy/update_excuses.html#mesa

[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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in chromium-browser source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in chromium-browser source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New

Bug description:
  [Impact]
  After patching Mesa with some driver updates, Chromium/Brave started seeing 
corrupt graphics. This was due to GPU acceleration being enabled in the browser 
by default now, and the old GPU shader cache is invalid in some ways and the 
browser is not able to recognize that the driver has changed, since the 
upstream version string hasn't changed. This is shown for instance with 
'glxinfo -B' or under 'chrome:gpu' from the browser.

  The fix is to make the upstream VERSION to have the full packaging
  version, this will then be used for the core profile version string as
  well.

  
  [Test case]

  - run stock jammy, install brave-browser from brave.com, launch brave-
  browser, check that 'brave://gpu' shows things are accelerated, then
  exit the browser

  - enable proposed, install libgl1-mesa-dri et al

  - launch brave-browser again, verify that gfx are not corrupted and
  brave://gpu is showing acceration being used

  with the pulled update, graphics would be severely corrupted

  
  [Where things could go wrong]
  There could be apps that expect the Mesa version string to only contain 
a.b.c, and break in some ways when that's no longer the case.

  
  --

  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2022310] Re: package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I don't know what is the isue. The sistem reported a bug and create a
  report, but i don't see any effect but the message itself.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Jun  2 08:12:08 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-10-04 (240 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2022310/+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 2008846] Re: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1

[Seth Arnold]

Of your suggestions, I like #1 the most; a reboot is usually a good idea
*anyway*, since there's always kernel updates to install, but I'd hold
off rebooting until you get the machine back into a happy state.

Try:

sudo kill  1224036
sudo apt install -f

You might also need:

sudo dpkg --configure -a

Then:

sudo apt update && sudo apt upgrade

Thanks

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

Title:
  package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade:
  installed libssl3:amd64 package post-installation script subprocess
  returned error exit status 1

Status in needrestart package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  encounter error when attempting to do sudo update, upgrade, and full-
  upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libssl3:amd64 3.0.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  1 10:28:26 2023
  ErrorMessage: installed libssl3:amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-10-01 (150 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: openssl
  Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: 
installed libssl3:amd64 package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2008846/+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 1965215] Re: [81FD, Realtek ALC236, Black Mic, Right] The external microphone is not detected

[Chris Chambers]

Same here on a HP 14 Stream laptop with this Realtek ALC236 sound card
running Xubuntu 20.04. Also pluging in an external headset and
microphone the laptop speakers do not mute and the headphones do not go
live, they remain muted.

Maybe worth noting that; Using pavucontrol having plugged in headset i
can switch to headphones which then transmit sound and the external
microphone opperates ok but even then pavucontrol states headset as un-
plugged same as before plugging in. Laptop speakers mute once switched
to headset and i presume the internal microphone is blanked.

With regret i have deinstalled Xubuntu and reinstalled Arch Linux and so
i cannot test further. It is obvious to me that this bug? is not
distribution specific and is generic becouse exactly the same problem in
Arch. I could test or check and report here from this Arch install if
such information is useful to you.

Best wishes to you, Chris

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

Title:
  [81FD, Realtek ALC236, Black Mic, Right] The external microphone is
  not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.4 LTS
  Release:  20.04

  When inserted in the 3.5mm phone jack, the external microphone is not
  detected, and thus the audio input doesn't auto-switch from the
  internal microphone to the external microphone.

  The problem probably is related to the kernel version, as kernels
  5.11.0-34, 5.11.0-36,5.11.0-37 and 5.11.0-38 works as expected, but
  kernels 5.4.0-104, 5.11.0-40, 5.11.0-41, 5.11.0-43, 5.11.0-44,
  5.11.0-46, 5.13.0-30 and 5.13.0-35 don't. A similar problem happens
  for Debian 11.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thales 1485 F pulseaudio
   /dev/snd/pcmC0D0p:   thales 1485 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 17 00:07:20 2022
  InstallationDate: Installed on 2022-03-09 (7 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_Jack: Black Mic, Right
  Symptom_Type: No auto-switch between inputs
  Title: [81FD, Realtek ALC236, Black Mic, Right] No autoswitch
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2021
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8RCN58WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40679 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330-15IKB
  dmi.ec.firmware.release: 1.58
  dmi.modalias: 
dmi:bvnLENOVO:bvr8RCN58WW:bd05/19/2021:br1.58:efr1.58:svnLENOVO:pn81FD:pvrLenovoideapad330-15IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad330-15IKB:skuLENOVO_MT_81FD_BU_idea_FM_ideapad330-15IKB:
  dmi.product.family: ideapad 330-15IKB
  dmi.product.name: 81FD
  dmi.product.sku: LENOVO_MT_81FD_BU_idea_FM_ideapad 330-15IKB
  dmi.product.version: Lenovo ideapad 330-15IKB
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965215/+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 2008846] Re: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1

[Derek]

I'm afraid I cant access the logs when that happened. Actually I don't
know the exact date that this started  happening on the updates. The
thing is that I cant use apt anymore, I wanted to install a package to
create a complete copy of the server in case something goes wrong.

Maybe the best solution is to restart the server instead of killing this 
process? 
Please I would need some advice as I have clients projects there.

I was thinking of buying a new server, try duplicate the plesk there and
all configuration, but that is a lot of work. So I will have this 3
options.

1.- Kill the process and see if it did work, if not... I wont have server for 
at least 4-5 hours until I configure and install all again.
2.- restart the server, this looks like a better aproach instead of killing 
services in the middle. and cross fingers that ubuntu solve it self. but again 
if not, and system just does not go will be in trouble.
3.- duplicating all server on other server.

What are your opinion?

Thank you in advance.

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

Title:
  package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade:
  installed libssl3:amd64 package post-installation script subprocess
  returned error exit status 1

Status in needrestart package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  encounter error when attempting to do sudo update, upgrade, and full-
  upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libssl3:amd64 3.0.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  1 10:28:26 2023
  ErrorMessage: installed libssl3:amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-10-01 (150 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: openssl
  Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: 
installed libssl3:amd64 package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2008846/+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 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore

[Sebastien Bacher]

I've tested it with files from https://filesamples.com/formats/heif
which was in the first returns of a google query for heif examples,
that's not an official recommendation of that website though...

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

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

Title:
  Cannot open HEIF/HEIC images in 23.04/lunar anymore

Status in eog package in Ubuntu:
  Invalid
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in libheif package in Ubuntu:
  Fix Released
Status in eog source package in Lunar:
  Invalid
Status in gdk-pixbuf source package in Lunar:
  Invalid
Status in libheif source package in Lunar:
  New

Bug description:
  * Impact

  The libheif loader is bailing out due to a missing plugin directory
  which leads to image viewer as eog not being able to open pictures in
  that format anymore

  * Testcase

  Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in
  eog

  * Where problems could occur

  The package build is using the option to not split the codec in
  separate plugins but the version of Lunar doesn't handle the missing
  plugins directory and bails out. The code of the version in mantic has
  been refactored in a way which fixes this problem. For lunar it's
  easier to just create the directory. The directory is included in the
  libheif1 binary but that should not create any conflict, it's a
  temporary situation for lunar only and even if the soname changed dpkg
  allows for several deb packages to provide the same directory.

  --


  In previous Ubuntu versions, including 22.10, I was able to open
  HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does
  not work anymore in 23.04.

  Running eog in a terminal displays:
  $ eog IMG_9996.HEIC

  ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  eog then shows "Could not load image “IMG_9996.HEIC”. Image loading
  failed."

  gpicview even crashes immediately:
  $ gpicview IMG_9996.HEIC
  Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module"

  ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin
  directory.

  ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory.
  Segmentation fault (core dumped)

  The problem concerns all HEIF/HEIC images I tested.

  The installed versions of the (possibly) relevant packages are:
  libheif1: 1.14.2-1
  heif-gdk-pixbuf: 1.14.2-1
  libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1
  eog: 44.0-1
  gpicview: 0.2.5-3build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+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 2008846] Re: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1

[Seth Arnold]

Thanks Adrien, that feels less worrying than I initially thought.
Yesterday I missed an unattended-upgrades that's been running since
March. Oof.

I honestly don't know what to suggest to Derek; killing those processes
feels like a good idea, since there's no terminal available to interact
with debconf, and sooner or later the consequences of that are going to
have to be faced. It's probably enough to kill it, and then do:

sudo apt install -f
sudo apt update && sudo apt upgrade

by hand afterwards, that'd probably get to a happy place. But I'm not
confident.

I like the idea of removing / pruning / moving the openssl maintainer
scripts; a lot of it feels like it was made for a previous world. And
it's certainly fragile, I see enough of these bug reports, too.

Thanks

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

Title:
  package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade:
  installed libssl3:amd64 package post-installation script subprocess
  returned error exit status 1

Status in needrestart package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  encounter error when attempting to do sudo update, upgrade, and full-
  upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libssl3:amd64 3.0.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  1 10:28:26 2023
  ErrorMessage: installed libssl3:amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-10-01 (150 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: openssl
  Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: 
installed libssl3:amd64 package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2008846/+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 2021484] Re: Editing a VPN ask to introduce credentials but if you cancel can be accessed anyway

[Seth Arnold]

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

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

Title:
  Editing a VPN ask to introduce credentials but if you cancel can be
  accessed anyway

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  I'm logged as a normal user without admin privileges. When I try to
  edit a VPN I'm asked to introduce the credentials of the admin,
  nevertheless if I click cancel I can still access to the VPN
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-settings 20.04.6
  ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98
  Uname: Linux 5.15.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 29 11:16:38 2023
  InstallationDate: Installed on 2022-05-04 (389 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2021484/+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 2022388] [NEW] the microfone dont work

[Ultroms]

Public bug reported:

the problem is with the sound card . As such if I have sound but it sounds very 
low even if I turn it up to the maximum with the sound buttons (yep i use a 
laptop) and I have to turn it up manually with alsamixer. And the worst thing 
is that even if I save the configuration to save the changes from the terminal 
when I reboot the device all the alsamixer configuration restarts. 
heres is the specification of my computer :
Audio:
  Device-1: Intel Tiger Lake-LP Smart Sound Audio
driver: sof-audio-pci-intel-tgl
  Sound API: ALSA v: k6.2.0-20-generic running: yes
  Sound Server-1: PipeWire v: 0.3.65 running: yes
My hardware:System:
  Host: carlos-NBD-WXX9 Kernel: 6.2.0-20-generic arch: x86_64 bits: 64
Desktop: GNOME v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster)
Machine:
  Type: Laptop System: HUAWEI product: NBD-WXX9 v: M1010
serial: 
  Mobo: HUAWEI model: NBD-WXX9-PCB-B4 v: M1010 serial: 
UEFI: HUAWEI v: 2.30 date: 07/04/2022
Battery:
  ID-1: BAT1 charge: 17.9 Wh (33.0%) condition: 54.2/54.9 Wh (98.7%)
volts: 7.5 min: 7.6
CPU:
  Info: quad core 11th Gen Intel Core i5-1135G7 [MT MCP] speed (MHz):
avg: 1364 min/max: 400/4200
Graphics:
  Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
  Device-2: Quanta ov9734_techfront_camera type: USB driver: uvcvideo
  Display: wayland server: X.Org v: 1.22.1.8 with: Xwayland v: 22.1.8
compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: iris gpu: i915 resolution: 1920x1080~60Hz
  API: OpenGL v: 4.6 Mesa 23.0.2 renderer: Mesa Intel Xe Graphics (TGL GT2)
Network:
  Device-1: Intel Wi-Fi 6 AX201 driver: iwlwifi
Drives:
  Local Storage: total: 476.94 GiB used: 149.06 GiB (31.3%)
Info:
  Processes: 337 Uptime: 1h 35m Memory: 7.54 GiB used: 4.27 GiB (56.6%)
  Shell: Bash inxi: 3.3.25

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  carlos 1967 F wireplumber
 /dev/snd/seq:carlos 1959 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  2 22:03:03 2023
InstallationDate: Installed on 2023-01-25 (128 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
PackageArchitecture: all
ProcEnviron:
 LANG=es_ES.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to lunar on 2023-04-21 (42 days ago)
dmi.bios.date: 07/04/2022
dmi.bios.release: 2.30
dmi.bios.vendor: HUAWEI
dmi.bios.version: 2.30
dmi.board.asset.tag: N/A
dmi.board.name: NBD-WXX9-PCB-B4
dmi.board.vendor: HUAWEI
dmi.board.version: M1010
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1010
dmi.ec.firmware.release: 2.30
dmi.modalias: 
dmi:bvnHUAWEI:bvr2.30:bd07/04/2022:br2.30:efr2.30:svnHUAWEI:pnNBD-WXX9:pvrM1010:rvnHUAWEI:rnNBD-WXX9-PCB-B4:rvrM1010:cvnHUAWEI:ct10:cvrM1010:skuC100:
dmi.product.family: MateBook D
dmi.product.name: NBD-WXX9
dmi.product.sku: C100
dmi.product.version: M1010
dmi.sys.vendor: HUAWEI

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


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

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

Title:
  the microfone dont work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the problem is with the sound card . As such if I have sound but it sounds 
very low even if I turn it up to the maximum with the sound buttons (yep i use 
a laptop) and I have to turn it up manually with alsamixer. And the worst thing 
is that even if I save the configuration to save the changes from the terminal 
when I reboot the device all the alsamixer configuration restarts. 
  heres is the specification of my computer :
  Audio:
Device-1: Intel Tiger Lake-LP Smart Sound Audio
  driver: sof-audio-pci-intel-tgl
Sound API: ALSA v: k6.2.0-20-generic running: yes
Sound Server-1: PipeWire v: 0.3.65 running: yes
  My hardware:System:
Host: carlos-NBD-WXX9 Kernel: 6.2.0-20-generic arch: x86_64 bits: 64
  Desktop: GNOME v: 44.0 Distro: Ubuntu 23.04 (Lunar Lobster)
  Machine:
Type: Laptop System: HUAWEI product: NBD-WXX9 v: M1010
  serial: 
Mobo: HUAWEI model: NBD-WXX9-PCB-B4 v: M1010 serial: 
  UEFI: HUAWEI v: 2.30 date: 07/04/2022
  Battery:
ID-1: BAT1 charge: 17.9 Wh (33.0%) condition: 54.2/54.9 Wh (98.7%)
  volts: 7.5 min: 7.6
  CPU:
Info: quad core 11th Gen Intel Core i5-1135G7 [MT MCP] speed (MHz):
  avg: 1364 min/max: 400/4200
  Graphics:
Device-1: Intel TigerLake-LP GT2 

[Touch-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics

[Sam]

Thank you very much Steve (and Timo and everyone else that has helped).
We will test it on a few systems this weekend.

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in chromium-browser source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in chromium-browser source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New

Bug description:
  [Impact]
  After patching Mesa with some driver updates, Chromium/Brave started seeing 
corrupt graphics. This was due to GPU acceleration being enabled in the browser 
by default now, and the old GPU shader cache is invalid in some ways and the 
browser is not able to recognize that the driver has changed, since the 
upstream version string hasn't changed. This is shown for instance with 
'glxinfo -B' or under 'chrome:gpu' from the browser.

  The fix is to make the upstream VERSION to have the full packaging
  version, this will then be used for the core profile version string as
  well.

  
  [Test case]

  - run stock jammy, install brave-browser from brave.com, launch brave-
  browser, check that 'brave://gpu' shows things are accelerated, then
  exit the browser

  - enable proposed, install libgl1-mesa-dri et al

  - launch brave-browser again, verify that gfx are not corrupted and
  brave://gpu is showing acceration being used

  with the pulled update, graphics would be severely corrupted

  
  [Where things could go wrong]
  There could be apps that expect the Mesa version string to only contain 
a.b.c, and break in some ways when that's no longer the case.

  
  --

  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mutter/42.5-0ubuntu1 (amd64)


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/jammy/update_excuses.html#mesa

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

[Touch-packages] [Bug 2003339] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mutter/42.5-0ubuntu1 (amd64)


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/jammy/update_excuses.html#mesa

[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 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 2015355] Re: Please backport patches for false atari partition detection to Ubuntu 20.04

[Steve Langasek]

Hello Dominic, or anyone else affected,

Accepted util-linux into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.34-0.1ubuntu9.4 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: util-linux (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

Title:
  Please backport patches for false atari partition detection to Ubuntu
  20.04

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The partition detection logic in libblkid1 can falsely report the
  presence of an atari partition. One place where this has a practical
  impact is in kubernetes where mount-utils will refuse to format the
  device (https://github.com/kubernetes/mount-
  utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441).

  [Test Plan]

  * Create a new qcow2 disk image:

  $ qemu-img create -f qcow2 test.img 20G

  * Boot a focal ISO with QEMU/KVM as if installing to test.img:

  $ qemu-system-x86_64 -enable-kvm -m 4096 -name test -drive
  file=test.img,format=qcow2 -net nic,model=virtio -net
  user,hostfwd=tcp::1022-:22 -vga virtio -cdrom ubuntu-20.04.6-desktop-
  amd64.iso

  * Using the live environment, format the empty disk. These particular
  commands were given as a reproducer on the upstream bug report
  (https://github.com/util-linux/util-linux/issues/1116).

  $ parted -s /dev/sda -- mklabel msdos
  $ parted -s /dev/sda -- mkpart primary 0% 10% mkpart primary 10% 30%

  * Run wipefs on /dev/sda to list partitions. On an affected machine,
  an atari partition will be listed. On a fixed machine, the incorrect
  atari listing will be gone.

  $ wipefs /dev/sda
  DEVICE OFFSET TYPE  UUID LABEL
  sda0x1fe  dos
  sda0x1d2  atari

  [Where problems could occur]

  These patches specifically address the atari prober logic in libblkid.
  Therefore, if we saw regressions it would be related to detecting
  atari partitions with libblkid. This would potentially impact tools
  such as wipefs and blkid, or any other tool that uses libblkid1 for
  this purpose.

  [Original Description]

  There are three patches in util-linux upstream that were released in
  util-linux 2.37 and prevent false detection of the atari partition
  table with blkid and wipefs. We see this mostly on LUKS devices
  initialised via luksFormat reporting there is an atari partition table
  on the device when it is empty. This causes issues in various places,
  but one key example for us is in kubernetes where mount-utils will
  refuse to format the device (https://github.com/kubernetes/mount-
  utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441)

  RedHat backported these fixes to RHEL 8 under
  https://bugzilla.redhat.com/show_bug.cgi?id=2060030 and it would be
  helpful if Ubuntu also backported them to Ubuntu 20.04 which is still
  running util-linux 2.34

  The request is to backport patches based on the
  https://github.com/util-linux/util-linux/issues/1159 upstream report.

  Upstream commits to cherry-pick the changes to 
libblkid/src/partitions/atari.c from:
  2cc76d50d7a14bef8e7b07fab11b26c9e49d36a2
  282ceadc3a72fc07dd0388b8880fd751490bb87f
  c70b4f2a5b99876d230b8f4f413c3bb3ee6647f1

  # lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.6 LTS
  Release:20.04
  Codename:   focal
  # blkid -V
  blkid from util-linux 2.34  (libblkid 2.34.0, 14-Jun-2019)
  # blkid -p -s TYPE -s PTTYPE -o export 
/dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted
  DEVNAME=dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted
  PTTYPE=atari
  # lsblk
  ...
  sdc  

[Touch-packages] [Bug 2017142] Autopkgtest regression report (mesa/22.2.5-0ubuntu0.1~22.04.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted mesa (22.2.5-0ubuntu0.1~22.04.2) for 
jammy have finished running.
The following regressions have been reported in tests triggered by the package:

gtk+3.0/3.24.33-1ubuntu2 (i386)
mutter/42.5-0ubuntu1 (amd64)


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/jammy/update_excuses.html#mesa

[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 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 2020474] Re: openssh-server-1:9.2p1-2ubuntu1 cannot be installed from active ssh session

[Nick Rosbrook]

You are correct that this is the same issue. However, the reason you are seeing 
this in Lunar is that
you are running with -proposed enabled, which is where packages are staged 
before being released to -release, or -updates for stable release updates. So, 
this means that you installed 1:9.0p1-1ubuntu8.1 from lunar-proposed, which 
contains the bug that causes the problem on upgrade. However, thanks to this 
bug report from you, we have uploaded 1:9.0p1-1ubuntu8.2 to lunar-proposed to 
fix the underlying issue *before* openssh is released to lunar-updates. This 
means that users who upgrade to 1:9.0p1-1ubuntu8.2 from 1:9.0p1-1ubuntu8 (i.e. 
they never installed 1:9.0p1-1ubuntu8.1) will not see this bug. Since a buggy 
version of openssh was not yet released to lunar-updates, we did not apply the 
extra patches that we did in mantic to work around the bug on upgrade (for 
mantic, a buggy version was released to mantic-release, so the situation was a 
bit different).

So, anyone running -proposed on kinetic or lunar will hit this bug once,
but those users should be able to reboot, run dpkg --configure -a, and
be sorted.

-- 
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:
  Fix Committed

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 

[Touch-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics

[Steve Langasek]

Hello Sam, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  After Mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in chromium-browser source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in chromium-browser source package in Lunar:
  Invalid
Status in mesa source package in Lunar:
  New

Bug description:
  [Impact]
  After patching Mesa with some driver updates, Chromium/Brave started seeing 
corrupt graphics. This was due to GPU acceleration being enabled in the browser 
by default now, and the old GPU shader cache is invalid in some ways and the 
browser is not able to recognize that the driver has changed, since the 
upstream version string hasn't changed. This is shown for instance with 
'glxinfo -B' or under 'chrome:gpu' from the browser.

  The fix is to make the upstream VERSION to have the full packaging
  version, this will then be used for the core profile version string as
  well.

  
  [Test case]

  - run stock jammy, install brave-browser from brave.com, launch brave-
  browser, check that 'brave://gpu' shows things are accelerated, then
  exit the browser

  - enable proposed, install libgl1-mesa-dri et al

  - launch brave-browser again, verify that gfx are not corrupted and
  brave://gpu is showing acceration being used

  with the pulled update, graphics would be severely corrupted

  
  [Where things could go wrong]
  There could be apps that expect the Mesa version string to only contain 
a.b.c, and break in some ways when that's no longer the case.

  
  --

  After today's Ubuntu 22.04 Mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The Mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to Mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with Mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Steve Langasek]

LP: #2008430 says "due to setuptools 66.x.x" which is only present in
lunar and later, and all these SRUs are for kinetic and earlier, so this
still doesn't look like a real-world test case...

** Changed in: python-debian (Ubuntu Kinetic)
   Status: New => Incomplete

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Incomplete
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 

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

[scottfk]

Seems this has now made its way downstream to openssh-server 9.0 (on a
different box):

The following packages will be upgraded:
  openssh-client openssh-server openssh-sftp-server
3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 1295 kB of archives.
After this operation, 65.5 kB disk space will be freed.
Do you want to continue? [Y/n] 
Get:1 http://ca.ports.ubuntu.com/ubuntu-ports lunar-proposed/main arm64 
openssh-sftp-server arm64 1:9.0p1-1ubuntu8.2 [36.0 kB]
Get:2 http://ca.ports.ubuntu.com/ubuntu-ports lunar-proposed/main arm64 
openssh-server arm64 1:9.0p1-1ubuntu8.2 [409 kB]
Get:3 http://ca.ports.ubuntu.com/ubuntu-ports lunar-proposed/main arm64 
openssh-client arm64 1:9.0p1-1ubuntu8.2 [849 kB]
Fetched 1295 kB in 1s (921 kB/s)
Preconfiguring packages ...
(Reading database ... 104735 files and directories currently installed.)
Preparing to unpack .../openssh-sftp-server_1%3a9.0p1-1ubuntu8.2_arm64.deb ...
Unpacking openssh-sftp-server (1:9.0p1-1ubuntu8.2) over (1:9.0p1-1ubuntu8.1) ...
Preparing to unpack .../openssh-server_1%3a9.0p1-1ubuntu8.2_arm64.deb ...
Unpacking openssh-server (1:9.0p1-1ubuntu8.2) over (1:9.0p1-1ubuntu8.1) ...
Preparing to unpack .../openssh-client_1%3a9.0p1-1ubuntu8.2_arm64.deb ...
Unpacking openssh-client (1:9.0p1-1ubuntu8.2) over (1:9.0p1-1ubuntu8.1) ...
Setting up openssh-client (1:9.0p1-1ubuntu8.2) ...
Setting up openssh-sftp-server (1:9.0p1-1ubuntu8.2) ...
Setting up openssh-server (1:9.0p1-1ubuntu8.2) ...
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
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for ufw (0.36.1-4.1) ...
Errors were encountered while processing:
 openssh-server
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)


Should I cut a new bug for this?  It's a different arch and a different version 
of Ubuntu, but it's the exact same symptom (and, likely, cause).

-- 
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:
  Fix Committed

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
   

[Touch-packages] [Bug 2011458] Autopkgtest regression report (openssh/1:9.0p1-1ubuntu7.3)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted openssh (1:9.0p1-1ubuntu7.3) for 
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

ganeti/3.0.2-1ubuntu1 (armhf)
gvfs/1.50.2-2 (amd64, arm64, ppc64el)
hg-git/0.10.4-3 (amd64, arm64, armhf, ppc64el, s390x)
libcloud/3.4.1-5 (s390x)
piuparts/1.1.5 (amd64, arm64, ppc64el, s390x)
sbuild/0.83.1ubuntu1 (arm64, ppc64el, s390x)


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/kinetic/update_excuses.html#openssh

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

[Touch-packages] [Bug 2011458] Autopkgtest regression report (openssh/1:9.0p1-1ubuntu8.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted openssh (1:9.0p1-1ubuntu8.2) for lunar 
have finished running.
The following regressions have been reported in tests triggered by the package:

ganeti/3.0.2-3 (arm64, ppc64el)


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/lunar/update_excuses.html#openssh

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

[Touch-packages] [Bug 2017420] Re: Cannot open HEIF/HEIC images in 23.04/lunar anymore

[Steve Langasek]

Where does one get a .heif file to use for the test case?

** Also affects: eog (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: gdk-pixbuf (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: libheif (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

** Changed in: gdk-pixbuf (Ubuntu Lunar)
   Status: New => Invalid

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

** Changed in: libheif (Ubuntu Lunar)
   Importance: Undecided => High

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

Title:
  Cannot open HEIF/HEIC images in 23.04/lunar anymore

Status in eog package in Ubuntu:
  Invalid
Status in gdk-pixbuf package in Ubuntu:
  Invalid
Status in libheif package in Ubuntu:
  Fix Released
Status in eog source package in Lunar:
  Invalid
Status in gdk-pixbuf source package in Lunar:
  Invalid
Status in libheif source package in Lunar:
  Incomplete

Bug description:
  * Impact

  The libheif loader is bailing out due to a missing plugin directory
  which leads to image viewer as eog not being able to open pictures in
  that format anymore

  * Testcase

  Install libheif1 and heif-gdk-pixbuf and try to open a .heif file in
  eog

  * Where problems could occur

  The package build is using the option to not split the codec in
  separate plugins but the version of Lunar doesn't handle the missing
  plugins directory and bails out. The code of the version in mantic has
  been refactored in a way which fixes this problem. For lunar it's
  easier to just create the directory. The directory is included in the
  libheif1 binary but that should not create any conflict, it's a
  temporary situation for lunar only and even if the soname changed dpkg
  allows for several deb packages to provide the same directory.

  --


  In previous Ubuntu versions, including 22.10, I was able to open
  HEIF/HEIC files by installing libheif1 and heif-gdk-pixbuf. This does
  not work anymore in 23.04.

  Running eog in a terminal displays:
  $ eog IMG_9996.HEIC

  ** (eog:44492): WARNING **: 14:29:17.537: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.537:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.538:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  ** (eog:44492): WARNING **: 14:29:17.543: Cannot read plugin
  directory.

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_is_static_image: assertion
  'GDK_IS_PIXBUF_ANIMATION (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_get_iter: assertion 'GDK_IS_PIXBUF_ANIMATION
  (animation)' failed

  (eog:44492): GdkPixbuf-CRITICAL **: 14:29:17.543:
  gdk_pixbuf_animation_iter_get_pixbuf: assertion
  'GDK_IS_PIXBUF_ANIMATION_ITER (iter)' failed

  eog then shows "Could not load image “IMG_9996.HEIC”. Image loading
  failed."

  gpicview even crashes immediately:
  $ gpicview IMG_9996.HEIC
  Gtk-Message: 14:30:30.216: Failed to load module "canberra-gtk-module"

  ** (gpicview:44624): WARNING **: 14:30:30.260: Cannot read plugin
  directory.

  ** (gpicview:44624): WARNING **: 14:30:30.265: Cannot read plugin directory.
  Segmentation fault (core dumped)

  The problem concerns all HEIF/HEIC images I tested.

  The installed versions of the (possibly) relevant packages are:
  libheif1: 1.14.2-1
  heif-gdk-pixbuf: 1.14.2-1
  libgdk-pixbuf-2.0-0: 2.42.10+dfsg-1build1
  eog: 44.0-1
  gpicview: 0.2.5-3build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/2017420/+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 2022107] Re: printing dubugging doesnt work!

[Adrian]

What is so difficult to read in the dump posted which clearly states
which description / version / release it is ..  and that cups isnt
available nor that the websites referred to fail.

Expected result .. PRINTS 
Actual result  DOESNT PRINT

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

Title:
  printing dubugging doesnt work!

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  1  cupsdisable OKI-C332-411ACB 
  cupsdisable: Operation failed: client-error-not-found

  2   wget http://people.canonical.com/~pitti/tmp/cups.upstart.debug
  --2023-06-01 21:57:49--  
http://people.canonical.com/~pitti/tmp/cups.upstart.debug
  Resolving people.canonical.com (people.canonical.com)... 185.125.188.97
  Connecting to people.canonical.com 
(people.canonical.com)|185.125.188.97|:80... connected.
  HTTP request sent, awaiting response... 301 Moved Permanently
  Location: https://people.canonical.com/~pitti/tmp/cups.upstart.debug 
[following]
  --2023-06-01 21:57:49--  
https://people.canonical.com/~pitti/tmp/cups.upstart.debug
  Connecting to people.canonical.com 
(people.canonical.com)|185.125.188.97|:443... connected.
  HTTP request sent, awaiting response... 403 Forbidden
  2023-06-01 21:57:49 ERROR 403: Forbidden.

  Description:  Ubuntu 20.04.6 LTS
  Release:  20.04

  sudo: aa-complain: command not found

  /usr/lib/cups/backend/snmp
  network socket://192.168.1.201 "OKI DATA CORP C332" "C332" "MFG:OKI DATA 
CORP;CMD:PCL,XPS,IBMPPR,EPSONFX,POSTSCRIPT,PDF,PCLXL,HIPERMIP,URF;MDL:C332;CLS:PRINTER;DES:OKI
 C332;CID:OK_N_B800;" ""

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.2
  ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98
  Uname: Linux 5.15.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  1 21:59:57 2023
  InstallationDate: Installed on 2023-04-25 (37 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  Lpstat: device for OKI_C332_411ACB@oki-c332-411acb.local: 
implicitclass://OKI_C332_411ACB%40oki-c332-411acb.local/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 3151:3020 YICHIP Wireless Device
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Novatech N150ZU
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/oki_c332_411...@oki-c332-411acb.local.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/oki_c332_411...@oki-c332-411acb.local.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-72-generic 
root=UUID=2c0e4998-ac9a-4c3c-ab96-b2b45fe5eab7 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TNO
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150ZU
  dmi.board.vendor: Novatech
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TNO:bd06/24/2019:br7.7:efr7.4:svnNovatech:pnN150ZU:pvrNotApplicable:rvnNovatech:rnN150ZU:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N150ZU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Novatech

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2022107/+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 2022364] Re: libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null) [16867:16867:0602/210638.112634:ERROR:gl_surface_presentation_helper.cc(2

[Nick Rosbrook]

** Package changed: ubuntu-release-upgrader (Ubuntu) => libva (Ubuntu)

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

Title:
  libva error: vaGetDriverNameByIndex() failed with unknown libva error,
  driver_name = (null)
  [16867:16867:0602/210638.112634:ERROR:gl_surface_presentation_helper.cc(260)]
  GetVSyncParametersIfAvailable() failed for 1 times!
  [16867:16867:0602/210717.919411:ERROR:gl_surface_presentation_helper.cc(260)]
  GetVSyncParametersIfAvailable() failed for 2 times!
  [16867:16867:0602/210721.210799:ERROR:gl_surface_presentation_helper.cc(260)]
  GetVSyncParametersIfAvailable() failed for 3 times!

Status in libva package in Ubuntu:
  New

Bug description:
  libva error: vaGetDriverNameByIndex() failed with unknown libva error, 
driver_name = (null)
  [16867:16867:0602/210638.112634:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 1 times!
  [16867:16867:0602/210717.919411:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 2 times!
  [16867:16867:0602/210721.210799:ERROR:gl_surface_presentation_helper.cc(260)] 
GetVSyncParametersIfAvailable() failed for 3 times!

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.16
  ProcVersionSignature: Ubuntu 5.19.0-43.44~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-43-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  2 21:05:25 2023
  InstallationDate: Installed on 2023-05-31 (1 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to jammy on 2023-06-02 (0 days ago)
  mtime.conffile..etc.update-manager.release-upgrades: 
2023-06-02T20:53:40.853011

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libva/+bug/2022364/+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 1993478] Re: package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade: postinstall script returned 1

[Benjamin Drung]

** Tags removed: foundations-todo

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

Title:
  package openssh-server 1:9.0p1-1ubuntu7 failed to install/upgrade:
  postinstall script returned 1

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

Bug description:
  [Impact]

  Users with /etc/ssh/sshd_config's that contain ListenAddress entries
  with the port specified will not be migrated to socket-activated ssh
  correctly, or may be migrated when they should not be (e.g. if
  ListenAddress, with a port number, is specified more than once). This
  leaves users with a broken sshd configuration.

  [Test Plan]

  There are 4 tests that should be used to verify the fix:

  1. Upgrade to Kinetic with just one ListenAddress entry, which
  specifies port number.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Before running the upgrade, make sure -proposed is enabled.
  * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, 
and then running apt dist-upgrade (-proposed is disabled when using 
ubuntu-release-upgrader).
  * On an affected system, ssh.socket will fail with `bad-setting` because 
/etc/systemd/system/ssh.socket.d/address.conf contains:

  [Socket]
  ListenStream=

  * On a patched system, ssh.socket will be active/listening, and
  /etc/systemd/system/ssh.socket.d/addresses.conf will contain the
  following:

  [Socket]
  ListenStream=
  ListenStream=0.0.0.0:1234

  2. Upgrade to Kinetic with multiple ListenAddress entries, each
  specifying port number.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234
  ListenAddress [::]:4321

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Before running the upgrade, make sure -proposed is enabled.
  * Upgrade to Kinetic by changing jammy -> kinetic in /etc/apt/sources.list, 
and then running apt dist-upgrade (-proposed is disabled when using 
ubuntu-release-upgrader).
  * On an affected system, migration will be attempted despite the multiple 
ListenAddress options, and ssh.socket will fail with `bad-setting` because 
/etc/systemd/system/ssh.socket.d/address.conf contains:

  [Socket]
  ListenStream=

  * On a patched system, the ListenAddress option will be parsed
  correctly, and migration will not be attempted.

  3. On a Kinetic system which was migrated, but with errors (e.g. test
  case #1, prior to being patched), installing the new package should
  correct the ssh.socket configuration.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Do NOT enable -proposed before the upgrade.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * After the openssh-server configuration fails, enable -proposed, and upgrade 
openssh-server.

  * The ssh.socket configuration should be fixed, and 
/etc/systemd/system/ssh.socket.d/addresses.conf should contain:
  [Socket]
  ListenStream=
  ListenStream=0.0.0.0:1234

  4. On a Kinetic system which was incorrectly migrated to ssh socket
  activation (e.g. test case #2, prior to being patched), installing the
  new package reverts to the previous behavior.

  * On a Jammy system, edit /etc/ssh/sshd_config so that it contains the
  following:

  [...defaults everywhere else...]

  #Port 22
  #AddressFamily any
  #ListenAddress 0.0.0.0
  #ListenAddress ::
  ListenAddress 0.0.0.0:1234
  ListenAddress [::]:4321

  [...defaults everywhere else...]

  * Run `systemctl restart ssh.service` and confirm that the new configuration 
works as expected.
  * Do NOT enable -proposed before the upgrade.
  * Run `do-release-upgrade` to upgrade to Kinetic (setting Prompt=normal in 
/etc/update-manager/release-upgrades if needed).
  * After the openssh-server configuration fails, enable -proposed, and upgrade 
openssh-server.
  * The socket-activated ssh migration should be reverted, and ssh.service 
should be running as before upgrade to Kinetic.

  [Where problems 

[Touch-packages] [Bug 1964828] Re: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'

[Benjamin Drung]

** Tags removed: foundations-todo

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

Title:
  /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError:
  'CasperMD5json'

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Released
Status in apport source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  If the user reports a bug and rejects to enter the root password for
  collecting information (like the CasperMD5json), the Ubuntu add_info
  hook will fail with a stack trace. The remaining code for collecting
  more information is not executed. So the resulting bug reports will be
  less helpful. The check_for_disk_error call is not reached and
  therefore skipped.

  [Test Plan]

  1. Install Ubuntu (e.g. from ubuntu-22.04-desktop-amd64.iso)
  2. Open a terminal
  3. Run: ubuntu-bug -f
  4. Select "installer" and click on OK
  5. Click on "abort" when ask for the password
  6. The terminal should not show a stacktrace

  [Where problems could occur]

  The changed code is the Ubuntu add_info hook. So this hook could fail
  due to a regression or reveal bugs in the later code path. The later
  code path could cause more more load on the users machine (but only
  when the user wants to report the issue). Apport will catch failing
  add_info hooks and store the failure in the report.

  [Orinial report]

  ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
  symb['add_info'](report, ui)
    File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info
  apport.hookutils.attach_casper_md5check(report,
    File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in 
attach_casper_md5check
  check = json.loads(report['CasperMD5json'])
    File "/usr/lib/python3.10/collections/__init__.py", line 1102, in 
__getitem__
  raise KeyError(key)
  KeyError: 'CasperMD5json'
  kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module 
"colorreload-gtk-module"
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity 22.04.7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperVersion: 1.467
  CurrentDesktop: KDE
  Date: Mon Mar 14 21:22:23 2022
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1964828/+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 1995100] Re: /usr/share/apport/whoopsie-upload-all:ValueError:/usr/share/apport/whoopsie-upload-all@249:main:collect_info:process_report:load

[Benjamin Drung]

** Tags removed: foundations-todo

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:ValueError:/usr/share/apport/whoopsie-upload-
  all@249:main:collect_info:process_report:load

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Kinetic:
  Fix Released

Bug description:
  Impact
  ==

  apport-unpack and whoopsie-upload-all can crash when fed with a
  malformed problem report. They should print a proper error message
  instead of crashing. This is the most occurring apport bug in Ubuntu
  22.10 (kinetic) with as of writing 14,822 reported crashes.

  Test Plan
  =

  1. Create malformed report:
  ```
  echo > malformed.crash
  ```
  2. Try to unpack it:
  ```
  apport-unpack malformed.crash unpack
  ```

  It should print an error message instead of a stack trace.

  Where problems could occur
  ==

  The patch touches the problem report handling and therefore can affect
  apport-unpack, apport-bug, whoopsie-upload-all. The change is covered
  with tests and apport has a test suite running during build and as
  autopkgtest.

  Original report
  ===

  ```
  Traceback (most recent call last):
    File "/usr/share/apport/whoopsie-upload-all", line 249, in 
  main()
    File "/usr/share/apport/whoopsie-upload-all", line 231, in main
  stamps = collect_info()
    File "/usr/share/apport/whoopsie-upload-all", line 162, in collect_info
  res = process_report(r)
    File "/usr/share/apport/whoopsie-upload-all", line 76, in process_report
  r.load(f, binary="compressed")
    File "/usr/lib/python3/dist-packages/problem_report.py", line 166, in load
  (key, value) = line.split(b":", 1)
  ValueError: not enough values to unpack (expected 2, got 1)
  ```

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.23.1-0ubuntu3, the problem page at 
https://errors.ubuntu.com/problem/134ffbe13e7dd9a7f79ad6a455c6e560669a9928 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1995100/+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 2015355] Re: Please backport patches for false atari partition detection to Ubuntu 20.04

[Nick Rosbrook]

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/util-linux/+git/util-linux/+merge/443898

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

Title:
  Please backport patches for false atari partition detection to Ubuntu
  20.04

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Focal:
  In Progress

Bug description:
  [Impact]

  The partition detection logic in libblkid1 can falsely report the
  presence of an atari partition. One place where this has a practical
  impact is in kubernetes where mount-utils will refuse to format the
  device (https://github.com/kubernetes/mount-
  utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441).

  [Test Plan]

  * Create a new qcow2 disk image:

  $ qemu-img create -f qcow2 test.img 20G

  * Boot a focal ISO with QEMU/KVM as if installing to test.img:

  $ qemu-system-x86_64 -enable-kvm -m 4096 -name test -drive
  file=test.img,format=qcow2 -net nic,model=virtio -net
  user,hostfwd=tcp::1022-:22 -vga virtio -cdrom ubuntu-20.04.6-desktop-
  amd64.iso

  * Using the live environment, format the empty disk. These particular
  commands were given as a reproducer on the upstream bug report
  (https://github.com/util-linux/util-linux/issues/1116).

  $ parted -s /dev/sda -- mklabel msdos
  $ parted -s /dev/sda -- mkpart primary 0% 10% mkpart primary 10% 30%

  * Run wipefs on /dev/sda to list partitions. On an affected machine,
  an atari partition will be listed. On a fixed machine, the incorrect
  atari listing will be gone.

  $ wipefs /dev/sda
  DEVICE OFFSET TYPE  UUID LABEL
  sda0x1fe  dos
  sda0x1d2  atari

  [Where problems could occur]

  These patches specifically address the atari prober logic in libblkid.
  Therefore, if we saw regressions it would be related to detecting
  atari partitions with libblkid. This would potentially impact tools
  such as wipefs and blkid, or any other tool that uses libblkid1 for
  this purpose.

  [Original Description]

  There are three patches in util-linux upstream that were released in
  util-linux 2.37 and prevent false detection of the atari partition
  table with blkid and wipefs. We see this mostly on LUKS devices
  initialised via luksFormat reporting there is an atari partition table
  on the device when it is empty. This causes issues in various places,
  but one key example for us is in kubernetes where mount-utils will
  refuse to format the device (https://github.com/kubernetes/mount-
  utils/blob/732a08ae47571516020ef99c303c70c1fa5b3e6c/mount_linux.go#L437-L441)

  RedHat backported these fixes to RHEL 8 under
  https://bugzilla.redhat.com/show_bug.cgi?id=2060030 and it would be
  helpful if Ubuntu also backported them to Ubuntu 20.04 which is still
  running util-linux 2.34

  The request is to backport patches based on the
  https://github.com/util-linux/util-linux/issues/1159 upstream report.

  Upstream commits to cherry-pick the changes to 
libblkid/src/partitions/atari.c from:
  2cc76d50d7a14bef8e7b07fab11b26c9e49d36a2
  282ceadc3a72fc07dd0388b8880fd751490bb87f
  c70b4f2a5b99876d230b8f4f413c3bb3ee6647f1

  # lsb_release -a
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04.6 LTS
  Release:20.04
  Codename:   focal
  # blkid -V
  blkid from util-linux 2.34  (libblkid 2.34.0, 14-Jun-2019)
  # blkid -p -s TYPE -s PTTYPE -o export 
/dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted
  DEVNAME=dev/mapper/pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted
  PTTYPE=atari
  # lsblk
  ...
  sdccrypto_LUKS
 a79d2982-74f2-44c7-bb29-460768ebfe64
  `-3600a09803830474a735d4c63744c4a56crypto_LUKS
 a79d2982-74f2-44c7-bb29-460768ebfe64
    `-pvc-7b331195-cd5a-4ab6-8fdc-552af4b9139d_encrypted

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

I also tested upgrades from 1:9.0p1-1ubuntu7.3 in kinetic-proposed to
1:9.0p1-1ubuntu8.2 in lunar-proposed to confirm we won't be introducing
bug 2020474:

root@kinetic:~# ssh localhost
Welcome to Ubuntu 22.10 (GNU/Linux 6.2.0-20-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

root@kinetic:~# apt-cache policy openssh-server
openssh-server:
  Installed: 1:9.0p1-1ubuntu7.3
  Candidate: 1:9.0p1-1ubuntu7.3
  Version table:
 *** 1:9.0p1-1ubuntu7.3 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 1:9.0p1-1ubuntu7.1 500
500 http://archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages
 1:9.0p1-1ubuntu7 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
root@kinetic:~# sed -i 's/kinetic/lunar/g' /etc/apt/sources.list
root@kinetic:~# apt update
Get:1 http://archive.ubuntu.com/ubuntu lunar InRelease [267 kB]
Get:2 http://security.ubuntu.com/ubuntu lunar-security InRelease [109 kB]
Get:3 http://security.ubuntu.com/ubuntu lunar-security/main amd64 Packages 
[69.9 kB]
Get:4 http://archive.ubuntu.com/ubuntu lunar-updates InRelease [109 kB]
Get:5 http://security.ubuntu.com/ubuntu lunar-security/main Translation-en 
[20.5 kB]
Get:6 http://security.ubuntu.com/ubuntu lunar-security/universe amd64 Packages 
[33.4 kB]
Get:7 http://security.ubuntu.com/ubuntu lunar-security/universe Translation-en 
[11.0 kB]
Get:8 http://archive.ubuntu.com/ubuntu lunar-proposed InRelease [255 kB]
   
Get:9 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages [1,396 kB]
Get:10 http://archive.ubuntu.com/ubuntu lunar/main Translation-en [513 kB]
Get:11 http://archive.ubuntu.com/ubuntu lunar/restricted amd64 Packages [143 kB]
Get:12 http://archive.ubuntu.com/ubuntu lunar/restricted Translation-en [21.9 
kB]
Get:13 http://archive.ubuntu.com/ubuntu lunar/universe amd64 Packages [15.0 MB]
Get:14 http://archive.ubuntu.com/ubuntu lunar/universe Translation-en [5,906 kB]
Get:15 http://archive.ubuntu.com/ubuntu lunar/multiverse amd64 Packages [236 kB]
Get:16 http://archive.ubuntu.com/ubuntu lunar/multiverse Translation-en [112 kB]
Get:17 http://archive.ubuntu.com/ubuntu lunar-updates/main amd64 Packages [124 
kB]
Get:18 http://archive.ubuntu.com/ubuntu lunar-updates/main Translation-en [33.5 
kB]
Get:19 http://archive.ubuntu.com/ubuntu lunar-updates/universe amd64 Packages 
[63.0 kB]
Get:20 http://archive.ubuntu.com/ubuntu lunar-updates/universe Translation-en 
[20.7 kB]
Get:21 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages 
[64.7 kB]
Get:22 http://archive.ubuntu.com/ubuntu lunar-proposed/main Translation-en 
[18.3 kB]
Get:23 http://archive.ubuntu.com/ubuntu lunar-proposed/restricted amd64 
Packages [82.7 kB]
Get:24 http://archive.ubuntu.com/ubuntu lunar-proposed/restricted 
Translation-en [15.6 kB]
Get:25 http://archive.ubuntu.com/ubuntu lunar-proposed/universe amd64 Packages 
[20.0 kB]
Get:26 http://archive.ubuntu.com/ubuntu lunar-proposed/universe Translation-en 
[9,732 B]
Get:27 http://archive.ubuntu.com/ubuntu lunar-proposed/multiverse amd64 
Packages [8,192 B]
Get:28 http://archive.ubuntu.com/ubuntu lunar-proposed/multiverse 
Translation-en [2,572 B]
Fetched 24.7 MB in 4s (5,656 kB/s) 
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
204 packages can be upgraded. Run 'apt list --upgradable' to see them.
root@kinetic:~# apt-cache policy openssh-server
openssh-server:
  Installed: 1:9.0p1-1ubuntu7.3
  Candidate: 1:9.0p1-1ubuntu8
  Version table:
 1:9.0p1-1ubuntu8.2 100
100 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
 1:9.0p1-1ubuntu8 500
500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
 *** 1:9.0p1-1ubuntu7.3 100
100 /var/lib/dpkg/status
root@kinetic:~# lsof -i :22
COMMAND  PID USER   FD   TYPE  DEVICE SIZE/OFF NODE NAME
systemd1 root   42u  IPv6 1991217  0t0  TCP *:ssh (LISTEN)
sshd1011 root3u  IPv6 1991217  0t0  TCP *:ssh (LISTEN)
ssh 1015 root3u  IPv6 1988536  0t0  TCP 
localhost:34296->localhost:ssh (ESTABLISHED)
sshd1016 root4u  IPv6 1992984  0t0  TCP 
localhost:ssh->localhost:34296 (ESTABLISHED)
root@kinetic:~# apt install openssh-server=1:9.0p1-1ubuntu8.2 
openssh-client=1:9.0p1-1ubuntu8.2 openssh-sftp-server=1:9.0p1-1ubuntu8.2 -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libssl3 openssl
Suggested packages:
  

[Touch-packages] [Bug 2011458] Re: ssh fails to rebind when it is killed with -HUP

[Nick Rosbrook]

I have verified the fix using openssh 1:9.0p1-1ubuntu8.2 from lunar-
proposed:

Test 1:

root@lunar:~# apt-cache policy openssh-server
openssh-server:
  Installed: 1:9.0p1-1ubuntu8.2
  Candidate: 1:9.0p1-1ubuntu8.2
  Version table:
 *** 1:9.0p1-1ubuntu8.2 500
500 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:9.0p1-1ubuntu8 500
500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
root@lunar:~# ssh localhost
The authenticity of host 'localhost (::1)' can't be established.
ED25519 key fingerprint is SHA256:pGn2A4yGeFN/7Rlk830HLUMQqsybaSmP36MPGpmKXmQ.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'localhost' (ED25519) to the list of known hosts.
Welcome to Ubuntu 23.04 (GNU/Linux 6.2.0-20-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

root@lunar:~# systemctl reload ssh
root@lunar:~# 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
 /run/systemd/system/service.d
 └─zzz-lxc-service.conf
 Active: active (running) since Fri 2023-06-02 14:13:03 UTC; 11s ago
TriggeredBy: ● ssh.socket
   Docs: man:sshd(8)
 man:sshd_config(5)
Process: 1030 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Process: 1062 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Process: 1063 ExecReload=/bin/kill -HUP $MAINPID (code=exited, 
status=0/SUCCESS)
   Main PID: 1031 (sshd)
  Tasks: 1 (limit: 18854)
 Memory: 3.2M
CPU: 101ms
 CGroup: /system.slice/ssh.service
 └─1031 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

Jun 02 14:13:03 lunar systemd[1]: Starting ssh.service - OpenBSD Secure Shell 
server...
Jun 02 14:13:03 lunar sshd[1031]: Server listening on :: port 22.
Jun 02 14:13:03 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell 
server.
Jun 02 14:13:04 lunar sshd[1032]: Accepted publickey for root from ::1 port 
53474 ssh2: RSA SHA256:KzrBiY2sWqLQ5WWGGUo>
Jun 02 14:13:04 lunar sshd[1032]: pam_unix(sshd:session): session opened for 
user root(uid=0) by (uid=0)
Jun 02 14:13:04 lunar sshd[1032]: pam_env(sshd:session): deprecated reading of 
user environment enabled
Jun 02 14:13:10 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure Shell 
server...
Jun 02 14:13:10 lunar sshd[1031]: Received SIGHUP; restarting.
Jun 02 14:13:10 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell 
server.
Jun 02 14:13:10 lunar sshd[1031]: Server listening on :: port 22.

Test 2:

root@lunar:~# vi /etc/default/ssh 
root@lunar:~# 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
root@lunar:~# ssh localhost
Welcome to Ubuntu 23.04 (GNU/Linux 6.2.0-20-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage
Last login: Fri Jun  2 14:13:04 2023 from ::1
debug1: PAM: reinitializing credentials
debug1: permanently_set_uid: 0/0
debug3: Copy environment: XDG_SESSION_ID=111
debug3: Copy environment: XDG_RUNTIME_DIR=/run/user/0
debug3: Copy environment: DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/0/bus
debug3: Copy environment: XDG_SESSION_TYPE=tty
debug3: Copy environment: XDG_SESSION_CLASS=user
debug3: Copy environment: 
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
debug3: Copy environment: LANG=en_US.UTF-8
Environment:
  LANG=en_US.UTF-8
  USER=root
  LOGNAME=root
  HOME=/root
  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
  SHELL=/bin/bash
  TERM=xterm-256color
  XDG_SESSION_ID=111
  XDG_RUNTIME_DIR=/run/user/0
  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/0/bus
  XDG_SESSION_TYPE=tty
  XDG_SESSION_CLASS=user
  SSH_CLIENT=::1 58114 22
  SSH_CONNECTION=::1 58114 ::1 22
  SSH_TTY=/dev/pts/2
root@lunar:~# 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
 /run/systemd/system/service.d
 └─zzz-lxc-service.conf
 Active: active (running) since Fri 2023-06-02 14:14:30 UTC; 3s ago

[Touch-packages] [Bug 2011458] Re: ssh fails to rebind when it is killed with -HUP

[Nick Rosbrook]

I have confirmed the fix using openssh 1:9.0p1-1ubuntu7.3 from kinetic-
proposed:

Test 1:

root@kinetic:~# apt-cache policy openssh-server
openssh-server:
  Installed: 1:9.0p1-1ubuntu7.3
  Candidate: 1:9.0p1-1ubuntu7.3
  Version table:
 *** 1:9.0p1-1ubuntu7.3 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 1:9.0p1-1ubuntu7.1 500
500 http://archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages
 1:9.0p1-1ubuntu7 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
root@kinetic:~# ssh localhost
The authenticity of host 'localhost (::1)' can't be established.
ED25519 key fingerprint is SHA256:xmU0f5QuqvJ8GZVhZihANPUgBhUzvYo96entI7JuoRk.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'localhost' (ED25519) to the list of known hosts.
Welcome to Ubuntu 22.10 (GNU/Linux 6.2.0-20-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

root@kinetic:~# systemctl reload ssh.service
root@kinetic:~# 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
 /run/systemd/system/service.d
 └─zzz-lxc-service.conf
 Active: active (running) since Fri 2023-06-02 13:48:58 UTC; 42s ago
TriggeredBy: ● ssh.socket
   Docs: man:sshd(8)
 man:sshd_config(5)
Process: 1012 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Process: 1046 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Process: 1047 ExecReload=/bin/kill -HUP $MAINPID (code=exited, 
status=0/SUCCESS)
   Main PID: 1013 (sshd)
  Tasks: 1 (limit: 18854)
 Memory: 3.2M
CPU: 94ms
 CGroup: /system.slice/ssh.service
 └─1013 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

Jun 02 13:48:58 kinetic systemd[1]: Starting OpenBSD Secure Shell server...
Jun 02 13:48:58 kinetic sshd[1013]: Server listening on :: port 22.
Jun 02 13:48:58 kinetic systemd[1]: Started OpenBSD Secure Shell server.
Jun 02 13:49:00 kinetic sshd[1014]: Accepted publickey for root from ::1 port 
44690 ssh2: RSA SHA256:A+T8Yt6KxQdy0hmT8>
Jun 02 13:49:00 kinetic sshd[1014]: pam_unix(sshd:session): session opened for 
user root(uid=0) by (uid=0)
Jun 02 13:49:00 kinetic sshd[1014]: pam_env(sshd:session): deprecated reading 
of user environment enabled
Jun 02 13:49:26 kinetic systemd[1]: Reloading OpenBSD Secure Shell server...
Jun 02 13:49:26 kinetic sshd[1013]: Received SIGHUP; restarting.
Jun 02 13:49:26 kinetic systemd[1]: Reloaded OpenBSD Secure Shell server.
Jun 02 13:49:27 kinetic sshd[1013]: Server listening on :: port 22.

Test 2:

root@kinetic:~# vi /etc/default/ssh 
root@kinetic:~# 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
root@kinetic:~# ssh localhost
Welcome to Ubuntu 22.10 (GNU/Linux 6.2.0-20-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage
Last login: Fri Jun  2 13:49:00 2023 from ::1
debug1: PAM: reinitializing credentials
debug1: permanently_set_uid: 0/0
debug3: Copy environment: XDG_SESSION_ID=104
debug3: Copy environment: XDG_RUNTIME_DIR=/run/user/0
debug3: Copy environment: DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/0/bus
debug3: Copy environment: XDG_SESSION_TYPE=tty
debug3: Copy environment: XDG_SESSION_CLASS=user
debug3: Copy environment: 
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
debug3: Copy environment: LANG=en_US.UTF-8
Environment:
  LANG=en_US.UTF-8
  USER=root
  LOGNAME=root
  HOME=/root
  
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
  SHELL=/bin/bash
  TERM=xterm-256color
  XDG_SESSION_ID=104
  XDG_RUNTIME_DIR=/run/user/0
  DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/0/bus
  XDG_SESSION_TYPE=tty
  XDG_SESSION_CLASS=user
  SSH_CLIENT=::1 47582 22
  SSH_CONNECTION=::1 47582 ::1 22
  SSH_TTY=/dev/pts/2
root@kinetic:~# 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
 

[Touch-packages] [Bug 1733321] Re: network-manager ADT tests fail with on ppc64el with artful/linux 4.13.0.17.18

[Łukasz Zemczak]

Resurrected the removed upload into bionic-proposed. After some
discussion we decided not to remove autopkgtest regression fix uploads
from -proposed for series that are transitioning to ESM as they might be
useful as a base for any ESM follow up uploads.

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

Title:
  network-manager ADT tests fail with on ppc64el with artful/linux
  4.13.0.17.18

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Artful:
  Won't Fix
Status in network-manager source package in Bionic:
  Won't Fix
Status in network-manager source package in Disco:
  Won't Fix
Status in network-manager source package in Eoan:
  Fix Released
Status in network-manager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The killswitches-no-urfkill autopkgtest fails sometimes because nmcli
  reports the old state when it's called right after rfkill
  block/unblock.

  ppc64el ADT log from failed testcase:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  artful/artful/ppc64el/n/network-manager/20171120_100719_28642@/log.gz

  Testcase output:
  -
  autopkgtest [10:04:48]: test killswitches-no-urfkill: [---
  make -C /lib/modules/4.13.0-17-generic/build 
KBUILD_SRC=/lib/modules/4.13.0-17-generic/build 
M=/tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests
  make[1]: Entering directory '/usr/src/linux-headers-4.13.0-17-generic'
    AR  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/built-in.o
    CC [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.mod.o
    LD [M]  /tmp/autopkgtest.yE1hsA/build.62e/src/debian/tests/fake-rfkill.ko
  make[1]: Leaving directory '/usr/src/linux-headers-4.13.0-17-generic'
  ERROR: NM could not track device state.
  autopkgtest [10:05:20]: test killswitches-no-urfkill: ---]
  autopkgtest [10:05:20]: test killswitches-no-urfkill:  - - - - - - - - - - 
results - - - - - - - - - -
  killswitches-no-urfkill FAIL non-zero exit status 1
  -

  Package versions [artful/ppc64el]:
  network-manager 1.8.4-1ubuntu3
  linux-meta 4.13.0.17.18

  [Test Case]

  Assume that test vm and host are ppc64

  1. deploy ppc64 vm instance ( with 1 cpu )
  2. modprobe mac80211_hwsim ( may need to install linux-modules-extra- pkg )
  3. apt install network-manager rfkill
  4. modify /etc/netplan/[conf], renderer as NetworkManager
  5. netplan apply
  6. run below command
  - nmcli radio wifi ; rfkill list 0 ; rfkill block 0 ; rfkill list 0 ; nmcli 
radio wifi ; rfkill list 0 ; rfkill unblock 0 ; rfkill list 0 ; nmcli radio wifi

  enabled
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  enabled
  0: fake: Wireless LAN
  Soft blocked: yes
  Hard blocked: no
  0: fake: Wireless LAN
  Soft blocked: no
  Hard blocked: no
  enabled

  second 'enabled' should be 'disabled' but not updated properly.

  Adding "udevadm settle" in test file ( killswitches-no-urkfill ) between
  rfkill block/unblock and nmcli radio wifi will help updating status changes 
after rfkill block/unblock.

  [Regression Potential]

  This fixes testcase only, so any regression would cause incorrect test
  pass/fail, and might cause other missed bugs.

  [scope]

  this is needed for all releases.  Debian does not include this
  autopkgtest, and so does not need this fix.

  [Other Info]

  this is caused by the 'systemd-rfkill.socket' listening to rfkill, and
  starting up 'systemd-rfkill.service' for any change.  On a 1-cpu
  system (which all autopkgtest instances for network-manager are), this
  service startup sometimes blocks the uevent from reaching network-
  manager before the autopkgtest proceeds to call nmcli to check the
  rfkill status.  This causes the test case to fail.

  There are (at least) 2 options to fix this:
  1) stop/disable the 'systemd-rfkill.socket' at the start of the autopkgtest
  2) call udevadm settle between the rfkill block/unblock and the nmcli call to 
check status

  This does not need to be fixed outside the test case, as normal nmcli
  use should be not done by users in a script immediately after changing
  rfkill state, nor is there anything that either rfkill or nmcli could
  even do to address this (technically, nmcli could internally issue a
  'udevadm settle' every time it's called, but that seems paranoid and
  extreme).

  [original description]

  On ppc64el architecture, it was observed that a fix for systemd is
  also needed (see bug 1734908) for the testcase to be successful.

  # original test case

  2.1. Download network-manager package 

[Touch-packages] [Bug 1813581] Re: gpgme1.0 ftbfs in 18.04 LTS

[Łukasz Zemczak]

Resurrected the removed upload into bionic-proposed. After some
discussion we decided not to remove autopkgtest regression fix uploads
from -proposed for series that are transitioning to ESM as they might be
useful as a base for any ESM follow up uploads.

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

Title:
  gpgme1.0 ftbfs in 18.04 LTS

Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in gpgme1.0 source package in Bionic:
  Won't Fix

Bug description:
  [Impact]
  according to
  
http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20181222-bionic.html

  gpgme1.0 ftbfs.

  * Start testing of TofuInfoTest *
  Config: Using QtTest library 5.9.5, Qt 5.9.5 (x86_64-little_endian-lp64 
shared (dynamic) release build; by GCC 7.3.0)
  PASS   : TofuInfoTest::initTestCase()
  PASS   : TofuInfoTest::testTofuNull()
  PASS   : TofuInfoTest::testTofuInfo()
  PASS   : TofuInfoTest::testTofuSignCount()
  PASS   : TofuInfoTest::testTofuKeyList()
  PASS   : TofuInfoTest::testTofuPolicy()
  FAIL!  : TofuInfoTest::testTofuConflict() 'sig.validity() == 
Signature::Marginal' returned FALSE. ()
     Loc: [t-tofuinfo.cpp(458)]
  PASS   : TofuInfoTest::cleanupTestCase()
  Totals: 7 passed, 1 failed, 0 skipped, 0 blacklisted, 2386ms
  * Finished testing of TofuInfoTest *
  FAIL: t-tofuinfo

  [Test case]
  build it

  [Regression potential]
  This only changes the test suite run during build, and that one currently 
fails, so it can't cause any regression.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1813581/+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] Autopkgtest regression report (openssh/1:9.0p1-1ubuntu7.2)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted openssh (1:9.0p1-1ubuntu7.2) for 
kinetic have finished running.
The following regressions have been reported in tests triggered by the package:

hg-git/0.10.4-3 (amd64, arm64, armhf, ppc64el, s390x)
piuparts/1.1.5 (amd64, arm64, ppc64el, s390x)
sbuild/0.83.1ubuntu1 (arm64, ppc64el, s390x)


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/kinetic/update_excuses.html#openssh

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

[Touch-packages] [Bug 2011458] Autopkgtest regression report (openssh/1:9.0p1-1ubuntu8.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted openssh (1:9.0p1-1ubuntu8.1) for lunar 
have finished running.
The following regressions have been reported in tests triggered by the package:

ganeti/3.0.2-3 (arm64, ppc64el)


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/lunar/update_excuses.html#openssh

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

[Touch-packages] [Bug 2011458] Please test proposed package

[Timo Aaltonen]

Hello Sergio, or anyone else affected,

Accepted openssh into kinetic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openssh/1:9.0p1-1ubuntu7.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

[Touch-packages] [Bug 2011458] Re: ssh fails to rebind when it is killed with -HUP

[Timo Aaltonen]

Hello Sergio, or anyone else affected,

Accepted openssh into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssh/1:9.0p1-1ubuntu8.2 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 2022322] Re: Gnome right butons bug

[Launchpad Bug Tracker]

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

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

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

Title:
  Gnome right butons bug

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  In the superior right corner, there are a region (about 5x5 cm2) that
  mouse do nothing, mainly in minimize and close butons, but ocouring to
  in menus, just in this corner.

  Double click in title bar force the restore and then, moving the
  software window to far of this corner, works properly.

  Thanks.

  Mr. Wagner Yaegashi

  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
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  2 06:13:24 2023
  DistUpgraded: 2023-05-12 23:47:44,660 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Samsung Electronics Co Ltd UHD Graphics 620 [144d:c804]
  InstallationDate: Installed on 2022-05-01 (396 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 340XAA/350XAA/550XAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=21a2de05-0384-44e8-9367-ab55a551cc2d ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to lunar on 2023-05-13 (20 days ago)
  dmi.bios.date: 07/14/2021
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P04REP.035.210714.ZW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP350XAA-KD1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9477A0K-C01-G001-S0001+10.0.17134
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04REP.035.210714.ZW:bd07/14/2021:br5.12:svnSAMSUNGELECTRONICSCO.,LTD.:pn340XAA/350XAA/550XAA:pvrP04REP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350XAA-KD1BR:rvrSGL9477A0K-C01-G001-S0001+10.0.17134:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PREP:
  dmi.product.family: Notebook 3 Series
  dmi.product.name: 340XAA/350XAA/550XAA
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREP
  dmi.product.version: P04REP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  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 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/+source/xorg/+bug/2022322/+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 2022107] Re: printing dubugging doesnt work!

[Sebastien Bacher]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

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

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

Title:
  printing dubugging doesnt work!

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  1  cupsdisable OKI-C332-411ACB 
  cupsdisable: Operation failed: client-error-not-found

  2   wget http://people.canonical.com/~pitti/tmp/cups.upstart.debug
  --2023-06-01 21:57:49--  
http://people.canonical.com/~pitti/tmp/cups.upstart.debug
  Resolving people.canonical.com (people.canonical.com)... 185.125.188.97
  Connecting to people.canonical.com 
(people.canonical.com)|185.125.188.97|:80... connected.
  HTTP request sent, awaiting response... 301 Moved Permanently
  Location: https://people.canonical.com/~pitti/tmp/cups.upstart.debug 
[following]
  --2023-06-01 21:57:49--  
https://people.canonical.com/~pitti/tmp/cups.upstart.debug
  Connecting to people.canonical.com 
(people.canonical.com)|185.125.188.97|:443... connected.
  HTTP request sent, awaiting response... 403 Forbidden
  2023-06-01 21:57:49 ERROR 403: Forbidden.

  Description:  Ubuntu 20.04.6 LTS
  Release:  20.04

  sudo: aa-complain: command not found

  /usr/lib/cups/backend/snmp
  network socket://192.168.1.201 "OKI DATA CORP C332" "C332" "MFG:OKI DATA 
CORP;CMD:PCL,XPS,IBMPPR,EPSONFX,POSTSCRIPT,PDF,PCLXL,HIPERMIP,URF;MDL:C332;CLS:PRINTER;DES:OKI
 C332;CID:OK_N_B800;" ""

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.2
  ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98
  Uname: Linux 5.15.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun  1 21:59:57 2023
  InstallationDate: Installed on 2023-04-25 (37 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  Lpstat: device for OKI_C332_411ACB@oki-c332-411acb.local: 
implicitclass://OKI_C332_411ACB%40oki-c332-411acb.local/
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b685 Chicony Electronics Co., Ltd Chicony USB2.0 
Camera
   Bus 001 Device 002: ID 3151:3020 YICHIP Wireless Device
   Bus 001 Device 004: ID 8087:0025 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Novatech N150ZU
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/oki_c332_411...@oki-c332-411acb.local.ppd'] failed with exit 
code 2: grep: /etc/cups/ppd/oki_c332_411...@oki-c332-411acb.local.ppd: 
Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-72-generic 
root=UUID=2c0e4998-ac9a-4c3c-ab96-b2b45fe5eab7 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2019
  dmi.bios.release: 7.7
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.07TNO
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: N150ZU
  dmi.board.vendor: Novatech
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Novatech
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.4
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.07TNO:bd06/24/2019:br7.7:efr7.4:svnNovatech:pnN150ZU:pvrNotApplicable:rvnNovatech:rnN150ZU:rvrNotApplicable:cvnNovatech:ct10:cvrN/A:skuNotApplicable:
  dmi.product.family: Not Applicable
  dmi.product.name: N150ZU
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Novatech

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/2022107/+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 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Benjamin Drung]

Bug #2008430 could be a use-case.

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  New
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

  [ Test Plan ]

  1. Install the affected package and pip 

[Touch-packages] [Bug 2022322] [NEW] Gnome right butons bug

[Wagner H Yaegashi]

Public bug reported:

In the superior right corner, there are a region (about 5x5 cm2) that
mouse do nothing, mainly in minimize and close butons, but ocouring to
in menus, just in this corner.

Double click in title bar force the restore and then, moving the
software window to far of this corner, works properly.

Thanks.

Mr. Wagner Yaegashi

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
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  2 06:13:24 2023
DistUpgraded: 2023-05-12 23:47:44,660 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: lunar
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Samsung Electronics Co Ltd UHD Graphics 620 [144d:c804]
InstallationDate: Installed on 2022-05-01 (396 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: SAMSUNG ELECTRONICS CO., LTD. 340XAA/350XAA/550XAA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=21a2de05-0384-44e8-9367-ab55a551cc2d ro quiet splash vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to lunar on 2023-05-13 (20 days ago)
dmi.bios.date: 07/14/2021
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P04REP.035.210714.ZW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP350XAA-KD1BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGL9477A0K-C01-G001-S0001+10.0.17134
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP04REP.035.210714.ZW:bd07/14/2021:br5.12:svnSAMSUNGELECTRONICSCO.,LTD.:pn340XAA/350XAA/550XAA:pvrP04REP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350XAA-KD1BR:rvrSGL9477A0K-C01-G001-S0001+10.0.17134:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-A5A5-A5A5-A5A5-PREP:
dmi.product.family: Notebook 3 Series
dmi.product.name: 340XAA/350XAA/550XAA
dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREP
dmi.product.version: P04REP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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 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 corruption 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/2022322

Title:
  Gnome right butons bug

Status in xorg package in Ubuntu:
  New

Bug description:
  In the superior right corner, there are a region (about 5x5 cm2) that
  mouse do nothing, mainly in minimize and close butons, but ocouring to
  in menus, just in this corner.

  Double click in title bar force the restore and then, moving the
  software window to far of this corner, works properly.

  Thanks.

  Mr. Wagner Yaegashi

  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
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun  2 06:13:24 2023
  DistUpgraded: 2023-05-12 23:47:44,660 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Samsung Electronics Co Ltd UHD Graphics 620 [144d:c804]
  InstallationDate: Installed on 2022-05-01 (396 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 340XAA/350XAA/550XAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=21a2de05-0384-44e8-9367-ab55a551cc2d ro quiet splash vt.handoff=7
  RebootRequiredPkgs: Error: path contained 

[Touch-packages] [Bug 1971242] Re: printing PDF appears always grey, no color

[Sebastien Bacher]

Till, sounds like we should at least SRU
https://github.com/OpenPrinting/cups/commit/9b31bae and
https://github.com/OpenPrinting/cups/commit/b0f1a00a to 22.04 to fix
that issue, could you work on that and maybe check if that are more
fixes worth SRUing as we do an upload?

** Changed in: cups (Ubuntu)
   Importance: Undecided => High

** Changed in: cups (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

-- 
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 2008846] Re: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1

[Adrien Nader]

Derek, do you have more logs for April 24? It would be very valuable to
know what started the apt/dpkg processes. These files would be useful
(most are rotated: most likely data for April 24 is in a foo.*.gz file):

apt/dpkg/unattended-upgrades logs:
- /var/log/apt/history.log*
- /var/log/apt/term.log*
- /var/log/dpkg.log*
 -/var/log/unattended-upgrades/*

system logs (in order to find out connection/disconnection times and possible 
other errors)
- /var/log/syslog*
- /var/log/auth.log*

System logs likely contain private information, especially syslog and
auth.log. All logs fairly explicit when it comes to dates and it should
be easy to narrow logs down to the appropriate time range and remove
whatever needs to be removed.

Thanks a lot. That would be tremendously helpful since, as you can see,
the actual error happens weeks before the report and it has been
difficult to collect useful logs.


Seth, I don't think needrestart spawns debconf (but launchpad/HTML doesn't 
display consecutive spaces as several ones). My understanding is as follows:

dpkg (1224019) sources/runs /etc/dpkg/dpkg.cfg.d/needrestart as PID 1224020
sh (1224020) spawns a subshell as PID 1224021
sh (1224021) spawns /sh /usr/lib/needrestart/dpkg-status as PID 1224022
dpkg-status (1224022) reads dpkg's output, probably until dpkg exits

dpkg (1224019) runs the grub postinst script, probably as PID 1224023 (not 
listed)
grub's postinst (1224023?) sources debconf's script which notices debconf is 
not running and therefore execs debconf which then spawns the grub postinst 
again as PID 1224024; AFAIU that's the intended behavior
grub's postinst (1224023) sits there waiting, possibly for results from debconf

Since the grub postinst never finishes, dpkg itself never finishes and
needrestart doesn't finish either.

Btw, I'm getting more motivated to get rid of the current postinst in
openssl because it's responsible for a large number of bug reports (both
because the behaviour is suboptimal and because it uses debconf and
gathers such bug reports [ I would also like this to be fixed debconf
side obviously ]).

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

Title:
  package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade:
  installed libssl3:amd64 package post-installation script subprocess
  returned error exit status 1

Status in needrestart package in Ubuntu:
  New
Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  encounter error when attempting to do sudo update, upgrade, and full-
  upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libssl3:amd64 3.0.2-0ubuntu1.8
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Mar  1 10:28:26 2023
  ErrorMessage: installed libssl3:amd64 package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-10-01 (150 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.8
  SourcePackage: openssl
  Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: 
installed libssl3:amd64 package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/needrestart/+bug/2008846/+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 1278223] Re: Mouse Flickering after adding 3rd Monitor

[Paul White]

This issue has sat with a status of 'Incomplete' for over three years
now without any comment and did not expire due to the presence of a 'Bug
watch'. Also the Ubuntu versions affected are all now out out of support
so I'm closing the report as 'Invalid' as it no longer refers to any
currently supported release of Ubuntu.

Please feel free to re-open this bug report if this is still an issue
when using a currently supported release of Ubuntu making sure that you
tell us in which release(s) you still experience this issue.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

** Changed in: xorg (Ubuntu)
   Status: Incomplete => 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/1278223

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
  If you are having an issue and want it addressed, it is most helpful to file 
a new report. If you were led here by DisplayLink's website, you were led here 
in error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.

  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 2022310] [NEW] package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Francisco Javier Ubeda Moret]

Public bug reported:

I don't know what is the isue. The sistem reported a bug and create a
report, but i don't see any effect but the message itself.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1
ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Fri Jun  2 08:12:08 2023
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2022-10-04 (240 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.9
SourcePackage: initramfs-tools
Title: package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I don't know what is the isue. The sistem reported a bug and create a
  report, but i don't see any effect but the message itself.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1
  ProcVersionSignature: Ubuntu 5.19.0-42.43~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Jun  2 08:12:08 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-10-04 (240 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.19.0-43-generic 5.19.0-43.44~22.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Launchpad Bug Tracker]

This bug was fixed in the package evolution-data-server - 3.48.2-1

---
evolution-data-server (3.48.2-1) unstable; urgency=medium

  [ Amin Bandali ]
  * New upstream release (LP: #2021528)
- Bug Fixes:
  + Camel: Set proper S/MIME signature verification status
(https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/474)
  + IMAP: Cannot remove labels added in Thunderbird
(https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/478)
  + WebDAV: Fails to discover iCloud address book
(https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/479)
  + Wrong S/MIME certificate selection for encrypted email
(https://gitlab.gnome.org/GNOME/evolution/-/issues/2345)

  [ Jeremy Bícha ]
  * Release to unstable

 -- Amin Bandali   Mon, 29 May 2023 14:53:31 -0400

** Changed in: evolution-data-server (Ubuntu)
   Status: Fix Committed => Fix Released

** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #474
   https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/474

** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #478
   https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/478

** Bug watch added: gitlab.gnome.org/GNOME/evolution-data-server/-/issues #479
   https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/479

** Bug watch added: gitlab.gnome.org/GNOME/evolution/-/issues #2345
   https://gitlab.gnome.org/GNOME/evolution/-/issues/2345

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

Title:
  Update evolution-data-server to 3.48.2

Status in evolution-data-server package in Ubuntu:
  Fix Released

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

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

  It is required to update the evolution app to 3.48.2 (LP: #)

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

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

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

  evolution-data-server is included in all the Ubuntu Desktop flavors
  except for Kubuntu, Lubuntu, and Xubuntu

  Other Info
  --
  There will be new evolution-data-server bugfix releases monthly until 
September.

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

[Robert]

Should be this change: Fixed default color settings for CMYK printers as
well (Issue #500)

-- 
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 2021484] Re: Editing a VPN ask to introduce credentials but if you cancel can be accessed anyway

[Cristobal Diaz Aircury]

Hello Seth. It can be edited, and even removed. More info that might be
useful:

I recently made some changes to limit the number of login attempts:

sudo nano /etc/pam.d/common-auth

auth[success=1 default=ignore]  pam_unix.so nullok_secure 
authrequiredpam_deny.so 
authrequired   pam_faillock.soonerr=fail deny=3 unlock_time=30 
authrequiredpam_permit.so 

Another change was to set Wayland as Windowing System.

Don't hesitate to ask me more info. Thanks for your time.

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

Title:
  Editing a VPN ask to introduce credentials but if you cancel can be
  accessed anyway

Status in ubuntu-settings package in Ubuntu:
  Incomplete

Bug description:
  I'm logged as a normal user without admin privileges. When I try to
  edit a VPN I'm asked to introduce the credentials of the admin,
  nevertheless if I click cancel I can still access to the VPN
  configuration.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-settings 20.04.6
  ProcVersionSignature: Ubuntu 5.15.0-72.79~20.04.1-generic 5.15.98
  Uname: Linux 5.15.0-72-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 29 11:16:38 2023
  InstallationDate: Installed on 2022-05-04 (389 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: ubuntu-settings
  UpgradeStatus: No upgrade log present (probably fresh install)

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