[Touch-packages] [Bug 2053165] Re: [noble] Version 2.7.5 causes software-properties to crash

2024-02-22 Thread liufuling2402
*** This bug is a duplicate of bug 2053228 ***
https://bugs.launchpad.net/bugs/2053228

请问什么时候能修复,我也遇到了这个问题。

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

Title:
  [noble] Version 2.7.5 causes software-properties to crash

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  Only since recent 2.7.5 update along with 0.99.42 for software-properties.
  Crash on start-up.

  $ software-properties-gtk 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)

^^^
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 163, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir,
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
109, in __init__
  self.backup_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
437, in backup_sourceslist
  source_bkp = SourceEntry(line=source.line,file=source.file)
   ^^
File "/usr/lib/python3/dist-packages/aptsources/sourceslist.py", line 509, 
in __init__
  raise ValueError("Classic SourceEntry cannot be written to .sources file")
  ValueError: Classic SourceEntry cannot be written to .sources file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/2053165/+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 1958019]

2024-02-22 Thread kernel
(In reply to Cameron Berkenpas from comment #832)
> The strong beep suggests you might have the older firmware.
> 
> If you have the old firmware, you might also notice your sound for your 
> left and right speakers are swapped.

The speakers are not swapped but how can I check the current version and
update these firmwares?

I moved the firmwares from https://neo-
zeon.de/~hiryu/tas/firmware-6.6.tar.bz2 to /usr/lib/firmware, so not
sure if this affected something.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread kernel
(In reply to Gergo K from comment #840)
> There is an ID collision.
> 
> Your audio controller's PCI SSID (17aa:3802) is the same as the "Lenovo Yoga
> DuetITL 2021" Codec SSID. The snd_hda_pick_fixup() function searches the PCI
> SSID before the Codec SSID in the same table. So it picks the
> ALC287_FIXUP_YOGA7_14ITL_SPEAKERS fixup not the ALC287_FIXUP_TAS2781_I2C.
> 
> 
> !!PCI Soundcards installed in the system
> !!--
> 
> 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device
> [8086:51cf] (rev 01)
>   Subsystem: Lenovo Device [17aa:3802]
> 
> I think a common fixup can be figured out, or a better solution from someone
> who knows this subsystem well.

Hm I see, not sure if this is the right place to talk about the code,
but is there a reason for the fixup table to be the same for PCI and
Codec SSIDs? (I know it's not like it could be separated at this point).
Also, is there a reason to match by PCI before Codec? A few ideas I was
thinking:

1. Just check if the PCI and Codec SSID match the exact SSIDs of this device - 
not elegant
2. For every lookup, check with both PCI and Codec SSID and see if they match 
the same entry, add a debug to these cases and use the Codec entry - not sure 
how common this is and if this will break other cases

Depending on how hard this problem is I may want to help with the code
if possible.

(sorry for the dupe, I pressed the save changes by mistake before)

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread kernel
(In reply to Gergo K from comment #840)
> There is an ID collision.
> 
> Your audio controller's PCI SSID (17aa:3802) is the same as the "Lenovo Yoga
> DuetITL 2021" Codec SSID. The snd_hda_pick_fixup() function searches the PCI
> SSID before the Codec SSID in the same table. So it picks the
> ALC287_FIXUP_YOGA7_14ITL_SPEAKERS fixup not the ALC287_FIXUP_TAS2781_I2C.
> 
> 
> !!PCI Soundcards installed in the system
> !!--
> 
> 00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device
> [8086:51cf] (rev 01)
>   Subsystem: Lenovo Device [17aa:3802]
> 
> I think a common fixup can be figured out, or a better solution from someone
> who knows this subsystem well.

Hm I see, not sure if this is the right place to talk about the code,
but is there a reason for the fixup table to be the same for PCI and
Codec SSIDs? (I know it's not like it could be separated at this point).
Also, is there a reason to match by PCI before Codec? A few ideas I
thought:

1. Just check if the PCI and Codec SSID match the exact SSIDs of this device 
(not elegant)
2. For every lookup, check with both

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread soyer
There is an ID collision.

Your audio controller's PCI SSID (17aa:3802) is the same as the "Lenovo
Yoga DuetITL 2021" Codec SSID. The snd_hda_pick_fixup() function
searches the PCI SSID before the Codec SSID in the same table. So it
picks the ALC287_FIXUP_YOGA7_14ITL_SPEAKERS fixup not the
ALC287_FIXUP_TAS2781_I2C.


!!PCI Soundcards installed in the system
!!--

00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device 
[8086:51cf] (rev 01)
Subsystem: Lenovo Device [17aa:3802]

I think a common fixup can be figured out, or a better solution from
someone who knows this subsystem well.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread kernel
(In reply to Gergo K from comment #836)
> Could you please comment out this line from patch_realtek.c and rebuild the
> kernel and start it without the module parameters?
> 
>   SND_PCI_QUIRK(0x17aa, 0x3802, "Lenovo Yoga DuetITL 2021",
> ALC287_FIXUP_YOGA7_14ITL_SPEAKERS),


http://alsa-project.org/db/?f=8d9465f9d22c4efdc3655373f1d32416516afacd

Yeah, it works! I'm curious what was the issue, can you give an overview
of it?



(In reply to Cameron Berkenpas from comment #838)
> Sounds like I should try this new firmware...
> 
> 
> kernel-firmware... Is that the repo?

https://gitlab.com/kernel-firmware/linux-firmware

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread cam
Sounds like I should try this new firmware...


kernel-firmware... Is that the repo?

On 2/22/24 6:56 PM, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #837 from Willian (ker...@willian.wang) ---
> (In reply to Cameron Berkenpas from comment #834)
>> Then that's the latest firmware as far as I know (that's my server lol).
>>
>> Not sure why you're getting the beep then.
> Oh, didn't know the server was yours, thank you lol. Unfortunately, the
> firmwares are not up to date compared to kernel-firmwares. Specifically the
> files TAS2XXX3881.bin, TAS2XXX38CB.bin, TAS2XXX38CD.bin, TIAS2781RCA2.bin.
>
> Updating the firmwares fixed the loud beep (which also sounds like something
> really broken) and my bass is much better than before. As a very subject
> comparison, the working bass at low volume makes my table shake a little, the
> old firmware sounds flat and doesn't move anything even at the highest
> volume.
> Windows is still a little better but probably because of the tuning than
> anything else.
>
> I tested the new firmware without the module parameter just in case it also
> fixes that, but it still doesn't work without it.
>
>
> (In reply to Gergo K from comment #836)
>> Could you please comment out this line from patch_realtek.c and rebuild the
>> kernel and start it without the module parameters?
>>
>>SND_PCI_QUIRK(0x17aa, 0x3802, "Lenovo Yoga DuetITL 2021",
>> ALC287_FIXUP_YOGA7_14ITL_SPEAKERS),
> I will test it right now.
>

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread kernel
(In reply to Cameron Berkenpas from comment #834)
> Then that's the latest firmware as far as I know (that's my server lol).
> 
> Not sure why you're getting the beep then.

Oh, didn't know the server was yours, thank you lol. Unfortunately, the
firmwares are not up to date compared to kernel-firmwares. Specifically
the files TAS2XXX3881.bin, TAS2XXX38CB.bin, TAS2XXX38CD.bin,
TIAS2781RCA2.bin.

Updating the firmwares fixed the loud beep (which also sounds like
something really broken) and my bass is much better than before. As a
very subject comparison, the working bass at low volume makes my table
shake a little, the old firmware sounds flat and doesn't move anything
even at the highest volume. Windows is still a little better but
probably because of the tuning than anything else.

I tested the new firmware without the module parameter just in case it
also fixes that, but it still doesn't work without it.


(In reply to Gergo K from comment #836)
> Could you please comment out this line from patch_realtek.c and rebuild the
> kernel and start it without the module parameters?
> 
>   SND_PCI_QUIRK(0x17aa, 0x3802, "Lenovo Yoga DuetITL 2021",
> ALC287_FIXUP_YOGA7_14ITL_SPEAKERS),

I will test it right now.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread soyer
Could you please comment out this line from patch_realtek.c and rebuild
the kernel and start it without the module parameters?

SND_PCI_QUIRK(0x17aa, 0x3802, "Lenovo Yoga DuetITL 2021",
ALC287_FIXUP_YOGA7_14ITL_SPEAKERS),

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread soyer
The latest firmware is probably in the linux-firmware package.
Do you still hear a difference when you disable Dolby in Windows?
Do you hear the beep after hibernation also?

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread cam
Then that's the latest firmware as far as I know (that's my server lol).

Not sure why you're getting the beep then.

On 2/22/24 13:31, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #833 from Willian (ker...@willian.wang) ---
> (In reply to Cameron Berkenpas from comment #832)
>> The strong beep suggests you might have the older firmware.
>>
>> If you have the old firmware, you might also notice your sound for your
>> left and right speakers are swapped.
> The speakers are not swapped but how can I check the current version and
> update
> these firmwares?
>
> I moved the firmwares from
> https://neo-zeon.de/~hiryu/tas/firmware-6.6.tar.bz2
> to /usr/lib/firmware, so not sure if this affected something.
>

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread cam
The strong beep suggests you might have the older firmware.

If you have the old firmware, you might also notice your sound for your 
left and right speakers are swapped.

On 2/22/24 12:06, bugzilla-dae...@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=208555
>
> --- Comment #831 from Willian (ker...@willian.wang) ---
> =(In reply to Gergo K from comment #830)
>> I don't know why it won't pick up your model.
>> Could you please run alsa-info after the patch and without the module
>> parameter?
> Yeah, I have no idea, I decided to use specifically the model of my speaker
> through trial and error.
> http://alsa-project.org/db/?f=93ba55541edee13c680039a8c00ff85930f37ad8
>
>
> I don't know how but the bass on Windows is still much better and I always
> hear
> a strong beep from both speakers when I get past the sddm lock screen when I
> turn on the laptop.
>

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread soyer
I don't know why it won't pick up your model.
Could you please run alsa-info after the patch and without the module parameter?

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread kernel
=(In reply to Gergo K from comment #830)
> I don't know why it won't pick up your model.
> Could you please run alsa-info after the patch and without the module
> parameter?

Yeah, I have no idea, I decided to use specifically the model of my speaker 
through trial and error.
http://alsa-project.org/db/?f=93ba55541edee13c680039a8c00ff85930f37ad8


I don't know how but the bass on Windows is still much better and I always hear 
a strong beep from both speakers when I get past the sddm lock screen when I 
turn on the laptop.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread kernel
(In reply to Gergo K from comment #828)
> Great to hear!
> I can create a patch, and it can be included in 6.6 and 6.7.
> 
> Can you test whether the headset jack works also?
> 
> And could you run alsa-info.sh? I think your model needs to be added to the
> patch_realtek.c to make it work without the module parameters.

I can confirm that headset jack works perfectly with this patch. With
6.7 it didn't even detect the headset plugged (didn't test it on 6.8
without the patch).

Here is the alsa-info after the patch: http://alsa-
project.org/db/?f=4bdd25202b2329c03bef10d0f6f0b4781987aa49

Thank you for your attention!

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread soyer
Great to hear!
I can create a patch, and it can be included in 6.6 and 6.7.

Can you test whether the headset jack works also?

And could you run alsa-info.sh? I think your model needs to be added to
the patch_realtek.c to make it work without the module parameters.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread kernel
(In reply to Gergo K from comment #826)
> Could someone please test if changing this fixup in the
> sound/pci/hda/patch_realtek.c fixes the volume control?
> 
>   [ALC287_FIXUP_TAS2781_I2C] = {
>   .type = HDA_FIXUP_FUNC,
>   .v.func = tas2781_fixup_i2c,
>   .chained = true,
>   .chain_id = ALC269_FIXUP_THINKPAD_ACPI,
>   },
> 
> to this:
> 
>   [ALC287_FIXUP_TAS2781_I2C] = {
>   .type = HDA_FIXUP_FUNC,
>   .v.func = tas2781_fixup_i2c,
>   .chained = true,
>   .chain_id = ALC285_FIXUP_THINKPAD_HEADSET_JACK,
>   },
> 
> It worked for ALC287_FIXUP_YOGA7_14ARB7_I2C.

Just tried it and it indeed works, nice! Do you know if this will be
merged soon (hopefully before 6.8 release)?

It still requires `options snd-sof-intel-hda-common hda_model=17aa:38be`
(doing nothing or using `hda_model=alc287-yoga9-bass-spk-pin` doesn't
work). But now I can control the volume using the default "Play HiFi
quality Music" without janky work around.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread soyer
Could someone please test if changing this fixup in the
sound/pci/hda/patch_realtek.c fixes the volume control?

[ALC287_FIXUP_TAS2781_I2C] = {
.type = HDA_FIXUP_FUNC,
.v.func = tas2781_fixup_i2c,
.chained = true,
.chain_id = ALC269_FIXUP_THINKPAD_ACPI,
},

to this:

[ALC287_FIXUP_TAS2781_I2C] = {
.type = HDA_FIXUP_FUNC,
.v.func = tas2781_fixup_i2c,
.chained = true,
.chain_id = ALC285_FIXUP_THINKPAD_HEADSET_JACK,
},

It worked for ALC287_FIXUP_YOGA7_14ARB7_I2C.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]

2024-02-22 Thread thornley.david
I do now :) You're right the hda_model=17aa:38be definitely forces the
tas driver to load properly (it is in dmesg) and the firmware link
seemed to fix a NULL error when I first tried it.

[5.770034] snd_hda_codec_realtek ehdaudio0D0: bound i2c-TIAS2781:00
(ops tas2781_hda_comp_ops [snd_hda_scodec_tas2781_i2c])


I tried both 6.8.0-rc5 and then fell back to 6.7.5 because in both of these the 
volume control didn't work at all (seems to be at full volume), even in 
"alsamixer -c 1". Note that originally, the sound was low/quiet but volume 
control did work.

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2054771] Re: mount root error with kernel 6.5.0.21

2024-02-22 Thread atactic
** Attachment added: "boot error"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2054771/+attachment/5748652/+files/IMG-20240223-WA0006.jpg

** Summary changed:

- mount root error with kernel 6.5.0.21
+ Kernel panic boot error with kernel 6.5.0.21

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

Title:
  Kernel panic boot error with kernel 6.5.0.21

Status in network-manager package in Ubuntu:
  New

Bug description:
  Booting on kernel 6.5.0.21-generic returns error:

  'Unable to mount root fs on unknown-block(0.0)'

  The system starts up correctly with the previous kernel
  6.7.0.17-generic

  Trying fixing 6.5.0.21-generic does not work:

  
  $ update-initramfs -u -k 6.5.0.21-generic
  update-initramfs: Generating /boot/initrd.img-6.5.0.21-generic
  touch: cannot touch '/boot/initrd.img-6.5.0.21-generic.new': Permission denied
  W: Kernel configuration /boot/config-6.5.0.21-generic is missing, cannot 
check for zstd compression support (CONFIG_RD_ZSTD)
  W: missing /lib/modules/6.5.0.21-generic
  W: Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/6.5.0.21-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  cat: 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic/modules.builtin: No 
such file or directory
  W: Can't find modules.builtin.modinfo (for locating built-in drivers' 
firmware, supported in Linux >=5.2)
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  I: The initramfs will attempt to resume from /dev/dm-2
  I: (UUID=ae16e50c-6748-4c2f-877f-b084acd65a51)
  I: Set the RESUME variable to override this.
  cp: cannot access '/etc/lvm/backup': Permission denied
  depmod: WARNING: could not open modules.order at 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or 
directory
  depmod: WARNING: could not open modules.builtin at 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or 
directory
  depmod: WARNING: could not open modules.builtin.modinfo at 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or 
directory
  /usr/sbin/mkinitramfs: 539: cannot create 
/boot/initrd.img-6.5.0.21-generic.new: Permission denied
  update-initramfs: failed for /boot/initrd.img-6.5.0.21-generic with 2.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2054771/+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 2054771] [NEW] Kernel panic boot error with kernel 6.5.0.21

2024-02-22 Thread atactic
Public bug reported:

Booting on kernel 6.5.0.21-generic returns error:

'Unable to mount root fs on unknown-block(0.0)'

The system starts up correctly with the previous kernel 6.7.0.17-generic

Trying fixing 6.5.0.21-generic does not work:


$ update-initramfs -u -k 6.5.0.21-generic
update-initramfs: Generating /boot/initrd.img-6.5.0.21-generic
touch: cannot touch '/boot/initrd.img-6.5.0.21-generic.new': Permission denied
W: Kernel configuration /boot/config-6.5.0.21-generic is missing, cannot check 
for zstd compression support (CONFIG_RD_ZSTD)
W: missing /lib/modules/6.5.0.21-generic
W: Ensure all necessary drivers are built into the linux image!
depmod: ERROR: could not open directory /lib/modules/6.5.0.21-generic: No such 
file or directory
depmod: FATAL: could not search modules: No such file or directory
cat: /var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic/modules.builtin: 
No such file or directory
W: Can't find modules.builtin.modinfo (for locating built-in drivers' firmware, 
supported in Linux >=5.2)
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
Command failed.
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
Command failed.
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
Command failed.
/dev/mapper/control: open failed: Permission denied
Failure to communicate with kernel device-mapper driver.
Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
Command failed.
I: The initramfs will attempt to resume from /dev/dm-2
I: (UUID=ae16e50c-6748-4c2f-877f-b084acd65a51)
I: Set the RESUME variable to override this.
cp: cannot access '/etc/lvm/backup': Permission denied
depmod: WARNING: could not open modules.order at 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or 
directory
depmod: WARNING: could not open modules.builtin at 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or 
directory
depmod: WARNING: could not open modules.builtin.modinfo at 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic: No such file or 
directory
/usr/sbin/mkinitramfs: 539: cannot create 
/boot/initrd.img-6.5.0.21-generic.new: Permission denied
update-initramfs: failed for /boot/initrd.img-6.5.0.21-generic with 2.

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "boot error"
   
https://bugs.launchpad.net/bugs/2054771/+attachment/5748651/+files/IMG_20240223_065906.jpg

** Attachment removed: "boot error"
   
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2054771/+attachment/5748651/+files/IMG_20240223_065906.jpg

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

Title:
  Kernel panic boot error with kernel 6.5.0.21

Status in network-manager package in Ubuntu:
  New

Bug description:
  Booting on kernel 6.5.0.21-generic returns error:

  'Unable to mount root fs on unknown-block(0.0)'

  The system starts up correctly with the previous kernel
  6.7.0.17-generic

  Trying fixing 6.5.0.21-generic does not work:

  
  $ update-initramfs -u -k 6.5.0.21-generic
  update-initramfs: Generating /boot/initrd.img-6.5.0.21-generic
  touch: cannot touch '/boot/initrd.img-6.5.0.21-generic.new': Permission denied
  W: Kernel configuration /boot/config-6.5.0.21-generic is missing, cannot 
check for zstd compression support (CONFIG_RD_ZSTD)
  W: missing /lib/modules/6.5.0.21-generic
  W: Ensure all necessary drivers are built into the linux image!
  depmod: ERROR: could not open directory /lib/modules/6.5.0.21-generic: No 
such file or directory
  depmod: FATAL: could not search modules: No such file or directory
  cat: 
/var/tmp/mkinitramfs_uR0VlQ/lib/modules/6.5.0.21-generic/modules.builtin: No 
such file or directory
  W: Can't find modules.builtin.modinfo (for locating built-in drivers' 
firmware, supported in Linux >=5.2)
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 (2022-05-18) and kernel driver (unknown 
version).
  Command failed.
  /dev/mapper/control: open failed: Permission denied
  Failure to communicate with kernel device-mapper driver.
  Incompatible libdevmapper 1.02.185 

[Touch-packages] [Bug 2052739] Autopkgtest regression report (tzdata/2024a-0ubuntu0.23.10)

2024-02-22 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted tzdata (2024a-0ubuntu0.23.10) for 
mantic have finished running.
The following regressions have been reported in tests triggered by the package:

astropy/5.3.2-1 (arm64)


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

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

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

Title:
  tzdata 2024a release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  The 2024a release contains the following changes:

  * Kazakhstan unifies on UTC+5 beginning 2024-03-01.
  * Palestine springs forward a week later after Ramadan.
  * zic no longer pretends to support indefinite-past DST.
  * localtime no longer mishandles Ciudad Juárez in 2422.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2024a
  * python-icu: test_2024a (only for focal and newer)

  So the test plan is to check that the autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+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 2054319] Re: System installed from jammy point release iso cannot upgrade to noble

2024-02-22 Thread Daniel van Vugt
The tracker-extract crash may be bug 1990630 or bug 1962585, because it
looks like both fixes haven't made it into jammy yet. But also this bug
list probably needs some maintenance:
https://bugs.launchpad.net/ubuntu/+source/tracker-miners

The gnome-shell crash is now tracked in bug 2054761.

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

Title:
  System installed from jammy point release iso cannot upgrade to noble

Status in gnome-shell package in Ubuntu:
  New
Status in policykit-1 package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  We have different crashes being encountered. In our auto-upgrade-
  testing, we see gnome-shell crash, however, when testing locally, I
  didn't experience this. @hyask did experience the gnome-shell crash
  though.

  When running an upgrade from jammy to noble in a virsh vm, about
  halfway through the upgrade process my gui dies. I then ran the
  upgrade from a console, to which it revealed that just the gui dies -
  the upgrade process, for me, continues and then laterally fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-release-upgrader-core 1:24.04.7
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu7
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CrashReports:
   640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 
14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash
   600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 
14:34:19.370597600 +:/var/crash/polkitd.0.crash
  Date: Mon Feb 19 14:53:39 2024
  InstallationDate: Installed on 2024-02-19 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: pkexec must be setuid root
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+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 2052739] Autopkgtest regression report (tzdata/2024a-0ubuntu0.22.04)

2024-02-22 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted tzdata (2024a-0ubuntu0.22.04) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

chrony/4.2-2ubuntu2 (s390x)
mtail/3.0.0~rc48-3 (amd64)


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

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

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

Title:
  tzdata 2024a release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  The 2024a release contains the following changes:

  * Kazakhstan unifies on UTC+5 beginning 2024-03-01.
  * Palestine springs forward a week later after Ramadan.
  * zic no longer pretends to support indefinite-past DST.
  * localtime no longer mishandles Ciudad Juárez in 2422.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2024a
  * python-icu: test_2024a (only for focal and newer)

  So the test plan is to check that the autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+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 2054620] Re: libdm returns wrong error code when dm-verity key cannot be found

2024-02-22 Thread Luca Boccassi
** Changed in: lvm2 (Ubuntu Noble)
   Status: New => Confirmed

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

Title:
  libdm returns wrong error code when dm-verity key cannot be found

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 source package in Noble:
  Confirmed

Bug description:
  When libcryptsetup tries to activate a signed dm-verity volume, and
  the key is not in the kernel keyring, libdevicemapper does not return
  the appropriate ENOKEY, so the failure cannot be distinguished from
  other generic issues.

  This is fixed in the lvm2 version 2.03.23 upstream release.

  Please consider backporting this patch for Noble.

  Upstream PR: https://gitlab.com/lvmteam/lvm2/-/merge_requests/3
  Upstream commit: 25ef7a7b1a876f491bd361369423d7309358f6c1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054620/+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 2054742] [NEW] mv on zfs causes out of memory, fixed in 9.2

2024-02-22 Thread Patrick Domack
Public bug reported:

coreutils from 6.0 to 9.2 causes out of memory errors when using zfs due
to recordsize is too large for coreutils to manage.

https://github.com/coreutils/coreutils/commit/6c343a55745a37a1d4d20f39a427170c37044a65

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

** Attachment added: "mv-strace.txt"
   
https://bugs.launchpad.net/bugs/2054742/+attachment/5748591/+files/mv-strace.txt

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

Title:
  mv on zfs causes out of memory, fixed in 9.2

Status in coreutils package in Ubuntu:
  New

Bug description:
  coreutils from 6.0 to 9.2 causes out of memory errors when using zfs
  due to recordsize is too large for coreutils to manage.

  
https://github.com/coreutils/coreutils/commit/6c343a55745a37a1d4d20f39a427170c37044a65

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2054742/+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 2054719] Re: base-files, glibc lockstep migration blocking bug

2024-02-22 Thread Julian Andres Klode
** Tags added: block-proposed

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

Title:
  base-files, glibc lockstep migration blocking bug

Status in base-files package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New

Bug description:
  With the new changes I'm uploading, taken from Helmut's patches on
  Debian bug tracker, base-files will own the /lib64 symlink, and /lib64
  in libc6 will move to /usr/lib64.

  Special care has been taken to not break upgrades: You can upgrade the
  two in any order.

  However, debootstrap requires both packages to be at a matching
  version:

  1. If base-files migrates first, the old libc6 would fail to unpack
  2. If glibc migrates first, and is bootstrapped before base-files, we do not 
end up with the /lib64 symlink at all because debootstrap only *moves* an 
existing /lib64 (which now is no longer present).

  Since upgrades are fine due to having the symlink already, we do not
  want to solve this by introducing dependencies: We could have added
  mutual Depends or Breaks, but they would have required temporarily
  deconfiguring one of the packages to unpack the other on upgrades.

  Hence we'll mark this bug as block-proposed and remove the tag once
  both are ready to land.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054719/+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 2052739] Please test proposed package

2024-02-22 Thread Andreas Hasenack
Hello Benjamin, or anyone else affected,

Accepted tzdata into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2024a-0ubuntu0.20.04 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  tzdata 2024a release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  The 2024a release contains the following changes:

  * Kazakhstan unifies on UTC+5 beginning 2024-03-01.
  * Palestine springs forward a week later after Ramadan.
  * zic no longer pretends to support indefinite-past DST.
  * localtime no longer mishandles Ciudad Juárez in 2422.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2024a
  * python-icu: test_2024a (only for focal and newer)

  So the test plan is to check that the autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+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 2052739] Re: tzdata 2024a release

2024-02-22 Thread Andreas Hasenack
Hello Benjamin, or anyone else affected,

Accepted tzdata into mantic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/tzdata/2024a-0ubuntu0.23.10 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: tzdata (Ubuntu Mantic)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-mantic

** Changed in: tzdata (Ubuntu Jammy)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed-jammy

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

Title:
  tzdata 2024a release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  The 2024a release contains the following changes:

  * Kazakhstan unifies on UTC+5 beginning 2024-03-01.
  * Palestine springs forward a week later after Ramadan.
  * zic no longer pretends to support indefinite-past DST.
  * localtime no longer mishandles Ciudad Juárez in 2422.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2024a
  * python-icu: test_2024a (only for focal and newer)

  So the test plan is to check that the autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+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 2052739] Please test proposed package

2024-02-22 Thread Andreas Hasenack
Hello Benjamin, or anyone else affected,

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

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

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

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

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

** Changed in: tzdata (Ubuntu Focal)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  tzdata 2024a release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Jammy:
  Fix Committed
Status in tzdata source package in Mantic:
  Fix Committed

Bug description:
  [ Impact ]

  The 2024a release contains the following changes:

  * Kazakhstan unifies on UTC+5 beginning 2024-03-01.
  * Palestine springs forward a week later after Ramadan.
  * zic no longer pretends to support indefinite-past DST.
  * localtime no longer mishandles Ciudad Juárez in 2422.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2024a
  * python-icu: test_2024a (only for focal and newer)

  So the test plan is to check that the autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+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 2052739] Re: tzdata 2024a release

2024-02-22 Thread Benjamin Drung
Some time ago, I converted all the manual tests from the SRU
documentation into autopkgtests. For example
https://git.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/tzdata/commit/?id=a70967f356720a37571dd0a301c3c99bea11abc7
implements the python3-icu test mentioned on the SRU documentation.

The python3-icu uses bin:tzdata-icu (or bin:tzdata on older releases).
The python3-icu test is about verifying that python3-icu does not break
after tzdata was updated.

I am also driving the updates for ESM by preparing them for bionic,
xenial, and trusty: https://code.launchpad.net/~ubuntu-core-
dev/ubuntu/+source/tzdata/+git/tzdata

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

Title:
  tzdata 2024a release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Confirmed
Status in tzdata source package in Jammy:
  Confirmed
Status in tzdata source package in Mantic:
  Confirmed

Bug description:
  [ Impact ]

  The 2024a release contains the following changes:

  * Kazakhstan unifies on UTC+5 beginning 2024-03-01.
  * Palestine springs forward a week later after Ramadan.
  * zic no longer pretends to support indefinite-past DST.
  * localtime no longer mishandles Ciudad Juárez in 2422.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2024a
  * python-icu: test_2024a (only for focal and newer)

  So the test plan is to check that the autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+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 2054319] Re: System installed from jammy point release iso cannot upgrade to noble

2024-02-22 Thread Brian Murray
I broke out the policykit failure, with an apport-package bug, into
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716

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

Title:
  System installed from jammy point release iso cannot upgrade to noble

Status in gnome-shell package in Ubuntu:
  New
Status in policykit-1 package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  We have different crashes being encountered. In our auto-upgrade-
  testing, we see gnome-shell crash, however, when testing locally, I
  didn't experience this. @hyask did experience the gnome-shell crash
  though.

  When running an upgrade from jammy to noble in a virsh vm, about
  halfway through the upgrade process my gui dies. I then ran the
  upgrade from a console, to which it revealed that just the gui dies -
  the upgrade process, for me, continues and then laterally fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-release-upgrader-core 1:24.04.7
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu7
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CrashReports:
   640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 
14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash
   600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 
14:34:19.370597600 +:/var/crash/polkitd.0.crash
  Date: Mon Feb 19 14:53:39 2024
  InstallationDate: Installed on 2024-02-19 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: pkexec must be setuid root
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+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 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1

2024-02-22 Thread Brian Murray
** Changed in: policykit-1 (Ubuntu)
Milestone: None => ubuntu-24.04-beta

** Tags added: need-duplicate-check rls-nn-incoming

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

Title:
  package polkitd 124-1 failed to install/upgrade: installed polkitd
  package post-installation script subprocess returned error exit status
  1

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  I was working on recreating bug 2054319 and did so by modifying my
  /etc/apt/sources.list file from jammy to noble and installing polkit
  and all its dependencies.

  bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
linux-modules-extra-6.5.0-14-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 
libzstd1 locales systemd systemd-dev systemd-oomd
systemd-resolved systemd-sysv systemd-timesyncd udev
  Suggested packages:
glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container 
systemd-homed systemd-userdbd systemd-boot
libqrencode4 libtss2-rc0
  Recommended packages:
libnss-nis libnss-nisplus
  The following NEW packages will be installed:
libduktape207 libsystemd-shared systemd-dev systemd-resolved
  The following packages will be upgraded:
gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg 
libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 
libsystemd0 libudev1 libzstd1 locales pkexec
policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev
  26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded.
  Need to get 34.9 MB of archives.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: polkitd 124-1
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Thu Feb 22 08:46:48 2024
  ErrorMessage: installed polkitd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-11-02 (112 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: policykit-1
  Title: package polkitd 124-1 failed to install/upgrade: installed polkitd 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+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 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1

2024-02-22 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package polkitd 124-1 failed to install/upgrade: installed polkitd
  package post-installation script subprocess returned error exit status
  1

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  I was working on recreating bug 2054319 and did so by modifying my
  /etc/apt/sources.list file from jammy to noble and installing polkit
  and all its dependencies.

  bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
linux-modules-extra-6.5.0-14-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 
libzstd1 locales systemd systemd-dev systemd-oomd
systemd-resolved systemd-sysv systemd-timesyncd udev
  Suggested packages:
glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container 
systemd-homed systemd-userdbd systemd-boot
libqrencode4 libtss2-rc0
  Recommended packages:
libnss-nis libnss-nisplus
  The following NEW packages will be installed:
libduktape207 libsystemd-shared systemd-dev systemd-resolved
  The following packages will be upgraded:
gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg 
libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 
libsystemd0 libudev1 libzstd1 locales pkexec
policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev
  26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded.
  Need to get 34.9 MB of archives.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: polkitd 124-1
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Thu Feb 22 08:46:48 2024
  ErrorMessage: installed polkitd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-11-02 (112 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: policykit-1
  Title: package polkitd 124-1 failed to install/upgrade: installed polkitd 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+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 1881504] Re: cross-testing essential packages fails

2024-02-22 Thread Brian Murray
** Tags added: adt-494

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

Title:
  cross-testing essential packages fails

Status in apt package in Ubuntu:
  Won't Fix
Status in autopkgtest package in Ubuntu:
  Confirmed
Status in gzip package in Ubuntu:
  New

Bug description:
  Testing gzip on i386 fails at replacing gzip(:amd64) with gzip:i386.

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-
  groovy/groovy/i386/g/gzip/20200528_195150_89f08@/log.gz

  ...
  autopkgtest [19:51:38]: testing package gzip version 1.10-2ubuntu1
  autopkgtest [19:51:38]: build not needed
  autopkgtest [19:51:38]: test simple-gzip: preparing testbed
  Note, using file '/tmp/autopkgtest.1PbIQv/1-autopkgtest-satdep.dsc' to get 
the build dependencies
  Reading package lists...
  Building dependency tree...
  Reading state information...
  Starting pkgProblemResolver with broken count: 0
  Starting 2 pkgProblemResolver with broken count: 0
  Done
  The following packages will be REMOVED:
gzip
  The following NEW packages will be installed:
build-essential cpp cpp-9 g++ g++-9 gcc gcc-10-base:i386 gcc-9 gcc-9-base
gzip:i386 libasan5 libatomic1 libc-dev-bin libc6:i386 libc6-dev libcc1-0
libcrypt-dev libcrypt1:i386 libgcc-9-dev libgcc-s1:i386 libgomp1 libisl22
libitm1 liblsan0 libmpc3 libquadmath0 libstdc++-9-dev libtsan0 libubsan1
linux-libc-dev
  WARNING: The following essential packages will be removed.
  This should NOT be done unless you know exactly what you are doing!
gzip
  0 upgraded, 30 newly installed, 1 to remove and 0 not upgraded.
  E: Essential packages were removed and -y was used without 
--allow-remove-essential.
  E: Failed to process build dependencies
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1881504/+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 2052739] Re: tzdata 2024a release

2024-02-22 Thread Andreas Hasenack
Finally, the SRU doc also says this: "Uploads should also be made to any
releases supported via ESM."

Are you going to drive that as well?

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

Title:
  tzdata 2024a release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Confirmed
Status in tzdata source package in Jammy:
  Confirmed
Status in tzdata source package in Mantic:
  Confirmed

Bug description:
  [ Impact ]

  The 2024a release contains the following changes:

  * Kazakhstan unifies on UTC+5 beginning 2024-03-01.
  * Palestine springs forward a week later after Ramadan.
  * zic no longer pretends to support indefinite-past DST.
  * localtime no longer mishandles Ciudad Juárez in 2422.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2024a
  * python-icu: test_2024a (only for focal and newer)

  So the test plan is to check that the autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+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 2043393] Re: Report.get_logind_session fails to determine session on cgroup2 systems

2024-02-22 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.28.0-0ubuntu1

---
apport (2.28.0-0ubuntu1) noble; urgency=medium

  * New upstream release
- ui: remove skipping crashes that happened during logout (LP: #2043393)
- setup: set minimum Java release to 8 (LP: #2045705)
- support systemd-coredump as core dump handler (LP: #2048136)
  * Drop patches that were applied upstream
  * Address pylint complaints in patches and package hooks
  * Replace build dependency pkg-config by pkgconf
  * Suggest python3-zstandard in python3-problem-report for read support

 -- Benjamin Drung   Thu, 22 Feb 2024 15:20:00 +0100

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

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

Title:
  Report.get_logind_session fails to determine session on cgroup2
  systems

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

Bug description:
  Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu
  18.04 only cgroup version 1). Report.get_logind_session will fail to
  determine the logind session and always return None if only cgroup2 is
  used.

  get_logind_session searches for cgroup lines with "name=systemd:" and
  then extracts the session from "/session-". This worked in Ubuntu
  16.04 but started failing in 18.04.

  Content of /proc/self/cgroup when printed from a terminal inside a
  Ubuntu desktop session:

  Ubuntu 16.04 (xenial)
  -

  ```
  12:cpuset:/
  11:perf_event:/
  10:pids:/user.slice/user-1000.slice
  9:blkio:/
  8:hugetlb:/
  7:net_cls,net_prio:/
  6:cpu,cpuacct:/
  5:devices:/user.slice
  4:freezer:/
  3:rdma:/
  2:memory:/
  1:name=systemd:/user.slice/user-1000.slice/session-c1.scope
  ```

  Ubuntu 18.04 (bionic)
  -

  ```
  12:freezer:/
  11:net_cls,net_prio:/
  10:memory:/
  9:rdma:/
  8:cpu,cpuacct:/
  7:devices:/user.slice
  6:perf_event:/
  5:cpuset:/
  4:pids:/user.slice/user-1000.slice/user@1000.service
  3:hugetlb:/
  2:blkio:/
  
1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
  0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
  ```

  Ubuntu 20.04 (focal)
  -

  ```
  13:memory:/user.slice/user-1000.slice/user@1000.service
  12:perf_event:/
  11:misc:/
  10:pids:/user.slice/user-1000.slice/user@1000.service
  9:hugetlb:/
  8:cpuset:/
  7:blkio:/
  6:devices:/user.slice
  5:cpu,cpuacct:/
  4:freezer:/
  3:rdma:/
  2:net_cls,net_prio:/
  
1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope
  
0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope
  ```

  Ubuntu 22.04 (jammy)
  -

  ```
  
0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2043393/+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 2045705] Re: FTBFS with default Java 21

2024-02-22 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.28.0-0ubuntu1

---
apport (2.28.0-0ubuntu1) noble; urgency=medium

  * New upstream release
- ui: remove skipping crashes that happened during logout (LP: #2043393)
- setup: set minimum Java release to 8 (LP: #2045705)
- support systemd-coredump as core dump handler (LP: #2048136)
  * Drop patches that were applied upstream
  * Address pylint complaints in patches and package hooks
  * Replace build dependency pkg-config by pkgconf
  * Suggest python3-zstandard in python3-problem-report for read support

 -- Benjamin Drung   Thu, 22 Feb 2024 15:20:00 +0100

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

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

Title:
  FTBFS with default Java 21

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

Bug description:
  Dear Maintainers,

  The package apport ftbfs with default Java 21.
  The relevant part of the build log:
  ---
  running build_java_subdir
  warning: [options] bootstrap class path not set in conjunction with -source 7
  error: Source option 7 is no longer supported. Use 8 or later.
  error: Target option 7 is no longer supported. Use 8 or later.
  Traceback (most recent call last):
File "/<>/setup.py", line 119, in 
  DistUtilsExtra.auto.setup(
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 125, in 
setup
  setuptools.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in 
setup
  return distutils.core.setup(**attrs)
 ^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
  return run_commands(dist)
 ^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
  dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
969, in run_commands
  self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in 
run_command
  super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
  cmd_obj.run()
File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line 
131, in run
  self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 
318, in run_command
  self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in 
run_command
  super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
  cmd_obj.run()
File "/<>/setuptools_apport/java.py", line 35, in run
  subprocess.check_call(javac + glob.glob("com/ubuntu/apport/*.java"))
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['javac', '-source', '7', '-target', 
'7', 'com/ubuntu/apport/ApportUncaughtExceptionHandler.java']' returned 
non-zero exit status 2.
  E: pybuild pybuild:395: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build
  dh_auto_build: error: pybuild --build -i python{version} -p "3.12 3.11" 
returned exit code 13
  make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:4: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  

  Build finished at 2023-12-04T07:37:06Z
  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2045705/+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 2048136] Re: Please support systemd-coredump as core dump handler

2024-02-22 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.28.0-0ubuntu1

---
apport (2.28.0-0ubuntu1) noble; urgency=medium

  * New upstream release
- ui: remove skipping crashes that happened during logout (LP: #2043393)
- setup: set minimum Java release to 8 (LP: #2045705)
- support systemd-coredump as core dump handler (LP: #2048136)
  * Drop patches that were applied upstream
  * Address pylint complaints in patches and package hooks
  * Replace build dependency pkg-config by pkgconf
  * Suggest python3-zstandard in python3-problem-report for read support

 -- Benjamin Drung   Thu, 22 Feb 2024 15:20:00 +0100

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

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

Title:
  Please support systemd-coredump as core dump handler

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

Bug description:
  There can only be one system core dump handler on a Linux system and
  Apport is the Ubuntu default core dump handler. Besides Apport other
  tools offer coredump handler, in particular systemd-coredump. Due to
  Apport being installed on all Ubuntu system by default none of these
  alternate system can be installed.

  There has been some user request for this integration to work. Proper
  integration between Apport and systemd-coredump would offer a better
  experience to developers who want to use systemd-coredump. systemd-
  coredump and coredumpctl provide more documentation and have more
  users upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2048136/+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 2052739] Re: tzdata 2024a release

2024-02-22 Thread Andreas Hasenack
I'm not familiar with this package, so maybe not the best person to
review this SRU, but here is another question. The SRU docs on tzdata
also mention python3-icu, but I don't see an update for that package
here or in the unapproved queue. Is that necessary? Or is it just about
verifying that python3-icu does not break after bin:tzdata-icu was
updated?

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

Title:
  tzdata 2024a release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Confirmed
Status in tzdata source package in Jammy:
  Confirmed
Status in tzdata source package in Mantic:
  Confirmed

Bug description:
  [ Impact ]

  The 2024a release contains the following changes:

  * Kazakhstan unifies on UTC+5 beginning 2024-03-01.
  * Palestine springs forward a week later after Ramadan.
  * zic no longer pretends to support indefinite-past DST.
  * localtime no longer mishandles Ciudad Juárez in 2422.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2024a
  * python-icu: test_2024a (only for focal and newer)

  So the test plan is to check that the autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+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 2052739] Re: tzdata 2024a release

2024-02-22 Thread Andreas Hasenack
The SRU documentation[1] on tzdata describes other, or additional, tests, to be 
performed in this package. Is that:
a) assumed, and will be done?
b) autopkgtests cover it?
c) was forgotten, and should be added to the test plan?


1. https://wiki.ubuntu.com/StableReleaseUpdates#tzdata

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

Title:
  tzdata 2024a release

Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Confirmed
Status in tzdata source package in Jammy:
  Confirmed
Status in tzdata source package in Mantic:
  Confirmed

Bug description:
  [ Impact ]

  The 2024a release contains the following changes:

  * Kazakhstan unifies on UTC+5 beginning 2024-03-01.
  * Palestine springs forward a week later after Ramadan.
  * zic no longer pretends to support indefinite-past DST.
  * localtime no longer mishandles Ciudad Juárez in 2422.

  [ Test Plan ]

  Test cases were added to the autopkgtest to cover the testing:

  * python: test_2024a
  * python-icu: test_2024a (only for focal and newer)

  So the test plan is to check that the autopkgtest succeeds.

  [ Other Info ]

  The autopkgtest for chrony is flaky on jammy and newer (see bug
  #2002910).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2052739/+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 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1

2024-02-22 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package polkitd 124-1 failed to install/upgrade: installed polkitd
  package post-installation script subprocess returned error exit status
  1

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  I was working on recreating bug 2054319 and did so by modifying my
  /etc/apt/sources.list file from jammy to noble and installing polkit
  and all its dependencies.

  bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
linux-modules-extra-6.5.0-14-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 
libzstd1 locales systemd systemd-dev systemd-oomd
systemd-resolved systemd-sysv systemd-timesyncd udev
  Suggested packages:
glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container 
systemd-homed systemd-userdbd systemd-boot
libqrencode4 libtss2-rc0
  Recommended packages:
libnss-nis libnss-nisplus
  The following NEW packages will be installed:
libduktape207 libsystemd-shared systemd-dev systemd-resolved
  The following packages will be upgraded:
gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg 
libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 
libsystemd0 libudev1 libzstd1 locales pkexec
policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev
  26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded.
  Need to get 34.9 MB of archives.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: polkitd 124-1
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Thu Feb 22 08:46:48 2024
  ErrorMessage: installed polkitd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-11-02 (112 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: policykit-1
  Title: package polkitd 124-1 failed to install/upgrade: installed polkitd 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+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 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1

2024-02-22 Thread Brian Murray
** Tags added: cuqa-automated-testing need-duplicate-check

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

Title:
  package polkitd 124-1 failed to install/upgrade: installed polkitd
  package post-installation script subprocess returned error exit status
  1

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  I was working on recreating bug 2054319 and did so by modifying my
  /etc/apt/sources.list file from jammy to noble and installing polkit
  and all its dependencies.

  bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
linux-modules-extra-6.5.0-14-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 
libzstd1 locales systemd systemd-dev systemd-oomd
systemd-resolved systemd-sysv systemd-timesyncd udev
  Suggested packages:
glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container 
systemd-homed systemd-userdbd systemd-boot
libqrencode4 libtss2-rc0
  Recommended packages:
libnss-nis libnss-nisplus
  The following NEW packages will be installed:
libduktape207 libsystemd-shared systemd-dev systemd-resolved
  The following packages will be upgraded:
gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg 
libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 
libsystemd0 libudev1 libzstd1 locales pkexec
policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev
  26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded.
  Need to get 34.9 MB of archives.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: polkitd 124-1
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Thu Feb 22 08:46:48 2024
  ErrorMessage: installed polkitd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-11-02 (112 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: policykit-1
  Title: package polkitd 124-1 failed to install/upgrade: installed polkitd 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+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 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1

2024-02-22 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: policykit-1 (Ubuntu)
   Status: New => Confirmed

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

Title:
  package polkitd 124-1 failed to install/upgrade: installed polkitd
  package post-installation script subprocess returned error exit status
  1

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  I was working on recreating bug 2054319 and did so by modifying my
  /etc/apt/sources.list file from jammy to noble and installing polkit
  and all its dependencies.

  bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
linux-modules-extra-6.5.0-14-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 
libzstd1 locales systemd systemd-dev systemd-oomd
systemd-resolved systemd-sysv systemd-timesyncd udev
  Suggested packages:
glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container 
systemd-homed systemd-userdbd systemd-boot
libqrencode4 libtss2-rc0
  Recommended packages:
libnss-nis libnss-nisplus
  The following NEW packages will be installed:
libduktape207 libsystemd-shared systemd-dev systemd-resolved
  The following packages will be upgraded:
gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg 
libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 
libsystemd0 libudev1 libzstd1 locales pkexec
policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev
  26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded.
  Need to get 34.9 MB of archives.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: polkitd 124-1
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Thu Feb 22 08:46:48 2024
  ErrorMessage: installed polkitd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-11-02 (112 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: policykit-1
  Title: package polkitd 124-1 failed to install/upgrade: installed polkitd 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+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 2054719] [NEW] base-files, glibc lockstep migration blocking bug

2024-02-22 Thread Julian Andres Klode
Public bug reported:

With the new changes I'm uploading, taken from Helmut's patches on
Debian bug tracker, base-files will own the /lib64 symlink, and /lib64
in libc6 will move to /usr/lib64.

Special care has been taken to not break upgrades: You can upgrade the
two in any order.

However, debootstrap requires both packages to be at a matching version:

1. If base-files migrates first, the old libc6 would fail to unpack
2. If glibc migrates first, and is bootstrapped before base-files, we do not 
end up with the /lib64 symlink at all because debootstrap only *moves* an 
existing /lib64 (which now is no longer present).

Since upgrades are fine due to having the symlink already, we do not
want to solve this by introducing dependencies: We could have added
mutual Depends or Breaks, but they would have required temporarily
deconfiguring one of the packages to unpack the other on upgrades.

Hence we'll mark this bug as block-proposed and remove the tag once both
are ready to land.

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

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

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

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

Title:
  base-files, glibc lockstep migration blocking bug

Status in base-files package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New

Bug description:
  With the new changes I'm uploading, taken from Helmut's patches on
  Debian bug tracker, base-files will own the /lib64 symlink, and /lib64
  in libc6 will move to /usr/lib64.

  Special care has been taken to not break upgrades: You can upgrade the
  two in any order.

  However, debootstrap requires both packages to be at a matching
  version:

  1. If base-files migrates first, the old libc6 would fail to unpack
  2. If glibc migrates first, and is bootstrapped before base-files, we do not 
end up with the /lib64 symlink at all because debootstrap only *moves* an 
existing /lib64 (which now is no longer present).

  Since upgrades are fine due to having the symlink already, we do not
  want to solve this by introducing dependencies: We could have added
  mutual Depends or Breaks, but they would have required temporarily
  deconfiguring one of the packages to unpack the other on upgrades.

  Hence we'll mark this bug as block-proposed and remove the tag once
  both are ready to land.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2054719/+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 2054716] Re: package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1

2024-02-22 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package polkitd 124-1 failed to install/upgrade: installed polkitd
  package post-installation script subprocess returned error exit status
  1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  I was working on recreating bug 2054319 and did so by modifying my
  /etc/apt/sources.list file from jammy to noble and installing polkit
  and all its dependencies.

  bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
linux-modules-extra-6.5.0-14-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 
libzstd1 locales systemd systemd-dev systemd-oomd
systemd-resolved systemd-sysv systemd-timesyncd udev
  Suggested packages:
glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container 
systemd-homed systemd-userdbd systemd-boot
libqrencode4 libtss2-rc0
  Recommended packages:
libnss-nis libnss-nisplus
  The following NEW packages will be installed:
libduktape207 libsystemd-shared systemd-dev systemd-resolved
  The following packages will be upgraded:
gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg 
libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin
libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 
libsystemd0 libudev1 libzstd1 locales pkexec
policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev
  26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded.
  Need to get 34.9 MB of archives.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: polkitd 124-1
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckMismatches: ./boot/grub/grub.cfg
  CasperMD5CheckResult: fail
  Date: Thu Feb 22 08:46:48 2024
  ErrorMessage: installed polkitd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-11-02 (112 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.11
  SourcePackage: policykit-1
  Title: package polkitd 124-1 failed to install/upgrade: installed polkitd 
package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/2054716/+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 2054716] [NEW] package polkitd 124-1 failed to install/upgrade: installed polkitd package post-installation script subprocess returned error exit status 1

2024-02-22 Thread Brian Murray
Public bug reported:

I was working on recreating bug 2054319 and did so by modifying my
/etc/apt/sources.list file from jammy to noble and installing polkit and
all its dependencies.

bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
  linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
  linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
  linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
  linux-modules-extra-6.5.0-14-generic
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 libglib2.0-bin
  libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 libzstd1 
locales systemd systemd-dev systemd-oomd
  systemd-resolved systemd-sysv systemd-timesyncd udev
Suggested packages:
  glibc-doc rng-tools low-memory-monitor polkitd-pkla systemd-container 
systemd-homed systemd-userdbd systemd-boot
  libqrencode4 libtss2-rc0
Recommended packages:
  libnss-nis libnss-nisplus
The following NEW packages will be installed:
  libduktape207 libsystemd-shared systemd-dev systemd-resolved
The following packages will be upgraded:
  gir1.2-polkit-1.0 libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg 
libc6-dev libgcrypt20 libglib2.0-0 libglib2.0-bin
  libnss-systemd libpam-systemd libpolkit-agent-1-0 libpolkit-gobject-1-0 
libsystemd0 libudev1 libzstd1 locales pkexec
  policykit-1 polkitd systemd systemd-oomd systemd-sysv systemd-timesyncd udev
26 upgraded, 4 newly installed, 0 to remove and 1407 not upgraded.
Need to get 34.9 MB of archives.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: polkitd 124-1
ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
Date: Thu Feb 22 08:46:48 2024
ErrorMessage: installed polkitd package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2023-11-02 (112 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.11
SourcePackage: policykit-1
Title: package polkitd 124-1 failed to install/upgrade: installed polkitd 
package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy need-duplicate-check third-party-packages

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

Title:
  package polkitd 124-1 failed to install/upgrade: installed polkitd
  package post-installation script subprocess returned error exit status
  1

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  I was working on recreating bug 2054319 and did so by modifying my
  /etc/apt/sources.list file from jammy to noble and installing polkit
  and all its dependencies.

  bdmurray@clean-jammy-amd64:~$ sudo apt-get install gir1.2-polkit-1.0 
libpolkit-agent-1-0:amd64 libpolkit-gobject-1-0:amd64 pkexec policykit-1 polkitd
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
linux-headers-6.2.0-26-generic linux-headers-6.2.0-36-generic 
linux-headers-6.5.0-14-generic
linux-hwe-6.2-headers-6.2.0-26 linux-hwe-6.2-headers-6.2.0-36 
linux-hwe-6.5-headers-6.5.0-14 linux-image-6.2.0-26-generic
linux-image-6.2.0-36-generic linux-image-6.5.0-14-generic 
linux-modules-6.2.0-26-generic linux-modules-6.2.0-36-generic
linux-modules-6.5.0-14-generic linux-modules-extra-6.2.0-26-generic 
linux-modules-extra-6.2.0-36-generic
linux-modules-extra-6.5.0-14-generic
  Use 'sudo apt autoremove' to remove them.
  The following additional packages will be installed:
libc-bin libc-dev-bin libc-devtools libc6 libc6-dbg libc6-dev libduktape207 
libgcrypt20 libglib2.0-0 

[Touch-packages] [Bug 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."

2024-02-22 Thread NetVicious
Same problem here with Ubuntu 22.04.4 LTS in a brand new AWS EC2
directly born as Ubuntu 22.

Setting up proftpd-core (1.3.7c+dfsg-1build1) ...
usermod: no changes
Synchronizing state of proftpd.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable proftpd
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.
dpkg: error processing package proftpd-core (--configure):
 installed proftpd-core package post-installation script subprocess returned 
error exit status 1


I fixed it editing /var/lib/dpkg/info/proftpd-core.postinst and commenting the 
deb-systemd-invoke commands, running the apt install another time and letting 
the postint script as it was after the package was installed correctly.

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

Title:
  Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute
  systemctl:  at /usr/bin/deb-systemd-invoke line 142."

Status in init-system-helpers package in Ubuntu:
  Triaged
Status in krb5 package in Ubuntu:
  Triaged

Bug description:
  I have a fresh install of Ubuntu Server 22.04.01 LTS.  After
  installing the server and running all updates, I run the following
  command:

  apt -y install slapd ldap-utils schema2ldif sasl2-bin
  libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc

  This will be installing krb5-kdc 1.19.2-2.

  This is in preparation for setting up an OpenLDAP server, a Kerberos
  server with an LDAP backend, and saslauthd for pass-through
  authentication.  krb5-kdc was auto-selected when running the steps in
  the guide here in my development environment:
  https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend
  When installing that, I get the following in the output:

  Setting up krb5-kdc (1.19.2-2) ...
  Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service 
→ /lib/systemd/system/krb5-kdc.service.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I do get the prompts for the realm, kdc, and admin server hostnames,
  and they are reflected in /etc/krb5.conf.  If I then run the
  following:

  dpkg-reconfigure krb5-kdc

  I am prompted for whether I want the package to create the Kerberos
  KDC configuration automatically, and when I say yes, it then repeats
  the following error:

  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I cannot find any further debug in the syslog or anything to indicate
  what the root cause is; the list of packages here are all installed
  together on a separate development server where I experimented with
  the configuration I will be deploying here in production so I don't
  think it's incompatible packages in the install list, but I am open to
  feedback on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2054319] Re: System installed from jammy point release iso cannot upgrade to noble

2024-02-22 Thread Julian Andres Klode
** No longer affects: tracker-miners (Ubuntu)

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

Title:
  System installed from jammy point release iso cannot upgrade to noble

Status in gnome-shell package in Ubuntu:
  New
Status in policykit-1 package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  We have different crashes being encountered. In our auto-upgrade-
  testing, we see gnome-shell crash, however, when testing locally, I
  didn't experience this. @hyask did experience the gnome-shell crash
  though.

  When running an upgrade from jammy to noble in a virsh vm, about
  halfway through the upgrade process my gui dies. I then ran the
  upgrade from a console, to which it revealed that just the gui dies -
  the upgrade process, for me, continues and then laterally fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-release-upgrader-core 1:24.04.7
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu7
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CrashReports:
   640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 
14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash
   600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 
14:34:19.370597600 +:/var/crash/polkitd.0.crash
  Date: Mon Feb 19 14:53:39 2024
  InstallationDate: Installed on 2024-02-19 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: pkexec must be setuid root
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+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 2053153] Re: initramfs-tools broken by libpam-tmpdir and /tmp mounted with noexec

2024-02-22 Thread Patrick Schleizer
Changed in initramfs-tools (Debian):
status: Unknown → Fix Released

This is wrong as you can see from the context of the ticket.

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

Title:
  initramfs-tools broken by libpam-tmpdir and /tmp mounted with noexec

Status in initramfs-tools package in Ubuntu:
  New
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  I would like to forward the bug that was reported against Debian
  "certain update-initramfs actions broken on systems with' from
  'cryptsetup-initramfs: cryptkeyctl script fails to discover
  decrypt_keyctl even when present" [1] to upstream initramfs-tools,
  which I think is here.

  To reproduce this bug in Debian:

  1) sudo apt install libpam-tmpdir

  2) Mount /tmp with noexec.

  This breaks the cryptkeyctl hook.

  Could you fix initramfs-tools compatibility with libpam-tmpdir and
  /tmp mounted with noexec please?

  Is there some more appropriate temporary folder for update-initramfs
  to use?

  By comparison, dracut has no such issue.

  [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1062756

  (Disclaimer: I am not affiliated with Debian and writing this on my
  own imitative.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2053153/+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 2054090] Re: Implicit rejection of PKCS#1 v1.5 RSA

2024-02-22 Thread David Fernandez Gonzalez
** Changed in: openssl (Ubuntu Bionic)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: openssl (Ubuntu Focal)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: openssl (Ubuntu Jammy)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: openssl (Ubuntu Mantic)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: openssl (Ubuntu Noble)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: openssl (Ubuntu Xenial)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

** Changed in: openssl (Ubuntu Trusty)
 Assignee: (unassigned) => David Fernandez Gonzalez (litios)

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

Title:
  Implicit rejection of PKCS#1 v1.5 RSA

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Trusty:
  New
Status in openssl source package in Xenial:
  New
Status in openssl source package in Bionic:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Jammy:
  New
Status in openssl source package in Mantic:
  New
Status in openssl source package in Noble:
  New

Bug description:
  OpenSSL 3.2.0 introduced a change on PKCS#1 v1.5 RSA to return random
  output instead of an exception when detecting wrong padding
  (https://github.com/openssl/openssl/pull/13817).

  There are available backports already:

  * 3.0 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c9s/0120-RSA-PKCS15-implicit-
  rejection.patch?ref_type=heads

  * 1.1.1 https://gitlab.com/redhat/centos-
  stream/rpms/openssl/-/blob/c8s/openssl-1.1.1-pkcs1-implicit-
  rejection.patch?ref_type=heads

  
  This change is needed to fix CVE-2023-50782.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2054090/+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 2043393] Re: Report.get_logind_session fails to determine session on cgroup2 systems

2024-02-22 Thread Benjamin Drung
** Changed in: apport (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  Report.get_logind_session fails to determine session on cgroup2
  systems

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu
  18.04 only cgroup version 1). Report.get_logind_session will fail to
  determine the logind session and always return None if only cgroup2 is
  used.

  get_logind_session searches for cgroup lines with "name=systemd:" and
  then extracts the session from "/session-". This worked in Ubuntu
  16.04 but started failing in 18.04.

  Content of /proc/self/cgroup when printed from a terminal inside a
  Ubuntu desktop session:

  Ubuntu 16.04 (xenial)
  -

  ```
  12:cpuset:/
  11:perf_event:/
  10:pids:/user.slice/user-1000.slice
  9:blkio:/
  8:hugetlb:/
  7:net_cls,net_prio:/
  6:cpu,cpuacct:/
  5:devices:/user.slice
  4:freezer:/
  3:rdma:/
  2:memory:/
  1:name=systemd:/user.slice/user-1000.slice/session-c1.scope
  ```

  Ubuntu 18.04 (bionic)
  -

  ```
  12:freezer:/
  11:net_cls,net_prio:/
  10:memory:/
  9:rdma:/
  8:cpu,cpuacct:/
  7:devices:/user.slice
  6:perf_event:/
  5:cpuset:/
  4:pids:/user.slice/user-1000.slice/user@1000.service
  3:hugetlb:/
  2:blkio:/
  
1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
  0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
  ```

  Ubuntu 20.04 (focal)
  -

  ```
  13:memory:/user.slice/user-1000.slice/user@1000.service
  12:perf_event:/
  11:misc:/
  10:pids:/user.slice/user-1000.slice/user@1000.service
  9:hugetlb:/
  8:cpuset:/
  7:blkio:/
  6:devices:/user.slice
  5:cpu,cpuacct:/
  4:freezer:/
  3:rdma:/
  2:net_cls,net_prio:/
  
1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope
  
0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope
  ```

  Ubuntu 22.04 (jammy)
  -

  ```
  
0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2043393/+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 2045705] Re: FTBFS with default Java 21

2024-02-22 Thread Benjamin Drung
** Changed in: apport (Ubuntu)
   Status: Triaged => Fix Committed

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

Title:
  FTBFS with default Java 21

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  Dear Maintainers,

  The package apport ftbfs with default Java 21.
  The relevant part of the build log:
  ---
  running build_java_subdir
  warning: [options] bootstrap class path not set in conjunction with -source 7
  error: Source option 7 is no longer supported. Use 8 or later.
  error: Target option 7 is no longer supported. Use 8 or later.
  Traceback (most recent call last):
File "/<>/setup.py", line 119, in 
  DistUtilsExtra.auto.setup(
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 125, in 
setup
  setuptools.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in 
setup
  return distutils.core.setup(**attrs)
 ^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
  return run_commands(dist)
 ^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
  dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
969, in run_commands
  self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in 
run_command
  super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
  cmd_obj.run()
File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line 
131, in run
  self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 
318, in run_command
  self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in 
run_command
  super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
  cmd_obj.run()
File "/<>/setuptools_apport/java.py", line 35, in run
  subprocess.check_call(javac + glob.glob("com/ubuntu/apport/*.java"))
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['javac', '-source', '7', '-target', 
'7', 'com/ubuntu/apport/ApportUncaughtExceptionHandler.java']' returned 
non-zero exit status 2.
  E: pybuild pybuild:395: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build
  dh_auto_build: error: pybuild --build -i python{version} -p "3.12 3.11" 
returned exit code 13
  make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:4: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  

  Build finished at 2023-12-04T07:37:06Z
  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2045705/+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 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)

2024-02-22 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-meta - 1.532

---
ubuntu-meta (1.532) noble; urgency=medium

  * Refreshed dependencies
  * Removed irqbalance from standard-recommends (LP: #1833322)

 -- Christian Ehrhardt   Thu, 22 Feb
2024 12:37:15 +0100

** Changed in: ubuntu-meta (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Please consider no more having irqbalance enabled by default (per
  image/use-case/TBD)

Status in cloud-images:
  New
Status in Release Notes for Ubuntu:
  In Progress
Status in Ubuntu on IBM z Systems:
  Opinion
Status in irqbalance package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1833322/+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 2044129] Re: ubuntu-bug does not allow for reporting a bug in "other software" manually giving a symptom description

2024-02-22 Thread Benjamin Drung
** Changed in: apport
Milestone: None => 2.28.1

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

Title:
  ubuntu-bug does not allow for reporting a bug in "other software"
  manually giving a symptom description

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  the man page of ubuntu-bug/apport-bug (what is the difference? why am
  I shown the manpage of apport-bug when typing man ubuntu-bug?) says
  running apport-bug without arguments results in showing me a list of
  symptoms.

  When I try to report a bug in some general program that is not related
  to the other 9 categories - which is most of the 1 apps in Ubuntu
  - I must chose "Other Problem" - but in contrary to the man page that
  tells me I am asked about further things, I only get "You need to
  specific the pakacge or PID".

  I currently try to report a bug in the things that identifies itself
  as "Ubuntu Software" in the Dock, but I have no idea what its correct
  program or package name is, and have no idea how to find that. In PS
  there is no process with "ubuntu" or "software" in its name.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu5
  ProcVersionSignature: Ubuntu 6.2.0-1015.15-lowlatency 6.2.16
  Uname: Linux 6.2.0-1015-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 21 14:38:42 2023
  InstallationDate: Installed on 2023-08-21 (92 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apport
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2044129/+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 2038650] Re: crash reports not sent to the Error Tracker

2024-02-22 Thread Benjamin Drung
** Changed in: apport
   Status: Fix Committed => Fix Released

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

Title:
  crash reports not sent to the Error Tracker

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Lunar:
  Fix Released
Status in apport source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  Crash reports aren't sent in when going through the UI, unless the
  user looks at the crash details.

  [ Test Plan ]

  0) Make sure that error reporting is set to manual in the system settings (in 
Privacy screen)
  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog. DO NOT look at the details of the report.
  4) ls -lh /var/crash/*xeyes*

  There should be 3 files:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  [ Where problems could occur ]

  If the patch is wrong, we actually see similar bugs for other UI
  paths, e.g. ticking the "Remember this" box, etc. I tried to cover
  them during manual testing but I might have missed some.

  [ Other Info ]
   
  If possible I'd like for us not to wait too long for this to mature in 
-proposed, as this would affect crashes during the upgrade.

  [ Original report ]
  From what I can tell when I click the send button to send a crash report to 
the Error Tracker the crash doesn't actually get sent. My testing process 
follows:

  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog
  4) ls -lh /var/crash

  I would expect there to be three files in /var/crash:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  However, after step #4 I'm only seeing the .crash file and not a
  .upload or .uploaded.  I was able to get the .upload and .uploaded
  files created if I chose to "View Report" and then click "Send".

  It's worth noting though that I did notice the size of the .crash file
  increase after clicking "Send" so some post-processing was done.

  ProblemType: BugDistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:12:46 2023
  InstallationDate: Installed on 2022-01-07 (637 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2038650/+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 1850804] Re: Tab completion warnings with ubuntu-bug when using alias for ls

2024-02-22 Thread Benjamin Drung
** Changed in: apport
   Status: Fix Committed => Fix Released

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

Title:
  Tab completion warnings with ubuntu-bug when using alias for ls

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

Bug description:
  When running ubuntu-bug on the command line, and tab completing the
  package name, the following warnings are printed:

  /usr/share/apport/symptoms/dist-upgrade.py: No such file or directory
  grep: /usr/share/apport/symptoms/release-upgrade.py: No such file or directory

  This happens when following alias is set:

  alias ls='ls -N --color=yes --time-style=long-iso'

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:

  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Thu Oct 31 10:54:43 2019
  InstallationDate: Installed on 2017-08-16 (805 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-10-04 (26 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1850804/+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 2043393] Re: Report.get_logind_session fails to determine session on cgroup2 systems

2024-02-22 Thread Benjamin Drung
** Changed in: apport
   Status: Fix Committed => Fix Released

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

Title:
  Report.get_logind_session fails to determine session on cgroup2
  systems

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Ubuntu >= 22.04 uses only cgroup2 (Ubuntu 20.04 used both and Ubuntu
  18.04 only cgroup version 1). Report.get_logind_session will fail to
  determine the logind session and always return None if only cgroup2 is
  used.

  get_logind_session searches for cgroup lines with "name=systemd:" and
  then extracts the session from "/session-". This worked in Ubuntu
  16.04 but started failing in 18.04.

  Content of /proc/self/cgroup when printed from a terminal inside a
  Ubuntu desktop session:

  Ubuntu 16.04 (xenial)
  -

  ```
  12:cpuset:/
  11:perf_event:/
  10:pids:/user.slice/user-1000.slice
  9:blkio:/
  8:hugetlb:/
  7:net_cls,net_prio:/
  6:cpu,cpuacct:/
  5:devices:/user.slice
  4:freezer:/
  3:rdma:/
  2:memory:/
  1:name=systemd:/user.slice/user-1000.slice/session-c1.scope
  ```

  Ubuntu 18.04 (bionic)
  -

  ```
  12:freezer:/
  11:net_cls,net_prio:/
  10:memory:/
  9:rdma:/
  8:cpu,cpuacct:/
  7:devices:/user.slice
  6:perf_event:/
  5:cpuset:/
  4:pids:/user.slice/user-1000.slice/user@1000.service
  3:hugetlb:/
  2:blkio:/
  
1:name=systemd:/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
  0::/user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
  ```

  Ubuntu 20.04 (focal)
  -

  ```
  13:memory:/user.slice/user-1000.slice/user@1000.service
  12:perf_event:/
  11:misc:/
  10:pids:/user.slice/user-1000.slice/user@1000.service
  9:hugetlb:/
  8:cpuset:/
  7:blkio:/
  6:devices:/user.slice
  5:cpu,cpuacct:/
  4:freezer:/
  3:rdma:/
  2:net_cls,net_prio:/
  
1:name=systemd:/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope
  
0::/user.slice/user-1000.slice/user@1000.service/apps.slice/apps-org.gnome.Terminal.slice/vte-spawn-ad936f4d-0d62-4ac4-bbd8-0e766d8a3b1f.scope
  ```

  Ubuntu 22.04 (jammy)
  -

  ```
  
0::/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-0c3f8b02-b112-4cab-accc-764cbb223bac.scope
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2043393/+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 2045705] Re: FTBFS with default Java 21

2024-02-22 Thread Benjamin Drung
** Changed in: apport
   Status: Fix Committed => Fix Released

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

Title:
  FTBFS with default Java 21

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Triaged

Bug description:
  Dear Maintainers,

  The package apport ftbfs with default Java 21.
  The relevant part of the build log:
  ---
  running build_java_subdir
  warning: [options] bootstrap class path not set in conjunction with -source 7
  error: Source option 7 is no longer supported. Use 8 or later.
  error: Target option 7 is no longer supported. Use 8 or later.
  Traceback (most recent call last):
File "/<>/setup.py", line 119, in 
  DistUtilsExtra.auto.setup(
File "/usr/lib/python3/dist-packages/DistUtilsExtra/auto.py", line 125, in 
setup
  setuptools.setup(**attrs)
File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 107, in 
setup
  return distutils.core.setup(**attrs)
 ^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
185, in setup
  return run_commands(dist)
 ^^
File "/usr/lib/python3/dist-packages/setuptools/_distutils/core.py", line 
201, in run_commands
  dist.run_commands()
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
969, in run_commands
  self.run_command(cmd)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in 
run_command
  super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
  cmd_obj.run()
File 
"/usr/lib/python3/dist-packages/setuptools/_distutils/command/build.py", line 
131, in run
  self.run_command(cmd_name)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/cmd.py", line 
318, in run_command
  self.distribution.run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 1233, in 
run_command
  super().run_command(command)
File "/usr/lib/python3/dist-packages/setuptools/_distutils/dist.py", line 
988, in run_command
  cmd_obj.run()
File "/<>/setuptools_apport/java.py", line 35, in run
  subprocess.check_call(javac + glob.glob("com/ubuntu/apport/*.java"))
File "/usr/lib/python3.11/subprocess.py", line 413, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['javac', '-source', '7', '-target', 
'7', 'com/ubuntu/apport/ApportUncaughtExceptionHandler.java']' returned 
non-zero exit status 2.
  E: pybuild pybuild:395: build: plugin distutils failed with: exit code=1: 
/usr/bin/python3 setup.py build
  dh_auto_build: error: pybuild --build -i python{version} -p "3.12 3.11" 
returned exit code 13
  make[1]: *** [debian/rules:12: override_dh_auto_build] Error 25
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:4: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  

  Build finished at 2023-12-04T07:37:06Z
  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2045705/+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 2028879] Re: Lack of default dpkg diverts causes test_get_file_package_diversion to fail

2024-02-22 Thread Benjamin Drung
** Changed in: apport
   Status: Fix Committed => Fix Released

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

Title:
  Lack of default dpkg diverts causes test_get_file_package_diversion to
  fail

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

Bug description:
  tests/integration/test_packaging_apt_dpkg.py::test_get_file_package_diversion
  fails if it doesn't detect any dpkg diversions. Apparently something
  (possibly dash?) stopped diverting something, so now there are no
  diversions in the autopkgtest environment and therefore this test
  fails.

  One option is to add something that does divert something, eg. vim, to
  the test dependencies. This fixes the issue for now, but isn't really
  a permanent solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2028879/+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 2031919] Re: /usr/share/apport/whoopsie-upload-all:TypeError:/usr/share/apport/whoopsie-upload-all@247:main:collect_info:process_report:add_gdb_info

2024-02-22 Thread Benjamin Drung
** Changed in: apport
   Status: Fix Committed => Fix Released

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:TypeError:/usr/share/apport/whoopsie-upload-
  all@247:main:collect_info:process_report:add_gdb_info

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

Bug description:
  ```
  Traceback (most recent call last):
File "/usr/share/apport/whoopsie-upload-all", line 247, in 
  main()
File "/usr/share/apport/whoopsie-upload-all", line 229, in main
  stamps = collect_info()
   ^^
File "/usr/share/apport/whoopsie-upload-all", line 160, in collect_info
  res = process_report(r)
^
File "/usr/share/apport/whoopsie-upload-all", line 108, in process_report
  r.add_gdb_info()
File "/usr/lib/python3/dist-packages/apport/report.py", line 930, in 
add_gdb_info
  environ["HOME"] = "/nonexistent"
  ~~~
  TypeError: 'str' object does not support item assignment
  ```

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2031919/+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 2048136] Re: Please support systemd-coredump as core dump handler

2024-02-22 Thread Benjamin Drung
** Changed in: apport
   Status: Fix Committed => Fix Released

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

Title:
  Please support systemd-coredump as core dump handler

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  There can only be one system core dump handler on a Linux system and
  Apport is the Ubuntu default core dump handler. Besides Apport other
  tools offer coredump handler, in particular systemd-coredump. Due to
  Apport being installed on all Ubuntu system by default none of these
  alternate system can be installed.

  There has been some user request for this integration to work. Proper
  integration between Apport and systemd-coredump would offer a better
  experience to developers who want to use systemd-coredump. systemd-
  coredump and coredumpctl provide more documentation and have more
  users upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2048136/+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 2051512] Re: apport ftbfs with Python 3.12 as the default

2024-02-22 Thread Benjamin Drung
** Changed in: apport
   Status: Fix Committed => Fix Released

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

Title:
  apport ftbfs with Python 3.12 as the default

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  New
Status in python3.12 package in Ubuntu:
  New
Status in apport source package in Noble:
  Fix Released
Status in python3-defaults source package in Noble:
  New
Status in python3.12 source package in Noble:
  New

Bug description:
  [Description]

  Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
  (maybe all?)

  [Test Plan]

  Run the following script:

  import gzip
  import io
  out = io.BytesIO()
  gzip.GzipFile("foo", mode="wb", fileobj=out, mtime=0).write(b"FooFoo")
  # print(out.getvalue())
  print(gzip.decompress(out.getvalue()))

  Expected output (as on Python 3.11):
  FooFoo

  Buggy output (tail end of the stack trace):
  EOFError: Compressed file ended before the end-of-stream marker was reached

  [Original report]

  debian/rules override_dh_auto_test
  make[1]: Entering directory '/<>'
  tests/run-linters --errors-only
  Skipping mypy tests, mypy is not installed
  Running pylint...
  * Module apport-retrace
  bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment 
(used-before-assignment)
  make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:4: binary] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2051512/+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 2052482] Re: Bad packet length 2424479189 Connection corrupted

2024-02-22 Thread Paride Legovini
Thanks for the additional information. By reading the pages Sergio
linked to I found one user writing:

  Downgrading openssh-server to version 8.0p1-19.el8_8 will
  revert the update and SSH will work again, although this
  probably not advisable.

That's definitely not advisable, but I think it's worth checking that
the older version actually works. This will help figuring out where the
problem is.

Then from https://linux.oracle.com/errata/ELSA-2024-12164.html I see
that newer openssh versions are available. Those are quite recent
(2024-02-14). Could you please test those and report your findings?

Thanks!

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

Title:
  Bad packet length 2424479189 Connection corrupted

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  ssh-clent:
  uname -a :5.15.0-48-generic #54-Ubuntu
  ```
  Ubuntu 22.04.3 LTS
  OpenSSH_8.9p1 Ubuntu-3ubuntu0.6, OpenSSL 3.0.2 15 Mar 2022
  ```

  ssh-server:
  ```
  OracleLinux 8.9
  OpenSSH_8.0p1, OpenSSL 1.1.1k  FIPS 25 Mar 2021
  ```

  ```
  userxxx@userxxx-H3C-X7-030s-0274:~$ ssh 192.168.xxx.xxx -vvv
  OpenSSH_8.9p1 Ubuntu-3ubuntu0.6, OpenSSL 3.0.2 15 Mar 2022
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
  debug1: /etc/ssh/ssh_config line 21: Applying options for *
  debug2: resolve_canonicalize: hostname 192.168.xxx.xxx is address
  debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts' -> 
'/home/userxxx/.ssh/known_hosts'
  debug3: expanded UserKnownHostsFile '~/.ssh/known_hosts2' -> 
'/home/userxxx/.ssh/known_hosts2'
  debug3: ssh_connect_direct: entering
  debug1: Connecting to 192.168.xxx.xxx [192.168.xxx.xxx] port 22.
  debug3: set_sock_tos: set socket 3 IP_TOS 0x10
  debug1: Connection established.
  debug1: identity file /home/userxxx/.ssh/id_rsa type 0
  debug1: identity file /home/userxxx/.ssh/id_rsa-cert type -1
  debug1: identity file /home/userxxx/.ssh/id_ecdsa type 2
  debug1: identity file /home/userxxx/.ssh/id_ecdsa-cert type -1
  debug1: identity file /home/userxxx/.ssh/id_ecdsa_sk type -1
  debug1: identity file /home/userxxx/.ssh/id_ecdsa_sk-cert type -1
  debug1: identity file /home/userxxx/.ssh/id_ed25519 type -1
  debug1: identity file /home/userxxx/.ssh/id_ed25519-cert type -1
  debug1: identity file /home/userxxx/.ssh/id_ed25519_sk type -1
  debug1: identity file /home/userxxx/.ssh/id_ed25519_sk-cert type -1
  debug1: identity file /home/userxxx/.ssh/id_xmss type -1
  debug1: identity file /home/userxxx/.ssh/id_xmss-cert type -1
  debug1: identity file /home/userxxx/.ssh/id_dsa type -1
  debug1: identity file /home/userxxx/.ssh/id_dsa-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.6
  debug1: Remote protocol version 2.0, remote software version OpenSSH_8.0
  debug1: compat_banner: match: OpenSSH_8.0 pat OpenSSH* compat 0x0400
  debug2: fd 3 setting O_NONBLOCK
  debug1: Authenticating to 192.168.xxx.xxx:22 as 'userxxx'
  debug3: record_hostkey: found key type ED25519 in file 
/home/userxxx/.ssh/known_hosts:20
  debug3: load_hostkeys_file: loaded 1 keys from 192.168.xxx.xxx
  debug1: load_hostkeys: fopen /home/userxxx/.ssh/known_hosts2: No such file or 
directory
  debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts: No such file or 
directory
  debug1: load_hostkeys: fopen /etc/ssh/ssh_known_hosts2: No such file or 
directory
  debug3: order_hostkeyalgs: have matching best-preference key type 
ssh-ed25519-cert-...@openssh.com, using HostkeyAlgorithms verbatim
  debug3: send packet: type 20
  debug1: SSH2_MSG_KEXINIT sent
  debug3: receive packet: type 20
  debug1: SSH2_MSG_KEXINIT received
  debug2: local client KEXINIT proposal
  debug2: KEX algorithms: 
curve25519-sha256,curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,sntrup761x25519-sha...@openssh.com,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,ext-info-c,kex-strict-c-...@openssh.com
  debug2: host key algorithms: 
ssh-ed25519-cert-...@openssh.com,ecdsa-sha2-nistp256-cert-...@openssh.com,ecdsa-sha2-nistp384-cert-...@openssh.com,ecdsa-sha2-nistp521-cert-...@openssh.com,sk-ssh-ed25519-cert-...@openssh.com,sk-ecdsa-sha2-nistp256-cert-...@openssh.com,rsa-sha2-512-cert-...@openssh.com,rsa-sha2-256-cert-...@openssh.com,ssh-ed25519,ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,sk-ssh-ed25...@openssh.com,sk-ecdsa-sha2-nistp...@openssh.com,rsa-sha2-512,rsa-sha2-256
  debug2: ciphers ctos: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
  debug2: ciphers stoc: 
chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com
  debug2: 

[Touch-packages] [Bug 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)

2024-02-22 Thread Christian Ehrhardt 
FYI: updated ubuntu-meta, now in noble-proposed as version 1.532

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

Title:
  Please consider no more having irqbalance enabled by default (per
  image/use-case/TBD)

Status in cloud-images:
  New
Status in Release Notes for Ubuntu:
  In Progress
Status in Ubuntu on IBM z Systems:
  Opinion
Status in irqbalance package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1833322/+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 2044129] Re: ubuntu-bug does not allow for reporting a bug in "other software" manually giving a symptom description

2024-02-22 Thread Benjamin Drung
** Changed in: apport
Milestone: 2.28.0 => None

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

Title:
  ubuntu-bug does not allow for reporting a bug in "other software"
  manually giving a symptom description

Status in Apport:
  Triaged
Status in apport package in Ubuntu:
  Triaged

Bug description:
  the man page of ubuntu-bug/apport-bug (what is the difference? why am
  I shown the manpage of apport-bug when typing man ubuntu-bug?) says
  running apport-bug without arguments results in showing me a list of
  symptoms.

  When I try to report a bug in some general program that is not related
  to the other 9 categories - which is most of the 1 apps in Ubuntu
  - I must chose "Other Problem" - but in contrary to the man page that
  tells me I am asked about further things, I only get "You need to
  specific the pakacge or PID".

  I currently try to report a bug in the things that identifies itself
  as "Ubuntu Software" in the Dock, but I have no idea what its correct
  program or package name is, and have no idea how to find that. In PS
  there is no process with "ubuntu" or "software" in its name.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu5
  ProcVersionSignature: Ubuntu 6.2.0-1015.15-lowlatency 6.2.16
  Uname: Linux 6.2.0-1015-lowlatency x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 21 14:38:42 2023
  InstallationDate: Installed on 2023-08-21 (92 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apport
  UpgradeStatus: Upgraded to mantic on 2023-11-05 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2044129/+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 2048136] Re: Please support systemd-coredump as core dump handler

2024-02-22 Thread Benjamin Drung
Last bit: https://github.com/canonical/apport/pull/290

** Changed in: apport (Ubuntu)
   Status: Triaged => Fix Committed

** Changed in: apport
   Status: Triaged => Fix Committed

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

Title:
  Please support systemd-coredump as core dump handler

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Committed

Bug description:
  There can only be one system core dump handler on a Linux system and
  Apport is the Ubuntu default core dump handler. Besides Apport other
  tools offer coredump handler, in particular systemd-coredump. Due to
  Apport being installed on all Ubuntu system by default none of these
  alternate system can be installed.

  There has been some user request for this integration to work. Proper
  integration between Apport and systemd-coredump would offer a better
  experience to developers who want to use systemd-coredump. systemd-
  coredump and coredumpctl provide more documentation and have more
  users upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2048136/+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 2051512] Re: apport ftbfs with Python 3.12 as the default

2024-02-22 Thread Benjamin Drung
** Also affects: apport
   Importance: Undecided
   Status: New

** Changed in: apport
Milestone: None => 2.28.0

** Changed in: apport
   Status: New => Fix Committed

** Changed in: apport
   Importance: Undecided => High

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

Title:
  apport ftbfs with Python 3.12 as the default

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  New
Status in python3.12 package in Ubuntu:
  New
Status in apport source package in Noble:
  Fix Released
Status in python3-defaults source package in Noble:
  New
Status in python3.12 source package in Noble:
  New

Bug description:
  [Description]

  Python 3.12 gzip.GZipFile.write() outputs truncated data in some cases
  (maybe all?)

  [Test Plan]

  Run the following script:

  import gzip
  import io
  out = io.BytesIO()
  gzip.GzipFile("foo", mode="wb", fileobj=out, mtime=0).write(b"FooFoo")
  # print(out.getvalue())
  print(gzip.decompress(out.getvalue()))

  Expected output (as on Python 3.11):
  FooFoo

  Buggy output (tail end of the stack trace):
  EOFError: Compressed file ended before the end-of-stream marker was reached

  [Original report]

  debian/rules override_dh_auto_test
  make[1]: Entering directory '/<>'
  tests/run-linters --errors-only
  Skipping mypy tests, mypy is not installed
  Running pylint...
  * Module apport-retrace
  bin/apport-retrace:577:44: E0601: Using variable 'crashid' before assignment 
(used-before-assignment)
  make[1]: *** [debian/rules:23: override_dh_auto_test] Error 2
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:4: binary] Error 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2051512/+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 2054681] Re: Merge console-setup (1.226) from Debian

2024-02-22 Thread Heinrich Schuchardt
** Changed in: console-setup (Ubuntu)
 Assignee: (unassigned) => Heinrich Schuchardt (xypron)

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

Title:
  Merge console-setup (1.226) from Debian

Status in console-setup package in Ubuntu:
  New

Bug description:
  In Debian console-setup (1.226) is available. It should be merged into
  Noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2054681/+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 2038650] Re: crash reports not sent to the Error Tracker

2024-02-22 Thread Benjamin Drung
** Also affects: apport
   Importance: Undecided
   Status: New

** Changed in: apport
Milestone: None => 2.28.0

** Changed in: apport
   Importance: Undecided => High

** Changed in: apport
   Status: New => Fix Committed

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

Title:
  crash reports not sent to the Error Tracker

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Lunar:
  Fix Released
Status in apport source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  Crash reports aren't sent in when going through the UI, unless the
  user looks at the crash details.

  [ Test Plan ]

  0) Make sure that error reporting is set to manual in the system settings (in 
Privacy screen)
  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog. DO NOT look at the details of the report.
  4) ls -lh /var/crash/*xeyes*

  There should be 3 files:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  [ Where problems could occur ]

  If the patch is wrong, we actually see similar bugs for other UI
  paths, e.g. ticking the "Remember this" box, etc. I tried to cover
  them during manual testing but I might have missed some.

  [ Other Info ]
   
  If possible I'd like for us not to wait too long for this to mature in 
-proposed, as this would affect crashes during the upgrade.

  [ Original report ]
  From what I can tell when I click the send button to send a crash report to 
the Error Tracker the crash doesn't actually get sent. My testing process 
follows:

  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog
  4) ls -lh /var/crash

  I would expect there to be three files in /var/crash:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  However, after step #4 I'm only seeing the .crash file and not a
  .upload or .uploaded.  I was able to get the .upload and .uploaded
  files created if I chose to "View Report" and then click "Send".

  It's worth noting though that I did notice the size of the .crash file
  increase after clicking "Send" so some post-processing was done.

  ProblemType: BugDistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:12:46 2023
  InstallationDate: Installed on 2022-01-07 (637 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2038650/+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 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)

2024-02-22 Thread Christian Ehrhardt 
FYI: Seed change landed

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

Title:
  Please consider no more having irqbalance enabled by default (per
  image/use-case/TBD)

Status in cloud-images:
  New
Status in Release Notes for Ubuntu:
  In Progress
Status in Ubuntu on IBM z Systems:
  Opinion
Status in irqbalance package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1833322/+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 1833322] Re: Please consider no more having irqbalance enabled by default (per image/use-case/TBD)

2024-02-22 Thread Christian Ehrhardt 
Steve was so kind reviewing and approving my proposal.
Doing that now is also helpful as it should make sure it still has quite some 
exposure and thereby chances for people to report issues (vs if we'd land it 
much later like after beta freeze).

Changes will:
- change the seeds in regard to irqbalance, but no change to irqbalance (the 
package)
- need an update of ubuntu-meta
- IMHO we also want a release notes entry.
- CPC might consider re-enabling it as image customization for some as shown in 
comment #39

I'm adjusting the bug tasks and state accordingly.

** Also affects: cloud-images
   Importance: Undecided
   Status: New

** Also affects: ubuntu-release-notes
   Importance: Undecided
   Status: New

** Changed in: ubuntu-release-notes
   Status: New => In Progress

** Changed in: ubuntu-z-systems
   Status: Confirmed => Opinion

** Changed in: irqbalance (Ubuntu)
   Status: Confirmed => Opinion

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Please consider no more having irqbalance enabled by default (per
  image/use-case/TBD)

Status in cloud-images:
  New
Status in Release Notes for Ubuntu:
  In Progress
Status in Ubuntu on IBM z Systems:
  Opinion
Status in irqbalance package in Ubuntu:
  Opinion
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1833322/+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 2031919] Re: /usr/share/apport/whoopsie-upload-all:TypeError:/usr/share/apport/whoopsie-upload-all@247:main:collect_info:process_report:add_gdb_info

2024-02-22 Thread Benjamin Drung
** Also affects: apport
   Importance: Undecided
   Status: New

** Changed in: apport
Milestone: None => 2.28.0

** Changed in: apport
   Importance: Undecided => Medium

** Changed in: apport
   Status: New => Fix Committed

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

Title:
  /usr/share/apport/whoopsie-upload-
  all:TypeError:/usr/share/apport/whoopsie-upload-
  all@247:main:collect_info:process_report:add_gdb_info

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Fix Released

Bug description:
  ```
  Traceback (most recent call last):
File "/usr/share/apport/whoopsie-upload-all", line 247, in 
  main()
File "/usr/share/apport/whoopsie-upload-all", line 229, in main
  stamps = collect_info()
   ^^
File "/usr/share/apport/whoopsie-upload-all", line 160, in collect_info
  res = process_report(r)
^
File "/usr/share/apport/whoopsie-upload-all", line 108, in process_report
  r.add_gdb_info()
File "/usr/lib/python3/dist-packages/apport/report.py", line 930, in 
add_gdb_info
  environ["HOME"] = "/nonexistent"
  ~~~
  TypeError: 'str' object does not support item assignment
  ```

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2031919/+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 2054683] Re: Please merge lvm2 2.03.16-3 from Debian unstable.

2024-02-22 Thread Dave Jones
Created MP as suggested by Bryce on the last merge (LP: #2020464)

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

Title:
  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

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

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

2024-02-22 Thread Dave Jones
Public bug reported:

Please merge lvm2 2.03.16-3 from Debian unstable.

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

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

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

Title:
  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

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

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

2024-02-22 Thread Dave Jones
Test builds may be found in ppa:waveform/lvm2
(https://launchpad.net/~waveform/+archive/ubuntu/lvm2)

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2/+merge/461016

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

Title:
  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

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

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

2024-02-22 Thread Dave Jones
Attaching patch against Debian unstable. For ease of review, relevant
commits and tags have been pushed to the following repository:

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

Specifically:

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

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

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


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

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

Title:
  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683/+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 2054681] [NEW] Merge console-setup (1.226) from Debian

2024-02-22 Thread Heinrich Schuchardt
Public bug reported:

In Debian console-setup (1.226) is available. It should be merged into
Noble.

** Affects: console-setup (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Merge console-setup (1.226) from Debian

Status in console-setup package in Ubuntu:
  New

Bug description:
  In Debian console-setup (1.226) is available. It should be merged into
  Noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2054681/+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 2054319] Re: System installed from jammy point release iso cannot upgrade to noble

2024-02-22 Thread Skia
Yeah, sorry, I forgot to mention. The crashes that happen in our Jenkins are 
already pushed to the error tracker.
Here are links to the latest oopses:
gnome-shell: https://errors.ubuntu.com/oops/af2e99fc-d101-11ee-8a58-fa163ec8ca8c
tracker-extract: 
https://errors.ubuntu.com/oops/7c05a805-d101-11ee-8a58-fa163ec8ca8c

Maybe Tim will have a link for the polkit crash, but I couldn't find
one.

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

Title:
  System installed from jammy point release iso cannot upgrade to noble

Status in gnome-shell package in Ubuntu:
  New
Status in policykit-1 package in Ubuntu:
  New
Status in tracker-miners package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  We have different crashes being encountered. In our auto-upgrade-
  testing, we see gnome-shell crash, however, when testing locally, I
  didn't experience this. @hyask did experience the gnome-shell crash
  though.

  When running an upgrade from jammy to noble in a virsh vm, about
  halfway through the upgrade process my gui dies. I then ran the
  upgrade from a console, to which it revealed that just the gui dies -
  the upgrade process, for me, continues and then laterally fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-release-upgrader-core 1:24.04.7
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu7
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CrashReports:
   640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 
14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash
   600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 
14:34:19.370597600 +:/var/crash/polkitd.0.crash
  Date: Mon Feb 19 14:53:39 2024
  InstallationDate: Installed on 2024-02-19 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: pkexec must be setuid root
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+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 1855402] Re: [TGL] mesa support

2024-02-22 Thread Timo Aaltonen
** Changed in: intel
   Status: New => Fix Released

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

Title:
  [TGL] mesa support

Status in intel:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  Description:

  this feature tracks the updates of mesa 3d for TGL support.

  We will update the commitid list as necessary

  Target Release: 20.04
  Target version: TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1855402/+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-02-22 Thread Daniel van Vugt
** Tags removed: kinetic lunar
** Tags added: udeng-2004

-- 
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 linux package in Ubuntu:
  In Progress
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Won't Fix

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=2 fastboot

  [ Test Plan ]

  1. Boot Ubuntu on a number of laptops that have the problem and verify no 
console text messages appear during boot.
  2. Verify you can switch VTs (e.g. Ctrl + Alt + F4) and log into them still.
  3. Reboot Ubuntu and remove the "splash" kernel parameter, now messages 
should appear.

  [ Where problems could occur ]

  Since the fix works by deferring fbcon's takeover of the console, the
  main problem encountered during its development was the inability to
  VT switch.

  [ 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/linux/+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 2054319] Re: System installed from jammy point release iso cannot upgrade to noble

2024-02-22 Thread Skia
** Tags added: rls-nn-incoming

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

Title:
  System installed from jammy point release iso cannot upgrade to noble

Status in gnome-shell package in Ubuntu:
  New
Status in policykit-1 package in Ubuntu:
  New
Status in tracker-miners package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  We have different crashes being encountered. In our auto-upgrade-
  testing, we see gnome-shell crash, however, when testing locally, I
  didn't experience this. @hyask did experience the gnome-shell crash
  though.

  When running an upgrade from jammy to noble in a virsh vm, about
  halfway through the upgrade process my gui dies. I then ran the
  upgrade from a console, to which it revealed that just the gui dies -
  the upgrade process, for me, continues and then laterally fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: ubuntu-release-upgrader-core 1:24.04.7
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu7
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CrashReports:
   640:1000:124:1592041:2024-02-19 14:26:22.564354912 +:2024-02-19 
14:51:56.318947066 +:/var/crash/_usr_libexec_tracker-extract-3.1000.crash
   600:0:124:833806:2024-02-19 14:34:18.370597600 +:2024-02-19 
14:34:19.370597600 +:/var/crash/polkitd.0.crash
  Date: Mon Feb 19 14:53:39 2024
  InstallationDate: Installed on 2024-02-19 (0 days ago)
  InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to noble on 2024-02-19 (0 days ago)
  VarLogDistupgradeAptclonesystemstate.tar.gz: Error: command ['pkexec', 'cat', 
'/var/log/dist-upgrade/apt-clone_system_state.tar.gz'] failed with exit code 
127: pkexec must be setuid root
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting
  mtime.conffile..etc.init.d.apport: 2024-02-14T15:51:44

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2054319/+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 2054675] [NEW] pulseaudio sound not working, coincides with brightness controller not working and screen flickering, occurred when computer attempted to go idle and instead flick

2024-02-22 Thread Jeremy
Public bug reported:

Description:Ubuntu 22.04.4 LTS
Release:22.04

pulseaudio:
  Installed: 1:15.99.1+dfsg1-1ubuntu2.1
  Candidate: 1:15.99.1+dfsg1-1ubuntu2.1
  Version table:
 *** 1:15.99.1+dfsg1-1ubuntu2.1 500
500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:15.99.1+dfsg1-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

I expected the computer to idle down and instead the computer did not
idle down and chose to flicker the brightness from dim to dark to 100%
and the audio stopped working. Keeping the dimmer on about 5% keeps the
brightness at 100% and stops the flickering. Bluetooth audio speaker
works.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: pass
Date: Thu Feb 22 03:17:38 2024
ExecutablePath: /usr/bin/pulseaudio
InstallationDate: Installed on 2023-10-18 (126 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/28/2022
dmi.bios.release: 1.57
dmi.bios.vendor: HP
dmi.bios.version: N75 Ver. 01.57
dmi.board.name: 8079
dmi.board.vendor: HP
dmi.board.version: KBC Version 85.79
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.ec.firmware.release: 133.121
dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.57:bd07/28/2022:br1.57:efr133.121:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr:sku1DV78US#ABA:
dmi.product.family: 103C_5336AN HP EliteBook
dmi.product.name: HP EliteBook 840 G3
dmi.product.sku: 1DV78US#ABA
dmi.sys.vendor: HP

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


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

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

Title:
  pulseaudio sound not working, coincides with brightness controller not
  working and screen flickering, occurred when computer attempted to go
  idle and instead flickered and crashed these applets

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 22.04.4 LTS
  Release:  22.04

  pulseaudio:
Installed: 1:15.99.1+dfsg1-1ubuntu2.1
Candidate: 1:15.99.1+dfsg1-1ubuntu2.1
Version table:
   *** 1:15.99.1+dfsg1-1ubuntu2.1 500
  500 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:15.99.1+dfsg1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  I expected the computer to idle down and instead the computer did not
  idle down and chose to flicker the brightness from dim to dark to 100%
  and the audio stopped working. Keeping the dimmer on about 5% keeps
  the brightness at 100% and stops the flickering. Bluetooth audio
  speaker works.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2.1
  ProcVersionSignature: Ubuntu 6.5.0-18.18~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Thu Feb 22 03:17:38 2024
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2023-10-18 (126 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/28/2022
  dmi.bios.release: 1.57
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.57
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.79
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 133.121
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.57:bd07/28/2022:br1.57:efr133.121:svnHP:pnHPEliteBook840G3:pvr:rvnHP:rn8079:rvrKBCVersion85.79:cvnHP:ct10:cvr:sku1DV78US#ABA:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G3
  dmi.product.sku: 1DV78US#ABA
  dmi.sys.vendor: HP

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


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

[Touch-packages] [Bug 1892225] Re: apport-gtk consumes 100% CPU for way too long after something crashes

2024-02-22 Thread Benjamin Drung
Can you reproduce it?

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

Title:
  apport-gtk consumes 100% CPU for way too long after something crashes

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Something (related to Cinnamon) crashes, so the usual popup appears
  telling me that something crashed, and asking me whether I wanted to
  send a report. I choose Send.

  Every time this happens, then a process called apport-gtk starts
  consuming 100% CPU and it goes on for several minutes, so long that I
  end up killing it.

  There's no way there is a good reason for consuming so much CPU for so
  long. If you need to do such an amount of processing just to generate
  and send a bug report, something is deeply broken. But if the
  operation actually had to be that computationally expensive, then you
  must do it in a less intensive way so that it can go on in the
  background, for no matter how long, without rendering me unable to use
  my  computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.4
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia
  ApportLog:
   ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: called for pid 2405, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: executable: 
/usr/bin/cinnamon (command line "cinnamon --replace")
   ERROR: apport (pid 2908) Wed Aug 19 18:39:29 2020: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 2908) Wed Aug 19 18:39:34 2020: wrote report 
/var/crash/_usr_bin_cinnamon.1000.crash
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   640:1000:110:69556:2020-08-19 18:39:33.732794284 +0200:2020-08-19 
18:39:34.732794284 +0200:/var/crash/_usr_bin_cinnamon-launcher.1000.crash
   640:1000:110:15432562:2020-08-19 18:39:34.466977487 +0200:2020-08-19 
18:42:42.722667813 +0200:/var/crash/_usr_bin_cinnamon.1000.crash
  CurrentDesktop: X-Cinnamon
  Date: Wed Aug 19 18:42:34 2020
  InstallationDate: Installed on 2013-10-11 (2503 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to focal on 2020-07-12 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1892225/+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 2023322] Re: GTK internal browser does not render with Nvidia drivers

2024-02-22 Thread Bug Watch Updater
** Changed in: webkit
   Status: Confirmed => Fix Released

** Bug watch added: bugs.webkit.org/ #261874
   https://bugs.webkit.org/show_bug.cgi?id=261874

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window 0x3a006dc.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Starting systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories...
  Jun 08 11:17:42 CCW-HAL systemd[1]: systemd-tmpfiles-clean.service: 
Deactivated successfully.
  Jun 08 11:17:42 CCW-HAL systemd[1]: Finished systemd-tmpfiles-clean.service - 
Cleanup of Temporary Directories.
  Jun 08 11:17:42 CCW-HAL systemd[1]: 
run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated 
successfully.
  Jun 08 11:18:10 CCW-HAL gnome-shell[3803]: Window manager warning: 

[Touch-packages] [Bug 2023322]

2024-02-22 Thread Georges Basile Stavracas Neto
After Sonny reached out on Mastodon, people reported a variety of
problems that were either tracked down to misconfigured systems (e.g.
missing NVIDIA GBM, no modesetting, etc), and the cases that did look
like interesting cases seemed to be fixed with WebKitGTK 2.42.5.

I think it's reasonable to assume this bug was fixed by the combination
of the various refactorings to DMA-BUF handling code in WebKitGTK, and
newer NVIDIA cards.

If anyone can reproduce reproduce this with a modern version (2.42+) of
WebKitGTK GTK4, please speak up and the issue can be reopened. But
please make sure to read
https://bugs.webkit.org/show_bug.cgi?id=261874#c32 and see if your issue
is not described in that comment.

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

Title:
  GTK internal browser does not render with Nvidia drivers

Status in Webkit:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in yelp package in Ubuntu:
  Invalid
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  When I go into Settings > Online Accounts > Google, I get to the
  prompt for email address, once in a while it stops accepting input
  there. But often I can get to the password screen. Once I do, I can't
  type anything or paste anything.

  This is a fresh install of Ubuntu 23.04 and I have installed all
  updates.

  Nothing in /var/crash

  Jun 08 11:15:59 CCW-HAL systemd[3523]: 
vte-spawn-8b4a59a3-a060-4bdd-92e6-285656bdb9a2.scope: Consumed 3.448s CPU time.
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:01 CCW-HAL gnome-shell[3803]: g_closure_unref: assertion 
'closure->ref_count > 0' failed
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
app-gnome-org.gnome.Terminal-10924.scope - Application launched by gnome-shell.
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Activating via systemd: service name='org.gnome.Terminal' 
unit='gnome-terminal-server.service' requested by ':1.167' (uid=1000 pid=10927 
comm="/usr/bin/gnome-terminal.real" label="unconfined")
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Starting gnome-terminal-server.service 
- GNOME Terminal Server...
  Jun 08 11:16:29 CCW-HAL dbus-daemon[3552]: [session uid=1000 pid=3552] 
Successfully activated service 'org.gnome.Terminal'
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started gnome-terminal-server.service 
- GNOME Terminal Server.
  Jun 08 11:16:29 CCW-HAL systemd[3523]: Started 
vte-spawn-9cee1911-372a-4bb4-8b57-694984e43990.scope - VTE child process 10955 
launched by gnome-terminal-server process 10931.
  Jun 08 11:16:49 CCW-HAL gnome-control-c[8079]: Error showing account: Child 
process exited with code 1
  Jun 08 11:16:53 CCW-HAL gnome-online-accounts-panel.desktop[9764]: GLib-GIO: 
Using cross-namespace EXTERNAL authentication (this will deadlock if server is 
GDBus < 2.73.3)GLib-GIO: _g_io_module_get_default: Found default implementation 
gvfs (GDaemonVfs) for ‘gio-vfs’GLib: unsetenv() is not thread-safe and should 
not be used after threads are createdGLib-GIO: _g_io_module_get_default: Found 
default implementation dconf (DConfSettingsBackend) for 
‘gsettings-backend’GoaBackend: Loading all providers: GoaBackend: - 
googleGoaBackend: - owncloudGoaBackend: - windows_liveGoaBackend: - 
exchangeGoaBackend: - lastfmGoaBackend: - imap_smtpGoaBackend: - 
kerberosGoaBackend: activated kerberos providerGLib-GIO: 
_g_io_module_get_default: Found default implementation gnutls 
(GTlsBackendGnutls) for ‘gio-tls-backend’Failed to create account: Dialog was 
dismissed
  Jun 08 11:16:53 CCW-HAL xdg-desktop-por[3907]: Realtime error: Could not map 
pid: Could not determine pid namespace: Could not find instance-id in process's 
/.flatpak-info
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session opened 
for user root(uid=0) by (uid=0)
  Jun 08 11:17:01 CCW-HAL CRON[11094]: (root) CMD (cd / && run-parts --report 
/etc/cron.hourly)
  Jun 08 11:17:01 CCW-HAL CRON[11093]: pam_unix(cron:session): session closed 
for user root
  Jun 08 11:17:06 CCW-HAL kernel: WebKitWebProces[11026]: segfault at 
55bd22ad9adc ip 55bd22ad9adc sp 7ffd1f6adbe8 error 14 likely on CPU 2 
(core 2, socket 0)
  Jun 08 11:17:06 CCW-HAL kernel: Code: Unable to access opcode bytes at 
0x55bd22ad9ab2.
  Jun 08 11:17:36 CCW-HAL gnome-shell[3803]: Window manager warning: 
WM_TRANSIENT_FOR window 0x3a02767 for 0x3a02778 window override-redirect is an 
override-redirect window and this is not correct according to the standard, so 
we'll fallback to the first non-override-redirect window