[Touch-packages] [Bug 1999960] Re: Xorg crash

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

** Changed in: ubuntu
   Status: New => Incomplete

** Summary changed:

- Xorg crash
+ Crash

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

Title:
  Crash

Status in Ubuntu:
  Incomplete

Bug description:
  It is the 10th time the Ubuntu just hang and restarted

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat Dec 17 12:38:26 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 620 [1043:15a0]
  MachineType: ASUSTeK COMPUTER INC. UX310UAK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=e067f662-d3f0-44de-970a-ef760eeb539a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2019
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX310UAK.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX310UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX310UAK.312:bd04/18/2019:br5.12:svnASUSTeKCOMPUTERINC.:pnUX310UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX310UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ZenBook
  dmi.product.name: UX310UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/+bug/160/+subscriptions


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

[Touch-packages] [Bug 2000359] Re: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable)

[Po-Hsu Lin]

I can confirm this has passed with K-aws 5.19.0-1016.17 ARM64
Thanks!

** Also affects: qa-regression-testing
   Importance: Undecided
   Status: New

** Changed in: qa-regression-testing
   Status: New => Fix Released

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

Title:
  posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed
  on K-5.19 arm64 (Unable to run test sub-executable)

Status in QA Regression Testing:
  Fix Released
Status in ubuntu-kernel-tests:
  New
Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Kinetic:
  New

Bug description:
  Issue found on Kinetic 5.19 ARM64 systems,

  The ApparmorTestsuites.test_regression_testsuite in
  ubuntu_qrt_apparmor will fail with posix_ipc test:

  running posix_ipc
  Fatal Error (posix_mq_rcv): Unable to run test sub-executable

  It's a bit hard to find which one is failing, here is the test output
  of ApparmorTestsuites.test_regression_testsuite:

  == BEGIN OF TEST OUPTUT ==
  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309514 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309547 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309797 Segmentation fault  (core dumped) $testexec "$@" > 
$outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309826 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309861 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309896 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309931 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root
   kernel does not support pivot_root domain transitions - skipping tests ...

  running posix_ipc
  Fatal Error (posix_mq_rcv): Unable to run test sub-executable

  running ptrace
     using ptrace v6 tests ...

  running pwrite

  running query_label

  running regex

  running rename

  running readdir

  running rw

  running socketpair

  running swap

  running sd_flags

  running setattr

  running symlink

  running syscall
   WARNING: syscall sysctl not supported by kernel headers, skipping tests ...

  running sysv_ipc
  Required feature 'ipc/sysv_mqueue' not available.. Skipping tests ...

  running tcp

  running unix_fd_server

  running unix_socket_pathname
  xpass: AF_UNIX pathname socket (dgram); confined server w/ access (rw)
  xpass: AF_UNIX pathname socket (dgram); confined client w/ access (rw)

  running unix_socket_abstract

  running 

[Touch-packages] [Bug 1999896] Re: cpu utilisation too high

[Daniel van Vugt]

Please open a terminal window and run 'top'. What process is using the
most CPU?

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  cpu utilisation too high

Status in Ubuntu:
  Incomplete

Bug description:
  Im running Ubuntu 20.04(With KDE desktop environment) on a dell inspiron 5378.
   Operating System: Kubuntu 20.04
  KDE Plasma Version: 5.18.8
  KDE Frameworks Version: 5.68.0
  Qt Version: 5.12.8
  Kernel Version: 5.15.0-56-generic
  OS Type: 64-bit
  Processors: 4 × Intel® Pentium® CPU 4415U @ 2.30GHz
  Memory: 3.6 GiB of RAM

  The ram usage is fine, i have no issues on that end my main concern is
  how quickly the cpu goes up to 100% utilistation in system monitor
  after opening the file manager and a few firefox tabs.

  If anyone can advise on the matter i would be more than grateful.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Dec 16 16:07:45 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:5906] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0740]
  InstallationDate: Installed on 2022-11-15 (30 days ago)
  InstallationMedia: Kubuntu 20.04.5 LTS "Focal Fossa" - Release amd64 
(20220831)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:2494 Elan Microelectronics Corp. Touchscreen
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:58c2 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 13-5378
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=6580df22-8c81-4fb7-bbcf-f074c7b6efc2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/15/2021
  dmi.bios.release: 1.36
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.36.0
  dmi.board.name: 0WFM43
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.36.0:bd12/15/2021:br1.36:svnDellInc.:pnInspiron13-5378:pvr:rvnDellInc.:rn0WFM43:rvrA00:cvnDellInc.:ct9:cvr:sku0740:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 13-5378
  dmi.product.sku: 0740
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 1999939] Re: The conky display stopped working after recent update

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => conky (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/139

Title:
  The conky display stopped working after recent update

Status in conky package in Ubuntu:
  New

Bug description:
  The conky display stopped working after recent update, see error message:
  X Error of failed request:  BadWindow (invalid Window parameter)
Major opcode of failed request:  20 (X_GetProperty)
Resource id in failed request:  0x201
Serial number of failed request:  105
Current serial number in output stream:  105

  I attach the .conkyrc file

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Fri Dec 16 15:32:42 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2019-10-28 (1145 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 
(20191026)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=9dfdf604-fe7f-4a57-b5c2-d1f354795add ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:sku:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

[Touch-packages] [Bug 2000024] Re: Font alignment/search bar size issue when using scaling factor > 1

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1999320
   Font alignment issue in search bar when using scaling factor > 1

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

Title:
  Font alignment/search bar size issue when using scaling factor > 1

Status in xorg package in Ubuntu:
  New

Bug description:
  When using 'gsettings set org.gnome.desktop.interface text-scaling-
  factor' command to set the scaling factor to something greater than 1,
  the text gets misaligned in the search bar, which seems to be too
  small (shown in an attachment here).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-56.62-generic 5.15.64
  Uname: Linux 5.15.0-56-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..01.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  525.60.11  Wed Nov 23 
23:04:03 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 18 18:07:13 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GA102 [GeForce RTX 3090] [10de:2204] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GA102 [GeForce RTX 3090] [1043:87b3]
  InstallationDate: Installed on 2022-12-18 (0 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-56-generic 
root=UUID=fc0c0197-bcc1-4eb2-abf4-af87b54ca0e2 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/2022
  dmi.bios.release: 22.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2204
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG STRIX Z690-E GAMING WIFI
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2204:bd11/30/2022:br22.4:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXZ690-EGAMINGWIFI:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
  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.5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/224/+subscriptions


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

[Touch-packages] [Bug 1999986] Re: ibus-daemon 170% CPU when using Flatpak Endeavour

[Gunnar Hjalmarsson]

A long shot: Install gnome-session:

sudo apt install gnome-session

log in to a "vanilla" GNOME session and see if you notice a difference
with respect to the endeavour behavior.

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

Title:
  ibus-daemon 170% CPU when using Flatpak Endeavour

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  - Install Endeavour from Flatpak: 
https://flathub.org/apps/details/org.gnome.Todo
  - Synchronize a few Google tasks list
  - Attempt to type in the new task bar
  - Observe that `ibus-daemon` uses 170% CPU for half a minute before typing is 
possible

  Ubuntu 22.10 with Gnome, with both English and Chinese input methods
  installed

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


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

[Touch-packages] [Bug 2000359] Re: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable)

[Steve Beattie]

This has been fixed in the regression tests in the upstream AppArmor
project, and that patch has been incorporated into the lp:qa-regression-
testing script for apparmor (thanks Georgia!), so tests for the kernel
should not fail in this way now.

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

Title:
  posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed
  on K-5.19 arm64 (Unable to run test sub-executable)

Status in ubuntu-kernel-tests:
  New
Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Kinetic:
  New

Bug description:
  Issue found on Kinetic 5.19 ARM64 systems,

  The ApparmorTestsuites.test_regression_testsuite in
  ubuntu_qrt_apparmor will fail with posix_ipc test:

  running posix_ipc
  Fatal Error (posix_mq_rcv): Unable to run test sub-executable

  It's a bit hard to find which one is failing, here is the test output
  of ApparmorTestsuites.test_regression_testsuite:

  == BEGIN OF TEST OUPTUT ==
  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309514 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309547 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309797 Segmentation fault  (core dumped) $testexec "$@" > 
$outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309826 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309861 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309896 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309931 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root
   kernel does not support pivot_root domain transitions - skipping tests ...

  running posix_ipc
  Fatal Error (posix_mq_rcv): Unable to run test sub-executable

  running ptrace
     using ptrace v6 tests ...

  running pwrite

  running query_label

  running regex

  running rename

  running readdir

  running rw

  running socketpair

  running swap

  running sd_flags

  running setattr

  running symlink

  running syscall
   WARNING: syscall sysctl not supported by kernel headers, skipping tests ...

  running sysv_ipc
  Required feature 'ipc/sysv_mqueue' not available.. Skipping tests ...

  running tcp

  running unix_fd_server

  running unix_socket_pathname
  xpass: AF_UNIX pathname socket (dgram); confined server w/ access (rw)
  xpass: AF_UNIX pathname socket (dgram); confined client w/ access (rw)

  running unix_socket_abstract

  running unix_socket_unnamed
  xpass: AF_UNIX unnamed 

[Touch-packages] [Bug 2000817] Re: Wrong SHA256-value computed on kinetic

[Bryce Harrington]

** Tags added: server-next

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

Title:
  Wrong SHA256-value computed on kinetic

Status in openldap package in Ubuntu:
  Triaged

Bug description:
  The OpenLDAP-contrib module sha2 (located in contrib/slapd-
  modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu
  kinetic. This breaks our current password-authentication in ldap.

  
  The problematic computation:

  $ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
  {SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=

  The (correct) reference-value on the same system (or older ubuntu
  Versions):

  $ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64
  K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=

  
  We nailed the problem down to a bug in the gcc-optimizer for strict-aliasing. 
so most probably the gcc-version on kinetic (v12.2.0) is the reason. The 
workaround is to compile the sha2-Module with the flag "-fno-strict-aliasing". 
Then the correct value is computed. An example taken from a git-compiled 
version of OpenLDAP 2.5.13:

  $ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o 
module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs
  {SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=


  
  Ubuntu:

  Description:Ubuntu 22.10
  Release:22.10

  OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1

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


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

[Touch-packages] [Bug 2000817] Re: Wrong SHA256-value computed on kinetic

[Bryce Harrington]

lunar, kinetic, and jammy all return the first result, while focal
provides the second:

triage-lunar+23.04: ~$ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
{SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=
triage-lunar+23.04: ~$ slapd -VV
@(#) $OpenLDAP: slapd 2.6.3+dfsg-1~exp1ubuntu1 (Nov 18 2022 21:07:45) $

triage-kinetic+22.10: ~$ slappasswd -s secret -h '{SHA256}' -o 
module-load=pw-sha2
{SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=
triage-kinetic+22.10: ~$ slapd -VV
@(#) $OpenLDAP: slapd 2.5.13+dfsg-1ubuntu1 (Sep 20 2022 19:30:47) $

triage-jammy+22.04: ~$ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
{SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=
triage-jammy+22.04: ~$ slapd -VV
@(#) $OpenLDAP: slapd 2.5.13+dfsg-0ubuntu0.22.04.1 (Aug  5 2022 14:51:52) $

triage-focal+20.04: ~$ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
{SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=
triage-focal+20.04: ~$ slapd -VV
@(#) $OpenLDAP: slapd  (Ubuntu) (May 12 2022 13:11:05) $
triage-focal+20.04: ~$ apt-cache policy slapd
slapd:
  Installed: 2.4.49+dfsg-2ubuntu1.9

On all releases, the openssl dgst call produces the same result,
K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=

Here's two other references mentioning the same problem, and same
suggested workaround:

* 
https://www.mail-archive.com/search?l=openldap-techni...@openldap.org=subject:%22%22=newest=1
* 
https://stackoverflow.com/questions/74928752/slappasswd-generating-a-strange-password-hash-sha256-only

I don't know whether there might be side effects from adding "-fno-
strict-aliasing".  However, the patch's compilation modifications looks
like it'll affect the performance of only just the sha2 module, so for
SRU policy this seems a narrow enough fix.  Since this is described in
the first link as a contrib module, that may explain why this issue
hasn't come to light earlier.

** Changed in: openldap (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Wrong SHA256-value computed on kinetic

Status in openldap package in Ubuntu:
  Triaged

Bug description:
  The OpenLDAP-contrib module sha2 (located in contrib/slapd-
  modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu
  kinetic. This breaks our current password-authentication in ldap.

  
  The problematic computation:

  $ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
  {SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=

  The (correct) reference-value on the same system (or older ubuntu
  Versions):

  $ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64
  K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=

  
  We nailed the problem down to a bug in the gcc-optimizer for strict-aliasing. 
so most probably the gcc-version on kinetic (v12.2.0) is the reason. The 
workaround is to compile the sha2-Module with the flag "-fno-strict-aliasing". 
Then the correct value is computed. An example taken from a git-compiled 
version of OpenLDAP 2.5.13:

  $ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o 
module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs
  {SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=


  
  Ubuntu:

  Description:Ubuntu 22.10
  Release:22.10

  OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1

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


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

[Touch-packages] [Bug 2000098] Re: I am not sure if i am right

[Daniel van Vugt]

It looks like the NVIDIA-525 driver is correctly installed and working.
What makes you think otherwise?

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  I am not sure if i am right

Status in Ubuntu:
  Incomplete

Bug description:
  I am not sure what i have done but the driver seems wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-26.27-generic 5.19.7
  Uname: Linux 5.19.0-26-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..01.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  525.60.11  Wed Nov 23 
23:04:03 UTC 2022
   GCC version:  gcc version 12.2.0 (Ubuntu 12.2.0-3ubuntu1)
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  BootLog: Error: [Errno 13] Erişim engellendi: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 20 00:56:43 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  DkmsStatus: nvidia/525.60.11, 5.19.0-26-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation TU116 [GeForce GTX 1660 SUPER] [10de:21c4] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] TU116 [GeForce GTX 
1660 SUPER] [1462:8d94]
  InstallationDate: Installed on 2022-12-17 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  MachineType: Gigabyte Technology Co., Ltd. B250M-Gaming 3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=tr_TR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-26-generic 
root=UUID=847b2ef5-caec-47e0-a734-a25d0e008f1a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/10/2018
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M-Gaming 3-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.:bvrF7:bd04/10/2018:br5.12:svnGigabyteTechnologyCo.,Ltd.:pnB250M-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB250M-Gaming3-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B250M-Gaming 3
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  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.4-2ubuntu1.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  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/+bug/298/+subscriptions


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

[Touch-packages] [Bug 1956039] Re: BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018)

[Alex Lane]

What fixed it for me was to remove my apt-cacher-ng container + cache,
then re-add it.

This resolved the issue on multiple servers.

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

Title:
  BADSIG 871920D1991BC93C Ubuntu Archive Automatic Signing Key (2018)
  

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Updating Jammy fails with:

  Get:2 http://archive.ubuntu.com/ubuntu jammy InRelease [270 kB] 
  Err:2 http://archive.ubuntu.com/ubuntu jammy InRelease
The following signatures were invalid: BADSIG 871920D1991BC93C Ubuntu 
Archive Automatic Signing Key (2018) 

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


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

[Touch-packages] [Bug 1999472] Re: Dark mode not working correctly

[Daniel van Vugt]

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

Thanks for the bug report. It appears you need to toggle the color
selection to get it to apply to the "toolbox" (aggregate menu):

Settings > Appearance > Style > Color = change values

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

** Tags added: kinetic

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

Title:
  Dark mode not working correctly

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Version of Ubuntu: 22.10
  Package: X.org
  Expected to happen: Toolbox on the top right corner should stay in dark mode 
all the time.
  What happened instead: When accessing appearance options at config menu, the 
toolbox on the top right corner goes white, not corresponding with the dark 
mode selected on the config menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1999472/+subscriptions


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

[Touch-packages] [Bug 1999320] Re: Font alignment issue when using scaling factor > 1

[Daniel van Vugt]

** Tags added: jammy

** Summary changed:

- Font alignment issue when using scaling factor > 1
+ Font alignment issue in search bar when using scaling factor > 1

** 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/1999320

Title:
  Font alignment issue in search bar when using scaling factor > 1

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  When I use a desktop interface text scaling factor of 1.5, the
  alignment text in the applications menu search bar is not set properly

  I have attached a screenshot showing the issue.

  1)
  Description:  Ubuntu 22.04.1 LTS
  Release:  22.04
  2) xorg:
Installed: 1:7.7+23ubuntu2
Candidate: 1:7.7+23ubuntu2
Version table:
   *** 1:7.7+23ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  3) text was centered
  4) it is not centered

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1999320/+subscriptions


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

[Touch-packages] [Bug 1999986] Re: ibus-daemon 170% CPU when using Flatpak Endeavour

[DuckDuckWhale]

Hi, I have it installed and the issue is still present on that version.
The upstream maintainer is unable to reproduce it on the newer Flatpak
version and suspects that it's related to Ubuntu instead:


Here's a snapshot of `top`:

```
top - 17:46:31 up 11 days,  3:23,  1 user,  load average: 2.76, 2.40, 3.11
Tasks: 520 total,   3 running, 515 sleeping,   0 stopped,   2 zombie
%Cpu(s): 24.4 us,  3.8 sy,  0.0 ni, 70.7 id,  1.1 wa,  0.0 hi,  0.0 si,  0.0 st
MiB Mem :  15635.1 total,359.1 free,   8045.4 used,   7230.6 buff/cache
MiB Swap:   8192.0 total,   4474.0 free,   3718.0 used.   3539.6 avail Mem 

PID USER  PR  NIVIRTRESSHR S  %CPU  %MEM TIME+ COMMAND  

 976155 user  20   0  717112 201224   6820 R 180.1   1.3   4:13.66 
ibus-daemon  
   2423 user  20   0 6867760 675268 198844 S  77.7   4.2   6662:37 
gnome-shell  
...
 977417 user  20   0 2346300 460536 100516 S   2.3   2.9   0:17.48 
endeavour 
```

** Bug watch added: gitlab.gnome.org/World/Endeavour/-/issues #475
   https://gitlab.gnome.org/World/Endeavour/-/issues/475

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

Title:
  ibus-daemon 170% CPU when using Flatpak Endeavour

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  - Install Endeavour from Flatpak: 
https://flathub.org/apps/details/org.gnome.Todo
  - Synchronize a few Google tasks list
  - Attempt to type in the new task bar
  - Observe that `ibus-daemon` uses 170% CPU for half a minute before typing is 
possible

  Ubuntu 22.10 with Gnome, with both English and Chinese input methods
  installed

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


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

[Touch-packages] [Bug 2001568] Re: unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  u-u is currently failing autopkgtest on arm64. It does not look like
  this is a new failure (2.8ubuntu1 appears to have had exactly the same
  failure) but it's due to the kernel-patterns test assuming that kernel
  flavors cannot be a suffix of each other. This is true under Debian,
  and under several architectures on Ubuntu, but the arm64 architecture
  on Ubuntu has -generic and -generic-64k flavors which cause the test
  to fail.

  The attached debdiff corrects the test for this case.

  One may wonder why the test currently passes under armhf, which has
  -generic and -generic-lpae flavors (I certainly did!). It turns out
  this is only because Ubuntu autopkgtest runs armhf in a container so
  the kernel release reported by "uname -r" (used in the test) does not
  meaningfully match anything in the apt cache.

  Given this, the attached debdiff also restricts the kernel-patterns
  test to isolation-machine as the test assumes a meaningful link
  between the running kernel and the packages in the archive which is
  only true in a VM or on the bare metal.

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


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

[Touch-packages] [Bug 2001568] Re: unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

[Dave Jones]

** Patch added: "uu-arm64-kernels.patch"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2001568/+attachment/5639009/+files/uu-arm64-kernels.patch

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

Title:
  unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  u-u is currently failing autopkgtest on arm64. It does not look like
  this is a new failure (2.8ubuntu1 appears to have had exactly the same
  failure) but it's due to the kernel-patterns test assuming that kernel
  flavors cannot be a suffix of each other. This is true under Debian,
  and under several architectures on Ubuntu, but the arm64 architecture
  on Ubuntu has -generic and -generic-64k flavors which cause the test
  to fail.

  The attached debdiff corrects the test for this case.

  One may wonder why the test currently passes under armhf, which has
  -generic and -generic-lpae flavors (I certainly did!). It turns out
  this is only because Ubuntu autopkgtest runs armhf in a container so
  the kernel release reported by "uname -r" (used in the test) does not
  meaningfully match anything in the apt cache.

  Given this, the attached debdiff also restricts the kernel-patterns
  test to isolation-machine as the test assumes a meaningful link
  between the running kernel and the packages in the archive which is
  only true in a VM or on the bare metal.

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


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

[Touch-packages] [Bug 2001568] [NEW] unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

[Dave Jones]

Public bug reported:

u-u is currently failing autopkgtest on arm64. It does not look like
this is a new failure (2.8ubuntu1 appears to have had exactly the same
failure) but it's due to the kernel-patterns test assuming that kernel
flavors cannot be a suffix of each other. This is true under Debian, and
under several architectures on Ubuntu, but the arm64 architecture on
Ubuntu has -generic and -generic-64k flavors which cause the test to
fail.

The attached debdiff corrects the test for this case.

One may wonder why the test currently passes under armhf, which has
-generic and -generic-lpae flavors (I certainly did!). It turns out this
is only because Ubuntu autopkgtest runs armhf in a container so the
kernel release reported by "uname -r" (used in the test) does not
meaningfully match anything in the apt cache.

Given this, the attached debdiff also restricts the kernel-patterns test
to isolation-machine as the test assumes a meaningful link between the
running kernel and the packages in the archive which is only true in a
VM or on the bare metal.

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "uu-arm64-kernels.patch"
   
https://bugs.launchpad.net/bugs/2001568/+attachment/5639008/+files/uu-arm64-kernels.patch

** Patch removed: "uu-arm64-kernels.patch"
   
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2001568/+attachment/5639008/+files/uu-arm64-kernels.patch

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

Title:
  unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  u-u is currently failing autopkgtest on arm64. It does not look like
  this is a new failure (2.8ubuntu1 appears to have had exactly the same
  failure) but it's due to the kernel-patterns test assuming that kernel
  flavors cannot be a suffix of each other. This is true under Debian,
  and under several architectures on Ubuntu, but the arm64 architecture
  on Ubuntu has -generic and -generic-64k flavors which cause the test
  to fail.

  The attached debdiff corrects the test for this case.

  One may wonder why the test currently passes under armhf, which has
  -generic and -generic-lpae flavors (I certainly did!). It turns out
  this is only because Ubuntu autopkgtest runs armhf in a container so
  the kernel release reported by "uname -r" (used in the test) does not
  meaningfully match anything in the apt cache.

  Given this, the attached debdiff also restricts the kernel-patterns
  test to isolation-machine as the test assumes a meaningful link
  between the running kernel and the packages in the archive which is
  only true in a VM or on the bare metal.

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


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

[Touch-packages] [Bug 2000276] Re: FIDO2 user verification impossible when using the ssh agent

[Lena Voytek]

Thank you for submitting this report. I attempted to verify on a fresh
install of Kinetic as a client and Jammy as a server using a Yubikey
Bio. ssh login worked for me both with and without ssh-agent active. I
unfortunately don't have a 5c to test with and the issue may lie
specifically with that. Have you tried this with multiple new ssh keys
to confirm the issue?

** Changed in: openssh (Ubuntu)
   Status: New => Incomplete

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

Title:
  FIDO2 user verification impossible when using the ssh agent

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I am having trouble setting up FIDO2 ssh keys with my yubikey 5C NFC
  if I want to enable user verification (user presence works fine).

  
  Steps to reproduce:

  = Prep work =

  Client (kinetic):
  * generate a key that requires user verification:
$ ssh-keygen -t ed25519-sk -f ~/.ssh/id_ed25519_verify_sk -O 
verify-required -C "this key requires UV"
[provide your authenticator PIN, touch it, and add an encryption password]

  Server (jammy):
  * add id_ed25519_verify_sk.pub to authorized_keys

  = Symptoms =

  Shell 1 (w/ssh agent):

  $ eval $(ssh-agent)
  Agent pid 3279738

  $ ssh-add ~/.ssh/id_ed25519_verify_sk
  Enter passphrase for /home/aieri/.ssh/id_ed25519_verify_sk: 
  Identity added: /home/aieri/.ssh/id_ed25519_verify_sk (this key requires UV)

  $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 fails\!"
  sign_and_send_pubkey: signing failed for ED25519-SK 
"/home/aieri/.ssh/id_ed25519_verify_sk" from agent: agent refused operation
  ubuntu@10.35.202.231: Permission denied (publickey).

  [note that the above is printed immediately, and that the yubikey does
  not light up]

  Shell 2 (no ssh agent):

  $ ssh ubuntu@10.35.202.231 -i ~/.ssh/id_ed25519_verify_sk "echo FIDO2 works\!"
  Enter passphrase for key '/home/aieri/.ssh/id_ed25519_verify_sk': 
  Enter PIN for ED25519-SK key /home/aieri/.ssh/id_ed25519_verify_sk: 
  Confirm user presence for key ED25519-SK 
SHA256:nhgS4c2rGtE7XKeez3rAsofrjJvsL6rmBLShZxfTXIY
  User presence confirmed
  FIDO2 works!


  NOTE: 
  * user _presence_ can be validated correctly with or without the ssh-agent: 
keys generated without `-O verify-required` work as expected (aside from bug 
1869897)

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


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

[Touch-packages] [Bug 654361] Re: GLX 1.3 programs (like clutter) fail with software rasteriser

[Oibaf]

Is this still an issue with a newer Ubuntu?

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

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

Title:
  GLX 1.3 programs (like clutter) fail with software rasteriser

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Clutter-using apps will fail to start with the software rasteriser with the 
message:
  """
  failed to create drawable
  Failed to initialise clutter: Unable to select the newly created GLX context
  """

  swrast_dri.so is probably missing some GLX 1.3 stuff to make this work
  properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: libgl1-mesa-dri 7.9~git20100924-0ubuntu2
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  Architecture: amd64
  DRM.card0.DisplayPort.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.DisplayPort.2:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.DisplayPort.3:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.HDMI_Type_A.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.HDMI_Type_A.2:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  DRM.card0.LVDS.1:
   status: connected
   enabled: enabled
   dpms: On
   modes: 1440x900
   edid-base64: 
AP///wAwrhRAACoSAQOAGhB46uWVk1ZPkCgoUFQBAQEBAQEBAQEBAQEBAQEB8BygoFCEGjAYEDYABaMQAAAY8BygoFCEGjAYEDYABaMQAAAYDwCVCjKVCjIZAQAwZABV/gBMVEQxMjFFUTNCCiAgAJM=
  DRM.card0.VGA.1:
   status: disconnected
   enabled: disabled
   dpms: Off
   modes: 
   edid-base64:
  Date: Mon Oct  4 14:00:13 2010
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100817)
  MachineType: LENOVO 7465CTO
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.35-22-generic 
root=UUID=e136bf5d-1b75-4152-9f1c-8f77220ef0f2 ro quiet splash
  ProcEnviron:
   LANGUAGE=en_AU:en_GB:en_US:en
   PATH=(custom, user)
   LANG=en_AU.utf8
   SHELL=/usr/bin/zsh
  SourcePackage: mesa
  dmi.bios.date: 03/10/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6DET63WW (3.13 )
  dmi.board.name: 7465CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6DET63WW(3.13):bd03/10/2010:svnLENOVO:pn7465CTO:pvrThinkPadX200s:rvnLENOVO:rn7465CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 7465CTO
  dmi.product.version: ThinkPad X200s
  dmi.sys.vendor: LENOVO
  system:
   distro: Ubuntu
   codename:   maverick
   architecture:   x86_64
   kernel: 2.6.35-22-generic

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


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

[Touch-packages] [Bug 2000359] Re: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable)

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~georgiag/qa-regression-testing/+git/qa-regression-testing/+merge/435084

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

Title:
  posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed
  on K-5.19 arm64 (Unable to run test sub-executable)

Status in ubuntu-kernel-tests:
  New
Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Kinetic:
  New

Bug description:
  Issue found on Kinetic 5.19 ARM64 systems,

  The ApparmorTestsuites.test_regression_testsuite in
  ubuntu_qrt_apparmor will fail with posix_ipc test:

  running posix_ipc
  Fatal Error (posix_mq_rcv): Unable to run test sub-executable

  It's a bit hard to find which one is failing, here is the test output
  of ApparmorTestsuites.test_regression_testsuite:

  == BEGIN OF TEST OUPTUT ==
  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309514 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309547 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309797 Segmentation fault  (core dumped) $testexec "$@" > 
$outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309826 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309861 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309896 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309931 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root
   kernel does not support pivot_root domain transitions - skipping tests ...

  running posix_ipc
  Fatal Error (posix_mq_rcv): Unable to run test sub-executable

  running ptrace
     using ptrace v6 tests ...

  running pwrite

  running query_label

  running regex

  running rename

  running readdir

  running rw

  running socketpair

  running swap

  running sd_flags

  running setattr

  running symlink

  running syscall
   WARNING: syscall sysctl not supported by kernel headers, skipping tests ...

  running sysv_ipc
  Required feature 'ipc/sysv_mqueue' not available.. Skipping tests ...

  running tcp

  running unix_fd_server

  running unix_socket_pathname
  xpass: AF_UNIX pathname socket (dgram); confined server w/ access (rw)
  xpass: AF_UNIX pathname socket (dgram); confined client w/ access (rw)

  running unix_socket_abstract

  running unix_socket_unnamed
  xpass: AF_UNIX unnamed socket (dgram); confined server (peer label w/ 
implicit perms)
  xpass: AF_UNIX unnamed socket (dgram); confined 

[Touch-packages] [Bug 1998639] Re: MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0

[Oibaf]

** Summary changed:

- MESA-INTEL: warning:
+ MESA-INTEL: warning: Performance support disabled, consider sysctl 
dev.i915.perf_stream_paranoid=0

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

Title:
  MESA-INTEL: warning: Performance support disabled, consider sysctl
  dev.i915.perf_stream_paranoid=0

Status in mesa package in Ubuntu:
  New

Bug description:
  MESA-INTEL: warning: Performance support disabled, consider sysctl
  dev.i915.perf_stream_paranoid=0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.39 [origin: unknown]
  ProcVersionSignature: Ubuntu 5.15.0-56.62~20.04.1-generic 5.15.64
  Uname: Linux 5.15.0-56-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Dec  2 13:09:19 2022
  InstallationDate: Installed on 2021-06-05 (545 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2022-11-30 (2 days ago)
  VarLogDistupgradeTermlog:
   
  mtime.conffile..etc.update-manager.release-upgrades: 
2022-11-29T19:37:54.229059

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


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

[Touch-packages] [Bug 2001556] [NEW] systemd-cryptenroll poorly communicates libtss2-rc0 dependency

[Kyler Hornor]

Public bug reported:

Description:

tpm2 support was added to jammy in 249.11-0ubuntu3.3 via LP1969375.
libtss2-rc0 was added as a suggested package.

$ systemd-cryptenroll --tpm2-device=list
TPM2 support is not installed.

Installing libtss2-rc0 allows this to resolve:
$ sudo apt install libtss2-rc0
$ systemd-cryptenroll --tpm2-device=list
PATHDEVICE  DRIVER
/dev/tpmrm0 VTPM0101:00 tpm_crb

While this isn't inherently an issue, two things are notable:

+ The manpage for systemd-cryptenroll makes no mention that the
suggested package needs to be installed (that I could find), this is
only noted via `apt depends`. I only happened to find this while
building from source.

+ The presented error implies that the pkg was build with -Dtpm2=false
(as I read it), which is not actually the case. It should properly
indicate the missing dep.

The choice to leave this as a suggested dep was deliberate, so I believe
resolution of the above two issues would suffice to provide enduser
clarity.

** 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/2001556

Title:
  systemd-cryptenroll poorly communicates libtss2-rc0 dependency

Status in systemd package in Ubuntu:
  New

Bug description:
  Description:

  tpm2 support was added to jammy in 249.11-0ubuntu3.3 via LP1969375.
  libtss2-rc0 was added as a suggested package.

  $ systemd-cryptenroll --tpm2-device=list
  TPM2 support is not installed.

  Installing libtss2-rc0 allows this to resolve:
  $ sudo apt install libtss2-rc0
  $ systemd-cryptenroll --tpm2-device=list
  PATHDEVICE  DRIVER
  /dev/tpmrm0 VTPM0101:00 tpm_crb

  While this isn't inherently an issue, two things are notable:

  + The manpage for systemd-cryptenroll makes no mention that the
  suggested package needs to be installed (that I could find), this is
  only noted via `apt depends`. I only happened to find this while
  building from source.

  + The presented error implies that the pkg was build with -Dtpm2=false
  (as I read it), which is not actually the case. It should properly
  indicate the missing dep.

  The choice to leave this as a suggested dep was deliberate, so I
  believe resolution of the above two issues would suffice to provide
  enduser clarity.

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


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

[Touch-packages] [Bug 2000359] Re: posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed on K-5.19 arm64 (Unable to run test sub-executable)

[Georgia Garcia]

Thanks for reporting this issue. I created a MR upstream to fix it
https://gitlab.com/apparmor/apparmor/-/merge_requests/962

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

Title:
  posix_ipc in test_regression_testsuite from ubuntu_qrt_apparmor failed
  on K-5.19 arm64 (Unable to run test sub-executable)

Status in ubuntu-kernel-tests:
  New
Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Kinetic:
  New

Bug description:
  Issue found on Kinetic 5.19 ARM64 systems,

  The ApparmorTestsuites.test_regression_testsuite in
  ubuntu_qrt_apparmor will fail with posix_ipc test:

  running posix_ipc
  Fatal Error (posix_mq_rcv): Unable to run test sub-executable

  It's a bit hard to find which one is failing, here is the test output
  of ApparmorTestsuites.test_regression_testsuite:

  == BEGIN OF TEST OUPTUT ==
  running aa_exec

  running access
  xfail: ACCESS file rx (r)
  xfail: ACCESS file rwx (r)
  xfail: ACCESS file r (wx)
  xfail: ACCESS file rx (wx)
  xfail: ACCESS file rwx (wx)
  xfail: ACCESS dir rwx (r)
  xfail: ACCESS dir r (wx)
  xfail: ACCESS dir rx (wx)
  xfail: ACCESS dir rwx (wx)

  running at_secure

  running introspect

  running capabilities
  (ptrace)
  (sethostname)
  (setdomainname)
  (setpriority)
  (setscheduler)
  (reboot)
  (chroot)
  (mlockall)
  (net_raw)

  running changeprofile

  running onexec

  running changehat

  running changehat_fork

  running changehat_misc

  *** A 'Killed' message from bash is expected for the following test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309514 Killed  $testexec "$@" > $outfile 2>&1

  *** A 'Killed' message from bash is expected for the following test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309547 Killed  $testexec "$@" > $outfile 2>&1

  running chdir

  running clone

  running coredump
  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309797 Segmentation fault  (core dumped) $testexec "$@" > 
$outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309826 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309861 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309896 Segmentation fault  $testexec "$@" > $outfile 2>&1

  *** A 'Segmentation Fault' message from bash is expected for the following 
test
  
/tmp/testlibxbcgpuwp/source/kinetic/apparmor-3.0.7/tests/regression/apparmor/prologue.inc:
 line 264: 309931 Segmentation fault  $testexec "$@" > $outfile 2>&1
  XFAIL: Error: corefile present when not expected -- COREDUMP (ix confinement)

  running deleted

  running environ

  running exec

  running exec_qual

  running fchdir

  running fd_inheritance

  running fork

  running i18n

  running link

  running link_subset

  running mkdir

  running mmap

  running mount
  using mount rules ...

  running mult_mount

  running named_pipe

  running namespaces

  running net_raw

  running open

  running openat

  running pipe

  running pivot_root
   kernel does not support pivot_root domain transitions - skipping tests ...

  running posix_ipc
  Fatal Error (posix_mq_rcv): Unable to run test sub-executable

  running ptrace
     using ptrace v6 tests ...

  running pwrite

  running query_label

  running regex

  running rename

  running readdir

  running rw

  running socketpair

  running swap

  running sd_flags

  running setattr

  running symlink

  running syscall
   WARNING: syscall sysctl not supported by kernel headers, skipping tests ...

  running sysv_ipc
  Required feature 'ipc/sysv_mqueue' not available.. Skipping tests ...

  running tcp

  running unix_fd_server

  running unix_socket_pathname
  xpass: AF_UNIX pathname socket (dgram); confined server w/ access (rw)
  xpass: AF_UNIX pathname socket (dgram); confined client w/ access (rw)

  running unix_socket_abstract

  running unix_socket_unnamed
  xpass: AF_UNIX unnamed socket (dgram); confined server (peer label w/ 
implicit perms)
  xpass: AF_UNIX unnamed socket (dgram); confined server 

[Touch-packages] [Bug 1724623] Re: Update ubuntu cloud info

[James Falcon]

"I'll leave the cloud-init team to comment, but I actually disagree."

Yeah, we already provide that info in a more raw state, and for cloud-
init, it won't help to pretty it up or do more parsing. Is there
something needed from cloud-init for this to work correctly?

** Changed in: cloud-init (Ubuntu)
   Status: New => Incomplete

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

Title:
  Update ubuntu cloud info

Status in apport package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  Incomplete

Bug description:
  add_cloud_info() in data/general-hooks/ubuntu.py needs an overhaul.

  Issues:
   - Using the presence of cloud-init to flag an image as a cloud image is 
incorrect now that ubuntu-server includes cloud-init (and ubuntu-core images)
   - Using the presence of EC2 metadata source is incorrect as many non-EC2 
clouds provide EC2 metadata.  Thus we have bugs like bug #1722946 that are 
tagged as an 'ec2-images' bug which are clearly on openstack
   - Marking all bugs that have cloud-init but no EC2 metadata source as an 
'uec-images' bug uses a name that no longer has meaning.

  Solution:
   - If cloud-init is present, check for /etc/cloud/build.info to indicate an 
Ubuntu cloud images, tag as 'cloud-images'.  Pull the build_name and serial 
from that file into the bug comments.
   - If cloud-init is present, check for the presence of 
/run/cloud-init/cloud.cfg.  Parse this yaml to determine the datasource type.  
Add the datasource used to the bug comment.

  I have filed bug #1724626 to ask cloud-init development to surface
  more information from ds-identify to help ID the cloud so that we can
  better tag/annotate the bug.  There may also be some info we can get
  to indicate the image ID on more clouds than just AWS.  At a minimum I
  would like to see dsidentify make the EC2 platform it found available
  for consumers in cloud.cfg.  This would allow us to identify AWS EC2
  from look-alike datasources so that we can tag a bug as ec2-images for
  bug really on AWS and add EC2 specific fields to the
  description/attachments.

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


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

[Touch-packages] [Bug 2000628] Re: The wifi password prompt disappear immediately after showing up on 22.04

[Sharcoux]

Thanks so much @brian-murray !

I didn't know how to find out the package responsible for that part!

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

Title:
  The wifi password prompt disappear immediately after showing up on
  22.04

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Some other people reported this bug
  [here](https://askubuntu.com/questions/1409433/22-04-cant-input-
  password-for-wifi)

  Basically, when you try to log into a network, there is no way to
  input your password. The only way to reach a visible network seems to
  be by one of the workarounds: use the "Connect to Hidden Network"
  option, or directly edit the network config files.

  It seems like a critical bug to me because it can demotivate new users
  of Ubuntu and Linux.

  I joined a screen record of the prompt blinking on screen.

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


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

[Touch-packages] [Bug 2000628] Re: The wifi password prompt disappear immediately after showing up on 22.04

[Brian Murray]

** Package changed: ubuntu => ubuntu-meta (Ubuntu)

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

Title:
  The wifi password prompt disappear immediately after showing up on
  22.04

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Some other people reported this bug
  [here](https://askubuntu.com/questions/1409433/22-04-cant-input-
  password-for-wifi)

  Basically, when you try to log into a network, there is no way to
  input your password. The only way to reach a visible network seems to
  be by one of the workarounds: use the "Connect to Hidden Network"
  option, or directly edit the network config files.

  It seems like a critical bug to me because it can demotivate new users
  of Ubuntu and Linux.

  I joined a screen record of the prompt blinking on screen.

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


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

[Touch-packages] [Bug 2000628] [NEW] The wifi password prompt disappear immediately after showing up on 22.04

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Some other people reported this bug
[here](https://askubuntu.com/questions/1409433/22-04-cant-input-
password-for-wifi)

Basically, when you try to log into a network, there is no way to input
your password. The only way to reach a visible network seems to be by
one of the workarounds: use the "Connect to Hidden Network" option, or
directly edit the network config files.

It seems like a critical bug to me because it can demotivate new users
of Ubuntu and Linux.

I joined a screen record of the prompt blinking on screen.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bot-comment
-- 
The wifi password prompt disappear immediately after showing up on 22.04
https://bugs.launchpad.net/bugs/2000628
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to ubuntu-meta 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 1998942] Re: openssl: merge 3.0.7-1 from Debian unstable

[Adrien Nader]

And PPA for this merge is available at
https://launchpad.net/~adrien-n/+archive/ubuntu/merge-openssl-3.0.7/ .

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

Title:
   openssl: merge 3.0.7-1 from Debian unstable

Status in openssl package in Ubuntu:
  In Progress

Bug description:
  Debian has moved to 3.0.7 in unstable. Now is a good time to merge it.

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


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

[Touch-packages] [Bug 1998942] Re: openssl: merge 3.0.7-1 from Debian unstable

[Adrien Nader]

Attached is a debdiff against Debian's 3.0.7-1.

** Patch added: "openssl_3.0.7-1-to-openssl_3.0.7-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1998942/+attachment/5638959/+files/openssl_3.0.7-1-to-openssl_3.0.7-1ubuntu1.debdiff

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

Title:
   openssl: merge 3.0.7-1 from Debian unstable

Status in openssl package in Ubuntu:
  In Progress

Bug description:
  Debian has moved to 3.0.7 in unstable. Now is a good time to merge it.

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


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

[Touch-packages] [Bug 1998942] Re: openssl: merge 3.0.7-1 from Debian unstable

[Adrien Nader]

Attached is a debdiff against Ubuntu's 3.0.5-2ubuntu2.

** Patch added: "openssl_3.0.5-2ubuntu2-to-openssl_3.0.7-1ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1998942/+attachment/5638958/+files/openssl_3.0.5-2ubuntu2-to-openssl_3.0.7-1ubuntu1.debdiff

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

Title:
   openssl: merge 3.0.7-1 from Debian unstable

Status in openssl package in Ubuntu:
  In Progress

Bug description:
  Debian has moved to 3.0.7 in unstable. Now is a good time to merge it.

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


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

[Touch-packages] [Bug 1946804] Re: ufw breaks boot on network root filesystem

[Mauricio Faria de Oliveira]

Hi. No, I haven't tested on that; but if this helps, the issue is
independent of platform/hypervisor as it's in ufw/firewall, thus the fix
should help anyway.

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

Title:
  ufw breaks boot on network root filesystem

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

Bug description:
  [Impact]

  A system with rootfs on iSCSI stops booting when ufw.service starts.
  The kernel logs iSCSI command/reset timeout until I/O fails and the
  root filesystem/journal break.

  The issue is that ufw_start() sets the default policy _first_, then
  adds rules _later_.

  So, a default INPUT policy of DROP (default setting in ufw) prevents
  further access to the root filesystem (blocks incoming iSCSI traffic)
  thus any rules that could help are not loaded (nor anything else.)

  [Fix]

  The fix is to set default policy after loading rules in ufw_start().
  That seems to be OK as `ip[6]tables-restore -n/--noflush` is used,
  and per iptables source, that only sets the chain policy.

  This allows the system to boot due to the RELATED,ESTABLISHED rule,
  that is introduced by before.rules in INPUT/ufw-before-input chain.

  The comparison of `iptables -L` before/after shows no differences
  (verified on a local rootfs); `run_tests.sh` has 0 skipped/errors.

  [Test Steps]

   * Install Ubuntu on an iSCSI (or other network-based) root filesystem.
     (eg, Oracle Cloud's bare-metal 'BM.Standard1.36' shape.)

   * sudo ufw enable

   * Observed: system may stall immediately if no prior iptables rules.
     (eg, iptables -A INPUT -p tcp -s 169.254.0.2 --sport 3260 -j ACCEPT)

   * Expected: system continues working.

   * sudo reboot

   * Observed: system boot stalls once ufw.service starts (see below.)
   * Expected: system boot should move on.

  [Regression Potential]

   * Potential regressions would be observed on ufw start/reload,
     when iptables rules are configured.

   * The resulting iptables configuration has been compared
     before/after the change, with identical rules on both.

  [Other Info]

   * Fixed in Debian and Jammy.

  [ufw info]

  # ufw --version
  ufw 0.36
  Copyright 2008-2015 Canonical Ltd.

  # lsb_release -cs
  focal

  [Boot Log]

  [ 232.168355] iBFT detected.
  Begin: Running /scripts/init-premount ... done.
  Begin: Mounting root file system ... Begin: Running /scripts/local-top ...
  Setting up software interface enp45s0f0np0
  ...
  [ 254.644505] Loading iSCSI transport class v2.0-870.
  [ 254.714938] iscsi: registered transport (tcp)
  [ 254.780129] scsi host12: iSCSI Initiator over TCP/IP
  ...
  [ 255.433491] sd 12:0:0:1: [sda] 251658240 512-byte logical blocks: (129 
GB/120 GiB)
  ...
  [ 256.379550] EXT4-fs (sda1): mounted filesystem with ordered data mode. 
Opts: (null)
  ...
  [ 266.620860] systemd[1]: Starting Uncomplicated firewall...
  Starting Uncomplicated firewall...
  ...
  [ 298.491560] session1: iscsi_eh_cmd_timed_out scsi cmd 310a6696 
timedout
  [ 298.580803] session1: iscsi_eh_cmd_timed_out return shutdown or nh
  [ 298.656262] session1: iscsi_eh_cmd_timed_out scsi cmd 94ad9246 
timedout
  [ 298.745237] session1: iscsi_eh_cmd_timed_out return shutdown or nh
  [ 298.745270] session1: iscsi_eh_abort aborting sc 310a6696
  [ 298.899644] session1: iscsi_eh_abort aborting [sc 310a6696 itt 0x13]
  [ 298.985788] session1: iscsi_exec_task_mgmt_fn tmf set timeout
  [ 302.075554] session1: iscsi_eh_cmd_timed_out scsi cmd 1a9458b5 
timedout
  [ 302.164786] session1: iscsi_eh_cmd_timed_out return shutdown or nh
  [ 314.107541] session1: iscsi_tmf_timedout tmf timedout
  [ 314.169797] connection1:0: detected conn error (1021)
  [ 314.232266] session1: iscsi_eh_abort abort failed [sc 310a6696 itt 
0x13]
  [ 314.323531] session1: iscsi_eh_abort aborting sc 94ad9246
  [ 314.399640] session1: iscsi_eh_abort sc never reached iscsi layer or it 
completed.
  [ 314.495578] session1: iscsi_eh_abort aborting sc 1a9458b5
  [ 314.571554] session1: iscsi_eh_abort sc never reached iscsi layer or it 
completed.
  [ 314.664050] session1: iscsi_eh_device_reset LU Reset [sc 310a6696 
lun 1]
  [ 314.755773] session1: iscsi_eh_device_reset dev reset result = FAILED
  [ 314.834736] session1: iscsi_eh_target_reset tgt Reset [sc 310a6696 
tgt <...>]
  [ 314.954144] session1: iscsi_eh_target_reset tgt <...> reset result = FAILED
  [ 315.063456] connection1:0: detected conn error (1021)
  [ 315.125743] session1: iscsi_eh_session_reset wait for relogin
  [ 398.843556] INFO: task systemd:1 blocked for more 

[Touch-packages] [Bug 2000868] Re: backport required for virtio_gpu_dri.so

[Oibaf]

For the record, the fix is already in upstream 22.3.0 and 22.2.5 (lunar
+ currently in "proposed" for kinetic), but not on 22.0.5 (jammy).

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

Title:
  backport required for virtio_gpu_dri.so

Status in mesa package in Ubuntu:
  New

Bug description:
  Hi,

  xorg crashing when using modsetting with virtio_gpu_dri as graphics
  driver in kvm guest. Kindly look into this conversation

  https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/291#note_1701920

  I think we need to backport
  https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19655 to fix
  this issue.

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


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

[Touch-packages] [Bug 1998263] Re: JPEG ( backing store not supported ) : many pictures won't open.

[Bug Watch Updater]

** Changed in: eog
   Status: Unknown => Fix Released

** Changed in: gdk-pixbuf
   Status: Unknown => Fix Released

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

Title:
  JPEG ( backing store not supported ) : many pictures won't open.

Status in Eye of GNOME:
  Fix Released
Status in gdk-pixbuf:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Jammy:
  Invalid
Status in gdk-pixbuf source package in Lunar:
  Fix Released

Bug description:
  Hi,

  22.10. Just try to open some .jpg files from my usual storage.

  Error interpreting jpeg file ( Backing store not supported. )

  Those same pictures open in other OSes ( 22.04, 20.04 and else. )

  Can't use those pictures as backgrounds.

  But able to open them in Gimp or Shotwell.

  Maybe related to : https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/issues/216

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: eog 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 23:31:36 2022
  InstallationDate: Installed on 2022-10-27 (33 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

[Ron Simpkin]

@Steve Fatula I resolved my issue with:

sudo loginctl enable-linger 

I'm not sure this is really the correct way to go about it, but it
ensures that everything is there for the user when the cron process
spawns.

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

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

Status in X2Go:
  New
Status in Xpra Terminal Server:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in x2goserver package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New

Bug description:
  I just upgraded from hirsute to impish using do-release-upgrade. On
  the upgraded system, I can't run either firefox or chromium (both of
  which worked fine under hirsute). Both fail with:

  /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
  NNN is my uid

  With firefox, I was able to fix the problem with:

  snap remove --purge firefox
  apt purge firefox
  apt install firefox

  Now firefox works. But I tried the same thing substituting chromium-
  browser for firefox, and it didn't help: chromium fails with the same
  error message.

  I guess there must be something left over from the hirsute version of
  snapd that isn't getting noticed or cleared by the impish version?

  Someone suggested this might be related to bug 1850667, but that bug
  is marked fixed as of a couple months ago, and I just did this upgrade
  today. Also, it doesn't mention the error message I'm seeing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snapd 2.53+21.10ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 18 18:12:45 2021
  InstallationDate: Installed on 2020-04-29 (568 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)

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


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

[Touch-packages] [Bug 1998263] Re: JPEG ( backing store not supported ) : many pictures won't open.

[Daniel van Vugt]

Sounds like the bug only exists in gdk-pixbuf 2.42.9 (Ubuntu 22.10) ...
https://gitlab.gnome.org/GNOME/eog/-/issues/255#note_1534033

** No longer affects: gnome-shell (Ubuntu)

** No longer affects: gnome-control-center (Ubuntu)

** Also affects: gdk-pixbuf (Ubuntu)
   Importance: Undecided
   Status: New

** Bug watch added: gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues #216
   https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/216

** Also affects: gdk-pixbuf via
   https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/216
   Importance: Unknown
   Status: Unknown

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Confirmed

** Changed in: gdk-pixbuf (Ubuntu)
   Status: Confirmed => Fix Released

** Tags added: fixed-in-gdk-pixbuf-2.42.10 fixed-upstream

** No longer affects: eog (Ubuntu)

** Bug watch added: gitlab.gnome.org/GNOME/eog/-/issues #255
   https://gitlab.gnome.org/GNOME/eog/-/issues/255

** Also affects: eog via
   https://gitlab.gnome.org/GNOME/eog/-/issues/255
   Importance: Unknown
   Status: Unknown

** Also affects: gdk-pixbuf (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: gdk-pixbuf (Ubuntu Lunar)
   Importance: Undecided
   Status: Fix Released

** Changed in: gdk-pixbuf (Ubuntu Jammy)
   Status: New => Invalid

** Tags added: rls-kk-incoming

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

Title:
  JPEG ( backing store not supported ) : many pictures won't open.

Status in Eye of GNOME:
  Unknown
Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Jammy:
  Invalid
Status in gdk-pixbuf source package in Lunar:
  Fix Released

Bug description:
  Hi,

  22.10. Just try to open some .jpg files from my usual storage.

  Error interpreting jpeg file ( Backing store not supported. )

  Those same pictures open in other OSes ( 22.04, 20.04 and else. )

  Can't use those pictures as backgrounds.

  But able to open them in Gimp or Shotwell.

  Maybe related to : https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/issues/216

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: eog 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 23:31:36 2022
  InstallationDate: Installed on 2022-10-27 (33 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1995329] Re: [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but immediately (4-5 secs) disconnect

[Daniel van Vugt]

** No longer affects: bluez (Ubuntu)

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

Title:
  [HP EliteBook 840 G8] [Intel AX201] Devices pair and connect, but
  immediately (4-5 secs) disconnect

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Recently upgraded to 22.10 (from I believe 20.04, not actually
  completely sure) and both of my Bluetooth devices have stopped
  working.

  They can pair and connect initially, but disconnect after 4-5 seconds.

  My headphones worked a while, but have not since been able to have
  them stay connected.

  Here's an output from bluetoothctl, which doesn't say much?

  Agent registered
  [CHG] Controller 10:3D:1C:43:3B:C6 Pairable: yes
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Controller 10:3D:1C:43:3B:C6 Discovering: yes
  [NEW] Device CB:78:4F:E1:45:7D LE_WH-1000XM4
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D TxPower: -21
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 40 d5 00 00 00  ...1..t@
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 87 04 02 48 e2 09 0e 30 0b 11 7a   .H...0..z   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -39
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [NEW] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 88 b5 06 90 44 00 8d e6 00 11 30   ..D.0   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device 94:DB:56:4F:20:7F Connected: yes
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device 94:DB:56:4F:20:7F Connected: no
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [bluetooth]# 
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Key: 0x012d
  [CHG] Device CB:78:4F:E1:45:7D ManufacturerData Value:
04 00 01 31 05 01 74 84 12 86 04 60 d5 00 00 00  ...1..t`
00 00 00 ... 
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Key: 
fe2c--1000-8000-00805f9b34fb
  [CHG] Device CB:78:4F:E1:45:7D ServiceData Value:
00 90 14 08 8e 2b 3a 42 02 89 00 11 74   .+:Bt   
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -35
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -36
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [DEL] Device D9:A2:A2:B7:40:35 P mesh
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -38
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37
  [CHG] Device CB:78:4F:E1:45:7D RSSI: -37

  

[Touch-packages] [Bug 1998470] Re: re-add s390x vectorized crc32 support to zlib in lunar

[Frank Heimes]

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

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

Title:
  re-add s390x vectorized crc32 support to zlib in lunar

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in zlib package in Ubuntu:
  Fix Committed

Bug description:
  At the beginning of Nov a new zlib version (1:1.2.13.dfsg) got merged from 
Debian sid to Ubuntu lunar.
  At this time it was already clear that this new version is no longer 
compatible with patch 
d/p/lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
  since this depends on zlib upstream PR 335 which has been superseded by 
upstream PR 478 with significant refactoring.
  Hence this patch was dropped and it was decided to backport (or better 
'forward port'?) this vectorized crc32 implementation for s390x.
  https://launchpad.net/ubuntu/+source/zlib/+changelog

  The new patch is now available as
  crc32vx-v4: "s390x: vectorize crc32"
  https://github.com/iii-i/zlib/commit/05710d5fb8eb1447289ebf11109e149ece95d839

  This LP bug is now to track the re-integration of the vectorized crc32
  implementation for s390x.

  So a few things needed to happen (from the changelog):
    * Re-add vectorized crc32 support for s390x by adding
  d/p/s390x-vectorize-crc32.patch
  (crc32vx-v4: s390x: vectorize crc32).
  This replaces the previously dropped patch:
  lp1932010-ibm-z-add-vectorized-crc32-implementation.patch
    * Remove option '--crc32-vx' for s390x in d/rules, that was previously just
  commented out, since it's no longer needed with the new s390x crc32 code.

  And since I bumped into a little build issue, I've also needed to:
    * Update d/p/410.patch to version 26f2c0a4e17e5558d779797d713aa37ebaeef390
  due to unused "const char *endptr;".

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


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