[Touch-packages] [Bug 47958] Re: ssh-agent clobbers LD_LIBRARY_PATH and other environment variables

[Q1Blue]

** Changed in: openssh (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  ssh-agent clobbers LD_LIBRARY_PATH and other environment variables

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh package in Debian:
  New

Bug description:
  Since /usr/bin/ssh-agent is setgid ssh, it unsets LD_LIBRARY_PATH.
  This made it impossible to set this variable in my dotfiles
  (.gnomerc).

  My solution was to write a wrapper script that prefixes the command with 
/usr/bin/env VAR=val ... for each variable that gets unset:


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


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

[Touch-packages] [Bug 1960964] Re: Gather additional info when creating a bug about a snap

[Launchpad Bug Tracker]

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

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

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

Title:
  Gather additional info when creating a bug about a snap

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  On the ubuntu-devel mailing list[1] it was suggested that apport
  should collect the following additional information when reporting a
  bug about a snap:

- snap changes --abs-time $SNAPNAME 
 
- snap connections $SNAPNAME
 
- snap info --abs-time $SNAPNAME
 
- for PROVIDER in $(grep default-provider 
/snap/$SNAPNAME/current/meta/snap.yaml | uniq | cut -d: -f2); do snap info 
--abs-time $PROVIDER; done  
  
- snap info --abs-time $(grep base: /snap/$SNAPNAME/current/meta/snap.yaml 
| cut -d: -f2)  

  This should be fairly straightforward we just need to decide on names
  for the keys in the report.

  [1] https://lists.ubuntu.com/archives/ubuntu-
  devel/2022-February/041836.html

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


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

[Touch-packages] [Bug 1811531] Re: remote execution vulnerability

[Bug Watch Updater]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

** CVE 

[Touch-packages] [Bug 1811531]

[Swamp-a]

SUSE-FU-2022:0454-1: An update that solves 54 vulnerabilities, contains
6 features and has 247 fixes is now available.

Category: feature (moderate)
Bug References: 
180,1000117,1000194,1000742,1002895,1003091,1005246,1010874,1010966,1011936,1015549,1027610,1027705,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042670,1049186,1049304,1050653,1050665,1055478,1055542,1056951,1057496,1062237,1066873,1068790,1070737,1070738,1070853,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087104,1088573,1090427,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097531,1098535,1099308,1099569,1102868,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112357,1115769,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150190,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1159235,1159538,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1178168,1178341,1178670,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1190781,1193357,428177,431945,589441,613497,637176,657698,658604,673071,715423,743787,747125,750618,751718,754447,754677,761500,784670,787526,799119,809831,811890,825221,828513,831629,834601,835687,839107,84331,855666,858239,867887,871152,885662,885882,889363,892480,898917,907584,912460,913229,915479,917607,917759,917815,922448,929736,930189,931978,935856,937912,939456,940608,942385,942751,944204,945455,946648,947357,947679,948198,954486,954690,961334,962291,963974,964204,964472,964474,965830,967128,968270,968601,975875,981848,988086,992988,992989,992992,993130,993825,993968,994910,996255,997614
CVE References: 
CVE-2011-3389,CVE-2011-4944,CVE-2012-0845,CVE-2012-1150,CVE-2013-1437,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2014-0012,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-4650,CVE-2014-7202,CVE-2014-7203,CVE-2014-9721,CVE-2015-2296,CVE-2016-10745,CVE-2016-1238,CVE-2016-9015,CVE-2017-18342,CVE-2017-6512,CVE-2018-18074,CVE-2018-20060,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426
JIRA References: ECO-3105,SLE-12986,SLE-17532,SLE-17957,SLE-7686,SLE-9135
Sources used:

NOTE: This line indicates an update has been released for the listed
product(s). At times this might be only a partial fix. If you have
questions please reach out to maintenance coordination.

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

Title:
  remote execution vulnerability

Status in zeromq3 package in Ubuntu:
  Fix Released
Status in zeromq3 package in Debian:
  Fix Released
Status in zeromq package in Suse:
  Fix Released

Bug description:
  Dear Maintainer,

  A remote execution vulnerability has been reported in zeromq. Full
  details can be found on the upstream issue tracker [1].

  The issue is fixed in upstream version v4.3.1, just released, or with
  the attached patch which is targeted for v4.2.5 (bionic and cosmic).

  The latest version will hopefully arrive in disco via debian unstable
  soon, but I would recommend patching older releases.

  As mentioned in the upstream tracker and the changelog, the issue can
  be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as
  I am aware no CVEs have been assigned nor have been requested as of
  now.

  [1] https://github.com/zeromq/libzmq/issues/3351

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


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

[Touch-packages] [Bug 1811531]

[Swamp-a]

SUSE-FU-2022:0447-1: An update that solves 54 vulnerabilities, contains
6 features and has 247 fixes is now available.

Category: feature (moderate)
Bug References: 
180,1000117,1000194,1000742,1002895,1003091,1005246,1010874,1010966,1011936,1015549,1027610,1027705,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042670,1049186,1049304,1050653,1050665,1055478,1055542,1056951,1057496,1062237,1066873,1068790,1070737,1070738,1070853,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087104,1088573,1090427,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097531,1098535,1099308,1099569,1102868,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112357,1115769,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150190,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1159235,1159538,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1178168,1178341,1178670,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1190781,1193357,428177,431945,589441,613497,637176,657698,658604,673071,715423,743787,747125,750618,751718,754447,754677,761500,784670,787526,799119,809831,811890,825221,828513,831629,834601,835687,839107,84331,855666,858239,867887,871152,885662,885882,889363,892480,898917,907584,912460,913229,915479,917607,917759,917815,922448,929736,930189,931978,935856,937912,939456,940608,942385,942751,944204,945455,946648,947357,947679,948198,954486,954690,961334,962291,963974,964204,964472,964474,965830,967128,968270,968601,975875,981848,988086,992988,992989,992992,993130,993825,993968,994910,996255,997614
CVE References: 
CVE-2011-3389,CVE-2011-4944,CVE-2012-0845,CVE-2012-1150,CVE-2013-1437,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2014-0012,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-4650,CVE-2014-7202,CVE-2014-7203,CVE-2014-9721,CVE-2015-2296,CVE-2016-10745,CVE-2016-1238,CVE-2016-9015,CVE-2017-18342,CVE-2017-6512,CVE-2018-18074,CVE-2018-20060,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426
JIRA References: ECO-3105,SLE-12986,SLE-17532,SLE-17957,SLE-7686,SLE-9135
Sources used:

NOTE: This line indicates an update has been released for the listed
product(s). At times this might be only a partial fix. If you have
questions please reach out to maintenance coordination.

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

Title:
  remote execution vulnerability

Status in zeromq3 package in Ubuntu:
  Fix Released
Status in zeromq3 package in Debian:
  Fix Released
Status in zeromq package in Suse:
  Fix Released

Bug description:
  Dear Maintainer,

  A remote execution vulnerability has been reported in zeromq. Full
  details can be found on the upstream issue tracker [1].

  The issue is fixed in upstream version v4.3.1, just released, or with
  the attached patch which is targeted for v4.2.5 (bionic and cosmic).

  The latest version will hopefully arrive in disco via debian unstable
  soon, but I would recommend patching older releases.

  As mentioned in the upstream tracker and the changelog, the issue can
  be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as
  I am aware no CVEs have been assigned nor have been requested as of
  now.

  [1] https://github.com/zeromq/libzmq/issues/3351

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


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

[Touch-packages] [Bug 1811531]

[Swamp-a]

SUSE-FU-2022:0452-1: An update that solves 54 vulnerabilities, contains
6 features and has 247 fixes is now available.

Category: feature (moderate)
Bug References: 
180,1000117,1000194,1000742,1002895,1003091,1005246,1010874,1010966,1011936,1015549,1027610,1027705,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042670,1049186,1049304,1050653,1050665,1055478,1055542,1056951,1057496,1062237,1066873,1068790,1070737,1070738,1070853,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087104,1088573,1090427,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097531,1098535,1099308,1099569,1102868,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112357,1115769,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150190,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1159235,1159538,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1178168,1178341,1178670,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1190781,1193357,428177,431945,589441,613497,637176,657698,658604,673071,715423,743787,747125,750618,751718,754447,754677,761500,784670,787526,799119,809831,811890,825221,828513,831629,834601,835687,839107,84331,855666,858239,867887,871152,885662,885882,889363,892480,898917,907584,912460,913229,915479,917607,917759,917815,922448,929736,930189,931978,935856,937912,939456,940608,942385,942751,944204,945455,946648,947357,947679,948198,954486,954690,961334,962291,963974,964204,964472,964474,965830,967128,968270,968601,975875,981848,988086,992988,992989,992992,993130,993825,993968,994910,996255,997614
CVE References: 
CVE-2011-3389,CVE-2011-4944,CVE-2012-0845,CVE-2012-1150,CVE-2013-1437,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2014-0012,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-4650,CVE-2014-7202,CVE-2014-7203,CVE-2014-9721,CVE-2015-2296,CVE-2016-10745,CVE-2016-1238,CVE-2016-9015,CVE-2017-18342,CVE-2017-6512,CVE-2018-18074,CVE-2018-20060,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426
JIRA References: ECO-3105,SLE-12986,SLE-17532,SLE-17957,SLE-7686,SLE-9135
Sources used:

NOTE: This line indicates an update has been released for the listed
product(s). At times this might be only a partial fix. If you have
questions please reach out to maintenance coordination.

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

Title:
  remote execution vulnerability

Status in zeromq3 package in Ubuntu:
  Fix Released
Status in zeromq3 package in Debian:
  Fix Released
Status in zeromq package in Suse:
  Fix Released

Bug description:
  Dear Maintainer,

  A remote execution vulnerability has been reported in zeromq. Full
  details can be found on the upstream issue tracker [1].

  The issue is fixed in upstream version v4.3.1, just released, or with
  the attached patch which is targeted for v4.2.5 (bionic and cosmic).

  The latest version will hopefully arrive in disco via debian unstable
  soon, but I would recommend patching older releases.

  As mentioned in the upstream tracker and the changelog, the issue can
  be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as
  I am aware no CVEs have been assigned nor have been requested as of
  now.

  [1] https://github.com/zeromq/libzmq/issues/3351

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


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

[Touch-packages] [Bug 1811531]

[Swamp-a]

SUSE-FU-2022:0444-1: An update that solves 51 vulnerabilities, contains
21 features and has 249 fixes is now available.

Category: feature (moderate)
Bug References: 
180,1000117,1000194,1000742,1002895,1003091,1005246,1010874,1010966,1011936,1015549,1027610,1027705,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042670,1049186,1049304,1050653,1050665,1055478,1055542,1056951,1057496,1062237,1066873,1068790,1070737,1070738,1070853,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087104,1088573,1090427,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097531,1098535,1099308,1099569,1102868,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112357,1115769,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150190,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1159235,1159538,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1177559,1178168,1178341,1178670,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1190781,1193357,428177,431945,637176,657698,658604,673071,715423,743787,747125,750618,751718,754447,754677,761500,784670,787526,799119,809831,811890,825221,828513,831629,834601,835687,839107,84331,855666,858239,867887,871152,885662,885882,889363,892480,898917,907584,912460,913229,915479,917607,917759,917815,922448,929736,930189,931978,935856,937912,939456,940608,942385,942751,944204,945455,946648,947357,947679,948198,954486,954690,961334,962291,963974,964204,964472,964474,965830,967128,968270,968601,975875,981848,988086,992988,992989,992992,993130,993825,993968,994910,996255,997614
CVE References: 
CVE-2011-3389,CVE-2011-4944,CVE-2012-0845,CVE-2012-1150,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2014-0012,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-4650,CVE-2014-7202,CVE-2014-7203,CVE-2014-9721,CVE-2015-2296,CVE-2016-10745,CVE-2016-9015,CVE-2017-18342,CVE-2018-18074,CVE-2018-20060,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426
JIRA References: 
ECO-3105,SLE-11435,SLE-12684,SLE-12986,SLE-13688,SLE-14253,SLE-15159,SLE-15860,SLE-15861,SLE-16754,SLE-17532,SLE-17957,SLE-18260,SLE-18354,SLE-18446,SLE-19264,SLE-3887,SLE-4480,SLE-4577,SLE-7686,SLE-9135
Sources used:
SUSE Manager Tools 15-BETA (src):venv-salt-minion-3002.2-159000.3.3.2

NOTE: This line indicates an update has been released for the listed
product(s). At times this might be only a partial fix. If you have
questions please reach out to maintenance coordination.

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

Title:
  remote execution vulnerability

Status in zeromq3 package in Ubuntu:
  Fix Released
Status in zeromq3 package in Debian:
  Fix Released
Status in zeromq package in Suse:
  Fix Released

Bug description:
  Dear Maintainer,

  A remote execution vulnerability has been reported in zeromq. Full
  details can be found on the upstream issue tracker [1].

  The issue is fixed in upstream version v4.3.1, just released, or with
  the attached patch which is targeted for v4.2.5 (bionic and cosmic).

  The latest version will hopefully arrive in disco via debian unstable
  soon, but I would recommend patching older releases.

  As mentioned in the upstream tracker and the changelog, the issue can
  be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as
  I am aware no CVEs have been assigned nor have been requested as of
  now.

  [1] https://github.com/zeromq/libzmq/issues/3351

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


-- 
Mailing list: https://launchpad.net/~to

[Touch-packages] [Bug 1811531]

[Swamp-a]

SUSE-FU-2022:0450-1: An update that solves 54 vulnerabilities, contains
6 features and has 247 fixes is now available.

Category: feature (moderate)
Bug References: 
180,1000117,1000194,1000742,1002895,1003091,1005246,1010874,1010966,1011936,1015549,1027610,1027705,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042670,1049186,1049304,1050653,1050665,1055478,1055542,1056951,1057496,1062237,1066873,1068790,1070737,1070738,1070853,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087104,1088573,1090427,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097531,1098535,1099308,1099569,1102868,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112357,1115769,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150190,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1159235,1159538,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1178168,1178341,1178670,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1190781,1193357,428177,431945,589441,613497,637176,657698,658604,673071,715423,743787,747125,750618,751718,754447,754677,761500,784670,787526,799119,809831,811890,825221,828513,831629,834601,835687,839107,84331,855666,858239,867887,871152,885662,885882,889363,892480,898917,907584,912460,913229,915479,917607,917759,917815,922448,929736,930189,931978,935856,937912,939456,940608,942385,942751,944204,945455,946648,947357,947679,948198,954486,954690,961334,962291,963974,964204,964472,964474,965830,967128,968270,968601,975875,981848,988086,992988,992989,992992,993130,993825,993968,994910,996255,997614
CVE References: 
CVE-2011-3389,CVE-2011-4944,CVE-2012-0845,CVE-2012-1150,CVE-2013-1437,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2014-0012,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-4650,CVE-2014-7202,CVE-2014-7203,CVE-2014-9721,CVE-2015-2296,CVE-2016-10745,CVE-2016-1238,CVE-2016-9015,CVE-2017-18342,CVE-2017-6512,CVE-2018-18074,CVE-2018-20060,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426
JIRA References: ECO-3105,SLE-12986,SLE-17532,SLE-17957,SLE-7686,SLE-9135
Sources used:

NOTE: This line indicates an update has been released for the listed
product(s). At times this might be only a partial fix. If you have
questions please reach out to maintenance coordination.

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

Title:
  remote execution vulnerability

Status in zeromq3 package in Ubuntu:
  Fix Released
Status in zeromq3 package in Debian:
  Fix Released
Status in zeromq package in Suse:
  Fix Released

Bug description:
  Dear Maintainer,

  A remote execution vulnerability has been reported in zeromq. Full
  details can be found on the upstream issue tracker [1].

  The issue is fixed in upstream version v4.3.1, just released, or with
  the attached patch which is targeted for v4.2.5 (bionic and cosmic).

  The latest version will hopefully arrive in disco via debian unstable
  soon, but I would recommend patching older releases.

  As mentioned in the upstream tracker and the changelog, the issue can
  be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as
  I am aware no CVEs have been assigned nor have been requested as of
  now.

  [1] https://github.com/zeromq/libzmq/issues/3351

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


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

[Touch-packages] [Bug 1811531]

[Swamp-a]

SUSE-FU-2022:0445-1: An update that solves 183 vulnerabilities, contains
21 features and has 299 fixes is now available.

Category: feature (moderate)
Bug References: 
180,1000117,1000194,1000677,1000742,1001148,1001912,1002585,1002895,1003091,1005246,1009528,1010874,1010966,1011936,1015549,1019637,1021641,1022085,1022086,1022271,1027079,1027610,1027688,1027705,1027908,1028281,1028723,1029523,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042392,1042670,1044095,1044107,1044175,1049186,1049304,1050653,1050665,1055478,1055542,1055825,1056058,1056951,1057496,1062237,1065363,1066242,1066873,1068790,1070737,1070738,1070853,1071905,1071906,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087102,1087104,1088573,1089039,1090427,1090765,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097158,1097531,1097624,1098535,1098592,1099308,1099569,1100078,1101246,1101470,1102868,1104789,1106197,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112209,1112357,1113534,1113652,1113742,1113975,1115769,1117951,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127080,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1131291,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150003,1150190,1150250,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1158809,1159235,1159538,1160163,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1177559,1178168,1178341,1178670,1179491,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182331,1182333,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1189521,1190781,1193357,356549,381844,394317,408865,428177,430141,431945,437293,442740,459468,489641,504687,509031,526319,590833,610223,610642,629905,637176,651003,657698,658604,670526,673071,693027,715423,720601,743787,747125,748738,749210,749213,749735,750618,751718,751946,751977,754447,754677,761500,774710,784670,784994,787526,793420,799119,802184,803004,809831,811890,822642,825221,828513,831629,832833,834601,835687,839107,84331,849377,855666,855676,856687,857203,857850,858239,867887,869945,871152,872299,873351,876282,876710,876712,876748,880891,885662,885882,889013,889363,892477,892480,895129,898917,901223,901277,901902,902364,906878,907584,908362,908372,912014,912015,912018,912292,912293,912294,912296,912460,913229,915479,917607,917759,917815,919648,920236,922448,922488,922496,922499,922500,926597,929678,929736,930189,931698,931978,933898,933911,934487,934489,934491,934493,935856,937085,937212,937492,937634,937912,939456,940608,942385,942751,943421,944204,945455,946648,947104,947357,947679,948198,952871,954256,954486,954690,957812,957813,957815,958501,961334,962291,963415,963974,964204,964472,964474,965830,967128,968046,968047,968048,968050,968265,968270,968374,968601,975875,976942,977584,977614,977615,977616,977663,978224,981848,982268,982575,983249,984323,985054,988086,990207,990392,990419,990428,991193,991877,992120,992988,992989,992992,993130,993819,993825,993968,994749,994844,994910,995075,995324,995359,995377,995959,996255,997043,997614,998190,999665,999666,999668
CVE References: 
CVE-2006-2937,CVE-2006-2940,CVE-2006-3738,CVE-2006-4339,CVE-2006-4343,CVE-2006-7250,CVE-2007-3108,CVE-2007-4995,CVE-2007-5135,CVE-2008-0891,CVE-2008-1672,CVE-2008-5077,CVE-2009-0590,CVE-2009-0591,CVE-2009-0789,CVE-2009-1377,CVE-2009-1378,CVE-2009-1379,CVE-2009-1386,CVE-2009-1387,CVE-2010-0740,CVE-2010-0742,CVE-2010-1633,CVE-2010-2939,CVE-2010-3864,CVE-2010-5298,CVE-2011-0014,CVE-2011-3207,CVE-2011-3210,CVE-2011-3389,CVE-2011-4108,CVE-2011-4576,CVE-2011-4577,CVE-2011-4619,CVE-2011-4944,CVE-2012-0027,CVE-2012-0050,CVE-2012-0845,CVE-2012-0884,CVE-2012-1150,CVE-2012-1165,CVE-2012-2110,CVE-2012-2686,CVE-2012-4929,CVE-2013-0166,CVE-2013-0169,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2013-4353,CVE-2013-6449,CVE-2013-6450,CVE-2014-0012,CVE-2014-0076,CVE-2014-0160,CVE-2014-0195,CVE-2014-0198,CVE-2014-0221,CVE-2014-0224,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-3470,CVE-2014-3505,CVE-2014-3506,CVE-2014-3507,CVE-2014-3508,CVE-2014-3509,CVE-2014-3510,CVE-2014-3511,CVE-2014-3512,CVE-2014-3513,CVE-2014-3566,CVE-2014-3567,CVE-2014-3568,CVE-2014-3570,CVE-2014-3571,CVE-2014-3572,CVE-2014-4650,CVE-2014-5139,CVE-2014-7202,CVE-2014-7203,CVE-2014-8275,CVE-2014

[Touch-packages] [Bug 1811531]

[Swamp-a]

SUSE-FU-2022:0456-1: An update that solves 54 vulnerabilities, contains
6 features and has 247 fixes is now available.

Category: feature (moderate)
Bug References: 
180,1000117,1000194,1000742,1002895,1003091,1005246,1010874,1010966,1011936,1015549,1027610,1027705,1029902,1030038,1032118,1032119,1035604,1039469,1040164,1040256,1041090,1042670,1049186,1049304,1050653,1050665,1055478,1055542,1056951,1057496,1062237,1066873,1068790,1070737,1070738,1070853,1071941,1073310,1073845,1073879,1074247,1076519,1077096,1077230,1078329,1079761,1080301,1081005,1081750,1081751,1082155,1082163,1082318,1083826,1084117,1084157,1085276,1085529,1085661,1087104,1088573,1090427,1090953,1093518,1093917,1094788,1094814,1094883,1095267,1096738,1096937,1097531,1098535,1099308,1099569,1102868,1108508,1109882,1109998,1110435,1110869,1110871,493,622,657,1112357,1115769,1118611,1119376,1119416,1119792,1121717,1121852,1122191,1123064,1123185,1123186,1123558,1124885,1125815,1126283,1126318,1127173,1128146,1128323,1128355,1129071,1129566,1130840,1132174,1132323,1132455,1132663,1132900,1135009,1136444,1138666,1138715,1138746,1139915,1140255,1141168,1142899,1143033,1143454,1143893,1144506,1149686,1149792,1150190,1150895,1153830,1155815,1156677,1156694,1156908,1157104,1157354,1159235,1159538,1161557,1161770,1162224,1162367,1162743,1163978,1164310,1165439,1165578,1165730,1165823,1165960,1166139,1166758,1167008,1167501,1167732,1167746,1168480,1168973,1169489,1170175,1170863,1171368,1171561,1172226,1172908,1172928,1173226,1173356,1174009,1174091,1174514,1175729,1176116,1176129,1176134,1176232,1176256,1176257,1176258,1176259,1176262,1176389,1176785,1176977,1177120,1177127,1178168,1178341,1178670,1179562,1179630,1179805,1180125,1180781,1181126,1181324,1181944,1182066,1182211,1182244,1182264,1182379,1182963,1183059,1183374,1183858,1184505,1185588,1185706,1185748,1186738,1187045,1190781,1193357,428177,431945,589441,613497,637176,657698,658604,673071,715423,743787,747125,750618,751718,754447,754677,761500,784670,787526,799119,809831,811890,825221,828513,831629,834601,835687,839107,84331,855666,858239,867887,871152,885662,885882,889363,892480,898917,907584,912460,913229,915479,917607,917759,917815,922448,929736,930189,931978,935856,937912,939456,940608,942385,942751,944204,945455,946648,947357,947679,948198,954486,954690,961334,962291,963974,964204,964472,964474,965830,967128,968270,968601,975875,981848,988086,992988,992989,992992,993130,993825,993968,994910,996255,997614
CVE References: 
CVE-2011-3389,CVE-2011-4944,CVE-2012-0845,CVE-2012-1150,CVE-2013-1437,CVE-2013-1752,CVE-2013-4238,CVE-2013-4314,CVE-2014-0012,CVE-2014-1829,CVE-2014-1830,CVE-2014-2667,CVE-2014-4650,CVE-2014-7202,CVE-2014-7203,CVE-2014-9721,CVE-2015-2296,CVE-2016-10745,CVE-2016-1238,CVE-2016-9015,CVE-2017-18342,CVE-2017-6512,CVE-2018-18074,CVE-2018-20060,CVE-2018-7750,CVE-2019-10906,CVE-2019-11236,CVE-2019-11324,CVE-2019-13132,CVE-2019-20907,CVE-2019-20916,CVE-2019-5010,CVE-2019-6250,CVE-2019-8341,CVE-2019-9740,CVE-2019-9947,CVE-2020-14343,CVE-2020-15166,CVE-2020-15523,CVE-2020-15801,CVE-2020-1747,CVE-2020-25659,CVE-2020-26137,CVE-2020-27783,CVE-2020-28493,CVE-2020-29651,CVE-2020-36242,CVE-2020-8492,CVE-2021-23336,CVE-2021-28957,CVE-2021-29921,CVE-2021-3177,CVE-2021-33503,CVE-2021-3426
JIRA References: ECO-3105,SLE-12986,SLE-17532,SLE-17957,SLE-7686,SLE-9135
Sources used:

NOTE: This line indicates an update has been released for the listed
product(s). At times this might be only a partial fix. If you have
questions please reach out to maintenance coordination.

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

Title:
  remote execution vulnerability

Status in zeromq3 package in Ubuntu:
  Fix Released
Status in zeromq3 package in Debian:
  Fix Released
Status in zeromq package in Suse:
  Fix Released

Bug description:
  Dear Maintainer,

  A remote execution vulnerability has been reported in zeromq. Full
  details can be found on the upstream issue tracker [1].

  The issue is fixed in upstream version v4.3.1, just released, or with
  the attached patch which is targeted for v4.2.5 (bionic and cosmic).

  The latest version will hopefully arrive in disco via debian unstable
  soon, but I would recommend patching older releases.

  As mentioned in the upstream tracker and the changelog, the issue can
  be mitigated by ASLR and by authentication via CURVE/GSSAPI. As far as
  I am aware no CVEs have been assigned nor have been requested as of
  now.

  [1] https://github.com/zeromq/libzmq/issues/3351

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


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

[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

[jeremyszu]

Hi Robie,

Thanks for sharing the changes with other flavors.
Just want to clarify the comment#14-16 are talking about Jammy which shouldn't 
blocking Focal#5 and Impish#10 SRU.

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Impish:
  In Progress
Status in systemd source package in Jammy:
  Fix Released

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

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  In some old HP platforms (contains Intel-HID and HPQ6001 in same
  machine), the user will aware the airplane mode toggled very quickly
  e.g. turn-on and turn-off immediately (or works good without problem,
  depends on how DM handles multiple rfkill events).

  In this case, you could check:
  1. sudo evtest
  # You probably could see 
  # ...
  # /dev/input/event8:  Intel HID events
  # ...
  # /dev/input/event11: Wireless hotkeys
  # or "HP Wireless hotkeys" depends on your kernel version

  2. try to listen these events when pressing airplane key, you will
  probably see these two events will send the keycode out.

  3. check the components own this event
  $ sudo udevadm info -a /dev/input/event11
  # ...
  # ATTRS{phys}=="hpq6001/input0"

  $ sudo udevadm info -a /dev/input/event8
  # ...
  #DRIVERS=="intel-hid"

  4. check your hwdb is affect.
  $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
  # If you didn't see anything then it means your intel-hid is unmask.

  5. You could report a bug to your DM for dealing with two rfkill events (same 
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as 
workaround (but it will be overwritten in next upgrade) by adding:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
  ```
  to /lib/udev/hwdb.d/60-keyboard.hwdb

  then
  $ systemd-hwdb update
  $ udevadm trigger

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

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


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

[Touch-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

[Daniel van Vugt]

** Also affects: pulseaudio (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session jammy
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log prese

[Touch-packages] [Bug 1961055] Re: Key load error: Failed to open key material file: No such file or directory

[geole0]

Hello

I worked around the problem by removing the words quiet splash from the entry 
menus of the /boot/grub/grub.cfg file so that I could enter the password. But 
the swap partition is not mounted.
Probably because is name is now SDA2 and not SDC2 which was the name during 
installation on a external drive.

sudo blkid | grep sda2
/dev/sda2: UUID="99ce927e-67ae-4e9a-93f1-ac637af7f34f" TYPE="crypto_LUKS" 
PARTUUID="caada0e6-030f-5143-93f8-8534629af79c"
a@a:~$ 


df -h
Sys. de fichiers Taille Utilisé Dispo Uti% 
Monté sur
tmpfs  583M2,1M  581M   1% /run
/dev/mapper/keystore-rpool 437M 28K  404M   1% 
/run/keystore/rpool
rpool/ROOT/ubuntu_trj428   444G3,1G  441G   1% /
tmpfs  2,9G3,3M  2,9G   1% 
/dev/shm
tmpfs  5,0M4,0K  5,0M   1% 
/run/lock
rpool/USERDATA/root_77w87m 441G384K  441G   1% /root
rpool/ROOT/ubuntu_trj428/var/mail  441G256K  441G   1% 
/var/mail
rpool/ROOT/ubuntu_trj428/var/snap  441G1,9M  441G   1% 
/var/snap
rpool/ROOT/ubuntu_trj428/var/www   441G256K  441G   1% 
/var/www
rpool/ROOT/ubuntu_trj428/srv   441G256K  441G   1% /srv
rpool/USERDATA/a_77w87m441G102M  441G   1% 
/home/a
rpool/ROOT/ubuntu_trj428/var/spool 441G384K  441G   1% 
/var/spool
rpool/ROOT/ubuntu_trj428/var/games 441G256K  441G   1% 
/var/games
rpool/ROOT/ubuntu_trj428/usr/local 441G512K  441G   1% 
/usr/local
rpool/ROOT/ubuntu_trj428/var/lib   442G1,3G  441G   1% 
/var/lib
rpool/ROOT/ubuntu_trj428/var/lib/AccountsService   441G256K  441G   1% 
/var/lib/AccountsService
rpool/ROOT/ubuntu_trj428/var/lib/NetworkManager441G256K  441G   1% 
/var/lib/NetworkManager
rpool/ROOT/ubuntu_trj428/var/lib/apt   441G 96M  441G   1% 
/var/lib/apt
rpool/ROOT/ubuntu_trj428/var/lib/dpkg  441G 51M  441G   1% 
/var/lib/dpkg
rpool/ROOT/ubuntu_trj428/var/log   441G3,2M  441G   1% 
/var/log
bpool/BOOT/ubuntu_trj428   1,8G 85M  1,7G   5% /boot
/dev/sdb1   98M 32M   67M  32% 
/boot/efi
tmpfs  583M 11M  573M   2% 
/run/user/1000


note The goog name seems /run/keystore/rpool

journalctl -b -p err
févr. 17 00:33:23 a systemd[1]: Timed out waiting for device /dev/sdc2



.

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

Title:
  Key load error: Failed to open key material file: No such file or
  directory

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello
  This morning I downloaded the UBUNTU JAMMY version which had just been made 
an hour earlier. I installed it asking for encryption.

  When I boot, the password is asked. He is accepted. But root mount is denied.
  ...
  find: /dev/zvol: No such file or directory
  key load error: Failed to open key matéral file No such file or directory

  Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted:
  permission denied

  Picture is here https://zupimages.net/viewer.php?id=22/07/v372.jpg

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


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

[Touch-packages] [Bug 1960601] Re: Ubuntu 20.04 stopped detecting HP LaserJet P2055dn after this morning's update

[ebsf]

@till-kamppeter, I'm not certain what you mean by the "upstream source."
The printer auto-installed when I installed Ubuntu 20.04 shortly after
its release.

After your post, I did:

# apt purge cups cups-client cups-bsd
# apt purge hplip hpijs printer-driver-gutenprint
# apt autoremove
# reboot
# apt install cups cups-client cups-bsd
# apt install printer-driver-gutenprint printer-driver-hpcups 
printer-driver-hpijs printer-driver-postscript-hp
# reboot
# journalctl -b 0

and got >2000 consecutive entries reading:

AVC apparmor="DENIED" operation="create" profile="snap.hplip-printer-
app.hplip-printer-app-server" pid=2211 comm="hplip-printer-a"
family="inet" sock_type="stream" protocol=0 requested_mask="create"
denied_mask="create"

AppArmor is not expressly configured (meaning no one here manually
configured it) on this system.

I'd guess this is what's at work but don't know.  Please advise.

Otherwise, regarding snap, I don't code around others' steaming piles.

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

Title:
  Ubuntu 20.04 stopped detecting HP LaserJet P2055dn after this
  morning's update

Status in cups package in Ubuntu:
  New

Bug description:
  I printed yesterday.

  I updated Ubuntu 20.04.3 this morning.

  The system now does not detect the HP LaserJet P2055dn to which it has
  been connected for years.

  The output of the command "apt-cache policy cups" is:

  cups:
Installed: 2.3.1-9ubuntu1.1
Candidate: 2.3.1-9ubuntu1.1
Version table:
   *** 2.3.1-9ubuntu1.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  What I expected to happen was to print a document.  Then, for the system to 
recognize the printer when I tried to reinstall it.

  What happened instead was that printing failed.  Settings > Printers >
  Additional Printer Settings vomited an error message saying that the
  printer may not be connected.  The print job hung on "Processing" for
  5-10 minutes before I terminated it.  I deleted the printer on the
  system and the system would / could not detect the device.  No obvious
  means exists to install a printer driver for a specified printer,
  which is an astonishing design failure for the platform.

  I have rebooted the system and the printer multiple times throughout
  this process.  I also attempted to update the system but no updates
  are available.  All the wiring and power is as before.

  The system recognizes any number of other USB devices connected to it,
  including scanners, etc., that are freshly powered on.  Power cycling
  the HP printer has no effect on lsusb output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162
  Uname: Linux 5.4.0-99-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog:
   E [11/Feb/2022:00:00:13 -0800] Unable to open listen socket for address 
[v1.::1]:631 - Address family not supported by protocol.
   E [11/Feb/2022:00:10:42 -0800] [Client 27] Returning HTTP Forbidden for 
CUPS-Add-Modify-Printer (ipp://localhost/printers/HP-LaserJet-P2055dn) from 
localhost
   E [11/Feb/2022:00:17:48 -0800] [Client 1329757] Returning IPP 
client-error-document-format-not-supported for Print-Job 
(ipp://localhost:631/printers/CUPS-BRF-Printer) from localhost.
  CurrentDesktop: ubuntu:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Fri Feb 11 00:44:52 2022
  InstallationDate: Installed on 2020-08-20 (539 days ago)
  InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  KernLog:
   
  Lpstat: device for CUPS-BRF-Printer: cups-brf:/
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/CUPS-BRF-Printer.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/CUPS-BRF-Printer.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=94757e46-a814-4c27-b3a5-4ff139bd211d ro ipv6.disable=1 nomodeset 
ipv6.disable=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1602
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79-E WS
  dmi.board.vendor: ASUS

[Touch-packages] [Bug 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10

[Launchpad Bug Tracker]

This bug was fixed in the package dh-python - 5.20220215

---
dh-python (5.20220215) unstable; urgency=medium

  * pybuild plugin: Explicitly unpack wheels using the "deb_system" sysconfig
scheme, allowing python3.10 to change the default sysconfig scheme to
"posix_local". (LP: #1960608)

 -- Stefano Rivera   Tue, 15 Feb 2022 20:26:39
-0400

** Changed in: dh-python (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 dh-python in Ubuntu.
https://bugs.launchpad.net/bugs/1960608

Title:
  python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with
  python3.10

Status in dh-python package in Ubuntu:
  Fix Released
Status in python-pip package in Ubuntu:
  New
Status in python3.10 package in Ubuntu:
  Confirmed

Bug description:
  pip3-root.sh expects world package to be installed in
  /usr/local/lib/python3.*/dist-packages whereas it is actually
  installed into /usr/lib/python3.10/site-packages/.

  It even fails to uninstall the package right after installing it:

  ubuntu@autopkgtest:~$ sudo python3 -m pip install world
  Collecting world
Using cached world-4.1.1-py3-none-any.whl
  Collecting atpublic
Using cached atpublic-3.0.1-py3-none-any.whl (4.8 kB)
  Installing collected packages: atpublic, world
  Successfully installed atpublic-3.0.1 world-4.1.1
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv
  ubuntu@autopkgtest:~$ sudo python3 -m pip uninstall world
  WARNING: Skipping world as it is not installed.
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1960608/+subscriptions


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

[Touch-packages] [Bug 1960083] Re: dirname applet missing from initramfs

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1960083

** Tags added: iso-testing

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

Title:
  dirname applet missing from initramfs

Status in busybox package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  The initramfs is currently being built without the dirname applet.
  This is causing issues with zfs encrypted devices, as cryptsetup is
  attempting to use dirname to determine the location of the system key.
  This results in the following error:

  /init: line 971: dirname: not found

  followed by a prompt that is missing the zpool name. For example

  "Please unlock disk keystore-" rather than "Please unlock disk
  keystore-rpool".

  After entering the password, the user is dropped to an initramfs
  shell.

  It appears that this was caused by a change in cryptsetup to suddenly
  need dirname to function properly.

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


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

[Touch-packages] [Bug 1960863] Re: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances

[Mauricio Faria de Oliveira]

Seth, ack; thanks!

Matthew, I uploaded the changes to Focal; thanks for the SRU!

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

Title:
  armv8 paca: poly1305 users see segfaults when pointer authentication
  in use on AWS Graviton 3 instances

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  In Progress

Bug description:
  [Impact]

  Support for hardware pointer authentication for armv8 systems was
  merged in openssl 1.1.1f, but it contains a bug in the implementation
  for poly1305 message authenticated code routines, which causes the
  calling program to fail pointer authentication, which causes the
  program to crash with a segmentation fault.

  You can easily test it by accessing any website that uses poly1305.
  There is no workaround except use a different MAC.

  [Testcase]

  This bug applies to armv8 systems which support pointer
  authentication. Start an armv8 instance, such as a c7g graviton 3
  instance on AWS, and make sure the paca flag is present in lscpu:

  $ grep paca /proc/cpuinfo
  Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp 
cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm 
dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm svebf16 i8mm bf16 dgh rng

  Next, attempt to connect to any website that uses poly1305 MAC.

  $ curl https://services.gradle.org/distributions/gradle-7.2-bin.zip --output 
gradle-7.2.bin
  % Total % Received % Xferd Average Speed Time Time Time Current
  Dload Upload Total Spent Left Speed
  0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Segmentation fault (core dumped)

  There is a test package available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf327917-test

  Install it, and poly1305 operations will no longer segfault.

  [Where problems could occur]

  The patch changes the order of operations for loading the SP and
  checking the AUTIASP against it, from checking the AUTIASP against
  nothing then loading the correct SP to check with, to the correct
  loading the SP and then checking the AUTIASP against the SP.

  This only changes one code path for armv8 systems, and other
  architectures are not affected. This is also only limited to poly1305
  MAC.

  If a regression were to occur, it would only affect users of poly1035
  MAC on armv8 with pacs support.

  [Other info]

  The fix landed upstream in openssl 1.1.1i with the following commit:

  commit 5795acffd8706e1cb584284ee5bb3a30986d0e75
  Author: Ard Biesheuvel 
  Date:   Tue Oct 27 18:02:40 2020 +0100
  Subject: crypto/poly1305/asm: fix armv8 pointer authentication
  Link: 
https://github.com/openssl/openssl/commit/5795acffd8706e1cb584284ee5bb3a30986d0e75

  This commit is already present in Impish onward. Only Focal needs the
  fix.

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


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

[Touch-packages] [Bug 1960460] Re: Fails to import ZFS rpool during boot

[William Wilson]

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

** This bug has been marked a duplicate of bug 1960083
   dirname applet missing from initramfs

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

Title:
  Fails to import ZFS rpool during boot

Status in systemd package in Ubuntu:
  New

Bug description:
  Fresh install using 20220202 Daily ISO with ZFS + Encryption selected
  from the installer

  The system ends up in busybox after entering the unlock key.

  Here is a part of the logs captured from the screen, the complete log
  can be found as an attachement:

  find: /dev/zvol/: No such file or directory 
  /init: line 971: dirname: not found
  BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu2) multi-call binary.

  Usage: basename FILE [SUFFIX]
  Strip directory path and SUFFIX from FILE 
  Please unlock disk keystore-:_

  Key load error: Failed to open key material file: No such file or
  directory

  Command: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_ui69ph /root// Message: 
filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied 
  filesystem 'rpool/ROOT/ubuntu_ui69ph' can not be mounted: Permission denied 
  mount: mounting rpool/ROOT/ubuntu_u169ph on /root// failed: Permission denied 
Error: 1

  Failed to mount rpool/ROOT/ubuntu ui69ph on /root//.
  Manually mount the filesystem and exit.

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


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

[Touch-packages] [Bug 1960768] Re: fwupd crash on stop

[Brian Murray]

** Tags removed: rls-jj-incoming

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

Title:
  fwupd crash on stop

Status in OEM Priority Project:
  Fix Released
Status in fwupd package in Ubuntu:
  Invalid
Status in libgusb package in Ubuntu:
  Fix Released
Status in libusb package in Ubuntu:
  Invalid

Bug description:
  I can reproduce crash with a similar stack as below as I stop fwupd
  service.

  https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661

  also test fwupd 1.7.5 
(https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175)
  still can reproduce this issue.

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


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

[Touch-packages] [Bug 1961108] [NEW] network options greyed out in paprefs

[Thomas Boehm]

Public bug reported:

I installed Kubuntu 21.10 which comes with pulseaudio
1:15.0+dfsg1-1ubuntu2.2. When I start paprefs all network options are
greyed out. The problem seems to be, that the directory with the modules
is called /usr/lib/pulse-15.0+dfsg1, but paprefs expects the modules in
/usr/lib/pulse-15.0

$ strace paprefs 2>&1 |grep /lib/pulse
access("/usr/lib/pulse-15.0/modules/module-esound-protocol-tcp.so", F_OK) = -1 
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-native-protocol-tcp.so", F_OK) = -1 
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-zeroconf-publish.so", F_OK) = -1 
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-zeroconf-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-raop-discover.so", F_OK) = -1 ENOENT 
(No such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rtp-recv.so", F_OK) = -1 ENOENT (No 
such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rtp-send.so", F_OK) = -1 ENOENT (No 
such file or directory)
access("/usr/lib/pulse-15.0/modules/module-rygel-media-server.so", F_OK) = -1 
ENOENT (No such file or directory)

Creating a symlink /usr/lib/pulse-15.0 solves the problem

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

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

Title:
  network options greyed out in paprefs

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I installed Kubuntu 21.10 which comes with pulseaudio
  1:15.0+dfsg1-1ubuntu2.2. When I start paprefs all network options are
  greyed out. The problem seems to be, that the directory with the
  modules is called /usr/lib/pulse-15.0+dfsg1, but paprefs expects the
  modules in /usr/lib/pulse-15.0

  $ strace paprefs 2>&1 |grep /lib/pulse
  access("/usr/lib/pulse-15.0/modules/module-esound-protocol-tcp.so", F_OK) = 
-1 ENOENT (No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-native-protocol-tcp.so", F_OK) = 
-1 ENOENT (No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-zeroconf-publish.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-zeroconf-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-raop-discover.so", F_OK) = -1 
ENOENT (No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-rtp-recv.so", F_OK) = -1 ENOENT 
(No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-rtp-send.so", F_OK) = -1 ENOENT 
(No such file or directory)
  access("/usr/lib/pulse-15.0/modules/module-rygel-media-server.so", F_OK) = -1 
ENOENT (No such file or directory)

  Creating a symlink /usr/lib/pulse-15.0 solves the problem

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


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

[Touch-packages] [Bug 1960863] Re: armv8 paca: poly1305 users see segfaults when pointer authentication in use on AWS Graviton 3 instances

[Seth Arnold]

None of us are ARM architecture experts but the upstream code nearby
doesn't look like it's changed since this patch was introduced:

https://github.com/openssl/openssl/blame/master/crypto/poly1305/asm/poly1305-armv8.pl
https://github.com/openssl/openssl/blame/OpenSSL_1_1_1-stable/crypto/poly1305/asm/poly1305-armv8.pl
https://github.com/openssl/openssl/blame/openssl-3.0/crypto/poly1305/asm/poly1305-armv8.pl

The debdiff looks like it makes sense to me, and it all feels pretty
plausible.

Thanks

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

Title:
  armv8 paca: poly1305 users see segfaults when pointer authentication
  in use on AWS Graviton 3 instances

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  In Progress

Bug description:
  [Impact]

  Support for hardware pointer authentication for armv8 systems was
  merged in openssl 1.1.1f, but it contains a bug in the implementation
  for poly1305 message authenticated code routines, which causes the
  calling program to fail pointer authentication, which causes the
  program to crash with a segmentation fault.

  You can easily test it by accessing any website that uses poly1305.
  There is no workaround except use a different MAC.

  [Testcase]

  This bug applies to armv8 systems which support pointer
  authentication. Start an armv8 instance, such as a c7g graviton 3
  instance on AWS, and make sure the paca flag is present in lscpu:

  $ grep paca /proc/cpuinfo
  Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp 
cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 sm3 sm4 asimddp sha512 sve asimdfhm 
dit uscat ilrcpc flagm ssbs paca pacg dcpodp svei8mm svebf16 i8mm bf16 dgh rng

  Next, attempt to connect to any website that uses poly1305 MAC.

  $ curl https://services.gradle.org/distributions/gradle-7.2-bin.zip --output 
gradle-7.2.bin
  % Total % Received % Xferd Average Speed Time Time Time Current
  Dload Upload Total Spent Left Speed
  0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0Segmentation fault (core dumped)

  There is a test package available in the following ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/sf327917-test

  Install it, and poly1305 operations will no longer segfault.

  [Where problems could occur]

  The patch changes the order of operations for loading the SP and
  checking the AUTIASP against it, from checking the AUTIASP against
  nothing then loading the correct SP to check with, to the correct
  loading the SP and then checking the AUTIASP against the SP.

  This only changes one code path for armv8 systems, and other
  architectures are not affected. This is also only limited to poly1305
  MAC.

  If a regression were to occur, it would only affect users of poly1035
  MAC on armv8 with pacs support.

  [Other info]

  The fix landed upstream in openssl 1.1.1i with the following commit:

  commit 5795acffd8706e1cb584284ee5bb3a30986d0e75
  Author: Ard Biesheuvel 
  Date:   Tue Oct 27 18:02:40 2020 +0100
  Subject: crypto/poly1305/asm: fix armv8 pointer authentication
  Link: 
https://github.com/openssl/openssl/commit/5795acffd8706e1cb584284ee5bb3a30986d0e75

  This commit is already present in Impish onward. Only Focal needs the
  fix.

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


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

[Touch-packages] [Bug 1930974] Re: software-properties-gtk is broken again

[Richard]

My software-properties-gtk is 0.99.9.8 on Ubuntu 20.04.3

$ software-properties-gtk

Response:

ERROR:dbus.proxies:Introspect error on :1.2681:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
Traceback (most recent call last):
  File "/usr/local/bin/software-properties-gtk", line 104, in 
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 222, in __init__
self.backend.Reload();
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
return self._connection.call_blocking(self._named_service,
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in 
call_blocking
reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name :1.2681 was not provided by any .service files
Error in sys.excepthook:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 72, in 
apport_excepthook
from apport.fileutils import likely_packaged, get_recent_crashes
  File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in 
from apport.report import Report
  File "/usr/lib/python3/dist-packages/apport/report.py", line 32, in 
import apport.fileutils
  File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 12, in 

import os, glob, subprocess, os.path, time, pwd, sys, requests_unixsocket
ModuleNotFoundError: No module named 'requests_unixsocket'

Original exception was:
Traceback (most recent call last):
  File "/usr/local/bin/software-properties-gtk", line 104, in 
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 222, in __init__
self.backend.Reload();
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
return self._proxy_method(*args, **keywords)
  File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
return self._connection.call_blocking(self._named_service,
  File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in 
call_blocking
reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name :1.2681 was not provided by any .service files

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

Title:
  software-properties-gtk is broken again

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  This issue is happening very often

  $ software-properties-gtk 
  ERROR:dbus.proxies:Introspect error on :1.127:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 211, in __init__
  self.backend.Reload();
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
  return self._proxy_method(*args, **keywords)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
  return self._connection.call_blocking(self._named_service,
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in 
call_blocking
  reply_message = self.send_message_with_reply_and_block(
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name :1.127 was not provided by any .service files

  
  I tried the usual solution I used before:

  $ sudo apt-get update && sudo apt-get install --reinstall python3-six
  python3-certifi

  However, the package is still broken and there is no way to open
  software and updates.

  
  =
  $ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  =
  $ apt-cache policy software-properties-gtk 
  software-properties-gtk:
Installed: 0.98.9.5
Candidate: 0.98.9.5
Version table:
   *** 0.98.9.5 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
  100 /var/lib/dpkg/status
   0.98.9.2 500
  500 http://archive.ubuntu.com/ubuntu focal-security/m

[Touch-packages] [Bug 1960768] Re: fwupd crash on stop

[Mario Limonciello]

> If fwupd is being backported to previous releases of Ubuntu it seems
like libgusb would also need to be backported.

Actually the bug was introduced in libgusb 0.3.8, fixed in libgusb
0.3.9.  If older releases have older than 0.3.8 they shouldn't need
libgusb backport.  See comment #3.

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

Title:
  fwupd crash on stop

Status in OEM Priority Project:
  Fix Released
Status in fwupd package in Ubuntu:
  Invalid
Status in libgusb package in Ubuntu:
  Fix Released
Status in libusb package in Ubuntu:
  Invalid

Bug description:
  I can reproduce crash with a similar stack as below as I stop fwupd
  service.

  https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661

  also test fwupd 1.7.5 
(https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175)
  still can reproduce this issue.

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


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

[Touch-packages] [Bug 1960768] Re: fwupd crash on stop

[Brian Murray]

If fwupd is being backported to previous releases of Ubuntu it seems
like libgusb would also need to be backported.

** Tags added: rls-jj-incoming

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

Title:
  fwupd crash on stop

Status in OEM Priority Project:
  Fix Released
Status in fwupd package in Ubuntu:
  Invalid
Status in libgusb package in Ubuntu:
  Fix Released
Status in libusb package in Ubuntu:
  Invalid

Bug description:
  I can reproduce crash with a similar stack as below as I stop fwupd
  service.

  https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661

  also test fwupd 1.7.5 
(https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175)
  still can reproduce this issue.

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


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

[Touch-packages] [Bug 1930974] Re: software-properties-gtk is broken again

[Brian Murray]

Please test this with the latest version of software-properties for your
release. That is version 0.99.9.8. Thanks in advance.

** Changed in: software-properties (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  software-properties-gtk is broken again

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  This issue is happening very often

  $ software-properties-gtk 
  ERROR:dbus.proxies:Introspect error on :1.127:/: 
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message 
recipient disconnected from message bus without replying
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 211, in __init__
  self.backend.Reload();
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 72, in __call__
  return self._proxy_method(*args, **keywords)
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
  return self._connection.call_blocking(self._named_service,
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in 
call_blocking
  reply_message = self.send_message_with_reply_and_block(
  dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The 
name :1.127 was not provided by any .service files

  
  I tried the usual solution I used before:

  $ sudo apt-get update && sudo apt-get install --reinstall python3-six
  python3-certifi

  However, the package is still broken and there is no way to open
  software and updates.

  
  =
  $ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  =
  $ apt-cache policy software-properties-gtk 
  software-properties-gtk:
Installed: 0.98.9.5
Candidate: 0.98.9.5
Version table:
   *** 0.98.9.5 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal-updates/main i386 Packages
  100 /var/lib/dpkg/status
   0.98.9.2 500
  500 http://archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu focal-security/main i386 Packages
   0.98.9 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  ==

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1930974/+subscriptions


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

[Touch-packages] [Bug 1961105] Re: apport-gtk crashed with SIGSEGV in g_type_create_instance()

[Marc Tardif]

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

Bug #1945114 no longer exists, are you sure this bug is a duplicate of
something that doesn't exist?

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

Title:
  apport-gtk crashed with SIGSEGV in g_type_create_instance()

Status in apport package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 22.04 with mainline kernel 5.15.23-051523-generic.
  I also have wayland disabled in /etc/gdm3/custom.conf. apport-cli runs
  fine but apport-gtk segfaults : /usr/bin/python3
  /usr/share/apport/apport-gtk

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: apport-gtk 2.20.11-0ubuntu77
  Uname: Linux 5.15.23-051523-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CrashReports:
   640:0:123:2052448:2022-02-10 21:13:52.669561017 -0500:2022-02-10 
21:13:52.357564711 -0500:/var/crash/_usr_libexec_fwupd_fwupd.0.crash
   640:1000:123:2128380:2022-02-16 12:33:07.544869439 -0500:2022-02-16 
14:26:00.524005476 -0500:/var/crash/_usr_share_teams_teams.1000.crash
   640:1000:123:6876484:2022-02-16 14:27:04.064037322 -0500:2022-02-16 
14:27:05.064037322 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:0:123:434929:2022-02-11 18:04:37.124000211 -0500:2022-02-11 
18:04:36.836000196 -0500:/var/crash/_usr_libexec_fprintd.0.crash
   640:1000:123:20933:2022-02-16 14:26:00.568005451 -0500:2022-02-16 
14:26:00.568005451 -0500:/var/crash/_usr_bin_apport-unpack.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 16 14:27:04 2022
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2022-02-11 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  InterpreterPath: /usr/bin/python3.9
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Python3Details: /home/dev/src/pyenv/shims/python3, Python 3.9.10, unpackaged
  SegvAnalysis:
   Segfault happened at: 0x7f7e9048dbd4:mov0x18(%rax),%rax
   PC (0x7f7e9048dbd4) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: apport-gtk crashed with SIGSEGV in g_type_create_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Touch-packages] [Bug 1961105] Re: apport-gtk crashed with SIGSEGV in g_type_create_instance()

[Apport retracing service]

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

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1961105/+attachment/5561451/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1961105/+attachment/5561453/+files/Disassembly.txt

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

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

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1961105/+attachment/5561460/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1961105/+attachment/5561461/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1961105/+attachment/5561462/+files/ThreadStacktrace.txt

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

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  apport-gtk crashed with SIGSEGV in g_type_create_instance()

Status in apport package in Ubuntu:
  New

Bug description:
  I'm running Ubuntu 22.04 with mainline kernel 5.15.23-051523-generic.
  I also have wayland disabled in /etc/gdm3/custom.conf. apport-cli runs
  fine but apport-gtk segfaults : /usr/bin/python3
  /usr/share/apport/apport-gtk

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: apport-gtk 2.20.11-0ubuntu77
  Uname: Linux 5.15.23-051523-generic x86_64
  ApportVersion: 2.20.11-0ubuntu77
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashCounter: 1
  CrashReports:
   640:0:123:2052448:2022-02-10 21:13:52.669561017 -0500:2022-02-10 
21:13:52.357564711 -0500:/var/crash/_usr_libexec_fwupd_fwupd.0.crash
   640:1000:123:2128380:2022-02-16 12:33:07.544869439 -0500:2022-02-16 
14:26:00.524005476 -0500:/var/crash/_usr_share_teams_teams.1000.crash
   640:1000:123:6876484:2022-02-16 14:27:04.064037322 -0500:2022-02-16 
14:27:05.064037322 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   640:0:123:434929:2022-02-11 18:04:37.124000211 -0500:2022-02-11 
18:04:36.836000196 -0500:/var/crash/_usr_libexec_fprintd.0.crash
   640:1000:123:20933:2022-02-16 14:26:00.568005451 -0500:2022-02-16 
14:26:00.568005451 -0500:/var/crash/_usr_bin_apport-unpack.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 16 14:27:04 2022
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2022-02-11 (5 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220202)
  InterpreterPath: /usr/bin/python3.9
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Python3Details: /home/dev/src/pyenv/shims/python3, Python 3.9.10, unpackaged
  SegvAnalysis:
   Segfault happened at: 0x7f7e9048dbd4:mov0x18(%rax),%rax
   PC (0x7f7e9048dbd4) ok
   source "0x18(%rax)" (0x0018) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: apport
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0
   g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: apport-gtk crashed with SIGSEGV in g_type_create_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo
  separator:

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


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

[Touch-packages] [Bug 1651451] Re: NSS Shared System Database non-functional

[Sergio Durigan Junior]

Thank you for this bug report.

It seems that it affects only Xenial installations, is that correct?
Would you be able to confirm whether this still applies for
Bionic/Focal/Jammy?

Thanks.

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

Title:
  NSS Shared System Database non-functional

Status in nss package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 appears to ship with libnsssysinit.so configured in
  /etc/pki/nssdb as it should be, but the library isn't *present*. So
  when applications such as Evolution attempt to open it, they fail:

  (evolution:20974): camel-WARNING **: Failed to initialize NSS SQL
  database in sql:/etc/pki/nssdb: NSS error -8126

  For background, see https://wiki.mozilla.org/NSS_Shared_DB_And_LINUX
  and https://wiki.mozilla.org/NSS_Shared_DB

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


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

[Touch-packages] [Bug 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland

[Brian Murray]

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

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

** Also affects: x11-utils (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: apport (Ubuntu Focal)
   Status: New => Triaged

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

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

Title:
  ubuntu-bug -w (using xprop) doesn't work under wayland

Status in apport package in Ubuntu:
  Fix Released
Status in x11-utils package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Triaged
Status in x11-utils source package in Focal:
  New
Status in apport source package in Impish:
  Triaged
Status in x11-utils source package in Impish:
  Invalid
Status in apport source package in Jammy:
  Fix Released
Status in x11-utils source package in Jammy:
  Invalid

Bug description:
  [Impact]

  This bug makes it more difficult for Wayland users to report bugs with
  apport. When a Wayland user tries to use the -w,--window option,
  apport fails silently. We do not want users to face a high barrier to
  submitting bug reports.

  The patch for this bug adds a message explaining that the -w,--window
  option cannot be used on Wayland, and suggests a method for finding
  the window's PID instead.

  [Test Plan]

  * Log on to Ubuntu on Wayland. You can check that 
$XDG_SESSION_TYPE=="wayland" in your current session.
  * Open a terminal, and run `ubuntu-bug -w`.
  * Click on any other window, and observe that the apport UI will not respond.

  [Where problems could occur]

  The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to
  'wayland'. If either of these strings in the patch were wrong, or the
  environment variable was not used in the target release, the condition
  would likely never be true.

  [Original Description]

  I want to report a Bug about the application Studio Controls.

  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.

  I close the message with a click on the appropriate button.

  I click on the window of the application "Studio Controls" that I want
  to report a bug about.

  Nothing happens.

  I wait for a few minutes. Still nothing happens.

  In the console where I started ubuntu-bug -w I see the following
  message:

  (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed

  What I expect:

  Usaully when I use this procedure, after a relatively short while a
  new message window pops up asking me if the bug should be reported and
  showing me the data that is sent to Launchpad.

  I tried other applications, too, same effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apport 2.20.11-0ubuntu71
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportLog:

  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:23 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

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


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

[Touch-packages] [Bug 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland

[Nick Rosbrook]

** Patch added: "apport-lp-1952947-impish.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+attachment/5561447/+files/apport-lp-1952947-impish.debdiff

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

Title:
  ubuntu-bug -w (using xprop) doesn't work under wayland

Status in apport package in Ubuntu:
  Fix Released
Status in x11-utils package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Triaged
Status in x11-utils source package in Focal:
  New
Status in apport source package in Impish:
  Triaged
Status in x11-utils source package in Impish:
  Invalid
Status in apport source package in Jammy:
  Fix Released
Status in x11-utils source package in Jammy:
  Invalid

Bug description:
  [Impact]

  This bug makes it more difficult for Wayland users to report bugs with
  apport. When a Wayland user tries to use the -w,--window option,
  apport fails silently. We do not want users to face a high barrier to
  submitting bug reports.

  The patch for this bug adds a message explaining that the -w,--window
  option cannot be used on Wayland, and suggests a method for finding
  the window's PID instead.

  [Test Plan]

  * Log on to Ubuntu on Wayland. You can check that 
$XDG_SESSION_TYPE=="wayland" in your current session.
  * Open a terminal, and run `ubuntu-bug -w`.
  * Click on any other window, and observe that the apport UI will not respond.

  [Where problems could occur]

  The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to
  'wayland'. If either of these strings in the patch were wrong, or the
  environment variable was not used in the target release, the condition
  would likely never be true.

  [Original Description]

  I want to report a Bug about the application Studio Controls.

  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.

  I close the message with a click on the appropriate button.

  I click on the window of the application "Studio Controls" that I want
  to report a bug about.

  Nothing happens.

  I wait for a few minutes. Still nothing happens.

  In the console where I started ubuntu-bug -w I see the following
  message:

  (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed

  What I expect:

  Usaully when I use this procedure, after a relatively short while a
  new message window pops up asking me if the bug should be reported and
  showing me the data that is sent to Launchpad.

  I tried other applications, too, same effect.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apport 2.20.11-0ubuntu71
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportLog:

  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:23 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

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


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

[Touch-packages] [Bug 1959085] Re: Ubuntu 21.10 boot stuck in initramfs

[Alan Baghumian]

I just found this, I encountered this exact same issue with Jammy
Desktop installer last night and filed a bug here : #1960974

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

Title:
  Ubuntu 21.10 boot stuck in initramfs

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  New

Bug description:
  Hi,

  I just installed the latest Ubuntu desktop from iso file
  ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose
  ZFS and native ZFS encryption of the filesystem. The installation went
  fine. Everything worked as expected.

  Then I upgraded the packages to the latest version via the Software
  updater. After reboot I'm stuck in the initramfs prompt. The following
  command fails:

  mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root//

  Permission denied.

  And the system never asks me for the password to unlock the root fs.

  So, I'm guessing that there is something wrong with the new initramfs
  disk: initrd.img-5.13.0-27-generic

  When I reboot and select the previous version in grub:
  initrd.img-5.13.0-27-generic, the system asks for the password and
  boots without a problem.

  Thanks.

  To summarize:

  1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. 
Minimal install.
  2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted 
and failed to boot the new version.

  I didn't customize anything or installed anything extra.

  root@ubud01:/var# lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10

  root@ubud01:/var# dpkg -l | grep zfs
  ii  libzfs4linux   2.0.6-1ubuntu2 
amd64OpenZFS filesystem library for Linux
  ii  zfs-initramfs  2.0.6-1ubuntu2 
amd64OpenZFS root filesystem capabilities for Linux - 
initramfs
  ii  zfs-zed2.0.6-1ubuntu2 
amd64OpenZFS Event Daemon
  ii  zfsutils-linux 2.0.6-1ubuntu2 
amd64command-line tools to manage OpenZFS filesystems

  root@ubud01:/var# dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-6ubuntu3.1
amd64Standalone shell setup for initramfs
  ii  cryptsetup-initramfs   2:2.3.6-0ubuntu1   
all  disk encryption support - initramfs integration
  ii  gnome-initial-setup40.4-1ubuntu1  
amd64Initial GNOME system setup helper
  ii  init   1.60build1 
amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.60build1 
all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu6   
all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu6   
amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu6   
all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.4-1.1ubuntu3.1 
amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.8-6.1ubuntu2   
amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu3  
all  Linux Standard Base init script functionality
  ii  ncurses-base   6.2+20201114-2build1   
all  basic terminal type definitions
  ii  sysvinit-utils 2.96-7ubuntu1  
amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu3 
amd64X server initialisation tool
  ii  zfs-initramfs  2.0.6-1ubuntu2 
amd64OpenZFS root filesystem capabilities for Linux - 
initramfs

  root@ubud01:/var# zfs list
  NAME   USED  AVAIL REFER  
MOUNTPOINT
  bpool  290M   542M   96K  
/boot
  bpool/BOOT 289M   542M   96K  none
  bpool/BOOT/ubuntu_gtw63h   288M   542M  156M  
/boot
  rpool

[Touch-packages] [Bug 1952947] Re: ubuntu-bug -w (using xprop) doesn't work under wayland

[Nick Rosbrook]

** Description changed:

+ [Impact]
+ 
+ This bug makes it more difficult for Wayland users to report bugs with
+ apport. When a Wayland user tries to use the -w,--window option, apport
+ fails silently. We do not want users to face a high barrier to
+ submitting bug reports.
+ 
+ The patch for this bug adds a message explaining that the -w,--window
+ option cannot be used on Wayland, and suggests a method for finding the
+ window's PID instead.
+ 
+ [Test Plan]
+ 
+ * Log on to Ubuntu on Wayland. You can check that 
$XDG_SESSION_TYPE=="wayland" in your current session.
+ * Open a terminal, and run `ubuntu-bug -w`.
+ * Click on any other window, and observe that the apport UI will not respond.
+ 
+ [Where problems could occur]
+ 
+ The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to
+ 'wayland'. If either of these strings in the patch were wrong, or the
+ environment variable was not used in the target release, the condition
+ would likely never be true.
+ 
+ [Original Description]
+ 
  I want to report a Bug about the application Studio Controls.
  
  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.
  
  I close the message with a click on the appropriate button.
  
  I click on the window of the application "Studio Controls" that I want
  to report a bug about.
  
  Nothing happens.
  
  I wait for a few minutes. Still nothing happens.
  
  In the console where I started ubuntu-bug -w I see the following
  message:
  
  (apport-gtk:11537): Gdk-CRITICAL **: 20:06:41.384:
  gdk_wayland_window_set_dbus_properties_libgtk_only: assertion
  'GDK_IS_WAYLAND_WINDOW (window)' failed
  
- 
  What I expect:
  
  Usaully when I use this procedure, after a relatively short while a new
  message window pops up asking me if the bug should be reported and
  showing me the data that is sent to Launchpad.
  
  I tried other applications, too, same effect.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: apport 2.20.11-0ubuntu71
  ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18
  Uname: Linux 5.13.0-21-lowlatency x86_64
  ApportLog:
-  
+ 
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec  1 20:01:23 2021
  InstallationDate: Installed on 2020-04-12 (597 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to impish on 2021-11-14 (16 days ago)

** Patch added: "apport-lp-1952947-focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1952947/+attachment/5561446/+files/apport-lp-1952947-focal.debdiff

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

Title:
  ubuntu-bug -w (using xprop) doesn't work under wayland

Status in apport package in Ubuntu:
  Fix Released
Status in x11-utils package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  Triaged
Status in x11-utils source package in Focal:
  New
Status in apport source package in Impish:
  Triaged
Status in x11-utils source package in Impish:
  Invalid
Status in apport source package in Jammy:
  Fix Released
Status in x11-utils source package in Jammy:
  Invalid

Bug description:
  [Impact]

  This bug makes it more difficult for Wayland users to report bugs with
  apport. When a Wayland user tries to use the -w,--window option,
  apport fails silently. We do not want users to face a high barrier to
  submitting bug reports.

  The patch for this bug adds a message explaining that the -w,--window
  option cannot be used on Wayland, and suggests a method for finding
  the window's PID instead.

  [Test Plan]

  * Log on to Ubuntu on Wayland. You can check that 
$XDG_SESSION_TYPE=="wayland" in your current session.
  * Open a terminal, and run `ubuntu-bug -w`.
  * Click on any other window, and observe that the apport UI will not respond.

  [Where problems could occur]

  The patch uses os.getenv to check that $XDG_SESSION_TYPE is set to
  'wayland'. If either of these strings in the patch were wrong, or the
  environment variable was not used in the target release, the condition
  would likely never be true.

  [Original Description]

  I want to report a Bug about the application Studio Controls.

  As I did it already quite a few times, I run "ubuntu-bug -w", get a
  message that I can select the window of the app I want to report a bug
  about after closing this message.

  I close the message with a click on the appropriate button.

  I click on the window of the application "Studio Controls" that I want
  to report a bug about.

  Nothing happens.

  I wait for a few minutes. Still nothing happens.

  In the console where I started ubuntu-bug -w I see

[Touch-packages] [Bug 1960404] Re: merge python-debian 0.1.43 from Debian sid

[Julian Andres Klode]

** Changed in: python-debian (Ubuntu)
   Status: New => Fix Committed

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

Title:
  merge python-debian 0.1.43 from Debian sid

Status in python-debian package in Ubuntu:
  Fix Committed

Bug description:
  Please merge the latest Debian version of this package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1960404/+subscriptions


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

[Touch-packages] [Bug 1961092] Re: Installing collectd pulls in the X.org stack

[Robie Basak]

Adding Seb for comment please.

** Changed in: libnotify (Ubuntu)
   Status: New => Triaged

** Changed in: libnotify (Ubuntu)
   Importance: Undecided => Medium

** Description changed:

  On Ubuntu Server, "apt install collectd" pulls in huge parts of the
  X.org stack, which is generally undesirable. This was brought up in
  #ubuntu-server earlier. Workaround: use --no-install-recommends
  
  This seems to be due to collectd -> libnotify4 -> gnome-shell -> ...
- chain of recommends. This appears to have been made worse in an Ubuntu
- delta regarding gnome-shell. Debian's packaging still recommends
- notification-daemon which still pulls in quite a lot.
+ chain. This appears to have been made worse in an Ubuntu delta regarding
+ gnome-shell. Debian's packaging still recommends notification-daemon
+ which still pulls in quite a lot.
  
  It seems odd to me that a lib* package would recommend anything, since
  they tend to be leaves in the dependency tree apart from other lib*
  packages. Further it's difficult to avoid depending on a lib* package
  for optional functionality, so it ends up being inconvenient as
  demonstrated in this use case.
  
  Wouldn't it be better for the desktop environment to recommend something
  that can receive notifications in order for the dependency system to do
  the sensible thing by default, instead of using Recommends from the
  notification sending end? Then headless systems wouldn't end up pulling
  in a "head" via Recommends.
  
  So my suggestion is to drop the Recommends from libnotify4 altogether,
  including in Debian.
  
  From a policy perspective, Recommends is defined as "The Recommends
  field should list packages that would be found together with this one in
  all but unusual installations". I think the headless case is a common
  installation, not an unusual one, so that disqualifies libnotify4
  anyway.

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

Title:
  Installing collectd pulls in the X.org stack

Status in libnotify package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu Server, "apt install collectd" pulls in huge parts of the
  X.org stack, which is generally undesirable. This was brought up in
  #ubuntu-server earlier. Workaround: use --no-install-recommends

  This seems to be due to collectd -> libnotify4 -> gnome-shell -> ...
  chain. This appears to have been made worse in an Ubuntu delta
  regarding gnome-shell. Debian's packaging still recommends
  notification-daemon which still pulls in quite a lot.

  It seems odd to me that a lib* package would recommend anything, since
  they tend to be leaves in the dependency tree apart from other lib*
  packages. Further it's difficult to avoid depending on a lib* package
  for optional functionality, so it ends up being inconvenient as
  demonstrated in this use case.

  Wouldn't it be better for the desktop environment to recommend
  something that can receive notifications in order for the dependency
  system to do the sensible thing by default, instead of using
  Recommends from the notification sending end? Then headless systems
  wouldn't end up pulling in a "head" via Recommends.

  So my suggestion is to drop the Recommends from libnotify4 altogether,
  including in Debian.

  From a policy perspective, Recommends is defined as "The Recommends
  field should list packages that would be found together with this one
  in all but unusual installations". I think the headless case is a
  common installation, not an unusual one, so that disqualifies
  libnotify4 anyway.

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


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

[Touch-packages] [Bug 1961092] [NEW] Installing collectd pulls in the X.org stack

[Robie Basak]

Public bug reported:

On Ubuntu Server, "apt install collectd" pulls in huge parts of the
X.org stack, which is generally undesirable. This was brought up in
#ubuntu-server earlier. Workaround: use --no-install-recommends

This seems to be due to collectd -> libnotify4 -> gnome-shell -> ...
chain. This appears to have been made worse in an Ubuntu delta regarding
gnome-shell. Debian's packaging still recommends notification-daemon
which still pulls in quite a lot.

It seems odd to me that a lib* package would recommend anything, since
they tend to be leaves in the dependency tree apart from other lib*
packages. Further it's difficult to avoid depending on a lib* package
for optional functionality, so it ends up being inconvenient as
demonstrated in this use case.

Wouldn't it be better for the desktop environment to recommend something
that can receive notifications in order for the dependency system to do
the sensible thing by default, instead of using Recommends from the
notification sending end? Then headless systems wouldn't end up pulling
in a "head" via Recommends.

So my suggestion is to drop the Recommends from libnotify4 altogether,
including in Debian.

>From a policy perspective, Recommends is defined as "The Recommends
field should list packages that would be found together with this one in
all but unusual installations". I think the headless case is a common
installation, not an unusual one, so that disqualifies libnotify4
anyway.

** Affects: libnotify (Ubuntu)
 Importance: Medium
 Status: Triaged

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

Title:
  Installing collectd pulls in the X.org stack

Status in libnotify package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu Server, "apt install collectd" pulls in huge parts of the
  X.org stack, which is generally undesirable. This was brought up in
  #ubuntu-server earlier. Workaround: use --no-install-recommends

  This seems to be due to collectd -> libnotify4 -> gnome-shell -> ...
  chain. This appears to have been made worse in an Ubuntu delta
  regarding gnome-shell. Debian's packaging still recommends
  notification-daemon which still pulls in quite a lot.

  It seems odd to me that a lib* package would recommend anything, since
  they tend to be leaves in the dependency tree apart from other lib*
  packages. Further it's difficult to avoid depending on a lib* package
  for optional functionality, so it ends up being inconvenient as
  demonstrated in this use case.

  Wouldn't it be better for the desktop environment to recommend
  something that can receive notifications in order for the dependency
  system to do the sensible thing by default, instead of using
  Recommends from the notification sending end? Then headless systems
  wouldn't end up pulling in a "head" via Recommends.

  So my suggestion is to drop the Recommends from libnotify4 altogether,
  including in Debian.

  From a policy perspective, Recommends is defined as "The Recommends
  field should list packages that would be found together with this one
  in all but unusual installations". I think the headless case is a
  common installation, not an unusual one, so that disqualifies
  libnotify4 anyway.

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


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

[Touch-packages] [Bug 1715642] Re: display problem

[Paul White ]

Nima, I thought it best to ask than to close just in case you still saw
a problem *related* in any way to the one that you saw while using the
Trusty release.

So, I'll close this as "Invalid" as the issue was never confirmed by
another user and the Trusty release in now EOL.

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

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

Title:
  display problem

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  when I run a program through wine that needs to reduce the resolution to 
windows xp basic (800 x 600), wine program stopping unexpectedly and my desktop 
changes resolution so every time I need to restart my ubuntu.
  for more information pls check the photo I sent.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116~14.04.1-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.22  Thu May  4 00:55:03 
PDT 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Sep  7 17:33:30 2017
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-93-generic, x86_64: installed
   nvidia-381, 381.22, 4.4.0-93-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d]
   NVIDIA Corporation GF108M [GeForce GT 540M] [10de:0df4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:108d]
  InstallationDate: Installed on 2016-12-06 (274 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: Micro-Star International Co., Ltd. GE620/GE620DX/FX620DX
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-93-generic 
root=UUID=f01602a0-6076-4436-9a4b-e05e01b6cdc5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16G5IMS V1.0F
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16G5
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16G5IMSV1.0F:bd05/26/2011:svnMicro-StarInternationalCo.,Ltd.:pnGE620/GE620DX/FX620DX:pvrTobefilledbyO.E.M.:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16G5:rvrTobefilledbyO.E.M.:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrTobefilledbyO.E.M.:
  dmi.product.name: GE620/GE620DX/FX620DX
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs 20090808ubuntu36
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Sep  7 17:29:53 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty2

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


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

[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy

[Christian Ehrhardt ]

Robie will take a look, but likely not immediately, more like next week.

** Tags removed: server-triage-discuss

** Changed in: six (Ubuntu)
 Assignee: (unassigned) => Robie Basak (racb)

** Changed in: pyyaml (Ubuntu)
 Assignee: (unassigned) => Robie Basak (racb)

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

Title:
  python3-yaml and python3-six are not co-installable with python-is-
  python2 in jammy

Status in pyyaml package in Ubuntu:
  Confirmed
Status in six package in Ubuntu:
  Confirmed

Bug description:
  The packages python3-yaml and python-is-python2 are not co-installable
  in jammy and I believe they should be.  This currently prevents me
  from upgrading one of my machines from focal to jammy.

  Further analysis with the help of Stefano Rivera revealed that what-
  is-python no longer produces a python-is-python2 package and the
  changelog hints at that being intentional.  Jammy still has a python2
  package, though.

  python3-yaml in jammy breaks on python (<2.7.18).  The python-is-
  python2 package in focal is version 2.7.17-4 and in impish it is
  2.7.18-9 and thus will be forcefully removed when going to jammy.

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


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

[Touch-packages] [Bug 1875407] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[edward prest]

while installing kicad v6 on brand new 20.04 install on ssd

using

sudo add-apt-repository --yes ppa:kicad/kicad-6.0-releases
sudo apt update
sudo apt install --install-recommends kicad
# If you want demo projects
sudo apt install kicad-demos

fails with


Processing triggers for desktop-file-utils (0.24-1ubuntu3) ...
Processing triggers for initramfs-tools (0.136ubuntu6.6) ...
update-initramfs: Generating /boot/initrd.img-5.13.0-28-generic
E: /usr/share/initramfs-tools/hooks/iscan failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.13.0-28-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
Errors were encountered while processing:
 initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package initramfs-tools 0.136ubuntu6 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Received this error when doing do-release-upgrade from ubuntu 18.04.4
  to 20.4

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
  Uname: Linux 4.15.0-96-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Apr 27 09:59:42 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-01-12 (1567 days ago)
  InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 
2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1875407/+subscriptions


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

[Touch-packages] [Bug 989961] Re: Provide a gmake symlink

[Julian Andres Klode]

Superseded by a no-change rebuild -4.1build1; it turns out the delta was
not needed anymore.

** Changed in: make-dfsg (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Provide a gmake symlink

Status in make-dfsg package in Ubuntu:
  Fix Committed

Bug description:
  Some, albeit older or proprietary software, expects a gmake symlink
  for gnu make.  Can this be provided?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/989961/+subscriptions


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

[Touch-packages] [Bug 1939973] Re: make 4.3-4.1 triggers build failures

[Julian Andres Klode]

I rebuilt make-dfsg 4.1 without changes and cross-toolchain-base mostly
finished building against it in the same bileto ppa, so this issue seems
resolved, probably some toolchain bug?

https://launchpad.net/~ci-train-ppa-
service/+archive/ubuntu/4783/+packages

** Changed in: make-dfsg (Ubuntu)
   Status: Confirmed => Fix Committed

** No longer affects: make-dfsg (Ubuntu Impish)

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

Title:
  make 4.3-4.1 triggers build failures

Status in make-dfsg package in Ubuntu:
  Fix Committed

Bug description:
  trying to rebuild cross-toolchain-base from
  https://launchpad.net/~ubuntu-toolchain-r/+archive/ubuntu/volatile/+packages

  triggers a build failure:

  [...]
  START stamp-dir/init-binutils
  tar -x -f  /usr/src/binutils/binutils-2.37.tar.xz
  set -e; cd binutils-2.37 ; cp -a /usr/src/binutils/debian/ . ; if [ -n 
"$(grep -v '^\#' /<>/debian/patches/binutils/series)" ]; then 
QUILT_PATCHES=/<>/debian/patches/binutils quilt --quiltrc 
/dev/null  push -a; fi; rm -rf .pc
  cd binutils-2.37 ; env -i CROSS_ARCHS="amd64 i386 s390x ppc64el arm64 armhf 
armel  powerpc" debian/rules stamps/control
  make: dpkg-architecture: No such file or directory
  make: lsb_release: No such file or directory
  make: lsb_release: No such file or directory
  make: pwd: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  make: dpkg-parsechangelog: No such file or directory
  debian/rules:163: *** unexpected source package name: .  Stop.
  make: *** [debian/rules:215: stamp-dir/init-binutils] Error 2
  dpkg-buildpackage.pl: error: debian/rules build subprocess returned exit 
status 2

  
  working around by omitting the -i option to env, or by setting PATH 
explicitly. Reverting to the version in the release pocket lets the c-t-b- 
build succeed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/make-dfsg/+bug/1939973/+subscriptions


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

[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Dariusz Gadomski]

I have prepared a patch for bionic and tested it:
# ip link add eth3 type dummy
# date; /usr/lib/klibc/bin/ipconfig -t 2 eth3; date
śro, 16 lut 2022, 15:20:26 CET
IP-Config: eth3 hardware address ba:e2:3c:e9:db:e4 mtu 1500 DHCP RARP
Lowered timeout to match user request = (2 s) 
IP-Config: no response after 2 secs - giving up
śro, 16 lut 2022, 15:20:28 CET

I have sponsored the patch for review (2.0.4-9ubuntu2.18.04.1).

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

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

Status in klibc package in Ubuntu:
  New
Status in klibc source package in Bionic:
  In Progress

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

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

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

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

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

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

  [Original Description]

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

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

  s->expire = now + 10;

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

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

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

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

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 1960947] Re: Graphical issues for GtKGL in software rendering

[J-P Nurmi]

I can confirm that libgtk-3-0 3.24.20-0ubuntu1.1 from focal-proposed
fixes the rendering issue.

I have tested with:

1) the attached minimal test case:

gcc -o testcase testcase.c `pkg-config --cflags --libs gtk+-3.0`
./testcase

2) a full-blown flutter app:

snap install --classic flutter
flutter config --enable-linux-desktop
flutter create test_app
cd test_app
flutter run


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

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

Title:
  Graphical issues for GtKGL in software rendering

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

Bug description:
  * Issue

  GTK applications using GL graphic show corruption problems under
  software rendering

  
  * Test case

  1. install gtk-3-examples
  2. $ LIBGL_ALWAYS_SOFTWARE=1 gtk3-demo
  3. select the gl example, it should render without issues

  * Regression potentiel

  The change is in the GL backend so check for rendering issues in GTK
  softwares using GL, including flutter applications

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


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

[Touch-packages] [Bug 1952107] Re: Google Contacts API Deprecated

[Braath Waate]

Upgrade to evolution 3.36.5-0ubuntu2 on Ubuntu 20.04.03 (focal) did not
fix the bug for me either.  I am wondering if anyone has gotten it to
work on focal.

To fix the bug on Ubuntu 18.04 (bionic), I had to compile the source
(master branch), largely following the instructions at
https://wiki.gnome.org/Apps/Evolution/Building, but I also had to build
libcmark and turn off introspection, vala, and weather to get it to
build.  I couldn't use the flatpak build because the machine is a laptop
and very limited on disk space.

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

Title:
  Google Contacts API Deprecated

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

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

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

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

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

  

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

  > Failed to connect address book “ : Contacts”

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

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

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

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


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

[Touch-packages] [Bug 1959126] Re: Consider update to 3.68.2

[Athos Ribeiro]

Bug 1737470 fix introduced
https://hg.mozilla.org/projects/nss/rev/dea71cbef9e03636f37c6cb120f8deccce6e17dd,
which is the patch applied as debian/patches/CVE-2021-43527.patch in the
current jammy package to fix CVE-2021-43527.

While Bug 1735028 is also private, its fix is not included in our
current patches.

Finally, SHA-2 support to mozilla::pkix's OCSP implementation is also
not present in our delta
(https://bugzilla.mozilla.org/show_bug.cgi?id=966856). Meaning that
going for the update would include support to SHA-2 hashes in CertIDs in
OCSP responses.



** Bug watch added: Mozilla Bugzilla #966856
   https://bugzilla.mozilla.org/show_bug.cgi?id=966856

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

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

Title:
  Consider update to 3.68.2

Status in nss package in Ubuntu:
  In Progress

Bug description:
  Debian is shipping nss 3.73.1, but that is not an ESR release. Ubuntu
  is on 3.68, which is ESR, but two releases behind: upstream has
  3.68.2.

  Here are upstream's release notes:
  3.68.1: 
https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/jFIuiWbCphk
  Changes:
   - Bug 1735028 - check for missing signedData field. 
   - Bug 1737470 - Ensure DER encoded signatures are within size limits.

  3.68.2: 
https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/uGRwqw6Ove8
  Change:
 - Bug 966856 - Add SHA-2 support to mozilla::pkix's OCSP implementation

  Our 3.68 package has a patch for CVE-2021-43527. It's unclear if any
  of the above changes is that CVE. The most promising one was bug
  1737470, but the bug is private.

  The request here is to investigate if our patched 3.68 has one or more
  of the fixes in the above point releases, and if it would be worth it
  to go to 3.68.2. I think we should not go to 3.7x.

  Ubuntu has been on 3.68 since impish.

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


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

[Touch-packages] [Bug 1960947] Re: Graphical issues for GtKGL in software rendering

[J-P Nurmi]

Hi all. The conditions for reproducing the issue: CSD + OpenGL + swrast.

Notice that the GTK GL example doesn't use CSD i.e. it doesn't set a
custom GtkWindow titlebar. I have attached a small test case that
reproduces the issue.

** Attachment added: "testcase.c"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960947/+attachment/5561410/+files/testcase.c

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

Title:
  Graphical issues for GtKGL in software rendering

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

Bug description:
  * Issue

  GTK applications using GL graphic show corruption problems under
  software rendering

  
  * Test case

  1. install gtk-3-examples
  2. $ LIBGL_ALWAYS_SOFTWARE=1 gtk3-demo
  3. select the gl example, it should render without issues

  * Regression potentiel

  The change is in the GL backend so check for rendering issues in GTK
  softwares using GL, including flutter applications

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


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

[Touch-packages] [Bug 1959126] Re: Consider update to 3.68.2

[Athos Ribeiro]

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

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

Title:
  Consider update to 3.68.2

Status in nss package in Ubuntu:
  In Progress

Bug description:
  Debian is shipping nss 3.73.1, but that is not an ESR release. Ubuntu
  is on 3.68, which is ESR, but two releases behind: upstream has
  3.68.2.

  Here are upstream's release notes:
  3.68.1: 
https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/jFIuiWbCphk
  Changes:
   - Bug 1735028 - check for missing signedData field. 
   - Bug 1737470 - Ensure DER encoded signatures are within size limits.

  3.68.2: 
https://groups.google.com/a/mozilla.org/g/dev-tech-crypto/c/uGRwqw6Ove8
  Change:
 - Bug 966856 - Add SHA-2 support to mozilla::pkix's OCSP implementation

  Our 3.68 package has a patch for CVE-2021-43527. It's unclear if any
  of the above changes is that CVE. The most promising one was bug
  1737470, but the bug is private.

  The request here is to investigate if our patched 3.68 has one or more
  of the fixes in the above point releases, and if it would be worth it
  to go to 3.68.2. I think we should not go to 3.7x.

  Ubuntu has been on 3.68 since impish.

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


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

[Touch-packages] [Bug 1961055] Re: Key load error: Failed to open key material file: No such file or directory

[geole0]

** Description changed:

  Hello
  This morning I downloaded the UBUNTU JAMMY version which had just been made 
an hour earlier. I installed it asking for encryption.
  
  When I boot, the password is asked. He is accepted. But root mount is denied.
  ...
  find: /dev/zvol: No such file or directory
  key load error: Failed to open key matéral file No such file or directory
  
  Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted: permission
  denied
  
- 
- Picture will come
+ Picture is here https://zupimages.net/viewer.php?id=22/07/v372.jpg

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

Title:
  Key load error: Failed to open key material file: No such file or
  directory

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello
  This morning I downloaded the UBUNTU JAMMY version which had just been made 
an hour earlier. I installed it asking for encryption.

  When I boot, the password is asked. He is accepted. But root mount is denied.
  ...
  find: /dev/zvol: No such file or directory
  key load error: Failed to open key matéral file No such file or directory

  Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted:
  permission denied

  Picture is here https://zupimages.net/viewer.php?id=22/07/v372.jpg

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


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

[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}

[Miriam España Acebal]

Verification for Focal... OK:

-> Availability from proposed

root@focal:~# apt list --upgradable -a | grep rsync

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

rsync/focal-proposed 3.1.3-8ubuntu0.2 amd64 [upgradable from: 3.1.3-8ubuntu0.1]
rsync/focal-updates,now 3.1.3-8ubuntu0.1 amd64 [installed,upgradable to: 
3.1.3-8ubuntu0.2]
rsync/focal 3.1.3-8 amd64

-> After installing, executing the test for scenario 16:

root@focal:~# rsync -avvvz --delete source_dir target_dir
.
.
send files finished
total: matches=0  hash_hits=0  false_alarms=0 data=9162752000
recv_files phase=2
recv_files finished
generate_files phase=3
generate_files finished

sent 9,750,166 bytes  received 3,805,745 bytes  186,978.08 bytes/sec
total size is 9,162,752,000  speedup is 675.92
[sender] _exit_cleanup(code=0, file=main.c, line=1207): about to call exit(0)
root@nagios-focal:~# 


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

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

Title:
  rsync hangs on select(5, [], [4], [], {60, 0}

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Bionic:
  Fix Committed
Status in rsync source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  What the user suffering from this bug experiences is that the big
  amount of informative messages related to the copy process with the
  three spawned processes(sender, receiver and generator)  exhaust the
  I/O buffer and the sync gets stuck, either because there are too many
  files to synchronise and/or because too many detail messages (levels
  of verbose mode) have been requested in the output.

  The fix, that comes from upstream and is applied there since version
  3.2.0., increments the size of the receiver's I/O buffer.

  [Test Plan]
  This test plan is for Focal, but it's the same for Bionic.

  0.Preparing the test environment:

  #Preparing the container
  lxc launch images:ubuntu/focal rsync-iobuffer-focal
  lxc shell rsync-iobuffer-focal
  apt update -y
  apt upgrade -y

  #Installing necessary tools
  apt install rsync

  #Get test cases from comments #16 and #19 on this LP bug: As test case
  #16 covers both aspects (a lot of files and upper verbosity) and test
  #19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19
  scenario  (but, please, feel to reach me it if you consider it
  necessary and I'll provide the steps and bad/good scenarios).

  cd /tmp/

  #16
  Paste the contents of https://pastebin.com/raw/ctzJJGwt:

  #!/bin/bash
  mkdir source_dir
  pushd source_dir
  dd if=/dev/zero of=source bs=600K count=1

  for i in `seq 1 11500`;
  do
  cp -v source file_$i;
  done

  rm source

  for i in `seq 1 10`;
  do
   dd if=/dev/zero of=file_large_$i bs=200M count=1
  done

  popd

  echo "Created 11500 files with size 600K and 10 files with size 200M, try the 
following command:"
  echo "rsync -avvvz --delete source_dir target_dir"

  in a new file script_comment16.sh

  chmod +x script_comment16.sh
  ./script_comment16.sh

  1. Bad cases (without and with using strace):

  # Scenario from comment 16
  $ rsync -avvvz --delete source_dir target_dir
  sending incremental file list
  [sender] make_file(source_dir,*,0)
  send_file_list done
  [sender] pushing local filters for /root/source_dir/
  [sender] make_file(source_dir/file_3048,*,2)
  [sender] make_file(source_dir/file_11358,*,2)
  [sender] make_file(source_dir/file_5914,*,2)
  [sender] make_file(source_dir/file_5880,*,2)
  [sender] make_file(source_dir/file_9318,*,2)
  [sender] make_file(source_dir/file_5539,*,2)
  [...]
  sending file_sum
  false_alarms=0 hash_hits=0 matches=0
  sender finished source_dir/file_10807
  send_files(903, source_dir/file_10808)
  send_files mapped source_dir/file_10808 of size 614400
  calling match_sums source_dir/file_10808
  source_dir/file_10808

  It hangs here, where using strace we can see:

  $ strace rsync -avvvz --delete source_dir target_dir
  source_dir/file_11280
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) 
= 262144
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) 
= 262144
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) = 
90112
  select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left 
{tv_sec=59, tv_usec=96})
  read(5, 
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 
1900) = 1900
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}

  1. Good cases:

  # Scenario from comment 16

  $ rsync -avvvz --delete source_dir target_dir
  sending incremental file list
  [

[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}

[Miriam España Acebal]

Verification for Focal... OK:

-> Availability from proposed:
root@nagios:~# apt list --upgradable -a | grep rsync

WARNING: apt does not have a stable CLI interface. Use with caution in
scripts.

rsync/focal-proposed 3.1.3-8ubuntu0.2 amd64 [upgradable from: 3.1.3-8ubuntu0.1]
rsync/focal-updates,now 3.1.3-8ubuntu0.1 amd64 [installed,upgradable to: 
3.1.3-8ubuntu0.2]
rsync/focal 3.1.3-8 amd64

-> After installing, executing test for scenario 16:
root@nagios:~# rsync -avvvz --delete source_dir target_dir
.
.
.
send files finished
total: matches=0  hash_hits=0  false_alarms=0 data=9162752000
recv_files phase=2
recv_files finished
generate_files phase=3
generate_files finished

sent 9,750,166 bytes  received 3,805,745 bytes  186,978.08 bytes/sec
total size is 9,162,752,000  speedup is 675.92
[sender] _exit_cleanup(code=0, file=main.c, line=1207): about to call exit(0)
root@nagios:~#

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

Title:
  rsync hangs on select(5, [], [4], [], {60, 0}

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Bionic:
  Fix Committed
Status in rsync source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  What the user suffering from this bug experiences is that the big
  amount of informative messages related to the copy process with the
  three spawned processes(sender, receiver and generator)  exhaust the
  I/O buffer and the sync gets stuck, either because there are too many
  files to synchronise and/or because too many detail messages (levels
  of verbose mode) have been requested in the output.

  The fix, that comes from upstream and is applied there since version
  3.2.0., increments the size of the receiver's I/O buffer.

  [Test Plan]
  This test plan is for Focal, but it's the same for Bionic.

  0.Preparing the test environment:

  #Preparing the container
  lxc launch images:ubuntu/focal rsync-iobuffer-focal
  lxc shell rsync-iobuffer-focal
  apt update -y
  apt upgrade -y

  #Installing necessary tools
  apt install rsync

  #Get test cases from comments #16 and #19 on this LP bug: As test case
  #16 covers both aspects (a lot of files and upper verbosity) and test
  #19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19
  scenario  (but, please, feel to reach me it if you consider it
  necessary and I'll provide the steps and bad/good scenarios).

  cd /tmp/

  #16
  Paste the contents of https://pastebin.com/raw/ctzJJGwt:

  #!/bin/bash
  mkdir source_dir
  pushd source_dir
  dd if=/dev/zero of=source bs=600K count=1

  for i in `seq 1 11500`;
  do
  cp -v source file_$i;
  done

  rm source

  for i in `seq 1 10`;
  do
   dd if=/dev/zero of=file_large_$i bs=200M count=1
  done

  popd

  echo "Created 11500 files with size 600K and 10 files with size 200M, try the 
following command:"
  echo "rsync -avvvz --delete source_dir target_dir"

  in a new file script_comment16.sh

  chmod +x script_comment16.sh
  ./script_comment16.sh

  1. Bad cases (without and with using strace):

  # Scenario from comment 16
  $ rsync -avvvz --delete source_dir target_dir
  sending incremental file list
  [sender] make_file(source_dir,*,0)
  send_file_list done
  [sender] pushing local filters for /root/source_dir/
  [sender] make_file(source_dir/file_3048,*,2)
  [sender] make_file(source_dir/file_11358,*,2)
  [sender] make_file(source_dir/file_5914,*,2)
  [sender] make_file(source_dir/file_5880,*,2)
  [sender] make_file(source_dir/file_9318,*,2)
  [sender] make_file(source_dir/file_5539,*,2)
  [...]
  sending file_sum
  false_alarms=0 hash_hits=0 matches=0
  sender finished source_dir/file_10807
  send_files(903, source_dir/file_10808)
  send_files mapped source_dir/file_10808 of size 614400
  calling match_sums source_dir/file_10808
  source_dir/file_10808

  It hangs here, where using strace we can see:

  $ strace rsync -avvvz --delete source_dir target_dir
  source_dir/file_11280
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) 
= 262144
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) 
= 262144
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) = 
90112
  select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left 
{tv_sec=59, tv_usec=96})
  read(5, 
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\240\0\0\0"..., 
1900) = 1900
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}) = 0 (Timeout)
  select(5, [], [4], [], {tv_sec=60, tv_usec=0}

  1. Good cases:

  # Scenario from comment 16

  $ rsync -avvvz --delete source_dir target_dir
  sending incremental file list
  [sender] make_file(source_dir,*,0)
  send_file_list done
  [sender] pushing local filters for

[Touch-packages] [Bug 1528921] Re: rsync hangs on select(5, [], [4], [], {60, 0}

[Miriam España Acebal]

Verification for Bionic... OK:

-> Availability from proposed:

root@bionic:/tmp# apt-cache policy rsync
rsync:
  Installed: 3.1.2-2.1ubuntu1.3
  Candidate: 3.1.2-2.1ubuntu1.3
  Version table:
 *** 3.1.2-2.1ubuntu1.3 500
500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 3.1.2-2.1ubuntu1.2 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
 3.1.2-2.1ubuntu1.1 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 3.1.2-2.1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages


-> After installing, executing test for scenario 16:
root@bionic:/tmp# 
.
.
.
send_files phase=2
send files finished
total: matches=0  hash_hits=0  false_alarms=0 data=9162752000
recv_files phase=2
recv_files finished
generate_files phase=3
generate_files finished

sent 9,750,855 bytes  received 3,629,561 bytes  201,209.26 bytes/sec
total size is 9,162,752,000  speedup is 684.79
[sender] _exit_cleanup(code=0, file=main.c, line=1196): about to call exit(0)
root@bionic:/tmp# 


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

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

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

Title:
  rsync hangs on select(5, [], [4], [], {60, 0}

Status in rsync:
  Unknown
Status in rsync package in Ubuntu:
  Fix Released
Status in rsync source package in Bionic:
  Fix Committed
Status in rsync source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  What the user suffering from this bug experiences is that the big
  amount of informative messages related to the copy process with the
  three spawned processes(sender, receiver and generator)  exhaust the
  I/O buffer and the sync gets stuck, either because there are too many
  files to synchronise and/or because too many detail messages (levels
  of verbose mode) have been requested in the output.

  The fix, that comes from upstream and is applied there since version
  3.2.0., increments the size of the receiver's I/O buffer.

  [Test Plan]
  This test plan is for Focal, but it's the same for Bionic.

  0.Preparing the test environment:

  #Preparing the container
  lxc launch images:ubuntu/focal rsync-iobuffer-focal
  lxc shell rsync-iobuffer-focal
  apt update -y
  apt upgrade -y

  #Installing necessary tools
  apt install rsync

  #Get test cases from comments #16 and #19 on this LP bug: As test case
  #16 covers both aspects (a lot of files and upper verbosity) and test
  #19 uses a huge tarball (120 Mb), I'm removing from this SRU the #19
  scenario  (but, please, feel to reach me it if you consider it
  necessary and I'll provide the steps and bad/good scenarios).

  cd /tmp/

  #16
  Paste the contents of https://pastebin.com/raw/ctzJJGwt:

  #!/bin/bash
  mkdir source_dir
  pushd source_dir
  dd if=/dev/zero of=source bs=600K count=1

  for i in `seq 1 11500`;
  do
  cp -v source file_$i;
  done

  rm source

  for i in `seq 1 10`;
  do
   dd if=/dev/zero of=file_large_$i bs=200M count=1
  done

  popd

  echo "Created 11500 files with size 600K and 10 files with size 200M, try the 
following command:"
  echo "rsync -avvvz --delete source_dir target_dir"

  in a new file script_comment16.sh

  chmod +x script_comment16.sh
  ./script_comment16.sh

  1. Bad cases (without and with using strace):

  # Scenario from comment 16
  $ rsync -avvvz --delete source_dir target_dir
  sending incremental file list
  [sender] make_file(source_dir,*,0)
  send_file_list done
  [sender] pushing local filters for /root/source_dir/
  [sender] make_file(source_dir/file_3048,*,2)
  [sender] make_file(source_dir/file_11358,*,2)
  [sender] make_file(source_dir/file_5914,*,2)
  [sender] make_file(source_dir/file_5880,*,2)
  [sender] make_file(source_dir/file_9318,*,2)
  [sender] make_file(source_dir/file_5539,*,2)
  [...]
  sending file_sum
  false_alarms=0 hash_hits=0 matches=0
  sender finished source_dir/file_10807
  send_files(903, source_dir/file_10808)
  send_files mapped source_dir/file_10808 of size 614400
  calling match_sums source_dir/file_10808
  source_dir/file_10808

  It hangs here, where using strace we can see:

  $ strace rsync -avvvz --delete source_dir target_dir
  source_dir/file_11280
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) 
= 262144
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 262144) 
= 262144
  read(3, 
"\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 90112) = 
90112
  select(6, [5], [4], [5], {tv_sec=60, tv_usec=0}) = 1 (in [5], left 
{tv_sec=59, tv_usec=96})
  read(5, 
"\0\0\0\0\0\0\0\1\0\240\0\0\0\0\0\0\0\0

[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

[Robie Basak]

OK, so if this is the risk, then I think we should consider what
mitigation might be appropriate at least.

There are many desktop environments packaged in Ubuntu, and some of them
may regress. I'm not sure it's practical to test them all, especially if
you don't have the hardware that might trigger the issue.

But perhaps we should at least contact the Ubuntu Flavors to see if they
have any opinion, since they are directly spending effort maintaining
some of those environments.

I'll send them an email so that they have an opportunity to comment. If
they'd like to make suggestions on how to mitigate this risk then they
can do that here. If they don't see any reason to object or make any
suggestions then I'll accept this SRU.

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Impish:
  In Progress
Status in systemd source package in Jammy:
  Fix Released

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

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  In some old HP platforms (contains Intel-HID and HPQ6001 in same
  machine), the user will aware the airplane mode toggled very quickly
  e.g. turn-on and turn-off immediately (or works good without problem,
  depends on how DM handles multiple rfkill events).

  In this case, you could check:
  1. sudo evtest
  # You probably could see 
  # ...
  # /dev/input/event8:  Intel HID events
  # ...
  # /dev/input/event11: Wireless hotkeys
  # or "HP Wireless hotkeys" depends on your kernel version

  2. try to listen these events when pressing airplane key, you will
  probably see these two events will send the keycode out.

  3. check the components own this event
  $ sudo udevadm info -a /dev/input/event11
  # ...
  # ATTRS{phys}=="hpq6001/input0"

  $ sudo udevadm info -a /dev/input/event8
  # ...
  #DRIVERS=="intel-hid"

  4. check your hwdb is affect.
  $ grep -rn "Intel HID" /lib/udev/hwdb.d/60-keyboard.hwdb
  # If you didn't see anything then it means your intel-hid is unmask.

  5. You could report a bug to your DM for dealing with two rfkill events (same 
as g-s-d[3]). Before your DM solves this issue, you could mask intel-hid as 
workaround (but it will be overwritten in next upgrade) by adding:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pn*:pvr*
  ```
  to /lib/udev/hwdb.d/60-keyboard.hwdb

  then
  $ systemd-hwdb update
  $ udevadm trigger

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

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


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

[Touch-packages] [Bug 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

[Łukasz Zemczak]

Since the patch has been submitted upstream and there was no hard
objection to it, I think you can proceed in preparing the SRU and
getting it uploaded for SRU review. Just be sure to include the upstream
link in the Forwarded: section of the patch. Thanks!

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

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

Status in klibc package in Ubuntu:
  New
Status in klibc source package in Bionic:
  In Progress

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

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

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

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

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

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

  [Original Description]

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

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

  s->expire = now + 10;

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

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

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

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

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

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

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

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

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

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

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


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

[Touch-packages] [Bug 1961055] [NEW] Key load error: Failed to open key material file: No such file or directory

[geole0]

Public bug reported:

Hello
This morning I downloaded the UBUNTU JAMMY version which had just been made an 
hour earlier. I installed it asking for encryption.

When I boot, the password is asked. He is accepted. But root mount is denied.
...
find: /dev/zvol: No such file or directory
key load error: Failed to open key matéral file No such file or directory

Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted: permission
denied


Picture will come

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

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

Title:
  Key load error: Failed to open key material file: No such file or
  directory

Status in systemd package in Ubuntu:
  New

Bug description:
  Hello
  This morning I downloaded the UBUNTU JAMMY version which had just been made 
an hour earlier. I installed it asking for encryption.

  When I boot, the password is asked. He is accepted. But root mount is denied.
  ...
  find: /dev/zvol: No such file or directory
  key load error: Failed to open key matéral file No such file or directory

  Message filesystem rpool/ROOT/ubuntu_trj428 canot be mounted:
  permission denied


  Picture will come

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


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

[Touch-packages] [Bug 1960947] Re: Graphical issues for GtKGL in software rendering

[Robie Basak]

Hello Sebastien, or anyone else affected,

Accepted gtk+3.0 into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/gtk+3.0/3.24.20-0ubuntu1.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: gtk+3.0 (Ubuntu Focal)
   Status: New => Fix Committed

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

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

Title:
  Graphical issues for GtKGL in software rendering

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

Bug description:
  * Issue

  GTK applications using GL graphic show corruption problems under
  software rendering

  
  * Test case

  1. install gtk-3-examples
  2. $ LIBGL_ALWAYS_SOFTWARE=1 gtk3-demo
  3. select the gl example, it should render without issues

  * Regression potentiel

  The change is in the GL backend so check for rendering issues in GTK
  softwares using GL, including flutter applications

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


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

[Touch-packages] [Bug 1961049] Re: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[MarioGonzalez]

It seems it *was* during some automatic apt update

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

Title:
  package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  It wasn't during any upgrade or installation. The "System program
  problem detected" just popped in. I just had the browser opened with a
  few tabs.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.7
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Feb 11 11:24:29 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-12-19 (1519 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-07-13 (582 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1961049/+subscriptions


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

[Touch-packages] [Bug 1961049] [NEW] package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[MarioGonzalez]

Public bug reported:

It wasn't during any upgrade or installation. The "System program
problem detected" just popped in. I just had the browser opened with a
few tabs.

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.7
ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
Uname: Linux 5.4.0-91-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Fri Feb 11 11:24:29 2022
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2017-12-19 (1519 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: Upgraded to focal on 2020-07-13 (582 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  It wasn't during any upgrade or installation. The "System program
  problem detected" just popped in. I just had the browser opened with a
  few tabs.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.7
  ProcVersionSignature: Ubuntu 5.4.0-91.102-generic 5.4.151
  Uname: Linux 5.4.0-91-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Feb 11 11:24:29 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-12-19 (1519 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2020-07-13 (582 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1961049/+subscriptions


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

[Touch-packages] [Bug 1960083] Re: dirname applet missing from initramfs

[geole0]

Hello
Oh!!!
jammy-desktop-amd64.iso 2022-02-16 08:353.1GDesktop image 
for 64-bit PC (AMD64) computers (standard download)

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

Title:
  dirname applet missing from initramfs

Status in busybox package in Ubuntu:
  Fix Released
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  The initramfs is currently being built without the dirname applet.
  This is causing issues with zfs encrypted devices, as cryptsetup is
  attempting to use dirname to determine the location of the system key.
  This results in the following error:

  /init: line 971: dirname: not found

  followed by a prompt that is missing the zpool name. For example

  "Please unlock disk keystore-" rather than "Please unlock disk
  keystore-rpool".

  After entering the password, the user is dropped to an initramfs
  shell.

  It appears that this was caused by a change in cryptsetup to suddenly
  need dirname to function properly.

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


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

[Touch-packages] [Bug 1958019]

[hyc]

(In reply to Lucas Tanure from comment #539)
> Hi, 
> 
> We are waiting for this patch series to be merged:
> 
> https://lkml.org/lkml/2022/1/21/471
> 
> Thanks
> Lucas

Hi, just wanted to confirm, adding these patches on top of 5.17-rc4
works for me on my 2021 Legion 7 (AMD). This is running Ubuntu 21.04. I
grabbed the kernel source from the Ubuntu tree, as linked here

https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.17-rc4/

And built following the instructions here

https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel

In the editconfigs step you have to navigate in menuconfig to Device Drivers /
X86 Platform Specific Device Drivers /
I2C and SPI multi instantiate pseudo device driver

and select that module. Then Exit/Save the config and build. It takes a
few minutes to build, but the process goes smoothly.

Thanks for getting this working!

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

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

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

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

  uname -r
  5.11.0-44-generic

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

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


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