date:20240122

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

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

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

Title:
  Apparmor crashes GPU acceleration

Status in apparmor package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Apparmor crashes GPU acceleration

  Firefox GPU acceleration started crashing after updating from Ubuntu
  22.10 to 23.04.

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

  $ apt-cache policy firefox
  firefox:
Installed: 113.0+build1-0ubuntu0.23.04.1~mt1
Candidate: 113.0+build1-0ubuntu0.23.04.1~mt1
Version table:
   1:1snap1-0ubuntu3 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main 
amd64 Packages
   *** 113.0+build1-0ubuntu0.23.04.1~mt1 999
  500 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy libglx-mesa0 
  libglx-mesa0:
Installed: 23.0.3~kisak1~k
Candidate: 23.0.3~kisak1~k
Version table:
   *** 23.0.3~kisak1~k 500
  500 https://ppa.launchpadcontent.net/kisak/kisak-mesa/ubuntu 
kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
   23.0.2-1ubuntu1 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main 
amd64 Packages

  $ apt-cache policy apparmor
  apparmor:
Installed: 3.0.8-1ubuntu2
Candidate: 3.0.8-1ubuntu2
Version table:
   *** 3.0.8-1ubuntu2 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main 
amd64 Packages
  100 /var/lib/dpkg/status

  # Expected behavior

  Firefox should not crash in WebGL aquarium and continue to work
  properly like on 22.10. It should successfully use my GPU to make
  scrolling smooths and save battery when watching videos.

  # Actual behavior

  1. Startup takes a second or two longer than usual
  2. Typing in the address bar is slow
  3. Scrolling takes 400% CPU usage
  4. Scrolling stutters
  5. VAAPI on https://www.w3schools.com/html/html5_video.asp is no longer used 
as shown in intel_gpu_top
  6. Fans start spinning and battery goes down fast
  7. glxtest failures had to be manually deleted in about:config
  8. Only a few fish in WebGL aquarium 
(https://webglsamples.org/aquarium/aquarium.html) load before Firefox 
force-closes with the message: "Mozilla Crash Reporter Firefox had a problem 
and crashed. Unfortunately, the crash reporter is unable to submit a crash 
report. Details: The application did not leave a crash dump file. Close"
  9. The following lines are relevant in dmesg after clearing it:

  [22157.695580] kauditd_printk_skb: 6 callbacks suppressed
  [22157.695582] audit: type=1400 audit(1683153440.994:2583): apparmor="DENIED" 
operation="capable" class="cap" profile="firefox" pid=15898 comm="firefox" 
capability=21  capname="sys_admin"
  [22157.739641] audit: type=1400 audit(1683153441.038:2584): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [22157.739647] audit: type=1400 audit(1683153441.038:2585): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [22157.739719] audit: type=1400 audit(1683153441.038:2586): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [22157.739729] audit: type=1400 audit(1683153441.038:2587): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [22157.769407] audit: type=1400 audit(1683153441.070:2588): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/proc/15898/oom_score_adj" pid=15898 comm="firefox" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=1000
  [22157.773042] audit: type=1400 audit(1683153441.074:2589): apparmor="DENIED" 
operation="file_mmap" class="file" profile="firefox//lsb_release" 
name="/usr/bin/dash" pid=15934 comm="lsb_release" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
  [22157.974718] audit: type=1400 audit(1683153441.274:2590): apparmor="DENIED" 
operation="open" class="file" profile="firefox" name="/proc/15898/cgroup" 
pid=15898 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  [22157.996255] audit: type=1400 audit(1683153441.298:2591): apparmor="DENIED"

[Touch-packages] [Bug 2018439] Re: Apparmor crashes GPU acceleration

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

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

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

Title:
  Apparmor crashes GPU acceleration

Status in apparmor package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed

Bug description:
  Apparmor crashes GPU acceleration

  Firefox GPU acceleration started crashing after updating from Ubuntu
  22.10 to 23.04.

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

  $ apt-cache policy firefox
  firefox:
Installed: 113.0+build1-0ubuntu0.23.04.1~mt1
Candidate: 113.0+build1-0ubuntu0.23.04.1~mt1
Version table:
   1:1snap1-0ubuntu3 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main 
amd64 Packages
   *** 113.0+build1-0ubuntu0.23.04.1~mt1 999
  500 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy libglx-mesa0 
  libglx-mesa0:
Installed: 23.0.3~kisak1~k
Candidate: 23.0.3~kisak1~k
Version table:
   *** 23.0.3~kisak1~k 500
  500 https://ppa.launchpadcontent.net/kisak/kisak-mesa/ubuntu 
kinetic/main amd64 Packages
  100 /var/lib/dpkg/status
   23.0.2-1ubuntu1 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main 
amd64 Packages

  $ apt-cache policy apparmor
  apparmor:
Installed: 3.0.8-1ubuntu2
Candidate: 3.0.8-1ubuntu2
Version table:
   *** 3.0.8-1ubuntu2 500
  500 https://gpl.savoirfairelinux.net/pub/mirrors/ubuntu lunar/main 
amd64 Packages
  100 /var/lib/dpkg/status

  # Expected behavior

  Firefox should not crash in WebGL aquarium and continue to work
  properly like on 22.10. It should successfully use my GPU to make
  scrolling smooths and save battery when watching videos.

  # Actual behavior

  1. Startup takes a second or two longer than usual
  2. Typing in the address bar is slow
  3. Scrolling takes 400% CPU usage
  4. Scrolling stutters
  5. VAAPI on https://www.w3schools.com/html/html5_video.asp is no longer used 
as shown in intel_gpu_top
  6. Fans start spinning and battery goes down fast
  7. glxtest failures had to be manually deleted in about:config
  8. Only a few fish in WebGL aquarium 
(https://webglsamples.org/aquarium/aquarium.html) load before Firefox 
force-closes with the message: "Mozilla Crash Reporter Firefox had a problem 
and crashed. Unfortunately, the crash reporter is unable to submit a crash 
report. Details: The application did not leave a crash dump file. Close"
  9. The following lines are relevant in dmesg after clearing it:

  [22157.695580] kauditd_printk_skb: 6 callbacks suppressed
  [22157.695582] audit: type=1400 audit(1683153440.994:2583): apparmor="DENIED" 
operation="capable" class="cap" profile="firefox" pid=15898 comm="firefox" 
capability=21  capname="sys_admin"
  [22157.739641] audit: type=1400 audit(1683153441.038:2584): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [22157.739647] audit: type=1400 audit(1683153441.038:2585): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [22157.739719] audit: type=1400 audit(1683153441.038:2586): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:02.0/revision" pid=15901 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [22157.739729] audit: type=1400 audit(1683153441.038:2587): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:02.0/config" pid=15901 comm="firefox" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [22157.769407] audit: type=1400 audit(1683153441.070:2588): apparmor="DENIED" 
operation="open" class="file" profile="firefox" 
name="/proc/15898/oom_score_adj" pid=15898 comm="firefox" requested_mask="w" 
denied_mask="w" fsuid=1000 ouid=1000
  [22157.773042] audit: type=1400 audit(1683153441.074:2589): apparmor="DENIED" 
operation="file_mmap" class="file" profile="firefox//lsb_release" 
name="/usr/bin/dash" pid=15934 comm="lsb_release" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=0
  [22157.974718] audit: type=1400 audit(1683153441.274:2590): apparmor="DENIED" 
operation="open" class="file" profile="firefox" name="/proc/15898/cgroup" 
pid=15898 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  [22157.996255] audit: type=1400 audit(1683153441.298:2591): apparmor="DENIED"

[Touch-packages] [Bug 2044304] Re: Apparmor crashes GPU acceleration in Firefox 120

2024-01-22 Thread Daniel Tang

*** This bug is a duplicate of bug 2018439 ***
https://bugs.launchpad.net/bugs/2018439

** This bug has been marked a duplicate of bug 2018439
   Apparmor crashes GPU acceleration

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

Title:
   Apparmor crashes GPU acceleration in Firefox 120

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  $ apt-cache policy apparmor
  apparmor:
Installed: 3.0.4-2ubuntu2.3
Candidate: 3.0.4-2ubuntu2.3
Version table:
   *** 3.0.4-2ubuntu2.3 500 (phased 20%)
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.0.4-2ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  $ apt-cache policy firefox
  firefox:
Installed: 120.0+build2-0ubuntu0.22.04.1~mt1
Candidate: 120.0+build2-0ubuntu0.22.04.1~mt1
Version table:
   1:1snap1-0ubuntu2 -1
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
   *** 120.0+build2-0ubuntu0.22.04.1~mt1 1001
 1001 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu 
jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  $ apt-cache policy libglx-mesa0
  libglx-mesa0:
Installed: 23.0.4-0ubuntu1~22.04.1
Candidate: 23.0.4-0ubuntu1~22.04.1
Version table:
   *** 23.0.4-0ubuntu1~22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   22.0.1-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages


  Firefox Apparmor profile seems out of date and needs extra
  permissions.

  The issue started happening in Firefox version 120 after an upgrade
  from 119.0.1.

  I do see the lots of DENIED Apparmor errors before the freeze/crash:

  
  AVC apparmor="DENIED" operation="open" class="file" profile="firefox" 
name="/sys/devices/pci:00/:00:01.0/:01:00.0/config" pid=11949 
comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0

  AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
  name="/sys/devices/pci:00/:00:01.0/:01:00.0/revision"
  pid=11949 comm="firefox" requested_mask="r" denied_mask="r" fsuid=1000
  ouid=0

  AVC apparmor="DENIED" operation="open" class="file" profile="firefox"
  name="/proc/34029/cgroup" pid=34029
  comm=49736F6C617465642057656220436F requested_mask="r" denied_mask="r"
  fsuid=1000 ouid=1000

  MESA: error: Failed to query drm device.
  libEGL warning: egl: failed to create dri2 screen

  Adding the following the following permissions to 
/etc/apparmor.d/local/usr.bin.firefox seems to mitigate the issue:
  /sys/devices/pci*/**/{config,revision} r,
  @{PROC}/[0-9]*/**/comm r,
  @{PROC}/[0-9]*/**/oom_score_adj w,

  Disabling the firefox profile also mitigates the issue. It seems the
  profile needs an update to include permissions required by Firefox
  120.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2044304/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble

2024-01-22 Thread dann frazier

I ran the above test:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-dannf-test/jammy/amd64/l/livecd-rootfs/20240123_035147_6470b@/log.gz

It does appear that systemd-udevd is trying to scan partitions at the
same time as losetup:

1599s ++ losetup --show -f -P -v binary/boot/disk-uefi.ext4
1600s + loop_device=/dev/loop0
1600s + '[' '!' -b /dev/loop0 ']'
1600s + rootfs_dev_mapper=/dev/loop0p1
1600s + '[' '!' -b /dev/loop0p1 ']'
1600s + echo '/dev/loop0p1 is not a block device'
1600s /dev/loop0p1 is not a block device
1600s + echo '=== dmesg ==='
1600s === dmesg ===
1600s + dmesg -c
1600s [  986.014824] EXT4-fs (loop0p1): mounted filesystem with ordered data 
mode. Opts: (null). Quota mode: none.
1600s [  992.684380] EXT4-fs (loop0p1): mounted filesystem with ordered data 
mode. Opts: (null). Quota mode: none.
1600s [ 1043.171603] loop0: detected capacity change from 0 to 4612096
1600s [ 1043.171924]  loop0: p1 p14 p15
1600s [ 1043.190421]  loop0: p1 p14 p15
1600s + cat /sys/kernel/debug/tracing/trace
1600s # tracer: function
1600s #
1600s # entries-in-buffer/entries-written: 2/2   #P:4
1600s #
1600s #_-=> irqs-off
1600s #   / _=> need-resched
1600s #  | / _---=> hardirq/softirq
1600s #  || / _--=> preempt-depth
1600s #  ||| / _-=> migrate-disable
1600s #   / delay
1600s #   TASK-PID CPU#  |  TIMESTAMP  FUNCTION
1600s #  | | |   | | |
1600s  losetup-50167   [002] .  1043.176845: bdev_disk_changed 
<-loop_reread_partitions
1600ssystemd-udevd-321 [000] .  1043.195003: bdev_disk_changed 
<-blkdev_get_whole
1600s + echo 0
1600s + ls -l /dev/loop0p1
1600s brw--- 1 root root 259, 3 Jan 23 03:51 /dev/loop0p1
1600s + exit 1
1600s + clean_loops


Maybe we just need something like this?

diff --git a/drivers/block/loop.c b/drivers/block/loop.c
index 48c530b83000e..52fda87f5d674 100644
--- a/drivers/block/loop.c
+++ b/drivers/block/loop.c
@@ -1366,13 +1366,13 @@ static int loop_configure(struct loop_device *lo, 
fmode_t mode,
if (partscan)
lo->lo_disk->flags &= ~GENHD_FL_NO_PART_SCAN;
 
-   /* enable and uncork uevent now that we are done */
-   dev_set_uevent_suppress(disk_to_dev(lo->lo_disk), 0);
-
loop_global_unlock(lo, is_loop);
if (partscan)
loop_reread_partitions(lo);
 
+   /* enable and uncork uevent now that we are done */
+   dev_set_uevent_suppress(disk_to_dev(lo->lo_disk), 0);
+
if (!(mode & FMODE_EXCL))
bd_abort_claiming(bdev, loop_configure);

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable in noble

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2042680] Re: lsb_release shows incorrect Ubuntu version

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

** Changed in: base-files (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  lsb_release shows incorrect Ubuntu version

Status in base-files package in Ubuntu:
  Expired

Bug description:
  Testing Ubuntu Noble Desktop for Raspberry PI daily ISO dated
  03-11-2023

  After installing and rebooting running lsb_release -a shows version
  23.10 not 24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: lsb-release 12.0-2
  ProcVersionSignature: Ubuntu 6.5.0-1006.8-raspi 6.5.3
  Uname: Linux 6.5.0-1006-raspi aarch64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  3 16:24:14 2023
  Dependencies:
   
  PackageArchitecture: all
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: lsb-release-minimal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2042680/+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 2050805] Re: [HP EliteBook 8560w] Can't change screen brightness

2024-01-22 Thread Daniel van Vugt

** Summary changed:

- brightness 
+ [HP EliteBook 8560w] Can't change screen brightness

** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (Ubuntu)

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

Title:
  [HP EliteBook 8560w] Can't change screen brightness

Status in linux-hwe-6.5 package in Ubuntu:
  New

Bug description:
  hi , i can't change my brightness it s blocked on max even if i us
  fn+f9 it show the bar of brightness changing but not the brightness in
  my screen

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 22 19:36:53 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GF106GLM [Quadro 2000M] [103c:1631]
  InstallationDate: Installed on 2024-01-16 (6 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Hewlett-Packard HP EliteBook 8560w
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=a21fb944-4d22-4f82-b6f9-85577ca2ec3d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2012
  dmi.bios.release: 15.34
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.22
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.39
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 1.57
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.22:bd01/05/2012:br15.34:efr1.57:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.39:cvnHewlett-Packard:ct10:cvr:skuWX563AV:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560w
  dmi.product.sku: WX563AV
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-6.5/+bug/2050805/+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 2049958] Re: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/bluetooth/obexd' before installing new version: Input/output er

2024-01-22 Thread Daniel van Vugt

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

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

Title:
  package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to
  make backup link of './usr/lib/bluetooth/obexd' before installing new
  version: Input/output error

Status in Ubuntu:
  Incomplete

Bug description:
  bug found during software update launched from bootable usb

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: bluez-obexd 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckMismatches: ./casper/minimal.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  Date: Sat Jan 20 00:18:32 2024
  DuplicateSignature:
   package:bluez-obexd:5.68-0ubuntu1
   Unpacking bluez-obexd (5.68-0ubuntu1.1) over (5.68-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-MsVzUs/045-bluez-obexd_5.68-0ubuntu1.1_amd64.deb 
(--unpack):
unable to make backup link of './usr/lib/bluetooth/obexd' before installing 
new version: Input/output error
  ErrorMessage: unable to make backup link of './usr/lib/bluetooth/obexd' 
before installing new version: Input/output error
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: bluez
  Title: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to 
make backup link of './usr/lib/bluetooth/obexd' before installing new version: 
Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 306
  dmi.board.asset.tag: Default string
  dmi.board.name: GL553VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr306:bd09/26/2018:br5.6:svnASUSTeKCOMPUTERINC.:pnGL553VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: GL
  dmi.product.name: GL553VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:57:7B:12:13:2F  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:1345 acl:0 sco:0 events:90 errors:0
TX bytes:3835 acl:0 sco:0 commands:90 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2049958/+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 2049540] Re: hundreds of differences in module list between initramfs-tools version 0.142ubuntu10 and version 0.142ubuntu11

2024-01-22 Thread Dan Bungert

Hi Ben,

> Is there any proof that these modules are needed?

It appears we have very different assumptions for how dracut was to be
brought on board.

Diffstat of 0.142ubuntu1[01].log looks like:
 1 file changed, 229 insertions(+), 661 deletions(-)

That sounds like a lot of changes, in a LTS.  I think we need to flip
the mindset here - the status quo of the modules present should be
preserved, and the differences should be justified.  Do we have
supporting evidence that all these changes are appropriate?  The risk
here is that inadequate testing happens and we get a trickle of bugs
like LP: #2042710 that will need to be SRUed.

> Using symbol regexes will be more fine-grained than including whole
directories.

I appreciate that the previous mechanism has certainly acquired some
bloat by including whole directories, but now that is the observable
shipping behavior and we risk regressing people who depend on that.  How
can we tell the difference?

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

Title:
  hundreds of differences in module list between initramfs-tools version
  0.142ubuntu10 and version 0.142ubuntu11

Status in initramfs-tools package in Ubuntu:
  Triaged
Status in initramfs-tools source package in Noble:
  Triaged

Bug description:
  When analyzing the kernel modules present in the current initrd, I
  have found that there are hundreds of such differences, and that this
  started with the move to dracut.

  I believe that the move to dracut was intended to be relatively module
  neutral - see LP: #2031841 and LP: #2042710 for more details on that.

  I'm attaching here a test case based on podman, where different
  versions of the initramfs-tools package are installed, and then the
  list of modules present in the initrd is analyzed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2049540/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2024-01-22 Thread Dave Jones

Okay, good enough for me -- I'll sponsor my aforementioned branch for
noble and have a look at the mantic and jammy SRUs tomorrow, assuming
everything builds happily in noble.

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

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12

** Changed in: cython (Debian)
   Status: New => Confirmed

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

Title:
  autopkg tests ignored for migration of python3-defaults adding 3.12

Status in cython package in Ubuntu:
  New
Status in cython-legacy package in Ubuntu:
  New
Status in ipykernel package in Ubuntu:
  New
Status in ironic-python-agent package in Ubuntu:
  New
Status in jupyter-client package in Ubuntu:
  New
Status in numpy package in Ubuntu:
  New
Status in python-memory-profiler package in Ubuntu:
  New
Status in python-oslo.versionedobjects package in Ubuntu:
  Fix Committed
Status in python-urllib3 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in rich package in Ubuntu:
  New
Status in sphinx-autoapi package in Ubuntu:
  New
Status in vcr.py package in Ubuntu:
  New
Status in cython package in Debian:
  Confirmed
Status in cython-legacy package in Debian:
  New
Status in ipykernel package in Debian:
  New
Status in jupyter-client package in Debian:
  New
Status in numpy package in Debian:
  New
Status in python-memory-profiler package in Debian:
  New
Status in python-urllib3 package in Debian:
  Fix Released
Status in rich package in Debian:
  Confirmed
Status in sphinx-autoapi package in Debian:
  Fix Released
Status in vcr.py package in Debian:
  Fix Released

Bug description:
  autopkg tests ignored for migration of python3-defaults adding 3.12:

  These are the autopkg tests for packages, which we'll ignore for the
  initial migration of python3-defaults adding 3.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2050836] [NEW] apport should prevent crash reporting for unsupported python versions

2024-01-22 Thread Brian Murray

Public bug reported:

The following bucket in the Ubuntu Error Tracker was brought to my
attention because a package update stopped phasing because of it.

https://errors.ubuntu.com/problem/51d4468e0e9096398f852e3aed0e51658b6ca603

Looking at the individual crashes, e.g.
https://errors.ubuntu.com/oops/2b3117f0-b6ea-11ee-b9e6-fa163e171f02,
we can see that the InterpreterPath is /usr/bin/python3.9 and that this
also appears in Python3Details.

I don't see an UnreportableReason in the report so these would likely
get sent to Launchpad also. Anyway, I don't think these types of crashes
(using an unsupported python version) should be reportable because there
isn't anything we as Ubuntu Developers can do to resolve this problem.

** Affects: apport (Ubuntu)
 Importance: Low
 Status: New

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

** Description changed:

  The following bucket in the Ubuntu Error Tracker was brought to my
  attention because a package update stopped phasing because of it.
  
  https://errors.ubuntu.com/problem/51d4468e0e9096398f852e3aed0e51658b6ca603
  
- Looking at the individual crashes,
- e.g.https://errors.ubuntu.com/oops/2b3117f0-b6ea-11ee-b9e6-fa163e171f02,
+ Looking at the individual crashes, e.g.
+ https://errors.ubuntu.com/oops/2b3117f0-b6ea-11ee-b9e6-fa163e171f02,
  we can see that the InterpreterPath is /usr/bin/python3.9 and that this
  also appears in Python3Details.
  
  I don't see an UnreportableReason in the report so these would likely
  get sent to Launchpad also. Anyway, I don't think these types of crashes
  (using an unsupported python version) should be reportable because there
  isn't anything we as Ubuntu Developers can do to resolve this problem.

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

Title:
  apport should prevent crash reporting for unsupported python versions

Status in apport package in Ubuntu:
  New

Bug description:
  The following bucket in the Ubuntu Error Tracker was brought to my
  attention because a package update stopped phasing because of it.

  https://errors.ubuntu.com/problem/51d4468e0e9096398f852e3aed0e51658b6ca603

  Looking at the individual crashes, e.g.
  https://errors.ubuntu.com/oops/2b3117f0-b6ea-11ee-b9e6-fa163e171f02,
  we can see that the InterpreterPath is /usr/bin/python3.9 and that
  this also appears in Python3Details.

  I don't see an UnreportableReason in the report so these would likely
  get sent to Launchpad also. Anyway, I don't think these types of
  crashes (using an unsupported python version) should be reportable
  because there isn't anything we as Ubuntu Developers can do to resolve
  this problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2050836/+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 2042587] Autopkgtest regression report (dnsmasq/2.86-1.1ubuntu0.5)

All autopkgtests for the newly accepted dnsmasq (2.86-1.1ubuntu0.5) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/249.11-0ubuntu3.11 (ppc64el)


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

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

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

Title:
  jammy's version breaks existing dhcp scripts with relay

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
  stopped working in an environment where a DHCP relay is in use.
  Instead of the expected client IP address, the script gets the _relay_
  IP address as an argument.

  This was fixed in 2.87, therefore making only jammy carry an affected
  package.

  [ Test Plan ]

  To easily test this on a single machine, a test script is being
  provided to setup networking and dnsmasq configuration.

  # Launch a jammy VM

  lxc launch ubuntu-daily:jammy j-dnsmasq-2042587 --vm

  # open a root shell in that VM. All subsequent commands must be
  executed as root in that VM

  lxc shell j-dnsmasq-2042587

  # download test script

  wget
  
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+attachment/5738174/+files/setup-
  and-server.sh

  # make it executable

  chmod +x setup-and-server.sh

  # install dnsmasq. Ignore the postinst error (because systemd-resolved
  is also running and there is a port conflict)

  apt update && apt install dnsmasq -y

  # run the setup script. It will configure things and start dnsmasq
  ready to be tested

  ./setup-and-server.sh

  # in another root session inside the vm (so run "lxc shell
  j-dnsmasq-2042587" in another terminal), run the proposed commands
  from the setup script (and press ctrl-c after the result is shown):

  No DHCP relay:

    ip netns exec client dhclient -d -v p2

  The setup script should log an IP that is not a relay. For example:
  dnsmasq-dhcp: DHCPDISCOVER(p1) aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPOFFER(p1) 192.168.47.150 aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587
  ###
  IP = 192.168.47.150
  ###

  With DHCP relay set to 192.168.47.9, IP should NOT be that address:

    ip netns exec client dhclient -d -v p2 -g 192.168.47.9

  With the affected dnsmasq package, we will see an error:
  dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587
  ###
  IP = 192.168.47.9
  TEST FAILED
  ###

  The error is that the obtained IP is that of the dhcp relay (provided
  via the -g option).

  With the fixed dnsmasq package, "TEST FAILED" must not appear, and the
  IP should not be that of the provided dhcp relay.

  [ Where problems could occur ]

  If the fix is incorrect, it would mean the dhcp-script would get an incorrect 
IP again, or perhaps we could have crashes in dnsmasq when dealing with buffers 
and pointers if the dhcp-script option is in use.
  This fix was committed upstream a few months after the bug was introduced, so 
it took a while to be noticed.

  [ Other Info ]
  Not at this time.

  [ Original description ]

  When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
  stopped working in an environment where a DHCP relay is in use.
  Instead of the expected client IP address, the script gets the _relay_
  IP address as an argument. From dnsmasq documentation for --dhcp-
  script:

  > The arguments to the process are "add", "old" or "del", the MAC
  address of the host (or DUID for IPv6) , the IP address, and the
  hostname, if known.

  I believe the change has been inadverently made in upstream commit
  527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692
  
(https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f)
  as the commit message only speaks about inet_ntoa replacement and not
  the behavioral change it also introduces (previously the relay address
  was only set to the environment variable, now it effectively overrides
  the prevoiusly set client's IP address).

  dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04

To

[Touch-packages] [Bug 2045570] Autopkgtest regression report (dnsmasq/2.86-1.1ubuntu0.5)

All autopkgtests for the newly accepted dnsmasq (2.86-1.1ubuntu0.5) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/249.11-0ubuntu3.11 (ppc64el)


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

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

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

Title:
  dnsmasq crash when no servers in resolv.conf

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever
  the file is updated. When that happens and for some reason there were
  no "nameserver" declarations in the updated file, dnsmasq can crash.

  Here is a log of a reproducer:
  $ dig +short @127.0.0.1 ubuntu.com
  ;; communications error to 127.0.0.1#53: timed out
  ;; communications error to 127.0.0.1#53: connection refused
  ;; communications error to 127.0.0.1#53: connection refused
  ;; no servers could be reached

  We can see the startup, then when resolv.conf is read again and no 
nameservers were found, and the crash:
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: started, version 2.86 
cachesize 150
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: DNS service limited to local 
subnets
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: compile time options: IPv6 
GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth 
cryptohash DNSSEC loop-detect inotify dumpfile
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: reading /etc/resolv.conf
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: using nameserver 
10.0.100.1#53
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: read /etc/hosts - 7 addresses
  Jan 03 13:57:13 j-dnsmasq-2045570 systemd[1]: Started dnsmasq - A lightweight 
DHCP and caching DNS server.
  Jan 03 13:58:01 j-dnsmasq-2045570 dnsmasq[1507]: no servers found in 
/etc/resolv.conf, will retry
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process 
exited, code=dumped, status=11/SEGV
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with 
result 'core-dump'.

  dnsmasq has provisions for this situation, we can see that in the
  13:58:01 message where it says it will retry, but due to this bug, it
  crashes instead.

  The problem was introduced[1] in version 2.86, and fixed in 2.87, so
  only jammy is affected.

  1. 
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=patch;h=d290630d31f4517ab26392d00753d1397f9a4114;hp=d2ad5dc073aaacaf22b117f16106282a73586803
  The commit message says:
  """
  This problem was introduced in 2.86.
  """

  And indeed, I wasn't able to crash 2.80 shipped in focal.

  [ Test Plan ]
  It might take a few tries to reproduce the bug, but here is the general 
outline. Also keep in mind that it's important to use a DNS name that isn't 
cached already by a previous query.

  # Create a jammy lxd container

  lxc launch ubuntu-daily:jammy j-dnsmasq-2045570

  # Enter the container

  lxc shell j-dnsmasq-2045570

  # From now on, all commands should be executed in the container.
  # Install dnsmasq, and disable systemd-resolved

  apt update && apt install -y dnsmasq

  # Disable systemd-resolved, and start dnsmasq

  systemctl disable --now systemd-resolved
  systemctl enable --now dnsmasq

  # In one terminal inside the container, watch the dnsmasq logs:

  journalctl -u dnsmasq.service -f

  # In another terminal, remove /etc/resolv.conf and create a new one, empty
  rm /etc/resolv.conf
  echo "nameserver 1.1.1.1" > /etc/resolv.conf

  # restart dnsmasq
  systemctl restart dnsmasq.service

  # Perform a dns query

  dig @127.0.0.1 +short linux.com

  # Comment the namserver directive in resolv.conf
  echo "#nameserver 1.1.1.1" > /etc/resolv.conf

  # Observe in the dnsmasq logs that it notices the change with a
  message like:

  Jan 03 14:14:51 j-dnsmasq-2045570 dnsmasq[2274]: no servers found in
  /etc/resolv.conf, will retry

  # Perform a *different* DNS query

  dig @127.0.0.1 +short ubuntu.com

  # Observe in the dnsmasq logs that it crashes.
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process 
exited, code=dumped, status=11/SEGV
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with 
result 'core-dump'.

  If it doesn't crash right away, repeat these steps a few times, but using a 
different domain name each time:
  - add "nameserver 127.0.0.1" to /etc/resolv.conf
  - observe that dnsmasq notices the change to the file

[Touch-packages] [Bug 2041396] Re: gdb 12.1 generates SIGILL on armhf

2024-01-22 Thread Brian Murray

Given the current size of the queues that might take some time. Could
you run the test locally on the same device which you verified the fix
on?

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

Title:
  gdb 12.1 generates SIGILL on armhf

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

Bug description:
  [ Impact ]

   * GDB 12.1 introduced a regression where it will break program execution 
when the program contains mixed ARM code and THUMB code.
   * Upstream stated they tested the changes on Ubuntu 20.04 and it went okay.

  [ Test Plan ]

  Considering the following C program:

  ```
  __attribute__((target("arm"), noinline))
  int thumb_func() {
    return 42;
  }

  __attribute__((target("thumb")))
  int main() { return thumb_func(); }
  ```

  If you build it using `gcc repro.c -ggdb3 -Og -o repro` and run the
  GDB using the following commands ...

  ```
  b 3
  r
  c
  ```

  (you can save the contents above to a file and run GDB using `gdb -x
  script ./repro`)

  ... you will notice GDB broke the program and threw SIGILL.
  If you run the program without GDB, the program exits normally.

  [ Where problems could occur ]

   * GDB is a complex software. As the patch suggests, it may break other use 
cases (like single-stepping) entirely.
   * Since this is an ARM-only patch, it's unlikely to affect other CPU 
architectures. However, it is possible that this fix may break ARM64 execution.

  [ Other Info ]
   
   * This bug has been fixed in GDB 13, but the fix was never backported to GDB 
12. You can find the upstream bug in the remote bug watch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/2041396/+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 2018996] Re: whoopsie uses 100% CPU indefinitely on chrome crash file

2024-01-22 Thread Peter Cornelius

+1

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

Title:
  whoopsie uses 100% CPU indefinitely on chrome crash file

Status in whoopsie package in Ubuntu:
  New

Bug description:
  $@ lsb_release -rd
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04

  
  $@ apt-cache policy whoopsie
  whoopsie:
Installed: 0.2.77
Candidate: 0.2.77
Version table:
   *** 0.2.77 500
  500 http://jp.archive.ubuntu.com/ubuntu lunar/main amd64 Packages
  100 /var/lib/dpkg/status

  
  TL;DR whoopsie will happily consume 100% for hours in what seems like a 
pretty futile attempt to deal with massive crash files. It should be more aware 
of what is a realistic crash to upload.

  This has happened a couple of times today, so I searched, found

  https://askubuntu.com/questions/1245078/woopsie-upload-all-process-
  consumes-cpu-100/1296481#1296481

  which suggested looking in /var/crash/

  where I found

  $@ ls -lh /var/crash/
  total 8.3G
  -rw-r- 1 fergal   whoopsie 8.3G May  8 23:03 
_opt_google_chrome_chrome.1000.crash

  I don't know what whoopsie was doing but I doubt that was ever going
  to be productive and I cannot have a service that is going to
  occasionally use 100% CPU for hours.

  Here's what `top` had to say before I killed it

94802 root  20   0   11.7g  11.3g  58624 R 100.0  36.6 108:11.76
  whoopsie-upload

  So it had been trying for 108 minutes and was using 11G of RAM.

  I would love to enable crash reporting but this is unacceptable. I've
  deleted the crash file and uninstalled whoopsie. I'll happily
  reinstall it if it gains some safeguards against this kind of thing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/2018996/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable in noble

2024-01-22 Thread dann frazier

I ran into this on jammy/amd64:
https://autopkgtest.ubuntu.com/results/autopkgtest-
jammy/jammy/amd64/l/livecd-rootfs/20240121_173406_e4f9a@/log.gz

I downloaded all of the amd64 failures and searched for this failure
pattern. These were the kernels that were running at the time:

"Linux 5.15.0-91-generic #101-Ubuntu SMP Tue Nov 14 13:30:08 UTC 2023"
"Linux 6.2.0-21-generic #21-Ubuntu SMP PREEMPT_DYNAMIC Fri Apr 14 12:34:02 UTC 
2023"
"Linux 6.3.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Jun  8 16:02:30 UTC 
2023"
"Linux 6.5.0-9-generic #9-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct  7 01:35:40 UTC 
2023"
"Linux 6.6.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov 30 10:27:29 UTC 
2023"

Here's the count of failures per image type:
 12 017-disk-image-uefi.binary
  3 018-disk-image.binary
  3 020-kvm-image.binary
  1 023-vagrant.binary
  1 024-vagrant.binary

I can confirm that /dev/loop0p1 is created by devtmpfs. This surprised
me because I'd never actually need to know what devtmpfs was, and I saw
devices being created even though I had SIGSTOP'd systemd-udevd. But
watching udevadm monitor and forktrace output convinced me.

I had a theory that something was opening the first created partition before 
all partitions were created. loop_reread_partitions() can fail without 
returning an error to userspace:
 https://elixir.bootlin.com/linux/v5.15.147/source/drivers/block/loop.c#L676

that could happen if bdev_disk_changed() aborts because it finds another 
partition on the device is open:
 https://elixir.bootlin.com/linux/v5.15.147/source/block/partitions/core.c#L662

But then we should see this in dmesg:
  pr_warn("%s: partition scan of loop%d (%s) failed (rc=%d)\n"

I added dmesg calls to check that:
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-dannf-test/jammy/amd64/l/livecd-rootfs/20240122_161631_62ecd@/log.gz

.. but no such message appeared, so that's not it. But what *is*
interesting there is that it shows *2* partition scan lines:

1248s [  990.855361] loop0: detected capacity change from 0 to 4612096
1248s [  990.855628]  loop0: p1 p14 p15
1248s [  990.874241]  loop0: p1 p14 p15

Previously we just saw 1:

1189s [  932.268459] loop0: detected capacity change from 0 to 4612096
1189s [  932.268715]  loop0: p1 p14 p15

That only gets printed when bdev_disk_changed() is called. So do we have
2 racing callers?

One thing that seems off is that loop_configure() unsuppresses uevents
for the full device before the partition scan, but loop_change_fd()
waits until the partition scan is complete. Shouldn't they be following
the same pattern? I wonder if that could cause the following race:

[livecd-rootfs] losetup creates /dev/loop0
[livecd-rootfs] kernel sends uevent for /dev/loop0
[livecd-rootfs] /dev/loop0p* appear in devtmpfs
  [udev] receives uevent for loop0
  [udev] partprobe /dev/loop0
[livecd-rootfs] losetup exit(0)
  [partprobe] /dev/loop0p* cleared
[livecd-rootfs] check for /dev/loop0p1 FAILS
  [partprobe] /dev/loop0p* recreated

I tried checking for this using ftrace in a local jammy VM. I haven't been able 
to reproduce this in a local VM, but I wanted to see what happens in a normal 
losetup.. er... setup.
 
> First I used losetup to create the device:

root@dannf-livecd-rootfs-debug:/sys/kernel/debug/tracing# loopdev="$(losetup 
--show -f -P -v /home/ubuntu/disk.img)"
root@dannf-livecd-rootfs-debug:/sys/kernel/debug/tracing# cat trace
# tracer: function
#
# entries-in-buffer/entries-written: 1/1   #P:1
#
#_-=> irqs-off
#   / _=> need-resched
#  | / _---=> hardirq/softirq
#  || / _--=> preempt-depth
#  ||| / _-=> migrate-disable
#   / delay
#   TASK-PID CPU#  |  TIMESTAMP  FUNCTION
#  | | |   | | |
 losetup-1996[000] .   657.573994: bdev_disk_changed 
<-loop_reread_partitions

> Only the expected bdev_disk_change() call
> Then I remove the device:

root@dannf-livecd-rootfs-debug:/sys/kernel/debug/tracing# losetup -v -d $loopdev
root@dannf-livecd-rootfs-debug:/sys/kernel/debug/tracing# cat trace
# tracer: function
#
# entries-in-buffer/entries-written: 3/3   #P:1
#
#_-=> irqs-off
#   / _=> need-resched
#  | / _---=> hardirq/softirq
#  || / _--=> preempt-depth
#  ||| / _-=> migrate-disable
#   / delay
#   TASK-PID CPU#  |  TIMESTAMP  FUNCTION
#  | | |   | | |
 losetup-1996[000] .   657.573994: bdev_disk_changed 
<-loop_reread_partitions
   systemd-udevd-2524[000] .   680.555336: bdev_disk_changed 
<-blkdev_get_whole

[Touch-packages] [Bug 566381] Re: Lag when using module-loopback

2024-01-22 Thread I. T. Pohjalainen

Still exists in Ubuntu 22.04.3 LTS. Measured exactly 148 ms delay with
wired headphones and an usb microphone.

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

Title:
  Lag when using module-loopback

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: pulseaudio

  Using
  pactl load-module module-loopback
  I can route the mic input through output. However, the audio that comes out 
is about half a second behind the audio coming in. This is okay for some 
things, but for others, like musical instruments, game consoles, etc., the lag 
makes it pretty much unusable for these uses.
  Back in alsa this used to work fine without lag.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
  Uname: Linux 2.6.32-19-generic x86_64
  NonfreeKernelModules: nls_iso8859_1 nls_cp437 btrfs zlib_deflate crc32c 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs vfat msdos fat jfs xfs exportfs 
reiserfs pata_jmicron acpiphp michael_mic arc4 hidp rfcomm binfmt_misc sco 
bridge stp bnep l2cap vboxnetadp vboxnetflt dm_crypt snd_hda_codec_idt 
snd_hda_codec_intelhdmi snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss 
snd_mixer_oss snd_pcm snd_seq_dummy snd_seq_oss snd_seq_midi vboxdrv 
snd_rawmidi joydev snd_seq_midi_event lp snd_seq snd_timer snd_seq_device 
lib80211_crypt_tkip snd parport soundcore wl dell_wmi btusb psmouse dell_laptop 
dcdbas ricoh_mmc snd_page_alloc lib80211 sdhci_pci sdhci led_class serio_raw 
bluetooth dm_raid45 xor fbcon tileblit font bitblit softcursor vga16fb vgastate 
usbhid hid i915 drm_kms_helper ohci1394 drm i2c_algo_bit ieee1394 sky2 
intel_agp ahci video output
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 0/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  matthew   10508 F pulseaudio
   /dev/snd/pcmC0D0c:   matthew   10508 F...m pulseaudio
   /dev/snd/pcmC0D0p:   matthew   10508 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xfe9fc000 irq 21'
 Mixer name : 'SigmaTel STAC9228'
 Components : 'HDA:14f12c06,14f1000f,0010 
HDA:10951392,1028022f,0010 HDA:83847616,1028022f,00100402'
 Controls  : 23
 Simple ctrls  : 12
  Date: Sun Apr 18 21:42:33 2010
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  dmi.bios.date: 03/10/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A11
  dmi.board.name: 0U990C
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd03/10/2008:svnDellInc.:pnInspiron1525:pvr:rvnDellInc.:rn0U990C:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Inspiron 1525
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/566381/+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 2047939] Re: Let tzdata not recommend tzdata-icu

2024-01-22 Thread Simon Déziel

@bdrung, I just noticed this package is now in universe in Noble. Is the
demotion related to this bug?

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

Title:
  Let tzdata not recommend tzdata-icu

Status in tzdata package in Ubuntu:
  Fix Released

Bug description:
  tzdata-icu was split out of tzdata in 2022g-7ubuntu1 in lunar. Stop
  letting tzdata recommend tzdata-icu. All packages that need the files
  in /usr/share/zoneinfo-icu should directly depend on tzdata-icu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2047939/+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 2045455] Re: add-apt-repository crashed with --- in _request()

2024-01-22 Thread Brian Murray

** Information type changed from Private to Public

** Changed in: software-properties (Ubuntu)
Milestone: None => ubuntu-24.04-beta

** Tags added: rls-nn-incoming

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Error encountered during first boot after installing ubuntu-unity-
  desktop on Live Server 24.04 Daily Build.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Nov 30 02:20:48 2023
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2023-11-30 (2 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily amd64 (20231129)
  InterpreterPath: /usr/bin/python3.11
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2045455/+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 2032910] Re: 60x11-common_xdg_path sets wrong XDG_DATA_DIRS on Plasma

2024-01-22 Thread Ken Sharp

** Tags added: jammy

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

Title:
  60x11-common_xdg_path sets wrong XDG_DATA_DIRS on Plasma

Status in xorg package in Ubuntu:
  New

Bug description:
  XDG_DATA_DIRS shouldn't include /usr/share/plasma by default.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  22.04
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  1:7.7+23ubuntu2
  3) What you expected to happen
  XDG_DATA_DIRS shouldn't include /usr/share/plasma

  4) What happened instead
  XDG_DATA_DIRS includes /usr/share/plasma

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2032910/+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 2009145] Re: Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

2024-01-22 Thread Ken Sharp

Is there actually something to do here for xorg?

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

Title:
  Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

Status in xorg package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17

  The dbus-x11 package is being deprecated. As a result, the Xfce
  packages from upstream Debian no longer pull it in. Until the xorg
  packages have been updated accordingly in Ubuntu, the Xubuntu settings
  found in /etc/xdg/xdg-xubuntu are ignored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2009145/+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 2050805] [NEW] brightness

2024-01-22 Thread yassyn bennani

Public bug reported:

hi , i can't change my brightness it s blocked on max even if i us fn+f9
it show the bar of brightness changing but not the brightness in my
screen

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 22 19:36:53 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Hewlett-Packard Company GF106GLM [Quadro 2000M] [103c:1631]
InstallationDate: Installed on 2024-01-16 (6 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: Hewlett-Packard HP EliteBook 8560w
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=a21fb944-4d22-4f82-b6f9-85577ca2ec3d ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/05/2012
dmi.bios.release: 15.34
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SVD Ver. F.22
dmi.board.name: 1631
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 01.39
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.ec.firmware.release: 1.57
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.22:bd01/05/2012:br15.34:efr1.57:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.39:cvnHewlett-Packard:ct10:cvr:skuWX563AV:
dmi.product.family: 103C_5336AN
dmi.product.name: HP EliteBook 8560w
dmi.product.sku: WX563AV
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session

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

Title:
  brightness

Status in xorg package in Ubuntu:
  New

Bug description:
  hi , i can't change my brightness it s blocked on max even if i us
  fn+f9 it show the bar of brightness changing but not the brightness in
  my screen

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 22 19:36:53 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GF106GLM [Quadro 2000M] [10de:0dda] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Hewlett-Packard Company GF106GLM [Quadro 2000M] [103c:1631]
  InstallationDate: Installed on 2024-01-16 (6 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Hewlett-Packard HP EliteBook 8560w
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=a21fb944-4d22-4f82-b6f9-85577ca2ec3d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/05/2012
  dmi.bios.release: 15.34
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SVD Ver. F.22
  dmi.board.name: 1631
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 01.39
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.ec.firmware.release: 1.57
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SVDVer.F.22:bd01/05/2012:br15.34:efr1.57:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.39:cvnHewlett-Packard:ct10:cvr:skuWX563AV:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8560w
  dmi.product.sku: WX563AV
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard

[Touch-packages] [Bug 2030684] Re: tzname[1] empty after tzset() with env TZ="UTC"

2024-01-22 Thread Sergio Durigan Junior

postgresql-15 has been Fix Released a while ago.  Marking the task
accordingly.

** Changed in: postgresql-15 (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/2030684

Title:
  tzname[1] empty after tzset() with env TZ="UTC"

Status in django-mailman3 package in Ubuntu:
  Fix Released
Status in php8.2 package in Ubuntu:
  Triaged
Status in postgresql-15 package in Ubuntu:
  Fix Released
Status in python-django package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in tzdata package in Ubuntu:
  Fix Released
Status in tzdata package in Debian:
  Fix Released

Bug description:
  The following program prints different output when run with tzdata
  2023c-7ubuntu1 from mantic, versus tzdata 2023c-8ubuntu1 from mantic-
  proposed:

  root@mantic:~# cat bug.c 
  #include 
  #include 
  #include 
  #include 
  #include 

  int main(void) {
  int r;

  r = setenv("TZ", ":UTC", 1);
  if (r < 0) {
  printf("Failed to set TZ env var: %s\n", strerror(errno));
  return 1;
  }

  tzset();

  printf("timezone = %lu, daylight = %d\n", timezone, daylight);
  printf("tzname[0] = %s, tzname[1] = %s\n", tzname[0], tzname[1]);
  }

  root@mantic:~# gcc bug.c
  root@mantic:~# ./a.out 
  timezone = 0, daylight = 0
  tzname[0] = UTC, tzname[1] = UTC
  root@mantic:~# apt-cache policy tzdata
  tzdata:
Installed: 2023c-7ubuntu1
Candidate: 2023c-7ubuntu1
Version table:
   *** 2023c-7ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu mantic/main amd64 Packages
  100 /var/lib/dpkg/status

  If I install tzdata from mantic-proposed, I get different output:

  root@mantic:~# vi /etc/apt/sources.list
  root@mantic:~# apt update && apt install tzdata
  Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease
  Hit:2 http://security.ubuntu.com/ubuntu mantic-security InRelease
  Get:3 http://archive.ubuntu.com/ubuntu mantic-proposed InRelease [118 kB]
  Hit:4 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
  Hit:5 http://archive.ubuntu.com/ubuntu mantic-backports InRelease
  Get:6 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 Packages 
[35.9 kB]
  Get:7 http://archive.ubuntu.com/ubuntu mantic-proposed/main Translation-en 
[14.8 kB]
  Get:8 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 DEP-11 
Metadata [2376 B]
  Get:9 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 c-n-f 
Metadata [1004 B]
  Get:10 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted amd64 
Packages [15.9 kB]
  Get:11 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted 
Translation-en [3564 B]
  Get:12 http://archive.ubuntu.com/ubuntu mantic-proposed/restricted amd64 
c-n-f Metadata [336 B]
  Fetched 192 kB in 1s (324 kB/s) 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  72 packages can be upgraded. Run 'apt list --upgradable' to see them.
  root@mantic:~# apt install tzdata=2023c-8ubuntu1
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  The following packages were automatically installed and are no longer 
required:
libefiboot1 libefivar1
  Use 'apt autoremove' to remove them.
  The following packages will be upgraded:
tzdata
  1 upgraded, 0 newly installed, 0 to remove and 72 not upgraded.
  Need to get 269 kB of archives.
  After this operation, 142 kB disk space will be freed.
  Get:1 http://archive.ubuntu.com/ubuntu mantic-proposed/main amd64 tzdata all 
2023c-8ubuntu1 [269 kB]
  Fetched 269 kB in 0s (867 kB/s)
  Preconfiguring packages ...
  (Reading database ... 39935 files and directories currently installed.)
  Preparing to unpack .../tzdata_2023c-8ubuntu1_all.deb ...
  Unpacking tzdata (2023c-8ubuntu1) over (2023c-7ubuntu1) ...
  Setting up tzdata (2023c-8ubuntu1) ...

  Current default time zone: 'Etc/UTC'
  Local time is now:  Mon Aug  7 21:18:35 UTC 2023.
  Universal Time is now:  Mon Aug  7 21:18:35 UTC 2023.
  Run 'dpkg-reconfigure tzdata' if you wish to change it.

  Scanning processes... 


 
  Scanning candidates...


 

  Restarting services...
  Service restarts being deferred:
   systemctl restart systemd-logind.service
   systemctl restart unattended-upgrades.service

  No containers need

[Touch-packages] [Bug 2041700] Re: release upgrade to 23.04 failed on Odroid N2+

** Tags removed: need-duplicate-check

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

Title:
  release upgrade to 23.04 failed on  Odroid N2+

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  Failure during release upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: python3 3.11.2-1
  Uname: Linux 5.15.0-odroid-arm64 aarch64
  ApportVersion: 2.26.1-0ubuntu2.1
  AptOrdering: NULL: ConfigurePending
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudBuildName: server
  CloudSerial: 20220423
  Date: Fri Oct 27 22:58:30 2023
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: python3-defaults
  Title: package python3 3.11.2-1 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to lunar on 2023-10-27 (0 days ago)
  modified.conffile..etc.apport.report-ignore.README.denylist: [deleted]
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2022-06-28T20:42:18.309253

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/2041700/+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 2042756] Re: package systemd 252.5-2ubuntu3.2 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package systemd 252.5-2ubuntu3.2 failed to install/upgrade: installed
  systemd package post-installation script subprocess returned error
  exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  I encountered the following while upgrading to lunar, which asked me to file 
here:
  ```
  /etc/gshadow: Group "nogroup" already exists.
  dpkg: error processing package systemd (--configure):
   installed systemd package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   systemd
  needrestart is being skipped since dpkg has failed
  packages have been installed but needrestart is suspended
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/systemd.0.crash'
  packages have been installed but needrestart is suspended
  Exception during pm.DoInstall():  E:Sub-process /usr/bin/dpkg returned an 
error code (1)
  ```

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: systemd 252.5-2ubuntu3.2
  ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Sun Nov  5 04:08:26 2023
  ErrorMessage: installed systemd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-10-19 (16 days ago)
  InstallationMedia: Ubuntu-Server 22.04.2 LTS "Jammy Jellyfish" - Release 
amd64 (20230217.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:3004 Qualcomm Atheros Communications AR3012 
Bluetooth 4.0
   Bus 001 Device 003: ID 0403:6001 Future Technology Devices International, 
Ltd FT232 Serial (UART) IC
   Bus 001 Device 004: ID 413c:2107 Dell Computer Corp. KB212-B Quiet Key 
Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Protectli VP4650
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-88-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  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.10
  SourcePackage: systemd
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Title: package systemd 252.5-2ubuntu3.2 failed to install/upgrade: installed 
systemd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2023-11-05 (0 days ago)
  dmi.bios.date: 12/08/2022
  dmi.bios.release: 1.0
  dmi.bios.vendor: 3mdeb
  dmi.bios.version: Dasharo (coreboot+UEFI) v1.0.19
  dmi.board.name: VP4650
  dmi.board.vendor: Protectli
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Protectli
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvn3mdeb:bvrDasharo(coreboot+UEFI)v1.0.19:bd12/08/2022:br1.0:efr0.0:svnProtectli:pnVP4650:pvr1.0:rvnProtectli:rnVP4650:rvr1.0:cvnProtectli:ct3:cvr:sku:
  dmi.product.family: Vault Pro
  dmi.product.name: VP4650
  dmi.product.version: 1.0
  dmi.sys.vendor: Protectli

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2042756/+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 2042825] Re: package udev 245.4-4ubuntu3.22 failed to install/upgrade: installed udev package post-installation script subprocess returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package udev 245.4-4ubuntu3.22 failed to install/upgrade: installed
  udev package post-installation script subprocess returned error exit
  status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  After updating the system, I get this error

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: udev 245.4-4ubuntu3.22
  ProcVersionSignature: Ubuntu 5.4.0-166.183-generic 5.4.252
  Uname: Linux 5.4.0-166-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules 
70-snap.gnome-calculator.rules 70-snap.zoom-client.rules 
70-snap.gnome-logs.rules 70-snap.firefox.rules 70-snap.slack.rules 
70-snap.gnome-system-monitor.rules
  Date: Wed Nov  1 20:35:58 2023
  ErrorMessage: installed udev package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2019-09-13 (1514 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Dell Inc. Latitude 5501
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-166-generic 
root=UUID=58414a1c-8bb9-4e71-a6db-e40231eeb7e0 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-minimal, 2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: systemd
  Title: package udev 245.4-4ubuntu3.22 failed to install/upgrade: installed 
udev package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/05/2023
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.26.0
  dmi.board.name: 0Y8H01
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.26.0:bd07/05/2023:svnDellInc.:pnLatitude5501:pvr:rvnDellInc.:rn0Y8H01:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5501
  dmi.product.sku: 0919
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2042825/+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 2043753] Re: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-installable with libnih1 which

** Tags removed: need-duplicate-check

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

Title:
  package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package
  libnih1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not co-
  installable with libnih1 which has multiple installed instances

Status in libnih package in Ubuntu:
  New

Bug description:
  was installing upgrade to ubuntu 20.04 and system reported crash.  no
  visible signs other the message appeared.  Upgrade continued for a
  while and then terminated.  I had libreoffice writer open at the time
  of the error.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libnih1 1.0.3-6ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-166.183-generic 5.4.252
  Uname: Linux 5.4.0-166-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 16 20:23:24 2023
  DuplicateSignature:
   package:libnih1:1.0.3-6ubuntu2
   Unpacking libnetpbm10 (2:10.0-15.4) over (2:10.0-15.3build1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-eWw3bF/0718-libnih-dbus1_1.0.3-12build1_amd64.deb 
(--unpack):
package libnih-dbus1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is 
not co-installable with libnih-dbus1 which has multiple installed instances
  ErrorMessage: package libnih1:amd64 (1.0.3-12build1) with field 'Multi-Arch: 
no' is not co-installable with libnih1 which has multiple installed instances
  InstallationDate: Installed on 2014-04-03 (3514 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  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: libnih
  Title: package libnih1 1.0.3-6ubuntu2 failed to install/upgrade: package 
libnih1:amd64 (1.0.3-12build1) with field 'Multi-Arch: no' is not 
co-installable with libnih1 which has multiple installed instances
  UpgradeStatus: Upgraded to jammy on 2023-11-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/2043753/+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 2046346] Re: add-apt-repository crashed with --- in _request()

*** This bug is a duplicate of bug 2045455 ***
https://bugs.launchpad.net/bugs/2045455

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2045455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2046346/+attachment/5728885/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2046346/+attachment/5728886/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2045455

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Error occurred after installation of Unity Daily Build 24.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Wed Dec 13 05:10:30 2023
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2023-12-13 (0 days ago)
  InstallationMedia: Ubuntu-Unity 24.04 LTS "Noble Numbat" - Daily amd64 
(20231212)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors: -- No entries --
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=C.UTF-8
   LANGUAGE=en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2046346/+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 2046856] Re: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status

** Tags removed: need-duplicate-check

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

Title:
  package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade:
  installed systemd-resolved package post-installation script subprocess
  returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
   Issue in upgrade of version, more details to be added

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: systemd-resolved 252.5-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-39.40-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudBuildName: server
  CloudID: configdrive
  CloudName: configdrive
  CloudPlatform: configdrive
  CloudSerial: 20221022
  CloudSubPlatform: config-disk (/dev/vdb)
  Date: Tue Dec 19 01:45:42 2023
  ErrorMessage: installed systemd-resolved package post-installation script 
subprocess returned error exit status 1
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: systemd
  Title: package systemd-resolved 252.5-2ubuntu3 failed to install/upgrade: 
installed systemd-resolved package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to lunar on 2023-12-19 (0 days ago)
  mtime.conffile..etc.systemd.resolved.conf: 2023-08-25T21:57:40.440350

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

** Tags removed: need-duplicate-check

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

Title:
  package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade:
  installed systemd-resolved package post-installation script subprocess
  returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  upgraded from 22.04 -> 24.04

  ProblemType: Package
  DistroRelease: Ubuntu 24.04
  Package: systemd-resolved 253.5-1ubuntu7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Wed Jan  3 21:06:55 2024
  ErrorMessage: installed systemd-resolved package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-02-27 (311 days ago)
  InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release 
amd64 (20220809)
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.1ubuntu5
   apt  2.7.6
  SourcePackage: systemd
  Title: package systemd-resolved 253.5-1ubuntu7 failed to install/upgrade: 
installed systemd-resolved package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to noble on 2024-01-03 (0 days ago)
  mtime.conffile..etc.systemd.resolved.conf: 2023-02-27T21:16:55.869158

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2047975/+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 2048497] Re: add-apt-repository crashed with --- in _request()

*** This bug is a duplicate of bug 2045455 ***
https://bugs.launchpad.net/bugs/2045455

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2045455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2048497/+attachment/5737315/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2048497/+attachment/5737316/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2045455

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Crash occurred during first boot after install ubunutu-desktop on Live
  Server 24.04 Daily.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  Uname: Linux 6.6.10-060610-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Jan  7 13:33:09 2024
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2024-01-07 (1 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 
(20240107)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors: -- No entries --
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2048497/+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 2049958] Re: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/bluetooth/obexd' before installing new version: Input/output er

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

** Tags removed: need-duplicate-check

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

Title:
  package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to
  make backup link of './usr/lib/bluetooth/obexd' before installing new
  version: Input/output error

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  bug found during software update launched from bootable usb

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: bluez-obexd 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckMismatches: ./casper/minimal.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  Date: Sat Jan 20 00:18:32 2024
  DuplicateSignature:
   package:bluez-obexd:5.68-0ubuntu1
   Unpacking bluez-obexd (5.68-0ubuntu1.1) over (5.68-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-MsVzUs/045-bluez-obexd_5.68-0ubuntu1.1_amd64.deb 
(--unpack):
unable to make backup link of './usr/lib/bluetooth/obexd' before installing 
new version: Input/output error
  ErrorMessage: unable to make backup link of './usr/lib/bluetooth/obexd' 
before installing new version: Input/output error
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: bluez
  Title: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to 
make backup link of './usr/lib/bluetooth/obexd' before installing new version: 
Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 306
  dmi.board.asset.tag: Default string
  dmi.board.name: GL553VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr306:bd09/26/2018:br5.6:svnASUSTeKCOMPUTERINC.:pnGL553VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: GL
  dmi.product.name: GL553VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:57:7B:12:13:2F  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:1345 acl:0 sco:0 events:90 errors:0
TX bytes:3835 acl:0 sco:0 commands:90 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2049958/+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 2040017] Re: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is dif

** Tags removed: need-duplicate-check

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

Title:
  package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade:
  trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-
  default.conf.example', which is different from other instances of
  package libasound2-plugins:i386

Status in alsa-plugins package in Ubuntu:
  Confirmed

Bug description:
  I dont know much about

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: libasound2-plugins 1.2.7.1-1ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Oct 21 02:05:11 2023
  DuplicateSignature:
   package:libasound2-plugins:1.2.7.1-1ubuntu2
   Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-KQ6wMx/50-libasound2-plugins_1.2.7.1-1ubuntu2_i386.deb 
(--unpack):
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  ErrorMessage: trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  InstallationDate: Installed on 2022-12-23 (301 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: alsa-plugins
  Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: 
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  UpgradeStatus: Upgraded to mantic on 2023-10-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/2040017/+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 2043165] Re: add-apt-repository crashed with --- in _request()

*** This bug is a duplicate of bug 2045455 ***
https://bugs.launchpad.net/bugs/2045455

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2045455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2043165/+attachment/5717728/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2043165/+attachment/5717729/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2045455

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Crash after first boot following installation of ubuntu-gnome-desktop
  on Ubuntu Live Server Daily Build 24.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Nov  8 12:10:34 2023
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2023-11-08 (2 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily amd64 (20231108)
  InterpreterPath: /usr/bin/python3.11
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2043165/+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 2044038] Re: package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

** Tags removed: need-duplicate-check

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

Title:
  package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-
  deb --control subprocess returned error exit status 2

Status in libx11 package in Ubuntu:
  New

Bug description:
  While updating

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libx11-6 2:1.6.9-2ubuntu1.2
  ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Nov 20 22:14:16 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libx11-6:2:1.6.9-2ubuntu1.2
   Unpacking cups-filters-core-drivers (1.27.4-1ubuntu0.2) over (1.27.4-1) ...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb' is 
not a Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb 
(--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems UHD Graphics 630 (Desktop 9 Series) 
[1019:a55d]
  InstallationDate: Installed on 2023-11-21 (0 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1c4f:0034 SiGma Micro Usb Mouse
   Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 001 Device 002: ID 046d:0825 Logitech, Inc. Webcam C270
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: EXO Ready C2 - Style C2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic 
root=UUID=e1ccedca-0d59-4553-a2e6-566868da99ab ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.10
  SourcePackage: libx11
  Title: package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Default string
  dmi.board.name: H310CH5-M2
  dmi.board.vendor: EXO
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: EXO
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd08/02/2019:br5.12:svnEXO:pnReadyC2-StyleC2:pvr1.0:rvnEXO:rnH310CH5-M2:rvr1.0:cvnEXO:ct3:cvr1.0:sku3629:
  dmi.product.family: Ready - Style
  dmi.product.name: Ready C2 - Style C2
  dmi.product.sku: 3629
  dmi.product.version: 1.0
  dmi.sys.vendor: EXO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/2044038/+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 2044040] Re: package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

*** This bug is a duplicate of bug 2044038 ***
https://bugs.launchpad.net/bugs/2044038

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2044038, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** This bug has been marked a duplicate of bug 2044038
   package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-deb 
--control subprocess returned error exit status 2

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

Title:
  package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-
  deb --control subprocess returned error exit status 2

Status in libx11 package in Ubuntu:
  New

Bug description:
  bugs while updating

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libx11-6 2:1.6.9-2ubuntu1.6
  ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Nov 20 22:14:16 2023
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libx11-6:2:1.6.9-2ubuntu1.2
   Unpacking cups-filters-core-drivers (1.27.4-1ubuntu0.2) over (1.27.4-1) ...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb' is 
not a Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb 
(--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems UHD Graphics 630 (Desktop 9 Series) 
[1019:a55d]
  InstallationDate: Installed on 2023-11-21 (0 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 1c4f:0034 SiGma Micro Usb Mouse
   Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory
   Bus 001 Device 002: ID 046d:0825 Logitech, Inc. Webcam C270
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: EXO Ready C2 - Style C2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic 
root=UUID=e1ccedca-0d59-4553-a2e6-566868da99ab ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.10
  SourcePackage: libx11
  Title: package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 5.12
  dmi.board.asset.tag: Default string
  dmi.board.name: H310CH5-M2
  dmi.board.vendor: EXO
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: EXO
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd08/02/2019:br5.12:svnEXO:pnReadyC2-StyleC2:pvr1.0:rvnEXO:rnH310CH5-M2:rvr1.0:cvnEXO:ct3:cvr1.0:sku3629:
  dmi.product.family: Ready - Style
  dmi.product.name: Ready C2 - Style C2
  dmi.product.sku: 3629
  dmi.product.version: 1.0
  dmi.sys.vendor: EXO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/2044040/+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 2044039] Re: package libavahi-glib1 0.7-4ubuntu7.1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

** Tags removed: need-duplicate-check

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

Title:
  package libavahi-glib1 0.7-4ubuntu7.1 failed to install/upgrade: dpkg-
  deb --control subprocess returned error exit status 2

Status in avahi package in Ubuntu:
  New

Bug description:
  While updating

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libavahi-glib1 0.7-4ubuntu7.1
  ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
  Uname: Linux 5.15.0-88-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Nov 20 22:14:13 2023
  DuplicateSignature:
   package:libavahi-glib1:0.7-4ubuntu7.1
   Unpacking cups-filters-core-drivers (1.27.4-1ubuntu0.2) over (1.27.4-1) ...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb' is 
not a Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb 
(--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  InstallationDate: Installed on 2023-11-21 (0 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.10
  SourcePackage: avahi
  Title: package libavahi-glib1 0.7-4ubuntu7.1 failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/2044039/+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 2045088] Re: package perl-modules-5.34 5.34.0-3ubuntu1.2 failed to install/upgrade: unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not permitted

** Tags removed: need-duplicate-check

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

Title:
  package perl-modules-5.34 5.34.0-3ubuntu1.2 failed to install/upgrade:
  unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new':
  Operation not permitted

Status in perl package in Ubuntu:
  New

Bug description:
  I was trying to exit Mozilla Thunderbird.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: perl-modules-5.34 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Nov 28 06:27:18 2023
  DpkgTerminalLog:
   Preparing to unpack .../perl-modules-5.34_5.34.0-3ubuntu1.3_all.deb ...
   Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.3) over (5.34.0-3ubuntu1.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/perl-modules-5.34_5.34.0-3ubuntu1.3_all.deb (--unpack):
unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not 
permitted
  DuplicateSignature:
   package:perl-modules-5.34:5.34.0-3ubuntu1.2
   Unpacking perl-modules-5.34 (5.34.0-3ubuntu1.3) over (5.34.0-3ubuntu1.2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/perl-modules-5.34_5.34.0-3ubuntu1.3_all.deb (--unpack):
unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not 
permitted
  ErrorMessage: unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': 
Operation not permitted
  InstallationDate: Installed on 2018-05-17 (2021 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: perl
  Title: package perl-modules-5.34 5.34.0-3ubuntu1.2 failed to install/upgrade: 
unable to open '/usr/share/perl/5.34.0/warnings.pm.dpkg-new': Operation not 
permitted
  UpgradeStatus: Upgraded to jammy on 2022-08-13 (472 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/perl/+bug/2045088/+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 2046646] Re: package fwupd 1.7.9-1~22.04.3 failed to install/upgrade: installed fwupd package post-installation script subprocess returned error exit status 127

** Tags removed: need-duplicate-check

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

Title:
  package fwupd 1.7.9-1~22.04.3 failed to install/upgrade: installed
  fwupd package post-installation script subprocess returned error exit
  status 127

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  i don't know lol

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: fwupd 1.7.9-1~22.04.3
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Dec 17 12:15:28 2023
  DuplicateSignature:
   package:fwupd:1.7.9-1~22.04.3
   Setting up linux-firmware (20220329.git681281e4-0ubuntu3.23) ...
   /usr/sbin/update-initramfs: 175: awk: Too many levels of symbolic links
   dpkg: error processing package linux-firmware (--configure):
installed linux-firmware package post-installation script subprocess 
returned error exit status 127
  ErrorMessage: installed fwupd package post-installation script subprocess 
returned error exit status 127
  InstallationDate: Installed on 2023-12-16 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  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: fwupd
  Title: package fwupd 1.7.9-1~22.04.3 failed to install/upgrade: installed 
fwupd package post-installation script subprocess returned error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2046646/+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 2047268] Re: package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-boot package post-installation script subprocess returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade:
  installed systemd-boot package post-installation script subprocess
  returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade:
  installed systemd-boot package post-installation script subprocess
  returned error exit status 1

  
  upgraded stuff through sudo ap-get and it gave me this error, i was also 
copying music and browsing the web at the time

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: systemd-boot 253.5-1ubuntu6.1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CloudArchitecture: x86_64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Fri Dec 22 15:58:01 2023
  DuplicateSignature:
   package:systemd-boot:253.5-1ubuntu6.1
   Setting up systemd-boot (253.5-1ubuntu6.1) ...
   dpkg: error processing package systemd-boot (--configure):
installed systemd-boot package post-installation script subprocess returned 
error exit status 1
  ErrorMessage: installed systemd-boot package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-12-20 (2 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: systemd
  Title: package systemd-boot 253.5-1ubuntu6.1 failed to install/upgrade: 
installed systemd-boot 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/systemd/+bug/2047268/+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 2047719] Re: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: new slapd package pre-installation script subprocess returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: new
  slapd package pre-installation script subprocess returned error exit
  status 1

Status in openldap package in Ubuntu:
  Incomplete

Bug description:
  Happened while upgrading ubuntu distro

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: slapd 2.4.49+dfsg-2ubuntu1.9
  ProcVersionSignature: Ubuntu 5.15.0-1053.61~20.04.1-azure 5.15.131
  Uname: Linux 5.15.0-1053-azure x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Fri Dec 29 23:55:31 2023
  ErrorMessage: new slapd package pre-installation script subprocess returned 
error exit status 1
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.15.0-1053-azure 
root=UUID=b9df59e6-c806-4851-befa-12402bca5828 ro console=tty1 console=ttyS0 
earlyprintk=ttyS0 rootdelay=300
  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: openldap
  Title: package slapd 2.4.49+dfsg-2ubuntu1.9 failed to install/upgrade: new 
slapd package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to jammy on 2023-12-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2047719/+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 2047664] Re: add-apt-repository crashed with --- in _request()

*** This bug is a duplicate of bug 2045455 ***
https://bugs.launchpad.net/bugs/2045455

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2045455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2047664/+attachment/5734193/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2047664/+attachment/5734194/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2045455

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Crash occured during first boot after installing ubuntu-unity-desktop
  on Liver Server 24.04 Daily.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  Uname: Linux 6.6.8-060608-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Dec 27 10:29:54 2023
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2023-12-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 
(20231226)
  InterpreterPath: /usr/bin/python3.11
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2047664/+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 2047782] Re: add-apt-repository crashed with --- in _request()

*** This bug is a duplicate of bug 2045455 ***
https://bugs.launchpad.net/bugs/2045455

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2045455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2047782/+attachment/5735059/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2047782/+attachment/5735060/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2045455

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Error occurred during first boot after install ubuntu-gnome-desktop on
  Ubuntu Live Server 24.04 Daily.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  Uname: Linux 6.6.8-060608-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon Jan  1 10:10:18 2024
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2024-01-01 (1 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 
(20240101)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors: -- No entries --
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2047782/+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 2048765] Re: package isc-dhcp-server 4.4.1-2.1ubuntu5.20.04.5 failed to install/upgrade: installed isc-dhcp-server package post-installation script subprocess returned error exit

** Tags removed: need-duplicate-check

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

Title:
  package isc-dhcp-server 4.4.1-2.1ubuntu5.20.04.5 failed to
  install/upgrade: installed isc-dhcp-server package post-installation
  script subprocess returned error exit status 127

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Failed when upgrading from 18.04 to 20.04

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: isc-dhcp-server 4.4.1-2.1ubuntu5.20.04.5
  ProcVersionSignature: Ubuntu 5.4.0-169.187~18.04.1-generic 5.4.257
  Uname: Linux 5.4.0-169-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jan  9 10:47:15 2024
  ErrorMessage: installed isc-dhcp-server package post-installation script 
subprocess returned error exit status 127
  InstallationDate: Installed on 2022-05-12 (606 days ago)
  InstallationMedia: Ubuntu-Server 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-169-generic 
root=UUID=905b71bd-9ca7-4f37-9b80-a766904e5fae ro usbcore.autosuspend=-1 
ipv6.disable=1 usb-storage.quirks=174c:55aa:u ipv6.disable=1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  SourcePackage: isc-dhcp
  Title: package isc-dhcp-server 4.4.1-2.1ubuntu5.20.04.5 failed to 
install/upgrade: installed isc-dhcp-server package post-installation script 
subprocess returned error exit status 127
  UpgradeStatus: Upgraded to focal on 2024-01-09 (0 days ago)
  mtime.conffile..etc.dhcp.dhcpd.conf: 2023-02-26T22:46:30.427609

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/2048765/+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 2049291] Re: add-apt-repository crashed with --- in _request()

*** This bug is a duplicate of bug 2045455 ***
https://bugs.launchpad.net/bugs/2045455

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2045455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2049291/+attachment/5739117/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2049291/+attachment/5739118/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2045455

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Error occured during first boot after installing Ubuntu Unity Daily
  24.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  Uname: Linux 6.7.0-060700-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Jan 13 20:37:52 2024
  ExecutablePath: /usr/bin/add-apt-repository
  ExecutableTimestamp: 1698150052
  InstallationDate: Installed on 2024-01-14 (0 days ago)
  InstallationMedia: Ubuntu-Unity 24.04 LTS "Noble Numbat" - Daily amd64 
(20240112)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors: -- No entries --
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcCwd: /home/gene
  ProcEnviron:
   LANG=C.UTF-8
   LANGUAGE=en
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2049291/+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 2039371] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Termin

** Tags removed: need-duplicate-check

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

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  was killed by signal (Terminated)

Status in network-manager package in Ubuntu:
  New

Bug description:
  With do-release-upgrade -d, Setting up network-manager hanged
  indefinitely with

  [...]
  Setting up network-manager (1.44.2-1ubuntu1) ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  ^[[CSKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  [...]

  Killing it resulted in

  Terminated
  SKIP: NetworkManager is not ready ...
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess was 
killed by signal (Terminated)

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sun Oct 15 00:40:40 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2023-01-13 (274 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  IpRoute:
   default via 192.168.0.254 dev wlp2s0 proto dhcp src 192.168.0.29 metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.29 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: network-manager
  Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: 
installed network-manager package post-installation script subprocess was 
killed by signal (Terminated)
  UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  starting  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039371/+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 2043953] Re: add-apt-repository crashed with --- in _request()

*** This bug is a duplicate of bug 2045455 ***
https://bugs.launchpad.net/bugs/2045455

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2045455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2043953/+attachment/5721094/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2043953/+attachment/5721095/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2045455

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Error occured after first boot following installing unity-desktop on
  Ubuntu Live Server Daily Build 24.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Nov 18 17:44:17 2023
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2023-11-18 (2 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily amd64 (20231118)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors: Nov 18 17:44:08 hostname kernel: workqueue: 
drain_vmap_area_work hogged CPU for >1us 8 times, consider switching to 
WQ_UNBOUND
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2043953/+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 2049958] [NEW] package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/bluetooth/obexd' before installing new version: Input/output

You have been subscribed to a public bug:

bug found during software update launched from bootable usb

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: bluez-obexd 5.68-0ubuntu1
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckMismatches: ./casper/minimal.squashfs
CasperMD5CheckResult: fail
CasperVersion: 1.486
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
Date: Sat Jan 20 00:18:32 2024
DuplicateSignature:
 package:bluez-obexd:5.68-0ubuntu1
 Unpacking bluez-obexd (5.68-0ubuntu1.1) over (5.68-0ubuntu1) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-MsVzUs/045-bluez-obexd_5.68-0ubuntu1.1_amd64.deb 
(--unpack):
  unable to make backup link of './usr/lib/bluetooth/obexd' before installing 
new version: Input/output error
ErrorMessage: unable to make backup link of './usr/lib/bluetooth/obexd' before 
installing new version: Input/output error
InterestingModules: rfcomm bnep btusb bluetooth
LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1
 apt  2.7.3
SourcePackage: bluez
Title: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to 
make backup link of './usr/lib/bluetooth/obexd' before installing new version: 
Input/output error
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2018
dmi.bios.release: 5.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 306
dmi.board.asset.tag: Default string
dmi.board.name: GL553VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr306:bd09/26/2018:br5.6:svnASUSTeKCOMPUTERINC.:pnGL553VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
dmi.product.family: GL
dmi.product.name: GL553VW
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: D0:57:7B:12:13:2F  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:1345 acl:0 sco:0 events:90 errors:0
TX bytes:3835 acl:0 sco:0 commands:90 errors:0

** Affects: bluez (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: amd64 apport-package mantic need-duplicate-check
-- 
package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to make 
backup link of './usr/lib/bluetooth/obexd' before installing new version: 
Input/output error
https://bugs.launchpad.net/bugs/2049958
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez in Ubuntu.

-- 
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 2045456] Re: add-apt-repository crashed with --- in _request()

*** This bug is a duplicate of bug 2045455 ***
https://bugs.launchpad.net/bugs/2045455

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2045455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2045456/+attachment/5725768/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2045456/+attachment/5725769/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2045455

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Error encountered during first boot after installing ubuntu-unity-
  desktop on Live Server 24.04 Daily Build.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Nov 30 02:20:48 2023
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2023-11-30 (2 days ago)
  InstallationMedia: Ubuntu-Server 24.04 "Noble Numbat" - Daily amd64 (20231129)
  InterpreterPath: /usr/bin/python3.11
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2045456/+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 2045509] Re: package humanity-icon-theme 0.6.16 failed to install/upgrade: unable to install new version of '/usr/share/icons/Humanity/apps/24/gnome-power-manager.svg': Permissio

** Tags removed: need-duplicate-check

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

Title:
  package humanity-icon-theme 0.6.16 failed to install/upgrade: unable
  to install new version of '/usr/share/icons/Humanity/apps/24/gnome-
  power-manager.svg': Permission denied

Status in humanity-icon-theme package in Ubuntu:
  New

Bug description:
  "sudo apt full-upgrade" failed on VSL

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: humanity-icon-theme 0.6.16
  ProcVersionSignature: Microsoft 4.4.0-22621.2506-Microsoft 4.4.35
  Uname: Linux 4.4.0-22621-Microsoft x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Sun Dec  3 18:45:03 2023
  Dependencies:
   
  Dmesg: [0.009695]  Microsoft 4.4.0-22621.2506-Microsoft 4.4.35
  DuplicateSignature:
   package:humanity-icon-theme:0.6.16
   Unpacking humanity-icon-theme (0.6.16) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-FRtpEe/080-humanity-icon-theme_0.6.16_all.deb (--unpack):
unable to install new version of 
'/usr/share/icons/Humanity/apps/24/gnome-power-manager.svg': Permission denied
  ErrorMessage: unable to install new version of 
'/usr/share/icons/Humanity/apps/24/gnome-power-manager.svg': Permission denied
  PackageArchitecture: all
  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: humanity-icon-theme
  Title: package humanity-icon-theme 0.6.16 failed to install/upgrade: unable 
to install new version of 
'/usr/share/icons/Humanity/apps/24/gnome-power-manager.svg': Permission denied
  UpgradeStatus: Upgraded to jammy on 2023-12-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/humanity-icon-theme/+bug/2045509/+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 2047598] Re: add-apt-repository crashed with --- in _request()

*** This bug is a duplicate of bug 2045455 ***
https://bugs.launchpad.net/bugs/2045455

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2045455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2047598/+attachment/5733617/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2047598/+attachment/5733618/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2045455

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Crash occured during first boot after installing ubuntu-desktop on
  Live Server Daily 24.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  Uname: Linux 6.6.8-060608-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Dec 27 10:29:54 2023
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2023-12-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 
(20231226)
  InterpreterPath: /usr/bin/python3.11
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2047598/+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 2047599] Re: add-apt-repository crashed with --- in _request()

*** This bug is a duplicate of bug 2045455 ***
https://bugs.launchpad.net/bugs/2045455

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2045455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2047599/+attachment/5733622/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2047599/+attachment/5733623/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2045455

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Crash occurred during first boot after installing ubuntu-desktop on
  Live Server 24.04 Daily build.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  Uname: Linux 6.6.8-060608-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 27 19:45:10 2023
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2023-12-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 
(20231226)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors: -- No entries --
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2047599/+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 2047614] Re: add-apt-repository crashed with --- in _request()

*** This bug is a duplicate of bug 2045455 ***
https://bugs.launchpad.net/bugs/2045455

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2045455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2047614/+attachment/5733673/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2047614/+attachment/5733674/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2045455

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Crash occured during first boot after installing ubuntu-gnome-desktop
  on Live Server 24.04 Daily.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  Uname: Linux 6.6.8-060608-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 27 21:55:29 2023
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2023-12-27 (1 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 
(20231226)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors: -- No entries --
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=en_US.UTF-8
   LANGUAGE=
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2047614/+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 2048616] Re: add-apt-repository crashed with --- in _request()

*** This bug is a duplicate of bug 2045455 ***
https://bugs.launchpad.net/bugs/2045455

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #2045455, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Tags removed: need-duplicate-check

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => Medium

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/2048616/+attachment/5737433/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/2048616/+attachment/5737434/+files/ProcStatus.txt

** This bug has been marked a duplicate of private bug 2045455

** Information type changed from Private to Public

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

Title:
  add-apt-repository crashed with --- in _request()

Status in software-properties package in Ubuntu:
  New

Bug description:
  Error occurred during first boot after installing ubuntu-gnome-desktop
  on Live Server 24.04 Daily.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.40
  Uname: Linux 6.6.10-060610-generic x86_64
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sun Jan  7 13:33:09 2024
  ExecutablePath: /usr/bin/add-apt-repository
  InstallationDate: Installed on 2024-01-07 (1 days ago)
  InstallationMedia: Ubuntu-Server 24.04 LTS "Noble Numbat" - Daily amd64 
(20240107)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors: -- No entries --
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/bin/add-apt-repository ppa:relan/exfat -y
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=linux
  Python3Details: /usr/bin/python3.11, Python 3.11.7, python3-minimal, 3.11.4-5
  PythonArgs: ['/usr/bin/add-apt-repository', 'ppa:relan/exfat', '-y']
  PythonDetails: N/A
  SourcePackage: software-properties
  Title: add-apt-repository crashed with --- in _request()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2048616/+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 2048098] Re: package avahi-daemon 0.7-4ubuntu7.3 failed to install/upgrade: installed avahi-daemon package post-installation script subprocess returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package avahi-daemon 0.7-4ubuntu7.3 failed to install/upgrade:
  installed avahi-daemon package post-installation script subprocess
  returned error exit status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  Happened during package upgrade performed by Software Updater gui
  applet. My *guess* is that it crashed because it wasn't equipped to
  handle a custom user avahi-daemon.conf (I have use-ipv4 and use-ipv6
  set to no in order to stop network printers from being aggressively
  added to my printer list).

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: avahi-daemon 0.7-4ubuntu7.3
  ProcVersionSignature: Ubuntu 5.4.0-159.176-generic 5.4.241
  Uname: Linux 5.4.0-159-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jan  4 10:41:54 2024
  ErrorMessage: installed avahi-daemon package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-08-25 (2688 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 
(20140204)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.10
  SourcePackage: avahi
  Title: package avahi-daemon 0.7-4ubuntu7.3 failed to install/upgrade: 
installed avahi-daemon package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2023-04-27 (251 days ago)
  mtime.conffile..etc.avahi.avahi-daemon.conf: 2023-04-28T14:41:17.016393

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/2048098/+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 2046624] Re: apparmor breaks surfshark vpn

2024-01-22 Thread John Johansen

*** This bug is a duplicate of bug 2046844 ***
https://bugs.launchpad.net/bugs/2046844

The surfshark profile has been uploaded to the
https://launchpad.net/~apparmor-dev/+archive/ubuntu/unprivileged-userns
ppa for testing

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

Title:
  apparmor breaks surfshark vpn

Status in apparmor package in Ubuntu:
  New

Bug description:
  with the new   apparmor Candidate: 4.0.0~alpha2-0ubuntu7
  Breaks my VPN

 *surfshark
  [33104:1216/072144.904027:FATAL:credentials.cc(127)] Check failed: . : 
Permission denied (13)
  Trace/breakpoint trap

  It will work with --no-sandbox "surfshark --no-sandbox" not ideal.
  I removed apparmor for proof

  *apt policy apparmor
  apparmor:
Installed: (none)
Candidate: 4.0.0~alpha2-0ubuntu7
Version table:
   4.0.0~alpha2-0ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu noble/main amd64 Packages
  Now my VPN works as expected, spent 2 hrs this morning with surfshark 
support, they will get back to me in a day or two, but they can't find anything 
wrong on their end.

  So far it points to apparmor

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apparmor (not installed)
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs
  ApportVersion: 2.27.0-0ubuntu6
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Dec 16 10:40:00 2023
  InstallationDate: Installed on 2023-12-10 (6 days ago)
  InstallationMedia: Xubuntu 24.04 "Noble Numbat" - Daily amd64 (20231127)
  SourcePackage: apparmor
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2023-12-12T09:43:48.905263

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2046624/+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 2047343] Re: The steam profile in 4.0.0~alpha2-0ubuntu7 does not support steam installed by steam-installer package

2024-01-22 Thread John Johansen

the adjusted steam profile has been uploaded to
https://launchpad.net/~apparmor-dev/+archive/ubuntu/unprivileged-userns
ppa for testing

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

Title:
  The steam profile in 4.0.0~alpha2-0ubuntu7 does not support steam
  installed by steam-installer package

Status in apparmor package in Ubuntu:
  New
Status in steam-installer package in Ubuntu:
  New

Bug description:
  The steam profile in 4.0.0~alpha2-0ubuntu7 only supports steam
  installed from the official website
  (https://cdn.cloudflare.steamstatic.com/client/installer/steam.deb),
  but does not support the installation by the steam-installer in the
  repository.

  The new user namespace creation restrictions will prevent steam
  installed by steam-installer from running Windows games.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2047343/+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 2046844] Re: AppArmor user namespace creation restrictions cause many applications to crash with SIGTRAP

2024-01-22 Thread John Johansen

Sorry for the delay on this, we had some bugs to chase down. The
following PPA has an update to how user namespace mediation is being
handled. For the unconfined case there are two options

1. If the unprivileged_userns profile does not exist, unprivileged user
namespace creation is denied as before.

2. If the unprivileged_userns profile exists (ie. is loaded into the
kernel), unprivileged user namespace creation is allowed an will result
in a transition into the unprivileged_userns profile. The
unprivileged_userns profile with then deny all capabilities within the
profile. Execution of applications is allowed within the
unprivileged_userns profile but, they will result in a stack with the
unprivileged_userns profile, that is to say the unprivileged_userns
profile can not be dropped (capabilities can not be gained).

There is still some additional functionality to land that will give
profile authors more control, but what is present here should be enough
to start testing.

https://launchpad.net/~apparmor-dev/+archive/ubuntu/unprivileged-userns

Note: the apparmor_restriction_unprivileged_unconfined needs to be
enabled to test the above user namespace behavior. See
https://gitlab.com/apparmor/apparmor/-/wikis/unprivileged_userns_restriction

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

Title:
  AppArmor user namespace creation restrictions cause many applications
  to crash with SIGTRAP

Status in akregator package in Ubuntu:
  Confirmed
Status in angelfish package in Ubuntu:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed
Status in bubblewrap package in Ubuntu:
  Confirmed
Status in cantor package in Ubuntu:
  Confirmed
Status in devhelp package in Ubuntu:
  Confirmed
Status in digikam package in Ubuntu:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Confirmed
Status in evolution package in Ubuntu:
  Confirmed
Status in falkon package in Ubuntu:
  Confirmed
Status in freecad package in Ubuntu:
  Confirmed
Status in ghostwriter package in Ubuntu:
  Confirmed
Status in gnome-packagekit package in Ubuntu:
  Confirmed
Status in goldendict-webengine package in Ubuntu:
  Confirmed
Status in kalgebra package in Ubuntu:
  Confirmed
Status in kchmviewer package in Ubuntu:
  Confirmed
Status in kdeplasma-addons package in Ubuntu:
  Confirmed
Status in kiwix package in Ubuntu:
  Confirmed
Status in konqueror package in Ubuntu:
  Confirmed
Status in kontact package in Ubuntu:
  Confirmed
Status in notepadqq package in Ubuntu:
  Confirmed
Status in opam package in Ubuntu:
  Confirmed
Status in pageedit package in Ubuntu:
  Confirmed
Status in plasma-desktop package in Ubuntu:
  Confirmed
Status in privacybrowser package in Ubuntu:
  Confirmed
Status in qmapshack package in Ubuntu:
  Confirmed
Status in qutebrowser package in Ubuntu:
  Confirmed
Status in rssguard package in Ubuntu:
  Confirmed
Status in steam package in Ubuntu:
  Confirmed
Status in supercollider package in Ubuntu:
  Confirmed
Status in tellico package in Ubuntu:
  Confirmed

Bug description:
  Hi, I run Ubuntu development branch 24.04 and I have a problem with
  Epiphany browser 45.1-1 (Gnome Web): program doesn't launch, and I get
  this error

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:12085): ERROR **: 14:44:35.023: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  $ epiphany
  bwrap: Creating new namespace failed: Permission denied

  ** (epiphany:30878): ERROR **: 22:22:26.926: Failed to fully launch 
dbus-proxy: Le processus fils s’est terminé avec le code 1
  Trappe pour point d'arrêt et de trace (core dumped)

  Thanks for your help!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/akregator/+bug/2046844/+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 1837227] Update Released

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

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

Title:
  systemd mount units fail during boot, while file system is correctly
  mounted

Status in systemd:
  New
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  systemd mount units fail during boot, and the system boots into emergency mode

  [Test Plan]
  This issue seems to happen randomly, and doesn't seem related to a specific 
mount unit.

  We've used a test script with good results during investigation to
  reproduce similar mount failures in a running system, and have seen a
  strong correlation between the script failures and the boot time mount
  failures.

  The attached 'rep-tmpfs.sh' script should be used to validate that
  mount points are working correctly under stress. One can run through
  the different variants as below:

  # ./rep-tmpfs.sh --variant-0
  # ./rep-tmpfs.sh --variant-1
  # ./rep-tmpfs.sh --variant-2
  # ./rep-tmpfs.sh --variant-3
  # ./rep-tmpfs.sh --variant-4

  All of these should run successfully without any reported errors.

  [Where problems could occur]
  The patches change the way systemd tracks and handles mount points in 
general, so potential regressions could affect other mount units. We should 
keep an eye out for any issues with mounting file systems, as well as rapid 
mount/unmount operations. Successful test runs with the reproducer script 
should increase reliability in having no new regressions.

  [Other Info]
  This has been tackled upstream with several attempts, which have resulted in 
the final patch from 2022:
    01400460ae16 core/mount: adjust deserialized state based on 
/proc/self/mountinfo

  For Bionic, systemd requires several dependency patches as below:
    6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a 
new unit cycle
    7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the 
other way round
    350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() 
results
    1d086a6e5972 mount: mark an existing "mounting" unit from 
/proc/self/mountinfo as "just_mounted"

  Additionally, the kernel also requires the following patches:
    28ca0d6d39ab list: introduce list_for_each_continue()
    9f6c61f96f2d proc/mounts: add cursor

  [Original Description]
  In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode 
with a failed mount unit (ext4 file system), while the corresponding file 
system is in fact correctly mounted. It happens roughly once every 1000 reboots.

  It seems to be related with this bug :
  https://github.com/systemd/systemd/issues/10872

  Is it possible to apply the fix
  
(https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21)
  in Ubuntu 18.04 ?

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1837227/+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 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted

This bug was fixed in the package systemd - 245.4-4ubuntu3.23

---
systemd (245.4-4ubuntu3.23) focal; urgency=medium

  [ Nick Rosbrook ]
  * core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File: 
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7793563bb38a84a3dc6bc0da1c08546c3b915ab8
  * dns-query: bump CNAME_MAX to 16 (LP: #2024009)
File: debian/patches/lp2024009-dns-query-bump-CNAME_MAX-to-16.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=193899d103d44c642d362e9916b14df844ec702f
  * Fall back to kexec when no kexec binary exists (LP: #1969365)
File: 
debian/patches/lp1969365-Fall-back-to-kexec-when-no-kexec-binary-exists.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3934f3794427dee4e72824998dd4c6e6d5875289
  * test: ignore LXC filesystem when checking for writable locations (LP: 
#2029352)
File: 
debian/patches/lp2029352-test-ignore-LXC-filesystem-when-checking-for-writable-loc.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=70facbfbf54c4ffb31ba392dbe3fec3084fdf3bc

  [ Heitor Alves de Siqueira ]
  * core/mount: adjust deserialized state based on /proc/self/mountinfo (LP: 
#1837227)
Author: Heitor Alves de Siqueira
File: 
debian/patches/lp1837227-core-mount-adjust-deserialized-state-based-on-proc-self-m.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a0a749953d309f48bc45140102adf205d1071c4d

 -- Nick Rosbrook   Tue, 21 Nov 2023 16:10:21 -0500

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

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

Title:
  systemd mount units fail during boot, while file system is correctly
  mounted

Status in systemd:
  New
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  systemd mount units fail during boot, and the system boots into emergency mode

  [Test Plan]
  This issue seems to happen randomly, and doesn't seem related to a specific 
mount unit.

  We've used a test script with good results during investigation to
  reproduce similar mount failures in a running system, and have seen a
  strong correlation between the script failures and the boot time mount
  failures.

  The attached 'rep-tmpfs.sh' script should be used to validate that
  mount points are working correctly under stress. One can run through
  the different variants as below:

  # ./rep-tmpfs.sh --variant-0
  # ./rep-tmpfs.sh --variant-1
  # ./rep-tmpfs.sh --variant-2
  # ./rep-tmpfs.sh --variant-3
  # ./rep-tmpfs.sh --variant-4

  All of these should run successfully without any reported errors.

  [Where problems could occur]
  The patches change the way systemd tracks and handles mount points in 
general, so potential regressions could affect other mount units. We should 
keep an eye out for any issues with mounting file systems, as well as rapid 
mount/unmount operations. Successful test runs with the reproducer script 
should increase reliability in having no new regressions.

  [Other Info]
  This has been tackled upstream with several attempts, which have resulted in 
the final patch from 2022:
    01400460ae16 core/mount: adjust deserialized state based on 
/proc/self/mountinfo

  For Bionic, systemd requires several dependency patches as below:
    6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a 
new unit cycle
    7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the 
other way round
    350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() 
results
    1d086a6e5972 mount: mark an existing "mounting" unit from 
/proc/self/mountinfo as "just_mounted"

  Additionally, the kernel also requires the following patches:
    28ca0d6d39ab list: introduce list_for_each_continue()
    9f6c61f96f2d proc/mounts: add cursor

  [Original Description]
  In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode 
with a failed mount unit (ext4 file system), while the corresponding file 
system is in fact correctly mounted. It happens roughly once every 1000 reboots.

  It seems to be related with this bug :

[Touch-packages] [Bug 1958019]

2024-01-22 Thread shenanigans

(In reply to Cameron Berkenpas from comment #805)
> I believe support for the 16ACHg6 was added quite a ways back.
> 
> On 1/18/24 05:36, bugzilla-dae...@kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=208555
> >
> > shenanig...@duck.com changed:
> >
> > What|Removed |Added
> >
> 
> >   CC||shenanig...@duck.com
> >
> > --- Comment #804 from shenanig...@duck.com ---
> > (In reply to Howard Chu from comment #791)
> >> (In reply to Miggy from comment #790)
> >>> It seems the sound no longer works for the legion 7 16achg6 on kernel
> 6.6.
> >>> It's been working great for the last year on all kernels, but 6.6 just
> >>> doesn't work.
> >>>
> >>> I'm not sure if anyone else is having similar issues? Manjaro Linux here.
> >> I had no luck with sound on Ubuntu's 6.2 either. I dropped back to 5.19 to
> >> get sound working again.
> > I have been lurking on this thread for a while. This thread has been up and
> > still active since 2020, I don't even know where / which suggestions I need
> > to
> > start following.
> >
> > I have 16ACHg6 too, (Alsa says that) it's running Realtek ALC287. I have a
> > fresh install of Ubuntu 22.04 with kernel 6.5.0-14-generic, I have updated
> my
> > BIOS and internal speakers hasn't been working at all since the first day.
> > External speakers (headphone, Bluetooth speakers) work just fine though.
> > Still
> > no luck with 16ACHg6 then ?
> >

Yes, I tried a few patches including the last one : linux-legion-sound-0.0.13. 
I can confirm it is not working on my 16ACHg6 with kernel 6.5.0-14. 
Thank you so much by the way for all of your help with so many patches !

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

[Touch-packages] [Bug 1969365] Update Released

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

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

Title:
  focal: backport kexec fallback patch

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

Bug description:
  It would be great if focal's systemd could have
  
https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3
  backported to it.

  [Impact]

  We have observed that kexec'ing to another kernel will fail as the
  drive containing the `kexec` binary has been unmounted by the time
  systemd attempts to do so, indicated in the console:

   Starting Reboot via kexec...
  [  163.960938] shutdown[1]: (sd-kexec) failed with exit status 1.
  [  163.963463] reboot: Restarting system

  [Test Plan]

  1) Launch a 20.04 instance
  2) `apt-get install kexec-tools`
  3) In `/boot`, filling in whatever  needed in your environment:

  kexec -l vmlinuz --initrd initrd.img --append ''

  4) `reboot`

  (I have reproduced this in a single-disk VM, so I assume it reproduces
  ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot`
  could be used to emulate the unmounting.)

  [Where problems could occur]

  Users could inadvertently be relying on the current behaviour: if they
  have configured their systems to kexec, they currently will be
  rebooting normally, and this patch would cause them to start actually
  kexec'ing.

  [Other info]

  We're currently maintaining a systemd tree with only this patch added
  to focal's tree: this patch has received a bunch of testing from us in
  focal.

  This patch landed in v246, so it's already present in supported
  releases later than focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969365/+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 1969365] Re: focal: backport kexec fallback patch

This bug was fixed in the package systemd - 245.4-4ubuntu3.23

---
systemd (245.4-4ubuntu3.23) focal; urgency=medium

  [ Nick Rosbrook ]
  * core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File: 
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7793563bb38a84a3dc6bc0da1c08546c3b915ab8
  * dns-query: bump CNAME_MAX to 16 (LP: #2024009)
File: debian/patches/lp2024009-dns-query-bump-CNAME_MAX-to-16.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=193899d103d44c642d362e9916b14df844ec702f
  * Fall back to kexec when no kexec binary exists (LP: #1969365)
File: 
debian/patches/lp1969365-Fall-back-to-kexec-when-no-kexec-binary-exists.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3934f3794427dee4e72824998dd4c6e6d5875289
  * test: ignore LXC filesystem when checking for writable locations (LP: 
#2029352)
File: 
debian/patches/lp2029352-test-ignore-LXC-filesystem-when-checking-for-writable-loc.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=70facbfbf54c4ffb31ba392dbe3fec3084fdf3bc

  [ Heitor Alves de Siqueira ]
  * core/mount: adjust deserialized state based on /proc/self/mountinfo (LP: 
#1837227)
Author: Heitor Alves de Siqueira
File: 
debian/patches/lp1837227-core-mount-adjust-deserialized-state-based-on-proc-self-m.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a0a749953d309f48bc45140102adf205d1071c4d

 -- Nick Rosbrook   Tue, 21 Nov 2023 16:10:21 -0500

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

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

Title:
  focal: backport kexec fallback patch

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

Bug description:
  It would be great if focal's systemd could have
  
https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3
  backported to it.

  [Impact]

  We have observed that kexec'ing to another kernel will fail as the
  drive containing the `kexec` binary has been unmounted by the time
  systemd attempts to do so, indicated in the console:

   Starting Reboot via kexec...
  [  163.960938] shutdown[1]: (sd-kexec) failed with exit status 1.
  [  163.963463] reboot: Restarting system

  [Test Plan]

  1) Launch a 20.04 instance
  2) `apt-get install kexec-tools`
  3) In `/boot`, filling in whatever  needed in your environment:

  kexec -l vmlinuz --initrd initrd.img --append ''

  4) `reboot`

  (I have reproduced this in a single-disk VM, so I assume it reproduces
  ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot`
  could be used to emulate the unmounting.)

  [Where problems could occur]

  Users could inadvertently be relying on the current behaviour: if they
  have configured their systems to kexec, they currently will be
  rebooting normally, and this patch would cause them to start actually
  kexec'ing.

  [Other info]

  We're currently maintaining a systemd tree with only this patch added
  to focal's tree: this patch has received a bunch of testing from us in
  focal.

  This patch landed in v246, so it's already present in supported
  releases later than focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969365/+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 2024009] Re: [PATCH] systemd-resolved can't follow more than 8 CNAMEs

This bug was fixed in the package systemd - 245.4-4ubuntu3.23

---
systemd (245.4-4ubuntu3.23) focal; urgency=medium

  [ Nick Rosbrook ]
  * core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File: 
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7793563bb38a84a3dc6bc0da1c08546c3b915ab8
  * dns-query: bump CNAME_MAX to 16 (LP: #2024009)
File: debian/patches/lp2024009-dns-query-bump-CNAME_MAX-to-16.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=193899d103d44c642d362e9916b14df844ec702f
  * Fall back to kexec when no kexec binary exists (LP: #1969365)
File: 
debian/patches/lp1969365-Fall-back-to-kexec-when-no-kexec-binary-exists.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3934f3794427dee4e72824998dd4c6e6d5875289
  * test: ignore LXC filesystem when checking for writable locations (LP: 
#2029352)
File: 
debian/patches/lp2029352-test-ignore-LXC-filesystem-when-checking-for-writable-loc.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=70facbfbf54c4ffb31ba392dbe3fec3084fdf3bc

  [ Heitor Alves de Siqueira ]
  * core/mount: adjust deserialized state based on /proc/self/mountinfo (LP: 
#1837227)
Author: Heitor Alves de Siqueira
File: 
debian/patches/lp1837227-core-mount-adjust-deserialized-state-based-on-proc-self-m.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a0a749953d309f48bc45140102adf205d1071c4d

 -- Nick Rosbrook   Tue, 21 Nov 2023 16:10:21 -0500

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

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

Title:
  [PATCH] systemd-resolved can't follow more than 8 CNAMEs

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

Bug description:
  [Impact]

  Using systemd-resolved to resolve a hostname which has more than 8
  CNAME redirects will fail because of the hard-coded limit. While this
  case is somewhat rare, the original reporter demonstrated a real-world
  scenario where this happened (although that particular hostname seems
  to be fixed now).

  [Test Plan]

  This test plan uses a LXC container to test systemd-resolved on Focal.
  If LXD has not been configured on your system, start with:

  $ lxd init --auto

  Then, create a Focal container with:

  $ lxc launch ubuntu-daily:focal focal

  Install dnsmasq-base if needed:

  $ apt install dnsmasq-base

  Stop other DNS servers:

  $ systemctl stop systemd-resolved
  $ kill -9 $(pgrep dnsmasq)

  Now, on the host start a new DNS server that listens on lxdbr0, and
  sets up an A record, and many CNAME records which ultimately redirect
  to the A record:

  $ dnsmasq \
  --cname=test10.lan,test9.lan \
  --cname=test9.lan,test8.lan \
  --cname=test8.lan,test7.lan \
  --cname=test7.lan,test6.lan \
  --cname=test6.lan,test5.lan \
  --cname=test5.lan,test4.lan \
  --cname=test4.lan,test3.lan \
  --cname=test3.lan,test2.lan \
  --cname=test2.lan,test1.lan \
  --cname=test1.lan,test0.lan \
  -k -i lxdbr0 -z -I lo --host-record=test0.lan,$IP

  where $IP is any host on your network.

  Now, obtain a shell in the Focal container:

  $ lxc exec focal bash

  Attempt to resolve test10.lan:

  $ resolvectl query test10.lan
  test10.lan: resolve call failed: CNAME loop detected, or CNAME resolving 
disabled on 'test2.lan'

  On an affected system, the above error will be seen. On a patched
  system, the hostname should be resolved.

  [Where problems could occur]

  The patch simply increases the maximum CNAME redirects that are
  allowed from 8 to 16, so a reasonable limit is still imposed. If an
  application specifically relied on systemd-resolved's limit being at
  8, then that application would potentially see new behavior.

  [Original Description]

  On Ubuntu 20.04 (systemd v245.4-4ubuntu3.21), hostname resolution only
  follows 8 CNAME redirections maximum.

  So when using a service like Azure Virtual Desktop that has between 9
  and 12 redirections, name resolution fails.

  $ host client.wvd.microsoft.com
  Host client.wvd.microsoft.com not found: 2(SERVFAIL)
  $ resolvectl query client.wvd.microsoft.com
  client.wvd.microsoft.com: resolve call failed: CNAME loop detected, or CNAME 
resolving disabled on 'waws-prod-zrh-ff7172dd.sip.p.azurewebsites.windows.net'

  On the other hand it's working fine on Ubuntu 20.04 because CNAME loop
  limit has been raised from 8 to 16.

  $ host client.wvd.microsoft.com
  client.wvd.microsoft.com is an alias for 
client.privatelink-global.wvd.microsoft.com.
  client.privatelink-global.wvd.microsoft.com is an alias

[Touch-packages] [Bug 2029352] Re: systemd/ 245.4-4ubuntu3.22 ADT test failure with linux/5.4.0-156.173

This bug was fixed in the package systemd - 245.4-4ubuntu3.23

---
systemd (245.4-4ubuntu3.23) focal; urgency=medium

  [ Nick Rosbrook ]
  * core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File: 
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7793563bb38a84a3dc6bc0da1c08546c3b915ab8
  * dns-query: bump CNAME_MAX to 16 (LP: #2024009)
File: debian/patches/lp2024009-dns-query-bump-CNAME_MAX-to-16.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=193899d103d44c642d362e9916b14df844ec702f
  * Fall back to kexec when no kexec binary exists (LP: #1969365)
File: 
debian/patches/lp1969365-Fall-back-to-kexec-when-no-kexec-binary-exists.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3934f3794427dee4e72824998dd4c6e6d5875289
  * test: ignore LXC filesystem when checking for writable locations (LP: 
#2029352)
File: 
debian/patches/lp2029352-test-ignore-LXC-filesystem-when-checking-for-writable-loc.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=70facbfbf54c4ffb31ba392dbe3fec3084fdf3bc

  [ Heitor Alves de Siqueira ]
  * core/mount: adjust deserialized state based on /proc/self/mountinfo (LP: 
#1837227)
Author: Heitor Alves de Siqueira
File: 
debian/patches/lp1837227-core-mount-adjust-deserialized-state-based-on-proc-self-m.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a0a749953d309f48bc45140102adf205d1071c4d

 -- Nick Rosbrook   Tue, 21 Nov 2023 16:10:21 -0500

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

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

Title:
  systemd/ 245.4-4ubuntu3.22  ADT test failure with linux/5.4.0-156.173

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

Bug description:
  [Impact]

  The armhf autopkgtest fails for focal and ultimately leads to less
  test coverage because other packages now won't block on these
  failures, and may not notice new regressions.

  [Test Plan]

  The test-execute test within root-unittests should pass.

  [Where problems could occur]

  The patch only changes a service file in the test tree of systemd, so
  this is not a change that will be seen on real Ubuntu systems. Hence
  any further problems would be seen only in the test-execute test.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd tests 
for linux/5.4.0-156.173 on focal. Whether this is caused by the dep8 tests of 
the tested source or the kernel has yet to be determined.
  root-unittests fails.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20230727_150132_9cd77@/log.gz

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

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

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

Title:
  [PATCH] systemd-resolved can't follow more than 8 CNAMEs

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

Bug description:
  [Impact]

  Using systemd-resolved to resolve a hostname which has more than 8
  CNAME redirects will fail because of the hard-coded limit. While this
  case is somewhat rare, the original reporter demonstrated a real-world
  scenario where this happened (although that particular hostname seems
  to be fixed now).

  [Test Plan]

  This test plan uses a LXC container to test systemd-resolved on Focal.
  If LXD has not been configured on your system, start with:

  $ lxd init --auto

  Then, create a Focal container with:

  $ lxc launch ubuntu-daily:focal focal

  Install dnsmasq-base if needed:

  $ apt install dnsmasq-base

  Stop other DNS servers:

  $ systemctl stop systemd-resolved
  $ kill -9 $(pgrep dnsmasq)

  Now, on the host start a new DNS server that listens on lxdbr0, and
  sets up an A record, and many CNAME records which ultimately redirect
  to the A record:

  $ dnsmasq \
  --cname=test10.lan,test9.lan \
  --cname=test9.lan,test8.lan \
  --cname=test8.lan,test7.lan \
  --cname=test7.lan,test6.lan \
  --cname=test6.lan,test5.lan \
  --cname=test5.lan,test4.lan \
  --cname=test4.lan,test3.lan \
  --cname=test3.lan,test2.lan \
  --cname=test2.lan,test1.lan \
  --cname=test1.lan,test0.lan \
  -k -i lxdbr0 -z -I lo --host-record=test0.lan,$IP

  where $IP is any host on your network.

  Now, obtain a shell in the Focal container:

  $ lxc exec focal bash

  Attempt to resolve test10.lan:

  $ resolvectl query test10.lan
  test10.lan: resolve call failed: CNAME loop detected, or CNAME resolving 
disabled on 'test2.lan'

  On an affected system, the above error will be seen. On a patched
  system, the hostname should be resolved.

  [Where problems could occur]

  The patch simply increases the maximum CNAME redirects that are
  allowed from 8 to 16, so a reasonable limit is still imposed. If an
  application specifically relied on systemd-resolved's limit being at
  8, then that application would potentially see new behavior.

  [Original Description]

  On Ubuntu 20.04 (systemd v245.4-4ubuntu3.21), hostname resolution only
  follows 8 CNAME redirections maximum.

  So when using a service like Azure Virtual Desktop that has between 9
  and 12 redirections, name resolution fails.

  $ host client.wvd.microsoft.com
  Host client.wvd.microsoft.com not found: 2(SERVFAIL)
  $ resolvectl query client.wvd.microsoft.com
  client.wvd.microsoft.com: resolve call failed: CNAME loop detected, or CNAME 
resolving disabled on 'waws-prod-zrh-ff7172dd.sip.p.azurewebsites.windows.net'

  On the other hand it's working fine on Ubuntu 20.04 because CNAME loop
  limit has been raised from 8 to 16.

  $ host client.wvd.microsoft.com
  client.wvd.microsoft.com is an alias for 
client.privatelink-global.wvd.microsoft.com.
  client.privatelink-global.wvd.microsoft.com is an alias for 
client.privatelink.wvd.microsoft.com.
  client.privatelink.wvd.microsoft.com is an alias for rdweb.wvd.microsoft.com.
  rdweb.wvd.microsoft.com is an alias for 
rdweb.privatelink-global.wvd.microsoft.com.
  rdweb.privatelink-global.wvd.microsoft.com is an alias for 
rdweb.privatelink.wvd.microsoft.com.
  rdweb.privatelink.wvd.microsoft.com is an alias for 
rdweb-prod-geo.trafficmanager.net.
  rdweb-prod-geo.trafficmanager.net is an alias for 
mrs-chnor1c101-rdweb-prod.wvd-ase-chnor1c101-prod.p.azurewebsites.net.
  mrs-chnor1c101-rdweb-prod.wvd-ase-chnor1c101-prod.p.azurewebsites.net is an 
alias for waws-prod-zrh-63daa049.sip.p.azurewebsites.windows.net.
  waws-prod-zrh-63daa049.sip.p.azurewebsites.windows.net is an alias for 
waws-prod-zrh-63daa049.cloudapp.net.
  waws-prod-zrh-63daa049.cloudapp.net has address 51.107.69.35

  Here's a quick fix that raises the max CNAME limit from 8 to 16 like
  it is in Ubuntu 22.04, it fixes the problem for me.

  Best regards,
  Vincent.

  --- systemd-245.4.ORIG/src/resolve/resolved-dns-query.c   2023-06-15 
16:58:25.454156663 +0200
  +++ systemd-245.4/src/resolve/resolved-dns-query.c2023-06-01 
14:30:09.0 +0200
  @@ -10,7 +10,7 @@
   #include "resolved-etc-hosts.h"
   #include "string-util.h"

  -#define CNAME_MAX 8
  +#define CNAME_MAX 16
   #define

[Touch-packages] [Bug 2035122] Update Released

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

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

Title:
  Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix

Bug description:
  [Impact]

  When working with ubuntu core or ubuntu core desktop, neither
  */etc/default/locale* nor */etc/default/keyboard* are modifiable, so
  it's not possible to set the global keyboard or the global language.
  This is required to allow to set the GDM language, and the default one
  during installation.

  The first half of the solution is to create the folder
  */etc/writable/default*, and make soft-links from
  */etc/default/locale* to */etc/writable/default/locale* and from
  */etc/default/keyboard* to */etc/writable/default/keyboard*, just like
  it is already being done with */etc/hostname*, */etc/issue*,
  */etc/localtime*, */etc/motd* and , */etc/timezone*.

  This solution, unfortunately, isn't complete. Although any application
  that just reads the files will work, not all of the applications that
  write to them will; specifically the systemd utilities that set the
  contents for those files, because they don't open the file directly;
  instead, they create first the new file in the same folder than the
  old one, fill its contents, and only then delete the old one and
  rename the new one. To solve this, systemd in Ubuntu already has
  several patches that detect if a file is a soft-link, in which case it
  replaces the old path with the destination one.

  Currently I have in place a patch for Ubuntu Core Desktop that
  implements both changes for both */etc/default/locale* and
  */etc/default/keyboard*.

  [Test plan]

  Using *sudo localectl set-locale xx_YY.UTF-8* in an Ubuntu Core or
  Ubuntu Core Desktop admin terminal must change the locale to the
  specified one, which can be checked by reading the
  */etc/default/locale* file. Also, *localectl* must return the new
  locale.

  Using *sudo dbus-send --system --print-reply
  --dest=org.freedesktop.locale1 /org/freedesktop/locale1
  org.freedesktop.locale1.SetX11Keyboard string:XX string:pc10Y string:
  string: boolean:true boolean:false" must change the
  */etc/default/keyboard* file to layout XX and model PC10Y (being Y
  either 1, 2, 4 or 5). Reading the file allows to check it. Also,
  *localectl status* must return the layout and model values in "X11
  Layout" and "X11 Model" entries.

  [Where problems could occur]

  In general, applications just read the content of the file and use the
  DBus interface to set the locale, so only those applications that
  modify by themselves the */etc/default/keyboard* and/or
  */etc/default/locale* would present a problem, in which case they
  would require specific patches. Anyway, those applications neither
  would work with the current state (with those files in a read-only
  filesystem).

  [Other info]

  For Noble, this will be addressed when we merge systemd v255 from
  Debian. This is only needed on core, so we don't need to fix for
  Mantic or Lunar.

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

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

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

Title:
  systemd/ 245.4-4ubuntu3.22  ADT test failure with linux/5.4.0-156.173

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

Bug description:
  [Impact]

  The armhf autopkgtest fails for focal and ultimately leads to less
  test coverage because other packages now won't block on these
  failures, and may not notice new regressions.

  [Test Plan]

  The test-execute test within root-unittests should pass.

  [Where problems could occur]

  The patch only changes a service file in the test tree of systemd, so
  this is not a change that will be seen on real Ubuntu systems. Hence
  any further problems would be seen only in the test-execute test.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd tests 
for linux/5.4.0-156.173 on focal. Whether this is caused by the dep8 tests of 
the tested source or the kernel has yet to be determined.
  root-unittests fails.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20230727_150132_9cd77@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2029352/+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 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

This bug was fixed in the package systemd - 249.11-0ubuntu3.12

---
systemd (249.11-0ubuntu3.12) jammy; urgency=medium

  * core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File: 
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
  * use read-only /etc hack in more places (LP: #2035122)
File: debian/patches/debian/UBUNTU-Support-system-image-read-only-etc.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c57406e850396a5d446aefe5e70a3aeaad080d72
  * autopkgtest: do not allow qemu to be used on ppc64el.
Almost every run on ppc64el takes 12 to 24 hours, so do this as a last
resort to relieve pressure on autopkgtest infrastructure.
File: debian/tests/upstream

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d125a1ed3f01e59dba2f370c13801bfb76c16f5d

 -- Nick Rosbrook   Tue, 21 Nov 2023 15:57:17 -0500

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

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

Title:
  Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix

Bug description:
  [Impact]

  When working with ubuntu core or ubuntu core desktop, neither
  */etc/default/locale* nor */etc/default/keyboard* are modifiable, so
  it's not possible to set the global keyboard or the global language.
  This is required to allow to set the GDM language, and the default one
  during installation.

  The first half of the solution is to create the folder
  */etc/writable/default*, and make soft-links from
  */etc/default/locale* to */etc/writable/default/locale* and from
  */etc/default/keyboard* to */etc/writable/default/keyboard*, just like
  it is already being done with */etc/hostname*, */etc/issue*,
  */etc/localtime*, */etc/motd* and , */etc/timezone*.

  This solution, unfortunately, isn't complete. Although any application
  that just reads the files will work, not all of the applications that
  write to them will; specifically the systemd utilities that set the
  contents for those files, because they don't open the file directly;
  instead, they create first the new file in the same folder than the
  old one, fill its contents, and only then delete the old one and
  rename the new one. To solve this, systemd in Ubuntu already has
  several patches that detect if a file is a soft-link, in which case it
  replaces the old path with the destination one.

  Currently I have in place a patch for Ubuntu Core Desktop that
  implements both changes for both */etc/default/locale* and
  */etc/default/keyboard*.

  [Test plan]

  Using *sudo localectl set-locale xx_YY.UTF-8* in an Ubuntu Core or
  Ubuntu Core Desktop admin terminal must change the locale to the
  specified one, which can be checked by reading the
  */etc/default/locale* file. Also, *localectl* must return the new
  locale.

  Using *sudo dbus-send --system --print-reply
  --dest=org.freedesktop.locale1 /org/freedesktop/locale1
  org.freedesktop.locale1.SetX11Keyboard string:XX string:pc10Y string:
  string: boolean:true boolean:false" must change the
  */etc/default/keyboard* file to layout XX and model PC10Y (being Y
  either 1, 2, 4 or 5). Reading the file allows to check it. Also,
  *localectl status* must return the layout and model values in "X11
  Layout" and "X11 Model" entries.

  [Where problems could occur]

  In general, applications just read the content of the file and use the
  DBus interface to set the locale, so only those applications that
  modify by themselves the */etc/default/keyboard* and/or
  */etc/default/locale* would present a problem, in which case they
  would require specific patches. Anyway, those applications neither
  would work with the current state (with those files in a read-only
  filesystem).

  [Other info]

  For Noble, this will be addressed when we merge systemd v255 from
  Debian. This is only needed on core, so we don't need to fix for
  Mantic or Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2035122/+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 2037281] Re: Shutdown when triggering daemon-reload early in boot

This bug was fixed in the package systemd - 245.4-4ubuntu3.23

---
systemd (245.4-4ubuntu3.23) focal; urgency=medium

[ Nick Rosbrook ]
* core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=7793563bb38a84a3dc6bc0da1c08546c3b915ab8
* dns-query: bump CNAME_MAX to 16 (LP: #2024009)
File: debian/patches/lp2024009-dns-query-bump-CNAME_MAX-to-16.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=193899d103d44c642d362e9916b14df844ec702f
* Fall back to kexec when no kexec binary exists (LP: #1969365)
File:
debian/patches/lp1969365-Fall-back-to-kexec-when-no-kexec-binary-exists.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3934f3794427dee4e72824998dd4c6e6d5875289
* test: ignore LXC filesystem when checking for writable locations (LP:
#2029352)
File:
debian/patches/lp2029352-test-ignore-LXC-filesystem-when-checking-for-writable-loc.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=70facbfbf54c4ffb31ba392dbe3fec3084fdf3bc

[ Heitor Alves de Siqueira ]
* core/mount: adjust deserialized state based on /proc/self/mountinfo (LP:
#1837227)
Author: Heitor Alves de Siqueira
File:
debian/patches/lp1837227-core-mount-adjust-deserialized-state-based-on-proc-self-m.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=a0a749953d309f48bc45140102adf205d1071c4d

-- Nick Rosbrook Tue, 21 Nov 2023 16:10:21 -0500

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

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

Title:
Shutdown when triggering daemon-reload early in boot

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

Bug description:
In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
where if a service, started earlier than devices are processed by
udev, does `systemctl daemon-reload`, the system shuts down. This is
due to devices for mounted filesystem temporarily taken dead, which
pulls most units down.

This was fixed by upstream in
https://github.com/systemd/systemd/pull/23218.

But this was not backported to the versions used by Ubuntu packages
for focal and jammy. The needed commit from that PR is the one with
message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`.

This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing
needed. And I suppose it does also for jammy.

I have manually tested the fix with Ubuntu Core 20, and this fixes our
issue.

We would like this patch to be backported to focal-updates and jammy-
updates.

Thank you in advance.

[ Impact ]

If a user adds a service that calls `systemctl daemon-reload`, and if
this service is started before systemd-udevd. And if the initrd is
systemd (the case of Ubuntu Core), then most service will be stopped
or cancel, and the machine will mostly shutdown everything and hang.

The fix has been backported down to 250 upstream. It is already on
kinetic and later.

The fix only affects systems where systemd is used in initrd.

[ Test Plan ]

On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on
any system that uses systemd in initrd.

Add a systemd service that calls `systemctl daemon-reload`.
The service should have `DefaultDependencies=no` in order to start as soon as
possible and be enabled.

Restart the machine.

If fix is not applied, after the service is started, most of units
with be shutdown, and the system will be unusable.

[ Where problems could occur ]

This should affect systems with systemd in initrd.

There are risks on systems that have an udev rule in initrd not
present in the main system.

There are risks on systems that use db_persist in initrd where the
device can potentially get dead state. Though this does not seem to
happen on Ubuntu Core 22, even though we use db_persist for dev mapper
devices. Regression is upstream bug #23429. Commits named
"core/device: device_coldplug(): don't set DEVICE_DEAD" and
"core/device: do not downgrade device state if it is already
enumerated" could be applied as well.

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

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

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

Title:
  Shutdown when triggering daemon-reload early in boot

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

Bug description:
  In Ubuntu Core 20, and Ubuntu Core 22, we are encountering an issue
  where if a service, started earlier than devices are processed by
  udev, does `systemctl daemon-reload`, the system shuts down. This is
  due to devices for mounted filesystem temporarily taken dead, which
  pulls most units down.

  This was fixed by upstream in
  https://github.com/systemd/systemd/pull/23218.

  But this was not backported to the versions used by Ubuntu packages
  for focal and jammy. The needed commit from that PR is the one with
  message `core/device: ignore DEVICE_FOUND_UDEV bit on switching root`.

  This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing
  needed. And I suppose it does also for jammy.

  I have manually tested the fix with Ubuntu Core 20, and this fixes our
  issue.

  We would like this patch to be backported to focal-updates and jammy-
  updates.

  Thank you in advance.

  [ Impact ]

  If a user adds a service that calls `systemctl daemon-reload`, and if
  this service is started before systemd-udevd. And if the initrd is
  systemd (the case of Ubuntu Core), then most service will be stopped
  or cancel, and the machine will mostly shutdown everything and hang.

  The fix has been backported down to 250 upstream. It is already on
  kinetic and later.

  The fix only affects systems where systemd is used in initrd.

  [ Test Plan ]

  On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on
  any system that uses systemd in initrd.

  Add a systemd service that calls `systemctl daemon-reload`.
  The service should have `DefaultDependencies=no` in order to start as soon as 
possible and be enabled.

  Restart the machine.

  If fix is not applied, after the service is started, most of units
  with be shutdown, and the system will be unusable.

  [ Where problems could occur ]

  This should affect systems with systemd in initrd.

  There are risks on systems that have an udev rule in initrd not
  present in the main system.

  There are risks on systems that use db_persist in initrd where the
  device can potentially get dead state. Though this does not seem to
  happen on Ubuntu Core 22, even though we use db_persist for dev mapper
  devices. Regression is upstream bug #23429. Commits named
  "core/device: device_coldplug(): don't set DEVICE_DEAD" and
  "core/device: do not downgrade device state if it is already
  enumerated" could be applied as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 2037281] Re: Shutdown when triggering daemon-reload early in boot

This bug was fixed in the package systemd - 249.11-0ubuntu3.12

---
systemd (249.11-0ubuntu3.12) jammy; urgency=medium

* core/device: ignore DEVICE_FOUND_UDEV bit on switching root (LP: #2037281)
File:
debian/patches/lp2037281-core-device-ignore-DEVICE_FOUND_UDEV-bit-on-switching-roo.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=00f86f0b20f794f30aabe7181912d2ec2207e292
* use read-only /etc hack in more places (LP: #2035122)
File: debian/patches/debian/UBUNTU-Support-system-image-read-only-etc.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=c57406e850396a5d446aefe5e70a3aeaad080d72
* autopkgtest: do not allow qemu to be used on ppc64el.
Almost every run on ppc64el takes 12 to 24 hours, so do this as a last
resort to relieve pressure on autopkgtest infrastructure.
File: debian/tests/upstream

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d125a1ed3f01e59dba2f370c13801bfb76c16f5d

-- Nick Rosbrook Tue, 21 Nov 2023 15:57:17 -0500

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

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

Title:
Shutdown when triggering daemon-reload early in boot

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

This was fixed by upstream in
https://github.com/systemd/systemd/pull/23218.

This patch applies to 245.4-4ubuntu3.22 (focal) without rebasing
needed. And I suppose it does also for jammy.

I have manually tested the fix with Ubuntu Core 20, and this fixes our
issue.

We would like this patch to be backported to focal-updates and jammy-
updates.

Thank you in advance.

[ Impact ]

The fix has been backported down to 250 upstream. It is already on
kinetic and later.

The fix only affects systems where systemd is used in initrd.

[ Test Plan ]

On Ubuntu Core 20 (with Core 22 kernel) or on Ubuntu Core 22. Or on
any system that uses systemd in initrd.

Add a systemd service that calls `systemctl daemon-reload`.
The service should have `DefaultDependencies=no` in order to start as soon as
possible and be enabled.

Restart the machine.

If fix is not applied, after the service is started, most of units
with be shutdown, and the system will be unusable.

[ Where problems could occur ]

This should affect systems with systemd in initrd.

There are risks on systems that have an udev rule in initrd not
present in the main system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2037281/+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 2049885] Re: Merge console-setup (1.223) from Debian

2024-01-22 Thread Simon Quigley

** Patch added: "delta-delta.patch"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2049885/+attachment/5741436/+files/delta-delta.patch

** Changed in: console-setup (Ubuntu)
   Status: New => Fix Committed

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

Title:
  Merge console-setup (1.223) from Debian

Status in console-setup package in Ubuntu:
  Fix Committed

Bug description:
  In Debian console-setup (1.223) 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/2049885/+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 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

2024-01-22 Thread Lukas Märdian

We talked to our systemd maintainer inside foundations and also reached
out to upstream system [1], which didn't lead anywhere. We shouldn't
need to bisect systemd-networkd and do a high impact systemd SRU to fix
a regression in a kernel update, where we can pinpoint the exact (small)
git commit.

We'd like to ask to have the kernel commit b0ad3c179059 reverted in the
Jammy kernels, to mitigate this regression.


[1] 
https://lists.freedesktop.org/archives/systemd-devel/2023-November/049693.html

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2024-01-22 Thread Aleksandr Mikhalitsyn

Thanks, Dave!

Your branch and changes are looking good to me.

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

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2024-01-22 Thread Dave Jones

I had a little time to look over this again in my patch-pilot shift. I
agree it's almost certainly best to just get LXC_DEVEL set correctly
quickly. Andreas' suggested branch is a good start, but I agree with the
critique that the DEP-8 test should be checking the installed headers
rather than the built source. Due to this, it's probably also best if
the test is named something other than "build". Also, I agree it
shouldn't be marked "superficial".

I've pushed a few commits on top of Andreas' to another clone here,
which also fixes a build-failure on noble (lib/systemd instead of
usr/lib/systemd in d/lxc-utils.install):

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

I've tested the DEP-8 passes with the branch, and crucially that it
fails when the LXC_DEVEL fix is reverted (which it does). If this looks
sane to someone else, I'm happy to sponsor this into noble (and start
SRU proceedings for mantic and jammy).

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

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12

** Changed in: python-urllib3 (Debian)
   Status: New => 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/2049369

Title:
  autopkg tests ignored for migration of python3-defaults adding 3.12

Status in cython package in Ubuntu:
  New
Status in cython-legacy package in Ubuntu:
  New
Status in ipykernel package in Ubuntu:
  New
Status in ironic-python-agent package in Ubuntu:
  New
Status in jupyter-client package in Ubuntu:
  New
Status in numpy package in Ubuntu:
  New
Status in python-memory-profiler package in Ubuntu:
  New
Status in python-oslo.versionedobjects package in Ubuntu:
  Fix Committed
Status in python-urllib3 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in rich package in Ubuntu:
  New
Status in sphinx-autoapi package in Ubuntu:
  New
Status in vcr.py package in Ubuntu:
  New
Status in cython package in Debian:
  New
Status in cython-legacy package in Debian:
  New
Status in ipykernel package in Debian:
  New
Status in jupyter-client package in Debian:
  New
Status in numpy package in Debian:
  New
Status in python-memory-profiler package in Debian:
  New
Status in python-urllib3 package in Debian:
  Fix Released
Status in rich package in Debian:
  Confirmed
Status in sphinx-autoapi package in Debian:
  Fix Released
Status in vcr.py package in Debian:
  Fix Released

Bug description:
  autopkg tests ignored for migration of python3-defaults adding 3.12:

  These are the autopkg tests for packages, which we'll ignore for the
  initial migration of python3-defaults adding 3.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2037907] Re: No package 'nss' found

2024-01-22 Thread Robert

same problem when trying to compile version 24.01.0.

 No package 'nss' found
 Could NOT find NSS3 (missing: NSS3_LIBRARIES NSS3_CFLAGS) (Required is at 
least version "3.68")

But

sudo apt-get install libnss3
-> libnss3 is already the newest version (2:3.68.2-0ubuntu1.2).

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

Title:
  No package 'nss' found

Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Have installed poppler on several systems, but experience issues in
  some cases.

  All the dependencies should be installed!

  Distro: Debian Bullseye 11

  
  # apt-get install libopenjp2-7-dev libfreetype6-dev libfontconfig1-dev 
libjpeg-dev libtiff5-dev
  # cd /var/bin && wget https://poppler.freedesktop.org/poppler-23.09.0.tar.xz 
&& tar -xvf poppler-23.09.0.tar.xz
  # cd poppler-23.09.0 && mkdir build && cd build
  # cmake ..

  
  CMake Warning at CMakeLists.txt:95 (message):

  
 No test data found in $testdatadir.
 You will not be able to run 'make test' successfully.


 The test data is not included in the source packages
 and is also not part of the main git repository. Instead,
 you can checkout the test data from its own git
 repository with:


   git clone git://git.freedesktop.org/git/poppler/test


 You should checkout the test data as a sibling of your
 poppler source folder or specify the location of your
 checkout with -DTESTDATADIR=/path/to/checkoutdir/test.


  -- Checking for module 'nss>=3.49'
  --   No package 'nss' found
  -- Could NOT find NSS3 (missing: NSS3_LIBRARIES NSS3_CFLAGS)
  CMake Warning at cmake/modules/MacroOptionalFindPackage.cmake:32 
(find_package):
By not providing "FindGpgmepp.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Gpgmepp", but
CMake did not find one.

Could not find a package configuration file provided by "Gpgmepp"
(requested version 1.19) with any of the following names:

  GpgmeppConfig.cmake
  gpgmepp-config.cmake

Add the installation prefix of "Gpgmepp" to CMAKE_PREFIX_PATH or set
"Gpgmepp_DIR" to a directory containing one of the above files.  If
"Gpgmepp" provides a separate development package or SDK, be sure it has
been installed.
  Call Stack (most recent call first):
CMakeLists.txt:158 (macro_optional_find_package)

  
  CMake Warning at CMakeLists.txt:198 (find_package):
By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5Core", but
CMake did not find one.

Could not find a package configuration file provided by "Qt5Core"
(requested version 5.12) with any of the following names:

  Qt5CoreConfig.cmake
  qt5core-config.cmake

Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set
"Qt5Core_DIR" to a directory containing one of the above files.  If
"Qt5Core" provides a separate development package or SDK, be sure it has
been installed.

  
  CMake Warning at CMakeLists.txt:199 (find_package):
By not providing "FindQt5Gui.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5Gui", but
CMake did not find one.

Could not find a package configuration file provided by "Qt5Gui" with any
of the following names:

  Qt5GuiConfig.cmake
  qt5gui-config.cmake

Add the installation prefix of "Qt5Gui" to CMAKE_PREFIX_PATH or set
"Qt5Gui_DIR" to a directory containing one of the above files.  If "Qt5Gui"
provides a separate development package or SDK, be sure it has been
installed.

  
  CMake Warning at CMakeLists.txt:200 (find_package):
By not providing "FindQt5Xml.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5Xml", but
CMake did not find one.

Could not find a package configuration file provided by "Qt5Xml" with any
of the following names:

  Qt5XmlConfig.cmake
  qt5xml-config.cmake

Add the installation prefix of "Qt5Xml" to CMAKE_PREFIX_PATH or set
"Qt5Xml_DIR" to a directory containing one of the above files.  If "Qt5Xml"
provides a separate development package or SDK, be sure it has been
installed.

  
  CMake Warning at CMakeLists.txt:201 (find_package):
By not providing "FindQt5Widgets.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"Qt5Widgets", but CMake did not find one.

Could not find a package configuration file provided by "Qt5Widgets" with
any of the following names:

  Qt5WidgetsConfig.cmake
  qt5widgets-config.cmake

Add the installation prefix of "Qt5Widgets" to CMAKE_PREFIX_PATH or set
"Qt5Widgets_DIR" to

[Touch-packages] [Bug 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2024-01-22 Thread Aleksandr Mikhalitsyn

>What are your thoughts on (a) and (b)?

>being marked as superficial won't block a migration if it fails (IIRC:
at least, it's definitely not a hard error). And we do want this to
"stop the line" if it fails, right?

Ideally, it's better to block upload of package if this fails, yes.
Because it's really bad to have LXC_DEVEL = 1 in the production release.

>b) it's checking something from the source code, which could be later
changed via d/rules during build. What I mean is that this is not the
place users will get the value of LXC_DEVEL from.

Yeah, ideally, yes. But I have just gone with the simplest possible
solution to check this.

>A DEP8 test is awesome, thanks for that. But it might too close to a
release for such a check. Imagine an SRU gets sponsored, then reviewed,
then accepted, and then we get the DEP8 result that says "oops,
LXC_DEVEL=1 is leaking again". How about also checking it during package
build? I won't block the upload on this, though, but it would be good to
have I think, even if later.

Ah, to be honest I was sure that this check will be performed before
uploading this change to the Ubuntu package repositories. Can you give
me a hint or send me to the manual about how to make this check during
the package build?

>I won't block the upload on this, though, but it would be good to have
I think, even if later.

Thanks for that. Yeah, I think that if everything seems generally fine
to you to upload this as it is I can do this further improvements and
modification in a later patches. As we anyways want (ideally) to rebase
this on top of debian/sid.

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

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2040406] Re: Merge openssh from Debian unstable for noble

2024-01-22 Thread Miriam España Acebal

Current version in Debian Sid is 1:9.6p1-3

** Changed in: openssh (Ubuntu)
 Assignee: (unassigned) => Miriam España Acebal (mirespace)

** Changed in: openssh (Ubuntu)
Milestone: None => ubuntu-24.01

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

Title:
  Merge openssh from Debian unstable for noble

Status in openssh package in Ubuntu:
  New

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1:9.4p1-1
  Ubuntu:   1:9.3p1-1ubuntu3

  
  The NOT SERVER TEAM team has maintained this package in the past and may be 
handling this merge.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  
  ### New Debian Changes ###

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

* New upstream release (https://www.openssh.com/releasenotes.html#9.4p1):
  - ssh-agent(1): PKCS#11 modules must now be specified by their full
paths. Previously dlopen(3) could search for them in system library
directories.
  - ssh(1): allow forwarding Unix Domain sockets via ssh -W.
  - ssh(1): add support for configuration tags to ssh(1). This adds a
ssh_config(5) 'Tag' directive and corresponding 'Match tag' predicate
that may be used to select blocks of configuration similar to the
pf.conf(5) keywords of the same name.
  - ssh(1): add a 'match localnetwork' predicate. This allows matching on
the addresses of available network interfaces and may be used to vary
the effective client configuration based on network location.
  - ssh(1), sshd(8), ssh-keygen(1): infrastructure support for KRL
extensions. This defines wire formats for optional KRL extensions and
implements parsing of the new submessages. No actual extensions are
supported at this point.
  - sshd(8): AuthorizedPrincipalsCommand and AuthorizedKeysCommand now
accept two additional %-expansion sequences: %D which expands to the
routing domain of the connected session and %C which expands to the
addresses and port numbers for the source and destination of the
connection.
  - ssh-keygen(1): increase the default work factor (rounds) for the
bcrypt KDF used to derive symmetric encryption keys for passphrase
protected key files by 50%.
  - ssh-agent(1): improve isolation between loaded PKCS#11 modules by
running separate ssh-pkcs11-helpers for each loaded provider.
  - ssh(1): make -f (fork after authentication) work correctly with
multiplexed connections, including ControlPersist (closes: #348741).
  - ssh(1): make ConnectTimeout apply to multiplexing sockets and not just
to network connections.
  - ssh-agent(1), ssh(1): improve defences against invalid PKCS#11 modules
being loaded by checking that the requested module contains the
required symbol before loading it.
  - sshd(8): fix AuthorizedPrincipalsCommand when AuthorizedKeysCommand
appears before it in sshd_config. Since OpenSSH 8.7 the
AuthorizedPrincipalsCommand directive was incorrectly ignored in this
situation.
  - sshd(8), ssh(1), ssh-keygen(1): remove vestigial support for KRL
signatures. When the KRL format was originally defined, it included
support for signing of KRL objects. However, the code to sign KRLs and
verify KRL signatues was never completed in OpenSSH. This release
removes the partially-implemented code to verify KRLs. All OpenSSH
tools now ignore KRL_SECTION_SIGNATURE sections in KRL files.
  - All: fix a number of memory leaks and unreachable/harmless integer
overflows.
  - ssh-agent(1), ssh(1): don't truncate strings logged from PKCS#11
modules.
  - sshd(8), ssh(1): better validate CASignatureAlgorithms in ssh_config
and sshd_config. Previously this directive would accept certificate
algorithm names, but these were unusable in practice as OpenSSH does
not support CA chains.
  - ssh(1): make `ssh -Q CASignatureAlgorithms` only list signature
algorithms that are valid for CA signing. Previous behaviour was to
list all signing algorithms, including certificate algorithms.
  - ssh-keyscan(1): gracefully handle systems where rlimits or the maximum
number of open files is larger than INT_MAX.
  - ssh-keygen(1): fix 'no comment' not showing on when running
`ssh-keygen -l` on multiple keys where one has a comment and other
following keys do not. bz3580
  - scp(1), sftp(1): adjust ftruncate() logic to handle servers that
reorder requests. Previously, if the server reordered requests then
the resultant file would be erroneously truncated.
  -

[Touch-packages] [Bug 2049995] Re: System volume doesn't change volume

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

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

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

Title:
  System volume doesn't change volume

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Hi, as described here https://askubuntu.com/questions/1487030/system-
  volume-doesnt-change-app-volume, I also have this problem.

  I've already tried to boot with a Manjaro USB live with Gnome and
  there the volume works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  japimentel   8590 F wireplumber
   /dev/snd/controlC0:  japimentel   8590 F wireplumber
   /dev/snd/seq:japimentel   8580 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 21 10:28:26 2024
  InstallationDate: Installed on 2023-11-21 (61 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2023
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MLCN21WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Pro 7 14APH8
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrMLCN21WW:bd07/12/2023:br1.21:efr1.21:svnLENOVO:pn82Y8:pvrYogaPro714APH8:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrYogaPro714APH8:skuLENOVO_MT_82Y8_BU_idea_FM_YogaPro714APH8:
  dmi.product.family: Yoga Pro 7 14APH8
  dmi.product.name: 82Y8
  dmi.product.sku: LENOVO_MT_82Y8_BU_idea_FM_Yoga Pro 7 14APH8
  dmi.product.version: Yoga Pro 7 14APH8
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2049995/+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 2047656] Re: [SRU] Players terminate after stopping and restarting

This bug was fixed in the package fluidsynth - 2.3.3-2.1ubuntu0.23.10.1

---
fluidsynth (2.3.3-2.1ubuntu0.23.10.1) mantic; urgency=medium

  * Patch to fix player termination after stopping and restarting (LP:
#2047656)

 -- Erich Eickmeyer   Wed, 03 Jan 2024 09:39:14
-0800

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

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

Title:
  [SRU] Players terminate after stopping and restarting

Status in fluidsynth package in Ubuntu:
  Fix Released
Status in fluidsynth source package in Mantic:
  Fix Released
Status in fluidsynth source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop
  of playback of a midi song, causing issues for a multitude of players
  including EasyABC. This will cause said player to be unable to
  playback again and perhaps even crash. See
  https://github.com/FluidSynth/fluidsynth/issues/1272, fix in
  
https://github.com/FluidSynth/fluidsynth/commit/377ab9db2f87bc407eeb940e0361edc77da77055.
  This is the included patch with the upload of
  2.3.3-2.1ubuntu-0.23.10.1

  [ Test Case ]

  * To reproduce the bug:

  # download sample midi file from wikiepdia:

  wget
  https://upload.wikimedia.org/wikipedia/commons/5/55/MIDI_sample.mid

  # play it with fluidsynth

  fluidsynth MIDI_sample.mid

  # at this point, you will actually be at a prompt. Wait for the song
  to play for a few seconds, then issue a stop command at that prompt:

  player_stop

  # And this is where the bug happens. Issue a continuation:

  player_cont

  And this is where things break:

  > player_cont
  > fluidsynth: error: The maximum playback duration has been reached. 
Terminating player!

  * With the fixed package, the audio resumes playback.

  [ What could go wrong ]

  This is actually a fix for a regression that was found in version
  2.3.3 of fluidsynth and fixed for 2.3.4, which can be found in noble.
  I think the only thing that can go wrong here is that this patch is
  not the actual fix and we need to find more solutions within.

  I have tested this in my PPA and it *seems* to fix it, but it would be
  nice if the original reporter could verify once this lands in
  proposed.

  [ Other information ]

  Included below is the original report, in which case the reporter
  deduces that the problem is the binary being spat-out is the 2.3.2
  version from the 2.3.3 sources. This is not the case, as it appears to
  be confusion due to the -2.1 Debian revision number. I assure, this is
  definitely the 2.3.3, and the bug, per the github link in the Impact
  section, is pertinent to this version.

  ---

  The latest package of fluidsynth should include the sources from
  version 2.3.3 but the binary includes only version 2.3.2

  This version has a bug (see
  https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to
  problems in EasyABC.

  Please include the latest version 2.3.3 from upstream in the ubuntu
  package.

  --

  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  $ apt-cache policy libfluidsynth3
  libfluidsynth3:
    Installiert:   2.3.3-2.1
    Installationskandidat: 2.3.3-2.1
    Versionstabelle:
   *** 2.3.3-2.1 500
  500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/+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 80900] Re: Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks

** Changed in: nss-mdns (Debian)
   Status: Unknown => Fix Released

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

Title:
  Avahi daemon prevents resolution of FQDNs ending in ".local" due to
  false negatives in the detection of ".local" networks

Status in avahi package in Ubuntu:
  Fix Released
Status in nss-mdns package in Ubuntu:
  Fix Released
Status in nss-mdns package in Debian:
  Fix Released

Bug description:
  Install Kubuntu Feisty
  Set the ip address to dhcp for eth0 (ethernet port)
  make sure the host name and domain name are set
  Hostname computer1
  DomainName mydomain.local
  allow DHCP to assign the IP address

  Ensure the computer details are registered in DNS for
  mydomain.local...

  computer names registered in DNS (FQDN)
  computer1.mydomain.local
  computer2.mydomain.local
  computer3.mydomain.local

  computer2 and computer3 are both running Kubuntu Dapper and are both
  using DHCP.

  if I issue the following comands on computer2 or computer3, it works
  correctly:

  ping computer2  (response received - ping good)
  ping computer3  (response received - ping good)
  ping computer2.mydomain.local   (response received - ping good)
  ping computer3.mydomain.local   (response received - ping good)

  if i issue the same commands from the feisty box (computer1), these
  are the results..

  ping computer2   (response received - ping good)
  ping computer3   (response received - ping good)
  ping computer2.mydomain.local   (unknown host)
  ping computer3.mydomain.local  (unknown host)
  for some reason if you try to ping the fully qualified domain name on feisty, 
it cant resolve it, yet it can resolve it using both static IP Addressing and 
DHCP addressing on Dapper. (i set the IP to static as well for the test) Static 
and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified 
domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu 
machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu 
server very soon though!)

  It can resolve the host name only though, and will return the fully
  qualified domain name in the response.

  cheers

  Rod.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/80900/+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 2045737] Re: Logitech MX Master 3 is detected as a keyboard in Power Statistics

** Changed in: upower
   Status: Unknown => New

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

Title:
  Logitech MX Master 3 is detected as a keyboard in Power Statistics

Status in Upower:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  My Logitech MX Master 3 is detected as a keyboard in Power Statistics,
  it's not a critical issue as beyond this everything works fine.

  I'm using the Logitech Unifying Receiver to connect my MX Keys
  Keyboard and MX Master 3 Mouse, those are working fine but sometimes I
  get the notification of low battery, but I'm not so sure what is the
  device as it says Keyboard and the mouse is identified by Power
  Statistics as a Keyboard.

  This is the info from Power Statistics window:

  Device: battery_hidpp_battery_o
  Type: Leyboard
  Model: Wireless Mouse MX Master 3
  Serial number: bc-83-96-ed
  Supply: No
  Refreshed: 0 seconds
  Present: Yes
  Rechargable: Yes
  State: Discharging
  Percentage: 50.0%

  
  This is the info related to the Dongle from lsusb:

  ```
  Bus 003 Device 012: ID 046d:c52b Logitech, Inc. Unifying Receiver
  ```

  lshw information:

  ```
*-input:12
 product: Logitech MX Keys
 physical id: e
 logical name: input33
 logical name: /dev/input/event6
 logical name: input33::capslock
 logical name: input33::compose
 logical name: input33::kana
 logical name: input33::numlock
 logical name: input33::scrolllock
 logical name: /dev/input/mouse2
 capabilities: usb
*-input:13
 product: Logitech MX Master 3
 physical id: f
 logical name: input34
 logical name: /dev/input/event7
 logical name: input34::capslock
 logical name: input34::compose
 logical name: input34::kana
 logical name: input34::numlock
 logical name: input34::scrolllock
 logical name: /dev/input/mouse3
 capabilities: usb
  ```

  From the information above, this could be related to another package
  (even the kernel?) and not specifically gnome-power-manager

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-power-manager 43.0-1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  6 08:33:41 2023
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2023-05-04 (215 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-power-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/2045737/+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 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate

2024-01-22 Thread Frank Heimes

verification on jammy was successful

** Description changed:

  === SRU information ===
  
  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422
  
  [Impact]
  Openssl using an engine dumps core upon certificate creation; other 
operations are probably affected too. Overall, engines are likely mostly 
unusable.
  
  [Test plan]
  - An openssl engine is req. to test the fix.
  - A z13 / LinuxONE LPAR or z/VM guest is needed, with attached APQN.
  - Check with 'lszcrypt -V' the availability (online) of the hw crypto 
resources.
  - Install the needed package that allows to exploit the hw crypto resources:
-   sudo apt-get install libica-utils libica? openssl-ibmca
+   sudo apt-get install libica-utils libica? openssl-ibmca
  - And copy a working sample openssf.cnf file:
-   sudo cp /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample 
/etc/ssl/openssl.cnf
- - Verify if the 'openssl engine' lists an ibmca engine, in addition to the 
dynamic engine:
-   (dynamic) Dynamic engine loading support
-   (ibmca) Ibmca hardware engine support  <===
+   sudo cp /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample 
/etc/ssl/openssl.cnf
+ - Verify if the 'openssl engine' lists an ibmca engine,
+   in addition to the dynamic engine:
+   openssl engine
+     (dynamic) Dynamic engine loading support
+     (ibmca) Ibmca hardware engine support  <===
  - try to create a new certificate, using this cmd-line:
-   openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
+   openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  - The above command must not lead to a 'Segmentation fault (core dumped)',
-   rather than create a proper certificate file.
-   Also watch /var/log/syslog / journalctl for more details.
+   rather than create a proper certificate file.
+   Also watch /var/log/syslog / journalctl for more details.
+ - Upgrade not only the openssl package itself,
+   but also libssl3, before verification.
  - The issue is fixed in openssl 3.0.8 which landed in lunar.
  
  [Where problems could occur]
  I don't pretend to understand the lifecycle of providers in openssl3 but the 
patch is simple and has been widely tested by now, including on ubuntu. Thus, I 
see little chance an unexpected problem would occur with it.
  
  [Patches]
  The patches come directly from upstream and apply cleanly.
  
  https://github.com/openssl/openssl/issues/18578
  
  *
  
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-
  sru-0001-Release-the-drbg-in-the-global-default-context-
  befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0
  
  === Original description ===
  
  openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem
  -keyout __key.pem --subj '/CN=US'
  
  ---Problem Description---
  OpenSSL with ibmca engine configured dumps core when creating a new 
certificate.
  
  # openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  # openssl req  -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  Segmentation fault (core dumped)
  
  # journalctl
  Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b 
ilc:2 in libc.so.6[3ffae08+1ca000]
  Jun 07 13:06:08 SYSTEM kernel: Failing address:  TEID: 
0800
  Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user 
ASCE.
  Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024
  Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded 
Not tainted 5.15.0-73-generic #80-Ubuntu
  Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0)
  Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708
  Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 
AS:0 CC:0 PM:0 RI:0 EA:3
  Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 
 02aa3289f9d0
  Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 
 02aa328a4300
  Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 
02aa03ff 
  Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 
03ffae437c22 03ffec2fe000
  Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2  
  lgr%r11,%r2
    03ffae11c700: 
4700bc0,0
   #03ffae11c704: 
b24f00a0ear%r10,%a0
   >03ffae11c708: 
58102018l%r1,24(%r2)

[Touch-packages] [Bug 2047656] Update Released

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

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

Title:
  [SRU] Players terminate after stopping and restarting

Status in fluidsynth package in Ubuntu:
  Fix Released
Status in fluidsynth source package in Mantic:
  Fix Committed
Status in fluidsynth source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Fluidsynth 2.3.3 has an issue where it will terminate upon start/stop
  of playback of a midi song, causing issues for a multitude of players
  including EasyABC. This will cause said player to be unable to
  playback again and perhaps even crash. See
  https://github.com/FluidSynth/fluidsynth/issues/1272, fix in
  
https://github.com/FluidSynth/fluidsynth/commit/377ab9db2f87bc407eeb940e0361edc77da77055.
  This is the included patch with the upload of
  2.3.3-2.1ubuntu-0.23.10.1

  [ Test Case ]

  * To reproduce the bug:

  # download sample midi file from wikiepdia:

  wget
  https://upload.wikimedia.org/wikipedia/commons/5/55/MIDI_sample.mid

  # play it with fluidsynth

  fluidsynth MIDI_sample.mid

  # at this point, you will actually be at a prompt. Wait for the song
  to play for a few seconds, then issue a stop command at that prompt:

  player_stop

  # And this is where the bug happens. Issue a continuation:

  player_cont

  And this is where things break:

  > player_cont
  > fluidsynth: error: The maximum playback duration has been reached. 
Terminating player!

  * With the fixed package, the audio resumes playback.

  [ What could go wrong ]

  This is actually a fix for a regression that was found in version
  2.3.3 of fluidsynth and fixed for 2.3.4, which can be found in noble.
  I think the only thing that can go wrong here is that this patch is
  not the actual fix and we need to find more solutions within.

  I have tested this in my PPA and it *seems* to fix it, but it would be
  nice if the original reporter could verify once this lands in
  proposed.

  [ Other information ]

  Included below is the original report, in which case the reporter
  deduces that the problem is the binary being spat-out is the 2.3.2
  version from the 2.3.3 sources. This is not the case, as it appears to
  be confusion due to the -2.1 Debian revision number. I assure, this is
  definitely the 2.3.3, and the bug, per the github link in the Impact
  section, is pertinent to this version.

  ---

  The latest package of fluidsynth should include the sources from
  version 2.3.3 but the binary includes only version 2.3.2

  This version has a bug (see
  https://github.com/FluidSynth/fluidsynth/issues/1272), which leads to
  problems in EasyABC.

  Please include the latest version 2.3.3 from upstream in the ubuntu
  package.

  --

  Description:  Ubuntu 23.10
  Release:  23.10
  Codename: mantic

  $ apt-cache policy libfluidsynth3
  libfluidsynth3:
    Installiert:   2.3.3-2.1
    Installationskandidat: 2.3.3-2.1
    Versionstabelle:
   *** 2.3.3-2.1 500
  500 http://de.archive.ubuntu.com/ubuntu mantic/universe amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fluidsynth/+bug/2047656/+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 2049885] Re: Merge console-setup (1.223) from Debian

2024-01-22 Thread Heinrich Schuchardt

The merge request is available in.
https://code.launchpad.net/~xypron/ubuntu/+source/console-setup/+git/console-setup/+merge/459147

When running 'dpkg-buildpackage -D -sa -d' file
Keyboard/KeyboardNames.pl is updated. I have put the changes due to this
into the patch titled "- generated file Keyboard/KeyboardNames.pl".

console-setup - 1.223ubuntu1 is available in ppa:xypron/merge-from-
debian.

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

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

Title:
  Merge console-setup (1.223) from Debian

Status in console-setup package in Ubuntu:
  New

Bug description:
  In Debian console-setup (1.223) 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/2049885/+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 2045737] Re: Logitech MX Master 3 is detected as a keyboard in Power Statistics

2024-01-22 Thread Julian Alarcon

** Package changed: gnome-power-manager (Ubuntu) => upower (Ubuntu)

** Bug watch added: gitlab.freedesktop.org/upower/upower/-/issues #215
   https://gitlab.freedesktop.org/upower/upower/-/issues/215

** Also affects: upower via
   https://gitlab.freedesktop.org/upower/upower/-/issues/215
   Importance: Unknown
   Status: Unknown

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

Title:
  Logitech MX Master 3 is detected as a keyboard in Power Statistics

Status in Upower:
  Unknown
Status in upower package in Ubuntu:
  New

Bug description:
  My Logitech MX Master 3 is detected as a keyboard in Power Statistics,
  it's not a critical issue as beyond this everything works fine.

  I'm using the Logitech Unifying Receiver to connect my MX Keys
  Keyboard and MX Master 3 Mouse, those are working fine but sometimes I
  get the notification of low battery, but I'm not so sure what is the
  device as it says Keyboard and the mouse is identified by Power
  Statistics as a Keyboard.

  This is the info from Power Statistics window:

  Device: battery_hidpp_battery_o
  Type: Leyboard
  Model: Wireless Mouse MX Master 3
  Serial number: bc-83-96-ed
  Supply: No
  Refreshed: 0 seconds
  Present: Yes
  Rechargable: Yes
  State: Discharging
  Percentage: 50.0%

  
  This is the info related to the Dongle from lsusb:

  ```
  Bus 003 Device 012: ID 046d:c52b Logitech, Inc. Unifying Receiver
  ```

  lshw information:

  ```
*-input:12
 product: Logitech MX Keys
 physical id: e
 logical name: input33
 logical name: /dev/input/event6
 logical name: input33::capslock
 logical name: input33::compose
 logical name: input33::kana
 logical name: input33::numlock
 logical name: input33::scrolllock
 logical name: /dev/input/mouse2
 capabilities: usb
*-input:13
 product: Logitech MX Master 3
 physical id: f
 logical name: input34
 logical name: /dev/input/event7
 logical name: input34::capslock
 logical name: input34::compose
 logical name: input34::kana
 logical name: input34::numlock
 logical name: input34::scrolllock
 logical name: /dev/input/mouse3
 capabilities: usb
  ```

  From the information above, this could be related to another package
  (even the kernel?) and not specifically gnome-power-manager

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-power-manager 43.0-1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  6 08:33:41 2023
  ExecutablePath: /usr/bin/gnome-power-statistics
  InstallationDate: Installed on 2023-05-04 (215 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-power-manager
  UpgradeStatus: Upgraded to mantic on 2023-11-03 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/2045737/+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 2045737] [NEW] Logitech MX Master 3 is detected as a keyboard in Power Statistics

You have been subscribed to a public bug:

My Logitech MX Master 3 is detected as a keyboard in Power Statistics,
it's not a critical issue as beyond this everything works fine.

I'm using the Logitech Unifying Receiver to connect my MX Keys Keyboard
and MX Master 3 Mouse, those are working fine but sometimes I get the
notification of low battery, but I'm not so sure what is the device as
it says Keyboard and the mouse is identified by Power Statistics as a
Keyboard.

This is the info from Power Statistics window:

Device: battery_hidpp_battery_o
Type: Leyboard
Model: Wireless Mouse MX Master 3
Serial number: bc-83-96-ed
Supply: No
Refreshed: 0 seconds
Present: Yes
Rechargable: Yes
State: Discharging
Percentage: 50.0%


This is the info related to the Dongle from lsusb:

```
Bus 003 Device 012: ID 046d:c52b Logitech, Inc. Unifying Receiver
```

lshw information:

```
  *-input:12
   product: Logitech MX Keys
   physical id: e
   logical name: input33
   logical name: /dev/input/event6
   logical name: input33::capslock
   logical name: input33::compose
   logical name: input33::kana
   logical name: input33::numlock
   logical name: input33::scrolllock
   logical name: /dev/input/mouse2
   capabilities: usb
  *-input:13
   product: Logitech MX Master 3
   physical id: f
   logical name: input34
   logical name: /dev/input/event7
   logical name: input34::capslock
   logical name: input34::compose
   logical name: input34::kana
   logical name: input34::numlock
   logical name: input34::scrolllock
   logical name: /dev/input/mouse3
   capabilities: usb
```

>From the information above, this could be related to another package
(even the kernel?) and not specifically gnome-power-manager

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-power-manager 43.0-1
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec  6 08:33:41 2023
ExecutablePath: /usr/bin/gnome-power-statistics
InstallationDate: Installed on 2023-05-04 (215 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
SourcePackage: gnome-power-manager
UpgradeStatus: Upgraded to mantic on 2023-11-03 (33 days ago)

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


** Tags: amd64 apport-bug mantic
-- 
Logitech MX Master 3 is detected as a keyboard in Power Statistics
https://bugs.launchpad.net/bugs/2045737
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to upower in Ubuntu.

-- 
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 1903995] Re: upower report wrong battery percentage for Logitech Unify devices

2024-01-22 Thread Julian Alarcon

Is it related to this? https://bugs.launchpad.net/ubuntu/+source/gnome-
power-manager/+bug/2045737

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

Title:
  upower report wrong battery percentage for Logitech Unify devices

Status in upower package in Ubuntu:
  Triaged

Bug description:
  The battery percentage reported by upower for Logitech devices
  connected using Unify receiver are wrong.  Below are the results for
  two devices: Mouse and Keyboard:

  * Battery percentages reported by Unify receiver using Solaar:

  $ solaar show  | grep -iP "^((  \d: )|(.*batt.*))"
    1: Wireless Keyboard K270(unifying)
   4: BATTERY STATUS {1000}
   Battery: 70%, discharging.
    2: Wireless Mouse MX Master
   7: BATTERY STATUS {1000}
   Battery: 20%, discharging.

  
  * Battery percentages reported by upower:

  $ upower -i /org/freedesktop/UPower/devices/keyboard_hidpp_battery_0
    native-path:  hidpp_battery_0
    model:Wireless Keyboard K270
    serial:   4003-1a-39-5f-c1
    power supply: no
    updated:  Thu 12 Nov 2020 13:59:18 CET (119 seconds ago)
    has history:  yes
    has statistics:   yes
    keyboard
  present: yes
  rechargeable:yes
  state:   discharging
  warning-level:   none
  battery-level:   normal
  percentage:  55% (should be ignored)
  icon-name:  'battery-low-symbolic'

  $ upower -i /org/freedesktop/UPower/devices/mouse_hidpp_battery_1
    native-path:  hidpp_battery_1
    model:Wireless Mouse MX Master
    serial:   4071-f8-eb-bf-d1
    power supply: no
    updated:  Thu 12 Nov 2020 14:03:14 CET (27 seconds ago)
    has history:  yes
    has statistics:   yes
    mouse
  present: yes
  rechargeable:yes
  state:   discharging
  warning-level:   low
  battery-level:   low
  percentage:  10% (should be ignored)
  icon-name:  'battery-caution-symbolic'


  Basically the difference is big so I'm getting a lot of notifications
  related to low battery even if the battery is OK:

  * Mouse, upower: 10%real (Solaar): 20%
  * Keyboard: upower: 70%real (Solaar): 55%



  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: upower 0.99.11-1build2
  ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
  Uname: Linux 5.4.0-53-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 12 13:58:35 2020
  InstallationDate: Installed on 2020-04-19 (206 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2020-06-17T11:02:56.934699

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1903995/+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 1994165] Autopkgtest regression report (openssl/3.0.2-0ubuntu1.13)

All autopkgtests for the newly accepted openssl (3.0.2-0ubuntu1.13) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

diffoscope/205 (armhf)
dotnet6/6.0.126-0ubuntu1~22.04.1 (amd64, arm64)
ganeti/3.0.2-1ubuntu1 (armhf)
linux-aws-5.19/5.19.0-1029.30~22.04.1 (arm64)
linux-aws-6.5/6.5.0-1011.11~22.04.1 (arm64)
linux-azure-6.2/6.2.0-1018.18~22.04.1 (arm64)
linux-gcp-6.2/6.2.0-1019.21~22.04.1 (arm64)
linux-gke/5.15.0-1048.53 (arm64)
linux-lowlatency-hwe-6.2/6.2.0-1018.18~22.04.1 (arm64)
linux-lowlatency-hwe-6.5/6.5.0-14.14.1~22.04.1 (arm64)
linux-mtk/5.15.0-1029.33 (arm64)
linux-nvidia-6.5/6.5.0-1010.10 (arm64)
linux-oracle-6.2/6.2.0-1017.18~22.04.1 (arm64)
puma/5.5.2-2ubuntu2 (arm64)
python-bonsai/1.3.0+ds-3build1 (armhf)
ruby3.0/3.0.2-7ubuntu2.4 (amd64, arm64, i386)
seqkit/2.1.0+ds-1 (s390x)


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

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

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

Title:
  CMS_final: do not ignore CMS_dataFinal result

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Kinetic:
  Won't Fix
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  S/MIME signature can fail silently
  The commit by upstream propagates the return code of some functions rather 
than ignore it.

  [Test plan]
  This issue is not very simple to reproduce because "openssl cms" cannot be 
used to do so. This has to be done with the openssl API instead.
  At least the bug reportere here and the one on openssl's bug tracker have 
confirmed the patch solves the issue. Additionally, the bug reporter here has 
tested the PPA that contains the patche and validated it. Finally, I read 
through the patch attentively.

  [Where problems could occur]
  At this point it is unlikely an error would appear. The openssl bug tracker 
mentions nothing related to this patch which landed more than a year ago. The 
patch is simple and doesn't change the code logic.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/pull/18876

  * 
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0001-REGRESSION-CMS_final-do-not-ignore-CMS_dataFinal-res.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0
  * 
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-sru-0002-Handle-SMIME_crlf_copy-return-code.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  https://github.com/openssl/openssl/pull/18876

  The CMS_dataFinal result is important as signature may fail, however, it
  is ignored while returning success from CMS_final.

  Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)"

  Thanks

  Upstream commit:

  ```
  commit 67c0460b89cc1b0644a1a59af78284dfd8d720af
  Author: Alon Bar-Lev 
  Date:   Tue Jul 26 15:17:06 2022 +0300

  Handle SMIME_crlf_copy return code

  Currently the SMIME_crlf_copy result is ignored in all usages. It does
  return failure when memory allocation fails.

  This patch handles the SMIME_crlf_copy return code in all
  occurrences.

  Signed-off-by: Alon Bar-Lev 

  Reviewed-by: Tomas Mraz 
  Reviewed-by: Paul Dale 
  Reviewed-by: Hugo Landau 
  (Merged from https://github.com/openssl/openssl/pull/18876)
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 2033422] Autopkgtest regression report (openssl/3.0.2-0ubuntu1.13)

All autopkgtests for the newly accepted openssl (3.0.2-0ubuntu1.13) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

diffoscope/205 (armhf)
dotnet6/6.0.126-0ubuntu1~22.04.1 (amd64, arm64)
ganeti/3.0.2-1ubuntu1 (armhf)
linux-aws-5.19/5.19.0-1029.30~22.04.1 (arm64)
linux-aws-6.5/6.5.0-1011.11~22.04.1 (arm64)
linux-azure-6.2/6.2.0-1018.18~22.04.1 (arm64)
linux-gcp-6.2/6.2.0-1019.21~22.04.1 (arm64)
linux-gke/5.15.0-1048.53 (arm64)
linux-lowlatency-hwe-6.2/6.2.0-1018.18~22.04.1 (arm64)
linux-lowlatency-hwe-6.5/6.5.0-14.14.1~22.04.1 (arm64)
linux-mtk/5.15.0-1029.33 (arm64)
linux-nvidia-6.5/6.5.0-1010.10 (arm64)
linux-oracle-6.2/6.2.0-1017.18~22.04.1 (arm64)
puma/5.5.2-2ubuntu2 (arm64)
python-bonsai/1.3.0+ds-3build1 (armhf)
ruby3.0/3.0.2-7ubuntu2.4 (amd64, arm64, i386)
seqkit/2.1.0+ds-1 (s390x)


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

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

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

Title:
  openssl: backport to jammy "clear method store / query cache
  confusion"

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [ATTENTION]
  This SRU contains THREE changes which are listed in the section below.

  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  This ( #2033422 ) is the "central" bug with the global information and 
debdiff.

  This SRU addresses three issues with Jammy's openssl version:
  - http://pad.lv/1994165: ignored SMIME signature errors
  - http://pad.lv/2023545: imbca engine dumps core
  - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections 
(this one)

  The SRU information has been added to the three bug reports and I am
  attaching the debdiff here only for all three.

  All the patches have been included in subsequent openssl 3.0.x
  releases which in turn have been included in subsequent Ubuntu
  releases. There has been no report of issues when updating to these
  Ubuntu releases.

  I have rebuilt the openssl versions and used abi-compliance-checker to
  compare the ABIs of the libraries in jammy and the one for the SRU.
  Both matched completely (FYI, mantic's matched completely too).

  I have also pushed the code to git (without any attempt to make it
  git-ubuntu friendly).

  
https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy-
  sru

  I asked Brian Murray about phasing speed and he concurs a slow roll-out is 
probably better for openssl. There is a small uncertainty because a security 
update could come before the phasing is over, effectively fast-forwarding the 
SRU. Still, unless there is already a current pre-advisory, this is probably 
better than a 10% phasing which is over after only a couple days anyway.
  NB: at the moment openssl doesn't phase slowly so this needs to be 
implemented.

  [Impact]
  Severely degraded performance for concurrent operations compared to openssl 
1.1. The performance is so degraded that some workloads fail due to timeouts or 
insufficient resources (noone magically has 5 times more machines). As a 
consequence, a number of people use openssl 1.1 instead and do not get security 
updates.

  [Test plan]
  Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py
 .

  To test, follow these steps:
  - run "time python3 main.py" # using the aforementioned main.py script
  - apt install -t jammy-proposed libssl3
  - run "time python3 main.py"
  - compare the runtimes for the two main.py runs

  You can run this on x86_64, Raspberry Pi 4 or any machine, and get a
  very large speed-up in all cases. The improvements are not
  architecture-dependant.

  Using this changeset, I get the following numbers for ten runs on my
  laptop:

  3.0.2:
  real  2m5.567s
  user  4m3.948s
  sys   2m0.233s

  this SRU:
  real  0m23.966s
  user  2m35.687s
  sys   0m1.920s

  As can be easily seen, the speed-up is massive: system time is divided
  by 60 and overall wall clock time is roughly five times lower.

  In http://pad.lv/2009544 , Rafael also shared his performance numbers
  and they are relatable to these. He used slightly different versions
  (upstreams rather than patched with cherry-picks) but at least one of
  the version used does not include other performance change. He also
  used

[Touch-packages] [Bug 2023545] Autopkgtest regression report (openssl/3.0.2-0ubuntu1.13)