[Touch-packages] [Bug 2042776] Re: [Lenovo IdeaPad S340-14IIL 81VV, Realtek ALC257, Speaker, Internal] No sound at all

2024-03-31 Thread Daniel Letzeisen
** Summary changed:

- [81VV, Realtek ALC257, Speaker, Internal] No sound at all
+ [Lenovo IdeaPad S340-14IIL 81VV, Realtek ALC257, Speaker, Internal] No sound 
at all

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

Title:
  [Lenovo IdeaPad S340-14IIL 81VV, Realtek ALC257, Speaker, Internal] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  No sound whatsoever not even on external speakers. I suspected a
  hardware problem at first and by the way drivers have been updated but
  same issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  joseph-vunanga   4569 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov  5 20:04:21 2023
  InstallationDate: Installed on 2023-03-30 (220 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [81VV, Realtek ALC257, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/15/2021
  dmi.bios.release: 1.27
  dmi.bios.vendor: LENOVO
  dmi.bios.version: CUCN27WW(V1.16)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76446 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo IdeaPad S340-14IIL
  dmi.ec.firmware.release: 1.27
  dmi.modalias: 
dmi:bvnLENOVO:bvrCUCN27WW(V1.16):bd06/15/2021:br1.27:efr1.27:svnLENOVO:pn81VV:pvrLenovoIdeaPadS340-14IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0T76446WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS340-14IIL:skuLENOVO_MT_81VV_BU_idea_FM_IdeaPadS340-14IIL:
  dmi.product.family: IdeaPad S340-14IIL
  dmi.product.name: 81VV
  dmi.product.sku: LENOVO_MT_81VV_BU_idea_FM_IdeaPad S340-14IIL
  dmi.product.version: Lenovo IdeaPad S340-14IIL
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2042776/+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 2040020] Re: [Lenovo Legion Pro 7 16IRX8 82WR, Realtek ALC287, Speaker, Internal] No sound at all

2024-03-31 Thread Daniel Letzeisen
You probably need a fixup in the kernel for 17aa:3846
Example: 
https://github.com/torvalds/linux/blob/486291a0e6246364936df1ecd64c90affef4b9c5/sound/pci/hda/patch_realtek.c#L10328

You probably also need updated cirrus firmware.

** Summary changed:

- [82WR, Realtek ALC287, Speaker, Internal] No sound at all
+ [Lenovo Legion Pro 7 16IRX8 82WR, Realtek ALC287, Speaker, Internal] No sound 
at all

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

Title:
  [Lenovo Legion Pro 7 16IRX8 82WR, Realtek ALC287, Speaker, Internal]
  No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Legion-Pro-7-16IRX8 has no sound from built-in speakers, sound works
  over bluetooth and monitor speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-35.35~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bamm   2380 F pulseaudio
   /dev/snd/controlC1:  bamm   2380 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct 20 17:02:36 2023
  InstallationDate: Installed on 2023-10-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bamm   2380 F pulseaudio
   /dev/snd/controlC1:  bamm   2380 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82WR, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/20/2023
  dmi.bios.release: 1.38
  dmi.bios.vendor: LENOVO
  dmi.bios.version: KWCN38WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76461 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion Pro 7 16IRX8
  dmi.ec.firmware.release: 1.38
  dmi.modalias: 
dmi:bvnLENOVO:bvrKWCN38WW:bd06/20/2023:br1.38:efr1.38:svnLENOVO:pn82WR:pvrLegionPro716IRX8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76461WIN:cvnLENOVO:ct10:cvrLegionPro716IRX8:skuLENOVO_MT_82WR_BU_idea_FM_LegionPro716IRX8:
  dmi.product.family: Legion Pro 7 16IRX8
  dmi.product.name: 82WR
  dmi.product.sku: LENOVO_MT_82WR_BU_idea_FM_Legion Pro 7 16IRX8
  dmi.product.version: Legion Pro 7 16IRX8
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2040020/+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 2056590] Re: No physical sound through speakers, settings show sound.

2024-03-31 Thread Daniel Letzeisen
You're going to need a kernel >= 6.7
https://github.com/torvalds/linux/blob/486291a0e6246364936df1ecd64c90affef4b9c5/sound/pci/hda/patch_realtek.c#L10086

You probably also need newer cirrus firmware: https://gitlab.com/asus-
linux/firmware/-/tree/main/cirrus

Ubuntu 24.04 will be released in a few weeks and have the needed
components.

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

** Summary changed:

- No physical sound through speakers, settings show sound.
+ [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294] No physical sound through 
speakers, settings show sound.

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

Title:
  [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294] No physical sound
  through speakers, settings show sound.

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Running a dual boot configuration with windows 11 and ubuntu 22.04 LTS.
  Bluetooth headset does not give problems.
  Microphone works, but bad quality.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: 
./pool/restricted/n/nvidia-graphics-drivers-525/libnvidia-compute-525_525.147.05-0ubuntu0.22.04.1_amd64.deb
  CasperMD5CheckResult: fail
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  8 18:11:08 2024
  InstallationDate: Installed on 2024-02-28 (9 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Zenbook 15 UM3504DA_UM3504DA, Realtek ALC294, Speaker, Internal] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/02/2023
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: UM3504DA.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UM3504DA
  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.:bvrUM3504DA.307:bd10/02/2023:br5.24:svnASUSTeKCOMPUTERINC.:pnZenbook15UM3504DA_UM3504DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUM3504DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: Zenbook
  dmi.product.name: Zenbook 15 UM3504DA_UM3504DA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2024-03-08T12:53:04.511698

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2056590/+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 2057957] Re: Headphone and speaker

2024-03-31 Thread Daniel Letzeisen
name 'Auto-Mute Mode'
value Disabled

You need to enable Auto-Mute in alsamixer.

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

Title:
  Headphone and speaker

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello, when connecting a headset to the PC, the sound comes out at the same 
time from the PC speaker and the headset.
  And the volume bar only appears to have an effect on the headphone jack. The 
sound coming out of the speaker remains the same volume.

  I tested it on the desktop, just turning down the volume, with the
  game Need for speed most wanted 2012, proton, on Steam (.deb)

  Steps to reproduce
  1 - Connect the headphones to the Laptop while it is still turned off
  2 - After connecting, carry out sound tests
  3 - the sound comes out of both headphones and speaker

  Thank you in advance, good luck to you always 

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-25.25~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  leandro 952 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 14 14:51:19 2024
  InstallationDate: Installed on 2024-01-13 (61 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/06/2023
  dmi.bios.release: 1.57
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GGCN57WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76466 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad 3 15ITL6
  dmi.ec.firmware.release: 1.57
  dmi.modalias: 
dmi:bvnLENOVO:bvrGGCN57WW:bd09/06/2023:br1.57:efr1.57:svnLENOVO:pn82MD:pvrIdeaPad315ITL6:rvnLENOVO:rnLNVNB161216:rvrSDK0T76466WIN:cvnLENOVO:ct10:cvrIdeaPad315ITL6:skuLENOVO_MT_82MD_BU_idea_FM_IdeaPad315ITL6:
  dmi.product.family: IdeaPad 3 15ITL6
  dmi.product.name: 82MD
  dmi.product.sku: LENOVO_MT_82MD_BU_idea_FM_IdeaPad 3 15ITL6
  dmi.product.version: IdeaPad 3 15ITL6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2057957/+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 1970069] Re: Annoying boot messages interfering with splash screen

2024-03-31 Thread Daniel van Vugt
In case anyone is wondering, you won't start to see an improvement until
you have at least:

linux >= 6.8.0-20.20 and
plymouth >= 24.004.60-1ubuntu6

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

Title:
  Annoying boot messages interfering with splash screen

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Kernel (and systemd) log messages appear during boot for many
  machines, when the user should be seeing only the BIOS logo and/or
  Plymouth splash screens.

  [ Workaround ]

  On most machines you can hide the problem by using these kernel parameters 
together:
    quiet splash loglevel=3 fastboot

  [ Original Description ]

  Since upgrading from 20.04.6 Desktop to 22.04, the boot screen is not
  as clean as it used to be.

  Basically, the flow used to be in 20.04:

  GRUB > Splash screen > Login prompt

  Currently in 22.04:

  GRUB > Splash screen > Messages (in the attached file) > Splash screen
  again for a sec > Login prompt

  All of those messages already existed in 20.04, the difference is that
  they were not appearing during boot.

  I was able to get rid of the "usb" related messages by just adding
  "loglevel=0" in GRUB. Currently is "quiet loglevel=0 splash".

  Regarding the fsck related message, I can get rid of them by adding
  "fsck.mode=skip".

  However, I do not want to just disable fsck or set the loglevel to 0.
  This is not a sustainable solution.

  Something definitely changed here. These messages are not of enough
  relevance to be shown at boot by default, and they should remain
  hidden like they were in Focal.

  Obviously a minor issue, but important to the whole look and feel of
  the OS for desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970069/+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 2059848] Re: Error in the calendar as shown in the print I attached

2024-03-31 Thread Daniel van Vugt
Please rename the video using Latin characters because Launchpad can't
handle other character sets and we're unable to download the video.

** 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/2059848

Title:
  Error in the calendar as shown in the print I attached

Status in Ubuntu:
  Incomplete

Bug description:
  The error happens when I click on the last days of the calendar

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-26.26~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Mar 30 16:28:25 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hightech Information System Ltd. Cedar [Radeon HD 
5000/6000/7350/8350 Series] [1787:5220]
  InstallationDate: Installed on 2024-03-29 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240220)
  MachineType: Semp Toshiba Informatica Ltda STI 007467
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-26-generic 
root=UUID=cffe7efc-9ab3-4fe8-93ad-c666ead76093 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/05/2012
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends, Inc.
  dmi.bios.version: 1.0
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: STI 007467
  dmi.board.vendor: Semp Toshiba Informatica Ltda
  dmi.chassis.type: 3
  dmi.chassis.vendor: Semp Toshiba Informatica Ltda
  dmi.modalias: 
dmi:bvnAmericanMegatrends,Inc.:bvr1.0:bd09/05/2012:br8.15:svnSempToshibaInformaticaLtda:pnSTI007467:pvrRev.10/00:rvnSempToshibaInformaticaLtda:rnSTI007467:rvr:cvnSempToshibaInformaticaLtda:ct3:cvr:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: STI 007467
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: Rev. 10/00
  dmi.sys.vendor: Semp Toshiba Informatica Ltda
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  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/2059848/+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 2059874] [NEW] on upgrade sshd-socket-generator conversion does not respect administrator intent

2024-03-31 Thread Andre Tomt
Public bug reported:

the openssh-server 1:9.6p1-3ubuntu11 postinst contains this code
snippet:

if [ "$action" == configure ]; then
  ..snip..
  if dpkg --compare-versions "$2" lt-nl 1:9.6p1-3ubuntu3~; then
..snip..
if [ -d /run/systemd/system ]; then
  # Make sure ssh.service is disabled.
  systemctl unmask ssh.service
  systemctl disable --now ssh.service > /dev/null 2>&1

  # sshd-socket-generator is invoked on daemon-reload.
  systemctl daemon-reload
  systemctl enable ssh.socket
fi
  fi
fi

This does not respect existing service and socket unit configuration, it
effectively re-enables a disabled ssh.service (and even a masked one),
and a manually disabled socket unit. I strongly suspect it does not
respect systemd presets either.

This is unexpected behaviour.

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

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

Title:
  on upgrade sshd-socket-generator conversion does not respect
  administrator intent

Status in openssh package in Ubuntu:
  New

Bug description:
  the openssh-server 1:9.6p1-3ubuntu11 postinst contains this code
  snippet:

  if [ "$action" == configure ]; then
..snip..
if dpkg --compare-versions "$2" lt-nl 1:9.6p1-3ubuntu3~; then
  ..snip..
  if [ -d /run/systemd/system ]; then
# Make sure ssh.service is disabled.
systemctl unmask ssh.service
systemctl disable --now ssh.service > /dev/null 2>&1

# sshd-socket-generator is invoked on daemon-reload.
systemctl daemon-reload
systemctl enable ssh.socket
  fi
fi
  fi

  This does not respect existing service and socket unit configuration,
  it effectively re-enables a disabled ssh.service (and even a masked
  one), and a manually disabled socket unit. I strongly suspect it does
  not respect systemd presets either.

  This is unexpected behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059874/+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 2059872] [NEW] Unable to listen on port 22 if multiple Port= present in sshd configuration

2024-03-31 Thread Andre Tomt
Public bug reported:

Recently introduced sshd-socket-generator for socket activation in
openssh 1:9.6p1-3ubuntu3 has a bug when dealing with multiple Port or
ListenAddress entries in the sshd configuration.

If you have multiple Port or ListenAddress and one of them is for port
22, it just skips it.

To show it clearly, here is an example:
Port 22
Port 1024

It generates:
ListenStream=
ListenStream=1024

Now nothing is listening to port 22, hence breaking existing
configurations.

This was tested on 1:9.6p1-3ubuntu11.

The intention seems to be to not generate the drop-in if only port 22 is
in use, but it does not account for the case of multiple Port or
ListenAddress where one of them is for port 22.

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

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

Title:
  Unable to listen on port 22 if multiple Port= present in sshd
  configuration

Status in openssh package in Ubuntu:
  New

Bug description:
  Recently introduced sshd-socket-generator for socket activation in
  openssh 1:9.6p1-3ubuntu3 has a bug when dealing with multiple Port or
  ListenAddress entries in the sshd configuration.

  If you have multiple Port or ListenAddress and one of them is for port
  22, it just skips it.

  To show it clearly, here is an example:
  Port 22
  Port 1024

  It generates:
  ListenStream=
  ListenStream=1024

  Now nothing is listening to port 22, hence breaking existing
  configurations.

  This was tested on 1:9.6p1-3ubuntu11.

  The intention seems to be to not generate the drop-in if only port 22
  is in use, but it does not account for the case of multiple Port or
  ListenAddress where one of them is for port 22.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059872/+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 1847088] Re: Cups appends extra page with %EndDocument %%EOF to every print

2024-03-31 Thread Fred Richardson
I'm having this same problem with a different distro - it's the
raspberrypi "bookworm" distro.  Everything works fine except that I get
these extra pages with "%%EndDocument" carriage return, a bunch of
whitespace and then "%%EOF".  I take it this is a cups issue?  Or maybe
it is a specific problem with my Xerox Phaser driver?

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

Title:
  Cups appends extra page with %EndDocument %%EOF to every print

Status in cups package in Ubuntu:
  New

Bug description:
  I am using cups with a printer connected via samba. The Printer is a
  Kyocera Taskalfa 5021ci. Every print I make through cups results in a
  last page with only

  %%EndDocument
  %%EOF

  on it. I've tried to debug this further and if I print with smbclient
  directly like this:

  $smbclient -W DOMAIN -U USER //server/printer
  Unable to initialize messaging context
  Enter NET.CHALMERS.SE\jochens's password: 
  Try "help" to get a list of possible commands.
  smb: \> print test.pdf
  putting file test.pdf as test.pdf (1947.9 kb/s) (average 1947.9 kb/s)
  smb: \> 

  it works without the extra page. I've tried to find the filter that
  adds the extra page but can not find it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1847088/+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 1951555] Re: python3-opencv / libgdal28 can not be used due to undefined dependencies related to libdap

2024-03-31 Thread Sudip Mukherjee
Thanks for reporting the bug. I tried to reproduce the issue on latest
Jammy and the error was not seen.

I checked the version of libgdal is libgdal30 v3.4.1+dfsg-1build4.
Can you please check and confirm if the issue is still seen. I am marking the 
bug as Incomplete, please mark it as New while replying.

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

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

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

Title:
  python3-opencv / libgdal28 can not be used due to undefined
  dependencies related to libdap

Status in gdal package in Ubuntu:
  Incomplete
Status in opencv package in Ubuntu:
  Incomplete

Bug description:
  Importing the python binding of opencv fails due to undefined symbols
  in libgdal:

  $ python3 -c "import cv2"
  Traceback (most recent call last):
File "", line 1, in 
  ImportError: /lib/libgdal.so.28: undefined symbol: _ZN6libdap5ErrorD1Ev

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgdal28 3.2.2+dfsg-3ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Uname: Linux 5.13.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu73
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov 19 09:47:42 2021
  InstallationDate: Installed on 2021-10-08 (41 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdal
  UpgradeStatus: Upgraded to jammy on 2021-11-08 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdal/+bug/1951555/+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 2059862] Re: Getting dependency error when trying to install vim on noble chroot

2024-03-31 Thread Juozas Pocius
** Summary changed:

- Getting dependency error when trying to install of vim on noble chroot
+ Getting dependency error when trying to install vim on noble chroot

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

Title:
  Getting dependency error when trying to install vim on noble chroot

Status in vim package in Ubuntu:
  New

Bug description:
  I'm getting dependency conflict when trying to install vim in Ubuntu
  noble chroot. The dependency version it wants is older then what is
  available in repositories. Running apt-get install vim fails with
  error as shown below:

  (chroot) $ sudo apt-get install vim
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   vim : Depends: vim-common (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 is 
to be installed
     Depends: vim-runtime (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  Apt-cache policy shows older version of vim available while in
  launchpad the newer version is shown, also the amd64 package version
  2:9.1.0016-1ubuntu6 is missing from repositories, no amd64 deb within
  repository pool directory of repository files

  (chroot) $ apt-cache policy vim
  vim:
    Installed: (none)
    Candidate: 2:9.1.0016-1ubuntu3
    Version table:
   2:9.1.0016-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages

  If vim was installed before, it would be uninstalled by upgrading vim-
  common and vim-runtime

  My sources list file:

  (chroot) $ cat /etc/apt/sources.list
  deb http://archive.ubuntu.com/ubuntu noble main restricted universe multiverse
  deb http://archive.ubuntu.com/ubuntu noble-security main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu noble-updates main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu noble-backports main restricted universe 
multiverse

  Contents of /etc/lsb-release

  (chroot) $ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=24.04
  DISTRIB_CODENAME=noble
  DISTRIB_DESCRIPTION="Ubuntu Noble Numbat (development branch)"

  Host is Ubuntu 22.04 LTS, using schroot 1.6.10 to access Ubuntu Noble
  chroot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2059862/+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 2059862] Re: Getting dependency error when trying to install of vim on noble chroot

2024-03-31 Thread Romwriter Launchpad
noble repositories are currently broken due to security disaster
response, cf. https://ubuntu.com/security/CVE-2024-3094

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2024-3094

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

Title:
  Getting dependency error when trying to install of vim on noble chroot

Status in vim package in Ubuntu:
  New

Bug description:
  I'm getting dependency conflict when trying to install vim in Ubuntu
  noble chroot. The dependency version it wants is older then what is
  available in repositories. Running apt-get install vim fails with
  error as shown below:

  (chroot) $ sudo apt-get install vim
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   vim : Depends: vim-common (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 is 
to be installed
     Depends: vim-runtime (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  Apt-cache policy shows older version of vim available while in
  launchpad the newer version is shown, also the amd64 package version
  2:9.1.0016-1ubuntu6 is missing from repositories, no amd64 deb within
  repository pool directory of repository files

  (chroot) $ apt-cache policy vim
  vim:
    Installed: (none)
    Candidate: 2:9.1.0016-1ubuntu3
    Version table:
   2:9.1.0016-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages

  If vim was installed before, it would be uninstalled by upgrading vim-
  common and vim-runtime

  My sources list file:

  (chroot) $ cat /etc/apt/sources.list
  deb http://archive.ubuntu.com/ubuntu noble main restricted universe multiverse
  deb http://archive.ubuntu.com/ubuntu noble-security main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu noble-updates main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu noble-backports main restricted universe 
multiverse

  Contents of /etc/lsb-release

  (chroot) $ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=24.04
  DISTRIB_CODENAME=noble
  DISTRIB_DESCRIPTION="Ubuntu Noble Numbat (development branch)"

  Host is Ubuntu 22.04 LTS, using schroot 1.6.10 to access Ubuntu Noble
  chroot

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2059862/+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 2059853] Re: apt amd64 2.7.14 is missing on Ubuntu Noble?

2024-03-31 Thread Julian Andres Klode
You may have heard about the xz-utils backdoor, compromised binaries
have been removed and replaced with older ones, and a partial amd64
rebuild is ongoing.

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

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

Title:
  apt amd64 2.7.14 is missing on Ubuntu Noble?

Status in apt package in Ubuntu:
  Invalid

Bug description:
  I can not find the apt amd64 version 2.7.14 on Ubuntu Noble. It seems apt 
only exists for non-amd64 architecture:
  https://packages.ubuntu.com/search?suite=noble=apt
  noble (admin): commandline package manager
  2.7.14: arm64 armhf i386 ppc64el riscv64 s390x

  I can not find any docs stating this. Is it a bug or ?
  Thank you very much.

  Steven

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2059853/+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 2059862] Re: Getting dependency error when trying to install of vim on noble chroot

2024-03-31 Thread Juozas Pocius
** Description changed:

  I'm getting dependency conflict when trying to install vim in Ubuntu
  noble chroot. The dependency version it wants is older then what is
  available in repositories. Running apt-get install vim fails with error
  as shown below:
  
- $ sudo apt-get install vim
+ (chroot) $ sudo apt-get install vim
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:
  
  The following packages have unmet dependencies:
-  vim : Depends: vim-common (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 is 
to be installed
-Depends: vim-runtime (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 
is to be installed
+  vim : Depends: vim-common (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 is 
to be installed
+    Depends: vim-runtime (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 
is to be installed
  E: Unable to correct problems, you have held broken packages.
  
  Apt-cache policy shows older version of vim available while in launchpad
  the newer version is shown, also the amd64 package version
  2:9.1.0016-1ubuntu6 is missing from repositories, no amd64 deb within
  repository pool directory of repository files
  
- $ apt-cache policy vim
+ (chroot) $ apt-cache policy vim
  vim:
-   Installed: (none)
-   Candidate: 2:9.1.0016-1ubuntu3
-   Version table:
-  2:9.1.0016-1ubuntu3 500
- 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
+   Installed: (none)
+   Candidate: 2:9.1.0016-1ubuntu3
+   Version table:
+  2:9.1.0016-1ubuntu3 500
+ 500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages
  
  If vim was installed before, it would be uninstalled by upgrading vim-
  common and vim-runtime
  
  My sources list file:
  
- $ cat /etc/apt/sources.list
+ (chroot) $ cat /etc/apt/sources.list
  deb http://archive.ubuntu.com/ubuntu noble main restricted universe multiverse
  deb http://archive.ubuntu.com/ubuntu noble-security main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu noble-updates main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu noble-backports main restricted universe 
multiverse
  
  Contents of /etc/lsb-release
  
- $ cat /etc/lsb-release 
+ (chroot) $ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=24.04
  DISTRIB_CODENAME=noble
  DISTRIB_DESCRIPTION="Ubuntu Noble Numbat (development branch)"
+ 
+ Host is Ubuntu 22.04 LTS, using schroot 1.6.10 to access Ubuntu Noble
+ chroot

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

Title:
  Getting dependency error when trying to install of vim on noble chroot

Status in vim package in Ubuntu:
  New

Bug description:
  I'm getting dependency conflict when trying to install vim in Ubuntu
  noble chroot. The dependency version it wants is older then what is
  available in repositories. Running apt-get install vim fails with
  error as shown below:

  (chroot) $ sudo apt-get install vim
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   vim : Depends: vim-common (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 is 
to be installed
     Depends: vim-runtime (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  Apt-cache policy shows older version of vim available while in
  launchpad the newer version is shown, also the amd64 package version
  2:9.1.0016-1ubuntu6 is missing from repositories, no amd64 deb within
  repository pool directory of repository files

  (chroot) $ apt-cache policy vim
  vim:
    Installed: (none)
    Candidate: 2:9.1.0016-1ubuntu3
    Version table:
   2:9.1.0016-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages

  If vim was installed before, it would be uninstalled by upgrading vim-
  common and vim-runtime

  My sources list file:

  (chroot) $ cat /etc/apt/sources.list
  deb http://archive.ubuntu.com/ubuntu noble main restricted universe multiverse
  deb http://archive.ubuntu.com/ubuntu noble-security main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu noble-updates main 

[Touch-packages] [Bug 2059862] [NEW] Getting dependency error when trying to install of vim on noble chroot

2024-03-31 Thread Juozas Pocius
Public bug reported:

I'm getting dependency conflict when trying to install vim in Ubuntu
noble chroot. The dependency version it wants is older then what is
available in repositories. Running apt-get install vim fails with error
as shown below:

(chroot) $ sudo apt-get install vim
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 vim : Depends: vim-common (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 is 
to be installed
   Depends: vim-runtime (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 is 
to be installed
E: Unable to correct problems, you have held broken packages.

Apt-cache policy shows older version of vim available while in launchpad
the newer version is shown, also the amd64 package version
2:9.1.0016-1ubuntu6 is missing from repositories, no amd64 deb within
repository pool directory of repository files

(chroot) $ apt-cache policy vim
vim:
  Installed: (none)
  Candidate: 2:9.1.0016-1ubuntu3
  Version table:
 2:9.1.0016-1ubuntu3 500
500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages

If vim was installed before, it would be uninstalled by upgrading vim-
common and vim-runtime

My sources list file:

(chroot) $ cat /etc/apt/sources.list
deb http://archive.ubuntu.com/ubuntu noble main restricted universe multiverse
deb http://archive.ubuntu.com/ubuntu noble-security main restricted universe 
multiverse
deb http://archive.ubuntu.com/ubuntu noble-updates main restricted universe 
multiverse
deb http://archive.ubuntu.com/ubuntu noble-backports main restricted universe 
multiverse

Contents of /etc/lsb-release

(chroot) $ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Ubuntu Noble Numbat (development branch)"

Host is Ubuntu 22.04 LTS, using schroot 1.6.10 to access Ubuntu Noble
chroot

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

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

Title:
  Getting dependency error when trying to install of vim on noble chroot

Status in vim package in Ubuntu:
  New

Bug description:
  I'm getting dependency conflict when trying to install vim in Ubuntu
  noble chroot. The dependency version it wants is older then what is
  available in repositories. Running apt-get install vim fails with
  error as shown below:

  (chroot) $ sudo apt-get install vim
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   vim : Depends: vim-common (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 is 
to be installed
     Depends: vim-runtime (= 2:9.1.0016-1ubuntu3) but 2:9.1.0016-1ubuntu6 
is to be installed
  E: Unable to correct problems, you have held broken packages.

  Apt-cache policy shows older version of vim available while in
  launchpad the newer version is shown, also the amd64 package version
  2:9.1.0016-1ubuntu6 is missing from repositories, no amd64 deb within
  repository pool directory of repository files

  (chroot) $ apt-cache policy vim
  vim:
    Installed: (none)
    Candidate: 2:9.1.0016-1ubuntu3
    Version table:
   2:9.1.0016-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu noble-updates/main amd64 Packages

  If vim was installed before, it would be uninstalled by upgrading vim-
  common and vim-runtime

  My sources list file:

  (chroot) $ cat /etc/apt/sources.list
  deb http://archive.ubuntu.com/ubuntu noble main restricted universe multiverse
  deb http://archive.ubuntu.com/ubuntu noble-security main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu noble-updates main restricted universe 
multiverse
  deb http://archive.ubuntu.com/ubuntu noble-backports main restricted universe 
multiverse

  Contents of /etc/lsb-release

  (chroot) $ cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=24.04
  DISTRIB_CODENAME=noble
  DISTRIB_DESCRIPTION="Ubuntu Noble Numbat (development branch)"

  Host is Ubuntu 22.04 LTS, using schroot 1.6.10 to access Ubuntu Noble
  chroot

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


-- 

[Touch-packages] [Bug 2059859] [NEW] pam_env(sshd:session): deprecated reading of user environment enabled

2024-03-31 Thread Romwriter Launchpad
Public bug reported:

Ubuntu 24.04 / openssh-server/noble-updates 1:9.6p1-3ubuntu3

sshd complains about "deprecated reading of user environment".

This should have been solved upstream, as far as I understand:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018106

Enclosed /etc/pam.d/sshd file is amended according to the debian bug
report.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: openssh-server 1:9.6p1-3ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Sun Mar 31 11:56:25 2024
ProcEnviron:
 LANG=de_DE.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: openssh
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
mtime.conffile..etc.pam.d.sshd: 2024-03-31T11:56:12.949543

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


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

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

Title:
  pam_env(sshd:session): deprecated reading of user environment enabled

Status in openssh package in Ubuntu:
  New

Bug description:
  Ubuntu 24.04 / openssh-server/noble-updates 1:9.6p1-3ubuntu3

  sshd complains about "deprecated reading of user environment".

  This should have been solved upstream, as far as I understand:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1018106

  Enclosed /etc/pam.d/sshd file is amended according to the debian bug
  report.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: openssh-server 1:9.6p1-3ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun Mar 31 11:56:25 2024
  ProcEnviron:
   LANG=de_DE.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  mtime.conffile..etc.pam.d.sshd: 2024-03-31T11:56:12.949543

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2059859/+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 2059856] Re: gdb 10.0 fails to examine any global variables in D programs

2024-03-31 Thread Bug Watch Updater
Launchpad has imported 5 comments from the remote bug at
https://sourceware.org/bugzilla/show_bug.cgi?id=31580.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2024-03-30T00:23:30+00:00 Zixing Liu wrote:

Created attachment 15447
Minimal reproducible example (D source code)

Hi there,

I have discovered a D class type resolution regression since GDB 10 (it
was working properly in GDB 9).

Please find the reproducer in the file attached. You can compile the
source code using either GDC or LDC2 (both can reproduce this issue):

gdc -g -O0 t.d -o t

To reproduce the bug, set the breakpoint to t.d:10 and examine the `i`
global variable (using `p t.i`). GDB will then complain that "'t.i' has
unknown type; cast it to its declared type."

I found a workaround to this problem by using `p (uv*)_D1t1iCQf2uv`, but
obviously, this is non-ideal: the developer may not know the mangled
variable name easily.

Since this looks like a regression, I did a simple `git bisect` that led
me to this commit: https://sourceware.org/git/?p=binutils-
gdb.git;a=commit;h=727b7b1864973c2645a554727afd0eaf1303673a. I am unsure
how demangle changes could affect the type resolution (maybe it's
because GDB got confused about which entity to decode?)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2059856/comments/0


On 2024-03-30T19:30:45+00:00 Tromey-b wrote:

Computing the "physname" decides that the symbol should be named:

(top-gdb) p physname
$37 = 0x2c70490 "_D1t1iCQf2uv"

... which is plainly wrong.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2059856/comments/1


On 2024-03-30T19:36:27+00:00 Tromey-b wrote:

Ok, so while gdb's symbol reader is still really wrong here --
this physname stuff is pretty broken -- the root cause of this
particular bug is also that libiberty does not auto-demangle
D symbols.

You can see this on the command line:

prentzel. c++filt  _D1t1iCQf2uv
_D1t1iCQf2uv
prentzel. c++filt -s dlang  _D1t1iCQf2uv
t.i

To my eye this seems to be an oversight in cplus-dem.c,
where the D code follows some earlier code; but perhaps
the author didn't realize that the reason the Ada
code does not check AUTO_DEMANGLING is that the
Ada encoding isn't unambiguous in the way the D encoding is.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2059856/comments/2


On 2024-03-30T19:49:00+00:00 Tromey-b wrote:

Testing a patch.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2059856/comments/3


On 2024-03-30T20:10:51+00:00 Tromey-b wrote:

https://sourceware.org/pipermail/gdb-patches/2024-March/207686.html

Reply at:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/2059856/comments/4


** Changed in: gdb
   Status: Unknown => Confirmed

** Changed in: gdb
   Importance: Unknown => Medium

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

Title:
  gdb 10.0 fails to examine any global variables in D programs

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  New

Bug description:
  Summary:

   * GDB 10.0 introduced a regression where it cannot inspect any global 
variables in any D programs compiled by any D compiler.
   * LDC2 and GDC upstream stated Focal does not have such a problem and stuck 
to this release for their test images.

  Reproduce steps:

  Considering the following D program:

  ```
  module t;

  class uv {
  int i;
  }

  __gshared uv i;
  int main() {
  i = new uv();
  return 0; // #break
  }
  ```

  If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`,
  run the GDB using the following commands ...

  ```
  b t.d:10
  p t.i
  ```

  ... you will notice GDB will complain that "'t.i' has unknown type;
  cast it to its declared type."

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2059856/+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 2059856] [NEW] gdb 10.0 fails to examine any global variables in D programs

2024-03-31 Thread Zixing Liu
Public bug reported:

Summary:

 * GDB 10.0 introduced a regression where it cannot inspect any global 
variables in any D programs compiled by any D compiler.
 * LDC2 and GDC upstream stated Focal does not have such a problem and stuck to 
this release for their test images.

Reproduce steps:

Considering the following D program:

```
module t;

class uv {
int i;
}

__gshared uv i;
int main() {
i = new uv();
return 0; // #break
}
```

If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`, run
the GDB using the following commands ...

```
b t.d:10
p t.i
```

... you will notice GDB will complain that "'t.i' has unknown type; cast
it to its declared type."

** Affects: gdb
 Importance: Medium
 Status: Confirmed

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

** Bug watch added: Sourceware.org Bugzilla #31580
   https://sourceware.org/bugzilla/show_bug.cgi?id=31580

** Also affects: gdb via
   https://sourceware.org/bugzilla/show_bug.cgi?id=31580
   Importance: Unknown
   Status: Unknown

** Changed in: gdb (Ubuntu)
Milestone: None => jammy-updates

** Summary changed:

- gdb 12.1 fails to examine any global variables in D programs
+ gdb 10.0 fails to examine any global variables in D programs

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

Title:
  gdb 10.0 fails to examine any global variables in D programs

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  New

Bug description:
  Summary:

   * GDB 10.0 introduced a regression where it cannot inspect any global 
variables in any D programs compiled by any D compiler.
   * LDC2 and GDC upstream stated Focal does not have such a problem and stuck 
to this release for their test images.

  Reproduce steps:

  Considering the following D program:

  ```
  module t;

  class uv {
  int i;
  }

  __gshared uv i;
  int main() {
  i = new uv();
  return 0; // #break
  }
  ```

  If you build it using `gdc -g -O0 t.d -o t` or `ldc2 -o t.o t.d -g`,
  run the GDB using the following commands ...

  ```
  b t.d:10
  p t.i
  ```

  ... you will notice GDB will complain that "'t.i' has unknown type;
  cast it to its declared type."

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2059856/+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 2059417] Re: Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

2024-03-31 Thread Adrien Nader
** Description changed:

+ NOTE: THIS IS AN ATTEMPT AT INCLUDING A BACKDOOR. THIS IS LEFT FOR
+ HISTORICAL PURPOSES ONLY AND MUST NOT BE DONE.
+ 
+ 
  Please sync xz-utils 5.6.1-1 (main) from Debian unstable (main)
  
  Hello! I am one of the upstream maintainers for XZ Utils. Version 5.6.1
  was recently released and uploaded to Debian as a bugfix only release.
  Notably, this fixes a bug that causes Valgrind to issue a warning on
  any application dynamically linked with liblzma. This includes a lot of
  important applications. This could break build scripts and test
  pipelines that expect specific output from Valgrind in order to pass.
  
  Additionally, this fixes a small typo for the man pages translations
  for Brazilian Portuguese, German, French, Korean, Romanian, and
  Ukrainian, and removes the need for patches applied for version
  5.6.0-0.2.
  
  The other bugfixes in this release have no impact on Ubuntu. They
  involve building with CMake or when building on a system without
  Landlock system calls defined (these are defined in Ubuntu).
  
  Changelog entries since current noble version 5.6.0-0.2:
  
  xz-utils (5.6.1-1) unstable; urgency=medium
  
    * Non-maintainer upload.
    * Import 5.6.1 (Closes: #1067708).
    * Takeover maintenance of the package.
  
   -- Sebastian Andrzej Siewior   Wed, 27 Mar
  2024 22:53:21 +0100
  
- 
  Excerpt from the NEWS entry from upstream:
  
  5.6.1 (2024-03-09)
  
- * liblzma: Fixed two bugs relating to GNU indirect function (IFUNC)
-   with GCC. The more serious bug caused a program linked with
-   liblzma to crash on start up if the flag -fprofile-generate was
-   used to build liblzma. The second bug caused liblzma to falsely
-   report an invalid write to Valgrind when loading liblzma.
+ * liblzma: Fixed two bugs relating to GNU indirect function (IFUNC)
+   with GCC. The more serious bug caused a program linked with
+   liblzma to crash on start up if the flag -fprofile-generate was
+   used to build liblzma. The second bug caused liblzma to falsely
+   report an invalid write to Valgrind when loading liblzma.
  
- * xz: Changed the messages for thread reduction due to memory
-   constraints to only appear under the highest verbosity level.
+ * xz: Changed the messages for thread reduction due to memory
+   constraints to only appear under the highest verbosity level.
  
- * Build:
+ * Build:
  
- - Fixed a build issue when the header file 
-   was present on the system but the Landlock system calls were
-   not defined in .
+ - Fixed a build issue when the header file 
+   was present on the system but the Landlock system calls were
+   not defined in .
  
- - The CMake build now warns and disables NLS if both gettext
-   tools and pre-created .gmo files are missing. Previously,
-   this caused the CMake build to fail.
+ - The CMake build now warns and disables NLS if both gettext
+   tools and pre-created .gmo files are missing. Previously,
+   this caused the CMake build to fail.
  
- * Minor improvements to man pages.
+ * Minor improvements to man pages.
  
- * Minor improvements to tests.
+ * Minor improvements to tests.

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

Title:
  Sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

Status in xz-utils package in Ubuntu:
  Won't Fix

Bug description:
  NOTE: THIS IS AN ATTEMPT AT INCLUDING A BACKDOOR. THIS IS LEFT FOR
  HISTORICAL PURPOSES ONLY AND MUST NOT BE DONE.

  
  Please sync xz-utils 5.6.1-1 (main) from Debian unstable (main)

  Hello! I am one of the upstream maintainers for XZ Utils. Version 5.6.1
  was recently released and uploaded to Debian as a bugfix only release.
  Notably, this fixes a bug that causes Valgrind to issue a warning on
  any application dynamically linked with liblzma. This includes a lot of
  important applications. This could break build scripts and test
  pipelines that expect specific output from Valgrind in order to pass.

  Additionally, this fixes a small typo for the man pages translations
  for Brazilian Portuguese, German, French, Korean, Romanian, and
  Ukrainian, and removes the need for patches applied for version
  5.6.0-0.2.

  The other bugfixes in this release have no impact on Ubuntu. They
  involve building with CMake or when building on a system without
  Landlock system calls defined (these are defined in Ubuntu).

  Changelog entries since current noble version 5.6.0-0.2:

  xz-utils (5.6.1-1) unstable; urgency=medium

    * Non-maintainer upload.
    * Import 5.6.1 (Closes: #1067708).
    * Takeover maintenance of the package.

   -- Sebastian Andrzej Siewior   Wed, 27 Mar
  2024 22:53:21 +0100

  Excerpt from the NEWS entry from