[Touch-packages] [Bug 2027631] Re: no signal to external monitor from HDMI port

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => mutter (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/2027631

Title:
  no signal to external monitor from HDMI port

Status in mutter package in Ubuntu:
  New

Bug description:
  On fresh installation of Ubuntu 22.04.2 LTS with and without latest updates 
there's no HDMI signal to external monitor. No display , no picture, no 
detection at all. 
  The hardware is functional under Windows the HDMI port is working. 
  What I've managed to research is some problems with Intel 12th gen CPU GPUs 
drivers where other user have similar problem. Some sources mention Wayland 
protocol as part of the problem but cannot clarify how  reliable that is. Tried 
changing display protocols on login but it didn't help.

  CPU i7-1255U , notebook: ASUS Expertbook B9400 CBA

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 00:53:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1f02]
  InstallationDate: Installed on 2023-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 8087:0033 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ASUS EXPERTBOOK B9400CBA_B9400CBA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=28808a14-059c-4b86-a687-ebd6d7ad1b12 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2022
  dmi.bios.release: 5.26
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: B9400CBA.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: B9400CBA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrB9400CBA.214:bd09/26/2022:br5.26:svnASUSTeKCOMPUTERINC.:pnASUSEXPERTBOOKB9400CBA_B9400CBA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnB9400CBA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS EXPERTBOOK
  dmi.product.name: ASUS EXPERTBOOK B9400CBA_B9400CBA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027631/+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 2027617] Re: Can't change build-in display refresh rate

[Daniel van Vugt]

Thanks for the bug report. Please run:

  sudo apt install drm-info
  drm_info > drminfo.txt

and attach the resulting text file here.

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

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

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

Title:
  Can't change build-in display refresh rate

Status in Ubuntu:
  Incomplete

Bug description:
  I guess it is related to the latest updates. Before I can change refresh rate.
  As for now, the refresh rate is fixed (59.88Hz) and I don't have any option 
to change it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 12:23:31 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:3802]
  InstallationDate: Installed on 2018-09-15 (1760 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80Y8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=56a0d470-0b27-4743-8549-8b7195c884a1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.release: 1.28
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB Glass
  dmi.ec.firmware.release: 0.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN28WW:bd08/23/2017:br1.28:efr0.29:svnLENOVO:pn80Y8:pvrLenovoYOGA920-13IKBGlass:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKBGlass:skuLENOVO_MT_80Y8_BU_idea_FM_YOGA920-13IKBGlass:
  dmi.product.family: YOGA 920-13IKB Glass
  dmi.product.name: 80Y8
  dmi.product.sku: LENOVO_MT_80Y8_BU_idea_FM_YOGA 920-13IKB Glass
  dmi.product.version: Lenovo YOGA 920-13IKB Glass
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2027617/+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 2022879] Re: No sound from Woofer speaker of Asus Zephyrus G14 2023

[cattin]

I have exactly the same issue with only the tweeters outputting sound. I
am also using the 2023 model of the G14 (the model with the RTX4090). In
contrast, I use Kubuntu 23.04 as the OS and also installed pipewire (not
pulse audio) in the hopes it does solve my problem.

The command given in comment 10 of the link above did, however, not
solve my problem. Did it help in your case?

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

Title:
  No sound from Woofer speaker of Asus Zephyrus G14 2023

Status in alsa-driver package in Ubuntu:
  New
Status in pipewire package in Ubuntu:
  New

Bug description:
  On Asus Zephyrus G14 2023, sound only comes out of the pair of tweeter
  speaker. The woofer speaker does not produce any sound at all on
  either on Analog Stereo, Analog Surround 4.0, or 2.1 configurations

  1)
  ┌─[surfer@M5-RGV]-[~]
  └──╼ $lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04
  )
  2)
  ┌─[surfer@M5-RGV]-[~]
  └──╼ $apt-cache policy pipewire
  pipewire:
Installed: 0.3.65-3
Candidate: 0.3.65-3
Version table:
   *** 0.3.65-3 500
  500 http://id.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  3) The Woofer/rear speaker should produce sound

  4) Sound only comes from the pair of tweeter speaker

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: pipewire 0.3.65-3
  Uname: Linux 6.3.5-060305-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Mon Jun  5 12:33:02 2023
  InstallationDate: Installed on 2023-05-31 (4 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pipewire
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2022879/+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 2027614] Re: Xorg Black Screen when upgrading packages (after CUDA installation)

[Daniel van Vugt]

Thanks for the bug report. Next time the screen goes black and after
rebooting, please run:

  journalctl -b-1 > prevboot.txt

and attach the resulting text file here.

** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)

** Changed in: nvidia-graphics-drivers-535 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Xorg Black Screen when upgrading packages (after CUDA installation)

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I am trying to setup CUDA on my system. Followed the instructions and
  everything seemed to work. Tried nvcc command and it works. After a
  reboot, tried to update packages with `apt update && apt full-
  upgrade`. The following is the output before I proceeded:

  The following NEW packages will be installed:
cpp-12 dctrl-tools dkms gcc-12 libasan8 libegl-mesa0:i386 libegl1:i386 
libgbm1:i386 libgcc-12-dev libgles2:i386 libopengl0:i386 libtsan2 
libwayland-client0:i386 libwayland-server0:i386 nvidia-dkms-535
  The following packages have been kept back:
alsa-ucm-conf gir1.2-adw-1 gjs libadwaita-1-0 libgjs0g libspeechd2 
python3-speechd speech-dispatcher speech-dispatcher-audio-plugins 
speech-dispatcher-espeak-ng ubuntu-advantage-tools
  The following packages will be upgraded:
libnvidia-cfg1-535 libnvidia-common-535 libnvidia-compute-535 
libnvidia-compute-535:i386 libnvidia-decode-535 libnvidia-decode-535:i386 
libnvidia-encode-535 libnvidia-encode-535:i386 libnvidia-extra-535
libnvidia-fbc1-535 libnvidia-fbc1-535:i386 libnvidia-gl-535 
libnvidia-gl-535:i386 libxnvctrl0 nvidia-compute-utils-535 nvidia-driver-535 
nvidia-kernel-common-535 nvidia-kernel-source-535 nvidia-utils-535
xserver-xorg-video-nvidia-535

  After a while, screen went black and had to do a hard reboot. I tried
  this two times on a fresh Ubuntu 22.04 installation and same thing
  happened. I am ready to provide any further information if needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.54.03  Tue Jun  6 
22:20:39 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 21:06:45 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d86]
   NVIDIA Corporation Device [10de:2782] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:88e5]
  InstallationDate: Installed on 2023-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: Micro-Star International Co., Ltd. MS-7D86
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=a9c91108-ed9d-4352-a779-fc46a70f4215 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Default string
  dmi.board.name: MEG Z790 ACE (MS-7D86)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.30:bd03/23/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D86:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ790ACE(MS-7D86):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D86
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: 

[Touch-packages] [Bug 1743291] Re: package libssl-dev:amd64 1.0.2g-1ubuntu4.10 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su

[Launchpad Bug Tracker]

[Expired for openssl (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package libssl-dev:amd64 1.0.2g-1ubuntu4.10 failed to install/upgrade:
  El paquete está en un estado grave de inconsistencia - debe
  reinstalarlo  antes de intentar su configuración.

Status in openssl package in Ubuntu:
  Expired

Bug description:
  1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl-dev:amd64 1.0.2g-1ubuntu4.10
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  AptOrdering:
   libssl1.0.0: Install
   libssl1.0.0: Configure
   libssl-dev: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Jan 14 16:58:10 2018
  DpkgHistoryLog:
   Start-Date: 2018-01-14  16:58:07
   Commandline: apt-get install --yes --force-yes -f
   Requested-By: lysanchez (1000)
   Upgrade: libssl1.0.0:amd64 (1.0.2g-1ubuntu4.9, 1.0.2g-1ubuntu4.10)
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-10-15 (91 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: openssl
  Title: package libssl-dev:amd64 1.0.2g-1ubuntu4.10 failed to install/upgrade: 
El paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes 
de intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743291/+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 1677502] Re: openssl issue in ARM linux

[Launchpad Bug Tracker]

[Expired for openssl (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  openssl issue in ARM linux

Status in openssl package in Ubuntu:
  Expired

Bug description:
  Hello, 
  I need to use tomcat7 (secure connection, https) on a raspeberry PI. When I 
try to connect using openSSL, I have this error (http works):

  1995663600:error:1006706B:elliptic curve 
routines:ec_GFp_simple_oct2point:point is not on curve:ecp_oct.c:417:
  1995663600:error:1408D132:SSL routines:ssl3_get_key_exchange:bad 
ecpoint:s3_clnt.c:1875:

   CERT INFO 

  No client certificate CA names sent
  ---
  SSL handshake has read 1316 bytes and written 7 bytes
  ---
  New, (NONE), Cipher is (NONE)
  Server public key is 2048 bit
  Secure Renegotiation IS supported
  Compression: NONE
  Expansion: NONE
  No ALPN negotiated
  SSL-Session:
  Protocol  : TLSv1.2
  Cipher: 
  Session-ID: 
58DCAFCE36E7037B17C1B489D7D556EDA35EDCD2169BD0E0270CD93AC92DEB5A
  Session-ID-ctx:
  Master-Key:
  Key-Arg   : None
  PSK identity: None
  PSK identity hint: None
  SRP username: None
  Start Time: 1490857908
  Timeout   : 300 (sec)
  Verify return code: 18 (self signed certificate)

  I'm using ubuntu xenial:

  rasp@rasp-desktop:~$ uname -a
  Linux rasp-desktop 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l 
armv7l armv7l GNU/Linux

  rasp@rasp-desktop:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial

  I did the same test both in the raspberry and in other platforms x86.
  I have the issue only in the raspeberry.

  Openssl version:
  rasp@rasp-desktop:~$ apt-cache policy openssl
  openssl:
Installato: 1.0.2g-1ubuntu4.6
Candidato:  1.0.2g-1ubuntu4.6
Tabella versione:
   *** 1.0.2g-1ubuntu4.6 500
  500 http://ports.ubuntu.com xenial-updates/main armhf Packages
  500 http://ports.ubuntu.com xenial-security/main armhf Packages
  100 /var/lib/dpkg/status
   1.0.2g-1ubuntu4 500
  500 http://ports.ubuntu.com xenial/main armhf Packages

  tomcat7 version:
  rasp@rasp-desktop:~$ apt-cache policy tomcat7
  tomcat7:
Installato: 7.0.68-1ubuntu0.1
Candidato:  7.0.68-1ubuntu0.1
Tabella versione:
   *** 7.0.68-1ubuntu0.1 500
  500 http://ports.ubuntu.com xenial-updates/universe armhf Packages
  500 http://ports.ubuntu.com xenial-security/universe armhf Packages
  100 /var/lib/dpkg/status
   7.0.68-1 500
  500 http://ports.ubuntu.com xenial/universe armhf Packages

  Java version:
  rasp@rasp-desktop:~$ java -version
  openjdk version "1.8.0_121"
  OpenJDK Runtime Environment (build 1.8.0_121-8u121-b13-0ubuntu1.16.04.2-b13)
  OpenJDK Zero VM (build 25.121-b13, interpreted mode)

  I have the problem only with the secure connection:
  rasp@rasp-desktop:/var/lib/tomcat7/logs$ curl 
http://localhost:8080/rest/services/hello
  Hello World!!!
  rasp@rasp-desktop:/var/lib/tomcat7/logs$ curl 
https://localhost:8443/rest/services/hello
  curl: (35) gnutls_handshake() failed: The request is invalid.

  rasp@rasp-desktop:/var/lib/tomcat7/logs$ wget 
https://localhost:8443/rest/services/hello
  --2017-03-30 09:40:07--  https://localhost:8443/rest/services/hello
  Resolving localhost (localhost)... 127.0.0.1
  Connecting to localhost (localhost)|127.0.0.1|:8443... connected.
  OpenSSL: error:1006706B:elliptic curve routines:ec_GFp_simple_oct2point:point 
is not on curve
  OpenSSL: error:1408D132:SSL routines:ssl3_get_key_exchange:bad ecpoint
  Unable to establish SSL connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1677502/+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 1806162] Re: package libssl1.1:i386 1.1.0g-2ubuntu4.1 failed to install/upgrade: installed libssl1.1:i386 package post-installation script subprocess was killed by signal (Broken

[Launchpad Bug Tracker]

[Expired for openssl (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  package libssl1.1:i386 1.1.0g-2ubuntu4.1 failed to install/upgrade:
  installed libssl1.1:i386 package post-installation script subprocess
  was killed by signal (Broken pipe)

Status in openssl package in Ubuntu:
  Expired

Bug description:
  ran sudo apt-get install update then sudo apt-get install upgrade and
  received this error.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libssl1.1:i386 1.1.0g-2ubuntu4.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 30 22:28:42 2018
  DuplicateSignature:
   package:libssl1.1:i386:1.1.0g-2ubuntu4.1
   Setting up libssl1.1:i386 (1.1.0g-2ubuntu4.1) ...
   dpkg: error processing package libssl1.1:i386 (--configure):
installed libssl1.1:i386 package post-installation script subprocess was 
killed by signal (Broken pipe)
  ErrorMessage: installed libssl1.1:i386 package post-installation script 
subprocess was killed by signal (Broken pipe)
  InstallationDate: Installed on 2018-11-23 (8 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: i386
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: openssl
  Title: package libssl1.1:i386 1.1.0g-2ubuntu4.1 failed to install/upgrade: 
installed libssl1.1:i386 package post-installation script subprocess was killed 
by signal (Broken pipe)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1806162/+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 2027641] Re: whole system has no sound

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  whole system has no sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Suddenly, the whole system has no sound.
  1\ Videos in web browser cannot start playing. the 'play' button does not 
work.
  2, Rhythmbox cannot play audio files. I click the 'play' button, but there is 
no sound and progress bar does not move forward.
  3, VLC cannot play audio file. The progress bar moves forward, but there is 
no sound.

  sound can recover with a system restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gle2108 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 10:25:42 2023
  InstallationDate: Installed on 2020-05-02 (1167 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to jammy on 2022-08-12 (334 days ago)
  dmi.bios.date: 08/12/2019
  dmi.bios.release: 1.9
  dmi.bios.vendor: HUAWEI
  dmi.bios.version: 1.09
  dmi.board.asset.tag: NULL
  dmi.board.name: HBL-WX9-PCB
  dmi.board.vendor: HUAWEI
  dmi.board.version: M1130
  dmi.chassis.asset.tag: NULL
  dmi.chassis.type: 10
  dmi.chassis.vendor: HUAWEI
  dmi.chassis.version: M1130
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnHUAWEI:bvr1.09:bd08/12/2019:br1.9:efr1.9:svnHUAWEI:pnHBL-WX9:pvrM1130:rvnHUAWEI:rnHBL-WX9-PCB:rvrM1130:cvnHUAWEI:ct10:cvrM1130:skuC233:
  dmi.product.family: MagicBook
  dmi.product.name: HBL-WX9
  dmi.product.sku: C233
  dmi.product.version: M1130
  dmi.sys.vendor: HUAWEI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2027641/+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 2026762] Re: gpu is not deceted

[Daniel van Vugt]

The attached files show your GPU is detected and the driver is working.
What exactly is the problem you are facing?

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

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

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

Title:
  gpu is not deceted

Status in Ubuntu:
  Incomplete

Bug description:
  it is not decting intel or nvidia driver

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
  Uname: Linux 5.15.0-76-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..65.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.54.03  Tue Jun  6 
22:20:39 UTC 2023
   GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04.1)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 10 22:47:51 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/535.54.03, 5.15.0-76-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GA104GL [RTX A4000] [10de:24b0] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GA104GL [RTX A4000] [1028:14ad]
  InstallationDate: Installed on 2023-07-05 (5 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  MachineType: Dell Inc. Precision 5820 Tower
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-76-generic 
root=UUID=b0bb8bdb-e3c0-4769-9192-4819dd4d31d6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2023
  dmi.bios.release: 2.30
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.30.0
  dmi.board.name: 06JWJY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.30.0:bd05/30/2023:br2.30:svnDellInc.:pnPrecision5820Tower:pvr:rvnDellInc.:rn06JWJY:rvrA01:cvnDellInc.:ct3:cvr:sku0738:
  dmi.product.family: Precision
  dmi.product.name: Precision 5820 Tower
  dmi.product.sku: 0738
  dmi.sys.vendor: Dell Inc.
  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.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2026762/+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 2027631] Re: no signal to external monitor from HDMI port

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (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/2027631

Title:
  no signal to external monitor from HDMI port

Status in xorg package in Ubuntu:
  New

Bug description:
  On fresh installation of Ubuntu 22.04.2 LTS with and without latest updates 
there's no HDMI signal to external monitor. No display , no picture, no 
detection at all. 
  The hardware is functional under Windows the HDMI port is working. 
  What I've managed to research is some problems with Intel 12th gen CPU GPUs 
drivers where other user have similar problem. Some sources mention Wayland 
protocol as part of the problem but cannot clarify how  reliable that is. Tried 
changing display protocols on login but it didn't help.

  CPU i7-1255U , notebook: ASUS Expertbook B9400 CBA

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul 13 00:53:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:46a8] (rev 0c) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1f02]
  InstallationDate: Installed on 2023-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 002: ID 8087:0033 Intel Corp. 
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ASUS EXPERTBOOK B9400CBA_B9400CBA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=28808a14-059c-4b86-a687-ebd6d7ad1b12 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2022
  dmi.bios.release: 5.26
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: B9400CBA.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: B9400CBA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrB9400CBA.214:bd09/26/2022:br5.26:svnASUSTeKCOMPUTERINC.:pnASUSEXPERTBOOKB9400CBA_B9400CBA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnB9400CBA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ASUS EXPERTBOOK
  dmi.product.name: ASUS EXPERTBOOK B9400CBA_B9400CBA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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.3
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2027631/+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 2027636] Re: [SRU] ucsi drivers missing in initramfs

[Loïc Minier]

** Attachment added: "debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+attachment/5685917/+files/debdiff

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

Title:
  [SRU] ucsi drivers missing in initramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Jammy:
  New

Bug description:
  [Impact]

  Some systems rely on a USB type-C UCSI connection; without the
  corresponding driver in the initramfs, USB storage might not be
  accessible. This is notably affecting NVIDIA Tegra systems such as
  Jetson AGX or the IGX and prevents completing USB boot for
  installation purposes.

  The initramfs-tools package has a list of relevant USB drivers to
  include for the default MODULES=most configuration, but didn't list
  the recently introduced ucsi one.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the ucsi driver. 
On jammy system, you can verify the current initrd doesn't contain 
typec_ucsi.ko by decompressing the initramfs and listing its files:
  $ zstdcat /boot/initrd.img-5.19.0-46-generic >/tmp/initrd
  $ lsinitramfs /tmp/initrd |grep typec_ucsi.ko
  cpio: premature end of archive

  
  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up typec_ucsi.ko:
  $ zstdcat /boot/initrd.img-5.19.0-46-generic >/tmp/initrd
  $ lsinitramfs /tmp/initrd |grep typec_ucsi.ko
  usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko
  cpio: premature end of archive

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing,
  typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew
  by 93403B from 122298948B to 122392351B, so by less than 0.08%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+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 2027636] [NEW] [SRU] ucsi drivers missing in initramfs

[Loïc Minier]

Public bug reported:

[Impact]

Some systems rely on a USB type-C UCSI connection; without the
corresponding driver in the initramfs, USB storage might not be
accessible. This is notably affecting NVIDIA Tegra systems such as
Jetson AGX or the IGX and prevents completing USB boot for installation
purposes.

The initramfs-tools package has a list of relevant USB drivers to
include for the default MODULES=most configuration, but didn't list the
recently introduced ucsi one.

[ Test Plan ]

The -generic kernel and probably all kernel flavors contain the ucsi driver. On 
jammy system, you can verify the current initrd doesn't contain typec_ucsi.ko 
by decompressing the initramfs and listing its files:
$ zstdcat /boot/initrd.img-5.19.0-46-generic >/tmp/initrd
$ lsinitramfs /tmp/initrd |grep typec_ucsi.ko
cpio: premature end of archive


After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up typec_ucsi.ko:
$ zstdcat /boot/initrd.img-5.19.0-46-generic >/tmp/initrd
$ lsinitramfs /tmp/initrd |grep typec_ucsi.ko
usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko
cpio: premature end of archive

[ Where problems could occur ]

This is making the initramfs slightly bigger. In my testing,
typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew by
93403B from 122298948B to 122392351B, so by less than 0.08%.

** Affects: initramfs-tools (Ubuntu)
 Importance: Medium
 Assignee: Loïc Minier (lool)
 Status: Fix Released

** Affects: initramfs-tools (Ubuntu Jammy)
 Importance: Medium
 Assignee: Loïc Minier (lool)
 Status: New

** Also affects: initramfs-tools (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: initramfs-tools (Ubuntu)
 Assignee: (unassigned) => Loïc Minier (lool)

** Changed in: initramfs-tools (Ubuntu Jammy)
 Assignee: (unassigned) => Loïc Minier (lool)

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Medium

** Changed in: initramfs-tools (Ubuntu Jammy)
   Importance: Undecided => Medium

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

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

Title:
  [SRU] ucsi drivers missing in initramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Jammy:
  New

Bug description:
  [Impact]

  Some systems rely on a USB type-C UCSI connection; without the
  corresponding driver in the initramfs, USB storage might not be
  accessible. This is notably affecting NVIDIA Tegra systems such as
  Jetson AGX or the IGX and prevents completing USB boot for
  installation purposes.

  The initramfs-tools package has a list of relevant USB drivers to
  include for the default MODULES=most configuration, but didn't list
  the recently introduced ucsi one.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the ucsi driver. 
On jammy system, you can verify the current initrd doesn't contain 
typec_ucsi.ko by decompressing the initramfs and listing its files:
  $ zstdcat /boot/initrd.img-5.19.0-46-generic >/tmp/initrd
  $ lsinitramfs /tmp/initrd |grep typec_ucsi.ko
  cpio: premature end of archive

  
  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up typec_ucsi.ko:
  $ zstdcat /boot/initrd.img-5.19.0-46-generic >/tmp/initrd
  $ lsinitramfs /tmp/initrd |grep typec_ucsi.ko
  usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko
  cpio: premature end of archive

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing,
  typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew
  by 93403B from 122298948B to 122392351B, so by less than 0.08%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+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 2027636] Re: [SRU] ucsi drivers missing in initramfs

[Loïc Minier]

I uploaded the fix to mantic early June:

initramfs-tools (0.142ubuntu4) mantic; urgency=medium

  * Include kernel/drivers/usb/typec/ucsi with MODULES=most along with other
USB-C storage drivers.

 -- Loïc Minier   Thu, 08 Jun 2023 17:49:02
+

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

Title:
  [SRU] ucsi drivers missing in initramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Jammy:
  New

Bug description:
  [Impact]

  Some systems rely on a USB type-C UCSI connection; without the
  corresponding driver in the initramfs, USB storage might not be
  accessible. This is notably affecting NVIDIA Tegra systems such as
  Jetson AGX or the IGX and prevents completing USB boot for
  installation purposes.

  The initramfs-tools package has a list of relevant USB drivers to
  include for the default MODULES=most configuration, but didn't list
  the recently introduced ucsi one.

  [ Test Plan ]

  The -generic kernel and probably all kernel flavors contain the ucsi driver. 
On jammy system, you can verify the current initrd doesn't contain 
typec_ucsi.ko by decompressing the initramfs and listing its files:
  $ zstdcat /boot/initrd.img-5.19.0-46-generic >/tmp/initrd
  $ lsinitramfs /tmp/initrd |grep typec_ucsi.ko
  cpio: premature end of archive

  
  After installing the updated initramfs-tools package, your current initramfs 
should be automatically rebuilt and pick up typec_ucsi.ko:
  $ zstdcat /boot/initrd.img-5.19.0-46-generic >/tmp/initrd
  $ lsinitramfs /tmp/initrd |grep typec_ucsi.ko
  usr/lib/modules/5.19.0-46-generic/kernel/drivers/usb/typec/ucsi/typec_ucsi.ko
  cpio: premature end of archive

  [ Where problems could occur ]

  This is making the initramfs slightly bigger. In my testing,
  typec_ucsi.ko was 99913B and /boot/initrd.img-5.19.0-46-generic grew
  by 93403B from 122298948B to 122392351B, so by less than 0.08%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027636/+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 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools

[Eilidh Martin]

There's a difference between "this package is required to allow people
to use our paid services" and "this package spams everyone who doesn't
pay for our paid services". This flies in the face of the whole ethos of
free software imo.

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

Title:
  ubuntu-minimal depends on ubuntu-advantage-tools

Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  This is counter to #1566183 There is no reason to enforce desktop
  users who manage machine on their own to install ubuntu-advantage-
  tools, especially when this is 'minimal' version.  This should include
  only essential packages to make the OS functional

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106
  Uname: Linux 5.4.0-73-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  4 18:54:56 2021
  InstallationDate: Installed on 2020-01-29 (491 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+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 2020913] Proposed package upload rejected

[Andreas Hasenack]

An upload of elfutils to jammy-proposed has been rejected from the
upload queue for the following reason: "Requested by sergiodj on IRC and
"in person" in a google meet.".

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

Title:
  /etc/profile.d/debuginfd.{sh,csh} are created with 600 permissions

Status in elfutils package in Ubuntu:
  Fix Released
Status in elfutils source package in Jammy:
  Incomplete

Bug description:
  [ Impact ]

  Users installing libdebuginfod-common (the package that ships the
  shell snippets responsible for configuring the DEBUGINFOD_URLS
  environment variable, which will ultimately be used by GDB to contact
  the Ubuntu debuginfod service) experience a problem caused by
  permissions being set too tightly for
  /etc/profile.d/debuginfod.{sh,csh}.  This results in DEBUGINFOD_URLS
  not being set for non-root users.

  [ Test Plan ]

  Inside a Jammy container:

  # apt install -y libdebuginfod-common
  # ls -lah /etc/profile.d/debuginfod*

  Verify that the permission of both files allow them to be world-
  readable.

  [ Where problems could occur ]

  Care has been taken to not modify existing file permissions
  unnecessarily by using "g+r,o+r" when invoking chmod, but it is still
  possible to conceive a scenario where upgrading the package would make
  the files world-readable when the user is actually expecting
  otherwise.  However, such "regression" would arguably not be something
  supported because if the intention is to prevent non-root users from
  making use of debuginfod, there are better ways to achieve it.

  [ Original Description ]

  In a fresh container, installing libdebuginfod-common gives a
  /etc/profile.d that looks like this:

  ```
  root@32f34f7e271e:/etc/profile.d# ls -lah
  total 24K
  drwxr-xr-x 1 root root 4.0K May 26 17:23 .
  drwxr-xr-x 1 root root 4.0K May 26 17:23 ..
  -rw-r--r-- 1 root root   96 Oct 15  2021 01-locale-fix.sh
  -rw--- 1 root root  677 May 26 17:23 debuginfod.csh
  -rw--- 1 root root  692 May 26 17:23 debuginfod.sh

  ```

  when I login as a nonprivledged user, DEBUGINFOD_URLS is not set
  because the permissions are incorrect on the profile files.

  ```
  # dpkg -l  | grep libdebug
  ii  libdebuginfod-common0.186-1build1   all   
   configuration to enable the Debian debug info server
  ```

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


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

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

[Launchpad Bug Tracker]

This bug was fixed in the package openssh - 1:9.3p1-1ubuntu1

---
openssh (1:9.3p1-1ubuntu1) mantic; urgency=medium

  * Merge with Debian unstable (LP: #2025664). Remaining changes:
- debian/rules: modify dh_installsystemd invocations for
  socket-activated sshd
- debian/openssh-server.postinst: handle migration of sshd_config options
  to systemd socket options on upgrade.
- debian/README.Debian: document systemd socket activation.
- debian/patches/socket-activation-documentation.patch: Document in
  sshd_config(5) that ListenAddress and Port no longer work.
- debian/openssh-server.templates: include debconf prompt explaining
  when migration cannot happen due to multiple ListenAddress values
- debian/.gitignore: drop file
- debian/openssh-server.postrm: remove systemd drop-ins for
  socket-activated sshd on purge
- debian/openssh-server.ucf-md5sum: update for Ubuntu delta
- debian/openssh-server.tmpfile,debian/systemd/ssh.service: Move
  /run/sshd creation out of the systemd unit to a tmpfile config so
  that sshd can be run manually if necessary without having to create
  this directory by hand.
- debian/patches/systemd-socket-activation.patch: Fix sshd
  re-execution behavior when socket activation is used
- debian/tests/systemd-socket-activation: Add autopkgtest for systemd socket
  activation functionality.
- d/p/test-set-UsePAM-no-on-some-tests.patch: set UsePAM=no for some tests
- Ensure smooth upgrade path from versions affected by LP: #2020474:
  + debian/openssh-server.postint: do not try to restart systemd units,
and instead indicate that a reboot is required
  + debian/tests/systemd-socket-activation: Reboot the testbed before 
starting the test
  + debian/rules: Do not stop ssh.socket on upgrade

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

  * Debconf translations:
- Romanian (thanks, Remus-Gabriel Chelu; closes: #1033178).
  * Properly fix date of 1:3.0.2p1-2 changelog entry (closes: #1034425).
  * New upstream release (https://www.openssh.com/releasenotes.html#9.3p1):
- [CVE-2023-28531] ssh-add(1): when adding smartcard keys to
  ssh-agent(1) with the per-hop destination constraints (ssh-add -h ...)
  added in OpenSSH 8.9, a logic error prevented the constraints from
  being communicated to the agent. This resulted in the keys being added
  without constraints. The common cases of non-smartcard keys and keys
  without destination constraints are unaffected. This problem was
  reported by Luci Stanescu (closes: #1033166).
- [SECURITY] ssh(1): Portable OpenSSH provides an implementation of the
  getrrsetbyname(3) function if the standard library does not provide
  it, for use by the VerifyHostKeyDNS feature. A specifically crafted
  DNS response could cause this function to perform an out-of-bounds
  read of adjacent stack data, but this condition does not appear to be
  exploitable beyond denial-of-service to the ssh(1) client.
- ssh-keygen(1), ssh-keyscan(1): accept -Ohashalg=sha1|sha256 when
  outputting SSHFP fingerprints to allow algorithm selection.
- sshd(8): add a `sshd -G` option that parses and prints the effective
  configuration without attempting to load private keys and perform
  other checks. This allows usage of the option before keys have been
  generated and for configuration evaluation and verification by
  unprivileged users.
- scp(1), sftp(1): fix progressmeter corruption on wide displays.
- ssh-add(1), ssh-keygen(1): use RSA/SHA256 when testing usability of
  private keys as some systems are starting to disable RSA/SHA1 in
  libcrypto.
- sftp-server(8): fix a memory leak.
- ssh(1), sshd(8), ssh-keyscan(1): remove vestigial protocol
  compatibility code and simplify what's left.
- Fix a number of low-impact Coverity static analysis findings.
- ssh_config(5), sshd_config(5): mention that some options are not
  first-match-wins.
- Rework logging for the regression tests. Regression tests will now
  capture separate logs for each ssh and sshd invocation in a test.
- ssh(1): make `ssh -Q CASignatureAlgorithms` work as the manpage says
  it should.
- ssh(1): ensure that there is a terminating newline when adding a new
  entry to known_hosts.
- sshd(8): harden Linux seccomp sandbox. Move to an allowlist of
  mmap(2), madvise(2) and futex(2) flags, removing some concerning
  kernel attack surface.
  * debian/README.Debian: Clarify that you need to restart ssh.socket after
overriding its ListenStream= option (LP: #2020560).
  * debian/openssh-server.postinst: Use "sshd -G" to parse the server
configuration file (closes: #959726).
  * Fix incorrect RRSET_FORCE_EDNS0 flags validation in SSHFP DNSSEC patch
(thanks, Ben Hutchings; closes: #909022).
  * Always use the internal mkdtemp 

[Touch-packages] [Bug 2025664] Re: Merge openssh 1:9.3p1-1 from Debian unstable

[Launchpad Bug Tracker]

This bug was fixed in the package openssh - 1:9.3p1-1ubuntu1

---
openssh (1:9.3p1-1ubuntu1) mantic; urgency=medium

  * Merge with Debian unstable (LP: #2025664). Remaining changes:
- debian/rules: modify dh_installsystemd invocations for
  socket-activated sshd
- debian/openssh-server.postinst: handle migration of sshd_config options
  to systemd socket options on upgrade.
- debian/README.Debian: document systemd socket activation.
- debian/patches/socket-activation-documentation.patch: Document in
  sshd_config(5) that ListenAddress and Port no longer work.
- debian/openssh-server.templates: include debconf prompt explaining
  when migration cannot happen due to multiple ListenAddress values
- debian/.gitignore: drop file
- debian/openssh-server.postrm: remove systemd drop-ins for
  socket-activated sshd on purge
- debian/openssh-server.ucf-md5sum: update for Ubuntu delta
- debian/openssh-server.tmpfile,debian/systemd/ssh.service: Move
  /run/sshd creation out of the systemd unit to a tmpfile config so
  that sshd can be run manually if necessary without having to create
  this directory by hand.
- debian/patches/systemd-socket-activation.patch: Fix sshd
  re-execution behavior when socket activation is used
- debian/tests/systemd-socket-activation: Add autopkgtest for systemd socket
  activation functionality.
- d/p/test-set-UsePAM-no-on-some-tests.patch: set UsePAM=no for some tests
- Ensure smooth upgrade path from versions affected by LP: #2020474:
  + debian/openssh-server.postint: do not try to restart systemd units,
and instead indicate that a reboot is required
  + debian/tests/systemd-socket-activation: Reboot the testbed before 
starting the test
  + debian/rules: Do not stop ssh.socket on upgrade

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

  * Debconf translations:
- Romanian (thanks, Remus-Gabriel Chelu; closes: #1033178).
  * Properly fix date of 1:3.0.2p1-2 changelog entry (closes: #1034425).
  * New upstream release (https://www.openssh.com/releasenotes.html#9.3p1):
- [CVE-2023-28531] ssh-add(1): when adding smartcard keys to
  ssh-agent(1) with the per-hop destination constraints (ssh-add -h ...)
  added in OpenSSH 8.9, a logic error prevented the constraints from
  being communicated to the agent. This resulted in the keys being added
  without constraints. The common cases of non-smartcard keys and keys
  without destination constraints are unaffected. This problem was
  reported by Luci Stanescu (closes: #1033166).
- [SECURITY] ssh(1): Portable OpenSSH provides an implementation of the
  getrrsetbyname(3) function if the standard library does not provide
  it, for use by the VerifyHostKeyDNS feature. A specifically crafted
  DNS response could cause this function to perform an out-of-bounds
  read of adjacent stack data, but this condition does not appear to be
  exploitable beyond denial-of-service to the ssh(1) client.
- ssh-keygen(1), ssh-keyscan(1): accept -Ohashalg=sha1|sha256 when
  outputting SSHFP fingerprints to allow algorithm selection.
- sshd(8): add a `sshd -G` option that parses and prints the effective
  configuration without attempting to load private keys and perform
  other checks. This allows usage of the option before keys have been
  generated and for configuration evaluation and verification by
  unprivileged users.
- scp(1), sftp(1): fix progressmeter corruption on wide displays.
- ssh-add(1), ssh-keygen(1): use RSA/SHA256 when testing usability of
  private keys as some systems are starting to disable RSA/SHA1 in
  libcrypto.
- sftp-server(8): fix a memory leak.
- ssh(1), sshd(8), ssh-keyscan(1): remove vestigial protocol
  compatibility code and simplify what's left.
- Fix a number of low-impact Coverity static analysis findings.
- ssh_config(5), sshd_config(5): mention that some options are not
  first-match-wins.
- Rework logging for the regression tests. Regression tests will now
  capture separate logs for each ssh and sshd invocation in a test.
- ssh(1): make `ssh -Q CASignatureAlgorithms` work as the manpage says
  it should.
- ssh(1): ensure that there is a terminating newline when adding a new
  entry to known_hosts.
- sshd(8): harden Linux seccomp sandbox. Move to an allowlist of
  mmap(2), madvise(2) and futex(2) flags, removing some concerning
  kernel attack surface.
  * debian/README.Debian: Clarify that you need to restart ssh.socket after
overriding its ListenStream= option (LP: #2020560).
  * debian/openssh-server.postinst: Use "sshd -G" to parse the server
configuration file (closes: #959726).
  * Fix incorrect RRSET_FORCE_EDNS0 flags validation in SSHFP DNSSEC patch
(thanks, Ben Hutchings; closes: #909022).
  * Always use the internal mkdtemp 

[Touch-packages] [Bug 2027617] Re: Can't change build-in display refresh rate

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (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/2027617

Title:
  Can't change build-in display refresh rate

Status in xorg package in Ubuntu:
  New

Bug description:
  I guess it is related to the latest updates. Before I can change refresh rate.
  As for now, the refresh rate is fixed (59.88Hz) and I don't have any option 
to change it.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 12:23:31 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:3802]
  InstallationDate: Installed on 2018-09-15 (1760 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80Y8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic 
root=UUID=56a0d470-0b27-4743-8549-8b7195c884a1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.release: 1.28
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5NCN28WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40688 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 920-13IKB Glass
  dmi.ec.firmware.release: 0.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr5NCN28WW:bd08/23/2017:br1.28:efr0.29:svnLENOVO:pn80Y8:pvrLenovoYOGA920-13IKBGlass:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKBGlass:skuLENOVO_MT_80Y8_BU_idea_FM_YOGA920-13IKBGlass:
  dmi.product.family: YOGA 920-13IKB Glass
  dmi.product.name: 80Y8
  dmi.product.sku: LENOVO_MT_80Y8_BU_idea_FM_YOGA 920-13IKB Glass
  dmi.product.version: Lenovo YOGA 920-13IKB Glass
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
  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/2027617/+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 2027581] Re: useradd grants root privileges to admin user

[Amin Bandali]

** Summary changed:

- useradd will grand root privileges  for admin user
+ useradd grants root privileges to admin user

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

Title:
  useradd grants root privileges to admin user

Status in sudo package in Ubuntu:
  New

Bug description:
  Hi,

  As part of the Ubuntu Core 20, if a developer creates a user named
  either admin or Admin, it will have  root privileges by default. I
  think that this is a security issue but it requires input from the
  security engineers/specialists.

  Basically, if you look at the sudoers file under `/etc/sudoers`, you
  will realize the following line;

  ```
  # Members of the admin group may gain root privileges
  %admin ALL=(ALL) ALL
  ```

  And if someone creates a user by using admin as name, the system
  provide root privilege.

  ```
  sudo useradd -s /bin/bash -u 8003 -d /home/Admin --extrausers Admin
  iotuc@ubuntu:~$ su Admin
  Password:
  Admin@ubuntu:/home/iotuc$ cat /etc/sudoers
  cat: /etc/sudoers: Permission denied
  Admin@ubuntu:/home/iotuc$ sudo cat /etc/sudoers
  [sudo] password for Admin:
  #
  # This file MUST be edited with the 'visudo' command as root.
  #
  # Please consider adding local content in /etc/sudoers.d/ instead of
  # directly modifying this file.
  #
  # See the man page for details on how to write a sudoers file.
  #
  Defaultsenv_reset
  Defaultsmail_badpass
  Defaults
secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin"
  # Host alias specification
  # User alias specification
  # Cmnd alias specification
  # User privilege specification
  rootALL=(ALL:ALL) ALL
  # Members of the admin group may gain root privileges
  %admin ALL=(ALL) ALL
  # Allow members of group sudo to execute any command
  %sudoALL=(ALL:ALL) ALL
  # See sudoers(5) for more information on "#include" directives:
  #includedir /etc/sudoers.d
  Admin@ubuntu:/home/iotuc$
  ```

  Similarly, if I create a username called aydogar, it does not have
  root privilege and this is expected.

  ```
  sudo useradd -s /bin/bash -u 8004 -d /home/aydogar --extrausers aydogar
  iotuc@ubuntu:~$ su aydogar
  Password:
  aydogar@ubuntu:/home/iotuc$ cat /etc/sudoers
  cat: /etc/sudoers: Permission denied
  aydogar@ubuntu:/home/iotuc$ sudo cat /etc/sudoers
  [sudo] password for aydogar:
  aydogar is not in the sudoers file.  This incident will be reported.
  aydogar@ubuntu:/home/iotuc$
  ```

  I think, this is a bug but would love here other ideas and inputs.

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

[Till Kamppeter]

Thank you very much. Marking the SRU for Jammy as verified ...

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

-- 
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:
  Fix Released
Status in okular package in Ubuntu:
  Confirmed
Status in cups source package in Jammy:
  Fix Committed

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.

  [ Impact ]

  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).

  Only an ugly command-line-based workaround, running the command

  lpadmin -p PRINTER -o print-color-mode-default=color

  makes the printer print in color.

  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers
  are affected.

  [ Test Plan ]

  Remove the workaround if you had applied it:

  lpadmin -p PRINTER -R print-color-mode-default

  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do

  lp -d PRINTER -o ColorModel=CMYK FILE.pdf

  Without the SRU applied you will get a grayscale/monochrome printout,
  with it applied, you will get a colored printout.

  To test without a printer:

  Stop CUPS:

  sudo systemctl stop cups

  Edit /etc/cups/cups-files.conf to have a line

  FiileDevice Yes

  and start CUPS again:

  sudo systemctl start cups

  Then create a queue using the attached sample PPD file:

  lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
  PDF_Printer-PDF.ppd

  Print a file to this queue as described above. When the job is done
  ("lpstat" does not show it any more), open /tmp/printout with a text
  editor. Check whether it contains a line

  @PJL SET RENDERMODE=COLOR

  near its beginning, and NOT a line

  @PJL SET RENDERMODE=GRAYSCALE

  [ Where problems could occur ]

  The patches are simple and they are also for some time in newer CUPS
  versions (2.4.2 and newer) which are included in several distributions
  (Ubuntu 22.10, 23.04, and others) and did not cause any complaints
  about color printing. So the regression potential is very low.

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 2026637] Re: [mantic] many useful apps are marked for auto removal

[Julian Andres Klode]

Generally the way to do this in Debian at least would be something like

1. move the removed dependencies/recommends to a ubuntu-desktop-legacy 
metapackage/seed
2. recommend that so it is installed
3. one cycle later, drop the recommends (or move it to suggests to keep it 
installed on upgrades*)

(*) In Ubuntu, ubuntu-release-upgrader removes Suggests

Adding the recommends for a month to transition devel users using apt,
and then removing it again and make u-r-u install it could make sense.

On the other hand we also kind of strive to have upgraded users have the
same experience (which is why we removed suggested-only packages in the
first place), so weigh the benefits.

One thing to note is APT's metapackage handling:

1. apt remove metapackage keeps dependencies automatically installed
2. apt install foo where foo conflicts with metapackage causes metapackage to 
be removed and the manual bit to transition to the dependencies.

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

Title:
  [mantic] many useful apps are marked for auto removal

Status in ubuntu-meta package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  Today update want remove a lot of apps.
  This happens on two systems installed from ISO dated 2023-06-07 and 2023-05-21
  corrado@corrado-n03-mm-0607:~$ sudo apt update && sudo apt upgrade
  [sudo] password for corrado: 
  Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
  Hit:3 http://archive.ubuntu.com/ubuntu mantic-backports InRelease
  Hit:4 http://archive.ubuntu.com/ubuntu mantic-security InRelease
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  All packages are up to date.
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
aisleriot baobab branding-ubuntu cheese cheese-common file-roller
gir1.2-rb-3.0 gnome-mahjongg gnome-mines gnome-sudoku gnome-video-effects
gstreamer1.0-clutter-3.0 guile-3.0-libs libavahi-ui-gtk3-0 libcairomm-1.16-1
libcdr-0.1-1 libchamplain-0.12-0 libchamplain-gtk-0.12-0 libcheese-gtk25
libcheese8 libclutter-gst-3.0-0 libdmapsharing-4.0-3 libevent-2.1-7
libfreehand-0.1-1 libfreerdp-client2-2 libglibmm-2.68-1
libgnome-games-support-1-3 libgnome-games-support-common libgpod-common
libgpod4 libgtkmm-4.0-0 libgupnp-igd-1.0-4 libixml10 liblc3-0 libminiupnpc17
libmspub-0.1-1 libmujs2 libnatpmp1 libpagemaker-0.0-0 libpangomm-2.48-1
libqqwing2v5 libreoffice-calc libreoffice-draw libreoffice-gnome
libreoffice-gtk3 libreoffice-impress librhythmbox-core10 libsdl-image1.2
libsdl1.2debian libsgutils2-1.46-2 libsigc++-3.0-0 libupnp13 libvisio-0.1-1
lp-solve media-player-info python3-mako python3-renderpm
python3-reportlab-accel remmina remmina-common remmina-plugin-rdp
remmina-plugin-secret remmina-plugin-vnc rhythmbox rhythmbox-data
rhythmbox-plugin-alternative-toolbar rhythmbox-plugins shotwell
shotwell-common simple-scan transmission-common transmission-gtk
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  corrado@corrado-n03-mm-0607:

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-desktop 1.505
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  9 08:53:45 2023
  InstallationDate: Installed on 2023-06-07 (31 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230607)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2026637/+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 2027614] Re: Xorg Black Screen when upgrading packages (after CUDA installation)

[Baris Basturk]

Now I get the following error if I run `apt full-upgrade`:

The following packages have unmet dependencies:
 nvidia-dkms-535 : Depends: nvidia-kernel-common-535 (= 535.54.03-0ubuntu1) but 
535.54.03-0ubuntu0.22.04.1 is installed
 nvidia-driver-535 : Depends: libnvidia-extra-535 (= 535.54.03-0ubuntu1) but 
535.54.03-0ubuntu0.22.04.1 is installed
 Depends: nvidia-compute-utils-535 (= 535.54.03-0ubuntu1) 
but 535.54.03-0ubuntu0.22.04.1 is installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

I feel like I never should've been prompted to install any updates in
the first place after CUDA install.

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

Title:
  Xorg Black Screen when upgrading packages (after CUDA installation)

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I am trying to setup CUDA on my system. Followed the instructions and
  everything seemed to work. Tried nvcc command and it works. After a
  reboot, tried to update packages with `apt update && apt full-
  upgrade`. The following is the output before I proceeded:

  The following NEW packages will be installed:
cpp-12 dctrl-tools dkms gcc-12 libasan8 libegl-mesa0:i386 libegl1:i386 
libgbm1:i386 libgcc-12-dev libgles2:i386 libopengl0:i386 libtsan2 
libwayland-client0:i386 libwayland-server0:i386 nvidia-dkms-535
  The following packages have been kept back:
alsa-ucm-conf gir1.2-adw-1 gjs libadwaita-1-0 libgjs0g libspeechd2 
python3-speechd speech-dispatcher speech-dispatcher-audio-plugins 
speech-dispatcher-espeak-ng ubuntu-advantage-tools
  The following packages will be upgraded:
libnvidia-cfg1-535 libnvidia-common-535 libnvidia-compute-535 
libnvidia-compute-535:i386 libnvidia-decode-535 libnvidia-decode-535:i386 
libnvidia-encode-535 libnvidia-encode-535:i386 libnvidia-extra-535
libnvidia-fbc1-535 libnvidia-fbc1-535:i386 libnvidia-gl-535 
libnvidia-gl-535:i386 libxnvctrl0 nvidia-compute-utils-535 nvidia-driver-535 
nvidia-kernel-common-535 nvidia-kernel-source-535 nvidia-utils-535
xserver-xorg-video-nvidia-535

  After a while, screen went black and had to do a hard reboot. I tried
  this two times on a fresh Ubuntu 22.04 installation and same thing
  happened. I am ready to provide any further information if needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.54.03  Tue Jun  6 
22:20:39 UTC 2023
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 21:06:45 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d86]
   NVIDIA Corporation Device [10de:2782] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:88e5]
  InstallationDate: Installed on 2023-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  MachineType: Micro-Star International Co., Ltd. MS-7D86
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=a9c91108-ed9d-4352-a779-fc46a70f4215 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.30
  dmi.board.asset.tag: Default string
  dmi.board.name: MEG Z790 ACE (MS-7D86)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 

[Touch-packages] [Bug 2027614] [NEW] Xorg Black Screen when upgrading packages (after CUDA installation)

[Baris Basturk]

Public bug reported:

Hi,

I am trying to setup CUDA on my system. Followed the instructions and
everything seemed to work. Tried nvcc command and it works. After a
reboot, tried to update packages with `apt update && apt full-upgrade`.
The following is the output before I proceeded:

The following NEW packages will be installed:
  cpp-12 dctrl-tools dkms gcc-12 libasan8 libegl-mesa0:i386 libegl1:i386 
libgbm1:i386 libgcc-12-dev libgles2:i386 libopengl0:i386 libtsan2 
libwayland-client0:i386 libwayland-server0:i386 nvidia-dkms-535
The following packages have been kept back:
  alsa-ucm-conf gir1.2-adw-1 gjs libadwaita-1-0 libgjs0g libspeechd2 
python3-speechd speech-dispatcher speech-dispatcher-audio-plugins 
speech-dispatcher-espeak-ng ubuntu-advantage-tools
The following packages will be upgraded:
  libnvidia-cfg1-535 libnvidia-common-535 libnvidia-compute-535 
libnvidia-compute-535:i386 libnvidia-decode-535 libnvidia-decode-535:i386 
libnvidia-encode-535 libnvidia-encode-535:i386 libnvidia-extra-535
  libnvidia-fbc1-535 libnvidia-fbc1-535:i386 libnvidia-gl-535 
libnvidia-gl-535:i386 libxnvctrl0 nvidia-compute-utils-535 nvidia-driver-535 
nvidia-kernel-common-535 nvidia-kernel-source-535 nvidia-utils-535
  xserver-xorg-video-nvidia-535

After a while, screen went black and had to do a hard reboot. I tried
this two times on a fresh Ubuntu 22.04 installation and same thing
happened. I am ready to provide any further information if needed.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-46-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.54.03  Tue Jun  6 22:20:39 
UTC 2023
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 12 21:06:45 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: This is the first time
GraphicsCard:
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:7d86]
 NVIDIA Corporation Device [10de:2782] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:88e5]
InstallationDate: Installed on 2023-07-12 (0 days ago)
InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
MachineType: Micro-Star International Co., Ltd. MS-7D86
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-46-generic 
root=UUID=a9c91108-ed9d-4352-a779-fc46a70f4215 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/23/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: 1.30
dmi.board.asset.tag: Default string
dmi.board.name: MEG Z790 ACE (MS-7D86)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.30:bd03/23/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D86:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMEGZ790ACE(MS-7D86):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7D86
dmi.product.sku: Default string
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
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.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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 freeze jammy ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.

[Touch-packages] [Bug 2027612] Re: bluetooth not recognicing device

[omarly666]

19:21:34 packagekitd: uid 1000 obtained auth for 
org.freedesktop.packagekit.system-sources-refresh
19:21:34 packagekitd: uid 1000 obtained auth for 
org.freedesktop.packagekit.system-sources-refresh
19:21:34 packagekitd: uid 1000 is trying to obtain 
org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
19:21:12 packagekitd: uid 1000 obtained auth for 
org.freedesktop.packagekit.system-sources-refresh
19:21:12 packagekitd: uid 1000 is trying to obtain 
org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
19:21:07 packagekitd: uid 1000 obtained auth for 
org.freedesktop.packagekit.system-sources-refresh
19:21:07 packagekitd: uid 1000 is trying to obtain 
org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
19:21:07 packagekitd: uid 1000 obtained auth for 
org.freedesktop.packagekit.system-sources-refresh
19:21:07 packagekitd: uid 1000 is trying to obtain 
org.freedesktop.packagekit.system-sources-refresh auth (only_trusted:0)
19:20:44 gnome-shell: Obtained a high priority EGL context
19:20:38 kernel: usbcore: registered new interface driver btusb
19:20:38 kernel: btrtl: module verification failed: signature and/or required 
key missing - tainting kernel

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

Title:
  bluetooth not recognicing device

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 
  I just updated and did a reboot.
  bt shows other devices, but I tried removing the one not connecting and it is 
gone

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  omarly 5248 F wireplumber
   /dev/snd/seq:omarly 5244 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 19:34:33 2023
  InstallationDate: Installed on 2022-08-21 (325 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to lunar on 2023-04-25 (78 days ago)
  dmi.bios.date: 09/10/2019
  dmi.bios.release: 2.76
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ETB6WW (2.76 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356AU8
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETB6WW(2.76):bd09/10/2019:br2.76:efr1.16:svnLENOVO:pn2356AU8:pvrThinkPadT430s:rvnLENOVO:rn2356AU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2356:
  dmi.product.family: ThinkPad T430s
  dmi.product.name: 2356AU8
  dmi.product.sku: LENOVO_MT_2356
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2027612/+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 2027612] [NEW] bluetooth not recognicing device

[omarly666]

Public bug reported:

ubuntu 23.04 
I just updated and did a reboot.
bt shows other devices, but I tried removing the one not connecting and it is 
gone

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
Uname: Linux 6.2.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  omarly 5248 F wireplumber
 /dev/snd/seq:omarly 5244 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 12 19:34:33 2023
InstallationDate: Installed on 2022-08-21 (325 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: Upgraded to lunar on 2023-04-25 (78 days ago)
dmi.bios.date: 09/10/2019
dmi.bios.release: 2.76
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ETB6WW (2.76 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2356AU8
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.ec.firmware.release: 1.16
dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETB6WW(2.76):bd09/10/2019:br2.76:efr1.16:svnLENOVO:pn2356AU8:pvrThinkPadT430s:rvnLENOVO:rn2356AU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2356:
dmi.product.family: ThinkPad T430s
dmi.product.name: 2356AU8
dmi.product.sku: LENOVO_MT_2356
dmi.product.version: ThinkPad T430s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug lunar

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

Title:
  bluetooth not recognicing device

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  ubuntu 23.04 
  I just updated and did a reboot.
  bt shows other devices, but I tried removing the one not connecting and it is 
gone

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13
  Uname: Linux 6.2.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  omarly 5248 F wireplumber
   /dev/snd/seq:omarly 5244 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 19:34:33 2023
  InstallationDate: Installed on 2022-08-21 (325 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220405)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: Upgraded to lunar on 2023-04-25 (78 days ago)
  dmi.bios.date: 09/10/2019
  dmi.bios.release: 2.76
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G7ETB6WW (2.76 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2356AU8
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnLENOVO:bvrG7ETB6WW(2.76):bd09/10/2019:br2.76:efr1.16:svnLENOVO:pn2356AU8:pvrThinkPadT430s:rvnLENOVO:rn2356AU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:skuLENOVO_MT_2356:
  dmi.product.family: ThinkPad T430s
  dmi.product.name: 2356AU8
  dmi.product.sku: LENOVO_MT_2356
  dmi.product.version: ThinkPad T430s
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2027612/+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 2026762] Re: gpu is not deceted

[sai]

can u tell me what to do clearly

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

Title:
  gpu is not deceted

Status in xorg package in Ubuntu:
  New

Bug description:
  it is not decting intel or nvidia driver

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
  Uname: Linux 5.15.0-76-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..65.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.54.03  Tue Jun  6 
22:20:39 UTC 2023
   GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04.1)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 10 22:47:51 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/535.54.03, 5.15.0-76-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GA104GL [RTX A4000] [10de:24b0] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GA104GL [RTX A4000] [1028:14ad]
  InstallationDate: Installed on 2023-07-05 (5 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  MachineType: Dell Inc. Precision 5820 Tower
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-76-generic 
root=UUID=b0bb8bdb-e3c0-4769-9192-4819dd4d31d6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2023
  dmi.bios.release: 2.30
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.30.0
  dmi.board.name: 06JWJY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.30.0:bd05/30/2023:br2.30:svnDellInc.:pnPrecision5820Tower:pvr:rvnDellInc.:rn06JWJY:rvrA01:cvnDellInc.:ct3:cvr:sku0738:
  dmi.product.family: Precision
  dmi.product.name: Precision 5820 Tower
  dmi.product.sku: 0738
  dmi.sys.vendor: Dell Inc.
  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.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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

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

[Nicola Soranzo]

@vorlon I've installed the 2.4.1op1-1ubuntu4.5 packages from -proposed
and, after correcting the printer configuration with `sudo lpadmin -p
PRINTER -o print-color-mode-default=color` it seems to work well, i.e.
it doesn't revert to monochrome after printing any more. Thanks!

-- 
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:
  Fix Released
Status in okular package in Ubuntu:
  Confirmed
Status in cups source package in Jammy:
  Fix Committed

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.

  [ Impact ]

  If the PPD file for a printer has a ColorModel option and the only
  choice in it for printing in color is not named RGB but CMYK instead,
  the printer cannot be made printing in color with intuitive methods,
  usually selcting the color choice in the print dialog (which makes
  ColorModel=CMYK be sent along with the job).

  Only an ugly command-line-based workaround, running the command

  lpadmin -p PRINTER -o print-color-mode-default=color

  makes the printer print in color.

  An example for printers with such PPDs are printers from RICOH and OEM
  (Lanier, InfoTec, Savin, ..), so many high-end color laser printers
  are affected.

  [ Test Plan ]

  Remove the workaround if you had applied it:

  lpadmin -p PRINTER -R print-color-mode-default

  If you have an affected printer, print a PDF file (or use the print
  functionality in an application) with colored content and choose the
  setting for color printing in the print dialog. When printing via
  command line do

  lp -d PRINTER -o ColorModel=CMYK FILE.pdf

  Without the SRU applied you will get a grayscale/monochrome printout,
  with it applied, you will get a colored printout.

  To test without a printer:

  Stop CUPS:

  sudo systemctl stop cups

  Edit /etc/cups/cups-files.conf to have a line

  FiileDevice Yes

  and start CUPS again:

  sudo systemctl start cups

  Then create a queue using the attached sample PPD file:

  lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-
  PDF_Printer-PDF.ppd

  Print a file to this queue as described above. When the job is done
  ("lpstat" does not show it any more), open /tmp/printout with a text
  editor. Check whether it contains a line

  @PJL SET RENDERMODE=COLOR

  near its beginning, and NOT a line

  @PJL SET RENDERMODE=GRAYSCALE

  [ Where problems could occur ]

  The patches are simple and they are also for some time in newer CUPS
  versions (2.4.2 and newer) which are included in several distributions
  (Ubuntu 22.10, 23.04, and others) and did not cause any complaints
  about color printing. So the regression potential is very low.

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 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  autopkgtest net is failing on 6.2 kernels with 'System is deadlocked
  on memory'

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools source package in Jammy:
  New
Status in initramfs-tools source package in Lunar:
  New

Bug description:
  [Impact]
  In debian/tests/run-image we instantiate an image with 512Mb of ram, but 
recent jammy/lunar 6.2 kernels need more than that.

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

  'net' test fails with a kernel panic due to out-of-memory.

  [Fix]

  Increase the size to 1Gb.

  [Test Plan]
  1. Download a lunar image:
  $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
  2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
  $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img

  [Where problems could occur]
  The usage of a larger image for the tests could fail if the the test system 
is low on ram size.

  Notes:
  It seems Mantic already uses 1G, so nothing has to be changed there. I also 
tested it locally and I confirm it works as expected there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 2026762] Re: gpu is not deceted

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (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/2026762

Title:
  gpu is not deceted

Status in xorg package in Ubuntu:
  New

Bug description:
  it is not decting intel or nvidia driver

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99
  Uname: Linux 5.15.0-76-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..65.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.54.03  Tue Jun  6 
22:20:39 UTC 2023
   GCC version:  gcc version 11.3.0 (Ubuntu 11.3.0-1ubuntu1~22.04.1)
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 10 22:47:51 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/535.54.03, 5.15.0-76-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GA104GL [RTX A4000] [10de:24b0] (rev a1) (prog-if 00 [VGA 
controller])
 Subsystem: Dell GA104GL [RTX A4000] [1028:14ad]
  InstallationDate: Installed on 2023-07-05 (5 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  MachineType: Dell Inc. Precision 5820 Tower
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-76-generic 
root=UUID=b0bb8bdb-e3c0-4769-9192-4819dd4d31d6 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/30/2023
  dmi.bios.release: 2.30
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.30.0
  dmi.board.name: 06JWJY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.30.0:bd05/30/2023:br2.30:svnDellInc.:pnPrecision5820Tower:pvr:rvnDellInc.:rn06JWJY:rvrA01:cvnDellInc.:ct3:cvr:sku0738:
  dmi.product.family: Precision
  dmi.product.name: Precision 5820 Tower
  dmi.product.sku: 0738
  dmi.sys.vendor: Dell Inc.
  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.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2026762/+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 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

[Benjamin Drung]

Thanks. You can find the code here: https://code.launchpad.net/~ubuntu-
core-dev/ubuntu/+source/initramfs-tools/+git/initramfs-tools

This is the porting commit: https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/initramfs-
tools/commit/?id=acf884d60729460c9afa32e2e41827d1d520b8a4

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

Title:
  autopkgtest net is failing on 6.2 kernels with 'System is deadlocked
  on memory'

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools source package in Jammy:
  New
Status in initramfs-tools source package in Lunar:
  New

Bug description:
  [Impact]
  In debian/tests/run-image we instantiate an image with 512Mb of ram, but 
recent jammy/lunar 6.2 kernels need more than that.

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

  'net' test fails with a kernel panic due to out-of-memory.

  [Fix]

  Increase the size to 1Gb.

  [Test Plan]
  1. Download a lunar image:
  $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
  2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
  $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img

  [Where problems could occur]
  The usage of a larger image for the tests could fail if the the test system 
is low on ram size.

  Notes:
  It seems Mantic already uses 1G, so nothing has to be changed there. I also 
tested it locally and I confirm it works as expected there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 2027576] Re: [Precision 5480, Intel Raptorlake-P HDMI, Digital Out, HDMI] Pulseaudio fails to detect card

[Ubuntu Foundations Team Bug Bot]

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

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

Title:
  [Precision 5480, Intel Raptorlake-P HDMI, Digital Out, HDMI]
  Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Dummy-output is the only available option. The laptop's speakers don't
  work, but I can hear audio if I use headphones.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', 
'/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 12 14:31:58 2023
  InstallationDate: Installed on 2023-07-12 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Digital Out, HDMI
  Title: [Precision 5480, Intel Raptorlake-P HDMI, Digital Out, HDMI] 
Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.3
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.1
  dmi.board.name: 03JVP1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: WKS057590
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.1:bd06/13/2023:br1.3:efr1.8:svnDellInc.:pnPrecision5480:pvr:rvnDellInc.:rn03JVP1:rvrA00:cvnDellInc.:ct10:cvr:sku0C40:
  dmi.product.family: Precision
  dmi.product.name: Precision 5480
  dmi.product.sku: 0C40
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2027576/+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 1926752] Re: [23.10 FEAT] libgmp SIMD optimizations

[Frank Heimes]

Many thx for your sponsorship, Graham!

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

Title:
  [23.10 FEAT] libgmp SIMD optimizations

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in gmp package in Ubuntu:
  Fix Committed

Bug description:
  Optimize the GNU MP Bignum Library using vector instructions.

  - Requirement for Full Homomorphic Encryption, libgmp is used as a backend 
for NTL
  - libgmp performance is critical also for GNU Cobol on Z.
  Here a customer requested using packed decimal instructions in libgmp which 
does not appear to fit for libgmp - however SIMD would help on distros with ALS 
z13

  https://gmplib.org/#STATUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1926752/+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 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

[Roxana Nicolescu]

Hi Benjamin,
Thanks for the fast feedback.
Yeah, I thought about it when I saw mantic had changed, but I saw it after I 
created the debdiffs and I was too lazy to change the approach.
I can look into that tomorrow morning, no problem.

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

Title:
  autopkgtest net is failing on 6.2 kernels with 'System is deadlocked
  on memory'

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools source package in Jammy:
  New
Status in initramfs-tools source package in Lunar:
  New

Bug description:
  [Impact]
  In debian/tests/run-image we instantiate an image with 512Mb of ram, but 
recent jammy/lunar 6.2 kernels need more than that.

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

  'net' test fails with a kernel panic due to out-of-memory.

  [Fix]

  Increase the size to 1Gb.

  [Test Plan]
  1. Download a lunar image:
  $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
  2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
  $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img

  [Where problems could occur]
  The usage of a larger image for the tests could fail if the the test system 
is low on ram size.

  Notes:
  It seems Mantic already uses 1G, so nothing has to be changed there. I also 
tested it locally and I confirm it works as expected there.

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

Rechecked autopkgtest results for distro-info, dput, gpgme1.0, and
python-debian:

* focal: distro-info, dput, gpgme1.0, and python-debian okay
* jammy: dput and python-debian okay
* kinetic: dput and python-debian okay

* jammy:
  - distro-info: livecd-rootfs/2.765.20 regression on amd64
  - gpgme1.0: ros-ros-comm/blacklisted regression on s390x
* lunar:
  - dput: dgit/blacklisted regression on s390x

The ros-ros-comm/blacklisted and dgit/blacklisted failures are no
regressions. I retried livecd-rootfs/2.765.20.

-- 
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 dput 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:
  Fix Released
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 dput 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:
  Fix Committed
Status in dput source package in Focal:
  Fix Committed
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
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:
  Fix Committed
Status in dput source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
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 dput source package in Kinetic:
  Fix Committed
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
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
Status in dput source package in Lunar:
  Fix Committed

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 

[Touch-packages] [Bug 2027594] [NEW] Split gstreamer1.0-plugins-bad to facilitate inclusion in Ubuntu main

[Jeremy Bícha]

Public bug reported:

Proposal

Split the gstreamer1.0-plugins-bad binary package to allow it to potentially be 
included in Ubuntu main

Background
--
Many years ago, gstreamer split their plugins into good, bad, and ugly.
ugly have legal concerns, etc.
bad are lower quality than good

This is somewhat poetically described at
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/tree/main/subprojects/gst-plugins-bad

Years ago, Ubuntu moved some plugins needed for webcam support in the
Cheese app from bad to good with assurances from upstream that they were
planning on moving those plugins themselves in a future release. That
never happened and it doesn't appear like upstream intends to move *any*
plugins from bad to good.

For many years, GNOME has considered the bad plugins one of their
standard dependencies. This is true not just for Cheese but also for
GTK4 and webkitgtk.

However, it's not really all the -bad plugins. Fedora for instance
explicitly disables some of the -bad set because of legal concerns. (If
Fedora has legal concerns, then it sounds like those plugins should be
moved to -bad but it really doesn't look like like plugins are being re-
categorized after their initial inclusion.)

1.22

Ubuntu maintains the package move as a large patch. For the 1.22 release, 
upstream made a bigger change to one of those moved plugins to have it depend 
on another -bad plugin. Instead of moving yet another plugin to -good, our 
patch just kept that plugin at its 1.20 codebase. This is problematic.

Debian
--
By moving the webcam and related dependencies back to -bad, we can reduce our 
packaging diff with Debian. At least for the good set, the only remaining 
difference with Debian is our changes to disable some features on i386. (And 
Debian may align their i386 support to more closely match Ubuntu's).

I think we would need additional MIRs (at least libnice, libva) to push
this new -bad split into Debian. But it may make sense there too.

Alternative
---
One approach would be to also split the source package. However, this was 
rejected because it would add to the complexity since there would be a need to 
keep 2 complex source packages in sync with each other.

Timeline

Ubuntu Desktop needs the limited bad set in main in time for Ubuntu 24.04 LTS. 
Our goal is to get it done for 23.10.

Remaining issues

Could GNOME provide a set of recommended -bad plugins we should try to ship by 
default?

** Affects: gst-plugins-bad1.0 (Ubuntu)
 Importance: High
 Assignee: Jeremy Bícha (jbicha)
 Status: In Progress


** Tags: mantic

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

Title:
  Split gstreamer1.0-plugins-bad to facilitate inclusion in Ubuntu main

Status in gst-plugins-bad1.0 package in Ubuntu:
  In Progress

Bug description:
  Proposal
  
  Split the gstreamer1.0-plugins-bad binary package to allow it to potentially 
be included in Ubuntu main

  Background
  --
  Many years ago, gstreamer split their plugins into good, bad, and ugly.
  ugly have legal concerns, etc.
  bad are lower quality than good

  This is somewhat poetically described at
  
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/tree/main/subprojects/gst-plugins-bad

  Years ago, Ubuntu moved some plugins needed for webcam support in the
  Cheese app from bad to good with assurances from upstream that they
  were planning on moving those plugins themselves in a future release.
  That never happened and it doesn't appear like upstream intends to
  move *any* plugins from bad to good.

  For many years, GNOME has considered the bad plugins one of their
  standard dependencies. This is true not just for Cheese but also for
  GTK4 and webkitgtk.

  However, it's not really all the -bad plugins. Fedora for instance
  explicitly disables some of the -bad set because of legal concerns.
  (If Fedora has legal concerns, then it sounds like those plugins
  should be moved to -bad but it really doesn't look like like plugins
  are being re-categorized after their initial inclusion.)

  1.22
  
  Ubuntu maintains the package move as a large patch. For the 1.22 release, 
upstream made a bigger change to one of those moved plugins to have it depend 
on another -bad plugin. Instead of moving yet another plugin to -good, our 
patch just kept that plugin at its 1.20 codebase. This is problematic.

  Debian
  --
  By moving the webcam and related dependencies back to -bad, we can reduce our 
packaging diff with Debian. At least for the good set, the only remaining 
difference with Debian is our changes to disable some features on i386. (And 
Debian may align their i386 support to more closely match Ubuntu's).

  I think we would need additional MIRs (at least libnice, libva) to
  push this new -bad split into 

[Touch-packages] [Bug 1926752] Re: [23.10 FEAT] libgmp SIMD optimizations

[Graham Inggs]

I sponsored the upload to mantic

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

Title:
  [23.10 FEAT] libgmp SIMD optimizations

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in gmp package in Ubuntu:
  Fix Committed

Bug description:
  Optimize the GNU MP Bignum Library using vector instructions.

  - Requirement for Full Homomorphic Encryption, libgmp is used as a backend 
for NTL
  - libgmp performance is critical also for GNU Cobol on Z.
  Here a customer requested using packed decimal instructions in libgmp which 
does not appear to fit for libgmp - however SIMD would help on distros with ALS 
z13

  https://gmplib.org/#STATUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1926752/+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 1926752] Re: [23.10 FEAT] libgmp SIMD optimizations

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

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

Title:
  [23.10 FEAT] libgmp SIMD optimizations

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in gmp package in Ubuntu:
  Fix Committed

Bug description:
  Optimize the GNU MP Bignum Library using vector instructions.

  - Requirement for Full Homomorphic Encryption, libgmp is used as a backend 
for NTL
  - libgmp performance is critical also for GNU Cobol on Z.
  Here a customer requested using packed decimal instructions in libgmp which 
does not appear to fit for libgmp - however SIMD would help on distros with ALS 
z13

  https://gmplib.org/#STATUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1926752/+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 2013543] Re: systemctl daemon-reexec forgets running services and starts everything new

[Nick Rosbrook]

It looks like the upstream issue has been fixed, so we can look into
getting this fixed in the next Jammy SRU.

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

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

** Tags added: systemd-sru-next

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

Title:
  systemctl daemon-reexec forgets running services and starts everything
  new

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Jammy:
  Triaged

Bug description:
  # Our problem #

  During a regular update of our container environment, `systemd` (and
  the related packages libpam-systemd, libsystemd0, libudev1, systemd-
  sysv and udev) were updated from `249.11-0ubuntu3.6` to
  `249.11-0ubuntu3.7`. We're talking only about Ubuntu 22.04. Our Ubuntu
  20.04 is working fine with `systemctl daemon-reexec`.

  In my opinion, the update was not the problem because we've tried
  downgrading and tried these versions: (current) `249.11-0ubuntu3.7`,
  `249.11-0ubuntu3.6`, `249.11-0ubuntu3.4` and `249.11-0ubuntu3.3`. The
  symptoms were the same.

  # Symptoms #

  The `/var/lib/dpkg/info/systemd.postinst` executes a `systemctl
  daemon-reexec` and that ended in a disaster. It seems that `systemd`
  is forgetting all it started children and tries to start nearly every
  configured service again. Naturally, the old services are still
  running, and the ports can't be opened twice and `systemd` won't give
  up. Here are some(!) of the logfiles:

  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Starting Create Volatile Files and 
Directories...
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found 
left-over process 130 (systemd-udevd) in control group while starting unit. 
Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found 
left-over process 31475 (systemd-udevd) in control group while starting unit. 
Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: systemd-udevd.service: Found 
left-over process 31476 (systemd-udevd) in control group while starting unit. 
Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.

  And...

  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Reached target System 
Initialization.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily apt download 
activities.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily apt upgrade and clean 
activities.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily dpkg database backup 
timer.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Periodic ext4 Online 
Metadata Check for All Filesystems.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Condition check resulted in Discard 
unused blocks once a week being skipped.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily rotation of log files.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily man-db regeneration.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Message of the Day.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Clean PHP session files 
every 30 mins.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Update the plocate database 
daily.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Daily Cleanup of Temporary 
Directories.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Reached target Basic System.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: System is tainted: cgroupsv1
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Reached target Timer Units.

  And...

  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: atd.service: Found left-over 
process 206 (atd) in control group while starting unit. Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Starting Deferred execution 
scheduler...
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: cron.service: Found left-over 
process 164 (cron) in control group while starting unit. Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: This usually indicates unclean 
termination of a previous run, or service implementation deficiencies.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: Started Regular background program 
processing daemon.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: dbus.service: Found left-over 
process 177 (dbus-daemon) in control group while starting unit. Ignoring.
  Mar 31 12:51:39 FQDN_REDACTED systemd[1]: 

[Touch-packages] [Bug 2019010] Re: environment variable SSH_ORIGINAL_COMMAND on server side set with wrong value

[Sergio Durigan Junior]

Hello Andrey,

This seems to be more of a support question than a bug per se, so I am
keeping this bug marked as Expired.  There are many places where you can
obtain help for the questions you are having; you can take a look at
https://www.ubuntu.com/support/community and choose one of the available
fora.

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

Title:
  environment variable SSH_ORIGINAL_COMMAND  on server side set with
  wrong value

Status in openssh package in Ubuntu:
  Expired

Bug description:
  After updating to Ubuntu 23.04 when running  scp command environment variable 
SSH_ORIGINAL_COMMAND on server side is set with 
SSH_ORIGINAL_COMMAND=/usr/libexec/openssh/sftp-server.
  With  previous version this environment variable  was set to "scp -t " or "scp -f  " depends on if it was push or get command to 
copy file from or to remote system
  SSH_ORIGINAL_COMMAND environment variable is used to validate scp command on 
server side.

  System information:
  lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu 23.04
  Release:  23.04

  
  apt-cache policy openssh-client
  openssh-client:
Installed: 1:9.0p1-1ubuntu8
Candidate: 1:9.0p1-1ubuntu8
Version table:
   *** 1:9.0p1-1ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2019010/+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 1926752] Re: [23.10 FEAT] libgmp SIMD optimizations

[Graham Inggs]

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

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

Title:
  [23.10 FEAT] libgmp SIMD optimizations

Status in Ubuntu on IBM z Systems:
  In Progress
Status in gmp package in Ubuntu:
  Fix Committed

Bug description:
  Optimize the GNU MP Bignum Library using vector instructions.

  - Requirement for Full Homomorphic Encryption, libgmp is used as a backend 
for NTL
  - libgmp performance is critical also for GNU Cobol on Z.
  Here a customer requested using packed decimal instructions in libgmp which 
does not appear to fit for libgmp - however SIMD would help on distros with ALS 
z13

  https://gmplib.org/#STATUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1926752/+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 1926752] Re: [23.10 FEAT] libgmp SIMD optimizations

[Graham Inggs]

** Changed in: gmp (Ubuntu)
 Assignee: (unassigned) => Graham Inggs (ginggs)

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

Title:
  [23.10 FEAT] libgmp SIMD optimizations

Status in Ubuntu on IBM z Systems:
  In Progress
Status in gmp package in Ubuntu:
  In Progress

Bug description:
  Optimize the GNU MP Bignum Library using vector instructions.

  - Requirement for Full Homomorphic Encryption, libgmp is used as a backend 
for NTL
  - libgmp performance is critical also for GNU Cobol on Z.
  Here a customer requested using packed decimal instructions in libgmp which 
does not appear to fit for libgmp - however SIMD would help on distros with ALS 
z13

  https://gmplib.org/#STATUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1926752/+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 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

[Benjamin Drung]

The net autopkgtest is too fragile in my opinion. For example [1] failed
to download the cloud-image. So I suggest to better backport the porting
of the net autopkgtest to the common test framework from initramfs-tools
0.142ubuntu3.

I can prepare the debdiff if you want.

[1] https://autopkgtest.ubuntu.com/results/autopkgtest-
mantic/mantic/amd64/i/initramfs-tools/20230502_101701_0a75f@/log.gz

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

Title:
  autopkgtest net is failing on 6.2 kernels with 'System is deadlocked
  on memory'

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools source package in Jammy:
  New
Status in initramfs-tools source package in Lunar:
  New

Bug description:
  [Impact]
  In debian/tests/run-image we instantiate an image with 512Mb of ram, but 
recent jammy/lunar 6.2 kernels need more than that.

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

  'net' test fails with a kernel panic due to out-of-memory.

  [Fix]

  Increase the size to 1Gb.

  [Test Plan]
  1. Download a lunar image:
  $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
  2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
  $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img

  [Where problems could occur]
  The usage of a larger image for the tests could fail if the the test system 
is low on ram size.

  Notes:
  It seems Mantic already uses 1G, so nothing has to be changed there. I also 
tested it locally and I confirm it works as expected there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

[Roxana Nicolescu]

** Patch added: "jammy.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+attachment/5685721/+files/jammy.debdiff

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

Title:
  autopkgtest net is failing on 6.2 kernels with 'System is deadlocked
  on memory'

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools source package in Jammy:
  New
Status in initramfs-tools source package in Lunar:
  New

Bug description:
  [Impact]
  In debian/tests/run-image we instantiate an image with 512Mb of ram, but 
recent jammy/lunar 6.2 kernels need more than that.

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

  'net' test fails with a kernel panic due to out-of-memory.

  [Fix]

  Increase the size to 1Gb.

  [Test Plan]
  1. Download a lunar image:
  $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
  2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
  $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img

  [Where problems could occur]
  The usage of a larger image for the tests could fail if the the test system 
is low on ram size.

  Notes:
  It seems Mantic already uses 1G, so nothing has to be changed there. I also 
tested it locally and I confirm it works as expected there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

[Roxana Nicolescu]

Jammy fix is attached.

Tested locally after downloading a jammy image and then I installed
aws-6.2 kernel:

$ autopkgtest initramfs-tools -- qemu autopkgtest-jammy-amd64.img
It uses the package in updates, therefore this fails:

Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... [   16.508817] mv invoked oom-killer: 
gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COM0
[   16.509481] CPU: 0 PID: 162 Comm: mv Not tainted 6.2.0-24-generic #24-Ubuntu
[   16.509891] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 
1.16.0-debian-1.16.0-5 04/01/2014
[   16.510640] Call Trace:
[   16.511260]  
[   16.511555]  dump_stack_lvl+0x48/0x70
[   16.512040]  dump_stack+0x10/0x20
[   16.512238]  dump_header+0x50/0x290
[   16.512436]  oom_kill_process+0x10d/0x1c0
[   16.512679]  out_of_memory+0x101/0x370
[   16.512904]  __alloc_pages_may_oom+0x112/0x1e0
[   16.513159]  __alloc_pages_slowpath.constprop.0+0x4c7/0xa20
[   16.513545]  __alloc_pages+0x31d/0x350
[   16.513867]  __folio_alloc+0x1d/0x60
[   16.514150]  ? policy_node+0x69/0x80
[   16.514378]  vma_alloc_folio+0x9f/0x3d0
[   16.514749]  shmem_alloc_folio+0x7c/0xd0
[   16.515089]  shmem_alloc_and_acct_folio+0x77/0x1c0
[   16.515362]  shmem_get_folio_gfp+0x311/0x7a0
[   16.515640]  ? touch_atime+0x44/0x1c0
[   16.515947]  shmem_write_begin+0x68/0x140
[   16.516260]  generic_perform_write+0xd0/0x220
[   16.516641]  __generic_file_write_iter+0xe8/0x1a0
[   16.516985]  ? apparmor_file_permission+0x85/0x1b0
[   16.517398]  generic_file_write_iter+0x70/0xf0
[   16.517723]  vfs_write+0x251/0x410
[   16.517998]  ksys_write+0x73/0x100
[   16.518240]  __x64_sys_write+0x19/0x30
[   16.518487]  do_syscall_64+0x5b/0x90
[   16.518780]  ? do_syscall_64+0x67/0x90
[   16.519059]  ? exit_to_user_mode_prepare+0x30/0xb0
[   16.519397]  ? syscall_exit_to_user_mode+0x29/0x50
[   16.519748]  ? do_syscall_64+0x67/0x90
[   16.520049]  entry_SYSCALL_64_after_hwframe+0x72/0xdc
[   16.520575] RIP: 0033:0x7fb923f309e4
[   16.521240] Code: 15 39 a4 0e 00 f7 d8 64 89 02 48 c7 c0 ff ff ff ff eb b7 
0f 1f 00 f3 0f 1e fa 80 3d fd 2b 0f 00 00 74 13 8
[   16.522170] RSP: 002b:7ffc2527fff8 EFLAGS: 0202 ORIG_RAX: 
0001
[   16.522674] RAX: ffda RBX:  RCX: 7fb923f309e4
[   16.523104] RDX: 0001 RSI: 7fb923dd3000 RDI: 000b
[   16.523545] RBP: 0001 R08:  R09: 
[   16.524004] R10: 0022 R11: 0202 R12: 000b
[   16.524433] R13: 7fb923dd3000 R14: 0001 R15: 0001
[   16.525104]  
[   16.525688] Mem-Info:
[   16.526175] active_anon:6 inactive_anon:28818 isolated_anon:0
[   16.526175]  active_file:61 inactive_file:40 isolated_file:0
[   16.526175]  unevictable:72423 dirty:3 writeback:0
[   16.526175]  slab_reclaimable:4768 slab_unreclaimable:4347
[   16.526175]  mapped:869 shmem:28384 pagetables:39
[   16.526175]  sec_pagetables:0 bounce:0
[   16.526175]  kernel_misc_reclaimable:0
[   16.526175]  free:1154 free_pcp:0 free_cma:0
[   16.528299] Node 0 active_anon:24kB inactive_anon:115272kB active_file:244kB 
inactive_file:160kB unevictable:289692kB isolao
[   16.530339] Node 0 DMA free:1492kB boost:0kB min:100kB low:124kB high:148kB 
reserved_highatomic:0KB active_anon:0kB inactivB
[   16.531975] lowmem_reserve[]: 0 349 349 349 349
[   16.532412] Node 0 DMA32 free:3124kB boost:2048kB min:4388kB low:4972kB 
high:5556kB reserved_highatomic:0KB active_anon:24kB
[   16.534130] lowmem_reserve[]: 0 0 0 0 0
[   16.534655] Node 0 DMA: 0*4kB 3*8kB (UM) 0*16kB 0*32kB 1*64kB (M) 1*128kB 
(M) 1*256kB (U) 2*512kB (UM) 0*1024kB 0*2048kB 0*B
[   16.535894] Node 0 DMA32: 103*4kB (UME) 13*8kB (UE) 25*16kB (UME) 9*32kB 
(UM) 4*64kB (UM) 1*128kB (U) 2*256kB (U) 2*512kB (B
[   16.537081] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 
hugepages_size=2048kB
[   16.537717] 100913 total pagecache pages
[   16.538011] 0 pages in swap cache
[   16.538234] Free swap  = 0kB
[   16.538456] Total swap = 0kB
[   16.538810] 130942 pages RAM
[   16.539197] 0 pages HighMem/MovableOnly
[   16.539423] 15971 pages reserved
[   16.539638] 0 pages hwpoisoned
[   16.539963] Tasks state (memory values in pages):
[   16.540267] [  pid  ]   uid  tgid total_vm  rss pgtables_bytes swapents 
oom_score_adj name
[   16.541167] [ 90] 090 2918  940614400
 0 systemd-udevd
[   16.541829] [159] 0   159  729  480368640
 0 copymods
[   16.542390] [162] 0   162  808  416409600
 0 mv
[   16.542829] 
oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=/,mems_allowed=0,global_oom,task_memcg=/,task=system0
[   16.544887] Out of memory: Killed process 90 (systemd-udevd) 
total-vm:11672kB, anon-rss:1072kB, file-rss:2688kB, shmem-rss:0
[   16.606543] mv invoked oom-killer: 

[Touch-packages] [Bug 2027581] [NEW] useradd will grand root privileges for admin user

[Bugra Aydogar]

Public bug reported:

Hi,

As part of the Ubuntu Core 20, if a developer creates a user named
either admin or Admin, it will have  root privileges by default. I think
that this is a security issue but it requires input from the security
engineers/specialists.

Basically, if you look at the sudoers file under `/etc/sudoers`, you
will realize the following line;

```
# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL
```

And if someone creates a user by using admin as name, the system provide
root privilege.

```
sudo useradd -s /bin/bash -u 8003 -d /home/Admin --extrausers Admin
iotuc@ubuntu:~$ su Admin
Password:
Admin@ubuntu:/home/iotuc$ cat /etc/sudoers
cat: /etc/sudoers: Permission denied
Admin@ubuntu:/home/iotuc$ sudo cat /etc/sudoers
[sudo] password for Admin:
#
# This file MUST be edited with the 'visudo' command as root.
#
# Please consider adding local content in /etc/sudoers.d/ instead of
# directly modifying this file.
#
# See the man page for details on how to write a sudoers file.
#
Defaultsenv_reset
Defaultsmail_badpass
Defaults
secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin"
# Host alias specification
# User alias specification
# Cmnd alias specification
# User privilege specification
rootALL=(ALL:ALL) ALL
# Members of the admin group may gain root privileges
%admin ALL=(ALL) ALL
# Allow members of group sudo to execute any command
%sudoALL=(ALL:ALL) ALL
# See sudoers(5) for more information on "#include" directives:
#includedir /etc/sudoers.d
Admin@ubuntu:/home/iotuc$
```

Similarly, if I create a username called aydogar, it does not have root
privilege and this is expected.

```
sudo useradd -s /bin/bash -u 8004 -d /home/aydogar --extrausers aydogar
iotuc@ubuntu:~$ su aydogar
Password:
aydogar@ubuntu:/home/iotuc$ cat /etc/sudoers
cat: /etc/sudoers: Permission denied
aydogar@ubuntu:/home/iotuc$ sudo cat /etc/sudoers
[sudo] password for aydogar:
aydogar is not in the sudoers file.  This incident will be reported.
aydogar@ubuntu:/home/iotuc$
```

I think, this is a bug but would love here other ideas and inputs.

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

** Description changed:

  Hi,
  
- As part of the Ubuntu Core 20.04, if a developer creates a user named
+ As part of the Ubuntu Core 20, if a developer creates a user named
  either admin or Admin, it will have  root privileges by default. I think
  that this is a security issue but it requires input from the security
  engineers/specialists.
  
  Basically, if you look at the sudoers file under `/etc/sudoers`, you
  will realize the following line;
  
  ```
  # Members of the admin group may gain root privileges
  %admin ALL=(ALL) ALL
  ```
  
- And if someone creates a user by using admin as name, the system provide root 
privilege. 
-  
+ And if someone creates a user by using admin as name, the system provide
+ root privilege.
+ 
  ```
  sudo useradd -s /bin/bash -u 8003 -d /home/Admin --extrausers Admin
  iotuc@ubuntu:~$ su Admin
- Password: 
+ Password:
  Admin@ubuntu:/home/iotuc$ cat /etc/sudoers
  cat: /etc/sudoers: Permission denied
  Admin@ubuntu:/home/iotuc$ sudo cat /etc/sudoers
- [sudo] password for Admin: 
+ [sudo] password for Admin:
  #
  # This file MUST be edited with the 'visudo' command as root.
  #
  # Please consider adding local content in /etc/sudoers.d/ instead of
  # directly modifying this file.
  #
  # See the man page for details on how to write a sudoers file.
  #
  Defaultsenv_reset
  Defaultsmail_badpass
  Defaults
secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/snap/bin"
  # Host alias specification
  # User alias specification
  # Cmnd alias specification
  # User privilege specification
  rootALL=(ALL:ALL) ALL
  # Members of the admin group may gain root privileges
  %admin ALL=(ALL) ALL
  # Allow members of group sudo to execute any command
  %sudoALL=(ALL:ALL) ALL
  # See sudoers(5) for more information on "#include" directives:
  #includedir /etc/sudoers.d
- Admin@ubuntu:/home/iotuc$ 
+ Admin@ubuntu:/home/iotuc$
  ```
  
  Similarly, if I create a username called aydogar, it does not have root
  privilege and this is expected.
  
  ```
  sudo useradd -s /bin/bash -u 8004 -d /home/aydogar --extrausers aydogar
  iotuc@ubuntu:~$ su aydogar
- Password: 
+ Password:
  aydogar@ubuntu:/home/iotuc$ cat /etc/sudoers
  cat: /etc/sudoers: Permission denied
  aydogar@ubuntu:/home/iotuc$ sudo cat /etc/sudoers
- [sudo] password for aydogar: 
+ [sudo] password for aydogar:
  aydogar is not in the sudoers file.  This incident will be reported.
- aydogar@ubuntu:/home/iotuc$ 
+ aydogar@ubuntu:/home/iotuc$
  ```
  
  I think, this is a bug but would love here other ideas and inputs.

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

Title:

[Touch-packages] [Bug 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

[Roxana Nicolescu]

** Patch added: "lunar.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+attachment/5685716/+files/lunar.debdiff

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

Title:
  autopkgtest net is failing on 6.2 kernels with 'System is deadlocked
  on memory'

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools source package in Jammy:
  New
Status in initramfs-tools source package in Lunar:
  New

Bug description:
  [Impact]
  In debian/tests/run-image we instantiate an image with 512Mb of ram, but 
recent jammy/lunar 6.2 kernels need more than that.

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

  'net' test fails with a kernel panic due to out-of-memory.

  [Fix]

  Increase the size to 1Gb.

  [Test Plan]
  1. Download a lunar image:
  $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
  2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
  $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img

  [Where problems could occur]
  The usage of a larger image for the tests could fail if the the test system 
is low on ram size.

  Notes:
  It seems Mantic already uses 1G, so nothing has to be changed there. I also 
tested it locally and I confirm it works as expected there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

[Roxana Nicolescu]

Lunar fix is attached.

Tested locally after downloading a lunar image:

$ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img
It uses the package in updates, therefore this fails:
Begin: Running /scripts/local-bottom ... done.
...
...
[   17.069410] Call Trace:
[   17.069504]  
[   17.069594]  dump_stack_lvl+0x48/0x70
[   17.069747]  dump_stack+0x10/0x20
[   17.069866]  panic+0x37b/0x3c0
[   17.070029]  out_of_memory+0x36c/0x370
[   17.070226]  __alloc_pages_may_oom+0x112/0x1e0
[   17.070480]  __alloc_pages_slowpath.constprop.0+0x4c7/0xa20
[   17.070761]  __alloc_pages+0x31d/0x350
[   17.070992]  alloc_pages+0x90/0x1a0
[   17.071179]  __get_free_pages+0x11/0x50
[   17.071362]  pgd_alloc+0x20/0xc0
[   17.071548]  mm_init+0x18a/0x390
[   17.071730]  dup_mm.constprop.0+0x51/0x120
[   17.071933]  copy_process+0xae3/0x1570
[   17.072165]  kernel_clone+0xbd/0x440
[   17.072373]  __do_sys_clone+0x76/0xb0
[   17.072587]  __x64_sys_clone+0x25/0x40
[   17.072816]  do_syscall_64+0x5b/0x90
[   17.073027]  ? syscall_exit_to_user_mode+0x29/0x50
[   17.073269]  ? do_syscall_64+0x67/0x90
[   17.073446]  ? do_user_addr_fault+0x1e8/0x720
[   17.073654]  ? exit_to_user_mode_prepare+0x30/0xb0
[   17.073871]  ? irqentry_exit_to_user_mode+0x9/0x20
[   17.074089]  ? irqentry_exit+0x43/0x50
[   17.074322]  ? exc_page_fault+0x91/0x1b0
[   17.074474]  entry_SYSCALL_64_after_hwframe+0x72/0xdc
[   17.074723] RIP: 0033:0x7fb27d64be07
[   17.074897] Code: 00 66 90 f3 0f 1e fa 64 48 8b 04 25 10 00 00 00 45 31 c0 
31 d2 31 f6 bf 11 00 20 01 4c 8d 90 d0 02 00 00 0
[   17.075588] RSP: 002b:7ffc9dba5538 EFLAGS: 0246 ORIG_RAX: 
0038
[   17.075976] RAX: ffda RBX:  RCX: 7fb27d64be07
[   17.076359] RDX:  RSI:  RDI: 01200011
[   17.076669] RBP:  R08:  R09: 
[   17.077004] R10: 7fb27d567a10 R11: 0246 R12: 0001
[   17.077354] R13: 556e56d9f5f0 R14: 556e56d9d798 R15: 
[   17.077722]  
[   17.078438] Kernel Offset: 0x2c0 from 0x8100 (relocation 
range: 0x8000-0xbfff)
[   17.079602] ---[ end Kernel panic - not syncing: System is deadlocked on 
memory ]---
qemu-system-x86_64: terminating on signal 15 from pid 7616 (timeout)
autopkgtest [14:15:54]: test net: ---]
autopkgtest [14:15:55]: test net:  - - - - - - - - - - results - - - - - - - - 
- -
net  FAIL non-zero exit status 124
autopkgtest [14:15:55]:  summary
amd64-klibc  PASS
amd64-busyboxPASS
amd64-ata-only   PASS
amd64-virtio-onlyPASS
amd64-separate-usr   PASS
amd64-panic-shellPASS
command1 PASS
net  FAIL non-zero exit status 124
qemu-system-x86_64: terminating on signal 15 from pid 40557 (/usr/bin/python3)

$ autopkgtest ~/canonical/initramf-tools/initramfs-tools_0.142ubuntu3.dsc -- 
qemu autopkgtest-lunar-amd64.img 
This is the fix and the results are good:

net  PASS
autopkgtest [14:32:26]:  summary
amd64-klibc  PASS
amd64-busyboxPASS
amd64-ata-only   PASS
amd64-virtio-onlyPASS
amd64-separate-usr   PASS
amd64-panic-shellPASS
command1 PASS
net  PASS
qemu-system-x86_64: terminating on signal 15 from pid 46267 (/usr/bin/python3)

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

Title:
  autopkgtest net is failing on 6.2 kernels with 'System is deadlocked
  on memory'

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools source package in Jammy:
  New
Status in initramfs-tools source package in Lunar:
  New

Bug description:
  [Impact]
  In debian/tests/run-image we instantiate an image with 512Mb of ram, but 
recent jammy/lunar 6.2 kernels need more than that.

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

  'net' test fails with a kernel panic due to out-of-memory.

  [Fix]

  Increase the size to 1Gb.

  [Test Plan]
  1. Download a lunar image:
  $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
  2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
  $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img

  [Where problems could occur]
  The usage of a larger image for the tests could fail if the the test system 
is low on ram size.

  Notes:
  It seems Mantic already uses 1G, so nothing has to be changed there. I also 
tested it locally and I confirm it works as expected there.

To manage notifications about this bug go 

[Touch-packages] [Bug 2027575] Re: autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

[Roxana Nicolescu]

** Description changed:

  [Impact]
  In debian/tests/run-image we instantiate an image with 512Mb of ram, but 
recent jammy/lunar 6.2 kernels need more than that.
  
  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz
  
  'net' test fails with a kernel panic due to out-of-memory.
  
  [Fix]
  
  Increase the size to 1Gb.
  
  [Test Plan]
  1. Download a lunar image:
  $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
  2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
- $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img 
- 
+ $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img
  
  [Where problems could occur]
  The usage of a larger image for the tests could fail if the the test system 
is low on ram size.
+ 
+ Notes:
+ It seems Mantic already uses 1G, so nothing has to be changed there. I also 
tested it locally and I confirm it works as expected there.

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

Title:
  autopkgtest net is failing on 6.2 kernels with 'System is deadlocked
  on memory'

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools source package in Jammy:
  New
Status in initramfs-tools source package in Lunar:
  New

Bug description:
  [Impact]
  In debian/tests/run-image we instantiate an image with 512Mb of ram, but 
recent jammy/lunar 6.2 kernels need more than that.

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

  'net' test fails with a kernel panic due to out-of-memory.

  [Fix]

  Increase the size to 1Gb.

  [Test Plan]
  1. Download a lunar image:
  $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
  2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
  $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img

  [Where problems could occur]
  The usage of a larger image for the tests could fail if the the test system 
is low on ram size.

  Notes:
  It seems Mantic already uses 1G, so nothing has to be changed there. I also 
tested it locally and I confirm it works as expected there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 2016145] Re: Wrong ownership for /var/lib/libuuid/

[Mauricio Faria de Oliveira]

Thanks for reporting this bug!

Could not reproduce with Kinetic (22.10) or Lunar (23.04).

Kinetic will EOL soon. Can you reproduce this with Lunar?

Thanks!


$ lsb_release -cs
No LSB modules are available.
lunar

$ uuidgen -t
039c7806-20ae-11ee-ba46-54e1ad759c00

...

$ lsb_release -cs
kinetic

$ uuidgen -t
1a838b2c-20ae-11ee-8bfa-335c39eef75c

$ dpkg -s uuid-runtime | grep Version:
Version: 2.38-4ubuntu1

$ ls -ld /var/lib/libuuid
drwxr-xr-x 2 root root 4096 May  3  2022 /var/lib/libuuid


** Changed in: util-linux (Ubuntu)
   Status: New => Invalid

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

Title:
  Wrong ownership for /var/lib/libuuid/

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 22.10, uuid-runtime version 2.38-4ubuntu1

  I noticed that if I ran "uuidgen -t" then I would get a line like this
  in my system logs: "uuidd: failed to open/lock clock counter"

  Using strace I saw that the reason was a lack of permission to write
  to "/var/lib/libuuid/clock.txt".  The directory "/var/lib/libuuid/" is
  owned by root, however "uuidd" is run as a systemd service
  (uuidd.service) as user "uuidd".  This fixed it: "sudo chown
  uuidd:uuidd /var/lib/libuuid/".

  So I think the uuid-runtime package should ensure that
  "/var/lib/libuuid" is owned by "uuid".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2016145/+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 1981769] Re: blkid fails to find btrfs zoned filesystem label or uuid

[Mauricio Faria de Oliveira]

The problem does not seem to be in util-linux, as it works correctly
with a loop device.

Can you confirm whether you have /dev/disk/by-label/ symlinks for the
new filesystem?

$ lsb_release -cs
jammy

$ truncate -s 15T disk.img
$ DEV=$(sudo losetup --find --show disk.img)

$ sudo mkfs.btrfs -O zoned -d single -m single -f $DEV -L cf1657839355
btrfs-progs v5.16.2
See http://btrfs.wiki.kernel.org for more information.

NOTE: several default settings have changed in version 5.15, please make sure
  this does not affect your deployments:
  - DUP for metadata (-m dup)
  - enabled no-holes (-O no-holes)
  - enabled free-space-tree (-R free-space-tree)

Label:  cf1657839355
UUID:   381ff1f0-714a-411e-95c5-0fbd67979da5
Node size:  16384
Sector size:4096
Filesystem size:15.00TiB
Block group profiles:
  Data: single  256.00MiB
  Metadata: single  256.00MiB
  System:   single  256.00MiB
SSD detected:   no
Zoned device:   yes
  Zone size:256.00MiB
Incompat features:  extref, skinny-metadata, no-holes, zoned
Runtime features:   free-space-tree
Checksum:   crc32c
Number of devices:  1
Devices:
   IDSIZE  PATH
115.00TiB  /dev/loop5

$ sudo blkid | grep $DEV
/dev/loop5: LABEL="cf1657839355" UUID="381ff1f0-714a-411e-95c5-0fbd67979da5" 
UUID_SUB="0c2c7073-6ee7-4d42-aefe-834cb0a7f1b2" BLOCK_SIZE="4096" TYPE="btrfs"

$ sudo mount LABEL=cf1657839355 /mnt
$ mount | grep /mnt
/dev/loop5 on /mnt type btrfs 
(rw,relatime,discard=async,space_cache=v2,subvolid=5,subvol=/)

$ ls -l /dev/disk/by-label/
total 0
lrwxrwxrwx 1 root root 11 Jul 12 12:03 UEFI -> ../../sda15
lrwxrwxrwx 1 root root 11 Jul 12 12:11 cf1657839355 -> ../../loop5
lrwxrwxrwx 1 root root 10 Jul 12 12:03 cloudimg-rootfs -> ../../sda1


** Changed in: util-linux (Ubuntu)
   Status: New => Incomplete

** Changed in: util-linux (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  blkid fails to find btrfs zoned filesystem label or uuid

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  System Info:

  lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  
  1. Using an HM SMR drive (I used: ST14000NM0007-2G) create a zoned btrfs 
filesystem

  sudo mkfs.btrfs -O zoned -d single -m single -f /dev/sdb -L cf1657839355
  btrfs-progs v5.16.2
  See http://btrfs.wiki.kernel.org for more information.

  Resetting device zones /dev/sdb (52156 zones) ...
  NOTE: several default settings have changed in version 5.15, please make sure
this does not affect your deployments:
- DUP for metadata (-m dup)
- enabled no-holes (-O no-holes)
- enabled free-space-tree (-R free-space-tree)

  Label:  cf1657839355
  UUID:   5b7d5659-0ed3-45d3-a36b-fb58eeb93f72
  Node size:  16384
  Sector size:4096
  Filesystem size:12.73TiB
  Block group profiles:
Data: single  256.00MiB
Metadata: single  256.00MiB
System:   single  256.00MiB
  SSD detected:   no
  Zoned device:   yes
Zone size:256.00MiB
  Incompat features:  extref, skinny-metadata, no-holes, zoned
  Runtime features:   free-space-tree
  Checksum:   crc32c
  Number of devices:  1
  Devices:
 IDSIZE  PATH
  112.73TiB  /dev/sdb

  2. Try to use LABEL method to mount

  sudo mount LABEL=cf1657839355 cf1657839355
  mount: cf1657839355: can't find LABEL=cf1657839355.

  Expected that LABEL would be found.  I suspect that libblkid is where
  the issue is since this commands returns all of my other block devices
  except for /dev/sdb.

  sudo blkid|grep sdb

  
  It will mount using hard coded device path

  sudo mount /dev/sdb cf1657839355
  df -h /dev/sdb
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sdb 13T  3.5M   13T   1% /cf1657839355
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-05-20 (421 days ago)
  InstallationMedia: Ubuntu-Server 20.10 "Groovy Gorilla" - Release amd64 
(20201022)
  Package: util-linux 2.37.2-4ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.15.0-41.44-generic 5.15.39
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-41-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-07-14 (1 days ago)
  UserGroups: N/A
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1981769/+subscriptions


-- 
Mailing list: 

[Touch-packages] [Bug 2027575] [NEW] autopkgtest net is failing on 6.2 kernels with 'System is deadlocked on memory'

[Roxana Nicolescu]

Public bug reported:

[Impact]
In debian/tests/run-image we instantiate an image with 512Mb of ram, but recent 
jammy/lunar 6.2 kernels need more than that.

Example of a test failure:
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

'net' test fails with a kernel panic due to out-of-memory.

[Fix]

Increase the size to 1Gb.

[Test Plan]
1. Download a lunar image:
$ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
$ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img 


[Where problems could occur]
The usage of a larger image for the tests could fail if the the test system is 
low on ram size.

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

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

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


** Tags: sru-20230612 sru-230230710

** Tags added: sru-20230612 sru-230230710

** Also affects: initramfs-tools (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

Title:
  autopkgtest net is failing on 6.2 kernels with 'System is deadlocked
  on memory'

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools source package in Jammy:
  New
Status in initramfs-tools source package in Lunar:
  New

Bug description:
  [Impact]
  In debian/tests/run-image we instantiate an image with 512Mb of ram, but 
recent jammy/lunar 6.2 kernels need more than that.

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/i/initramfs-tools/20230619_135049_ab1cb@/log.gz

  'net' test fails with a kernel panic due to out-of-memory.

  [Fix]

  Increase the size to 1Gb.

  [Test Plan]
  1. Download a lunar image:
  $ autopkgtest-buildvm-ubuntu-cloud -v -a amd64 -r lunar
  2. Run autotestpkg tests from initramfs-tools package. The "net" test is the 
one that depends on the image instantiated by 'run-image'. The testcase should 
complete successfully without the kernel panic.
  $ autopkgtest initramfs-tools -- qemu autopkgtest-lunar-amd64.img 

  
  [Where problems could occur]
  The usage of a larger image for the tests could fail if the the test system 
is low on ram size.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2027575/+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 2020913] Re: /etc/profile.d/debuginfd.{sh, csh} are created with 600 permissions

[Robie Basak]

I discussed this with Sergio elsewhere and we concluded that we don't
want to change behaviour in Jammy to opt users in to start automatically
reaching debuginfod.ubuntu.com without further discussion. So for this
bug, we'll consider the issue to be simply that if the user configures a
server in /etc/debuginfod/, then the installed profile snippets won't
pick it up so that won't work. Sergio will update the User Impact, Test
Plan etc and then we'll be able to fix and validate this on that basis.

Changing behaviour in Jammy by opting users in to debuginfod.ubuntu.com
by default would then be a separate discussion and (if necessary)
tracked in a separate bug.

** Changed in: elfutils (Ubuntu Jammy)
   Status: In Progress => Incomplete

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

Title:
  /etc/profile.d/debuginfd.{sh,csh} are created with 600 permissions

Status in elfutils package in Ubuntu:
  Fix Released
Status in elfutils source package in Jammy:
  Incomplete

Bug description:
  [ Impact ]

  Users installing libdebuginfod-common (the package that ships the
  shell snippets responsible for configuring the DEBUGINFOD_URLS
  environment variable, which will ultimately be used by GDB to contact
  the Ubuntu debuginfod service) experience a problem caused by
  permissions being set too tightly for
  /etc/profile.d/debuginfod.{sh,csh}.  This results in DEBUGINFOD_URLS
  not being set for non-root users.

  [ Test Plan ]

  Inside a Jammy container:

  # apt install -y libdebuginfod-common
  # ls -lah /etc/profile.d/debuginfod*

  Verify that the permission of both files allow them to be world-
  readable.

  [ Where problems could occur ]

  Care has been taken to not modify existing file permissions
  unnecessarily by using "g+r,o+r" when invoking chmod, but it is still
  possible to conceive a scenario where upgrading the package would make
  the files world-readable when the user is actually expecting
  otherwise.  However, such "regression" would arguably not be something
  supported because if the intention is to prevent non-root users from
  making use of debuginfod, there are better ways to achieve it.

  [ Original Description ]

  In a fresh container, installing libdebuginfod-common gives a
  /etc/profile.d that looks like this:

  ```
  root@32f34f7e271e:/etc/profile.d# ls -lah
  total 24K
  drwxr-xr-x 1 root root 4.0K May 26 17:23 .
  drwxr-xr-x 1 root root 4.0K May 26 17:23 ..
  -rw-r--r-- 1 root root   96 Oct 15  2021 01-locale-fix.sh
  -rw--- 1 root root  677 May 26 17:23 debuginfod.csh
  -rw--- 1 root root  692 May 26 17:23 debuginfod.sh

  ```

  when I login as a nonprivledged user, DEBUGINFOD_URLS is not set
  because the permissions are incorrect on the profile files.

  ```
  # dpkg -l  | grep libdebug
  ii  libdebuginfod-common0.186-1build1   all   
   configuration to enable the Debian debug info server
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/2020913/+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 1926752] debdiff_gmp_mantic_from_6.2.1+dfsg1-1.1ubuntu1_to__6.2.1+dfsg1-1.1ubuntu2.diff

[bugproxy]

Default Comment by Bridge

** Attachment added: 
"debdiff_gmp_mantic_from_6.2.1+dfsg1-1.1ubuntu1_to__6.2.1+dfsg1-1.1ubuntu2.diff"
   
https://bugs.launchpad.net/bugs/1926752/+attachment/5685690/+files/debdiff_gmp_mantic_from_6.2.1+dfsg1-1.1ubuntu1_to__6.2.1+dfsg1-1.1ubuntu2.diff

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

Title:
  [23.10 FEAT] libgmp SIMD optimizations

Status in Ubuntu on IBM z Systems:
  In Progress
Status in gmp package in Ubuntu:
  In Progress

Bug description:
  Optimize the GNU MP Bignum Library using vector instructions.

  - Requirement for Full Homomorphic Encryption, libgmp is used as a backend 
for NTL
  - libgmp performance is critical also for GNU Cobol on Z.
  Here a customer requested using packed decimal instructions in libgmp which 
does not appear to fit for libgmp - however SIMD would help on distros with ALS 
z13

  https://gmplib.org/#STATUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1926752/+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 1926752] Re: [23.10 FEAT] libgmp SIMD optimizations

[Frank Heimes]

added updated debdiff

** Patch added: 
"debdiff_gmp_mantic_from_6.2.1+dfsg1-1.1ubuntu1_to__6.2.1+dfsg1-1.1ubuntu2.diff"
   
https://bugs.launchpad.net/ubuntu/+source/gmp/+bug/1926752/+attachment/5685689/+files/debdiff_gmp_mantic_from_6.2.1+dfsg1-1.1ubuntu1_to__6.2.1+dfsg1-1.1ubuntu2.diff

** Changed in: gmp (Ubuntu)
 Assignee: Frank Heimes (fheimes) => (unassigned)

** Information type changed from Private to Public

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

Title:
  [23.10 FEAT] libgmp SIMD optimizations

Status in Ubuntu on IBM z Systems:
  In Progress
Status in gmp package in Ubuntu:
  In Progress

Bug description:
  Optimize the GNU MP Bignum Library using vector instructions.

  - Requirement for Full Homomorphic Encryption, libgmp is used as a backend 
for NTL
  - libgmp performance is critical also for GNU Cobol on Z.
  Here a customer requested using packed decimal instructions in libgmp which 
does not appear to fit for libgmp - however SIMD would help on distros with ALS 
z13

  https://gmplib.org/#STATUS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1926752/+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 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).

[Chris Guiver]

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

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support (Bluetooth A2DP codecs).

Status in PulseAudio:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in Arch Linux:
  Invalid

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1838151/+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 2019212] Autopkgtest regression report (mesa/23.0.4-0ubuntu1~22.04.1)

[Ubuntu SRU Bot]

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

gtk4/blacklisted (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/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/2019212

Title:
  Backport packages for 22.04.3 HWE stack

Status in mesa package in Ubuntu:
  Invalid
Status in mesa-amber package in Ubuntu:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa-amber source package in Jammy:
  Fix Committed

Bug description:
  [Impact]
  The graphics HWE stack from lunar needs to be backported to jammy for 22.04.3

  mesa
  - new major release (23.0.4)

  mesa-amber
  - a minor update from upstream mesa (21.3.7 -> 21.3.9), though there were no 
changes to the classic dri drivers
  - drops old i915 driver, while mesa provides the more modern i915_dri.so 
called 
i915g
  - fixes installation (LP: #2006744) and image build

  [Test case]
  mesa:
  Install the new mesa on various hw configs, check that everything still works 
like before or better.

  mesa-amber:
  no need to test anything besides checking that the packages can be installed 
next to mesa and image build is fixed

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll backport 
the final stable release of 23.0.x in order to minimize the chance for those.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2019212/+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 2021948] Autopkgtest regression report (mesa/23.0.4-0ubuntu1~22.04.1)

[Ubuntu SRU Bot]

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

gtk4/blacklisted (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/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/2021948

Title:
  New bugfix release 23.0.4

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

Bug description:
  [Impact]

  This is the last point-release of the 23.0.x-series, we should put it
  in lunar so latest bugfixes would get there, and in jammy for 22.04.3
  image.

  We'll include an additional bugfix (a revert) to fix GPU hangs on some
  AMD gpu's running certain games.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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

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

[Julian Andres Klode]

The approach to take would be to add a block-proposed-jammy tag and then
the SRU can be processed and it will just say in proposed until another
SRU gets along that replaces (and includes) it, but at least it's built
and reviewed and visible to everyone.

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

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

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

Bug description:
  [Impact]

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

  Vendor ID: ARM
  Model: 0

  [Fix]

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

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

  [Test Steps]

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

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

  [What Could Go Wrong]

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+subscriptions


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