date:20211124

** Tags added: impish

** Changed in: qtwebkit-opensource-src (Ubuntu Impish)
   Status: New => In Progress

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

Title:
  webkit javascript segmentation fault

Status in Ubuntu on IBM z Systems:
  In Progress
Status in qtwebkit-opensource-src package in Ubuntu:
  In Progress
Status in qtwebkit-opensource-src source package in Focal:
  New
Status in qtwebkit-opensource-src source package in Hirsute:
  New
Status in qtwebkit-opensource-src source package in Impish:
  In Progress
Status in qtwebkit-opensource-src source package in Jammy:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

   * WebKit Javascript engine is causing a segmentation fault on big
  endian (s390x) systems.

   * This happens for example when transferring an html to a pdf file
  using wkhtmltopdf.

   * The fix is relatively simple with changing loadisFromInstruction to 
loadpFromInstruction
 in macro getProperty(slow), which solves this unpleasant situation.

   * The JIT ocde is 32bit (even on 64bit systems),
 hence is crucial to make sure the lower part of a 64bit value is taken on 
big endian systems.

  [Test Plan]

   * Testing is very straight forward by following these steps:

   * install the following packages (incl. their dependencies):
 $ sudo apt install libqt5webkit5 wkhtmltopdf

   * create an html file like this:
 $ vi index.html
 $ cat index.html
 
 
   
   
 
   
 
   
 

   * create a JavaScript file like this:
 $ vi min.js
 $ cat min.js
 var i = Math.max

   * call wkhtmltopdf to process the local files:
 $ wkhtmltopdf --enable-local-file-access index.html test.pdf

   * if it's broken one gets this output:
 Loading page (1/2)
 Segmentation fault (core dumped) ] 50%
 and no pdf file was generated:
 $ ls *.pdf
 ls: cannot access '*.pdf': No such file or directory

   * in case it's fixed one gets this output:
 Loading page (1/2)
 Printing pages (2/2)   
 Done   
 and a pdf file was generated and in placed in the current directory (with 
more than 0 bytes size):
 $ ls -l ./*.pdf
 -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf

  [Where problems could occur]

   * While this issue only affects big endian systems (like s390x),
 a bad fix may have an impact on little endian systems, too
 for example in case the wrong function got used in the macro.

   * But loadpFromInstruction is known to work for LE and BE systems;

   * and on top cross-architecture builds were done:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470

   * and tested on s390x (if the fix works) and on non-s390x (regression
  testing).

   * The changes are otherwise very limited, just:
 macro getProperty(slow)
 -loadisFromInstruction(6, t1)
 +loadpFromInstruction(6, t1)
 hence I think there is not much more to say.

  [Other Info]
   
   * The maintainer of the Debian packages (Dmitry Shachnev)
 is going to add this to the Debian package, too.

   * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs
  are ongoing.

   * The issue does not occur with the very latest upstream version anymore,
 and was fixed in a similar way as part of a commit
 that fixes numerous other CLoop issues on top:
 "Fix all CLoop JSC test failures (including some LLInt bugs due to recent 
bytecode format change)."
 commit 3fdde71c7d95d758a61fcbc4c58168616794c102

  __

  == Comment: #0 - Andreas Krebbel  - 2021-11-15 
09:29:44 ==
  ---Problem Description---
  Segmentation fault from WebKit Javascript engine

  Contact Information = andreas.kreb...@de.ibm.com

  ---uname output---
  Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 
s390x s390x s390x GNU/Linux

  Machine Type = IBM Z

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   index.html:
  
  
    
    

    
  
    
  

  min.js:
  var i = Math.max

  wkhtmltopdf index.html test.pdf
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Loading page (1/2)
  Segmentation fault (core dumped) ] 17%

  Userspace tool common name: wkhtmltopdf

  The userspace tool has the following bit modes: 64

  Userspace rpm: libqt5webkit5

  Userspace tool obtained from project website:  na

  *Additional Instructions for andreas.kreb...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Andreas Krebbel  - 2021-11-15 
09:44:04 ==
  In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes 
the property offset as pointer size

[Touch-packages] [Bug 1951470] Re: webkit javascript segmentation fault

qtwebkit debdiff (impish)

** Patch added: "qtwebkit debdiff (impish)"
   
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1951470/+attachment/5543117/+files/debdiff-qtwebkit-lp1951470-impish.patch

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

Title:
  webkit javascript segmentation fault

Status in Ubuntu on IBM z Systems:
  In Progress
Status in qtwebkit-opensource-src package in Ubuntu:
  In Progress
Status in qtwebkit-opensource-src source package in Focal:
  New
Status in qtwebkit-opensource-src source package in Hirsute:
  New
Status in qtwebkit-opensource-src source package in Impish:
  New
Status in qtwebkit-opensource-src source package in Jammy:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

   * WebKit Javascript engine is causing a segmentation fault on big
  endian (s390x) systems.

   * This happens for example when transferring an html to a pdf file
  using wkhtmltopdf.

   * The fix is relatively simple with changing loadisFromInstruction to 
loadpFromInstruction
 in macro getProperty(slow), which solves this unpleasant situation.

   * The JIT ocde is 32bit (even on 64bit systems),
 hence is crucial to make sure the lower part of a 64bit value is taken on 
big endian systems.

  [Test Plan]

   * Testing is very straight forward by following these steps:

   * install the following packages (incl. their dependencies):
 $ sudo apt install libqt5webkit5 wkhtmltopdf

   * create an html file like this:
 $ vi index.html
 $ cat index.html
 
 
   
   
 
   
 
   
 

   * create a JavaScript file like this:
 $ vi min.js
 $ cat min.js
 var i = Math.max

   * call wkhtmltopdf to process the local files:
 $ wkhtmltopdf --enable-local-file-access index.html test.pdf

   * if it's broken one gets this output:
 Loading page (1/2)
 Segmentation fault (core dumped) ] 50%
 and no pdf file was generated:
 $ ls *.pdf
 ls: cannot access '*.pdf': No such file or directory

   * in case it's fixed one gets this output:
 Loading page (1/2)
 Printing pages (2/2)   
 Done   
 and a pdf file was generated and in placed in the current directory (with 
more than 0 bytes size):
 $ ls -l ./*.pdf
 -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf

  [Where problems could occur]

   * While this issue only affects big endian systems (like s390x),
 a bad fix may have an impact on little endian systems, too
 for example in case the wrong function got used in the macro.

   * But loadpFromInstruction is known to work for LE and BE systems;

   * and on top cross-architecture builds were done:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470

   * and tested on s390x (if the fix works) and on non-s390x (regression
  testing).

   * The changes are otherwise very limited, just:
 macro getProperty(slow)
 -loadisFromInstruction(6, t1)
 +loadpFromInstruction(6, t1)
 hence I think there is not much more to say.

  [Other Info]
   
   * The maintainer of the Debian packages (Dmitry Shachnev)
 is going to add this to the Debian package, too.

   * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs
  are ongoing.

   * The issue does not occur with the very latest upstream version anymore,
 and was fixed in a similar way as part of a commit
 that fixes numerous other CLoop issues on top:
 "Fix all CLoop JSC test failures (including some LLInt bugs due to recent 
bytecode format change)."
 commit 3fdde71c7d95d758a61fcbc4c58168616794c102

  __

  == Comment: #0 - Andreas Krebbel  - 2021-11-15 
09:29:44 ==
  ---Problem Description---
  Segmentation fault from WebKit Javascript engine

  Contact Information = andreas.kreb...@de.ibm.com

  ---uname output---
  Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 
s390x s390x s390x GNU/Linux

  Machine Type = IBM Z

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   index.html:
  
  
    
    

    
  
    
  

  min.js:
  var i = Math.max

  wkhtmltopdf index.html test.pdf
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Loading page (1/2)
  Segmentation fault (core dumped) ] 17%

  Userspace tool common name: wkhtmltopdf

  The userspace tool has the following bit modes: 64

  Userspace rpm: libqt5webkit5

  Userspace tool obtained from project website:  na

  *Additional Instructions for andreas.kreb...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Andreas Krebbel  - 2021-11-15 
09:44:04 ==
  In CodeBlock

[Touch-packages] [Bug 1951470] Re: webkit javascript segmentation fault

** Merge proposal linked:
   
https://code.launchpad.net/~fheimes/ubuntu/+source/qtwebkit-opensource-src/+git/qtwebkit-opensource-src/+merge/412357

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

Title:
  webkit javascript segmentation fault

Status in Ubuntu on IBM z Systems:
  In Progress
Status in qtwebkit-opensource-src package in Ubuntu:
  In Progress
Status in qtwebkit-opensource-src source package in Focal:
  New
Status in qtwebkit-opensource-src source package in Hirsute:
  New
Status in qtwebkit-opensource-src source package in Impish:
  New
Status in qtwebkit-opensource-src source package in Jammy:
  In Progress

Bug description:
  SRU Justification:

  [Impact]

   * WebKit Javascript engine is causing a segmentation fault on big
  endian (s390x) systems.

   * This happens for example when transferring an html to a pdf file
  using wkhtmltopdf.

   * The fix is relatively simple with changing loadisFromInstruction to 
loadpFromInstruction
 in macro getProperty(slow), which solves this unpleasant situation.

   * The JIT ocde is 32bit (even on 64bit systems),
 hence is crucial to make sure the lower part of a 64bit value is taken on 
big endian systems.

  [Test Plan]

   * Testing is very straight forward by following these steps:

   * install the following packages (incl. their dependencies):
 $ sudo apt install libqt5webkit5 wkhtmltopdf

   * create an html file like this:
 $ vi index.html
 $ cat index.html
 
 
   
   
 
   
 
   
 

   * create a JavaScript file like this:
 $ vi min.js
 $ cat min.js
 var i = Math.max

   * call wkhtmltopdf to process the local files:
 $ wkhtmltopdf --enable-local-file-access index.html test.pdf

   * if it's broken one gets this output:
 Loading page (1/2)
 Segmentation fault (core dumped) ] 50%
 and no pdf file was generated:
 $ ls *.pdf
 ls: cannot access '*.pdf': No such file or directory

   * in case it's fixed one gets this output:
 Loading page (1/2)
 Printing pages (2/2)   
 Done   
 and a pdf file was generated and in placed in the current directory (with 
more than 0 bytes size):
 $ ls -l ./*.pdf
 -rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf

  [Where problems could occur]

   * While this issue only affects big endian systems (like s390x),
 a bad fix may have an impact on little endian systems, too
 for example in case the wrong function got used in the macro.

   * But loadpFromInstruction is known to work for LE and BE systems;

   * and on top cross-architecture builds were done:
 https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470

   * and tested on s390x (if the fix works) and on non-s390x (regression
  testing).

   * The changes are otherwise very limited, just:
 macro getProperty(slow)
 -loadisFromInstruction(6, t1)
 +loadpFromInstruction(6, t1)
 hence I think there is not much more to say.

  [Other Info]
   
   * The maintainer of the Debian packages (Dmitry Shachnev)
 is going to add this to the Debian package, too.

   * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs
  are ongoing.

   * The issue does not occur with the very latest upstream version anymore,
 and was fixed in a similar way as part of a commit
 that fixes numerous other CLoop issues on top:
 "Fix all CLoop JSC test failures (including some LLInt bugs due to recent 
bytecode format change)."
 commit 3fdde71c7d95d758a61fcbc4c58168616794c102

  __

  == Comment: #0 - Andreas Krebbel  - 2021-11-15 
09:29:44 ==
  ---Problem Description---
  Segmentation fault from WebKit Javascript engine

  Contact Information = andreas.kreb...@de.ibm.com

  ---uname output---
  Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 
s390x s390x s390x GNU/Linux

  Machine Type = IBM Z

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   index.html:
  
  
    
    

    
  
    
  

  min.js:
  var i = Math.max

  wkhtmltopdf index.html test.pdf
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Loading page (1/2)
  Segmentation fault (core dumped) ] 17%

  Userspace tool common name: wkhtmltopdf

  The userspace tool has the following bit modes: 64

  Userspace rpm: libqt5webkit5

  Userspace tool obtained from project website:  na

  *Additional Instructions for andreas.kreb...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Andreas Krebbel  - 2021-11-15 
09:44:04 ==
  In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes 
the pro

[Touch-packages] [Bug 1951827] Re: APT crashes with Segmentation fault

Closing as invalid directly then, as it's the wrong place to report and
no data about the crash seems to be available, so waiting 60 days for
expiry seems unnecessary.

** Changed in: apt (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  APT crashes with Segmentation fault

Status in apt package in Ubuntu:
  Invalid

Bug description:
  **System:**

  - OS Type: Linux

  - OS: Debian 10

  - APT / APT-utils version: 2.24

  
  **Bug description:**

  When trying to execute apt commands from the command line, apt crashes
  with the Segmentation fault error and nothing more.

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


-- 
Mailing list: https://launchpad.net/~touch-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] Re: Support manual firmware upgrading for Foxconn and Quectel modems.

2021-11-24 Thread Robie Basak

Before I was relying on the information presented here and the changelog
in the upload to consider regression risk. Today I reviewed the patches
in more detail expecting to find what has been described. What's going
on in 01_modem-quectel.patch? This says "add support for EM120/160 PCIe
modules" and it seems to be adding support for a PCIe variant of a modem
in the code that already supports a USB variant. But your changelog just
says "Support manual firmware upgrading" with no mention of support for
additional modems. Are you actually additionally adding support for this
modem hardware where support didn't exist previously? I see no mention
of additional additional modem support anywhere in this bug so far.

If so, then will you be able to test the regular functionality of these
modems - both USB and PCIe - during SRU verification please? Do you have
these two modems available? This would be to ensure that 1) the changes
to modemmanager that relate to the USB variant haven't regressed; and 2)
the changes to add support for the PCIe variant is actually working. If
you can do this, then please add this to the Test Plan. If not, then
further discussion is needed.

It looks like Impish no longer carries this patch as 1.16.6-2ubuntu1 was
removed, so we also need an upload of this to Impish please.

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

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. Prepare the modem’s firmware and install the firmware upgrading
application provided by Foxconn and Quectel
4. Using the firmware upgrading application to upgrade the modem’s firmware
5. Verify if the modem’s firmware upgrading is successful
6. Reboot
7. Verify if the upgraded modem firmware is still working

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

[Touch-packages] [Bug 1951827] Re: APT crashes with Segmentation fault

2021-11-24 Thread Michal Dziczkowski

This was only a informative bug report because Ubuntu and Debian share
many common packages.

This bug has appeared suddenly and without any warning or possibility to
backtrack, so it would be good that Ubuntu dev team was aware of it.

Have a nice day ;-)

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

Title:
  APT crashes with Segmentation fault

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  **System:**

  - OS Type: Linux

  - OS: Debian 10

  - APT / APT-utils version: 2.24

  
  **Bug description:**

  When trying to execute apt commands from the command line, apt crashes
  with the Segmentation fault error and nothing more.

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


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

[Touch-packages] [Bug 1951432] Re: fail to build from source

This bug was fixed in the package icu - 66.1-2ubuntu2.1

---
icu (66.1-2ubuntu2.1) focal-security; urgency=medium

  * SECURITY UPDATE: Double Free
- debian/patches/CVE-2021-30535-prereq.patch: Fix invalid free when
  using long locale name in Locale functions in
  source/common/locid.cpp.
- debian/patches/CVE-2021-30535.patch: Fix edge cases with baseName
  in setKeywordValue function in source/common/locid.cpp to
  prevent double free and protect from heap corruption.
- CVE-2021-30535
  * Fix failing tests causing build-time failures: (LP: #1951432)
- debian/patches/tzdata-2020f-tztest.patch: Add Time Zones data
  related to tzdata version 2020f in TestCanonicalID function in
  source/test/intltest/tztest.cpp to prevent tests from failing.
- debian/patches/tzdata-2021b-tests.patch: Fix TestCalendar function
  in source/test/cintltst/ccaltst.c and TestGenericAPI in
  source/test/intltest/tztest.cpp to accept tz.version with longer
  string size to prevent tests from failing.
- debian/patches/skip-tztests.patch: Skip specific Time Zones tests in
  TestAliasedNames and TestCanonicalID functions in
  source/test/intltest/tztest.cpp. They don't match with data from
  updated tzdata and needed to be skiped to prevent tests from failing.
  * Fix autopkg tests:
- debian/tests/control: add libicu-dev and pkg-config dependencies in
  smoke test, and build-essential dependency in build-test.
- debian/tests/smoke: change smoke test tool from icu-config (deprecated)
  to pkg-config.
- debian/tests/ustring.cpp: add 'using namespace icu'.

 -- Rodrigo Figueiredo Zaiden   Tue, 23
Nov 2021 11:50:52 -0300

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

Title:
  fail to build from source

Status in icu package in Ubuntu:
  Fix Released

Bug description:
  When building ICU package from source, Time Zones tests are failing, leading 
to a build failure.
  This is happening because for Ubuntu, ICU uses tzdata package to retrieve 
Time Zone information
  And, tzdata is updated but ICU tests are not.

  The tests that are failing are:
  1)TestAliasedNames, TestCanonicalID:
   TestAliasedNames {
   different at 8
   

   } ERRORS (1) in TestAliasedNames

   TestCanonicalID {
   FAIL: getCanonicalID(America/Coral_Harbour) returned 
America/Coral_Harbour expected:America/Cayman
   FAIL: getCanonicalID(America/Coral_Harbour) returned 
America/Coral_Harbour expected:America/Cayman
   FAIL: getCanonicalID(America/Coral_Harbour) returned 
America/Coral_Harbour expected:America/Cayman

   } ERRORS (3) in TestCanonicalID

  -- These does not have a fix in upstream and need to be fixed (hirsute
  and focal).

  There are other issues that have fixes in upstream and need to be patched:
  2) TestGenericAPI
   TestGenericAPI {
   FAIL: getTZDataVersion returned 2021a3

   } ERRORS (1) in TestGenericAPI

  -- https://github.com/unicode-org/icu/commit/7561cb28 need to be
  patched (hirsute and focal)

  3) TestCanonicalID
   TestCanonicalID {
   FAIL: getCanonicalID(Australia/Hobart) returned Australia/Hobart 
expected:Australia/Currie
   FAIL: getCanonicalID(Australia/Tasmania) returned Australia/Hobart 
expected:Australia/Currie
   FAIL: getCanonicalID(Australia/Hobart) returned Australia/Hobart 
expected:Australia/Currie
   FAIL: getCanonicalID(Australia/Tasmania) returned Australia/Hobart 
expected:Australia/Currie
   FAIL: getCanonicalID(Australia/Hobart) returned Australia/Hobart 
expected:Australia/Currie
   FAIL: getCanonicalID(Australia/Tasmania) returned Australia/Hobart 
expected:Australia/Currie

   } ERRORS (6) in TestCanonicalID

  -- https://github.com/unicode-org/icu/commit/25eb1510 need to be
  patched (focal)

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


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

[Touch-packages] [Bug 1951432] Re: fail to build from source

This bug was fixed in the package icu - 67.1-6ubuntu2.1

---
icu (67.1-6ubuntu2.1) hirsute-security; urgency=medium

  * SECURITY UPDATE: Double Free
- debian/patches/CVE-2021-30535-prereq.patch: Fix invalid free when
  using long locale name in Locale functions in
  source/common/locid.cpp.
- debian/patches/CVE-2021-30535.patch: Fix edge cases with baseName
  in setKeywordValue function in source/common/locid.cpp to
  prevent double free and protect from heap corruption.
- CVE-2021-30535
  * fix failing tests causing build-time failure: (LP: #1951432)
- debian/patches/tzdata-2021b-tests.patch: Fix TestCalendar function
  in source/test/cintltst/ccaltst.c and TestGenericAPI in
  source/test/intltest/tztest.cpp to accept tz.version with longer
  string size to prevent tests from failing.
- debian/patches/skip-tztests.patch: Skip specific Time Zones tests in
  TestAliasedNames and TestCanonicalID functions in
  source/test/intltest/tztest.cpp. They don't match with data from
  updated tzdata and needed to be skiped to prevent tests from failing.

 -- Rodrigo Figueiredo Zaiden   Thu, 18
Nov 2021 13:51:35 -0300

** Changed in: icu (Ubuntu)
   Status: In Progress => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-30535

** Changed in: icu (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  fail to build from source

Status in icu package in Ubuntu:
  Fix Released

Bug description:
  When building ICU package from source, Time Zones tests are failing, leading 
to a build failure.
  This is happening because for Ubuntu, ICU uses tzdata package to retrieve 
Time Zone information
  And, tzdata is updated but ICU tests are not.

  The tests that are failing are:
  1)TestAliasedNames, TestCanonicalID:
   TestAliasedNames {
   different at 8
   

   } ERRORS (1) in TestAliasedNames

   TestCanonicalID {
   FAIL: getCanonicalID(America/Coral_Harbour) returned 
America/Coral_Harbour expected:America/Cayman
   FAIL: getCanonicalID(America/Coral_Harbour) returned 
America/Coral_Harbour expected:America/Cayman
   FAIL: getCanonicalID(America/Coral_Harbour) returned 
America/Coral_Harbour expected:America/Cayman

   } ERRORS (3) in TestCanonicalID

  -- These does not have a fix in upstream and need to be fixed (hirsute
  and focal).

  There are other issues that have fixes in upstream and need to be patched:
  2) TestGenericAPI
   TestGenericAPI {
   FAIL: getTZDataVersion returned 2021a3

   } ERRORS (1) in TestGenericAPI

  -- https://github.com/unicode-org/icu/commit/7561cb28 need to be
  patched (hirsute and focal)

  3) TestCanonicalID
   TestCanonicalID {
   FAIL: getCanonicalID(Australia/Hobart) returned Australia/Hobart 
expected:Australia/Currie
   FAIL: getCanonicalID(Australia/Tasmania) returned Australia/Hobart 
expected:Australia/Currie
   FAIL: getCanonicalID(Australia/Hobart) returned Australia/Hobart 
expected:Australia/Currie
   FAIL: getCanonicalID(Australia/Tasmania) returned Australia/Hobart 
expected:Australia/Currie
   FAIL: getCanonicalID(Australia/Hobart) returned Australia/Hobart 
expected:Australia/Currie
   FAIL: getCanonicalID(Australia/Tasmania) returned Australia/Hobart 
expected:Australia/Currie

   } ERRORS (6) in TestCanonicalID

  -- https://github.com/unicode-org/icu/commit/25eb1510 need to be
  patched (focal)

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


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

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2021-11-24 Thread Sergio Durigan Junior

** Tags removed: server-todo

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  Confirmed
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  Fix Released
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1639452] Re: systemd ExecStartPre test config

2021-11-24 Thread Christian Ehrhardt 

** Changed in: dnsmasq (Ubuntu Bionic)
 Assignee: (unassigned) => Miriam España Acebal (mirespace)

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

Title:
  systemd ExecStartPre test config

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Bionic:
  Triaged
Status in dnsmasq source package in Focal:
  Triaged

Bug description:
  The standard configuration file of dnsmasq is complete commented out.
  The real configuration is saved in /etc/dnsmasq.d, so the test of
  systemd is a fake.

  In the Service Section of /lib/systemd/system/dnsmasq.service the
  ExecStartPre directive should be set to "/usr/sbin/dnsmasq --conf-
  dir=/etc/dnsmasq.d --test"

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


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

[Touch-packages] [Bug 1922464] Re: GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-daemon.plugins.xsettings' does not contain a key named 'antialiasing'

Sorry for the delay, I finally got back to that request but it's not as
simple as backporting the one patch, the codebase changed between .20
and .25 and other changes are needed. Would anyone interest to work on a
proper backport and testing, I personally doesn't really have the free
slots for doing that at the moment.

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

Title:
  GNOME 40: GTK3 apps crash with: Settings schema 'org.gnome.settings-
  daemon.plugins.xsettings' does not contain a key named 'antialiasing'

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Focal:
  Triaged

Bug description:
  Applications running with GTK < 3.24.26 crash when running under GNOME
  40. This was fixed in GTK 3.24.26 by MR
  https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3219

  Please package either current GTK 3 (3.24.28) or include the given MR
  in the current build.

  Thanks!

  Example crash:

  ```
  Starting program: /home/mjog/Projects/GNOME/geary/+build/test/test-client
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  [New Thread 0x7fffeb8a7640 (LWP 58239)]
  [New Thread 0x7fffeb086640 (LWP 58240)]
  [New Thread 0x7fffea839640 (LWP 58241)]

  (test-client:58235): GLib-GIO-ERROR **: 10:42:55.448: Settings schema
  'org.gnome.settings-daemon.plugins.xsettings' does not contain a key
  named 'antialiasing'

  Thread 1 "test-client" received signal SIGTRAP, Trace/breakpoint trap.
  0x774a5ea7 in g_log_structured_array () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  (gdb) bt
  #0  0x774a5ea7 in g_log_structured_array ()
  at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #1  0x774a62b9 in g_log_default_handler () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #2  0x774a64fe in g_logv () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #3  0x774a67b3 in g_log () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #4  0x7735d9d1 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #5  0x7735e030 in  () at /lib/x86_64-linux-gnu/libgio-2.0.so.0
  #6  0x773625d1 in g_settings_get_enum () at 
/lib/x86_64-linux-gnu/libgio-2.0.so.0
  #7  0x710d90ea in update_xft_settings (screen=0x55a8d810)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:404
  #8  0x710d3c7d in init_settings (screen=0x55a8d810)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:828
  #9  _gdk_wayland_screen_new (display=0x55a8a0e0)
  at wayland/../../../../../gdk/wayland/gdkscreen-wayland.c:1320
  #10 _gdk_wayland_display_open (display_name=)
  at wayland/../../../../../gdk/wayland/gdkdisplay-wayland.c:617
  #11 0x71072635 in gdk_display_manager_open_display
  (manager=, name=0x0) at 
../../../../gdk/gdkdisplaymanager.c:462
  #12 0x76d011fb in gtk_init_check (argc=, 
argv=)
  at ../../../../gtk/gtkmain.c:1110
  #13 gtk_init_check (argc=, argv=)
  at ../../../../gtk/gtkmain.c:1102
  #14 0x76d0122d in gtk_init (argc=, argv=)
  at ../../../../gtk/gtkmain.c:1167
  #15 0x555b4854 in _vala_main (args=0x7fffdda8, args_length1=1)
  at ../test/test-client.vala:32
  #16 0x555b5213 in main (argc=1, argv=0x7fffdda8) at 
../test/test-client.vala:9
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libgtk-3-0 3.24.25-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Sun Apr  4 11:11:05 2021
  InstallationDate: Installed on 2018-08-13 (964 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: gtk+3.0
  UpgradeStatus: Upgraded to hirsute on 2021-04-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1922464/+subscriptions


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

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

2021-11-24 Thread paquin pierre

I can confirm crash on latest 20.04 is still there.

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


-- 
Mailing list: https://launchpad.net/~touch-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-11-24 Thread Alberto Mardegan

I can confirm that Ratchanan's patches work (well, I only tried the one
on timedated, as the one on timedatectl is not essential to fix this
bug).

But I don't think that it should be treated separately from the existing
patch we have, so I'm attaching a refreshed patch which includes
Ratchanan's change. Still, we probably want to explore other solutions,
since Dan (@ddstreet) is also right that carrying hacks for 7 years is
something we should avoid doing.

But I don't have many alternative ideas :-( Unfortunately, bind-mounting
/etc/writable/localtime over /etc/localtime does not work, because when
mounting, the kernel follows all symbolic links, so we end up bind-
mounting the timezone file (for example
"/usr/share/zoneinfo/Europe/Berlin") on top of itself :-)

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

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

[Touch-packages] [Bug 1650688] Re: timedatectl set-timezone fails on UC16

2021-11-24 Thread Alberto Mardegan

** Patch added: "Support-system-image-read-only-etc.patch"

https://bugs.launchpad.net/snappy/+bug/1650688/+attachment/5543088/+files/Support-system-image-read-only-etc.patch

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

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 the localtime symbolic link with a relative path to
the zoneinfo directory, which results in an invalid link.

$ sudo timedatectl set-timezone America/Detroit

$ sudo timedatectl
Local time: Fri 2016-12-16 18:18:49 EST
Universal time: Fri 2016-12-16 23:18:49 UTC
RTC time: Fri 2016-12-16 23:18:49
Time zone: America/Detroit (EST, -0500)
Network time

[Touch-packages] [Bug 1952107] [NEW] Google Contacts API Deprecated

2021-11-24 Thread Yeshayohu Zirkind

Public bug reported:

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

** Affects: evolution-data-server (Ubuntu)
 Importance: Undecided
 Status: New

-- 
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 package in Ubuntu:
  New

Bug description:
  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/ubuntu/+source/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 1951943] Re: Engine crashes when loading the configuration more than once

** Changed in: openssl (Ubuntu Focal)
   Status: New => In Progress

** Description changed:

  [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 are unfortunately *SKIPPED* during the build as part of the
- upstream regression test suite
+ 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

-- 
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:
  New
Status in openssl source package in Bionic:
  New
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:
  In Progress
Status in openssl source package in Jammy:
  New

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

** Description changed:

  [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 is run during the build as part of the upstream regression test
- suite
+ The test are unfortunately *SKIPPED* during the build as part of the
+ upstream regression test suite
  
  [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

-- 
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:
  New
Status in openssl source package in Bionic:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Hirsute:
  In Progress
Status in openssl source package in Impish:
  In Progress
Status in openssl source package in Jammy:
  New

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 are unfortunately *SKIPPED* during the build as part of the
  upstream regression test suite

  [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 1657897] Re: Failure to report rhosts

2021-11-24 Thread Athos Ribeiro

A patch was proposed (and merged) in the linked upstream bug:

https://github.com/cyrusimap/cyrus-sasl/pull/6

This seems to be marked for the 2.2.0 release.

The next steps here would be to backport and verify the fix.

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

Title:
  Failure to report rhosts

Status in Cyrus-sasl2:
  New
Status in cyrus-sasl2 package in Ubuntu:
  Triaged

Bug description:
  
  When using sasl2-bin and saslauthd it will fail to work correctly with pam.

  The first major problem is that that it will fail to report the rhost
  address in the log which means auth failures cannot be policed and no
  useful data (the ip address) is reported to the log file. Example
  below during a password brute force attempt.

  Jan 19 21:57:16 mail saslauthd[1534]: pam_unix(smtp:auth): check pass; user 
unknown
  Jan 19 21:57:16 mail saslauthd[1534]: pam_unix(smtp:auth): authentication 
failure; logname= uid=0 euid=0 tty= ruser= rhost=

  The other issue is that it would be great to be able to ip restrict
  logins based on pam module configuration. Based on previous reading
  and as far as I can tell the remote ip address is not supported
  between the imap/pop/smtp process and sasl2 is it possible to add
  support for this?

  Technically this is a long standing security issue because fail2ban
  cannot be used to process the syslog file and auto block the host
  during brute force password attempts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/1657897/+subscriptions


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

[Touch-packages] [Bug 1948533] Re: (No Subject)

2021-11-24 Thread Tiphen Ti

for Marc Deslauriers

Hi,
openvpn doesnt create any file in /etc/NetworkManager/system-connections
(I dont have any script up option in my openvpn config files since I want 
network manager to define dns not openvpn, it worked perfect untill ubunut 
version 21.1

here for the wired connection: in /etc/NetworkManager/system-connections


[ipv4]
dns=1.1.1.1;
dns-search=
ignore-auto-dns=true
method=auto

[ipv6]
addr-gen-mode=stable-privacy
dns-search=
method=disabled



>
> If you look into the openvpn configuration file that Network Manager
> creates for your connection in /etc/NetworkManager/system-connections,
> could you please paste the [ipv4] and [ipv6] sections?
>
> ** No longer affects: ubuntu
>
> ** Changed in: network-manager (Ubuntu)
> Status: New => Incomplete
>
> ** Information type changed from Public Security to Public
>
> -
>
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1948533
>
> Title:
> any dns defined in network-manager doesnt go in openvpn tunnel (leaks
> on gnome/mate/xubuntu only in 21.10)
>
> Status in network-manager package in Ubuntu:
> Incomplete
>
> Bug description:
> in all linux including ubuntu up to version 21.04, when dns is set to not 
> automatic in network manager and one dns is set manually (exemple 1.1.1.1) 
> when openvpn is used the dns is going through the vpn tunnel.
> On ubuntu 21.10 (I tested ubuntu, ubuntu mate and xubuntu)I can affirm the 
> dns in this case is not going trough the vpn.it is leaking.I have used ubuntu 
> for years this is first time this problem occurs (21.10).(and it s not just a 
> question of packages because on my arch linux installs I never had such 
> problem, so it must be a config problem.
>
> (when using packages stubby or dnscrypt-proxy (to encrypt dns queries)
> and dns 127.0.0.1 is set in network-manager the dns does goes trough
> the vpn (but stubby service needs to be sometimes reloded, it is less
> reliable that it used to be with previous versions of ubuntu)
>
> (I cannot speculate where the bug is from (network-manager, systemd
> resolved etc)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1948533/+subscriptions

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

Title:
  any dns defined in network-manager doesnt go in openvpn tunnel (leaks
  on gnome/mate/xubuntu only in 21.10)

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  in all linux including ubuntu up to version 21.04, when dns is set to not 
automatic in network manager and one dns is set manually (exemple 1.1.1.1) when 
openvpn is used the dns is going through the vpn tunnel.
  On ubuntu 21.10 (I tested ubuntu, ubuntu mate and xubuntu)I can affirm the 
dns in this case is not going trough the vpn.it is leaking.I have used ubuntu 
for years this is first time this problem occurs (21.10).(and it s not just a 
question of packages because on my arch linux installs I never had such 
problem, so it must be a config problem.

  (when using packages stubby or dnscrypt-proxy (to encrypt dns queries)
  and dns 127.0.0.1 is set in network-manager the dns does goes trough
  the vpn (but stubby service needs to be sometimes reloded, it is less
  reliable that it used to be with previous versions of ubuntu)

  (I cannot speculate where the bug is from (network-manager, systemd
  resolved etc)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1948533/+subscriptions


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

2021-11-24 Thread Timo Aaltonen

see Debian bugs

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994873
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=994955

we can't keep valgrind enabled, or libdrm.pc would be broken

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

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

-- 
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:
  Incomplete
Status in mesa source package in Focal:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed

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 1949603] Re: iptables-save -c shows incorrect counters with iptables-nft

This bug was fixed in the package iptables - 1.8.7-1ubuntu4

---
iptables (1.8.7-1ubuntu4) jammy; urgency=medium

  [ Andrea Righi ]
  * Fix counters with iptables-nft and add a test case (LP: #1949603)
- d/p/9005-iptables-nft-fix-Z-option.patch
  * Enable iptables selftest in autopkgtest

  [ Dimitri John Ledkov ]
  * Chmod patched test case in autopkgtest as well.
  * Add nftables:native depends in the autopkgtest and switch to
isolation-machine.
  * Upload to jammy.

 -- Andrea Righi   Wed, 03 Nov 2021 15:50:49
+

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

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

Title:
  iptables-save -c shows incorrect counters with iptables-nft

Status in iptables package in Ubuntu:
  Fix Released
Status in iptables source package in Impish:
  Confirmed
Status in iptables source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Starting with Impish I noticed that the kernel selftest xfrm_policy.sh
  is always failing. Initially I thought it was a kernel issue, but
  debugging further I found that the reason is that with Impish we're
  using iptables-nft by default instead of iptables-legacy.

  This test (./tools/testing/selftests/net/xfrm_policy.sh in the kernel
  source directory) is creating a bunch of network namespaces and
  checking the iptables counters for the defined policies, in particular
  this is the interesting part:

  check_ipt_policy_count()
  {
  ns=$1

  ip netns exec $ns iptables-save -c |grep policy | ( read c rest
  ip netns exec $ns iptables -Z
  if [ x"$c" = x'[0:0]' ]; then
  exit 0
  elif [ x"$c" = x ]; then
  echo "ERROR: No counters"
  ret=1
  exit 111
  else
  exit 1
  fi
  )
  }

  If I use iptables-nft the counters are never [0:0] as they should be,
  so the test is failing. With iptables-legacy they are [0:0] and the
  test is passing.

  [Test case]

  tools/testing/selftests/net/xfrm_policy.sh from the Linux kernel
  source code.

  [Fix]

  Apply iptables upstream commit:

  5f1fcace ("iptables-nft: fix -Z option")

  In this way also with iptables-nft the counters are reported
  correctly.

  [Regression potential]

  We may require other upstream commits now that the -Z option is
  working properly with iptables-nft.

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


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

[Touch-packages] [Bug 1951470] Re: webkit javascript segmentation fault

** Description changed:

+ SRU Justification:
+ 
+ [Impact]
+ 
+  * WebKit Javascript engine is causing a segmentation fault on big
+ endian (s390x) systems.
+ 
+  * This happens for example when transferring an html to a pdf file
+ using wkhtmltopdf.
+ 
+  * The fix is relatively simple with changing loadisFromInstruction to 
loadpFromInstruction
+in macro getProperty(slow), which solves this unpleasant situation.
+ 
+  * The JIT ocde is 32bit (even on 64bit systems),
+hence is crucial to make sure the lower part of a 64bit value is taken on 
big endian systems.
+ 
+ [Test Plan]
+ 
+  * Testing is very straight forward by following these steps:
+ 
+  * install the following packages (incl. their dependencies):
+$ sudo apt install libqt5webkit5 wkhtmltopdf
+ 
+  * create an html file like this:
+$ vi index.html
+$ cat index.html
+
+
+  
+  
+
+  
+
+  
+
+ 
+  * create a JavaScript file like this:
+$ vi min.js
+$ cat min.js
+var i = Math.max
+ 
+  * call wkhtmltopdf to process the local files:
+$ wkhtmltopdf --enable-local-file-access index.html test.pdf
+ 
+  * if it's broken one gets this output:
+Loading page (1/2)
+Segmentation fault (core dumped) ] 50%
+and no pdf file was generated:
+$ ls *.pdf
+ls: cannot access '*.pdf': No such file or directory
+ 
+  * in case it's fixed one gets this output:
+Loading page (1/2)
+Printing pages (2/2)   
+Done   
+and a pdf file was generated and in placed in the current directory (with 
more than 0 bytes size):
+$ ls -l ./*.pdf
+-rw-rw-r-- 1 ubuntu ubuntu 1339 Nov 24 11:48 ./test.pdf
+ 
+ [Where problems could occur]
+ 
+  * While this issue only affects big endian systems (like s390x),
+a bad fix may have an impact on little endian systems, too
+for example in case the wrong function got used in the macro.
+ 
+  * But loadpFromInstruction is known to work for LE and BE systems;
+ 
+  * and on top cross-architecture builds were done:
+https://launchpad.net/~fheimes/+archive/ubuntu/lp1951470
+ 
+  * and tested on s390x (if the fix works) and on non-s390x (regression
+ testing).
+ 
+  * The changes are otherwise very limited, just:
+macro getProperty(slow)
+-loadisFromInstruction(6, t1)
++loadpFromInstruction(6, t1)
+hence I think there is not much more to say.
+ 
+ [Other Info]
+  
+  * The maintainer of the Debian packages (Dmitry Shachnev)
+is going to add this to the Debian package, too.
+ 
+  * This issue affects Ubuntu jammy, impish, hirsute and focal - SRUs are
+ ongoing.
+ 
+  * The issue does not occur with the very latest upstream version anymore,
+and was fixed in a similar way as part of a commit
+that fixes numerous other CLoop issues on top:
+"Fix all CLoop JSC test failures (including some LLInt bugs due to recent 
bytecode format change)."
+commit 3fdde71c7d95d758a61fcbc4c58168616794c102
+ 
+ __
+ 
  == Comment: #0 - Andreas Krebbel  - 2021-11-15 
09:29:44 ==
  ---Problem Description---
  Segmentation fault from WebKit Javascript engine
-  
- Contact Information = andreas.kreb...@de.ibm.com 
-  
+ 
+ Contact Information = andreas.kreb...@de.ibm.com
+ 
  ---uname output---
  Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 
s390x s390x s390x GNU/Linux
-  
- Machine Type = IBM Z 
-  
+ 
+ Machine Type = IBM Z
+ 
  ---Debugger---
  A debugger is not configured
-  
+ 
  ---Steps to Reproduce---
-  index.html:
+  index.html:
  
  
-   
-   
+   
+   
  
-   
- 
-   
+   
+ 
+   
  
  
  min.js:
  var i = Math.max
  
  wkhtmltopdf index.html test.pdf
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Loading page (1/2)
  Segmentation fault (core dumped) ] 17%
-  
- Userspace tool common name: wkhtmltopdf 
-  
- The userspace tool has the following bit modes: 64 
+ 
+ Userspace tool common name: wkhtmltopdf
+ 
+ The userspace tool has the following bit modes: 64
  
  Userspace rpm: libqt5webkit5
  
- Userspace tool obtained from project website:  na 
-  
+ Userspace tool obtained from project website:  na
+ 
  *Additional Instructions for andreas.kreb...@de.ibm.com:
  -Attach ltrace and strace of userspace application.
  
  == Comment: #1 - Andreas Krebbel  - 2021-11-15 
09:44:04 ==
  In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes 
the property offset as pointer size (hence 64 bit) value:
  
  2141: instructions[i + 6].u.pointer =
  reinterpret_cast(op.operand);
  
  while the same slot is accessed later by the jitted code as 32 bit
  integer:
  
  macro getProperty(slow)
- loadisFromInstruction(6, t1)
+ loadisFromInstruction(6, t1)
  
  This fails on big endian targets since the integer access takes the
  higher part o

[Touch-packages] [Bug 1896772] Re: systemd-resolved configures no Current Scopes on start

2021-11-24 Thread janl

I still have this

  Failed to save link data /run/systemd/resolve/netif/2: Permission
denied

problem on 21.10 when getting a dhcp lease. The netif directory:

  drwxr-xr-x 2 root root 40 nov.  24  2021 /run/systemd/resolve/netif

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

Title:
  systemd-resolved configures no Current Scopes on start

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Running groovy on the desktop, with the systemd packages that migrated
  today(/overnight EDT).

  # Steps to reproduce:

  1) `systemctl restart systemd-resolved.service`

  (This is a minimal reproducer, but I first saw this after an apt
  upgrade of systemd.)

  # Expected behaviour:

  DNS continues to work, status looks like this:

  Link 2 (enp5s0)
Current Scopes: DNS
  DefaultRoute setting: yes
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no
Current DNS Server: 192.168.1.1
   DNS Servers: 192.168.1.1
DNS Domain: ~.
lan

  # Actual behaviour:

  DNS is unconfigured:

  Link 2 (enp5s0)
Current Scopes: none
  DefaultRoute setting: no
 LLMNR setting: yes
  MulticastDNS setting: no
DNSOverTLS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  # Workaround

  Disconnecting and reconnecting my network connection restored DNS
  functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: systemd 246.5-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: i3
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Wed Sep 23 09:05:42 2020
  InstallationDate: Installed on 2019-05-07 (504 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash 
resume=UUID=73909634-a75d-42c9-8f66-a69138690756 pcie_aspm=off vt.handoff=7
  RebootRequiredPkgs: gnome-shell
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
   --
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (92 days ago)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

[Touch-packages] [Bug 1951470] Re: webkit javascript segmentation fault

** Also affects: qtwebkit-opensource-src (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: qtwebkit-opensource-src (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: qtwebkit-opensource-src (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: qtwebkit-opensource-src (Ubuntu Jammy)
   Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
   Status: Confirmed

** Changed in: qtwebkit-opensource-src (Ubuntu Jammy)
   Status: Confirmed => In Progress

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

** Tags added: jammy

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

Title:
  webkit javascript segmentation fault

Status in Ubuntu on IBM z Systems:
  In Progress
Status in qtwebkit-opensource-src package in Ubuntu:
  In Progress
Status in qtwebkit-opensource-src source package in Focal:
  New
Status in qtwebkit-opensource-src source package in Hirsute:
  New
Status in qtwebkit-opensource-src source package in Impish:
  New
Status in qtwebkit-opensource-src source package in Jammy:
  In Progress

Bug description:
  == Comment: #0 - Andreas Krebbel  - 2021-11-15 
09:29:44 ==
  ---Problem Description---
  Segmentation fault from WebKit Javascript engine
   
  Contact Information = andreas.kreb...@de.ibm.com 
   
  ---uname output---
  Linux 193438490afd 5.8.15-301.fc33.s390x #1 SMP Thu Oct 15 15:55:57 UTC 2020 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM Z 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   index.html:
  
  




  

  

  min.js:
  var i = Math.max

  wkhtmltopdf index.html test.pdf
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-root'
  Loading page (1/2)
  Segmentation fault (core dumped) ] 17%
   
  Userspace tool common name: wkhtmltopdf 
   
  The userspace tool has the following bit modes: 64 

  Userspace rpm: libqt5webkit5

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for andreas.kreb...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #1 - Andreas Krebbel  - 2021-11-15 
09:44:04 ==
  In CodeBlock.cpp the code preparing the operands of op_get_from_scope writes 
the property offset as pointer size (hence 64 bit) value:

  2141: instructions[i + 6].u.pointer =
  reinterpret_cast(op.operand);

  while the same slot is accessed later by the jitted code as 32 bit
  integer:

  macro getProperty(slow)
  loadisFromInstruction(6, t1)

  This fails on big endian targets since the integer access takes the
  higher part of the 64 bit value.

  Changing:

  macro getProperty(slow)
  loadisFromInstruction(6, t1)

  to

  macro getProperty(slow)
  loadpFromInstruction(6, t1)

  in llint/LowLevelInterpreter64.asm fixes the problem for me.

  
  I could not reproduce the problem on Ubuntu 20.10. In upstream webkit the 
problem got fixed as a side effect of a larger change but in the end quite 
similar to the change I'm proposing. The value resides somewhere else now but 
it is accessed as 64 bit value in getProperty:

  macro getProperty()
  loadp OpGetFromScope::Metadata::m_operand[t5], t1


  If you have the jsc binary from the webkit package available the
  problem can be reproduced with just 'jsc -e "i=Math.min"'

  == Comment: #2 - Andreas Krebbel  -
  2021-11-15 09:49:55 ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1951470/+subscriptions


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

** Changed in: openssl (Ubuntu Hirsute)
   Status: New => In Progress

-- 
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:
  New
Status in openssl source package in Bionic:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Hirsute:
  In Progress
Status in openssl source package in Impish:
  In Progress
Status in openssl source package in Jammy:
  New

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 is run during the build as part of the upstream regression
  test suite

  [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 1952083] [NEW] Add support for Beige Goby

2021-11-24 Thread Timo Aaltonen

Public bug reported:

Impact]

New hardware support for AMD's Beige Goby needs a commit backported to
mesa. This is only needed on focal, skipping hirsute (no kernel support
there). Fixed in impish and up.

[Test plan]

Install updates, boot a BG machine and check that the desktop has full
hardware acceleration.

[Where problems could occur]

Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
could go wrong.

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: mesa (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

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

** Description changed:

  Impact]
  
  New hardware support for AMD's Beige Goby needs a commit backported to
  mesa. This is only needed on focal, skipping hirsute (no kernel support
- there).
+ there). Fixed in impish and up.
  
  [Test plan]
  
  Install updates, boot a BG machine and check that the desktop has full
  hardware acceleration.
  
  [Where problems could occur]
  
  Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
  could go wrong.

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

Title:
  Add support for Beige Goby

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New

Bug description:
  Impact]

  New hardware support for AMD's Beige Goby needs a commit backported to
  mesa. This is only needed on focal, skipping hirsute (no kernel
  support there). Fixed in impish and up.

  [Test plan]

  Install updates, boot a BG machine and check that the desktop has full
  hardware acceleration.

  [Where problems could occur]

  Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what
  could go wrong.

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


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

** Description changed:

  [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 is run during the build as part of the upstream regression test
+ suite
+ 
  [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

** Changed in: openssl (Ubuntu Impish)
   Status: New => In Progress

-- 
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:
  New
Status in openssl source package in Bionic:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Hirsute:
  New
Status in openssl source package in Impish:
  In Progress
Status in openssl source package in Jammy:
  New

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 is run during the build as part of the upstream regression
  test suite

  [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 1949553] Autopkgtest regression report (xorg-server/2:1.20.13-1ubuntu1~20.04.1)

2021-11-24 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted xorg-server 
(2:1.20.13-1ubuntu1~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

aptdaemon/1.1.1+bzr982-0ubuntu32.3 (arm64)


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

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

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

Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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:
  Incomplete
Status in mesa source package in Focal:
  In Progress
Status in xorg-server source package in Focal:
  Fix Committed

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 1639452] Re: systemd ExecStartPre test config

2021-11-24 Thread Miriam España Acebal

** Changed in: dnsmasq (Ubuntu Focal)
 Assignee: (unassigned) => Miriam España Acebal (mirespace)

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

Title:
  systemd ExecStartPre test config

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Bionic:
  Triaged
Status in dnsmasq source package in Focal:
  Triaged

Bug description:
  The standard configuration file of dnsmasq is complete commented out.
  The real configuration is saved in /etc/dnsmasq.d, so the test of
  systemd is a fake.

  In the Service Section of /lib/systemd/system/dnsmasq.service the
  ExecStartPre directive should be set to "/usr/sbin/dnsmasq --conf-
  dir=/etc/dnsmasq.d --test"

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


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

[Touch-packages] [Bug 1944788] Re: URI defined for connectivity check is relative to search domain

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

Thank you for your bug report, that was discussed in bug #1880258 and is
fixed in the current Ubuntu serie

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Low

** This bug has been marked a duplicate of bug 1880258
   Add trailing dot to make connectivity-check.ubuntu.com. absolute and reduce 
NXDOMAIN warning noise

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

Title:
  URI defined for connectivity check is relative to search domain

Status in network-manager package in Ubuntu:
  New

Bug description:
  The connectivity check URI as defined in
  /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf is not an
  absolute FQDN (doesn't end in a dot). As such, resolving connectivity-
  check.ubuntu.com generates queries for connectivity-
  check.ubuntu.com.localdomain (assuming a common default search domain
  of "localdomain") in addition to the expected connectivity-
  check.ubuntu.com . Or, if your ISP provided search domain is
  myisp.net, then connectivity-check.ubuntu.com.myisp.net is also
  queried.

  To reduce unintended traffic, may I suggest a trailing dot to ensure
  the host portion of the URI is a FQDN? Ex:

  uri=http://connectivity-check.ubuntu.com./

  # lsb_release -rd
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  # apt-cache policy network-manager-config-connectivity-ubuntu
  network-manager-config-connectivity-ubuntu:
    Installed: 1.22.10-1ubuntu2.2
    Candidate: 1.22.10-1ubuntu2.2
    Version table:
   *** 1.22.10-1ubuntu2.2 500
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu focal-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.22.10-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu focal/main i386 Packages

  # What I expected to happen:
  Sep 23 18:48:45 dnsmasq[415]: query[] connectivity-check.ubuntu.com from 
192.168.0.111
  Sep 23 18:48:45 dnsmasq[415]: query[] connectivity-check.ubuntu.com from 
192.168.0.111
  Sep 23 18:50:55 dnsmasq[415]: query[A] connectivity-check.ubuntu.com from 
192.168.0.111
  (requests resulting in NXDOMAIN or NODATA-IPv6 are made twice)

  # What happened instead:
  Sep 23 17:02:49 dnsmasq[415]: query[] connectivity-check.ubuntu.com from 
192.168.0.111
  Sep 23 17:02:49 dnsmasq[415]: query[] connectivity-check.ubuntu.com from 
192.168.0.111
  Sep 23 17:02:49 dnsmasq[415]: query[] 
connectivity-check.ubuntu.com.localdomain from 192.168.0.111
  Sep 23 17:02:49 dnsmasq[415]: query[] 
connectivity-check.ubuntu.com.localdomain from 192.168.0.111
  Sep 23 17:04:42 dnsmasq[415]: query[A] connectivity-check.ubuntu.com from 
192.168.0.111

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1944788/+subscriptions


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

[Touch-packages] [Bug 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume

It probably doesn't make sense to fix hirsute at this point unless you
need the fix there?

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

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

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

** Changed in: pulseaudio (Ubuntu Focal)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: pulseaudio (Ubuntu Impish)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: pulseaudio (Ubuntu Hirsute)
   Status: In Progress => Won't Fix

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

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 1951667] Re: [SRU] pulseaudio: restore hdmi audio be active output after resume