[Touch-packages] [Bug 2075988] Re: Add comments to default config to explain Ubuntu deltas

[Mitchell Dzurick]

Works for me, I just wanted to make this bug since I've seen some
complaints (see the discourse link) to help raise awareness.

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

Title:
  Add comments to default config to explain Ubuntu deltas

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Hello, reading https://discourse.ubuntu.com/t/sshd-now-uses-socket-
  based-activation-ubuntu-22-10-and-later/30189/44 a great point is made
  here.

  Can we put some comments in the default config explaining the deltas
  we make? This would be the most visible place for end-users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2075988/+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 2060666] Re: [SRU] Memory leak in krb5 version 1.17

[Mitchell Dzurick]

There was one more testbed failure for arm64 balsa. I reran that.

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

Title:
  [SRU] Memory leak in krb5 version 1.17

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Commit 
https://github.com/krb5/krb5/commit/1cd2821c19b2b95e39d5fc2f451a035585a40fa5
  altered the memory management of krb5_gss_inquire_cred(), introducing defcred 
to act as
  an owner pointer when the function must acquire a default credential.
  The commit neglected to update the code to release the default cred
  along the successful path. The old code does not trigger because
  cred_handle is now reassigned, so the default credential is leaked.

  Resulting gradual increase in memory usage (memory leak) and eventual
  crash.

  [ Test Plan ]

  Setup 3 VMs:

  1. Windows Server act as Domain controller (AD)
  2. Windows machine AD Joined with Ostress installed. (Ostress is part of RML 
utilities 
https://learn.microsoft.com/en-us/troubleshoot/sql/tools/replay-markup-language-utility)
  3. SQL on Linux AD Joined ( configuration steps 
https://learn.microsoft.com/en-us/sql/linux/sql-server-linux-ad-auth-adutil-tutorial?view=sql-server-ver16)

  On the Machine with OStress create a file (name it disconnect.ini)
  with the following content under the same folder “C:\Program
  Files\Microsoft Corporation\RMLUtils” where OStress is installed.

  disconnect.ini
  ==

  [Connection Options]
  LoginTimeout=30
  QuotedIdentifier=Off
  AutocommitMode=On
  DisconnectPct=100.0
  MaxThreadErrors=0

  [Query Options]
  NoSQLBindCol=Off
  NoResultDisplay=Off
  PrepareExecute=Off
  ExecuteAsync=Off
  RollbackOnCancel=Off
  QueryTimeout=0
  QueryDelay=0
  MaxRetries=0
  BatchDisconnectPct=0.0
  CancelPct=0.00
  CancelDelay=0
  CancelDelayMin=0
  CursorType=
  CursorConcurrency=
  RowFetchDelay=0

  [Replay Options]
  Sequencing Options=global sequence
  ::Sequencing Options=global sequence, dtc replay
  DTC Timeout=
  DTC Machine=(local)
  Playback Coordinator=(local)
  StartSeqNum=
  StopSeqNum=
  TimeoutFactor=1.0

  Run the following command to start the load using Ostress, change
  Server name (-S) accordingly and the number of threads (-n) as needed.

  Start 4 different CMD consoles and use the following different commands for 
each CMD window:
  1. ostress.exe -E -S -Q"select * from sys.all_objects" -q 
-cdisconnect.ini -n40 -r999 -oc:\temp\log01 -T146
  2. ostress.exe -E -S -Q"select * from sys.all_views" -q 
-cdisconnect.ini -n40 -r999 -oc:\temp\log02 -T146
  3. ostress.exe -E -S -Q"select * from sys.all_columns" -q 
-cdisconnect.ini -n40 -r999 -oc:\temp\log03 -T146
  4. ostress.exe -E -S -Q"select * from sys.all_parameters" -q 
-cdisconnect.ini -n40 -r999 -oc:\temp\log04 -T146

  After a run of about 5 hours, the memory usage for this is expected to be 
around 5G with the fix.
  Without the fix, it was observed that it reached around ~22G in 5 hours. 
Hence the increase in 
  memory usage can be observed if the ostress.exe programs are let to run 
longer.

  [ Where problems could occur ]

   The fix may not fix the memory leak or could result in releasing the memory
   early in a different code path, and thus resulting in crashes.
   
   A mitigating fact is that the fix has been in Ubuntu since at least 22.04 and
   they do not exhibit any issues.
   
   Likewise I've previously provided the fix in a PPA 
https://launchpad.net/~pponnuvel/+archive/ubuntu/krb5-focal
   to user who's been hit by this issue. They've tested and confirmed it fixes 
the memory leak.
   
  [ Other Info ]

  The commit
  https://github.com/krb5/krb5/commit/098f874f3b50dd2c46c0a574677324b5f6f3a1a8
  fixes the leak.

  The fix has been included in newer krb5 releases (Jammy, and Noble
  have the releases with the fix).

  Bionic doesn't have the commit the introduced the memory leak in the first 
place.
  So this will be a Focal-only backport.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/2060666/+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 2075988] [NEW] Add comments to default config to explain Ubuntu deltas

[Mitchell Dzurick]

Public bug reported:

Hello, reading https://discourse.ubuntu.com/t/sshd-now-uses-socket-
based-activation-ubuntu-22-10-and-later/30189/44 a great point is made
here.

Can we put some comments in the default config explaining the deltas we
make? This would be the most visible place for end-users.

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

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

Title:
  Add comments to default config to explain Ubuntu deltas

Status in openssh package in Ubuntu:
  New

Bug description:
  Hello, reading https://discourse.ubuntu.com/t/sshd-now-uses-socket-
  based-activation-ubuntu-22-10-and-later/30189/44 a great point is made
  here.

  Can we put some comments in the default config explaining the deltas
  we make? This would be the most visible place for end-users.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2075988/+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 2073950] Re: Merge curl 8.9.0-1 from Debian unstable

[Mitchell Dzurick]

Hi Dominik, do be aware of https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1077190

** Bug watch added: Debian Bug tracker #1077190
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1077190

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

Title:
  Merge curl 8.9.0-1 from Debian unstable

Status in curl package in Ubuntu:
  In Progress
Status in curl source package in Oracular:
  In Progress

Bug description:
  This is the tracking bug report for merging curl 8.9.0-1 from Debian
  unstable into Ubuntu Oracular Oriole.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2073950/+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 2064457] Re: Merge rsync from Debian unstable for oracular

[Mitchell Dzurick]

** Changed in: rsync (Ubuntu)
 Assignee: Sergio Durigan Junior (sergiodj) => Mitchell Dzurick (mitchdz)

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

Title:
  Merge rsync from Debian unstable for oracular

Status in rsync package in Ubuntu:
  New

Bug description:
  Upstream: tbd
  Debian:   3.3.0-1
  Ubuntu:   3.2.7-1ubuntu1


  Debian does new releases regularly, so it's likely there will be newer
  versions available before FF that we can pick up if this merge is done
  later in the cycle.

  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.

  If this merge pulls in a new upstream version, also consider adding an
  entry to the Oracular Release Notes:
  https://discourse.ubuntu.com/c/release/38

  
  ### New Debian Changes ###

  rsync (3.3.0-1) unstable; urgency=medium

[ Aquila Macedo Costa ]
* d/control: Bump Standards-Version to 4.6.2

[ Samuel Henrique ]
* New upstream version 3.3.0 (closes: #1068630)
* Bump Standards-Version to 4.7.0
* Update patches
* d/patches: Drop merged patches
* d/control: Drop dependency on lsb-base
* d/rsync.lintian-overrides: Update overrides

   -- Samuel Henrique   Fri, 12 Apr 2024 00:28:29
  +0100

  rsync (3.2.7-1) unstable; urgency=medium

[ Juri Grabowski ]
* New upstream version 3.2.7
* Remove patches included in new release

[ Helmut Grohne ]
* Fix FTCBFS: Use native instances for python build depends
  (closes: #1022988).

[ Samuel Henrique ]
* d/rsync.lintian-overrides: Update findings as per lintian changes
* d/patches: Add two upstream patches to fix issues post 3.2.7 release:
  - trust_the_sender_on_a_local_transfer.patch
  - avoid_quoting_of_tilde_when_its_a_destination_arg.patch

   -- Samuel Henrique   Sun, 18 Dec 2022 14:10:54
  +

  rsync (3.2.6-4) unstable; urgency=medium

* Upload to unstable
  - d/patches:
~ fix_files_from.patch: Upstream patch to address the files-from issue.
~ fix_relative.patch: Upstream patch to fix exclusion of /. with
  --relative.
~ fix_remote_filter_rules_validation.patch: Upstream patch to fix bug
  with validating remote filter rules.
  (closes: #1018296, #1019561)

   -- Samuel Henrique   Wed, 21 Sep 2022 18:58:57
  +0100

  rsync (3.2.6-3) experimental; urgency=medium

* d/patches:
  - fix_files_from.patch: Upstream patch to address the files-from issue,
likely to also be related to #1019561 and #1018296
  - fix_relative.patch: Upstream patch to fix exclusion of /. with 
--relative

   -- Samuel Henrique   Wed, 14 Sep 2022 19:25:19
  +0100

  rsync (3.2.6-2) experimental; urgency=medium

* d/p/fix_remote_filter_rules_validation.patch: New upstream patch to try to
  fix #1019561 and #1018296

   -- Samuel Henrique   Tue, 13 Sep 2022 20:55:01
  +0100

  rsync (3.2.6-1) unstable; urgency=medium

* New upstream version 3.2.6
  - Added a safety check that prevents the sender from removing destination
files when a local copy using --remove-source-files has some files that
are shared between the sending & receiving hierarchies, including the
case where the source dir & destination dir are identical
(closes: #1016102)
* Bump Standards-Version to 4.6.1

   -- Samuel Henrique   Sat, 10 Sep 2022 20:03:51
  +0100

  rsync (3.2.5-1) unstable; urgency=medium

* New upstream version 3.2.5
  - Added some file-list safety checking that helps to ensure that a rogue
sending rsync can't add unrequested top-level names and/or include
recursive names that should have been excluded by the sender. These
extra safety checks only require the receiver rsync to be updated. When
dealing with an untrusted sending host, it is safest to copy into a
dedicated destination directory for the remote content (i.e. don't copy
into a destination directory that contains files that aren't from the
remote host unless you trust the remote host)
(closes: #1016543, CVE-2022-29154).
  - The build date that goes into the manpages is now based on the
developer's release date, not on the build's local-timezone
interpretation of the date (closes: #1009981)

   -- Samuel Henrique   Tue, 16 Aug 2022 11:03:48
  +0100

  rsync (3.2.4-1) unstable; urgency=medium

[ Samuel Henrique ]
* New upstream version 3.2.4
  - Work around a glibc bug where lchmod() breaks in a chroot w/o /proc
mounted (closes: #995046).
  - rsync.1: remove prepended backticks which broke --stop-after and
--stop-at formatting (closes: #1007990).


  ### Old Ubuntu Delta ###

  rsync (3.2.7-1ubuntu1) noble; urgency=medium

  

[Touch-packages] [Bug 2060967] Re: noble/rsync buffer overflow detected

[Mitchell Dzurick]

Package is in proposed now. Testing in an LXC container shows a fix of
this behavior.

$ lxc launch ubuntu-daily:noble n

$ lxc shell n

# dpkg -s rsync | grep Version:
Version: 3.2.7-1build2

# rsync -F --delete-after --archive /etc/os-release /tmp/
*** buffer overflow detected ***: terminated
rsync: connection unexpectedly closed (11 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(231) 
[sender=3.2.7]

# cat 

[Touch-packages] [Bug 2060967] Re: noble/rsync buffer overflow detected

[Mitchell Dzurick]

The debian patch looks promising in my local testing. I uploaded a test
package to run dep8 tests against. If those look green I'll submit my MP
and get it in ASAP.

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

Title:
  noble/rsync buffer overflow detected

Status in rsync package in Ubuntu:
  In Progress
Status in rsync source package in Focal:
  Invalid
Status in rsync source package in Jammy:
  Invalid
Status in rsync source package in Mantic:
  Invalid

Bug description:
  Hi,

  running the following test case in a current (today/2024-04-11) Noble
  install leads to a "buffer overflow detected":

  $ rsync -F --delete-after --archive /etc/fstab 127.0.0.1:/tmp/
  *** buffer overflow detected ***: terminated
  rsync: connection unexpectedly closed (11 bytes received so far) [sender]
  rsync error: error in rsync protocol data stream (code 12) at io.c(231) 
[sender=3.2.7]

  Original use case for the above striped down rsync options is the
  ansible module "synchronize".

  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Apr 11 14:38:46 2024
  Dependencies:
   gcc-14-base 14-20240330-1ubuntu2
   init-system-helpers 1.66ubuntu1
   libacl1 2.3.2-1
   libc6 2.39-0ubuntu8
   libgcc-s1 14-20240330-1ubuntu2
   libidn2-0 2.3.7-2
   liblz4-1 1.9.4-1
   libpopt0 1.19+dfsg-1
   libunistring5 1.1-2
   libxxhash0 0.8.2-2
   libzstd1 1.5.5+dfsg2-2
   lsb-base 11.6
   sysvinit-utils 3.08-6ubuntu2
   zlib1g 1:1.3.dfsg-3.1ubuntu2
  DistroRelease: Ubuntu 24.04
  Package: rsync 3.2.7-1build2
  PackageArchitecture: amd64
  ProcCpuinfoMinimal:
   processor: 0
   vendor_id: GenuineIntel
   cpu family   : 6
   model: 60
   model name   : Intel Core Processor (Haswell, no TSX, IBRS)
   stepping : 1
   microcode: 0x1
   cpu MHz  : 2397.222
   cache size   : 16384 KB
   physical id  : 0
   siblings : 1
   core id  : 0
   cpu cores: 1
   apicid   : 0
   initial apicid   : 0
   fpu  : yes
   fpu_exception: yes
   cpuid level  : 13
   wp   : yes
   flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc 
rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
hypervisor lahf_lm abm cpuid_fault pti ssbd ibrs ibpb fsgsbase bmi1 avx2 smep 
bmi2 erms invpcid xsaveopt arat md_clear
   bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_unknown
   bogomips : 4794.44
   clflush size : 64
   cache_alignment  : 64
   address sizes: 40 bits physical, 48 bits virtual
   power management:
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  SourcePackage: rsync
  Tags: noble
  Uname: Linux 6.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2060967/+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 2060967] Re: noble/rsync buffer overflow detected

[Mitchell Dzurick]

** Changed in: rsync (Ubuntu)
 Assignee: (unassigned) => Mitchell Dzurick (mitchdz)

** Changed in: rsync (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  noble/rsync buffer overflow detected

Status in rsync package in Ubuntu:
  In Progress
Status in rsync source package in Focal:
  Invalid
Status in rsync source package in Jammy:
  Invalid
Status in rsync source package in Mantic:
  Invalid

Bug description:
  Hi,

  running the following test case in a current (today/2024-04-11) Noble
  install leads to a "buffer overflow detected":

  $ rsync -F --delete-after --archive /etc/fstab 127.0.0.1:/tmp/
  *** buffer overflow detected ***: terminated
  rsync: connection unexpectedly closed (11 bytes received so far) [sender]
  rsync error: error in rsync protocol data stream (code 12) at io.c(231) 
[sender=3.2.7]

  Original use case for the above striped down rsync options is the
  ansible module "synchronize".

  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Apr 11 14:38:46 2024
  Dependencies:
   gcc-14-base 14-20240330-1ubuntu2
   init-system-helpers 1.66ubuntu1
   libacl1 2.3.2-1
   libc6 2.39-0ubuntu8
   libgcc-s1 14-20240330-1ubuntu2
   libidn2-0 2.3.7-2
   liblz4-1 1.9.4-1
   libpopt0 1.19+dfsg-1
   libunistring5 1.1-2
   libxxhash0 0.8.2-2
   libzstd1 1.5.5+dfsg2-2
   lsb-base 11.6
   sysvinit-utils 3.08-6ubuntu2
   zlib1g 1:1.3.dfsg-3.1ubuntu2
  DistroRelease: Ubuntu 24.04
  Package: rsync 3.2.7-1build2
  PackageArchitecture: amd64
  ProcCpuinfoMinimal:
   processor: 0
   vendor_id: GenuineIntel
   cpu family   : 6
   model: 60
   model name   : Intel Core Processor (Haswell, no TSX, IBRS)
   stepping : 1
   microcode: 0x1
   cpu MHz  : 2397.222
   cache size   : 16384 KB
   physical id  : 0
   siblings : 1
   core id  : 0
   cpu cores: 1
   apicid   : 0
   initial apicid   : 0
   fpu  : yes
   fpu_exception: yes
   cpuid level  : 13
   wp   : yes
   flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc 
rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
hypervisor lahf_lm abm cpuid_fault pti ssbd ibrs ibpb fsgsbase bmi1 avx2 smep 
bmi2 erms invpcid xsaveopt arat md_clear
   bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_unknown
   bogomips : 4794.44
   clflush size : 64
   cache_alignment  : 64
   address sizes: 40 bits physical, 48 bits virtual
   power management:
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  SourcePackage: rsync
  Tags: noble
  Uname: Linux 6.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2060967/+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 2060967] Re: noble/rsync buffer overflow detected

[Mitchell Dzurick]

This looks like it could already be fixed in debian with
https://salsa.debian.org/debian/rsync/-/commit/d3a0eccf989175b096c10b6c42b02b1ee1306a00

I'll try an ubuntu build with this patch and report back.

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

Title:
  noble/rsync buffer overflow detected

Status in rsync package in Ubuntu:
  Triaged
Status in rsync source package in Focal:
  Invalid
Status in rsync source package in Jammy:
  Invalid
Status in rsync source package in Mantic:
  Invalid

Bug description:
  Hi,

  running the following test case in a current (today/2024-04-11) Noble
  install leads to a "buffer overflow detected":

  $ rsync -F --delete-after --archive /etc/fstab 127.0.0.1:/tmp/
  *** buffer overflow detected ***: terminated
  rsync: connection unexpectedly closed (11 bytes received so far) [sender]
  rsync error: error in rsync protocol data stream (code 12) at io.c(231) 
[sender=3.2.7]

  Original use case for the above striped down rsync options is the
  ansible module "synchronize".

  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Apr 11 14:38:46 2024
  Dependencies:
   gcc-14-base 14-20240330-1ubuntu2
   init-system-helpers 1.66ubuntu1
   libacl1 2.3.2-1
   libc6 2.39-0ubuntu8
   libgcc-s1 14-20240330-1ubuntu2
   libidn2-0 2.3.7-2
   liblz4-1 1.9.4-1
   libpopt0 1.19+dfsg-1
   libunistring5 1.1-2
   libxxhash0 0.8.2-2
   libzstd1 1.5.5+dfsg2-2
   lsb-base 11.6
   sysvinit-utils 3.08-6ubuntu2
   zlib1g 1:1.3.dfsg-3.1ubuntu2
  DistroRelease: Ubuntu 24.04
  Package: rsync 3.2.7-1build2
  PackageArchitecture: amd64
  ProcCpuinfoMinimal:
   processor: 0
   vendor_id: GenuineIntel
   cpu family   : 6
   model: 60
   model name   : Intel Core Processor (Haswell, no TSX, IBRS)
   stepping : 1
   microcode: 0x1
   cpu MHz  : 2397.222
   cache size   : 16384 KB
   physical id  : 0
   siblings : 1
   core id  : 0
   cpu cores: 1
   apicid   : 0
   initial apicid   : 0
   fpu  : yes
   fpu_exception: yes
   cpuid level  : 13
   wp   : yes
   flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc 
rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
hypervisor lahf_lm abm cpuid_fault pti ssbd ibrs ibpb fsgsbase bmi1 avx2 smep 
bmi2 erms invpcid xsaveopt arat md_clear
   bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_unknown
   bogomips : 4794.44
   clflush size : 64
   cache_alignment  : 64
   address sizes: 40 bits physical, 48 bits virtual
   power management:
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  SourcePackage: rsync
  Tags: noble
  Uname: Linux 6.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2060967/+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 2060967] Re: noble/rsync buffer overflow detected

[Mitchell Dzurick]

** Also affects: rsync (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: rsync (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: rsync (Ubuntu Mantic)
   Importance: Undecided
   Status: New

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

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

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

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

Title:
  noble/rsync buffer overflow detected

Status in rsync package in Ubuntu:
  Triaged
Status in rsync source package in Focal:
  Invalid
Status in rsync source package in Jammy:
  Invalid
Status in rsync source package in Mantic:
  Invalid

Bug description:
  Hi,

  running the following test case in a current (today/2024-04-11) Noble
  install leads to a "buffer overflow detected":

  $ rsync -F --delete-after --archive /etc/fstab 127.0.0.1:/tmp/
  *** buffer overflow detected ***: terminated
  rsync: connection unexpectedly closed (11 bytes received so far) [sender]
  rsync error: error in rsync protocol data stream (code 12) at io.c(231) 
[sender=3.2.7]

  Original use case for the above striped down rsync options is the
  ansible module "synchronize".

  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Apr 11 14:38:46 2024
  Dependencies:
   gcc-14-base 14-20240330-1ubuntu2
   init-system-helpers 1.66ubuntu1
   libacl1 2.3.2-1
   libc6 2.39-0ubuntu8
   libgcc-s1 14-20240330-1ubuntu2
   libidn2-0 2.3.7-2
   liblz4-1 1.9.4-1
   libpopt0 1.19+dfsg-1
   libunistring5 1.1-2
   libxxhash0 0.8.2-2
   libzstd1 1.5.5+dfsg2-2
   lsb-base 11.6
   sysvinit-utils 3.08-6ubuntu2
   zlib1g 1:1.3.dfsg-3.1ubuntu2
  DistroRelease: Ubuntu 24.04
  Package: rsync 3.2.7-1build2
  PackageArchitecture: amd64
  ProcCpuinfoMinimal:
   processor: 0
   vendor_id: GenuineIntel
   cpu family   : 6
   model: 60
   model name   : Intel Core Processor (Haswell, no TSX, IBRS)
   stepping : 1
   microcode: 0x1
   cpu MHz  : 2397.222
   cache size   : 16384 KB
   physical id  : 0
   siblings : 1
   core id  : 0
   cpu cores: 1
   apicid   : 0
   initial apicid   : 0
   fpu  : yes
   fpu_exception: yes
   cpuid level  : 13
   wp   : yes
   flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc 
rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
hypervisor lahf_lm abm cpuid_fault pti ssbd ibrs ibpb fsgsbase bmi1 avx2 smep 
bmi2 erms invpcid xsaveopt arat md_clear
   bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_unknown
   bogomips : 4794.44
   clflush size : 64
   cache_alignment  : 64
   address sizes: 40 bits physical, 48 bits virtual
   power management:
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  SourcePackage: rsync
  Tags: noble
  Uname: Linux 6.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2060967/+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 2060967] Re: noble/rsync buffer overflow detected

[Mitchell Dzurick]

I was able to reproduce this in a noble LXD container.

$ lxc launch ubuntu-daily:noble n
$ lxc shell n
# ssh-keygen -t rsa
# cat ~/.ssh/id_rsa.pub >> ~/.ssh/authorized_keys
# touch testfile.txt
# rsync -F --delete-after --archive /root/testfile.txt 127.0.0.1:/tmp/
The authenticity of host '127.0.0.1 (127.0.0.1)' can't be established.
ED25519 key fingerprint is SHA256:1w9TL8K1uwpKXpyd9rFuNQPQNJ5EolG3NGNbdkUl9VE.
This key is not known by any other names.
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added '127.0.0.1' (ED25519) to the list of known hosts.
*** buffer overflow detected ***: terminated



rsync: connection unexpectedly closed (34 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(231) 
[sender=3.2.7]

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

Title:
  noble/rsync buffer overflow detected

Status in rsync package in Ubuntu:
  Triaged
Status in rsync source package in Focal:
  New
Status in rsync source package in Jammy:
  New
Status in rsync source package in Mantic:
  New

Bug description:
  Hi,

  running the following test case in a current (today/2024-04-11) Noble
  install leads to a "buffer overflow detected":

  $ rsync -F --delete-after --archive /etc/fstab 127.0.0.1:/tmp/
  *** buffer overflow detected ***: terminated
  rsync: connection unexpectedly closed (11 bytes received so far) [sender]
  rsync error: error in rsync protocol data stream (code 12) at io.c(231) 
[sender=3.2.7]

  Original use case for the above striped down rsync options is the
  ansible module "synchronize".

  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Apr 11 14:38:46 2024
  Dependencies:
   gcc-14-base 14-20240330-1ubuntu2
   init-system-helpers 1.66ubuntu1
   libacl1 2.3.2-1
   libc6 2.39-0ubuntu8
   libgcc-s1 14-20240330-1ubuntu2
   libidn2-0 2.3.7-2
   liblz4-1 1.9.4-1
   libpopt0 1.19+dfsg-1
   libunistring5 1.1-2
   libxxhash0 0.8.2-2
   libzstd1 1.5.5+dfsg2-2
   lsb-base 11.6
   sysvinit-utils 3.08-6ubuntu2
   zlib1g 1:1.3.dfsg-3.1ubuntu2
  DistroRelease: Ubuntu 24.04
  Package: rsync 3.2.7-1build2
  PackageArchitecture: amd64
  ProcCpuinfoMinimal:
   processor: 0
   vendor_id: GenuineIntel
   cpu family   : 6
   model: 60
   model name   : Intel Core Processor (Haswell, no TSX, IBRS)
   stepping : 1
   microcode: 0x1
   cpu MHz  : 2397.222
   cache size   : 16384 KB
   physical id  : 0
   siblings : 1
   core id  : 0
   cpu cores: 1
   apicid   : 0
   initial apicid   : 0
   fpu  : yes
   fpu_exception: yes
   cpuid level  : 13
   wp   : yes
   flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc 
rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
hypervisor lahf_lm abm cpuid_fault pti ssbd ibrs ibpb fsgsbase bmi1 avx2 smep 
bmi2 erms invpcid xsaveopt arat md_clear
   bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_unknown
   bogomips : 4794.44
   clflush size : 64
   cache_alignment  : 64
   address sizes: 40 bits physical, 48 bits virtual
   power management:
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  SourcePackage: rsync
  Tags: noble
  Uname: Linux 6.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2060967/+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 2060967] Re: noble/rsync buffer overflow detected

[Mitchell Dzurick]

Quickly testing Jammy/Mantic in a similar fashion as above I do not see
the buffer overflow.

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

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

Title:
  noble/rsync buffer overflow detected

Status in rsync package in Ubuntu:
  Triaged
Status in rsync source package in Focal:
  New
Status in rsync source package in Jammy:
  New
Status in rsync source package in Mantic:
  New

Bug description:
  Hi,

  running the following test case in a current (today/2024-04-11) Noble
  install leads to a "buffer overflow detected":

  $ rsync -F --delete-after --archive /etc/fstab 127.0.0.1:/tmp/
  *** buffer overflow detected ***: terminated
  rsync: connection unexpectedly closed (11 bytes received so far) [sender]
  rsync error: error in rsync protocol data stream (code 12) at io.c(231) 
[sender=3.2.7]

  Original use case for the above striped down rsync options is the
  ansible module "synchronize".

  ProblemType: Bug
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Apr 11 14:38:46 2024
  Dependencies:
   gcc-14-base 14-20240330-1ubuntu2
   init-system-helpers 1.66ubuntu1
   libacl1 2.3.2-1
   libc6 2.39-0ubuntu8
   libgcc-s1 14-20240330-1ubuntu2
   libidn2-0 2.3.7-2
   liblz4-1 1.9.4-1
   libpopt0 1.19+dfsg-1
   libunistring5 1.1-2
   libxxhash0 0.8.2-2
   libzstd1 1.5.5+dfsg2-2
   lsb-base 11.6
   sysvinit-utils 3.08-6ubuntu2
   zlib1g 1:1.3.dfsg-3.1ubuntu2
  DistroRelease: Ubuntu 24.04
  Package: rsync 3.2.7-1build2
  PackageArchitecture: amd64
  ProcCpuinfoMinimal:
   processor: 0
   vendor_id: GenuineIntel
   cpu family   : 6
   model: 60
   model name   : Intel Core Processor (Haswell, no TSX, IBRS)
   stepping : 1
   microcode: 0x1
   cpu MHz  : 2397.222
   cache size   : 16384 KB
   physical id  : 0
   siblings : 1
   core id  : 0
   cpu cores: 1
   apicid   : 0
   initial apicid   : 0
   fpu  : yes
   fpu_exception: yes
   cpuid level  : 13
   wp   : yes
   flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc 
rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
hypervisor lahf_lm abm cpuid_fault pti ssbd ibrs ibpb fsgsbase bmi1 avx2 smep 
bmi2 erms invpcid xsaveopt arat md_clear
   bugs : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_unknown
   bogomips : 4794.44
   clflush size : 64
   cache_alignment  : 64
   address sizes: 40 bits physical, 48 bits virtual
   power management:
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  SourcePackage: rsync
  Tags: noble
  Uname: Linux 6.8.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2060967/+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 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect

[Mitchell Dzurick]

Just want to update this bug - I have not found a fix for this. Instead
I've been relying on the Logitech universal receiver which is working
great in my experience.

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  New

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2055776] Re: After updating ubuntu, the network to which the subnet address is assigned does not become active in KVM.

[Mitchell Dzurick]

Thanks Tim! With more people having a seemingly similar issue I re-
opened it as New and subscribed ubuntu-server to take a look at this
again.

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

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

Title:
  After updating ubuntu, the network to which the subnet address is
  assigned does not become active in KVM.

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  phenomenon:
After updating ubuntu, the network to which the subnet address is assigned 
does not become active in KVM.

  Cause:
This is because the following dnsmasq update operation performed by apt's 
automatic update causes an error. It worked properly with dnsmasq 2.80, but 
does not work properly with 2.90.

  $ cat /var/log/apt/history.log
  (snip)
  Start-Date: 2024-02-27  06:17:31
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: dnsmasq-base:amd64 (2.80-1.1ubuntu1.7, 2.90-0ubuntu0.20.04.1)
  End-Date: 2024-02-27  06:17:44
  (snip)
  $

  Cause details:
As a premise, bind-dynamic is set in the dnsmasq config file for KVM. Below 
is an example.

  $ cat default.conf 
  ##WARNING:  THIS IS AN AUTO-GENERATED FILE. CHANGES TO IT ARE LIKELY TO BE
  ##OVERWRITTEN AND LOST.  Changes to this configuration should be made using:
  ##virsh net-edit default
  ## or other application using the libvirt API.
  ##
  ## dnsmasq conf file created by libvirt
  strict-order
  user=libvirt-dnsmasq
  pid-file=/run/libvirt/network/default.pid
  except-interface=lo
  bind-dynamic
  interface=virbr0
  dhcp-range=192.168.122.2,192.168.122.254,255.255.255.0
  dhcp-no-override
  dhcp-authoritative
  dhcp-lease-max=253
  dhcp-hostsfile=/var/lib/libvirt/dnsmasq/default.hostsfile
  addn-hosts=/var/lib/libvirt/dnsmasq/default.addnhosts
  $ 

  
  When starting the network with KVM (virsh net-start), dnsmasq started from 
KVM executes the make_sock function twice as shown below.

 $ cat network.c
 (snip)
 1087 static struct listener *create_listeners(union mysockaddr *addr, int 
do_
 1087 tftp, int dienow)
 1088 {
 1089   struct listener *l = NULL;
 1090   int fd = -1, tcpfd = -1, tftpfd = -1;
 1091 
 1092   (void)do_tftp;
 1093 
 1094   if (daemon->port != 0)
 1095 {
 1096   fd = make_sock(addr, SOCK_DGRAM, dienow);
 1097   tcpfd = make_sock(addr, SOCK_STREAM, dienow);
 1098 }
 (snip)

  The following code causes an issue with the update made in dnsmasq
  2.90.

 $ cat network.c
 (snip)
  895 static int make_sock(union mysockaddr *addr, int type, int dienow)
  896 {
  (snip)
  934   if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
  935 {
  936   if (dienow)
  937 die(s, daemon->addrbuff, EC_BADNET);
  938   else
  939 my_syslog(LOG_WARNING, s, daemon->addrbuff, 
strerror(errno))939 ;
  940 }
  (snip)

  
  function "make_sock" in network.c:1096 binds the socket to 192.168.122.1/24, 
and then make_sock in network.c:1097 tries to bind to the same address. 
However, in network.c:934, when errno==98 occurs, network.c:937 is executed, so 
dnsmasq does not cause a startup error. As a result, virsh net-start fails.

  As a temporary workaround, it will work if you try not to die.

  $ diff -u  network_c_back  network.c 
  --- network_c_back  2024-02-29 15:36:05.156467935 +
  +++ network.c 2024-02-29 15:36:38.733324350 +
  @@ -934,7 +934,8 @@
 if (!option_bool(OPT_CLEVERBIND) || errno != EADDRNOTAVAIL)
{
  if (dienow)
  - die(s, daemon->addrbuff, EC_BADNET);
  + my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
  + //die(s, daemon->addrbuff, EC_BADNET);
  else
my_syslog(LOG_WARNING, s, daemon->addrbuff, strerror(errno));
}
  $ 

  If bind-dynamic is set, it should be modified so that it works even if
  errno==98.

  For reference, in the case of dnsmasq 2.80, the code is as follows, so
  no error occurs.

  network.c
  699 static int make_sock(union mysockaddr *addr, int type, int dienow)
  700 {
  701   int family = addr->sa.sa_family;
  702   int fd, rc, opt = 1;
  (snip)
  715 err:
  716   errsave = errno;
  717   port = prettyprint_addr(addr, daemon->addrbuff);
  718   if (!option_bool(OPT_NOWILD) && !option_bool(OPT_CLEVERBIND))
  719 sprintf(daemon->addrbuff, "port %d", port);
  720   s = _("failed to create listening socket for %s: %s");
  721   
  722   if (fd != -1)
  723 close (fd);
  724 
  725   errno = errsave;
  726 
  727   if (dienow)
  728 {
  729   /* failure to bind addresses given by --listen-address at 
this
  

[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

Ran the autopkgtest on a new PPA with my changes enabled by default and
the test still fails[0]. I believe this is fine enough to ignore simply
because this test has always been failing like this.

[0] - https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-mitchdz-
python2.7-opt-test-enabled-
default/jammy/amd64/p/python2.7/20240313_174406_9bb00@/log.gz

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  Fix Committed
Status in python2.7 source package in Jammy:
  Fix Committed
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  When compiling Python extensions using Python2, CFLAGS optimization
  flags are dropped.

  This behavior has been caused by our update in this patch
  
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
  which differs from upstream.

  The fix modifies the portion of code in Lib/distutils/sysconfig.py
  which gets the cflags from the environments, and includes the dropped
  OPT flag from get_config_vars().

  [ Test Plan ]

  There will be 2 separate tests for this bug:
  * Ensuring no-change rebuilds are not changed
  * Ensuring local builds are not changed unless environment variable is set

  Test 1) No-change rebuilds

  To test that no-change rebuilds are not changed, the package python-
  stdlib-extensions will be built against the new python2.7, and confirm
  the compiler flags are not altered. This will be a manual test and
  visual inspection of the build logs.

  Test 2) Functional test

  1. Create test container
  $ lxc launch ubuntu:jammy jammy-2002043
  $ lxc shell jammy-2002043

  2. Install required packages
  For Jammy
  # apt update -y && apt install -y python2 python-pip
  For Focal
  # apt update -y && apt install -y python2 python-setuptools gcc

  3. Create test files
  # mkdir testprog
  # cd testprog
  # cat >setup.py 

[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

The only focal autopkgtest that really has me confused in the python2.7
failure. This is due to a unit test that fails. The strange thing is
that this unit test actually fails in the Jammy autopkgtest, but the
Jammy autopkgtest passes anyways. It has always been like this.

You will see

1643s FAIL: test_customize_compiler 
(distutils.tests.test_sysconfig.SysconfigTestCase)
1643s --
1643s Traceback (most recent call last):
1643s   File "/usr/lib/python2.7/distutils/tests/test_sysconfig.py", line 110, 
in test_customize_compiler
1643s 'env_cc --sc-cflags --env-cflags --env-cppflags')
1643s AssertionError: 'env_cc -fno-strict-aliasing --env-cflags --env-cppflags' 
!= 'env_cc --sc-cflags --env-cflags --env-cppflags'


Which has always been like this - my patch did not cause this change.

I think this should be safe to ignore simply because the package has
always been like this, and if it is an issue we should've found a bug
for it by now.

I tried to see if the Debian autopkgtest also sees this behavior, but
unfortunately those logs have been removed due to the retention policy.

I'm curious if the change I am doing will fix this unit test... So I
created a PPA with the change enabled by default and will come back when
the results are ready.

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  Fix Committed
Status in python2.7 source package in Jammy:
  Fix Committed
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  When compiling Python extensions using Python2, CFLAGS optimization
  flags are dropped.

  This behavior has been caused by our update in this patch
  
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
  which differs from upstream.

  The fix modifies the portion of code in Lib/distutils/sysconfig.py
  which gets the cflags from the environments, and includes the dropped
  OPT flag from get_config_vars().

  [ Test Plan ]

  There will be 2 separate tests for this bug:
  * Ensuring no-change rebuilds are not changed
  * Ensuring local builds are not changed unless environment variable is set

  Test 1) No-change rebuilds

  To test that no-change rebuilds are not changed, the package python-
  stdlib-extensions will be built against the new python2.7, and confirm
  the compiler flags are not altered. This will be a manual test and
  visual inspection of the build logs.

  Test 2) Functional test

  1. Create test container
  $ lxc launch ubuntu:jammy jammy-2002043
  $ lxc shell jammy-2002043

  2. Install required packages
  For Jammy
  # apt update -y && apt install -y python2 python-pip
  For Focal
  # apt update -y && apt install -y python2 python-setuptools gcc

  3. Create test files
  # mkdir testprog
  # cd testprog
  # cat >setup.py 

[Touch-packages] [Bug 2026757] Re: dnsmasq on Ubuntu Jammy crashes on neutron-dhcp-agent updates

[Mitchell Dzurick]

I wonder if the latest update to Jammy has fixed the issue? Is this
issue still occurring for you when upgrading to the Jammy package
version 2.90-0ubuntu0.22.04.1 Julia?

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

Title:
  dnsmasq on Ubuntu Jammy crashes on neutron-dhcp-agent updates

Status in Ironic:
  Triaged
Status in neutron:
  New
Status in dnsmasq package in Ubuntu:
  Invalid
Status in dnsmasq source package in Jammy:
  Incomplete
Status in dnsmasq source package in Kinetic:
  Won't Fix
Status in dnsmasq source package in Lunar:
  Invalid
Status in dnsmasq source package in Mantic:
  Invalid

Bug description:
  The Ironic project's CI has been having major blocking issues moving
  to utilizing Ubuntu Jammy and with some investigation we were able to
  isolate the issues down to the dhcp updates causing dnsmasq to crash
  on Ubuntu Jammy, which ships with dnsmasq 2.86. This issue sounds
  similar to an issue known about to the dnsmasq maintainers, where
  dnsmasq would crash with updates occurring due to configuration
  refresh[0].

  This resulted in us upgrading dnsmasq to the version which ships with
  Ubuntu Lunar.

  Which was no better. Dnsmasq still crashed upon record updates for
  addresses and ports getting configuration added/changed/removed.

  We later downgraded to the version of dnsmasq shipped in Ubuntu Focal,
  and dnsmasq stopped crashing and appeared stable enough to utilize for
  CI purposes.

  ** Kernel log from Ubuntu Jammy Package **

  [229798.876726] dnsmasq[81586]: segfault at 7c28 ip 7f6e8313147e sp 
7fffb3d6f830 error 4 in libc.so.6[7f6e830b4000+195000]
  [229798.876745] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [229805.444912] dnsmasq[401428]: segfault at dce8 ip 7fe63bf6a47e sp 
7ffdb105b440 error 4 in libc.so.6[7fe63beed000+195000]
  [229805.444933] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230414.213448] dnsmasq[401538]: segfault at 78b8 ip 7f12160e447e sp 
7ffed6ef2190 error 4 in libc.so.6[7f1216067000+195000]
  [230414.213467] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [230465.098989] dnsmasq[402665]: segfault at c378 ip 7f81458f047e sp 
7fff0db334a0 error 4 in libc.so.6[7f8145873000+195000]
  [230465.099005] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231787.247374] dnsmasq[402863]: segfault at 7318 ip 7f3940b9147e sp 
7ffc8df4f010 error 4 in libc.so.6[7f3940b14000+195000]
  [231787.247392] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [231844.886399] dnsmasq[405182]: segfault at dc58 ip 7f32a29e147e sp 
7ffddedd7480 error 4 in libc.so.6[7f32a2964000+195000]
  [231844.886420] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234692.482154] dnsmasq[405289]: segfault at 67d8 ip 7fab0c5c447e sp 
7fffd6fd8fa0 error 4 in libc.so.6[7fab0c547000+195000]
  [234692.482173] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a

  ** Kernel log entries from Ubuntu Lunar package **

  [234724.842339] dnsmasq[409843]: segfault at fffd ip 
7f35a147647e sp 7ffd536038c0 error 5 in libc.so.6[7f35a13f9000+195000]
  [234724.842368] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [234784.918116] dnsmasq[410019]: segfault at fffd ip 
7f634233947e sp 7fff33877f20 error 5 in libc.so.6[7f63422bc000+195000]
  [234784.918133] Code: 98 13 00 e8 04 b9 ff ff 0f 1f 40 00 f3 0f 1e fa 48 85 
ff 0f 84 bb 00 00 00 55 48 8d 77 f0 53 48 83 ec 18 48 8b 1d 92 39 17 00 <48> 8b 
47 f8 64 8b 2b a8 02 75 57 48 8b 15 18 39 17 00 64 48 83 3a
  [235022.163339] dnsmasq[410151]: segfault at fffd ip 
7f21dd37f47e sp 

[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

i took a look at the other focal packages and put my thoughts.

RELEASE=focal
TRIGGER=python2.7/2.7.18-1~20.04.4


release  arch packageversion   exitcode 
 triggersrequester
---  ---  -     
 --  -

focali386 dbus-python1.2.16-1build114   
 python2.7/2.7.18-1~20.04.4
Has always been giving the exit code 14 ever since glibc/2.31-0ubuntu6   back 
in 2020
In hints as force-badtest 
https://git.launchpad.net/~ubuntu-release/britney/+git/hints-ubuntu/tree/ubuntu-release?h=focal#n230

focali386 libxml22.9.10+dfsg-5ubuntu0.20.04.6  12   
 python2.7/2.7.18-1~20.04.4
Has been failing since glibc/2.30-0ubuntu3 in 2019
In hints as force-badtest 
https://git.launchpad.net/~ubuntu-release/britney/+git/hints-ubuntu/tree/ubuntu-release?h=focal#n236

focalarm64llvm-toolchain-7   1:7.0.1-124
 python2.7/2.7.18-1~20.04.4
focalarmhfllvm-toolchain-7   1:7.0.1-124
 python2.7/2.7.18-1~20.04.4
focalppc64el  llvm-toolchain-7   1:7.0.1-124
 python2.7/2.7.18-1~20.04.4
This package has just never passed on any of these architectures. I'm not sure 
why it's not passing.


focalamd64mercurial  5.3.1-1ubuntu14
 python2.7/2.7.18-1~20.04.4
focalarm64mercurial  5.3.1-1ubuntu14
 python2.7/2.7.18-1~20.04.4
focalarmhfmercurial  5.3.1-1ubuntu14
 python2.7/2.7.18-1~20.04.4
focali386 mercurial  5.3.1-1ubuntu112   
 python2.7/2.7.18-1~20.04.4
focalppc64el  mercurial  5.3.1-1ubuntu14
 python2.7/2.7.18-1~20.04.4
focals390xmercurial  5.3.1-1ubuntu14
 python2.7/2.7.18-1~20.04.4
Mentioned by Andreas already


focalamd64pam-python 1.0.7-1ubuntu14
 python2.7/2.7.18-1~20.04.4
focalarm64pam-python 1.0.7-1ubuntu14
 python2.7/2.7.18-1~20.04.4
focalarmhfpam-python 1.0.7-1ubuntu14
 python2.7/2.7.18-1~20.04.4
focalppc64el  pam-python 1.0.7-1ubuntu14
 python2.7/2.7.18-1~20.04.4
focals390xpam-python 1.0.7-1ubuntu14
 python2.7/2.7.18-1~20.04.4
Mentioned by Andreas already


focali386 python-debian  0.1.36ubuntu1.1   12   
 python2.7/2.7.18-1~20.04.4
Fails due to unmet dependencies since glibc/2.30-0ubuntu3. I didn't notice 
anything in the hints.

focali386 python-pbr 5.4.5-0ubuntu112   
 python2.7/2.7.18-1~20.04.4
Fails due to unmet dependencies since glibc/2.30-0ubuntu3. I didn't notice 
anything in the hints.


focalamd64python2.7  2.7.18-1~20.04.4  4
 python2.7/2.7.18-1~20.04.4
focalarm64python2.7  2.7.18-1~20.04.4  4
 python2.7/2.7.18-1~20.04.4
focalarmhfpython2.7  2.7.18-1~20.04.4  4
 python2.7/2.7.18-1~20.04.4
focali386 python2.7  2.7.18-1~20.04.4  4
 python2.7/2.7.18-1~20.04.4
focalppc64el  python2.7  2.7.18-1~20.04.4  4
 python2.7/2.7.18-1~20.04.4
focals390xpython2.7  2.7.18-1~20.04.4  4
 python2.7/2.7.18-1~20.04.4
Mentioned in the comment above - seems to be the same tests are failing in the 
Jammy results, but jammy passes the overall test. I'm not sure currently about 
this and would like to dig into it a little bit.

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  Fix Committed
Status in python2.7 source package in Jammy:
  Fix Committed
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  When compiling Python extensions using Python2, CFLAGS optimization
  flags are dropped.

  This behavior has been caused by our update in this patch
  
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
  which differs from upstream.

  The fix modifies the portion of code in Lib/distutils/sysconfig.py
  

[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

Hi Andreas, the test_customize_compiler flag test has always failed. I'm
curious about why it's failing but the autopkgtest as a whole is
passing.

In fact, the same failures occur for both jammy/focal since forever -
yet they seem to be the reason w hy the Focal autopkgtest fails, whereas
Jammy happily passes the test even with these failures present.

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  Fix Committed
Status in python2.7 source package in Jammy:
  Fix Committed
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  When compiling Python extensions using Python2, CFLAGS optimization
  flags are dropped.

  This behavior has been caused by our update in this patch
  
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
  which differs from upstream.

  The fix modifies the portion of code in Lib/distutils/sysconfig.py
  which gets the cflags from the environments, and includes the dropped
  OPT flag from get_config_vars().

  [ Test Plan ]

  There will be 2 separate tests for this bug:
  * Ensuring no-change rebuilds are not changed
  * Ensuring local builds are not changed unless environment variable is set

  Test 1) No-change rebuilds

  To test that no-change rebuilds are not changed, the package python-
  stdlib-extensions will be built against the new python2.7, and confirm
  the compiler flags are not altered. This will be a manual test and
  visual inspection of the build logs.

  Test 2) Functional test

  1. Create test container
  $ lxc launch ubuntu:jammy jammy-2002043
  $ lxc shell jammy-2002043

  2. Install required packages
  For Jammy
  # apt update -y && apt install -y python2 python-pip
  For Focal
  # apt update -y && apt install -y python2 python-setuptools gcc

  3. Create test files
  # mkdir testprog
  # cd testprog
  # cat >setup.py 

[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

Thanks a ton Mauricio! Would we be good to start phasing the Jammy
package then while I investigate the Focal failures? I'll start taking a
look at Focal today.

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  Fix Committed
Status in python2.7 source package in Jammy:
  Fix Committed
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  When compiling Python extensions using Python2, CFLAGS optimization
  flags are dropped.

  This behavior has been caused by our update in this patch
  
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
  which differs from upstream.

  The fix modifies the portion of code in Lib/distutils/sysconfig.py
  which gets the cflags from the environments, and includes the dropped
  OPT flag from get_config_vars().

  [ Test Plan ]

  There will be 2 separate tests for this bug:
  * Ensuring no-change rebuilds are not changed
  * Ensuring local builds are not changed unless environment variable is set

  Test 1) No-change rebuilds

  To test that no-change rebuilds are not changed, the package python-
  stdlib-extensions will be built against the new python2.7, and confirm
  the compiler flags are not altered. This will be a manual test and
  visual inspection of the build logs.

  Test 2) Functional test

  1. Create test container
  $ lxc launch ubuntu:jammy jammy-2002043
  $ lxc shell jammy-2002043

  2. Install required packages
  For Jammy
  # apt update -y && apt install -y python2 python-pip
  For Focal
  # apt update -y && apt install -y python2 python-setuptools gcc

  3. Create test files
  # mkdir testprog
  # cd testprog
  # cat >setup.py 

[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

mfo: thanks for catching the ctrlc+ctrlv error! It sounds like we are
just waiting to re-run the autopkgtest then.

Let me know if you would like any additional testing from me!

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  Fix Committed
Status in python2.7 source package in Jammy:
  Fix Committed
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  When compiling Python extensions using Python2, CFLAGS optimization
  flags are dropped.

  This behavior has been caused by our update in this patch
  
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
  which differs from upstream.

  The fix modifies the portion of code in Lib/distutils/sysconfig.py
  which gets the cflags from the environments, and includes the dropped
  OPT flag from get_config_vars().

  [ Test Plan ]

  There will be 2 separate tests for this bug:
  * Ensuring no-change rebuilds are not changed
  * Ensuring local builds are not changed unless environment variable is set

  Test 1) No-change rebuilds

  To test that no-change rebuilds are not changed, the package python-
  stdlib-extensions will be built against the new python2.7, and confirm
  the compiler flags are not altered. This will be a manual test and
  visual inspection of the build logs.

  Test 2) Functional test

  1. Create test container
  $ lxc launch ubuntu:jammy jammy-2002043
  $ lxc shell jammy-2002043

  2. Install required packages
  For Jammy
  # apt update -y && apt install -y python2 python-pip
  For Focal
  # apt update -y && apt install -y python2 python-setuptools gcc

  3. Create test files
  # mkdir testprog
  # cd testprog
  # cat >setup.py 

[Touch-packages] [Bug 2055455] Re: dnsmasq-base causes network device virbr0 to shut down

[Mitchell Dzurick]

Thanks for taking the time to make this bug report to make Ubuntu
better!

I tried reproducing your failure and unfortunately am not able to in a
VM/container setup. I think this may need some extra configuration to
reproduce the failure.

Starting with something basic, would you mind sharing these 2 files?
Please remove/censor any information you do not want to share such as
MAC address.

/etc/libvirt/qemu/networks/default.xml
/etc/dnsmasq.d-available/libvirt-daemon

And any other configuration files that you think may be useful.

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

Title:
  dnsmasq-base causes network device virbr0 to shut down

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Installing dnsmasq-base v2.90-0ubuntu0.22.04.1 causes network device
  virbr0 to shut down during the boot-up process. Device virbr0 is
  installed by the libvirtd daemon. libvirtd gets an unexpected error
  when dnsmasq is called and then the address record for virbr0 is
  withdrawn.

  This problem goes away when reverting back to dnsmasq-base v2.86-1.1

  The attached text file provides relevant status reports which
  illustrate this problem. (status is shown for the system when using
  dnsmasq-base v2.90-0ubuntu0.22.04.1 when the problem occurs and then
  when the system operates correctly using dnsmasq-base v2.86-1.1)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dnsmasq-base 2.90-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 29 10:29:20 2024
  InstallationDate: Installed on 2018-10-08 (1970 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2055455/+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 2055455] Re: dnsmasq-base causes network device virbr0 to shut down

[Mitchell Dzurick]

I must've opened this bug up in the morning before Marc commented and
just got back around to posting the question. Apologies for asking for
the same information!

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

Title:
  dnsmasq-base causes network device virbr0 to shut down

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  Installing dnsmasq-base v2.90-0ubuntu0.22.04.1 causes network device
  virbr0 to shut down during the boot-up process. Device virbr0 is
  installed by the libvirtd daemon. libvirtd gets an unexpected error
  when dnsmasq is called and then the address record for virbr0 is
  withdrawn.

  This problem goes away when reverting back to dnsmasq-base v2.86-1.1

  The attached text file provides relevant status reports which
  illustrate this problem. (status is shown for the system when using
  dnsmasq-base v2.90-0ubuntu0.22.04.1 when the problem occurs and then
  when the system operates correctly using dnsmasq-base v2.86-1.1)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: dnsmasq-base 2.90-0ubuntu0.22.04.1
  ProcVersionSignature: Ubuntu 5.15.0-60.66-generic 5.15.78
  Uname: Linux 5.15.0-60-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 29 10:29:20 2024
  InstallationDate: Installed on 2018-10-08 (1970 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2055455/+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 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."

[Mitchell Dzurick]

Also, the various packages here have a similar error message but the
error is probably caused by different things. This is a generic error
message from init-system-helpers.

Now, with that said, I agree init-system-helpers should be more verbose
when this error happens.

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

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

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

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

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

  This will be installing krb5-kdc 1.19.2-2.

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

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

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

  dpkg-reconfigure krb5-kdc

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+subscriptions


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

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

[Mitchell Dzurick]

netvicious or Dan, do you have the AMI that you used to produce that
error with proftpd-core?

I also tried reproduction on ami-0dffe9017aa8424a2 in eu-north-1 and was
not able to reproduce that failure.

I just booted a fresh t3.micro instance with the above AMI, then
proceeded to run `apt update -y && apt install -y  proftpd`.

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

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

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

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

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

  This will be installing krb5-kdc 1.19.2-2.

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

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

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

  dpkg-reconfigure krb5-kdc

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+subscriptions


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

[Touch-packages] [Bug 2053146] Re: openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is slightly wrong

[Mitchell Dzurick]

Thanks for the additional info Ake!

Do you happen to have simple steps you could share to help reproduce the
issue?

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

Title:
  openssh 8.9p1 for Jammy auth2-gss patch for gssapi-keyex method is
  slightly wrong

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  The Authmethod struct now have 4 entries but the initialization of the
  method_gsskeyex in the debian/patches/gssapi.patch only have 3
  entries.

  The struct was changed in upstream commit 
dbb339f015c33d63484261d140c84ad875a9e548 as
  ===
  @@ -104,7 +104,8 @@ struct Authctxt {
   
   struct Authmethod {
  char*name;
  -   int (*userauth)(struct ssh *);
  +   char*synonym;
  +   int (*userauth)(struct ssh *, const char *);
  int *enabled;
   };

  ===

  The incorrect code does
  ===
  +Authmethod method_gsskeyex = {
  +   "gssapi-keyex",
  +   userauth_gsskeyex,
  +   _authentication
  +};
  ===
  but should have a NULL between the "gssapi-keyex" string and userauth_gsskeyex

  
  This is now (change from Focal) causing gssapi-keyex to be disabled.

  
  ===
  lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  ===
  apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.9p1-3ubuntu0.6
Candidate: 1:8.9p1-3ubuntu0.6
Version table:
   *** 1:8.9p1-3ubuntu0.6 500
  500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu 
jammy-updates/main amd64 Packages
  500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu 
jammy-security/main amd64 Packages
  100 /var/lib/dpkg/status
   1:8.9p1-3 500
  500 http://faiserver.hpc2n.umu.se/mirrors/ubuntu/ubuntu jammy/main 
amd64 Packages

  ===

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2053146/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

Attached is my manual verification steps of testing the proposed package
for Focal.

Package version tested: 2.7.18-1~20.04.4

Part of the verification process is to ensure no regressions happen in
no-change rebuilds of the current wheels compiled with python2.7 in our
archives. It was determined that the best way to do this was to make
this feature opt-in, so a test is performed to ensure that functionally
no changes happen for no-change rebuilds.

This was tested in this PPA -
https://launchpad.net/~mitchdz/+archive/ubuntu/python-stdlib-extensions-
py2-opt

Observe the build logs and see

The specific build log for Focal is
https://launchpadlibrarian.net/714574260/buildlog_ubuntu-focal-
amd64.python-stdlib-extensions_2.7.18-1ubuntu1~focal1_BUILDING.txt.gz

Where you will see the following lines showing the workaround is not
used:

cd 2.7 && python2.7 setup.py build
running build
running build_ext
There is a workaround to now inherit optimization CFLAGS when compiling wheels.
To enable this, set APPLY_LP2002043_UBUNTU_CFLAGS_WORKAROUND in your
environment. See LP: https://launchpad.net/bugs/2002043 for further context.
APPLY_LP2002043_UBUNTU_CFLAGS_WORKAROUND not detected.
building 'gdbm' extension
creating build
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/Modules
x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time 
-D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-CxOYiX/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC -I. 
-I/usr/include/python2.7 -c Modules/gdbmmodule.c -o 
build/temp.linux-x86_64-2.7/Modules/gdbmmodule.o
creating build/lib.linux-x86_64-2.7
x86_64-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-Bsymbolic-functions -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv 
-O2 -Wall -Wstrict-prototypes -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-CxOYiX/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security 
-Wl,-Bsymbolic-functions -Wl,-z,relro -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-CxOYiX/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
build/temp.linux-x86_64-2.7/Modules/gdbmmodule.o -lgdbm -o 
build/lib.linux-x86_64-2.7/gdbm.so
building '_tkinter' extension

Notice the lack of the OPT flags (-DNDEBUG -g -fwrapv -O2 -Wall
-Wstrict-prototypes) in the compile time flags for the module.


** Attachment added: "PYthon2.7_focal_opt_flags_verification.txt"
   
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+attachment/5746688/+files/PYthon2.7_focal_opt_flags_verification.txt

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

** Description changed:

  [ Impact ]
  
  When compiling Python extensions using Python2, CFLAGS optimization
  flags are dropped.
  
  This behavior has been caused by our update in this patch
  
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
  which differs from upstream.
  
  The fix modifies the portion of code in Lib/distutils/sysconfig.py which
  gets the cflags from the environments, and includes the dropped OPT flag
  from get_config_vars().
  
  [ Test Plan ]
  
  There will be 2 separate tests for this bug:
  * Ensuring no-change rebuilds are not changed
  * Ensuring local builds are not changed unless environment variable is set
  
  Test 1) No-change rebuilds
  
  To test that no-change rebuilds are not changed, the package python-
  stdlib-extensions will be built against the new python2.7, and confirm
  the compiler flags are not altered. This will be a manual test and
  visual inspection of the build logs.
  
  Test 2) Functional test
  
  1. Create test container
  $ lxc launch ubuntu:jammy jammy-2002043
- $ lxc shell ubuntu:jammy jammy-2002043
+ $ lxc shell jammy-2002043
  
  2. Install required packages
  For Jammy
  # apt update -y && apt install -y python2 python-pip
  For Focal
- # apt update -y && apt install -y python2 python-setuptools
+ # apt update -y && apt install -y python2 python-setuptools gcc
  
  3. Create test files
  # mkdir testprog
  # cd testprog
  # cat >setup.py 

[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

Attached is my manual verification steps of testing the proposed package
for Jammy.

Package version 2.7.18-13ubuntu1.2

Part of the verification process is to ensure no regressions happen in
no-change rebuilds of the current wheels compiled with python2.7 in our
archives. It was determined that the best way to do this was to make
this feature opt-in, so a test is performed to ensure that functionally
no changes happen for no-change rebuilds.

This was tested in this PPA -
https://launchpad.net/~mitchdz/+archive/ubuntu/python-stdlib-extensions-
py2-opt

Observe the build logs and see

The specific build log for Jammy is
https://launchpadlibrarian.net/714574054/buildlog_ubuntu-jammy-
amd64.python-stdlib-extensions_2.7.18-1ubuntu1~jammy1_BUILDING.txt.gz

Where you will see the following lines showing the workaround is not
used:

cd 2.7 && python2.7 setup.py build
running build
running build_ext
There is a workaround to now inherit optimization CFLAGS when compiling wheels.
To enable this, set APPLY_LP2002043_UBUNTU_CFLAGS_WORKAROUND in your
environment. See LP: https://launchpad.net/bugs/2002043 for further context.
APPLY_LP2002043_UBUNTU_CFLAGS_WORKAROUND not detected.
building 'gdbm' extension
creating build
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/Modules
x86_64-linux-gnu-gcc -fno-strict-aliasing -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-ffile-prefix-map=/build/python2.7-RH0SVf/python2.7-2.7.18=. -flto=auto 
-ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong 
-Wformat -Werror=format-security -fPIC -I. -I/usr/include/python2.7 -c 
Modules/gdbmmodule.c -o build/temp.linux-x86_64-2.7/Modules/gdbmmodule.o
creating build/lib.linux-x86_64-2.7
x86_64-linux-gnu-gcc -shared -Wl,-O1 -Wl,-Bsymbolic-functions 
-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z,relro 
-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-ffile-prefix-map=/build/python2.7-RH0SVf/python2.7-2.7.18=. -flto=auto 
-ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong 
-Wformat -Werror=format-security -Wl,-Bsymbolic-functions -flto=auto 
-ffat-lto-objects -flto=auto -Wl,-z,relro -Wdate-time -D_FORTIFY_SOURCE=2 -g 
-ffile-prefix-map=/build/python2.7-RH0SVf/python2.7-2.7.18=. -flto=auto 
-ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong 
-Wformat -Werror=format-security -fPIC 
build/temp.linux-x86_64-2.7/Modules/gdbmmodule.o -lgdbm -o 
build/lib.linux-x86_64-2.7/gdbm.so
building '_tkinter' extension


Notice the lack of the OPT flags (-DNDEBUG -g -fwrapv -O2 -Wall 
-Wstrict-prototypes) in the compiletime flags.

** Attachment added: "Python2.7_jammy_opt_flags_verification.txt"
   
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+attachment/5746685/+files/Python2.7_jammy_opt_flags_verification.txt

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

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  Fix Committed
Status in python2.7 source package in Jammy:
  Fix Committed
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  When compiling Python extensions using Python2, CFLAGS optimization
  flags are dropped.

  This behavior has been caused by our update in this patch
  
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
  which differs from upstream.

  The fix modifies the portion of code in Lib/distutils/sysconfig.py
  which gets the cflags from the environments, and includes the dropped
  OPT flag from get_config_vars().

  [ Test Plan ]

  There will be 2 separate tests for this bug:
  * Ensuring no-change rebuilds are not changed
  * Ensuring local builds are not changed unless environment variable is set

  Test 1) No-change rebuilds

  To test that no-change rebuilds are not changed, the package python-
  stdlib-extensions will be built against the new python2.7, and confirm
  the compiler flags are not altered. This will be a manual test and
  visual inspection of the build logs.

  Test 2) Functional test

  1. Create test container
  $ lxc launch ubuntu:jammy jammy-2002043
  $ lxc shell ubuntu:jammy jammy-2002043

  2. Install required packages
  For Jammy
  # apt update -y && apt install -y python2 python-pip
  For Focal
  # apt update -y && apt install -y python2 python-setuptools

  3. Create test files
  # mkdir testprog
  # cd testprog
  # cat >setup.py 

[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

That's a great idea Andreas! It's a little difficult to pinpoint the
exact OPT flags as they are bunched up with the other compiler flags, so
I'll add a test in addition to the current ones which makes it easier to
see what's happening.

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  Fix Committed
Status in python2.7 source package in Jammy:
  Fix Committed
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  When compiling Python extensions using Python2, CFLAGS optimization
  flags are dropped.

  This behavior has been caused by our update in this patch
  
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
  which differs from upstream.

  The fix modifies the portion of code in Lib/distutils/sysconfig.py
  which gets the cflags from the environments, and includes the dropped
  OPT flag from get_config_vars().

  [ Test Plan ]

  There will be 2 separate tests for this bug:
  * Ensuring no-change rebuilds are not changed
  * Ensuring local builds are not changed unless environment variable is set

  Test 1) No-change rebuilds

  To test that no-change rebuilds are not changed, the package python-
  stdlib-extensions will be built against the new python2.7, and confirm
  the compiler flags are not altered. This will be a manual test and
  visual inspection of the build logs.

  Test 2) Functional test

  1. Create test container
  $ lxc launch ubuntu:jammy jammy-2002043
  $ lxc shell ubuntu:jammy jammy-2002043

  2. Install required packages
  For Jammy
  # apt update -y && apt install -y python2 python-pip
  For Focal
  # apt update -y && apt install -y python2 python-setuptools

  3. Create test files
  # mkdir testprog
  # cd testprog
  # cat >setup.py 

[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

** Merge proposal linked:
   
https://code.launchpad.net/~mitchdz/ubuntu/+source/python2.7/+git/python2.7/+merge/459844

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  In Progress
Status in python2.7 source package in Jammy:
  In Progress
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  [ Impact ]

  When compiling Python extensions using Python2, CFLAGS optimization
  flags are dropped.

  This behavior has been caused by our update in this patch
  
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
  which differs from upstream.

  The fix modifies the portion of code in Lib/distutils/sysconfig.py
  which gets the cflags from the environments, and includes the dropped
  OPT flag from get_config_vars().

  [ Test Plan ]

  There will be 2 separate tests for this bug:
  * Ensuring no-change rebuilds are not changed
  * Ensuring local builds are not changed unless environment variable is set

  Test 1) No-change rebuilds

  To test that no-change rebuilds are not changed, the package python-
  stdlib-extensions will be built against the new python2.7, and confirm
  the compiler flags are not altered. This will be a manual test and
  visual inspection of the build logs.

  Test 2) Functional test

  1. Create test container
  $ lxc launch ubuntu:jammy jammy-2002043
  $ lxc shell ubuntu:jammy jammy-2002043

  2. Install required packages
  For Jammy
  # apt update -y && apt install -y python2 python-pip
  For Focal
  # apt update -y && apt install -y python2 python-setuptools

  3. Create test files
  # mkdir testprog
  # cd testprog
  # cat >setup.py 

[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

** Description changed:

  [ Impact ]
  
  When compiling Python extensions using Python2, CFLAGS optimization
  flags are dropped.
  
  This behavior has been caused by our update in this patch
  
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
  which differs from upstream.
  
  The fix modifies the portion of code in Lib/distutils/sysconfig.py which
  gets the cflags from the environments, and includes the dropped OPT flag
  from get_config_vars().
  
  [ Test Plan ]
  
  There will be 2 separate tests for this bug:
  * Ensuring no-change rebuilds are not changed
  * Ensuring local builds are not changed unless environment variable is set
  
  Test 1) No-change rebuilds
  
  To test that no-change rebuilds are not changed, the package python-
  stdlib-extensions will be built against the new python2.7, and confirm
  the compiler flags are not altered. This will be a manual test and
  visual inspection of the build logs.
  
  Test 2) Functional test
  
  1. Create test container
- $ lxc launch ubuntu:jammy jammy-2002043 
+ $ lxc launch ubuntu:jammy jammy-2002043
  $ lxc shell ubuntu:jammy jammy-2002043
  
  2. Install required packages
+ For Jammy
  # apt update -y && apt install -y python2 python-pip
+ For Focal
+ # apt update -y && apt install -y python2 python-setuptools
  
  3. Create test files
  # mkdir testprog
  # cd testprog
  # cat >setup.py 

[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

Description Updated. I'll work on getting the patch for Jammy approved
and then I will create the patch for Focal. I expect (and would love)
feedback on wording for the new print statements I made.

** Description changed:

- Compiling a Python extension using Python2 (Python 2.7.18) is making use
- of wrong compiler flags, hence dropping required optimizations when
- required. This is happening only when python2 is installed from Ubuntu's
- repositories. By default, Python's distutils module uses compiler and
- linker flags used to compile Python itself to be used to compile
- extensions.
+ [ Impact ]
  
- Steps to reproduce:
- 1) On Ubuntu 20.04, install python2 using apt package manager.
- 2) After successful installation, verify the CFLAGS variable from sysconfig 
module. On my machine, the output is 
+ When compiling Python extensions using Python2, CFLAGS optimization
+ flags are dropped.
  
- Python 2.7.18 (default, Jul  1 2022, 12:27:04)
- [GCC 9.4.0] on linux2
- Type "help", "copyright", "credits" or "license" for more information.
- >>> import sysconfig
- >>> sysconfig.get_config_var('CFLAGS')
- '-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security  '
+ This behavior has been caused by our update in this patch
+ 
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz
+ which differs from upstream.
  
- 3) Build a test extension module using python2 and verify the compilation 
flags. 
- python2 setup.py build_ext --inplace
+ The fix modifies the portion of code in Lib/distutils/sysconfig.py which
+ gets the cflags from the environments, and includes the dropped OPT flag
+ from get_config_vars().
  
- Output from below command is not matching with our expected above CFLAGS. 
- aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time 
-D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c testmodule.c -o 
build/temp.linux-aarch64-2.7/testmodule.o
+ [ Test Plan ]
+ 
+ There will be 2 separate tests for this bug:
+ * Ensuring no-change rebuilds are not changed
+ * Ensuring local builds are not changed unless environment variable is set
+ 
+ Test 1) No-change rebuilds
+ 
+ To test that no-change rebuilds are not changed, the package python-
+ stdlib-extensions will be built against the new python2.7, and confirm
+ the compiler flags are not altered. This will be a manual test and
+ visual inspection of the build logs.
+ 
+ Test 2) Functional test
+ 
+ 1. Create test container
+ $ lxc launch ubuntu:jammy jammy-2002043 
+ $ lxc shell ubuntu:jammy jammy-2002043
+ 
+ 2. Install required packages
+ # apt update -y && apt install -y python2 python-pip
+ 
+ 3. Create test files
+ # mkdir testprog
+ # cd testprog
+ # cat >setup.py 

[Touch-packages] [Bug 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

Thanks Nafees! I'll go ahead and prepare the SRU and move forward with
it.

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  In Progress
Status in python2.7 source package in Jammy:
  In Progress
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  Compiling a Python extension using Python2 (Python 2.7.18) is making
  use of wrong compiler flags, hence dropping required optimizations
  when required. This is happening only when python2 is installed from
  Ubuntu's repositories. By default, Python's distutils module uses
  compiler and linker flags used to compile Python itself to be used to
  compile extensions.

  Steps to reproduce:
  1) On Ubuntu 20.04, install python2 using apt package manager.
  2) After successful installation, verify the CFLAGS variable from sysconfig 
module. On my machine, the output is 

  Python 2.7.18 (default, Jul  1 2022, 12:27:04)
  [GCC 9.4.0] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sysconfig
  >>> sysconfig.get_config_var('CFLAGS')
  '-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security  '

  3) Build a test extension module using python2 and verify the compilation 
flags. 
  python2 setup.py build_ext --inplace

  Output from below command is not matching with our expected above CFLAGS. 
  aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time 
-D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c testmodule.c -o 
build/temp.linux-aarch64-2.7/testmodule.o

  
  On further investigation, it looks like Ubuntu's specific patch applied on 
libpython2.7-stdlib package is altering the original upstream implementation of 
distutils/sysconfig.py code.

  Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
  Patch - 
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz

  Below is the code block which is causing the issue, where the presence of 
configure_cflags is modifying cflags. This code is result of ubuntu's patch and 
doesn't come directly from upstream python implementation.
  File - /usr/lib/python2.7/distutils/sysconfig.py
  Part of code block:
  elif configure_cflags:
  cflags = ' '.join(str(x) for x in (basecflags, configure_cflags, 
extra_cflags) if x)
  ldshared = ldshared + ' ' + configure_cflags

  
  I don't see problem on Python3 though we have extra code added from patch 
there as well. Patch used on python3, is not modifying the cflags completely 
and instead appending new flags to cflags.
  On python3 (tested on Ubuntu 20.04)
  File - /usr/lib/python3.8/distutils/sysconfig.py
  Part of code block which doesn't alter cflags completely
  elif configure_cflags:
  cflags = cflags + ' ' + configure_cflags
  ldshared = ldshared + ' ' + configure_cflags

  
  Request to update the python2 patch to behave similar to what is been done on 
python3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

Nafees, while exploring adding this change, a priority is to not cause
any regressions in packages already built in the archives. This is
unfortunately a non-trivial change so I'm proposing making this an opt-
in change, but make an informative message whenever someone compiles
wheels, so they can be made aware of it. This will make it so there's
minimal chances of regression, and spreads the word of this change.

How does this solution sound? I have the change staged in
https://code.launchpad.net/~mitchdz/ubuntu/+source/python2.7/+git/python2.7/+merge/458533

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  In Progress
Status in python2.7 source package in Jammy:
  In Progress
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  Compiling a Python extension using Python2 (Python 2.7.18) is making
  use of wrong compiler flags, hence dropping required optimizations
  when required. This is happening only when python2 is installed from
  Ubuntu's repositories. By default, Python's distutils module uses
  compiler and linker flags used to compile Python itself to be used to
  compile extensions.

  Steps to reproduce:
  1) On Ubuntu 20.04, install python2 using apt package manager.
  2) After successful installation, verify the CFLAGS variable from sysconfig 
module. On my machine, the output is 

  Python 2.7.18 (default, Jul  1 2022, 12:27:04)
  [GCC 9.4.0] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sysconfig
  >>> sysconfig.get_config_var('CFLAGS')
  '-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security  '

  3) Build a test extension module using python2 and verify the compilation 
flags. 
  python2 setup.py build_ext --inplace

  Output from below command is not matching with our expected above CFLAGS. 
  aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time 
-D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c testmodule.c -o 
build/temp.linux-aarch64-2.7/testmodule.o

  
  On further investigation, it looks like Ubuntu's specific patch applied on 
libpython2.7-stdlib package is altering the original upstream implementation of 
distutils/sysconfig.py code.

  Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
  Patch - 
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz

  Below is the code block which is causing the issue, where the presence of 
configure_cflags is modifying cflags. This code is result of ubuntu's patch and 
doesn't come directly from upstream python implementation.
  File - /usr/lib/python2.7/distutils/sysconfig.py
  Part of code block:
  elif configure_cflags:
  cflags = ' '.join(str(x) for x in (basecflags, configure_cflags, 
extra_cflags) if x)
  ldshared = ldshared + ' ' + configure_cflags

  
  I don't see problem on Python3 though we have extra code added from patch 
there as well. Patch used on python3, is not modifying the cflags completely 
and instead appending new flags to cflags.
  On python3 (tested on Ubuntu 20.04)
  File - /usr/lib/python3.8/distutils/sysconfig.py
  Part of code block which doesn't alter cflags completely
  elif configure_cflags:
  cflags = cflags + ' ' + configure_cflags
  ldshared = ldshared + ' ' + configure_cflags

  
  Request to update the python2 patch to behave similar to what is been done on 
python3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

** Merge proposal linked:
   
https://code.launchpad.net/~mitchdz/ubuntu/+source/python2.7/+git/python2.7/+merge/458533

** Changed in: python2.7 (Ubuntu Jammy)
 Assignee: Ghadi Rahme (ghadi-rahme) => Mitchell Dzurick (mitchdz)

** Changed in: python2.7 (Ubuntu Focal)
 Assignee: Ghadi Rahme (ghadi-rahme) => Mitchell Dzurick (mitchdz)

** Changed in: python2.7 (Ubuntu Lunar)
 Assignee: Ghadi Rahme (ghadi-rahme) => (unassigned)

** Changed in: python2.7 (Ubuntu Mantic)
 Assignee: Ghadi Rahme (ghadi-rahme) => (unassigned)

** Changed in: python2.7 (Ubuntu Kinetic)
 Assignee: Ghadi Rahme (ghadi-rahme) => (unassigned)

** Changed in: python2.7 (Ubuntu Bionic)
 Assignee: Ghadi Rahme (ghadi-rahme) => (unassigned)

** Changed in: python2.7 (Ubuntu)
 Assignee: Ghadi Rahme (ghadi-rahme) => (unassigned)

** Changed in: python2.7 (Ubuntu Focal)
   Status: Won't Fix => In Progress

** Changed in: python2.7 (Ubuntu Jammy)
   Status: Won't Fix => In Progress

** Changed in: python2.7 (Ubuntu)
   Status: In Progress => Invalid

** Changed in: python2.7 (Ubuntu Kinetic)
   Status: Won't Fix => Invalid

** Changed in: python2.7 (Ubuntu Lunar)
   Status: Won't Fix => Invalid

** Changed in: python2.7 (Ubuntu Mantic)
   Status: Won't Fix => Invalid

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  Invalid
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  In Progress
Status in python2.7 source package in Jammy:
  In Progress
Status in python2.7 source package in Kinetic:
  Invalid
Status in python2.7 source package in Lunar:
  Invalid
Status in python2.7 source package in Mantic:
  Invalid

Bug description:
  Compiling a Python extension using Python2 (Python 2.7.18) is making
  use of wrong compiler flags, hence dropping required optimizations
  when required. This is happening only when python2 is installed from
  Ubuntu's repositories. By default, Python's distutils module uses
  compiler and linker flags used to compile Python itself to be used to
  compile extensions.

  Steps to reproduce:
  1) On Ubuntu 20.04, install python2 using apt package manager.
  2) After successful installation, verify the CFLAGS variable from sysconfig 
module. On my machine, the output is 

  Python 2.7.18 (default, Jul  1 2022, 12:27:04)
  [GCC 9.4.0] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sysconfig
  >>> sysconfig.get_config_var('CFLAGS')
  '-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security  '

  3) Build a test extension module using python2 and verify the compilation 
flags. 
  python2 setup.py build_ext --inplace

  Output from below command is not matching with our expected above CFLAGS. 
  aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time 
-D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c testmodule.c -o 
build/temp.linux-aarch64-2.7/testmodule.o

  
  On further investigation, it looks like Ubuntu's specific patch applied on 
libpython2.7-stdlib package is altering the original upstream implementation of 
distutils/sysconfig.py code.

  Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
  Patch - 
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz

  Below is the code block which is causing the issue, where the presence of 
configure_cflags is modifying cflags. This code is result of ubuntu's patch and 
doesn't come directly from upstream python implementation.
  File - /usr/lib/python2.7/distutils/sysconfig.py
  Part of code block:
  elif configure_cflags:
  cflags = ' '.join(str(x) for x in (basecflags, configure_cflags, 
extra_cflags) if x)
  ldshared = ldshared + ' ' + configure_cflags

  
  I don't see problem on Python3 though we have extra code added from patch 
there as well. Patch used on python3, is not modifying the cflags completely 
and instead appending new flags to cflags.
  On python3 (tested on Ubuntu 20.04)
  File - /usr/lib/python3.8/distutils/sysconfig.py
  Part of code block which doesn't alter cflags completely
  elif configure_cflags:
  cflags = cflags + ' ' + configure_cflags
  ldshared = ldshared + ' ' + configure_cflags

  
  Request to update the python2 pat

[Touch-packages] [Bug 2048081] Re: package openssh-client 1:8.9p1-3ubuntu0.5 failed to install/upgrade: não pode copiar dados extráidos para './usr/lib/openssh/ssh-pkcs11-helper' para '/usr/lib/openss

[Mitchell Dzurick]

In the terminal I see dpkg-deb (sub-processo): ZSTD_decompressStream error : 
Corrupted block detected 
 which makes me think the package was corrupted in transport.

Try

sudo apt-get clean
sudo apt-get update


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

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

Title:
  package openssh-client 1:8.9p1-3ubuntu0.5 failed to install/upgrade:
  não pode copiar dados extráidos para './usr/lib/openssh/ssh-
  pkcs11-helper' para '/usr/lib/openssh/ssh-pkcs11-helper.dpkg-new': fim
  de ficheiro ou stream inesperado

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Do not upgrade

  dpkg-deb: erro: o subprocesso  retornou erro do status de 
saída 2
  dpkg: erro ao processar o arquivo 
/var/cache/apt/archives/openssh-client_1%3a8.9p1-3ubuntu0.6_amd64.deb 
(--unpack):
   não pode copiar dados extráidos para './usr/lib/openssh/ssh-pkcs11-helper' 
para '/usr/lib/openssh/ssh-pkcs11-helper.dpkg-new': fim de ficheiro ou s
  tream inesperado
  Erros foram encontrados durante o processamento de:
   /var/cache/apt/archives/openssh-client_1%3a8.9p1-3ubuntu0.6_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: openssh-client 1:8.9p1-3ubuntu0.5
  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
  AptOrdering:
   libsqlite3-0:i386: Install
   libsqlite3-0:amd64: Install
   openssh-client:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jan  4 09:23:18 2024
  ErrorMessage: não pode copiar dados extráidos para 
'./usr/lib/openssh/ssh-pkcs11-helper' para 
'/usr/lib/openssh/ssh-pkcs11-helper.dpkg-new': fim de ficheiro ou stream 
inesperado
  InstallationDate: Installed on 2023-12-30 (4 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_8.9p1 Ubuntu-3ubuntu0.5, OpenSSL 3.0.2 15 Mar 2022
  SourcePackage: openssh
  Title: package openssh-client 1:8.9p1-3ubuntu0.5 failed to install/upgrade: 
não pode copiar dados extráidos para './usr/lib/openssh/ssh-pkcs11-helper' para 
'/usr/lib/openssh/ssh-pkcs11-helper.dpkg-new': fim de ficheiro ou stream 
inesperado
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2048081/+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 2040389] Re: Merge libmnl from Debian unstable for noble

[Mitchell Dzurick]

The only Ubuntu delta is now in Debian. Requesting a sync.

** Merge proposal linked:
   
https://code.launchpad.net/~mitchdz/ubuntu/+source/libmnl/+git/libmnl/+merge/457925

** Tags removed: needs-merge
** Tags added: needs-sync

** Summary changed:

- Merge libmnl from Debian unstable for noble
+ Sync libmnl from Debian unstable for noble

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

Title:
  Sync libmnl from Debian unstable for noble

Status in libmnl package in Ubuntu:
  New

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1.0.5.2
  Ubuntu:   1.0.4-3ubuntu1

  There is nothing yet to merge for libmnl currently, but this ticket is
  filed prospectfully for tracking purposes in case a merge does become
  available later this cycle.

  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.

  ### Old Ubuntu Delta ###

  libmnl (1.0.4-3ubuntu1) kinetic; urgency=medium

    * Static build does not work for libmnl (-lmnl) (LP: #1971523)

   -- Michal Maloszewski   Thu, 21 Jul
  2022 14:02:16 +0200

  libmnl (1.0.4-3build2) jammy; urgency=high

    * No change rebuild for ppc64el baseline bump.

   -- Julian Andres Klode   Thu, 24 Mar 2022
  13:13:28 +0100

  libmnl (1.0.4-3build1) impish; urgency=medium

    * No-change rebuild to build packages with zstd compression.

   -- Matthias Klose   Thu, 07 Oct 2021 12:16:42 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/2040389/+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 2040389] Re: Merge libmnl from Debian unstable for noble

[Mitchell Dzurick]

** Changed in: libmnl (Ubuntu)
 Assignee: (unassigned) => Mitchell Dzurick (mitchdz)

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

Title:
  Merge libmnl from Debian unstable for noble

Status in libmnl package in Ubuntu:
  New

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1.0.5.2
  Ubuntu:   1.0.4-3ubuntu1

  There is nothing yet to merge for libmnl currently, but this ticket is
  filed prospectfully for tracking purposes in case a merge does become
  available later this cycle.

  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.

  ### Old Ubuntu Delta ###

  libmnl (1.0.4-3ubuntu1) kinetic; urgency=medium

    * Static build does not work for libmnl (-lmnl) (LP: #1971523)

   -- Michal Maloszewski   Thu, 21 Jul
  2022 14:02:16 +0200

  libmnl (1.0.4-3build2) jammy; urgency=high

    * No change rebuild for ppc64el baseline bump.

   -- Julian Andres Klode   Thu, 24 Mar 2022
  13:13:28 +0100

  libmnl (1.0.4-3build1) impish; urgency=medium

    * No-change rebuild to build packages with zstd compression.

   -- Matthias Klose   Thu, 07 Oct 2021 12:16:42 +0200

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/2040389/+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] Re: jammy's version breaks existing dhcp scripts with relay

[Mitchell Dzurick]

** Tags added: server-todo

-- 
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:
  New
Status in dnsmasq source package in Jammy:
  Triaged

Bug 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+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 2043114] Re: sshd segmentation fault on 20.04.6 (focal)

[Mitchell Dzurick]

Thank you Ivaylo for creating this bug report and helping make Ubuntu
better!

I have 2 follow up questions:
1. How often do these segmentation faults occur for you?
2. Have you tried to SSH to the Focal server from multiple other systems? Do 
you encounter this issue with multiple systems, or is it only observed with one?

Could you also run `apport-collect 2043114` in the server that is
encountering the seg faults? This will gather debugging information that
may be valuable.

I see the backtrace has the error
nextinuse = 

I briefly looked into the upstream repository to try and find related
commits to this issue and didn't see any commits pop out at me

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

Title:
  sshd segmentation fault on 20.04.6 (focal)

Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  We have a physical server running Ubuntu 20.04.6 LTS (amd64) and 
openssh-server 1:8.2p1-4ubuntu0.9. Sometimes sshd crashes with a segmentation 
fault on remote login with key authentication:
  [193107.651745] sshd[1229630]: segfault at 5557eba6a008 ip 7f2326a2ca53 
sp 7ffcba40c510 error 4 in libc-2.31.so[7f23269b8000+178000]

  We’ve changed only the following values in the stock sshd_config file:

  LogLevel DEBUG
  PasswordAuthentication no
  MaxStartups 100:30:100

  The server is used for automated software testing, and sometimes our test 
suite might make a large amount of SSH connections in a short period of time, 
which seems to be correlated with the crashes. But at the same time, I have to 
note that the connection count was not near the MaxStartups limit, and we’ve 
had crashes before adding that setting.
  Since the backtrace shows the debug logging function in the stack, we’re 
currently experimenting with using `LogLevel INFO` to try and isolate the issue.

  I am attaching the backtrace. I could provide the full dump file,
  although I am hesitant due to the possibility of private keys or other
  sensitive information leaking.

  # apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.2p1-4ubuntu0.9
Candidate: 1:8.2p1-4ubuntu0.9
Version table:
   *** 1:8.2p1-4ubuntu0.9 500
  500 http://mirrors.storpool.com/ubuntu/archive focal-updates/main 
amd64 Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:8.2p1-4 500
  500 http://mirrors.storpool.com/ubuntu/archive focal/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2043114/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

Hi, I have the patch modified how I want it to, I'm still exploring ways
to blocklist the current launchpad builds, as I'm not sure I can extract
the necessary metadata in distutils.sysconfig.

I'll be exploring more next week and attempting to find a reliable way
to determine the name of the python wheel being built in the file that
we are making the change.

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  In Progress
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  Won't Fix
Status in python2.7 source package in Jammy:
  Won't Fix
Status in python2.7 source package in Kinetic:
  Won't Fix
Status in python2.7 source package in Lunar:
  Won't Fix
Status in python2.7 source package in Mantic:
  Won't Fix

Bug description:
  Compiling a Python extension using Python2 (Python 2.7.18) is making
  use of wrong compiler flags, hence dropping required optimizations
  when required. This is happening only when python2 is installed from
  Ubuntu's repositories. By default, Python's distutils module uses
  compiler and linker flags used to compile Python itself to be used to
  compile extensions.

  Steps to reproduce:
  1) On Ubuntu 20.04, install python2 using apt package manager.
  2) After successful installation, verify the CFLAGS variable from sysconfig 
module. On my machine, the output is 

  Python 2.7.18 (default, Jul  1 2022, 12:27:04)
  [GCC 9.4.0] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sysconfig
  >>> sysconfig.get_config_var('CFLAGS')
  '-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security  '

  3) Build a test extension module using python2 and verify the compilation 
flags. 
  python2 setup.py build_ext --inplace

  Output from below command is not matching with our expected above CFLAGS. 
  aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time 
-D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c testmodule.c -o 
build/temp.linux-aarch64-2.7/testmodule.o

  
  On further investigation, it looks like Ubuntu's specific patch applied on 
libpython2.7-stdlib package is altering the original upstream implementation of 
distutils/sysconfig.py code.

  Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
  Patch - 
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz

  Below is the code block which is causing the issue, where the presence of 
configure_cflags is modifying cflags. This code is result of ubuntu's patch and 
doesn't come directly from upstream python implementation.
  File - /usr/lib/python2.7/distutils/sysconfig.py
  Part of code block:
  elif configure_cflags:
  cflags = ' '.join(str(x) for x in (basecflags, configure_cflags, 
extra_cflags) if x)
  ldshared = ldshared + ' ' + configure_cflags

  
  I don't see problem on Python3 though we have extra code added from patch 
there as well. Patch used on python3, is not modifying the cflags completely 
and instead appending new flags to cflags.
  On python3 (tested on Ubuntu 20.04)
  File - /usr/lib/python3.8/distutils/sysconfig.py
  Part of code block which doesn't alter cflags completely
  elif configure_cflags:
  cflags = cflags + ' ' + configure_cflags
  ldshared = ldshared + ' ' + configure_cflags

  
  Request to update the python2 patch to behave similar to what is been done on 
python3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/2002043/+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 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect

[Mitchell Dzurick]

Thank you Daniel! Over the week I upgraded my laptop to Mantic, so can
no longer test for Jammy.

I still can't discover my logitech mice in Mantic, so maybe still the
same situation.

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] acpidump.txt

[Mitchell Dzurick]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2040657/+attachment/5715734/+files/acpidump.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] modified.conffile..etc.bluetooth.main.conf.txt

[Mitchell Dzurick]

apport information

** Attachment added: "modified.conffile..etc.bluetooth.main.conf.txt"
   
https://bugs.launchpad.net/bugs/2040657/+attachment/5715736/+files/modified.conffile..etc.bluetooth.main.conf.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] syslog.txt

[Mitchell Dzurick]

apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/2040657/+attachment/5715738/+files/syslog.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] rfkill.txt

[Mitchell Dzurick]

apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/2040657/+attachment/5715737/+files/rfkill.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] UdevDb.txt

[Mitchell Dzurick]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2040657/+attachment/5715733/+files/UdevDb.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] getfacl.txt

[Mitchell Dzurick]

apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/2040657/+attachment/5715735/+files/getfacl.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] ProcModules.txt

[Mitchell Dzurick]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2040657/+attachment/5715732/+files/ProcModules.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] ProcCpuinfoMinimal.txt

[Mitchell Dzurick]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2040657/+attachment/5715730/+files/ProcCpuinfoMinimal.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] ProcCpuinfo.txt

[Mitchell Dzurick]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2040657/+attachment/5715729/+files/ProcCpuinfo.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] ProcInterrupts.txt

[Mitchell Dzurick]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2040657/+attachment/5715731/+files/ProcInterrupts.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] Lsusb-v.txt

[Mitchell Dzurick]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/2040657/+attachment/5715728/+files/Lsusb-v.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] Lsusb.txt

[Mitchell Dzurick]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/2040657/+attachment/5715726/+files/Lsusb.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] Lsusb-t.txt

[Mitchell Dzurick]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/2040657/+attachment/5715727/+files/Lsusb-t.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] Lspci-vt.txt

[Mitchell Dzurick]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2040657/+attachment/5715725/+files/Lspci-vt.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] Dependencies.txt

[Mitchell Dzurick]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2040657/+attachment/5715723/+files/Dependencies.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect

[Mitchell Dzurick]

apport information

** Tags added: apport-collected mantic wayland-session

** Description changed:

  I lost the proprietary USB dongle and decided I wanted to try bluetooth
  with this particular mouse. I am able to connect with bluetooth on
  Windows 11, but the device doesn't even show up in `bluetoothctl scan
  on`.
  
  This is seen on Jammy with bluez 5.64-0ubuntu1
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.27.0-0ubuntu5
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 23.10
+ InstallationDate: Installed on 2023-03-06 (242 days ago)
+ InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
+ NonfreeKernelModules: zfs
+ Package: bluez 5.68-0ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  LANG=en_US.UTF-8
+  PATH=(custom, no user)
+  SHELL=/usr/bin/zsh
+  TERM=xterm-256color
+  XDG_RUNTIME_DIR=
+ ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
+ Tags: mantic wayland-session
+ Uname: Linux 6.5.0-10-generic x86_64
+ UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
+ UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
+ _MarkForUpload: True
+ dmi.bios.date: 07/18/2023
+ dmi.bios.release: 1.58
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N2HET75W (1.58 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20QDUS
+ dmi.board.vendor: LENOVO
+ dmi.board.version: SDK0J40709 WIN
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.ec.firmware.release: 1.25
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
+ dmi.product.family: ThinkPad X1 Carbon 7th
+ dmi.product.name: 20QDUS
+ dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
+ dmi.product.version: ThinkPad X1 Carbon 7th
+ dmi.sys.vendor: LENOVO
+ hciconfig:
+  hci0:Type: Primary  Bus: USB
+   BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
+   UP RUNNING PSCAN ISCAN INQUIRY 
+   RX bytes:21473 acl:0 sco:0 events:2871 errors:0
+   TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
+ mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2040657/+attachment/5715722/+files/CurrentDmesg.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 

[Touch-packages] [Bug 2040657] Lspci.txt

[Mitchell Dzurick]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2040657/+attachment/5715724/+files/Lspci.txt

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1
  --- 
  ProblemType: Bug
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 23.10
  InstallationDate: Installed on 2023-03-06 (242 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  NonfreeKernelModules: zfs
  Package: bluez 5.68-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/usr/bin/zsh
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Tags: mantic wayland-session
  Uname: Linux 6.5.0-10-generic x86_64
  UpgradeStatus: Upgraded to mantic on 2023-10-31 (3 days ago)
  UserGroups: adm cdrom dip libvirt lp lpadmin lxd plugdev sambashare sbuild 
sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2023
  dmi.bios.release: 1.58
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2HET75W (1.58 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20QDUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.25
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2HET75W(1.58):bd07/18/2023:br1.58:efr1.25:svnLENOVO:pn20QDUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDUS:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QD_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20QDUS
  dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:AB:D5:BB:40:FD  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN ISCAN INQUIRY 
RX bytes:21473 acl:0 sco:0 events:2871 errors:0
TX bytes:692880 acl:0 sco:0 commands:2838 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2023-08-16T12:28:27.725767

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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] Re: jammy's version breaks existing dhcp scripts with relay

[Mitchell Dzurick]

Thanks for taking the time to report this bug Timo!

Do you have steps for how you setup dnsmasq so it can be more easy to
reproduce your issue?

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

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

Bug 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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+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 2040281] Re: mkhomedir and pam_mount incompatibility

[Mitchell Dzurick]

Hi Virginie, I tried to reproduce this in an LXD vm

$ lxc launch ubuntu:jammy j --vm
$ lxc shell j
# apt install -y sssd-ad sssd-tools realmd adcli
# pam-auth-update --enable mkhomedir
# sudo add-apt-repository "deb http://archive.ubuntu.com/ubuntu $(lsb_release 
-sc) main universe restricted multiverse"
# apt install -y lib_pam_mount

Now add


Under  in /etc/security/pam_mount.conf.xml

# adduser mitch
# su mitch
$ ls ~/
shared


I see the shared folder in my test, is your issue that you don't see the shared 
folder?

** Changed in: libpam-mount (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  mkhomedir and pam_mount incompatibility

Status in libpam-mount package in Ubuntu:
  Incomplete
Status in pam package in Ubuntu:
  Incomplete

Bug description:
  Hello
  I have use realm to join a domain without difficulty and use
  pam-auth-update --enable mkhomedir, as suggest by the documentation
  The problem is, when a new user log into the system, the content of /etc/skel 
is not copy into the new home directory, even if Download Desktop are 
created.
  Adduser work normally and the homedirectory is created fine.
  The problem come from the additional pam module pam_mount, in my case this 
one try to mount a shared ressource in the homedir of the user.
  By default in /etc/pam.d/common.session pam_mount is called before 
pam_mkhomedir.so.
  If I deplace the pam_mkhomedir line before the pam_mount everything is 
working fine

  
  Thanks for your attention

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libpam-mount/+bug/2040281/+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 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect

[Mitchell Dzurick]

I am able to connect with the unifying receiver which is good enough for
now. It'd still be nice for regular bluetooth to work.

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  New

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] Re: bluez does not detect Logitech Pebble M350, no option to connect

[Mitchell Dzurick]

Actually after opening this bug I decided to try my MX master 3S with
bluetooth mode and that's not detected either. I also tried a pair of
airpods and those are not seen.

the weird part is that I am actively using some samsung galaxy buds with
this laptop via bluetooth and they work.

So perhaps there's something generally wrong with bluetooth discovery on
my laptop.

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  New

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2040657] [NEW] bluez does not detect Logitech Pebble M350, no option to connect

[Mitchell Dzurick]

Public bug reported:

I lost the proprietary USB dongle and decided I wanted to try bluetooth
with this particular mouse. I am able to connect with bluetooth on
Windows 11, but the device doesn't even show up in `bluetoothctl scan
on`.

This is seen on Jammy with bluez 5.64-0ubuntu1

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

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

Title:
  bluez does not detect Logitech Pebble M350, no option to connect

Status in bluez package in Ubuntu:
  New

Bug description:
  I lost the proprietary USB dongle and decided I wanted to try
  bluetooth with this particular mouse. I am able to connect with
  bluetooth on Windows 11, but the device doesn't even show up in
  `bluetoothctl scan on`.

  This is seen on Jammy with bluez 5.64-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2040657/+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 2039752] Re: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Mitchell Dzurick]

@Markle Liu if you still have your system in the affected state, could
you please give the output of these following commands?

# systemctl status ssh.{socket,service} tinysshd.socket
# lsof -i :22
# systemctl list-units | grep ssh

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

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

Title:
  package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I don't known, but the system report the bug

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: openssh-server 1:9.0p1-1ubuntu8.5
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 19 09:27:02 2023
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-18 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: 
installed openssh-server 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/openssh/+bug/2039752/+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 2039752] Re: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Mitchell Dzurick]

Interesting, I tried in a new LXC container and I see it working now.
$ lxc launch ubuntu:lunar l
$ lxc shell l
# apt install -y openssh-client=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-sftp-server=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-server=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-server=1:9.0p1-1ubuntu8.5 -y


In my original container, the upgrade failed because tinysshd.socket was using 
port 22 so when openssh-server.postinst attempted to run `deb-systemd-invoke 
restart ssh.socket` it failed due to resource issues (port 22 already being 
used) which caused dpkg to fail. I assume this is the same case in the bug 
report

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

Title:
  package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I don't known, but the system report the bug

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: openssh-server 1:9.0p1-1ubuntu8.5
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 19 09:27:02 2023
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-18 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: 
installed openssh-server 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/openssh/+bug/2039752/+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 2039752] Re: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Mitchell Dzurick]

I only see those errors in a container. When I launch a VM to try this,
I see no errors.

$ lxc launch ubuntu:lunar l-vm --vm
$ lxc shell l-vm
# apt install -y openssh-client=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-sftp-server=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-server=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-server=1:9.0p1-1ubuntu8.5
...
Setting up openssh-client (1:9.0p1-1ubuntu8.5) ...
Setting up openssh-sftp-server (1:9.0p1-1ubuntu8.5) ...
Setting up openssh-server (1:9.0p1-1ubuntu8.5) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Processing triggers for man-db (2.11.2-1) ...
Processing triggers for ufw (0.36.1-4.1ubuntu0.1) ...
Scanning processes...   
  
Scanning linux images...
  

Running kernel seems to be up-to-date.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on this
host.

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

Title:
  package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I don't known, but the system report the bug

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: openssh-server 1:9.0p1-1ubuntu8.5
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 19 09:27:02 2023
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-18 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: 
installed openssh-server 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/openssh/+bug/2039752/+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 2039752] Re: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: installed openssh-server package post-installation script subprocess returned error exit status

[Mitchell Dzurick]

Relevant Dpkg errors:

openssh-server (1:9.0p1-1ubuntu8.5) over (1:9.0p1-1ubuntu8)
...
Setting up openssh-server (1:9.0p1-1ubuntu8.5) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned 
error exit status 1

So this error was seen when upgrading from the release version of
openssh in Lunar to the current latest version in updates.

I tried to reproduce in an lxc container. Had to downgrade 2 packages like so:
$ lxc launch ubuntu:lunar l
$ lxc shell l
# apt install -y openssh-sftp-server=1:9.0p1-1ubuntu8 -y --allow-downgrades
# apt install -y openssh-client=1:9.0p1-1ubuntu8 -y --allow-downgrades

upon downgrading openssh-server I see this error

Selecting previously unselected package openssh-server.
(Reading database ... 33940 files and directories currently installed.)
Preparing to unpack .../openssh-server_1%3a9.0p1-1ubuntu8_amd64.deb ...
Unpacking openssh-server (1:9.0p1-1ubuntu8) ...
Setting up openssh-server (1:9.0p1-1ubuntu8) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned 
error exit stat
us 1
dmesg: read kernel buffer failed: Operation not permitted
 Processing triggers 
for man-db (2.11.
2-1) ...
Processing triggers for ufw (0.36.1-4.1ubuntu0.1) ...
Errors were encountered while processing:
 openssh-server
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)


Attempting to upgrade to 8.5 I see:

root@l:~# apt-cache policy openssh-server
Setting up openssh-client (1:9.0p1-1ubuntu8.5) ...
Setting up openssh-sftp-server (1:9.0p1-1ubuntu8.5) ...
Setting up openssh-server (1:9.0p1-1ubuntu8.5) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 145.
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess returned 
error exit stat
us 1
dmesg: read kernel buffer failed: Operation not permitted
 Processing triggers 
for man-db (2.11.
2-1) ...
Processing triggers for ufw (0.36.1-4.1ubuntu0.1) ...
Errors were encountered while processing:
 openssh-server
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  returned error exit status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  I don't known, but the system report the bug

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: openssh-server 1:9.0p1-1ubuntu8.5
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Oct 19 09:27:02 2023
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-18 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: openssh
  Title: package openssh-server 1:9.0p1-1ubuntu8.5 failed to install/upgrade: 
installed openssh-server 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/openssh/+bug/2039752/+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 2038561] Re: Requesting Ubuntu package manager to release openssh updates to focal and jammy

[Mitchell Dzurick]

Hi Prashanth,

Unless there's a good reason, the Jammy/Focal version of openssh will
stay the version it is. Likely, any changes to this package will be
specific commits which will have to go through the SRU process[0] if it
can be justified.

Is there a reason you are trying to test the latest openssl on Jammy?
Unless something happens, the openssl version in Jammy should remain the
version it is, excluding SRUs which are mentioned above, so Jammy
shouldn't need to support OpenSSL 3.1.X.

[0] - https://wiki.ubuntu.com/StableReleaseUpdates

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

Title:
  Requesting Ubuntu package manager to release openssh updates to focal
  and jammy

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  We're are unable to test OpenSSL 3.1 versions on Ubuntu 22.04 and
  20.04 machines because the machine gets bricked and loses SSH after
  installation of OpenSSL 3.1.2.

  This is because SSHD gets restarted when OpenSSL 3.1 gets installed.
  But it fails to come up and we lose SSH access to the box.

  Debug logging on SSHD shows the below error when it tries to start : 
  OpenSSL version mismatch. Built against 3020, you have 30100020

  After researching in online forums, it appears that this is an OpenSSH bug 
and it's been fixed in version 9.4p1 and 9.5p1 via this fix : 
  
https://github.com/openssh/openssh-portable/commit/b7afd8a4ecaca8afd3179b55e9db79c0ff210237

  However, it appears that only 8.9p1 version of openssh-client and
  openssh-server are available in Ubuntu packages.

  Requesting you to please release openssh versions 9.4p1 or 9.5p1 on
  Jammy and Focal which will help us move past this bug and start
  testing OpenSSL 3.1 for our use cases.

  
  Additional information about our environment:
  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  $ apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.9p1-3ubuntu0.4
Candidate: 1:8.9p1-3ubuntu0.4
Version table:
   *** 1:8.9p1-3ubuntu0.4 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:8.9p1-3ubuntu0.3 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:8.9p1-3 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2038561/+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 2038561] Re: Requesting Ubuntu package manager to release openssh updates to focal and jammy

[Mitchell Dzurick]

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

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

Title:
  Requesting Ubuntu package manager to release openssh updates to focal
  and jammy

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  We're are unable to test OpenSSL 3.1 versions on Ubuntu 22.04 and
  20.04 machines because the machine gets bricked and loses SSH after
  installation of OpenSSL 3.1.2.

  This is because SSHD gets restarted when OpenSSL 3.1 gets installed.
  But it fails to come up and we lose SSH access to the box.

  Debug logging on SSHD shows the below error when it tries to start : 
  OpenSSL version mismatch. Built against 3020, you have 30100020

  After researching in online forums, it appears that this is an OpenSSH bug 
and it's been fixed in version 9.4p1 and 9.5p1 via this fix : 
  
https://github.com/openssh/openssh-portable/commit/b7afd8a4ecaca8afd3179b55e9db79c0ff210237

  However, it appears that only 8.9p1 version of openssh-client and
  openssh-server are available in Ubuntu packages.

  Requesting you to please release openssh versions 9.4p1 or 9.5p1 on
  Jammy and Focal which will help us move past this bug and start
  testing OpenSSL 3.1 for our use cases.

  
  Additional information about our environment:
  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  $ apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.9p1-3ubuntu0.4
Candidate: 1:8.9p1-3ubuntu0.4
Version table:
   *** 1:8.9p1-3ubuntu0.4 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:8.9p1-3ubuntu0.3 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:8.9p1-3 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2038561/+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 2038561] Re: Requesting Ubuntu package manager to release openssh updates to focal and jammy

[Mitchell Dzurick]

Hello Prashanth, thank you very much for making this bug report and
making Ubuntu better!

Are you building openssl 3.1.2 or pulling the package from somewhere?

I tried installing a slightly newer version in a jammy LXC container and
see this error when trying to install libssl3 (a requirement to install
the newer openssl package).

I did:
$ lxc launch ubuntu:jammy j
$ lxc shell j
# apt install -y ssh
# wget 
http://ftp.us.debian.org/debian/pool/main/o/openssl/libssl3_3.1.3-1_amd64.deb
# dpkg -i libssl3_3.1.3-1_amd64.deb
dpkg: regarding libssl3_3.1.3-1_amd64.deb containing libssl3:amd64:
 libssl3:amd64 breaks openssh-client (<< 1:9.4p1)
  openssh-client (version 1:8.9p1-3ubuntu0.4) is present and installed.

dpkg: error processing archive libssl3_3.1.3-1_amd64.deb (--install):
 installing libssl3:amd64 would break openssh-client, and
 deconfiguration is not permitted (--auto-deconfigure might help)
Errors were encountered while processing:
 libssl3_3.1.3-1_amd64.deb

So the package is aware that this configuration will not work.


FWIW I tried adding the patch you mentioned into openssh, and it builds fine, 
but one of the tests now fails - 
https://launchpad.net/~mitchdz/+archive/ubuntu/lp2038561-openssh-version-mismatch/+packages

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

Title:
  Requesting Ubuntu package manager to release openssh updates to focal
  and jammy

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  We're are unable to test OpenSSL 3.1 versions on Ubuntu 22.04 and
  20.04 machines because the machine gets bricked and loses SSH after
  installation of OpenSSL 3.1.2.

  This is because SSHD gets restarted when OpenSSL 3.1 gets installed.
  But it fails to come up and we lose SSH access to the box.

  Debug logging on SSHD shows the below error when it tries to start : 
  OpenSSL version mismatch. Built against 3020, you have 30100020

  After researching in online forums, it appears that this is an OpenSSH bug 
and it's been fixed in version 9.4p1 and 9.5p1 via this fix : 
  
https://github.com/openssh/openssh-portable/commit/b7afd8a4ecaca8afd3179b55e9db79c0ff210237

  However, it appears that only 8.9p1 version of openssh-client and
  openssh-server are available in Ubuntu packages.

  Requesting you to please release openssh versions 9.4p1 or 9.5p1 on
  Jammy and Focal which will help us move past this bug and start
  testing OpenSSL 3.1 for our use cases.

  
  Additional information about our environment:
  $ lsb_release -rd
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  $ apt-cache policy openssh-server
  openssh-server:
Installed: 1:8.9p1-3ubuntu0.4
Candidate: 1:8.9p1-3ubuntu0.4
Version table:
   *** 1:8.9p1-3ubuntu0.4 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   1:8.9p1-3ubuntu0.3 500
  500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
   1:8.9p1-3 500
  500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 
Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2038561/+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 2031340] Re: slic3r-prusa autopkgtest flaky

[Mitchell Dzurick]

Just adding that I tried rebuilding the package and tests are still
failing 2.6.1+dfsg-3

https://launchpad.net/~mitchdz/+archive/ubuntu/slic3r-prusa-
mantic/+builds?build_text=_state=all

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

Title:
  slic3r-prusa autopkgtest flaky

Status in fontconfig package in Ubuntu:
  Fix Released
Status in gmp package in Ubuntu:
  Fix Released
Status in nlopt package in Ubuntu:
  Fix Released
Status in slic3r-prusa package in Ubuntu:
  New

Bug description:
  autopkgtest was added to slic3r-prusa as late as last April. They have
  never let version 2.6.0 of slic3r-prusa migrate to Debian testing, and
  seemingly need more work. slic3r-prusa 2.6.0+dfsg-2 was uploaded to
  unstable on July 27 but hasn't migrated to testing yet due to failing
  autopkgtest.

  In Ubuntu the flaky tests currently prevent fontconfig and nlopt (in
  addition to slic3r-prusa itself) from migrating to mantic-release.
  Probably some kind of hint is motivated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/2031340/+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 2002043] Re: Python extension modules get built using wrong compiler flags with python2

[Mitchell Dzurick]

Hi Nafees, I'll be looking into this bug. Planning to have some more
updates next week.

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

Title:
  Python extension modules get built using wrong compiler flags with
  python2

Status in python2.7 package in Ubuntu:
  In Progress
Status in python2.7 source package in Bionic:
  Won't Fix
Status in python2.7 source package in Focal:
  Won't Fix
Status in python2.7 source package in Jammy:
  Won't Fix
Status in python2.7 source package in Kinetic:
  Won't Fix
Status in python2.7 source package in Lunar:
  Won't Fix
Status in python2.7 source package in Mantic:
  Won't Fix

Bug description:
  Compiling a Python extension using Python2 (Python 2.7.18) is making
  use of wrong compiler flags, hence dropping required optimizations
  when required. This is happening only when python2 is installed from
  Ubuntu's repositories. By default, Python's distutils module uses
  compiler and linker flags used to compile Python itself to be used to
  compile extensions.

  Steps to reproduce:
  1) On Ubuntu 20.04, install python2 using apt package manager.
  2) After successful installation, verify the CFLAGS variable from sysconfig 
module. On my machine, the output is 

  Python 2.7.18 (default, Jul  1 2022, 12:27:04)
  [GCC 9.4.0] on linux2
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import sysconfig
  >>> sysconfig.get_config_var('CFLAGS')
  '-fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes 
-Wdate-time -D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security  '

  3) Build a test extension module using python2 and verify the compilation 
flags. 
  python2 setup.py build_ext --inplace

  Output from below command is not matching with our expected above CFLAGS. 
  aarch64-linux-gnu-gcc -pthread -fno-strict-aliasing -Wdate-time 
-D_FORTIFY_SOURCE=2 -g 
-fdebug-prefix-map=/build/python2.7-vvQ8AI/python2.7-2.7.18=. 
-fstack-protector-strong -Wformat -Werror=format-security -fPIC 
-I/usr/include/python2.7 -c testmodule.c -o 
build/temp.linux-aarch64-2.7/testmodule.o

  
  On further investigation, it looks like Ubuntu's specific patch applied on 
libpython2.7-stdlib package is altering the original upstream implementation of 
distutils/sysconfig.py code.

  Package - https://packages.ubuntu.com/focal/libpython2.7-stdlib
  Patch - 
http://archive.ubuntu.com/ubuntu/pool/universe/p/python2.7/python2.7_2.7.18-1~20.04.3.diff.gz

  Below is the code block which is causing the issue, where the presence of 
configure_cflags is modifying cflags. This code is result of ubuntu's patch and 
doesn't come directly from upstream python implementation.
  File - /usr/lib/python2.7/distutils/sysconfig.py
  Part of code block:
  elif configure_cflags:
  cflags = ' '.join(str(x) for x in (basecflags, configure_cflags, 
extra_cflags) if x)
  ldshared = ldshared + ' ' + configure_cflags

  
  I don't see problem on Python3 though we have extra code added from patch 
there as well. Patch used on python3, is not modifying the cflags completely 
and instead appending new flags to cflags.
  On python3 (tested on Ubuntu 20.04)
  File - /usr/lib/python3.8/distutils/sysconfig.py
  Part of code block which doesn't alter cflags completely
  elif configure_cflags:
  cflags = cflags + ' ' + configure_cflags
  ldshared = ldshared + ' ' + configure_cflags

  
  Request to update the python2 patch to behave similar to what is been done on 
python3.

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