[Touch-packages] [Bug 1947099] Update Released

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

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

Title:
  ipconfig does not honour user-requested timeouts in some cases

Status in klibc package in Ubuntu:
  Won't Fix
Status in klibc source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  In some cases, ipconfig can take a longer time than the user-specified 
timeouts, causing unexpected delays.

  [Test Plan]

  - Check that the ipconfig utility is able to obtain an IP through
  dhcp:

  # ip l set dev ens9 down
  # date; /usr/lib/klibc/bin/ipconfig ens9; date

  - Check if it respects the timeout (i.e. 2 seconds in the example
  below):

  # ip l set dev ens9 down
  # date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date

  - The original issue is that timeout is being ignored when not
  receiving any reply from a DHCP Server, so for this test you have to
  stop your DHCP Server (i.e. dnsmasq) and then test the timeouts:

  # ip l set dev ens9 down
  # date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date

  # ip l set dev ens9 down
  # date; /usr/lib/klibc/bin/ipconfig -t 5 ens9; date

  Make sure it times out respectivelly in 2 and 5 seconds.

  [racb: pending agreement with the SRU team; please see comment 37]

  Any situation where ipconfig encounters an error sending the DHCP
  packet, it will automatically set a delay of 10 seconds, which could
  be longer than the user-specified timeout. It can be reproduced by
  creating a dummy interface and attempting to run ipconfig on it with a
  timeout value of less than 10:

  # ip link add eth1 type dummy
  # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
  Thu Nov 18 04:46:13 EST 2021
  IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  Thu Nov 18 04:46:23 EST 2021

  ^ Notice above, ipconfig thinks that it waited 2 seconds, but the
  timestamps show an actual delay of 10 seconds.

  [Where problems could occur]
  Please see reproduction steps above. We are seeing this in production too 
(see comment #2).

  [Other Info]
  A patch to fix the issue is being proposed here. It is a safe fix - it only 
checks before going into sleep that the timeout never exceeds the 
user-requested value.

  [Original Description]

  In some cases, ipconfig can take longer than the user-specified
  timeouts, causing unexpected delays.

  in main.c, in function loop(), the process can go into
  process_timeout_event() (or process_receive_event() ) and if it
  encounters an error situation, will set an attempt to "try again
  later" at time equal now + 10 seconds by setting

  s->expire = now + 10;

  This can happen at any time during the main event loop, which can end
  up extending the user-specified timeout if "now + 10" is greater than
  "start_time + user-specified-timeout".

  I believe a patch like the following is needed to avoid this problem:

  --- a/usr/kinit/ipconfig/main.c
  +++ b/usr/kinit/ipconfig/main.c
  @@ -437,6 +437,13 @@ static int loop(void)

  if (timeout > s->expire - now.tv_sec)
  timeout = s->expire - now.tv_sec;
  +
  +   /* Compensate for already-lost time */
  +   gettimeofday(, NULL);
  +   if (now.tv_sec + timeout > start + loop_timeout) {
  +   timeout = loop_timeout - (now.tv_sec - start);
  +   printf("Lowered timeout to match user request 
= (%d s) \n", timeout);
  +   }
  }

  I believe the current behaviour is buggy. This is confirmed when the
  following line is executed:

  if (loop_timeout >= 0 &&
  now.tv_sec - start >= loop_timeout) {
  printf("IP-Config: no response after %d "
     "secs - giving up\n", loop_timeout);
  rc = -1;
  goto bail;
  }

  'loop_timeout' is the user-specified time-out. With a value of 2, in
  case of error, this line prints:

  IP-Config: no response after 2 secs - giving up

  So it thinks that it waited 2 seconds - however, in reality it had
  actually waited for 10 seconds.

  The suggested code-change ensures that the timeout that is actually
  used never exceeds the user-specified 

[Touch-packages] [Bug 1972056] Please test proposed package

2022-06-09 Thread Łukasz Zemczak
Hello Oibaf, or anyone else affected,

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

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

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

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

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

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

Title:
  [openssl3] please sync openssl.cnf to ease changing security level

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Kinetic:
  Fix Released
Status in openssl package in Debian:
  Fix Released

Bug description:
  [Impact]

  The OpenSSL 3.0 lead to a lot of broken setups. Some of them are
  regressions, but others are simply broken due to the use of outdated
  algorithms, such as SHA-1 signature on certificates. Changing the
  security level is a common action to identify and work around such
  cases, and as such the user should be able to change it easily  in the
  default config file.

  The fix is to partially revert our delta that ignored a Debian patch:
  instead of ignoring the patch entirely, we modify it to only affect
  the default configuration file, and in a way that matches our
  patchset. Using this approach will allow us to pick up on Debian's
  changes more easily during subsequent merges.

  [Test Plan]

  To easily check that the setting is taken into account, one can use
  'openssl ciphers -s'

  $ openssl ciphers -v -s | wc -l # Uses the default value
  30
  $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=2' | wc -l
  30
  $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=3' | wc -l
  24
  $ vim /etc/ssl/openssl.cf # edit the config file to bump the seclevel to 3
  $ openssl ciphers -v -s | wc -l # Uses the new value from the config file
  24

  [Where problems could occur]

  The changes could break the overall configuration of OpenSSL!

  [Origin report]
  openssl.cnf as provided misses some directive, which make it a bit difficult 
to change security level, which since openssl 3 disables SHA1 signatures.

  See also this Debian bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1010360 and the committed fix:
  
https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4

  Can you please sync this change in Ubuntu openssl?

  This way one should just add a single directive to change the security
  level.

  Thanks.

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


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


[Touch-packages] [Bug 1947588] Please test proposed package

2022-06-09 Thread Łukasz Zemczak
Hello Matt, or anyone else affected,

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

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

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

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

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

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

Title:
  Infinite Loop in OpenSSL s_server

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Confirmed
Status in openssl source package in Impish:
  Confirmed
Status in openssl source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  The TLS test server `openssl s_server` can very easily be led into an
  infinite loop if configured with incompatible settings and used via
  DTLS. This makes it harder to test one's TLS configuration.

  [Test plan]

  In one session:
  $ openssl s_server -nocert -psk 01020304 -dtls1
  In parallel:
  $ openssl s_client -dtls1 -psk 01020304

  The server session will enter an infinite loop:
  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  ... etc...

  [Where problems could occur]

  The patch is fairly self-contained, so regressions should only occur in
  the `openssl s_server` application, and not in the libssl or libcrypto
  libraries.
  However, the patch could break said server, which might be used in e.g.
  autopkgtests.

  [Original report]
  Launching openssl s_server as follows:

  $ openssl s_server -nocert -psk 01020304 -dtls1

  And using openssl s_client to connect to it like this:

  $ openssl s_client -dtls1 -psk 01020304

  Results in s_server entering an infinite loop:

  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR

  ...and so on...

  I have confirmed that upstream OpenSSL does not have this issue in a
  default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug
  with these commands (https://github.com/openssl/openssl/issues/16707)
  and it was while working on the fix for that issue
  (https://github.com/openssl/openssl/pull/16838) that I noticed this
  problem in the Ubuntu packages.

  $ lsb_release -rd
  Description: Ubuntu 21.04
  Release: 21.04

  $ apt-cache policy openssl
  openssl:
Installed: 1.1.1j-1ubuntu3.5
Candidate: 1.1.1j-1ubuntu3.5
Version table:
   *** 1.1.1j-1ubuntu3.5 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.1j-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  $ openssl version -a
  OpenSSL 1.1.1j 16 Feb 2021
  built on: Mon Aug 23 17:02:39 2021 UTC
  platform: debian-amd64
  options: bn(64,64) rc4(16x,int) des(int) blowfish(ptr)
  compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack 
-g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM 
-DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time 

[Touch-packages] [Bug 1974037] Please test proposed package

2022-06-09 Thread Łukasz Zemczak
Hello Simon, or anyone else affected,

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

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

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

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

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

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

Title:
  openssl: EVP_EC_gen() segfault without init

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Kinetic:
  Fix Released
Status in openssl package in Debian:
  Fix Released

Bug description:
  [Impact]

  The fix for
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997 has
  broken some code paths as the new string comparison functions now need
  initialization, triggering segafults.

  The provided debdiff fixes the immediate issue and also settles on a
  new implementation not requiring the initialization in the first
  place.

  [Test Plan]

  Since this is a regression fix, we first need to check that the
  original bug hasn't cropped up again:

  sudo locale-gen tr_TR.UTF-8
  LANG=C curl https://ubuntu.com/ > /dev/null # This work
  LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This should work as 
well

  For the regression itself:

  sudo apt install libssl-dev
  cat < openssl_test.c
  #include 
  int main()
  {
  EVP_PKEY_Q_keygen(NULL, NULL, "EC", "P-256");
  }
  EOF
  gcc openssl_test.c -lcrypto -lssl -o openssl_test
  ./openssl_test

  
  [Where problems could occur]

  This new patch set is relatively massive, on top of another massive one.
  Some new regressions could crop up of a similar kind. Furthermore, the
  homegrown string comparison function could be buggy, leading to algorithm 
name mismatches.

  [Other info]

  The patches all come from upstream and have been merged on their 3.0
  maintenance branch.

  [Original report]

  Source: sscg
  Version: 3.0.2-1
  Severity: serious
  Tags: ftbfs

  https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1

  ...
   1/10 generate_rsa_key_test FAIL  0.01s   killed by signal 11 
SIGSEGV
  04:32:21 MALLOC_PERTURB_=87 
/<>/obj-x86_64-linux-gnu/generate_rsa_key_test
  ...

  Summary of Failures:

   1/10 generate_rsa_key_test FAIL  0.01s   killed by signal
  11 SIGSEGV

  Ok: 9
  Expected Fail:  0
  Fail:   1
  Unexpected Pass:0
  Skipped:0
  Timeout:0
  dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=4 ninja test returned exit code 1
  make: *** [debian/rules:6: binary-arch] Error 25

  This has also been reported on the openssl-users mailing list:

  https://www.mail-archive.com/openssl-users@openssl.org/msg90830.html

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


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


[Touch-packages] [Bug 1978093] Re: openssl: FTBFS due to expired certificates

2022-06-09 Thread Łukasz Zemczak
Hello Simon, or anyone else affected,

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

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

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

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

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

** Changed in: openssl (Ubuntu Jammy)
   Status: New => Fix Committed

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

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

Title:
  openssl: FTBFS due to expired certificates

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Bionic:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Impish:
  New
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Kinetic:
  Confirmed

Bug description:
  [Impact]

  Some certificates in the openssl package expired on 2022-06-01, making
  the test suite fail. This needs to be fixed to facilitate future
  security updates.

  [Test Plan]

  Build the package. It currently fails with the following test summary:

  80-test_ssl_new.t(Wstat: 256 Tests: 30 Failed: 1)
Failed test:  12
Non-zero exit status: 1

  [Where problems could occur]

  I supposed this could break the build even worse.

  [Other Info]
   
  This currently prevents 3.0.2-0ubuntu1.3 in Jammy from publication.

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


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


[Touch-packages] [Bug 1947588] Re: Infinite Loop in OpenSSL s_server

2022-06-08 Thread Łukasz Zemczak
Hello Matt, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  Infinite Loop in OpenSSL s_server

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Confirmed
Status in openssl source package in Impish:
  Confirmed
Status in openssl source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  The TLS test server `openssl s_server` can very easily be led into an
  infinite loop if configured with incompatible settings and used via
  DTLS. This makes it harder to test one's TLS configuration.

  [Test plan]

  In one session:
  $ openssl s_server -nocert -psk 01020304 -dtls1
  In parallel:
  $ openssl s_client -dtls1 -psk 01020304

  The server session will enter an infinite loop:
  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  ... etc...

  [Where problems could occur]

  The patch is fairly self-contained, so regressions should only occur in
  the `openssl s_server` application, and not in the libssl or libcrypto
  libraries.
  However, the patch could break said server, which might be used in e.g.
  autopkgtests.

  [Original report]
  Launching openssl s_server as follows:

  $ openssl s_server -nocert -psk 01020304 -dtls1

  And using openssl s_client to connect to it like this:

  $ openssl s_client -dtls1 -psk 01020304

  Results in s_server entering an infinite loop:

  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR

  ...and so on...

  I have confirmed that upstream OpenSSL does not have this issue in a
  default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug
  with these commands (https://github.com/openssl/openssl/issues/16707)
  and it was while working on the fix for that issue
  (https://github.com/openssl/openssl/pull/16838) that I noticed this
  problem in the Ubuntu packages.

  $ lsb_release -rd
  Description: Ubuntu 21.04
  Release: 21.04

  $ apt-cache policy openssl
  openssl:
Installed: 1.1.1j-1ubuntu3.5
Candidate: 1.1.1j-1ubuntu3.5
Version table:
   *** 1.1.1j-1ubuntu3.5 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.1j-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  $ openssl version -a
  OpenSSL 1.1.1j 16 Feb 2021
  built on: Mon Aug 23 17:02:39 2021 UTC
  platform: debian-amd64
  options: bn(64,64) rc4(16x,int) des(int) blowfish(ptr)
  compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack 
-g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM 

[Touch-packages] [Bug 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level

2022-06-08 Thread Łukasz Zemczak
Hello Oibaf, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  [openssl3] please sync openssl.cnf to ease changing security level

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Kinetic:
  Fix Released
Status in openssl package in Debian:
  Fix Released

Bug description:
  [Impact]

  The OpenSSL 3.0 lead to a lot of broken setups. Some of them are
  regressions, but others are simply broken due to the use of outdated
  algorithms, such as SHA-1 signature on certificates. Changing the
  security level is a common action to identify and work around such
  cases, and as such the user should be able to change it easily  in the
  default config file.

  The fix is to partially revert our delta that ignored a Debian patch:
  instead of ignoring the patch entirely, we modify it to only affect
  the default configuration file, and in a way that matches our
  patchset. Using this approach will allow us to pick up on Debian's
  changes more easily during subsequent merges.

  [Test Plan]

  To easily check that the setting is taken into account, one can use
  'openssl ciphers -s'

  $ openssl ciphers -v -s | wc -l # Uses the default value
  30
  $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=2' | wc -l
  30
  $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=3' | wc -l
  24
  $ vim /etc/ssl/openssl.cf # edit the config file to bump the seclevel to 3
  $ openssl ciphers -v -s | wc -l # Uses the new value from the config file
  24

  [Where problems could occur]

  The changes could break the overall configuration of OpenSSL!

  [Origin report]
  openssl.cnf as provided misses some directive, which make it a bit difficult 
to change security level, which since openssl 3 disables SHA1 signatures.

  See also this Debian bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1010360 and the committed fix:
  
https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4

  Can you please sync this change in Ubuntu openssl?

  This way one should just add a single directive to change the security
  level.

  Thanks.

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


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


[Touch-packages] [Bug 1974037] Re: openssl: EVP_EC_gen() segfault without init

2022-06-08 Thread Łukasz Zemczak
Hello Simon, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  openssl: EVP_EC_gen() segfault without init

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Kinetic:
  Fix Released
Status in openssl package in Debian:
  Fix Released

Bug description:
  [Impact]

  The fix for
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997 has
  broken some code paths as the new string comparison functions now need
  initialization, triggering segafults.

  The provided debdiff fixes the immediate issue and also settles on a
  new implementation not requiring the initialization in the first
  place.

  [Test Plan]

  Since this is a regression fix, we first need to check that the
  original bug hasn't cropped up again:

  sudo locale-gen tr_TR.UTF-8
  LANG=C curl https://ubuntu.com/ > /dev/null # This work
  LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This should work as 
well

  For the regression itself:

  sudo apt install libssl-dev
  cat < openssl_test.c
  #include 
  int main()
  {
  EVP_PKEY_Q_keygen(NULL, NULL, "EC", "P-256");
  }
  EOF
  gcc openssl_test.c -lcrypto -lssl -o openssl_test
  ./openssl_test

  
  [Where problems could occur]

  This new patch set is relatively massive, on top of another massive one.
  Some new regressions could crop up of a similar kind. Furthermore, the
  homegrown string comparison function could be buggy, leading to algorithm 
name mismatches.

  [Other info]

  The patches all come from upstream and have been merged on their 3.0
  maintenance branch.

  [Original report]

  Source: sscg
  Version: 3.0.2-1
  Severity: serious
  Tags: ftbfs

  https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1

  ...
   1/10 generate_rsa_key_test FAIL  0.01s   killed by signal 11 
SIGSEGV
  04:32:21 MALLOC_PERTURB_=87 
/<>/obj-x86_64-linux-gnu/generate_rsa_key_test
  ...

  Summary of Failures:

   1/10 generate_rsa_key_test FAIL  0.01s   killed by signal
  11 SIGSEGV

  Ok: 9
  Expected Fail:  0
  Fail:   1
  Unexpected Pass:0
  Skipped:0
  Timeout:0
  dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=4 ninja test returned exit code 1
  make: *** [debian/rules:6: binary-arch] Error 25

  This has also been reported on the openssl-users mailing list:

  https://www.mail-archive.com/openssl-users@openssl.org/msg90830.html

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


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


[Touch-packages] [Bug 1959993] Update Released

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

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

Title:
  SRU of LXC 4.0.12 to focal (upstream bugfix release)

Status in lxc package in Ubuntu:
  In Progress
Status in lxc source package in Focal:
  Fix Committed
Status in lxc source package in Impish:
  Fix Released

Bug description:
  LXC released 4.0.12 as a bugfix release and is now in jammy. We'd like
  to line things up in focal.

  [Impact]
  The proposed SRU will bump from 4.0.6 all the way to 4.0.12, lining it up 
with what's currently in jammy. We've been skipping a few of the bugfix 
releases in focal so far, mostly catching up when we're starting to see 
problems with the older version.

  In this case, we've seen a number of issues when running with the HWE
  kernels as well as autopkgtest issues on foreign architectures (arm64
  and s390x), all those will go away with this bump as we've confirmed
  everything is clean in jammy.

  Changelog:

    * Cherry-pick upstream bugfixes (stable-4.0):
  - 0002-lxc-checkconfig-Fix-bashism.patch
  - 0003-doc-Fix-reverse-allowlist-denylist.patch

    * New upstream bugfix release (4.0.12):
  (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288)
  - Fixed CRIU restoration of containers with pre-created veth interfaces
  - Fixed issue with kernels lacking SMT support
  - Extended cgroup2 config options in lxc.mount.auto (cgroup2)
  - lxc-download now relies on HTTPS for validation (avoids GPG issues)

    * New upstream bugfix release (4.0.11):
  (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427)
  - Core scheduling support (lxc.sched.core)
  - riscv64 support in lxc.arch
  - Significantly improved bash completion profile
  - Greater use of the new VFS mount API (when supported by the kernel)
  - Fix containers with empty network namespaces
  - Handle kernels that lack TIOCGPTPEER
  - Improve CPU bitmask/id handling (handle skipped CPU numbers)
  - Reworked the tests to run offline

    * New upstream bugfix release (4.0.10):
  (https://discuss.linuxcontainers.org/t/lxc-4-0-10-has-been-released/11618)
  - Fix issues with less common architectures
  - Support for additional idmap mounts
  - nft support in lxc-net
  - Cleaner mount entries for sys:mixed
  - Switched GPG server to keyserver.ubuntu.com

    * New upstream bugfix release (4.0.9):
  (https://discuss.linuxcontainers.org/t/lxc-4-0-9-has-been-released/10999)
  - Fix incorrect personality setting when running 32bit containers on 64bit

    * New upstream bugfix release (4.0.8):
  - Fix CGroup attach against older running containers

    * New upstream bugfix release (4.0.7):
  - Testing improvements including fixes from oss-fuzz
  - Rework of the attach codepath
  - Cgroup handling rework

    * Bump to debhelper 12 (allows focal SRUs)
    * Bump standards to 4.6.0.1
    * Add lintian overrides for incorrect bashism detection
    * Remove bash completion install logic (now done upstream)

  Just like Ubuntu itself, upstream releases long term support releases,
  e.g. 4.0, and then periodic point releases including all the
  accumulated bugfixes.

  Only the latest upstream release gets full support from the upstream
  developers, everyone else is expected to first update to it before
  receiving any kind of support.

  This should qualify under the minor/micro upstream bugfix release
  allowance of the SRU policy, letting us SRU this without paperwork for
  every single change included in this upstream release.

  [Test Plan]
  lxc has autopkgtests which will assert that the binaries built in -proposed 
are functional.

  [Where problems could occur]
  This is catching up a fair bit on recent kernel API changes, including 
cgroup1/cgroup2 support, handling of nftables, riscv64 and core scheduling 
which were all needed to properly handle the most recent HWE kernels especially 
as we're getting ready for Ubuntu 22.04's 5.15 to get pushed to focal.

  We've had all that code running on well over a million of LXD snap
  users for a few months now without seeing any issues (or more
  precisely, those issues we found have been all been resolved as of
  4.0.12).

  However what LXD exercises isn't 100% of LXC and it's certainly possible that 
we missed a corner case in one of those changes.
  The good news is that this would 

[Touch-packages] [Bug 1971712] Update Released

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

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+subscriptions


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


[Touch-packages] [Bug 1933491] Update Released

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

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

Title:
  kmod add zstd support

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Focal:
  Fix Released
Status in kmod source package in Impish:
  Fix Released
Status in kmod source package in Jammy:
  Fix Released
Status in kmod package in Debian:
  New

Bug description:
  [Impact]

   * To safe diskspace, upcoming devel series / hwe kernels may turn on
  zstd kernel module compression. Kmod since impish support zstd
  support. But in order to keep hwe kernels at parity, or allow
  inspecting jammy modules from focal host, it would be beneficial for
  kmod in focal to support zstd compressed modules.

  [Test Plan]

   * Pick any kernel module

   * Compress it with zstd: $ zstd *.ko

   * Check that modinfo can read it: $ modinfo *.ko.zst

  [Where problems could occur]

   * kmod will gain a new dependecy on libzstd1, however it should
  already be present, because dpkg in focal depends on libzstd1 already.

   * initramfs-tools already supports compressed modules, but in focal
  at the moment it does so in an inefficient manner (regresses
  bootspeed), this has been improved in
  https://launchpad.net/ubuntu/+source/initramfs-tools/0.140ubuntu8 and
  is yet to be SRUed into Focal.

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


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


[Touch-packages] [Bug 1959375] Re: [SRU] Please support group manipulation with "extrausers"

2022-05-30 Thread Łukasz Zemczak
Hey Chris! Any reason you only released the focal one?

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

Title:
  [SRU] Please support group manipulation with "extrausers"

Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Bionic:
  Fix Committed
Status in shadow source package in Focal:
  Fix Released
Status in shadow source package in Impish:
  Won't Fix
Status in shadow source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  * In order to use the microk8s snap in Ubuntu Core, one currently
  needs to be root. This is far from optimal, since normally (on desktop
  and server installations) this is not necessary.

  * This make it hard to provide consistent documentation on microk8s
  across all supported device, if we have to take the "sudo" command
  into account, and how file permissions for generated files might be
  affected.

  
  [Test Plan]

  The issue can be reproduced on Ubuntu Core 18, 20 and 22. The steps
  are as following (replace "" with the actual path of your
  Ubuntu Core image file:

  qemu-system-x86_64 -enable-kvm -smp 2 -m 1500 \
  -netdev user,id=mynet0,hostfwd=tcp::8022-:22,hostfwd=tcp::8090-:80 \
  -device virtio-net-pci,netdev=mynet0 \
  -drive file=,format=raw

  After configuring your account, connect to youd device via SSH:

  ssh @localhost -p 8022

  And issue these commands

  sudo snap install microk8s --channel=latest/edge/stable

  # microk8s is going to eat up all your disk space, so stop it as soon
  # as the prompt comes back:
  sudo microk8s stop

  # Add your user to the microk8s group
  sudo usermod -G snap_microk8s $(whoami)

  The last command will fail unless this bug is fixed. If the bug is
  fixed, the command will succeed, and after logging out and in again,
  you can verify that you've been added to the snap_microk8s group by
  running the "groups" command.

  
  [Where problems could occur]

  * The patch only touches error code paths and adds a fallback
  mechanism in them. Therefore, "normal" operations, where these
  commands would have succeeded before, will not be affected at all.

  * In those cases when usermod fails because it failed to find or load
  the requested user/group, we reset the user/group database paths to
  our writable user/group databases, and retry the operation. Note that
  the path for our database is hardcoded in the program source, so the
  security risk seems contained. We do not add additional command-line
  parameters.

  
  [Other Info]

  Original bug description
  

  Currently doing something like:

  sudo usermod -a -G snap_microk8s dbeamonte

  on a Ubuntu Core system will fail with

  usermod: /etc/group.15965: Read-only file system

  This is because the existing usermod patches to detect
  the extrausers file do not cover this case. Attached
  a simple patch that enables it. I will give this patch
  a test run in our image PPA for jammy and if things look
  good I would like upload to 22.04 and SRU for 20.04 and
  18.04.

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


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


[Touch-packages] [Bug 1968154] Update Released

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

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

Title:
  Only keep 2 kernels

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

  We remove the requirement to keep the most recently installed version,
  previously recorded in APT::LastInstalledKernel, to achieve this, as
  we had 3 hard requirements so far:

  1. keep booted kernel
  2. keep highest version
  3. keep most recently installed

  1 can't be removed as it would break running systems, 2 is what you
  definitely want to keep.

  During normal system lifetime, the most recently installed kernel is
  the same as the highest version, so 2==3, and there are no changes to
  behavior.

  Likewise, if you most recently installed an older kernel manually for
  debugging, it would be manually installed and not subject to removal,
  even if the rule is dropped.

  The behavior really only changes if you install an older kernel, and
  then mark it auto - that older kernel becomes automatically removable
  immediately after it is marked as auto.

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


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


[Touch-packages] [Bug 1962541] Update Released

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

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

Title:
  PEAP wifi can't connect (ubuntu live/installer is also not working

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

Bug description:
  * Impact

  Connecting to some PEAP wifi doesn't work anymore since the openssl3
  transition

  Details on the issue can be found on
  http://lists.infradead.org/pipermail/hostap/2022-May/040511.html

  * Test case

  Try using a PEAP wifi not implementing RFC5746, it should be able to
  connect

  * Regression potential

  The change allows to connect to less secure WiFis the same way that
  wpa allowed before openssl3, lower security enforcement isn't ideal
  but still better than non working hardware.

  

  WPA2 enterprise can't connect PEAP
  ubuntu 22.04 live/installer is not working too

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.6
  Uname: Linux 5.16.0-kali1-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu78
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar  1 09:18:42 2022
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)
  VarLogDistupgradeTermlog:

  mtime.conffile..etc.update-manager.release-upgrades:
  2022-02-27T21:07:16.553410

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


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


[Touch-packages] [Bug 1968997] Update Released

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

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

Title:
  openssl has catastrophic issues when locale set to TR_UTF8

Status in openssl package in Ubuntu:
  Fix Committed
Status in openssl source package in Jammy:
  Fix Released
Status in openssl source package in Kinetic:
  Fix Committed

Bug description:
  [Impact]

  Due to the case comparison differences in the Turkish locale, some routines in
  OpenSSL fail to recognize some algorithm names as valid, unexpectedly breaking
  crypto.

  [Test Plan]

  This bug is really easy to trigger:

  sudo locale-gen tr_TR.UTF-8
  LANG=C curl https://ubuntu.com/ > /dev/null # This work
  LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This fails

  The error is curl: (35) error:0372:digital envelope
  routines::decode error

  [Where problems could occur]

  This patch set is relatively massive, and can cause regressions, as 
illustrated
  by the patch #5 which fixes one such regression. Those regressions would 
likely
  show up as either libssl crashes, in case of uninitialized objects, or as
  algorithm selection failures if somehow the case comparison is buggy.

  [Other Info]
   
  The fix has already been released upstream as part of their 3.0.3 release.

  [Original report]
  I noticed this when I checked "ua status". It alerted me that I should check 
my openssl configuration.

  "ua status
  Failed to access URL: 
https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy
  Cannot verify certificate of server
  Please check your openssl configuration."

  I also figured wget doesn't work with https:// URLs at all.

  On web I found:
  https://github.com/openssl/openssl/issues/18039

  So I changed locale to C_UTF-8

  #locale
  LANG=tr_TR.UTF-8
  LANGUAGE=
  LC_CTYPE="tr_TR.UTF-8"
  LC_NUMERIC=tr_TR.UTF-8
  LC_TIME=tr_TR.UTF-8
  LC_COLLATE="tr_TR.UTF-8"
  LC_MONETARY=tr_TR.UTF-8
  LC_MESSAGES="tr_TR.UTF-8"
  LC_PAPER=tr_TR.UTF-8
  LC_NAME=tr_TR.UTF-8
  LC_ADDRESS=tr_TR.UTF-8
  LC_TELEPHONE=tr_TR.UTF-8
  LC_MEASUREMENT=tr_TR.UTF-8
  LC_IDENTIFICATION=tr_TR.UTF-8
  LC_ALL=
  casaba@ship-macbook:/backups$ sudo locale-gen c
  ca_AD ca_ES.UTF-8 ca_IT ckb_IQ cs_CZ cy_GB.UTF-8
  ca_AD.UTF-8 ca_ES@valencia ca_IT.UTF-8 cmn_TW cs_CZ.UTF-8
  ca_ES ca_FR ce_RU crh_UA cv_RU
  ca_ES@euro ca_FR.UTF-8 chr_US csb_PL cy_GB
  casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8
  Generating locales (this might take a while)...
C.UTF-8... done
  Generation complete.
  casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8
  casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8

  Now the result is (after logout/login)

  ua status
  SERVICE ENTITLED STATUS DESCRIPTION
  cc-eal yes n/a Common Criteria EAL2 Provisioning Packages
  cis yes n/a Security compliance and audit tools
  esm-infra yes n/a UA Infra: Extended Security Maintenance (ESM)
  fips yes n/a NIST-certified core packages
  fips-updates yes n/a NIST-certified core packages with priority security 
updates
  livepatch yes n/a Canonical Livepatch service

  Enable services with: ua enable 

   Account: il...@fastmail.fm
  Subscription: il...@fastmail.fm

  If Ubuntu 22 ships with current configuration, entire TR will suffer
  considering you can't find http:// downloads anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssl 3.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Apr 14 10:21:09 2022
  InstallationDate: Installed on 2021-12-29 (105 days ago)
  InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago)
  mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505

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


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


[Touch-packages] [Bug 1971712] Re: Add support for Intel DG2

2022-05-12 Thread Łukasz Zemczak
Hello Timo, or anyone else affected,

Accepted mesa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/22.0.1-1ubuntu2.1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: mesa (Ubuntu Jammy)
   Status: New => Fix Committed

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

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in linux-oem-5.17 source package in Jammy:
  New
Status in mesa source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+subscriptions


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


[Touch-packages] [Bug 1965901] Please test proposed package

2022-05-06 Thread Łukasz Zemczak
Hello Sebastien, or anyone else affected,

Accepted libqmi into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libqmi/1.30.4-1~ubuntu20.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: modemmanager (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  SRU the new 1.18 serie to focal for hwe

Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in libmbim source package in Focal:
  Fix Committed
Status in libqmi source package in Focal:
  Fix Committed
Status in modemmanager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  We want to update to the newer serie for better hardware support
  (support for Quectel EM120R-GL and EM160R-GL)

  [Test Plan]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Where problems could occur]

  The new version no longer automatically performs the FCC unlock
  procedure by default, see details on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/

  It means some modem will stop working out of the box.
  Users can manually install the unlock utility as described in the "FCC unlock 
procedures in ModemManager >= 1.18.4" section in the page above.

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


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


[Touch-packages] [Bug 1965901] Please test proposed package

2022-05-06 Thread Łukasz Zemczak
Hello Sebastien, or anyone else affected,

Accepted modemmanager into focal-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/modemmanager/1.18.6-1~ubuntu20.04.1
in a few hours, and then in the -proposed repository.

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

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

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

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

** Tags added: blocked-proposed-focal

** Tags removed: blocked-proposed-focal
** Tags added: block-proposed-focal

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

Title:
  SRU the new 1.18 serie to focal for hwe

Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in libmbim source package in Focal:
  Fix Committed
Status in libqmi source package in Focal:
  Fix Committed
Status in modemmanager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  We want to update to the newer serie for better hardware support
  (support for Quectel EM120R-GL and EM160R-GL)

  [Test Plan]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Where problems could occur]

  The new version no longer automatically performs the FCC unlock
  procedure by default, see details on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/

  It means some modem will stop working out of the box.
  Users can manually install the unlock utility as described in the "FCC unlock 
procedures in ModemManager >= 1.18.4" section in the page above.

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


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


[Touch-packages] [Bug 1965901] Re: SRU the new 1.18 serie to focal for hwe

2022-05-06 Thread Łukasz Zemczak
Added the block-proposed-focal tag until we have clarity on how to
proceed with the missing auto-unlocking functionality.

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

Title:
  SRU the new 1.18 serie to focal for hwe

Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in libmbim source package in Focal:
  Fix Committed
Status in libqmi source package in Focal:
  Fix Committed
Status in modemmanager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  We want to update to the newer serie for better hardware support
  (support for Quectel EM120R-GL and EM160R-GL)

  [Test Plan]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Where problems could occur]

  The new version no longer automatically performs the FCC unlock
  procedure by default, see details on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/

  It means some modem will stop working out of the box.
  Users can manually install the unlock utility as described in the "FCC unlock 
procedures in ModemManager >= 1.18.4" section in the page above.

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


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


[Touch-packages] [Bug 1965901] Re: SRU the new 1.18 serie to focal for hwe

2022-05-06 Thread Łukasz Zemczak
Hello Sebastien, or anyone else affected,

Accepted libmbim into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/libmbim/1.26.2-1~ubuntu20.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: libmbim (Ubuntu Focal)
   Status: New => Fix Committed

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

** Changed in: libqmi (Ubuntu Focal)
   Status: New => Fix Committed

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

Title:
  SRU the new 1.18 serie to focal for hwe

Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New
Status in libmbim source package in Focal:
  Fix Committed
Status in libqmi source package in Focal:
  Fix Committed
Status in modemmanager source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  We want to update to the newer serie for better hardware support
  (support for Quectel EM120R-GL and EM160R-GL)

  [Test Plan]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Where problems could occur]

  The new version no longer automatically performs the FCC unlock
  procedure by default, see details on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/

  It means some modem will stop working out of the box.
  Users can manually install the unlock utility as described in the "FCC unlock 
procedures in ModemManager >= 1.18.4" section in the page above.

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


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


[Touch-packages] [Bug 1965901] Re: SRU the new 1.18 serie to focal for hwe

2022-05-06 Thread Łukasz Zemczak
So this is a bit of a pickle this SRU. Basically we need to decide on
one of the two worlds: staying compliant with what the manufacturers
demand (not performing the FCC unlock by default) and not breaking users
(as previously modemmanager was automatically performing the unlock). We
would probably need to consult someone regarding the legal aspect of
automatically unlocking the devices - so it's something we really should
do. Since by default we should really REALLY make sure that we're not
breaking existing users, but then again - we shouldn't be doing things
that are 'not okay' by our main packages as well.

However, in the meantime, I'll review the SRU as-is, without the auto-
unlocking, consider pulling it into focal-proposed and then set a block-
proposed tag until we know for sure which way to go. We can always patch
the package with the unlocks and re-upload, if needed.

A bit of additional data regarding the regression potential of this change, 
maybe even some pros of just going with 1.118 as-is:
 * From what I know, some of the locked modems (the Lenovo-shipped ones I 
think?) are already broken by a firmware upgrade right now.
 * Users upgrading to the next LTS (22.04), once upgrades are enabled, will 
encounter this issue anyway, having to manually perform the unlock.

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

Title:
  SRU the new 1.18 serie to focal for hwe

Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  We want to update to the newer serie for better hardware support
  (support for Quectel EM120R-GL and EM160R-GL)

  [Test Plan]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Where problems could occur]

  The new version no longer automatically performs the FCC unlock
  procedure by default, see details on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/

  It means some modem will stop working out of the box.
  Users can manually install the unlock utility as described in the "FCC unlock 
procedures in ModemManager >= 1.18.4" section in the page above.

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


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


[Touch-packages] [Bug 1965901] Re: SRU the new 1.18 serie to focal for hwe

2022-05-04 Thread Łukasz Zemczak
Putting a bit more thought into this, I'm a bit concerned by regressing
user. The plus side, as per our face-to-face discussion, there are not
many modem users, but still... maybe I'd like to investigate some
possibilities.

Reading up on the modemmanager page gave me some necessary context here.
I agree with the upstream decision not to unlock modems automatically
and their recommendation for distributions not doing it automatically as
well. That being said, 20.04 has been released with auto-unlocking, so
this feels like going against our stability principles in Ubuntu. Some
question here regarding this: does the new modemmanager add some new FCC
locked modems in 1.18 in comparison to 1.16? Since one fair way to go
forward in my eyes (at least right now) would be to keep auto-unlocking
the previously supported modems but require manual unlocks of the new
ones. Are there any new ones? Or does this basically only relate and
lock down those that were previously available?

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

Title:
  SRU the new 1.18 serie to focal for hwe

Status in libmbim package in Ubuntu:
  New
Status in libqmi package in Ubuntu:
  New
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  We want to update to the newer serie for better hardware support
  (support for Quectel EM120R-GL and EM160R-GL)

  [Test Plan]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Where problems could occur]

  The new version no longer automatically performs the FCC unlock
  procedure by default, see details on
  https://modemmanager.org/docs/modemmanager/fcc-unlock/

  It means some modem will stop working out of the box.
  Users can manually install the unlock utility as described in the "FCC unlock 
procedures in ModemManager >= 1.18.4" section in the page above.

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


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


[Touch-packages] [Bug 1940141] Re: OpenSSL servers can send a non-empty status_request in a CertificateRequest

2022-04-28 Thread Łukasz Zemczak
Per comments from Marc, let's proceed without making this fix optional.
Let's just keep our eyes and ears open for any possible regressions
caused by this change landing in bionic.

** Changed in: openssl (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  The issue leads to various client failures with TLS 1.3 as described
  in, e.g.

  https://github.com/golang/go/issues/35722
  https://github.com/golang/go/issues/34040

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file 
test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
  CertificateRequest, Length=1570
    request_context (len=0):
    extensions, length = 1567
  extension_type=status_request(5), length=1521
     - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   
0..
    000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   
0.+.0..
    001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   
0...0..
    002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   
0..1.0...UG
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

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


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


[Touch-packages] [Bug 1940141] Please test proposed package

2022-04-28 Thread Łukasz Zemczak
Hello Nicolas, or anyone else affected,

Accepted openssl into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.1~18.04.16
in a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  OpenSSL servers can send a non-empty status_request in a
  CertificateRequest

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  openssl does not conform to RFC8446, Sec. 4.4.2.1., by sending a
  CertificateRequest message to the client with a non-empty
  status_request extension.

  This issue was fixed in openssl-1.1.1d and is included in Focal
  onward.

  Upstream issue is tracked at https://github.com/openssl/openssl/issues/9767
  Upstream patch review at https://github.com/openssl/openssl/pull/9780

  The issue leads to various client failures with TLS 1.3 as described
  in, e.g.

  https://github.com/golang/go/issues/35722
  https://github.com/golang/go/issues/34040

  [Test Plan]

  The issue can be reproduced by building with `enable-ssl-trace`
  and then running `s_server` like this:

  ```
  openssl s_server -key key.pem -cert cert.pem -status_file 
test/recipes/ocsp-response.der -Verify 5
  ```

  And running `s_client` like this:

  ```
  openssl s_client -status -trace -cert cert.pem -key key.pem
  ```

  The output shows a `status_request` extension in the
  `CertificateRequest` as follows:

  Received Record
  Header:
    Version = TLS 1.2 (0x303)
    Content Type = ApplicationData (23)
    Length = 1591
    Inner Content Type = Handshake (22)
  CertificateRequest, Length=1570
    request_context (len=0):
    extensions, length = 1567
  extension_type=status_request(5), length=1521
     - 01 00 05 ed 30 82 05 e9-0a 01 00 a0 82 05 e2   
0..
    000f - 30 82 05 de 06 09 2b 06-01 05 05 07 30 01 01   
0.+.0..
    001e - 04 82 05 cf 30 82 05 cb-30 82 01 1a a1 81 86   
0...0..
    002d - 30 81 83 31 0b 30 09 06-03 55 04 06 13 02 47   
0..1.0...UG
  ...more lines omitted...

  If the `status_request` extension is present in a
  `CertificateRequest` then it must be empty according to RFC8446,
  Sec. 4.4.2.1.

  [Where problems could occur]

  The patch disables the `status_request` extension inside a
  `CertificateRequest`. Applications expecting the incorrect,
  non-empty reply for the `status_request` extension will break
  with this patch.

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


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


[Touch-packages] [Bug 1747499] Re: 98-reboot-required and Interaction with livepatch

2022-04-27 Thread Łukasz Zemczak
** Also affects: update-notifier (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: unattended-upgrades (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  98-reboot-required and Interaction with livepatch

Status in unattended-upgrades package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in unattended-upgrades source package in Focal:
  New
Status in update-notifier source package in Focal:
  New

Bug description:
  
  [Impact]

   * If a system is using canonical livepatch, has it enabled, and
  patches are applied, it could be confusing for a user to receive a
  "system restart required" messages in the MOTD when logging in.

   * Livepatch is available on LTS releases. Thus, the users can be
  confused following a kernel update on 20.04.

   * The upload prevents update-notifier and unattended-ugprades hooks from 
adding "system restart"-related messages to motd when Livepatch is enabled.
  Livepatch, when enabled, already contributes to the motd message so there is 
no need to have duplicate (and sometimes contradictory) information.

  [Test Plan]

   * how to reproduce the bug:

 1. Install and boot a 20.04 server VM
 2. Make sure it runs a generic kernel (or another flavour that supports 
Livepatch)
 3. Enable Livepatch using the following command:
 $ ua attach # replace  by an actual contract token
 4. Upgrade the kernel (if you are already running the latest available 
kernel update, you can install a different flavour)
 5. Upon logging in again, the motd will show ***System restart required***.

   * other testing appropriate to perform before landing this update:

* Making sure that the patch has no impact when livepatch is not enabled.
* The motd should show ***System restart required*** after upgrading the 
kernel if livepatch is not enabled.

  [Where problems could occur]

   * The change updates a hook script in /etc/kernel/postinst.d/.
  Scripts in this directory are executing when upgrading / installing a
  kernel. If somehow the script is broken, it can prevent dpkg for
  succeeding when upgrading / installing the kernel.

   * If the implementation is wrong, we might end up "losing" the
  ***System restart required*** message when livepatch is disabled

  [Original bug description]

  If a system is using canonical livepatch, has it enabled, and patches
  are applied, it could be confusing for a user to receive a "system
  restart required" messages in the MOTD when logging in.

  That message, when present, is printed by 98-reboot-required which
  essentially just cats /var/run/reboot-required to stdout. That file is
  placed by packages that require a reboot so that they are properly
  used in their updated versions. Examples that come to mind are libc
  and the kernel.

  There is a secondary file that can be created which says which
  packages requested the reboot. That would be /var/run/reboot-
  required.pkgs

  Ideally that script should not print out the reboot required message
  if a) livepatch is installed and enabled; b) the only trigger for the
  reboot is a kernel update.

  For (a), one can use the command "ubuntu-advantage is-livepatch-
  enabled" and check $?. That is in the ubuntu-advantage-tools package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1747499/+subscriptions


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


[Touch-packages] [Bug 1968154] Re: Only keep 2 kernels

2022-04-25 Thread Łukasz Zemczak
Can you mention a bit more about the APT::LastInstalledKernel logic
usage removal in this SRU? What was it used before? Since right now this
SRU seems to be dropping its use + only keeping track of 2 kernels, can
you help me understand the implications of that (as I didn't know about
this logic before)?

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

Title:
  Only keep 2 kernels

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in apt source package in Bionic:
  New
Status in unattended-upgrades source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in unattended-upgrades source package in Focal:
  New
Status in apt source package in Impish:
  In Progress
Status in unattended-upgrades source package in Impish:
  New

Bug description:
  [Impact]
  APT currently keeps 3 kernels or even 4 in some releases. Our boot partition 
is sized for a steady state of 2 kernels + 1 new one being unpacked, hence 
users run out of space and new kernels fail to install, upgrade runs might 
abort in the middle. It's not nice.

  [Test plan]
  1. Have two kernels installed (let's call them version 3, 2)
  2. Check that both kernels are not autoremovable
  3. Install an old kernel (let's call it 1), and mark it automatic
  4. Check that 1 will be autoremovable (apt autoremove -s)
  5. Reboot into 1, check that 2 is autoremovable (apt autoremove -s)
  6. Actually remove 2
  7. Reboot into 3 and check that both 1 and 3 are now not autoremovable

  unattended-upgrades may need changes to its test suite to accommodate
  this.

  [Where problems could occur]
  We could keep the wrong kernels installed that the user did not expect.

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


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


[Touch-packages] [Bug 1966179] Re: The airplane hotkey does not work on lots of HP platforms

2022-04-25 Thread Łukasz Zemczak
Hello Andy, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.6 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-impish

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

** Tags added: verification-needed-focal

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

Title:
  The airplane hotkey does not work on lots of HP platforms

Status in OEM Priority Project:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  [Where problems could occur]
  If we don't have whitelist in focal and impish, then the airplane key won't 
work on new HP platforms.

  Please refer to Bug #1955997 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966179/+subscriptions


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


[Touch-packages] [Bug 1967038] Please test proposed package

2022-04-25 Thread Łukasz Zemczak
Hello Andy, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.17 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


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


[Touch-packages] [Bug 1967038] Please test proposed package

2022-04-25 Thread Łukasz Zemczak
Hello Andy, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.6 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-focal

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

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


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


[Touch-packages] [Bug 1966179] Please test proposed package

2022-04-25 Thread Łukasz Zemczak
Hello Andy, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.17 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  The airplane hotkey does not work on lots of HP platforms

Status in OEM Priority Project:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  [Where problems could occur]
  If we don't have whitelist in focal and impish, then the airplane key won't 
work on new HP platforms.

  Please refer to Bug #1955997 as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1966179/+subscriptions


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


[Touch-packages] [Bug 1967038] Re: Add mic mute key for HP Elite x360 series

2022-04-25 Thread Łukasz Zemczak
Hello Andy, or anyone else affected,

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

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

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

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

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

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

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

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

** Tags added: verification-needed-impish

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

Title:
  Add mic mute key for HP Elite x360 series

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Committed

Bug description:
  Upstream commit:
  
https://github.com/systemd/systemd/commit/f09f6dc2c8f59b2b58159cc413b605a547c8646e

  [Impact]

   * User can't use mic mute key if they buy Elite x360 G9 series.

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1967038/+subscriptions


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


[Touch-packages] [Bug 1968997] Re: openssl has catastrophic issues when locale set to TR_UTF8

2022-04-15 Thread Łukasz Zemczak
Upstream did a review of these changes and I think they have some valid points:
https://github.com/openssl/openssl/pull/18115#issuecomment-1099784064

I'm also worried that the newlocale() calls have no corresponding
freelocale() counterparts. I think this needs a bit more tinkering
before we proceed - in lieu of these uncertainties, I'll reject if from
the queue.

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

Title:
  openssl has catastrophic issues when locale set to TR_UTF8

Status in openssl package in Ubuntu:
  Fix Committed

Bug description:
  I noticed this when I checked "ua status". It alerted me that I should
  check my openssl configuration.

  "ua status
  Failed to access URL: 
https://contracts.canonical.com/v1/resources?architecture=amd64=5.15.0-25-generic=jammy
  Cannot verify certificate of server
  Please check your openssl configuration."

  I also figured wget doesn't work with https:// URLs at all.

  On web I found:
  https://github.com/openssl/openssl/issues/18039

  So I changed locale to C_UTF-8

  #locale
  LANG=tr_TR.UTF-8
  LANGUAGE=
  LC_CTYPE="tr_TR.UTF-8"
  LC_NUMERIC=tr_TR.UTF-8
  LC_TIME=tr_TR.UTF-8
  LC_COLLATE="tr_TR.UTF-8"
  LC_MONETARY=tr_TR.UTF-8
  LC_MESSAGES="tr_TR.UTF-8"
  LC_PAPER=tr_TR.UTF-8
  LC_NAME=tr_TR.UTF-8
  LC_ADDRESS=tr_TR.UTF-8
  LC_TELEPHONE=tr_TR.UTF-8
  LC_MEASUREMENT=tr_TR.UTF-8
  LC_IDENTIFICATION=tr_TR.UTF-8
  LC_ALL=
  casaba@ship-macbook:/backups$ sudo locale-gen c
  ca_AD   ca_ES.UTF-8 ca_IT   ckb_IQ  cs_CZ 
  cy_GB.UTF-8
  ca_AD.UTF-8 ca_ES@valencia  ca_IT.UTF-8 cmn_TW  cs_CZ.UTF-8   
  
  ca_ES   ca_FR   ce_RU   crh_UA  cv_RU 
  
  ca_ES@euro  ca_FR.UTF-8 chr_US  csb_PL  cy_GB 
  
  casaba@ship-macbook:/backups$ sudo locale-gen C.UTF-8 
  Generating locales (this might take a while)...
C.UTF-8... done
  Generation complete.
  casaba@ship-macbook:/backups$ update-locale LANG=C.UTF8
  casaba@ship-macbook:/backups$ sudo update-locale LANG=C.UTF8

  Now the result is (after logout/login)

  ua status
  SERVICE   ENTITLED  STATUSDESCRIPTION
  cc-ealyes   n/a   Common Criteria EAL2 Provisioning Packages
  cis   yes   n/a   Security compliance and audit tools
  esm-infra yes   n/a   UA Infra: Extended Security Maintenance 
(ESM)
  fips  yes   n/a   NIST-certified core packages
  fips-updates  yes   n/a   NIST-certified core packages with priority 
security updates
  livepatch yes   n/a   Canonical Livepatch service

  Enable services with: ua enable 

   Account: il...@fastmail.fm
  Subscription: il...@fastmail.fm

  If Ubuntu 22 ships with current configuration, entire TR will suffer
  considering you can't find http:// downloads anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssl 3.0.2-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Apr 14 10:21:09 2022
  InstallationDate: Installed on 2021-12-29 (105 days ago)
  InstallationMedia: Lubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819)
  SourcePackage: openssl
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago)
  mtime.conffile..etc.ssl.openssl.cnf: 2022-04-10T13:11:20.222505

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


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


[Touch-packages] [Bug 1966800] Re: systemd locks up due to incorrect handling of time zone changes

2022-04-07 Thread Łukasz Zemczak
** Tags removed: rls-jj-incoming

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

Title:
  systemd locks up due to incorrect handling of time zone changes

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  New
Status in systemd package in Fedora:
  Unknown

Bug description:
  Recently on systems in Ireland, systemd became unresponsive due the
  change from GMT to Irish Standard Time. This is due to Ireland being
  unique in having their standard time during the summer, unlike most
  regions.

  Related to: https://bugzilla.redhat.com/show_bug.cgi?id=1941335
  Fixed by: 
https://github.com/systemd/systemd-stable/commit/a8b66ca9af811148b67ee952ab32748f88b8bba3

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


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


[Touch-packages] [Bug 1926860] Re: XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

2022-04-07 Thread Łukasz Zemczak
** Changed in: systemd (Ubuntu)
   Status: Confirmed => In Progress

** Tags removed: rls-jj-incoming

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

Title:
  XP Pen Star 03 graphic tablet not running on Ubuntu later than 18.04

Status in systemd package in Ubuntu:
  In Progress
Status in xserver-xorg-input-libinput package in Ubuntu:
  Invalid
Status in xserver-xorg-input-libinput package in Arch Linux:
  New

Bug description:
  The XP Pen Star 03 graphics tablet worked on Ubuntu 18.04 but is no
  longer working in any other Version of Ubuntu released afterwards.

  I tested 20.04 and am currently running 21.04. it is recognized but in
  the system settings it says not tablet and not stylus found.

  The terminal gives me the info that the UC-Logic TABLET 1060N  is
  plugged in. In the system settings it shows "Wacom Tablet" but says
  not tablet and stylus pen are recognized.

  It works perfectly fine on my 18.04 install.

  I found a few reports on the internet with the exact same issue. They
  installed some evdev driver and somehow managed to resolve. I was not
  able to do so yet.

  If the tablet used to work out of the box with Ubuntu 18.04 I wonder
  why it is no longer working.

  There is also a XP Pen Star 03 V2 by now. The tablet look identical
  but the hardware or firmware must be different.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubuntu-release-upgrader-core 1:21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  2 03:16:00 2021
  InstallationDate: Installed on 2021-04-15 (16 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210415)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubuntu-release-upgrader
  Symptom: dist-upgrade
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Touch-packages] [Bug 1968047] Re: Ubuntu 22.04 Beta - Unable to compile ruby version 2.7.5, 3.0.3 and 3.3.3 problem with the openssl-dev package

2022-04-07 Thread Łukasz Zemczak
** Tags removed: rls-jj-incoming

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

Title:
  Ubuntu 22.04 Beta - Unable to compile ruby version 2.7.5, 3.0.3 and
  3.3.3  problem with the openssl-dev package

Status in openssl package in Ubuntu:
  New

Bug description:
  This problem only exists in Ununto 22.04 beta
  When attempting to comple ruby (any version - I have tried 2.7.5, 3.0.3 & 
3.1.1) it fails becuase of a problem with the libssl-dev package.  The previous 
version of Ubuntu used version 1.1.1.  The new version uses 
openssl-dev/libssl-dev 3.0.2

  $ lsb_release -rd
  Description:Ubuntu Jammy Jellyfish (development branch)
  Release:22.04

  sudo apt-cache policy libssl-dev
  libssl-dev:
Installed: 3.0.2-0ubuntu1
Candidate: 3.0.2-0ubuntu1
Version table:
   *** 3.0.2-0ubuntu1 500
  500 http://au.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

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


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


[Touch-packages] [Bug 1967593] Re: kernel modules going missing after reboot

2022-04-07 Thread Łukasz Zemczak
** Tags removed: rls-jj-incoming

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

Title:
  kernel modules going missing after reboot

Status in cloud-initramfs-tools package in Ubuntu:
  Confirmed
Status in linux-kvm package in Ubuntu:
  New
Status in linux-lowlatency package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  EDIT: There are no accurate results in the package search, but it is
  for the kernel shown below Linux 5.15.0-23-generic x86_64. Also for
  the low latency kernel and other versions 5.4, 5.13, 5.14, 5.17. So it
  is not kernel specific. It must be a problem with configuration, but
  reinstalling doesnt fix it.

  EDIT2: it turns out this is caused by the cloud-initramfs-copymods
  package mounting over modules locations. Removed it and reinstalled
  kernel modules package (extras didnt seem necessary, but probably
  prudent too).


  This affects several different kernels I've tried in 22.04.

  This post basically sums it up:
  
https://unix.stackexchange.com/questions/405146/removed-lib-modules-folder-after-every-reboot
  detailed answer: https://unix.stackexchange.com/a/499580/346155

  And this one from upgrading from 20.04 to 22.04:
  
https://askubuntu.com/questions/1400470/kernel-module-not-getting-installed-after-upgrade

  Basically, for some reason the kernel modules are being mounted over
  after reboot.

  My image was built on top of a cloud-init image, but removing the recommeded 
package "cloud-initramfs-copymods" that mounts over modules didnt work for me. 
Adding the snd_hda_intel module to the boot config /etc/initramfs-tools/modules 
did fix my issue for this module. But how many others will not be available?
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-23-generic 
root=UUID=5d51cbd2-a1de-48f6-b8b6-00709c787fa0 ro
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-23-generic N/A
   linux-backports-modules-5.15.0-23-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  RfKill:

  Tags:  jammy uec-images
  Uname: Linux 5.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-04-01 (1 days ago)
  UserGroups: libvirt sudo
  WifiSyslog:

  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.13.0-1ubuntu1.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-4.2
  dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.13.0-1ubuntu1.1:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-4.2
  dmi.sys.vendor: QEMU
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2189 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 22.04
  IwConfig:
   lono wireless extensions.

   enp1s0no wireless extensions.

   virbr0no wireless extensions.
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, 

[Touch-packages] [Bug 1947311] Re: Unexpected partition growth on first boot on impish for raspberry pi

2022-04-06 Thread Łukasz Zemczak
Not an expert in seeds, but the changes made sense. Merged and pushed!

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

Title:
  Unexpected partition growth on first boot on impish for raspberry pi

Status in cloud-init package in Ubuntu:
  Invalid
Status in linux-raspi package in Ubuntu:
  Invalid
Status in ubuntu-image package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Hi,

  On Raspberry Pi since Impish, the partition always grows even if I set
  the following in user-data of cloud-init.

  growpart:
mode: off
devices: ['/']

  I have tested this on 21.04, and it works, but is broken on 21.10.
  (partition always grows)

  I've also tested this in KVM on amd64, and it works (partition does
  NOT grow).

  This is a problem for me because I am using runcmd in cloud init to
  migrate my drive to LVM/LUKS, and the partitioning step fails because
  the drive is already full.

  Cheers,
  Noah

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


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


[Touch-packages] [Bug 1967620] Re: [FFe] LXC 5.0 LTS

2022-04-06 Thread Łukasz Zemczak
** Changed in: lxc (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  [FFe] LXC 5.0 LTS

Status in lxc package in Ubuntu:
  Triaged

Bug description:
  LXC 5.0 LTS will very soon be released.
  The upstream release has been held up due to an incomplete port to meson (and 
deprecation of autotools), it's otherwise been ready to go for a few months.

  As far as LXC releases go, it's a very light one. Comparing it to
  current 4.0.12, we have:

   - No liblxc API changes at all (no new symbols or changes to headers)
   - Addition of a few configuration keys:
 - lxc.cgroup.dir.monitor.pivot
 - lxc.cgroup.dir.monitor
 - lxc.cgroup.dir.container.inner
 - lxc.cgroup.dir.container
 - lxc.time.offset.boot
 - lxc.time.offset.monotonic
 - veth.n_rxqueues
 - veth.n_txqueues
 - veth.vlan.id
 - veth.vlan.tagged.id
   - Port to meson (replacing autotools)

  Diffstat:
  ```
  stgraber@dakara:~/data/code/lxc/lxc (lxc/master)$ git diff lxc-4.0.12.. . | 
diffstat
   .gitignore |1 
   config/init/systemd/Makefile.am|   10 +
   config/init/systemd/lxc-net.service.in |1 
   configure.ac   |5 
   doc/api-extensions.md  |9 +
   doc/ja/lxc.container.conf.sgml.in  |  129 -
   doc/lxc.container.conf.sgml.in |   98 
   lxc.spec.in|1 
   meson.build|4 
   src/lxc/api_extensions.h   |3 
   src/lxc/cgroups/cgfsng.c   |   93 +++
   src/lxc/cmd/lxc-checkconfig.in |6 -
   src/lxc/cmd/lxc_monitord.c |   59 +
   src/lxc/cmd/lxc_user_nic.c |2 
   src/lxc/conf.c |   11 +
   src/lxc/confile.c  |  664 
+---
   src/lxc/network.c  |   18 ++-
   src/lxc/network.h  |4 
   src/lxc/terminal.c |1 
   src/lxc/terminal.h |3 
   src/lxc/tools/lxc_autostart.c  |8 +
   src/lxc/utils.c|3 
   src/tests/aa.c |2 
   src/tests/config_jump_table.c  |2 
   src/tests/containertests.c |2 
   src/tests/get_item.c   |   90 ++-
   src/tests/getkeys.c|2 
   src/tests/locktests.c  |2 
   src/tests/lxc-test-utils.c |   16 +-
   src/tests/meson.build  |  534 
++
   src/tests/mount_injection.c|2 
   src/tests/parse_config_file.c  |   17 ++
   src/tests/reboot.c |2 
   src/tests/share_ns.c   |4 
   src/tests/snapshot.c   |2 
   35 files changed, 1676 insertions(+), 134 deletions(-)
  ```

  LXC 4.0.12 which we released on Feb 1st has all the bugfixes and other
  non-feature changes from LXC 5.0, making this quite a small and
  generally safe delta.

  The new features can be roughly categorized as:
   - Improve flexibility in cgroup configuration (make naming of /sys/fs/cgroup 
directories configurable)
   - Add support for the time namespace (clock offset)
   - Add support for configuring (basic sysctl) the number of veth queues
   - Add support for bridge VLAN filtering on veth devices

  
  LXC 5.0 will be an upstream LTS with a support duration matching that of 
Ubuntu 22.04 or until June 2027. Jammy currently ships LXC 4.0.12 which is only 
supported until June 2025 and will not see new bugfix releases after LXC 5.0 
comes out (only security).

  LXC is unseeded and in universe these days. The main goal of putting
  the new LTS in the release is to reduce the maintenance cost for the
  Ubuntu LTS and to satisfy some of Canonical's customers that are
  directly using those packages and would expect a consistent set of LTS
  releases.

  LXCFS 5.0 is already in jammy and LXD 5.0 has similarly been released,
  though that one ships exclusively as a snap.


  If we can get general agreement that getting this LXC release in
  Ubuntu 22.04 is fine, what I can do to fast track things a bit is
  upload a 5.0~git-hash version which still relies on autotools, get
  that do clear autopkgtest and CI and then follow that up with the
  final 5.0 with the meson port as soon as it's complete on our side
  (expecting about a week, just got two directories to port).

  As a reminder, this is all unseeded and in universe, so overall impact
  should be quite low.

  Full upstream 

[Touch-packages] [Bug 1902464] Update Released

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

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

Title:
  The rear panel of Lenovo P620 doesn't support more than one audio
  device at the same time

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  == SRU Justification ==
  [Impact]
  On P620, only single port can work on rear panel. For example, when the 
Line-Out is plugged, the Mic won't work anymore.

  [Fix]
  Use upstream version of UCM to handle port priority correctly, instead of 
separate ports into different profiles.

  [Test]
  Once the UCM is in place, all three ports of rear panel work correctly.

  [Where problems could occur]
  UCM is not a static thing - it's actually interpreted differently at higher 
level. So any change in userspace daemons other than PulseAudio may not like 
the change and can interpret the UCM in another way.

  == Original Bug Report ==
  After backporting following patches from PA and alsa-ucm-conf and then it 
works.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/290
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/354
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/355

  https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/USB-
  Audio [landed by aa74f4c12eefcc98582572d2fc48982cf7478b51]

  Here is the test PPA:
  https://launchpad.net/~os369510/+archive/ubuntu/oem-package-test

  Since the upstream not yet accepted those patches, the regression
  potential may quite high.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1902464/+subscriptions


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


[Touch-packages] [Bug 1966418] Re: [jammy regression] Evolution does not display message content anymore

2022-03-31 Thread Łukasz Zemczak
** Changed in: mesa (Ubuntu)
Milestone: None => ubuntu-22.04

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

Title:
  [jammy regression] Evolution does not display message content anymore

Status in Gnome DevHelp:
  Invalid
Status in Mesa:
  Unknown
Status in Webkit:
  Confirmed
Status in epiphany-browser package in Ubuntu:
  Invalid
Status in evolution package in Ubuntu:
  Invalid
Status in gnome-control-center package in Ubuntu:
  Invalid
Status in liferea package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  Impact
  --
  All webkit using apps for affected users display a blank screen.

  Original Bug Report
  ---
  Evolution has suddenly stopped displaying message contents on the last 24h. 
Starting it up from the command line shows this output:

  ```
  EGLDisplay Initialization failed: EGL_NOT_INITIALIZED
  Cannot create EGL context: invalid display (last error: EGL_SUCCESS)
  ```

  I don't know if it's related, but googling around shows some webkitgtk
  hits on this error.

  The email contents are however clickable. They're just not rendered to
  screen (see attached file).

  Deleting the evolution folders from `~/.config`, `~/.cache` and
  `~/.local/share` does not help.

  Email accounts are all google, configured through gnome online
  accounts.

  Workaround #1
  -
  You can run the app from the command line with
  WEBKIT_DISABLE_COMPOSITING_MODE=1 evolution
  (Replace evolution with the name of the webkit app you are trying to use)

  Workaround #2
  -
  Log out.
  Select your name on the login screen.
  Click the gear button and choose Ubuntu on Xorg.
  Enter your password to finish logging in.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evolution 3.44.0-1
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: sway
  Date: Fri Mar 25 10:55:49 2022
  SourcePackage: evolution
  UpgradeStatus: Upgraded to jammy on 2022-03-01 (24 days ago)

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


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


[Touch-packages] [Bug 1952107] Proposed package removed from archive

2022-03-22 Thread Łukasz Zemczak
The version of evolution-data-server in the proposed pocket of Focal
that was purported to fix this bug report has been removed because one
or more bugs that were to be fixed by the upload have failed
verification and been in this state for more than 10 days.

** Tags removed: verification-needed

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Confirmed
Status in evolution-data-server source package in Focal:
  Confirmed
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions


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


[Touch-packages] [Bug 1952107] Proposed package removed from archive

2022-03-22 Thread Łukasz Zemczak
The version of evolution-data-server in the proposed pocket of Focal
that was purported to fix this bug report has been removed because one
or more bugs that were to be fixed by the upload have failed
verification and been in this state for more than 10 days.

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Confirmed
Status in evolution-data-server source package in Focal:
  Confirmed
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions


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


[Touch-packages] [Bug 1952107] Proposed package removed from archive

2022-03-22 Thread Łukasz Zemczak
The version of evolution in the proposed pocket of Focal that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Confirmed
Status in evolution-data-server source package in Focal:
  Confirmed
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions


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


[Touch-packages] [Bug 1952107] Proposed package removed from archive

2022-03-22 Thread Łukasz Zemczak
The version of evolution in the proposed pocket of Focal that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Confirmed
Status in evolution-data-server source package in Focal:
  Confirmed
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions


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


[Touch-packages] [Bug 1952107] Proposed package removed from archive

2022-03-22 Thread Łukasz Zemczak
The version of evolution-data-server in the proposed pocket of Focal
that was purported to fix this bug report has been removed because one
or more bugs that were to be fixed by the upload have failed
verification and been in this state for more than 10 days.

** Changed in: evolution-data-server (Ubuntu Focal)
   Status: Fix Committed => Confirmed

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Confirmed
Status in evolution-data-server source package in Focal:
  Confirmed
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions


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


[Touch-packages] [Bug 1952107] Proposed package removed from archive

2022-03-22 Thread Łukasz Zemczak
The version of evolution in the proposed pocket of Focal that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

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

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Confirmed
Status in evolution-data-server source package in Focal:
  Confirmed
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions


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


[Touch-packages] [Bug 1965791] Re: Update tzdata to version 2022a

2022-03-22 Thread Łukasz Zemczak
Hello Brian, or anyone else affected,

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

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

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

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

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

** Changed in: tzdata (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Update tzdata to version 2022a

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Impish:
  Fix Committed
Status in tzdata source package in Jammy:
  In Progress

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza | grep 2022

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); 
print(str(tz.utcoffset(datetime(2022, 3, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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


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


[Touch-packages] [Bug 1965791] Please test proposed package

2022-03-22 Thread Łukasz Zemczak
Hello Brian, or anyone else affected,

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

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

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

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

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

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

Title:
  Update tzdata to version 2022a

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Impish:
  Fix Committed
Status in tzdata source package in Jammy:
  In Progress

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza | grep 2022

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); 
print(str(tz.utcoffset(datetime(2022, 3, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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


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


[Touch-packages] [Bug 1965791] Re: Update tzdata to version 2022a

2022-03-22 Thread Łukasz Zemczak
Hello Brian, or anyone else affected,

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

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

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

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

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

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

** Tags added: verification-needed verification-needed-impish

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

** Tags added: verification-needed-focal

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

Title:
  Update tzdata to version 2022a

Status in tzdata package in Ubuntu:
  In Progress
Status in tzdata source package in Bionic:
  Fix Committed
Status in tzdata source package in Focal:
  Fix Committed
Status in tzdata source package in Impish:
  Fix Committed
Status in tzdata source package in Jammy:
  In Progress

Bug description:
  New upstream version affecting the following timestamp:

  $region/$timezone = Asia/Gaza

  Verification is done with 'zdump'. The first timezone that gets
  changed in the updated package is dumped with 'zdump -v
  $region/$timezone_that_changed' (this needs to be greped for in
  /usr/share/zoneinfo/). [For example: 'zdump -v Asia/Gaza'.] This is
  compared to the same output after the updated package got installed.
  If those are different the verification is considered done.

  [Test Case for all releases]
  1) zdump -v Asia/Gaza | grep 2022

  For releases with ICU timezone data verification is done using the following 
with dates before and after the change:
  [Test Case for releases >= 20.04 LTS]
  1) sudo apt-get install python3-icu
  2) python3 -c 'from datetime import datetime; from icu import ICUtzinfo, 
TimeZone; tz = ICUtzinfo(TimeZone.createTimeZone('Asia/Gaza')); 
print(str(tz.utcoffset(datetime(2022, 3, 26'

  Additionally, an upstream update of tzdata removed the 'old' SystemV
  timezones, so we should ensure that they are kept in Ubuntu 20.04 LTS
  and earlier releases. Subsequently, these should be checked for using
  the following:

  [Test Case for releases <= 20.04 LTS]
  diff <(zdump -v America/Phoenix | cut -d' ' -f2-) <(zdump -v SystemV/MST7 | 
cut -d' ' -f2-)

  Nothing should be returned by the above command.

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


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


[Touch-packages] [Bug 1961427] Re: zlib: compressBound() returns an incorrect result on z15

2022-03-21 Thread Łukasz Zemczak
Currently dropping 1:1.2.11.dfsg-2ubuntu8 from jammy-proposed per the
uploader's request:

09:55 < fheimes> Dear ubuntu-release team, could you please drop/remove zlib 
2.11.dfsg-2ubuntu8 from jammy-proposed (LP#1961427)?
09:55 < fheimes> An incompatibility with HTSlib was detected, I'm in contact 
with the initial reporter and author of the patch to get that solved, but this 
might take a while (hence I restart from scratch on this is probably best).

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

Title:
  zlib: compressBound() returns an incorrect result on z15

Status in Ubuntu on IBM z Systems:
  New
Status in zlib package in Ubuntu:
  In Progress
Status in zlib source package in Focal:
  New
Status in zlib source package in Impish:
  New
Status in zlib source package in Jammy:
  In Progress

Bug description:
  SRU Justification:
  ==

  [Impact]

  * zlib: compressBound() returns an incorrect result on IBM z15
  hardware.

  * Passing the result of compressBound() to compress() results
    in an error code.

  * This is because compressBound() is not adjusted for DFLTCC.

  [Fix]

  * Adjust compressBound() for DFLTCC like it's already done
    for deflateBound().

  * Since zlib project does not accept patches at the moment,
    the fix has been integrated into the DFLTCC pull request:
    https://github.com/madler/zlib/pull/410
    The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  * The fix extracted out of the above is:
    
https://launchpadlibrarian.net/589857296/debdiff_zlib_1.2.11.dfsg-2ubuntu7_to_zlib_1.2.11.dfsg-2ubuntu8_jammy.diff

  [Test Plan]

  * An IBM z15 system (LPAR, z/VM guest or KVM virtual machine)
    with Ubuntu Server 21.10 (or 22.04).

  * A test can be done  based on the following C test program:
    #include 
    #include 
    #include 
    int main() {
    Bytef in_buf[128], out_buf[1024];
    for (size_t i = 0; i < sizeof(in_buf); i++)
    in_buf[i] = rand();
    uLongf dest_len = compressBound(sizeof(in_buf));
    assert(dest_len <= sizeof(out_buf));
    int ret = compress(out_buf, _len,
   in_buf, sizeof(in_buf));
    assert(ret == Z_OK);
    }

  * The test needs to be done by IBM, due to the requirements
    for the special z15 hardware.

  * A successful test was just completed, based on the version in jammy-
  proposed, which is at the same code level that the impish version this
  SRU is targeted for.

  [Where problems could occur]

  * If the adjustment of compressBound() for DFLTCC is done
    erroneously the issue can still be present or in worst case
    even affect Z systems other than z15 only.

  * The compression can become errorneous with the new changes,
    e.g. in compressBound.

  * Mistakes in dfltcc_free_window OF and especially DEFLATE_BOUND_COMPLEN,
    (incl. the bit definitions), may cause various and unforseen defects.

  * Any build time issues that might have been introduced by this patch
    can be identified by a test build; this was done and is available here:
    https://launchpad.net/~fheimes/+archive/ubuntu/lp1961427

  [Other Info]

  * Ubuntu jammy, impish and focal are affected.
  __

  Description:   zlib: compressBound() returns an incorrect result on z15
  Symptom:   Passing the result of compressBound() to compress()
     results in an error code.
  Problem:   compressBound() is not adjusted for DFLTCC.
  Solution:  Adjust compressBound() for DFLTCC like it's already done
     for deflateBound(). Since zlib project does not accept
     patches at the moment, the fix has been integrated into
     the DFLTCC pull request:
     https://github.com/madler/zlib/pull/410
     The commitid is b25781e735363e04f6c56e21431c47e4afc50b17.

  Reproduction:  z15 only:
     #include 
     #include 
     #include 
     int main() {
     Bytef in_buf[128], out_buf[1024];
     for (size_t i = 0; i < sizeof(in_buf); i++)
     in_buf[i] = rand();
     uLongf dest_len = compressBound(sizeof(in_buf));
     assert(dest_len <= sizeof(out_buf));
     int ret = compress(out_buf, _len,
    in_buf, sizeof(in_buf));
     assert(ret == Z_OK);
     }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1961427/+subscriptions


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


[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

2022-03-17 Thread Łukasz Zemczak
Thank you for the detailed explanation Fabio, the impact of the bug is
now much better understood. Can I ask for an update of the Impact field
in the SRU description above? In a summary, but also getting into a bit
more details about how this differs from focal+ etc.

One thing I worry about in this SRU is basically what has been mentioned by Ben 
Hutchings as a follow up to the patch forwarded upstream:
https://lists.zytor.com/archives/klibc/2021-December/004635.html

I worry that since this issue in ipconfig has been around for *so long* that 
people could have actually started depending on the behavior being as-is. I 
don't think klibc's ipconfig is too widely used (as klibc-utils only has like 2 
reverse-dependencies), but it's still something to consider.
I think I'm not generally against this SRU. Similar to Robie I would like some 
regression potential analysis done and included in the [Where problems could 
occur] section - one of them being what I mentioned above. Can you think of any 
other issues this change could cause? In integration or in different parts of 
the code? Can we mitigate this somehow by performing some additional testing?

If you could modify the two sections of the SRU description, I'd be
ready to accept this into bionic-proposed.

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

Title:
  ipconfig does not honour user-requested timeouts in some cases

Status in klibc package in Ubuntu:
  New
Status in klibc source package in Bionic:
  Incomplete

Bug description:
  
  [Impact]
  In some cases, ipconfig can take a longer time than the user-specified 
timeouts, causing unexpected delays.

  [Test Plan]
  Any situation where ipconfig encounters an error sending the DHCP packet, it 
will automatically set a delay of 10 seconds, which could be longer than the 
user-specified timeout. It can be reproduced by creating a dummy interface and 
attempting to run ipconfig on it with a timeout value of less than 10:

  # ip link add eth1 type dummy
  # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
  Thu Nov 18 04:46:13 EST 2021
  IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  Thu Nov 18 04:46:23 EST 2021

  ^ Notice above, ipconfig thinks that it waited 2 seconds, but the
  timestamps show an actual delay of 10 seconds.

  [Where problems could occur]
  Please see reproduction steps above. We are seeing this in production too 
(see comment #2).

  [Other Info]
  A patch to fix the issue is being proposed here. It is a safe fix - it only 
checks before going into sleep that the timeout never exceeds the 
user-requested value.

  [Original Description]

  In some cases, ipconfig can take longer than the user-specified
  timeouts, causing unexpected delays.

  in main.c, in function loop(), the process can go into
  process_timeout_event() (or process_receive_event() ) and if it
  encounters an error situation, will set an attempt to "try again
  later" at time equal now + 10 seconds by setting

  s->expire = now + 10;

  This can happen at any time during the main event loop, which can end
  up extending the user-specified timeout if "now + 10" is greater than
  "start_time + user-specified-timeout".

  I believe a patch like the following is needed to avoid this problem:

  --- a/usr/kinit/ipconfig/main.c
  +++ b/usr/kinit/ipconfig/main.c
  @@ -437,6 +437,13 @@ static int loop(void)

  if (timeout > s->expire - now.tv_sec)
  timeout = s->expire - now.tv_sec;
  +
  +   /* Compensate for already-lost time */
  +   gettimeofday(, NULL);
  +   if (now.tv_sec + timeout > start + loop_timeout) {
  +   timeout = loop_timeout - (now.tv_sec - start);
  +   printf("Lowered timeout to match user request 
= (%d s) \n", timeout);
  +   }
  }

  I believe the current behaviour is buggy. This is confirmed when the
  following line is executed:

  if (loop_timeout >= 0 &&
  now.tv_sec - start >= loop_timeout) {
  printf("IP-Config: no response after %d "
     "secs - giving up\n", loop_timeout);
  rc = -1;
  goto bail;
  }

  'loop_timeout' is the user-specified time-out. With a value of 2, in
  case of error, this line prints:

  IP-Config: no response after 2 secs - giving up

  So it thinks that it waited 2 seconds - however, in reality it had
  actually waited for 10 seconds.

  The suggested code-change ensures that the timeout that is actually
  used never exceeds the user-specified 

[Touch-packages] [Bug 1960863] Update Released

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

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

Title:
  armv8 paca: poly1305 users see segfaults when pointer authentication
  in use on AWS Graviton 3 instances

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

Bug description:
  [Impact]

  Support for hardware pointer authentication for armv8 systems was
  merged in openssl 1.1.1f, but it contains a bug in the implementation
  for poly1305 message authenticated code routines, which causes the
  calling program to fail pointer authentication, which causes the
  program to crash with a segmentation fault.

  You can easily test it by accessing any website that uses poly1305.
  There is no workaround except use a different MAC.

  [Testcase]

  This bug applies to armv8 systems which support pointer
  authentication. Start an armv8 instance, such as a c7g graviton 3
  instance on AWS, and make sure the paca flag is present in lscpu:

  $ grep paca /proc/cpuinfo
  Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp 
cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm 
dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm svebf16 i8mm bf16 dgh rng

  Next, attempt to connect to any website that uses poly1305 MAC.

  $ curl https://services.gradle.org/distributions/gradle-7.2-bin.zip --output 
gradle-7.2.bin
  % Total % Received % Xferd Average Speed Time Time Time Current
  Dload Upload Total Spent Left Speed
  0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Segmentation fault (core dumped)

  There is a test package available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf327917-test

  Install it, and poly1305 operations will no longer segfault.

  [Where problems could occur]

  The patch changes the order of operations for loading the SP and
  checking the AUTIASP against it, from checking the AUTIASP against
  nothing then loading the correct SP to check with, to the correct
  loading the SP and then checking the AUTIASP against the SP.

  This only changes one code path for armv8 systems, and other
  architectures are not affected. This is also only limited to poly1305
  MAC.

  If a regression were to occur, it would only affect users of poly1035
  MAC on armv8 with pacs support.

  [Other info]

  The fix landed upstream in openssl 1.1.1i with the following commit:

  commit 5795acffd8706e1cb584284ee5bb3a30986d0e75
  Author: Ard Biesheuvel 
  Date:   Tue Oct 27 18:02:40 2020 +0100
  Subject: crypto/poly1305/asm: fix armv8 pointer authentication
  Link: 
https://github.com/openssl/openssl/commit/5795acffd8706e1cb584284ee5bb3a30986d0e75

  This commit is already present in Impish onward. Only Focal needs the
  fix.

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


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


[Touch-packages] [Bug 1960947] Update Released

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

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

Title:
  Graphical issues for GtKGL in software rendering

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Focal:
  Fix Committed

Bug description:
  * Issue

  GTK applications using GL graphic show corruption problems under
  software rendering

  
  * Test case

  1. install gtk-3-examples
  2. $ LIBGL_ALWAYS_SOFTWARE=1 gtk3-demo
  3. select the gl example, it should render without issues

  * Regression potentiel

  The change is in the GL backend so check for rendering issues in GTK
  softwares using GL, including flutter applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960947/+subscriptions


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


[Touch-packages] [Bug 1960034] Update Released

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

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  Fix Committed
Status in systemd source package in Impish:
  Invalid

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-29.32 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220204_114518_6b600@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220201_135548_7f169@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220201_110103_b02e4@/log.gz

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


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


[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

2022-02-16 Thread Łukasz Zemczak
Since the patch has been submitted upstream and there was no hard
objection to it, I think you can proceed in preparing the SRU and
getting it uploaded for SRU review. Just be sure to include the upstream
link in the Forwarded: section of the patch. Thanks!

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

Title:
  ipconfig does not honour user-requested timeouts in some cases

Status in klibc package in Ubuntu:
  New
Status in klibc source package in Bionic:
  In Progress

Bug description:
  
  [Impact]
  In some cases, ipconfig can take a longer time than the user-specified 
timeouts, causing unexpected delays.

  [Test Plan]
  Any situation where ipconfig encounters an error sending the DHCP packet, it 
will automatically set a delay of 10 seconds, which could be longer than the 
user-specified timeout. It can be reproduced by creating a dummy interface and 
attempting to run ipconfig on it with a timeout value of less than 10:

  # ip link add eth1 type dummy
  # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
  Thu Nov 18 04:46:13 EST 2021
  IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  Thu Nov 18 04:46:23 EST 2021

  ^ Notice above, ipconfig thinks that it waited 2 seconds, but the
  timestamps show an actual delay of 10 seconds.

  [Where problems could occur]
  Please see reproduction steps above. We are seeing this in production too 
(see comment #2).

  [Other Info]
  A patch to fix the issue is being proposed here. It is a safe fix - it only 
checks before going into sleep that the timeout never exceeds the 
user-requested value.

  [Original Description]

  In some cases, ipconfig can take longer than the user-specified
  timeouts, causing unexpected delays.

  in main.c, in function loop(), the process can go into
  process_timeout_event() (or process_receive_event() ) and if it
  encounters an error situation, will set an attempt to "try again
  later" at time equal now + 10 seconds by setting

  s->expire = now + 10;

  This can happen at any time during the main event loop, which can end
  up extending the user-specified timeout if "now + 10" is greater than
  "start_time + user-specified-timeout".

  I believe a patch like the following is needed to avoid this problem:

  --- a/usr/kinit/ipconfig/main.c
  +++ b/usr/kinit/ipconfig/main.c
  @@ -437,6 +437,13 @@ static int loop(void)

  if (timeout > s->expire - now.tv_sec)
  timeout = s->expire - now.tv_sec;
  +
  +   /* Compensate for already-lost time */
  +   gettimeofday(, NULL);
  +   if (now.tv_sec + timeout > start + loop_timeout) {
  +   timeout = loop_timeout - (now.tv_sec - start);
  +   printf("Lowered timeout to match user request 
= (%d s) \n", timeout);
  +   }
  }

  I believe the current behaviour is buggy. This is confirmed when the
  following line is executed:

  if (loop_timeout >= 0 &&
  now.tv_sec - start >= loop_timeout) {
  printf("IP-Config: no response after %d "
     "secs - giving up\n", loop_timeout);
  rc = -1;
  goto bail;
  }

  'loop_timeout' is the user-specified time-out. With a value of 2, in
  case of error, this line prints:

  IP-Config: no response after 2 secs - giving up

  So it thinks that it waited 2 seconds - however, in reality it had
  actually waited for 10 seconds.

  The suggested code-change ensures that the timeout that is actually
  used never exceeds the user-specified timeout.

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


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


[Touch-packages] [Bug 1949553] Update Released

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

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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


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


[Touch-packages] [Bug 1956915] Update Released

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

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

Title:
  New bugfix release 21.2.6

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Fix Released
Status in mesa source package in Impish:
  Fix Released

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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


[Touch-packages] [Bug 1933491] Re: kmod add zstd support

2022-01-31 Thread Łukasz Zemczak
Quick question from IRC here, for tracking:

17:38 < sil2100> xnox: hey, reviewing the kmod SRU for zstd - I have a question 
re:  the debian/rules change of the added --disable-test-modules
17:38 < sil2100> What effect does it have? Why is that needed?

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

Title:
  kmod add zstd support

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Focal:
  New
Status in kmod source package in Impish:
  Fix Released
Status in kmod source package in Jammy:
  Fix Released
Status in kmod package in Debian:
  New

Bug description:
  [Impact]

   * To safe diskspace, upcoming devel series / hwe kernels may turn on
  zstd kernel module compression. Kmod since impish support zstd
  support. But in order to keep hwe kernels at parity, or allow
  inspecting jammy modules from focal host, it would be beneficial for
  kmod in focal to support zstd compressed modules.

  [Test Plan]

   * Pick any kernel module

   * Compress it with zstd: $ zstd *.ko

   * Check that modinfo can read it: $ modinfo *.ko.zst

  [Where problems could occur]

   * kmod will gain a new dependecy on libzstd1, however it should
  already be present, because dpkg in focal depends on libzstd1 already.

   * initramfs-tools already supports compressed modules, but in focal
  at the moment it does so in an inefficient manner (regresses
  bootspeed), this has been improved in
  https://launchpad.net/ubuntu/+source/initramfs-tools/0.140ubuntu8 and
  is yet to be SRUed into Focal.

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


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


[Touch-packages] [Bug 1951519] Update Released

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

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

Title:
  ubiquity 20.04.15.17 fails to build (test_timezone)

Status in tzdata package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  Fix Released
Status in tzdata source package in Focal:
  Invalid
Status in ubiquity source package in Focal:
  Fix Released
Status in tzdata source package in Jammy:
  Invalid
Status in ubiquity source package in Jammy:
  Fix Released

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  When trying to build ubiquity from source,

  sudo apt update
  sudo apt -y dist-upgrade
  sudo apt-get build-dep ubiquity
  sudo apt install -y fakeroot
  apt source ubiquity
  cd ubiquity-*
  dpkg-buildpackage -us -uc
  [...]
  test_has_battery (test_upower.UPowerTests) ... ok
  test_check_hostname (test_usersetup.UserSetupTests) ... ok
  test_check_username (test_usersetup.UserSetupTests) ... ok
  test_default_username (test_usersetup.UserSetupTests) ... ok
  test_default_username_strips_invalid_characters 
(test_usersetup.UserSetupTests) ... ok
  test_hostname_check (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
  test_unicode (test_usersetup.UserSetupTests) ... ok

  ==
  FAIL: test_city_entry (test_timezone.TimezoneTests)
  --
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
  return func(*args, **keywargs)
    File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in 
test_city_entry
  self.assertEqual(set(results), set(expected))
  AssertionError: Items in the first set but not the second:
  ('Eastern', 'Bahamas')
  Items in the second set but not the first:
  ('Eastern', 'Canada')

  --
  Ran 89 tests in 19.319s

  FAILED (failures=1)
  xauth/Xrdb output:
  make: *** [debian/rules:228: tests] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  It keeps failing regardless of release.

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


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


[Touch-packages] [Bug 1952107] Update Released

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

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

Title:
  Google Contacts API Deprecated

Status in evolution-data-server:
  Unknown
Status in evolution package in Ubuntu:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution source package in Focal:
  Fix Committed
Status in evolution-data-server source package in Focal:
  Fix Committed
Status in evolution source package in Impish:
  Fix Released
Status in evolution-data-server source package in Impish:
  Fix Released

Bug description:
  * Impact
  The google contacts integration with the GNOME component will stop working 
since it relies on an API which is going to be shutdown

  * Testcase
  - use evolution
  - add a google account
  - go the contacts section

  The contacts stored on the google account should be listed, no error
  should be displayed

  * Regression potential
  The patch changes the google contact backend so any potential issue is likely 
to be with contacts integration.

  

  I opened Evolution today and a red banner appeared on top with the
  following message:

  > Failed to connect address book “ : Contacts”

  > Invalid request URI or header, or unsupported nonstandard parameter:
  Contacts API is being deprecated. Migrate to People API to retain
  programmatic access to Google Contacts. See
  https://developers.google.com/people/contacts-api-migration.

  I found the upstream bug report for this[0], which references the commit[1] 
that fixes it.
  However, that commit is in release 3.42.0, whereas Ubuntu 21.10 currently has 
3.40.4-1. Is it possible to backport this commit so that Evolution will 
continue to work properly?

  [0]: https://gitlab.gnome.org/GNOME/evolution/-/issues/1658
  [1]: 
https://gitlab.gnome.org/GNOME/evolution-data-server/-/commit/d63a1ce3921a6a6c573a6a

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1952107/+subscriptions


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


[Touch-packages] [Bug 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.

2022-01-13 Thread Łukasz Zemczak
Sponsored the change, it should now be in the focal Unapproved queue,
waiting from someone from the SRU team to review and accept. I also
pushed the change to the git repository.

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

Title:
  [SRU] network-manager can’t modify MTU automatically based on what
  ModemManager exposes for WWAN modems.

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  Some 4G/5G mobile networks(for ex., AT) requires a specific MTU
  setting, this setting will be exposed by the ModemManager for network-
  manger to configure the MTU of the modem network interface .

  The current modem-manager v1.22.10-1ubuntu2.2  in focal can’t pass
  AT’s modem system certification.

  [Fix]

  This upstream patch can resolve this bug:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631

  [Test Plan]

  1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an
  AT SIM card in US

  2. Enable 4G modem and connect to AT apn

  $ sudo mmcli -i 0 --pin=
  $ sudo mmcli --modem 0 --enable
  $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome"
  $ sudo nmcli radio wwan on
  $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn 
emome
  $ sudo nmcli connection up id mymodem

  3. Check if the MTU got from the following results are the same:

  $ sudo mmcli --bearer 5 | mtu
  $ ifconfig mhi_mbim0 | grep mtu

  * Expected result:
  Both MTUs are the same value 1430
  * Actual tested result:
  Different values (one is 1430 , another is 1500)

  [Where problems could occur]

  Very low.
  This is a simple fix: network-manager gets the MTU from the ModemManager then 
sets the MTU of the modem interface.

  [Other info]

  1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+subscriptions


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


[Touch-packages] [Bug 1951519] Re: ubiquity 20.04.15.17 fails to build (test_timezone)

2022-01-12 Thread Łukasz Zemczak
Hello Ark74, or anyone else affected,

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

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

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

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

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

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

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

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

Title:
  ubiquity 20.04.15.17 fails to build (test_timezone)

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

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  When trying to build ubiquity from source,

  sudo apt update
  sudo apt -y dist-upgrade
  sudo apt-get build-dep ubiquity
  sudo apt install -y fakeroot
  apt source ubiquity
  cd ubiquity-*
  dpkg-buildpackage -us -uc
  [...]
  test_has_battery (test_upower.UPowerTests) ... ok
  test_check_hostname (test_usersetup.UserSetupTests) ... ok
  test_check_username (test_usersetup.UserSetupTests) ... ok
  test_default_username (test_usersetup.UserSetupTests) ... ok
  test_default_username_strips_invalid_characters 
(test_usersetup.UserSetupTests) ... ok
  test_hostname_check (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_bogus_dns (test_usersetup.UserSetupTests) ... ok
  test_hostname_check_exists (test_usersetup.UserSetupTests) ... ok
  test_unicode (test_usersetup.UserSetupTests) ... ok

  ==
  FAIL: test_city_entry (test_timezone.TimezoneTests)
  --
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/mock/mock.py", line 1330, in patched
  return func(*args, **keywargs)
    File "/home/ark/ubiquity-20.04.15.17/tests/test_timezone.py", line 58, in 
test_city_entry
  self.assertEqual(set(results), set(expected))
  AssertionError: Items in the first set but not the second:
  ('Eastern', 'Bahamas')
  Items in the second set but not the first:
  ('Eastern', 'Canada')

  --
  Ran 89 tests in 19.319s

  FAILED (failures=1)
  xauth/Xrdb output:
  make: *** [debian/rules:228: tests] Error 1
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2

  It keeps failing regardless of release.

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


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


[Touch-packages] [Bug 1956915] Please test proposed package

2022-01-10 Thread Łukasz Zemczak
Hello Timo, or anyone else affected,

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

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

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

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

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

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

Title:
  New bugfix release 21.2.6

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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


[Touch-packages] [Bug 1956915] Re: New bugfix release 21.2.6

2022-01-10 Thread Łukasz Zemczak
Hello Timo, or anyone else affected,

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

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

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

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

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

** Changed in: mesa (Ubuntu Impish)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

** Tags added: verification-needed-focal

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

Title:
  New bugfix release 21.2.6

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Focal:
  Fix Committed
Status in mesa source package in Impish:
  Fix Committed

Bug description:
  [Impact]

  This is the last point-release of the 21.2.x-series, we should put it
  in impish so latest bugfixes would get there, and in focal for 20.04.4
  image.

  [Test case]

  Install the updates, test desktop use and some basic games etc on at
  least AMD and Intel hw.

  [Where things could go wrong]

  It's possible that some apps (like games) might regress on some hw,
  but there should not be a big risk for more wider bugs appearing in
  this update, since upstream and vendor (Intel) CI machinery have
  tested these.

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


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


[Touch-packages] [Bug 1949553] Re: Backport packages for 20.04.4 HWE stack

2022-01-10 Thread Łukasz Zemczak
Hello Timo, or anyone else affected,

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

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

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

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

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

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

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

Title:
  Backport packages for 20.04.4 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Fix Committed
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Released

Bug description:
  [Impact]

  These are needed for 20.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: adds some new api, no changes to old stuff

  llvm-13: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

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


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


[Touch-packages] [Bug 1955797] Re: [SRU] network-manager can’t modify MTU automatically based on what ModemManager exposes for WWAN modems.

2022-01-10 Thread Łukasz Zemczak
Hey Jerry! This looks good and I can certainly sponsor it for you.

One question before I do that though. Looking at the original source commit:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499?commit_id=212758ea05a4c13d65f36b55c90aee7919642631
It is mentioned there by some user that MM can also expose this via MTU from 
the IPv6 bearer, not only IPv4. Not sure if this is an use case we are 
concerned about, and if there was a follow up patch for this use case.
Can you take a look and give me a sign if we should still continue as-is? 
Thanks!

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

Title:
  [SRU] network-manager can’t modify MTU automatically based on what
  ModemManager exposes for WWAN modems.

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Focal:
  New

Bug description:
  [Impact]

  Some 4G/5G mobile networks(for ex., AT) requires a specific MTU
  setting, this setting will be exposed by the ModemManager for network-
  manger to configure the MTU of the modem network interface .

  The current modem-manager v1.22.10-1ubuntu2.2  in focal can’t pass
  AT’s modem system certification.

  [Fix]

  This upstream patch can resolve this bug:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/499/diffs?commit_id=212758ea05a4c13d65f36b55c90aee7919642631

  [Test Plan]

  1. Use a Lenovo platform SE30 including 4G Quectel EM160 modem and an
  AT SIM card in US

  2. Enable 4G modem and connect to AT apn

  $ sudo mmcli -i 0 --pin=
  $ sudo mmcli --modem 0 --enable
  $ sudo mmcli -m 0 --simple-connect="pin=,apn=emome"
  $ sudo nmcli radio wwan on
  $ sudo nmcli connection add type gsm ifname wwan0p2MBIM con-name mymodem apn 
emome
  $ sudo nmcli connection up id mymodem

  3. Check if the MTU got from the following results are the same:

  $ sudo mmcli --bearer 5 | mtu
  $ ifconfig mhi_mbim0 | grep mtu

  * Expected result:
  Both MTUs are the same value 1430
  * Actual tested result:
  Different values (one is 1430 , another is 1500)

  [Where problems could occur]

  Very low.
  This is a simple fix: network-manager gets the MTU from the ModemManager then 
sets the MTU of the modem interface.

  [Other info]

  1. Network-manager v1.30.0-1ubuntu3 in hirsute has included the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1955797/+subscriptions


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


[Touch-packages] [Bug 1946096] Update Released

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

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

Title:
  Support manual firmware upgrading for Foxconn and Quectel modems.

Status in OEM Priority Project:
  In Progress
Status in modemmanager package in Ubuntu:
  Fix Released
Status in modemmanager source package in Focal:
  Fix Released
Status in modemmanager source package in Hirsute:
  Fix Released

Bug description:
  [Impact]

  The modem certification requires that different modem firmware is used for 
different network carrier.
  This needs the firmware upgrading capability during the modem certification 
process.

  The modem manufacture vendors (Foxconn and Quectel) provided utilities to do 
modem's firmware upgrading manually.(LP#1943774, LP#1943780)
  These utilities are verified to be working when the recent versions(> v 
1.18.2) of ModemManager are used with.

  To support manual firmware upgrading on the current Focal release which is 
using ModemManager v 1.16.6, we need to apply some patches from v 1.18.2.
  The requested upstream patches are listed as below:
  * for Quectel EM160 4G
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/83ac82470589a3672092a0ba0be855093b1cf5e2
  * for Foxconn T99W175
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/21ae558fe3600c84b3ca7dcd9bf50a3ba576c7c9
    
**https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/76e700f4fd703f952208993330ab098305c13d6b
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/52bf2c641171ded9e617022f40497c8984520371
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/33e2b023ef01bea9da37ae2beb192f7d92bce47a
    ** 
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/f72046701659073fbfa97516e155865647acb154

  The firmware upgrading was verified using the patched ModemManager v 1.16.6 
with the following 2 modems:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem

  [Test Plan]

  1. Install the Ubuntu image.
  2. Boot and login the system.
  3. Verify if the modem is working
  4. Prepare the modem’s firmware and install the firmware upgrading 
application provided by Foxconn and Quectel
  5. Using the firmware upgrading application to upgrade the modem’s firmware
  6. Verify if the modem’s firmware upgrading is successful
  7. Reboot
  8. Verify if the upgraded modem firmware is still working

  --- Regression test ---

  Verify if one USB modem are still working with these patches for PCIe
  modems.

  [Where problems could occur]

  The requested update has 2 parts:

  1. Informative
     1.1 Provide more information about modems whose drivers use WWAN subsystem 
in kernel 5.13
     1.2 Modem manufacture's private utilities can use this information to do 
modem's FW upgrading manually

  2. Changes are specific to Foxconn and Quectel modems
     2.1 Modified code are only used by Foxconn and Quectel modems during their 
FW upgrading. (matched by vendor_id and product_id)

  In current Ubuntu's certification records for modem:
  * No other modem uses WWAN subsystem in kernel 5.13
  * Modem's FW update is not supported via ModemManager ( < v1.18 )

  There is no certificated modems can do the firmware upgrading flow for the 
regression test.
  This update should not affect existing modems.

  The problem would be limited to these two mentioned modems.
  Each carrier mapping .conf file is for a specific modem.
  ModemManager will load one of the carrier mapping conf files via the modem 
manufacturer’s plugin ( if the PCIe VID & PID is matched by the plugin.)
  We cannot verify if the carrier mapping is correct. This relies on the 
manufacturer to provide the correct mapping.

  The carrier mapping .conf files is verified by modem’s manufacture according 
to the tested SIM card published by different countries.
  Modem manufacturer confirmed that the content in the .conf file is absolutely 
correct.

  [Other Info]

  The firmware and the upgrading utilities can be downloaded from the following 
link:
  * LP#1943774 for Quectel modems
  * LP#1943780 for Foxconn modems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1946096/+subscriptions


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

[Touch-packages] [Bug 1650688] Re: timedatectl set-timezone fails on UC16

2021-12-13 Thread Łukasz Zemczak
Hello Tony, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.53 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  timedatectl set-timezone fails on UC16

Status in Snappy:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  SRU
  ===

  [Impact]

   * The bug prevents timedated from recognizing and correctly set the
  system's timezone when running Ubuntu Core 16, 18 and 20.

   * This causes by timedated fails to take Ubuntu Core's /etc/writable
  redirection into account.

   * The recognizing part is fixed by making the code take writable
  redirection into account.

   * The set part is fixed by making the code link to the absolute path
  instead of a relative one.

   * Currently core snaps worked around the set part by providing a
  wrapper script which re-create /etc/writable/localtime afterward.
  However this does not cover DBus users.

  [Test Plan]

   * On classics systems: ensure the proposed systemd package is installed.
     On Ubuntu Core systems: build a new core snap including proposed package, 
and install it. Replaces timedatectl with timedatectl.real to test skipping the 
wrapper.

  (Note that one can simulate core snap's /etc/writable redirection by
  running this image creation hook [1] on the system.)

  [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
  core/hooks/08-etc-writable.chroot?h=ubuntu/focal

   * On freshly boot system: query the timezone using `timedatectl`. The
  timezone should corresponds to `readlink -f /etc/localtime` and does
  not show `n/a`.

   * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`.
  `readlink -f /etc/localtime` should points to an existing file.

   * Run `sudo systemctl restart systemd-timedated.service`. Then, query
  the timezone again: `timedatectl`. It should show the previously set
  timezone and not `n/a`.

   * Run `sudo systemctl status systemd-timedated.service`. This should
  show no sign of timedated crashing.

  [Where problems could occur]

   * It's possible that the redirection handling code will be sub-par
  and causes crash. However, it's not likely because the similar pieces
  of code is in the previous patch since Ubuntu 16.04.

   * If it does: the patched `get_timezone()` function is used in 2
  places: the networkd's DHCP server [3] and the timedated itself.

     - Networkd is used primarily on servers where NetworkManage is
  absent. It's possible that this patch causes the user to loss access
  to the server due to networkd crash when setting up network
  interfaces, and requires physical access to fix. However, the code
  path is executed when DHCP is enabled only. I think it's not common
  for users to have networkd's DHCP server enabled: the feature seems to
  gear towards desktop users wanting to share internet connection, and
  in those cases they're more likely to use NetworkManager.

     - The timedated itself is likely used by the programs that involves
  in time-related functions. If a crash occur, in the worst case users
  won't be able to set time or timezone via timedated. However, users
  should still be able to e.g. set time using `date` or set timezone
  using /etc/localtime (assuming online guides still consider systems
  

[Touch-packages] [Bug 1650688] Re: timedatectl set-timezone fails on UC16

2021-12-13 Thread Łukasz Zemczak
I have accepted this fix for all the prepared systemd SRUs. I see that
LP: #1953172 has been created to track the future snapd work, but do you
know if work on this is already ongoing? Did you hear anything from the
snapd team regarding when we can expect it to land?

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

Title:
  timedatectl set-timezone fails on UC16

Status in Snappy:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  SRU
  ===

  [Impact]

   * The bug prevents timedated from recognizing and correctly set the
  system's timezone when running Ubuntu Core 16, 18 and 20.

   * This causes by timedated fails to take Ubuntu Core's /etc/writable
  redirection into account.

   * The recognizing part is fixed by making the code take writable
  redirection into account.

   * The set part is fixed by making the code link to the absolute path
  instead of a relative one.

   * Currently core snaps worked around the set part by providing a
  wrapper script which re-create /etc/writable/localtime afterward.
  However this does not cover DBus users.

  [Test Plan]

   * On classics systems: ensure the proposed systemd package is installed.
     On Ubuntu Core systems: build a new core snap including proposed package, 
and install it. Replaces timedatectl with timedatectl.real to test skipping the 
wrapper.

  (Note that one can simulate core snap's /etc/writable redirection by
  running this image creation hook [1] on the system.)

  [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
  core/hooks/08-etc-writable.chroot?h=ubuntu/focal

   * On freshly boot system: query the timezone using `timedatectl`. The
  timezone should corresponds to `readlink -f /etc/localtime` and does
  not show `n/a`.

   * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`.
  `readlink -f /etc/localtime` should points to an existing file.

   * Run `sudo systemctl restart systemd-timedated.service`. Then, query
  the timezone again: `timedatectl`. It should show the previously set
  timezone and not `n/a`.

   * Run `sudo systemctl status systemd-timedated.service`. This should
  show no sign of timedated crashing.

  [Where problems could occur]

   * It's possible that the redirection handling code will be sub-par
  and causes crash. However, it's not likely because the similar pieces
  of code is in the previous patch since Ubuntu 16.04.

   * If it does: the patched `get_timezone()` function is used in 2
  places: the networkd's DHCP server [3] and the timedated itself.

     - Networkd is used primarily on servers where NetworkManage is
  absent. It's possible that this patch causes the user to loss access
  to the server due to networkd crash when setting up network
  interfaces, and requires physical access to fix. However, the code
  path is executed when DHCP is enabled only. I think it's not common
  for users to have networkd's DHCP server enabled: the feature seems to
  gear towards desktop users wanting to share internet connection, and
  in those cases they're more likely to use NetworkManager.

     - The timedated itself is likely used by the programs that involves
  in time-related functions. If a crash occur, in the worst case users
  won't be able to set time or timezone via timedated. However, users
  should still be able to e.g. set time using `date` or set timezone
  using /etc/localtime (assuming online guides still consider systems
  without systemd). Timedated is DBus-activated, and thus a crash should
  be self-healing.

   * The set part would also affects the clasic systems. However, I
  believe nothing else actually rely on /etc/localtime being a relative
  path, otherwise the /etc/writable redirection would causes even more
  problem, and would have been reported.

  [3] Yes, I'm surprised that there's a DHCP server inside systemd
  codebase.

  [Other Info]

   * This is also useful for UBports's Ubuntu Touch. We continue using
  system-image system where the rootfs is read-only, and thus is
  affected by this bug similarly to Ubuntu Core. I've tested the Focal
  version of the package on our (currently in development) Focal Ubuntu
  Touch image, and the fix works.

  

  [Original bug description]

  On a system running UC16, the file /etc/localtime is a link that
  points to /etc/writable/localtime.

  On a freshly installed system, /etc/writable/localtime is a fully-
  qualified link that points at /usr/share/zoneinfo/UTC.

  If timedatectl is used to set the timezone to something else,
  timedated updates 

[Touch-packages] [Bug 1952599] Re: virt: Support detection for ARM64 Hyper-V guests (fixed upstream)

2021-12-13 Thread Łukasz Zemczak
Hello Gauthier, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.53 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  virt: Support detection for ARM64 Hyper-V guests (fixed upstream)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * The detection of Microsoft Hyper-V VMs is done by cpuid currently,
  however there is no cpuid on ARM64. And since ARM64 is now a supported
  architecture for Microsoft Hyper-V guests[0], then introduce a more
  generic way to detect whether a guest is running as a Hyper-V guest: check 
  if /sys/class/dmi/id/product_version starts with "Hyper-V".

   * This bug has already been fixed upstream[1][2]

  [Test Plan]

   * While changes have been made in the kernel for ARM64 on Hyper-V,
  there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we
  just want to make sure no regression is introduced.

   * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still
  return MSFT (should still rely on cpuid here)

  [Where problems could occur]

   * The main risk is for the system to detect Hyper-V virt erroneously.
  An issue was reported upstream after the first commit was merged[3].
  For this reason, systemd is now looking for "Hyper-V" (in
  /sys/class/dmi/id/product_version) and not "Microsoft" (in
  /sys/class/dmi/id/bios_vendor)

   * This change might also break virt detection on hyper-v AMD64.
  That's why we need testing. However, AMD64 virt detection should still
  rely on cpuid instead of DMI as cpuid takes priority over DMI.

  [0] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467
  [1] https://github.com/systemd/systemd/pull/20998/files
  [2] https://github.com/systemd/systemd/pull/21475/files
  [3] https://github.com/systemd/systemd/issues/21468

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


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


[Touch-packages] [Bug 1650688] Re: timedatectl set-timezone fails on UC16

2021-12-13 Thread Łukasz Zemczak
Hello Tony, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  timedatectl set-timezone fails on UC16

Status in Snappy:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  SRU
  ===

  [Impact]

   * The bug prevents timedated from recognizing and correctly set the
  system's timezone when running Ubuntu Core 16, 18 and 20.

   * This causes by timedated fails to take Ubuntu Core's /etc/writable
  redirection into account.

   * The recognizing part is fixed by making the code take writable
  redirection into account.

   * The set part is fixed by making the code link to the absolute path
  instead of a relative one.

   * Currently core snaps worked around the set part by providing a
  wrapper script which re-create /etc/writable/localtime afterward.
  However this does not cover DBus users.

  [Test Plan]

   * On classics systems: ensure the proposed systemd package is installed.
     On Ubuntu Core systems: build a new core snap including proposed package, 
and install it. Replaces timedatectl with timedatectl.real to test skipping the 
wrapper.

  (Note that one can simulate core snap's /etc/writable redirection by
  running this image creation hook [1] on the system.)

  [1] https://git.launchpad.net/livecd-rootfs/tree/live-build/ubuntu-
  core/hooks/08-etc-writable.chroot?h=ubuntu/focal

   * On freshly boot system: query the timezone using `timedatectl`. The
  timezone should corresponds to `readlink -f /etc/localtime` and does
  not show `n/a`.

   * Set a new timezone: `sudo timedatectl set-timezone Asia/Bangkok`.
  `readlink -f /etc/localtime` should points to an existing file.

   * Run `sudo systemctl restart systemd-timedated.service`. Then, query
  the timezone again: `timedatectl`. It should show the previously set
  timezone and not `n/a`.

   * Run `sudo systemctl status systemd-timedated.service`. This should
  show no sign of timedated crashing.

  [Where problems could occur]

   * It's possible that the redirection handling code will be sub-par
  and causes crash. However, it's not likely because the similar pieces
  of code is in the previous patch since Ubuntu 16.04.

   * If it does: the patched `get_timezone()` function is used in 2
  places: the networkd's DHCP server [3] and the timedated itself.

     - Networkd is used primarily on servers where NetworkManage is
  absent. It's possible that this patch causes the user to loss access
  to the server due to networkd crash when setting up network
  interfaces, and requires physical access to fix. However, the code
  path is executed when DHCP is enabled only. I think it's not common
  for users to have networkd's DHCP server enabled: the feature seems to
  gear towards desktop users wanting to share internet connection, and
  in those cases they're more likely to use NetworkManager.

     - The timedated itself is likely used by the programs that involves
  in time-related functions. If a crash occur, in the worst case users
  won't be able to set time or timezone via timedated. However, users
  should still be able to e.g. set time using `date` or set timezone
  using /etc/localtime (assuming online guides still consider systems
  

[Touch-packages] [Bug 1944711] Re: restarting systemd-logind loses all existing sessions

2021-12-13 Thread Łukasz Zemczak
Hello Dan, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  restarting systemd-logind loses all existing sessions

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

Bug description:
  [impact]

  restarting the systemd-logind service loses all existing sessions

  [test case]

  ubuntu@test-f:~$ loginctl list-sessions
  SESSION  UID USER   SEAT TTY
     3789 1000 ubuntu  pts/0

  1 sessions listed.
  ubuntu@test-f:~$ journalctl -b -u systemd-logind
  -- Logs begin at Thu 2021-09-23 11:11:57 UTC, end at Thu 2021-09-23 11:22:55 
UTC. --
  Sep 23 11:22:51 test-f systemd[1]: Starting Login Service...
  Sep 23 11:22:51 test-f systemd-logind[198]: New seat seat0.
  Sep 23 11:22:51 test-f systemd[1]: Started Login Service.
  Sep 23 11:22:52 test-f systemd-logind[198]: New session 3789 of user ubuntu.
  ubuntu@test-f:~$ sudo systemctl restart systemd-logind
  ubuntu@test-f:~$ journalctl -b -u systemd-logind
  -- Logs begin at Thu 2021-09-23 11:11:57 UTC, end at Thu 2021-09-23 11:23:07 
UTC. --
  Sep 23 11:22:51 test-f systemd[1]: Starting Login Service...
  Sep 23 11:22:51 test-f systemd-logind[198]: New seat seat0.
  Sep 23 11:22:51 test-f systemd[1]: Started Login Service.
  Sep 23 11:22:52 test-f systemd-logind[198]: New session 3789 of user ubuntu.
  Sep 23 11:23:07 test-f systemd[1]: Stopping Login Service...
  Sep 23 11:23:07 test-f systemd[1]: systemd-logind.service: Succeeded.
  Sep 23 11:23:07 test-f systemd[1]: Stopped Login Service.
  Sep 23 11:23:07 test-f systemd[1]: Starting Login Service...
  Sep 23 11:23:07 test-f systemd-logind[469]: Failed to add user by file name 
1000, ignoring: Invalid argument
  Sep 23 11:23:07 test-f systemd-logind[469]: User enumeration failed: Invalid 
argument
  Sep 23 11:23:07 test-f systemd-logind[469]: User of session 3789 not known.
  Sep 23 11:23:07 test-f systemd-logind[469]: Session enumeration failed: No 
such file or directory
  Sep 23 11:23:07 test-f systemd-logind[469]: New seat seat0.
  Sep 23 11:23:07 test-f systemd[1]: Started Login Service.
  ubuntu@test-f:~$ loginctl list-sessions
  No sessions.

  [regression potential]

  any regression would likely occur during a systemd-logind restart,
  likely causing a loss of current login sessions.

  [scope]

  this is needed only in f

  this is fixed upstream by commit
  ac4e03d45bcf4ad2e570cabdb218e9bac003cc80 which is included in v246, so
  this is fixed in h and later already.

  in b, the function used to parse the /run/systemd/users/* files allows
  either usernames or uids, so this bug does not exist there

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


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


[Touch-packages] [Bug 1952599] Re: virt: Support detection for ARM64 Hyper-V guests (fixed upstream)

2021-12-13 Thread Łukasz Zemczak
Hello Gauthier, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-focal

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

Title:
  virt: Support detection for ARM64 Hyper-V guests (fixed upstream)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * The detection of Microsoft Hyper-V VMs is done by cpuid currently,
  however there is no cpuid on ARM64. And since ARM64 is now a supported
  architecture for Microsoft Hyper-V guests[0], then introduce a more
  generic way to detect whether a guest is running as a Hyper-V guest: check 
  if /sys/class/dmi/id/product_version starts with "Hyper-V".

   * This bug has already been fixed upstream[1][2]

  [Test Plan]

   * While changes have been made in the kernel for ARM64 on Hyper-V,
  there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we
  just want to make sure no regression is introduced.

   * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still
  return MSFT (should still rely on cpuid here)

  [Where problems could occur]

   * The main risk is for the system to detect Hyper-V virt erroneously.
  An issue was reported upstream after the first commit was merged[3].
  For this reason, systemd is now looking for "Hyper-V" (in
  /sys/class/dmi/id/product_version) and not "Microsoft" (in
  /sys/class/dmi/id/bios_vendor)

   * This change might also break virt detection on hyper-v AMD64.
  That's why we need testing. However, AMD64 virt detection should still
  rely on cpuid instead of DMI as cpuid takes priority over DMI.

  [0] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467
  [1] https://github.com/systemd/systemd/pull/20998/files
  [2] https://github.com/systemd/systemd/pull/21475/files
  [3] https://github.com/systemd/systemd/issues/21468

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


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


[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine

2021-12-13 Thread Łukasz Zemczak
Hello Andy, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-focal

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

Title:
  Add Microphone mute key mapping for Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Dell machine add new microphone mute key on keyboard, add this key mapping 
to make it work.
  [Test Plan]

   * Use a Dell machine, which has this microphone mute key, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions


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


[Touch-packages] [Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models

2021-12-13 Thread Łukasz Zemczak
Hello Yao, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-focal

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

Title:
  Add ACCEL_LOCATION=base property for 6 Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  This hwdb update is to avoid unwanted screen rotation when tilting the
  laptop.

  This is the update to the previously rolled back SRU LP: #1938259

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install 
this package and ensure the kernel is updated to the latest.
   * Screen should be correct side up in login screen and desktop.
   * Tilt the laptop and the screen should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * Only models with the same Dell SKU would be affected.

  [scope]

  this is needed for all releases

  this is being added to upstream by
  https://github.com/systemd/systemd/pull/20314 and
  https://github.com/systemd/systemd/pull/20661

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions


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


[Touch-packages] [Bug 1948476] Re: [SRU] Allow target units to fail

2021-12-13 Thread Łukasz Zemczak
Hello Alfonso, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  [SRU] Allow target units to fail

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

Bug description:
  [Impact]

  A systemd regression in focal made it think that target units cannot
  fail, which produced warnings like:

  emergency.target: Requested dependency OnFailure=reboot.target ignored
  (target units cannot fail).

  So the OnFailure settings are ignored for targets (see
  https://github.com/snapcore/core-initrd/issues/33 for details).
  Upstream fixed the issue in v246:
  
https://github.com/systemd/systemd/commit/94d1ddbd7cd15b1073757eb5ae0645c83f0b414c

  [Test Plan]

  Test on a UC system and check that the above warnings are not shown
  anymore. Check that when a target service type fails, the OnFailure
  setting is used and the mentioned service is run.

  [Where problems could occur]

  Issues might happen if some target has an OnFailure setting that was
  never run in the past because of this bug, and the behavior is not
  really right because it was never tested. However, OnFailure is not
  used that much on 20.04 in target services:

  /lib/systemd $ find . -name \*.target | xargs grep OnFailure
  /lib/systemd $ 
  /etc/systemd $ find . -name \*.target | xargs grep OnFailure
  /etc/systemd $ 

  I've seen it only in emergency.target for UC20.

  [Other Info]
   
  None

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


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


[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine

2021-12-13 Thread Łukasz Zemczak
Hello Andy, or anyone else affected,

Accepted systemd into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/245.4-4ubuntu3.14 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-focal

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

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions


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


[Touch-packages] [Bug 1926547] Re: Add Dell Privacy Mic Mute Key mapping

2021-12-13 Thread Łukasz Zemczak
Hello Andy, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Impish)
   Status: New => Fix Committed

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

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

Title:
  Add Dell Privacy Mic Mute Key mapping

Status in OEM Priority Project:
  Fix Released
Status in OEM Priority Project focal series:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
     GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * The change can only work with kernel commit on some specific hardware, ex. 
Latitude 9520. The commit series is 
"hardware-privacy-implementation-for-dell-laptop" in alsa-devel kernel tree.
     https://patchwork.kernel.org/project/alsa-devel/list/?series=465445
   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1926547/+subscriptions


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


[Touch-packages] [Bug 1952599] Re: virt: Support detection for ARM64 Hyper-V guests (fixed upstream)

2021-12-13 Thread Łukasz Zemczak
Hello Gauthier, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Impish)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

Title:
  virt: Support detection for ARM64 Hyper-V guests (fixed upstream)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Focal:
  New
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * The detection of Microsoft Hyper-V VMs is done by cpuid currently,
  however there is no cpuid on ARM64. And since ARM64 is now a supported
  architecture for Microsoft Hyper-V guests[0], then introduce a more
  generic way to detect whether a guest is running as a Hyper-V guest: check 
  if /sys/class/dmi/id/product_version starts with "Hyper-V".

   * This bug has already been fixed upstream[1][2]

  [Test Plan]

   * While changes have been made in the kernel for ARM64 on Hyper-V,
  there is no way to start an ARM64 VM on Hyper-V at the moment. Thus we
  just want to make sure no regression is introduced.

   * start an Hyper-V amd64 VM and make sure "systemd-detect-virt" still
  return MSFT (should still rely on cpuid here)

  [Where problems could occur]

   * The main risk is for the system to detect Hyper-V virt erroneously.
  An issue was reported upstream after the first commit was merged[3].
  For this reason, systemd is now looking for "Hyper-V" (in
  /sys/class/dmi/id/product_version) and not "Microsoft" (in
  /sys/class/dmi/id/bios_vendor)

   * This change might also break virt detection on hyper-v AMD64.
  That's why we need testing. However, AMD64 virt detection should still
  rely on cpuid instead of DMI as cpuid takes priority over DMI.

  [0] 
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7aff79e297ee1aa0126924921fd87a4ae59d2467
  [1] https://github.com/systemd/systemd/pull/20998/files
  [2] https://github.com/systemd/systemd/pull/21475/files
  [3] https://github.com/systemd/systemd/issues/21468

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


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


[Touch-packages] [Bug 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models

2021-12-13 Thread Łukasz Zemczak
Hello Yao, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Impish)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

Title:
  Add ACCEL_LOCATION=base property for 6 Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  New
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  This hwdb update is to avoid unwanted screen rotation when tilting the
  laptop.

  This is the update to the previously rolled back SRU LP: #1938259

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install 
this package and ensure the kernel is updated to the latest.
   * Screen should be correct side up in login screen and desktop.
   * Tilt the laptop and the screen should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * Only models with the same Dell SKU would be affected.

  [scope]

  this is needed for all releases

  this is being added to upstream by
  https://github.com/systemd/systemd/pull/20314 and
  https://github.com/systemd/systemd/pull/20661

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943561/+subscriptions


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


[Touch-packages] [Bug 1952733] Re: Add Dell Privacy Mic Mute Key mapping for another Dell machine

2021-12-13 Thread Łukasz Zemczak
Hello Andy, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Impish)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

Title:
  Add Dell Privacy Mic Mute Key mapping for another Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  New
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Dell introduces new function called Dell Privacy, it utilizes
  hardware mute to control audio and camera. The commit map the reported
  key event to mic mute for making userspace can work as before, "Mic
  Mute" dialog pop-up while the mic mute button is pressed.

  [Test Plan]

   * Use a Dell machine, which has Dell privacy function, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952733/+subscriptions


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


[Touch-packages] [Bug 1952735] Re: Add Microphone mute key mapping for Dell machine

2021-12-13 Thread Łukasz Zemczak
Hello Andy, or anyone else affected,

Accepted systemd into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/248.3-1ubuntu8.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: systemd (Ubuntu Impish)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-impish

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

Title:
  Add Microphone mute key mapping for Dell machine

Status in OEM Priority Project:
  Confirmed
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  New
Status in systemd source package in Hirsute:
  New
Status in systemd source package in Impish:
  Fix Committed
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * Dell machine add new microphone mute key on keyboard, add this key mapping 
to make it work.
  [Test Plan]

   * Use a Dell machine, which has this microphone mute key, and press mic mute 
key.
 GUI will pop up "Mic Mute" icon.

  [Where problems could occur]

   * This change adds key event mapping in hwdb, which won't impact
  other hardware.

   any regression would likely cause problems with key(s) from the
  specific dell kb matching the modified listing in the hw db.

  [Other Info]

   * This change has been verified on Dell machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1952735/+subscriptions


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


[Touch-packages] [Bug 1953712] Re: 5.15.2 rebuild against libopenssl3 requires patches and dependency fixes

2021-12-09 Thread Łukasz Zemczak
$ remove-package -m "Agreed not to rebuild this for now against OpenSSL3, needs 
more changes (LP: #1953712)" -s jammy-proposed -e 5.15.2+dfsg-14ubuntu2 
qtbase-opensource-src
Removing packages from jammy-proposed:
qtbase-opensource-src 5.15.2+dfsg-14ubuntu2 in jammy
libqt5concurrent5 5.15.2+dfsg-14ubuntu2 in jammy amd64
libqt5concurrent5 5.15.2+dfsg-14ubuntu2 in jammy arm64
libqt5concurrent5 5.15.2+dfsg-14ubuntu2 in jammy armhf
libqt5concurrent5 5.15.2+dfsg-14ubuntu2 in jammy i386
libqt5concurrent5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el
libqt5concurrent5 5.15.2+dfsg-14ubuntu2 in jammy s390x
libqt5core5a 5.15.2+dfsg-14ubuntu2 in jammy amd64
libqt5core5a 5.15.2+dfsg-14ubuntu2 in jammy arm64
libqt5core5a 5.15.2+dfsg-14ubuntu2 in jammy armhf
libqt5core5a 5.15.2+dfsg-14ubuntu2 in jammy i386
libqt5core5a 5.15.2+dfsg-14ubuntu2 in jammy ppc64el
libqt5core5a 5.15.2+dfsg-14ubuntu2 in jammy s390x
libqt5dbus5 5.15.2+dfsg-14ubuntu2 in jammy amd64
libqt5dbus5 5.15.2+dfsg-14ubuntu2 in jammy arm64
libqt5dbus5 5.15.2+dfsg-14ubuntu2 in jammy armhf
libqt5dbus5 5.15.2+dfsg-14ubuntu2 in jammy i386
libqt5dbus5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el
libqt5dbus5 5.15.2+dfsg-14ubuntu2 in jammy s390x
libqt5gui5 5.15.2+dfsg-14ubuntu2 in jammy amd64
libqt5gui5 5.15.2+dfsg-14ubuntu2 in jammy arm64
libqt5gui5 5.15.2+dfsg-14ubuntu2 in jammy armhf
libqt5gui5 5.15.2+dfsg-14ubuntu2 in jammy i386
libqt5gui5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el
libqt5gui5 5.15.2+dfsg-14ubuntu2 in jammy s390x
libqt5network5 5.15.2+dfsg-14ubuntu2 in jammy amd64
libqt5network5 5.15.2+dfsg-14ubuntu2 in jammy arm64
libqt5network5 5.15.2+dfsg-14ubuntu2 in jammy armhf
libqt5network5 5.15.2+dfsg-14ubuntu2 in jammy i386
libqt5network5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el
libqt5network5 5.15.2+dfsg-14ubuntu2 in jammy s390x
libqt5opengl5 5.15.2+dfsg-14ubuntu2 in jammy amd64
libqt5opengl5 5.15.2+dfsg-14ubuntu2 in jammy arm64
libqt5opengl5 5.15.2+dfsg-14ubuntu2 in jammy armhf
libqt5opengl5 5.15.2+dfsg-14ubuntu2 in jammy i386
libqt5opengl5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el
libqt5opengl5 5.15.2+dfsg-14ubuntu2 in jammy s390x
libqt5opengl5-dev 5.15.2+dfsg-14ubuntu2 in jammy amd64
libqt5opengl5-dev 5.15.2+dfsg-14ubuntu2 in jammy arm64
libqt5opengl5-dev 5.15.2+dfsg-14ubuntu2 in jammy armhf
libqt5opengl5-dev 5.15.2+dfsg-14ubuntu2 in jammy i386
libqt5opengl5-dev 5.15.2+dfsg-14ubuntu2 in jammy ppc64el
libqt5opengl5-dev 5.15.2+dfsg-14ubuntu2 in jammy s390x
libqt5printsupport5 5.15.2+dfsg-14ubuntu2 in jammy amd64
libqt5printsupport5 5.15.2+dfsg-14ubuntu2 in jammy arm64
libqt5printsupport5 5.15.2+dfsg-14ubuntu2 in jammy armhf
libqt5printsupport5 5.15.2+dfsg-14ubuntu2 in jammy i386
libqt5printsupport5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el
libqt5printsupport5 5.15.2+dfsg-14ubuntu2 in jammy s390x
libqt5sql5 5.15.2+dfsg-14ubuntu2 in jammy amd64
libqt5sql5 5.15.2+dfsg-14ubuntu2 in jammy arm64
libqt5sql5 5.15.2+dfsg-14ubuntu2 in jammy armhf
libqt5sql5 5.15.2+dfsg-14ubuntu2 in jammy i386
libqt5sql5 5.15.2+dfsg-14ubuntu2 in jammy ppc64el
libqt5sql5 5.15.2+dfsg-14ubuntu2 in jammy s390x
libqt5sql5-ibase 5.15.2+dfsg-14ubuntu2 in jammy amd64
libqt5sql5-ibase 5.15.2+dfsg-14ubuntu2 in jammy arm64
libqt5sql5-ibase 5.15.2+dfsg-14ubuntu2 in jammy armhf
libqt5sql5-ibase 5.15.2+dfsg-14ubuntu2 in jammy i386
libqt5sql5-ibase 5.15.2+dfsg-14ubuntu2 in jammy ppc64el
libqt5sql5-ibase 5.15.2+dfsg-14ubuntu2 in jammy s390x
libqt5sql5-mysql 5.15.2+dfsg-14ubuntu2 in jammy amd64
libqt5sql5-mysql 5.15.2+dfsg-14ubuntu2 in jammy arm64
libqt5sql5-mysql 5.15.2+dfsg-14ubuntu2 in jammy armhf
libqt5sql5-mysql 5.15.2+dfsg-14ubuntu2 in jammy i386
libqt5sql5-mysql 5.15.2+dfsg-14ubuntu2 in jammy ppc64el
libqt5sql5-mysql 5.15.2+dfsg-14ubuntu2 in jammy s390x
libqt5sql5-odbc 5.15.2+dfsg-14ubuntu2 in jammy amd64
libqt5sql5-odbc 5.15.2+dfsg-14ubuntu2 in jammy arm64
libqt5sql5-odbc 5.15.2+dfsg-14ubuntu2 in jammy armhf
   

[Touch-packages] [Bug 1782984] Re: Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple applications

2021-12-09 Thread Łukasz Zemczak
Any update on this bug and the status of focal?

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

Title:
  Assertion `!xcb_xlib_threads_sequence_lost' failed with multiple
  applications

Status in libx11 package in Ubuntu:
  Fix Released
Status in libx11 source package in Bionic:
  Fix Committed
Status in libx11 source package in Focal:
  Fix Committed
Status in libx11 source package in Groovy:
  Won't Fix

Bug description:
  [Impact]

  There is a race in libx11 causing applications to randomly abort. It's
  not trivial to reproduce, but there are enough duplicates that this
  deserves an SRU to bionic & focal.

  [Fix]

  Backport a commit from upstream:

  From dbb55e1a5e82870466b095097d9e46046680ec25 Mon Sep 17 00:00:00 2001
  From: Frediano Ziglio 
  Date: Wed, 29 Jan 2020 09:06:54 +
  Subject: [PATCH] Fix poll_for_response race condition

  In poll_for_response is it possible that event replies are skipped
  and a more up to date message reply is returned.
  This will cause next poll_for_event call to fail aborting the program.

  This was proved using some slow ssh tunnel or using some program
  to slow down server replies (I used a combination of xtrace and strace).

  How the race happens:
  - program enters into poll_for_response;
  - poll_for_event is called but the server didn't still send the reply;
  - pending_requests is not NULL because we send a request (see call
to  append_pending_request in _XSend);
  - xcb_poll_for_reply64 is called from poll_for_response;
  - xcb_poll_for_reply64 will read from server, at this point
server reply with an event (say sequence N) and the reply to our
last request (say sequence N+1);
  - xcb_poll_for_reply64 returns the reply for the request we asked;
  - last_request_read is set to N+1 sequence in poll_for_response;
  - poll_for_response returns the response to the request;
  - poll_for_event is called (for instance from another poll_for_response);
  - event with sequence N is retrieved;
  - the N sequence is widen, however, as the "new" number computed from
last_request_read is less than N the number is widened to N + 2^32
(assuming last_request_read is still contained in 32 bit);
  - poll_for_event enters the nested if statement as req is NULL;
  - we compare the widen N (which now does not fit into 32 bit) with
request (which fits into 32 bit) hitting the throw_thread_fail_assert.

  To avoid the race condition and to avoid the sequence to go back
  I check again for new events after getting the response and
  return this last event if present saving the reply to return it
  later.

  To test the race and the fix it's helpful to add a delay (I used a
  "usleep(5000)") before calling xcb_poll_for_reply64.

  Original patch written by Frediano Ziglio, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/34

  Reworked primarily for readability by Peter Hutterer, see
  https://gitlab.freedesktop.org/xorg/lib/libx11/-/merge_requests/53

  Signed-off-by: Peter Hutterer 

  bionic needs another commit so that the real fix applies.

  [Test case]

  It's a race condition, the SRU sponsor (tjaalton) does not have a test
  case for this, but the bug subscribers seem to.

  
  [Where things could go wrong]

  In theory there might be a case where a race still happens, but since
  this has been upstream for a year now with no follow-up commits, it's
  safe to assume that there are no regressions.

  
  --

  STEPS TO REPRODUCE
  ==
  The bug seems to occur when clicking on a file or folder. It is random and 
difficult to provide clear steps to reproduce. It is, however, a common 
situation.

  EXPECTED RESULTS
  
  pcmanfm works without problem.

  ACTUAL RESULTS
  ==
  All pcmanfm windows become unresponsive, though background processes (e.g. 
copying) may continue without problem. with the same error message in 
~/.cache/lxsession/LXDE/run.log:

  [xcb] Unknown sequence number while processing queue
  [xcb] Most likely this is a multi-threaded client and XInitThreads has not 
been called
  [xcb] Aborting, sorry about that.
  pcmanfm: xcb_io.c:259: poll_for_event: Assertion 
`!xcb_xlib_threads_sequence_lost' failed.
  ** Message: 19:58:49.267: app.vala:130: pcmanfm exit with this type of exit: 6
  ** Message: 19:58:49.268: app.vala:148: Exit not normal, try to reload

  (note the timestamp on the message will vary)

  AFFECTED VERSIONS
  =
  1.2.5-3ubuntu1
  NOT 1.2.4-1ubuntu0.1

  UPSTREAM BUG
  
  https://sourceforge.net/p/pcmanfm/bugs/1089/

  ADDITIONAL NOTES
  
  Other GTK2 file managers (e.g. Thunar) and applications (e.g. GIMP, Leafpad) 
seem to have the same problems. This is probably at least rooted in a GTK2 bug:
  https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710

  To further 

[Touch-packages] [Bug 1951667] Update Released

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

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

Title:
  [SRU] pulseaudio: restore hdmi audio be active output after resume

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Committed
Status in pulseaudio source package in Hirsute:
  Won't Fix
Status in pulseaudio source package in Impish:
  Fix Committed
Status in pulseaudio source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  On the machines with legacy HDA audio driver, when users plug a hdmi/dp 
monitor, the active output device is still speaker, need users to manually 
select the hdmi, then the hdmi audio will be the users' preference, once it is 
plugged, it should become the active output automatically. But with the current 
PA, after reboot and suspend/resume, the hdmi can't change to be active output 
automatically anymore.

  [Fix]
  Backport an upstream fix, this will fix the issue of "preferred ports being 
cleaned by a mistake"

  [Test]
  On a machine with legacy HDA audio driver, install the patched pulseaudio, 
then run 'rm ~/.config/pulse/*; reboot', plug a hdmi monitor, select the hdmi 
audio to be active, with the hdmi monitor plugged and reboot, suspend and 
resume, check what is the active output, it is still the hdmi audio.

  [Where problems could occur]
  This patch is in the card-restore.c, if it could introduce regression, it 
will be on the default active input/output devices, for example, users select a 
input or output device to be active, after reboot, if those devices are 
available, they should be active, but they could be replaced by other devices 
if a regression is introduced. But this possibility is very low since we tested 
the patch on a couple of desktop and laptop machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1951667/+subscriptions


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


[Touch-packages] [Bug 1952918] Re: Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed

2021-12-06 Thread Łukasz Zemczak
Ok, removing fluidsynth from jammy-proposed for now, please be sure to
re-introduce it once the other transitions make it through.

I checked the rdeps of libfluidsynth3 from -proposed though, and it seems we 
have two packages in jammy-proposed that have been rebuilt to now depend on 
libfluidsynth3 instead of libfluidsynth2. I'm leaving them there as-is, but 
it's good to know that those are already involved with the SONAME bump:
* mpd
* minuet

$ remove-package -s jammy-proposed -m "Temporarily dropping from -proposed to 
let other transitions finish first. To be reintroduced (LP: #1952918)" 
fluidsynth
Removing packages from jammy-proposed:
fluidsynth 2.2.4-2 in jammy
fluidsynth 2.2.4-2 in jammy amd64
fluidsynth 2.2.4-2 in jammy arm64
fluidsynth 2.2.4-2 in jammy armhf
fluidsynth 2.2.4-2 in jammy i386
fluidsynth 2.2.4-2 in jammy ppc64el
fluidsynth 2.2.4-2 in jammy riscv64
fluidsynth 2.2.4-2 in jammy s390x
libfluidsynth-dev 2.2.4-2 in jammy amd64
libfluidsynth-dev 2.2.4-2 in jammy arm64
libfluidsynth-dev 2.2.4-2 in jammy armhf
libfluidsynth-dev 2.2.4-2 in jammy i386
libfluidsynth-dev 2.2.4-2 in jammy ppc64el
libfluidsynth-dev 2.2.4-2 in jammy riscv64
libfluidsynth-dev 2.2.4-2 in jammy s390x
libfluidsynth3 2.2.4-2 in jammy amd64
libfluidsynth3 2.2.4-2 in jammy arm64
libfluidsynth3 2.2.4-2 in jammy armhf
libfluidsynth3 2.2.4-2 in jammy i386
libfluidsynth3 2.2.4-2 in jammy ppc64el
libfluidsynth3 2.2.4-2 in jammy riscv64
libfluidsynth3 2.2.4-2 in jammy s390x
Comment: Temporarily dropping from -proposed to let other transitions finish 
first. To be reintroduced (LP: #1952918)
Remove [y|N]? y
1 package successfully removed.


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

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

Title:
  Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed

Status in fluidsynth package in Ubuntu:
  Fix Released

Bug description:
  fluidsynth 2.2.4-2 (currently in jammy-proposed) has a SONAME bump:

    libfluidsynth2 -> libfluidsynth3

  which is a fairly large transition:

  $ reverse-depends -b -l src:fluidsynth | wc -l
  30

  This list of reverse-dependencies has exactly one package in common
  with other two currently ongoing transitions:

  $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l 
src:libidn)
  vlc

  $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l 
src:liburing)
  mpd

  These other two transitions are almost done, hopefully just requiring
  couple of minor uploads (merging a new Debian revision of ghostscript
  and uploading a new Ubuntu revision of exim4 to resolve a components-
  mismatch).

  I think it it would be better to finish these other two transitions
  first, without fluidsynth, and then sync fluidsynth again, to be
  handled separately.

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


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


[Touch-packages] [Bug 1952918] Re: Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed

2021-12-06 Thread Łukasz Zemczak
Let me try looking into that.

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

Title:
  Please temporarely pull fluidsynth 2.2.4-2 from jammy-proposed

Status in fluidsynth package in Ubuntu:
  New

Bug description:
  fluidsynth 2.2.4-2 (currently in jammy-proposed) has a SONAME bump:

    libfluidsynth2 -> libfluidsynth3

  which is a fairly large transition:

  $ reverse-depends -b -l src:fluidsynth | wc -l
  30

  This list of reverse-dependencies has exactly one package in common
  with other two currently ongoing transitions:

  $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l 
src:libidn)
  vlc

  $ comm -12 <(reverse-depends -b -l src:fluidsynth) <(reverse-depends -b -l 
src:liburing)
  mpd

  These other two transitions are almost done, hopefully just requiring
  couple of minor uploads (merging a new Debian revision of ghostscript
  and uploading a new Ubuntu revision of exim4 to resolve a components-
  mismatch).

  I think it it would be better to finish these other two transitions
  first, without fluidsynth, and then sync fluidsynth again, to be
  handled separately.

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


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


[Touch-packages] [Bug 1951943] Please test proposed package

2021-11-26 Thread Łukasz Zemczak
Hello Dimitri, or anyone else affected,

Accepted openssl into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/1.1.1-1ubuntu2.1~18.04.14
in a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  Engine crashes when loading the configuration more than once

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Bionic:
  Fix Committed
Status in openssl source package in Focal:
  Fix Committed
Status in openssl source package in Hirsute:
  Fix Committed
Status in openssl source package in Impish:
  Fix Committed
Status in openssl source package in Jammy:
  Confirmed

Bug description:
  [Impact]

   * Engine crashes when loading the configuration more than once

   * Upstream started to avoid loading engines twice by using dynamic
  ids to track the loaded engines correctly

   * OpenSSL 3
  
https://github.com/openssl/openssl/commit/81c11349c2a0e945aa3dfc6bd81c957363dd2011
 (bugfix)
  
https://github.com/openssl/openssl/commit/38e2957249c90317a26a080c7e7eb186dd5b6598
 (test case)

   * OpenSSL 1.1.1 backports:
  
https://github.com/openssl/openssl/commit/9b06ebb1edfddffea083ba36090af7eb7cad207b
 (bugfix)
  https://github.com/openssl/openssl/pull/17083 (test case)

  [Test Plan]

   * https://github.com/openssl/openssl/issues/17023 lists multiple ways
  how one can trigger the issue at hand, but also test case implements
  this issue too by explicitly attempting to load an engine multiple
  times and checking that it is operational.

  The test a is run during the build as part of the upstream regression
  test suite, for the shared library build (as static build does not
  support engines), so you'll see one pass and one skip in the log.

  [Where problems could occur]

   * Separately we have started to fix userspace packages that
  needlessly load configuration files multiple times, which used to
  trigger this issue. The codepaths changed are with engine use, how
  they are loaded/unloaded/used. It is possible that this fix will make
  some engines to start working and be used resulting in new behaviour.
  But also exposing bugs in the engines that previously were installed &
  configured but not actually used.

  [Other Info]

   * Previous bug reports about this issues are:
  https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518
  https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528

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


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


[Touch-packages] [Bug 1951943] Re: Engine crashes when loading the configuration more than once

2021-11-26 Thread Łukasz Zemczak
Hello Dimitri, or anyone else affected,

Accepted openssl into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/1.1.1f-1ubuntu2.10 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-focal

** Changed in: openssl (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Engine crashes when loading the configuration more than once

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Bionic:
  Fix Committed
Status in openssl source package in Focal:
  Fix Committed
Status in openssl source package in Hirsute:
  Fix Committed
Status in openssl source package in Impish:
  Fix Committed
Status in openssl source package in Jammy:
  Confirmed

Bug description:
  [Impact]

   * Engine crashes when loading the configuration more than once

   * Upstream started to avoid loading engines twice by using dynamic
  ids to track the loaded engines correctly

   * OpenSSL 3
  
https://github.com/openssl/openssl/commit/81c11349c2a0e945aa3dfc6bd81c957363dd2011
 (bugfix)
  
https://github.com/openssl/openssl/commit/38e2957249c90317a26a080c7e7eb186dd5b6598
 (test case)

   * OpenSSL 1.1.1 backports:
  
https://github.com/openssl/openssl/commit/9b06ebb1edfddffea083ba36090af7eb7cad207b
 (bugfix)
  https://github.com/openssl/openssl/pull/17083 (test case)

  [Test Plan]

   * https://github.com/openssl/openssl/issues/17023 lists multiple ways
  how one can trigger the issue at hand, but also test case implements
  this issue too by explicitly attempting to load an engine multiple
  times and checking that it is operational.

  The test a is run during the build as part of the upstream regression
  test suite, for the shared library build (as static build does not
  support engines), so you'll see one pass and one skip in the log.

  [Where problems could occur]

   * Separately we have started to fix userspace packages that
  needlessly load configuration files multiple times, which used to
  trigger this issue. The codepaths changed are with engine use, how
  they are loaded/unloaded/used. It is possible that this fix will make
  some engines to start working and be used resulting in new behaviour.
  But also exposing bugs in the engines that previously were installed &
  configured but not actually used.

  [Other Info]

   * Previous bug reports about this issues are:
  https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518
  https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528

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


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


[Touch-packages] [Bug 1951943] Re: Engine crashes when loading the configuration more than once

2021-11-26 Thread Łukasz Zemczak
Hello Dimitri, or anyone else affected,

Accepted openssl into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/openssl/1.1.1j-1ubuntu3.6 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed-hirsute

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

Title:
  Engine crashes when loading the configuration more than once

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Bionic:
  Confirmed
Status in openssl source package in Focal:
  In Progress
Status in openssl source package in Hirsute:
  Fix Committed
Status in openssl source package in Impish:
  Fix Committed
Status in openssl source package in Jammy:
  Confirmed

Bug description:
  [Impact]

   * Engine crashes when loading the configuration more than once

   * Upstream started to avoid loading engines twice by using dynamic
  ids to track the loaded engines correctly

   * OpenSSL 3
  
https://github.com/openssl/openssl/commit/81c11349c2a0e945aa3dfc6bd81c957363dd2011
 (bugfix)
  
https://github.com/openssl/openssl/commit/38e2957249c90317a26a080c7e7eb186dd5b6598
 (test case)

   * OpenSSL 1.1.1 backports:
  
https://github.com/openssl/openssl/commit/9b06ebb1edfddffea083ba36090af7eb7cad207b
 (bugfix)
  https://github.com/openssl/openssl/pull/17083 (test case)

  [Test Plan]

   * https://github.com/openssl/openssl/issues/17023 lists multiple ways
  how one can trigger the issue at hand, but also test case implements
  this issue too by explicitly attempting to load an engine multiple
  times and checking that it is operational.

  The test a is run during the build as part of the upstream regression
  test suite, for the shared library build (as static build does not
  support engines), so you'll see one pass and one skip in the log.

  [Where problems could occur]

   * Separately we have started to fix userspace packages that
  needlessly load configuration files multiple times, which used to
  trigger this issue. The codepaths changed are with engine use, how
  they are loaded/unloaded/used. It is possible that this fix will make
  some engines to start working and be used resulting in new behaviour.
  But also exposing bugs in the engines that previously were installed &
  configured but not actually used.

  [Other Info]

   * Previous bug reports about this issues are:
  https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518
  https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528

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


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


[Touch-packages] [Bug 1951943] Re: Engine crashes when loading the configuration more than once

2021-11-26 Thread Łukasz Zemczak
Hello Dimitri, or anyone else affected,

Accepted openssl into impish-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/1.1.1l-1ubuntu1.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-impish

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

Title:
  Engine crashes when loading the configuration more than once

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Bionic:
  Confirmed
Status in openssl source package in Focal:
  In Progress
Status in openssl source package in Hirsute:
  In Progress
Status in openssl source package in Impish:
  Fix Committed
Status in openssl source package in Jammy:
  Confirmed

Bug description:
  [Impact]

   * Engine crashes when loading the configuration more than once

   * Upstream started to avoid loading engines twice by using dynamic
  ids to track the loaded engines correctly

   * OpenSSL 3
  
https://github.com/openssl/openssl/commit/81c11349c2a0e945aa3dfc6bd81c957363dd2011
 (bugfix)
  
https://github.com/openssl/openssl/commit/38e2957249c90317a26a080c7e7eb186dd5b6598
 (test case)

   * OpenSSL 1.1.1 backports:
  
https://github.com/openssl/openssl/commit/9b06ebb1edfddffea083ba36090af7eb7cad207b
 (bugfix)
  https://github.com/openssl/openssl/pull/17083 (test case)

  [Test Plan]

   * https://github.com/openssl/openssl/issues/17023 lists multiple ways
  how one can trigger the issue at hand, but also test case implements
  this issue too by explicitly attempting to load an engine multiple
  times and checking that it is operational.

  The test a is run during the build as part of the upstream regression
  test suite, for the shared library build (as static build does not
  support engines), so you'll see one pass and one skip in the log.

  [Where problems could occur]

   * Separately we have started to fix userspace packages that
  needlessly load configuration files multiple times, which used to
  trigger this issue. The codepaths changed are with engine use, how
  they are loaded/unloaded/used. It is possible that this fix will make
  some engines to start working and be used resulting in new behaviour.
  But also exposing bugs in the engines that previously were installed &
  configured but not actually used.

  [Other Info]

   * Previous bug reports about this issues are:
  https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1921518
  https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1940528

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


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


[Touch-packages] [Bug 1921518] Update Released

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

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

Title:
  OpenSSL "double free" error

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

Bug description:
  [Impact]
  openssl config file is being loaded twice, causing engines to be loaded twice 
if specified therein, causing double free errors and other strange behavior.

  [Test plan]
  Run the command of the package being tested in

  gdb  -ex "break CONF_modules_load_file" -ex "run" --args

  and make sure it only breaks one.

  Regression test:

  In default Ubuntu configuration, either no openssl configuration is provided, 
or it contains no settings that affect wget. This code path changes how/when 
openssl configuration is loaded and used by openssl. One should verify that:
  1) wget continues to work without openssl.cnf
  2) wget continues to work with stock ubuntu unmodified openssl.cnf
  3) wget continue to honor and use custom TLS settings that one may have 
specified in openssl.cnf (for example custom engine)

  
  [Where problems could occur]

  wget: This is an upstream change that changes initialization and is in
  use in later releases. Since it mostly removes an unneeded call to the
  load file function, a regression could be a config file being ignored,
  but it seems unlikely given the use in later releases

  
  [Original bug report]
  "double free" error is seen when using curl utility. Error is from 
libcrypto.so which is part of the OpenSSL package. This happens only when 
OpenSSL is configured to use a dynamic engine.

  OpenSSL version is 1.1.1f

  The issue is not encountered if
  http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead.

  OpenSSL can be configured to use a dynamic engine by editing the
  default openssl config file which is located at '/etc/ssl/openssl.cnf'
  on Ubuntu systems.

  On Bluefield systems, config diff to enable PKA dynamic engine, is as
  below:

  +openssl_conf = conf_section
  +
   # Extra OBJECT IDENTIFIER info:
   #oid_file  = $ENV::HOME/.oid
   oid_section= new_oids

  +[ conf_section ]
  +engines = engine_section
  +
  +[ engine_section ]
  +bf = bf_section
  +
  +[ bf_section ]
  +engine_id=pka
  +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so
  +init=0
  +

  engine_id above refers to dynamic engine name/identifier.
  dynamic_path points to the .so file for the dynamic engine.

  # curl -O https://tpo.pe/pathogen.vim

  double free or corruption (out)

  Aborted (core dumped)

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


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


[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

2021-11-25 Thread Łukasz Zemczak
Hey guys, sorry for taking so long to comment. I agree with Eric here
that we should get this patch upstreamed. Since we're only seeing this
issue on bionic, I think it's safe to only backport it to bionic - but
preferably after it's submitted upstream and some upstream people
eyeballing it. It's always useful to get upstream's input on the changes
we want to propose here + this will not be a dangling bionic-only change
that way.

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

Title:
  ipconfig does not honour user-requested timeouts in some cases

Status in klibc package in Ubuntu:
  New
Status in klibc source package in Bionic:
  In Progress

Bug description:
  
  [Impact]
  In some cases, ipconfig can take a longer time than the user-specified 
timeouts, causing unexpected delays.

  [Test Plan]
  Any situation where ipconfig encounters an error sending the DHCP packet, it 
will automatically set a delay of 10 seconds, which could be longer than the 
user-specified timeout. It can be reproduced by creating a dummy interface and 
attempting to run ipconfig on it with a timeout value of less than 10:

  # ip link add eth1 type dummy
  # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
  Thu Nov 18 04:46:13 EST 2021
  IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  Thu Nov 18 04:46:23 EST 2021

  ^ Notice above, ipconfig thinks that it waited 2 seconds, but the
  timestamps show an actual delay of 10 seconds.

  [Where problems could occur]
  Please see reproduction steps above. We are seeing this in production too 
(see comment #2).

  [Other Info]
  A patch to fix the issue is being proposed here. It is a safe fix - it only 
checks before going into sleep that the timeout never exceeds the 
user-requested value.

  [Original Description]

  In some cases, ipconfig can take longer than the user-specified
  timeouts, causing unexpected delays.

  in main.c, in function loop(), the process can go into
  process_timeout_event() (or process_receive_event() ) and if it
  encounters an error situation, will set an attempt to "try again
  later" at time equal now + 10 seconds by setting

  s->expire = now + 10;

  This can happen at any time during the main event loop, which can end
  up extending the user-specified timeout if "now + 10" is greater than
  "start_time + user-specified-timeout".

  I believe a patch like the following is needed to avoid this problem:

  --- a/usr/kinit/ipconfig/main.c
  +++ b/usr/kinit/ipconfig/main.c
  @@ -437,6 +437,13 @@ static int loop(void)

  if (timeout > s->expire - now.tv_sec)
  timeout = s->expire - now.tv_sec;
  +
  +   /* Compensate for already-lost time */
  +   gettimeofday(, NULL);
  +   if (now.tv_sec + timeout > start + loop_timeout) {
  +   timeout = loop_timeout - (now.tv_sec - start);
  +   printf("Lowered timeout to match user request 
= (%d s) \n", timeout);
  +   }
  }

  I believe the current behaviour is buggy. This is confirmed when the
  following line is executed:

  if (loop_timeout >= 0 &&
  now.tv_sec - start >= loop_timeout) {
  printf("IP-Config: no response after %d "
     "secs - giving up\n", loop_timeout);
  rc = -1;
  goto bail;
  }

  'loop_timeout' is the user-specified time-out. With a value of 2, in
  case of error, this line prints:

  IP-Config: no response after 2 secs - giving up

  So it thinks that it waited 2 seconds - however, in reality it had
  actually waited for 10 seconds.

  The suggested code-change ensures that the timeout that is actually
  used never exceeds the user-specified timeout.

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


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


[Touch-packages] [Bug 1940528] Re: curl 7.68 does not init OpenSSL correctly

2021-11-15 Thread Łukasz Zemczak
Hello Dimitri, or anyone else affected,

Accepted curl into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/curl/7.68.0-1ubuntu2.8
in a few hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  curl 7.68 does not init OpenSSL correctly

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Bionic:
  New
Status in curl source package in Focal:
  Fix Committed

Bug description:
  [Impact]

   * curl 7.68 does not correctly use OpenSSL 1.1.0+ api to init OpenSSL
  global state prior to executing any OpenSSL APIs. This may lead to
  duplicate engine initiation, which upon engine unload may cause use-
  after-free or double-free of any methods that engine installs. This
  has been fixed in curl 7.74 by correctly calling OpenSSL init api
  prior to any other calls to OpenSSL apis.

  [Test Plan]

   * This should be reproducible with any engines that allocate &
  register methods, and free them upon engine unload. Then use curl with
  openssl backend to test for corrupted stack.

   * I.e. on arm64, compile and configure pka engine from
  
https://github.com/Mellanox/pka/commit/b0f32fa05298bf9e3997ea43fc1c11b90e0d662f
  (i.e. without the double-free protections proposed in
  https://github.com/Mellanox/pka/pull/37 ) on any arm64 hardware, there
  is no need for the engine to actually work or have access to anything,
  as the issue is reproducible when engine is enabled but cannot be
  effectively used.

   * curl any https website

  ...
  PKA_DEV: pka_dev_open_ring_vfio: error: failed to get ring 50 device name
  PKA_ENGINE: PKA instance is invalid
  PKA_ENGINE: failed to retrieve valid instance
  100   338  100   3380 0   3520  0 --:--:-- --:--:-- --:--:--  3520
  (exit status 0)

  is good output from fixed curl.

  Whereas:

  PKA_ENGINE: PKA instance is invalid
  PKA_ENGINE: failed to retrieve valid instance
  100   338  100   3380 0   1169  0 --:--:-- --:--:-- --:--:--  1169
  Segmentation fault (core dumped)
  (exit status non-zero)

  is bad output from currently broken curl.

  [Where problems could occur]

   * Correctly calling OpenSSL init function prior to any other OpenSSL
  apis changes the behaviour of the library slightly - specifically
  openssl configuration file and engines are initialised and loaded
  earlier, meaning that site-local customizations are applied correctly
  whenever using curl cli utility or libcurl4 (the openssl version of
  curl). This will make engine support working correctly across the
  board. However, if one has missconfigured openssl conf and
  missconfigured engines which are now actually attempted to be used one
  may experience unexpected behaviour changes (since potentially
  existing configuration was not actually taking effect).

  [Other Info]
   
   * References:
  https://github.com/curl/curl/commit/1835cb916e0d40eb8bc1165d5627a0b64f911bac
  https://github.com/openssl/openssl/issues/13548
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518

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


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


[Touch-packages] [Bug 1921518] Re: OpenSSL "double free" error

2021-11-15 Thread Łukasz Zemczak
Hello Mahantesh, or anyone else affected,

Accepted wget into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/wget/1.20.3-1ubuntu2
in a few hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  OpenSSL "double free" error

Status in openssl package in Ubuntu:
  Incomplete
Status in wget package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Incomplete
Status in wget source package in Focal:
  Fix Committed

Bug description:
  [Impact]
  openssl config file is being loaded twice, causing engines to be loaded twice 
if specified therein, causing double free errors and other strange behavior.

  [Test plan]
  Run the command of the package being tested in

  gdb  -ex "break CONF_modules_load_file" -ex "run" --args

  and make sure it only breaks one.

  Regression test:

  In default Ubuntu configuration, either no openssl configuration is provided, 
or it contains no settings that affect wget. This code path changes how/when 
openssl configuration is loaded and used by openssl. One should verify that:
  1) wget continues to work without openssl.cnf
  2) wget continues to work with stock ubuntu unmodified openssl.cnf
  3) wget continue to honor and use custom TLS settings that one may have 
specified in openssl.cnf (for example custom engine)

  
  [Where problems could occur]

  wget: This is an upstream change that changes initialization and is in
  use in later releases. Since it mostly removes an unneeded call to the
  load file function, a regression could be a config file being ignored,
  but it seems unlikely given the use in later releases

  
  [Original bug report]
  "double free" error is seen when using curl utility. Error is from 
libcrypto.so which is part of the OpenSSL package. This happens only when 
OpenSSL is configured to use a dynamic engine.

  OpenSSL version is 1.1.1f

  The issue is not encountered if
  http://www.openssl.org/source/openssl-1.1.1f.tar.gz is used instead.

  OpenSSL can be configured to use a dynamic engine by editing the
  default openssl config file which is located at '/etc/ssl/openssl.cnf'
  on Ubuntu systems.

  On Bluefield systems, config diff to enable PKA dynamic engine, is as
  below:

  +openssl_conf = conf_section
  +
   # Extra OBJECT IDENTIFIER info:
   #oid_file  = $ENV::HOME/.oid
   oid_section= new_oids

  +[ conf_section ]
  +engines = engine_section
  +
  +[ engine_section ]
  +bf = bf_section
  +
  +[ bf_section ]
  +engine_id=pka
  +dynamic_path=/usr/lib/aarch64-linux-gnu/engines-1.1/pka.so
  +init=0
  +

  engine_id above refers to dynamic engine name/identifier.
  dynamic_path points to the .so file for the dynamic engine.

  # curl -O https://tpo.pe/pathogen.vim

  double free or corruption (out)

  Aborted (core dumped)

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


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


[Touch-packages] [Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18

2021-11-08 Thread Łukasz Zemczak
Thank you Michael for verifying this! As per my earlier question during
our last-week's sync: do you think it would be possible to have this
running for instance as part of the coreXX-edge testing that Sergio is
doing? Since we'd like to make sure we don't reintroduce this issue at
some point by accident.

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

Title:
  systemd randomly fails to activate mount units in Ubuntu Core 18

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  Since a month or so, we've been seeing random failures in our snapd
  spread tests where systemd could not start the mount unit associated
  with a snap because of a failed dependency.

  The issue is described in the comments to PR
  https://github.com/snapcore/snapd/pull/10935, but I'll summarize it
  here.

  When starting a snap, snapd creates a mount unit to mount the snap's
  squashfs (the template is
  
https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205).
  The snapd asks systemd to reload the configuration, and starts the
  mount unit.

  The failure we've observed is that sometimes systemd decides to stop
  our mount unit (search for "Unmounting Mount unit for test-snapd-svc-
  flip-flop" in the attached log), and then tries to reactivate it
  again, and at that point it fails.

  When I asked for help, Lukas pointed out that the latest update
  contains a patch that is related to reload handling and mount units:
  
http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz
  (the patch itself is better visible at
  
https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656).
  When looking at the systemd git log, though, I noticed another patch
  that was applied shortly after this one, which also seems related but
  was not backported:
  
https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0

  Since the stopping of our mount unit happens immediately after a
  systemd reload, it actually seems very likely that the inclusion of
  f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what
  causes our woes (though, indeed, the issue is not reliably
  reproducible, so we cannot be sure).

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


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


[Touch-packages] [Bug 1917920] Update Released

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

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

Title:
  magic-proxy broke with iptables 1.8.7-1ubuntu2

Status in launchpad-buildd:
  Invalid
Status in iptables package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in lxd package in Ubuntu:
  Invalid
Status in iptables source package in Bionic:
  Invalid
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in lxd source package in Bionic:
  Invalid
Status in iptables source package in Focal:
  Invalid
Status in livecd-rootfs source package in Focal:
  Fix Committed
Status in lxd source package in Focal:
  Invalid
Status in iptables source package in Hirsute:
  Invalid
Status in livecd-rootfs source package in Hirsute:
  Fix Committed
Status in lxd source package in Hirsute:
  Invalid

Bug description:
  [Impact]
  The fixes for this bug (including the fixes for LP:#1944906) need to be 
backported to hirsute, focal and bionic) to be able to re-enable  the 
"repo-snapshot-stamp" feature for image builds. That feature is important to 
get consistent image builds (means the same set of packages included in the 
different images) when doing multiple builds (eg. for AWS, Azure and GCE).

  [Test Plan]
  - build a livecd-rootfs image with the changes for every series in a PPA
  - Do build an image with the livecd-rootfs from the PPA and enable the 
repo-snapshot-stamp feature
  - Check that the build did not fail or hang

  [Where problems could occur]
  The codepath that will be changed is only executed in livecd-rootfs if the 
repo-snapshot-stamp feature is enabled. And that feature is currently broken so 
it shouldn't be enabled anywhere.

  [Original description]

  when iptables got upgraded from 1.8.5-3ubuntu4 to 1.8.7-1ubuntu2 magic
  proxy stopped working in livecd-rootfs.

  It does very simple thing:

  iptables -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner
  daemon -j REDIRECT --to 8080

  inside hirsute lxd container, with quite high privileges, in a bionic
  VM, running 4.15 kernel.

  With 1.8.5 above worked fine, with 1.8.7 somehow there was no outbound
  connectivity the very first http networking command after the above
  call would just hang indefinitely.

  However, if one does this instead:

  iptables -vv -t nat -S
  iptables-legacy -vv -t nat -S
  iptables -vv -t nat -A OUTPUT -p tcp --dport 80 -m owner ! --uid-owner daemon 
-j REDIRECT --to 8080

  somehow magically everything starts to work fine.

  weird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/launchpad-buildd/+bug/1917920/+subscriptions


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


[Touch-packages] [Bug 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18

2021-11-05 Thread Łukasz Zemczak
** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Lukas Märdian (slyon)

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

Title:
  systemd randomly fails to activate mount units in Ubuntu Core 18

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Jammy:
  New

Bug description:
  Since a month or so, we've been seeing random failures in our snapd
  spread tests where systemd could not start the mount unit associated
  with a snap because of a failed dependency.

  The issue is described in the comments to PR
  https://github.com/snapcore/snapd/pull/10935, but I'll summarize it
  here.

  When starting a snap, snapd creates a mount unit to mount the snap's
  squashfs (the template is
  
https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205).
  The snapd asks systemd to reload the configuration, and starts the
  mount unit.

  The failure we've observed is that sometimes systemd decides to stop
  our mount unit (search for "Unmounting Mount unit for test-snapd-svc-
  flip-flop" in the attached log), and then tries to reactivate it
  again, and at that point it fails.

  When I asked for help, Lukas pointed out that the latest update
  contains a patch that is related to reload handling and mount units:
  
http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz
  (the patch itself is better visible at
  
https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656).
  When looking at the systemd git log, though, I noticed another patch
  that was applied shortly after this one, which also seems related but
  was not backported:
  
https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0

  Since the stopping of our mount unit happens immediately after a
  systemd reload, it actually seems very likely that the inclusion of
  f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what
  causes our woes (though, indeed, the issue is not reliably
  reproducible, so we cannot be sure).

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


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


[Touch-packages] [Bug 1949116] Re: libgl1-mesa-dri depends on libllvm12 from universe

2021-11-03 Thread Łukasz Zemczak
Ok, promoted both the source and the one binary package:

$ change-override -c main -s hirsute-updates -t llvm-toolchain-12 
Override component to main
llvm-toolchain-12 1:12.0.0-3ubuntu1~21.04.2 in hirsute: universe/misc -> main
Override [y|N]? y
1 publication overridden.
$ change-override -c main -s hirsute-updates libllvm12 
Override component to main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute amd64: 
universe/libs/optional/100% -> main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute arm64: 
universe/libs/optional/100% -> main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute armhf: 
universe/libs/optional/100% -> main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute i386: 
universe/libs/optional/100% -> main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute ppc64el: 
universe/libs/optional/100% -> main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute riscv64: 
universe/libs/optional/100% -> main
libllvm12 1:12.0.0-3ubuntu1~21.04.2 in hirsute s390x: 
universe/libs/optional/100% -> main
Override [y|N]? y
7 publications overridden.

** Changed in: mesa (Ubuntu Hirsute)
   Status: New => Fix Committed

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

Title:
  libgl1-mesa-dri depends on libllvm12 from universe

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU
  bug 1932311) on a system that does not have universe enabled because
  it depends on libllvm12 from universe. This was not the case with the
  version of libgl1-mesa-dri in the release pocket because it depended
  upon libllvm11.

  (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

  (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri
  Package: libgl1-mesa-dri
  Architecture: amd64
  Version: 21.0.3-0ubuntu0.3
  Multi-Arch: same
  Priority: optional
  Section: libs
  Source: mesa
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian X Strike Force 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 37016
  Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 
2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31),
  libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 
3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s
  vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 
1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4)
  Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb

  This is blocking some CPC builds:
  
https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039

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


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


[Touch-packages] [Bug 1949116] Re: libgl1-mesa-dri depends on libllvm12 from universe

2021-11-03 Thread Łukasz Zemczak
Ok, promoting this, but I'll also make sure that the security team is
aware of that. Let's ping them.

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

Title:
  libgl1-mesa-dri depends on libllvm12 from universe

Status in mesa package in Ubuntu:
  Invalid
Status in mesa source package in Hirsute:
  Fix Committed

Bug description:
  It's not possible to install libgl1-mesa-dri from hirsute-updates (SRU
  bug 1932311) on a system that does not have universe enabled because
  it depends on libllvm12 from universe. This was not the case with the
  version of libgl1-mesa-dri in the release pocket because it depended
  upon libllvm11.

  (hirsute-amd64)root@impulse:~# apt-get install libgl1-mesa-dri
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgl1-mesa-dri : Depends: libllvm12 (>= 1:9~svn298832-1~) but it is not 
installable
  E: Unable to correct problems, you have held broken packages.

  (hirsute-amd64)root@impulse:~# apt-cache show libgl1-mesa-dri
  Package: libgl1-mesa-dri
  Architecture: amd64
  Version: 21.0.3-0ubuntu0.3
  Multi-Arch: same
  Priority: optional
  Section: libs
  Source: mesa
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian X Strike Force 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 37016
  Depends: libc6 (>= 2.33), libdrm-amdgpu1 (>= 2.4.100), libdrm-intel1 (>= 
2.4.38), libdrm-nouveau2 (>= 2.4.66), libdrm-radeon1 (>= 2.4.31),
  libdrm2 (>= 2.4.75), libelf1 (>= 0.142), libexpat1 (>= 2.0.1), libgcc-s1 (>= 
3.4), libglapi-mesa (= 21.0.3-0ubuntu0.3), libllvm12 (>= 1:9~s
  vn298832-1~), libsensors5 (>= 1:3.5.0), libstdc++6 (>= 5.2), libvulkan1 (>= 
1.2.131.2), libzstd1 (>= 1.3.2), zlib1g (>= 1:1.1.4)
  Filename: pool/main/m/mesa/libgl1-mesa-dri_21.0.3-0ubuntu0.3_amd64.deb

  This is blocking some CPC builds:
  
https://launchpad.net/~cloud-images/+livefs/ubuntu/hirsute/cpc-development/+build/306039

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


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


  1   2   3   4   5   6   7   8   9   10   >