date:20230711

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

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

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

Title:
  Crashes with segmentation fault operating asn1_meth_table

Status in openssl package in Ubuntu:
  Expired

Bug description:
  Trying to update Server Access Certificate with DigiDoc client for
  Estonian ID cards crashes implicating an OpenSSL problem.

  The problem has been there from OpenSSL 1.0.0, but does not happen
  using OpenSSL 0.9.8.

  Debugging with Valgrind gives variety of:

  Invalid free() / delete / delete[] / realloc()
  Invalid write of size n
  Invalid read of size n

  The context is:

  ==5779==at 0x402B06C: free (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==5779==by 0x6A818C9: CRYPTO_free (mem.c:393)
  ==5779==by 0x6AEB82A: engine_free_util (eng_lib.c:136)
  ==5779==by 0x6AEC798: engine_unlocked_finish (eng_init.c:112)
  ==5779==by 0x6AED607: engine_table_register (eng_table.c:178)
  ==5779==by 0x6AEFC7A: ENGINE_set_default_pkey_asn1_meths (tb_asnmth.c:106)
  ==5779==by 0x6AEE3B7: ENGINE_set_default (eng_fat.c:96)

  I'm currently testing it on Ubuntu 12.04 beta 2 with

  * opensc 0.12.1-1ubuntu4
  * libssl1.0.0 1.0.1-2ubuntu4
  * qdigidoc 0.4.0-0ubuntu4

  The problem has been also tested on Oneiric and discussed in some
  length at: http://code.google.com/p/esteid/issues/detail?id=168

  I attach also some debug logs.

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


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

[Touch-packages] [Bug 1260230] Re: Memory leak in libcrypto.so\libssl.so

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

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

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

Title:
  Memory leak in libcrypto.so\libssl.so

Status in openssl package in Ubuntu:
  Expired

Bug description:
  I've found a bug in openssl 1.0.1-4ubuntu5.10. Was trying to use
  libpq\libmysql.so to connect to database and did not specify sslmode
  so it used ssl to connect to database, when i've checked with valgrind
  i've detected some memory leak:

  ==25346== Memcheck, a memory error detector
  ==25346== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
  ==25346== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
  ==25346== Command: ./test
  ==25346==
  ==25346==
  ==25346== HEAP SUMMARY:
  ==25346== in use at exit: 81,152 bytes in 2,769 blocks
  ==25346==   total heap usage: 4,388 allocs, 1,619 frees, 281,833 bytes 
allocated
  ==25346==
  ==25346== 160 (40 direct, 120 indirect) bytes in 1 blocks are definitely lost 
in loss record 229 of 279
  ==25346==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==25346==by 0x416E84E: nss_parse_service_list (nsswitch.c:678)
  ==25346==by 0x416EFC9: __nss_database_lookup (nsswitch.c:175)
  ==25346==by 0x4EB6168: ???
  ==25346==by 0x4EB7B5C: ???
  ==25346==by 0x4125FA6: getpwuid_r@@GLIBC_2.1.2 (getXXbyYY_r.c:256)
  ==25346==by 0x405F691: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404C6BD: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404D06A: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404EC4A: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404EF2F: ??? (in /usr/lib/libpq.so.5.4)
  ==25346==by 0x404F31E: PQconnectStart (in /usr/lib/libpq.so.5.4)
  ==25346==
  ==25346== LEAK SUMMARY:
  ==25346==definitely lost: 40 bytes in 1 blocks
  ==25346==indirectly lost: 120 bytes in 10 blocks
  ==25346==  possibly lost: 0 bytes in 0 blocks
  ==25346==still reachable: 80,992 bytes in 2,758 blocks
  ==25346== suppressed: 0 bytes in 0 blocks
  ==25346== Reachable blocks (those to which a pointer was found) are not shown.
  ==25346== To see them, rerun with: --leak-check=full --show-reachable=yes
  ==25346==
  ==25346== For counts of detected and suppressed errors, rerun with: -v
  ==25346== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)


  with sslmode=disable i see this:
  ==28708== Memcheck, a memory error detector
  ==28708== Copyright (C) 2002-2011, and GNU GPL'd, by Julian Seward et al.
  ==28708== Using Valgrind-3.7.0 and LibVEX; rerun with -h for copyright info
  ==28708== Command: ./test
  ==28708==
  ==28708==
  ==28708== HEAP SUMMARY:
  ==28708== in use at exit: 160 bytes in 11 blocks
  ==28708==   total heap usage: 138 allocs, 127 frees, 46,314 bytes allocated
  ==28708==
  ==28708== 160 (40 direct, 120 indirect) bytes in 1 blocks are definitely lost 
in loss record 11 of 11
  ==28708==at 0x402BE68: malloc (in 
/usr/lib/valgrind/vgpreload_memcheck-x86-linux.so)
  ==28708==by 0x416E84E: nss_parse_service_list (nsswitch.c:678)
  ==28708==by 0x416EFC9: __nss_database_lookup (nsswitch.c:175)
  ==28708==by 0x4EB6168: ???
  ==28708==by 0x4EB7B5C: ???
  ==28708==by 0x4125FA6: getpwuid_r@@GLIBC_2.1.2 (getXXbyYY_r.c:256)
  ==28708==by 0x405F691: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404C6BD: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404D06A: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404EC4A: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404EF2F: ??? (in /usr/lib/libpq.so.5.4)
  ==28708==by 0x404F31E: PQconnectStart (in /usr/lib/libpq.so.5.4)
  ==28708==
  ==28708== LEAK SUMMARY:
  ==28708==definitely lost: 40 bytes in 1 blocks
  ==28708==indirectly lost: 120 bytes in 10 blocks
  ==28708==  possibly lost: 0 bytes in 0 blocks
  ==28708==still reachable: 0 bytes in 0 blocks
  ==28708== suppressed: 0 bytes in 0 blocks
  ==28708==
  ==28708== For counts of detected and suppressed errors, rerun with: -v
  ==28708== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)

  also test openssl program(attached) have a leak 47700 bytes

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


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

[Touch-packages] [Bug 1320094] Re: segfault from aes ccm encryption after RSA key generation and EVP_PKEY_assign_RSA()

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

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

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

Title:
  segfault from aes ccm encryption after RSA key generation and
  EVP_PKEY_assign_RSA()

Status in openssl package in Ubuntu:
  Expired

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

  2) apt-cache policy libssl1.0.0
  libssl1.0.0:
Installed: 1.0.1-4ubuntu5.13
Candidate: 1.0.1-4ubuntu5.13
Version table:
   *** 1.0.1-4ubuntu5.13 0
  500 http://be.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ precise-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.1-4ubuntu3 0
  500 http://be.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

  For the sourcecode that triggers the segfault see the attachement.

  3/4)

  I was testing aes ccm encryption when I stumbled over a segmentation fault.
  I was able to reproduce this error using code from the openssl demos  at 
openssl.org.

  I started with demos/evp/aesccm.c and added rsa key generation as used in 
'demos/tunala/cb.c' and convert this rsa key into an EVP_PKEY key as done in 
'demos/selfsign.c'. Then I added this rsa key generation function in front of 
the aes ccm encryption and decryption.
  Finally, a for loop repeatedly performs the keygeneration, aes ccm encryption 
and aes ccm decryption. This eventually results in a segmentation fault during 
aes ccm encryption (see gdb output below) on a x64 Ubuntu 12.04 with latest 
openssl version as provided by ubuntu package system (1.0.1-4ubuntu5.13).

  Note that the segfault only occurs if the rsa key is assigned to an EVP_PKEY. 
Otherwise, if only the RSA key is generated, the segfault does not occur.
  Furthermore, the segfault does not occur if I use the standard openssl 
libraries from openssl.org.

  When encountering this error in my own code I could observe that the error 
occurred more often on a machine that only runs the standard processes and is 
accessed remotely by ssh, compared to a local workstation with running 
webbrowser, development IDE, etc., where the error occurred rather seldom. 
Hence, I have the feeling that this could be related to too little
  randomness for the RNG, but I do not have any idea how to debug this.

  
  === gdb backtrace ===

  (gdb) run
  Starting program: /home/hiller/openssl_bug/aesccm
  AES CCM Encrypt:
  Plaintext:
   - c8 d2 75 f9 19 e1 7d 7f-e6 9c 2a 1f 58 93 9d fe   ..u...}...*.X...
  0010 - 4d 40 37 91 b5 df 13 10-  M@7.
  Ciphertext:
   - 8a 0f 3d 82 29 e4 8e 74-87 fd 95 a2 8a d3 92 c8   ..=.)..t
  0010 - 0b 36 81 d4 fb c7 bb fd-  .6..
  Tag:
   - 2d d6 ef 1c 45 d4 cc b7-23 dc 07 44 14 db 50 6d   -...E...#..D..Pm
  AES CCM Derypt:
  Ciphertext:
   - 8a 0f 3d 82 29 e4 8e 74-87 fd 95 a2 8a d3 92 c8   ..=.)..t
  0010 - 0b 36 81 d4 fb c7 bb fd-  .6..
  Plaintext:
   - c8 d2 75 f9 19 e1 7d 7f-e6 9c 2a 1f 58 93 9d fe   ..u...}...*.X...
  0010 - 4d 40 37 91 b5 df 13 10-  M@7.
  AES CCM Encrypt:
  [ the output above is repeated several times ]

  Program received signal SIGSEGV, Segmentation fault.
  0x0090 in ?? ()
  (gdb) backtrace
  #0  0x0090 in ?? ()
  #1  0x77a948d4 in CRYPTO_ccm128_encrypt_ccm64 (ctx=0x604fd0,
  inp=0x401240
  "\310\322u\371\031\341}\177\346\234*\037X\223\235\376M@7\221\265\337\023\020",

  out=0x7fffe0c0
  "\310\322u\371\031\341}\177\346\234*\037X\223\235\376M@7\221\265\337\023\020",
  len=24, stream=) at ccm128.c:354
  #2  0x77af1688 in aes_ccm_cipher (ctx=0x604e10,
  out=0x7fffe0c0
  "\310\322u\371\031\341}\177\346\234*\037X\223\235\376M@7\221\265\337\023\020",

  in=0x401240
  "\310\322u\371\031\341}\177\346\234*\037X\223\235\376M@7\221\265\337\023\020",
  len=24) at e_aes.c:1275
  #3  0x77aedaa2 in EVP_EncryptUpdate (ctx=0x604e10,
  out=0x7fffe0c0
  "\310\322u\371\031\341}\177\346\234*\037X\223\235\376M@7\221\265\337\023\020",
  outl=0x7fffe0bc,
  in=0x401240
  "\310\322u\371\031\341}\177\346\234*\037X\223\235\376M@7\221\265\337\023\020",
  inl=) at evp_enc.c:314
  #4  0x00400e37 in aes_ccm_encrypt () at aesccm.c:106
  #5  0x004010ce in main (argc=1, argv=0x7fffe5e8) at aesccm.c:161

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


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

[Touch-packages] [Bug 1441461] Re: openssl verify fails with "certificate signature failure"

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

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

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

Title:
  openssl verify fails with "certificate signature failure"

Status in openssl package in Ubuntu:
  Expired

Bug description:
  I have a intermediate certificate signed by my own CA, which works fine on 
other systems.
  but openssl (1.0.1f-1ubuntu2.11) installed with apt-get will always fails 
with "certificate signature failure"

  but openssl binary compiled myself with the same version of code
  (1.0.1f), works.

  so i wonder if this is a bug of openssl?

  certificate details and version info is at
  https://gist.github.com/bearice/e2dd5d4245472e1b3992

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


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

[Touch-packages] [Bug 1612711] Re: TLS negotiation fails

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

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

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

Title:
  TLS negotiation fails

Status in openssl package in Ubuntu:
  Expired

Bug description:
  This seems like a duplicate of #965371, however that is marked fixed,
  so I don't know.

  I'm running 16.04.1.  I'm setting up OpenLDAP with TLS.  I've followed
  the instructions at https://help.ubuntu.com/lts/serverguide/openldap-
  server.html#openldap-tls, and test with the command openssl s_client
  -connect my.server.com:389 -showcerts and I get the error:

  140668035487384:error:140790E5:SSL routines:ssl23_write:ssl handshake
  failure:s23_lib.c:177

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


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

[Touch-packages] [Bug 1865558] Re: gdm-session-worker segmentation fault when checking online crl from smartcard authentication

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

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

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

Title:
  gdm-session-worker segmentation fault when checking online crl from
  smartcard authentication

Status in openssl package in Ubuntu:
  Expired

Bug description:
  Error occurs after pin for the PIV card is entered into the GNOME login GUI.
  Error in /var/log/messages:
  gdm-session-wor[23783]: segfault at 0 ip 7f3e851589ab sp 7ffd2e747300 
error 6 in libcrypto.so.1.1[7f3e84f6a000+29b000]

  Remove "crl_online" from cert_policy in
  /etc/pam_pkcs11/pam_pkcs11.conf and there is no segmentation fault.

  openssl 1.1.1-1ubuntu2.1~18.04.5
  opensc 0.17.0-3
  libpam-pkcs11 0.6.9-2build2

  Using opensc pkcs11_module.
  Smartcard has a CRL URL set with FQDN and the prefix of the URL is http://.
  This did not exist in Ubuntu 16. This started in 18.04 (first release) and 
has existed in all minor versions of 18.

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


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

[Touch-packages] [Bug 1991606] Autopkgtest regression report (gpgme1.0/1.13.1-7ubuntu2.1)

2023-07-11 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted gpgme1.0 (1.13.1-7ubuntu2.1) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

ros-ros-comm/blacklisted (s390x)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#gpgme1.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in dput package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  Fix Released
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in dput source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  Fix Committed
Status in dput source package in Focal:
  Fix Committed
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  Fix Committed
Status in python-debian source package in Focal:
  Fix Committed
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  Fix Released
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  Fix Committed
Status in dput source package in Jammy:
  Fix Committed
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  Fix Committed
Status in python-debian source package in Jammy:
  Fix Committed
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in dput source package in Kinetic:
  Fix Committed
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  Fix Released
Status in python-debian source package in Kinetic:
  Fix Committed
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New
Status in dput source package in Lunar:
  Fix Committed

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(se

[Touch-packages] [Bug 2019212] Re: Backport packages for 22.04.3 HWE stack

2023-07-11 Thread Harm van Bakel

Actually, looks like I was wrong. After reverting the proposed
repository, reinstalling only the new mesa and mesa-amber packages, and
rebooting, color management is working properly. The breakage must have
been due to another package update.

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

Title:
  Backport packages for 22.04.3 HWE stack

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

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

  mesa
  - new major release (23.0.4)

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

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

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

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

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


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

[Touch-packages] [Bug 2019212] Re: Backport packages for 22.04.3 HWE stack

2023-07-11 Thread Harm van Bakel

After testing packages from the proposed repository for the pending
22.04.3 point release I noticed that color management profiles are no
longer being applied in an Xorg session. I suspect this may be related
to the mesa packages as I noticed the breakage when rebooting shortly
after updating to the 23.0.4 version, though it's possible that there
were other proposed packages installed at the same time. Re-applying the
icc profile or e.g. switching to the red/green 'inverted' test icc
profile no longer have any effect after the update.

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

Title:
  Backport packages for 22.04.3 HWE stack

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

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

  mesa
  - new major release (23.0.4)

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

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

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

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

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


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

[Touch-packages] [Bug 1983618] Re: New upstream microrelease 2.5.13

** Tags removed: needs-mre-backport

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

Title:
  New upstream microrelease 2.5.13

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

   * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.13.

  This update includes bugfixes only following the SRU policy exception
  defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

  [ Major Changes ]

   * See the list of bugs fixed in this release here:

  https://lists.openldap.org/hyperkitty/list/openldap-
  annou...@openldap.org/thread/3PLJDVP7QWTRFHC2GPQTGBLEQFCBUZZ2/

  [ Test Plan ]

   * Upstream gitlab pipeline results:
  https://git.openldap.org/openldap/openldap/-/pipelines/4504

   * Upstream "call for testing":
  https://lists.openldap.org/hyperkitty/list/openldap-
  techni...@openldap.org/thread/RXOSXVLKTIDM4XJUA5EZZ42677JXRHYN/

   * As described in the MRE wiki page for OpenLDAP, the test plan is to
  build the package in bileto and make sure that (1) all build-time
  tests pass and (2) all autopkgtest runs (from reverse dependencies)
  also pass.

   * Build log (amd64) confirming that the build-time testsuite has been
  performed and completed successfully: https://launchpad.net/~ci-train-
  ppa-service/+archive/ubuntu/4887/+build/24250107

   * Bileto ticket: https://bileto.ubuntu.com/#/ticket/4895

  [ Where problems could occur ]

   * Upstream tests are always executed during build-time. There are
  many reverse dependencies whose dep8 tests depend on OpenLDAP so the
  coverage is good. Nevertheless, there is always a risk for something
  to break since we are dealing with a microrelease upgrade. Whenever a
  test failure is detected, we will be on top of it and make sure it
  doesn't affect existing users.

  [ Other Info ]

   * This is a reoccurring MRE. See below for links to previous OpenLDAP
  MREs.

   * CVEs fixed by this release:
     - None.

  Current versions in supported releases that got updates:
   openldap | 2.5.12+dfsg-0ubuntu0.22.04.1 | jammy-updates   | source

  Special cases:
  - None.

  Previous MREs for OpenLDAP:
  - https://pad.lv/1977627

  As usual we test and prep from the PPA and then push through
  SRU/Security as applicable.

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


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

[Touch-packages] [Bug 2027079] Re: New upstream microrelease 2.5.15

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

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/446555

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

Title:
   New upstream microrelease 2.5.15

Status in openldap package in Ubuntu:
  Invalid
Status in openldap source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

   * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.15.

  This update includes bugfixes only following the SRU policy exception
  defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

  [ Major Changes ]

   * See the list of bugs fixed in this release here:

  https://lists.openldap.org/hyperkitty/list/openldap-
  annou...@openldap.org/thread/ZQC6MWMJMETDFWV3UHDKESBFPHHTNO5S/

  [ Test Plan ]

   * Upstream gitlab pipeline results:
  
https://git.openldap.org/openldap/openldap/-/commit/d0fbbc3599148e1033218ec097bf5ab5f6236c76/pipelines?ref=OPENLDAP_REL_ENG_2_5_15

   * Upstream "call for testing":

  https://lists.openldap.org/hyperkitty/list/openldap-
  techni...@openldap.org/message/HUNFQO6GJR7CCJAYKMTRXE44ZPHBKKMD/

   * As described in the MRE wiki page for OpenLDAP, the test plan is to
  build the package in a PPA and make sure that (1) all build-time tests
  pass and (2) all autopkgtest runs (from reverse dependencies) also
  pass.

   * Build log (amd64) confirming that the build-time testsuite has been 
performed and completed successfully:
    - 
https://launchpadlibrarian.net/676793029/buildlog_ubuntu-jammy-amd64.openldap_2.5.15+dfsg-0ubuntu0.22.04.1_BUILDING.txt.gz

  [ Where problems could occur ]

   * Upstream tests are always executed during build-time. There are
  many reverse dependencies whose dep8 tests depend on OpenLDAP so the
  coverage is good. Nevertheless, there is always a risk for something
  to break since we are dealing with a microrelease upgrade. Whenever a
  test failure is detected, we will be on top of it and make sure it
  doesn't affect existing users.

  [ Other Info ]

   * This is a reoccurring MRE. See below for links to previous OpenLDAP
  MREs.

   * CVEs fixed by this release:
     - None.

  Current versions in supported releases that got updates:
   openldap | 2.5.14+dfsg-0ubuntu0.22.04.2 | jammy-updates   | source

  Special cases:
  - None.

  Previous MREs for OpenLDAP:
  - https://pad.lv/1977627
  - https://pad.lv/1983618
  - https://pad.lv/2007625

  As usual we test and prep from the PPA and then push through
  SRU/Security as applicable.

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


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

Re: [Touch-packages] [Bug 2024546] Re: Netplan not bringing up IPv6 address when dhcp6: true specified

2023-07-11 Thread Philipp Kern

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

On 2023-07-10 15:38, Lukas Märdian wrote:
> This seems to be a more generic issue with DHCP client vs Oracle OCI 
> and
> unrelated to Netplan:
> 
> https://community.oracle.com/customerconnect/discussion/687610/oci-
> ipv6-address-not-assigned-to-oci-ubuntu-instance-by-dhcp

At least for systemd-networkd I fixed the issue in 
https://github.com/systemd/systemd/pull/28138.

Kind regards
Philipp Kern

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

Title:
  DHCP not bringing up IPv6 address when dhcp6: true specified

Status in netplan:
  Invalid
Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  I have a netplan configuration with dhcp6: true specified for my
  network interface, however no IPv6 address comes up.

  dhclient -6 brings the address up without issue, proving that the DHCP
  server is responding.

  So why isn't Netplan configuring the IP address?

  network:
  version: 2
  ethernets:
  enp0s6:
  dhcp4: true
  dhcp6: true
  match:
  macaddress: 02:00:17:xx:xx:xx
  set-name: enp0s6

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2024546/+subscriptions


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

[Touch-packages] [Bug 2027079] Re: New upstream microrelease 2.5.15

** Description changed:

[ Impact ]

- * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.15.
+ * MRE for the latest stable OpenLDAP 2.5.x release, 2.5.15.

This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

[ Major Changes ]

- * See the list of bugs fixed in this release here:
+ * See the list of bugs fixed in this release here:

https://lists.openldap.org/hyperkitty/list/openldap-
annou...@openldap.org/thread/ZQC6MWMJMETDFWV3UHDKESBFPHHTNO5S/

[ Test Plan ]

- * Upstream gitlab pipeline results:
+ * Upstream gitlab pipeline results:

https://git.openldap.org/openldap/openldap/-/commit/d0fbbc3599148e1033218ec097bf5ab5f6236c76/pipelines?ref=OPENLDAP_REL_ENG_2_5_15

- * Upstream "call for testing":
+ * Upstream "call for testing":

https://lists.openldap.org/hyperkitty/list/openldap-
techni...@openldap.org/message/HUNFQO6GJR7CCJAYKMTRXE44ZPHBKKMD/

- * As described in the MRE wiki page for OpenLDAP, the test plan is to
+ * As described in the MRE wiki page for OpenLDAP, the test plan is to
build the package in a PPA and make sure that (1) all build-time tests
pass and (2) all autopkgtest runs (from reverse dependencies) also pass.

- * Build log (amd64) confirming that the build-time testsuite has been
performed and completed successfully:
- - TBD
+ * Build log (amd64) confirming that the build-time testsuite has been
performed and completed successfully:
+ -
https://launchpadlibrarian.net/676793029/buildlog_ubuntu-jammy-amd64.openldap_2.5.15+dfsg-0ubuntu0.22.04.1_BUILDING.txt.gz

[ Where problems could occur ]

- * Upstream tests are always executed during build-time. There are many
+ * Upstream tests are always executed during build-time. There are many
reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage
is good. Nevertheless, there is always a risk for something to break
since we are dealing with a microrelease upgrade. Whenever a test
failure is detected, we will be on top of it and make sure it doesn't
affect existing users.

[ Other Info ]

- * This is a reoccurring MRE. See below for links to previous OpenLDAP
+ * This is a reoccurring MRE. See below for links to previous OpenLDAP
MREs.

- * CVEs fixed by this release:
-- None.
+ * CVEs fixed by this release:
+ - None.

Special cases:
- None.

Previous MREs for OpenLDAP:
- https://pad.lv/1977627
- https://pad.lv/1983618
- https://pad.lv/2007625

As usual we test and prep from the PPA and then push through
SRU/Security as applicable.

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

Title:
New upstream microrelease 2.5.15

Status in openldap package in Ubuntu:
New
Status in openldap source package in Jammy:
In Progress

Bug description:
[ Impact ]

* MRE for the latest stable OpenLDAP 2.5.x release, 2.5.15.

This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

[ Major Changes ]

* See the list of bugs fixed in this release here:

https://lists.openldap.org/hyperkitty/list/openldap-
annou...@openldap.org/thread/ZQC6MWMJMETDFWV3UHDKESBFPHHTNO5S/

[ Test Plan ]

* Upstream gitlab pipeline results:

https://git.openldap.org/openldap/openldap/-/commit/d0fbbc3599148e1033218ec097bf5ab5f6236c76/pipelines?ref=OPENLDAP_REL_ENG_2_5_15

* Upstream "call for testing":

https://lists.openldap.org/hyperkitty/list/openldap-
techni...@openldap.org/message/HUNFQO6GJR7CCJAYKMTRXE44ZPHBKKMD/

* As described in the MRE wiki page for OpenLDAP, the test plan is to
build the package in a PPA and make sure that (1) all build-time tests
pass and (2) all autopkgtest runs (from reverse dependencies) also
pass.

* Build log (amd64) confirming that the build-time testsuite has been
performed and completed successfully:
-
https://launchpadlibrarian.net/676793029/buildlog_ubuntu-jammy-amd64.openldap_2.5.15+dfsg-0ubuntu0.22.04.1_BUILDING.txt.gz

[ Where problems could occur ]

* Upstream tests are always executed during build-time. There are
many reverse dependencies whose dep8 tests depend on OpenLDAP so the
coverage is good. Nevertheless, there is always a risk for something
to break since we are dealing with a microrelease upgrade. Whenever a
test failure is detected, we will be on top of it and make sure it
doesn't affect existing users.

[ Other Info ]

* This is a reoccurring MRE. See below for links to previous OpenLDAP
MREs.

* CVEs fixed by this release:
- None.

Current

[Touch-packages] [Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build

2023-07-11 Thread Sebastien Bacher

** Changed in: glib2.0 (Ubuntu)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => High

** Changed in: glib2.0 (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  glib2.0 (2.77.0 ) breaks Netplan build

Status in glib2.0 package in Ubuntu:
  In Progress

Bug description:
  Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
  mantic-proposed.

  See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3

  When I downgrade glib in my sbuild environment, everything works as
  expected:

  $ apt install libglib2.0-0=2.76.3-1ubuntu1
  libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1
  libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1

  The build also works fine in Debian unstable, which is using glib2.0
  2.74.6-2.

  Netplan is using plenty of GLib's keyfile functions
  (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to
  producing a different output with this newer release (some strange
  line breaks injected in the middle of a keyfile).

  
  Example keyfile from the test_wifis.test_wifi_wowlan test, that should be 
generated by Netplan and the way it fails:

  Expected output:
  ```
  [connection]
  id=netplan-wl0-homenet
  type=wifi
  interface-name=wl0

  [wifi]
  wake-on-wlan=330
  ssid=homenet
  mode=infrastructure

  [ipv4]
  method=link-local

  [ipv6]
  method=ignore
  ```

  Failure:
  ```
  E   AssertionError: '[con[88 
chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 
chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n'
  E [connection]
  E id=netplan-wl0-homenet
  E type=wifi
  E interface-name=wl0
  E 
  E [wifi]
  E wake-on-wlan=330
  E   - 
  E ssid=homenet
  E mode=infrastructure
  E   + 
  E [ipv4]
  E method=link-local
  E 
  E [ipv6]
  E method=ignore
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2026826/+subscriptions


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

[Touch-packages] [Bug 2027079] [NEW] New upstream microrelease 2.5.15

Public bug reported:

[ Impact ]

* MRE for the latest stable OpenLDAP 2.5.x release, 2.5.15.

This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

[ Major Changes ]

* See the list of bugs fixed in this release here:

https://lists.openldap.org/hyperkitty/list/openldap-
annou...@openldap.org/thread/ZQC6MWMJMETDFWV3UHDKESBFPHHTNO5S/

[ Test Plan ]

* Upstream gitlab pipeline results:
https://git.openldap.org/openldap/openldap/-/commit/d0fbbc3599148e1033218ec097bf5ab5f6236c76/pipelines?ref=OPENLDAP_REL_ENG_2_5_15

* Upstream "call for testing":

https://lists.openldap.org/hyperkitty/list/openldap-
techni...@openldap.org/message/HUNFQO6GJR7CCJAYKMTRXE44ZPHBKKMD/

* Build log (amd64) confirming that the build-time testsuite has been
performed and completed successfully:
- TBD

[ Where problems could occur ]

* Upstream tests are always executed during build-time. There are many
reverse dependencies whose dep8 tests depend on OpenLDAP so the coverage
is good. Nevertheless, there is always a risk for something to break
since we are dealing with a microrelease upgrade. Whenever a test
failure is detected, we will be on top of it and make sure it doesn't
affect existing users.

[ Other Info ]

* This is a reoccurring MRE. See below for links to previous OpenLDAP
MREs.

* CVEs fixed by this release:
- None.

Current versions in supported releases that got updates:
openldap | 2.5.14+dfsg-0ubuntu0.22.04.2 | jammy-updates | source

Special cases:
- None.

Previous MREs for OpenLDAP:
- https://pad.lv/1977627
- https://pad.lv/1983618
- https://pad.lv/2007625

As usual we test and prep from the PPA and then push through
SRU/Security as applicable.

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

** Affects: openldap (Ubuntu Jammy)
Importance: Undecided
Assignee: Sergio Durigan Junior (sergiodj)
Status: In Progress

** Tags: server-todo

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

** Changed in: openldap (Ubuntu Jammy)
Assignee: (unassigned) => Sergio Durigan Junior (sergiodj)

** Tags added: server-todo

** Changed in: openldap (Ubuntu Jammy)
Status: New => In Progress

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

Title:
New upstream microrelease 2.5.15

Status in openldap package in Ubuntu:
New
Status in openldap source package in Jammy:
In Progress

Bug description:
[ Impact ]

* MRE for the latest stable OpenLDAP 2.5.x release, 2.5.15.

This update includes bugfixes only following the SRU policy exception
defined at https://wiki.ubuntu.com/OpenLDAPUpdates.

[ Major Changes ]

* See the list of bugs fixed in this release here:

https://lists.openldap.org/hyperkitty/list/openldap-
annou...@openldap.org/thread/ZQC6MWMJMETDFWV3UHDKESBFPHHTNO5S/

[ Test Plan ]

* Upstream gitlab pipeline results:

https://git.openldap.org/openldap/openldap/-/commit/d0fbbc3599148e1033218ec097bf5ab5f6236c76/pipelines?ref=OPENLDAP_REL_ENG_2_5_15

* Upstream "call for testing":

https://lists.openldap.org/hyperkitty/list/openldap-
techni...@openldap.org/message/HUNFQO6GJR7CCJAYKMTRXE44ZPHBKKMD/

* Build log (amd64) confirming that the build-time testsuite has been
performed and completed successfully:
- TBD

[ Where problems could occur ]

[ Other Info ]

* This is a reoccurring MRE. See below for links to previous OpenLDAP
MREs.

* CVEs fixed by this release:
- None.

Current versions in supported releases that got updates:
openldap | 2.5.14+dfsg-0ubuntu0.22.04.2 | jammy-updates | source

Special cases:
- None.

Previous MREs for OpenLDAP:
- https://pad.lv/1977627
- https://pad.lv/1983618
- https://pad.lv/2007625

As usual we test and prep from the PPA and then push through
SRU/Security as applicable.

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

[Touch-packages] [Bug 2026199] Re: Please merge 3.137 into mantic

2023-07-11 Thread Dan Bungert

Uploaded, thanks!

** Changed in: adduser (Ubuntu)
 Assignee: Mateus Rodrigues de Morais (mateus-morais) => Dan Bungert 
(dbungert)

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

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

Title:
  Please merge 3.137 into mantic

Status in adduser package in Ubuntu:
  Fix Committed

Bug description:
  The upstream version 3.137 should be merged into mantic. The current
  version is 3.134ubuntu1.

  * PPA for review: 
https://launchpad.net/~mateus-morais/+archive/ubuntu/adduser-merge-lp2026199
  * Git rebase of Ubuntu delta available at: 
https://code.launchpad.net/~mateus-morais/ubuntu/+source/adduser/+git/adduser-devel/+ref/ubuntu/devel
- To be pushed to ubuntu/devel at 
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/adduser/+git/adduser

  Note: this is a tracking bug

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


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

[Touch-packages] [Bug 1958019]

2023-07-11 Thread chrisemke

Hello guys, have you seen this?
https://forums.lenovo.com/topic/findpost/2713/5210709/6004369?random=nZpbsgdmR0RbJdDLI7lLW8H0NabNneIv_1e738b0f207dd4082957db2fd078d035
Apparently there was some progress on the lenovo forum, they marked it as a 
solution so I decided to send the link here. I hope it helps

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

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

2023-07-11 Thread Dan Bungert

** Merge proposal unlinked:
   
https://code.launchpad.net/~dbungert/ubuntu-sponsoring/+git/ubuntu-sponsoring/+merge/446529

-- 
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:
  In Progress
Status in python2.7 source package in Jammy:
  In Progress
Status in python2.7 source package in Kinetic:
  In Progress
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 2023229] Re: Autopkgtest failure for tests-in-lxd

** Merge proposal linked:
   
https://code.launchpad.net/~enr0n/ubuntu/+source/systemd/+git/systemd/+merge/446548

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

Title:
  Autopkgtest failure for tests-in-lxd

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Kinetic:
  Triaged
Status in systemd source package in Lunar:
  Triaged
Status in systemd source package in Mantic:
  Triaged

Bug description:
  Autopackagetests on multiple Jammy kernels show the same failure on
  the test-in-lxd test

  Error: Aliases already exists: autopkgtest/ubuntu/jammy/amd64
  autopkgtest [16:33:58]: test tests-in-lxd: ---]
  autopkgtest [16:33:58]: test tests-in-lxd:  - - - - - - - - - - results - - - 
- - - - - - -
  tests-in-lxd FAIL non-zero exit status 1

  Where the error seems to be triggered by debian/tests/tests-in-lxd

  lxc publish systemd-lxc --alias $IMAGE

  
  To be determined if this a problem in the autopkgtest infrastructure or test 
bug.

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


-- 
Mailing list: https://launchpad.net/~touch-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

** Merge proposal linked:
   
https://code.launchpad.net/~dbungert/ubuntu-sponsoring/+git/ubuntu-sponsoring/+merge/446529

-- 
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:
  In Progress
Status in python2.7 source package in Jammy:
  In Progress
Status in python2.7 source package in Kinetic:
  In Progress
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 2002043] Re: Python extension modules get built using wrong compiler flags with python2

2023-07-11 Thread Dan Bungert

** Merge proposal unlinked:
   
https://code.launchpad.net/~dbungert/ubuntu-sponsoring/+git/ubuntu-sponsoring/+merge/446529

-- 
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:
  In Progress
Status in python2.7 source package in Jammy:
  In Progress
Status in python2.7 source package in Kinetic:
  In Progress
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 2026888] [NEW] Autopkgtest failing on s390x

2023-07-11 Thread Danilo Egea Gondolfo

Public bug reported:

Autopkgtests are consistently failing on s390x.

More specifically, the test 04-getroot-sssd is failing.

The reason is not evident because the stderr is being redirected to
/dev/null. After testing a PPA without the redirection, I was able to
see the error below:


ldap_sasl_interactive_bind: Can't contact LDAP server (-1)


The reason seems to be that the slapd daemon is not ready yet when the test 
calls ldapmodify.

Adding a simple "sleep", as already done in another place in the same
test, is enough to workaround the issue. Ideally it should try the
command again if it fails using some sort of exponential backoff.

A sleep-based workaround was proposed as part of
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2025655

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

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

Title:
  Autopkgtest failing on s390x

Status in sudo package in Ubuntu:
  New

Bug description:
  Autopkgtests are consistently failing on s390x.

  More specifically, the test 04-getroot-sssd is failing.

  The reason is not evident because the stderr is being redirected to
  /dev/null. After testing a PPA without the redirection, I was able to
  see the error below:

  
  ldap_sasl_interactive_bind: Can't contact LDAP server (-1)

  
  The reason seems to be that the slapd daemon is not ready yet when the test 
calls ldapmodify.

  Adding a simple "sleep", as already done in another place in the same
  test, is enough to workaround the issue. Ideally it should try the
  command again if it fails using some sort of exponential backoff.

  A sleep-based workaround was proposed as part of
  https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/2025655

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


-- 
Mailing list: https://launchpad.net/~touch-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

** Merge proposal linked:
   
https://code.launchpad.net/~dbungert/ubuntu-sponsoring/+git/ubuntu-sponsoring/+merge/446529

-- 
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:
  In Progress
Status in python2.7 source package in Jammy:
  In Progress
Status in python2.7 source package in Kinetic:
  In Progress
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 2026227] Re: Backport 4.0 ABI for AppArmor 3 in mantic

This bug was fixed in the package apparmor - 3.0.8-1ubuntu4

---
apparmor (3.0.8-1ubuntu4) mantic; urgency=medium

  * Backport 4.0 ABI from upstream (LP: #2026227)
- d/p/u/add-4.0-abi.patch

 -- Alex Murray   Thu, 06 Jul 2023 12:14:15
+0930

** Changed in: apparmor (Ubuntu Mantic)
   Status: New => Fix Released

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

Title:
  Backport 4.0 ABI for AppArmor 3 in mantic

Status in apparmor package in Ubuntu:
  Fix Released
Status in apparmor source package in Mantic:
  Fix Released

Bug description:
  To support the use of AppArmor policies that specify features like
  userns, add the new 4.0 ABI from upstream
  https://gitlab.com/apparmor/apparmor/-/merge_requests/1061.

  Note this should not be enabled by default (as the existing AppArmor
  profiles have not been updated to account for this) but it will allow
  easier testing of profiles that want to support this new ABI.

  Also note this ABI is identical to that provided by the kernel in
  mantic and lunar currently:

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Mantic Minotaur (development branch)
  Release:  23.10
  Codename: mantic
  # uname -a
  Linux sec-mantic-amd64 6.3.0-7-generic #7-Ubuntu SMP PREEMPT_DYNAMIC Thu Jun  
8 16:02:30 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
  # diff /etc/apparmor.d/abi/4.0 <(aa-features-abi -x)
  # md5sum /etc/apparmor.d/abi/4.0 <(aa-features-abi -x)
  f17b0a97806d733b5b884d8a1c2fea37  /etc/apparmor.d/abi/4.0
  f17b0a97806d733b5b884d8a1c2fea37  /dev/fd/63

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


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

[Touch-packages] [Bug 2026885] [NEW] nano is not available in Jammy i386

2023-07-11 Thread Ken Sharp

Public bug reported:

There is no i386 Nano package in Jammy. I used Nano all the time
including in chroots, which is where this reared its ugly head.

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


** Tags: focal i386 jammy kinetic lunar mantic

** Tags added: focal kinetic lunar mantic

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

Title:
  nano is not available in Jammy i386

Status in nano package in Ubuntu:
  New

Bug description:
  There is no i386 Nano package in Jammy. I used Nano all the time
  including in chroots, which is where this reared its ugly head.

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


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

[Touch-packages] [Bug 2024599] Re: linux-image-5.15.0-1032-realtime locks up under scheduler test load

2023-07-11 Thread Colin Ian King

Thanks JJ, much appreciated :-)

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

Title:
  linux-image-5.15.0-1032-realtime locks up under scheduler test load

Status in apparmor package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in apparmor source package in Jammy:
  New
Status in linux source package in Jammy:
  Incomplete
Status in apparmor source package in Kinetic:
  New
Status in linux source package in Kinetic:
  New
Status in apparmor source package in Lunar:
  New
Status in linux source package in Lunar:
  New
Status in apparmor source package in Mantic:
  New
Status in linux source package in Mantic:
  Incomplete

Bug description:
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04
  Codename: jammy

  uname -a
  Linux jammie-amd64-efi 5.15.0-1032-realtime #35-Ubuntu SMP PREEMPT_RT Tue Jan 
24 11:45:03 UTC 2023 x86_64
  x86_64 x86_64 GNU/Linux

  free
     totalusedfree  shared  buff/cache   
available
  Mem: 4013888  200984 34390121204  373892 
3744628
  Swap:4014076   0 4014076

  Running in a kvm-qemu, 8 cpus, cpu Intel Core Processor (Skylake,
  IBRS):

  how to reproduce issue:

  git clone https://github.com/ColinIanKing/stress-ng
  sudo apt-get update
  sudo apt-get build-dep stress-ng
  sudo apt-get install libeigen3-dev libmpfr-dev libkmod-dev libxxhash-dev 
libglvnd-dev libgbm-dev
  cd stress-ng
  make clean
  make -j 8
  sudo ./stress-ng --class scheduler --all 1 -v --vmstat 1 -t 30m

  ..wait for all the stressors to get invoked, system becomes
  unresponsive, can't ^C stress-ng, can't swap consoles on the VM,
  appears to be hard locked.

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


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

[Touch-packages] [Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build

2023-07-11 Thread Danilo Egea Gondolfo

Might be related to https://gitlab.gnome.org/GNOME/glib/-/issues/2927

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2927
   https://gitlab.gnome.org/GNOME/glib/-/issues/2927

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

Title:
  glib2.0 (2.77.0 ) breaks Netplan build

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
  mantic-proposed.

  See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3

  When I downgrade glib in my sbuild environment, everything works as
  expected:

  $ apt install libglib2.0-0=2.76.3-1ubuntu1
  libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1
  libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1

  The build also works fine in Debian unstable, which is using glib2.0
  2.74.6-2.

  Netplan is using plenty of GLib's keyfile functions
  (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to
  producing a different output with this newer release (some strange
  line breaks injected in the middle of a keyfile).

  
  Example keyfile from the test_wifis.test_wifi_wowlan test, that should be 
generated by Netplan and the way it fails:

  Expected output:
  ```
  [connection]
  id=netplan-wl0-homenet
  type=wifi
  interface-name=wl0

  [wifi]
  wake-on-wlan=330
  ssid=homenet
  mode=infrastructure

  [ipv4]
  method=link-local

  [ipv6]
  method=ignore
  ```

  Failure:
  ```
  E   AssertionError: '[con[88 
chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 
chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n'
  E [connection]
  E id=netplan-wl0-homenet
  E type=wifi
  E interface-name=wl0
  E 
  E [wifi]
  E wake-on-wlan=330
  E   - 
  E ssid=homenet
  E mode=infrastructure
  E   + 
  E [ipv4]
  E method=link-local
  E 
  E [ipv6]
  E method=ignore
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2026826/+subscriptions


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

[Touch-packages] [Bug 2026814] Re: package apparmor 3.0.8-1ubuntu2.1 failed to install/upgrade: installed apparmor package post-installation script subprocess returned error exit status 1

2023-07-11 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

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

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

Title:
  package apparmor 3.0.8-1ubuntu2.1 failed to install/upgrade: installed
  apparmor package post-installation script subprocess returned error
  exit status 1

Status in apparmor package in Ubuntu:
  Invalid

Bug description:
  ubuntu unity is being used.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: apparmor 3.0.8-1ubuntu2.1
  ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
  Uname: Linux 6.2.0-24-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jul 11 18:34:08 2023
  ErrorMessage: installed apparmor package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-07-11 (0 days ago)
  InstallationMedia: Ubuntu-Unity 23.04 "Lunar Lobster" - Release amd64 
(20230419)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic 
root=UUID=fb045af7-2921-4e16-932c-8a1bd04f1db7 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: apparmor
  Title: package apparmor 3.0.8-1ubuntu2.1 failed to install/upgrade: installed 
apparmor 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/apparmor/+bug/2026814/+subscriptions


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

[Touch-packages] [Bug 2026307] Re: ssh-askpass-gnome pops up for every sudo command

2023-07-11 Thread Lena Voytek

Hmm, I tested the workaround on lunar too just to make sure and it works
for me. After the .desktop file is created the inhibitShortcutsDialog
will show up one more time. Notably the description of the dialog box
will change to contain the Name entry for the desktop file - in this
case "GNOME ssh-askpass" rather than the executable name "gnome-ssh-
askpass". After clicking "allow" it shouldn't pop up ever again.

If it still has that name the Exec path may be wrong in the desktop
file. Make sure it says "Exec=/usr/lib/openssh/gnome-ssh-askpass".
Alternatively the local desktop file entry just might not be working and
it may be worth adding the file to /usr/share/applications/ instead.
This also works for me. Hope that helps, thanks!

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

Title:
  ssh-askpass-gnome pops up for every sudo command

Status in openssh package in Ubuntu:
  New
Status in openssh source package in Jammy:
  Triaged
Status in openssh source package in Kinetic:
  Triaged
Status in openssh source package in Lunar:
  Triaged

Bug description:
  When running multiple commands like this:
   
  SUDO_ASKPASS=/usr/lib/openssh/gnome-ssh-askpass sudo -A cp ./ez_bkup 
/usr/local/bin/ 

  from my gtk4 app, the ssh-askpass-gnome dialog and the gnome
  inhibitShortcutsDialog pops up. i click allow on the
  inhibitShortcutsDialog, then enter my password, which is accepted,
  then they both pop up again for each of these sudo commands my app
  calls.

  This happens in ubuntu 22.04-23.04 (completely updated) using gnome.
  If i use xfce in the same ubuntu versions, the gnome dialog doesn't
  pop up, of course, and ssh-askpass-gnome works properly (one entry and
  then all commands executed without further prompting). Fedora 37 works
  properly with gnome x11 or wayland, and xfce. Not sure if this is a
  bug in ubuntu's ssh-askpass-gnome, gnome-shell, or both/something
  else.

  ubuntu 23.04 is using GNOME Shell 44.2 and ssh-askpass-gnome
  1:9.0p1-1ubuntu8.2

  fedora is using openssh-askpass-8.8p1-10.fc37 and GNOME Shell 43.6

  thanks

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


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

[Touch-packages] [Bug 2026730] Re: Merge dash 0.5.12-6 from debian

2023-07-11 Thread Dominik Viererbe

** Merge proposal linked:
   
https://code.launchpad.net/~dviererbe/ubuntu/+source/dash/+git/dash/+merge/446503

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

Title:
  Merge dash 0.5.12-6 from debian

Status in dash package in Ubuntu:
  New

Bug description:
  This is a tracking bug to merge dash 0.5.12-6 from debian.

  Below now follows the report of the automated merge of the Ubuntu
  changes to the dash source package against the new Debian version.

  This file is designed to be both human readable and machine-parseable.
  Any line beginning with four spaces is a file that should be
  downloaded for the complete merge set.

  
  Here are the particulars of the three versions of dash that were
  chosen for the merge.  The base is the newest version that is a common
  ancestor of both the Ubuntu and Debian packages.  It may be of a
  different upstream version, but that's not usually a problem.

  The files are the source package itself, and the patch from the common
  base to that version.

  base: 0.5.12-2
  dash_0.5.12-2.dsc
  dash_0.5.12.orig.tar.gz
  dash_0.5.12-2.debian.tar.xz

  ubuntu: 0.5.12-2ubuntu1
  dash_0.5.12-2ubuntu1.dsc
  dash_0.5.12.orig.tar.gz
  dash_0.5.12-2ubuntu1.debian.tar.xz

  base -> ubuntu
  dash_0.5.12-2ubuntu1.patch

  debian: 0.5.12-6
  dash_0.5.12-6.dsc
  dash_0.5.12.orig.tar.gz
  dash_0.5.12-6.debian.tar.xz

  base -> debian
  dash_0.5.12-6.patch

  
  Generated Result
  

  Due to conflict or error, it was not possible to automatically create
  a source package.  Instead the result of the merge has been placed
  into the following tar file which you will need to turn into a source
  package once the problems have been resolved.

  dash_0.5.12-6ubuntu1.src.tar.gz

  
  Conflicts
  =

  In one or more cases, there were different changes made in both Ubuntu
  and Debian to the same file; these are known as conflicts.

  It is not possible for these to be automatically resolved, so this
  source needs human attention.

  Those files marked with 'C ' contain diff3 conflict markers, which can
  be resolved using the text editor of your choice.  Those marked with
  'C*' could not be merged that way, so you will find .UBUNTU and
  .DEBIAN files instead and should choose one of them or a combination
  of both, moving it to the real filename and deleting the other.

C  debian/tests/control

  
  Once you have a source package you are happy to upload, you should
  make sure you include the orig.tar.* if appropriate and information
  about all the versions included in the merge.

  Use the following command to generate a correct .changes file:

$ dpkg-genchanges -S -v0.5.12-2ubuntu1

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


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

[Touch-packages] [Bug 2026730] Re: Merge dash 0.5.12-6 from debian

2023-07-11 Thread Dominik Viererbe

I am currently building the merged package here:
https://launchpad.net/~dviererbe/+archive/ubuntu/dash-merge-
lp2026730-mantic/+packages

** Changed in: dash (Ubuntu)
 Assignee: (unassigned) => Dominik Viererbe (dviererbe)

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

Title:
  Merge dash 0.5.12-6 from debian

Status in dash package in Ubuntu:
  New

Bug description:
  This is a tracking bug to merge dash 0.5.12-6 from debian.

  Below now follows the report of the automated merge of the Ubuntu
  changes to the dash source package against the new Debian version.

  This file is designed to be both human readable and machine-parseable.
  Any line beginning with four spaces is a file that should be
  downloaded for the complete merge set.

  
  Here are the particulars of the three versions of dash that were
  chosen for the merge.  The base is the newest version that is a common
  ancestor of both the Ubuntu and Debian packages.  It may be of a
  different upstream version, but that's not usually a problem.

  The files are the source package itself, and the patch from the common
  base to that version.

  base: 0.5.12-2
  dash_0.5.12-2.dsc
  dash_0.5.12.orig.tar.gz
  dash_0.5.12-2.debian.tar.xz

  ubuntu: 0.5.12-2ubuntu1
  dash_0.5.12-2ubuntu1.dsc
  dash_0.5.12.orig.tar.gz
  dash_0.5.12-2ubuntu1.debian.tar.xz

  base -> ubuntu
  dash_0.5.12-2ubuntu1.patch

  debian: 0.5.12-6
  dash_0.5.12-6.dsc
  dash_0.5.12.orig.tar.gz
  dash_0.5.12-6.debian.tar.xz

  base -> debian
  dash_0.5.12-6.patch

  
  Generated Result
  

  Due to conflict or error, it was not possible to automatically create
  a source package.  Instead the result of the merge has been placed
  into the following tar file which you will need to turn into a source
  package once the problems have been resolved.

  dash_0.5.12-6ubuntu1.src.tar.gz

  
  Conflicts
  =

  In one or more cases, there were different changes made in both Ubuntu
  and Debian to the same file; these are known as conflicts.

  It is not possible for these to be automatically resolved, so this
  source needs human attention.

  Those files marked with 'C ' contain diff3 conflict markers, which can
  be resolved using the text editor of your choice.  Those marked with
  'C*' could not be merged that way, so you will find .UBUNTU and
  .DEBIAN files instead and should choose one of them or a combination
  of both, moving it to the real filename and deleting the other.

C  debian/tests/control

  
  Once you have a source package you are happy to upload, you should
  make sure you include the orig.tar.* if appropriate and information
  about all the versions included in the merge.

  Use the following command to generate a correct .changes file:

$ dpkg-genchanges -S -v0.5.12-2ubuntu1

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


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

[Touch-packages] [Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build

** Description changed:

  Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
  mantic-proposed.
  
  See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3
  
  When I downgrade glib in my sbuild environment, everything works as
  expected:
  
  $ apt install libglib2.0-0=2.76.3-1ubuntu1
  libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1
  libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1
  
  The build also works fine in Debian unstable, which is using glib2.0
  2.74.6-2.
  
  Netplan is using plenty of GLib's keyfile functions
  (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to producing
  a different output with this newer release (some strange line breaks
  injected in the middle of a keyfile).
+ 
+ 
+ Example keyfile from the test_wifis.test_wifi_wowlan test, that should be 
generated by Netplan and the way it fails:
+ 
+ Expected output:
+ ```
+ [connection]
+ id=netplan-wl0-homenet
+ type=wifi
+ interface-name=wl0
+ 
+ [wifi]
+ wake-on-wlan=330
+ ssid=homenet
+ mode=infrastructure
+ 
+ [ipv4]
+ method=link-local
+ 
+ [ipv6]
+ method=ignore
+ ```
+ 
+ Failure:
+ ```
+ E   AssertionError: '[con[88 
chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 
chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n'
+ E [connection]
+ E id=netplan-wl0-homenet
+ E type=wifi
+ E interface-name=wl0
+ E 
+ E [wifi]
+ E wake-on-wlan=330
+ E   - 
+ E ssid=homenet
+ E mode=infrastructure
+ E   + 
+ E [ipv4]
+ E method=link-local
+ E 
+ E [ipv6]
+ E method=ignore
+ ```

** Tags added: rls-mm-incoming

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

Title:
  glib2.0 (2.77.0 ) breaks Netplan build

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
  mantic-proposed.

  See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3

  When I downgrade glib in my sbuild environment, everything works as
  expected:

  $ apt install libglib2.0-0=2.76.3-1ubuntu1
  libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1
  libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1

  The build also works fine in Debian unstable, which is using glib2.0
  2.74.6-2.

  Netplan is using plenty of GLib's keyfile functions
  (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to
  producing a different output with this newer release (some strange
  line breaks injected in the middle of a keyfile).

  
  Example keyfile from the test_wifis.test_wifi_wowlan test, that should be 
generated by Netplan and the way it fails:

  Expected output:
  ```
  [connection]
  id=netplan-wl0-homenet
  type=wifi
  interface-name=wl0

  [wifi]
  wake-on-wlan=330
  ssid=homenet
  mode=infrastructure

  [ipv4]
  method=link-local

  [ipv6]
  method=ignore
  ```

  Failure:
  ```
  E   AssertionError: '[con[88 
chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 
chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n'
  E [connection]
  E id=netplan-wl0-homenet
  E type=wifi
  E interface-name=wl0
  E 
  E [wifi]
  E wake-on-wlan=330
  E   - 
  E ssid=homenet
  E mode=infrastructure
  E   + 
  E [ipv4]
  E method=link-local
  E 
  E [ipv6]
  E method=ignore
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2026826/+subscriptions


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

[Touch-packages] [Bug 2026719] Re: Low Volume 22.04 Realtek ALC285 HP Pavilion 15-ec2xxx

2023-07-11 Thread Dilip

HDAJackRetask installed and screenshot added

** Attachment added: "Screenshot from 2023-07-11 15-59-39.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2026719/+attachment/5685421/+files/Screenshot%20from%202023-07-11%2015-59-39.png

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

Title:
  Low Volume 22.04 Realtek ALC285 HP Pavilion 15-ec2xxx

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have dual boot Windows 10, volume is high even at 50%. The same
  YouTube video, VLC player, Rhythmbox have poor audio volume even at
  100%. Relying on Bluetooth speakers for some media. I tried various
  GUI tools, alsa-mixer. The volume is 100%. Looks like something to do
  with the driver level or ALSA.

  When I used alsamixer in the Terminal, I got this ( screenshot
  attached )


  The issue is the same with internal speakers mainly. But my Bluetooth
  speakers also give more sound on Windows 10.

  Description:  Ubuntu 22.04.2 LTS
  Release:  22.04

  Please let me know if you need any other info. My laptop is a 2 year
  old HP Pavilion 15-ec2xxx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2026719/+subscriptions


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

[Touch-packages] [Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build

I'm tagging this block-proposed to avoid this broken GLib to move into
mantic-release.

** Tags added: block-proposed

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

Title:
  glib2.0 (2.77.0 ) breaks Netplan build

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
  mantic-proposed.

  See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3

  When I downgrade glib in my sbuild environment, everything works as
  expected:

  $ apt install libglib2.0-0=2.76.3-1ubuntu1
  libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1
  libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1

  The build also works fine in Debian unstable, which is using glib2.0
  2.74.6-2.

  Netplan is using plenty of GLib's keyfile functions
  (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to
  producing a different output with this newer release (some strange
  line breaks injected in the middle of a keyfile).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2026826/+subscriptions


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

[Touch-packages] [Bug 2026826] [NEW] glib2.0 (2.77.0 ) breaks Netplan build

Public bug reported:

Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
mantic-proposed.

See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3

When I downgrade glib in my sbuild environment, everything works as
expected:

$ apt install libglib2.0-0=2.76.3-1ubuntu1
libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1
libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1

The build also works fine in Debian unstable, which is using glib2.0
2.74.6-2.

Netplan is using plenty of GLib's keyfile functions
(https://docs.gtk.org/glib/struct.KeyFile.html), which seem to producing
a different output with this newer release (some strange line breaks
injected in the middle of a keyfile).

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: block-proposed

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

Title:
  glib2.0 (2.77.0 ) breaks Netplan build

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in
  mantic-proposed.

  See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3

  When I downgrade glib in my sbuild environment, everything works as
  expected:

  $ apt install libglib2.0-0=2.76.3-1ubuntu1
  libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1
  libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1

  The build also works fine in Debian unstable, which is using glib2.0
  2.74.6-2.

  Netplan is using plenty of GLib's keyfile functions
  (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to
  producing a different output with this newer release (some strange
  line breaks injected in the middle of a keyfile).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2026826/+subscriptions


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

[Touch-packages] [Bug 2026814] [NEW] package apparmor 3.0.8-1ubuntu2.1 failed to install/upgrade: installed apparmor package post-installation script subprocess returned error exit status 1

2023-07-11 Thread Eric

Public bug reported:

ubuntu unity is being used.

ProblemType: Package
DistroRelease: Ubuntu 23.04
Package: apparmor 3.0.8-1ubuntu2.1
ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
Uname: Linux 6.2.0-24-generic x86_64
ApportVersion: 2.26.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
Date: Tue Jul 11 18:34:08 2023
ErrorMessage: installed apparmor package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2023-07-11 (0 days ago)
InstallationMedia: Ubuntu-Unity 23.04 "Lunar Lobster" - Release amd64 (20230419)
ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic 
root=UUID=fb045af7-2921-4e16-932c-8a1bd04f1db7 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.21ubuntu1
 apt  2.6.0
SourcePackage: apparmor
Title: package apparmor 3.0.8-1ubuntu2.1 failed to install/upgrade: installed 
apparmor package post-installation script subprocess returned error exit status 
1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package lunar

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

Title:
  package apparmor 3.0.8-1ubuntu2.1 failed to install/upgrade: installed
  apparmor package post-installation script subprocess returned error
  exit status 1

Status in apparmor package in Ubuntu:
  New

Bug description:
  ubuntu unity is being used.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: apparmor 3.0.8-1ubuntu2.1
  ProcVersionSignature: Ubuntu 6.2.0-24.24-generic 6.2.12
  Uname: Linux 6.2.0-24-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jul 11 18:34:08 2023
  ErrorMessage: installed apparmor package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2023-07-11 (0 days ago)
  InstallationMedia: Ubuntu-Unity 23.04 "Lunar Lobster" - Release amd64 
(20230419)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-6.2.0-24-generic 
root=UUID=fb045af7-2921-4e16-932c-8a1bd04f1db7 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.11, Python 3.11.2, python3-minimal, 3.11.2-1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0
  SourcePackage: apparmor
  Title: package apparmor 3.0.8-1ubuntu2.1 failed to install/upgrade: installed 
apparmor 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/apparmor/+bug/2026814/+subscriptions


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

[Touch-packages] [Bug 2024546] Re: DHCP not bringing up IPv6 address when dhcp6: true specified