[Touch-packages] [Bug 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

Title:
  Clicking a calendar date in the bottom row of the panel calendar
  causes a graphical glitch

Status in GNOME Shell:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  If you click a calendar date in the bottom row of the top panel
  calendar, the backdrop shrinks and the dates overflow out of the
  backdrop boundaries.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 28 16:25:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD 
Graphics] [1462:129c]
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 
1650 Mobile / Max-Q] [1462:129c]
  InstallationDate: Installed on 2022-04-22 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  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 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1970800/+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 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Daniel Black]

Could it be  -flto/-ffat-lto-objects related (like
https://jira.mariadb.org/browse/MDEV-25633)? The top part of the stack
trace looks the same.

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

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

Status in mariadb-10.6 package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
   ahasenack: IIRC, originally Launchpad was FTBFSing on mariadb that 
included io_uring support because upstream were doing a build time test for 
io_uring (and I think still are), which is wrong because it should be done at 
runtime since the lack of io_uring availablity at build time doesn't tell us 
about its availablity at runtime.
   But then the Launchpad builders got updated to a newer release and 
therefore a newer kernel that supported it.
   AIUI, that's how we ended up with a successful build in the Jammy 
release pocket (of 10.6).
   I think the lp builders are using the focal hwe kernel
   5.4.0-something
   let me check that build log
   But then something changed that caused this current FTBFS, and I 
haven't tracked down what that is.
   hm, both are 10.6.7
   release and proposed
   What puzzles me is that if the root cause is a memlock rlimit issue 
then why did it work before?
   So since there's a contradiction somewhere, maybe one or more of my 
"facts" above is wrong.
   this is the current failure
   2022-04-14  8:11:49 0 [Warning] mariadbd: io_uring_queue_init() 
failed with ENOMEM: try larger memory locked limit, ulimit -l, or 
https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd 
(262144 bytes required)
   and ulimit -l confirms that the limit is lower
   Max locked memory 6553665536  
  bytes 
   just 64kbytes
   Yeah but then how did the release pocket build work?
   either the limit was different back then
   or ... stuff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+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 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Daniel Black]

On the assembly generated by create_linux_aio (in the mariadbd packages
in Ubuntu-22.04, 10.6.7-2:

(gdb) disassemble tpool::create_linux_aio,+200
Dump of assembler code from 0x5640cf2e1fb0 to 0x5640cf2e2078:
   0x5640cf2e1fb0 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+0>:  
endbr64 
   0x5640cf2e1fb4 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+4>:  
push   %rbp
   0x5640cf2e1fb5 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+5>:  
mov%rsp,%rbp
   0x5640cf2e1fb8 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+8>:  
push   %r14
   0x5640cf2e1fba <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+10>: 
mov%esi,%r14d
   0x5640cf2e1fbd <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+13>: 
push   %r13
   0x5640cf2e1fbf <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+15>: 
mov%rdi,%r13
   0x5640cf2e1fc2 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+18>: 
mov$0x158,%edi
   0x5640cf2e1fc7 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+23>: 
push   %r12
   0x5640cf2e1fc9 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+25>: 
sub$0x8,%rsp
   0x5640cf2e1fcd <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+29>: 
call   0x5640ceacb570 <_Znwm@plt>
   0x5640cf2e1fd2 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+34>: 
mov%r14d,%edx
   0x5640cf2e1fd5 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+37>: 
mov%r13,%rsi
   0x5640cf2e1fd8 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+40>: 
mov%rax,%rdi
   0x5640cf2e1fdb <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+43>: 
mov%rax,%r12
   0x5640cf2e1fde <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+46>: 
call   0x5640cf2e1dd0 <(anonymous 
namespace)::aio_uring::aio_uring(tpool::thread_pool*, int)>
   0x5640cf2e1fe3 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+51>: 
add$0x8,%rsp
   0x5640cf2e1fe7 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+55>: 
mov%r12,%rax
   0x5640cf2e1fea <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+58>: 
pop%r12
   0x5640cf2e1fec <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+60>: 
pop%r13
   0x5640cf2e1fee <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+62>: 
pop%r14
   0x5640cf2e1ff0 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+64>: 
pop%rbp
   0x5640cf2e1ff1 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+65>: 
ret
   0x5640cf2e1ff2 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+66>: 
endbr64 
   0x5640cf2e1ff6 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+70>: 
mov%rax,%rdi
   0x5640cf2e1ff9 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+73>: 
mov%rdx,%rax
   0x5640cf2e1ffc <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+76>: 
jmp0x5640ceb23308 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi-8121512>
   0x5640cf2e2001 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+81>: 
endbr64 
   0x5640cf2e2005 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+85>: 
mov%rax,%r13
   0x5640cf2e2008 <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+88>: 
mov%rdx,%r14
   0x5640cf2e200b <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi+91>: 
jmp0x5640ceb232fa <_ZN5tpool16create_linux_aioEPNS_11thread_poolEi.cold>
--Type  for more, q to quit, c to continue without paging--c
   0x5640cf2e2010 <_ZN5tpool19thread_pool_generic17create_native_aioEi+0>:  
endbr64 
   0x5640cf2e2014 <_ZN5tpool19thread_pool_generic17create_native_aioEi+4>:  
push   %rbp
   0x5640cf2e2015 <_ZN5tpool19thread_pool_generic17create_native_aioEi+5>:  
mov%rsp,%rbp
   0x5640cf2e2018 <_ZN5tpool19thread_pool_generic17create_native_aioEi+8>:  
push   %r14
   0x5640cf2e201a <_ZN5tpool19thread_pool_generic17create_native_aioEi+10>: 
mov%esi,%r14d
   0x5640cf2e201d <_ZN5tpool19thread_pool_generic17create_native_aioEi+13>: 
push   %r13
   0x5640cf2e201f <_ZN5tpool19thread_pool_generic17create_native_aioEi+15>: 
mov%rdi,%r13
   0x5640cf2e2022 <_ZN5tpool19thread_pool_generic17create_native_aioEi+18>: 
mov$0x158,%edi
   0x5640cf2e2027 <_ZN5tpool19thread_pool_generic17create_native_aioEi+23>: 
push   %r12
   0x5640cf2e2029 <_ZN5tpool19thread_pool_generic17create_native_aioEi+25>: 
sub$0x8,%rsp
   0x5640cf2e202d <_ZN5tpool19thread_pool_generic17create_native_aioEi+29>: 
call   0x5640ceacb570 <_Znwm@plt>
   0x5640cf2e2032 <_ZN5tpool19thread_pool_generic17create_native_aioEi+34>: 
mov%r14d,%edx
   0x5640cf2e2035 <_ZN5tpool19thread_pool_generic17create_native_aioEi+37>: 
mov%r13,%rsi
   0x5640cf2e2038 <_ZN5tpool19thread_pool_generic17create_native_aioEi+40>: 
mov%rax,%rdi
   0x5640cf2e203b <_ZN5tpool19thread_pool_generic17create_native_aioEi+43>: 
mov%rax,%r12
   0x5640cf2e203e 

[Touch-packages] [Bug 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot

[Brian Murray]

** Attachment added: "dist-upgrade-timing"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+attachment/5584814/+files/dist-upgrade-timing

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

Title:
  Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
  reboot

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Upgrading on a virtual machine from 20.04 to 22.04. I have had this
  happen twice now, I got one upgrade done without this bug.

  Basically the package installation stops at dbus package asking for a
  reboot as it was unable to upgrade as dbus-daemon was running. And
  rebooting at this stage obviously will cause a non-functioning system.

  Added a screenshot of the upgrade window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot

[Brian Murray]

I also did an upgrade from Focal to Jammy and recorded the upgrade
process using script and there was no long pause on dbus. I'll attach
both the timing file and recording.

One could watch the upgrade using `scriptreplay dist-upgrade-timing
dist-upgrade` and pass the `-d` argument if you don't want to watch it
in real time.

** Attachment added: "dist-upgrade"
   
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+attachment/5584813/+files/dist-upgrade

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

Title:
  Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
  reboot

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Upgrading on a virtual machine from 20.04 to 22.04. I have had this
  happen twice now, I got one upgrade done without this bug.

  Basically the package installation stops at dbus package asking for a
  reboot as it was unable to upgrade as dbus-daemon was running. And
  rebooting at this stage obviously will cause a non-functioning system.

  Added a screenshot of the upgrade window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Daniel Black]

Note the runtime detection in innodb_use_native_aio_default affects the
default value only. Users can explicity set this and really on distros
to provide patched kernels.

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

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

Status in mariadb-10.6 package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
   ahasenack: IIRC, originally Launchpad was FTBFSing on mariadb that 
included io_uring support because upstream were doing a build time test for 
io_uring (and I think still are), which is wrong because it should be done at 
runtime since the lack of io_uring availablity at build time doesn't tell us 
about its availablity at runtime.
   But then the Launchpad builders got updated to a newer release and 
therefore a newer kernel that supported it.
   AIUI, that's how we ended up with a successful build in the Jammy 
release pocket (of 10.6).
   I think the lp builders are using the focal hwe kernel
   5.4.0-something
   let me check that build log
   But then something changed that caused this current FTBFS, and I 
haven't tracked down what that is.
   hm, both are 10.6.7
   release and proposed
   What puzzles me is that if the root cause is a memlock rlimit issue 
then why did it work before?
   So since there's a contradiction somewhere, maybe one or more of my 
"facts" above is wrong.
   this is the current failure
   2022-04-14  8:11:49 0 [Warning] mariadbd: io_uring_queue_init() 
failed with ENOMEM: try larger memory locked limit, ulimit -l, or 
https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd 
(262144 bytes required)
   and ulimit -l confirms that the limit is lower
   Max locked memory 6553665536  
  bytes 
   just 64kbytes
   Yeah but then how did the release pocket build work?
   either the limit was different back then
   or ... stuff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+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 1970800] Re: Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Clicking a calendar date in the bottom row of the panel calendar
  causes a graphical glitch

Status in xorg package in Ubuntu:
  New

Bug description:
  If you click a calendar date in the bottom row of the top panel
  calendar, the backdrop shrinks and the dates overflow out of the
  backdrop boundaries.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 
11:24:05 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 28 16:25:17 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed
   virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD 
Graphics] [1462:129c]
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 
1650 Mobile / Max-Q] [1462:129c]
  InstallationDate: Installed on 2022-04-22 (6 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/18/2019
  dmi.bios.release: 1.8
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16S3IMS.108
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16S3
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1:
  dmi.product.family: Prestige
  dmi.product.name: Prestige 15 A10SC
  dmi.product.sku: 16S3.1
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  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 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1970800/+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 1970800] [NEW] Clicking a calendar date in the bottom row of the panel calendar causes a graphical glitch

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

If you click a calendar date in the bottom row of the top panel
calendar, the backdrop shrinks and the dates overflow out of the
backdrop boundaries.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..02.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.60.02  Wed Mar 16 11:24:05 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 28 16:25:17 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 virtualbox/6.1.32, 5.15.0-25-generic, x86_64: installed
 virtualbox/6.1.32, 5.15.0-27-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation CometLake-U GT2 [UHD Graphics] [8086:9b41] (rev 02) (prog-if 
00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] CometLake-U GT2 [UHD 
Graphics] [1462:129c]
   Subsystem: Micro-Star International Co., Ltd. [MSI] TU117M [GeForce GTX 1650 
Mobile / Max-Q] [1462:129c]
InstallationDate: Installed on 2022-04-22 (6 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Micro-Star International Co., Ltd. Prestige 15 A10SC
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/18/2019
dmi.bios.release: 1.8
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: E16S3IMS.108
dmi.board.asset.tag: Default string
dmi.board.name: MS-16S3
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: REV:1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16S3IMS.108:bd11/18/2019:br1.8:svnMicro-StarInternationalCo.,Ltd.:pnPrestige15A10SC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16S3:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:sku16S3.1:
dmi.product.family: Prestige
dmi.product.name: Prestige 15 A10SC
dmi.product.sku: 16S3.1
dmi.product.version: REV:1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
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 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu
-- 
Clicking a calendar date in the bottom row of the panel calendar causes a 
graphical glitch
https://bugs.launchpad.net/bugs/1970800
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

-- 
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 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Daniel Black]

Actually create_linux_aio (tpool/aio_liburing.cc:194) should already
catch this exception. So compiler error?

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

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

Status in mariadb-10.6 package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
   ahasenack: IIRC, originally Launchpad was FTBFSing on mariadb that 
included io_uring support because upstream were doing a build time test for 
io_uring (and I think still are), which is wrong because it should be done at 
runtime since the lack of io_uring availablity at build time doesn't tell us 
about its availablity at runtime.
   But then the Launchpad builders got updated to a newer release and 
therefore a newer kernel that supported it.
   AIUI, that's how we ended up with a successful build in the Jammy 
release pocket (of 10.6).
   I think the lp builders are using the focal hwe kernel
   5.4.0-something
   let me check that build log
   But then something changed that caused this current FTBFS, and I 
haven't tracked down what that is.
   hm, both are 10.6.7
   release and proposed
   What puzzles me is that if the root cause is a memlock rlimit issue 
then why did it work before?
   So since there's a contradiction somewhere, maybe one or more of my 
"facts" above is wrong.
   this is the current failure
   2022-04-14  8:11:49 0 [Warning] mariadbd: io_uring_queue_init() 
failed with ENOMEM: try larger memory locked limit, ulimit -l, or 
https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd 
(262144 bytes required)
   and ulimit -l confirms that the limit is lower
   Max locked memory 6553665536  
  bytes 
   just 64kbytes
   Yeah but then how did the release pocket build work?
   either the limit was different back then
   or ... stuff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+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 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Daniel Black]

Assertion cause:

$  podman run --rm --cap-add=CAP_SYS_PTRACE -e MARIADB_ROOT_PASSWORD=bob -ti 
--user mysql  m106_jammy_debug  bash
mysql@0740c1895ab4:/$ gdb --args  mariadbd --bootstrap
GNU gdb (Ubuntu 12.0.90-0ubuntu1) 12.0.90
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from mariadbd...
Reading symbols from 
/usr/lib/debug/.build-id/44/991764aba74dce2376ff38060a66adb6cfe4c0.debug...
(gdb) r
Starting program: /usr/sbin/mariadbd --bootstrap
warning: Error disabling address space randomization: Function not implemented
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
2022-04-28 22:59:13 0 [Note] /usr/sbin/mariadbd (server 
10.6.7-MariaDB-2ubuntu1) starting as process 14 ...
[New Thread 0x7f1b390b2640 (LWP 17)]
[New Thread 0x7f1b245c0640 (LWP 18)]
2022-04-28 22:59:13 0 [Note] InnoDB: The first data file './ibdata1' did not 
exist. A new tablespace will be created!
2022-04-28 22:59:13 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-04-28 22:59:13 0 [Note] InnoDB: Number of pools: 1
2022-04-28 22:59:13 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-04-28 22:59:13 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp 
(disabling future attempts)
2022-04-28 22:59:13 0 [Warning] mariadbd: io_uring_queue_init() failed with 
ENOSYS: try uprading the kernel

Thread 1 "mariadbd" received signal SIGABRT, Aborted.
__pthread_kill_implementation (no_tid=0, signo=6, threadid=139754903728000) at 
./nptl/pthread_kill.c:44
44  ./nptl/pthread_kill.c: No such file or directory.
(gdb) bt
#0  __pthread_kill_implementation (no_tid=0, signo=6, threadid=139754903728000) 
at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=6, threadid=139754903728000) at 
./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=139754903728000, signo=signo@entry=6) at 
./nptl/pthread_kill.c:89
#3  0x7f1b38a42476 in __GI_raise (sig=sig@entry=6) at 
../sysdeps/posix/raise.c:26
#4  0x7f1b38a287f3 in __GI_abort () at ./stdlib/abort.c:79
#5  0x5640ceb351dc in _Unwind_SetGR.cold ()
#6  0x5640cf4218af in __gcc_personality_v0 ()
#7  0x7f1b39743c64 in ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
#8  0x7f1b39744321 in _Unwind_RaiseException () from 
/lib/x86_64-linux-gnu/libgcc_s.so.1
#9  0x7f1b38eae54b in __cxa_throw () from 
/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x5640ceb232ed in (anonymous namespace)::aio_uring::aio_uring 
(this=, tpool=, max_aio=, 
this=, tpool=, 
max_aio=) at ../tpool/./tpool/aio_liburing.cc:63
#11 0x5640cf2e2043 in tpool::create_linux_aio (max_aio=2048, 
pool=0x5640d1625cf0) at ../tpool/./tpool/aio_liburing.cc:194
#12 tpool::thread_pool_generic::create_native_aio (this=0x5640d1625cf0, 
max_io=2048) at ../tpool/./tpool/tpool_generic.cc:285
#13 0x5640ceaea297 in tpool::thread_pool::configure_aio 
(this=0x5640d1625cf0, use_native_aio=, max_io=max_io@entry=2048) 
at ../storage/innobase/./tpool/tpool.h:215
#14 0x5640ceaf07d5 in os_aio_init () at 
../storage/innobase/./storage/innobase/os/os0file.cc:3759
#15 0x5640ceb037f8 in srv_start (create_new_db=) at 
../storage/innobase/./storage/innobase/srv/srv0start.cc:1180
#16 0x5640cf1815b9 in innodb_init (p=) at 
../storage/innobase/./storage/innobase/handler/ha_innodb.cc:4275
#17 0x5640ceef25f2 in ha_initialize_handlerton (plugin=0x5640d14d8b00) at 
./sql/handler.cc:659
#18 0x5640cecb5c7f in plugin_initialize (tmp_root=0x7ffdb8bea250, 
plugin=0x5640d14d8b00, argc=0x5640cfbe92e0 , 
argv=0x5640d14a1860, options_only=)
at ./sql/sql_plugin.cc:1463
#19 0x5640cecb9a84 in plugin_init (argc=, argv=, flags=1) at ./sql/sql_plugin.cc:1756
#20 0x5640ceb8cf5b in init_server_components () at ./sql/mysqld.cc:5046
#21 0x5640ceb921fa in mysqld_main (argc=, argv=) at ./sql/mysqld.cc:5661
#22 0x7f1b38a29d90 in __libc_start_call_main 
(main=main@entry=0x5640ceb35240 , argc=argc@entry=2, 
argv=argv@entry=0x7ffdb8becb68)
at ../sysdeps/nptl/libc_start_call_main.h:58
#23 0x7f1b38a29e40 in __libc_start_main_impl (main=0x5640ceb35240 
, argc=2, argv=0x7ffdb8becb68, init=, 
fini=, 
rtld_fini=, stack_end=0x7ffdb8becb58) at 
../csu/libc-start.c:392
#24 0x5640ceb7cbe5 in _start ()


So it looks like an uncaught exception.

Testing with:

diff --git 

[Touch-packages] [Bug 1940141] Autopkgtest regression report (openssl/1.1.1-1ubuntu2.1~18.04.16)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted openssl (1.1.1-1ubuntu2.1~18.04.16) for 
bionic have finished running.
The following regressions have been reported in tests triggered by the package:

openvswitch/2.9.8-0ubuntu0.18.04.2 (amd64, i386)
dovecot/1:2.2.33.2-1ubuntu4.7 (armhf)


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

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#openssl

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

Thank you!

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

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

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

Bug description:
  [Impact]

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

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

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

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

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

  [Test Plan]

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

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

  And running `s_client` like this:

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

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

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

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

  [Where problems could occur]

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

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


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

[Touch-packages] [Bug 1970731] Re: iptables empty when using firewalld

[Jamie Strandboge]

Reassigning to firewalld as the description mentions that ufw is
disabled.

This is not a bug though because iptables relies on certain
tables/chains being used and it looks like firewalld doesn't use those
(which is fine for firewalld to do). You should be able to see all
netfilter firewall rules with 'nft' but you'll only see rules that are
added to the (now non-default) tables/chains that iptables expects
(INPUT, OUTPUT, etc). More specifically, 'nft' will see the rules that
'iptables' creates but not necessarily the other way around.

** Package changed: ufw (Ubuntu) => firewalld (Ubuntu)

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

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

Title:
  iptables empty when using firewalld

Status in firewalld package in Ubuntu:
  Invalid

Bug description:
  Summary:
  I am using firewalld/jammy,now 1.1.1-1ubuntu1 on my vpn server. The vpn 
server is using wireguard and I could successfully configure zones and policies 
in firewalld. Yet, iptables does not show the rules from firewalld.

  1) System
  root@vpn:~# uname -a
  Linux vpn 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux
  root@vpn:~# lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  All updates installed.

  
  2) What happens:

  I am setting rules with firewall-cmd.

  These firewall rules are visible with:
 nft list table inet firewalld
  but not with 'iptables'.

  3) What I expect to happen:

  The toutput of
iptables --list
  should also reflect firewalld settings.

  4) What happened instead

  However, the iptables output shows only empty tables (filter, mangle,
  nat).

  root@vpn:~# iptables -t nat --list
  # Warning: iptables-legacy tables present, use iptables-legacy to see them
  Chain PREROUTING (policy ACCEPT)
  target prot opt source   destination 

  Chain INPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain OUTPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain POSTROUTING (policy ACCEPT)
  target prot opt source   destination 
  root@vpn:~# iptables -t filter --list
  # Warning: iptables-legacy tables present, use iptables-legacy to see them
  Chain INPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain FORWARD (policy ACCEPT)
  target prot opt source   destination 

  Chain OUTPUT (policy ACCEPT)
  target prot opt source   destination 
  root@vpn:~# iptables-legacy -t nat --list
  Chain PREROUTING (policy ACCEPT)
  target prot opt source   destination 

  Chain INPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain OUTPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain POSTROUTING (policy ACCEPT)
  target prot opt source   destination 
  root@vpn:~# iptables-legacy -t filter --list
  Chain INPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain FORWARD (policy ACCEPT)
  target prot opt source   destination 

  Chain OUTPUT (policy ACCEPT)
  target prot opt source   destination 

  
  5) Further information

  The ufw firewall is disabled and uninstalled.

  According to the release notes of 22.04, the backend has changed to nftables. 
  I was assuming, that the backend default is kind of transparent to the user, 
meaning iptables should still work as normal. 

  I wonder if on my system is iptables correctly linked to the backend.

  Iptables points to xtables-nft-multi:
  root@vpn:~# ls -l /usr/sbin/iptables
  lrwxrwxrwx 1 root root 26 Aug 24  2021 /usr/sbin/iptables -> 
/etc/alternatives/iptables
  root@vpn:~# ls -l /etc/alternatives/iptables
  lrwxrwxrwx 1 root root 22 Apr 25 18:56 /etc/alternatives/iptables -> 
/usr/sbin/iptables-nft
  root@vpn:~# ls -l /usr/sbin/iptables-nft
  lrwxrwxrwx 1 root root 17 Mar 24 12:58 /usr/sbin/iptables-nft -> 
xtables-nft-multi
  root@vpn:~# ls -l /usr/sbin/xtables-nft-multi
  -rwxr-xr-x 1 root root 224296 Mar 24 12:58 /usr/sbin/xtables-nft-multi

  
  Perhaps this is an issue with the upgrade process of ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firewalld/+bug/1970731/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Vitor Martins]

I tried also #22 + #36 + reboot, still having "0A0C0103:SSL
routines::internal error"

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Ekinoks]

Thanks for the suggestion Simon, but unfortunately, #22 + #36 + reboot
didn't work for me (I'm trying to connect to eduroam's WIFI).

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Daniel Black]

>From 5.12 kernel memory locked pages aren't needed -
https://github.com/axboe/liburing/issues/246#issuecomment-816965961.

In #1969160 I tested the upcoming 10.6 release (probably next week
sometime) for crashes in uring initialization failures and it didn't.
Apart from some error log differences from ENOMEM, ENOSYS etc are
handles the same way in the fallback.

I haven't quite concluded how the 10.6.7 release is crashing at the
moment.

With https://bugs.launchpad.net/ubuntu/+source/linux-
hwe-5.13/+bug/195 I assume the jammy kernel 5.15.0 has the right
patches to make 5.15.0 safe despite the MariaDB code not distinguishing
it as so (suggestions of improving kernel version detection welcome).

** Bug watch added: github.com/axboe/liburing/issues #246
   https://github.com/axboe/liburing/issues/246

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

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

Status in mariadb-10.6 package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
   ahasenack: IIRC, originally Launchpad was FTBFSing on mariadb that 
included io_uring support because upstream were doing a build time test for 
io_uring (and I think still are), which is wrong because it should be done at 
runtime since the lack of io_uring availablity at build time doesn't tell us 
about its availablity at runtime.
   But then the Launchpad builders got updated to a newer release and 
therefore a newer kernel that supported it.
   AIUI, that's how we ended up with a successful build in the Jammy 
release pocket (of 10.6).
   I think the lp builders are using the focal hwe kernel
   5.4.0-something
   let me check that build log
   But then something changed that caused this current FTBFS, and I 
haven't tracked down what that is.
   hm, both are 10.6.7
   release and proposed
   What puzzles me is that if the root cause is a memlock rlimit issue 
then why did it work before?
   So since there's a contradiction somewhere, maybe one or more of my 
"facts" above is wrong.
   this is the current failure
   2022-04-14  8:11:49 0 [Warning] mariadbd: io_uring_queue_init() 
failed with ENOMEM: try larger memory locked limit, ulimit -l, or 
https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd 
(262144 bytes required)
   and ulimit -l confirms that the limit is lower
   Max locked memory 6553665536  
  bytes 
   just 64kbytes
   Yeah but then how did the release pocket build work?
   either the limit was different back then
   or ... stuff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+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 1689381] Re: FTBFS cp: cannot stat 'doc/fontconfig-user.html'

[themusicgod1]

** Tags added: jammy

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

Title:
  FTBFS cp: cannot stat 'doc/fontconfig-user.html'

Status in fontconfig package in Ubuntu:
  New

Bug description:
  while attempting to build with debuild:

  debuild -us -uc -b
  ...
  Adding cdbs dependencies to debian/libfontconfig1-dbg.substvars
  dh_installdirs -plibfontconfig1-dbg \

  dh_installdocs -pfontconfig ./README ./NEWS ./AUTHORS
  cp: cannot stat 'doc/fontconfig-user.html': No such file or directory
  dh_installdocs: cp --reflink=auto -a doc/fontconfig-user.html 
debian/fontconfig/usr/share/doc/fontconfig returned exit code 1
  /usr/share/cdbs/1/rules/debhelper.mk:235: recipe for target 
'binary-install/fontconfig' failed
  make: *** [binary-install/fontconfig] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
2
  debuild: fatal error at line 1116:
  dpkg-buildpackage -rfakeroot -us -uc -b failed
  z@aisha:~/fontconfig/fontconfig-2.11.94/debian$ 

  ubuntu: 17.10 artful
  libfontconfig1-dev:  2.11.94-0ubuntu2

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libfontconfig1-dev (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Mon May  8 19:23:10 2017
  InstallationDate: Installed on 2016-05-07 (366 days ago)
  InstallationMedia:
   
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: fontconfig
  UpgradeStatus: Upgraded to artful on 2017-05-08 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1689381/+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 1269840] Re: ubuntu-bug ubuntu-bug doesn't work

[themusicgod1]

** Tags added: jammy

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

Title:
  ubuntu-bug ubuntu-bug doesn't work

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  ubuntu-bug doesn't make program lookup when package lookup failed.
  This is inconvenient for users, who don't know about `which` command.
  Is it possible to automate lookup and continue search until something
  matches?

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport 2.12.5-0ubuntu2.2
  ProcVersionSignature: Ubuntu 3.11.0-15.23-generic 3.11.10
  Uname: Linux 3.11.0-15-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.12.5-0ubuntu2.2
  Architecture: i386
  CrashReports:
   640:1000:122:1423125:2014-01-09 20:22:25.104739665 +0300:2014-01-09 
20:22:26.104739665 
+0300:/var/crash/_usr_lib_i386-linux-gnu_bamf_bamfdaemon.1000.crash
   640:1000:122:157297300:2014-01-09 20:56:44.036795854 +0300:2014-01-09 
20:56:45.036795854 +0300:/var/crash/_usr_bin_compiz.1000.crash
   640:0:122:4884804:2014-01-10 13:10:06.891414880 +0300:2014-01-10 
13:10:07.891414880 +0300:/var/crash/_usr_bin_Xorg.0.crash
  Date: Thu Jan 16 18:10:59 2014
  InstallationDate: Installed on 2012-03-12 (675 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to saucy on 2013-10-21 (87 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1269840/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Alex Reinking]

I'm happy to say that the approach outlined in #22 worked for me. I used
the CipherString option in #36, too, but didn't try without. Glad I
found this thread.

The network in question is UC Berkeley's eduroam.

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1970806] [NEW] package rsyslog 8.2102.0-2ubuntu2 failed to install/upgrade: o subprocesso instalado, do pacote rsyslog, o script post-installation retornou erro do status de saíd

[Aurelio Mesquita Galvão]

Public bug reported:

No more comments.

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: rsyslog 8.2102.0-2ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
Uname: Linux 5.4.0-77-generic x86_64
ApportVersion: 2.20.11-0ubuntu71.1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Thu Apr 28 18:35:37 2022
ErrorMessage: o subprocesso instalado, do pacote rsyslog, o script 
post-installation retornou erro do status de saída 128
InstallationDate: Installed on 2020-08-13 (622 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 3.9.4-1build1
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2.1
 apt  2.0.6
SourcePackage: rsyslog
Title: package rsyslog 8.2102.0-2ubuntu2 failed to install/upgrade: o 
subprocesso instalado, do pacote rsyslog, o script post-installation retornou 
erro do status de saída 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package impish

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

Title:
  package rsyslog 8.2102.0-2ubuntu2 failed to install/upgrade: o
  subprocesso instalado, do pacote rsyslog, o script post-installation
  retornou erro do status de saída 128

Status in rsyslog package in Ubuntu:
  New

Bug description:
  No more comments.

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: rsyslog 8.2102.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-77.86-generic 5.4.119
  Uname: Linux 5.4.0-77-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Apr 28 18:35:37 2022
  ErrorMessage: o subprocesso instalado, do pacote rsyslog, o script 
post-installation retornou erro do status de saída 128
  InstallationDate: Installed on 2020-08-13 (622 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2.1
   apt  2.0.6
  SourcePackage: rsyslog
  Title: package rsyslog 8.2102.0-2ubuntu2 failed to install/upgrade: o 
subprocesso instalado, do pacote rsyslog, o script post-installation retornou 
erro do status de saída 128
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

[Bruce Elrick]

I should add, the results in comment 22 indicate that the fix is active
and working.

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

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

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

Bug description:
  [Impact]

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

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

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

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

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

  [Test Plan]

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

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

  And running `s_client` like this:

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

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

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

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

  [Where problems could occur]

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

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


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

[Touch-packages] [Bug 1968876] Re: ssh-agent: Error connecting to agent: Connection refused

[David Michael Pick]

I have been having the same problem without the involvement of git.

Raspberry Pi 4, 4GB, upgraded to Ubuntu 22.04 from 21.10. Same commands 
worked with 21.10 that fail with 22.04.

Boot machine. Login, and this starts an agent, but I'm not sure if it's 
actually ssh-agent or if it's the Gnome version. Open terminal window. 
add keys to the agent using ssh-add. Open another terminal window and 
try to use slogin to another machine. Get the eerror message.

The very first time it happened a popup appeared about the ssh-agent 
crashing and asking if I wanted to send a diagnostic dump to Ububtu. I 
dis. Didn't get asked this subsequent times.

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

Title:
  ssh-agent: Error connecting to agent: Connection refused

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: openssh 1:8.9p1-3
  Architecture: arm64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE

  raspberry pi 4. The keys are added, but for example, when cloning a
  repository via ssh, the ssh agent crashes, restarting does not help,
  the repository is not cloned. When launch the command ssh-add -L Error
  connecting to agent: Connection refused. I rolled back to the package
  version 1: 8.8p1-1 and everything works fine.

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


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

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

[Bruce Elrick]

I pulled the proposed source:

  $ pull-lp-source openssl bionic

built with tracing enabled:

  $ cd openssl-1.1.1
  $ sed -i -e '/^CONFARGS  =/a CONFARGS += enable-ssl-trace' debian/rules
  $ debuild -us -uc -b 2>&1 | tee ../debuild.log
  $ cd ..

installed:
  $ sudo dpkg -i libssl1.1_1.1.1-1ubuntu2.1~18.04.16_amd64.deb 
openssl_1.1.1-1ubuntu2.1~18.04.16_amd64.deb

tested:

  $ openssl req -x509 -sha256 -nodes -days 365 -newkey rsa:2048 -keyout key.pem 
-out cert.pem
  $ openssl s_server -key key.pem -cert cert.pem -status_file 
openssl-1.1.1/test/recipes/ocsp-response.der -Verify 5 2>&1 | tee s_server.log &
  $ openssl s_client -status -trace -cert cert.pem -key key.pem 2>&1 | tee 
s_client.log (^c)
  $ grep -B1 -A4 CertificateRequest s_client.log
Inner Content Type = Handshake (22)
  CertificateRequest, Length=45
request_context (len=0): 
extensions, length = 42
  extension_type=signature_algorithms(13), length=38
ecdsa_secp256r1_sha256 (0x0403)
  $ tail -6 s_server.log 
  ---
  No server certificate CA names sent
  CIPHER is TLS_AES_256_GCM_SHA384
  Secure Renegotiation IS supported
  
  ERROR

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

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

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

Bug description:
  [Impact]

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

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

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

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

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

  [Test Plan]

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

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

  And running `s_client` like this:

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

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

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

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

  [Where problems could occur]

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

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


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

[Touch-packages] [Bug 1959345] Re: vulkaninfo reports error

[Gary Taverner]

I don't see amdgpu-pro when I do this:

→ apt list --installed |grep amdgpu

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

libdrm-amdgpu1/bionic-updates,now 2.4.101-2~18.04.1 amd64 [installed]
xserver-xorg-video-amdgpu-hwe-18.04/bionic-updates,now 19.1.0-1~18.04.1 amd64 
[installed,automatic]

lspci -v shows no amdgpu-pro

Curious, how can you tell I have amdgpu-pro installed?  There is no
mention of it in the reports above.  Maybe the problem is a mixed up
installation?

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1966849] Re: gzip exec format error under WSL1

[Robert Giles]

Chiming in that it'd be great if this (gzip-1.10-4ubuntu4) continued to
work in WSL1.

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

Title:
  gzip exec format error under WSL1

Status in gzip:
  New
Status in gzip package in Ubuntu:
  Confirmed

Bug description:
  gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows
  19044.1620, making WSL pretty much unusable.

  bash: /usr/bin/gzip: cannot execute binary file: Exec format error

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gzip 1.10-4ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35
  Uname: Linux 4.4.0-19041-Microsoft x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Mar 29 06:40:33 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gzip
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gzip/+bug/1966849/+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 1840375] [shadow/xenial] verification still needed

[Brian Murray]

The fix for this bug has been awaiting testing feedback in the -proposed
repository for xenial for more than 90 days.  Please test this fix and
update the bug appropriately with the results.  In the event that the
fix for this bug is still not verified 15 days from now, the package
will be removed from the -proposed repository.

** Tags added: removal-candidate

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

Title:
  groupdel doesn't support extrausers

Status in snapd:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in shadow source package in Xenial:
  Fix Committed
Status in shadow source package in Bionic:
  Fix Released
Status in shadow source package in Disco:
  Won't Fix

Bug description:
  snapd needs the ability to call 'groupdel --extrausers foo' to clean
  up after itself, but --extrausers is currently unsupported.

  [Impact]
  On ubuntu-core systems we want to be able to manage "extrausers" in the same
  way as regular users. This requires updates to the various 
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.

  This is an important feature for Ubuntu Core

  [Test Case]
  0. upgrade the "passwd" to the version in {xenial,bionic}-proposed
  1. install the libnss-extrausers and add "extrauers" to the passwd and shadow 
line (see /usr/share/doc/libnss-extrausers/README for the modifications in 
sswitch.conf)
  2. run "groupadd --extrausers foo" and verify "grep foo 
/var/lib/extrausers/group"
  3  check /var/lib/extrausers/group for the new "foo" group
  4. run "groupdel --extrausers foo"
  5. check /var/lib/extrausers/group and ensure the "foo" group is removed

  [Regression Potential]

   * low: this adds a new (optional) option which is off by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+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 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

[Andreas Hasenack]

Since mariadb on the current jammy kernel disables io_uring at startup,
I'm considering disabling io_uring entirely in the jammy mariadb build.
The only scenario where io_uring would be used by the jammy mariadb is
if the user ran a different kernel than the one shipped with jammy.

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

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

Status in mariadb-10.6 package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
   ahasenack: IIRC, originally Launchpad was FTBFSing on mariadb that 
included io_uring support because upstream were doing a build time test for 
io_uring (and I think still are), which is wrong because it should be done at 
runtime since the lack of io_uring availablity at build time doesn't tell us 
about its availablity at runtime.
   But then the Launchpad builders got updated to a newer release and 
therefore a newer kernel that supported it.
   AIUI, that's how we ended up with a successful build in the Jammy 
release pocket (of 10.6).
   I think the lp builders are using the focal hwe kernel
   5.4.0-something
   let me check that build log
   But then something changed that caused this current FTBFS, and I 
haven't tracked down what that is.
   hm, both are 10.6.7
   release and proposed
   What puzzles me is that if the root cause is a memlock rlimit issue 
then why did it work before?
   So since there's a contradiction somewhere, maybe one or more of my 
"facts" above is wrong.
   this is the current failure
   2022-04-14  8:11:49 0 [Warning] mariadbd: io_uring_queue_init() 
failed with ENOMEM: try larger memory locked limit, ulimit -l, or 
https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd 
(262144 bytes required)
   and ulimit -l confirms that the limit is lower
   Max locked memory 6553665536  
  bytes 
   just 64kbytes
   Yeah but then how did the release pocket build work?
   either the limit was different back then
   or ... stuff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+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 1970634] Re: FTBFS: test failure due to low memlock limit

[Andreas Hasenack]

I added a task for systemd to consider raising the default
RLIMIT_MEMLOCK limit.

This upstream commit raises the default limit to 8Mb:

https://github.com/systemd/systemd/commit/852b62507b2

The way things are now, the following scenario does NOT work out of the
box:

- jammy lxd on focal host
- apt install mariadb-server

mariadb will crash and core dump because of the low MEMLOCK limit. Its
systemd service file even has this line to raise the limit:

LimitMEMLOCK=524288

But that does not have any effect from inside the unprivileged lxd
container.

Jammy lxd on jammy host will work just because the jammy kernel (5.15.0)
is deemed unsafe[1] for uring by mariadb, and then uring is disabled
during startup.


1. 
https://github.com/MariaDB/server/blob/10.6/storage/innobase/handler/ha_innodb.cc#L19480

** Summary changed:

- FTBFS: test failure due to low memlock limit
+ FTBFS: mariadb fails to start due to low MEMLOCK limit

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

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

Status in mariadb-10.6 package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
   ahasenack: IIRC, originally Launchpad was FTBFSing on mariadb that 
included io_uring support because upstream were doing a build time test for 
io_uring (and I think still are), which is wrong because it should be done at 
runtime since the lack of io_uring availablity at build time doesn't tell us 
about its availablity at runtime.
   But then the Launchpad builders got updated to a newer release and 
therefore a newer kernel that supported it.
   AIUI, that's how we ended up with a successful build in the Jammy 
release pocket (of 10.6).
   I think the lp builders are using the focal hwe kernel
   5.4.0-something
   let me check that build log
   But then something changed that caused this current FTBFS, and I 
haven't tracked down what that is.
   hm, both are 10.6.7
   release and proposed
   What puzzles me is that if the root cause is a memlock rlimit issue 
then why did it work before?
   So since there's a contradiction somewhere, maybe one or more of my 
"facts" above is wrong.
   this is the current failure
   2022-04-14  8:11:49 0 [Warning] mariadbd: io_uring_queue_init() 
failed with ENOMEM: try larger memory locked limit, ulimit -l, or 
https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd 
(262144 bytes required)
   and ulimit -l confirms that the limit is lower
   Max locked memory 6553665536  
  bytes 
   just 64kbytes
   Yeah but then how did the release pocket build work?
   either the limit was different back then
   or ... stuff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+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 1970634] Re: FTBFS: test failure due to low memlock limit

[Andreas Hasenack]

** Also 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/1970634

Title:
  FTBFS: test failure due to low memlock limit

Status in mariadb-10.6 package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
   ahasenack: IIRC, originally Launchpad was FTBFSing on mariadb that 
included io_uring support because upstream were doing a build time test for 
io_uring (and I think still are), which is wrong because it should be done at 
runtime since the lack of io_uring availablity at build time doesn't tell us 
about its availablity at runtime.
   But then the Launchpad builders got updated to a newer release and 
therefore a newer kernel that supported it.
   AIUI, that's how we ended up with a successful build in the Jammy 
release pocket (of 10.6).
   I think the lp builders are using the focal hwe kernel
   5.4.0-something
   let me check that build log
   But then something changed that caused this current FTBFS, and I 
haven't tracked down what that is.
   hm, both are 10.6.7
   release and proposed
   What puzzles me is that if the root cause is a memlock rlimit issue 
then why did it work before?
   So since there's a contradiction somewhere, maybe one or more of my 
"facts" above is wrong.
   this is the current failure
   2022-04-14  8:11:49 0 [Warning] mariadbd: io_uring_queue_init() 
failed with ENOMEM: try larger memory locked limit, ulimit -l, or 
https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd 
(262144 bytes required)
   and ulimit -l confirms that the limit is lower
   Max locked memory 6553665536  
  bytes 
   just 64kbytes
   Yeah but then how did the release pocket build work?
   either the limit was different back then
   or ... stuff

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mariadb-10.6/+bug/1970634/+subscriptions


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

[Touch-packages] [Bug 1940528] Re: curl 7.68 does not init OpenSSL correctly

[Launchpad Bug Tracker]

This bug was fixed in the package curl - 7.68.0-1ubuntu2.10

---
curl (7.68.0-1ubuntu2.10) focal-security; urgency=medium

  * SECURITY UPDATE: OAUTH2 bypass
- debian/patches/CVE-2022-22576.patch: check sasl additional
  parameters for conn resuse in lib/strcase.c, lib/strcase.h,
  lib/url.c, lib/urldata.h, lib/vtls/vtls.c.
- CVE-2022-22576
  * SECURITY UPDATE: Credential leak on redirect
- debian/patches/CVE-2022-27774-1.patch: store conn_remote_port
  in the info struct to make it available after the connection ended
  in lib/connect.c, lib/urldata.h.
- debian/patches/CVE-2022-27774-2.patch: redirects to other protocols
  or ports clear auth in lib/transfer.c.
- debian/patches/CVE-2022-27774-3*.patch: adds tests to verify
  these fix in tests/data/Makefile.inc, tests/data/test973,
  tests/data/test974, tests/data/test975, tests/data/test976.
- CVE-2022-27774
  * SECURITY UPDATE: Bad local IPV6 connection reuse
- debian/patches/CVE-2022-27775.patch: include the zone id in the
  'bundle' haskey in lib/conncache.c.
- CVE-2022-27775
  * SECURITY UPDATE: Auth/cookie leak on redirect
- debian/patches/CVE-2022-27776.patch: avoid auth/cookie on redirects
  same host diff port in lib/http.c, lib/urldata.h.
- CVE-2022-27776

 -- Leonidas Da Silva Barbosa   Mon, 25 Apr
2022 10:02:10 -0300

** Changed in: curl (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

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

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

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

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

Title:
  curl 7.68 does not init OpenSSL correctly

Status in curl package in Ubuntu:
  Fix Released
Status in curl source package in Bionic:
  New
Status in curl source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * curl 7.68 does not correctly use OpenSSL 1.1.0+ api to init OpenSSL
  global state prior to executing any OpenSSL APIs. This may lead to
  duplicate engine initiation, which upon engine unload may cause use-
  after-free or double-free of any methods that engine installs. This
  has been fixed in curl 7.74 by correctly calling OpenSSL init api
  prior to any other calls to OpenSSL apis.

  [Test Plan]

   * This should be reproducible with any engines that allocate &
  register methods, and free them upon engine unload. Then use curl with
  openssl backend to test for corrupted stack.

   * I.e. on arm64, compile and configure pka engine from
  
https://github.com/Mellanox/pka/commit/b0f32fa05298bf9e3997ea43fc1c11b90e0d662f
  (i.e. without the double-free protections proposed in
  https://github.com/Mellanox/pka/pull/37 ) on any arm64 hardware, there
  is no need for the engine to actually work or have access to anything,
  as the issue is reproducible when engine is enabled but cannot be
  effectively used.

   * curl any https website

  ...
  PKA_DEV: pka_dev_open_ring_vfio: error: failed to get ring 50 device name
  PKA_ENGINE: PKA instance is invalid
  PKA_ENGINE: failed to retrieve valid instance
  100   338  100   3380 0   3520  0 --:--:-- --:--:-- --:--:--  3520
  (exit status 0)

  is good output from fixed curl.

  Whereas:

  PKA_ENGINE: PKA instance is invalid
  PKA_ENGINE: failed to retrieve valid instance
  100   338  100   3380 0   1169  0 --:--:-- --:--:-- --:--:--  1169
  Segmentation fault (core dumped)
  (exit status non-zero)

  is bad output from currently broken curl.

  [Where problems could occur]

   * Correctly calling OpenSSL init function prior to any other OpenSSL
  apis changes the behaviour of the library slightly - specifically
  openssl configuration file and engines are initialised and loaded
  earlier, meaning that site-local customizations are applied correctly
  whenever using curl cli utility or libcurl4 (the openssl version of
  curl). This will make engine support working correctly across the
  board. However, if one has missconfigured openssl conf and
  missconfigured engines which are now actually attempted to be used one
  may experience unexpected behaviour changes (since potentially
  existing configuration was not actually taking effect).

  [Other Info]
   
   * References:
  https://github.com/curl/curl/commit/1835cb916e0d40eb8bc1165d5627a0b64f911bac
  https://github.com/openssl/openssl/issues/13548
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1921518

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


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

[Touch-packages] [Bug 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot

[Brian Murray]

I tested an upgrade from Impish to Jammy today in a virtual machine and
from what I could tell (I didn't watch the whole process) the upgrade
did not stop when dbus was installed although the message posted in the
screenshots was display. Looking at my /var/log/dist-upgrade/main.log we
can see that the total upgrade took only 16 minutes so it's unlikely
that 10 of that was spent waiting.

2022-04-28 10:17:16,728 DEBUG quirks: running StartUpgrade
2022-04-28 10:17:16,728 DEBUG running Quirks.StartUpgrade
2022-04-28 10:17:16,728 DEBUG skipping 'README' (no '.')
2022-04-28 10:17:16,728 DEBUG killing update-notifier
2022-04-28 10:17:16,735 DEBUG killing kblueplugd kbluetooth4
2022-04-28 10:17:16,744 INFO cache.commit()
2022-04-28 10:31:57,413 DEBUG cache.commit() returned None
2022-04-28 10:31:57,542 DEBUG openCache()
2022-04-28 10:31:59,650 DEBUG Comparing 5.13.0-19 with
2022-04-28 10:31:59,650 DEBUG Comparing 5.13.0-30 with 5.13.0-19
2022-04-28 10:31:59,650 DEBUG Comparing 5.13.0-40 with 5.13.0-30
2022-04-28 10:31:59,650 DEBUG Comparing 5.15.0-27 with 5.13.0-40
2022-04-28 10:31:59,751 DEBUG /openCache(), new cache size 71806
2022-04-28 10:31:59,751 DEBUG quirks: running jammyPostUpgrade
2022-04-28 10:31:59,751 DEBUG running Quirks.jammyPostUpgrade

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

Title:
  Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
  reboot

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Upgrading on a virtual machine from 20.04 to 22.04. I have had this
  happen twice now, I got one upgrade done without this bug.

  Basically the package installation stops at dbus package asking for a
  reboot as it was unable to upgrade as dbus-daemon was running. And
  rebooting at this stage obviously will cause a non-functioning system.

  Added a screenshot of the upgrade window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1966849] Re: gzip exec format error under WSL1

[Joerg-k]

Just realized that my 22.04 installation was still running in WSL1... No
more error after switching to WSL2.

** Summary changed:

- gzip exec format error under WSL
+ gzip exec format error under WSL1

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

Title:
  gzip exec format error under WSL1

Status in gzip:
  New
Status in gzip package in Ubuntu:
  Confirmed

Bug description:
  gzip version 1.10-4ubuntu3 fails to run under WSL1 on Windows
  19044.1620, making WSL pretty much unusable.

  bash: /usr/bin/gzip: cannot execute binary file: Exec format error

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gzip 1.10-4ubuntu3
  ProcVersionSignature: Microsoft 4.4.0-19041.1237-Microsoft 4.4.35
  Uname: Linux 4.4.0-19041-Microsoft x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Tue Mar 29 06:40:33 2022
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/usr/bin/fish
  SourcePackage: gzip
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gzip/+bug/1966849/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Thomas]

Simon, I tried your suggestion followed by running sudo systemctl
restart wpa_supplicant.service and I still am unable to connect.

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1969960] Re: Jammy's /etc/os-release missing LTS string in VERSION

[Launchpad Bug Tracker]

This bug was fixed in the package base-files - 12ubuntu5

---
base-files (12ubuntu5) kinetic; urgency=medium

  * /etc/issue{,.net}, /etc/{lsb,os}-release: Welcome to Kinetic Kudu!

 -- Łukasz 'sil2100' Zemczak   Tue, 26 Apr
2022 17:47:05 +0200

** Changed in: base-files (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Jammy's /etc/os-release missing LTS string in VERSION

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Jammy:
  Fix Released

Bug description:
  [Description]

  In Jammy (base-files 12ubuntu4) we have:

  $ grep VERSION= /etc/os-release 
  VERSION="22.04 (Jammy Jellyfish)"

  but expected is:

  VERSION="22.04 LTS (Jammy Jellyfish)"

  Compare with Focal:

  $ grep VERSION= /etc/os-release 
  VERSION="20.04.4 LTS (Focal Fossa)"

  [Impact]

  Having VERSION without LTS is inconsistent with the previous LTS
  releases and is wrong, as the official name of the release is "22.04
  LTS". This can confuse users.

  Any script relying on VERSION to detect if the Ubuntu version it is
  running on in an LTS won't be work as expected.

  [Test Plan]

  1. grep VERSION= /etc/os-release 
  2. check that it is: VERSION="22.04 LTS (Jammy Jellyfish)"

  [Where problems could occur]

  Software already packaged in Jammy may already have adapted to the
  fact that VERSION doesn't have the LTS string in it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1969960/+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 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install

[Brian Murray]

There was a question about whether or not this error prevents non-
interactive vim from working, the answer is no.

ubuntu@ubuntu:~$ view /var/log/syslog
E1187: Failed to source defaults.vim
Press ENTER or type command to continue
ubuntu@ubuntu:/tmp$ cat junk.txt
abc
ubuntu@ubuntu:/tmp$ vi -c "%s/abc/ABC" -c ":xa" junk.txt
ubuntu@ubuntu:/tmp$ cat junk.txt
ABC

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

Title:
  vim.tiny reports 'E1187: Failed to source defaults.vim' on execution
  in default install

Status in vim package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04

  When running vim.tiny it says:

  $ vim.tiny
  E1187: Failed to source defaults.vim
  Press ENTER or type command to continue

  This is due to the defaults.vim file not being available.  If you just
  run it as vi

  $ vi

  this message does not appear as vim.tiny runs in compatibility mode.  I found 
mention of this issue in:
  https://github.com/grml/grml-etc-core/issues/99

  The defaults.vim file is provided by the package vim-runtime.

  I'm unsure what the issue is, if something needs to be in
  /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg
  claims vimrc is in vim-common, but no file is installed for me from
  that package, or if vim-runtime needs to be a required package for
  vim-tiny

  $ dpkg -S /etc/vim/vimrc
  vim-common: /etc/vim/vimrc
  $ ls -al /etc/vim/vimrc
  ls: cannot access '/etc/vim/vimrc': No such file or directory

  I discovered this because my .selected-editor was vim.tiny after
  running crontab -e

  $ crontab -e

  Select an editor.  To change later, run 'select-editor'.
    1. /bin/nano< easiest
    2. /usr/bin/vim.tiny
    3. /bin/ed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: vim-tiny 2:8.2.3995-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
  Uname: Linux 5.15.0-1005-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 13 11:56:35 2022
  ImageMediaBuild: 20201022
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+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 1962454] Re: Oops pages show wrong time window in JournalErrors

[Brian Murray]

** Tags added: fr-2321

** Tags removed: fr-2321 rls-jj-incoming
** Tags added: jammy

** Tags added: fr-2321

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

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

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

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

Title:
  Oops pages show wrong time window in JournalErrors

Status in Apport:
  New
Status in Errors:
  Invalid
Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Jammy:
  Triaged

Bug description:
  For example, I just experienced a crash at:

Feb 28 17:31:12

  And the JournalErrors entries are:

Feb 28 17:31:30 - Feb 28 17:31:41

  So don't relate to the crash.

  But it should be possible to tell journalctl to collect entries
  starting *before* the crash and cover the full crash timeframe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1962454/+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 1896772] Re: systemd-resolved configures no Current Scopes on start

[Brian Murray]

** Tags added: fr-2319

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

** Also affects: isc-dhcp (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

** Changed in: isc-dhcp (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: isc-dhcp (Ubuntu Jammy)
   Importance: Undecided => High

** Tags removed: rls-jj-incoming

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

Title:
  systemd-resolved configures no Current Scopes on start

Status in ifupdown package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed
Status in ifupdown source package in Jammy:
  Fix Released
Status in isc-dhcp source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

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

  # Steps to reproduce:

  1) `systemctl restart systemd-resolved.service`

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

  # Expected behaviour:

  DNS continues to work, status looks like this:

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

  # Actual behaviour:

  DNS is unconfigured:

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

  # Workaround

  Disconnecting and reconnecting my network connection restored DNS
  functionality.

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

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


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

[Touch-packages] [Bug 1959345] Re: vulkaninfo reports error

[Gary Taverner]

'if its vulkan driver does not install its icd file in the correct
place, there's nothing we can do about that'

Thank you for your help. I was not aware of that interaction, only of
what the installed package vulkan-mesa-drivers claimed as stated at the
beginning of this report.

'apt-cache show says that vulkan-mesa-drivers provides vulkan-icd'.

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959475] Re: "machinectl shell" connections immediately terminated

[Brian Murray]

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

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

** Tags removed: rls-ff-incoming rls-jj-incoming

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

Title:
  "machinectl shell" connections immediately terminated

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  New

Bug description:
  The command "machinectl shell" does not work in systemd
  249.9-0ubuntu2:

  $ sudo machinectl shell ns-xxx
  Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

  Connection to machine ns-xxx terminated.

  The issue seems to be described here:
  
https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
  https://github.com/systemd/systemd/issues/22234

  and solved here:

  
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Simon Chopin]

For those for whom the steps in #22 didn't work, does adding the
following line in /etc/wpa_supplicant/openssl.cnf right below the
"Options = UnsafeLegacyRenegotiation" line work?

CipherString = DEFAULT@SECLEVEL=1

(that's in addition of the other steps outlined in #22)

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04

[Michal Zubkowicz]

I've got 16GB of RAM. It's a pretty new laptop - LG Gram 17Z90p

Before my changes initrd had size 118MB, after changes: 27MB.
file command output was: ASCII cpio archive (SVR4 with no CRC)

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

Title:
  Initrd out of memory error after upgrade to 22.04

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 22.04 system is unbootable because of "out of memory" 
error when loading initial ramdisk. I was able to fix it by editing cat 
/etc/initramfs-tools/initramfs.conf
  and changing configuration to:
  MODULES=dep
  COMPRESS=xz
  RUNSIZE=15%

  Not sure which one helped, but I can test it if needed.

  System information:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  initramfs-tools:
Installed: 0.140ubuntu13
Candidate: 0.140ubuntu13
Version table:
   *** 0.140ubuntu13 500
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Patrick Aoude]

Fresh install of 22.04 and enterprise wifi at work is no longer working.
Steps in comment #22 did not work for me.

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1959475] Re: "machinectl shell" connections immediately terminated

[Matthieu Clemenceau]

** Tags added: fr-2315

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

Title:
  "machinectl shell" connections immediately terminated

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  New

Bug description:
  The command "machinectl shell" does not work in systemd
  249.9-0ubuntu2:

  $ sudo machinectl shell ns-xxx
  Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

  Connection to machine ns-xxx terminated.

  The issue seems to be described here:
  
https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
  https://github.com/systemd/systemd/issues/22234

  and solved here:

  
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1968845] Re: Upgrade to 22.04 from 20.04 ends with dbus installation asking for a reboot

[Brian Murray]

** Changed in: dbus (Ubuntu)
   Importance: Undecided => High

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

Title:
  Upgrade to 22.04 from 20.04 ends with dbus installation asking for a
  reboot

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  Upgrading on a virtual machine from 20.04 to 22.04. I have had this
  happen twice now, I got one upgrade done without this bug.

  Basically the package installation stops at dbus package asking for a
  reboot as it was unable to upgrade as dbus-daemon was running. And
  rebooting at this stage obviously will cause a non-functioning system.

  Added a screenshot of the upgrade window.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1968845/+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 1969375] Re: systemd-cryptenroll does not support TPM2 devices

[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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1969375

Title:
  systemd-cryptenroll does not support TPM2 devices

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  systemd-cryptenroll can make use of tpm2 modules to bind against
  secure boot pcrs and enable auto unlocking of luks devices.

  Following the instructions here:
  https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll

  the following commands fail on ubuntu jammy (5.15.0-25-generic)

  root@testbox:~# systemd-cryptenroll --tpm2-device=list
  TPM2 not supported on this build.
  root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3
   Please enter current passphrase for disk /dev/sda3: ***
  root@testbox:~# echo $?
  1

  It appears that this issue has been resolved in the debian build for
  systemd here:  https://salsa.debian.org/systemd-
  team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8

  Can we get the same modifications to the Jammy systemd build?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969375/+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 1959475] Re: "machinectl shell" connections immediately terminated

[Lukas Märdian]

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

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

Title:
  "machinectl shell" connections immediately terminated

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Focal:
  New

Bug description:
  The command "machinectl shell" does not work in systemd
  249.9-0ubuntu2:

  $ sudo machinectl shell ns-xxx
  Connected to machine ns-xxx. Press ^] three times within 1s to exit session.

  Connection to machine ns-xxx terminated.

  The issue seems to be described here:
  
https://forum.manjaro.org/t/the-machinectl-shell-command-stopped-working-after-systemd-upgrade-to-250-2-1/99899
  https://github.com/systemd/systemd/issues/22234

  and solved here:

  
https://github.com/systemd/systemd/commit/e8cf09b2a2ad0d48e5493050d54251d5f512d9b6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1959475/+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 1802483] Re: Notifications emitted by a snap with local files or desktop files use wrong namespace

[Jeremy Bicha]

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

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

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

Title:
  Notifications emitted by a snap with local files or desktop files use
  wrong namespace

Status in libnotify package in Ubuntu:
  In Progress
Status in libnotify source package in Focal:
  In Progress
Status in libnotify source package in Jammy:
  In Progress

Bug description:
  As can be tested using this example snap:
   - https://github.com/3v1n0/notify-send-test-snap

  Basically the icons are referenced using absolute paths in snap
  environment, while they should be readapted so that they depend on
  $SNAP location.

  As we do with appindicators and libunity emblems.

  

  [ Impact ]

  Icons sonuds and desktop files referenced by a snapped app using
  notifications aren't exposed to the desktop in absolute paths

  [ Test case ]

  Build the test snap (or install it from the attached files to this bug):
    git clone https://github.com/3v1n0/notify-send-test-snap
    snapcraft prime
    snap try prime

  To use the pre-built snap 
(https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7)
    snap install --dangerous notify-send-test-snap_*.snap

  Check that icons are shown when launching:
    notify-send-test-snap
    notify-send-test-snap.image-path
notify-send-test-snap.image-uri

  Ensure that desktop entry is correctly sent, monitoring the dbus
  session:

   In a terminal:
     dbus-monitor --session --monitor 
"interface='org.freedesktop.Notifications'"

   In the other:
     notify-send-test-snap.desktop-entry
     notify-send-test-snap.desktop-entry-explicit-id
     notify-send-test-snap.desktop-entry-explicit-file-name
     notify-send-test-snap.desktop-entry-explicit-path
     notify-send-test-snap.desktop-entry-explicit-uri
     notify-send-test-snap.desktop-entry-explicit-snapped-uri

  The
   `desktop-entry` value sent to dbus should be either:
     - A `notify-send-test-snap_`-prefixed desktop ID
     - A .desktop file path (readable from both inside and outside the snap)
     - A .desktop file uri (readable from both inside and outside the snap)

  [ Regression potential ]

  Normal applications that are run with a SNAP environment variable set,
  might use wrong paths for files or desktop file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+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 1896772] Re: systemd-resolved configures no Current Scopes on start

[Brian Murray]

** Changed in: isc-dhcp (Ubuntu)
   Importance: Undecided => High

** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

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

Title:
  systemd-resolved configures no Current Scopes on start

Status in ifupdown package in Ubuntu:
  Fix Released
Status in isc-dhcp package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Confirmed

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

  # Steps to reproduce:

  1) `systemctl restart systemd-resolved.service`

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

  # Expected behaviour:

  DNS continues to work, status looks like this:

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

  # Actual behaviour:

  DNS is unconfigured:

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

  # Workaround

  Disconnecting and reconnecting my network connection restored DNS
  functionality.

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

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


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

[Touch-packages] [Bug 1970647] Re: notify-send exit code doesn't match result

[Jeremy Bicha]

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

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

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

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

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

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

** Changed in: libnotify (Ubuntu Jammy)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: libnotify (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: libnotify (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  notify-send exit code doesn't match result

Status in libnotify package in Ubuntu:
  In Progress
Status in libnotify source package in Focal:
  In Progress
Status in libnotify source package in Jammy:
  In Progress

Bug description:
  No error exit code is returned by notify-send on failure

  [ Test case ]

  1. Run:
 jhbuild run env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error
  2. In a terminal "error" should be printed

  [ Regression potential ]

  Programs relying on notify-send may have errors when they did not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1970647/+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 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install

[Brian Murray]

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

** Tags removed: rls-jj-incoming
** Tags added: rls-jj-notfixing

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

Title:
  vim.tiny reports 'E1187: Failed to source defaults.vim' on execution
  in default install

Status in vim package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04

  When running vim.tiny it says:

  $ vim.tiny
  E1187: Failed to source defaults.vim
  Press ENTER or type command to continue

  This is due to the defaults.vim file not being available.  If you just
  run it as vi

  $ vi

  this message does not appear as vim.tiny runs in compatibility mode.  I found 
mention of this issue in:
  https://github.com/grml/grml-etc-core/issues/99

  The defaults.vim file is provided by the package vim-runtime.

  I'm unsure what the issue is, if something needs to be in
  /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg
  claims vimrc is in vim-common, but no file is installed for me from
  that package, or if vim-runtime needs to be a required package for
  vim-tiny

  $ dpkg -S /etc/vim/vimrc
  vim-common: /etc/vim/vimrc
  $ ls -al /etc/vim/vimrc
  ls: cannot access '/etc/vim/vimrc': No such file or directory

  I discovered this because my .selected-editor was vim.tiny after
  running crontab -e

  $ crontab -e

  Select an editor.  To change later, run 'select-editor'.
    1. /bin/nano< easiest
    2. /usr/bin/vim.tiny
    3. /bin/ed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: vim-tiny 2:8.2.3995-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
  Uname: Linux 5.15.0-1005-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 13 11:56:35 2022
  ImageMediaBuild: 20201022
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04

[Brian Murray]

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => High

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

Title:
  Initrd out of memory error after upgrade to 22.04

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 22.04 system is unbootable because of "out of memory" 
error when loading initial ramdisk. I was able to fix it by editing cat 
/etc/initramfs-tools/initramfs.conf
  and changing configuration to:
  MODULES=dep
  COMPRESS=xz
  RUNSIZE=15%

  Not sure which one helped, but I can test it if needed.

  System information:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  initramfs-tools:
Installed: 0.140ubuntu13
Candidate: 0.140ubuntu13
Version table:
   *** 0.140ubuntu13 500
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970402/+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 1970762] [NEW] liblzma failed to decompress a valid lzma file

[Qianqian Fang]

Public bug reported:

The lzma file can be accessed here:
https://kwafoo.coe.neu.edu/~fangq/share/temp/mat.lzma

This file was created using the public domain lzma C library written by
Igor Pavlov. It can be decompressed on Ubuntu 20.04 using `lzma -d`,
based on LZMA SDK 9.22, but on either Ubuntu 18.04 and 22.04, where lzma
is built based on liblzma, it gives a "Compressed data is corrupted"
error.


here is the log on Ubuntu 20.04 - where LZMA SDK based lzma works

```
fangq@ubuntu20_04:~$ lzma --version
LZMA command line tool 9.22
LZMA SDK 9.22

fangq@ubuntu20_04:~$ lzma -v -d mat.lzma
mat.lzma:21.83% -- replaced with mat
```

however, on Ubuntu 22.04, lzma -d does not work (same for 18.04)
```
fangq@ubuntu18_04:~$ lzma --version
xz (XZ Utils) 5.2.5
liblzma 5.2.5

fangq@ubuntu22_04$ lzma -v -d mat.lzma
mat.lzma (1/1)
 99.9 %   1,500.9 KiB / 1,920.0 KiB = 0.782
lzma: mat.lzma: Compressed data is corrupt
 99.9 %   1,500.9 KiB / 1,920.0 KiB = 0.782   
```

Because of this, I also noticed that the official lzma module of Python
fails to decompress this file. I want to add that using `lzma` or `lzma-
purejs` npm module, node.js script can correctly decompress this file.

** Affects: xz-utils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  liblzma failed to decompress a valid lzma file

Status in xz-utils package in Ubuntu:
  New

Bug description:
  The lzma file can be accessed here:
  https://kwafoo.coe.neu.edu/~fangq/share/temp/mat.lzma

  This file was created using the public domain lzma C library written
  by Igor Pavlov. It can be decompressed on Ubuntu 20.04 using `lzma
  -d`, based on LZMA SDK 9.22, but on either Ubuntu 18.04 and 22.04,
  where lzma is built based on liblzma, it gives a "Compressed data is
  corrupted" error.

  
  here is the log on Ubuntu 20.04 - where LZMA SDK based lzma works

  ```
  fangq@ubuntu20_04:~$ lzma --version
  LZMA command line tool 9.22
  LZMA SDK 9.22

  fangq@ubuntu20_04:~$ lzma -v -d mat.lzma
  mat.lzma:  21.83% -- replaced with mat
  ```

  however, on Ubuntu 22.04, lzma -d does not work (same for 18.04)
  ```
  fangq@ubuntu18_04:~$ lzma --version
  xz (XZ Utils) 5.2.5
  liblzma 5.2.5

  fangq@ubuntu22_04$ lzma -v -d mat.lzma
  mat.lzma (1/1)
   99.9 %   1,500.9 KiB / 1,920.0 KiB = 0.782   
 
  lzma: mat.lzma: Compressed data is corrupt
   99.9 %   1,500.9 KiB / 1,920.0 KiB = 0.782   
  ```

  Because of this, I also noticed that the official lzma module of
  Python fails to decompress this file. I want to add that using `lzma`
  or `lzma-purejs` npm module, node.js script can correctly decompress
  this file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xz-utils/+bug/1970762/+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 1970402] Re: Initrd out of memory error after upgrade to 22.04

[Heinrich Schuchardt]

How much memory does your machine have? How big was the extracted
initramfs?

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  Initrd out of memory error after upgrade to 22.04

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 22.04 system is unbootable because of "out of memory" 
error when loading initial ramdisk. I was able to fix it by editing cat 
/etc/initramfs-tools/initramfs.conf
  and changing configuration to:
  MODULES=dep
  COMPRESS=xz
  RUNSIZE=15%

  Not sure which one helped, but I can test it if needed.

  System information:
  Description:Ubuntu 22.04 LTS
  Release:22.04

  initramfs-tools:
Installed: 0.140ubuntu13
Candidate: 0.140ubuntu13
Version table:
   *** 0.140ubuntu13 500
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main i386 Packages
  100 /var/lib/dpkg/status

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


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

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

[Brian Murray]

** Also affects: openssl (Ubuntu Kinetic)
   Importance: Critical
 Assignee: Simon Chopin (schopin)
   Status: In Progress

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

** Tags removed: rls-jj-incoming

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

Title:
  openssl has catastrophic issues when locale set to TR_UTF8

Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Jammy:
  New
Status in openssl source package in Kinetic:
  In Progress

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

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

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

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

  So I changed locale to C_UTF-8

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

  Now the result is (after logout/login)

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

  Enable services with: ua enable 

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

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

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

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


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

[Touch-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

[Mario Limonciello]

Just to correct a few of the targets on this issue.  
* The reverts mentioned in #30 need to be pulled into linux-firmware for focal. 
 
* They're already included in jammy.

** Changed in: amd
   Status: New => Fix Released

** No longer affects: mesa (Ubuntu)

** Also affects: linux-firmware (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: linux-firmware (Ubuntu Focal)
 Assignee: (unassigned) => Juerg Haefliger (juergh)

** Changed in: linux-firmware (Ubuntu)
   Status: Invalid => Fix Released

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

Title:
  linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0]
  retry page fault"

Status in amd:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware source package in Focal:
  New
Status in linux-firmware source package in Hirsute:
  Won't Fix

Bug description:
  After upgrading linux-firmware from 1.190.5 to 1.197 (as part of the
  upgrade from Ubuntu 20.10 to 21.04), I started experiencing frequent
  and severe GPU instability. When this happens, I see this error in
  dmesg:

  [20061.061069] amdgpu :03:00.0: amdgpu: [gfxhub0] retry page fault 
(src_id:0 ring:0 vmid:1 pasid:32769, for process Xorg pid 1141 thread Xorg:cs0 
pid 1236)
  [20061.061103] amdgpu :03:00.0: amdgpu:   in page starting at address 
0x80401000 from client 27
  [20061.061135] amdgpu :03:00.0: amdgpu: 
VM_L2_PROTECTION_FAULT_STATUS:0x00101031
  [20061.061147] amdgpu :03:00.0: amdgpu:  Faulty UTCL2 client ID: TCP 
(0x8)
  [20061.061157] amdgpu :03:00.0: amdgpu:  MORE_FAULTS: 0x1
  [20061.061167] amdgpu :03:00.0: amdgpu:  WALKER_ERROR: 0x0
  [20061.061174] amdgpu :03:00.0: amdgpu:  PERMISSION_FAULTS: 0x3
  [20061.061183] amdgpu :03:00.0: amdgpu:  MAPPING_ERROR: 0x0
  [20061.061189] amdgpu :03:00.0: amdgpu:  RW: 0x0

  I'll attach a couple of full dmesgs that I collected.

  Many of the times when this happens, the screen and keyboard freeze
  irreversibly (I tried waiting for more than 30 minutes, but it doesn't
  help). I can still log in via ssh though. When there's no freeze, I
  can continue using the computer normally, but the laptop fans keep
  running are always running and the battery depletes fast. There's
  probably something on a permanent loop either in the kernel or in the
  GPU.

  This bug happens several times a day, rendering the machine so
  unstable as to be almost unusable. It is a severe regression and I'm
  aghast that it passed AMD's Quality Assurance.

  After downgrading back to linux-firmware 1.190.5, the machine is back
  to the previous, mostly-reliable state. Which is to say, this bug is
  gone, I'm just left with the other amdgpu suspend bug I've learned to
  live with since I bought this computer.

  Please revert the amdgpu firmware in this package as soon as possible.
  This is unbearable.

  Relevant information:
  Ubuntu version: 21.04
  Linux kernel: 5.11.0-17-generic x86_64
  CPU model: AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx
  GPU: 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Picasso (rev c1)
  Laptop model: Lenovo Ideapad S145

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


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

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

[Łukasz Zemczak]

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

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

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

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

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

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

Bug description:
  [Impact]

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

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

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

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

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

  [Test Plan]

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

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

  And running `s_client` like this:

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

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

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

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

  [Where problems could occur]

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

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


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

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

[Łukasz Zemczak]

Hello Nicolas, or anyone else affected,

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

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

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

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

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

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

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

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

Bug description:
  [Impact]

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

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

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

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

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

  [Test Plan]

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

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

  And running `s_client` like this:

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

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

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

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

  [Where problems could occur]

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

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


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

[Touch-packages] [Bug 1959345] Re: vulkaninfo reports error

[Timo Aaltonen]

we as in 'ubuntu'

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 1959345] Re: vulkaninfo reports error

[Timo Aaltonen]

you have the amdgpu-pro driver installed, if it's vulkan driver does not
install it's icd file in the correct place, there's nothing we can do
about that

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  vulkaninfo reports error

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Tracker says mesa-vulkan-drivers is not in Ubuntu!?
  mesa-vulkan-drivers/bionic-updates,now 20.0.8-0ubuntu1~18.04.1 amd64 
[installed]

  Ubuntu 18.04.6 LTS
  AMD Ryzen 7 2700x eight-core processor x 16
  AMD Radeon rx 5700 xt

  apt-cache show says that vulkan-mesa-drivers provides vulkan-icd.
  find / -name vulkan-icd finds nothing
  vulkaninfo reports:
  ERROR: [Loader Message] Code 0 : loader_get_json: Failed to open JSON file 
amd_icd64.json

  There is an intel_icd.x86_64.json and radeon_icd.x86_64.json in
  /usr/share/vulkan/icd.d/

  Either the error is a false positive or I should have amd_icd64.json - and 
then maybe all the other problems with the GPU would go away!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  gary  12435 F pulseaudio
   /dev/snd/controlC2:  gary  12435 F pulseaudio
   /dev/snd/controlC0:  gary  12435 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=4cce61c8-7d97-4fc3-8c3f-abfa4fd2810c
  InstallationDate: Installed on 2020-02-14 (740 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. B450 AORUS ELITE
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-99-generic 
root=UUID=88ad01a0-775b-4405-b569-8928dac46131 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 5.4.0-99.112~18.04.1-generic 5.4.162
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-99-generic N/A
   linux-backports-modules-5.4.0-99-generic  N/A
   linux-firmware1.173.20
  RfKill:
   
  Tags:  bionic
  Uname: Linux 5.4.0-99-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/13/2021
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F63d
  dmi.board.asset.tag: Default string
  dmi.board.name: B450 AORUS ELITE
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF63d:bd10/13/2021:svnGigabyteTechnologyCo.,Ltd.:pnB450AORUSELITE:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450AORUSELITE:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: B450 MB
  dmi.product.name: B450 AORUS ELITE
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1959345/+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 257135] Re: notify-send(1) can't replace an existing notification

[Treviño]

** Changed in: libnotify (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  notify-send(1) can't replace an existing notification

Status in libnotify package in Ubuntu:
  In Progress
Status in libnotify package in Debian:
  Fix Released

Bug description:
  Binary package hint: libnotify-bin

  Ubuntu 8.04, libnotify-bin 0.4.4-3build1.

  notify-send(1) is very useful but it doesn't tell me the notification
  ID that's been created, nor does it let me specify that to replace an
  earlier notification.  See http://www.galago-
  project.org/specs/notification/0.9/x408.html#command-notify, in
  particular the replaces_id parameter and the return value.

  I'd like to be able to use it something like

  id=$(notify-send --show-id foo)
  sleep 60
  notify-send --replace $id bar

  This would be great for long-running shell scripts that are monitoring
  something.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/257135/+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 383875] Re: add convenience function "notify_has_server_cap" to notify.h

[Treviño]

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

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

Title:
  add convenience function "notify_has_server_cap" to notify.h

Status in galago-daemon:
  New
Status in libnotify package in Ubuntu:
  Fix Released

Bug description:
  Inspired by http://bugzilla.gnome.org/show_bug.cgi?id=584857#c2 I
  added a convenience function to libnotify that allows easy testing for
  certain capabilities: gboolean notify_has_server_cap(const char*
  capability)

  Attaching patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/galago-daemon/+bug/383875/+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 725435] Re: notify-osd a memory hog (memory leak?)

[Treviño]

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

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

Title:
  notify-osd a memory hog (memory leak?)

Status in libnotify package in Ubuntu:
  Invalid
Status in notify-osd package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: notify-osd

  Noticed this today on my lucid box in top:
  2647 myaccount  20   0 1196m 595m 3528 S0 29.7   1:09.68 notify-osd

  I don't think a simple notifcation daemon should suck up more than a
  Gig of memory of which half is real memory.  It's the first time I
  noticed this.  I don't have too much information at this point.

  $ dpkg -l notify-osd*
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name  Version 
  Description
  
+++-=-=-==
  ii  notify-osd0.9.29-0ubuntu2 
  daemon that displays passive pop-up notifications
  ii  notify-osd-icons  0.6 
  Notify-OSD icons

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/725435/+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 1969934] Re: Update evolution-data-server to 3.44.1

[Jeremy Bicha]

** Description changed:

  Impact
  --
+ This is a new stable release in the 3.44 series (corresponding with GNOME 42).
+ 
+ https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/3.44.1/NEWS
+ 
+ It is required to update evolution to 3.44.1
  
  Test Case
  -
+ Install the update
+ Log out and log back in (or restart)
+ Ensure that GNOME Calendar and Evolution still work fine.
  
  What Could Go Wrong
  ---
+ As a component of GNOME core, there is a micro-release exception for 
evolution-data-server
+ 
+ https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

** Description changed:

  Impact
  --
  This is a new stable release in the 3.44 series (corresponding with GNOME 42).
  
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/3.44.1/NEWS
  
- It is required to update evolution to 3.44.1
+ It is required to update evolution to 3.44.1 (LP: #1969935)
  
  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.
  
  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server
  
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

** Changed in: evolution-data-server (Ubuntu)
   Status: Triaged => In Progress

** Also affects: evolution-data-server (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: evolution-data-server (Ubuntu Jammy)
   Importance: Undecided => Low

** Changed in: evolution-data-server (Ubuntu Jammy)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

** Changed in: evolution-data-server (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: evolution-data-server (Ubuntu)
 Assignee: (unassigned) => Jeremy Bicha (jbicha)

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

Title:
  Update evolution-data-server to 3.44.1

Status in evolution-data-server package in Ubuntu:
  In Progress
Status in evolution-data-server source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series (corresponding with GNOME 42).

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.1/NEWS

  It is required to update evolution to 3.44.1 (LP: #1969935)

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1969934/+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 1970735] [NEW] package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[sandmouse]

Public bug reported:

Encountered during a regular do-release-upgrade

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.7
ProcVersionSignature: Ubuntu 4.15.0-69.78-generic 4.15.18
Uname: Linux 4.15.0-69-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Apr 28 12:52:22 2022
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2016-01-27 (2283 days ago)
InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
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 2022-04-28 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check

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

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:
  Encountered during a regular do-release-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.7
  ProcVersionSignature: Ubuntu 4.15.0-69.78-generic 4.15.18
  Uname: Linux 4.15.0-69-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Apr 28 12:52:22 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2016-01-27 (2283 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  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 2022-04-28 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1970735/+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 1970731] [NEW] iptables empty when using firewalld

[Peter Englmaier]

Public bug reported:

Summary:
I am using firewalld/jammy,now 1.1.1-1ubuntu1 on my vpn server. The vpn server 
is using wireguard and I could successfully configure zones and policies in 
firewalld. Yet, iptables does not show the rules from firewalld.

1) System
root@vpn:~# uname -a
Linux vpn 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 
x86_64 x86_64 GNU/Linux
root@vpn:~# lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:22.04

All updates installed.


2) What happens:

I am setting rules with firewall-cmd.

These firewall rules are visible with:
   nft list table inet firewalld
but not with 'iptables'.

3) What I expect to happen:

The toutput of
  iptables --list
should also reflect firewalld settings.

4) What happened instead

However, the iptables output shows only empty tables (filter, mangle,
nat).

root@vpn:~# iptables -t nat --list
# Warning: iptables-legacy tables present, use iptables-legacy to see them
Chain PREROUTING (policy ACCEPT)
target prot opt source   destination 

Chain INPUT (policy ACCEPT)
target prot opt source   destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination 

Chain POSTROUTING (policy ACCEPT)
target prot opt source   destination 
root@vpn:~# iptables -t filter --list
# Warning: iptables-legacy tables present, use iptables-legacy to see them
Chain INPUT (policy ACCEPT)
target prot opt source   destination 

Chain FORWARD (policy ACCEPT)
target prot opt source   destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination 
root@vpn:~# iptables-legacy -t nat --list
Chain PREROUTING (policy ACCEPT)
target prot opt source   destination 

Chain INPUT (policy ACCEPT)
target prot opt source   destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination 

Chain POSTROUTING (policy ACCEPT)
target prot opt source   destination 
root@vpn:~# iptables-legacy -t filter --list
Chain INPUT (policy ACCEPT)
target prot opt source   destination 

Chain FORWARD (policy ACCEPT)
target prot opt source   destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination 


5) Further information

The ufw firewall is disabled and uninstalled.

According to the release notes of 22.04, the backend has changed to nftables. 
I was assuming, that the backend default is kind of transparent to the user, 
meaning iptables should still work as normal. 

I wonder if on my system is iptables correctly linked to the backend.

Iptables points to xtables-nft-multi:
root@vpn:~# ls -l /usr/sbin/iptables
lrwxrwxrwx 1 root root 26 Aug 24  2021 /usr/sbin/iptables -> 
/etc/alternatives/iptables
root@vpn:~# ls -l /etc/alternatives/iptables
lrwxrwxrwx 1 root root 22 Apr 25 18:56 /etc/alternatives/iptables -> 
/usr/sbin/iptables-nft
root@vpn:~# ls -l /usr/sbin/iptables-nft
lrwxrwxrwx 1 root root 17 Mar 24 12:58 /usr/sbin/iptables-nft -> 
xtables-nft-multi
root@vpn:~# ls -l /usr/sbin/xtables-nft-multi
-rwxr-xr-x 1 root root 224296 Mar 24 12:58 /usr/sbin/xtables-nft-multi


Perhaps this is an issue with the upgrade process of ubuntu.

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

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

Title:
  iptables empty when using firewalld

Status in ufw package in Ubuntu:
  New

Bug description:
  Summary:
  I am using firewalld/jammy,now 1.1.1-1ubuntu1 on my vpn server. The vpn 
server is using wireguard and I could successfully configure zones and policies 
in firewalld. Yet, iptables does not show the rules from firewalld.

  1) System
  root@vpn:~# uname -a
  Linux vpn 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 
x86_64 x86_64 x86_64 GNU/Linux
  root@vpn:~# lsb_release -rd
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  All updates installed.

  
  2) What happens:

  I am setting rules with firewall-cmd.

  These firewall rules are visible with:
 nft list table inet firewalld
  but not with 'iptables'.

  3) What I expect to happen:

  The toutput of
iptables --list
  should also reflect firewalld settings.

  4) What happened instead

  However, the iptables output shows only empty tables (filter, mangle,
  nat).

  root@vpn:~# iptables -t nat --list
  # Warning: iptables-legacy tables present, use iptables-legacy to see them
  Chain PREROUTING (policy ACCEPT)
  target prot opt source   destination 

  Chain INPUT (policy ACCEPT)
  target prot opt source   destination 

  Chain OUTPUT (policy ACCEPT)
  

[Touch-packages] [Bug 1922786] Re: Apt install of local deb files shows a notification causing confusion

[Harpreet Singh]

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=22.04
DISTRIB_CODENAME=jammy
DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS"

# Bug
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'google-chrome-stable' instead of 
'./google-chrome-stable_current_amd64.deb'
The following NEW packages will be installed:
  google-chrome-stable
0 to upgrade, 1 to newly install, 0 to remove and 0 not to upgrade.
Need to get 0 B/84.4 MB of archives.
After this operation, 274 MB of additional disk space will be used.
Get:1 /home/hstest-vmw/Downloads/google-chrome-stable_current_amd64.deb 
google-chrome-stable amd64 101.0.4951.41-1 [84.4 MB]
Selecting previously unselected package google-chrome-stable.
(Reading database ... 174260 files and directories currently installed.)
Preparing to unpack .../google-chrome-stable_current_amd64.deb ...
Unpacking google-chrome-stable (101.0.4951.41-1) ...
Setting up google-chrome-stable (101.0.4951.41-1) ...
update-alternatives: using /usr/bin/google-chrome-stable to provide 
/usr/bin/x-www-browser (x-www-browser) in auto mode
update-alternatives: using /usr/bin/google-chrome-stable to provide 
/usr/bin/gnome-www-browser (gnome-www-browser) in au
to mode
update-alternatives: using /usr/bin/google-chrome-stable to provide 
/usr/bin/google-chrome (google-chrome) in auto mode
Processing triggers for gnome-menus (3.36.0-1ubuntu3) ...
Processing triggers for man-db (2.10.2-1) ...
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for desktop-file-utils (0.26-1ubuntu3) ...
N: Download is performed unsandboxed as root as file 
'/home/hstest-vmw/Downloads/google-chrome-stable_current_amd64.deb' couldn't be 
accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

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

Title:
  Apt install of local deb files shows a notification causing confusion

Status in apt package in Ubuntu:
  Triaged

Bug description:
  
  Installation for a local deb file shows a notification message that causes a 
lot of confusion whether the package has been successfully installed or not.

  Steps to reproduce
  =
  - Download a package file (xxx.deb)
  - Install the package file from command line "sudo apt install ./xxx.deb"
  - A notification messages shows up at the end of the installation saying:
   "Download is performed unsandboxed as root as file 
'/home/fredli/harddisc/External/Nordic/nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb'
 couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)"

  -> Expected no notification or warnings if installation finished
  successfully.

  It seems that this is only "Notifcation message" BUT it causes a lot
  of confusion whether the package has been installed or not. The
  package seems to be installed correctly from what I understand.

  $ apt --version
  apt 2.2.2 (amd64)

  $ lsb_release -rd
  Description:  Ubuntu Hirsute Hippo (development branch)
  Release:  21.04

  Full log:
  ==
  $ sudo apt install ./nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb 
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Note, selecting 'nrf-command-line-tools' instead of 
'./nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb'
  The following NEW packages will be installed:
nrf-command-line-tools
  0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  After this operation, 22,6 MB of additional disk space will be used.
  Get:1 
/home/fredli/harddisc/External/Nordic/nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb
 nrf-command-line-tools amd64 10.12.1 [3 406 kB]
  Selecting previously unselected package nrf-command-line-tools.
  (Reading database ... 149444 files and directories currently installed.)
  Preparing to unpack .../nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb ...
  Unpacking nrf-command-line-tools (10.12.1) ...
  Setting up nrf-command-line-tools (10.12.1) ...
  N: Download is performed unsandboxed as root as file 
'/home/fredli/harddisc/External/Nordic/nRF-Command-Line-Tools_10_12_1_Linux-amd64.deb'
 couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1922786/+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 1970086] Re: GSM modem does not work properly (driver / config issue)

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  GSM modem does not work properly (driver / config issue)

Status in libmbim package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The GSM Modem does not work properly in Network. 
  There is no IPv6 connection. 
  Modem is Sierra Wireless, Inc. EM7421
  GSM Modem EM7421 works perfect with Xubuntu 21.10 and it works perfect with 
Ubuntu 21.10. SIM card, APN etc. same as in U21.10 do work fine (same machine 
Fujitsu E5511).  

  Need to correct broken settings to get EM7421 properly show and handle
  IPv6 connections.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sysyadmin   1066 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sun Apr 24 10:50:46 2022
  InstallationDate: Installed on 2022-04-24 (0 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5511
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=adf3ffda-d8d8-4b33-9786-041e074965c7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2022
  dmi.bios.release: 2.28
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 2.28
  dmi.board.name: FJNB2E8
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: C3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.chassis.version: LIFEBOOK E5511
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.28:bd03/17/2022:br2.28:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5511:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E8:rvrC3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5511:skuSK01:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK E5511
  dmi.product.sku: SK01
  dmi.product.version: 10601736746
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1970086/+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 1970086] Re: GSM modem does not work properly (driver / config issue)

[Launchpad Bug Tracker]

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

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

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

Title:
  GSM modem does not work properly (driver / config issue)

Status in libmbim package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The GSM Modem does not work properly in Network. 
  There is no IPv6 connection. 
  Modem is Sierra Wireless, Inc. EM7421
  GSM Modem EM7421 works perfect with Xubuntu 21.10 and it works perfect with 
Ubuntu 21.10. SIM card, APN etc. same as in U21.10 do work fine (same machine 
Fujitsu E5511).  

  Need to correct broken settings to get EM7421 properly show and handle
  IPv6 connections.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-25-generic 5.15.0-25.25
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sysyadmin   1066 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sun Apr 24 10:50:46 2022
  InstallationDate: Installed on 2022-04-24 (0 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: FUJITSU CLIENT COMPUTING LIMITED LIFEBOOK E5511
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic 
root=UUID=adf3ffda-d8d8-4b33-9786-041e074965c7 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-25-generic N/A
   linux-backports-modules-5.15.0-25-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/17/2022
  dmi.bios.release: 2.28
  dmi.bios.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.bios.version: Version 2.28
  dmi.board.name: FJNB2E8
  dmi.board.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.board.version: C3
  dmi.chassis.type: 10
  dmi.chassis.vendor: FUJITSU CLIENT COMPUTING LIMITED
  dmi.chassis.version: LIFEBOOK E5511
  dmi.modalias: 
dmi:bvnFUJITSUCLIENTCOMPUTINGLIMITED:bvrVersion2.28:bd03/17/2022:br2.28:svnFUJITSUCLIENTCOMPUTINGLIMITED:pnLIFEBOOKE5511:pvr10601736746:rvnFUJITSUCLIENTCOMPUTINGLIMITED:rnFJNB2E8:rvrC3:cvnFUJITSUCLIENTCOMPUTINGLIMITED:ct10:cvrLIFEBOOKE5511:skuSK01:
  dmi.product.family: LIFEBOOK-FTS
  dmi.product.name: LIFEBOOK E5511
  dmi.product.sku: SK01
  dmi.product.version: 10601736746
  dmi.sys.vendor: FUJITSU CLIENT COMPUTING LIMITED

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1970086/+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 1968412] Re: When trying to open the program it says that i need to be in a special group to use it

[Launchpad Bug Tracker]

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

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

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

Title:
  When trying to open the program it says that i need to be in a special
  group to use it

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Version: 0.99.22
  Kubuntu version 22.04
  I expected it to open up the software properties without any errors.
  It said that i need to be in a special group (wheel) to use it.
  It says the password is incorrect even though i use this password to log in.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-qt 0.99.22
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Sat Apr  9 11:59:59 2022
  InstallationDate: Installed on 2022-04-09 (0 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1968412/+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 1969959] Re: [nouveau] Weird colors after startup (Ubuntu 22.04)

[Daniel van Vugt]

This might turn out to be related to bug 1965882.

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

** Changed in: mesa (Ubuntu)
   Importance: Undecided => High

** Tags added: regression-release rls-jj-incoming

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

Title:
  [nouveau] Weird colors after startup (Ubuntu 22.04)

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I started Ubuntu 22.04 from a live pen drive. Everything seems fine,
  the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
  appears. When hitting "Try Ubuntu", the screen turns black for a
  couple of seconds and then re-appears in yellow and brown colors,
  feels like a 4 color display (white, black, yellow and orange) and I
  can hardly see anything - sending this bug report from that live
  system right after starting it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:54:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 
00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7C56
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550-A PRO (MS-7C56)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C56
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 1970449] Re: GPG keys are not shown in Software and Updates

[Manfred Hampl]

Fact is: software-properties-gtk does not show the registered apt gpg keys in 
the "Authentication" tab on my Ubuntu 21.10 and 22.04 systems.
My Ubuntu 20.04 shows the registered keys in the window.

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

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Canonical livepatch icon doesn't appear on the title bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1970449] Re: GPG keys are not shown in Software and Updates

[Manfred Hampl]

Due to the fact that the system in question showed two different issues,
there is a mix of information related to the two problems.

I have tried to clean that up a bit.

** Package changed: ubuntu-release-upgrader (Ubuntu) => software-
properties (Ubuntu)

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

Title:
  GPG keys are not shown in Software and Updates

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Canonical livepatch icon doesn't appear on the title bar.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntu-release-upgrader-core 1:22.04.10
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 26 20:48:04 2022
  InstallationDate: Installed on 2022-04-25 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1970449/+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 1969959] Re: [nouveau][amdgpu] Weird colors after startup (Ubuntu 22.04)

[Daniel van Vugt]

I completely agree, it's a bad user experience.

The reason why proprietary drivers like Nvidia are historically not
installed by default I think is because they have their own license
conditions.

In practice the real problem here seems to be the bugginess of the open
source nouveau driver you will get instead. It's been causing pain for
us for years and I would tend to think we should partially disable it.
Maybe just disable the acceleration part (mesa) and not the KMS part
(kernel).

** Summary changed:

- [nouveau][amdgpu] Weird colors after startup (Ubuntu 22.04)
+ [nouveau] Weird colors after startup (Ubuntu 22.04)

** Package changed: mutter (Ubuntu) => mesa (Ubuntu)

** No longer affects: xorg-server (Ubuntu)

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

Title:
  [nouveau] Weird colors after startup (Ubuntu 22.04)

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  I started Ubuntu 22.04 from a live pen drive. Everything seems fine,
  the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
  appears. When hitting "Try Ubuntu", the screen turns black for a
  couple of seconds and then re-appears in yellow and brown colors,
  feels like a 4 color display (white, black, yellow and orange) and I
  can hardly see anything - sending this bug report from that live
  system right after starting it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:54:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 
00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7C56
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550-A PRO (MS-7C56)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C56
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1969959/+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 1970068] Re: L2TP+IPSec not working after upgrade to 22.04 LTS

[msaxl]

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

this is probably not a duplicate but this
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/961

#1951832 does talk about a issue with xl2tpd, looking at this log
output, the ppp session is established but is terminated afer 1.5
minutes. A lot of bytes where sent, but none was received. looks like
the ppp packet was routed inside the ppp tunnel (this is, according to
Douglas Kosovic, a regression in network manager)

** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #961
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/961

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

Title:
  L2TP+IPSec not working after upgrade to 22.04 LTS

Status in network-manager package in Ubuntu:
  New
Status in network-manager-l2tp package in Ubuntu:
  New
Status in ppp package in Ubuntu:
  New
Status in xl2tpd package in Ubuntu:
  New

Bug description:
  In 20.04LTS i was able to connect to my work over the L2TP tunel. Now
  it seems like this in journald:

  kwi 24 01:00:37 nm-l2tp-service[11368]: xl2tpd started with pid 11433
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Not looking for kernel 
SAref support.
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Using l2tp kernel 
support.
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: xl2tpd version 
xl2tpd-1.3.16 started on crushXnitro PID:11433
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Written by Mark 
Spencer, Copyright (C) 1998, Adtran, Inc.
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Forked by Scott Balmos 
and David Stipp, (C) 2001
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Inherited by Jeff 
McAdams, (C) 2002
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Forked again by 
Xelerance (www.xelerance.com) (C) 2006-2016
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Listening on IP address 
0.0.0.0, port 49636
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Connecting to host 
X.X.X.X, port 1701
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Connection established 
to X.X.X.X, 1701.  Local: 19994, Remote: 201 (ref=0/0).
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Calling on tunnel 19994
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: Call established with 
X.X.X.X, Local: 65441, Remote: 142, Serial: 1 (ref=0/0)
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: start_pppd: I'm running:
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "/usr/sbin/pppd"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "plugin"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "pppol2tp.so"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "pppol2tp"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "7"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "passive"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "nodetach"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: ":"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: "file"
  kwi 24 01:00:37 NetworkManager[11433]: xl2tpd[11433]: 
"/run/nm-l2tp-bd8ac49b-a2e9-4094-91dc-17a13ce61ec8/ppp-options"
  kwi 24 01:00:37 pppd[11434]: Plugin pppol2tp.so loaded.
  kwi 24 01:00:37 pppd[11434]: Plugin 
/usr/lib/pppd/2.4.9/nm-l2tp-pppd-plugin.so loaded.
  kwi 24 01:00:37 pppd[11434]: pppd 2.4.9 started by root, uid 0
  kwi 24 01:00:37 pppd[11434]: Using interface ppp0
  kwi 24 01:00:37 pppd[11434]: Connect: ppp0 <-->
  kwi 24 01:00:37 pppd[11434]: Overriding mtu 1500 to 1400
  kwi 24 01:00:37 pppd[11434]: Overriding mru 1500 to mtu value 1400
  kwi 24 01:00:37 NetworkManager[1017]:   [1650754837.9839] manager: 
(ppp0): new Ppp device (/org/freedesktop/NetworkManager/Devices/6)
  kwi 24 01:00:38 pppd[11434]: CHAP authentication succeeded
  kwi 24 01:00:38 charon[11397]: 10[KNL] interface ppp0 activated
  kwi 24 01:00:38 charon[11397]: 13[KNL] fe80::81ee:6717:6637:2084 appeared on 
ppp0
  kwi 24 01:00:38 charon[11397]: 14[KNL] flags changed for 
fe80::81ee:6717:6637:2084 on ppp0
  kwi 24 01:00:38 pppd[11434]: local  LL address fe80::81ee:6717:6637:2084
  kwi 24 01:00:38 pppd[11434]: remote LL address fe80::::00f0:0c0e
  kwi 24 01:00:38 charon[11397]: 16[KNL] 192.168.57.181 appeared on ppp0
  kwi 24 01:00:38 NetworkManager[1017]:   [1650754838.0741] device 
(ppp0): state change: unmanaged -> unavailable (reason 'connection-assumed', 
sys-iface-state: 'external')
  kwi 24 01:00:38 charon[11397]: 08[KNL] 192.168.57.181 disappeared from ppp0
  kwi 24 01:00:38 charon[11397]: 10[KNL] 192.168.57.181 appeared on ppp0
  kwi 24 01:00:38 NetworkManager[1017]:   [1650754838.0751] device 
(ppp0): state change: unavailable -> disconnected (reason 'none', 
sys-iface-state: 

[Touch-packages] [Bug 1970449] [NEW] GPG keys are not shown in Software and Updates

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Canonical livepatch icon doesn't appear on the title bar.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: ubuntu-release-upgrader-core 1:22.04.10
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 26 20:48:04 2022
InstallationDate: Installed on 2022-04-25 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-bug dist-upgrade jammy wayland-session
-- 
GPG keys are not shown in Software and Updates
https://bugs.launchpad.net/bugs/1970449
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to software-properties in Ubuntu.

-- 
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 1969959] [NEW] [nouveau] Weird colors after startup (Ubuntu 22.04)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I started Ubuntu 22.04 from a live pen drive. Everything seems fine, the
usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
appears. When hitting "Try Ubuntu", the screen turns black for a couple
of seconds and then re-appears in yellow and brown colors, feels like a
4 color display (white, black, yellow and orange) and I can hardly see
anything - sending this bug report from that live system right after
starting it up.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CasperVersion: 1.470
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 15:54:05 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
 Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 00 
[VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Micro-Star International Co., Ltd. MS-7C56
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed 
maybe-ubiquity quiet splash ---
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/30/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: A.40
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B550-A PRO (MS-7C56)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7C56
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: xorg-server (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 amdgpu apport-bug jammy nouveau ubuntu
-- 
[nouveau] Weird colors after startup (Ubuntu 22.04)
https://bugs.launchpad.net/bugs/1969959
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to mesa in Ubuntu.

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

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

[Lukas Märdian]

All autopkgtest regressions on Focal/Impish could be resolved by re-
running them with appropriate triggers.

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

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

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

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

  [Test Plan]
  Press airplane hokey.

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

  Please refer to Bug #1955997 as well.

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


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

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

[Lukas Märdian]

All autopkgtest regressions on Focal/Impish/Jammy could be resolved by
re-running them with appropriate triggers.

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

Title:
  Add mic mute key for HP Elite x360 series

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

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

  [Impact]

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

  [Test Plan]

   * Test mic mute key on Elite x360 G9 series.

  
  [Where problems could occur]

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

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


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

[Touch-packages] [Bug 1958267] Re: "Connection failed" for WPA Enterprise network (e.g. eduroam)

[Chaitanya Rahangdale]

Upgraded to 22.04 and started facing issues w.r.t. WiFi.
Steps in comment #22 did not work for me.

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

Title:
  "Connection failed" for WPA Enterprise network (e.g. eduroam)

Status in wpa package in Ubuntu:
  Confirmed
Status in wpa source package in Jammy:
  Confirmed

Bug description:
  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

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